Database Develop

[Q] HTC one bricked? stuck on HTC logo

Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.

limache said:
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
Click to expand...
Click to collapse
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)

Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium

Quis89 said:
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.

Toxicoblivion said:
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Click to expand...
Click to collapse
It's thought this is a safety feature so that you can't accidentally long press power and restart in dark places like your pocket.

@rider5512 Sounds right to me. Thanks for clarifying.

Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?

limache said:
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
Click to expand...
Click to collapse
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.

crushalot said:
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
Click to expand...
Click to collapse
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?

limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
fastboot erase cache

limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.

crushalot said:
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
Click to expand...
Click to collapse
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".

limache said:
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
Click to expand...
Click to collapse
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?

crushalot said:
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
Click to expand...
Click to collapse
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.

I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium

hardstuffmuc said:
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.

limache said:
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
Click to expand...
Click to collapse
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.

limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
crushalot said:
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
Click to expand...
Click to collapse
Hmmm okay so the other poster's suggestion was to get an OTG cable (a micro usb to USB cable right?) and connect the USB with the ROM directly the phone. Do you think this would be a big difference or no? I just don't know if the issue is the internal storage itself or the mode of pushing the ROM.
Otherwise, I'm pretty much scratching my head and have no idea what else I could do =/.

Just for anyone else who's having issues, I've tried using TWRP's install function with the OTG cable but it still doesn't mount. Just letting people know.

if you are noob to recover your phone you can try some services like this
i revived my HTC one by them
http://goo.gl/1DMXlq

[STOCK][M][TMO] Guide H811 20i & 20o Bootloader Unlock + Root + TWRP

Note : This guide is for H-81120-I & H-81120-O the latest update any firmware version below it will cause hard-brick so be careful before attempting anything, i wont be held responsible.
As a user with less knowledge about Commands and all, i was searching for answers by reading threads here and there and found my answers though some time tricky and sometimes easy.
Also in reading those threads i found many fellow members stumble upon resulting Soft bricks and in some cases a Hard brick or can say making their beloved G4 a paper weight.
So i thought i must put some really easy steps in order to clearly guide people like me who are too noob to understand the sophisticated developers steps.
Another reason for this Thread is also i saw many people asking about how to etc after updating to 20-O update for our H811 MM.
Few things to Prepare before Start
1- Properly Install Drivers for your H811 Variant of G4, cant find them Install LG Bridge.
2- Read the Whole thread before starting anything.
3- Confirm that all requirements are full filled and your variant is capable of everything mention in the OP.
4- Enable Developer Option then inside it enable OEM unlock and Usb debugging.
5- Always use Command prompt as Administrator.
6- Make a folder name G4 and paste all the file required for the unlocking in it for easy access and remembrance.
7- For Safer side after unlocking the bootloader boot into TWRP from fast boot and do not install TWRP.
8- Flash your SuperSU after that boot into android and see if all works.
9- Again Via Fastboot boot into TWRP make a backup of everything working fine. Boot into android.
0- Again same Via Fastboot boot into TWRP and now install your TWRP image via TWRP install function. So if by any means this is the culprit you can still revive your phone via your backup.
Attachments to Download
1- Adb Package can be found Here.
2- Download the latest TWRP.img 3.0+ from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Since downloading is complete now simply unzip the adb folder (containing fastboot by default) and paste both the TWRP image file and SUPERSU zip inside it.
Now Hold Shift and Open Command prompt here.
1- Input command to see if your device is visible in ADB.
Code:
adb devices
if you see your device and the status is off line then there will be a prompt on your G4 screen waiting for approval, accept it and input same command now all will be fine.
2- Now input below commands one by one. ( All credits to Autoprime )
Code:
adb reboot bootloader ( This will reboot your device to Fastboot mode )
fastboot oem unlock ( This will wipe all your data )
fastboot getvar unlocked ( This will check your bootloader status: Should be successful )
fastboot boot twrp-3.0.2-0-h811.img ( Phone boots TWRP ) Please put the full file name with .img extension or it wont work.
3- Now the Phone should be in TWRP install SuperSU from there which you have already pasted inside your external SD card.
4- Reboot to system and see if SuperSU is installed. In some cases First flash of SuperSU does not work if your case is same the again boot to Fastboot and from there boot into recovery, since your bootloader is unlocked no need to repeat the unlock OEM command.
5- Now for safer side follow the steps 7, 9, 0 mention in Preparation heading above.
Hopefully all will be in your favor.
Useful Links if you still fail
Kdz 20-O after download must be unzipped
H81120o_00_0613.kdz
LGUP Software:
( All credits to MicroMod777 )
Disclaimer: Nothing in this thread is my work, if i have missed any credit please do let me know i will add. I know several guides are available for same purpose so if any body finds it offending any rights can ask the moderators to remove this thread. The purpose only is to guide simple people like me to save their devices from getting bricked.

