Related
Q&A for [FIX][BOOT][LOGO][titan] Remove Unlocked Bootloader Warning
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Wow. This is pretty awesome.
download logo.bin.txt and remove .txt and boot your phone in bootloader and enter following command.
this logo remove unlock waring and this logo is from latest update.
Code:
fastboot flash logo logo.bin
bootloader relock Moto g 2nd gen
Hi How do you relock the boot loader because all the online tutorials don't work.
This works with Android L?
Does it works on Moto G 2014 - XT1063 - whit Lollipop?... ?
Gracias!
100% working
It worked perfectly, thank you
Funcionou perfeitamente, obrigado
vikasb32 said:
download logo.bin.txt and remove .txt and boot your phone in bootloader and enter following command.
this logo remove unlock waring and this logo is from latest update.
Code:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
Is Android Lollipop supported?
After flashing this, my phone bootloops a random amount of times(Sometimes 2, sometimes 5, etc.) after turning it off.. It does eventually boot (so far), however having to wait 15-20 minutes when I need to turn it off and back on is incredibly annoying.. Can anyone assist? If it's relevant, I have an XT1064 on the 5.0.1 software, bootloader is unlocked, and I have the TWRP 2.7.1.1 recovery installed. Thanks!
Chrisshemur said:
After flashing this, my phone bootloops a random amount of times(Sometimes 2, sometimes 5, etc.) after turning it off.. It does eventually boot (so far), however having to wait 15-20 minutes when I need to turn it off and back on is incredibly annoying.. Can anyone assist? If it's relevant, I have an XT1064 on the 5.0.1 software, bootloader is unlocked, and I have the TWRP 2.7.1.1 recovery installed. Thanks!
Click to expand...
Click to collapse
TWRP is now 2.8.4.0 beta and Chainfires root is now 2.44beta the new root cures lollipop bootloops, also there probably is a 5.0.2 update for xt1064
reefuge said:
TWRP is now 2.8.4.0 beta and Chainfires root is now 2.44beta the new root cures lollipop bootloops, also there probably is a 5.0.2 update for xt1064
Click to expand...
Click to collapse
Where do I locate the 2.44 SuperSU beta to download? Would I just flash this in TWRP?
Edit: Flashed 2.44 and the bootloops are gone! Thanks!
I have a major problem with this.
The zip works fine, I flash and I'm okay. And ever since, it's taking FOREVER to boot up. Usually, the phone will stay on the M logo screen, and then after a minute or so turn off and restart, showing the same M logo again. This usually repeats twice until it finally gets to the lock screen, but today showing my friends the slow boot time, it happened three times. We timed it and it took a total of 6 minutes (I forced it off and restarted after it did it the third time once). Can anyone help me with this horrible problem?
Worked like a charm...THANKS!
How to flash this bin file to hide the boot loader img
how to hide by flashing..anyone,...?
mat987541 said:
Hi How do you relock the boot loader because all the online tutorials don't work.
Click to expand...
Click to collapse
You need to flash the latest firmware or else the bootloader will not recognize the firmware signature. Get them from here http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
aadisheshu said:
how to hide by flashing..anyone,...?
Click to expand...
Click to collapse
Code:
fastboot flash logo.bin
as admin. make sure you have the correct drivers.
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
JWACK72 said:
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
Click to expand...
Click to collapse
What device do you have, XT1095, XT1097, etc? And you are not able to boot into the bootloader using vol down + power correct?
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
JWACK72 said:
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
Click to expand...
Click to collapse
If it boots to fastboot, it's not dead. Just reflash the recovery and you're good to go.
Sent from my XT1095 using Tapatalk
Was there a resolution for this? I'm having a similar problem. I'm not sure how I got to this status, but here's what I'm dealing with:
Device: XT1095
Bootloader: Unlocked
Rooted, ROM - Resurrection Remix, TWRP
Turning on the phone reaches the RR bootsplash and proceeds to bootloop.
When holding down the power and volume down, it will enter fastboot.
When I try to open TWRP recovery, it'll show the blue TWRP screen and just sit there.
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
bibbin said:
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
Click to expand...
Click to collapse
Do you have a USB-OTG device plugged in while trying to start TWRP? If so remove it, you can mount it after TWRP starts if this helps.
Have you tried a different build of TWRP? I'm currently using the one built by invisiblek, one of the CM devs for the victara. It was built and posted on December 8th and is here: http://www.invisiblek.org/twrp/twrp_2.8.7.0-0624b8bd_victara.img
Have you tried flashing the stock recovery to see if that will start? If it does, you could use the factory reset option there and then try reinstalling TWRP. (TWRP has a settings directory in /sdcard and maybe that is corrupted.)
There have been a few people posting with this problem but I've not seen a definitive fix for it.
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
bibbin said:
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
Click to expand...
Click to collapse
That's interesting, the TWRP Manager has never worked correctly for me although it's been a long time since I've tried it.
To flash manually, you actually need fastboot which is usually installed along with adb. If you open a command window, and type in fastboot and it runs, the rest is pretty easy. If it doesn't run, this thread has the 15 second ADB/Fastboot installer, select to install it system-wide: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Download the recovery image, rename the file to twrp.img, then open a command window in the folder where you downloaded it (type cmd then Enter in the address line at the top of the folder window.)
When the command window is open and the phone is in bootloader mode and connected to the computer with the USB cable, enter the command "fastboot device" (without the quotes) If everything is working it will list the serial number of your phone.
Then enter "fastboot flash recovery twrp.img" (without the quotes) to start the flashing process, ignore the size mismatch message. It will only take a few seconds to complete.
Use the volume down key to highlight recovery, then volume up to select it. Hopefully TWRP will boot up and you'll be good to go!
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
bibbin said:
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
Click to expand...
Click to collapse
Reflash stock rom from fastboot.
Sent from my XT1095 using Tapatalk
UPDATE: Thanks all. Well, after fiddling around with various methods of reinstalling TWRP, I managed to get it reinstalled and all is back to normal now.
Looking for an answer I have not been able to find as to recovering a used N6.
What I have is a used N6, with TWRP 6.8.7.1 (newest version I believe) no recovery files and does not appear to have a working system on it. The bootloader has been relocked (won't allow unlocking or reflashing of stock firmware). What I am guessing is some one unlocked it, modified it, and relocked it then somehow messed up and wiped the system ... Guessing.
It has the older 71.10 bootloader on it now, not sure if it updated beyond 5.11 or not.
Just thinking (as I write this) would it be possible to make an image of another N6 put it on a OTG thumb drive and restore that or if possible push recovery files through Fastboot or possibly ADB in recovery?
Or am I out luck?
Any know fixes?
My recommendation would be to push files through fastboot. Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
As a note, I recently had to go through this process and the FLASH ALL file was failing to flash the system file. The answer was to manually flash each file myself (directions provided in the same post). It was fairly easy once I realized the issues with FLASH ALL.
As soon as you get android booting, go back and unlocked the bootloader. I don't get all these people locking their bootloaders... ESPECIALLY with a rom and custom recovery!
The above is almost the right advice, but IIRC it wont work with a locked bootloader.
Fortunately you have TWRP installed. Don't mess with your recovery partition until you get this sorted.
Just go download a rom, any will probably work... I would stick with an AOSP one and maybe download the 5.1.1
You may be able to just mount the phone as an MTP device, I think that may be supported by TWRP at this time? Or sideload/push.
Gimme a sec, I'll post some links
---------- Post added at 01:29 PM ---------- Previous post was at 01:14 PM ----------
As I said most roms will probably be OK, But to be specific I would just grab a 5.1.1 version of pure nexus... say the last 5.1.1 version
https://www.androidfilehost.com/?w=files&flid=34545
Download page for pure nexus (this does not include gapps)
Specifically I would download this one, as I said its the last 5.1.1 version. I say this because the bootloader should be fine with it whether its updated or not (I couldn't find a list of what bootloader is what version)
https://www.androidfilehost.com/?fid=24052804347817485
Boot to recovery, and see if your phone shows up under my computer. MTP transfer should be enabled by default in TWRP and is supported by TWRP version > 2.8
If you can't get it to show up as an MTP device, you should be able to see it with ADB while booted into TWRP. Use either the push command
http://stackoverflow.com/questions/...mand-to-push-a-file-on-device-without-sd-card (discussion on push)
push maybe to /sdcard if the directory exists.
I'd probably just use sideload though,
https://twrp.me/faq/ADBSideload.html
One of these should work
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
I'll leave it to you to find gapps for 5.1.1
I don't think you would need them though as android should still load and work fine with out them. I would simply start up the phone with the rom installed, turn on allow oem unlock, boot immediately back into bootloader and unlock the boot loader. If something happens to that recovery partition the phone is a paperweight with the bootloader locked... really not worth keeping it locked.
Once you get the bootloader unlocked, update to something current and worry about gapps then?
Thank you so much guys!! Will give this run as soon as I have a chance and update the post(may take a day or so been pretty busy at work and such)
UPDATE : @scryan Hey just want to say that did the trick, had to use a thumb drive and OTG cable to load the ROM. But was in and out with an now unlocked bootloader in under 30 minutes.
Thanks again guys!!
Hello people,
I have an OnePlus 3T, which does not start the OS. I can open Fastboot Mode or TWRP. I do not even know which OS is installed (I think stock rom, but do not know). When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted". When I boot into system, it stops at the black "Powered by android" Screen (very first screen).
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
So what Information do I have so far (with my amateur knowledge):
adb shell getprop ...
ro.build.version.release: 6.0.1
ro.build.version.sdk: 23
ro.build.display.id: omni_oneplus3-eng 6.0.1 MOB31K eng.jc.20170208.012427 test-keys
ro.modversion: OmniROM-6.0.1-20170208-oneplus3-HOMEMADE
ro.twrp.version: 3.0.4-1
When I start the bootloader:
Product_Name - msm8996
Variant - MTP UFS
Bootloader Version -
Baseband Version -
Serial Number - *****
Secure Boot - enabled
Device State - unlocked
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
I tried to flash the stock ROM => did not work (with this Error 7)
So my first question: Which OS do I have? Really Marshmallow 6.0.1?
Second: Do you need more infos?
Third and most important: How to repair this mess?
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Thank you very much for your help.
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
thes3usa said:
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
Click to expand...
Click to collapse
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
elchico92 said:
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
Click to expand...
Click to collapse
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
elchico92 said:
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
Click to expand...
Click to collapse
Nope, that's the complete stock Zip. Unless you want to install OOS, that's not the one to Sideload.
Download the FW only from here: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
And then Sideload it, reboot back to recovery, and then Sideload the ROM.
elchico92 said:
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
Click to expand...
Click to collapse
What is in the TWRP folder, anything? The TWRP folder would normally only be created, if a backup was created. You can possibly just boot TWRP, select the RESTORE option, select the backup from the TWRP folder, and get the phone up and running again.
Another possibility, if you aren't that up on adb commands (sideload, etc.), since you can access the internal storage, just download a ROM or fill stock ROM zip onto your PC, then just drag/copy to internal storage. Then boot TWRP, select INSTALL, pick the file, and flash it.
What is the background of the device, how do you not know the OS version? Did you receive it this way, or fixing it for a friend or something?
---------- Post added at 09:19 AM ---------- Previous post was at 09:12 AM ----------
elchico92 said:
When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted".
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Click to expand...
Click to collapse
That isn't the dm-verity notification. The dm-verity notification screen is similar, but says "dm-verity is not started in enforcing mode".
What you described is the bootloader unlocked warning screen. The bootloader unlocked warning screen is expected and normal (in fact, unavoidable) if the bootloader is unlocked. And unlocked bootloader is required for TWRP, flashing custom ROMs, etc.
dm-verity warning screen is in fact normal, as well, if you have TWRP installed. That one can be disabled by a couple different methods. But it's only purpose is to notify a "average" user that the system has been modified. For XDA users that are intentionally modifying their phones (TWRP, root, etc.) the warning is pretty meaningless. Under certain conditions, dm-verity will prevent the phone from booting. But TWRP and root in themselves, will normally not do that.
Neither warning means you have the wrong kernel, necessarily. And unless you (or someone else) tried to flash a kernel, there really isn't any reason to believe that.
---------- Post added at 09:29 AM ---------- Previous post was at 09:19 AM ----------
elchico92 said:
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
Click to expand...
Click to collapse
Flashing stock recovery will (by definition) replace TWRP with stock recovery. You probably have recovery, just the stock one (not TWRP) which is fairly useless in your case (can't flash custom ROMs, root, etc.).
elchico92 said:
I tried to flash the stock ROM => did not work (with this Error 7)
Click to expand...
Click to collapse
Can't really troubleshoot this, unless you tell us what file exactly (file name) and where you got it from. "Stock ROM" is far too vague, and can literally mean a dozen or more different things.
Also, what version TWRP?
Using a TWRP version which does not support Oreo is one reason for Error 7. Or you may have tried a file intended for the 3, not the 3T. So these details need to be provided, before we can figure out what went wrong.
elchico92 said:
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
Click to expand...
Click to collapse
You kind of need to decide which of those you want. Otherwise, there are just too many options for us to give.
Yet another option (in addition to those given) would be to flash the full stock OOS zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Then before rebooting, flash Magisk to root, and you should be all set. The full zip will put you on a fully stock baseline (including firmware). Which, if you aren't sure if you want stock, beta or custom ROM, is not a bad place to be; you can see what the "stock" condition is, before messing with things like custom ROMs. But again, it's totally subjective and a matter of personal preference, and you really do need to decide for yourself what is best for you (as an individual) at this time.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
Why not just sideload stock ROM which includes the firmware? Make life easier
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Yeah, that is a good option, among many. As I mentioned, there are just too many options since the original poster hasn't even decided stock or custom ROM.
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Since OP hasn't mentioned whether he wants to use a stock or custom ROM. So I gave him the link for the latest FW, in case he wants to use a recently updated custom ROM without needing to download the whole Stock zip.
Done!
Thanks a lot. The phone is working again.
I have flashed with adb sideload the firmware and the ResurrectionRemix-Rom (Nougat) and then via TWRP the gapps.
So I hope, everthing will be fine now.
answers:
- TWRP-folder: yeah I created one because I thought, maybe to restore will fix anything
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
- background: it was the phone of a friend of mine => he never heard anything about ROMs etc
The thread can be closed.
elchico92 said:
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
Click to expand...
Click to collapse
I already offered to troubleshoot this error for your, but you never supplied the requested info. Don't assume it is the "right one" next time, but rather, give exact file names, version numbers, and let us verify. Mistakes happen, and it always is good to have another set of eyes look at the specifics.
---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------
elchico92 said:
The thread can be closed.
Click to expand...
Click to collapse
Threads on xda don't get closed, just because you solved your current issue. Others may have a similar problem, and may want to ask questions, etc.
I'm stuck in Fastboot Mode & TWRP without OS
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
slykereven said:
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
Click to expand...
Click to collapse
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Resolved
OK, that's a little crazy but it's working, i've got a one plus 3T A3003, but i had to install Stable9.0.3+Firmware+Modem_OnePlus3.zip and not the one for the 3T ..... then install the last lineage os 17, and everything seems to work for now !!!
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
BillGoss said:
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Hi, thank's for your help, i didn't see your answer before and i have resolved the issue with other method
Official Downloads
https://twrp.me/lenovo/lenovo_X704F.html
Unofficial Downloads
https://www.androidfilehost.com/?w=files&flid=295687
Changelog for unofficial builds
twrp-3.3.1-0-X704F-20190604-codeworkx.img
- Updated to twrp 3.3.1
- Updated prebuilt kernel
- Removed lenovocust from backup
twrp-3.3.0-0-X704F-20190523-codeworkx.img
- initial build
Sources
Device tree: https://github.com/Teamwin/android_device_lenovo_X704F
Kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953
I've seen you are working with yener90 for this device. His TWRP is valid for F, L and few other variants.
Are you able to let us know if yours is the same? Or still testing and too early to know?
Thank you (I follow you in the OnePlus 5 project too).
Flowah123 said:
I've seen you are working with yener90 for this device. His TWRP is valid for F, L and few other variants.
Are you able to let us know if yours is the same? Or still testing and too early to know?
Thank you (I follow you in the OnePlus 5 project too).
Click to expand...
Click to collapse
That seems to be the case
"TARGET_OTA_ASSERT_DEVICE := TB-X704A,TB-X704F,TB-X704L,TBX704,tb_x704a,tb_x704f,tb_x704l"
(https://github.com/codeworkx/android_device_lenovo_X704F/blob/android-9.0/BoardConfig.mk)
There's official support now.
https://twrp.me/lenovo/lenovo_X704F.html
twrp-3.3.1-0-X704F.img verified working on a new TB-X704V. Everything seems to be working.
---------- Post added at 19:36 ---------- Previous post was at 19:04 ----------
Maybe I spoke too soon.
I tried installing Yener90's Lineage OS 16 image only my TB-X704V device and it failed to boot. That's fine, but then I tried to restore the OEM image that I had backed up previously. Unfortunately, I am not able to get back to a booting system.
black.kahder said:
twrp-3.3.1-0-X704F.img verified working on a new TB-X704V. Everything seems to be working.
---------- Post added at 19:36 ---------- Previous post was at 19:04 ----------
Maybe I spoke too soon.
I tried installing Yener90's Lineage OS 16 image only my TB-X704V device and it failed to boot. That's fine, but then I tried to restore the OEM image that I had backed up previously. Unfortunately, I am not able to get back to a booting system.
Click to expand...
Click to collapse
Look at the other thread. 3.3.0 works as expected. Use the old twrp for my current ROM or wait for the next update, which will support 3.3.0
I don't have experience customizing TWRP images for specific devices, so let me apologize in advance for my n00b questions...
How similar are the x704f and x705f tablets? I'm wondering if it might be possible to use an x704f TWRP image on an x705f. Lenovo recently released a stock ROM for Pie on the x705f. Now I'm finally able to unlock the bootloader. The previous stock ROM would not respond to fastboot oem unlock commands. I was then able to fastboot flash a bootloader image pre patched with Magisk so now the tab is rooted and happy. However, I still feel insecure without TWRP as it seems to be a key tool that I use for emergency ADB access, flashing, and making nandroid backups. How big of a project do you think it would be to make a customized image for the x705f? Do you think that is something where I would have to start from scratch? Or could the x704f image be used as a template that I could easily modify with information specific to the x705f?
Thanks for your time. I truly appreciate any help or advice you can give me on this.
Chaser
on my tb-x704f twrp on starts in landscape orientation. the last version i used was 3.2.3 and here i could use both orientations.
i also can't restore an backup because i can't write to the system partition. can this https://forum.xda-developers.com/showpost.php?p=79681018&postcount=259 fix the problem?
gene2 said:
i also can't restore an backup because i can't write to the system partition. can this https://forum.xda-developers.com/showpost.php?p=79681018&postcount=259 fix the problem?
Click to expand...
Click to collapse
No, it won't, it's a magisk module that allows R/W to the system partition after boot up to
facilitate some apps. that require it for full root access.
The problem was that i had no r/w to system partition. the restore works, but the system doesn't start. i have a boot loop with the lenovo logo. i have wiped dalvik, cache and system. after that i also made the normal wipe. then i restored the backup and after restart i have the boot loop. is there anything more to do? this was all i have to do on my other devices.
gene2 said:
The problem was that i had no r/w to system partition. the restore works, but the system doesn't start. i have a boot loop with the lenovo logo. i have wiped dalvik, cache and system. after that i also made the normal wipe. then i restored the backup and after restart i have the boot loop. is there anything more to do? this was all i have to do on my other devices.
Click to expand...
Click to collapse
Sounds like encryption is compromised, restore stock ROm, re-boot and start again.
See my other post to you here:-
https://forum.xda-developers.com/showpost.php?p=80273515&postcount=5
Hello, I have tried TWRP for TB-X704F on TB-X704A, but though my bootloader is unlocked, I have the latest SDK tools, and fastboot flash recovery recovery.img seems to take, nothing I do causes the device to boot into TWRP. I cannot sideload lineagos using stock recovery, and so for now I seem to be stuck. Any suggestions? I'd like to move past Android 7.1 for a more secure OS.
I've had the EXACT same problem with a TB-X704A. I've been waiting for someone else to say so. I'm sorry I don't have a solution but I'm hoping someone more knowledgeable then me sees our problem. Thanks to everyone, especially codeworkx who does this stuff!
Mddaddy said:
Hello, I have tried TWRP for TB-X704F on TB-X704A, but though my bootloader is unlocked, I have the latest SDK tools, and fastboot flash recovery recovery.img seems to take, nothing I do causes the device to boot into TWRP. I cannot sideload lineagos using stock recovery, and so for now I seem to be stuck. Any suggestions? I'd like to move past Android 7.1 for a more secure OS.
Click to expand...
Click to collapse
You have to reboot to recovery manually not via fastboot. Unplug from pc and hold power and volume up it should boot into twrp this way cus f version should work
---------- Post added at 04:02 AM ---------- Previous post was at 03:55 AM ----------
kirknado18 said:
You have to reboot to recovery manually not via fastboot. Unplug from pc and hold power and volume up it should boot into twrp this way cus f version should work
Click to expand...
Click to collapse
Twrp for tb x704f should work on all 704 versions but you have to boot into recovery manually not through adb fastboot it wont boot up that way for some reason. Let me know if this solves the problem.
I wanted to update from LineageOS 16 to LineageOS 17. Instructions there say to upgrade to latest TWRP (https://forum.xda-developers.com/th...m-lineageos-17-0-lenovo-tab4-10-plus-t4016705). I downloaded the unofficial twrp-3.3.1-0-X704F-20190604-codeworkx.img, flashed using adb, but when trying to go into recovery mode - will not go into recovery. Tries, then reboots again, and goes into LineageOS 16.
Downloaded the "official" version form (https://dl.twrp.me/X704F/), version twrp-3.4.0-0-X704F.img, again flashed using adb - again same results. Cannot get into recovery mode, boots twice and goes back into LineageOS 16.
So - something didn't go quite right - how do I get into recovery mode?
tundrwd said:
I wanted to update from LineageOS 16 to LineageOS 17. Instructions there say to upgrade to latest TWRP (https://forum.xda-developers.com/th...lineageos-17-0-lenovo-tab4-10-plus-t4016705). I downloaded the unofficial twrp-3.3.1-0-X704F-20190604-codeworkx.img, flashed using adb, but when trying to go into recovery mode - will not go into recovery. Tries, then reboots again, and goes into LineageOS 16.
Downloaded the "official" version form (https://dl.twrp.me/X704F/), version twrp-3.4.0-0-X704F.img, again flashed using adb - again same results. Cannot get into recovery mode, boots twice and goes back into LineageOS 16.
So - something didn't go quite right - how do I get into recovery mode?
Click to expand...
Click to collapse
Unplug from USB. Hold power and volume up buttons until the bootloader loads. Use the volume rocker to select "Recovery mode". Press power button to confirm.
jfaheyfan said:
Unplug from USB. Hold power and volume up buttons until the bootloader loads. Use the volume rocker to select "Recovery mode". Press power button to confirm.
Click to expand...
Click to collapse
I'm aware of how to get into recovery - it WON'T go into recovery. Starts up, the Moto screen flashes, it reboots, Moto screen again, then loads LineageOS. So I simply cannot get into recovery once selecting "Recovery Mode".
tundrwd said:
I'm aware of how to get into recovery - it WON'T go into recovery. Starts up, the Moto screen flashes, it reboots, Moto screen again, then loads LineageOS. So I simply cannot get into recovery once selecting "Recovery Mode".
Click to expand...
Click to collapse
What model is your tablet?
I have an A model and an F model. I've used the same TWRP on both the A and F. This particular instance is just the A model - TBX-704A
tundrwd said:
I have an A model and an F model. I've used the same TWRP on both the A and F. This particular instance is just the A model - TBX-704A
Click to expand...
Click to collapse
You're not the first:
https://forum.xda-developers.com/showpost.php?p=81254945&postcount=12
https://forum.xda-developers.com/showpost.php?p=82183753&postcount=13
Not sure of the significance, but "Moto" doesn't appear in the boot sequence of my TB-X704N (changed to TB-X704L after I installed LOS 17.1). I get "Lenovo" in an orange rectangle.
My next step would be to try https://dl.twrp.me/X704F/twrp-3.3.1-0-X704F.img . Better yet would be to hear from someone who's installed LOS 17.1 on an "A" model.
---------- Post added at 08:03 PM ---------- Previous post was at 07:42 PM ----------
I installed TWRP 3.4.0 on my TB-X704N (Chinese Tab 4 10+ with 4G) three weeks ago. I went on to install LOS 17.1 (https://forum.xda-developers.com/th...7-0-lenovo-tab4-10-plus-t4016705/post81141501). Everything went well just by following instructions. Thank you, codeworkx!