Related
I somehow managed to lock myself out of the phone, no boot, no fastboot recovery mode, no access through adb (device not recognized), no nothing. Anyways just looking for assistance in this. I know there must be a way, but I haven't seen anything clear enough to precisely *unbrick* my beloved ASUS Zenfone 2 Laser ZE551KL Z00TD. I've resorted to a Samsung Galaxy S5 that I rebuilt from an old broken ones spare parts. I'm more of a hardware repairer so flashing ROMS and all that is rather new to me. But I was having some success early on when trying to flash CM.13 onto it using ADB and TWRP, which is when the trouble started. I flashed the wrong recovery.img I think and somehow locked myself out completely. I'm not sure exactly what I did wrong, but after many failed attempts to flash CM.13 Marshmallow, I tried to revert back to the stock ROM and then realized that I didn't make a backup recovery.img. Doh! So now I'm completely stuck with a really nice looking paper weight. Please help! :angel:
okay man, if you connect your phone without battery using usb cable to your pc? and device manager shows any newly detected device for a few seconds? try this and reply me...
crossmanx said:
okay man, if you connect your phone without battery using usb cable to your pc? and device manager shows any newly detected device for a few seconds? try this and reply me...
Click to expand...
Click to collapse
I did plug in the device, while the battery was still in it, and it came up as an unrecognized device when the balloon popped up at the bottom right of the PC screen. I unplugged it, took out the battery, and plugged back in, but nothing showed up this time. Although I didn't look in device manager though. But I will try that next. What's your thoughts on helping me solve this issue? I'd really like to learn how the actual company first loads their firmware onto the devices. Like what kinds of software and equipment they use. I'm sure it's on a major scale though and probably have machines doing most of the work, just like an automobile assembly line. LOL. But I really want to get this ASUS Zenphone unbricked. So any help would be awesome. Thanks very much!
thanks man! I think you have to download QUALCOMM drivers! from internet. and install it into your pc. after installing drivers there will be a connection into your device manager when you connect your phone with pc. it maybe QUALCOMM 9006/9008, or QDLOADER or Qualcomm mmc storage. is this shows up into your pc, you are done,, you can push firmware parts into your device using qpst or qfil softwares. I will send you the link for guide.
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
---------- Post added at 10:54 AM ---------- Previous post was at 10:49 AM ----------
try to search"unbrick all qualcomm snapdragon devices" into google and you will find out how to unbrick using qfil/qpst. you have to download stock firmware for your phone.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
give results.
Thanks Man!!! I really appreciate the help. I'll try all this and report back. Thanks Again!
Well I realize it's been awhile, got pretty busy at work, I run a computer and smartphone repair shop.
But I've managed to get as far as getting the right drivers installed under COM PORTS, because it was showing up as RELINK HS-USB QDLoader 9008.
So after uninstalling those com ports drivers by uninstalling the device (you need to click the check box to uninstall drivers).
Then by holding down simultaneously the power + volume up + volume down buttons, while then connecting the usb cable back to the computer.
The device now showed up under other devices in device manager as QHSUSB_BULK. I searched and downloaded the Qualcomm HS-USB QDLoader 9008 drivers and installed them (The download was simply named Qualcomm_USB_Drivers.)
I installed the drivers to the QHSUSB_BULK device by clicking update driver software and then selecting them by browsing to where I saved them, in this case to my desktop. Note: I first had to download the .zip file, then extract that into my desktop folder I just called Firmware and Drivers. The name of the Driver pack I downloaded was called "Qualcomm_Drivers_QDLoader"
Now the device shows up as Qualcomm HS-USB QDLoader 9008 (COM10). I reconnected the device using the same method of holding down the volume up+volume down+power all at the same time with one hand and the other to plug in the micro USB cable that was linked to the PC. But I did this after which I took out the battery for about 20 seconds and placed it back in. This way I could check to see if the device was truly connected at that com port.
I have a plethora of software installed already to include, android debugging tools aka ADB+Fastboot+Tools unzipped using WINRAR to the desktop folder "adb", I also for some reason have AndroidSDKSlim.zip extracted to the desktop which just has the adb and fastboot tools in them. I also have QPST which has QFIL and a lot of other developer tools, and eMMC_DL_Tool_for_customer_ENG_V5.2.0R. I'm thinking I'll be needing these soon, so that's why when searching I just downloaded and installed all of these programs.
I'm at the point now where the phone is plugged in and the COM PORT appears to be open as far as I can tell.
Now I just have to figure out how to get the partitions, stock firmware, and all that back onto the phone so that I can unlock it, root it, load TWRP recovery, and then get it all back to life.
Any suggestions? Anyone? @crossmanx thanks for helping to get me started. Do you know where to go from here? I'm not even sure I have the right ASUS drivers installed, but I think that I do. This should be all I need correct?
Thank you. I'll continue to be as detailed as possible in my steps to recover my *hard bricked "ZE551KL Z00TD". Oh but on another note, I have heard that the stock rom or image recovery for the Asus Zenphone Selfie Z00T may work as well, but I'm afraid to try that. I just want to get this device back up and running with either the stock rom or and update MM rom like CM.13. Cheers!
WormholeMatt said:
Well I realize it's been awhile, got pretty busy at work, I run a computer and smartphone repair shop.
But I've managed to get as far as getting the right drivers installed under COM PORTS, because it was showing up as RELINK HS-USB QDLoader 9008.
So after uninstalling those com ports drivers by uninstalling the device (you need to click the check box to uninstall drivers).
Then by holding down simultaneously the power + volume up + volume down buttons, while then connecting the usb cable back to the computer.
The device now showed up under other devices in device manager as QHSUSB_BULK. I searched and downloaded the Qualcomm HS-USB QDLoader 9008 drivers and installed them (The download was simply named Qualcomm_USB_Drivers.)
I installed the drivers to the QHSUSB_BULK device by clicking update driver software and then selecting them by browsing to where I saved them, in this case to my desktop. Note: I first had to download the .zip file, then extract that into my desktop folder I just called Firmware and Drivers. The name of the Driver pack I downloaded was called "Qualcomm_Drivers_QDLoader"
Now the device shows up as Qualcomm HS-USB QDLoader 9008 (COM10). I reconnected the device using the same method of holding down the volume up+volume down+power all at the same time with one hand and the other to plug in the micro USB cable that was linked to the PC. But I did this after which I took out the battery for about 20 seconds and placed it back in. This way I could check to see if the device was truly connected at that com port.
I have a plethora of software installed already to include, android debugging tools aka ADB+Fastboot+Tools unzipped using WINRAR to the desktop folder "adb", I also for some reason have AndroidSDKSlim.zip extracted to the desktop which just has the adb and fastboot tools in them. I also have QPST which has QFIL and a lot of other developer tools, and eMMC_DL_Tool_for_customer_ENG_V5.2.0R. I'm thinking I'll be needing these soon, so that's why when searching I just downloaded and installed all of these programs.
I'm at the point now where the phone is plugged in and the COM PORT appears to be open as far as I can tell.
Now I just have to figure out how to get the partitions, stock firmware, and all that back onto the phone so that I can unlock it, root it, load TWRP recovery, and then get it all back to life.
Any suggestions? Anyone? @crossmanx thanks for helping to get me started. Do you know where to go from here? I'm not even sure I have the right ASUS drivers installed, but I think that I do. This should be all I need correct?
Thank you. I'll continue to be as detailed as possible in my steps to recover my *hard bricked "ZE551KL Z00TD". Oh but on another note, I have heard that the stock rom or image recovery for the Asus Zenphone Selfie Z00T may work as well, but I'm afraid to try that. I just want to get this device back up and running with either the stock rom or and update MM rom like CM.13. Cheers!
Click to expand...
Click to collapse
asus firmware for your device model is available on asus web site, download that and open that zip file, in that you will find boot.img, aboot or amass or droidboot.img, and also system.img files, and you have to push that into your device using qfil/qpst. i thibk you can do it also by emmc_dl is qualcomm drivers are installed properly and shows up as com_port, u just have to enter comport number and it wish push your files into device..
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
if you only push droidboot img then you will be able to get into the volume+ + power combo mode, so you can get access to fastboot, and after that you know all the procedures....
---------- Post added at 06:14 PM ---------- Previous post was at 06:04 PM ----------
well actually all the qualcomm based devices are unbrickable so sont worry your phone will be live again... you have to just experimenting it on...
well actually i dont have this phone...i am thinking about buying asus ze601kl? is this a good phone? how'z the performance and stability of cm13 snapshot version on your device? is dual sim and all the other things works without any bug? or it has any bug?
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
asus has such funky things in stock boot image as it verifies everytime on boot for valid image, if you have unlocked its bootloader before and try to update its firmware or install stock rom it creates problem. so cm13 is better choice.
crossmanx said:
asus firmware for your device model is available on asus web site, download that and open that zip file, in that you will find boot.img, aboot or amass or droidboot.img, and also system.img files, and you have to push that into your device using qfil/qpst. i thibk you can do it also by emmc_dl is qualcomm drivers are installed properly and shows up as com_port, u just have to enter comport number and it wish push your files into device..
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
if you only push droidboot img then you will be able to get into the volume+ + power combo mode, so you can get access to fastboot, and after that you know all the procedures....
---------- Post added at 06:14 PM ---------- Previous post was at 06:04 PM ----------
well actually all the qualcomm based devices are unbrickable so sont worry your phone will be live again... you have to just experimenting it on...
well actually i dont have this phone...i am thinking about buying asus ze601kl? is this a good phone? how'z the performance and stability of cm13 snapshot version on your device? is dual sim and all the other things works without any bug? or it has any bug?
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
asus has such funky things in stock boot image as it verifies everytime on boot for valid image, if you have unlocked its bootloader before and try to update its firmware or install stock rom it creates problem. so cm13 is better choice.
Click to expand...
Click to collapse
Well, here I am ready to upload the ROM to the phone using QFIL. The phone is identified by the port. The only thing I'm having trouble with now is finding the "RAWPROGRAMMER" file to load from the firmware.
I'm not sure what else to do, I can't find the file anywhere.
Maybe this is when they say I need to get ahold of someone else exact same phone, root it, load twrp, and backup their original stock rom? I'm not sure. I just feel soo close to getting this done, but I keep missing files. I'm trying to load CM.13 but inside the folders for the firmware, there isn't any file in there. I've already found the patch file and the .mbn file that I need. Just missing the rawprogrammer file.
This is giving me a headache. LOL
Actually the only file I need is the .xml file that it asks for in QFIL. Which I guess is supposed to be in the stock rom somewhere. But in order to get that, I'm guessing I'll have to use my wifes phone (she has the exact same model as I do). I'll just have to make sure to not delete anything or mess up her phone. lol
And I'm also thinking that I will have to install stock ROM first before flashing the CM.13. So I'll have to get that stock ROM from her phone, since I deleted mine on accident.
that xml file is basically a partition structure file for your phone emmc. i think it might be there in your firmware.zip
you just have to find rawprogrammer file, i think it is there where you find unbrick guide for all qualcomm devices.....you just try that file it might work for your phone too..and after adding rawprogrammer you can add firmware parts from firmware.zip file or you also can clone your wife's phone emmc, using emmc dump to raw extension.
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
you dont need to install stock rom first, only you need to send droidboot,recovery or maybe boot partitions, if you have deleted modem and other partitions, then those will also. if you get fastboot then you can flash twrp and can flash cm13.
---------- Post added at 03:09 PM ---------- Previous post was at 03:00 PM ----------
there will be different named xml file in firmware.zip for you phone's firmware you just try try yourself available xml files in firmware. if it will be wrong xml then it will auto terminate no need to worry.
What happened man! there is no response from you, since very long time!! I think you have solved the problem and been very happy with the phone live again.
flash stock firmware using this tool: maybe it works
https://androiddatahost.com/326a2
crossmanx said:
What happened man! there is no response from you, since very long time!! I think you have solved the problem and been very happy with the phone live again.
Click to expand...
Click to collapse
Nope, I still haven't unbricked it just yet. I had to put it on hold for a bit while I got much work done. But I will try again soon. I miss my phone. :'( lol
Same problem ZE601Kl
WormholeMatt said:
Nope, I still haven't unbricked it just yet. I had to put it on hold for a bit while I got much work done. But I will try again soon. I miss my phone. :'( lol
Click to expand...
Click to collapse
Hi Guys ,
Same problem happened for me with my Asus Zenfone 2 laser Ze601Kl.
I have tried QFIL , QPST all the qualcomm related softwares to make it work , but everytime i am getting same error " SAHARA FAIL "
I have tried with COLOR OS for One Plus One and which was having one chinese flasher and sadly that also showing the same error ,
AS far as i know i have installed the qualcomm drivers successfully and it is showing in device manager also . I have tried with Windows 7 X64 , Windows XP SP 2 . Still no luck
My phone has been dead since 1 month Somebody please help me
ZB500KL in Qualcomm HS-USB QDLoader 9008 no fastboot
Please help
I in Russia
Asus ZenFone Go ZB500KL in Qualcomm Snapdragon 410 MSM8916 detected pc only Qualcomm HS-USB QDLoader 9008. Please help
Try this https://forum.xda-developers.com/zenfone-3/help/hard-brick-asus-zenfone-3-ze520kl-t3483874/page3
Follow last post, technically you only need adb connectivity to flash all at once with one click. Hope this will help you.
Of course, now you need the rom for your device.
Sent from my ZenFone 3 using XDA Labs
crossmanx said:
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
Click to expand...
Click to collapse
Good to see anyone talking about LINUX here! I have my ZE550KL briked and the only thing I've been able to do till now are booting in fastboot and Android Recovery modes.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
Click to expand...
Click to collapse
Wow, this helped me a lot! My Linux system was not able to recognize the device but reinserting the battery and trying volumeUP+PowerButton did the trick! Now running 'fastbood devices' lists it and of course that made it visible through Virtualbox too [Windows 7 guest OS].
Now, considering that I would really like to resuscitate my phone by using LINUX, what else should I do in order to succeed?
Thanks a lot and best regards.
crossmanx said:
thanks man! I think you have to download QUALCOMM drivers! from internet. and install it into your pc. after installing drivers there will be a connection into your device manager when you connect your phone with pc. it maybe QUALCOMM 9006/9008, or QDLOADER or Qualcomm mmc storage. is this shows up into your pc, you are done,, you can push firmware parts into your device using qpst or qfil softwares. I will send you the link for guide.
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
---------- Post added at 10:54 AM ---------- Previous post was at 10:49 AM ----------
try to search"unbrick all qualcomm snapdragon devices" into google and you will find out how to unbrick using qfil/qpst. you have to download stock firmware for your phone.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
give results.
Click to expand...
Click to collapse
can you help me
same mode, manage to flash and download finish success.
Finish Download
Start Download
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
Finish Download
sorry dude, i have no more info about asus devices. so can't help. remember only buy phones which have flashtools available like lenovo, mi, oppo, zuk etc.
Help me! my moto e3 power imei invalid I can't flash orrignal db file plz help me sir
Flash again
https://drive.google.com/file/d/0B176Cbvuapswa3A0RndRcF85cUE/view?usp=drivesdk
And
Untick preloader option
If not work above trick
Do this
Enter your device imei
From play store
https://play.google.com/store/apps/details?id=com.cryptotel.chamelephon
sagary727 said:
Help me! my moto e3 power imei invalid I can't flash orrignal db file plz help me sir
Click to expand...
Click to collapse
I had same problem bro.
After rooting I had solved the problem of invalid IMEI
But I can't fix my WiFi nvram warning 0x02
If you already rooted your device can you give me your WiFi and and WiFi_custom file from your device's root folder?????
---------- Post added at 03:08 AM ---------- Previous post was at 03:04 AM ----------
sagary727 said:
Help me! my moto e3 power imei invalid I can't flash orrignal db file plz help me sir
Click to expand...
Click to collapse
Db files are not working in current sn_writer_tool for mt6735
You can use this application ,but your device must be rooted
https://play.google.com/store/apps/details?id=com.cryptotel.chamelephon
solved
sagary727 said:
Help me! my moto e3 power imei invalid I can't flash orrignal db file plz help me sir
Click to expand...
Click to collapse
I think you used sp flash tool with format + download
So ok
You have to again Flash with format + download
Why?
Because error files will format from your device
After flashing , don't power up your device
Just disconnect your device
And download sn writer tool V1.15552.00
Then extract in computer and open
Tick on , barcode,IMEI ,bt address,WiFi adress and serial no.
Then, tick on,IMEI checksum,dual imei
Then, choose your modem and apdp file
And save it
Then click on start,and fill up proper details
And now connect your Moto E3 power with usb
And it take some time
And it will show successfully pass (with green sign)
And then power up your smartphone
Now it's fix
---------- Post added at 06:37 AM ---------- Previous post was at 06:36 AM ----------
gupta8914 said:
I had same problem bro.
After rooting I had solved the problem of invalid IMEI
But I can't fix my WiFi nvram warning 0x02
If you already rooted your device can you give me your WiFi and and WiFi_custom file from your device's root folder?
---------- Post added at 03:08 AM ---------- Previous post was at 03:04 AM ----------
Db files are not working in current sn_writer_tool for mt6735
You can use this application ,but your device must be rooted
https://play.google.com/store/apps/details?id=com.cryptotel.chamelephon
Click to expand...
Click to collapse
I think you used sp flash tool with format + download
So ok
You have to again Flash with format + download
Why?
Because error files will format from your device
After flashing , don't power up your device
Just disconnect your device
And download sn writer tool V1.15552.00
Then extract in computer and open
Tick on , barcode,IMEI ,bt address,WiFi adress and serial no.
Then, tick on,IMEI checksum,dual imei
Then, choose your modem and apdp file
And save it
Then click on start,and fill up proper details
And now connect your Moto E3 power with usb
And it take some time
And it will show successfully pass (with green sign)
And then power up your smartphone
Now it's fix
turjyasaha said:
Flash again
https://drive.google.com/file/d/0B176Cbvuapswa3A0RndRcF85cUE/view?usp=drivesdk
And
Untick preloader option
Click to expand...
Click to collapse
Does this flash successfully because I read in many thread that people brick their phones by flashing it through sp flash tool
Can you confirm please
Br
Shahzaib Jahangir
#Unlockerplus
u can also use mtk.droid tool
imei number invalid
turjyasaha said:
Flash again
https://drive.google.com/file/d/0B176Cbvuapswa3A0RndRcF85cUE/view?usp=drivesdk
And
Untick preloader option
Click to expand...
Click to collapse
moto e3 power custom rom lineage os imei number invalid plz hillp me i am try
chamelephon and uncal tool and hero tool and imei.exe
nvram backup ne hai mere passs
gupta8914 said:
I think you used sp flash tool with format + download
So ok
You have to again Flash with format + download
Why?
Because error files will format from your device
After flashing , don't power up your device
Just disconnect your device
And download sn writer tool V1.15552.00
Then extract in computer and open
Tick on , barcode,IMEI ,bt address,WiFi adress and serial no.
Then, tick on,IMEI checksum,dual imei
Then, choose your modem and apdp file
And save it
Then click on start,and fill up proper details
And now connect your Moto E3 power with usb
And it take some time
And it will show successfully pass (with green sign)
And then power up your smartphone
Now it's fix
---------- Post added at 06:37 AM ---------- Previous post was at 06:36 AM ----------
I think you used sp flash tool with format + download
So ok
You have to again Flash with format + download
Why?
Because error files will format from your device
After flashing , don't power up your device
Just disconnect your device
And download sn writer tool V1.15552.00
Then extract in computer and open
Tick on , barcode,IMEI ,bt address,WiFi adress and serial no.
Then, tick on,IMEI checksum,dual imei
Then, choose your modem and apdp file
And save it
Then click on start,and fill up proper details
And now connect your Moto E3 power with usb
And it take some time
And it will show successfully pass (with green sign)
And then power up your smartphone
Now it's fix
Click to expand...
Click to collapse
How To Know Barcode, BT Address, Wifi Address?
sagary727 said:
Help me! my moto e3 power imei invalid I can't flash orrignal db file plz help me sir
Click to expand...
Click to collapse
I tried many method but failed like you.Some tools write imei but not permanently (after reset same problem) some method need rooted device. As you have already lost DB file no use of flashing again.So here is best solution and permanent imei writer for your device and many device.
Search on Google >>>> maui meta v9
Here is the tutorial >>>>>>> forum(dot)hovatek(dot)com/thread-12328(dot)html
im not able to write full address because im new but it is complete i think
I hope you already solved , those who didn't and are in same problem Google for Maui Meta v9 and after successfully solving your problem with this tool write a full how to guide here.
I used Maui Meta v9 (and thats best solution for imei writing) don't know about superior versions. Give them a try
---------- Post added at 06:48 PM ---------- Previous post was at 06:40 PM ----------
Shabby The Dev said:
Does this flash successfully because I read in many thread that people brick their phones by flashing it through sp flash tool
Can you confirm please
Br
Shahzaib Jahangir
#Unlockerplus
Click to expand...
Click to collapse
No and yes ....it can soft brick and noobs like me feel their device gone forever but not or very rare chances (I did many time and felt my device gone but I'm answering from same device) Just do some research and keep another device handy for doing unbricking research and procedure step by step
I have an Axon 7 with a broken screen (including part of the touch panel). The screen shows all black but the device does turn on and is fully functioning. I am currently BL unlocked, rooted, and running CRDroid so I'm wondering if I send in the phone for repair if ZTE will give me a hard time. I would also like some way to access the phone because atm I cannot due to my password falling in an area of the screen with the broken touch panel. Is there a way to relock the BL without having the screen working on the device? Thanks for any help
Also would something along the lines of this adapter allow me to use a mouse and tv to access the phone?
The screen is broken they can't check if bootloader is unlocked I think. You have no other choice anyway
CKH4 said:
I have an Axon 7 with a broken screen (including part of the touch panel). The screen shows all black but the device does turn on and is fully functioning. I am currently BL unlocked, rooted, and running CRDroid so I'm wondering if I send in the phone for repair if ZTE will give me a hard time. I would also like some way to access the phone because atm I cannot due to my password falling in an area of the screen with the broken touch panel. Is there a way to relock the BL without having the screen working on the device? Thanks for any help
Also would something along the lines of this adapter allow me to use a mouse and tv to access the phone?
Click to expand...
Click to collapse
You can use MiFlash over EDL to reinstall stock (there are full system packages for A2017 and A2017G on the 4th category brick repair manual) and then use axon7toolkit to relock the bootloader
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
CKH4 said:
I have an Axon 7 with a broken screen (including part of the touch panel). The screen shows all black but the device does turn on and is fully functioning. I am currently BL unlocked, rooted, and running CRDroid so I'm wondering if I send in the phone for repair if ZTE will give me a hard time. I would also like some way to access the phone because atm I cannot due to my password falling in an area of the screen with the broken touch panel. Is there a way to relock the BL without having the screen working on the device? Thanks for any help
Also would something along the lines of this adapter allow me to use a mouse and tv to access the phone?
Click to expand...
Click to collapse
You can use MiFlash over EDL to reinstall stock (there are full system packages for A2017 and A2017G on the 4th category brick repair manual) and then use axon7toolkit to relock the bootloader
Choose an username... said:
You can use MiFlash over EDL to reinstall stock (there are full system packages for A2017 and A2017G on the 4th category brick repair manual) and then use axon7toolkit to relock the bootloader
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
You can use MiFlash over EDL to reinstall stock (there are full system packages for A2017 and A2017G on the 4th category brick repair manual) and then use axon7toolkit to relock the bootloader
Click to expand...
Click to collapse
Forgive me but I don't know how to get into EDL mode?
CKH4 said:
Forgive me but I don't know how to get into EDL mode?
Click to expand...
Click to collapse
But what model is it? G, U, Chinese? If you can get into EDL but don't have the necessary packages (A2017U, don't know where they are) then there's not much that you can do...
Ask djkuz for the A2017U_FULL_EDL package if you can't find it. And can you please send the link if you get it? Many people are needing this package and I tell everyone to go bother djkuz lol
Basically you have two ways: Use adb if you can (either from the system with USB debugging and having previously authorized the PC you are using, which is pretty far-fetched, or with FTM mode [turn it off, hold Power and Volume down for like 20 seconds], or the easier way, which I think doesn't work for all models, which is: Plug the USB cable on the PC but not on the phone, With the phone off, hold both volume buttons (only volume, not power) and insert the USB-C cable. Your PC should detect the phone as Qualcomm HS-USB QDLoader 9008 on Device Manager under Ports (Com & LPT), or if you don't have the driver, as QUSB_BULK. If it appears as QUSB_BULK download and install the USB drivers from the 4th category brick repair manual. After you have the drivers installed and you have the qdloader thing, go to its properties and make sure that the bitrate is set to 115200 or 128000. If not put it there.
When you have the QDloader thing, fire up MiFlash and your phone should appear listed as COM x (3, 4, 5... Doesn't matter). Then you load up the folder (you use folders on MiFlash, not zips) and flash the stuff. When it finishes let it boot, then use axon7toolkit to relock the phone.
This is in case they change the screen of the phone. You'd have to pay $80 if they turned it on after the screen replacement and saw the warning text... Not good!
I think I'll make a guide sometime
I sent my A2017G back for repair a while ago because of a faulty battery/charging/power mechanism. I was not able to relock the bootloader anymore. The tech rep at the service desk switched on the phone when I returned it, saw the warning message on screen, said "hey, what is that message, does it do that all the time?", on which I replied "well yeah, it does that when the bootloader is unlocked.", took it in for repair anyways, and 2 weeks later I could collect a replacement A2017G without any remarks on unlocking/rooting/customwhatever. Maybe other companies are not as easy as this, but I was very happy to see my A2017 repaired/replaced.
Choose an username... said:
But what model is it? G, U, Chinese? If you can get into EDL but don't have the necessary packages (A2017U, don't know where they are) then there's not much that you can do...
Ask djkuz for the A2017U_FULL_EDL package if you can't find it. And can you please send the link if you get it? Many people are needing this package and I tell everyone to go bother djkuz lol
Basically you have two ways: Use adb if you can (either from the system with USB debugging and having previously authorized the PC you are using, which is pretty far-fetched, or with FTM mode [turn it off, hold Power and Volume down for like 20 seconds], or the easier way, which I think doesn't work for all models, which is: Plug the USB cable on the PC but not on the phone, With the phone off, hold both volume buttons (only volume, not power) and insert the USB-C cable. Your PC should detect the phone as Qualcomm HS-USB QDLoader 9008 on Device Manager under Ports (Com & LPT), or if you don't have the driver, as QUSB_BULK. If it appears as QUSB_BULK download and install the USB drivers from the 4th category brick repair manual. After you have the drivers installed and you have the qdloader thing, go to its properties and make sure that the bitrate is set to 115200 or 128000. If not put it there.
When you have the QDloader thing, fire up MiFlash and your phone should appear listed as COM x (3, 4, 5... Doesn't matter). Then you load up the folder (you use folders on MiFlash, not zips) and flash the stuff. When it finishes let it boot, then use axon7toolkit to relock the phone.
This is in case they change the screen of the phone. You'd have to pay $80 if they turned it on after the screen replacement and saw the warning text... Not good!
I think I'll make a guide sometime
Click to expand...
Click to collapse
I used MiFlash to restore to EDL full stock B19 but now the device will not respond to holding the power button. Axon7Toolkit says that my device isn't visible to ADB. What would my next steps be?
CKH4 said:
I used MiFlash to restore to EDL full stock B19 but now the device will not respond to holding the power button. Axon7Toolkit says that my device isn't visible to ADB. What would my next steps be?
Click to expand...
Click to collapse
I think that happened to me... It's really weird but I managed to fix it by connecting it to the wall charger and holding the power button once the charging screen appeared.
This phone...
Any way to make the att v35 work on verizon? It should have the hardware is it a firmware update ? I'm a bit noon level at all this custom Rom stuff. I need some directions if I am able to do something please
From my understanding, even flashing an AT&T model to USA unlocked firmware does NOT carrier unlock the phone. You have to get the carrier unlock code from AT&T.
eviling said:
Any way to make the att v35 work on verizon? It should have the hardware is it a firmware update ? I'm a bit noon level at all this custom Rom stuff. I need some directions if I am able to do something please
Click to expand...
Click to collapse
verizon=CDMA
ATT=GSM
az090631 said:
verizon=CDMA
ATT=GSM
Click to expand...
Click to collapse
Flashing to NAO carrier unlocked should give it CDMA bands, if V35 can be Frankenstein'ed like V30.
---------- Post added at 05:20 AM ---------- Previous post was at 05:18 AM ----------
Guyinlaca said:
From my understanding, even flashing an AT&T model to USA unlocked firmware does NOT carrier unlock the phone. You have to get the carrier unlock code from AT&T.
Click to expand...
Click to collapse
It's probably carrier unlocked, but hasn't been flashed to NAO carrier unlocked firmware so it still has the AT&T V35 bands.
ChazzMatt said:
Flashing to NAO carrier unlocked should give it CDMA bands, if V35 can be Frankenstein'ed like V30.
---------- Post added at 05:20 AM ---------- Previous post was at 05:18 AM ----------
It's probably carrier unlocked, but hasn't been flashed to NAO carrier unlocked firmware so it still has the AT&T V35 bands.
Click to expand...
Click to collapse
it is indeed carrier unlocked but the att version of the phone neglects the cdma bands im not an idiot <_< but i figured the hardswarts their should be a matter of firmware. do i need to root unlock and custom rom al to get this firmware? or can i just get the firmware updated through a kernal update or somehting? idk im so rusty at this **** lol
eviling said:
it is indeed carrier unlocked but the att version of the phone neglects the cdma bands im not an idiot <_< but i figured the hardswarts their should be a matter of firmware. do i need to root unlock and custom rom al to get this firmware? or can i just get the firmware updated through a kernal update or somehting? idk im so rusty at this **** lol
Click to expand...
Click to collapse
I'll quote myself again, because I did say what to do... then I'll give you more information.
ChazzMatt said:
It's probably carrier unlocked, but hasn't been flashed to NAO carrier unlocked firmware so it still has the AT&T V35 bands.
Click to expand...
Click to collapse
You need to use Dev Patched LGUP to cross flash to NAO carrier unlocked firmware.
You do NOT need to root. We do not have any custom ROMs for V35.
You just need the Dev Patched LGUP from one of the other threads and cross flash to NAO (North American Open Market) firmware over your AT&T V35 model.
KDZ
V350ULM20f_00_NAO_US_OP_0218.kdz
https://lg-firmwares.com/downloads-file/22230/V350ULM20f_00_NAO_US_OP_0218
Flash in Refurbish mode. Then Master Reset for good measure:
Master Reset -- using buttons:
1. Unplug phone and turn it OFF.
2. Press and hold the Power and Volume down buttons.
3. When the LG logo appears, quickly release the Power button only -- then immediately press Power button again, while STILL pressing the Volume down button until you see the screen to select Yes to erase and reset everything.
4. Release both buttons so you can make your choices.
With your device powered off, press and hold the Power button and Volume Down buttons simultaneously for a few seconds.
When the LG logo appears, quickly release and then re-hold the Power button while keep holding the Volume Down button.
Let go of the buttons when the onscreen menu appears.
When you see the option to Delete all user data (including LG and carrier apps) and reset all settings message prompt, press the Volume Down button to highlight Yes.
Then press the Power button to reset the device.
Wait until the reset is complete then reboot your device. If it’s able to boot up successfully, proceed with the initial setup.
Click to expand...
Click to collapse
Dev Patched LGUP
_________________
HOW TO INSTALL DEV PATCHED LGUP
1) DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
2. Extract LGUP_DualMode.zip to a folder on your PC.
3. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
4. Then in that same folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode. READ THAT AGAIN.
5. Now, launch LGUP using the desktop shortcut created, NOT the folder icon!
As mentioned before, use REFURBISH or PARTITION DL modes. Refurbish is probably better.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
It's all fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
* Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
* Try different USB port,
* Try different USB cable,
* Try different computer.
* Reinstall LG mobile drivers on your PC.
* Reinstall dev patched LGUP again.
* Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
ChazzMatt said:
I'll quote myself again, because I did say what to do... then I'll give you more information.
You need to use Dev Patched LGUP to cross flash to NAO carrier unlocked firmware.
You do NOT need to root. We do not have any custom ROMs for V35.
You just need the Dev Patched LGUP from one of the other threads and cross flash to NAO (North American Open Market) firmware over your AT&T V35 model.
Flash in Refurbish mode. Then Master Reset for good mesure:
Master Reset -- using buttons:
1. Unplug phone and turn it OFF.
2. Press and hold the Power and Volume down buttons.
3. When the LG logo appears, quickly release the Power button only -- then immediately press Power button again, while STILL pressing the Volume down button until you see the screen to select Yes to erase and reset everything.
4. Release both buttons so you can make your choices.
Dev Patched LGUP
https://www.lanzous.com/i3y5ocd
KDZ
V350ULM20d_00_NAO_US_OP_0612.kdz
https://lg-firmwares.com/downloads-file/20225/V350ULM20d_00_NAO_US_OP_0612.kdz
______
If that Dev Patched LGUP doesn't work, try this one below. Screenshot is just an example of how it is flashed, but it's for a different model.
_________________
HOW TO INSTALL DEV PATCHED LGUP
1) DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
2. Extract LGUP_DualMode.zip to a folder on your PC.
3. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
4. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode
5. Launch LGUP using the desktop shortcut.
As mentioned before, use REFURBISH or PARTITION DL modes. Refurbish is probably better.
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
It's all fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again.
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
Click to expand...
Click to collapse
im sorry forgive my ignorance i looked up your initial insturctions to no result so i posted a replyu in a last bid attempt and low and behold it worked! thank you sir i was arguing with my womans saying it has to be possible thank you! and its 9.0! im sure i wont be getting another update now that its unlocked the way it is. but its getitng 4g lte from verizon on my company sim now i can cancle my plan saved me 200$ for sure my damn dog ate my company phone and i only had my old phone to use. got it unlocked from att since i bought it outright and it wouldnt get 4g lte (data) but appears to be working perfectl;y now! awsome! been working on this for 3 weeks lol was trying to trade my phone on facebook
eviling said:
im sorry forgive my ignorance i looked up your initial insturctions to no result so i posted a replyu in a last bid attempt and low and behold it worked! thank you sir i was arguing with my womans saying it has to be possible thank you! and its 9.0! im sure i wont be getting another update now that its unlocked the way it is. but its getitng 4g lte from verizon on my company sim now i can cancle my plan saved me 200$ for sure my damn dog ate my company phone and i only had my old phone to use. got it unlocked from att since i bought it outright and it wouldnt get 4g lte (data) but appears to be working perfectl;y now! awsome! been working on this for 3 weeks lol was trying to trade my phone on facebook
Click to expand...
Click to collapse
You're welcome!
For future updates, you'll flash future NAO KDZ releases via this same Dev Patched LGUP -- but next time you can use "Upgrade" mode instead of "Refurbish". It's like a manual OTA and will save your data.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
I'll quote myself again, because I did say what to do... then I'll give you more information.
You need to use Dev Patched LGUP to cross flash to NAO carrier unlocked firmware.
You do NOT need to root. We do not have any custom ROMs for V35.
You just need the Dev Patched LGUP from one of the other threads and cross flash to NAO (North American Open Market) firmware over your AT&T V35 model.
Flash in Refurbish mode. Then Master Reset for good mesure:
Master Reset -- using buttons:
1. Unplug phone and turn it OFF.
2. Press and hold the Power and Volume down buttons.
3. When the LG logo appears, quickly release the Power button only -- then immediately press Power button again, while STILL pressing the Volume down button until you see the screen to select Yes to erase and reset everything.
4. Release both buttons so you can make your choices.
Dev Patched LGUP
https://www.lanzous.com/i3y5ocd
KDZ
V350ULM20d_00_NAO_US_OP_0612.kdz
https://lg-firmwares.com/downloads-file/20225/V350ULM20d_00_NAO_US_OP_0612.kdz
______
If that Dev Patched LGUP doesn't work, try this one below. Screenshot is just an example of how it is flashed, but it's for a different model.
_________________
HOW TO INSTALL DEV PATCHED LGUP
1) DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
2. Extract LGUP_DualMode.zip to a folder on your PC.
3. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
4. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode
5. Launch LGUP using the desktop shortcut.
As mentioned before, use REFURBISH or PARTITION DL modes. Refurbish is probably better.
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
It's all fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again.
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
Click to expand...
Click to collapse
@ChazzMatt,
That's what I love about DEV patched LGUP--It let's you bend the rules and do some things that would normally require root access, specifically:
--DUMPing of any partition, allowing for data backup and recovery, even on encrypted partitions, since you can also dump the encrypt partition.
--Cross flashing .kdz's from other variants utilizing the same hardware
and
--Flashing only specific partitions from a given .kdz
and I definitely agree that CHIPERASE and BOARD DL are to be avoided--
The most useful options besides REFURBISH and UPGRADE are DUMP and possibly PARTITION DL
Sorry for inserting my two cents into your thread.
TecKnight
Hi.All.I have cross flashed LG v40 Hong Kong version Rom Android 9 with the Korean Android 10 using lgup.
THE Rom was installed but I lost radio.no signal. So then on the advice of a friend I flashed partition dl modem a and modem b from a European version 9.and when the phone rebooted it shows security warnings and says all slots are unbeatable. Any way to put oh in fastboot mode so that lgup can identify.Any easy way out.thx
serpent android said:
Hi.All.I have cross flashed LG v40 Hong Kong version Rom Android 9 with the Korean Android 10 using lgup.
THE Rom was installed but I lost radio.no signal. So then on the advice of a friend I flashed partition dl modem a and modem b from a European version 9.and when the phone rebooted it shows security warnings and says all slots are unbeatable. Any way to put oh in fastboot mode so that lgup can identify.Any easy way out.thx
Click to expand...
Click to collapse
First of all, these are LG V35 forums but that's fine I guess since the V35 and V40 are same exact when it comes to how to unbrick. You can't mix Android 9 and 10 like that, no wonder you got bricked. At this point, even if somehow you get into LG UP, make sure you don't use any options in LG UP or any other tool that you don't know about. Lot of people tend to use options like 'chiperase' thinking it will fix the phone but they make matters worse and permanently loose their IMEI and EFS partition info.
For LG UP you need download mode, not fastboot mode. Are you able to get to download mode by holding volume up button while the phone is turned off and by plugging in the USB cable that is connected to the computer? I think you should still be able to get into download mode even if phone can't boot but If you can't get into download mode this way and can't boot into android, the next option will be using QFIL/QPST by putting phone into EDL mode. Since the process of unbricking will be same for both V35 and V40 phones, I will briefly guide you here for others with V35 to see this info but if you need further help, it would be best to post in LG V40 forums. The QFIL/QPST folder and V35 engineering bootloader from link below work for both V35 and V40 but rest of files such as firehose and actual partition files are different between the two models.
First go to the LG V40 unlock guide post here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
and download QPST, firehose and v35eng bootloader files attached to the above post and thank the OP. You can just follow that guide as if you want to unlock bootloader but basically you are going to put phone in EDL mode using that guide so you can run QFIL and access partition table using partition manager and flash the files necessary for download mode. All you need is bootloader and and laf partitions to get into download mode which are abl_a or abl_b (based on which slot you are booting from, slot a or b), and laf_a or laf_b. Important to note that laf_a and laf_b are same exact files actually, same is true for abl_a and abl_b. I am uploading the files for V40 on Mega as these were too large for XDA but if anyone needs them for V35 just post here and me or someone else can upload them:
https://mega.nz/folder/o2xEnCSb#W5icT64hASwKk67G9IngEQ
MD5s: abl_a: 3a9e506523e92b6a242af2e1cb5987fd, abl_b: 3a9e506523e92b6a242af2e1cb5987fd, laf_a: cf9edf4748f768cfa3c88ca362ff36b3, laf_b: cf9edf4748f768cfa3c88ca362ff36b3
After you download attached files, flash abl_a file to abl_a partition, then abl_b file to abl_b partition, flash laf_a file to laf_a partition and laf_b file to laf_b partition. You can use Xsavi's guide to put the phone in EDL mode, start partition manager, then use the option load image and flash the files to their respective partitions. I don't remember if these are from Oreo or Pie as I don't own V40 anymore but I think for unbricking purposes it shouldn't matter as you are going to flash a whole KDZ on top of these anyways. Once done, turn phone off, start LG UP on your PC, hold volume up button while you attach the USB cable to the phone and it should put the phone in download mode. Use partition DL and flash full KDZ either Oreo or Pie first before you try going to Android 10, best would be flashing Oreo first as some people have had problems going straight to Pie or Android 10.
Android# said:
First of all, these are LG V35 forums but that's fine I guess since the V35 and V40 are same exact when it comes to how to unbrick. You can't mix Android 9 and 10 like that, no wonder you got bricked. At this point, even if somehow you get into LG UP, make sure you don't use any options in LG UP or any other tool that you don't know about. Lot of people tend to use options like 'chiperase' thinking it will fix the phone but they make matters worse and permanently loose their IMEI and EFS partition info.
For LG UP you need download mode, not fastboot mode. Are you able to get to download mode by holding volume up button while the phone is turned off and by plugging in the USB cable that is connected to the computer? I think you should still be able to get into download mode even if phone can't boot but If you can't get into download mode this way and can't boot into android, the next option will be using QFIL/QPST by putting phone into EDL mode. Since the process of unbricking will be same for both V35 and V40 phones, I will briefly guide you here for others with V35 to see this info but if you need further help, it would be best to post in LG V40 forums. The QFIL/QPST folder and V35 engineering bootloader from link below work for both V35 and V40 but rest of files such as firehose and actual partition files are different between the two models.
First go to the LG V40 unlock guide post here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
and download QPST, firehose and v35eng bootloader files attached to the above post and thank the OP. You can just follow that guide as if you want to unlock bootloader but basically you are going to put phone in EDL mode using that guide so you can run QFIL and access partition table using partition manager and flash the files necessary for download mode. All you need is bootloader and and laf partitions to get into download mode which are abl_a or abl_b (based on which slot you are booting from, slot a or b), and laf_a or laf_b. Important to note that laf_a and laf_b are same exact files actually, same is true for abl_a and abl_b. I am uploading the files for V40 on Mega as these were too large for XDA but if anyone needs them for V35 just post here and me or someone else can upload them:
https://mega.nz/folder/o2xEnCSb#W5icT64hASwKk67G9IngEQ
MD5s: abl_a: 3a9e506523e92b6a242af2e1cb5987fd, abl_b: 3a9e506523e92b6a242af2e1cb5987fd, laf_a: cf9edf4748f768cfa3c88ca362ff36b3, laf_b: cf9edf4748f768cfa3c88ca362ff36b3
After you download attached files, flash abl_a file to abl_a partition, then abl_b file to abl_b partition, flash laf_a file to laf_a partition and laf_b file to laf_b partition. You can use Xsavi's guide to put the phone in EDL mode, start partition manager, then use the option load image and flash the files to their respective partitions. I don't remember if these are from Oreo or Pie as I don't own V40 anymore but I think for unbricking purposes it shouldn't matter as you are going to flash a whole KDZ on top of these anyways. Once done, turn phone off, start LG UP on your PC, hold volume up button while you attach the USB cable to the phone and it should put the phone in download mode. Use partition DL and flash full KDZ either Oreo or Pie first before you try going to Android 10, best would be flashing Oreo first as some people have had problems going straight to Pie or Android 10.
Click to expand...
Click to collapse
Thanks for the reply sir. Ur amazing.These set of instructions seem alot to me
Yes im doing the same to get into the dl mode but cant enter..by holding power and volume up whilst plugging the usb.but its stuck in a bootloop.
serpent android said:
Thanks for the reply sir. Ur amazing.These set of instructions seem alot to me
Yes im doing the same to get into the dl mode but cant enter..by holding power and volume up whilst plugging the usb.but its stuck in a bootloop.
Click to expand...
Click to collapse
You don't need to hold power button. Phone needs to be turned off. Hold volume up and plug in usb cable. Since you are in bootloop, keep holding volume up button (don't hold power button) and plug usb cable in. Once the bootloop cycle restarts it should go in download mode, just don't let go of volume up button until in download mode. If you still can't enter download mode, you are pretty much out of options and have to use EDL mode as i explained above to unbrick your phone.
Android# said:
You don't need to hold power button. Phone needs to be turned off. Hold volume up and plug in usb cable. Since you are in bootloop, keep holding volume up button (don't hold power button) and plug usb cable in. Once the bootloop cycle restarts it should go in download mode, just don't let go of volume up button until in download mode. If you still can't enter download mode, you are pretty much out of options and have to use EDL mode as i explained above to unbrick your phone.
Click to expand...
Click to collapse
Thanks a lot. Yes i am holdingvolume up button and inserting usb c but it doesnt go into dowmload mode. But edl mode also requires to boot phone or can it work in a bootloop
---------- Post added at 10:50 AM ---------- Previous post was at 10:35 AM ----------
Anothet thing i want to add is that the ph is going in factory reset and even erases all user data.ive even done that. So that means that the ph isnt bricked? But even after that it doesnt go in DL mode
serpent android said:
Thanks a lot. Yes i am holdingvolume up button and inserting usb c but it doesnt go into dowmload mode. But edl mode also requires to boot phone or can it work in a bootloop
---------- Post added at 10:50 AM ---------- Previous post was at 10:35 AM ----------
Anothet thing i want to add is that the ph is going in factory reset and even erases all user data.ive even done that. So that means that the ph isnt bricked? But even after that it doesnt go in DL mode
Click to expand...
Click to collapse
Yeah if you can't enter download mode then in my opinion using QFil and EDL mode is probably the only way to go. You need to read the unlock guide by Xsavi, that i linked earlier: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
You are not required to boot the phone in order to enter EDL mode but it does require lot of patience as you have to hold volume down and power button until phone screen turns off suddenly to reboot, rapidly start pressing volume up key while still holding the volume down and power button. While you do this phone needs to be plugged in with usb cable and you have to have QFIL window open. Once the phone enters EDL mode, the screen will be dark and blank, but it is detected in QFIL window, you know that you are in EDL 9008 mode.
Unbricking your phone will require a lot of reading, patience, and making sure you understand what you are doing. It seems complicated and overwhelming but trust me when you have all the files setup and are ready to go, the whole process takes like 5 minutes and is not so hard. Again, the key is reading the guides and steps multiple times before you proceed so you know exactly what you are doing.
Android# said:
Yeah if you can't enter download mode then in my opinion using QFil and EDL mode is probably the only way to go. You need to read the unlock guide by Xsavi, that i linked earlier: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
You are not required to boot the phone in order to enter EDL mode but it does require lot of patience as you have to hold volume down and power button until phone screen turns off suddenly to reboot, rapidly start pressing volume up key while still holding the volume down and power button. While you do this phone needs to be plugged in with usb cable and you have to have QFIL window open. Once the phone enters EDL mode, the screen will be dark and blank, but it is detected in QFIL window, you know that you are in EDL 9008 mode.
Unbricking your phone will require a lot of reading, patience, and making sure you understand what you are doing. It seems complicated and overwhelming but trust me when you have all the files setup and are ready to go, the whole process takes like 5 minutes and is not so hard. Again, the key is reading the guides and steps multiple times before you proceed so you know exactly what you are doing.
Click to expand...
Click to collapse
Thanks im doing reading will getur expert advice soon
Also, factory reset will not help at this point because part of your rom is android 9 and other part is android 10. Erasing userdata and cache (factory reset) in itself will not fix that. What i don't understand though is that just flashing modem_a and modem_b from Android 9 should still allow you to enter download mode since you didn't alter bootloader or the laf partitions. In my opinion the phone should still be able to enter download mode even if it is bootlooping unless more changes were made to phone where bootloader and/or laf partitions were also altered. In any case, it doesn't matter anymore I guess.
Edit: Great, good luck, hope you get it unbricked!
Android# said:
Also, factory reset will not help at this point because part of your rom is android 9 and other part is android 10. Erasing userdata and cache (factory reset) in itself will not fix that. What i don't understand though is that just flashing modem_a and modem_b from Android 9 should still allow you to enter download mode since you didn't alter bootloader or the laf partitions. In my opinion the phone should still be able to enter download mode even if it is bootlooping unless more changes were made to phone where bootloader and/or laf partitions were also altered. In any case, it doesn't matter anymore I guess.
Edit: Great, good luck, hope you get it unbricked!
Click to expand...
Click to collapse
Yes i didnt alter anything apart from the modem partitions thats it and dl mode unavailable.thats the issue.so does this necessarily mean that booting into qfil is the ultimate solution
Can you please tell me that i dont want bootloader unlocked just want dl mode..so for this do i have to follow the whole guide or just part of it to enter edl mode...pls enlighten
Hi sir. I have bootlted into qualcom 9008 mode used qfil and flashed the required partitions which were successfully done. But the phone still cannot boot into download mode . after i flashed i simply exit the qfil and. Piwer down he phone but it still does the same as before and cant get into download mode
.did i miss something
Hello,
For quite a while I am searching for a working method to root my SM-A500FU running on Android 6.0.1.
There is no OEM Unlock button available whatever I try.
All root methods I found need OEM Unlock so they don't do the trick.
Is there a way to get the rooting done?
And if so, please provide me the steps to do.
Thanks in advance.
You can root your phone...
Hello,
Please read my whole reply. I have an SM-A500G and my device also did not have OEM unlock too. i searched hidden developer options and it was not there. Did you look in developer options? If you did, did you find it? If yes carry on with the other root methods you have found but if you have not, follow my steps. For my device, I somehow rooted my device without OEM unlock option by using the steps below written by me. I am very sure this will work on your device too as we both have Samsung Galaxy A5 2015 with different varients.[/SIZE]
Before starting, please be aware that rooting will void your warranty and if the steps I have given below are not done properly, you will brick your device. Please don't blame me if you got your device bricked. :fingers-crossed:
1. Firstly, you need a windows pc and then go to this link and download the whole folder with the name "Samsung Galaxy A5 2015 Root Method". Do not miss a file and extract all the files from the zip into the folder with a name "Samsung Galaxy A5 2015 Root Method" . Link: https://drive.google.com/drive/folders/1Yx3NgLaEfxW-vYdoKSk0u3N3KbEbktlP?usp=sharing
2. Then navigate to the folder called "Odin3_v3.09" and run the file with name "Odin3 v3.09.exe". Run it with admin rights.
3. In you phone, navigate to developer options and turn on "USB debugging". I am pretty sure that this option will be there. If you don't know how to get developer options, go to setting, about, and tap 3 times on the build number and you will unlock developer options.
4. Now power off your device and reboot into download mode by pressing power button, home button and volume down all together. Press volume up when you see the screen. (the screen is a blue-green colour and it says either press volume up or down, press volume up)
5. Now connect your phone to pc with usb debug enabled on phone.
6. In Odin, If you see device is added, you are good to go. If not reconnect your device.
7. Now in odin, press the button named "AP" and navigate to the "Samsung Galaxy A5 2015 Root Method" and click on the file named "twrp_20191005_a5ultexx (1).tar" and open it.
8. Now in the options section, uncheck "Auto Reboot" and check (if not already) "F. Reset Time". Leave everything else as it is.
9. Press The button "Start"
10. Wait until you see "Pass" in odin.
11. In your phone, you will see that it is "downloading" and there is a white line that is completed. Now to get out of download mode, press power button, home button and volume down all together until you see a black screen.
12. Immediately, you need to press power button, home button and volume up all together until you see the boot screen with yellow text saying "set warranty bit: recovery"
13. Now you will boot into recovery.
14. Now download "Magisk v20.zip" from this link on your pc. Link: https://drive.google.com/file/d/11O2f0HymbcVZ7hQvkGFxGHcB1ShHSr8H/view?usp=sharing
Don't extract it.
15. Now drag or copy and paste "Magisk v20.zip" to the phone's internal storage.
16. In your phone, in twrp recovery. press the install button and navigate to "Magisk v20.zip". Press on it.
17. Now swipe to install and wait a few seconds or minutes.
18. After completion, press the "Wipe Cache/Dalvik" button.
19. Afterwards, press reboot (system)
20. If you see the boot screen with "set warranty bit: kernel", you are good to go and wait till it boots the system.
21. Congratulations, your phone is now rooted!
In step 20, if you see "set warranty bit: recovery" and red text above it, try this: Power off the device in twrp (recovery) in the reboot section and connect to a power supply. If you see 'set warranty bit:kernel' and a charging sign, you are good to go. You just need to hold the power button and wait till it turns off and turns on again. Just wait until it boots the system and you are rooted.
Nice try
Thanks for the effort but did not work.
Odin does not show pass but gives fail every time I try.
How to fix this one?
Lion1969 said:
Thanks for the effort but did not work.
Odin does not show pass but gives fail every time I try.
How to fix this one?
Click to expand...
Click to collapse
Firstly, did you disable auto reboot in odin? Secondly, do you have the latest bootloaders and modems for the device? (If not, you can find them here: https://forum.xda-developers.com/samsung-a-series/general/ref-a500xx-modems-bootloaders-collection-t3496463 Thirdly, there is another option where you use CF-Auto Root and I will link a tutorial on how to do that. Please note that the tutorial has OEM Unlock within it but you don't need it. If you want me to give to give you a guide on it, just ask me. The tutorial link: https://www.youtube.com/watch?v=SXGTIwx1ffk
Also, turn on captions in the tutorial as it says the instructions on the captions and then in odin, turn on "Auto Reboot"
InfernoWolf19 said:
Firstly, did you disable auto reboot in odin? Secondly, do you have the latest bootloaders and modems for the device? (If not, you can find them here: https://forum.xda-developers.com/samsung-a-series/general/ref-a500xx-modems-bootloaders-collection-t3496463 Thirdly, there is another option where you use CF-Auto Root and I will link a tutorial on how to do that. Please note that the tutorial has OEM Unlock within it but you don't need it. If you want me to give to give you a guide on it, just ask me. The tutorial link: https://www.youtube.com/watch?v=SXGTIwx1ffk
Also, turn on captions in the tutorial as it says the instructions on the captions and then in odin, turn on "Auto Reboot"
Click to expand...
Click to collapse
Hi InfernoWolf19,
I disabled auto reboot in Odin.
I installed the latest bootloaders and modems as instructed.
Odin still gives me a fail.
The third option I did exactly as in the YouTube video but also got a fail.
Maybe I forgot something so could you please drop the link to a written guide.
Thanks in advance
Lion1969 said:
Hi InfernoWolf19,
I disabled auto reboot in Odin.
I installed the latest bootloaders and modems as instructed.
Odin still gives me a fail.
The third option I did exactly as in the YouTube video but also got a fail.
Maybe I forgot something so could you please drop the link to a written guide.
Thanks in advance
Click to expand...
Click to collapse
1. Download latest Samsung drivers from this link: https://i1.samsungusbdriver.com/wp-content/uploads/Samsung_USB_Driver_v1.5.63.0.zip
2. Enable usb debugging in developer options in phone and boot into download mode.
3. Open odin, in odin, enable auto reboot and f. reset time.
4. Click the AP button and navigate to the CF Auto Root File. You can get it from here: https://download.chainfire.eu/699/CF-Root1/CF-Auto-Root-a5ulte-a5ultexx-sma500fu.zip?retrieve_file=1
5. Press Start
Hopefully this time, you get pass.
---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------
Could you also provide me with some screenshots when odin shows fail. If possible, a video of you flashing the root file.
InfernoWolf19 said:
1. Download latest Samsung drivers from this link: https://i1.samsungusbdriver.com/wp-content/uploads/Samsung_USB_Driver_v1.5.63.0.zip
2. Enable usb debugging in developer options in phone and boot into download mode.
3. Open odin, in odin, enable auto reboot and f. reset time.
4. Click the AP button and navigate to the CF Auto Root File. You can get it from here: https://download.chainfire.eu/699/CF-Root1/CF-Auto-Root-a5ulte-a5ultexx-sma500fu.zip?retrieve_file=1
5. Press Start
Hopefully this time, you get pass.
---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------
Could you also provide me with some screenshots when odin shows fail. If possible, a video of you flashing the root file.
Click to expand...
Click to collapse
I can't make a video..
I discovered that I can't get my wifi on anymore now, must have something to do with the 2 files I replaced (see above).
The list with bootloaders and modems is about 2 years old, is there a newer available??
Unfortunately I don't know what versions I had before so I can put those back so at least my wifi works again.
It seems I am getting more problems instead of less… help help
Lion1969 said:
I can't make a video..
I discovered that I can't get my wifi on anymore now, must have something to do with the 2 files I replaced (see above).
The list with bootloaders and modems is about 2 years old, is there a newer available??
Unfortunately I don't know what versions I had before so I can put those back so at least my wifi works again.
It seems I am getting more problems instead of less… help help
Click to expand...
Click to collapse
Could you give me you country code or name because then I can find the stock firmware for the device which contains the updated bootloader and modem. With a stock firmware, you can get your latest modems back therefore your wifi works again. i think you flashed the modem incorrectly or the modem is very old. Either way, I need the country name you live in so that i can find the stock firmware from Sammobile - https://www.sammobile.com/samsung/galaxy-a5/firmware/SM-A500FU/
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Please reply ASAP as I want to help you as immediately as possible as it is my fault your WiFi is not working.
InfernoWolf19 said:
Could you give me you country code or name because then I can find the stock firmware for the device which contains the updated bootloader and modem. With a stock firmware, you can get your latest modems back therefore your wifi works again. i think you flashed the modem incorrectly or the modem is very old. Either way, I need the country name you live in so that i can find the stock firmware from Sammobile - https://www.sammobile.com/samsung/galaxy-a5/firmware/SM-A500FU/
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Please reply ASAP as I want to help you as immediately as possible as it is my fault your WiFi is not working.
Click to expand...
Click to collapse
Hi
I live in The Netherlands an already found this one:
A500FUXXU1CSB1_A500FUPHN1CSB1_A500FUXXU1CPI2_HOME.tar
Put it in Odin and said that it was ok.
Phone reboots but keeps hanging on Samsung logo??
Lion1969 said:
Hi
I live in The Netherlands an already found this one:
A500FUXXU1CSB1_A500FUPHN1CSB1_A500FUXXU1CPI2_HOME.tar
Put it in Odin and said that it was ok.
Phone reboots but keeps hanging on Samsung logo??
Click to expand...
Click to collapse
Wait a few minutes or hours. If still hanging, you probably flashed the wrong one. To fix try flashing the stock firmware again or a different rom. Hope this helps
Hi,
I searched for hours to find one that worked with Odin.
After about 30(wtf?) minutes my phone entered set up:
-select language
-connect to wifi
Then I must login with my Samsung account.
Did everything correct but does not work.
What's next??
Lion1969 said:
Hi,
I searched for hours to find one that worked with Odin.
After about 30(wtf) minutes my phone entered set up:
-select language
-connect to wifi
Then I must login with my Samsung account.
Did everything correct but does not work.
What's next??
Click to expand...
Click to collapse
Can you tell me if your wifi works?
My wifi works now
Lion1969 said:
Hi,
I searched for hours to find one that worked with Odin.
After about 30(wtf) minutes my phone entered set up:
-select language
-connect to wifi
Then I must login with my Samsung account.
Did everything correct but does not work.
What's next??
Click to expand...
Click to collapse
If wifi works, congratulations but did you flash the HOME.CSC version? If not, you lost all your data because you flashed a version which removes all of your data. If it is my fault, feel free to ban me from XDA or do anything if it is my fault. :crying:
---------- Post added at 07:06 PM ---------- Previous post was at 07:02 PM ----------
Lion1969 said:
Hi,
I searched for hours to find one that worked with Odin.
After about 30(wtf) minutes my phone entered set up:
-select language
-connect to wifi
Then I must login with my Samsung account.
Did everything correct but does not work.
What's next??
Click to expand...
Click to collapse
If you linked your device to a google or samsung account, it means backup were saved which means you can recover your lost data. Im terribly sorry if you lost your data as I should have given more instructions on which one to flash. Im sorry.
I could not find such a Version.
But now... i can't Access my phone.
Samsung account needed.
I entered correct info but can't get in.
Lion1969 said:
I could not find such a Version.
But now... i can't Access my phone.
Samsung account needed.
I entered correct info but can't get in.
Click to expand...
Click to collapse
What does it say?
---------- Post added at 07:13 PM ---------- Previous post was at 07:10 PM ----------
Maybe try resetting or changing password on that samsung account
Processing failed
Lion1969 said:
Processing failed
Click to expand...
Click to collapse
So you are connected to wifi right? Try going back and reconnecting to wifi and typ in your account.
---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------
InfernoWolf19 said:
So you are connected to wifi right? Try going back and reconnecting to wifi and typ in your account.
Click to expand...
Click to collapse
Also, did you lose your data?
I already changed password with my laptop but did not work.
Logically... it is a "strange" Version running now and maybe the data don't fit the original one
Lion1969 said:
I already changed password with my laptop but did not work.
Logically... it is a "strange" Version running now and maybe the data don't fit the original one
Click to expand...
Click to collapse
Log into you samsung account via comp or any device. Go to security. Then add a secondary security to the account which will be a code. Once this is complete when you go to log in to your samsung account on your phone. If your phone locks you out using the password still it will then automatically use the secondary security. Samsung will automatically tect you a code your phone will sync with this code opening your samsung account. Hope this helps.
---------- Post added at 07:23 PM ---------- Previous post was at 07:20 PM ----------
InfernoWolf19 said:
Log into you samsung account via comp or any device. Go to security. Then add a secondary security to the account which will be a code. Once this is complete when you go to log in to your samsung account on your phone. If your phone locks you out using the password still it will then automatically use the secondary security. Samsung will automatically tect you a code your phone will sync with this code opening your samsung account. Hope this helps.
Click to expand...
Click to collapse
Yeah. You lost all your data because you flashed an older android version firmware. I guess I should stop trying to help people.