As by reading the thread many people are falling for permanent TWRP installation as its mention in the OP anyways for people not getting permanent Recovery follow below:
Boot to TWRP from fastboot Bootloader
When recovery comes up click Install >>>> then in the right below corner you ll see a tab for IMAGE >>> press it browse the recovery IMG which you stored in your SD card >>> swipe to flash >>> From asking where to install >>> select recovery >>> DONE.

SignatureBoy said:
Attachments to Download
1- Adb Package can be found Here.
2- Download the from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Click to expand...
Click to collapse
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.

DrakenFX said:
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
the ADB package i uploaded contains the Fastboot inside it
The thread clearly states it for 20-O

SignatureBoy said:
the ADB package i uploaded contains the Fastboot inside it
Click to expand...
Click to collapse
ok i meant the TWRP file needs to be in the same folder where Fastboot file is

DrakenFX said:
ok i meant the TWRP file needs to be in the same folder where Fastboot file is
Click to expand...
Click to collapse
That is also mention if you read the first post,
Since downloading is complete now simply make a folder and put all files downloaded inside it unzip the adb folder and paste both the TWRP image file and SUPERSU zip inside it.
Click to expand...
Click to collapse

SignatureBoy said:
DrakenFX said:
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
The thread clearly states it for 20-O
Click to expand...
Click to collapse
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.

ApokrifX said:
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.
Click to expand...
Click to collapse
yes it is for 20-O only

SignatureBoy said:
yes it is for 20-O only
Click to expand...
Click to collapse
Thanks for clarification. I’d change 1st post a bit:
Few things to Prepare before Start
0. LG G4 with 20o (stock) firmware.

When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
DanGarion said:
When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
Click to expand...
Click to collapse
Nevermind, I forgot about OEM Unlock...

thanks for the write up

This is not specific to 20o. It's the same steps we've been using all along. Nothing new to see here.
Sent from my LG-H811 using XDA-Developers mobile app

problem with fastboot
Thanks you for helping:fingers-crossed:

problem with fastboot
Hi,
I am a newbie in xda. I am trying to root and install TWRP into my lg g4. I am using software version H81120o. I checked enable OEM unlock and USB debugging. I have downloaded lg driver though lg bridge and all the files from the post. However, I got two problem while installing the twrp-3.0.2-0-h811.img.
1st problem (stuck here and need to reboot also not showing h811 on "the list of devices attached" after typing command "adb reboot bootloader"):
C:\Windows\system32>adb devices
List of devices attached
LGH811xxxxxxxx device
C:\Windows\system32>adb reboot bootloader
C:\Windows\system32>fastboot oem unlock
...
FAILED (remote: Already unlocked)
finished. total time: 0.012s
C:\Windows\system32>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.004s
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
cannot load 'twrp-3.0.2-0-h811.img': No error
2. 2nd problem(stuck here and need to reboot):
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
< waiting for device >
I checked online this problem might do with driver not up to date. Under device manager, my lg g4 is recognized under android device with android bootloader interface.
What should I do now?
Thanks you for helping:fingers-crossed:

This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??

I did everything but can't seem to get TWRP installed

Thanks a lot for this write up. I have been trying for about 2 weeks to root my g4 and it worked finally, So many thanks to you

The Remedy said:
This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??
Click to expand...
Click to collapse
same problem here but I just now got it working...sort of . I still can not make anything come up except the factory data reset when I use the phone volume and power button.
I thought it might be just that I wasn't coordinated enough so I downloaded this small app to do a recovery reboot.
After I installed the app and used it, I got the little android guy with his chest opened with the red triangle. I took out my battery, put it back in and booted my phone with the power button.
I then connected my phone to computer via usb and went back into adb and opened TWRP and installed the twrp-3.0.2-0-h811.img again but this time I looked around a little more first, and noticed a setting to either install in boot or recovery partition. I selected recovery partition (neither were selected) and installed it. Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.

I had the same issue but when u get into twrp make sure the IMG is in your SD card and to permanently have twrp installed go to home and press install.. Choose from image and install hope this helps
Sent from my LGLS992 using Tapatalk

fuzzy_ said:
same problem here but I just now got it working...sort of ................
Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.
Click to expand...
Click to collapse
In regard to booting into TWRP recovery with just the power and vol buttons, I just read this on another thread:
It boots into what appears to look like a default LG G4 factory reset page. For me, i clicked reset, and then yes, and surprisingly it brought me to where i wanted to go. TWRP Recovery.
I tried this and it worked for me as well.
I had been there before and tried it and it did a factory reset after I had spent an hour or two tweaking my phone, I was not a happy person. This time I did feel almost positive I had TWRP installed correctly and did not have nearly as much time spent getting things set up like I want them on my phone...It was still scary pressing that reset button and yes button.
If you don't have TWRP (or maybe some other recovery) installed it will factory reset your phone. I just thought I would share this and what happened with me. Do it at your own risk.

Rooting Android 7.0 on Nexus 6

Hello,
Does any one know if the below link still applies to rooting all firmware versions (Android Version = 7.0, Build NBD92D) on the Nexus 6 (Project Fi)?
https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Thanks in advance!

