Related
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
without enabling oem unlock in the developer options, nope. but you can use the stock recovery to check if a factory reset would help.
Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).
win465 said:
Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).
Click to expand...
Click to collapse
Had you unencrypted?
Yes, but i flashed backed to stock kernal.
win465 said:
Yes, but i flashed backed to stock kernal.
Click to expand...
Click to collapse
How?
Using the nexus tool kit. After that I locked the bootloader to sideload the update.
win465 said:
Using the nexus tool kit. After that I locked the bootloader to sideload the update.
Click to expand...
Click to collapse
Were you rooted before all of this too?
Nope
Evolution_Tech said:
Were you rooted before all of this too?
Click to expand...
Click to collapse
Nope
win465 said:
Nope
Click to expand...
Click to collapse
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.
Evolution_Tech said:
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.
Click to expand...
Click to collapse
Thank you for your help
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.
RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
Click to expand...
Click to collapse
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.
Possible idea
Evolution_Tech said:
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.
Click to expand...
Click to collapse
There's some more concrete info in the first couple pages, especially regarding our N6's:
http://forum.xda-developers.com/nexus-9/help/to-toggle-allow-oem-unlock-via-fastboot-t3091119
Hope this helps.
I'll keep my eyes open for anything that seems pertinent.
Best of luck
RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.
Click to expand...
Click to collapse
I get this error message "system partition has unexpected contents" (Status 7).
win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
Can you fastboot boot twrp recovery? And if that is possible, will twrp flash zips with a locked bootloader?
Edit: I'm almost certain fastboot boot recovery won't work with a locked bootloader. I almost thought I had a good idea.
I am in the same situation. Bootloader locked and no custom recovery nor adb enabled. surprisingly enough, yesterday my phone could boot up but it's stuck now in the configuration process. I cannot access to the settings so I can check usb debugging or oem unlock. I can only access the dialer. my question is: is there anyway to do that with just a dialer code?
Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).
Didgeridoohan said:
Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).
Click to expand...
Click to collapse
Sorry for the noob question but where can I find these OTAs and how to install one of them? Does it require usb debugging to be enabled?
Try to port a TWRP recovery, but failed. I just used the "boot-repacker-4.0.1" to unpack and try to merge it to the twrp-2.8.7.0H901.img. My device was rooted and flash using flashify download from google play.
https://www.dropbox.com/s/ewkeg8kb5xbb366/Stock%20Recovery?dl=0 Stock Recovery.img
https://www.androidfilehost.com/?fid=24269982086988199 TWRP for LG-H901<--- can anyone help to port this one?
http://boot-recovery-repacker.software.informer.com/ Boot Repacker Tools for Pack and UnPack img
@hoi_lai can you tell me the way you rooted your phone? Mine having a F600L.
hoi_lai said:
Try to port a TWRP recovery, but failed. I just used the "boot-repacker-4.0.1" to unpack and try to merge it to the twrp-2.8.7.0H901.img. My device was rooted and flash using flashify download from google play.
https://www.dropbox.com/s/ewkeg8kb5xbb366/Stock%20Recovery?dl=0 Stock Recovery.img
http://boot-recovery-repacker.software.informer.com/ Boot Repacker
Click to expand...
Click to collapse
How to root F600s. Thanks!
I think the vendor did it by edited their .tot file with corresponding .dll before flashing it with LG flash tools. http://www.lgbbs.com/thread-7260-1-1.html
Well not sure if it has a unlocked no but you absolutely need a unlocked boot loader to even touch the stock recovery
mr turtle droid said:
Well not sure if it has a unlocked no but you absolutely need a unlocked boot loader to even touch the stock recovery
Click to expand...
Click to collapse
Under developer's option, there is a check box to enable oem unlock bootloader, so I don't think it was the cause. I can use adb to boot into fastboot mode. And with Flashfire.apk developed by the well known developer "Chainfire", I can even backup the whole phone and flash .zip file without custom recovery. However, If the system crash and cannot boot, you cannot get into the app to restore it. So, porting the custom recovery is crucial.
Use fastboot to flash the recovery image then?
Pretty sure the check box for enable oem unlock bootloader is on every v10 version. It's just that the only one that it actually *works* on and actually unlocks the bootloader is the USA t-mobile version.
Sent from my pretty nifty brand new LG V10
You can't replace the recovery while the bootloader is locked. The only partition than can be touched n modified is system.
Sent from my LG-H900 using Tapatalk
MysteryEmotionz said:
You can't replace the recovery while the bootloader is locked. The only partition than can be touched n modified is system.
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
Is there any hope to have an exploit that can break the bootloader lock?
hoi_lai said:
Is there any hope to have an exploit that can break the bootloader lock?
Click to expand...
Click to collapse
I'm working on it but I work 6 days a week n have a family. I requested certain files that I needed that would help but never received them also
Sent from my LG-H900 using Tapatalk
Is this thread still alive?
Hello, i want to install custom rom but as i know first i must to unlock bootloader.
I did download Samsung drivers, i installed adb and allowed USB debugging but when i write command "adb reboot bootloader" my phone just reboot. How can i unlok bootloader to install custom recovery and custom rom
why unlock boot loader? u can directly write custom recovery or root
asadnow2k said:
why unlock boot loader? u can directly write custom recovery or root
Click to expand...
Click to collapse
I tried install recovery with odin but still it's not working
Kernelus said:
I tried install recovery with odin but still it's not working
Click to expand...
Click to collapse
What is the version of your device and version of Android?
boyan81 said:
What is the version of your device and version of Android?
Click to expand...
Click to collapse
It is SM-G800F and android version 6.0.1
I just want to install custom rom I did it on manye devices but here i can't. :/
Kernelus said:
It is SM-G800F and android version 6.0.1
I just want to install custom rom I did it on manye devices but here i can't. :/
Click to expand...
Click to collapse
Before you flash twrp with odin unchecked autoreboot, when done, reinsert the battery and try to boot in twrp by pressing up+home+power.
Or did you try this :https://forum.xda-developers.com/ga...uide-rooting-g800f-marshmallow-6-0-1-t3558915
boyan81 said:
Before you flash twrp with odin unchecked autoreboot, when done, reinsert the battery and try to boot in twrp by pressing up+home+power.
Or did you try this :https://forum.xda-developers.com/ga...uide-rooting-g800f-marshmallow-6-0-1-t3558915
Click to expand...
Click to collapse
Try this link
https://android.stackexchange.com/questions/77872/how-to-unlock-bootloader-on-samsung-devices
Can I try Odin and fastboot while I have installed Linux not windows?
Sames issue
boyan81 said:
Before you flash twrp with odin unchecked autoreboot, when done, reinsert the battery and try to boot in twrp by pressing up+home+power.
Or did you try this :https://forum.xda-developers.com/ga...uide-rooting-g800f-marshmallow-6-0-1-t3558915
Click to expand...
Click to collapse
Hi, I have the same setup and I've tried both methods to get root with no success. I had TWRP but the quickroot took it back out. Error shows binarys not installed so was wondering if unlocking the bootloader might fix the issue. Any suggestions? Also SuperSU has been updated according to Play store.
Thanks in advance.
so i tried rooting my redmi4x device for the first time but i think i had insufficient amount of charge not it dosent boot but shows the mi logo and it doesnt go to recovery mode either
i think i soft bricked it please help
flash lazyflasher zip from TWRP recovery
atmfd said:
it doesnt go to recovery
Click to expand...
Click to collapse
satyajit2412 said:
flash lazyflasher zip from TWRP recovery
Click to expand...
Click to collapse
But it doesn't go to recovery.
It will go to fastboot mode though and then with MiFlash you can restore working system.
I got everything fixed but thanks anyway
atmfd said:
I got everything fixed but thanks anyway
Click to expand...
Click to collapse
How?
atmfd said:
so i tried rooting my redmi4x device for the first time but i think i had insufficient amount of charge not it dosent boot but shows the mi logo and it doesnt go to recovery mode either
i think i soft bricked it please help
Click to expand...
Click to collapse
Go to fastboot and install custom recovery
Then flash laze flasher then flash rom.
??
chandypandy said:
??
Click to expand...
Click to collapse
TWRP
https://forum.xda-developers.com/moto-x4/development/root-moto-x4-t3696180
icarolessa said:
TWRP
https://forum.xda-developers.com/moto-x4/development/root-moto-x4-t3696180
Click to expand...
Click to collapse
Tried, doesn't work for the google fi variant
chandypandy said:
Tried, doesn't work for the google fi variant
Click to expand...
Click to collapse
TWRP Official
https://dl.twrp.me/payton/twrp-3.2.1-0-payton.img.html
It doesn't work
Works for my Android One X4
I think it is probably better to start with
https://twrp.me/motorola/motorolamotox4.html
chandypandy said:
It doesn't work
Click to expand...
Click to collapse
What problem are you having? Did you enable usb debugging?
The hardware is the same.
Twski said:
The hardware is the same.
Click to expand...
Click to collapse
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error
icarolessa said:
What problem are you having? Did you enable usb debugging?
Click to expand...
Click to collapse
https://dl.xda-developers.com/4/4/6....png?key=wua4zgqvFDcsrdLnpuLl_w&ts=1522291710
Our devices don't have a recovery partition to flash to.
Read the install instructions correctly:
https://twrp.me/motorola/motorolamotox4.html
You should use "fastboot boot twrp-3.2.1-0-payton.img" instead.
Then, follow along:
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your password, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
Click to expand...
Click to collapse
chandypandy said:
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error
Click to expand...
Click to collapse
I think the right command is this:
fastboot flash boot [file name].img
No,
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image.
Click to expand...
Click to collapse
chandypandy said:
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error
Click to expand...
Click to collapse
I could be wrong but it seems like you are trying to flash TWRP to the recovery partition and there's no such thing on this phone. You have to temporarily boot TWRP and the keep following the instructions.
Is anybody able to backup / restore the phone with android one on encrypted file system??, im using the official twrp, but restoring backups just cause bootloops
is it necessary to unlock the bootloader before?
If you're asking if the bootloader needs to be unlocked to install magisk, absolutely!
Sorry for the dumb question but how do you unlock the bootloader on the Fi Android one Version?
Potential fix
chandypandy said:
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error
Click to expand...
Click to collapse
If you are still haven't fixed this yet the issue is you need to fastboot boot the boot twrp image and then flash the flash image inside twrp. The guide on TWRP official will give you a guide on how to do this, the files required are also there.