Hi friends today I am going to tell you how to root k4 note which have Android 6.0 (M.M).
Many members have already given this process but in some place the needed files are missing and some other place the process is not explained clearly. So to slove this I have made all in one file and given the process as simple as possible by me.
This process have worked very fine for me. Rooted 8 k4 notes without any problem.
Read all and follow. And do it on your own risk. I am not responsible if anything go wrong.
First of all I would like to introduce myself ( I know it's not necessary but to some of them to believe my work )
Myself is Kaushik. I have been using XDA since 2 years but never opened an account and replied in posts. Now after learning a lot I thought I should also start replying. May be I am a junior member here but not truly a junior member.
I have flashed more then 250 mobile of all brands. And thanks to XDA my success rate is 99.7 %
Thanks to XDA to making me local gadget guru. Now here every one believe that if even service center also fail to slove some software problems but at last kaushik will surly pass.
OK now let's see how to root.
(This will void your warranty)
(Phone will factory reset, which means all of the apps and data will be gone, not the internal sd)
(To root Lenovo K4 note you need to first unlock the bootloader. See below to know how to do it )
1. First download the two files from the links I have given.
All files needed to install twrp and root are in one zip file. Link is below.
https://mega.nz/#!D8MAwSzK!BYSzl4FGE_dbLy5wwzS0lbwSSNbelB7eMmfwdQjDoos
Usb ADB drivers for k4 note. Link below.
https://mega.nz/#!281yHDoI!iuIynHRqf8ui7IffStBhwrJvHJ4NBn1eExy_MYpr13o
Now to unlock bootloader.
2. Now in your mobile go to 'Settings' / 'About Device' / press 7 times on built number to unlock Developer options.
3. Now go to Developer options and click on 'OEM Unlocking' and press enable.
4. Next enable the USB debugging.
Your bootloader is now unlocked.
Now in PC extract the downloaded files
5. Install lenovo adb drivers ( it is in the link I have provided ) on your pc
6. Go to adb folder and press and hold shiftkey and right click with mouse. Select open command from here.
7. type adb reboot bootloader You need to authorize the pc if not done already. (The phone will boot onto fastboot, you can see small fastboot written on the left corner of the screen once the phone boots)
8. Now open adb folder and open 'unlock_bootloder'. A message will be displayed in mobile to press volume up key to continue. Press volume up key. A message in pc cmd will display as press any key to continue. Now press any key.
9. Now in cmd type fastboot flash recovery recovery.img
A message will be displayed as done.
Next part is very important
10. After its done press volume up and down button together with power button. Once you see the lenovo white screen, release the power button, release the volume keys once the screen goes black, wait for few minutes till you boot into the new custom recovery.
To avoid black screen set brightness below 30 in twrp settings. ( Not so important if don't understand how to do it )
11. Now the recovery allow modifications by just swiping and the goto mount and tick system and go back
12. Now go to advance, then file manager, then system, and delete the file named, recovery from boot.p ( if you are facing problem plz see point 14. )
13. After done do back and flash supersu.zip. (it is in the link which I have provided)
Now you phone is rooted and the supersu app will appear in the app drawer.
14. If you are facing problem with file manager flash aroma file manager ( it is in the link ). It will open in twrp. Now go to system and delete recovery from boot.p.
If you do not delete the said file again stock recovery will be replaced. If it happens so again you must repeat the steps from step 1.
Next to install xposed after boot up install xposed.apk (app is in the link)
Next flash xposed zip file. (Zip in the link )
Please don't forget to hit thanks if it helped you.
It will make me post more and help others.
Thanks
Regards
Kaushik.
Is this process safe??
HELP ! Fastboot doesn't recognize my device
s230 update brought a lot of issues thus I downgraded to s218 & now on s219. I am able to get adb to recognize my device but not fastboot. Therefore I am unable to unlock bootloader!
When I type in " adb reboot bootloader" or click on the "unlock_recovery.bat" file provided, I get booted into a dark screen where "fastboot" is written at the bottom left & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
Paras1259 said:
Is this process safe??
Click to expand...
Click to collapse
Yes it's 100℅ safe bro. But how ever if you do any mistake I will not be responsible.
sujitmohanty2012 said:
s230 update brought a lot of issues thus I downgraded to s218 & now on s219. I am able to get adb to recognize my device but not fastboot. Therefore I am unable to unlock bootloader!
When I type in " adb reboot bootloader" or click on the "unlock_recovery.bat" file provided, I get booted into a dark screen where "fastboot" is written at the bottom left & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
Click to expand...
Click to collapse
I Too have faced same problem. But I have installed all the drivers and it started working back to normal. So install the drivers which I have given in the link. Plz hit thanks if helpful. And plz make sure you have unlocked bootloader in developer options
Ongoli Koushik said:
I Too have faced same problem. But I have installed all the drivers and it started working back to normal. So install the drivers which I have given in the link. Plz hit thanks if helpful. And plz make sure you have unlocked bootloader in developer options
Click to expand...
Click to collapse
Thank you for the followup! I am surely gonna give this another go
What is the version of TWRP...
Sent from my Vibe K4 Note using XDA Labs
the internal memory is almost full after flashing twrp by this method.. any solution
the internal memory is almost full after flashing twrp by this method.. any solution plzz..
I am going to flash a new rom (6.0.1 ROM) ... So do I just flash Xposed??
anaynymous said:
I am going to flash a new rom (6.0.1 ROM) ... So do I just flash Xposed??
Click to expand...
Click to collapse
i have a7010a48 and after flash to S219_160810_row missing imei and Version of the radio module.How to fix it.
sujitmohanty2012 said:
s230 update brought a lot of issues thus I downgraded to s218 & now on s219. I am able to get adb to recognize my device but not fastboot. Therefore I am unable to unlock bootloader!
When I type in " adb reboot bootloader" or click on the "unlock_recovery.bat" file provided, I get booted into a dark screen where "fastboot" is written at the bottom left & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
Click to expand...
Click to collapse
Bro you have to reset your lenovo vibe k4 note using spflash tool
bro, how to enter recovery mode for second time? i try press volume up+down+power, after white screen i release power button, after black screen i release all button, but nothing happend.. your tutorial fully working, i can install supersu.. plz help me..
salaminder said:
bro, how to enter recovery mode for second time? i try press volume up+down+power, after white screen i release power button, after black screen i release all button, but nothing happend.. your tutorial fully working, i can install supersu.. plz help me..
Click to expand...
Click to collapse
Check this . you will be able to know
https://www.youtube.com/watch?v=uF_F0G2eEhg
---------- Post added at 01:09 PM ---------- Previous post was at 01:09 PM ----------
udeshdhiman said:
Bro you have to reset your lenovo vibe k4 note using spflash tool
Click to expand...
Click to collapse
Why do I reset?
Is this ROM works for all ROW numbers?
Hi Koushik,
I have some questions,
Is this ROM works for all ROW numbers? present my device having s232 ROW.
Is this process will erase internal memory, coz i want to root my device to recover some files from internal memory.
Can you give me replay on this
Thanks.
My Phone Volume Down broken
Hi Bro.
My volume down button was broken, any alternate method
ask
does it work in android 5.0 s152?
stock recovery
please i need stock recovery lenovo a7010a48 s232
can i delete TWRP
alsa7er said:
please i need stock recovery lenovo a7010a48 s232[/QUOTE
Flash whole rom via sp flash tool
Click to expand...
Click to collapse
naandha114 said:
alsa7er said:
please i need stock recovery lenovo a7010a48 s232[/QUOTE
Flash whole rom via sp flash tool
Click to expand...
Click to collapse
ok thank you:good:
Click to expand...
Click to collapse
Related
Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
ODIN download mode
- Turn your device off and unplug it
- Wait 30 seconds (screen off doesn't mean the device has finished turning off)
- Press-and-hold the power button and very shortly after (0.5 seconds, but not simultaneously) press-and-hold the left volume button
- Release the buttons as soon as you see something on screen. You should be looking at a USB icon and a digging Android.
- Make sure the digging Android is flashing. If the USB icon is flashing, press the left volume button to switch to the Android.
- Press the right volume button to select and enter download mode
Bootloader unlock
Flashing this firmware will also unlock the bootloader.
Included languages
Deutsch
English (UK)
English (US)
Espanol
Italiano
Nederlands
Portugues
Instructions (Windows)
- Download and extract the attached Odin zip file
- Download and extract the ROM (you should end up with three .tar.md5 files)
- Go into bootloader mode, as described above
- Start Odin
- Look at the attached Odin screenshot, make sure of the following:
--- Re-Partition: NOT checked
--- Auto Reboot: checked
--- F. Reset Time: checked
--- Flash Lock: NOT checked
--- Phone EFS clear: NOT checked
--- Phone Bootloader Update: NOT checked
- Press the big BOOTLOADER button on the right and select the "BOOTLOADER_P7100BUKC8.tar.md5" file
- Press the big PDA button on the right and select the "PDA_SIGNED_HRI83_BUKDF.tar.md5" file
- Press the big PHONE button on the right and select the "MODEM_HRI83_BUKDF_REV_03.tar.md5" file
- Connect your device with the USB cable
- Wait a few seconds, Odin should say it is now connected
- Hit the Start button, and wait until the device boots
- Press the Thanks button below this post and/or donate
Random notes
"adb reboot recovery", "adb reboot download" and "adb reboot bootloader" now appear to be working, they weren't on the KD9 ROM my device came with.
Download
Here is the link: http://www.multiupload.com/LWN6RHF8WJ
NOTICE: FLASHING ALSO WIPES YOUR SD-CARD !
Chainfire said:
Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
Click to expand...
Click to collapse
Nice gift!
My bootloader was locked before this update, and I did not attempt to unlock it. Download mode tells me the OEM lock is now unlocked. Please confirm! (I may be a dumbass )
Click to expand...
Click to collapse
Do you see the open padlock on the boot logo screen?
bcmobile said:
Nice gift!
Do you see the open padlock on the boot logo screen?
Click to expand...
Click to collapse
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !
Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.
Chainfire said:
Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.
Click to expand...
Click to collapse
Yay! They do work if you do a adb reboot from the shell, but anyway, that's history now.
If you see the open padlock, you're in business. Im guessing that ROM was not meant for general public... in fact, if it came from where I think it came from, it wasn't
EDIT: So it has the stock recovery menu as well? Can you possibly do a system/boot/recovery dump to save us the pain of Odin?
EDIT2:
Chainfire said:
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !
Click to expand...
Click to collapse
fastboot oem unlock
I love Samsung... now
No Chinese at all, what a pity......
is it android 3.0.1 or android 3.1?
My device (bought in a vodafone ita store) has P7100BUKDF ROM and was already unlocked.
Myeah I was able to flash root after flashing this firmware, so it does unlock, it appears.
EDIT: Someone on twitter confirmed this unlocked the bootloader for him as well.
Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method
gjroeleveld said:
Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method
Click to expand...
Click to collapse
If you press enough buttons the menu appears in recovery
Added the SD-CARD wipe notice for ya
How do root this firmware ?
Thanks
http://forum.xda-developers.com/showthread.php?t=1079781 ?
any one know the difference between this one and stock rom? would be interesting to see if samsung changed anything.
Has anyone tried flashing with Heimdall in Linux?
As for the question about the difference with the original ROM I can tell that as mentioned in the first post more languages are supported.
The rest seems about the same as the previous rom.
Yes, it's also the only change I noticed from the stock room, but in my case is great since now it supports Portuguese (my native language).
I just unlocked my bootloader following your steps. It shows unlocked when booting back up but now it is not recognized by my pc when connecting through usb. I tried rebooting both pc and tablet. I also tried uninstalling the drivers from Samsung and reinstalling it but still no go. I have a Galaxy Tab 10.1v from Google I/O and the usb is gone. I cannot even charge from usb now. Are the files posted the correct ones for this device because it is not working. Does anyone have the correct ones? Any help would be appreciated.
The Google I/O Tab as far as I know is not a 10.1v, thus you shouldn't be using these files on it!
Yeah I figured that out now. I was following the root guide and I thought I was supposed to use this. Everything seems to work but the usb. But I can still connect to Odin and reflash. Is there anyway to get it back?
Note : This guide is for H-81120-I & H-81120-O the latest update any firmware version below it will cause hard-brick so be careful before attempting anything, i wont be held responsible.
As a user with less knowledge about Commands and all, i was searching for answers by reading threads here and there and found my answers though some time tricky and sometimes easy.
Also in reading those threads i found many fellow members stumble upon resulting Soft bricks and in some cases a Hard brick or can say making their beloved G4 a paper weight.
So i thought i must put some really easy steps in order to clearly guide people like me who are too noob to understand the sophisticated developers steps.
Another reason for this Thread is also i saw many people asking about how to etc after updating to 20-O update for our H811 MM.
Few things to Prepare before Start
1- Properly Install Drivers for your H811 Variant of G4, cant find them Install LG Bridge.
2- Read the Whole thread before starting anything.
3- Confirm that all requirements are full filled and your variant is capable of everything mention in the OP.
4- Enable Developer Option then inside it enable OEM unlock and Usb debugging.
5- Always use Command prompt as Administrator.
6- Make a folder name G4 and paste all the file required for the unlocking in it for easy access and remembrance.
7- For Safer side after unlocking the bootloader boot into TWRP from fast boot and do not install TWRP.
8- Flash your SuperSU after that boot into android and see if all works.
9- Again Via Fastboot boot into TWRP make a backup of everything working fine. Boot into android.
0- Again same Via Fastboot boot into TWRP and now install your TWRP image via TWRP install function. So if by any means this is the culprit you can still revive your phone via your backup.
Attachments to Download
1- Adb Package can be found Here.
2- Download the latest TWRP.img 3.0+ from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Since downloading is complete now simply unzip the adb folder (containing fastboot by default) and paste both the TWRP image file and SUPERSU zip inside it.
Now Hold Shift and Open Command prompt here.
1- Input command to see if your device is visible in ADB.
Code:
adb devices
if you see your device and the status is off line then there will be a prompt on your G4 screen waiting for approval, accept it and input same command now all will be fine.
2- Now input below commands one by one. ( All credits to Autoprime )
Code:
adb reboot bootloader ( This will reboot your device to Fastboot mode )
fastboot oem unlock ( This will wipe all your data )
fastboot getvar unlocked ( This will check your bootloader status: Should be successful )
fastboot boot twrp-3.0.2-0-h811.img ( Phone boots TWRP ) Please put the full file name with .img extension or it wont work.
3- Now the Phone should be in TWRP install SuperSU from there which you have already pasted inside your external SD card.
4- Reboot to system and see if SuperSU is installed. In some cases First flash of SuperSU does not work if your case is same the again boot to Fastboot and from there boot into recovery, since your bootloader is unlocked no need to repeat the unlock OEM command.
5- Now for safer side follow the steps 7, 9, 0 mention in Preparation heading above.
Hopefully all will be in your favor.
Useful Links if you still fail
Kdz 20-O after download must be unzipped
H81120o_00_0613.kdz
LGUP Software:
( All credits to MicroMod777 )
Disclaimer: Nothing in this thread is my work, if i have missed any credit please do let me know i will add. I know several guides are available for same purpose so if any body finds it offending any rights can ask the moderators to remove this thread. The purpose only is to guide simple people like me to save their devices from getting bricked.
As by reading the thread many people are falling for permanent TWRP installation as its mention in the OP anyways for people not getting permanent Recovery follow below:
Boot to TWRP from fastboot Bootloader
When recovery comes up click Install >>>> then in the right below corner you ll see a tab for IMAGE >>> press it browse the recovery IMG which you stored in your SD card >>> swipe to flash >>> From asking where to install >>> select recovery >>> DONE.
SignatureBoy said:
Attachments to Download
1- Adb Package can be found Here.
2- Download the from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Click to expand...
Click to collapse
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
DrakenFX said:
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
the ADB package i uploaded contains the Fastboot inside it
The thread clearly states it for 20-O
SignatureBoy said:
the ADB package i uploaded contains the Fastboot inside it
Click to expand...
Click to collapse
ok i meant the TWRP file needs to be in the same folder where Fastboot file is
DrakenFX said:
ok i meant the TWRP file needs to be in the same folder where Fastboot file is
Click to expand...
Click to collapse
That is also mention if you read the first post,
Since downloading is complete now simply make a folder and put all files downloaded inside it unzip the adb folder and paste both the TWRP image file and SUPERSU zip inside it.
Click to expand...
Click to collapse
SignatureBoy said:
DrakenFX said:
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
The thread clearly states it for 20-O
Click to expand...
Click to collapse
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.
ApokrifX said:
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.
Click to expand...
Click to collapse
yes it is for 20-O only
SignatureBoy said:
yes it is for 20-O only
Click to expand...
Click to collapse
Thanks for clarification. I’d change 1st post a bit:
Few things to Prepare before Start
0. LG G4 with 20o (stock) firmware.
When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
DanGarion said:
When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
Click to expand...
Click to collapse
Nevermind, I forgot about OEM Unlock...
thanks for the write up
This is not specific to 20o. It's the same steps we've been using all along. Nothing new to see here.
Sent from my LG-H811 using XDA-Developers mobile app
problem with fastboot
Thanks you for helping:fingers-crossed:
problem with fastboot
Hi,
I am a newbie in xda. I am trying to root and install TWRP into my lg g4. I am using software version H81120o. I checked enable OEM unlock and USB debugging. I have downloaded lg driver though lg bridge and all the files from the post. However, I got two problem while installing the twrp-3.0.2-0-h811.img.
1st problem (stuck here and need to reboot also not showing h811 on "the list of devices attached" after typing command "adb reboot bootloader"):
C:\Windows\system32>adb devices
List of devices attached
LGH811xxxxxxxx device
C:\Windows\system32>adb reboot bootloader
C:\Windows\system32>fastboot oem unlock
...
FAILED (remote: Already unlocked)
finished. total time: 0.012s
C:\Windows\system32>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.004s
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
cannot load 'twrp-3.0.2-0-h811.img': No error
2. 2nd problem(stuck here and need to reboot):
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
< waiting for device >
I checked online this problem might do with driver not up to date. Under device manager, my lg g4 is recognized under android device with android bootloader interface.
What should I do now?
Thanks you for helping:fingers-crossed:
This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??
I did everything but can't seem to get TWRP installed
Thanks a lot for this write up. I have been trying for about 2 weeks to root my g4 and it worked finally, So many thanks to you
The Remedy said:
This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??
Click to expand...
Click to collapse
same problem here but I just now got it working...sort of . I still can not make anything come up except the factory data reset when I use the phone volume and power button.
I thought it might be just that I wasn't coordinated enough so I downloaded this small app to do a recovery reboot.
After I installed the app and used it, I got the little android guy with his chest opened with the red triangle. I took out my battery, put it back in and booted my phone with the power button.
I then connected my phone to computer via usb and went back into adb and opened TWRP and installed the twrp-3.0.2-0-h811.img again but this time I looked around a little more first, and noticed a setting to either install in boot or recovery partition. I selected recovery partition (neither were selected) and installed it. Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.
I had the same issue but when u get into twrp make sure the IMG is in your SD card and to permanently have twrp installed go to home and press install.. Choose from image and install hope this helps
Sent from my LGLS992 using Tapatalk
fuzzy_ said:
same problem here but I just now got it working...sort of ................
Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.
Click to expand...
Click to collapse
In regard to booting into TWRP recovery with just the power and vol buttons, I just read this on another thread:
It boots into what appears to look like a default LG G4 factory reset page. For me, i clicked reset, and then yes, and surprisingly it brought me to where i wanted to go. TWRP Recovery.
I tried this and it worked for me as well.
I had been there before and tried it and it did a factory reset after I had spent an hour or two tweaking my phone, I was not a happy person. This time I did feel almost positive I had TWRP installed correctly and did not have nearly as much time spent getting things set up like I want them on my phone...It was still scary pressing that reset button and yes button.
If you don't have TWRP (or maybe some other recovery) installed it will factory reset your phone. I just thought I would share this and what happened with me. Do it at your own risk.
Credits go to: @ashyx, @mauam, @jedld, @Chainfire
Prerequisite:
Padded kernel for T280
http://forum.xda-developers.com/attachment.php?attachmentid=3881481&d=1474417563 (unpack with 7zip and put it to memory card)
SYSTEMMODE SuperSU (REQUIRED)
http://forum.xda-developers.com/attachment.php?attachmentid=3861602&d=1472738213 (put it to memory card)
All required drivers from Samsung Smart Switch
Odin 3.10
TWRP
https://www.androidfilehost.com/?fid=312968872162492913
Your unit should be fully charged
OEM unlock and USB Debugging enabled and allow your host computer
Steps:
1. Connect your tablet with your host computer
2. Open prompt and locate to your adb folder (platform-tools) and enter
Code:
adb reboot download
If it doesn't work, look at your tablet to see any prompt to allow your host computer
3. Open your Odin. Make sure auto reboot is not checked (but TWRP isn't overridden). Choose AP and locate your TWRP file. You may see secure check failed. Don't worry. Just press and hold power+volume down+home key together and wait for few seconds.
4. Enter TWRP by pressing power+volume up+home key together. You should see the boot screen. Keep pressing these buttons until the boot screen disappears. You should enter TWRP.
5. Locate your memory card. Flash systemmode SuperSU first, go back, and flash padded image as "boot".
6. (Optional) wipe cache and dalvik cache.
7. Reboot
8. It may take a while to boot up
9. You tablet rooted.
Hey, this works! Thank you for writing it up!
Success on a Samsung A6 SM-T280 (version 5.1.1 if memory serves).
Instructions weren't clear enough, got **** stuck in toaster...
Nah jk, it worked man!
EDIT: This is a lot harder than I thought it would be.... I lost root and did a reset and did it all again. This time after I got it rooted, I got rid of the SuperSU and downloaded the one from market. It updated binary easily.
sovereignjerk said:
Instructions weren't clear enough, got **** stuck in toaster...
Nah jk, it worked man!
EDIT: This is a lot harder than I thought it would be.... I lost root and did a reset and did it all again. This time after I got it rooted, I got rid of the SuperSU and downloaded the one from market. It updated binary easily.
Click to expand...
Click to collapse
I keep getting Custom Binary (Recovery) blocked from FRP lock. Did you get this as well?
mdsohal02 said:
I keep getting Custom Binary (Recovery) blocked from FRP lock. Did you get this as well?
Click to expand...
Click to collapse
Make sure you OEM unlock under the developer settings.
jedld said:
Make sure you OEM unlock under the developer settings.
Click to expand...
Click to collapse
Thank you Sorry, I haven't rooted an android device since the EVO 4G. Things have changed in the meantime.
---------- Post added at 02:48 AM ---------- Previous post was at 02:11 AM ----------
Does anyone know how to disable the OTA update notification once I am rooted ?
Does really count as a root? I thought needed bootloader...
sovereignjerk said:
Does really count as a root? I thought needed bootloader...
Click to expand...
Click to collapse
Yes, it's root.
The key is the recovery has SHA key embedded to bypass the bootloader.
mingkee said:
Yes, it's root.
The key is the recovery has SHA key embedded to bypass the bootloader.
Click to expand...
Click to collapse
Hi guys, has anyone tried APP2SD after rooting.?
After Step 3 it takes me to a warning screen with two options 1. Vol up to continue 2. Vol down to restart device.
So I go with option 1 but instead of taking me to TWRP it takes me back to download mode and at the top left corner this is what is shown.
ODIN MODE (In Red)
SECURE DOWNLOAD: ENABLE (In Blue)
MDM DOWNLOADBLOCK: O (In Red)
PRODUCT NAME: SM-T280
CURRENT BIN: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: OFF
USB Init Start!
USB core reset done
I made sure to uncheck auto reboot but couldn't find anything about TWRP not being overridden so maybe that's the problem, what am I doing wrong?
Can someone do a video tutorial about this root?
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Wingchundub said:
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Click to expand...
Click to collapse
i advise you to search youtube on how to use adb. This is how i learned. Its too complicated to write it. But when you see video its easy. In simplest way adb is cmd opened in adb file. Than in cmd you write commands like adb flash, or adb format and stuff
Wingchundub said:
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Click to expand...
Click to collapse
You don't need adb. Just boot to download mode normally.
ashyx said:
You don't need adb. Just boot to download mode normally.
Click to expand...
Click to collapse
Ashyx
Will link2sd/app2sd after root.?
ahmedyar91 said:
Ashyx
Will link2sd/app2sd after root.?
Click to expand...
Click to collapse
I don't see why not.
Will try and post
Finally rooted.
I came across this post and worked first time.
I installed supersu via trwp, then flashed img as boot in trwp also.
Worked perfectly
http://forum.xda-developers.com/gal...covery-samsung-galaxy-tab-a6-sm-t280-t3475381
ecstaseey said:
After Step 3 it takes me to a warning screen with two options 1. Vol up to continue 2. Vol down to restart device.
So I go with option 1 but instead of taking me to TWRP it takes me back to download mode and at the top left corner this is what is shown.
ODIN MODE (In Red)
SECURE DOWNLOAD: ENABLE (In Blue)
MDM DOWNLOADBLOCK: O (In Red)
PRODUCT NAME: SM-T280
CURRENT BIN: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: OFF
USB Init Start!
USB core reset done
I made sure to uncheck auto reboot but couldn't find anything about TWRP not being overridden so maybe that's the problem, what am I doing wrong?
Click to expand...
Click to collapse
Here's a more detailed guide. It's based on this thread: http://www.droidviews.com/root-samsung-galaxy-tab-a-sm-t280-and-install-twrp/
raakaysh said:
Here's a more detailed guide. It's based on this thread: http://www.droidviews.com/root-samsung-galaxy-tab-a-sm-t280-and-install-twrp/
Click to expand...
Click to collapse
That is the old method and no longer relevant.
Just follow the steps in the OP below.
http://forum.xda-developers.com/showthread.php?t=3475381
Hey guys,
I have recentley purchased a used Lenovo ZUK Z2 PRO from someone on Ebay, Later I found out that the original rom of this phone only supports English (mixed with chinese) and Chinese language, the whole Software looks too Iphoney for my taste so I rather have clean Stock android, prefferbly 7.1 8.0 or 8.1 as long as its stable and doesnt drain the battery too much, will someone be kind enough to help me out step by step? prefferbly via KIK messenger or something?
I've downloaded root checker to see if the phone has been rooted already it says root access is not properly installed on this device? see image below.
maserati2011 said:
Hey guys,
I've downloaded root checker to see if the phone has been rooted already it says root access is not properly installed on this device? see image below.
Click to expand...
Click to collapse
Hi, you have unlock bootloader . Maybe you have twrp . Just restart your phone and when you see start menu , press volume button and choose recovery . If you have twrp , just read Aex or RR threads , how to install the latest roms . It is bit difficult because of treble project . There are all informations about "how to install"
mar.ur said:
Hi, you have unlock bootloader . Maybe you have twrp . Just restart your phone and when you see start menu , press volume button and choose recovery . If you have twrp , just read Aex or RR threads , how to install the latest roms . It is bit difficult because of treble project . There are all informations about "how to install"
Click to expand...
Click to collapse
can you guide me through it please? my knowledge of rooting and flashing and unlocking is almost zero.
maserati2011 said:
can you guide me through it please? my knowledge of rooting and flashing and unlocking is almost zero.
Click to expand...
Click to collapse
read this to know some basic things
https://zukfans.eu/community/thread...-read-this-before-creating-a-new-thread.7603/
mar.ur said:
read this to know some basic things
https://zukfans.eu/community/thread...-read-this-before-creating-a-new-thread.7603/
Click to expand...
Click to collapse
Thank you, I will read it, but can you or someone else guide me through it live?
any one can help please?
ok i made some progess, now i want to unlock the bootloader i have adb, fastboot and unlock bootloader img in the same folder, when i open cmd and type adb reboot bootloader i get error device not found.
help?
in the developer options i can't see oem unlock, where can i find it?
maserati2011 said:
in the developer options i can't see oem unlock, where can i find it?
Click to expand...
Click to collapse
It isn't available in Zui 3.1 . You needn't unlock bootloader . When you restart your phone and see menu start ( for 5 sec ) use vol button to choose fastboot or recovery . Check it , maybe you have already had a Twrp .
mar.ur said:
It isn't available in Zui 3.1 . You needn't unlock bootloader . When you restart your phone and see menu start ( for 5 sec ) use vol button to choose fastboot or recovery . Check it , maybe you have already had a Twrp .
Click to expand...
Click to collapse
i dont think so because i installed the original rom 1.9 through QFIL first then i got updates over the air my z2 pro runs on official ZUI version 3.1.194 ST
what should i do now to unlock the bootloader?
mar.ur said:
It isn't available in Zui 3.1 . You needn't unlock bootloader . When you restart your phone and see menu start ( for 5 sec ) use vol button to choose fastboot or recovery . Check it , maybe you have already had a Twrp .
Click to expand...
Click to collapse
i have reverted back to ZUI 1.9 again with QFIL, i still dont see OEM Unlock option in the developer options?
maserati2011 said:
i have reverted back to ZUI 1.9 again with QFIL, i still dont see OEM Unlock option in the developer options?
Click to expand...
Click to collapse
In that case you have two ways to unlock bootloder
1. https://drive.google.com/file/d/1rqcY7WyYi6AN9MyfUqVWwm1CMCe7Tbmv/view
2. put this file in your phone and rename it to update
https://mega.nz/#!lgxXCBpA!4OlvXDYaeof__h8TPHwXDUUKAijP-qn8lHgfOdVPBfw
run update app tap three dots at right upper edge and choose recovery . In recovery choose english and update
After that you get oem unlock in developer options .
mar.ur said:
In that case you have two ways to unlock bootloder
1. https://drive.google.com/file/d/1rqcY7WyYi6AN9MyfUqVWwm1CMCe7Tbmv/view
2. put this file in your phone and rename it to update
https://mega.nz/#!lgxXCBpA!4OlvXDYaeof__h8TPHwXDUUKAijP-qn8lHgfOdVPBfw
run update app tap three dots at right upper edge and choose recovery . In recovery choose english and update
After that you get oem unlock in developer options .
Click to expand...
Click to collapse
which 1 is safer? and in method 1 in the video i see 2 files named recovery, where can i get those?
maserati2011 said:
which 1 is safer? and in method 1 in the video i see 2 files named recovery, where can i get those?
Click to expand...
Click to collapse
For the first you need bootloader_unlock.img from lenovo . Both are "safe"
twrp20180311
https://github.com/cosmedd/android_...eases/download/20180311/20180311_recovery.img
mar.ur said:
In that case you have two ways to unlock bootloder
1. https://drive.google.com/file/d/1rqcY7WyYi6AN9MyfUqVWwm1CMCe7Tbmv/view
2. put this file in your phone and rename it to update
https://mega.nz/#!lgxXCBpA!4OlvXDYaeof__h8TPHwXDUUKAijP-qn8lHgfOdVPBfw
run update app tap three dots at right upper edge and choose recovery . In recovery choose english and update
After that you get oem unlock in developer options .
Click to expand...
Click to collapse
for the 1st method the instructions aren't very clear, i see not 1 but different recovery images where can i get both? do i need both? and where can i get the txt file with all the commands? and the video ends at the 3rd or 4th command, does it mean the remaining commands are not important or what? and will this method help me get pass the OEM lock on my current ZUI 1.9 ?
for the 2nd method, do i have to unzip the zip file after i download it or no? and should i put it anywhere on the storage or does it have to be a specific map in the root or something>?
mar.ur said:
For the first you need bootloader_unlock.img from lenovo . Both are "safe"
twrp20180311
https://github.com/cosmedd/android_...eases/download/20180311/20180311_recovery.img
Click to expand...
Click to collapse
ok thanks, i tried the 2end method, i can see the oem unlock option and everything but now when i open cmd and type adb reboot bootloader i get error device is offline or device not found.
what to do now??
maserati2011 said:
ok thanks, i tried the 2end method, i can see the oem unlock option and everything but now when i open cmd and type adb reboot bootloader i get error device is offline or device not found.
what to do now??
Click to expand...
Click to collapse
In developer options turn on usb debugging , then in CMD ( turn on screen on your phone )
ADB devices ( get popup authorization on your phone - tick it )
mar.ur said:
In developer options turn on usb debugging , then in CMD ( turn on screen on your phone )
ADB devices ( get popup authorization on your phone - tick it )
Click to expand...
Click to collapse
didn't help, here is what i got:
fastboot>adb devices
List of devices attached
device offline
maserati2011 said:
didn't help, here is what i got:
fastboot>adb devices
List of devices attached
aa528557 offline
Click to expand...
Click to collapse
try adb devices
after that
adb kill-server
and try again
mar.ur said:
In developer options turn on usb debugging , then in CMD ( turn on screen on your phone )
ADB devices ( get popup authorization on your phone - tick it )
Click to expand...
Click to collapse
ok after many failed tries i succeded (i had to use a newer version of ADB + fastboot) but now i get a warning messege after reboot from fastboot mode see image below
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.