gil_happy said:
Hello,
Does any one know if the below link still applies to rooting all firmware versions (Android Version = 7.0, Build NBD92D) on the Nexus 6 (Project Fi)?
https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Thanks in advance!
Click to expand...
Click to collapse
Flash Magisk. Install Magisk Manager. Done.
Optional: Install cool modules to modify your phone further.

I found out that this ( http://www.wugfresh.com/nrt/ ) was an easy and up to date way to get rooted... Read all the instructions and watch videos if you need to before doing anything
http://www.wugfresh.com/nrt/

_P__ said:
I found out that this ( http://www.wugfresh.com/nrt/ ) was an easy and up to date way to get rooted... Read all the instructions and watch videos if you need to before doing anything
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Personally I prefer not to rely on toolkits. It's better to do things yourself so you can troubleshoot and fix if anything goes wrong.

snowrelyt said:
Flash Magisk. Install Magisk Manager. Done.
Optional: Install cool modules to modify your phone further.
Click to expand...
Click to collapse
I am in the process of trying the Magisk route and I'm having difficulty understanding the flash process. I have downloaded the Magisk-v11.1 zip to my Windows desktop and then copied it into the /Download directory on my Nexus 6. After googling a few things, I'm confused about how to flash / install on my Nexus 6. Some articles come up indicating I need to install TWRP Recovery, but I'm confused even more if I need to install this? Then I read another article (which I can't find now) about powering device down, then holding Vol Up, Vol Down, and PWR buttons to power phone back on and put in Recovery Mode (I think), and navigate and install the ZIP file. If this is the correct method, I didn't see an option to install from file or install from zip file.

gil_happy said:
I am in the process of trying the Magisk route and I'm having difficulty understanding the flash process. I have downloaded the Magisk-v11.1 zip to my Windows desktop and then copied it into the /Download directory on my Nexus 6. After googling a few things, I'm confused about how to flash / install on my Nexus 6. Some articles come up indicating I need to install TWRP Recovery, but I'm confused even more if I need to install this? Then I read another article (which I can't find now) about powering device down, then holding Vol Up, Vol Down, and PWR buttons to power phone back on and put in Recovery Mode (I think), and navigate and install the ZIP file. If this is the correct method, I didn't see an option to install from file or install from zip file.
Click to expand...
Click to collapse
Hey... You may flash TWRP recovery from bootloader using fastboot command. You can't root using stock recovery...
Download the latest TWRP from here and save it on your computer, preferably in the same folder you have ADB/fastboot:
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img
Just remove all security first before proceeding with the next steps (lockscreen scheme, password, pin. You can reenable them afterward. Just to avoid issues with twrp).
Your bootloader must be unlocked, otherwise unlock it first (you can find infos regarding bootloader unlock method in the general section of the Nexus 6 forum). Once/if the bootloader is unlocked, power down your device. Just press volume down and power button for a few seconds until you see a green Android laying down with it's belly opened...
Use fastboot to install TWRP using this command:
fastboot flash recovery twrp-3.1.0-0-shamu.img (the file you saved earlier on your computer).
Once it's finished, use the volume rocker and select "recovery mode" and press power button. It will reboot to TWRP.
Allow TWRP to make system modifications. Then tap install and go to the folder you saved the magical zip and install it.
Reboot and install magical manager as @snowrelyt said and you'll be ok.
Every info's you need can be found on the forum. If you're unsure, just ask again...
Good luck...

