I am trying to flash TWRP on 10B (was running 23C and did KDZ flash back to 10B). Rooted via Stump, installed BusyBox, TWRP Mananger and Official TWRP App. Since TWRP didn't appear to install TWRP I did some more research I read people had success with 'Partitions Backup' to backup stock recovery partition and then use 'Flashify' to install TWRP. So I downloaded the twrp-3.0.2-0-vs985.img and installed that to recovery after backing up stock. Next reboot takes me into TWRP. If I then boot normally and then shutdown and enter recovery again I'm back in stock recovery. So it's like the flash is temporary.
Anybody care to educate me about what I am doing wrong. I'm sure this was easier in the days of the 'all-in-one' root/TWRP installer but can't download that anymore and I'm tired of the updates and poor performance so want to try custom ROM's.
Any help would be appreciated. I am thinking maybe I need to install recovery again when booted into TWRP? Not sure.
I am wondering if the flash doesn't work because I flashed a TWRP img without the "bump" designation? I am beginning to think the best way to install reliably is using the 'dd' command from adb over remote PC connection (or via su in a terminal shell if advisable)? Any thoughts on using this method and whether I can go right to the latest version of TWRP for the vs985 (twrp-3.0.2-0-vs985.img).
skay said:
I am wondering if the flash doesn't work because I flashed a TWRP img without the "bump" designation? I am beginning to think the best way to install reliably is using the 'dd' command from adb over remote PC connection (or via su in a terminal shell if advisable)? Any thoughts on using this method and whether I can go right to the latest version of TWRP for the vs985 (twrp-3.0.2-0-vs985.img).
Click to expand...
Click to collapse
I think you might have solved your own problem! You can't use just any TWRP image. It has to be specifically bumped for the G3.
iBolski said:
I think you might have solved your own problem! You can't use just any TWRP image. It has to be specifically bumped for the G3.
Click to expand...
Click to collapse
Thanks for the reply iB. I only tried flashing with the VS985 img files. But I didn't start with one that specifically had the "bump" or "bumped" designation in the filename. I am wondering if the later version that I used doesn't actually install bump to recovery but it intended to be installed as an updated version of TWRP on a previously "bumped" recovery image? Sorry for getting into the weeds here but I actually just stayed rooted on 23C for quite a while until I couldn't take it anymore. I looked at moving up to G4, G5, V10 and V20 but it seems like the G3 is the best value LG phone for custom ROMs and hardware is still not bad overall.
Anyone know of a way to determine if recovery has been flashed with TWRP img before attempting 'factory reset' option? I based my questions thus far on the assumption that if it flashed successfully I would see only the 'factory reset' and 'reboot' options in the new recovery, but I see all 5 options as before flashing TWRP.
skay said:
Anyone know of a way to determine if recovery has been flashed with TWRP img before attempting 'factory reset' option? I based my questions thus far on the assumption that if it flashed successfully I would see only the 'factory reset' and 'reboot' options in the new recovery, but I see all 5 options as before flashing TWRP.
Click to expand...
Click to collapse
It's been a long time (over a year) since I last used TWRP on my G3 (which is now in the cell phone cemetery as it died last December), but I believe if you boot normally, hook your phone to your PC and use adb reboot-recovery, it SHOULD go straight into TWRP, but I could be wrong. Otherwise, factory reset is the only way to get to it. The normal "recovery" screen shows up first, from what I remember and you have to go that route to get to TWRP. You should always, always back up your phone whenever doing things like this anyways. I don't know if there is a way to "verify" that it is installed, so once again, backup everything first. Just in case.
Thanks for the help and the confirmation that the standard recovery is expected once it's installed. Based on videos I expected something different. But I tried it after backing up and it works fine. Now time to flash!!
Related
I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
mochamoo said:
I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
Click to expand...
Click to collapse
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Thank you. My s4 is rooted. I *think* that I have solved my issue. I was able to get it to go into Odin mode power+vol down. I didn't connect to a computer (am at work and all of my android tools are at home). I just cancelled out of Odin mode and it booted up just fine. Now I tried to go into recovery again and got the same error as above and was able to get out of it the same way. I was able to go into ROM manager and flash regular non-touch CWM recovery and was able to boot to it without issue.
I suspect that my flash of the touch via terminal emulator didn't work right. Can anyone who has done it this way let me know how long the flash should take? I was at the su prompt and entered the dd line above (copy and pasted to avoid typos). It appeared to do something...there were some numbers maybe 5 or 6 per line and then it went back to the prompt so thought it was done. This didn't take it more than about 15 seconds to do. What should I see here?
I know that I can just flash it via ROM manager but wanted to be able to do it myself without rom manager and also be able to flash the latest twrp img if I want to (goo.im seems broken at the moment). Maybe I will try to do it via Odin later.
TIA.
you rock
I just got this same error and your steps worked perfect
Same problem except on i545vrufnk1
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Hello, I went to flash a recovery package with flashify and got the black screen with kernel fail. I was on the latest nk1 kernel.
please help
Hi! I'm really sorry to revive such an ancient thread but I've a similar problem.
I tried to use the dd command to update TWRP and wound up at this spot, but I was running a custom 5.1.1 system (jflte dev something or other from oct 2014 - recovery needed to be updated in order to install 7.1.1). So I tried to ODIN back to the old bootloader because I read it may have just become locked again, and now the system seems broken or missing, I'm not sure which. Phone no longer boots into the system and I get this error at recovery, so I'm hoping that if I flash an older factory image onto the phone, it'll restore it.
My question is, if I flash a stock image onto the phone, will it overwrite the bootloader and make my custom recovery dreams impossible? I went as far as to transplant the insides of this phone into a replacement when it first broke to maintain my MDK bootloader, so I'm really hoping I didn't **** myself here.
----
Edit:
So I've fixed my phone! The whole ordeal wasn't too too bad, but it was somewhat time consuming and difficult to divine on my own.
Now, I realize now I may have actually flashed the wrong .img file, which may have caused this whole issue. I'm actually not certain, because through the method that I fixed this problem with, I was able to flash what I would later find out was an incorrect .img for the recovery (jfltexx instead of jfltevzw ) but it did work properly, and I only found out when I got an error on trying to install the LineageOS zip.
I tried a bunch of things, but the one that worked was converting a twrp .img file to a .lok (loki) file. At the time of this writing, it happens that there's a bug in the latest twrp version that also prevents you from installing the system, but downgrading back to an older version will work, and I assume after 3.1.2 the bug will be fixed.
In order to do this, I wiped the system back to an MDK 4.2.2 system image I found here: https://forum.xda-developers.com/showthread.php?t=2301259
(dead link? Here's an archive: https://archive.is/LDnaY - I hit a bunch of dead links when I was figuring this process out and it was frustrating)
which preserved the mdk bootloader (because flashing anything newer than this will lock the bootloader, I've been told. I didn't dare try.)
I rooted that image by downgrading to the prerelease kernel and using motochopper to root, then upgraded back to the mdk kernel.
Then I grabbed the loki_tool from this thread:
https://forum.xda-developers.com/lg-g2/general/guide-how-to-flash-cwm-6-0-4-4-lokitool-t2813514
(Dead link? Here's an archive: https://archive.is/F7k29 )
and used a twrp .img file to create the recovery.lok file
Flashing through this method restored my custom recovery, and also made the samsung unlocked padlock bootscreen go away (I miss it already!). Having Android 7.1.2 on this phone is quite a treat though!
Hope that anyone else who winds up here in the future finds this useful! And I hope those links
This quick guide explains how to root the LG G2, install latest recovery and backup and restore modified partitions. I've tested it personally with the D802 32GB version D80220h but works also with other G2 models. Just choose the proper version on each step.
1) Root the LG G2 using ioroot, which is the only known method for Kitkat 4.4.2
[ROOT] Root your G2 [ATT|VZW|TMO|KT|RGS|BELL|TELUS|OPEN] [Yay!]
IORoot25
There you can see all supported G2 models. You need to connect the phone to a computer with the LG drivers installed, so the phone is recognized and you can run the script inside ioroot. Then check that you are root on the phone using simple apps like Root Checker.
2) Backup the 4 partitions modified by AutoRec (requires root)
AutoRec leaves 4 partitions modified after running it, as stated here
bender_007 said:
^ aboot, boot, laf + recovery
Click to expand...
Click to collapse
So it would be wise to backup them in case you want to have the original boot and recovery without having to flash the stock rom again.
You can use Terminal emulator for android (easiest way) or do it remotely from your computer using SSH Server. The keyboard Hacker's Keyboard is recommended for auto-completion.
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot-g2
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot-g2
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf-g2
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery-g2
Now you have the 4 partitions backed up on your sdcard and you can copy them elsewhere.
3) Install twrp recovery using the AutoRec apk (requires root)
AutoRec - KitKat recovery installer
AutoRec will perform some operations and install twrp 2.7.0.0 in this case.
WARNING: if you run AutoRec you will lose the knock on feature to wake up the phone double touching on the screen. You can regain the feature at any moment if you restore later the 4 modified partitions (but you will lose custom recovery).
4) Flash recovery update or install a new one
AutoRec installs TWRP 2.7.0.0. You can install a newer version or cwm instead of twrp. Download the zip for your device, put it on the sdcard and flash it from recovery. TWRP is the recommended one.
twrp2 from Techerrata (a lot of g2 versions)
[RECOVERY] CWM D802/F320(K/L/S)/ATT/VZW [v6.0.4.4][CACHE][LOKI][OTG][ZIP][CN/EN]
* Reboot to recovery
To enter recovery on the D802 after AutoRec run "adb reboot recovery" from your computer with the phone connected, or power off the phone, push power+vol down and when the logo appears release the press again both buttons. Stock rom may not allow you to enter recovery or different models may have different key combinations.
* Restore the 4 modified partitions
Just interchange "if" with "of". You will regain the knock on feature if you had it on stock.
Code:
su
dd of=/dev/block/platform/msm_sdcc.1/by-name/aboot if=/sdcard/aboot-g2
dd of=/dev/block/platform/msm_sdcc.1/by-name/boot if=/sdcard/boot-g2
dd of=/dev/block/platform/msm_sdcc.1/by-name/laf if=/sdcard/laf-g2
dd of=/dev/block/platform/msm_sdcc.1/by-name/recovery if=/sdcard/recovery-g2
nice guide, just one thought though, isn't using the bumped recovery preferable these days?
meangreenie said:
nice guide, just one thought though, isn't using the bumped recovery preferable these days?
Click to expand...
Click to collapse
You mean if it's better the stock recovery? Well it is in terms of security, in case your phone gets stolen nobody can enter in recovery mode and dump a cwm backup.
Goodone! thx sharing!
In my variant(Sprint G2):
ZVE cannot rooted with any tool but Stump, using other way may cause Stump refuse to work. so plz note it.
Flashing cloudykernel (etc) can regain knock on.
LS89 said:
Goodone! thx sharing!
In my variant(Sprint G2):
ZVE cannot rooted with any tool but Stump, using other way may cause Stump refuse to work. so plz note it.
Flashing cloudykernel (etc) can regain knock on.
Click to expand...
Click to collapse
I don't get it, I have knock on working perfectly despite doing all this from a different guide, no matter if its stock kernel or dorimanx.
I used ioroot then autorec, still have knock on working perfectly well.
The only time I lost it was right after installing dorimanx, but even then a simple Touch Firmware upgrade using hidden menu brought it right back.
Its explained in detail in the Dorimanx thread.
My only current issue right now is, that flashing a newer TWRP zip fails, but I haven't felt the need to have the newest one, so I just left it alone.
Did I miss anything? (I'm on a VS980 btw, 24a stock with dorimanx kernel)
Xer0 WindKey said:
I don't get it, I have knock on working perfectly despite doing all this from a different guide, no matter if its stock kernel or dorimanx.
I used ioroot then autorec, still have knock on working perfectly well.
The only time I lost it was right after installing dorimanx, but even then a simple Touch Firmware upgrade using hidden menu brought it right back.
Its explained in detail in the Dorimanx thread.
My only current issue right now is, that flashing a newer TWRP zip fails, but I haven't felt the need to have the newest one, so I just left it alone.
Did I miss anything? (I'm on a VS980 btw, 24a stock with dorimanx kernel)
Click to expand...
Click to collapse
with rooted LS980 ZVE stockfireware, use AutoRec get TWRP will lose KnockOn.
it's very funny, Touch Firmware upgrade just fix KnockOn,(it will be kinda "lag")
annnnnnd , KnockCode will be "KnockOn+KnockCode",
first, two tap to lignt up screen (no only hit the same point, but also two point not too far away )
fix it by flashing CloudyKernel , DorimanxKernal...
or upgrade bootloader(no tested, if just get TWRP,only flash bumped recovery.img, no more downgrade bootloader)
your issue sounds weird, did you try to flash img by flashify the app?
Is ioroot the only way to root 20h? I read that stump root also still works and that's a one click PC free solution. I haven't tried it myself yet though.
stefan1975 said:
Is ioroot the only way to root 20h? I read that stump root also still works and that's a one click PC free solution. I haven't tried it myself yet though.
Click to expand...
Click to collapse
Yes can confirm stump root works on 20h tried it on my unrooted d802
few days before i restart my phone into recovery mode as a result my entire data go deleted as it factory reset my phone (first time i have noticed that by entering recovery mode phone got factory reset)
however now i have managed to installed twrp but now scared into recovery mode as i am not sure it was successfully installed or not.. IF NOT then again my phone will be factory reset
kindly any one let me know how do i check that my phone has TWRP or not
First, more information. What version of the stock ROM are you on (10B, 12B, etc) and what way did you install TWRP?
You can always use the superuser terminal commands in @bweN diorD 's stickied thread in General to pull an .IMG of your currently installed recovery, then you can use am Android app like @scary alien 's AFV / Android File Verifier to check the MD5 hash of what you pulled and compare it to the MD5 of what you flashed.
10b and used twrp manager from playstore
The rest of process u mentioned was gone above my head.. Kindly let me know easy way any software which cal tell me twrp installed or not
komalsaeed said:
10b and used twrp manager from playstore
The rest of process u mentioned was gone above my head.. Kindly let me know easy way any software which cal tell me twrp installed or not
Click to expand...
Click to collapse
There's no other way other than what I told you unless TWRP Manager reports what's installed. TWRP Manager has never failed to install TWRP for me on any ROM that's supported, which includes 10B, not sure about 12B, but definitely not any newer, 23C, 24B or 35B. If you're on 10B, you installed TWRP Manager, gave it root permissions and told it to install TWRP for the VS985 I wouldn't have any doubt that it worked. I've done it in that same scenario several times.
To clarify not working on 23C and above, it will actually install TWRP just fine on any of them. You just either won't be able to use it, or you won't be able to boot the ROM after, or both, because of the secure boot error, but that has nothing to do with TWRP itself.
@bender_007 's autorec app will install an older version of TWRP just fine on 23C or 24B. The one in the Play Store is ONLY for 23C and if you expand the description of the app, he gives a link to his XDA thread in the non-Verizon G3 General section, where has separate versions for 23C and 24B. Once you use his app on 23C or 24B, you can flash the latest version from the older version.
Can confirm about autorec, I used it on version 24B to install TWRP, but I accidentally installed it in 35B and got the secure boot error. I was able to boot to recovery right before that however, so if this happens to you, you can boot to TWRP using the Volume Down + Power button trick to get into custom recovery and choosing "Factory data reset" which won't delete your data, and connect your phone to a PC to move your stuff out before restoring it.
Anyway, if you're comfortable with ADB I have successfully flashed TWRP with these instructions
techhexium said:
Anyway, if you're comfortable with ADB I have successfully flashed TWRP with these instructions
Click to expand...
Click to collapse
You were able to use ADB to install TWRP on 35B or 24B? I'm trying to get it on 35B rooted with Kingroom and replaced with SuperSU and keep getting the Secure Boot Error.
wishx said:
You were able to use ADB to install TWRP on 35B or 24B? I'm trying to get it on 35B rooted with Kingroom and replaced with SuperSU and keep getting the Secure Boot Error.
Click to expand...
Click to collapse
thats because it cant be done directly without changing other partitions too.
bweN diorD said:
thats because it cant be done directly without changing other partitions too.
Click to expand...
Click to collapse
I should have rephrased that. Did you successfully install TWRP on 35B or only 24B?
wishx said:
I should have rephrased that. Did you successfully install TWRP on 35B or only 24B?
Click to expand...
Click to collapse
i havent tried, but i dont see why it couldnt be done the same way we did with the first L build before all the automated methods were made.
bweN diorD said:
i havent tried, but i dont see why it couldnt be done the same way we did with the first L build before all the automated methods were made.
Click to expand...
Click to collapse
You wouldn't happen to know how people are installing TWRP on 35B without getting Secure Boot Errors, would you?
wishx said:
You wouldn't happen to know how people are installing TWRP on 35B without getting Secure Boot Errors, would you?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=64088875
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
ganiman said:
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
Click to expand...
Click to collapse
Your understanding of TWRP is right. Basically, we dd the twrp image with OS 4.5.3 bootloaders (the only bootloaders that will boot unsigned recovery) and then before leaving TWRP flash back (almost) current bootloaders and recovery.
You should be able to adb-sideload the OS 5.1.2 update to fix the freeze. Was device rooted before it updated? Do you know what OS it was on? If you have adb access while device is frozen, run these commands for current OS info:
adb shell getprop ro.build.version.fireos
adb shell getprop ro.build.version.number
No CM12 available. Mostly-working CM11 is here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138
BTW, I assume you tried wiping cache and/or factory reset in recovery. If not, I'd do that first.
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
undesputed said:
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
Click to expand...
Click to collapse
Reinstallt it try this TWRP http://www.mediafire.com/download/15g5i63gke9ddgp/kiwi_twrp_3-21_recovery.img its version 3.0.2.0 (Most recent)
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
mooms said:
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
Click to expand...
Click to collapse
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Arobase40 said:
Do you mean 3.0.2.0 is newer and supports more partitions than 5-14 ???
Click to expand...
Click to collapse
Their both 3.0.2.0 the one I just posted has more features
Sent from my SM-N920T using Tapatalk
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
@clsA
frp is labeled as "UNLOCK" as oppsed to bootloader labeled as "UNLOCKED".
If it's just about removing my google account, will this be resolved the next time I do a factory reset?
Nevertheless, thank you so much for the command fastboot boot twrp.img, I realized that that was what I had used the last time.
I'm currently able to boot into TWRP this way. Awesome!
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
mooms said:
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
Click to expand...
Click to collapse
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
clsA said:
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
Click to expand...
Click to collapse
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
mooms said:
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
Click to expand...
Click to collapse
USB-OTG works flawlessly on the 5-14 version I was not able to use it with the newer one @yuweng posted in his guide
the screen shots show all the partitions it's able to work with
Arobase40 said:
I thought 3.0.2.0 was just an interim version between twrp_2-27 and twrp_5-14... ^^
Click to expand...
Click to collapse
your confusing TWRP versions with TWRP release dates
2-27 and 5-14 are release dates where as 3.0.2.0 is the version of TWRP not the date
the first version of TWRP for this device was actually 2.8.7.0 and was released on 2-16-2016
Same issue
Hey so I have the same exact issue umm did you ever resolve this problem becuSe I can't seem to crack it and it's a bit frustrating cuz by no means am I a pro but coming from using the OnePlus one the OnePlus 2 the OnePlus x and the Nexus 6 rooting them and restoring them after many failed attempts resulting in bricking my phone and even eventually unbrick them I do know a thing or two and I am stumped please help you are the only other person in this world other then my self that seems to be having this issue if you don't mind would you be so kind and email gmail me cuz I don't use or check this forum often thanks millerfamily805
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
Can it be used with other honor devices?
Got my answer... Thanks...
Sent from my PLK-L01 using XDA Labs
It depend on the device