Related
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?
INSTALL TWRP:
1- Make sure you have an unlocked bootloader. Get your specific unlock code for your Huawei P8 from this page: https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail make sure to register using facebook method that way you will get the code directly. Make sure to stop adblock extension in your browser from blocking the facebook link.
- After getting your unlock code follow the last part of the tutorial http://www.teamandroid.com/2015/06/07/unlock-bootloader-huawei-p8/ starting from step 3.. By the way in the link step 6 is wrong, to enter fastboot mode simply turn off the device and remove any connections from the pc then hold volume down and connect back the usb connection to pc at the same time; it should power the device in fastboot mode.
2. Download the latest TWRP from here: https://dl.twrp.me/p8/, If there is no new update after version 2.8.7.1 then flash this version: http://forum.xda-developers.com/showpost.php?p=65499548&postcount=564. The official TWRP version 2.8.7.1 doesn't work on Marshmallow it will cause an endless bootloop.
- Ty to @rodlane for providing the Twrp. It's working fine.
3. Put TWRP image file in the ADB and Fastboot folder. Then from ADB and Fastboot Folder hold shift and right click to open CMD(command prompt) from there. Once CMD is open run the following code:
adb devices (This will show if your device is connected)
adb reboot bootloader (will reboot the device in bootloader mode)
fastboot devices
fastboot flash recovery "name of the twrp file downloaded .img" ( ex: fastboot flash recovery twrp-2.8.7.1-p8.img )
4. Manually restart the device, by holding power until it restarts.
* A more detailed tutorial for downloading drivers and prerequisites needed which i didn't cover. Ty Sarang. http://www.androidsage.com/2016/01/29/how-to-install-twrp-recovery-on-your-android-device/.
In step 4 in the link to go to bootloader mode for our device turn off the device. Then hold volume down and connect the usb to pc or laptop this will boot the device in bootloader mode. Or you can use the CMD command as suggested earlier.
ROOT P8
1. Download the latest SU.zip from here. http://forum.xda-developers.com/showpost.php?p=64161125.
2. Put the Su zip in SD card or internal memory.
3. When phone is OFF hold (volume up + power key) together until you see Huawei startup logo then release. After you boot into Twrp make sure to select read only mode when the Twrp starts.
Note: If you can't boot into twrp although you flashed it correctly, do this:
*After flashing twrp. restart the device manually by holding power until it restarts.
*From ADB and Fastboot Folder hold shift and right click to open CMD(command prompt) from there. Once CMD is open run the following code:
-adb devices
-adb reboot recovery
4. Inside Twrp go to advance-> Terminal. Click select and type the following code without the quotation "echo SYSTEMLESS=true>>/data/.supersu". Already explained why in Chainfire page. <-----VERY IMPORTANT STEP TO DO OR SU WILL NOT BE INSTALLED AND YOU WILL BE STUCK IN A BOOTLOOP
5. Go back to install menu, and flash the SU zip. After that restart the the device it should restart without a bootloop.
Thanks to @Chainfire for SU and help, and @ralfbergs for pointing out the need to use the command line http://forum.xda-developers.com/showpost.php?p=65458498&postcount=302.
P.S: (12-07-16) I have sold my P8, so I can no longer help with any new updates to the device i am really sorry. I wish everyone the best of luck. Take care
Hi!
Thanks, but not working for me.
I flashed the twrp with success, but my
phone has the stock recovery not the twrp.
I cant understand why.
Any idea?
Ok, I got it. The nu twrp is the solution.
http://forum.xda-developers.com/showpost.php?p=65499548&postcount=564
voison said:
Hi!
Thanks, but not working for me.
I flashed the twrp with success, but my
phone has the stock recovery not the twrp.
I cant understand why.
Any idea?
Click to expand...
Click to collapse
I think I've seen somewhere, NOT to reboot the phone with fastboot command after flashing recovery, use buttons instead and hold Volume Up while booting, otherwise custom recovery will bee overwritten by stock again.
tomtro74 said:
I think I've seen somewhere, NOT to reboot the phone with fastboot command after flashing recovery, use buttons instead and hold Volume Up while booting, otherwise custom recovery will bee overwritten by stock again.
Click to expand...
Click to collapse
I agree with you, I put it there incase someone needed the code. But before when rooting by flashing a .bat file inside the file the code used had the command line without losing the recovery that's why I also put it there. But it's not a must use anyway. Thanks.
I want to ask: my P8 has root, and successfully installed the xposed framework program, most framework programs can be normal use, however, is the most important Gravitybox program can not run, don't know what the reason, who knows what's the solution?
dosent work for me i have flashed the twrp recovery and i shut down the phone then vol+ with power i accessed the erecovery and the recovery request wifi to download files then failed ....
tt_man said:
dosent work for me i have flashed the twrp recovery and i shut down the phone then vol+ with power i accessed the erecovery and the recovery request wifi to download files then failed ....
Click to expand...
Click to collapse
Are you sure you flashed correctly?, if you are, try the twrp file suggested by Voison. Another reason could be the combo keys used to boot to twrp in lollipop its( volume up + power) but i can't confirm if it's the same for Marshmallow.
x_h168 said:
I want to ask: my P8 has root, and successfully installed the xposed framework program, most framework programs can be normal use, however, is the most important Gravitybox program can not run, don't know what the reason, who knows what's the solution?
Click to expand...
Click to collapse
How did you installed Xposed Framework?
Hi, sorry for the OT, but I cannot create a thread so I have to write here. I have a Huawei P8 and I would like to unlock the bootloader but every time I try to connect to the huawei site it always tell me that the server is busy, so I'm hopeless. Can someone help me and do it for me?
Information:
Product: HUAWEI GRA-L09
SN: S7M0216108011240
IMEI: 869370023363473
Product ID: 08552512
Rashad83 said:
4. Inside Twrp go to advance-> Terminal. Click select and type the following code without the quotation "echo FSTABSYSTEMRW=true>>/data/.supersu". Already explained why in Chainfire page.
Click to expand...
Click to collapse
THIS DOESN'T WORK AND WILL LEAD TO A BOOTLOOP!!!
The proper command to use in terminal is:
Code:
echo SYSTEMLESS=true>>/data/.supersu
@Rashad83 you should test and troubleshoot before writing a guide. Your signature says your P8 is still on Lollipop...
@all: I am gonna write a proper howto, not just a quick brainless cut & paste from here and there
Regards
AD2076 said:
THIS DOESN'T WORK AND WILL LEAD TO A BOOTLOOP!!!
The proper command to use in terminal is:
Code:
echo SYSTEMLESS=true>>/data/.supersu
@Rashad83 you should test and troubleshoot before writing a guide. Your signature says your P8 is still on Lollipop...
@all: I am gonna write a proper howto, not just a quick brainless cut & paste from here and there
Regards
Click to expand...
Click to collapse
I apologize from everyone for the mistyping that is in the command line, and for causing any bootloop.
@AD2076:
1. Since you are so perfect, and know how to read signatures you should know there is no beta rom for my model's region and i can't test the code, but never the less i have got feedback from others who have tested the command line and it works for them http://forum.xda-developers.com/showpost.php?p=65555974&postcount=26,http://forum.xda-developers.com/showpost.php?p=65568736&postcount=29 , and yeah i have pointed to the right command line back then. If you follow my thread towards the end you will notice i have linked a post to the right command line -> "and ralfbergs for pointing out the need to use the command line http://forum.xda-developers.com/show...&postcount=302".
2. Negativity never solves problems but the opposite it causes ill feelings, I am a human being and i make mistakes that's why the likes of you can post back and correct me, but there is a proper way of doing it without causing ill feelings and embarrassment to others, something like the inbox you could have messaged me to correct the command line without being insulting. I have nothing to gain from writing this thread except helping others in need.
3. You should never take my word or any other for that matter without double checking, that's why we have Google. And my only wrong doing in writing this thread is copying the wrong command line out of hurry which i have my self to blame but the likes of you makes it hard to do any good.
4. "I am gonna write a proper howto, not just a quick brainless cut & paste from here and there". Really..!, may i know what part is copy and pasts beside the command line?, By the way it's "How To" and not howto.......
1. Since you are so perfect, and know how to read signatures you should know there is no beta rom for my model's region and i can't test the code, but never the less i have got feedback from others who have tested the command line and it works for them http://forum.xda-developers.com/showpost.php?p=65555974&postcount=26,http://forum.xda-developers.com/showpost.php?p=65568736&postcount=29
Click to expand...
Click to collapse
Looks I am not so good at reading signatures... not as good as you in writing guides you can't try for sure.
others... they probably enabled system rw in twrp
and yeah i have pointed to the right command line back then. If you follow my thread towards the end you will notice i have linked a post to the right command line.
Click to expand...
Click to collapse
I did and found the proper command line, but in a "guide" I expect to find exact and doublechecked instructions
2. Negativity never solves problems but the opposite it causes ill feelings, I am a human being and i make mistakes that's why the likes of you can post back and correct me, but there is a correct way of doing it without causing ill feelings and embarrassment to others, something like the inbox you could have messaged me to correct the command line without being insulting. I have nothing to gain from writing this thread except helping others in need.
Click to expand...
Click to collapse
I tried to be positive pointing out the proper command line to save others from bootloop
I didn't mean to be insulting but I was angry after a lot of time spent for a typo
3. You should never take my word or any other for that matter without double checking, that's why we have Google. And my only wrong doing in writing this thread is copying the wrong command line out of hurry which i have my self to blame but the likes of you makes it hard to do any good.
Click to expand...
Click to collapse
No one should write a "guide" in a hurry and without doublechecking and testing it, imho
BTW @Rashad83 I am glad you edited the post, you saved some headaches to others and some time to me. Now your one is almost a proper guide and I can confirm it works. Just a few notes:
fastboot reboot is not necessary and can be problematic to start in recovery later
vol+ and power combo works in marshmallows too
to have the combo work please keep keys pressed until the huawei logo appears
twrp-2.8.7.1 doesn't work (I am on B317), new_twrp does
please reformat it better, it's ugly :angel:
Now, just to be positive, let me link this
guide
No need to downgrade to B170 or whatever... it works using B317 from huawei site.
Apologize for your ill feelings
AD2076 said:
Looks I am not so good at reading signatures... not as good as you in writing guides you can't try for sure.
others... they probably enabled system rw in twrp
Click to expand...
Click to collapse
Clearly you are "not as good as me" in writing proper english either.
"I expect to find exact and doublechecked" english when commenting. You are so perfect.
Please don't consider replying, i have had enough of your condescending remarks.
Hey there, I'm having issues getting into TWRP after flashing it. No matter what I do my phone will not boot into recovery at all, it just boot loops for a little bit before rebooting normally. If it does boot into recovery its the standard one, not TWRP. Any ideas?
Edit: My phone is the GRA-UL00 variant, running build C470B181. Stock EMUI 3.1 Lollipop.
PointyFinger said:
Hey there, I'm having issues getting into TWRP after flashing it. No matter what I do my phone will not boot into recovery at all, it just boot loops for a little bit before rebooting normally. If it does boot into recovery its the standard one, not TWRP. Any ideas?
Edit: My phone is the GRA-UL00 variant, running build C470B181. Stock EMUI 3.1 Lollipop.
Click to expand...
Click to collapse
This thread is for Marshmallow Twrp and root which is different from Lollipop especially the root method. For installing Twrp on Lollipop:
- Make sure you unlocked the bootloader.
- You have all the needed drivers installed in your pc. i have linked a very detailed guide for how to install Twrp and drivers needed please follow it, here is another one with root for our device http://www.droidviews.com/root-huawei-p8-and-install-twrp-recovery/.
*In step 5 in the link use twrp-2.8.7.1-p8.img instead of the old one,the command will be:
fastboot flash recovery twrp-2.8.7.1-p8.img.
*After that manually restart the device, by holding power until it restarts. Then When phone is OFF hold (volume up + power key) together until you see Huawei startup logo then release. You should be able to boot into twrp. To root continue with the link steps.
I already waited 14 days..and today i tried with facebook account for the unlock code....
"The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days"
I'm not able to flash anything on this phone...fastboot says it's unlocked but can't flash?
Verstuurd vanaf mijn HUAWEI GRA-L09 met Tapatalk
AeonSL said:
I already waited 14 days..and today i tried with facebook account for the unlock code....
"The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days"
I'm not able to flash anything on this phone...fastboot says it's unlocked but can't flash?
Verstuurd vanaf mijn HUAWEI GRA-L09 met Tapatalk
Click to expand...
Click to collapse
So did you manage to get the unlock code or not?, or is it telling you the huawei id is wrong, and your not able to get it.
No it is telling me that the the huawei id has not been used for 14 days...???
Verstuurd vanaf mijn HUAWEI GRA-L09 met Tapatalk
AeonSL said:
No it is telling me that the the huawei id has not been used for 14 days...???
Verstuurd vanaf mijn HUAWEI GRA-L09 met Tapatalk
Click to expand...
Click to collapse
Try another huawei id using the Huawei id generator method. For me when i tried to unlock the code it gave me a message "wrong id" so i used this method.
http://forum.xda-developers.com/p8l...otloader-root-p8-p8lite-t3164956#post62851688
Also i just saw this post he had issues with Huawei id too. http://forum.xda-developers.com/showpost.php?p=65673335&postcount=181
Not working...it gives me the same message that the id has not been used for 14 days..?
Verstuurd vanaf mijn HUAWEI GRA-L09 met Tapatalk
Now, I know this tutorial exists all over the place, like one-click and UnjustifiedDev tutorial but none seemed to work. I am sharing the steps and method I used IN-DEPTH command for command on how to unlock, flash, and root the LG G4 from Tmobile.
NOTE THIS WILL FACTORY RESET YOUR DEVICE SO BACKUP ALL YOUR DATA
1. Activate developer settings by entering the about section and tapping build number 7 times.
2. Enter your developer settings and MAKE sure you have 'Allow OEM unlock' and 'USB Debugging' enabled.
3. Download the latest SuperSU zip and move it onto your SD card.
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
5. Once the Command window is linked to the folder, connect your device via USB and allow the connection.
6. On the command window type 'adb reboot bootloader' and the device should reboot with the fastboot options on the upper left of the phone screen
7. Once again on the command window type 'fastboot oem unlock' and the command window should say OKAY and complete the action.
8. To Confirm that the device is unlocked type 'fastboot getvar unlock' and the window should respond with 'Unlock: YES'
9. Now download the latest available TWRP and drop it into the platform-tools folder where your ADB.exe is located.
10. On your Command Window type 'fastboot flash recovery "NAME OF TWRP FILE" if you get the error ' cannot load 'twrp-X.X.X.X-h811' you need to add .img to the end of the filename
11. Once the process completes you will see 'target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 1.088s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time:'
THE FAILED UNKNOWN COMMAND NOTICE CAN BE IGNORED
12. Once the process completes the device may not let you enter recovery from the traditional method using the buttons on the back of the phone so the easiest method is to, on your command window, type
'fastboot boot twrp-2.8.7.0-h811.img' and the device should respond within just a few seconds and reboot into TWRP.
13. Once the device reboots, enter twrp and tap on install and locate the SuperSU.zip and allow it to install.
14. Once the process completes successfully, wipe cache to be safe and reboot your device.
15. Resetup your device and restore your data if necessary and install a root checker from Google Play to confirm root!
THATS IT GUYS! This took me a long time to figure this out and it's a combination of different methods to get it to work!
All credit goes to the Devs of TWRP and SuperSU!
I posted in General because I'm a new user so please move to appropriate forums! thanks!
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Please refer to the first line of my post. I understand that there are a large series of posts about how to do this but this is the only one that works for me even with me running android M.
Shows how to install TWRP for devices on 6.0
marcviado said:
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Click to expand...
Click to collapse
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
marcviado said:
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
Click to expand...
Click to collapse
It is totally there... I looked at that guide for a really long time too. I concede.
joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Yes it does. You do not need to use any codes, just enable oem unlocking in dev settings and type fastboot oem unlock and it will be unlocked.
Can't get twrp installed
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
I have the G4 LGUS991 gotta can I tell if it's h811?
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
Click to expand...
Click to collapse
What if your device could not be found despite having the latest LG drivers?
mr_blonde55 said:
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
Click to expand...
Click to collapse
Can't remember which thread, but I ran into the same problem you have and solved it by using an additional command like fastboot erase userdata. If you google it, you'll see the commands I mean. Basically, I had to factory reset the device through fastboot first (it sits there for several minutes to do this) before installing/booting twrp. And yes, the log will show that the process was successful, not a failure as mentioned by OP. Once I did that, I booted in twrp and flashed the rom zip without any trouble.
So, you guys mean we have Marshmallow on T mobile G4, I didn't get it yet.
Please somebody give me a link to the OTA or update.zip for MM of LG G4
This one worked for me!
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Sent from my LG-H811 using XDA-Developers mobile app
NardVa said:
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Click to expand...
Click to collapse
Could you help me with is or point me in the right direction ? Please & thanks
Sent from my LG-H811 using XDA Labs
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
Majestyk007 said:
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
Click to expand...
Click to collapse
I keep getting this problem.
Sent from my LG-H811 using XDA Labs
I've just got a H811 and it automatically updated to Android 6 when I loaded it up. I will be giving this guide a go this evening. Many of the other links on the web are for lollipop and were released when the phone came out, so I'm thankful that this seems straight forward. http://uslugi.nie-spamuj.eu/rtv,1,0.html Hoping that it goes that way.
How to lock bootloader or hide status: bootloader state: unlocked?
Sr for my English!
So I followed this guide and I appear to be soft bricked at best and hard bricked at worst. I did read the other guide linked in the second response and I found a major difference that might be my problem. So in the guide linked in the second response it doesn't say to even try flashing TWRP from fastboot. It says to just boot from it then install it from within TWRP. I followed the steps verbatim and my phone is currently stuck at the T-Mobile splash screen. Any suggestions? I have tried to boot into recovery by holding down and the power and releasing the power for a second when the logo comes up. I get into the Factory data reset screen and select Yes twice then the green guy shows up and the phone resets but stays at the T-Mobile splash screen. I don't have ADB or fastboot with the phone in this state.
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
rmdeathwish said:
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
Click to expand...
Click to collapse
It's not buggy at all. All the tedium has already been bypassed if you already have Marshmallow installed.
Follow autoprime's original guide, steps 2, 4, 5, 6, and 8 under the Bootloader OEM Unlock + Root section. I would recommend a more up-to-date version of TWRP than 2.8.7.1 though. Go to TWRP's download site for the latest version.
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
foxcell said:
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
Click to expand...
Click to collapse
Which Moto E5 Play do you have? There are several variants. Look for your model number in SETTINGS>>ABOUT PHONE and I should be able to help you out. As long as your device boots into TWRP normally, a fix shouldn't be difficult.
By the way, the "bad key" and "N/A" notofications are completely normal, and will occur even when your device does boot normally into the Android OS. However, there are custom boot logos you can flash to hide the screen.
MotoJunkie01 said:
Which Moto E5 Play do you have? There are several variants. Look for your model number in SETTINGS>>ABOUT PHONE and I should be able to help you out. As long as your device boots into TWRP normally, a fix shouldn't be difficult.
By the way, the "bad key" and "N/A" notofications are completely normal, and will occur even when your device does boot normally into the Android OS. However, there are custom boot logos you can flash to hide the screen.
Click to expand...
Click to collapse
Thank you for replying! In TWRP I don't see any 'About Phone' in Settings, it just has General (with check boxes), Time Zone, Screen, Vibration, and Language.
However, product/variant does appear when I boot into bootloader, it says: Product/Variant: james XT1921-5 16GB P3
foxcell said:
Thank you for replying! In TWRP I don't see any 'About Phone' in Settings, it just has General (with check boxes), Time Zone, Screen, Vibration, and Language.
However, product/variant does appear when I boot into bootloader, it says: Product/Variant: james XT1921-5 16GB P3
Click to expand...
Click to collapse
Yeah I wasn't even thinking -- with no way to boot up, you can't check settings. But, xt1921-5 is good news. That's the variant I own and support.
Ok, go to my thread here and download the stock ROM in the download link. Get the most recent one I have listed, which is the current stock ROM. Download it on a PC preferably. Connect your device and PC and copy the ROM over to your external SD card (external SD is necessary because /data needs to be formatted). In TWRP recovery mode you can transfer the ROM from PC to device. Once ROM is on external storage, follow the precise instructions in my thread. You'll be up and going before you know it.
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2
MotoJunkie01 said:
Yeah I wasn't even thinking -- with no way to boot up, you can't check settings. But, xt1921-5 is good news. That's the variant I own and support.
Ok, go to my thread here and download the stock ROM in the download link. Get the most recent one I have listed, which is the current stock ROM. Download it on a PC preferably. Connect your device and PC and copy the ROM over to your external SD card (external SD is necessary because /data needs to be formatted). In TWRP recovery mode you can transfer the ROM from PC to device. Once ROM is on external storage, follow the precise instructions in my thread. You'll be up and going before you know it.
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2
Click to expand...
Click to collapse
Thank you, I will try it and report back, if not today then tomorrow. Thanks again!
foxcell said:
Thank you, I will try it and report back, if not today then tomorrow. Thanks again!
Click to expand...
Click to collapse
Good luck. And just follow the instructions to the letter and it'll go smoothly.
Well I got some bad news... phone is stuck in a boot loop now, and no longer loads TWRP. I followed your directions and Oreo installed with no errors or warnings. Since going to Reboot -> System, it boots, says "N/A", then reboots.
I can get out of the boot loop by pressing volume down + power key, and from there I can access Android recovery (says 'bad key' when booting, instead of 'N/A') which gives me various options. It can still read SD cards and even says the proper OS.
I think it can still be saved since I can access Android recovery. I haven't tried the format system or cache options from Android recovery, because that might permanently screw it up.
Anyways... I'm here if you have any advice on what I can do. Maybe I should of bought an E4, lol.
Would you suggest I follow this?
https://forum.xda-developers.com/moto-e5/how-to/firmware-restoring-moto-e5-play-to-t3820053
I have no data on the phone so everything can be wiped no problem.
MotoJunkie01 said:
Good luck. And just follow the instructions to the letter and it'll go smoothly.
Click to expand...
Click to collapse
Would you suggest I follow this?
https://forum.xda-developers.com/mot...ay-to-t3820053
I have no data on the phone so everything can be wiped no problem.
foxcell said:
Would you suggest I follow this?
https://forum.xda-developers.com/mot...ay-to-t3820053
I have no data on the phone so everything can be wiped no problem.
Click to expand...
Click to collapse
Yes. Follow that guide to the letter. However, avoid flashing gpt.bin and bootloader.img. Otherwise, follow the instructions exactly. Please note that the "bad key" and/or "N/A" notifications you see during boot up are completely normal and have no real significance here. There are custom boot logos you can install to hide the notifications.
MotoJunkie01 said:
Yes. Follow that guide to the letter. However, avoid flashing gpt.bin and bootloader.img. Otherwise, follow the instructions exactly. Please note that the "bad key" and/or "N/A" notifications you see during boot up are completely normal and have no real significance here. There are custom boot logos you can install to hide the notifications.
Click to expand...
Click to collapse
I did as followed, and phone is restored!!! Now when starting up it says "bad key" so I assume that means bootloader is still unlocked?
I still want to root and such, but I think I'll wait because rooting instructions I found were vague and trying to follow them got me into the situation I was in, lol.
Thanks for your help!!
foxcell said:
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77283595&postcount=196
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.