Okay, I admit I'm fairly new to this. There were threads regarding bootloop on Nexus 5 but none of them were quite useful.
Here is what happened:
My Nexus 5 ran the 4.4.4 KitKat stock rom. I wanted to try out the latest CM12 nightly for Nexus 5, and also gain experience of the android system. So, I rooted my phone and installed CWM recovery. Everything was fine and I followed the procedures to install the rom. I wiped out cache, data, dalvik cache. But then, as I flashed the cm12 zip file, it gave me a status 7 error saying that my bootloader version is not the one the zip needs.
Initial bootloader version: hhz11k
Required bootloader version: hhz12d
At this point, I could still use my phone with the factory reset version.
So, I unlocked my bootloader and using fastboot upgraded my bootloader to hhz12d version (I had downloaded the image of this bootloader version). This, I believe, is where my problems started.
After doing so, rebooted my phone and then it got stuck in a bootloop. I looked up various threads on how to get out of the loop but none worked. I couldn't push files into the phone using the adb shell. I discovered that CWM gave the error "E: Can't mount /sdcard". I can't see the internal storage when I connect to PC via USB either.
I tried installing the initial version of the bootloader but that didn't solve anything either. Could anyone give me a decent approach to maybe flash a stock image of Nexus or get my phone out of the bootloop? Thanks for reading this. Help, please?
GavelTrouble said:
Okay, I admit I'm fairly new to this. There were threads regarding bootloop on Nexus 5 but none of them were quite useful.
Here is what happened:
My Nexus 5 ran the 4.4.4 KitKat stock rom. I wanted to try out the latest CM12 nightly for Nexus 5, and also gain experience of the android system. So, I rooted my phone and installed CWM recovery. Everything was fine and I followed the procedures to install the rom. I wiped out cache, data, dalvik cache. But then, as I flashed the cm12 zip file, it gave me a status 7 error saying that my bootloader version is not the one the zip needs.
Initial bootloader version: hhz11k
Required bootloader version: hhz12d
At this point, I could still use my phone with the factory reset version.
So, I unlocked my bootloader and using fastboot upgraded my bootloader to hhz12d version (I had downloaded the image of this bootloader version). This, I believe, is where my problems started.
After doing so, rebooted my phone and then it got stuck in a bootloop. I looked up various threads on how to get out of the loop but none worked. I couldn't push files into the phone using the adb shell. I discovered that CWM gave the error "E: Can't mount /sdcard". I can't see the internal storage when I connect to PC via USB either.
I tried installing the initial version of the bootloader but that didn't solve anything either. Could anyone give me a decent approach to maybe flash a stock image of Nexus or get my phone out of the bootloop? Thanks for reading this. Help, please?
Click to expand...
Click to collapse
You should have upgraded your system to 5.1 using factory images, then flash twrp, then flash cm.
flash the system image.
https://developers.google.com/android/nexus/images
Yes, I saw this as an option. But do I use the Android SDK as mentioned in the webpage or do I use Odin to flash the system image? Thanks.
Is there any proper guide to use any of the above apps for Nexus?
GavelTrouble said:
Yes, I saw this as an option. But do I use the Android SDK as mentioned in the webpage or do I use Odin to flash the system image? Thanks.
Is there any proper guide to use any of the above apps for Nexus?
Click to expand...
Click to collapse
Odin is only for Samsung devices!
Follow this guide: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Somewhat new to this, but I successfully rooted my 6633 which has stock 4.4.4 (Which I re-installed the stock firmware fresh). Afterward I Installed TWRP and attempted to create a custom recovery (I could never boot into recovery and tried many times and many ways), and assume I must at least create a custom recovery. Anyway, in attempting to create the recovery I tried to flash the img file. However, I could not find an image for the 6633 and (stupidly) flashed the image for the z3c. But other than freezing the phone the first time I shut it down, everything on the phone works fine. But a recovery was never created. I then found an img for the 6633 and tried to flash it but simply got an error message saying that "Failed remote: image is not a boot image". Apparently either the original mistakenly loaded (z3c) image won't let me flash another over it (unlikely, since it may have never even loaded) or (more likely) the new correct image is bad or corrupted. It is called "bootZ3dualmonxtest01.img" and was downloaded from another site. Searching this site I did find a kernel for the Z3 6653 but there is not any kernel for the 6633.
Again the phone works fine and I can do some file management things in the root, but the whole reason for doing this rooting process is so I can flash a mod to fix the crappy ringtone volume, that I located in another thread on this forum. It's been a journey & I had a lot of fun learning, but I'm not even sure that, in the end, the mod will even fix the ringtone volume (although posters on that thread claim it works). But that's a whole other issue. (lol). Sorry for the wordiness. I read the forums a lot and tried to be thorough. I know there are a lot of really smart people helping newbies like me. Any help is appreciated.
First of all, you can't flash custom kernels on Locked bootloader (I guess you've never unlocked it)
Second, if you wan't just to flash a zip file with sound mod then after rooting and installing TWRP, boot in TWRP and Install the zip. Thats it. You don't need custom kernel or any other recovery. TWRP is fine enough.
G-FACE said:
First of all, you can't flash custom kernels on Locked bootloader (I guess you've never unlocked it)
Second, if you wan't just to flash a zip file with sound mod then after rooting and installing TWRP, boot in TWRP and Install the zip. Thats it. You don't need custom kernel or any other recovery. TWRP is fine enough.
Click to expand...
Click to collapse
Thanks so much for your reply. However, the Bootloader was unlocked the whole time. In fact, the process did seem to correctly flash the wrong kernel (xperia Z3c). The reason I was trying to create a custom recovery is that I am apparently unable to boot to TWRP. I had read in another forum that the Z3 Dual does not come with a stock recovery and that a custom one has to be installed.
In any case, I followed the instructions to boot to TWRP (which gave a couple of methods), and it continues to just either just boot normally, or it I get an error "Damaged SD Card" and I lose some minor functionality. In that case, the phone won't shut down and I have to hold the power button and up volume to kill it. But then if I power it on, everything is normal. This error sequence only occurs when I try to boot into recovery.
Is it possible that when I flashed the wrong kernel (using the Xperia Z3c kernel) that I created this issue? I assumed that the reason for the error was that there was no stock recovery and one could be created by flashing the kernel image.
There is no stock recovery on Z3.
Here is a custom kernel for D6633, but you need to be on stock 23.0.F.1.74 firmware: http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
You can ask the dev there to prepare for you a custom kernel for another firmware version if you want.
Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible
try these roms.
rocketfans14 said:
Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible
Click to expand...
Click to collapse
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.
Zte blade l said:
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.
Click to expand...
Click to collapse
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.
Not much difference.
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..
rocketfans14 said:
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.
Click to expand...
Click to collapse
it is not necessary to unloack bootloader for tab 2 as it comes with a unlocked bootloader from stock.
Zte blade l said:
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..
Click to expand...
Click to collapse
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?
rocketfans14 said:
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?
Click to expand...
Click to collapse
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...?
Tab 2 has got marshmallow.
Zte blade l said:
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...��
Tab 2 has got marshmallow.
Click to expand...
Click to collapse
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.
billysam said:
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.
Click to expand...
Click to collapse
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..
When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
rocketfans14 said:
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..
Click to expand...
Click to collapse
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.
rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
Did you clear dalvik cache in recovery before flashing rom?
Zte blade l said:
Did you clear dalvik cache in recovery before flashing rom?
Click to expand...
Click to collapse
Yes, I cleared the top four options in recovery, and formatted data before flashing.
billysam said:
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.
Click to expand...
Click to collapse
That's what I did. Let me just briefly summarize what I have done:
used odin with twrp
booted into recovery and made back up
cleared dalvik, cache, system, and data, formatted data
flashed update supersu, booted into system and checked root with root checker
rebooted into recovery, cleared dalvik, cache, system, and data, formatted data again
flashed cm12.1 and gapps, rebooted but ran into bootloop at splash screen
rebooted into recovery and restored back up
So I'm rooted and on stock 4.2.2 currently.
champ1919 said:
When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Click to expand...
Click to collapse
I did.
Try flashing blisspop or slimLP.
Dear folks,
first of all let me thank you for all the good work in here.
I’m quiet used to ADB, fastboot, unlocked bootloaders, TWRP, Custom Roms etc since I've been routing my HTCs for couple years by now.
The other day a friend of mine, owner of a Nokia 3, asked me, if I could possibly “ungoogle” his phone. My idea was it to clean-install LineageOS, since it comes without GApps in first place.
That being said I found some instructions on the internet how to do it – not here at xda though.
I. What I did at first:
I unlocked the bootloader, getting the “orange state”-warning.
I flashed TWRP, removed encryption and installed LineageOS.
Result: Nothing – device wouldn’t boot.
Then I thought I had to relock the bootloader, so that’s what I did and I got the “red state”-error. :angel:
So I ended up flashing original FW with OST. :good:
Ever since that, the bootloader had that “orange state”-warning, no matter what I tried. It is unlocked already. Even flashing the stock boot I found in here gave me that warning. Relocking bootloader fails. But I learned, that “orange state” is still OK. Is that true?
II. What I did next:
I considered if the bootloader is not the problem, maybe recovery is.
So from fastboot I booted TWRP.img, leaving the original recovery untouched, removed encryption and installed LineageOS.
Result: Nothing – device wouldn’t boot.
Since I didn’t really know what the problem was I ended up flashing original FW with OST.
III. What I did next:
I considered that recovery CAN’T be the problem, since it was untouched. Is that true?
So it had to be the bootloader.
I booted original FW, installed Magisk Manager, created a patched boot.
The I booted into TWRP, removed encryption, installed LineageOS, flashed the patched boot.
Result: Nothing - device wouldn’t boot.
Now here it could be the point that my “stock boot” could have been broken in first place already, since it had the “orange state” ever since (see I.) Could this be the problem? If yes, how could I overcome this issue? Flashing the stock boot from xda didn’t help (see also I.) Since I didn’t really know what the problem was I ended up flashing original FW with OST.
IV. What I did next:
I flashed TWRP with SP Flash (Thanks for the wonderful guide @SkaboXD) to keep my locked/untouched/whatever bootloader (again: bootloader here isn’t locked anymore, no chance for me to relock it).
Then I booted into TWRP, removed encryption, installed LineageOS.
Result: Nothing - device wouldn’t boot.
Since I didn’t really know what the problem was I ended up flashing original FW with OST.
Tu sum it up:
I am kind of proud to have reached one and the same goal over many different ways now
But I’ve spent hours of reading through the threads here and trying to find my way and nothing worked. I have never experienced problem like those with my HTCs and could need some serious help now, please.:fingers-crossed:
Q1: Is it even possible install LineageOS on a Nokia 3? That’s what I considered lately.
If yes: How? What am I doing wrong?
If no: What other options do I have to “ungoogle” the device? Root and manually remove all apps? I’m afraid, I won’t find all and that google is hidden somewhere else as well.
Thank you in advance!
wutzkman said:
Dear folks,
first of all let me thank you for all the good work in here.
I’m quiet used to ADB, fastboot, unlocked bootloaders, TWRP, Custom Roms etc since I've been routing my HTCs for couple years by now.
The other day a friend of mine, owner of a Nokia 3, asked me, if I could possibly “ungoogle” his phone. My idea was it to clean-install LineageOS, since it comes without GApps in first place.
That being said I found some instructions on the internet how to do it – not here at xda though.
I. What I did at first:
I unlocked the bootloader, getting the “orange state”-warning.
I flashed TWRP, removed encryption and installed LineageOS.
Result: Nothing – device wouldn’t boot.
Then I thought I had to relock the bootloader, so that’s what I did and I got the “red state”-error. :angel:
So I ended up flashing original FW with OST. :good:
Ever since that, the bootloader had that “orange state”-warning, no matter what I tried. It is unlocked already. Even flashing the stock boot I found in here gave me that warning. Relocking bootloader fails. But I learned, that “orange state” is still OK. Is that true?
II. What I did next:
I considered if the bootloader is not the problem, maybe recovery is.
So from fastboot I booted TWRP.img, leaving the original recovery untouched, removed encryption and installed LineageOS.
Result: Nothing – device wouldn’t boot.
Since I didn’t really know what the problem was I ended up flashing original FW with OST.
III. What I did next:
I considered that recovery CAN’T be the problem, since it was untouched. Is that true?
So it had to be the bootloader.
I booted original FW, installed Magisk Manager, created a patched boot.
The I booted into TWRP, removed encryption, installed LineageOS, flashed the patched boot.
Result: Nothing - device wouldn’t boot.
Now here it could be the point that my “stock boot” could have been broken in first place already, since it had the “orange state” ever since (see I.) Could this be the problem? If yes, how could I overcome this issue? Flashing the stock boot from xda didn’t help (see also I.) Since I didn’t really know what the problem was I ended up flashing original FW with OST.
IV. What I did next:
I flashed TWRP with SP Flash (Thanks for the wonderful guide @SkaboXD) to keep my locked/untouched/whatever bootloader (again: bootloader here isn’t locked anymore, no chance for me to relock it).
Then I booted into TWRP, removed encryption, installed LineageOS.
Result: Nothing - device wouldn’t boot.
Since I didn’t really know what the problem was I ended up flashing original FW with OST.
Tu sum it up:
I am kind of proud to have reached one and the same goal over many different ways now
But I’ve spent hours of reading through the threads here and trying to find my way and nothing worked. I have never experienced problem like those with my HTCs and could need some serious help now, please.:fingers-crossed:
Q1: Is it even possible install LineageOS on a Nokia 3? That’s what I considered lately.
If yes: How? What am I doing wrong?
If no: What other options do I have to “ungoogle” the device? Root and manually remove all apps? I’m afraid, I won’t find all and that google is hidden somewhere else as well.
Thank you in advance!
Click to expand...
Click to collapse
no it's not possible currently, that ROM doesn't work. The only way is to manually remove apps. You have my thread about manually removing apps here: https://forum.xda-developers.com/nokia-3/how-to/guide-how-apps-uninstall-t3804425
he can also remove google keyboard if he don't like it, but first install 2nd keyboard then remove Gboard. Location: /system/app/LatinIME
Google Play Store: /system/priv-app/Phonesky
Google Play Services: /system/priv-app/GmsCore
There are also more Google stuff that i am not sure is it good to remove.
If i find a way to remove Google apps completely i will tell you. When i get Nokia 3 again, I will maybe make stock based ROM with debloated apps, build.prop tweaks (that actually work), volume steps mode (without Xposed and build.prop), advanced reboot option (not sure on this one), Vanced YouTube, odexed and many more...
Stay tuned.
SkaboXD said:
no it's not possible currently, that ROM doesn't work. The only way is to manually remove apps. You have my thread about manually removing apps here: https://forum.xda-developers.com/nokia-3/how-to/guide-how-apps-uninstall-t3804425
he can also remove google keyboard if he don't like it, but first install 2nd keyboard then remove Gboard. Location: /system/app/LatinIME
Google Play Store: /system/priv-app/Phonesky
Google Play Services: /system/priv-app/GmsCore
There are also more Google stuff that i am not sure is it good to remove.
If i find a way to remove Google apps completely i will tell you. When i get Nokia 3 again, I will maybe make stock based ROM with debloated apps, build.prop tweaks (that actually work), volume steps mode (without Xposed and build.prop), advanced reboot option (not sure on this one), Vanced YouTube, odexed and many more...
Stay tuned.
Click to expand...
Click to collapse
Ok, then I wonder, why someone put instructions for the installation on the internet. What's wrong with people nowadays?
Anyways, thank you very much! At least I know, that I can stop my efforts at this point and it wasn't me being stupid :good:
I will stick to your guide. Does it matter, which version I use? 7.1.1? 8.0? 8.1? My plan now is to update to 8.1 since it comes with the highest security patches and then dig through the whole process of ungoogling the device.
Last one so far: Any idea how to get rid of that orange warning in the bootloader? It's not that big of a deal, but if there is a chance to get rid of it I'd be happy.
Your future plans for the Nokia 3 sound pretty awesome. Let me know when you're done - no pressure here.
wutzkman said:
Ok, then I wonder, why someone put instructions for the installation on the internet. What's wrong with people nowadays?
Anyways, thank you very much! At least I know, that I can stop my efforts at this point and it wasn't me being stupid :good:
I will stick to your guide. Does it matter, which version I use? 7.1.1? 8.0? 8.1? My plan now is to update to 8.1 since it comes with the highest security patches and then dig through the whole process of ungoogling the device.
Last one so far: Any idea how to get rid of that orange warning in the bootloader? It's not that big of a deal, but if there is a chance to get rid of it I'd be happy.
Your future plans for the Nokia 3 sound pretty awesome. Let me know when you're done - no pressure here.
Click to expand...
Click to collapse
Yeah, i encountered this too when there was no bootloader unlock guides on xda, all were fake, that's why i first check xda before doing anything.
No it doesn't matter, i used Android 7.1.1 December 2017 Security Patch before i gave it to my brother.
No idea, i think we need to modify some partition like aboot and include some changes but not sure currently.
Tnx for support, i will open a thread where we can discuss about changes you want to see in stock modified rom and advices what else i can do.
SkaboXD said:
no it's not possible currently, that ROM doesn't work. The only way is to manually remove apps. You have my thread about manually removing apps here: https://forum.xda-developers.com/nokia-3/how-to/guide-how-apps-uninstall-t3804425
he can also remove google keyboard if he don't like it, but first install 2nd keyboard then remove Gboard. Location: /system/app/LatinIME
Google Play Store: /system/priv-app/Phonesky
Google Play Services: /system/priv-app/GmsCore
There are also more Google stuff that i am not sure is it good to remove.
If i find a way to remove Google apps completely i will tell you. When i get Nokia 3 again, I will maybe make stock based ROM with debloated apps, build.prop tweaks (that actually work), volume steps mode (without Xposed and build.prop), advanced reboot option (not sure on this one), Vanced YouTube, odexed and many more...
Stay tuned.
Click to expand...
Click to collapse
better Build a rom based on oreo GO coz mt6737 is completely supported
tech2update said:
better Build a rom based on oreo GO coz mt6737 is completely supported
Click to expand...
Click to collapse
not sure if i can, low ram property patch doesn't work when i tested last time, but i will check it again.
SkaboXD said:
Yeah, i encountered this too when there was no bootloader unlock guides on xda, all were fake, that's why i first check xda before doing anything.
No it doesn't matter, i used Android 7.1.1 December 2017 Security Patch before i gave it to my brother.
No idea, i think we need to modify some partition like aboot and include some changes but not sure currently.
Tnx for support, i will open a thread where we can discuss about changes you want to see in stock modified rom and advices what else i can do.
Click to expand...
Click to collapse
Hi @SkaboXD,
to me it seems you have the most knowledge about rooting a Nokia 3 and always give solide answers, so I'd like to ask you directly.
After quite a while now I finally found the delight to spend more time with my friend's Nokia again. I flashed TWRP "successfully" but for whatever reason the phone won't load it. It also doesn't matter which TWRP-version I try. Not even booting directly into TWRP via fastboot boot xxx.img works. Every time I try it starts up stock 8.1. rom.
Any idea why this could be? What should I do? Reflashing the thing with OST again?
I tried that already^^ but when I started my OST-Tool it asked me for some weird login-data? It has never done that before.
Furthermore, once I get over that point, I plan to root it with SU, since I want to have a regular root, not a systemless one. Is there anything special to consider? Or will it be just the regular way
Install/Boot TWRP --> flash SU.zip --> boot device --> boom, you're done?
Sorry for the bother and thank you in advance!
wutzkman said:
Hi @SkaboXD,
to me it seems you have the most knowledge about rooting a Nokia 3 and always give solide answers, so I'd like to ask you directly.
After quite a while now I finally found the delight to spend more time with my friend's Nokia again. I flashed TWRP "successfully" but for whatever reason the phone won't load it. It also doesn't matter which TWRP-version I try. Not even booting directly into TWRP via fastboot boot xxx.img works. Every time I try it starts up stock 8.1. rom.
Any idea why this could be? What should I do? Reflashing the thing with OST again?
I tried that already^^ but when I started my OST-Tool it asked me for some weird login-data? It has never done that before.
Furthermore, once I get over that point, I plan to root it with SU, since I want to have a regular root, not a systemless one. Is there anything special to consider? Or will it be just the regular way
Install/Boot TWRP --> flash SU.zip --> boot device --> boom, you're done?
Sorry for the bother and thank you in advance!
Click to expand...
Click to collapse
hmm, i think that our twrp is not compatible with 8.1 yet, the only method that could work is flashing Magisk (SuperSU won't work, it's depreciated) with my guide but I'm not sure does it work on 8.1, i didn't tested. It would be easier if i have phone, in this moment i can't help much.
SkaboXD said:
hmm, i think that our twrp is not compatible with 8.1 yet, the only method that could work is flashing Magisk (SuperSU won't work, it's depreciated) with my guide but I'm not sure does it work on 8.1, i didn't tested. It would be easier if i have phone, in this moment i can't help much.
Click to expand...
Click to collapse
Ok just in general then: I don't give much about the version to be honest. After I fix my OST, I can reflash to 7.1, that's fine.
My thoughts now: Once I'm back to 7.1, I will boot into TWRP, do the whole magisk-magic with patched bootloader and so on...
I) I only know magisk as a systemless root, meaning I cannot delete unwanted apps for example. Is there any chance to get rid of them anyways?
II) I learned when keeping the original recovery, system OTAs are still possible. Will they destroy root?
If yes, I truly need to root at the latest system version possible. Will 8.0 work with root? Or just 7.1?
wutzkman said:
Ok just in general then: I don't give much about the version to be honest. After I fix my OST, I can reflash to 7.1, that's fine.
My thoughts now: Once I'm back to 7.1, I will boot into TWRP, do the whole magisk-magic with patched bootloader and so on...
I) I only know magisk as a systemless root, meaning I cannot delete unwanted apps for example. Is there any chance to get rid of them anyways?
II) I learned when keeping the original recovery, system OTAs are still possible. Will they destroy root?
If yes, I truly need to root at the latest system version possible. Will 8.0 work with root? Or just 7.1?
Click to expand...
Click to collapse
1.yes you can with systemless root, maybe you got misinformed. In fact i deleted system apps with Magisk.
2.true, 8.0 work with root. OTA will destroy root but you can just flash it again.
wutzkman said:
Hi @SkaboXD,
to me it seems you have the most knowledge about rooting a Nokia 3 and always give solide answers, so I'd like to ask you directly.
After quite a while now I finally found the delight to spend more time with my friend's Nokia again. I flashed TWRP "successfully" but for whatever reason the phone won't load it. It also doesn't matter which TWRP-version I try. Not even booting directly into TWRP via fastboot boot xxx.img works. Every time I try it starts up stock 8.1. rom.
Any idea why this could be? What should I do? Reflashing the thing with OST again?
I tried that already^^ but when I started my OST-Tool it asked me for some weird login-data? It has never done that before.
Furthermore, once I get over that point, I plan to root it with SU, since I want to have a regular root, not a systemless one. Is there anything special to consider? Or will it be just the regular way
Install/Boot TWRP --> flash SU.zip --> boot device --> boom, you're done?
Sorry for the bother and thank you in advance!
Click to expand...
Click to collapse
Yeah, last time I tried booting twrp I had that same problem, device wouldn't enter recovery
fastboot reboot recovery wouldn't work, eventually I flashed the recovery partition and on reboot held down the power and volume down buttons while the phone was plugged to my laptop before it finally entered recovery
redweaver said:
Yeah, last time I tried booting twrp I had that same problem, device wouldn't enter recovery
fastboot reboot recovery wouldn't work, eventually I flashed the recovery partition and on reboot held down the power and volume down buttons while the phone was plugged to my laptop before it finally entered recovery
Click to expand...
Click to collapse
Did you flash recovery with SPFlash? Because I tried to flash it with fastboot, even before I tried to boot into it. Neither one worked out for me.
Which Android version are you at?
wutzkman said:
Did you flash recovery with SPFlash? Because I tried to flash it with fastboot, even before I tried to boot into it. Neither one worked out for me.
Which Android version are you at?
Click to expand...
Click to collapse
No I used fastboot. Oreo 8.1. I think something happens during that orange state message that keeps fastboot from booting into recovery.
One other thing you can try - though it's a long route is:
1. first back up boot and recovery partitions with spflash - very important else your phone might not boot again
2. after backing up the partitions, flash the boot partition either with spflash or fastboot then reboot. You should boot into recovery.
3. The only problem is that you would need to manually patch the boot.img if you want to flash magisk (normally flashing magisk patches the boot partition from recovey) then flash the boot partition with the modified boot.img otherwise your phone won't boot anymore
redweaver said:
No I used fastboot. Oreo 8.1. I think something happens during that orange state message that keeps fastboot from booting into recovery.
One other thing you can try - though it's a long route is:
1. first back up boot and recovery partitions with spflash - very important else your phone might not boot again
2. after backing up the partitions, flash the boot partition either with spflash or fastboot then reboot. You should boot into recovery.
3. The only problem is that you would need to manually patch the boot.img if you want to flash magisk (normally flashing magisk patches the boot partition from recovey) then flash the boot partition with the modified boot.img otherwise your phone won't boot anymore
Click to expand...
Click to collapse
I've wasted quite some time trying root 8.1 with magisk, but no matter what I did, I always ended up with a softbrick. So you got me hooked up here.
Just to make sure. I flashed FW NE1-215H-0-00WW-B02 (I believe) via OST. (Strange sideeffect here: After flashing the whole new FW with OST, the phone already knew my WiFi and already had Magisk installed, both still from my older installations. I wonder why this is and I have not found a way around it yet )
After the flashed with OST I had two system updates via OTA, so right now I am on Oreo 8.1 stock with security updates from Jan05 '19, in other words: the latest FW possible. What next? According to you:
1. I back up boot and recovery. You mean stock boot and stock recovery, right? I believe my boot is not stock anymore, since it already has that orange state warning. Any way around it? Flashing stock 7.1.1 boot didn'T do any better. Anyways, any other chance to back it up without SPFlash? I have no clue how to back up boot and recovery with SPFlash.
2. I need to flash boot? Not recovery? What should I flash boot with? And then I will have to boot into recovery, like TWRP for example? Any suggestions which one to take? Currently I want to use TWRP 3.2.1-0 by SkaboXD (https://mega.nz/#!qIhFkKia!AkUMvQJ0P...hlCNaZfy2gE4vE) And that is the point, that is not working for me. I cannot boot directly into it, nor can I boot it after flashing. What am I doing wrong?
3. I have to patch boot.img manually. But how can I patch it without having Magisk installed?
Thank you for your time!
wutzkman said:
I've wasted quite some time trying root 8.1 with magisk, but no matter what I did, I always ended up with a softbrick. So you got me hooked up here.
Just to make sure. I flashed FW NE1-215H-0-00WW-B02 (I believe) via OST. (Strange sideeffect here: After flashing the whole new FW with OST, the phone already knew my WiFi and already had Magisk installed, both still from my older installations. I wonder why this is and I have not found a way around it yet )
After the flashed with OST I had two system updates via OTA, so right now I am on Oreo 8.1 stock with security updates from Jan05 '19, in other words: the latest FW possible. What next? According to you:
1. I back up boot and recovery. You mean stock boot and stock recovery, right? I believe my boot is not stock anymore, since it already has that orange state warning. Any way around it? Flashing stock 7.1.1 boot didn'T do any better. Anyways, any other chance to back it up without SPFlash? I have no clue how to back up boot and recovery with SPFlash.
2. I need to flash boot? Not recovery? What should I flash boot with? And then I will have to boot into recovery, like TWRP for example? Any suggestions which one to take? Currently I want to use TWRP 3.2.1-0 by SkaboXD (https://mega.nz/#!qIhFkKia!AkUMvQJ0P...hlCNaZfy2gE4vE) And that is the point, that is not working for me. I cannot boot directly into it, nor can I boot it after flashing. What am I doing wrong?
3. I have to patch boot.img manually. But how can I patch it without having Magisk installed?
Thank you for your time!
Click to expand...
Click to collapse
Sorry for the delay in getting back to you.
1. Your boot and recovery are stock since its the system update that installs them
Orange state just means your bootloader had been tampered with, it has nothing to do with whether your boot or recovery images are stock
2. You flash the twrp image. Ideally you should flash recovery partition, but in this case flashing recovery isn't working for you. Basically your phone is refusing to boot into recovery. What this method does is force the phone to boot the twrp image
3. If you're not using magisk or su, may I ask why you want to enter recovery for in the first place?
As an aside I just realised that you can flash boot.img from twrp, so instead of manually patching the boot.img, just flash stock boot and then flash your SU or magisk or whatever it is that you want to flash from recovery
redweaver said:
Sorry for the delay in getting back to you.
1. Your boot and recovery are stock since its the system update that installs them
Orange state just means your bootloader had been tampered with, it has nothing to do with whether your boot or recovery images are stock
2. You flash the twrp image. Ideally you should flash recovery partition, but in this case flashing recovery isn't working for you. Basically your phone is refusing to boot into recovery. What this method does is force the phone to boot the twrp image
3. If you're not using magisk or su, may I ask why you want to enter recovery for in the first place?
As an aside I just realised that you can flash boot.img from twrp, so instead of manually patching the boot.img, just flash stock boot and then flash your SU or magisk or whatever it is that you want to flash from recovery
Click to expand...
Click to collapse
Don't worry too much about it. We all have more important stuff than rooting a Nokia 3 to do.
1. Thank you! I've just learned something new :highfive:
2. I flash TWRP to boot partition? I did not think of that, but from what you say it definitely makes sense. And now I see, why I need a backup of my 8.1 stock boot and recovery. Perhaps, I should find out how to backup with SPFlash by now :fingers-crossed: . Too bad, there is no stable Oreo-FW out there. :angel:
3. I actually want to "ungoogle" the phone and therefore, I indeed want to use magisk. But I need TWRP in some way to install it.
Once I have TWRP at boot partition and loaded it, can I flash boot from there? In other words, can boot partition overwrite itself? I doubt it. How about:
a) I create a patched_boot.img right now manually with Magisk Manager, but without installing magisk zip.
b) I use fastboot to flash TWRP to boot and load into it
c) I install Magisk from there and reboot to fastboot again
c) I use fastboot to flash patched_boot.img and reboot the whole thing.
That could do the trick in theory, couldn't it?
wutzkman said:
Don't worry too much about it. We all have more important stuff than rooting a Nokia 3 to do.
1. Thank you! I've just learned something new :highfive:
2. I flash TWRP to boot partition? I did not think of that, but from what you say it definitely makes sense. And now I see, why I need a backup of my 8.1 stock boot and recovery. Perhaps, I should find out how to backup with SPFlash by now :fingers-crossed: . Too bad, there is no stable Oreo-FW out there. :angel:
3. I actually want to "ungoogle" the phone and therefore, I indeed want to use magisk. But I need TWRP in some way to install it.
Once I have TWRP at boot partition and loaded it, can I flash boot from there? In other words, can boot partition overwrite itself? I doubt it. How about:
a) I create a patched_boot.img right now manually with Magisk Manager, but without installing magisk zip.
b) I use fastboot to flash TWRP to boot and load into it
c) I install Magisk from there and reboot to fastboot again
c) I use fastboot to flash patched_boot.img and reboot the whole thing.
That could do the trick in theory, couldn't it?
Click to expand...
Click to collapse
I figured the flashing to boot partition one time when my phone kept booting into recovery after a failed ota update. I checked the install script and found out that at one point the boot partition is flashed with the recovery image
You definitely need to backup your boot image unless you want to risk not being able to boot your phone anymore
Flashing boot should be possible, after all even when you boot into twrp you can flash another recovery, in fact when you do a twrp restore especially one that has a recovery backup, you usually overwrite even the partition that twrp is installed on. Your method too would work, but I think it's easier to just let magisk do the job, i've had too many failed attempts at patching a boot image
redweaver said:
I figured the flashing to boot partition one time when my phone kept booting into recovery after a failed ota update. I checked the install script and found out that at one point the boot partition is flashed with the recovery image
You definitely need to backup your boot image unless you want to risk not being able to boot your phone anymore
Flashing boot should be possible, after all even when you boot into twrp you can flash another recovery, in fact when you do a twrp restore especially one that has a recovery backup, you usually overwrite even the partition that twrp is installed on. Your method too would work, but I think it's easier to just let magisk do the job, i've had too many failed attempts at patching a boot image
Click to expand...
Click to collapse
I MADE IT! :victory:
As it turned out I stumbled over quite some weird different problems:
a) As mentioned, I was not able to boot into TWRP recovery for whatever reason. So flashing TWRP to boot partition and therefore forcing the device to boot it did the trick. Thank you for this excellent advice!:good:
b) When Magisk tried to patch the boot image automatically, it always came up with a boot image of 0 kb in size. Of course, this could not work at all. So, manually creating a patched_boot.img and flashing it after the installation of magisk turned out to be the way to go.:laugh:
c) For whatever reason fastboot had quite some problems with my the device. It obviously kept producing strange, not reproducible errors. So I arranged myself with SPFlash and was good to go.
So now I have a full system backup for Oreo 8.1 stock and a full system backup for Oreo 8.1 with magisk root.:highfive:
I can work my way through ungoogling the device and whenever I screw up, I can simply recover with my backup
So Thank you @redweaver and also Thank you @SkaboXD for all the help!
So Yeah, The LineageOs Version Which is Based on Android Nougat is Very Near For Its Release! Compiled From Source With Nokia 3 Device Tree, Vendor & Also using Kernel Source!
Does anyone know if this build was ever released?
I am not experienced, so if I hit a wall would be stuck, but can follow directions and would like very much to install Lineage OS on my Nokia 3.