Related
Hello XDA community, I am a 100% new noob who is interested in getting started with rooting. I am going to get right to the point with what I am working with, what I have done, and what I need some help with. May my journey with lovely pictures be a helpful guide for all those who follow me (I find it is easier to understand things with lots of images).
Used this thread to begin my journey on rooting an old Nook HD tablet.
Started with a factory reset but it automatically updated according to my settings page, so one of my question is; does it matter what software version my device is running before I root it?
Followed instructions in PeteInSequim guide and created an 8 GB Micro SD Card with all the files.
Green = CM-12.1_Installation_20150925 Instructions PDF
Light Blue = Files from NookHD-bootable-CWM-6046-for-emmc-BOOTFILES-rev0-(07.13.14)
Red = CyanogenMod 12.1 (No official release on their website)
Orange = ClockworkMod_Recovery (Couldn't find website for other versions)
Yellow = TWRP Recovery (They may have a newer version)
Purple = TK-GAPPS (Which I downloaded the STOCK package, and am not sure if that is compatible)
This is what I have done so far, and would like advise on what I should do before I advance, specifically around the TWRP VS. CWM with relation to the GAPPS packages. In the tutorial (PDF), I believe they use the CWM to install TWRP, I think TWRP is better and is the only of the two who will support my GAPPS package, but would like someone to help clarify so I don't make a permanent mistake. Also, should I use newer versions of anything? Should I even be attempting CM-12.1 if it is not officially supported? I don't want to have to keep making changes and not changing backgrounds or settings... should I go for the more stable CM-11, if so would I have to completely change my process?
Thanks for the help,
Buckaroo9
I'm a bit lazy when it comes to installing incremental releases, so I prefer to do simple "dirty installs". This means re-flashing without wiping the old installation, which can be done in seconds with no consequences.
But a dirty install will probably fail if you have made user-interface changes, even if you try to reverse out those changes before flashing. You can still install revisions any time you wish, but you must do the wipes first. This means you will have to go through the set-up procedure all over again, which takes a lot longer than a dirty install.
CM-12.1 for our Nooks should eventually be offered among the official nightly releases, and hopefully a milestone release now and then. I might consider UI tweaks after installing one of these, then settle down for a long quite period of no more updates.
If a stable CM-12.1 ever happens, we'll all be installing CM-13 by then.
Click to expand...
Click to collapse
PeteInSequim
Could you please explain this concept slightly more to me? How much would I be able to change and what would the consequences be? If I make changes would I always have to do a clean wipe, would that mean I would have to not make changes and constantly wait for updates? This uncertainty is kind of pushing me away from rooting...
Buckaroo9 said:
...
This is what I have done so far, and would like advise on what I should do before I advance, specifically around the TWRP VS. CWM with relation to the GAPPS packages. In the tutorial (PDF), I believe they use the CWM to install TWRP, I think TWRP is better and is the only of the two who will support my GAPPS package, but would like someone to help clarify so I don't make a permanent mistake.
Click to expand...
Click to collapse
The files you got look right, although I'd recommend using the smaller micro or even nano GApps packages as you can always add more apps later on.
Just use CWM to flash TWRP first, then boot to TWRP to wipe /data and flash CWM and GApps.
Also, should I use newer versions of anything? Should I even be attempting CM-12.1 if it is not officially supported? I don't want to have to keep making changes and not changing backgrounds or settings... should I go for the more stable CM-11, if so would I have to completely change my process?
...
Click to expand...
Click to collapse
CM12.1 for the HD/HD+ is not officially supported and, more importantly, is no longer enhanced/maintained (its original developer has recently moved onto CM13). I've been using CM12.1 for about a month now: the apps' performance can be noticeably more snappy but not consistently so, on the downside couple of apps/features that used to work on CM11 no longer work.
If you're looking for a reasonably newer but stable CM version, I'd suggest you try CM11 (either M12 snapshot or one of the recent "nightly" releases).
digixmax said:
Just use CWM to flash TWRP first, then boot to TWRP to wipe /data and flash CWM and GApps.
Click to expand...
Click to collapse
Is there any reason TWRP can't flash itself?
digixmax said:
I'd recommend using the smaller micro or even nano GApps packages as you can always add more apps later on.
Click to expand...
Click to collapse
Is there any downside to using a larger GApps, and if I can always add more, does that mean I can mix and match, are the essentially just packages of Apps that I am side-loading?
digixmax said:
If you're looking for a reasonably newer but stable CM version, I'd suggest you try CM11 (either M12 snapshot or one of the recent "nightly" releases).
Click to expand...
Click to collapse
I am definably leaning towards more stable, but in your opinion, what features would I loose from CM12 (Android 5.0 Lollipop)? Someone made a good point that, the most advanced, newest, and coolest software will always be unstable. You have to trade off the cutting edge for reliability and support.
As a new member to rooting, I think I may start with more stable things, and then work my way up.
Buckaroo9 said:
Is there any reason TWRP can't flash itself?
Click to expand...
Click to collapse
The TWRP flashable zip file you have contains a TWRP image that is compiled for internal EMMC. Once installed, it can be used to flash CM, GApps, or another version of CWM or TWRP to replace itself.
To flash from SD you need to find and use a TWRP recovery image that is compiled for SD.
Is there any downside to using a larger GApps, and if I can always add more, does that mean I can mix and match, are the essentially just packages of Apps that I am side-loading?
Click to expand...
Click to collapse
You can use a Zip archive program like 7-zip to open up and browse the content of these GApps zip packages to see and compare their particular mixes of apps.
I am definably leaning towards more stable, but in your opinion, what features would I loose from CM12 (Android 5.0 Lollipop)?
Click to expand...
Click to collapse
This depends on your particular use and choice of apps for the tablet, but as examples, the Hulu app and USB Host feature which work on CM11 don't work on CM12.1.
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about 14GB from flashing ROMS and such.Everything seems to have gone smoothly however when I try the oem unlock command I am told that the device is already unlocked.I proceeded to root and then I tried to flash TWRP but I get permission denied.
Also,my Play Store just crashed when I try and type in an app to search for.
The question is-how do I know which factory image is right for my device?
There are a number of 5.1.1 images,I selected the one marked for all carriers except T-Mobile.Could I have selected the wrong image to be causing some of these problems?
Or should I just go ahead and jump up to 6.0.1-there is only 1 image for that release.
I would't think the image mattered that much but something is wrong here.
I got the phone last week from the Amazon sale and I activated it no problem on Verizon and flashed several ROMS no issue.
Advice is much appreciated.
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
dahawthorne said:
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
Click to expand...
Click to collapse
Thanks for the detailed response. I was running 5.1 initially because that is what the phone booted with and I like full-featured ROMS like BlissPop. I guess I'll give 6.0.1 a whirl.It just seemed like it was too new to be rock solid. I had as many features on my old S3 running 4.4.2 as I have seen since then if not more actually. I am curious about Google Now On Tap however.
Hopefully this gets me fixed up.Cheers.
chiadrum said:
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about .......
Click to expand...
Click to collapse
It is possible that the issue is caused because you downgraded the bootloader by flashing 5.1.1.
Flash the complete latest stock 6.0.1 images.
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig. I am guessing that is normal?
The 5.1.1 started working fine after an update all but I still couldn't install TWRP fyi.
Let's see how Marshmallow tastes!
The "does not contain boot.sig and recovery.sig" is standard. I have no idea why it continues to appear version after version, but it has no effect on the installation.
chiadrum said:
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig.
Click to expand...
Click to collapse
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
NLBeev said:
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
Click to expand...
Click to collapse
Thanks guys.
chiadrum said:
Thanks guys.
Click to expand...
Click to collapse
Ok more strangeness.pPhone is working fine,no issues.However I am unable to unlock bootloader using the fastboot OEM unlock command.
The message is "Not supported command in current status".
Yes,OEM unlock is allowed in Dev Options.I tried turning that off in case the indicator was faulty and then I couldn't even attempt to unlock,immediate failure.
Tried this several times after reboots as well.
Build MMB29K.
Any ideas?
Would it be too simple an answer to say that it's because the phone is already unlocked? You couldn't install a new ROM with a locked bootloader.
I myself have been a bit surprised by the peremptory & derogatory comments of some of the very senior members in these forums when people ask what seem to be questions with obvious answers, and I'm beginning to see their point...
Still, I also recognise that an "easy" question is one that you know the answer to, and I don't want to put people off asking questions. Being knocked back myself several times hasn't stopped me asking.
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
chiadrum said:
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
Click to expand...
Click to collapse
Confirmed I am an idiot.Device is unlocked already. Wasn't expecting that.The people way smarter than me who prepared that image took care of it for me.
Not an idiot at all. Like I said, an easy question is one that you know the answer to. Experience counts...
It's not the image that is unlocked - it's the device. Once unlocked, you have to specifically lock it again, but it's neither simple nor a good idea. An unlocked device gives you a far better chance to recover from errors.
I've got this new OnePlus 3t A3003. I'm happy with the performance battery and everything but there's this one issue that troubles me. I got the device unlocked bootloader and flashed aospa. Everything was nice and smooth then I flashed SuperSU later. The phone got reset and wiped except for the internal storage. I didn't know what to do and I just left it. Then later I came across some audio mods and tried flashing it again the same thing happened. So I tested and came to the conclusion that flashing anything wipes device. Why does this happen?
What versions TWRP and SuperSU? Just a guess, but maybe an older version with some compatibility issue? Try another version TWRP?
Otherwise, what version firmware? I don't know if AOSPA updates firmware (as some ROMs do). Maybe try to update OOS to current version 4.1.6 and start with fresh firmware, and install current version TWRP again, etc.
My phone is encrypted so what happens is I flashed something then the phone boots and asks for the password to unlock first then after entering it resets. I didn't know why I even switched roms rn using resurrection remix 7.1.2 latest version and still same problem.So im pretty sure the problem isn't with the rom. Twrp is latest version afaik and with rr rom magisk comes so I'm on v12 of magisk. I'll try using another version of twrp and oos.
redpoint73 said:
What versions TWRP and SuperSU? Just a guess, but maybe an older version with some compatibility issue? Try another version TWRP?
Otherwise, what version firmware? I don't know if AOSPA updates firmware (as some ROMs do). Maybe try to update OOS to current version 4.1.6 and start with fresh firmware, and install current version TWRP again, etc.
Click to expand...
Click to collapse
Thanks mate, there was something wrong with the twrp version I had. I flashed the latest version of twrp 3.1.1 I think and that seemed to solve the issue.
The other problem i have is when i try to flash bluesparks twrp and go to recovery the sceen is blank and only the led glows but i can flash the officaial twrp and flash roms but they come with error 7 and when i flash a oxygen os it gets stuck in updating system image
ak_bagade said:
but i can flash the officaial twrp and flash roms but they come with error 7 and when i flash a oxygen os it gets stuck in updating system image
Click to expand...
Click to collapse
Error 7 often means you are trying to flash an Oreo ROM with an older version TWRP which does not support Oreo.
But we can't tell from the info provided by you. Always give version numbers and other details for TWRP (and blu_spark TWRP) you are having trouble with, as well as the ROMs you are trying.
Also, make sure you are using the right TWRP and ROMs for 3 versus 3T (another reason for Error 7).
redpoint73 said:
Error 7 often means you are trying to flash an Oreo ROM with an older version TWRP which does not support Oreo.
But we can't tell from the info provided by you. Always give version numbers and other details for TWRP (and blu_spark TWRP) you are having trouble with, as well as the ROMs you are trying.
Also, make sure you are using the right TWRP and ROMs for 3 versus 3T (another reason for Error 7).
Click to expand...
Click to collapse
its the latest bluesparks
ak_bagade said:
its the latest bluesparks
Click to expand...
Click to collapse
I said: always give a version number. "latest bluesparks" isn't a version number. I can't count how many times I've seen folks claim they flashed the "latest" recovery. And when prompted for more info, we find out that they aren't even close, sometimes flashing a version TWRP from 2 years ago or older! Not saying this is necessarily your case. But we don't know for certain, if you don't give us precise and accurate info to work with.
You also said you flashed official TWRP. What version number exactly?
You also need to tell us what custom ROMs (and versions) you tried to flash. And what version OOS did you try to flash?
Some friendly advice, try to take more than 5 seconds to type a response to questions we ask you. Provide as much detail as possible, and answer all the quesions. For that matter, when asking for help, posting 2 or 3 (poorly typed) sentences is rarely enough info to go on. Again, provide as much detail and specific info as possible.
this is mostly an outdated firmware issue, Always make sure you have the latest firmware for your device
Firmware 4.5.1/nougat/3T
Firmware 4.5.0/nougat/3
or you can try the Oreo ones
(Stable)
Firmware 5.0.0/Oreo/3T
Firmware 5.0.0/Oreo/3
(Open Beta)
Firmware OB20/Oreo/3T
Firmware OB29/Oreo/3
OP3T firmware thread https://forum.xda-developers.com/oneplus-3t/how-to/firmware-modem-collection-flashable-zips-t3565535
OP3 firmware thread https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
redpoint73 said:
I said: always give a version number. "latest bluesparks" isn't a version number. I can't count how many times I've seen folks claim they flashed the "latest" recovery. And when prompted for more info, we find out that they aren't even close, sometimes flashing a version TWRP from 2 years ago or older! Not saying this is necessarily your case. But we don't know for certain, if you don't give us precise and accurate info to work with.
You also said you flashed official TWRP. What version number exactly?
You also need to tell us what custom ROMs (and versions) you tried to flash. And what version OOS did you try to flash?
Some friendly advice, try to take more than 5 seconds to type a response to questions we ask you. Provide as much detail as possible, and answer all the quesions. For that matter, when asking for help, posting 2 or 3 (poorly typed) sentences is rarely enough info to go on. Again, provide as much detail and specific info as possible.
Click to expand...
Click to collapse
the bluesparks twrp which i flashed is 8.61 op-3t
and the official twrp which works is 3.2.1-0
so when i use the official twrp i have to remove the "assert" from the updater script and flash the rom or else i get the error 7
Something which has come up recently is that my homebutton/fingerprint sensor does not work (its like it doesnt exist) when i flash any rom from android 7-8.1.
So i came to stock by relocked the bootloader by the way like it happens when you hardbrick your device. now im in marshmallow.
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
The other funny thing is that when i called oneplus to help me with flashing the latest software there method helps me to get the bluesparks twrp but since i keep flashing i lose the twrp so thats the only way i can bliuesparks twrp
ak_bagade said:
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
Click to expand...
Click to collapse
Doesn't work like that, the home button, fp sensor "files" are not in TWRP, or managed by FW in any way. All of these are in the /system folder of the ROM that is installed. Which is why they don't work in TWRP.
Have you been on MM since you got this phone? If so, your firmware is heavily outdated, and that's why you end up with the White LED of Death. Try flashing the latest Open Beta over stock recovery. Make sure to unlock your bootloader first. Then flash any variant of TWRP you want, and then see if you still get the White LED of Death.
ak_bagade said:
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
Click to expand...
Click to collapse
You shouldn't be locking the bootloader if you are flashing custom recovery and custom ROMs, and you don't need a locked bootloader to flash official updates either. Really, there is no reason to lock the bootloader unless you are worried about security concerns; want a "full stock" conditions, etc. And for most xda users, an unlocked bootloader is going to be the highly preferable condition. Further, locking the bootloader requires be full stock (including stock recovery, not TWRP). And trying to lock the bootloader under any other condition, is asking for trouble.
I agree with the recommendation above, to flash the full zip of the Open Beta or official OOS update, which will put you on a fully "stock" baseline including firmware. Then go from there.
---------- Post added at 09:19 AM ---------- Previous post was at 09:07 AM ----------
ak_bagade said:
The other funny thing is that when i called oneplus to help me with flashing the latest software there method helps me to get the bluesparks twrp but since i keep flashing i lose the twrp so thats the only way i can bliuesparks twrp
Click to expand...
Click to collapse
If flashing the official zips with TWRP (including blu_sparks), you will always lose TWRP (overwritten with stock recovery) if you reboot after flashing the update. You can prevent this by flashing root (SuperSU, Magisk) or a custom kernel before rebooting (after the update).
Hi, im currently on xiaomi.eu beta 20.1.2. From what I learnt the firmware is updated to 20.1.2. If I want to flash Pixel Experience, which recommends 9.11.7 or higher. Should i downgrade my firmware? I heard downgrading will brick the device.
No ARB, isn't enforced by Xiaomi...not yet.
Make a local backup and save it to your desktop so when you come back to Xiaomi.EU you can restore much faster.
Instructions here: https://xiaomi.eu/community/threads...om-restored-in-eu-rom-after.52880/post-510238
As far as the firmware, you can try a simple factory reset and try flashing, it may work since 9.17 is probably just the minimum firmware needed. But I am not sure because I haven't used that Rom recently. On the other hand, I can tell you that I tried some other roms recently out of boredom and for me they do not yet equal the current Xiaomi.EU in overall stability.
tsongming said:
No ARB, isn't enforced by Xiaomi...not yet.
Make a local backup and save it to your desktop so when you come back to Xiaomi.EU you can restore much faster.
As far as the firmware, you can try a simple factory reset and try flashing, it may work since 9.17 is probably just the minimum firmware needed. But I am not sure because I haven't used that Rom recently. On the other hand, I can tell you that I tried some other roms recently out of boredom and for me they do not yet equal the current Xiaomi.EU in overall stability.
Click to expand...
Click to collapse
thank you very much for the swift reply! Yeah because some roms have firmwares built to them at a older version, i dont know whether flashing them will brick the phone or not. I'm just itching to try out the other roms at this state. I went from global stable to pe and many roms then ended up with EU. But as time goes by, needed to check out them at present state
steveeekong said:
thank you very much for the swift reply! Yeah because some roms have firmwares built to them at a older version, i dont know whether flashing them will brick the phone or not. I'm just itching to try out the other roms at this state. I went from global stable to pe and many roms then ended up with EU. But as time goes by, needed to check out them at present state
Click to expand...
Click to collapse
Just be sure to get a full TWRP backup. I recommended the version on my Persist thread. if you have the full backup you will never need to worry.
Also, I certainly understand wanting to see what else it is out there. Unfortunately, many roms do not provide good how to install instructions. As long as you use the recommended firmware along with DM Verity if needed, you should not have any issues, and bricking your phone is very unlikely.
Before attempting to install any rom read the OP and the last few pages at the end of the post.