Hello! I have an unlocked bootloader on my Z3 and am currently on 5.0.2 (.28) Lollipop. I rooted it with Kingo Root. I am on the step where i am trying to flash a recovery. I have tried manually to flash a twrp.img via fastboot, via NUT's automatic installer, and both don't seem to work. Although they push the files on the phone and say success, I cannot boot into recovery, it flashes red for 2 seconds and skips to OS. I tried also downgrading to 4.4, but giefroot fails to work for some reason. What am I doing wrong?
flash FOTA recovery!
Related
Has anyway found a way to Root the OnePlus One without having to flash a custom recovery with the new 33R OTA?
(yes I didn't check the CM recovery)
*But after I updated to the 33R update I still had root access intact, despite gaining root by boot and not having unlocked the bootloader under 33R. The problem was I did a factory reset and obviously it reflashed the newer bootloader and I lost root access (yes stupid)
This can no longer be done 'fastboot boot twrpimgname.img' with the 33R update ;
Aren't One Plus all about give you the power so why did they go ahead and block boot custom recovery that worked before ??
This is the under 33R OTA =
C:\adb>adb reboot bootloader
C:\adb>fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
downloading 'openrecovery-twrp-2.7.1.1-bacon.img'...
OKAY [ 0.402s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.404s
Seems the have patched being able to boot a custom recovery without unlocking the boot loader
Yes I realized the the 'Update CM recovery' option but not after I updated to 33R (my oneplus was rooted without having to unlock the boot loader)
I did do a Nandriod backup of course before the 33R OTA.
The nandriod backup is rooted without having to unlock the bootloader via this ' fastboot boot twrpimgname.img '
Is their no way yet to boot a custom recovery without unlocking the boot loader ? Does one have to wait for a update twrp recovery to boot not flash ?
The question is: WHY?
the locked bootloader is locked because it allows only booting a signed recovery, if you use a custom-unsigned-by-manufacturer recovery there is no sense in keeping the bootloader locked.....
OnePlus knows that 90% of the users are rooting and unlocking, so there is no sense to keep it unlocked.... in case of necessity, you can relock the bootloader !!!
Anyway, you wrote in the wrong section !!!
mcbyte_it said:
The question is: WHY?
the locked bootloader is locked because it allows only booting a signed recovery, if you use a custom-unsigned-by-manufacturer recovery there is no sense in keeping the bootloader locked.....
OnePlus knows that 90% of the users are rooting and unlocking, so there is no sense to keep it unlocked.... in case of necessity, you can relock the bootloader !!!
Anyway, you wrote in the wrong section !!!
Click to expand...
Click to collapse
What area is the right one, my bad.
Also asking if their is a way around the 33R to boot custom recovery
Why though?? You don't need to boot to a custom recovery. Just unlock the bootloader, it doesn't void your warranty. You have absolutely nothing to lose by doing it, and absolutely nothing to gain by leaving it locked.
Transmitted via Bacon
timmaaa said:
Why though?? You don't need to boot to a custom recovery. Just unlock the bootloader, it doesn't void your warranty. You have absolutely nothing to lose by doing it, and absolutely nothing to gain by leaving it locked.
Transmitted via Bacon
Click to expand...
Click to collapse
Just an innocent wipe... and he only wants root.
Yeah and the right way to get root is to unlock your bootloader, install TWRP, and flash SuperSU.
Back stuff up, unlock bootloader, restore stuff. It's stupid to try to 'hack' into the world's easiest phone to root.
Transmitted via Bacon
go back to 25R an root it
then untick the update recovery in develop settings
install recovery twrp
now remember to have the update recovery
install the 33R
with twrp an in the end choose fix permissions
now u can download from phone it will come up to fully root
just hit fully root an install with twrp
it will download root
an restart in recovery wait fore it to finnish an u are now rooted on 33R
Have you tried towelroot? https://towelroot.com/
-fluffy- said:
go back to 25R an root it
then untick the update recovery in develop settings
install recovery twrp
now remember to have the update recovery
install the 33R
with twrp an in the end choose fix permissions
now u can download from phone it will come up to fully root
just hit fully root an install with twrp
it will download root
an restart in recovery wait fore it to finnish an u are now rooted on 33R
Click to expand...
Click to collapse
How's he meant to go back without an unlocked bootloader??
Transmitted via Bacon
Whilst upgrading to Oxygen OS, I ran into an issue (wiped all partitions however ADB Sideload did not work so I got stuck with no OS). In an attempt to completely wipe the phone, I tried to lock and relock the bootloader, forgetting that the phone required to be booted up in order to unlock the bootloader. So now, I am stuck with no OS and with a locked bootloader (so I am unable to flash the factory image). I am also unable to unlock the bootloader as I cannot boot the phone. I still have access to TWRP, however upon pushing a rom onto the memory, it failed to flash. I am assuming this is due to the locked bootloader, however I am not sure.
If anyone has any ideas on how I can fix the phone, I would greatly appreciate it.
Thanks!
This is what you need:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
You flash that from TWRP and it'll unlock your bootloader again.
Transmitted via Bacon
I’m currently using NRT 2.1.4 and i’ve tried rooting my device a few times now and it never installs SuperSU and I can’t boot into TWRP as it shows the android laying down w/ the red exclamation, which is odd since it does go into TWRP during the process of rooting...
But I do not have TWRP installed because of the NRT process
Steps I have taken:
Unlock Bootloader
Flash stock + Unroot (Latest version MMB29Q)
Root & Custom Recovery
When I do the root step, it boots into bootloader, goes in a temporary twrp, then launches normally and says to update SuperSU binaries and check busybox, but neither SuperSU or busybox get added into my app list
It also sometimes says ADB recovery device not found on some attempts..
Is there any way for me to root my Nexus 5?
I have repeatedly flashed the stock with the newest version and still haven’t been able to root.
I have tried relocking the bootloader and unlocking it, but upon unlocking it again, it says that it's already unlocked...?
(Bootloader shows LOCK STATE - unlocked when trying to relock bootloader)
I have been able to root my Nexus 7 2013, but can't seem to get my Nexus 5 to work..
How about flashing TWRP via fastboot, then use the volume/power button to immediately boot into TWRP, and then flash supersu?
The bootloader will not relock?
audit13 said:
How about flashing TWRP via fastboot, then use the volume/power button to immediately boot into TWRP, and then flash supersu?
The bootloader will not relock?
Click to expand...
Click to collapse
Yeah, I don't know why, when I try to OEM lock and unlock it says it's already unlocked, which is odd.
But I did the TWRP via fastboot and installed SuperSU that way, thanks.
Glad it worked for your phone.
Help me to unlock bootloader and root
Hello Guys, I want to unlock the bootloader on my N5. My phone is in Android Ver 6.0.2 with Feb patch(Build Number MMB29Q). Please help me in doing so. Also i would root my device, i would prefer TWRP. Please anybody...
Boot the phone into fastboot, connect the phone to your computer, and use fastboot commands to unlock the bootloader, flash TWRP, and flash supersu for root.
Unlocking the bootloader will wipe the phone.
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Sony Xperia Z5 premium. I had an unlocked bootloader and custom ROM. I was going to resell the phone, so I used flashtool to re-lock the bootloader and flashed a stock ROM. E6853, flashed correct model specific .ftf file. So...now I have a working stock phone. I do not have access to the bootloader, or recovery. When i adb reboot bootloader, it goes to a black screen with a blue LED. If I volume down when plugging in USB, it does the same thing. I am not rooted, so I can't flash from within the OS. I think I relocked the bootloader successfully, but can't unlock it now, because I can't access the fastboot. Does anyone have any ideas?
Z5 Premium 5.1.1 firmware .200
Hey guys, i have a problem, my Bootloader is locked and i can't access my recovery, and there is no rom installed, what should i do now? i can't access Developer options to Allow OEM unlock because there is no OS.
am i screwed? or there is something i can do?
Iago Duarte said:
Hey guys, i have a problem, my Bootloader is locked and i can't access my recovery, and there is no rom installed, what should i do now? i can't access Developer options to Allow OEM unlock because there is no OS.
am i screwed? or there is something i can do?
Click to expand...
Click to collapse
Did you ever enable developer options and allow USB debugging? If so, and you can connect to ADB on a PC, you can flash stock firmware back onto the phone.
or try this:
As I didn't have USB debugging enabled I couldn't connect to the phone via ADB, but if you put it into recovery mode you can use Fastboot. Hold down the power key to turn the device off and turn it on while holding down Vol Down to load up recovery mode.
Click to expand...
Click to collapse
However, with locked bootloader there is no room for error in flashing firmware via ADB or you will brick the phone. You have to flash the correct firmware exactly for your phone, with the same level of bootloader you already have or newer. You can't flash Mexico over Brazil or Lollipop over Marshmallow. Has to be exactly what was made for your phone, either what you already had or newer (if it exists).
What OS was installed before?
But WHY is there no ROM installed? What did you do?
The OS installed before was the most recent Stock MM Brazil, i installed the stock rom, it worked, then i wanted to go back to stock recovery, it it worked too, then i wanted to locked my bootloader, i locked, after that i couldn't enter recovery, neither boot to OS.
Iago Duarte said:
The OS installed before was the most recent Stock MM Brazil, i installed the stock rom, it worked, then i wanted to go back to stock recovery, it it worked too, then i wanted to locked my bootloader, i locked, after that i couldn't enter recovery, neither boot to OS.
Click to expand...
Click to collapse
You wanted to re-lock your bootloader? Unlocked bootloader = God mode.
Did you ever have TWRP? You said you wanted to go back to "stock recovery" (not sure why, it's mostly useless compared to TWRP custom recovery.)
I'm not sure why re-locking the bootloader would wipe the OS...
But you can boot to the bootloader screen using the volume and power button and re-flash the stock firmware, using ADB. Here's the link to the newest Brazil Marshmallow for XT1225:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
This guy below got out of a jam because he had an unlocked bootloader, which is very forgiving. Locked bootloader is harder.
https://forum.xda-developers.com/moto-maxx/help/maxx-xt1225-br-hard-brick-help-please-t3661803
Yeah, i don't know what happened either, why the **** did my OS got Wiped?
Can i flash the stock rom with the bootloader locked via ADB? how?
Iago Duarte said:
Yeah, i don't know what happened either, why the **** did my OS got Wiped?
Can i flash the stock rom with the bootloader locked via ADB? how?
Click to expand...
Click to collapse
You have to boot to the bootloader screen manually, using the volume + power button trick.
Once on the bootloader screen, when you plug you phone into a PC with ADB installed, it should recognize it.
Then, flash the full stock firmware, from the link above. It's Brazil Marshmallow firmware with December 2016 Security Update. I don't know of any newer right now. You have Brazil XT1225, so that Brazil firmware is compatible with your phone.
But with locked bootloader you have to flash exact same version or newer made for your phone, and you have to enter the commands correctly or you may brick your phone. (When I flashed from Puerto Rico Kitkat to India Lollipop, I messed up. But since my bootloader was unlocked, I just reflashed again, when I realized my mistake.)
If you are not sure of the steps, google Motorola firmware ADB. Here's a couple of excellent tutorials:
How to Manually Official Firmware on any Motorola Device
https://forum.xda-developers.com/dr...force-how-to-manually-flash-official-t3282077
I use this one above. IGNORE where it says you need an unlocked bootloader, because he's talking about cross-region flashing which you are NOT doing. You are flashing your own region firmware.
This one below is by rootjunky and he while he also discusses RSDLite, later in the article he says ADB/fastboot are best as RSDLite can stall.
Motorola Firmware Restore Plus Unbrick
http://www.rootjunky.com/motorola-firmware-restore/
If you get your phone running again, I suggest you unlock the bootloader. There are ways to hide an unlocked bootloader (like Magisk), if that's why you locked it back... But an unlocked bootloader + root makes it YOUR phone and much easier to recover from disasters.
Thanks a lot Chazz, it worked, thanks for the help, really appreciate it, thanks for all the useful tips too.