Develop Bugs

[Root]Wileyfox Swift

Hi all,
found out how to root this device!
Here the steps:
Make sure you have fastboot installed on your computer: https://wiki.cyanogenmod.org/w/Fastboot
download supersu zip from here
https://download.chainfire.eu/696/supersu/
save it to your external sdcard
enable developer options (settings - about - click mutliple times on the build number).
enable OEM unlock in the developer options settings on the device.
reboot Wileyfox Swift into fastboot mode: with the device powered down, hold the Volume Up and connect USB
to unlock the boot loader, WARNING!!! This wipes your user data!!!
on your computer type
Code:
fastboot oem unlock
fastboot -i 0x2970 oem unlock-go
fastboot oem unlock-go
download latest recovery image from here
http://download.cyanogenmod.org/?device=crackling
to boot the custom recovery, on your computer type
Code:
fastboot boot <name_of_recovery>.img
OR
install recovery
Code:
fastboot flash recovery <name_of_recovery>.img
and reboot into recovery manually (remove and reinstall battery, hold volume down and power buttons.
install supersu update zip from recovery menu (choose zip from extenal SD)
reboot and enjoy root access

Thanks
I went a step forward and installed the CM nightly.

mermigas said:
Thanks
I went a step forward and installed the CM nightly.
Click to expand...
Click to collapse
Does the camera work? I tried one of the first nightlies but the camera crashed, so this was no option for me.

olli_o said:
Does the camera work? I tried one of the first nightlies but the camera crashed, so this was no option for me.
Click to expand...
Click to collapse
No problem with camera for me.
All works fine and smooth
No bugs nored

olli_o said:
4) reboot directly into recovery. Normal system boot reinstalls stock recovery.
5) install supersu update zip from recovery menu
Click to expand...
Click to collapse
When in recovery I press apply update and sd card, before i've even selected supersu, which returns:
Install failed
Installation aborted
Installation aborted
any ideas?

monethys said:
When in recovery I press apply update and sd card, before i've even selected supersu, which returns:
Install failed
Installation aborted
Installation aborted
any ideas?
Click to expand...
Click to collapse
This is stange. I modified the instructions a little, does it also happen if you follow these steps?

OTA?
Will I be able to update my phone (ota?) after the root?
I'm fine with having to reroot

rebane2001 said:
Will I be able to update my phone (ota?) after the root?
I'm fine with having to reroot
Click to expand...
Click to collapse
Incremental auto-update won't work rooted. But you can manually update. See here

Followed instructions and now have a rooted wileyfox swift thank you

olli_o said:
Hi all,
found out how to root this device!
Here the steps:
download supersu zip from here
save it to your external sdcard
enable developer options (settings - about - click mutliple times on the build number).
enable OEM unlock in the developer options settings on the device.
reboot Wileyfox Swift into fastboot mode: with the device powered down, hold the Volume Up and connect USB
to unlock the boot loader, WARNING!!! This wipes your user data!!!
on your computer type
Code:
fastboot oem unlock
fastboot -i 0x2970 oem unlock-go
fastboot oem unlock-go
download latest recovery image from here
to boot the custom recovery, on your computer type
Code:
fastboot boot <name_of_recovery>.img
install supersu update zip from recovery menu (choose zip from extenal SD)
reboot and enjoy root access
Click to expand...
Click to collapse
In case anyone has a similar issue:
I could unlock. I could install the recovery. But SuperSU was coming up with signature errors and wouldn't install. I discovered that this was because the recovery was being overwritten (I flashed it to the device because "fastboot boot..." was not working).
I could not get the device to flash the recovery then reboot to recovery without it going into normal boot first and rewriting the recovery so that I would not be able to install SU.
The solution I found for this was to take the back of the phone off.
Flash the recovery: fastboot flash recovery "recovery file name".img
Then just pull the battery.
Hold the volume down when you put the battery back in and launch the device still holding volume down.
Remember to release the power button once you see fox logo or you'll reboot again.
Now I installed SuperSU without a hitch and all is good.
Hope that helps anyone who is stuck.
Links removed from quote so as not to trigger spam bot.

