Related
Ok I am annoyed with the other thread of people scamming money for something that can be done for free
Here are the tools you need to unlock your diamond for free - when you are finished you will have a SECURITY UNLOCKED and SIM UNLOCKED diamond.
----------------INSTRUCTIONS------------------
FULLY CHARGE YOUR PHONE, CONNECT IT TO ACTIVE SYNC ON THE PC
STEP 1: - HardSPL unlock
Run ROMUpdateUtility.exe from folder STEP1, allow the flash and reboot and let it finish all its tasks on first boot
STEP1.b - Now Make sure you have downgraded your radio version to a version below 1.02.XXX - If your radio is already below 1.02.XXX, then continue to STEP 2 - if not, then downgrade the radio now FROM INTERNAL STORAGE FLASH, and then continue to step 2
STEP 2: - Radio Unlock
Run DiamonCustomRUU.exe from folder STEP 2, allow the flash, and reboot and let it finish all its tasks on boot
STEP 3: - Sim and Security Unlock
Copy DiamUnlock.exe from folder STEP 3 onto the the 4GB storage card of the phone, now goto file explorer in the phone, and run DiamUnlock.exe, it will open up the options to SIM UNLOCK and SECURITY UNLOCK - tick these boxes and press UNLOCK
If all is well it will say UNLOCKED, now reboot your phone with any simcard in, YOUR DIAMOND IS NOW UNLOCKED !
(Older versions of DiamUnlock.exe closed very quickly and you had to try many times to click on the unlock buttons, I have included the fixed version I think that does not close quickly and should be very easy to unlock)
Download Unlocking Tools
http://rapidshare.com/files/411854232/DIAMOND_UNLOCKER.rar
Buy me a Coffee / Pint if this helped unlock your Diamond !
REPLY
Post with a reply if you successfully managed to Unlock your Diamond using these tools
I used the same tools some time ago. Not these ones specificly, but the steps are the same and the programs seem to be identical. I still had to use the older version where the program closed very quickly, but I managed to do it.
Good luck to you all.
I cant pass step 2... it says flashing error and i cat boot win mobile... then i flash step 1 again and boot. But i cannot execute unloker because step 2 is not complete. Any idea?
Hi,
Step 2 stop with error 226 flash write.
axisminden said:
Hi,
Step 2 stop with error 226 flash write.
Click to expand...
Click to collapse
Downgrade your radio to radio 1.00.25.05 before unlocking
RADIO
Yes you must have a radio version below 1.02.XXX
If you need to downgrade your radio, then Perform Step 1 first (HardSPL)
Then downgrade your radio to below version 1.02.XXX
Then continue with Step 2 and then Step 3
magicdave26 said:
Yes you must have a radio version below 1.02.XXX
If you need to downgrade your radio, then Perform Step 1 first (HardSPL)
Then downgrade your radio to below version 1.02.XXX
Then continue with Step 2 and then Step 3
Click to expand...
Click to collapse
I perform step 1, no problem.
I try to change radio to v1.00.25.05 but i get same error 226.
So, i cant perform step 2.
EDIT: I downgrade radio from internal storage succesful, then step 2 works ok, and step 3 ok. Thanks!
aplqq said:
I perform step 1, no problem.
I try to change radio to v1.00.25.05 but i get same error 226.
So, i cant perform step 2.
Click to expand...
Click to collapse
yes it has come same error while flshing process
sorry,
stupid question.
after that all, i can upgrade radio or install a other Rom without delete the unlock?
greetings
michael
EDIT : I perform step 1-3, no problem., i think radio upgrade does not work, because Radio Version is 1.20Olinex.
Now i will try any other SIMcard
aplqq said:
I perform step 1, no problem.
I try to change radio to v1.00.25.05 but i get same error 226.
So, i cant perform step 2.
EDIT: I downgrade radio from internal storage succesful, then step 2 works ok, and step 3 ok. Thanks!
Click to expand...
Click to collapse
No problem
Ok so flashing from the internal storage is a better solution for the radio
axisminden said:
sorry,
stupid question.
after that all, i can upgrade radio or install a other Rom without delete the unlock?
greetings
michael
EDIT : I perform step 1-3, no problem., i think radio upgrade does not work, because Radio Version is 1.20Olinex.
Now i will try any other SIMcard
Click to expand...
Click to collapse
Radio 1.20Olinex is the unlocked radio you need for Sim unlock
Once you perform sim unlock, you can flash a new radio of your choice and simlock and security lock will stay UNLOCKED
Yes, you can.
It works.
thank's a lot
michael
axisminden said:
Yes, you can.
It works.
thank's a lot
michael
Click to expand...
Click to collapse
No problem
Free is good
Bump
Bumping this guide
Hahaha, how do you know if a particular phone is already irrelevant? When moderators don't care about their scams any more on that particular model.
Threads like this used to be locked and banned immediately on sight back in the day, so that moderators and their friends could scam people for $$$ cash. Anyone who posted tools or links to methods on doing it for free, within the hour they'd disappear.
leonatan25 said:
Hahaha, how do you know if a particular phone is already irrelevant? When moderators don't care about their scams any more on that particular model.
Threads like this used to be locked and banned immediately on sight back in the day, so that moderators and their friends could scam people for $$$ cash. Anyone who posted tools or links to methods on doing it for free, within the hour they'd disappear.
Click to expand...
Click to collapse
Well... a google search brings these tools up pretty quickly anyway so I guess it would be pointless to close this thread
Just thought Id stick it all together in one place for people who havent yet managed it
WORKKKKKSSSSS HAHAAAA !!
thanks man !!!!!!!!!it bores me to see that some guys here resorted to extortion to propose a so-called help to unlocking a device!
i dnt want to lose money for stupid things on this forum, the govt of my country f**ks me enough this way
courtax92 said:
WORKKKKKSSSSS HAHAAAA !!
thanks man !!!!!!!!!it bores me to see that some guys here resorted to extortion to propose a so-called help to unlocking a device!
i dnt want to lose money for stupid things on this forum, the govt of my country f**ks me enough this way
Click to expand...
Click to collapse
Haha I know, thats why I made this thread, free world FTW lol
I'm happy to read that this program works! I unfortunately payed for a code (wrong code) for my HD, and even now i found only people who ask me money, but i want to be sure first! ... now i'm here (in the wrong forum i know) to ask you a solution for me! I would like to use my HD....and not my old NOKIA!!
Byeeee
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. I have been trying to unlock this phone for 2 days now!
Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well my code is 16 numbers long. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same.
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Tread3r said:
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. For purposes of convenience and time (I have been trying to unlock this phone for 2 days now!) I will post my IMEI code here ( 3529000059203526 ) and the unlock code given to me by sony through email (61CAA387DC11C4CF).
I hope this doesnt break any rules or anything.
I am doing this to see if anyone here can help me. Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well as you can see my code is 16 numbers long, so in effect I only entered up to number "5". I would like to know if anyone is willing to test my IMEI and see if they get the same code. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key, this is why I am posting. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same (as above).
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Click to expand...
Click to collapse
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Thanks for the advice, I will edit it ASAP.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Hey he removed the imei number from his original message but that's pointless unless u remove it from your quote
Sent from my Xperia S using xda app-developers app
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Chriszo said:
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Click to expand...
Click to collapse
Glad to hear im not alone . No I still haven't found a way to unlock it. Sorry for asking but what does "PN" mean? Just so we are clear.
Ok thanks for your answer. No problem, but its just a mistake. Correctly it should be "PM" for personal message. I thought you would write on this way so I cant read any reasults
UPDATE:
I have tried other processes that all have the same steps, be it they were simplified programs with GUI's. I have come to the conclusion that my fastboot driver was installed incorrectly, because the first time I installed it on my phone I was able to see the S1 bootloader icon on device manager and I was able to click on it fast enough to enable it to install the driver. And correct me if im wrong but when we press UP on the volume rocker on our XS's and connect it to the USB we should see a blue right light? Well that is what happens when I do it so I assume I installed it correctly then.
Now after these first few failed attempts at unlocking I got frustrated and just factory reset my phone, completely ( I made back ups of course). This time however I used a program which is suppose to install all the drivers and simplify the whole unlocking process, I dont remember what program exactly, i'll check my files and get back to you guys on that.
Again it failed, showing the FAILED ("oem" error message) so I checked the steps from Doomlords guide and re checked my device manager. This time when I connect my phone it doesnt show the S1 bootloader icon on Dev manager, instead it shows "android phone ADB Interface". BUT I still get the blue LED when I connect my phone via USB, so does that mean I have fastboot on my phone again? ( I assume I do because the program I used says it did install it correctly and it even showed the "install anyway" window)
I am almost loosing all hope to unlock my XS , maybe I got a lemon phone or did something wrong again. I am willing to do another factory reset and restart the whole process again. This time I will follow every single step on the official website and see what happens.
But before I do that I want to ask, does anyone know of any news or whereabouts for an unofficial unlock bootloader process? I know its a long shot because we already have an official way but as from recent experience it doesnt work 100% of the time.
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Chriszo said:
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Click to expand...
Click to collapse
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Tread3r said:
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Click to expand...
Click to collapse
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
It was AOKP, the advanced project for this device.
I think your right, but in how far is the bootloader linked to the needed kernel? And why cant the bootloader be unlocked several times...?
Of course the kernel is a main part of the rom, but without an unlocked bootloader even the kernel would not be accepted by the bootloader. Thats the problem with other firmwares/ roms why you have to unlock it
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
razormc said:
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
Click to expand...
Click to collapse
I am using Windows 7 and I have used flashtool. I believe the drivers are correct because,as you said, the blue LED does show and stay while I fastboot my phone. Same goes for the green LED when I go to flashboot.
Chriszo said:
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
Click to expand...
Click to collapse
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Tread3r said:
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Click to expand...
Click to collapse
First, unlock your bl. Then root. I done that on my old Arc S and it works great.
Sent from my LT26i using xda developers-app
@ Tread3r:
Yes the drivers are installed correctly, because the phone starts into fastboot and flashboot with each the right light.
Thats the great problem with our devices. I did it nearly the same way and Ive got a similar problem, as the first answers describe in this post. Actual the original stock rom is installed on my Sony and all works correctly, but its just a short-term workaround
The bootloader unlockind process still end in an error message and that is my problem.
@ Vatih:
Nice try, but this is our problem... :/
---------- Post added at 11:41 AM ---------- Previous post was at 10:57 AM ----------
I cant believe it myself, but the alternative way works, althought I cant read anythink in the tool because of the language...
I've got the superuser app and root permissions and all works.
This link helped me: http://forum.xda-developers.com/showthread.php?p=39498268
It's the tool for the "new" firmware, .55, the latest from sony.
Hope, its also succesfully with your devices
I solved our problem. My bootloader is now open
I did it with the unlock, flashtool tool of this forum that helps you to open the bootloader and flash kernels and roms.
http://forum.xda-developers.com/showthread.php?t=2087337
Seems like just the code was wrong.
It worked with the first try
But be careful, although its just the bootloader, all data will be deleted. My phone is empty again :/ Of course I've got some backups...
hello guys
need yout help, tried searching google for sulotion but came up empty.
ive rooted the lg g4 h815(android 6.0-V20c-SEA) before via iroot pc but after factory reset its returned to be unrooted.
when i try to root again its keep failing because of debugging issue (the software keep telling me its not in debugging altough it is)
i think the problem is when i do usb debugging - connecting to pc the option is checked in the check box but it turns gray.whats the problem is? how can i fix it ?
thank you in advance
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, if the the G4 Factory Reset protocol deletes the system partition, and then reinstalls it, then this would explain why/if you lost root, I do not know if that's the protocol though. If iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
I recommend wiping Data, Cache and Dalvik from TWRP next time, if that's not what you did this time. :good:
Williquah said:
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, although I've never heard of that, if iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
Click to expand...
Click to collapse
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
mikmikush said:
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
Click to expand...
Click to collapse
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Williquah said:
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Click to expand...
Click to collapse
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
About phone ????
mikmikush said:
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
Click to expand...
Click to collapse
Sorry for forgetting the whole reason you're in this problem is because of a factory reset lol, of course you have your data backed up. And trust me, I understand about the brick, I really messed up my G3 2 years back. Thanks also for the device pictures, could you post a shot of "About Phone=>>Software Info". That would be great!
Funny thing I just did that same phone rotation thing very recently XD
Lol love rotation, here
mikmikush said:
Click to expand...
Click to collapse
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Williquah said:
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Click to expand...
Click to collapse
Thank you thank you! You are awesome.
I will follow the links later and reply ...
I will ???? thank you
@mikmikush You're welcome, my pleasure!
Williquah said:
@mikmikush You're welcome, my pleasure!
Click to expand...
Click to collapse
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
its like my problem?
what did u do?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
H815 SEA?/Same software version and error?
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
htr5 said:
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Click to expand...
Click to collapse
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Williquah said:
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
H815 SEA?/Same software version and error?
Click to expand...
Click to collapse
Williquah said:
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Click to expand...
Click to collapse
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
mikmikush said:
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
Click to expand...
Click to collapse
Trust me, I understand your frustration, I'm going to make a guide for you in the next 6 hours or so.
Try a different computer if you can, I haven't had adb fail but many other tools sometimes work
on different computers for me. I've also heard "Dell PC Suite" should be uninstalled as it could cause adb hang ups,
if you have it. @htr5's guide might work for you if you have a software update available, I'm not sure though since it's not specifically for your device.
Regardless, I'm sure you will need to use adb soon, so we have to fix that.
I will try to make that guide asap, I obviously can only do so much, again, since I don't have your device, hopefully it will help though. I highly suggest trying on a fresh/different computer though.
Edit: Try USB 2.0 if you were using a 3.0 port (3.0 ports have the SS along with the usb "logo")
USB 2.0 is on the right:
"H815 SEA Root/General Guide"
@mikmikush
It does seem that you can treat your SEA device very similarly to the EU common version, in ways such as flashing KDZ's and rooting.
I cannot confirm this, but mentions in this thread: http://forum.xda-developers.com/g4/help/safe-root-h815-v10b-sea-variant-t3184152 make it seem like it should be okay.
Aoi_sora9x said:
I'm a SEA variant holder here.
It's fine, you can use the Low Effort Root method. You can also flash the EU open KDZ without any problem.
You lose VoLTE, but to me it doesn't matter so I don't really care.
I'm running the latest 10E ATM, and it's much much better than 10B, so flash away.
Click to expand...
Click to collapse
Yes, that post is for v10b, but it should also work for v20d/v20c. (Not the Low Effort Root method) - You will be working with EU software v20d.. while you are with SEA v20c,
so it's up to you if you want to try this, but it's the closest I can come right now. Thank @htr5 because I believe he has all of this in his guide, and I'll probably send you to his guide halfway through.
You may lose some features or brick your device by flashing firmware/software made for other devices. Trust your instinct!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install adb setup from here this includes necessary adb drivers, adb itself, and fastboot.
2. Install LG Mobile Driver
3. Download LGUP tool from here (This is for restoring your device to stock if you softbrick via KDZ)
Follow this thread if/when you need to.
4. Here contains a KDZ for EU v20C, which I'm 99.9% sure will match your current software, even though it says for EU.
5. Here contains every partition including the KDZ for 20d by @autoprime, which will be necessary if you decide to root from @htr5's guide (v20d Root Method)
6. Once again, try to unlock the bootloader officially through LG, if you are successful, you can follow @htr5's 20d Root Guide here
7. Be careful and let me know how it goes
@autoprime Mentions that there is "NO anti-rollback qfuse used in this update" (20d) so if you flash the 20d KDZ and it works, I believe you should then be able to downgrade successfully to an earlier firmware version - without worrying about qfuse - and root using a Lollipop (5.0/5.1) method if you can't get anywhere on Marshmallow (6.0). - This I'm not 100% positive about, again, but it is my thinking.
Please thank anyone I mentioned and anyone who's link I provided, they all deserve it!
Hi all.
IMPORTANT S7 T-Mobile and S8 T-Mobile are Qualcomm based and MY METHOD DOES NOT WORK. I WILL UPDATE WHEN/IF IT DOES
UPDATE 27.01.2018
MAGISK........
I am having trouble unlocking on phones with Magisk installed for ROOT
Nothing against Magisk, I personally use and love it. Feel free to install this AFTER UNLOCK
I'm just having trouble with the unlock using Magisk.
I am offering a free unlock via
I will still gladly accept any donations that come my way via PayPal ([email protected])
But DONATION is 100% OPTIONAL
All i ask is RESPECT and PATIENCE. (if these are not given then I may CHOOSE not to help you)
Remember this is taking time away from my wife and family to help YOU!
This is a FREE remote unlock service. AT YOUR OWN RISK.
No, I will not share my method..... as it could get patched by Samsung.
Here we go........
SEE CURRENT SUPPORTED MODELS AND FIRMWARES HERE
F.A.Q
Q. What if my IMEI is bad or blacklisted?
A. There are a few times of blacklist... T-Mobile seems to block INTERNAL only if non payment. Others will block if non payment or lost/stolen.
This does not effect SIM unlock, I can do it regardless.... However, you WILL NOT GET NETWORK SIGNAL IF BLOCKED
Check here for T-mobile https://www.t-mobile.com/verifyIMEI.aspx and also here for all models http://imei24.com/blacklist_check/
If you are not sure ask first!
Q. Can you change/repair my IMEI?
A. HELL NO. This is not only against XDA Rules but it is illegal in most countries, including mine.
Q. Is this really free?
A. Yes, although I do hope for a donation for my time and effort
Q. When are you available?
A. See below.
Q. Can we get on with it all ready?
A. Yes!
Remote Sim Unlock Preparation
Contact
Please be considerate of my time zone this it GMT +03 (UTC +13), check here NZDT https://www.timeanddate.com/time/zones/nzdt I am usually available after work 5PM until 8PM.
I am also available some weekends. Leave me a message on hangouts here with [email protected] and i will get back to you ASAP.
Please contact me when you are ready after reading below. Contact [email protected] via Google Hangouts.
If you do not have a reply within 24 hours then please email me with your gmail address on [email protected] and I will add you to hangouts.
Google Hangouts is needed so you can follow directions as I unlock your device. Everyone with a Google accounts has Google Hangouts.
You can access it via hangouts.google.com
Phone Settings ALL Models
Disable FRP by enabling OEM UNLOCK
http://techbeasts.com/how-enable-oem-unlock-android-lollipop-marshmallow/
Enable USB debugging
https://forum.xda-developers.com/fire-phone/general/guide-enable-usb-debugging-setup-t2859697
Revoke USB authorization (if applicable)
Developer Settings > Revoke USB authorization
GSM Only
Phone dialer > *#0808# > USB = AP
Phone dialer > *#0808# > USB SETTINGS = DM + ACM/MODMEM + ADB (note, will say ACM or MODEM)
If and only IF the above doesn’t work then try:
Developer Settings > USB Configuration > RNDIS (USB Ethernet)
SPRINT Only
Phone dialer > ##3424# >Qualcomm USB settings > DM + ADB + Modem
If the above asks for MSL or doesn’t work then try:
Developer Settings > USB Configuration > RNDIS (USB Ethernet) then we can get MSL to enable the above if you need MSL
For those that don't know... the 5th to last digit in the firmware is the BOOTLOADER (BL) version. YOU CAN'T GO BACK!!
i.e G920TUVU5EQC2 the BL version is 5 so you can't flash anything less than BL version 5
PC
You will need a Windows PC for the software. Please ensure you have Windows 7 or newer
Windows Vista and XP are NOT RECOMMENDED (for anything lol).
Please download FlexiHub http://www.eltima.com/wiki/user-guides/flexihub-windows/installation.html and install on your PC.
Please reboot after install.
Please create a FREE flexihub account here https://flexihub.eltima.com/user/registration/ AFTER ENTER DETAILS, YOU WILL SEE A PAYMENT PAGE... CLOSE WINDOW NOW. FREE ACCOUNT ALREADY CREATED
Or I have a few accounts if you wish to use one just let me know.
Please have FlexiHub open and logged in.
Unlocking Process
When you have contacted me and I have replied that we are ready you may proceed to:
Open flexihub and log in to your account
DO NOT SEND COM PORT. THIS IS USELESS TO ME ALONE
If needed click 'UNLOCK' on the phone's driver so it can be accessed (i.e Samsung_Android OR Gadget_Serial OR MSMxxxx)
Right click on your phone's driver in flexihub(i.e Samsung_Android OR Gadget_Serial OR MSMxxxx) and click send invite.
Type in [email protected] and click OK.
I will connect to the device and proceed from there.
Please watch phone for USB Authorization prompt.
Check the box then press OK.
I will disconnect and reconnect as required (using FlexiHub).
Watch phone Screen for SU (ROOT) prompt and press GRANT.
All you need to do is watch the phone for USB Authorization and ROOT grant.
Please follow the instructions I send via Google Hangouts
After we are finished you can return your device settings to as they were and you can remove FlexiHub from PC.
Please kindly donate via PayPal to [email protected] (once again 100% optional)
I appreciate the unlock you did for me over a year ago, and i personally think its awesome that youre putting this out there for folks to get their phones unlocked mate!! Very nice work sir. Keep it up!! Question for ya tho, the process to unlock something like an S5, it requires a piece of hardware that youre using on your end, correct?
youdoofus said:
I appreciate the unlock you did for me over a year ago, and i personally think its awesome that youre putting this out there for folks to get their phones unlocked mate!! Very nice work sir. Keep it up!! Question for ya tho, the process to unlock something like an S5, it requires a piece of hardware that youre using on your end, correct?
Click to expand...
Click to collapse
S5 T-Mobile? No idea. I think it's Qualcomm based and all the hardware unlocks are only for Exynos T-Mobile. Hence no support for S7/S8 T-Mobile too
Successfully unlocked my T-mobile s6 edge after i tried for days. Worked like a charm. I love this guy. I offered him sex but he politely declined. Pay this guy for his time!
Edit: Paid! sorry it took 6 hours. errands. and no it was not demanded. donated.
Invite sent
SM-G925T
Hi guys, just bought a phone which is sm-G925t and its unlocked (dont know how to unlock it since bought i can use other simcard) i cant install update OTA, just trying to ask, if i flash a firmware to nougat (latest t mobile firmware in s*mmobile.com) will my phone locked again?
Heres my phone baseband
G925TUVU5EPK5 ( i installed gold eagle rom i dont know if its affect the baseband or not)
Looking forward for answer
Thanks guys
Mkhrdn said:
Hi guys, just bought a phone which is sm-G925t and its unlocked (dont know how to unlock it since bought i can use other simcard) i cant install update OTA, just trying to ask, if i flash a firmware to nougat (latest t mobile firmware in s*mmobile.com) will my phone locked again?
Heres my phone baseband
G925TUVU5EPK5 ( i installed gold eagle rom i dont know if its affect the baseband or not)
Looking forward for answer
Thanks guys
Click to expand...
Click to collapse
Have same problem n same question hope i can find answer soon
stifilz said:
S5 T-Mobile? No idea. I think it's Qualcomm based and all the hardware unlocks are only for Exynos T-Mobile. Hence no support for S7/S8 T-Mobile too
Click to expand...
Click to collapse
.can you help me unlock s6. From boost. I got hit by a truck and my phone broke. I don't trust people online. But xda always. Boost to mobile. ? Please. Lmk
Hey guys, I just noticed in his original post stifilz mentions there not being a direct unlock for the s7 frmo tmobile but there is a service that does instant usb unlocks on T-Mobile S7 and edge variants. Unfortunately its a paid service and expensive but i have used and know for a fact it works and isnt a server side unlock. If you guys want info just inbox me. I dont want to hijack stifilz thread much other than to say there are definitely hardware/usb unlocks available for T-Mobile S7 variants (ATT and it's S7 active too)
Still offering this guys
This guy is great. It was a struggle because my system was antiquated and my internet is slow, but he managed to GSM unlock my SM-G900P Galaxy S5. I sent a donation.
Im still doing this been very few at the moment :/
Directions Unclear. I've created a black hole, and we're all screwed.
Forgive me, if I'm being particularly dense, but I'm a little unclear about this whole process. Is this Flexihub business mission critical? Or is it just one of the available options. The reason I'm asking is that I can't easily get access to a PC. Is this a deal breaker, or is an alternative available? As far as I can determine, access to a PC is the only qualification that I'm lacking.
Thanks for the effort you must be putting into providing such a generous service
ExidusElectric said:
Forgive me, if I'm being particularly dense, but I'm a little unclear about this whole process. Is this Flexihub business mission critical? Or is it just one of the available options. The reason I'm asking is that I can't easily get access to a PC. Is this a deal breaker, or is an alternative available? As far as I can determine, access to a PC is the only qualification that I'm lacking.
Thanks for the effort you must be putting into providing such a generous service
Click to expand...
Click to collapse
Flexihub is my method of connecting your phone to my PC, without it I can't unlock phone....
stifilz said:
Flexihub is my method of connecting your phone to my PC, without it I can't unlock phone....
Click to expand...
Click to collapse
Right... So that means that a PC shouldn't be required on the other end, right? Since it's the mobile device you'd ostensibly be tinkering with?
ExidusElectric said:
Right... So that means that a PC shouldn't be required on the other end, right? Since it's the mobile device you'd ostensibly be tinkering with?
Click to expand...
Click to collapse
Read that again. You need PC.
stifilz said:
Flexihub is my method of connecting your phone to my PC, without it I can't unlock phone....
Click to expand...
Click to collapse
stifilz said:
Read that again. You need PC.
Click to expand...
Click to collapse
Okay, I've done some further reading. It makes sense. Guess I'll just have to surilvive without unlocking.
I'm having a problem, in the settings of my s6 edge the phone model is sm-g925f but the baseband is G925TUVU4 it means the phone is a t-mobile phone and now I want to flash the latest nougat firmware of t-mobile and I want to know if I do so will it lock my phone and I won't be able to use another sim card?
Available
Hey, Are you available still?
Bump.
Still doing this.
Few changes made to thread for clarity,
Mainly........
SEE CURRENT SUPPORTED MODELS AND FIRMWARES HERE
EDL Stock Firmware
Nougat AT&T Z999 B30
Nougat AT&T Z999 B37
Oreo China Z999 2.1
Oreo NTT DoCoMo Z-01K B32
SD Stock Firmware
Nougat Russia Z999 1.1
Oreo China Z999 1.11
Nougat China Z999 1.11 Fallback Pack
Oreo China Z999 2.10
Firehose files
AT&T Z999 Firehose (Extract with 7zip) Might work with the China Z999 but unknown
NTT DoCoMo Z-01K Firehose (Extract with 7zip)
TIM Z999 Firehose (Extract with 7zip)
Incomplete pre-production firmware (Do not use)
P996A26V1.0.0B07
P996A25V1.0.0B20
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download the firmware and firehose from above
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_ufs_firehose_8996_ddr.elf file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your phone
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
Mine just in case
Thank u!! Just finding where I can update my att version firmware. I am still on b22. No OTA available. So sad...
Thx for sharing!!
my phone has been unlocked. will it be locked again after flashing??
your advice appreciated......
alhtc said:
my phone has been unlocked. will it be locked again after flashing??
your advice appreciated......
Click to expand...
Click to collapse
I am assuming you mean sim unlocked, if so I haven't ever seen it be relocked by flashing the device back to stock. But I can't be 100% for this device.
i followed up to no.9 Plug in your phone
but nothing happened...
shall i boot in bootloader mode?
i boot to recovery but after choosing bootloader mode, the phone just reboot and go into android...
---------- Post added at 02:03 PM ---------- Previous post was at 01:43 PM ----------
i also tried factory test mode. and the phone can be identified in QFIL
when i run adb command "adb reboot edl",
it shows:
* daemon not running. starting it now *
CreateProcess failure, error 2
* failed to start daemon *
error: cannot connect to daemon
Thank you!!
Thank you so much for your huge contribution!!
This opens a door to many possibilities!
Once again, thank you!
alhtc said:
i followed up to no.9 Plug in your phone
but nothing happened...
shall i boot in bootloader mode?
i boot to recovery but after choosing bootloader mode, the phone just reboot and go into android...
---------- Post added at 02:03 PM ---------- Previous post was at 01:43 PM ----------
i also tried factory test mode. and the phone can be identified in QFIL
when i run adb command "adb reboot edl",
it shows:
* daemon not running. starting it now *
CreateProcess failure, error 2
* failed to start daemon *
error: cannot connect to daemon
Click to expand...
Click to collapse
Plugging in your phone isn't meant to do anything itself you need a working adb install so you can then do adb reboot edl to get into the proper mode. Ftm is not the proper mode.
deadman96385 said:
Plugging in your phone isn't meant to do anything itself you need a working adb install so you can then do adb reboot edl to get into the proper mode. Ftm is not the proper mode.
Click to expand...
Click to collapse
thank u for the reply!
can you give more hint on how to do a working adb install??
i have tried some methods but seems doesn't work...
i also tried to enter EDL by pressing vol + & - and power button. and try download the firmware but failed too.
have been trying different version of adb driver...
usb debugging unlocked.
different type C cable.
different PC.
but still having the following results:
* daemon not running. starting it now *
CreateProcess failure, error 2
* failed to start daemon *
error: cannot connect to daemon
really want to update the Axon M to make it usable again. it's laggy and poor camera in this early firmware.
Can I ask a stupid question?
Can I install firmware update by SD card? I see the option but I don't have the resources....
can flash china rom to japan phone ??, last time i can flash att rom to china phone but signal bad and lost 1 sim
Alright so I'm not sure what I'm doing wrong. I keep getting various errors such as; Expecting SAHARA_END_TRANSFER but found: 0, didn't revive hello packet, or rx_data:247 Error occurred while reading from COM port. The error is just different based on what application. I've tried QFIL, the ZPST in your MEGA folder, MiFlash, and a modified version of the Axon 7 EDL tool. All give errors, unless I use my Axon 7 witch I am able to fully control in EDL mode. I think the basic problem is my Axon M can't be accessed, and I'm not sure what I'm doing wrong there. Any advice?
AT&T AXON M update issue
Hello Deadman 96385 thank you for your guidance . I have been looking for info to update my axon m (att version) and i downloaded all files and drivers that you provided. The first issue is one of the drivers which is this ZTE_V889F_V880G_V955_A2_Drivers . I extracted zip file and installed other drivers but i couldn't install this driver ZTE_V889F_V880G_V955_A2_Drivers . I believe i'm doing something wrong or i miss something. One another issue is after step 8 . Should i go into FTM mode to start process ? Adb gives an error such as deamon not started or running etc.. For sure we missed something . Can you explain this part a bit detailed if you have some time ? I will be appreciated if you can guide us in this part.
Thank you
Have a nice day
Thanks for the huge contribution. Is it possible to flash Chinese ROM on the AT&T phone. thanks
Please somebody help me to beat that " sahara fail " . Trying to update ZTE axon m (at&t z999). I installed all necessary drivers and files. QPST as well and still getting sahara error. Sahara failed , sahara failed , sahara failed . My phone is going to explode soon. Booted phone maybe 100 times to edl mode . everything is fine but that sahara ruins everything. I cannot update the phone. Windows 10 64 bit installed all drivers provided by developers but cannot flash rom. I have done research but there was no specific info regarding that getting" sahara fail error ". I just do not understand where did i go wrong ? if there is anyone who can help with this ???
Thank you
wta
which firmware should i download ?
the sd ones ? or the edl ones ?
just to be sure, if u have the time pls read my explanation, and pls tell me if I'm doing right or wrong (while I'm downloading the firmware files about 2 hours)
I just got at&t zte axon m (I live in indonesia)
it's unlocked (I could use my simcard to phone, and edge is working)
but I want to use 4G and tethering (which not working atm), and at&t messages backup & sync often nags me to put at&t number when I'm doing anything like changing the setting, etc.
so I think I want to upgrade the phone to oreo with chinese (would this remove that annoying at&t messages backup & sync) and hopefully makes my 4G and tethering working (if not then as long as my call working like now then it's ok too) and hopefully the battery would be better (read that oreo battery management is far better than nougat).
I would prefer to use cn 2.2 firmware as it has got the google play back (from what I read cn 2.1 remove the google play ?), but can't find it anywhere, and ur guide here seems to be the most detailed one. so I think I would gamble with cn 2.1 firmware (that maybe would let me update from setting to cn 2.2 ?)
what do u think ? would this work ?
if not pls warn me right away
thx in advance
oh and 1 more think. which firehose file should I use ? for now I downloaded the at&t one. or should I use the other ?
edited again :
found my answer.
so there was someone already trying and break his zte axon m. phew, I almost got to the last step, and was just trying to find how to boot into edl mode and found this :
https://forum.xda-developers.com/axon-m/help/bricked-edl-mode-t3844487
Hello myfire888 , according to my knowledge you cannot flash custom roms or custom recoveries to AT&T devices unless you unlock their bootloaders. I have an AT&T AXON M as well . I got it a month ago and it is 4G/LTE support. Phone is good but as i said we cannot flash custom roms on AT&T devices or unlock bootloaders. I've done a research and there is no way to unlock bootloaders of at&t devices(thsi is what i know so far, maybe there are some people who can do it but not me ). I have a galaxy S7 EDGE AT&T and it is the same like axon m. You need updates from AT&T only . Recently i found AT&T 's updates from xda but i was unable to flash the rom. I installed every drivers and other files and got a sahara error failed many times. I will not buy AT&T devices anymore. They work good but we cannot flash custom roms or recovery . We are lucky that some developers upload these updates on XDA otherwise it is really hard to find them. AT&T does not provide their update on their website. That sucks.
Good luck friend
galaxys2ci said:
Hello myfire888 , according to my knowledge you cannot flash custom roms or custom recoveries to AT&T devices unless you unlock their bootloaders. I have an AT&T AXON M as well . I got it a month ago and it is 4G/LTE support. Phone is good but as i said we cannot flash custom roms on AT&T devices or unlock bootloaders. I've done a research and there is no way to unlock bootloaders of at&t devices(thsi is what i know so far, maybe there are some people who can do it but not me ). I have a galaxy S7 EDGE AT&T and it is the same like axon m. You need updates from AT&T only . Recently i found AT&T 's updates from xda but i was unable to flash the rom. I installed every drivers and other files and got a sahara error failed many times. I will not buy AT&T devices anymore. They work good but we cannot flash custom roms or recovery . We are lucky that some developers upload these updates on XDA otherwise it is really hard to find them. AT&T does not provide their update on their website. That sucks.
Good luck friend
Click to expand...
Click to collapse
phew luckily I havent proceed through the flash yet, or I'll have another brick in my house.
u live in us ? use at&t ? because mine should support 4G/LTE too but only 2G run, and no tethering (well tethering would be useless too even if it can with only 2G)
can't find any chinese axon m on ebay too, so i just bought the at&t unlocked one.
this phone is near perfect, and I'd like to say "who needs huawei mate x and samsung galaxy fold when u have zte axon m" haha
oh well, I have use plan B and using mifi for now. it just not feels good to bring another extra modem.
i'm not living in us but i got the phone from somebody who brought this phone from us . it's sim unlocked not bootloader thats why we cannot flash custom roms. I have the update but i cannot flash it . ZTE is complicated phone to update . i have a samsung at&t and i update without an issue . samsung is easy to update. Before you update your phone do a research regarding your phone's model. Your phone should support 4G / LTE . Did you check network settings ? Mobile networks or network settings . it should say 2G/3G/4G etc.. check it. I cannot find any tutorial or solution to flash update on axon m unfortunately. I downloaded every single drivers but still can't flash it .