Betas, DP, etc. sometimes have more updated modem, kernel and bootloader.
Would it worth to flash bootloader?
AFAIK, it provides no benefit for you while being booted into the OS.
Related
I'm on the latest official OTA of 4.2.1
Do I need to unlock the bootloader to root?
I read this http://forum.xda-developers.com/showthread.php?t=2187982
and I'm still not sure whats happening... Do I need to downgrade to root, and do I need to unlock the bootloader to flash TWRP?
I know a bit of what I'm doing as I have rooted and flashed roms on an htc desire and a samsung s2x (t989).
On 4.2.1 theres the occasional hiccup and freezes when I use chrome... Is this still an issue in the custom roms? Also my Settings app crashes when I try to load the "Running" tab in the apps section of settings lol
Can someone point me in the right direct?
Chris9446 said:
I'm on the latest official OTA of 4.2.1
Do I need to unlock the bootloader to root?
Click to expand...
Click to collapse
Well, you have two basic options:
Get root without unlocking.
That is good, if you want to stick with stock ROM, but want to run Apps that need root access.
Or if you don't want to unlock for any reason.
More details in this thread: [JB ROOT] motochopper works! (Root JB 4.1.1 & 4.2.1 with locked bootloader!)
Unlock and install the patched TWRP for -4.2.
This will allow you to root stock ROM easily or you can install custom ROMs.
Be careful: You have the boot loader 4.2, which means you need to pick the patched TWRP for that boot loader and you need to pick one of the ROMs supporting the 4.2 boot loader.
People have bricked their TF300Ts not using the patched TWRP -4.2 version.
There are currently only two ROMs available, but more should be coming soon, as Asus has finally released the new kernel source code.
If your preferred custom ROM supports only the 4.1 boot loader, you need to downgrade. Or just wait a little, as you like...
I read this http://forum.xda-developers.com/showthread.php?t=2187982
and I'm still not sure whats happening... Do I need to downgrade to root, and do I need to unlock the bootloader to flash TWRP?
Click to expand...
Click to collapse
No and yes.
You can use the tool from the tread above just get root; no downgrading, no unlocking.
But yes, if you want to install TWRP, you need to unlock your device first.
You only need to downgrade for installing a custom ROM that does not (yet) support the 4.2 boot loader.
On 4.2.1 theres the occasional hiccup and freezes when I use chrome... Is this still an issue in the custom roms? Also my Settings app crashes when I try to load the "Running" tab in the apps section of settings lol
Click to expand...
Click to collapse
I have not used stock ROM for a while, but generally people report that most custom ROMs run much smoother than stock Asus ROM:
I would suggest downgrading ti the 4.1.1 bootloader, as there is a much larger variety or ROMS available.
f69m said:
Well, you have two basic options:
Get root without unlocking.
That is good, if you want to stick with stock ROM, but want to run Apps that need root access.
Or if you don't want to unlock for any reason.
More details in this thread: [JB ROOT] motochopper works! (Root JB 4.1.1 & 4.2.1 with locked bootloader!)
Unlock and install the patched TWRP for -4.2.
This will allow you to root stock ROM easily or you can install custom ROMs.
Be careful: You have the boot loader 4.2, which means you need to pick the patched TWRP for that boot loader and you need to pick one of the ROMs supporting the 4.2 boot loader.
People have bricked their TF300Ts not using the patched TWRP -4.2 version.
There are currently only two ROMs available, but more should be coming soon, as Asus has finally released the new kernel source code.
If your preferred custom ROM supports only the 4.1 boot loader, you need to downgrade. Or just wait a little, as you like...
No and yes.
You can use the tool from the tread above just get root; no downgrading, no unlocking.
But yes, if you want to install TWRP, you need to unlock your device first.
You only need to downgrade for installing a custom ROM that does not (yet) support the 4.2 boot loader.
I have not used stock ROM for a while, but generally people report that most custom ROMs run much smoother than stock Asus ROM:
Click to expand...
Click to collapse
Thanks was a lot of great information! I rooted my pad and did a few speed optimization things such as re-trimming and now its much smoother! Maybe I'll try a custom rom later but as for now, I'm happy with the updates that Asus provides
cmendonc2 said:
I would suggest downgrading ti the 4.1.1 bootloader, as there is a much larger variety or ROMS available.
Click to expand...
Click to collapse
I'll keep that in mind but I believe there should be more soon as f69m, stated that asus release the kernel for 4.2
I signed that petition in your signature as well
I'd say go for the 'full experience'. Having an unlocked device also allows you to reflash ROMs at will and can also help in a pinch when it comes to backups/restores. Also, if you happen to lose root, it's easily re-rootable through the bootloader.
I'd just be careful of the current TWRP 4.2.1 recovery blob. I just flashed the one released this morning and I am currently getting this weird double screen thing. Best bet is to sit tight at the moment; an update should be out shortly.
danjng said:
I'd just be careful of the current TWRP 4.2.1 recovery blob. I just flashed the one released this morning and I am currently getting this weird double screen thing. Best bet is to sit tight at the moment; an update should be out shortly.
Click to expand...
Click to collapse
Well, stay away from the TWRP 2.5.0.0-4.2 provided in some thread today, but TWRP 2.4.4.0-4.2 should still be working fine.
Sent from my TF300T using Tapatalk HD
Since we have gotten no updates or way of OEM unlocking, wouldn't it be possible to request SONY for the Linux Kernel source (spirit of the GNU GPL) of this handset and build a ROM using it just to get past the bootloader?
I am thinking about this in terms of the Amazon Fire tablet that is bootloader locked but somehow got a working CM 12 (or was it 13... can't remember).
ROM is different from kernel, you don't build ROMs from kernels.... and you won't be able to flash a custom kernel without an unlocked bootloader unfortunately.
if its oem locked, what about to flash global rom for ur phone and then proceed from there? as far as i know global roms are not lockedd so strictly
Hi.
I'm right now on TS CM 13.1 and I want to try the RR. But I didn't unlock the bootloader officially, so I need to do it properly now so I won't end with an locked bootloader.
While I'm waiting for the approval... can I just flash the latest China dev ROM with my current recovery? Or should I flash it from fastboot?
Thank you.
Since you have a custom recovery, try Xiaomi.eu or miGlobe, though be careful as I think latest versions (Android 7) will lock the bootloader. To be safe, I'd flash an older version with Android 5.1 for now.
You can't try RR 5.8.1 based on Android 7.1 as it requires lollipop bootloader.
Or you can flash 6.12.22 and then update to any Nougat Miui Rom available on Xiaomi.eu. This is done via Updater app.
Sent from my Mi-4c using Tapatalk
I didn't realise there was a previous RR version with lollipop bootloader.
I already got the SMS with the approval from Xiaomi. I though it would take long. So, if get that right, I should first flash an older Android 5.1.1 Dev ROM and than update it with the Updater app to the latest version with 7.1 . This will lock the bootloader and than I can unlock it officially.
If I do it from from fastboot I can flash directly the latest 7.1 dev ROM, right?
Thank you guys. I always messed around with ROM's with my old GNex, but this Miui stuff confuses me a bit.
No need. Just go in TWRP and see the RR N thread there is a link to nougat blobs. Install that and then install newer TWRP that works with nougat (see android development). I think at this point you'd have to unlock bootloader. Then install room normally
But, as I read in the RR N thread, after I flash those blobs I'll end up with a locked bootloader if I previously unlocked it unofficially. As I did.
And, at least I think, I can only unlock it again from an official ROM. That's why I want to flash Miui.
X-static said:
But, as I read in the RR N thread, after I flash those blobs I'll end up with a locked bootloader if I previously unlocked it unofficially. As I did.
And, at least I think, I can only unlock it again from an official ROM. That's why I want to flash Miui.
Click to expand...
Click to collapse
Whether you have unlocked your device officially or not, it will still lock your bootloader. The key here is if you have the permission to unlock it. If not, then don't proceed. You can officially unlock your bootloader after 5 business days upon receiving the SMS.
Ok. I do have the permission. And can I unlock the bootloader right away with mi flash unlock on a custom ROM or do I need the official miui ROM?
Worked for me with no OS, so I assume you do not need miui.
X-static said:
Ok. I do have the permission. And can I unlock the bootloader right away with mi flash unlock on a custom ROM or do I need the official miui ROM?
Click to expand...
Click to collapse
After you flash the blobs, the bootloader will be locked. Unlock it via Mi Flash. Then flash a Nougat compatible TWRP and you're good to go in flashing Nougat RR.
I've looked all through the forums and haven't found a clear tutorial on how to do this, if it can even be done.
I have a Verizon bought, bootloader unlocked, Magisk rooted Pixel 2 with TWRP and a custom kernel (Flash 2.06) installed running 8.1.0 with the December security patch.
How would I go about updating to future monthly patches (e.g. January's)?
I'd prefer to not lose all data (i.e. OTA-like), but am willing to start clean. Definitely do not want to risk losing the unlocked bootloader.
Is it possible? Willing to try if there is a semi-reasonable assurance of success.
Thanks.
If you're familiar with fastboot you can pull out the image.zip from the factory image and fastboot it with the command
Code:
fastboot update whateverthelongassimagename.zip
Leaving out the -w in that command won't wipe anything. If not, you'll have to get the stock boot image and take the OTA. Either way you'll have to temp flash TWRP again, installer to keep it there and your kernel and Magisk.
When we get an update that requires a new bootloader, that will have to be via OTA or adb sideload. VZW seems to have blocked us from fastbooting that.
JRJ442 said:
When we get an update that requires a new bootloader, that will have to be via OTA or adb sideload. VZW seems to have blocked us from fastbooting that.
Click to expand...
Click to collapse
I'm guessing on Verizon you wouldn't want to update the bootloader anyways since that would likely fix the current method of unlocking those phones.
clcdev said:
I'm guessing on Verizon you wouldn't want to update the bootloader anyways since that would likely fix the current method of unlocking those phones.
Click to expand...
Click to collapse
They most likely will patch the unlock yes, but they're not going to send an update that will relock the bootloaders that have been unlocked. So I wouldn't see an issue with updating it. Unless for some reason you need to lock it back. The bootloader in this months security update is still the same as last months. Version number is the same.
Hello.
I have a bootloader locked Pixel 7 Pro with the April 2023 stock build.
I would like to downgrade to the October or November 2022 build.
Is there any way I can accomplish this?.
Thank you.
EDIT: Got an OTA build, but recovery is saying downgrades are not allowed.
Any other way?
Unless you unlock the bootloader, you cannot downgrade using an OTA. How you tried to flash the full firmware? Why are you trying to downgrade to a firmware that far behind anyways?
schmeggy929 said:
Unless you unlock the bootloader, you cannot downgrade using an OTA. How you tried to flash the full firmware? Why are you trying to downgrade to a firmware that far behind anyways?
Click to expand...
Click to collapse
Reason, because on Pixel 7 and 7 Pro, firmwares from October and November, deleting an app, you can carrier unlock them, so I am trying to do that. I did it already with a 7 Pro which had the October firmware, obviously, if there is a reset on the phone, it gets locked again, but at least it's something.
I tried using the flashme.bat script, PixelFlasher, used OTA and Full firmwares, Fastboot and Recovery, nothing.
You cannot downgrade to a lower security patch without wiping data. Unlocked bootloader has the same behaviour.
Lossyx said:
You cannot downgrade to a lower security patch without wiping data. Unlocked bootloader has the same behaviour.
Click to expand...
Click to collapse
The phone is clean, so no data on it.
SirRhor said:
The phone is clean, so no data on it.
Click to expand...
Click to collapse
Oh my bad. Then I am not so sure ,sorry. This is my first Pixel.