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
Related
hey everyone !!
firstly, apologies if this should be somewhere else or if ive repeated someone else's problem.
hope you can help. ive got an HTC One and im trying to root it because i want to install a custom rom. ive tried lots and lots of ways including rom manager, superuser, fastboot, superboot. TWRP, CWM and your all in one toolkit but everything fails.. i was wondering if i have a problem with the internal storage. i tried to transfer a jpeg to the phone using HTC sync manager. i left it to transfer and went to work. 8 hours later the progress bar hadnt moved. i tried to transfer a boot image and it keeps timing out. rom manager comes back with errors when i do anything. for example if i try to go into fix permissions i get "an error occured while attempting to run privileged commands" im beginning to think that rooting this mobile is an impossibility. please help !!!
Did u unlock the bootloader?
Sent from my EndeavorU using Tapatalk 2
shiningarmor said:
Did u unlock the bootloader?
Sent from my EndeavorU using Tapatalk 2
Click to expand...
Click to collapse
hey shin hows it going ?
the bootloader is unlocked but i have noticed that the mobile is s- on. im guessing that i need to switch to s- off. is that possible ?
thanx matey !!
graemebonny said:
hey shin hows it going ?
the bootloader is unlocked but i have noticed that the mobile is s- on. im guessing that i need to switch to s- off. is that possible ?
thanx matey !!
Click to expand...
Click to collapse
You won't have S-Off unless you have it unlocked from the get go, ie a developers phone.
All you need to do is follow everything from this thread and youre good to go.
http://forum.xda-developers.com/showthread.php?t=2182792&highlight=how+to+root
The whole process should take about half an hour max as if you haven't made an account with HTC dev unlock then you will have to, they will send you a key once you send them the read out from your phone.
It's a really easy procedure to be honest.
dladz said:
You won't have S-Off unless you have it unlocked from the get go, ie a developers phone.
All you need to do is follow everything from this thread and youre good to go.
http://forum.xda-developers.com/showthread.php?t=2182792&highlight=how+to+root
The whole process should take about half an hour max as if you haven't made an account with HTC dev unlock then you will have to, they will send you a key once you send them the read out from your phone.
It's a really easy procedure to be honest.
Click to expand...
Click to collapse
hey dude
as i said the bootloader is already unlocked so i dont have to do all that again. the method u suggest is one of the many i already tried and it didnt work. its info is all wrong. it keeps referring to the SD card. The HTC one doesnt come with an SD card ??? it has internal storage.
Graeme
Don't forget to erase cache after you flashed your recovery, this can cause many problems.
fastboot flash recovery recovery.img
fastboot erase cache
If you don't erase cache, this could be your problem.
Possible solution :
Did you try this method? Don't use any All-in-One tool to do this, do take the time to do this manually via an SDK/ADB command window (see my signature if it is not installed on your computer)
Download the boot.img HERE made by Paul O'Brien and the CWM recovery by Flyhalf205 HERE place both files in your platform-tools of your SDK folder.
Reboot into Bootloader mode
Plug your USB cable and make certain that FASTBOOT USB is highligted
At the prompt type>fastboot flash boot boot.img
Success message
Again at the prompt type>fastboot erase cache
Success message
At the prompt type>fastboot reboot-bootloader
Your phone will reboot in Bootloader mode
At the prompt type>fastboot flash recovery recovery.img
Success message
Againt at the prompt type>fastboot erase cache
Success message
At the prompt type>fastboot reboot
Once rebooted check if you have the Superuser application in the app Drawer
Did you manage to get recovery installed ok?
graemebonny said:
hey everyone !!
firstly, apologies if this should be somewhere else or if ive repeated someone else's problem.
hope you can help. ive got an HTC One and im trying to root it because i want to install a custom rom. ive tried lots and lots of ways including rom manager, superuser, fastboot, superboot. TWRP, CWM and your all in one toolkit but everything fails.. i was wondering if i have a problem with the internal storage. i tried to transfer a jpeg to the phone using HTC sync manager. i left it to transfer and went to work. 8 hours later the progress bar hadnt moved. i tried to transfer a boot image and it keeps timing out. rom manager comes back with errors when i do anything. for example if i try to go into fix permissions i get "an error occured while attempting to run privileged commands" im beginning to think that rooting this mobile is an impossibility. please help !!!
Click to expand...
Click to collapse
The sd card Nens referring to is the internal storage
Sent from my GT-I9300 using Tapatalk 2
Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
EDIT: What I did from beginning was followed this video "How to Root the HTC One-FlamingArio"to the point where you try and flash the recovery fastboot. That didnt work so after trying to fix that I tried How To Root HTC One & Unlock Bootloader - Easiest & User Friendly- The smoking Android ( super boot a 1 click install) that made my bootloader screen turn to tampered. after that I tried One_M7_All-In-One_Kit_v1.
Note in all in one kit I did erase cache and standard recovery works fine, I've re-installed it may times.
Cant post links yet but I gave video names.
EDIT: when I do the cmd fastboot devices my device shows up when I do adb devices nothing shows up could this be part of the problem?
Thank you all for your help, I re-installed all the programs on my laptop and redid all the steps and it worked. Bye!
Try this in ABD fastboot erase cache then flash the recovery again i hope this helps:fingers-crossed:
What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps
Tonberry23 said:
Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
Click to expand...
Click to collapse
Keep an eye on this thread http://forum.xda-developers.com/showthread.php?t=2302870
Many people are looking for the Telus RUU.
Can you still access standard recovery? If so try reverting to factory settings (all data will be lost) and try to boot.
If you can get it to boot you should have more luck in trying to root your device.
I know that I had some issue's trying to get root on my device. But once I got S-off with revone, I was able to install root no problem.
ArmedandDangerous said:
What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps
Click to expand...
Click to collapse
But I would agree, if you can post the steps you have taken so we know where the bottleneck is.
Hope this helps you out bud
Still need help
Tonberry23 said:
Still need help
Click to expand...
Click to collapse
Nice to see you sorted it
Assuming you have actually flashed a recovery image to your device, you will then need to push a ROM to your sd card so that you can flash it in recovery.
Just do the following:
1. I am guessing you have the HTC drivers installed on your PC.
2. Download the attached adb.zip and unzip it to a folder on your C drive and call the folder whatever you like.
3. Boot your device into recovery and plug it in to a powered USB port on your PC.
4. Navigate to the folder that you just created on your PC and copy your ROM zip into it. rename the ROM zip to 'rom.zip' to make life easy.
5. Inside the folder, press and hold the shift key and right click in a blank part of the window and select 'Open command window here' (screenshot attached).
6. Type 'adb push rom.zip /sdcard' (don't use the quote marks)
7. Press 'enter'
8. Once the zip has finished being pushed to your sdcard, you can reboot into recovery and then flash it as normal.
EDIT: That will teach me not to read to the very end of a post. I'll leave this here for someone else.
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
EDIT: Got it resolved!
In order to get into Recovery I had to use the following commands in the bootloader:
fastboot format cache
fastboot format userdata
After doing this I was able to boot into recovery. However, recovery showed 0MB available storage and wouldn't mount /data, which prevented me from installing anything. It also wouldn't allow me to copy anything to the SD card using Android File Transfer or ADB sideloading.
To solve this I went into "Wipe" while in recovery and did a full format (the one that requires you to type "yes" before proceeding"
After doing this and booting back into recovery, I had full storage space back and recovery was able to mount /data. At this point I just copy/pasted the 5.1.1 ROM onto the sdcard with Android File Transfer. Once installed, I flashed the ROM and it booted right up.
I then skipped through the setup to get to settings and in developer settings I ticked the box to allow OEM unlocking. After doing that, I booted back into the bootloader and used the fastboot command "fastboot oem unlock" to unlock the bootloader again.
Once that was done I was able to use fastboot commands to flash the M preview all over again.
Hopefully you don't find yourself in this mess, but if you do, I'm hoping the above solution works for you.
sn0warmy said:
Well, I really did it this time. In my efforts of messing the the M Preview build and trying to eliminate the verification failed startup message I really locked up the phone. I locked the bootloader and now the phone will not boot into either recovery or the ROM. It won't let me "fastboot OEM unlock" the device either because it requires me to go into settings and check the allow OEM unlock. However, since I can't boot into the ROM, I cannot do that.
I'm really stuck here. Any ideas?
Click to expand...
Click to collapse
Hope you can RMA it
akellar said:
Hope you can RMA it
Click to expand...
Click to collapse
Well.... s**t.
sn0warmy said:
Well.... s**t.
Click to expand...
Click to collapse
Is TWRP installed?
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
I did something similar this past weekend while trying to do the 5.1.1 upgrade with the OTA files before the Factory images were available.
Try and use the WugFresh tool to wipe the cache and such, and try some of the other obvious settings in the tool.
It was late and I'm not 100% sure what I did but I do remember reflashing the LRX22C from the factory image using the tool. Everything I did was from the tool minus the 5.1 OTA that came through once I was able to get back into the device. From there I was able to unlock the bootloader again.
I was worried myself that I might have to send the phone back but I just kept trying, don't give up just yet. I've been told many times it's almost impossible to brick an android device now a days.
Good luck!
sn0warmy said:
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
Click to expand...
Click to collapse
Enable MTP in TWRP then drag n drop.
rootSU said:
Enable MTP in TWRP then drag n drop.
Click to expand...
Click to collapse
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
sn0warmy said:
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
Click to expand...
Click to collapse
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
rootSU said:
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
Click to expand...
Click to collapse
Success!
TWRP was also reporting 0mb available storage. I went into Wipe and performed a full format. Booted back into recovery and storage was showingt he full amount again. I was then able to plug the phone in and enable MTP and drag/drop the 5.1.1 ROM onto the SD card. Just flashed it and it booted right up!
I'm going to update the OP with all this info just in case someone else runs into the issue and needs help.
Thanks for your help!
sn0warmy said:
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
Click to expand...
Click to collapse
Hi,
I faced the same condition like you experienced, with some differences:
- the phone stuck in "Google" logo
- stock recovery is accessible from bootloader
- I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
any ideas what to do next?
================ edited- add below info on how I got stuck
So my N6 was still on 5.0 (has not been updated to 5.1). I decided to try the M preview. I downloaded the preview, and began the process as follows:
1. reboot into bootloader
2. fastboot oem unlock
3. flash-all (success on loading the bootloader and radio, but error on updating the image)
4. hence i followed to flash individually:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
5. and comes the stupid thing ! --> fastboot oem lock (really really regret why I did this)
6. and then once reboot, it stuck in Google logo forever
However, I am still able to access:
- bootloader (fastboot recognize the device, but wouldn't allow me to fastboot oem unlock)
- able to go to stock recovery, and as mentioned above:
I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
I tried to adb sideload the M preview image and 5.1 LMY47I but both showing the above error....
hope you can shed some light on this...
Please does anyone have a solution to this? please help me
Iambenqazy said:
Please does anyone have a solution to this? please help me
Click to expand...
Click to collapse
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Strephon Alkhalikoi said:
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Click to expand...
Click to collapse
.
OK What i was trying to do was to flash a stock recovery, i start it by running the flash-it all.bat file in the factory image zip, it changed the user interface of the bootloader after first reboot and and had an error for "archive: recovery.sig not found" (something like). the phone status shows Software Version: Modified and fastboot oem unlock dont give the confirmation.
and
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
If you can't even get into the bootloader (volume down and power) you may have to have the device serviced. Do you get a response when you type "adb devices"?
Iambenqazy said:
.
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
Click to expand...
Click to collapse
Maybe it just crashed at a black screen? Does a very long press of the power button (over 10 secs) cause it to react?
Or maybe the battery is empty? Try connecting the power supply for some time.
i did that but no response.
Iambenqazy said:
i did that but no response.
Click to expand...
Click to collapse
The very dead battery is a real possibility. The thing is, using the charger that came with the phone isn't going to help. If you think the battery being dead is a possibility, you would need to plug the phone into a USB port on a PC, that is a very slow charge. Leave it on there overnight then unplug and replug. If the led at the top of the screen lights or the battery icon shows on the screen, you have hope. At this point using the original charger should get the battery going again. In this case, plan on replacing the battery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
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?
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.