I have been having issues with the power button on my nexus s as seen here: http://forum.xda-developers.com/showthread.php?t=1504577. I attempted to lock my bootloader in order to take it in for service but i ran into some issues. I was able to flash a stock rom/recovery/radio package from http://forum.xda-developers.com/showthread.php?t=1445621 but my bootloader refuses to respond in any way. The volume buttons won't navigate the menu and any attempts to use fastboot or adb in bootloader fail because adb/fastboot cannot find the device. Anybody know how i can fix this? The only way for me to get service is to relock the bootloader but i can't relock it.
Which one did you take?
Related
So I tried to update to KitKat 4.4 and was never able to get passed the loading screen. I booted into ClockworkMod Recovery and wiped everything and now the device will not go passed the Google loading screen. The device is no longer recognized when I plug into the computer and I cannot access through Wugs.
I called Google and they are sending out an RMA for this device (I did not tell them it was unlocked) and they are sending out a replacement.
Is there anyway that I can remove ClockworkMod Recovery and re-lock this device without being able to access the device through a computer?
BrianXP7 said:
Whoa, RMA's should be only used for last resort bootloader bricks! Since you still have the bootloader ("Google" logo at startup), hold Power + Volume Down to enter Fastboot mode and try reflashing the factory images. Just to be safer, use the Universal Naked Drivers and skip with bootloader image. Don't forget to have the ADB and Fastboot binaries in the same folder. I wouldn't recommend toolkits as they don't expose new users with these situations.
If you need anything else, let me know. If I completely missed on what you needed, sorry about that.
Also, just as long as the bootloader update isn't interrupted or type "fastboot erase bootloader" you should be fine without an RMA.
Click to expand...
Click to collapse
thanks for the reply.
I am able to boot in recovery mode on the device and this is recognized by Wugs as "ADB - device on". When I attempt any flash, it checks Fastboot status and I receive notification that the "Fastboot device was not found". I cannot find a compatible driver when I am in fastboot mode running on a Windows 7 x64 machine.
Any idea on how I can get this N7 to function, return to stock, or at least remove ClockworkMod and lock the bootloader so I can RMA?
Hello,
today to my utmost rage i accepted system update, as i never had problems with getting the phoned rooted etc. after updates. But little did I know it was emui 5.0 along with android 7.0 update which pretty much rekt me.
The details of my phone:
HUAWEI VNS-L21
VNS-L21C09B336
kernel 4.1.18-g5e26674
Can provide more if needed.
The only thing I did was to get TWRP through SRKTool from here, xda, and rooting through it. And it worked flawlessly to my needs.
After the update I lost twrp, so without searching back then i tried to get it back through SRKTool to no avail. Downloaded newer SRKTool, same thing.
Then I started searching for more information regarding how to root my phone, during which I found out that I'm PHONE Unlocked FRP locked at fastboot.
And of course my "Disable OEM lock" in developer options is greyed out.
I tried p9toolkit from here, I tried command syntaxes in adb's fastboot, everything with USB debugging, nothing did anything. I can't flash either new TWRP or Revolution Recovery because the FRP lock isn't letting me flash anything, and for some reason i can't relock bootloader. I have correct unlock code, command line syntaxes just failed and p9toolkit produced errors saying that my unlock code is wrong (which is not true, I checked at huawei's site) or my phone is locked/unlocked depending on me trying to lock it or unlock it.
Even the built in recovery fails to get the package when I try to restore with it.
The boot message that "my device can't be trusted" is of course still present.
Feeling defeated I did a factory reset along with both wipes, hoping that'll let me change OEM lock in dev options and will clean the phone of many root related settings, but OEM lock is still greyed out.
Basically it seems the phone is locked in some kind of limbo of having bootloader unlocked but locked when you try to flash anything, because of FRP, and I can't relock to unlock FRP...and so on.
I would be extremely grateful if someone could help with sorting this out, basically I only want root, but it's just a mess overall.
Did you already try to dload an UODATE.APP file? If not:
1) create a folder on your external SD card named DLOAD
2) Download your firmware's update.zip file and extract it
3) put the extracted update.app file in the dload folder
4) boot phone with volume up + volume down + power
5) this will relock bootloader, install stock Android, stock recovery, stock boot (basically make every single thing stock) do you can start over again by rooting nougat!
I did not try it because I have no idea how to find the correct firmware for my phone, I have used the firmware finder from xda but the amount of results pretty much overwhelmed me so I didn't try anything with it, as i would probably get my situation worse.
EDIT: i found this site http://hwmt.ru/oth/HWFF/info/view.php?find_model= and there is update.zip of seemingly the same version as mine, is this the correct file http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v87119/f2/full/update.zip?
Uninstalled magisk and the screen is black, only vibrates when pressing power button or the right side of the screen. I don't even know how to turn off the phone. I was able to do it because the warning of the bootloader being unlocked appears. How I can flash stock rom? abd won't recognize the phone.
I saw https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448 this while searching but I'm scared since it locks the bootloader after.
Thank you
EnderEgg said:
Uninstalled magisk and the screen is black, only vibrates when pressing power button or the right side of the screen. I don't even know how to turn off the phone. I was able to do it because the warning of the bootloader being unlocked appears. How I can flash stock rom? abd won't recognize the phone.
I saw https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448 this while searching but I'm scared since it locks the bootloader after.
Thank you
Click to expand...
Click to collapse
Can you get into fastboot? Hold down both volume buttons together and see if you can force your device into fastboot mode. Then from there, get the TWRP img file and use fastboot to boot the image, then flash the stock OOS rom, either from TWRP install option or with adb sideload of you're comfortable doing that.
H4X0R46 said:
Can you get into fastboot? Hold down both volume buttons together and see if you can force your device into fastboot mode. Then from there, get the TWRP img file and use fastboot to boot the image, then flash the stock OOS rom, either from TWRP install option or with adb sideload of you're comfortable doing that.
Click to expand...
Click to collapse
I can, could you link me to a tutorial how to boot the image? I got it already, but unsure of how to proceed. Many thanks!
edit: now when I connect it to the PC it stays on the warning that the boot loader is unlocked
Now I was able to start TWRP but I still don't know how to send the file to the phone;
ADB recognizes the phone when TWRP is running
I think it's solved, thanks a bunch!
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked
Choose an username... said:
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked
Click to expand...
Click to collapse
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.
Spooderman46 said:
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.
Click to expand...
Click to collapse
I never mentioned the axon7toolkit. That one is finicky, I don't recommend it. I was talking about EDL Tool (you might even find it if you google it), it's here in the ROMs, kernels, development section.
Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Predatorhaze said:
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Click to expand...
Click to collapse
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?
SaintZ93 said:
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?
Click to expand...
Click to collapse
Sorry
Hi all,
I've ran into a problem while attempting to flash TWRP recovery to my Lemfo LEM8 watch. When I boot into the bootloader I found out that it is still locked so I tried unlocking the bootloader by executing the command: fastboot oem unlock. Now the problem is that in order to actually unlock the bootloader I have to press the vol up button which is a problem since the Lemfo LEM8 doesn't have any volume buttons....
The reason why I want to unlocker the bootloader is because I want to temporarily boot into TWRP recovery, why temporarily? Because I am not sure I succesfully ported the TWRP recovery for my watch and I don't want to brick the watch with flashing a faulty recovery.
I know the tool: flashtool which can also flash the recovery to the device ofcouse but I rather temporarily boot into the recovery instead of permanently flashing it with flashtool.
Steps I took:
HTML:
adb reboot bootloader
fastboot devices
0123456789ABCDEF fastboot
fastboot oem unlock
....
So my question for you guys is: does anyone know how to simulate a volume up key press so I can unlock the bootloader?
Any other suggestions on how to install the recovery are welcome aswell ofcourse!
Thanks in advance,
Kasper
kaspertje100 said:
Hi all,
I've ran into a problem while attempting to flash TWRP recovery to my Lemfo LEM8 watch. When I boot into the bootloader I found out that it is still locked so I tried unlocking the bootloader by executing the command: fastboot oem unlock. Now the problem is that in order to actually unlock the bootloader I have to press the vol up button which is a problem since the Lemfo LEM8 doesn't have any volume buttons....
The reason why I want to unlocker the bootloader is because I want to temporarily boot into TWRP recovery, why temporarily? Because I am not sure I succesfully ported the TWRP recovery for my watch and I don't want to brick the watch with flashing a faulty recovery.
I know the tool: flashtool which can also flash the recovery to the device ofcouse but I rather temporarily boot into the recovery instead of permanently flashing it with flashtool.
...
So my question for you guys is: does anyone know how to simulate a volume up key press so I can unlock the bootloader?
Any other suggestions on how to install the recovery are welcome aswell ofcourse!
Thanks in advance,
Kasper
Click to expand...
Click to collapse
You do not need to unlock the bootloader on a LEM8. It does not actually validate the contents of anything you flash into recovery at all. Use SP Tools (flashtool, as you mentioned) to flash recovery (and/or system and boot if you like). You will need a scatter file specifically for the LEM8, which is available around the 'net. If your custom TWRP does not work, just flash the original recovery back in. (Make sure you extract the original recovery first, also using flashtool, or pull it out of the most recent firmware image if you choose to download one.) As long as you use the right scatter file and only replace recovery, you will not brick the watch. You might get a boot loop, but that's easy to fix by simply reflashing the original recovery.
I am in the same position. I think I have both root and TWRP but cannot load them in to test.
From what I have found is that the command "fastboot oem unlock" is only used with older Android ROMs and you need to go into developer options and turn on OEM Unlock.
You then issue the command "fastboot flashing unlock" so that you can then flash the twrp recovery image by issuing the command "fastboot flash boot recovery.img" or whatever you named it.
The problem is that the command "fastboot flashing unlock" results in a warning message on the watch screen that requires you to tap an accept radio button or similar. Unfortunately this radio button is hidden behind the curved screen at the bottom and you cannot use the round to square screen found on the turn off screen to bring it into view..
Edit: On a closer look with a magnifying glass when I retried it asked to push the volume button up, but since there are no volume buttons on the device then ???????
If anyone has a solution, I would be grateful.
I used Magisk to patch the boot.img to give root and Team Hovatek's Mediatek Auto TWRP Recovery Porter to incorporate TWRP into the recovery.img.
I have tried the SP Flashtool in many configurations without success. The watch simply refuses to reboot and I have to use SP Flashtool to flash the stock ROM back on it to get it to work.
Any help would be appreciated.
I Can't find Scatter File for Lemfo LEM8
Brentworth said:
You do not need to unlock the bootloader on a LEM8. It does not actually validate the contents of anything you flash into recovery at all. Use SP Tools (flashtool, as you mentioned) to flash recovery (and/or system and boot if you like). You will need a scatter file specifically for the LEM8, which is available around the 'net. If your custom TWRP does not work, just flash the original recovery back in. (Make sure you extract the original recovery first, also using flashtool, or pull it out of the most recent firmware image if you choose to download one.) As long as you use the right scatter file and only replace recovery, you will not brick the watch. You might get a boot loop, but that's easy to fix by simply reflashing the original recovery.
Click to expand...
Click to collapse
Please could ou tell me where i can find the scatter file for Lemfo Lem8, I've tryed to search on the net for days, but I can't find it.
Markap76 said:
Please could ou tell me where i can find the scatter file for Lemfo Lem8, I've tryed to search on the net for days, but I can't find it.
Click to expand...
Click to collapse
http://roundandroidwatches.proboards.com/thread/2937/lemfo-lem8-z29-m6739-16gb
Register and download your firmware; the scatter will be in the extracted download.
Or create one using the likes of WwR_MTK
Also, for the volume up issue - have you tried connecting a USB keyboard to your watch using a USB to Micro USB adapter? Long shot but never know? I've connected a mouse before and it worked. However Android had already booted and loaded the GUI so not sure about the lower boot level drivers etc