*** nevermind sorted it***
So i made a schoolboy error and forgot to backup TA.
I installed Androplus kernel and twrp (recovery works) but booting the phone gives device cant be trusted error.
Can i flash a firmware with flashtool to get back up and running?
You might try to lock the bootloader with Flashtool. I do not see the point of it but it might stop that pesky warning on boot. Tell us if you succeeded please.
Flashing a stock ROM will just give you a stock kernel, system and overwrite the recovery partition. The bootloader will reain unlocked.
Related
Hi there:
So, I've decided to unroot and relock my Xoom 4G, in anticipation of the official JB release. When I lock the bootloader (fastboot oem lock), the device locks, reboots, then comes up with the "Failed image SOS 0x0002" error. If I then unlock the bootloader, it boots into Honeycomb just fine.
Now, I'm assuming that I need my bootloader locked to do the upgrade, because there is a small update I'm notified on (HLK75F), and when I try to install it, the devices reboots, and I get the yellow bang and can go no further until a hard reset.
So, I can't boot with locked bootloader; can't do updates with an unlocked bootloader.
Can anyone advise?
Thanks!
shmengie said:
Hi there:
So, I've decided to unroot and relock my Xoom 4G, in anticipation of the official JB release. When I lock the bootloader (fastboot oem lock), the device locks, reboots, then comes up with the "Failed image SOS 0x0002" error. If I then unlock the bootloader, it boots into Honeycomb just fine.
Now, I'm assuming that I need my bootloader locked to do the upgrade, because there is a small update I'm notified on (HLK75F), and when I try to install it, the devices reboots, and I get the yellow bang and can go no further until a hard reset.
So, I can't boot with locked bootloader; can't do updates with an unlocked bootloader.
Can anyone advise?
Thanks!
Click to expand...
Click to collapse
You can do updates with an unlocked bootloader as long as it is stock. The lock doesn't have anything to do with that.
However: The fact that it can't boot when locked suggests that your not back to 100% stock. Re-download images for your Xoom from http://developer.motorola.com/products/software/ and re-flash them.
airesch said:
The fact that it can't boot when locked suggests that your not back to 100% stock.
Click to expand...
Click to collapse
Incorrect. If you've been running with your bootloader unlocked, then decide to lock it, 99% of the time it won't boot, even if you're running 100% stock. For example, if you're on stock 4.0.4 with an unlocked bootloader, then decide to re-lock it, it won't boot. If your bootloader is unlocked, the only way your Xoom will boot after locking it is to install one of the firmware packages listed for your device at http://developer.motorola.com/xoomsoftware, as you correctly pointed out. Once you flash those images with fastboot, you can then lock your bootloader and it will boot. Once it boots, just keep applying the system updates as it prompts you and eventually you'll end up on the latest version available for your device.
oldblue910 said:
Incorrect. If you've been running with your bootloader unlocked, then decide to lock it, 99% of the time it won't boot, even if you're running 100% stock. For example, if you're on stock 4.0.4 with an unlocked bootloader, then decide to re-lock it, it won't boot. If your bootloader is unlocked, the only way your Xoom will boot after locking it is to install one of the firmware packages listed for your device at http://developer.motorola.com/xoomsoftware, as you correctly pointed out. Once you flash those images with fastboot, you can then lock your bootloader and it will boot. Once it boots, just keep applying the system updates as it prompts you and eventually you'll end up on the latest version available for your device.
Click to expand...
Click to collapse
The cause of that 99% is because rooting the Xoom also changes the boot image (to set certain parameters,) and unless you have the clean boot image (of the right version that your updates are at,) it's not 100% stock. Even then, sometimes the rooting process (or if you have also installed busybox and not uninstalled it,) can update timestamps on folders in the system image which will foul up the checksums. I have restored a nandroid of my stock installs, re-flashed the boot and recovery to the right versions, and had it relock successfully several times. The trick is to have those images so all the checksums line up.
Lesson here: If it won't boot when locked, then it wasn't exatcly 100%.
Thanks, guys. I will try redownloading the img files and go through the fastboot commands again.
airesch said:
Lesson here: If it won't boot when locked, then it wasn't exatcly 100%.
Click to expand...
Click to collapse
False. Run unrooted pure stock 4.0.4 on an unlocked bootloader. After that, lock your bootloader and watch what happens.
Also, rooting only modifies your boot image if you use one of those pointless universal root methods. If you simply unlock, flash a mod recovery, and flash the Superuser ZIP from androidsu.com, it leaves the boot image untouched. An insecure boot image is only needed if you want root access in ADB, which 99% of rooted users couldn't care less about.
Sent from my Nexus S using Tapatalk 2
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
Whenever I try unlock bootloader bug out FAILED (remote: Command did not allowed).
I have Bootloader unlock allowed.
I tried in CMD - Fastboot and Flashtoo and out this same problem.
When I tried twice unlock bootloader I get OKAY and I try turn on my phone, I walk in bootloop.
Where is problem?
Hi! So actually you did unlocked your bootloader (as i understand), and when you turn on your device after the unlock you go into bootloop. This is something normal. You need to flash the stock .ftf with flashtool (i recommend you to use old versions like 0.9.11.0). Have a look here:
http://forum.xda-developers.com/xperia-l/help/bootloop-unlocking-bootloader-t2675892 ! Good luck!
What firmware version did you flashed. I have flashed firmware for c2104 and i got this bootloop. Make sure you flash the propper firmware verison for your device.
noobp said:
Hi! So actually you did unlocked your bootloader (as i understand), and when you turn on your device after the unlock you go into bootloop. This is something normal. You need to flash the stock .ftf with flashtool (i recommend you to use old versions like 0.9.11.0). Have a look here:
http://forum.xda-developers.com/xperia-l/help/bootloop-unlocking-bootloader-t2675892 ! Good luck!
What firmware version did you flashed. I have flashed firmware for c2104 and i got this bootloop. Make sure you flash the propper firmware verison for your device.
Click to expand...
Click to collapse
When I tried it, in Service Menu I have "Rooting status: Unkown".
I have bad code in Bootloader unlock Wizard and I can't change it, field is inactive.
I have firmware C2104, I don't have any branding.
After flashing recovery I tried to relock my device after relocking my device not starting (only blinking) later unlocked my bl device automatically start up.
flashtool and reflashing ftf firmware and power on phone and done
No I cant lock bl after flashing recovery. I need super su and drm fix so after flashing recovery I tried to lock my device. Device is not booting
Later unlocked my device normal booting. I need ota updates so I need to lock my device and also I need recovery so plz help me(senior members)
divakarhero said:
No I cant lock bl after flashing recovery. I need super su and drm fix so after flashing recovery I tried to lock my device. Device is not booting
Click to expand...
Click to collapse
Maybe you have to choose between root and locked BL? Read this:
https://source.android.com/security/verifiedboot/
I can't say more because I never tried to lock again my XA (useless?).
Recently rooted my new Zenfone 7. Is it possible to remove Bootloader unlocked Warning message at the start up of the system? Thanks for an answer.
re-lock the bootloader
Boot into fastboot, then send this command from your pc.
fastboot oem asus-lock
how did you get root to work? I followed the instructions listed and it would not work for me.
I followed the instructions there: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/ in fastboot mode you should update android drivers manually through device manager to get it work otherwise you'll get " waiting on device " error and it won't flash TWRP.
Is it possible to remove Bootloader unlocked warning without re-locking device though?
Jkm15 said:
I followed the instructions there: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/ in fastboot mode you should update android drivers manually through device manager to get it work otherwise you'll get " waiting on device " error and it won't flash TWRP.
Click to expand...
Click to collapse
Getting TWRP on and working was fine. It was when I went and tried to flash Magisk that it kept causing a bootloop.
Jkm15 said:
Is it possible to remove Bootloader unlocked warning without re-locking device though?
Click to expand...
Click to collapse
Why? Unless you plan on overwriting TWRP, there is no benefit to having it unlocked all the time. TWRP will still work after it is re-locked. and you can unlock it again via the app anytime you need to update.
Joeb2000 said:
Getting TWRP on and working was fine. It was when I went and tried to flash Magisk that it kept causing a bootloop.
Why? Unless you plan on overwriting TWRP, there is no benefit to having it unlocked all the time. TWRP will still work after it is re-locked. and you can unlock it again via the app anytime you need to update.
Click to expand...
Click to collapse
Had locked bootloader on device with magisk. Result is fastboot loop =|
Same wish here. that warning screen is ugly....