I received my bootloader unlock code yesterday so started the procedure to unlock it.
I got the dreaded 50% error, I fixed this by connecting the phone in fastboot to the miui sweet where it let me update to the latest version # 7.5. I installed TWRP and then after rebooting I lost wifi and the use of TWRP.
At the moment after spending all morning on the internet looking for answers I am stuck. My phone works but has no wifi and cannot access TWRP.
I have seen there is a tut for the soup kitchen to create a new img file but cannot find the original version I need.
I want to install the CM 13 rom, please someone offer advise on next steps to take.
Thanks
Gary
Garyj881 said:
I received my bootloader unlock code yesterday so started the procedure to unlock it.
I got the dreaded 50% error, I fixed this by connecting the phone in fastboot to the miui sweet where it let me update to the latest version # 7.5. I installed TWRP and then after rebooting I lost wifi and the use of TWRP.
At the moment after spending all morning on the internet looking for answers I am stuck. My phone works but has no wifi and cannot access TWRP.
I have seen there is a tut for the soup kitchen to create a new img file but cannot find the original version I need.
I want to install the CM 13 rom, please someone offer advise on next steps to take.
Thanks
Gary
Click to expand...
Click to collapse
https://youtu.be/G_P7Qd3kpAI follow this video
Thanks for the link, I am struggling to get it to work.
I will look at uploading some pictures to better explain myself.
Ok here is a picture.
I can't complete the guide in the video.
When I get to the stage with CMD, I verify its sees my phone but when I drag the twrp image over I get the error below.
The first error is where I forgot to drag over the image file, second is what I need help with.
Okay, from what I understand, you flashed a Stock MIUI ROM through fastboot, right? And then you are trying to flash TWRP.
From what I know, flashing a firmware through Fastboot relocks the bootloader. Can you check if you bootloader is locked or unlocked? If it is locked, then unlock it again and then flash TWRP.
use the command "fastboot oem device-info" to check bootloader status.
If it is locked, unlock bootloader again.
If already unlocked, then flash TWRP using "fastboot flash recovery twrp-3.0.2-2-kenzo.img"
or alternatively use "fastboot boot recovery twrp-3.0.2-2-kenzo.img" to boot into TWRP without flashing it and then install the recovery image from within it. You do have to copy the TWRP img file to the phone storage first.
It says bootlodaer unlocked - true, so that's fine.
I cannot install twrp at all through cmd at all from the video.
I must be missing someting but dont know what. Is there an alternative method of installing it?
Garyj881 said:
Ok here is a picture.
I can't complete the guide in the video.
When I get to the stage with CMD, I verify its sees my phone but when I drag the twrp image over I get the error below.
The first error is where I forgot to drag over the image file, second is what I need help with.
Click to expand...
Click to collapse
draging the file into cmd copies the path of the file with its name which gives you an error..the error just says that it is unable to locate the file.just delete "c\adb " from the below line the you are done.
fastboot flash recoveryc:\adb\twrp-3.0.2.2-kenzo.img
the right way to do is
fastboot flash recovery twrp-3.0.2-2-kenzo.img
2'nd step :- fastboot boot twrp-3.0.2-2-kenzo.img
Hitesh, with your help I got it top work and sucsessfully installed CM13.
Rather than creating a new thread and spamming the forums, I hope you can also help with the below.
Link to my issues is here in this thread
http://forum.xda-developers.com/redmi-note/development/rom-aicp-11-dior-t3273430/page3
My post http://forum.xda-developers.com/showpost.php?p=68186362&postcount=27
After trying the CM13 and not being happy with the performance I decided to try aicp 11.00 Dior Nightly but can't install due to error.
I now have a phone with no system on so usesless to me.
I need to get this working today if you or someone could help me.
i made the error of not backing up the CM but I have MIUI backup but dont want to go back to this for fear of Bricking my phone.
Ok, this is where I am at.
I believe my phone is bricked.
I followed online guide to no avail. - http://en.miui.com/thread-235865-1-1.html
I run fasboot then EDL mode but MIflash will not work, please see below picture.
Please help me fix my RN3
Thank you
Garyj881 said:
Ok, this is where I am at.
I believe my phone is bricked.
I followed online guide to no avail. - http://en.miui.com/thread-235865-1-1.html
I run fasboot then EDL mode but MIflash will not work, please see below picture.
Please help me fix my RN3
Thank you
Click to expand...
Click to collapse
Click on browse>advanced and show me what you have selected
justinxfan said:
Click on browse>advanced and show me what you have selected
Click to expand...
Click to collapse
Thank you for your reply, was losing hope
I attached my phone in EDL mode, and this flashes in bottom tray.
This is picture of advanced section.
And again error at end when doing flash.
Thanks again.
I m going to work right now, so wont be able to reply fo 8 hrs
Garyj881 said:
Thank you for your reply, was losing hope
I attached my phone in EDL mode, and this flashes in bottom tray.
This is picture of advanced section.
And again error at end when doing flash.
Thanks again.
I m going to work right now, so wont be able to reply fo 8 hrs
Click to expand...
Click to collapse
That's whats wrong. You have the wrong files selected
fastboot script: flash all.bat
flash programmer go into images folder and select the file named something like firehose 8976 or similar
also for rawprogram and patch find the corresponding xml files in the images folder.
Garyj881 said:
I received my bootloader unlock code yesterday so started the procedure to unlock it.
I got the dreaded 50% error, I fixed this by connecting the phone in fastboot to the miui sweet where it let me update to the latest version # 7.5. I installed TWRP and then after rebooting I lost wifi and the use of TWRP.
At the moment after spending all morning on the internet looking for answers I am stuck. My phone works but has no wifi and cannot access TWRP.
I have seen there is a tut for the soup kitchen to create a new img file but cannot find the original version I need.
I want to install the CM 13 rom, please someone offer advise on next steps to take.
Thanks
Gary
Click to expand...
Click to collapse
I know this issue. Wait for 3-4 more days. And then again try with Mi Tools and official unlock code. It will work.
Dhananjay Bhosale on youtube explained this problem already.
justinxfan said:
That's whats wrong. You have the wrong files selected
fastboot script: flash all.bat
flash programmer go into images folder and select the file named something like firehose 8976 or similar
also for rawprogram and patch find the corresponding xml files in the images folder.
Click to expand...
Click to collapse
I don't think my pc is seeing my phone correctly.
I load EDL and phone goes black with red flashing led.
When black, I open up MIFlash. I then browse for Kenzo image and click ok then refresh.
I then click advanced and confirm I have chosen correct image, raw and patch file - which I have.
I then click flash and get error as pictured.
So it look likes I was doing everything correct but still doesn't work.
I doesn't show in picture but link to programmer, raw and patch are as follows.
Programmer - C:\Users\Gary\Desktop\kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global\images\prog_emmc_firehose_8976_ddr.mbn
Raw - C:\Users\Gary\Desktop\kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global\images\rawprogram0.xml
Patch - C:\Users\Gary\Desktop\kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global\images\patch0.xml
So I think links are correct.
Before I tried Dior, I updated to V7.5. Image file is for Kenzo V7.3.7.
Not sure if it matters.
justinxfan said:
That's whats wrong. You have the wrong files selected
fastboot script: flash all.bat
flash programmer go into images folder and select the file named something like firehose 8976 or similar
also for rawprogram and patch find the corresponding xml files in the images folder.
Click to expand...
Click to collapse
bravonova said:
I know this issue. Wait for 3-4 more days. And then again try with Mi Tools and official unlock code. It will work.
Dhananjay Bhosale on youtube explained this problem already.
Click to expand...
Click to collapse
Hi Bravonova.
I already fixed this, see http://forum.xda-developers.com/showpost.php?p=68187140&postcount=8
If I get this fixed today, I will donate £10.00 to charity of your choice
Garyj881 said:
I don't think my pc is seeing my phone correctly.
I load EDL and phone goes black with red flashing led.
When black, I open up MIFlash. I then browse for Kenzo image and click ok then refresh.
I then click advanced and confirm I have chosen correct image, raw and patch file - which I have.
I then click flash and get error as pictured.
So it look likes I was doing everything correct but still doesn't work.
I doesn't show in picture but link to programmer, raw and patch are as follows.
Programmer - C:\Users\Gary\Desktop\kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global\images\prog_emmc_firehose_8976_ddr.mbn
Raw - C:\Users\Gary\Desktop\kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global\images\rawprogram0.xml
Patch - C:\Users\Gary\Desktop\kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global\images\patch0.xml
So I think links are correct.
Before I tried Dior, I updated to V7.5. Image file is for Kenzo V7.3.7.
Not sure if it matters.
Click to expand...
Click to collapse
In the browse don't select the images folder select the folder that contains everything.
HI, no difference I'm afraid.
If possible could I add you to Skype for making this easier?
Just noticed in MiFlash for device name it stays as COM3 and doesn#t show device name, could it be that it can't see my devioce properly?
I feel like Im typing to myself here but trying to give as much information as possible.
Reading another unbrick method. It says open adb folder and open cmd with shift. In CMD I type devices, it then say list of devices attached BUT nothing there!
Then I type adb reboot edl - error device (null) not found.
I don't think it sees my phone......
Hopefully that is enough for you to know the problem.
How to fix please?
Garyj881 said:
I don't think my pc is seeing my phone correctly.
I load EDL and phone goes black with red flashing led.
When black, I open up MIFlash. I then browse for Kenzo image and click ok then refresh.
I then click advanced and confirm I have chosen correct image, raw and patch file - which I have.
I then click flash and get error as pictured.
So it look likes I was doing everything correct but still doesn't work.
I doesn't show in picture but link to programmer, raw and patch are as follows.
Programmer - C:\Users\Gary\Desktop\kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global\images\prog_emmc_firehose_8976_ddr.mbn
Raw - C:\Users\Gary\Desktop\kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global\images\rawprogram0.xml
Patch - C:\Users\Gary\Desktop\kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global\images\patch0.xml
So I think links are correct.
Before I tried Dior, I updated to V7.5. Image file is for Kenzo V7.3.7.
Not sure if it matters.
Click to expand...
Click to collapse
If the error shows reached the end you need to restart the pc
And as far as I see from your pics you should extract the tgz rom to C:/ROM/MIUI and all files should be in that
Remember when you extract a file it first creates a folder with the name of the file and then extracts using winRar.
This worked for me
Hit thanks if I helped.
---------- Post added at 08:48 PM ---------- Previous post was at 08:44 PM ----------
How did you fixed the 50% hurdle? By just flashing the latest firmware and then trying to unlock? You did officially unlock right?
B'coz it didn't work for me.
Related
HELP Please !
My htc explorer initially got stuck at the htc logo at boot and won't go any further.
I searched for solutions on xda and tried to install Cyanogenmod 10.2 on it. Now the device gets stuck at cyanogenmod boot animation (was going on until half -an-hour ! )
Next i searched some more, caught TWRP recovery on a glance. Tried installing it, but my Laptop ( Win8.1 x64 ) doesnt recognize the device whatsover, even after installing the adb drivers and HTC SYNC. !
Now i finally installed FLYROM v4 refined, and the phone is stuck at htc 'quietly brilliant' logo . !
PLEASE get me out of this misery ! I want my little buddy back in action
Please .. Anybody ?
Nobody to help ?
I dont have an HTC phone or knowledge. but in our phone. we use tool to flash stock firmware. as in pure stock. removing anything. give it a try
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
http://forum.xda-developers.com/showthread.php?t=1816836 this link shows tutorials on how to unbrick your phone. hope i helped
Thanks, but no luck
pjohn23 said:
I dont have an HTC phone or knowledge. but in our phone. we use tool to flash stock firmware. as in pure stock. removing anything. give it a try
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
http://forum.xda-developers.com/showthread.php?t=1816836 this link shows tutorials on how to unbrick your phone. hope i helped
Click to expand...
Click to collapse
I tried many custom ROMs and ended up bootlooping all of them ( Indefinite cyanogenmod animation , for about 48 minutes on average) !
I want to do a full erase of the device and reinstall these ROMs , bu i don't know how to do it .. searched for quite long but no proper instuctions on that
DrSakethReddy said:
I tried many custom ROMs and ended up bootlooping all of them ( Indefinite cyanogenmod animation , for about 48 minutes on average) !
I want to do a full erase of the device and reinstall these ROMs , bu i don't know how to do it .. searched for quite long but no proper instuctions on that
Click to expand...
Click to collapse
dont you have flashtools?
More INFO needed.
pjohn23 said:
dont you have flashtools?
Click to expand...
Click to collapse
I didn't get you.
I have these tools mentioned in almost every HTC explorer resuscitation page :
1. HTC Sync
2. adb drivers
3. Fastboot driver
4. TWRP 2.x.x
5. Stock ROM and
6. 6 varieties of Custom ROMs ! (all get stuck in bootloop )
DrSakethReddy said:
I didn't get you.
I have these tools mentioned in almost every HTC explorer resuscitation page :
1. HTC Sync
2. adb drivers
3. Fastboot driver
4. TWRP 2.x.x
5. Stock ROM and
6. 6 varieties of Custom ROMs ! (all get stuck in bootloop )
Click to expand...
Click to collapse
what i mean is windows tool that can flash stock rom on your phone. if it has. you should use that and wipe everything
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
es0tericcha0s said:
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
Click to expand...
Click to collapse
Thank you very much, for your reply
I hit thanks button too
I'll get back to you soon as i perform the steps you've stated in a Win 7 PC.
sadly NO
pjohn23 said:
what i mean is windows tool that can flash stock rom on your phone. if it has. you should use that and wipe everything
Click to expand...
Click to collapse
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
DrSakethReddy said:
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
Click to expand...
Click to collapse
Goodluck bro. sorry for no help. i dont have HTC and everythings waay more easier on a xperia phone
DrSakethReddy said:
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
Click to expand...
Click to collapse
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
pjohn23 said:
Goodluck bro. sorry for no help. i dont have HTC and everythings waay more easier on a xperia phone
Click to expand...
Click to collapse
Hey ! C'mon. Don't say u didn't help !
Providing a light to this thread for others to answer it too was the read deal you made !
Thanks again, bro
AWESOME !
es0tericcha0s said:
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
Click to expand...
Click to collapse
Great ! I love getting things done easier with tools !
I'll give this a shot too, and then if this doesn't work, i'll head for the recovery.img flashing .
Thanks
Unsuccessful ! (error)
es0tericcha0s said:
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
Click to expand...
Click to collapse
Hello, i followed the exact steps that you provided, but i got an error in the cmd saying :
"unknown partition 'boot,img'
error: cannot determine image filename for 'boot.img' !
I'll try the RUU method now.
Alas ! Error again
es0tericcha0s said:
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
Click to expand...
Click to collapse
I've done the adb command method and failed, now i've even performed updating it with RUU, but i have this result :
ERROR 155: unkown error
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and update your phone.
DrSakethReddy said:
Hello, i followed the exact steps that you provided, but i got an error in the cmd saying :
"unknown partition 'boot,img'
error: cannot determine image filename for 'boot.img' !
I'll try the RUU method now.
Click to expand...
Click to collapse
I'm so sorry! I left out something in that command! It's:
fastboot flash boot boot.img
Sorry, poor proofreading skills.
As far as the 155 error, I think you also might need to do this in bootloader / fastboot mode (if the previous command doesn't get you going with the rom you are already on - it should):
fastboot oem lock
Then re-run RUU.
Sorry guys, for a very late reply.
I tried all the methods you said, with the new command too, but alas ! The device didn't get a life.
I'm gonna use it as a very costly paperweight now !
Hard brick for OPT happens when you change critical partitions. It will follow improper firmware flash or accidental erase of certain partitions. The phone won't show any response when hardbricked.
The solution for OPT is similar to OPO - you just need a Qualcomm driver and a recover package. The only full recovery package available is very big and it restore the phone to Hyrdogen OS, with everything wiped. So it would not be very attractive.
Fortunately, thanks to this post from Chinese supporting forum, a minimal version of restore package is provided. It does not wipe user data and guarantee a recovery entry. you would normally be freed using this package. if not, please use the full package in the end of the post
Download link for driver
Download link for Recovery tool
uncompress the files to a local folder.
First step, turn off drive signature enforcement in windows 8/8.1/10. Tutorial Here
Second step, hold the power key for 20 seconds to force turn off power. connect OPT to usb, hold volume+ and power until your PC finds a new hardware (if it doesn't work, try hold volume+ and volume- together)
Third step, go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics 9006" device. Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Fourth step, when the driver is installed properly, run MSM8994DownloadTool.exe in the recover tools folder, using admin privileges . Clear start in top left corner and wait for it to finish.
Now your OPT should be able to enter TWRP recovery. It still won't boot but you can manually flash anything again (like the full Oxygen OS package).
The procedure is tested by me twice. Enjoy!
p.s: sorry the recovery image in the A2001_save_brick_mini.rar is Chinese. Please download this file, change the name to recovery.img and substitute the file in the recovery tool before flashing.
UPDATE：full Oxygen OS 150805 restoration package for those who experience recovery entry problem. Note that this package wipes everything including internal storage!
Awesome, I will go ahead and make a full recovery tool that includes these files as well as the latest version of OxygenOS as I did with the Oneplus one.
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
CoreGaming said:
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
Click to expand...
Click to collapse
Like i did before with my mod of the toolkit
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
okay and were can i get this package for the OPT?
CoreGaming said:
okay and were can i get this package for the OPT?
Click to expand...
Click to collapse
Havn't made it yet, still need to work on it. It is a little different than OPO so it might take some time.
okay this will be great. Take your time i'm ready
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Lord Boeffla said:
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Click to expand...
Click to collapse
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Zyxxeil said:
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Click to expand...
Click to collapse
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Click to expand...
Click to collapse
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Click to expand...
Click to collapse
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Lord Boeffla said:
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Click to expand...
Click to collapse
HydrogenOS definitely has the option because it is how I flashed TWRP in the first place
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
Without recovery how do you flash hydrogenOS?
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Wow thanks, I was trying to do it with the one you posted but I couldn't since it was missing the info for system sectors. Now i can make my tool
Zyxxeil said:
Without recovery how do you flash hydrogenOS?
Click to expand...
Click to collapse
Using this tool and the full recovery package? Or am I missing something here?
khr0n0s said:
Using this tool and the full recovery package? Or am I missing something here?
Click to expand...
Click to collapse
The tool posted does not contain a system, but he is going to post the full one soon.
Zyxxeil said:
The tool posted does not contain a system, but he is going to post the full one soon.
Click to expand...
Click to collapse
Precisely, that is exactly what I meant. Fingers crossed that will solve this.
It could be I successfully recoverd following a hint by user @Zyxxeil (many thanks for the help).
If all works I will post soon what I did.
But - have everything running now again. Next I try to flash twrp again and root. If that worked, I will post the steps.
Andi
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Very nice. Wait for it...
Is a Version with Oxygen OS also aviable?
I would like to know how to upgrade to a new ROM (Lollipop or better) on my Verizon HTC One Max with the option to return to stock. Software Information: 4.4.2, Sense 6.0, 3.09.605.3, 6.20, 4.60_002, 15432, 5
I was told to use (and did) Sunshine and then downloaded SuperSU from Google Store (per very detailed instructions and was told to not choose TWRP when the question popped up to choose one or the other (common/normal?)).
My phone is now UNLOCK and S-OFF as well as Rooted (but I'm having a lot of problems with blank screens, etc. and even had the black screen with the red ! in a red triangle (and I don’t know how I got it to boot up again (pushed pwr buttons, vol +/-, etc.)). However, that is as far as I’ve gotten. Confused am I.
I don’t know how to flash; however, I’ve been trying to figure it out, but I’m lost.
I’ve downloaded a lot of files from other threads, but the instructions, while detailed, didn’t say HOW to flash or add TWRP where I (a NEWBORN NEWBIE/NOOBIE) could understand, etc. Is there a place where all this is together?
Am I out of luck or would someone PLEASE help me fix and upgrade it with the option to return to stock if needed? I would love to have Sense 7.0, if possible. I apologize for such a long post/thread.
THANK YOU SO VERY MUCH!!!!!
P. S. My phone is now Prepaid Verizon (was Postpaid). Don't know if that matters. I have pics of the files I downloaded from one of your great guys, but they are on my computer. Not sure how to upload. I AM GLAD THAT I FOUND YOUR SITE!!!!!
@LoveSpock I am going to make this short and simple...
First off the Verizon Max software only goes up to 4.4.2. If you want to upgrade you'll need a custom rom which is why you S-OFF and unlocked...
You will need to get familiar with fastboot commands. Google is your friend on how to use if you don't know how to. Here is the link to the TWRP image for your device. http://flyhalf205.com/recoveries/openrecovery-twrp-2.8.7.1-t6univ.img Once you get fastboot setup you will type in the command fastboot flash recovery openrecovery-twrp-2.8.7.1-t6univ.img Make sure you have everything in the same directory when executing the command.
From there you are free to wipe then flash anything you would like. Wiping will delete your data so text, contacts that are stored on local phone(not sim or google) will be deleted.
@Flyhalf205
Thank you for your response and instructions. Does this mean I don't need to do anything to the SUPERSU that is already on the phone (and what it did)?.... Following your instructions will wipe everything?
I'll definitely need to take out my sd card. I've saved a ton of stuff on it. ...and backup my contacts and text messages.
I have some more googling and try to learn what you wrote for me to learn. I'll also have to find out what ROM to use....
Your Padawan thanks you.
LoveSpock said:
@Flyhalf205
Thank you for your response and instructions. Does this mean I don't need to do anything to the SUPERSU that is already on the phone (and what it did)?.... Following your instructions will wipe everything?
I'll definitely need to take out my sd card. I've saved a ton of stuff on it. ...and backup my contacts and text messages.
I have some more googling and try to learn what you wrote for me to learn. I'll also have to find out what ROM to use....
Your Padawan thanks you.
Click to expand...
Click to collapse
Shouldn't worry about supersu. Most custom ROMs are going to have that prebuilt into it. Once you get TWRP we will go further into detail about how stuff works.
If you use twrp no need to take your SD card out just go to setting and unchecked SD card and like lovespoke said make sure to dl the right file you can dl right fastboot files here on xda just search it
Hey! Don't mean to hijack the thread but I'm in the same boat. I've never rooted and I'm looking to root my Verizon HTC one max. I'd also like to maybe install a custom Rom but I'm a noob so I'm not quite sure what I'm doing. Ok so it's my understanding that sunshine will root, s-off, AND unlock my boot loader? Btw I have no idea what those terms mean. Anyway, if someone could please confirm that about sunshine, it would really help me out. I've already downloaded and installed sunshine on my phone but I haven't paid the $25 yet.
Xx Moe, I strongly suggest you READ the various threads on XDA about unlocking bootloaders, gaining S-OFF and rooting. You can easily brick a device and there's much less support for the Max now than there was when it came out more than two years ago.
I don't believe Verizon HTC One Max's can be rooted without unlocking bootloader/gaining S-OFF and the exclusive method for that is Sunshine (unless you know someone with a Java card). Once you're bootloader unlocked and S-OFF, you can then "flash" any partition on the device and that's how to brick the device.
Once you are bootloader unlocked and S-OFF, you start by flashing a 'recovery', which is usually the latest version of TWRP for the HTC One Max. Don't flash a recovery for a different device. (Google "Team Win Recovery Project"). Once you have a custom recovery you can "wipe" your device and flash a new ROM.
Wiping deletes all data, or some data, depending upon how you wipe, and there are not very many Verizon HTC One Max ROMs out there that are fully functional. Check the threads, one sticky thread has a listing of ROMs.
Finally, I don't believe anyone has gotten Marshmallow going on a Max, so expect the "best" you'll be able to do is a Lollipop ROM or a Cyanogen Mod equivalent.
Awesome! Thanks for the super quick reply. So yes, sunshine will s-off and unlock boot loader. That seemed to be the million dollar question since (like you said) the one max doesn't have very much support anymore. I'm definitely going to keep reading the forums because I don't want to brick my phone. I've also been watching some tutorials on YouTube. Everything (so far) seems pretty straight forward now, but you can never be too careful. Thanks for your help hgoldner!
Flyhalf205 said:
@LoveSpock I am going to make this short and simple...
First off the Verizon Max software only goes up to 4.4.2. If you want to upgrade you'll need a custom rom which is why you S-OFF and unlocked...
You will need to get familiar with fastboot commands. Google is your friend on how to use if you don't know how to. Here is the link to the TWRP image for your device. http://flyhalf205.com/recoveries/openrecovery-twrp-2.8.7.1-t6univ.img Once you get fastboot setup you will type in the command fastboot flash recovery openrecovery-twrp-2.8.7.1-t6univ.img Make sure you have everything in the same directory when executing the command.
From there you are free to wipe then flash anything you would like. Wiping will delete your data so text, contacts that are stored on local phone(not sim or google) will be deleted.
Click to expand...
Click to collapse
Hey flyhalf, is there a thread on here on how to learn about adb fastboot, and flash the custom recovery for noobs? I cant seem to find it. I'm trying to install a custom rom on my htc one max but this is my first time ever rooting/unlocking an android. Ive searched the site but i cant find a tutorial on how to install the custom recovery or learn about adb yet. I have sunshine already on my phone but i havent used it yet because i want to know exactly what im doing before i pay the $25. Any help is appreciated. I already know how to get into the bootloader by pressing the power and volume down buttom at the same time while the phone is turned off.
Xx MOE said:
Hey flyhalf, is there a thread on here on how to learn about adb fastboot, and flash the custom recovery for noobs? I cant seem to find it. I'm trying to install a custom rom on my htc one max but this is my first time ever rooting/unlocking an android. Ive searched the site but i cant find a tutorial on how to install the custom recovery or learn about adb yet. I have sunshine already on my phone but i havent used it yet because i want to know exactly what im doing before i pay the $25. Any help is appreciated. I already know how to get into the bootloader by pressing the power and volume down buttom at the same time while the phone is turned off.
Click to expand...
Click to collapse
I'm heading to bed now. If I get time tomorrow I'll try to explain. If not we can setup team viewer and I can just set your computer up for you.
Sent from my Nexus 9 using Tapatalk
Flyhalf205 said:
I'm heading to bed now. If I get time tomorrow I'll try to explain. If not we can setup team viewer and I can just set your computer up for you.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
That would be awesome, but i think i found something from google. https://twrp.me/devices/htconemaxverizon.html
I downloaded the sdk and corresponding java that the site recommended. I attached a screenshot of my pc to show where im at in that process.
Xx MOE said:
That would be awesome, but i think i found something from google. https://twrp.me/devices/htconemaxverizon.html
I downloaded the sdk and corresponding java that the site recommended. I attached a screenshot of my pc to show where im at in that process.
Click to expand...
Click to collapse
I also downloaded the android-sdk_r24.4.1-windows.zip file but i moved it out of my downloads file, so it didn't show up on my screenshot
Xx MOE said:
I also downloaded the android-sdk_r24.4.1-windows.zip file but i moved it out of my downloads file, so it didn't show up on my screenshot
Click to expand...
Click to collapse
Download the platform tools and the android usb driver. Don't need anything else.
But basically if your s-off yet. Boot into HBOOT. Power off phone and hold down both power button and the volume down button. Select fastboot using the power button. Your computer should hopefully automatically pick up drivers and call the device "My HTC" in the device manager. If not you'll need to go in and manually assign the downloaded driver using the link above to the Android device in device manager.
Download twrp image file into the same directory as the platform tools downloaded to. In windows, right click while holding down shift anywhere on the white blank area in platform tools and click on "open command window here".. From there you will type in the command fastboot flash recovery recoveryFileName.img
If it says waiting for device. Check device manager and make sure the driver is installed right.
Flyhalf205 said:
Download the platform tools and the android usb driver. Don't need anything else.
But basically if your s-off yet. Boot into HBOOT. Power off phone and hold down both power button and the volume down button. Select fastboot using the power button. Your computer should hopefully automatically pick up drivers and call the device "My HTC" in the device manager. If not you'll need to go in and manually assign the downloaded driver using the link above to the Android device in device manager.
Download twrp image file into the same directory as the platform tools downloaded to. In windows, right click while holding down shift anywhere on the white blank area in platform tools and click on "open command window here".. From there you will type in the command fastboot flash recovery recoveryFileName.img
If it says waiting for device. Check device manager and make sure the driver is installed right.
Click to expand...
Click to collapse
Ok, so if im doing this correctly, the twrp img should be in the platform tools folder and my computer should recognize my phone as "my htc" as shown in my attached screenshot...
Xx MOE said:
Ok, so if im doing this correctly, the twrp img should be in the platform tools folder and my computer should recognize my phone as "my htc" as shown in my attached screenshot...
Click to expand...
Click to collapse
Yes. That is correct so far.
Flyhalf205 said:
Yes. That is correct so far.
Click to expand...
Click to collapse
Perfect! Thank you so much! now all i have to do is use sunshine to s-off/unlock bootloader and follow this thread: http://forum.xda-developers.com/showthread.php?t=2498746 to install custom recovery and i should now be able to flash custom roms! Thanks for your help! A donation will be coming your way soon! :good::good::good::highfive:
Almost Ready....
Flyhalf205 said:
Shouldn't worry about supersu. Most custom ROMs are going to have that prebuilt into it. Once you get TWRP we will go further into detail about how stuff works.
Click to expand...
Click to collapse
I've been out of commission... Sorry about the long wait.
I'm sure you've been very busy.
I found the fastboot.exe file and placed it and your twrp file into a folder on my desktop. Before I run fastboot and add your twrp img file, what would the next step be? .... I don't have have a ROM yet to add to the phone. Should I have that first? Would you please direct me to the right one for me? I noted in one of your replies to another member that there isn't a Marshmallow one, yet.
Do I need the ADB file?
Thank you,
Your Padawan.
Flyhalf205 said:
Yes. That is correct so far.
Click to expand...
Click to collapse
Would you recommend uninstalling the HTC program that automatically picks up the phone?
LoveSpock said:
I've been out of commission... Sorry about the long wait.
I'm sure you've been very busy.
I found the fastboot.exe file and placed it and your twrp file into a folder on my desktop. Before I run fastboot and add your twrp img file, what would the next step be? .... I don't have have a ROM yet to add to the phone. Should I have that first? Would you please direct me to the right one for me? I noted in one of your replies to another member that there isn't a Marshmallow one, yet.
Do I need the ADB file?
Thank you,
Your Padawan.
Click to expand...
Click to collapse
I forget if you were s-off or s-on but you will need to be s-off or your bootloader will need to be unlocked.. You don't need a rom just yet. You could flash recovery and flash root for starters. But once you get it flashed we can start on what to do next.
Update...
Flyhalf205 said:
Shouldn't worry about supersu. Most custom ROMs are going to have that prebuilt into it. Once you get TWRP we will go further into detail about how stuff works.
Click to expand...
Click to collapse
Flyhalf205 said:
I forget if you were s-off or s-on but you will need to be s-off or your bootloader will need to be unlocked.. You don't need a rom just yet. You could flash recovery and flash root for starters. But once you get it flashed we can start on what to do next.
Click to expand...
Click to collapse
Sorry... I started the thread back in January. I've been out of commission and starting over.
I had used Sunshine to S-off and Unlock. I used SU to root. I knew nothing about flashing or fastboot and am still learning. One of your original responses to my original post said that google was my friend, so I googled per your advice and found some information on fastboot.
I don't know what flash root means in your response above.
You had also gave me the link to the TWRP image for my phone. You also wrote "Make sure you have everything in the same directory when executing the command." I've added 2 of the pics again as well as one of your img file in the directory I created when I loaded Android Studio.
The Android Studio I downloaded is the latest. Does that make a difference? I did find info on this site about a minimal adb and fastboot. Would that have been better?
I'm imagining my phone will be out of commission until the new ROM is installed, right? (See how I'm still such a Newbie/Noobie!)
Thank you!
Your Padawan
Hi there guys,
I'm new to the forum so apologies if this has been posted in the wrong place.
So I was directed to this forum to attempt to solve a different problem but in my hast, I have caused an even bigger problem!
So initially I was having problems with the new Android Wear update with regards to rooting, so I wanted to find a way to roll the software back or restore the device to stock.
I came across this post http://forum.xda-developers.com/g-watch/development/tool-lg-g-watch-return-to-stock-t3158349 and attempt to do as advised, but half way through the process, the program froze. I then tried to reset the watch from the button at the back, but the watch is now stuck on the fastboot menu. I used ADB to see if I could still connect to the device but no devices can be found.
I have checked the device manager and can see the device as "Android Bootloader Interface" but can't seem to get it past the fastboot menu.
Any help would be much appreciated.
Thanks in advance.
just do it again, as long you can get fastboot, you are safe.
Jaocagomez said:
just do it again, as long you can get fastboot, you are safe.
Click to expand...
Click to collapse
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Montezz1 said:
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Click to expand...
Click to collapse
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Xmaster24 said:
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Click to expand...
Click to collapse
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Montezz1 said:
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Click to expand...
Click to collapse
Check the bootloader lock status and report back
Xmaster24 said:
Check the bootloader lock status and report back
Click to expand...
Click to collapse
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Montezz1 said:
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Click to expand...
Click to collapse
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Xmaster24 said:
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Click to expand...
Click to collapse
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Montezz1 said:
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Click to expand...
Click to collapse
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Xmaster24 said:
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Click to expand...
Click to collapse
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Montezz1 said:
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Click to expand...
Click to collapse
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Xmaster24 said:
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Click to expand...
Click to collapse
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Montezz1 said:
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Click to expand...
Click to collapse
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Xmaster24 said:
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Click to expand...
Click to collapse
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Montezz1 said:
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Click to expand...
Click to collapse
This device I just want to know if you ever actually successfully flashed anything to this device
Xmaster24 said:
This device I just want to know if you ever actually successfully flashed anything to this device
Click to expand...
Click to collapse
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Montezz1 said:
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Click to expand...
Click to collapse
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Montezz1 said:
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Click to expand...
Click to collapse
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Xmaster24 said:
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Click to expand...
Click to collapse
I do not believe it...
After all of this, it was the drivers...
I don't get it though!! I tried to reinstall them before and nothing changed!
It's only when I completely deleted them and reinstalled that it worked.
Honestly dude, thank you so much for your help and patience. My watch is now working and paired with my phone.
I'm waiting for it to sync but hopefully I will be able to run ADB and all will be well again
Thanks you so much again.
woops didn't put this in guides, sorry
This should work for any KDZ firmware of any LG Device, but figured I'd write this for the Wing, as so far, its the only LG phone I own and the one I'm most determined with
This is not a full Root Tutorial. This is a step in the correct direction though. These are the After-Steps, so bootloader unlock is still needed. Sorry
What You'll need
- KDZ Tools (see attachment -- virus total scan just because: https://www.virustotal.com/gui/file...zODc2ZTViOWQ1MTlmN2Q0NzFiMjI6MTYzNzgyMTYwNg==)
- Firmware KDZ file
- Magisk Manager installed on device that IS NOT your LG Wing (at least for me, explained below)
Instructions (video coming soon)
1.) Download KDZ Tools and extract them to a folder somewhere.
-- I usually make one on my external drive and drop stuff there, but desktop works too
2.) Download whatever firmware KDZ file you need
3.) Put that KDZ File in the same folder as the KDZ Tools
4.) Run "OneKeyExtraction.bat" and select Y if the KDZ is in the folder with this same file
5.) This takes A LONG WHILE and you need a good large bit of storage space available (50gb+) because the extraction goes raw format and some image files at first take up 20+GB as 1 file
6.) Once complete, you should have a folder named "F100X_usersigned_etc" ... open that to find your img firmware files. There's 31GB of IMG files here if its the Android 11 1020 KR FW
7.) Copy one of the boot.img to your device with Magisk Manager installed
-- The reason I stated on a different device, is that at least for me, Magisk Manager kept failing to patch on my LG Wing. When I put the boot.img on my OnePlus 7 Pro 5G, it patched just fine
8.) Open magisk manager, select Install, Select and Patch a File, select the Boot.img and patch it
9.) Once patched, that's a rooted boot.img, pull it off your device back to your computer and hold on to it for when we get a way to flash it and root the device!
root theory:
Interupting the LGUp flashing process of firmware when it gets to boot partitions to load custom boot.img's. How to do this exactly, not sure. If there's a way we can re-kdz these files from KDZ tool, that might work too
I can tell you right now, it wont work because the bootloader is locked. The hash of the patched boot.img on the phone won't match and you will get "Your device has failed a routine check, your phone is unbootable."
Sorry to debunk your theory. We need a firehose and a engineering bootloader.
Leronex_1 said:
I can tell you right now, it wont work because the bootloader is locked. The hash of the patched boot.img on the phone won't match and you will get "Your device has failed a routine check, your phone is unbootable."
Sorry to debunk your theory. We need a firehose and a engineering bootloader.
Click to expand...
Click to collapse
hey it was worth a shot
KaptinBoxxi said:
hey it was worth a shot
Click to expand...
Click to collapse
Sure need lg wing firehose , can help to find it??
Bahmale said:
Sure need lg wing firehose , can help to find it??
Click to expand...
Click to collapse
Don't even have a clue of where to look so I won't be looking for it
i've done it with
"adb reboot fastboot
adb flash boot_a boot_a.img
adb flash boot_b boot_b.img"
both boot img a & b patched with magisk and by the way the phone i bought come with unlocked bootloader
mercuris said:
i've done it with
"adb reboot fastboot
adb flash boot_a boot_a.img
adb flash boot_b boot_b.img"
both boot img a & b patched with magisk and by the way the phone i bought come with unlocked bootloader
Click to expand...
Click to collapse
you got a rare device then. I can't even load fastboot, just download mode for lgup.
mercuris said:
i've done it with
"adb reboot fastboot
adb flash boot_a boot_a.img
adb flash boot_b boot_b.img"
both boot img a & b patched with magisk and by the way the phone i bought come with unlocked bootloader
Click to expand...
Click to collapse
What model do you have? I.e. F100VM10i
Glad you got it working btw!
kaluna00 said:
What model do you have? I.e. F100VM10i
Glad you got it working btw!
Click to expand...
Click to collapse
screen shot in another section shows it was a verizon demo model by the looks of it. F100V
KaptinBoxxi said:
screen shot in another section shows it was a verizon demo model by the looks of it. F100V
Click to expand...
Click to collapse
This is from the Verizon model (non demo).
Also i accidentally added the software version earlier.
i accidentally delete some lg apps and the phone stuck in bootloop the other day so i restore the phone using lgup just selected the refurbished option, the phone restored still in unlocked bootloader mode
mercuris said:
i accidentally delete some lg apps and the phone stuck in bootloop the other day so i restore the phone using lgup just selected the refurbished option, the phone restored still in unlocked bootloader mode
Click to expand...
Click to collapse
Hi, are you willing to dump the bootloader from your phone? Because it looks like you have a development device, so it has an unlockable engineering bootloader that can be used to unlock other LG Wing and Velvet devices.
Wish39 said:
Hi, are you willing to dump the bootloader from your phone? Because it looks like you have a development device, so it has an unlockable engineering bootloader that can be used to unlock other LG Wing and Velvet devices.
Click to expand...
Click to collapse
i dun mind just i dunno how to do that, if you can guide me it would be nice, or you can show me the instructions
mercuris said:
i dun mind just i dunno how to do that, if you can guide me it would be nice, or you can show me the instructions
Click to expand...
Click to collapse
Others can help on our discord server, I'll admit I'm not well versed on dumping partitions through stuff like ADB.
https://discord.gg/Zw9Uk9DWE2
mercuris said:
i dun mind just i dunno how to do that, if you can guide me it would be nice, or you can show me the instructions
Click to expand...
Click to collapse
You can also contact @Leronex_1 he can help you with dumping the bootloader
will do what i can to contribute, no problem
mercuris said:
will do what i can to contribute, no problem
Click to expand...
Click to collapse
Thanks, I recommend to join the Discord server though since me and Leronex are not always online on XDA, we are more active on Discord since its a live chat platform, not a forum like XDA. If you dont have a Discord account you can just create one.
If anyone else is reading this you are welcome to join the server as well.
Wish39 said:
Thanks, I recommend to join the Discord server though since me and Leronex are not always online on XDA, we are more active on Discord since its a live chat platform, not a forum like XDA. If you dont have a Discord account you can just create one.
If anyone else is reading this you are welcome to join the server as well.
Click to expand...
Click to collapse
will do
kaluna00 said:
This is from the Verizon model (non demo).
Also i accidentally added the software version earlier.
Click to expand...
Click to collapse
Reason I guessed demo device is because of the 0'd IMEI, but I guess as a dev device, 0'd imei is gonna be there too
Any progress on this? Sounded like you guys were making some good ground and then the thread went a little bit cold. No pressure. Just checking in. Thanks and Merry Christmas!