Help
olli_o said:
Hi all,
found out how to root this device!
[*]download latest recovery image from here
/download.cyanogenmod.org/?device=crackling[/
[/LIST]
Click to expand...
Click to collapse
All the list from here is a nightly build. Can you give the stable mod? I'm noob so can follow it. it is very hard for me to make it work I'm still working to install the fast boot for mac. I found this:
bash <(curl -s htps:/raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
It seems to work when i check this command:
adb devices
BUT NOT SURE if this is safe.
Please provide link for recovery or rom which i can follow using your guide. There are many in the link above but which one is stable and i can use that all the of the system functioning.
Thank you in advance.

I hope this will help someone figure things out w/ what i did... LOL
Thanks ALL. Basically the post above helped to root my phone but its been hard for me and as mentioned in my previous post, I'm noob. So here is what i did after the fastboot issue and continue on even though i didn't know if the install is safe since my OS X was able to detect the device/phone as mentioned above.
1. On fastboot, i just use "fastboot devices" to verify my phone is connected. This command did not work "fastboot -i 0x2970 devices"
2. Then use, "fastboot oem unlock-go" and i waited about 20sec as the terminal returned that message and then it was confirmed unlocked. These commands did not work "fastboot oem unlock, fastboot -i 0x2970 oem unlock-go" my terminal just froze and did nothing.
3. Then i use this to check if it is unlocked "fastboot oem device-info"
4. Using the link on downloading the recovery, i just click all of upper part with the picture and found the .img file see below:
Swift
Wileyfox - crackling
Download Latest Nightly (this is .zip file)
Download Latest Nightly Recovery (this is the .img file which i used)
Device Wiki 2016-01-07
5. update: i did erase recovery "fastboot erase recovery"
i use two commands and both works "fastboot flash recovery cm-12.1-20160107-NIGHTLY-crackling-recovery.img"
(here is the terminal msg: target reported max download size of 268435456 bytes
sending 'recovery' (23110 KB)...
OKAY [ 0.727s]
writing 'recovery'...
OKAY [ 0.387s]
finished. total time: 1.114s)
and this "fastboot boot cm-12.1-20160107-NIGHTLY-crackling-recovery.img"
(here is the terminal msg:downloading 'boot.img'...
OKAY [ 0.727s]
booting...
OKAY [ 0.186s]
finished. total time: 0.913s)
(I LEARNED THE HARD WAY THE .img file must be IN THE SAME DIRECTORY of the fastboot - but PLEASE ASK THE EXPERTS and don't copy if i did something wrong)
6. Next should be the auto reboot that suppose to happen but it didn't. So i took " k_web9000" advice and just pull the battery off (i didn't have any choice its not doing anything... heheh).
6. To boot in Recovery - i followed this :With the device powered down, hold the Volume Down and Power buttons.
7. Next should install the SuperSU.zip file (Please make sure to use chrome since my Safari auto unzip the file and wasted so much of my time troubleshooting... i mean hours retracing my steps ...funny) Just update it and locate the sdcard and look for the .zip file
8. Then it just rebooted after the install and on the boot screen i saw 4 files that where updated.
9. Finally, i checked for the root by downloading root checker and it was verified rooted.
Now you have been noobified
A SYSTEM UPDATE POP-UP 12.1 YOG7DAS2FI Incremental about 48MB BUT DIDNT TOUCH IT, What do i need do? Can i update?
PLEASE LET ME KNOW HOW TO UPDATE TO THE LATEST ONE WITHOUT LOSING MY ROOT.
OR HOW TO INSTALL CYANOGENMOD easy way please . i can see CYANOGEN OS 12.1-YOG4PAS33J on my device
PLEASE HELP. THANKS

You cannot update whilst you are rooted.
If you want to have the latest then CM Nightly is your best option.
How to
https://wiki.cyanogenmod.org/w/Install_CM_for_crackling

How?
mermigas said:
You cannot update whilst you are rooted.
If you want to have the latest then CM Nightly is your best option.
How to
]https://wiki.cyanogenmod.org/w/Install_CM_for_crackling]
Click to expand...
Click to collapse
Thanks for the info and link!! Awesome!
" 4. In ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm a menu selection, but for some devices a physical home key acts as a selector. Some devices have touch enabled ClockworkMod Recovery, in which case you may be able to swipe to, or touch, menu selections.
5. Optional (Recommended): Select backup and restore to create a backup."
In the link you gave, how did they get the clockworkmod recovery? I downloaded & installed it in the google store but it say can not use due to the device not listed. All icons are grayed and i also tried TWRP same issue.
The link also pointed to the nightly build, is there a stable release, doesn't need much update, i can use daily and without the hiccups.
Lastly, if there is no clockworkmod, how do you get it backup as recommended in the link you gave and as quoted above.
Many thanks in advance.

There is only official CM recovery and back up is not possible. Use Titaniumfor back up. You can also use twrp recovery posted in general section. Nightlies are more than stable.

Something is not right...
mermigas said:
You cannot update whilst you are rooted.
If you want to have the latest then CM Nightly is your best option.
How to
https://wiki.cyanogenmod.org/w/Install_CM_for_crackling
Click to expand...
Click to collapse
i was afraid of updating coz my data might be deleted but it seems the OTA update didn't delete my data. My version now is 13.0-20160127-NIGHTLY-crackling but the downside is the google play is not present anymore. i will try install the gapp again.
i don't know if i did it right, some say you need TWRP but it works just fine w/o TWRP in updating via OTA. I also try to install TWRP but i can't get it to work, so i can backup my phone. Last option is what you suggested the titanium backup.
Please let me know if i did right and the gapp if this always going to be installed again. i will be using the same gapp file and report what happen. thanks
Report:
i tried to install gapp file but i didn't use the previous gappfile since the it needs for 6.0 android and i used arm64 but gave error:70 which is the space issue via emulated option. So i go to cyangenmod recovery>apply update> from sdcard1 and "install failed - installation aborted". I can't even see the files on my sdcard. How do you now fix this?
Also can i have the right TWRP file and instruction for Wileyfox Swift PLEASE? thanks

Something went wrong! Please help
I can't to get the gapp to installed.
I wipe everything using the cm recovery and i also was able to install TWRP recovery and it does always hangs when installing the gapp -arm64-aroma (i can choose what to install). I also reinstall 12.1 and 13 but failed again when installing any gapp even in nano version (please note that i wipe everything). in my last attempt i wipe: dalvik, system, cache, data, internal storage & android secure but nothing works to install the gapp. Btw, when i wipe from the 1st time i always get this error "e: unable to find partition size for '/recovery"
PLEASE HELP

I had a few problems doing this from Ubuntu 15.10.
1. ADB did not see the device although it worked fine on my Nexus 4 showing that adb/fastboot were configured correctly. I had to go to /home/.android and create the document 'adb_usb.ini' (right click, new document) which contains the text '0x2970'.
Once this was done I had to run the following commands
adb kill-server
adb start-server
This allowed ADB to see the device but it said that it was offline.
2. I had to create the file /etc/udev/rules.d/51-android.rules (type into terminal 'sudo nano /etc/udev/rules.d/51-android.rules') and paste in the following line, save it (ctrl+x, y, enter).
SUBSYSTEM=="usb", ATTR{idVendor}=="2970", ATTR{idProduct}=="2282", MODE="0666"
sudo service udev restart
After this ADB and fastboot recognized the device and allowed me to follow the directions posted above or on the cyanogenmod wiki.
Hope that is of some use to someone!!!

Also the Cyanogen Recovery was both unpleasant to use and caused problems trying to install GApps, I had to switch to using the unofficial TWRP recovery which worked first time and is a much better interface.

Hey do we need to unlock a bootloader before installing the custom recovery on this device? Thanks.

LG G4: TWRP Recovery not working

Dear folks,
today I ran into a problem while trying to root my new LG G4 (H815).
It seems I succesfully unlocked my bootloader since it writes "BOOTLOADER STATUS: UNLOCKED" at every startup.
Now I tried to install TWRP recovery; I downloaded the newest version for my device from the official TWRP website.
I used the following command:
Code:
fastboot flash recovery twrp.img
I got the following output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (31620 KB)...
OKAY [ 0.923s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 1.226s
Then I left fastboot via
Code:
fastboot reboot
.
But when I try to boot into recovery mode via
Code:
adb reboot recovery
I just get a picture of a broken android figure with a red triangle over its chest.
When I use the hardware key combinations and then answer "YES" it simply does a default factory reset.
I'm using elementaryOS 0.3 (based on Ubuntu Linux). I already tried different ways (with or without sudo, using the adb version which comes with the full Android SDK or the version featured in the Ubuntu repositories).
Nothing seems to work...
I hope I described my problem right and you can help me.
Thanks for all replys and greetings from Germany.
EDIT:
I now got into recovery using
Code:
fastboot boot twrp.img
.
From there I installed stock-20a-rooted.zip. That seemed to work. But when I boot the phone normally it just shows me the LG logo forever and doesn't boot into normal os. Only removing the battery gets it off again. Factory reset doesn't help either.

I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!

DerPedde said:
I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!
Click to expand...
Click to collapse
I did that but now I get a bootloop while starting the normal os. Factory reset doesn't help.

Update: When I connect my device with my PC while the bootloop is active, sometimes a Window pops up on my desktop asking for my PIN to unlock it. When I enter it nothing happens.

Ouch...corrupt twrp.img file?
---------- Post added at 12:49 PM ---------- Previous post was at 12:42 PM ----------
So maybe its best to start all over again...get into download mode via holding volume up and Power on. Then install original kdz via LGUP tool. Maybe you have a look at the german Android Hilfe forum, there are also the kdz files for download. Good luck!

DerPedde said:
Ouch...corrupt twrp.img file?
Click to expand...
Click to collapse
Maybe... While in TWRP it looked like always...
EDIT:
Yes, I'm just downloading the KDZ files... Gonna flash it today. However, Thanks for your support!

I just succesfully installed autoroot kernel, flashing kdz was the solution. However, I still can't write TWRP into recovery partition, but at least I got what I wanted.
Thanks for your support!

you can write twrp by using twrp manager from playstore(2.8.7.0) then when you're IN recovery flash 3.0.0.0 (download from official twrp site or from orginal android development of LG G4) or use in adb fastboot boot (recovery).img

HELP!
DerPedde said:
I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!
Click to expand...
Click to collapse
Hi everybody. I'm a newbie in root, xda and forums in general, so please don't shoot me and help me if you can..
I rooted my lg g4 te first time thanks xda, but after having installed nougat via twrp, root is missing in any check, and twrp can be installed but not launched in fastboot. I tried EVERY guide i found in xda, but that famous command "fastboot boot something.img" is still not working... any idea?
Thanks

Oneplus 3 Boot Loop

So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?

[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1

If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY

anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"

revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.

anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now

Errr... fastboot can unlock the bootloader. fastboot oem unlock

emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.

never ever relock your bootloader while you in custom OS

oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me

revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.

Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.

Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.

emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.

anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works

U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post

^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).

Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.

rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?

revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.

Unable to Install any TWRP Image on my Nokia 6.1 (2018) - Getting Stuck on Splash Screen

Hi Team,
I have an spare Nokia 6.1 (2018) smartphone (Model # - TA -1089)) at my home which I wasn't using since 2-3 years.
Today, I got hands on it, and tried to use it for my development needs.
To begin with, I unlocked its boot-loader using this guide to unlock Nokia 6.1 (2018)
and within "Developer Options", I can see that the "OEM Unlocking" option reads - "Bootloader is already unlocked."
Now, as a next step, I am trying to install TWRP recovery, but nothing seems to be working. No matter which image I try, I get stuck on the TWRP splash screen.
I have tried TWRP Images from the following websites and many more:
TWRP.me
Get Droid Tips - Here when I click on the "Download" option, I get redirected to the "TWRP.me" website only, whose images are not working.
In addition, I have ensured that "ADB and Fastboot" + "Nokia USB Drivers" & other contingencies are properly installed on my system & are not the underlying issue.
I tried running the code
Code:
fastboot flash recovery twrp.img
and my phone got stuck on the TWRP splash screen. Ultimately, I had to use OSA tool and flash the STOCK ROM to get my device working again.
Many websites suggested to simply boot the TWRP and so I used this command:
Code:
fastboot boot twrp.img
in the "Download" mode and then again, nothing happened and I got stuck on the TWRP splash screen.
Note: The only difference between above two commands being - my stock recovery worked fine after executing the 2nd command, and I could boot into my device without much trouble.
Here's my Device Overview:
Device Name - Nokia 6.1
Model & hardware = TA-1089
OS version - Android 10
Security Patch Level - May 1, 2020
Build Number - 00WW_4_15c
Can someone now please suggest where I could be going wrong?
What's my goal:
Root Nokia 6.1 & to be able to install Custom ROM's on Nokia 6.1 and use that device for development purposes
and in case anything goes wrong,
Flash the STOCK ROM again using OSA Tool and bring the device back to its current state.

Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here

And also not fla#h
It is a/b partition so only boot done your goals and boom
Everytime you need to temporarily boot twrp

White_devil_04200 said:
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
Click to expand...
Click to collapse
Hi @White_devil_04200
Thank you for redirecting me to this Telegram channel.
However, let me share that - On the channel, I found "twrp-3.3.1-1-PL2.img" listed as the TWRP image that works.
The conflict is that - I downloaded this version only from multiple sites & after flashing it, got stuck on TWRP splash screen. I had to use OSA tool to reflash Android OS & restore the stock recovery.
And, when I ran the code -
Code:
fastboot boot twrp.img
, then also I got stuck on the splash screen, but was able to reboot into the OS successfully.
Note: Also, I tried switching the slots too (from 'a' to 'b' or vice versa') but then also, nothing worked for me.
I hope you get my problem, and would now assist me accordingly.

this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.

Bảo Dora said:
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Click to expand...
Click to collapse
Thanks @Bảo Dora for sharing your TWRP file and for the instructions.
I was finally able to boot into TWRP (used another file, of course), and then successfully get "root" access on my device.
Also, I read that if you execute the command:
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
you shall permanently install TWRP on your device, which may or may not be the first preference of many users.
Having said that, am glad that it worked out for you. However, I still prefer to use just the "boot" command to avoid changing my stock recovery.
Thanks for your help again.
Cheers,
Manu

For potential readers of this thread, I would like to explain one thing here.
"fastboot flash recovery twrp.img" does NOT change your stock recovery on Nokia 6.1. Because this phone has "A/B system updates" and due to that the recovery RAM disk is now contained in the boot.img file. So Nokia 6.1 has not recovery partition so if you execute the "fastboot flash recovery twrp.img" command it only shows an error message and nothing is changed on your device.
Common issue on Nokia 6.1 is that when you execute only this one command "fastboot boot twrp.img" then it stucks on androidone logo.
But for some special reason, if you execute "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" it successfully boots into TWRP recovery.
Really there is nothing to worry about. This procedure is safe and really works.

White_devil_04200 said:
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
Click to expand...
Click to collapse
And also wipe data with help of fastboot ! Yes it is important if you facing stuck on twrp logo

mAnN14 said:
Thanks @Bảo Dora for sharing your TWRP file and for the instructions.
I was finally able to boot into TWRP (used another file, of course), and then successfully get "root" access on my device.
Also, I read that if you execute the command:
you shall permanently install TWRP on your device, which may or may not be the first preference of many users.
Having said that, am glad that it worked out for you. However, I still prefer to use just the "boot" command to avoid changing my stock recovery.
Thanks for your help again.
Cheers,
Manu
Click to expand...
Click to collapse
Hi,
which file did you use at the end? i have the same problem..

AndreaMariaBono said:
Hi,
which file did you use at the end? i have the same problem..
Click to expand...
Click to collapse
Let me try and find that file link again bro. It's been time I performed the root process, so I will have to search for it.
Will share it with you at the earliest.
Till then, stay calm and be safe.

Bảo Dora said:
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Click to expand...
Click to collapse
I accidentally found a way to permanently install twrp on nokia 6.1..you don't have to temp boot it every time

sayanmitra753 said:
I accidentally found a way to permanently install twrp on nokia 6.1..you don't have to temp boot it every time
Click to expand...
Click to collapse
I don't think it works...

MricCall said:
I don't think it works...
Click to expand...
Click to collapse
Bro it works in real..i am using it on my device

use comand
adb erase userdata
then
adb erase system
adb arase vendor
then fastboot reboot

Hello,
i have nearly the same problem atm.
I successfully unlocked the device.
When i do to 'fastboot boot twrp.img' in 8 of 10 cases it stucks on Android One screen but sometimes it stucks at twrp boot screen.
I have tried multible twrp versions for Nokia 6.1 PL2.
I also tried 'fastboot flash recovery twrp.img' but here comes a adb error that says:
Sending 'recovery' (38592 KB) OKAY [ 1.064s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
On Galaxy S6 this works fine for installing permanently but here i event cant boot into twrb.
Any advices pls?

N0t3xx_A said:
Hello,
i have nearly the same problem atm.
I successfully unlocked the device.
When i do to 'fastboot boot twrp.img' in 8 of 10 cases it stucks on Android One screen but sometimes it stucks at twrp boot screen.
I have tried multible twrp versions for Nokia 6.1 PL2.
I also tried 'fastboot flash recovery twrp.img' but here comes a adb error that says:
Sending 'recovery' (38592 KB) OKAY [ 1.064s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
On Galaxy S6 this works fine for installing permanently but here i event cant boot into twrb.
Any advices pls?
Click to expand...
Click to collapse
"fastboot flash boot recovery.img" and reboot into recover using Vol+ & Power.

Recovering data on a DEAD Redmi Note 8 PRO

Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.

how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.

Thanks for the hint, but I am not happy with the idea of someone playing with my data

1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC

Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.

Any idea? Should I give up?

If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info

Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.

Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.

If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?

So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?

Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons

MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?

You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b

I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.

Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.

Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?

Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.

Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?

Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5