Related
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.
Hey everyone, so tonight I got the 4.4 ota on my N7, I am unlocked and rooted but stock everything including recovery.
After updating, my N7 keeps going to stalk recovery and that's it.
I know I can just reflash everything but I have a few very important files. Is there a way to reflash 4.3 without losing data or accessing the data partition while soft bricked so I can recovery my files?
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
chrisinsocalif said:
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
Click to expand...
Click to collapse
I'm not sure. I'd like to have this confirmed before I do anything. It's not urgent as the due date on my prgect isn't for another couple of weeks. But thanks. I'll look at that as a last resort.
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
chrisinsocalif said:
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
Click to expand...
Click to collapse
ADB or Wugs root kit don't see my Nexus 7 as it keeps rebooting to the dead droid and I know I don't have it set for debugging. Guess I'm screwed.
When you say "dead droid", you're referring to fastboot mode, right? (Android icon with a bunch of text below it, starting with "Fastboot Mode" in red.)
If you have fastboot, you can flash TWRP Recovery 2.6.3.0. Download it from Team Win's site (Google it). Then:
fastboot flash recovery openrecovery-twrp-2.6.3.0-grouper.img
fastboot reboot-bootloader
Use the Volume keys to select "Recovery Mode" and hit Power. Once you see the TWRP menu, you should have adb root access automatically. Connect tablet to USB, and use adb pull to download the contents of /sdcard:
adb pull /sdcard /dumphere
Replace "dumphere" with whatever directory you want to dump to. I'm sure there's better guides and explanations for this, but this is the quick version.
I guess you could reflash stock recovery afterwards, but I can't think of a reason why you'd want to. It's not like it's that useful.
As a rule of thumb, you should at least know how to get around a command line, and use adb and fastboot before mucking around with your tablet.
-XCN-
P.S. I could be mistaken, but I don't think internal storage (which is /sdcard, or /data/media) is overwritten when you flash a ROM. Obviously, backup first before trying.
I have a VS980:
I rooted and installed twrp recovery.
I triedto install pac_vs980-dev-20140731
I copied it to root of my phone along with the gapps-kk-20140105-signed.zip.
I made a backup of everything on the phone, Then did a full wipe of everything.
I installed the two zips, and it says sucessful. Then goes into a boot loop!
I tried to recover the the backup and it is not found!
IDK what to do it is my girlfriends phone and she is absolutly ripped **** with me. I need serious help to fix this I have no idea what went wrong or how to fix it please help willing to make a paypal payment to anyone who can actually fix this. I was trying a new rom but adb sideload won't load either!
I keep seeing people saying that some commands work for them but when I am in twrp and click advanced and terminal command it loads up what looks like a file browser and I am lost. I seriously need to fix .
I tried the following:
from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
But both commands say there's no space left. what should i try now?
I'm new to this phone but can't you just load the phone's SD into the computer in twrp?
That's what I would do with my old phones.
drivenby said:
I'm new to this phone but can't you just load the phone's SD into the computer in twrp?
That's what I would do with my old phones.
Click to expand...
Click to collapse
No this phone doesn't have an SD Card, and the computer isn't seeing the phone at all while plugged in.
I ended up downloading the LG Flash tool and the stock KDZ file it took seconds and completely fixed the phone,
Just had to boot the phone into download mode (Press Volume Up and insert USB cord while phone is off)
and uploaded the KDZ file and all is new, still rooted, but other then that everything is back to full stock.
I don't understand why people don't just make KDZ files for the custom roms! It's much easier!
I know, I meant "mount as USB drive" option in twrp.
They probably need to digitally sign it for a kdz to work , so I don't think they can just "make" a kdz
Have you tried to go back into twrp and wiped the dalvick again. Then tried to reboot.
If all else fails, use the Return To Stock Guide in the general section. What version of Android did you have on the phone before you flashed this? You need to make sure the rom matches the baseband you're using.
( I posted this elsewhere, but i guess its beter in the actual HTCONE section) , mod feel free to delete my other one, thank you.
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
OnlyEYEShine said:
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
Click to expand...
Click to collapse
Here is a TWRP nandroid backup. You will have to put TWRP 2.6.3.3 on your phone. You will unzip the file and the resulting folder you will put on your phone in the following directory: //sdcard/TWRP/BACKUP/<Serial #>/<Name_of_folder>. If you are not able to get TWRP on your phone and the folder on your phone then you will need to find a Windows machine. Here is what you will need to do:
** Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone.
** Go to your bootloader. Do:
Code:
fastboot oem lock
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
** Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
majmoz said:
Here is a TWRP nandroid backup. You will have to put TWRP 2.6.3.3 on your phone. You will unzip the file and the resulting folder you will put on your phone in the following directory: //sdcard/TWRP/BACKUP/<Serial #>/<Name_of_folder>. If you are not able to get TWRP on your phone and the folder on your phone then you will need to find a Windows machine. Here is what you will need to do:
** Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone.
** Go to your bootloader. Do:
Code:
fastboot oem lock
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
** Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
Click to expand...
Click to collapse
Thanks for the info !!!,
But right off of the top, i am confused. I am currently downloading TMRP nandroid back up, as you said in beginning. Thing is i am unaware how to get that file onto my phone. Since it is stuck on the recovery page.... (DL is going to take a while on this machine), But if this fails, ill probably end up just tossing the phone, as i dont know anyone , nor have access to a PC machine. Sadly.
update - will attempt to push this thru via Terminal / adb will keep u posted !
-Update .. @majmoz well, i got hold of a PC laptop, did an adb / fastboot installed, dl'd the RUU, but i cant find the file from it after running the RUU. I even did cmd - Echo %temp% to make sure i was in the correct temp folder etc. Searched every sub folder there , and no zip files , or android.txt files was found . and i sorted them as u said as well.
Will continue trying tho...
Updated again - Well this time as RUU was installing again, i went to the temp files faster, and found 2 files Rom_01 & Rom_02 both zip files. But was unable to find any android text file. So now im at a standstill.
OnlyEYEShine said:
update - will attempt to push this thru via Terminal / adb will keep u posted !
-Update .. @majmoz well, i got hold of a PC laptop, did an adb / fastboot installed, dl'd the RUU, but i cant find the file from it after running the RUU. I even did cmd - Echo %temp% to make sure i was in the correct temp folder etc. Searched every sub folder there , and no zip files , or android.txt files was found . and i sorted them as u said as well.
Will continue trying tho...
Click to expand...
Click to collapse
The RUU Update Window should still be on the computer when you are looking for the files. Once the RUU goes past the first screen, the folder will be erased. You should also sort the /Temp folder by date so the most recent folder is at the top.
majmoz said:
The RUU Update Window should still be on the computer when you are looking for the files. Once the RUU goes past the first screen, the folder will be erased. You should also sort the /Temp folder by date so the most recent folder is at the top.
Click to expand...
Click to collapse
If i would of refreshed the page i would of seen your response, as i just re-editted my last post. with another update. =0)
I found 2 files with rom, Rom_01 & Rom_02 , both are zip files. but i cant find any android text file .
another thing, i am trying to find adb devices , but it is not locating my phone . I was able to earlier reboot into bootloader , etc. Now it tells me repeatedly that device is not found , i have tried adb kill-server, start-server etc. .. and phone is still on cyanogen simple recovery screen . .
Thanks again for ur time & help .. .definetly is appreciated !
OnlyEYEShine said:
If i would of refreshed the page i would of seen your response, as i just re-editted my last post. with another update. =0)
I found 2 files with rom, Rom_01 & Rom_02 , both are zip files. but i cant find any android text file .
another thing, i am trying to find adb devices , but it is not locating my phone . I was able to earlier reboot into bootloader , etc. Now it tells me repeatedly that device is not found , i have tried adb kill-server, start-server etc. .. and phone is still on cyanogen simple recovery screen . .
Thanks again for ur time & help .. .definetly is appreciated !
Click to expand...
Click to collapse
Keep both ROM files and save them for future use. Since you are able to use the PC, I would just run the RUU from the PC. Then in the future try to figure out how to run the two ROM files on your Mac. Just start the RUU again and let it do its thing.
majmoz said:
Keep both ROM files and save them for future use. Since you are able to use the PC, I would just run the RUU from the PC. Then in the future try to figure out how to run the two ROM files on your Mac. Just start the RUU again and let it do its thing.
Click to expand...
Click to collapse
Hey hey , good morning. Had some errands to do last nite then fell asleep. Going to attempt this again today . Oh, and i did run the RUU on the PC so thats where ill keep them also.
Will attempt to see if i can even connect to the phone with ADB, it seemed as if i was unable to last nite.
-update I got the phone to load to bootloader, & to fastboot usb I will try now to attempt this after coffee.. =0)
HAHAHAHHAHA ,, Oh man. Ok well being that it was pretty late last nite, and i had just woken up earlier .... I didnt realize that the RUU actually does the entire process on the PC. and that i DIDNT need to use cmd., and adb etc.
I want to thank you a TON @majmoz With my day or two of aggravation , then to just not get it right last nite.. I think i wasnt there mentally to actually read and pay attention.
My phone is in set up mode now. So i am 99% sure it is all good... Again, thanks , i definetly appreciate it !
OnlyEYEShine said:
HAHAHAHHAHA ,, Oh man. Ok well being that it was pretty late last nite, and i had just woken up earlier .... I didnt realize that the RUU actually does the entire process on the PC. and that i DIDNT need to use cmd., and adb etc.
I want to thank you a TON @majmoz With my day or two of aggravation , then to just not get it right last nite.. I think i wasnt there mentally to actually read and pay attention.
My phone is in set up mode now. So i am 99% sure it is all good... Again, thanks , i definetly appreciate it !
Click to expand...
Click to collapse
Glad you are back in business! :good:
@majmoz Hey i tried sending a PM earlier . but i see it never went thru in my sent Messages.
Just wondering if you can help me one last time. As i stated, i MUST have tmobile wifi calling. I initially had my bootloader unlocked months ago, and only rooted it few days before this brick issue.
Now since i did this process to fix the phone, i see bootloader = Relocked.
I dont want to add any custom roms etc, I simple want to root the device again. I know when i just did it , it was quick n easy and simple. But as im googling for the process now, i cant seem to find any that is similar to what i just did a few days ago. The processes seem extremely long. I think i just added a superuser apk of sorts , and it rooted.
Thanks again !
OnlyEYEShine said:
@majmoz Hey i tried sending a PM earlier . but i see it never went thru in my sent Messages.
Just wondering if you can help me one last time. As i stated, i MUST have tmobile wifi calling. I initially had my bootloader unlocked months ago, and only rooted it few days before this brick issue.
Now since i did this process to fix the phone, i see bootloader = Relocked.
I dont want to add any custom roms etc, I simple want to root the device again. I know when i just did it , it was quick n easy and simple. But as im googling for the process now, i cant seem to find any that is similar to what i just did a few days ago. The processes seem extremely long. I think i just added a superuser apk of sorts , and it rooted.
Thanks again !
Click to expand...
Click to collapse
Here is a step by step guide with pictures. This is called the HTCDev method and it is pretty standard. It just looks like a lot of steps but it isn't that bad.
majmoz said:
Here is a step by step guide with pictures. This is called the HTCDev method and it is pretty standard. It just looks like a lot of steps but it isn't that bad.
Click to expand...
Click to collapse
Gotcha, will try this in an hour or so . Have some errands to run. Thanks again !
OnlyEYEShine said:
Gotcha, will try this in an hour or so . Have some errands to run. Thanks again !
Click to expand...
Click to collapse
Keep this for future reference on how to flash the two RUU ROM zip files:
From nkk71's SuperGUIDE to returning 100% back to stock - Post #1211
http://forum.xda-developers.com/showpost.php?p=55921790&postcount=1211
How to flash two RUU ROM zip files
Code:
[B]fastboot oem rebootRUU
fastboot flash zip RUU_ROM_1.zip [COLOR="Red"][I]<-- hboot preupdate[/I][/COLOR]
fastboot flash zip RUU_ROM_1.zip[COLOR="Red"][I] <-- rest of the files in "1"[/I][/COLOR]
fastboot flash zip RUU_ROM_2.zip [I][COLOR="Red"]<-- files in "2" (kernel, touchscreen drivers 2, wipe userdate)[/COLOR][/I]
fastboot reboot-bootloader
[/B]
Click to expand...
Click to collapse
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.