5.1 said:
Hey... You may flash TWRP recovery from bootloader using fastboot command. You can't root using stock recovery...
Download the latest TWRP from here and save it on your computer, preferably in the same folder you have ADB/fastboot:
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img
Just remove all security first before proceeding with the next steps (lockscreen scheme, password, pin. You can reenable them afterward. Just to avoid issues with twrp).
Your bootloader must be unlocked, otherwise unlock it first (you can find infos regarding bootloader unlock method in the general section of the Nexus 6 forum). Once/if the bootloader is unlocked, power down your device. Just press volume down and power button for a few seconds until you see a green Android laying down with it's belly opened...
Use fastboot to install TWRP using this command:
fastboot flash recovery twrp-3.1.0-0-shamu.img (the file you saved earlier on your computer).
Once it's finished, use the volume rocker and select "recovery mode" and press power button. It will reboot to TWRP.
Allow TWRP to make system modifications. Then tap install and go to the folder you saved the magical zip and install it.
Reboot and install magical manager as @snowrelyt said and you'll be ok.
Every info's you need can be found on the forum. If you're unsure, just ask again...
Good luck...
Click to expand...
Click to collapse
Thank you for this info... now I've gone down another rabbit hole after reading on different web sites
You say the bootloader must be unlocked - again after reading on different sites, there are 2 methods to determine if the bootloader is unlocked:
a) dial *#*#7378423#*#* (this did not work which upon reading said this method might now work)
b) C:\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
So 2 things; I read that if the bootloader is not unlocked and you need to unlock it, it will wipe your phone (obviously I can't have that) and secondly, the command to determine if the bootloader is unlocked did not seem to work for some reason on my PC (the 'fastboot devices' detected my phone when I ran it).

gil_happy said:
Thank you for this info... now I've gone down another rabbit hole after reading on different web sites
You say the bootloader must be unlocked - again after reading on different sites, there are 2 methods to determine if the bootloader is unlocked:
a) dial *#*#7378423#*#* (this did not work which upon reading said this method might now work)
b) C:\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
So 2 things; I read that if the bootloader is not unlocked and you need to unlock it, it will wipe your phone (obviously I can't have that) and secondly, the command to determine if the bootloader is unlocked did not seem to work for some reason on my PC (the 'fastboot devices' detected my phone when I ran it).
Click to expand...
Click to collapse
Well search how to boot into bootloader...
In bootloader you'll see this result:
Device is unlocked status code 3
If it says device locked... Well... You know what to do if you wish root...
Good luck...

5.1 said:
Hey... You may flash TWRP recovery from bootloader using fastboot command. You can't root using stock recovery...
Download the latest TWRP from here and save it on your computer, preferably in the same folder you have ADB/fastboot:
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img
Just remove all security first before proceeding with the next steps (lockscreen scheme, password, pin. You can reenable them afterward. Just to avoid issues with twrp).
Your bootloader must be unlocked, otherwise unlock it first (you can find infos regarding bootloader unlock method in the general section of the Nexus 6 forum). Once/if the bootloader is unlocked, power down your device. Just press volume down and power button for a few seconds until you see a green Android laying down with it's belly opened...
Use fastboot to install TWRP using this command:
fastboot flash recovery twrp-3.1.0-0-shamu.img (the file you saved earlier on your computer).
Once it's finished, use the volume rocker and select "recovery mode" and press power button. It will reboot to TWRP.
Allow TWRP to make system modifications. Then tap install and go to the folder you saved the magical zip and install it.
Reboot and install magical manager as @snowrelyt said and you'll be ok.
Every info's you need can be found on the forum. If you're unsure, just ask again...
Good luck...
Click to expand...
Click to collapse
5.1 said:
Well search how to boot into bootloader...
In bootloader you'll see this result:
Device is unlocked status code 3
If it says device locked... Well... You know what to do if you wish root...
Good luck...
Click to expand...
Click to collapse
Thanks so much! The bootloader was unlocked (I guess from an earlier root I performed using a Toolkit), and now I am rooted using Magisk.

gil_happy said:
Thanks so much! The bootloader was unlocked (I guess from an earlier root I performed using a Toolkit), and now I am rooted using Magisk.
Click to expand...
Click to collapse
Nice. Be careful what you do with your phone though. Since you seem to lack a bit of knowledge (no offence here). Read well before flashing anything... Avoid as much as possible the use of toolkits. I say this, since there are a lot of people bricking their device, unsure about what they did...
Cheers...

5.1 said:
Nice. Be careful what you do with your phone though. Since you seem to lack a bit of knowledge (no offence here). Read well before flashing anything... Avoid as much as possible the use of toolkits. I say this, since there are a lot of people bricking their and unsure about what they did...
Cheers...
Click to expand...
Click to collapse
No problem at all... thanks for the tips and advice

When i downloaded the RootNexus6MacToolkit, i unzipped the file and got this......RootNexus6MacToolkitzip.cpgz 411 bytes. What does that mean?

grunt0300 said:
When i downloaded the RootNexus6MacToolkit, i unzipped the file and got this......RootNexus6MacToolkitzip.cpgz 411 bytes. What does that mean?
Click to expand...
Click to collapse
It's the universe telling you to stop using toolkits...
Seriously though, further up this thread there are quite good instructions on how to root without toolkits.

Didgeridoohan said:
It's the universe telling you to stop using toolkits...
Seriously though, further up this thread there are quite good instructions on how to root without toolkits.
Click to expand...
Click to collapse
My problem has always been the command line. I've been reading up on terminal commands, and i might give it another try. A number of years ago, i bricked a Samsung Galaxy 3, and i've been gun shy ever since. I split my hard drive a while back, and if i can't figure out these commands, i'll go to the Windows 10 side and use Wug's toolkit.

grunt0300 said:
My problem has always been the command line. I've been reading up on terminal commands, and i might give it another try. A number of years ago, i bricked a Samsung Galaxy 3, and i've been gun shy ever since. I split my hard drive a while back, and if i can't figure out these commands, i'll go to the Windows 10 side and use Wug's toolkit.
Click to expand...
Click to collapse
As long as you keep your bootloader unlocked it's pretty difficult to brick a Nexus...
And to root your device you only really need to use two terminal commands. While in the bootloader (press and hold power + volume down to get there) run these commands from your computer (you can get adb and fastboot from here):
Code:
fastboot oem unlock
fastboot flash recovery <[I]insert_path_and_name_of_recovery_image_file_here[/I]>
The first one unlocks your bootloader. That will wipe your device though, so make sure to have a backup. If it's already unlocked, disregard....
The second one installs a custom recovery. Get the latest TWRP from here: https://twrp.me/motorola/motorolanexus6.html
After that you can boot to TWRP (from the bootloader), and flash the root zip of your choice.
Those are the basics. You've got lots more info in the stickies in the forum.

Didgeridoohan said:
As long as you keep your bootloader unlocked it's pretty difficult to brick a Nexus...
And to root your device you only really need to use two terminal commands. While in the bootloader (press and hold power + volume down to get there) run these commands from your computer (you can get adb and fastboot from here):
Code:
fastboot oem unlock
fastboot flash recovery <[I]insert_path_and_name_of_recovery_image_file_here[/I]>
The first one unlocks your bootloader. That will wipe your device though, so make sure to have a backup. If it's already unlocked, disregard....
The second one installs a custom recovery. Get the latest TWRP from here: https://twrp.me/motorola/motorolanexus6.html
After that you can boot to TWRP (from the bootloader), and flash the root zip of your choice.
Those are the basics. You've got lots more info in the stickies in the forum.
Click to expand...
Click to collapse
Getting my Nexus 6 next week. I'll let you know how it turned out. Thanks.

Can somebody please point me in the right direction? (I've searched)

I need to root my G4 on TMO. It's on 6.0 and all I have done is enabled dev options - usb debugging- enable OEM in the menu. I've rooted devices before but it's been awhile. I obviously need to start from the beginning here, I assume by unlocking bootloader. I can't find any thread to start with as they are either outdated or for a different version of Android, or I just couldn't find one. I would really appreciate it if somebody could just link me to the thread/guide I need to be in! Thank you so much if you can!

MTN927 said:
I need to root my G4 on TMO. It's on 6.0 and all I have done is enabled dev options - usb debugging- enable OEM in the menu. I've rooted devices before but it's been awhile. I obviously need to start from the beginning here, I assume by unlocking bootloader. I can't find any thread to start with as they are either outdated or for a different version of Android, or I just couldn't find one. I would really appreciate it if somebody could just link me to the thread/guide I need to be in! Thank you so much if you can!
Click to expand...
Click to collapse
note it can only be unlock in this versions.. ill place them from oldest to newest 20i-(20p-20q-20r-20v) if you in any of the versions in parenthesis doent downgrade tp 20i... 20i is antirollback V2 all other in parenthsis is V3 you can switch bak and forth from 20p-to 20v.
well you have developers option enabled and OEM unlock
minimal adb. fastboot install it follow instructions. https://forum.xda-developers.com/showthread.php?t=2317790
download TWRP from here h811 and h815 same app for both. https://twrp.me/devices/lgg4.html
have 2 copies on in SD card other in minmal adb fastboot folder.
Bootloader OEM Unlock + Root:
Starting with the Android 6.0 20x bootloader it has to be unlocked, sorta like a Nexus, with fastboot. Previously only 'OEM Unlock' had to be toggled in Android Developer settings for TWRP or custom boot images to work.
download superSU
connect usb cable to phone.. then go to location folder of minimal adb.. ezample Crogramfiles/minimal.
then in the folder in a empty space press shift key.. and right click on mouse button . you should see open command prompt from here.. select it.
a new window should appear. enter this command
adb reboot bootloader and see screen for confirmation to acsess phone select yes.
if it doesnt boot into bootloader try command again
once booted youll see small letter on phone screen then enter command
fastboot oem unlock (this wipes ALL data!!)
it should restart phone. and optimize all apps...and bootloader should unlock
do same for twrp.... make sure command name of twrp is the same in the file example command is like this..
fastboot boot twrp-2.8.7.1-h811.img and file TWRP is say.. twrp.30.00 it wont work rename either command or files or both and name it twrp.img same in command. once it boot into twrp .. go to install then press button that says image. so the twrp.img you have in sd card appears/ select it then on next window tick recovery. swipe left to install permanently and you are done. flash new rom or superSU.
hope i make sense good luck

raptorddd said:
note it can only be unlock in this versions.. ill place them from oldest to newest 20i-(20p-20q-20r-20v) if you in any of the versions in parenthesis doent downgrade tp 20i... 20i is antirollback V2 all other in parenthsis is V3 you can switch bak and forth from 20p-to 20v.
well you have developers option enabled and OEM unlock
minimal adb. fastboot install it follow instructions. https://forum.xda-developers.com/showthread.php?t=2317790
download TWRP from here h811 and h815 same app for both. https://twrp.me/devices/lgg4.html
have 2 copies on in SD card other in minmal adb fastboot folder.
Bootloader OEM Unlock + Root:
Starting with the Android 6.0 20x bootloader it has to be unlocked, sorta like a Nexus, with fastboot. Previously only 'OEM Unlock' had to be toggled in Android Developer settings for TWRP or custom boot images to work.
download superSU
connect usb cable to phone.. then go to location folder of minimal adb.. ezample Crogramfiles/minimal.
then in the folder in a empty space press shift key.. and right click on mouse button . you should see open command prompt from here.. select it.
a new window should appear. enter this command
adb reboot bootloader and see screen for confirmation to acsess phone select yes.
if it doesnt boot into bootloader try command again
once booted youll see small letter on phone screen then enter command
fastboot oem unlock (this wipes ALL data!!)
it should restart phone. and optimize all apps...and bootloader should unlock
do same for twrp.... make sure command name of twrp is the same in the file example command is like this..
fastboot boot twrp-2.8.7.1-h811.img and file TWRP is say.. twrp.30.00 it wont work rename either command or files or both and name it twrp.img same in command. once it boot into twrp .. go to install then press button that says image. so the twrp.img you have in sd card appears/ select it then on next window tick recovery. swipe left to install permanently and you are done. flash new rom or superSU.
hope i make sense good luck
Click to expand...
Click to collapse
I'm on 20v, so I should be good.

MTN927 said:
I'm on 20v, so I should be good.
Click to expand...
Click to collapse
yes . thats latest version.. thats good.

OK, I got twrp installed but the two SU's I've flashed don't work. I have SU installed, it needs to update binaires, I try that but it fails every time. Root checkers say I'm not rooted. I think I'm using the wrong SU zip. Any help? Your guide was great btw.
EDIT: OK, now it says i am rooted but I can't get the SU binary to update. It fails every time and then asks me to reboot and try again. Any ideas?
UPDATE: Ok, the SU binary finally updated successfully! I think I'm all good! Gonna check out some custom ROMS later. Any recommendations?

Lineage
https://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-lg-g4-t3477475

Unlocking / Rooting Nokia 1 stock rom guide

Step 1 (Unlocking bootloader) :
Make sure you have adb and fastboot .
get your serial number.
Code:
adb shell getprop ro.serialno
calculate md5 of the serial number of device ( i used this https://passwordsgenerator.net/md5-hash-generator/).
Reboot bootloader.
Code:
adb reboot bootloader
Unlock using key (md5code=md5 of your serial number).
Code:
fastboot oem key md5code
Code:
fastboot oem unlock
Step 2 (flashing twrp fixing encryption problem):
Download twrp :=https://www.androidfilehost.com/?fid=1322778262903986803
Reboot bootloader by connecting power button + usb cable + volume down and type
Code:
fastboot flash recovery TWRP-3.2.3-TwrpBuilder-2018-08-21_14.img
.
Reboot recovery by using power button + usb connected + volume up at same time .
Download fstab:=> https://gist.githubusercontent.com/androidlover5842/e5fccc739251bb75ad7cf1d8ddc36e0d/raw/a4646983b481c02462cd0cfbf8decb9edf4f2ac9/fstab.mt6735 and go to mount menu in twrp => mount vendor and update fstab using this commnd .
Code:
adb push fstab.mt6735 /vendor/etc/fstab.mt6735
make backup of boot using backup option and flash stock recovery as boot (you can get stock recovery from here )
reboot system and it should reboot into stock recovery
wipe data using stock recovery
reboot back to twrp by pressing power + usb + volume button.
restore boot and flash magisk.
XDA:DevDB Information
Unlocking / Rooting Nokia 1 stock rom, Tool/Utility for the Nokia 1
Contributors
androidlover5842
Version Information
Status: Stable
Created 2018-08-21
Last Updated 2018-08-21

unlock failed
it seems the key did not work. Maybe imei is involved in generating key? (my Nokia 1 is dual sim)
---------- Post added at 11:44 PM ---------- Previous post was at 11:26 PM ----------
slim404 said:
it seems the key did not work. Maybe imei is involved in generating key? (my Nokia 1 is dual sim)
Click to expand...
Click to collapse
SOLVED.
I had to allow OEM unlocking in Developer Settings

androidlover5842 said:
Step 2 (flashing twrp fixing encryption problem):
reboot system and it should reboot into stock recovery
Click to expand...
Click to collapse
Hmm all good till this step, but the device stuck doesn't reboot into stock recovery but bootloop TWRP
Obviously i messed up something and i wonder what it is

ObviousSimple said:
Hmm all good till this step, but the device stuck doesn't reboot into stock recovery but bootloop TWRP
Obviously i messed up something and i wonder what it is
Click to expand...
Click to collapse
I got the same problem. I found out the recovery file he linked to was that of a single SIM Nokia 1 (TA-1060) mine is a Dual Sim Nokia 1 (TA-1047)
I downloaded the TA-1047 original firmware (I googled it)
I used it to reflash boot and recovery. Then redid everything using this time the right original recovery.bin from the TA-1047 firmware and it worked

Android Downgrade
I'm planning to buy this phone but I don't like the software. Can I install Android Kit Kat on it?

Hi! I have soft-bricked Nokia 1 ta-1047(recovery bootloop). How can i unlock bootloader without checkin OEM unlock in dev settings? Thks!

Hi! I had some trouble understanding the instructions. Step 1 worked without a hitch but I ran into some problems in step 2. I'd be really grateful for some help.
Do I copy the text in the link, paste it into a .txt file and then save it to "ftsab.mt6735" in the Minimal And Adb Fastboot folder on my pc?
Do I press cancel when twrp asks me for a password? Or do I need a password? I pressed cancel.
When I go into "mount" in twrp and click on "vendor" do I then go the command window on my pc (from the adb fastboot folder) and type "adb push fstab.mt6735 /vendor/etc/fstab.mt6735"? This is what I did and it might have come with an error I'm not sure.
What is the backup of boot for? I guess it's just a safety measure. For some reason I couldn't do that because it said something about encyption (I think, unless I'm getting mixed up with before) so I had to skip that step and go onto flashing the recovery. The instructions now say "flash stock recovery as boot (you can get stock recovery from here)". Is the stock recovery the "recovery.bin" file and do I put that in the adb and fastboot folder? I did that and typed "fastboot flash recovery recovery.bin" in the command window. Was that right or not?
The instuctions say "restart the system" Is that from the twrp menu? I restarted the phone via twrp but it didn't restart into stock recovery it restarted into the normal operating system. I knew then that I'd done something wrong. I then turned off the phone and tried accessing the stock recovery by pressing the volume up and power on and it started in twrp! Am I getting confused? Please can someone help me! Thank you!

anhadsingha said:
I'm planning to buy this phone but I don't like the software. Can I install Android Kit Kat on it?
Click to expand...
Click to collapse
No you can't and why would you want KitKat. Kitkat was good 5 versions ago
---------- Post added at 03:20 PM ---------- Previous post was at 03:17 PM ----------
mountainair said:
Hi! I had some trouble understanding the instructions. Step 1 worked without a hitch but I ran into some problems in step 2. I'd be really grateful for some help.
Do I copy the text in the link, paste it into a .txt file and then save it to "ftsab.mt6735" in the Minimal And Adb Fastboot folder on my pc?
Do I press cancel when twrp asks me for a password? Or do I need a password? I pressed cancel.
When I go into "mount" in twrp and click on "vendor" do I then go the command window on my pc (from the adb fastboot folder) and type "adb push fstab.mt6735 /vendor/etc/fstab.mt6735"? This is what I did and it might have come with an error I'm not sure.
What is the backup of boot for? I guess it's just a safety measure. For some reason I couldn't do that because it said something about encyption (I think, unless I'm getting mixed up with before) so I had to skip that step and go onto flashing the recovery. The instructions now say "flash stock recovery as boot (you can get stock recovery from here)". Is the stock recovery the "recovery.bin" file and do I put that in the adb and fastboot folder? I did that and typed "fastboot flash recovery recovery.bin" in the command window. Was that right or not?
The instuctions say "restart the system" Is that from the twrp menu? I restarted the phone via twrp but it didn't restart into stock recovery it restarted into the normal operating system. I knew then that I'd done something wrong. I then turned off the phone and tried accessing the stock recovery by pressing the volume up and power on and it started in twrp! Am I getting confused? Please can someone help me! Thank you!
Click to expand...
Click to collapse
If you're phone booted fine into system and you can access twrp then just flash magisk as you've done ok and the phone and twrp are working

How to "flash stock recovery as boot" ?
How to "flash stock recovery as boot" ? I went to fastboot mode and flashed recovery.bin then rebooted to recovery and it showed "no commands". No options were there.

ttocs99 said:
If you're phone booted fine into system and you can access twrp then just flash magisk as you've done ok and the phone and twrp are working
Click to expand...
Click to collapse
Thanks. But I'm still not sure. I confess I'm a novice. I actually ended up bricking my phone because I went on to do something wrong. I'll get another phone this week to try and root again, hopefully successfully this time. Isn't the step to make a backup of the boot really important because we have to flash that boot near the end? I thought it was necessary. I also wonder whether I should have typed "fastboot boot recovery.img" instead of "fastboot flash recovery recovery.img" because the instructions say "flash stock recovery as boot"? Edit: Perhaps I'm wrong again
madmax786 said:
How to "flash stock recovery as boot" ? I went to fastboot mode and flashed recovery.bin then rebooted to recovery and it showed "no commands". No options were there.
Click to expand...
Click to collapse
Did you manage to get a backup of the boot?

I can have no access in the udev/ etc.... Can you please explain the following steps how to do it? is it a linux command that needs to be done on a linux running computer or does it works on Windows too?
i was indeed happy that it completed the backup to my external SD Card made with Magisk a patched boot image, but doesn't seem to be rooted after all, what next? it says every time Magisk is not installed do i have to flash it in minimal ADB
Sincerely

Des.Coene said:
I can have no access in the udev/ etc.... Can you please explain the following steps how to do it? is it a linux command that needs to be done on a linux running computer or does it works on Windows too?
i was indeed happy that it completed the backup to my external SD Card made with Magisk a patched boot image, but doesn't seem to be rooted after all, what next? it says every time Magisk is not installed do i have to flash it in minimal ADB
Sincerely
Click to expand...
Click to collapse
Rooting this for now is a gamble there is only 1 stock ROM to flash and it's for the UK single SIM varient of the Nokia 1 only thing you can have is root and twrp and maybe flash a gsi but most of them are still buggy if you can flash stock and stay that way untill further development.

ttocs99 said:
Rooting this for now is a gamble there is only 1 stock ROM to flash and it's for the UK single SIM varient of the Nokia 1 only thing you can have is root and twrp and maybe flash a gsi but most of them are still buggy if you can flash stock and stay that way untill further development.
Click to expand...
Click to collapse
There seem to be buggy , certainly when 2 different chip sets are used in several Nokia 1 series
the mt6737 as i have & the mt6735 there's what i've been struggling with.
Thanks anyways for the advice
Sincerely

Des.Coene said:
There seem to be buggy , certainly when 2 different chip sets are used in several Nokia 1 series
the mt6737 as i have & the mt6735 there's what i've been struggling with.
Thanks anyways for the advice
Sincerely
Click to expand...
Click to collapse
I have the mt6735 but shouldn't be long for a custom ROM as root and twrp have been achieved.

madmax786 said:
How to "flash stock recovery as boot" ? I went to fastboot mode and flashed recovery.bin then rebooted to recovery and it showed "no commands". No options were there.
Click to expand...
Click to collapse
Hi,i got the exact same problem

ramnus said:
Hi,i got the exact same problem
Click to expand...
Click to collapse
Hi, try holding the power button for a few seconds and then releasing it and pressing volume up.
For the record, I managed to root my ta 1060 phone. Thanks everyone. I think I had a problem initially because twrp asked for a password due to phone encryption and I ignored it. I managed to bypass that password screen by not rebooting after flashing twrp, instead going straight into twrp and following the instructions.
I've now got a problem getting usb otg to work. I've added the files android.hardware.usb.host.xml, handheld_core_hardware.xml and tablet_core_hardware.xmls. It's showing as enabled in all the app checkers but Usb Otg Helper says E: Mount directory could not be created, E: This app will not work, OTG mass storage not supported?, NTFS write support failed(no fuse). That's not a topic for here though. If anyone can help, can they pm me please

Nokia 1 root
mountainair said:
Hi! I had some trouble understanding the instructions. Step 1 worked without a hitch but I ran into some problems in step 2. I'd be really grateful for some help.
Do I copy the text in the link, paste it into a .txt file and then save it to "ftsab.mt6735" in the Minimal And Adb Fastboot folder on my pc?
Do I press cancel when twrp asks me for a password? Or do I need a password? I pressed cancel.
When I go into "mount" in twrp and click on "vendor" do I then go the command window on my pc (from the adb fastboot folder) and type "adb push fstab.mt6735 /vendor/etc/fstab.mt6735"? This is what I did and it might have come with an error I'm not sure.
What is the backup of boot for? I guess it's just a safety measure. For some reason I couldn't do that because it said something about encyption (I think, unless I'm getting mixed up with before) so I had to skip that step and go onto flashing the recovery. The instructions now say "flash stock recovery as boot (you can get stock recovery from here)". Is the stock recovery the "recovery.bin" file and do I put that in the adb and fastboot folder? I did that and typed "fastboot flash recovery recovery.bin" in the command window. Was that right or not?
The instuctions say "restart the system" Is that from the twrp menu? I restarted the phone via twrp but it didn't restart into stock recovery it restarted into the normal operating system. I knew then that I'd done something wrong. I then turned off the phone and tried accessing the stock recovery by pressing the volume up and power on and it started in twrp! Am I getting confused? Please can someone help me! Thank you!
Click to expand...
Click to collapse
Have you found password ?

Help please
Des.Coene said:
There seem to be buggy , certainly when 2 different chip sets are used in several Nokia 1 series
the mt6737 as i have & the mt6735 there's what i've been struggling with.
Thanks anyways for the advice
Sincerely
Click to expand...
Click to collapse
Buddy is there anyway I could get stock or custom rom to bootup my bricked MT6737 TA1056 ??
I’m stuck in a blank screen and vibration

xdakanwal said:
Have you found password ?
Click to expand...
Click to collapse
No, when I found it asked for a password I realised I shouldn't have rebooted the system and so I wiped the data and flashed twrp again and no more password.

My TA-1066 is basically dead. Unlocked, doesn't boot into recovery, flashing the ROM fixed it last time this happened. Now it doesnt. In a bootloop with the NOKIA logo.
Help would be really appreciated.
---------- Post added at 07:23 AM ---------- Previous post was at 07:23 AM ----------
My TA-1066 is basically dead. Unlocked, doesn't boot into recovery, flashing the ROM fixed it last time this happened. Now it doesnt. In a bootloop with the NOKIA logo.
Help would be really appreciated.