Hi, I a have a T-Mobile P769 and my issue pertains to unlocking and achieveing a non-inverted (non-mirrored) recovery.
Here is what I have done so far:
1. Unlocking
Using kuma's guide: http://forum.xda-developers.com/showthread.php?t=2601480&highlight=recovery, I was been able to unlock the bootloader, load his themed ROM and have the non-mirrored screen, non-mirrored recovery and touch fixed.
Lets, call this State 1:
Code:
kuma's themed ROM - kumakan 3.4
non-mirrored logo
non-mirrored CWM 0.0.4.5 Touch
non-mirrored system
fixed touchscreen
unlocked bootloader
rooted
However I think the non-mirrored recovery is a 2nd-init recovery and my original recovery is also present, correct?
Because I didn't like the ROM and wanted to move to CM 11 for my device I proceeded to step 2 below.
2. Installing CM 11 - First attempt
I flashed this ROM: http://forum.xda-developers.com/showthread.php?t=2728404, from the non-mirrored ROM, and got error, "Status 7", which I believe was because of an older recovery or 2nd-init recovery?
3. Installing CM 11 - Second attempt
Anyhow, I rebooted and got a dead android with a read triangle. I then proceeded to use Lelus' tool: http://forum.xda-developers.com/showthread.php?t=2292828 to get to fastboot and flash CWM 6.0.4.8.
This recovery was however mirrored, I then flashed the CM 11 ROM, which flashed successfully along with the required GApps.
Let's call this State 2:
Code:
CM 11 - 20140902
non-mirrored logo
mirrored CWM 6.0.4.8 non-toruch
non-mirrored system
wonky touchscreen
unlocked bootloader
rooted
3. Fixing toushcreen
So to fix the messed up touchscreen I booted into recovery, and flashed Lelus' "Fix_Touch-V20F.zip", what this did was give me another dead android and again I had to flash recovery using Lelus' fastboot.
I then used this method: http://forum.xda-developers.com/showpost.php?p=39268215&postcount=24 to fix the issue but the path the sdcard was incorrect for the CM 11 setup, which I change to "/storage/sdcard1/" from "/sdcard/external_sd/" and now the touch was fixed.
Let's call this State 3:
Code:
CM 11 - 20140902
non-mirrored logo
mirrored CWM 6.0.4.8 non-touch
non-mirrored system
fixed touchscreen
unlocked bootloader
rooted
4. Fixing recovery
Now, my issue is that the recovery is mirrored and I have noticed if I enter recovery and even if I don't do anything in it except just reboot, then the touchscreen becomes wonky again.
I want to know if there is anyway to have the recovery non-mirrored as well as have the touchscreen fixed once and for all permanently. Or is this not possible?
Issue fixed, using modded recovery based on @kuma82's work and hints.
I installed the CWM 6.0.4.8 No-Touch that I modded (Can be found here) and then flashed the "cwm_ts_fix_p769.zip", now no issue, can use recovery perfectly normal and no more worky screen. Yey!
State 4 achieved:
Let's call this State 3:
Code:
CM 11 - 20140902
non-mirrored logo
non-mirrored CWM 6.0.4.8 non-touch
non-mirrored system
fixed touchscreen
unlocked bootloader
rooted
Look for the cwmtouchfix zip in the files to put on SD card in
http://forum.xda-developers.com/showthread.php?t=2584997
And flash it via recovery
Sent from my Nexus 7 using XDA Free mobile app
BlueKnightedDragon said:
Look for the cwmtouchfix zip in the files to put on SD card in
http://forum.xda-developers.com/showthread.php?t=2584997
And flash it via recovery
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Nope, didn't fix it.
Issue fixed, using modded recovery based on @kuma82's work and hints.
I installed the CWM 6.0.4.8 No-Touch that I modded (Can be found here and then flashed the "cwm_ts_fix_p769.zip", now no issue, can use recovery perfectly normal and no more worky screen. Yey!
mohitgarg said:
Issue fixed, using modded recovery based on @kuma82's work and hints.
I installed the CWM 6.0.4.8 No-Touch that I modded (Can be found here and then flashed the "cwm_ts_fix_p769.zip", now no issue, can use recovery perfectly normal and no more worky screen. Yey!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=51885331&postcount=2
you missed this
oh and congratulations on unlocking..
kuma82 said:
http://forum.xda-developers.com/showpost.php?p=51885331&postcount=2
you missed this
Click to expand...
Click to collapse
Actually I didn't, while searching for a solution to my problem, I stumbled onto that thread, and saw someone request the recovery for P769, I wondered what could be different, and the mirror issue was mentioned as well, so I give it a go, and then I read what fixed it, so I said, why not try the other recoveries this way.
Thanks a lot for that recovery and the hint on using Bob's CWM's kernel with the ramdisk of other recoveries.
Help
Hi, I have a t-mobile p769 too and it says it's from april 2013, I did all the process and it doesn't work, when I reboot to unlock bootloader nothing happens!!! :crying:
I appreciate your help
Really all you can do is try to do it again from the beginning and hope it works or go back to stock and fix your touch screen. It's hit or miss with these phones since there is no guarantee it will unlock
Sent from my Nexus 7 using XDA Free mobile app
Did you wait for 30-45mins after booting into the Euro 20B? A lot of people don't take that step seriously.
mohitgarg said:
Did you wait for 30-45mins after booting into the Euro 20B? A lot of people don't take that step seriously.
Click to expand...
Click to collapse
Yes I have and I turned on the mobile data and wifi and I put a movie on youtube for 1 hour just to make sure.
BlueKnightedDragon said:
Really all you can do is try to do it again from the beginning and hope it works or go back to stock and fix your touch screen. It's hit or miss with these phones since there is no guarantee it will unlock
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
That's what I being doing, and I think I'm going to make a backup just to not installing all apps again I think I'm not going to give up until this is unlocked
Related
So first off let me say that clearly i'm not any sort of expert. I was fooling around with different roms for my htc one and read somewhere that a OTA to 4.4 was available for the stock rom. After reverting to the stock rom (official release) I found that I could not install the update because of the version of TWRP I had installed. Apparently it was not current enough. Anyway I installed clockwork mod only to find out that (again) i installed an older version. Sooooo I installed the newest version or TWRP I could find aaaaannnndddd..... Bootloop. When I try to enter recovery it shows the clockworkmod Icon then reboots and stays that way until the battery dies (which is built in of course and not removable). Any help would be much appreciated. Thanks!
Search for your device first before making a thread
Officerfatboy said:
So first off let me say that clearly i'm not any sort of expert. I was fooling around with different roms for my htc one and read somewhere that a OTA to 4.4 was available for the stock rom. After reverting to the stock rom (official release) I found that I could not install the update because of the version of TWRP I had installed. Apparently it was not current enough. Anyway I installed clockwork mod only to find out that (again) i installed an older version. Sooooo I installed the newest version or TWRP I could find aaaaannnndddd..... Bootloop. When I try to enter recovery it shows the clockworkmod Icon then reboots and stays that way until the battery dies (which is built in of course and not removable). Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Here is the link of HTC One section on XDA. Head to that and choose from available ROMs :
HTC One - XDA
Enjoy..!!
Java Baba said:
Here is the link of HTC One section on XDA. Head to that and choose from available ROMs :
HTC One - XDA
Enjoy..!!
Click to expand...
Click to collapse
Well the issue is I cant install a working rom becuase my recovery doesnt work either.
Officerfatboy said:
Well the issue is I cant install a working rom becuase my recovery doesnt work either.
Click to expand...
Click to collapse
its not even close to a brick. rest you should find out .
or
Just call it a brick and buy a new phone.
Can you install twrp through fastboot on HTC devices?
If so, reinstall it.
Sent from my Nexus 5 using xda premium
setup ADB and FASTBOOT first
Officerfatboy said:
Well the issue is I cant install a working rom becuase my recovery doesnt work either.
Click to expand...
Click to collapse
Well okay...
First of all head to this link and download the desired recovery image from the list (with or without TOUCH- both are equally functional) :
http: // www clockworkmod com/ rommanager
( REMOVE SPACES IN BETWEEN THE LINK TEXT)
Go to fastboot mode (from ur device):
Switch off the device, press & hold Volume down + power key simultaneously till you get a special mode.
This special mode is nothing but a Bootloader. In bootloader, select fastboot mode option (using Volume keys & power button)
Now put the recovery image which u have downloaded into the working folder of ADB.
Now Check u are in fastboot mode or not:
Code:
fastboot devices
If your device is listed with above code then enter this code in terminal:
Code:
fastboot flash recovery ----------.img
replace the ------ with your recently downloaded CWM recovery image filename i.e.recovery-clockwork-6.0.4.6-m7.img
All done...
Now Boot into recovery and Do whatever you want..!!
GL...!!
Pain-N-Panic said:
Can you install twrp through fastboot on HTC devices?
If so, reinstall it.
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
I didn't know you could do that! thanks! super fixed! : )
Just some things before we start. My Phone is the P769 and I'm a total noob.
Alright, I rooted my phone yesterday and then proceeded to download CWM, the app of course. So, when I went to setup a custom recovery, I picked from the options they had their, to which I picked the P760. Low and behold, I found it was a horrible failure when I rebooted into recovery because I got the security error...I think I soft-bricked it? Correct me if I'm wrong. Anyways, I just downloaded the LGSupport Tool and eventually fixed it.
So I think my question is, where can I get a custom recovery for the P769? Am I supposed to be looking for that in the first place? As you can see, I'm quite lost.
Is your bootloader unlocked?
Sent from my LG-P769 using XDA Free mobile app
BlueKnightedDragon said:
Is your bootloader unlocked?
Sent from my LG-P769 using XDA Free mobile app
Click to expand...
Click to collapse
Um...I want to say no.
Do you want custom recovery to flash themed stock roms or custom rom (like cm 11) cause for the latter you need to unlock bootloader first
Sent from my LG-P769 using XDA Free mobile app
BlueKnightedDragon said:
Do you want custom recovery to flash themed stock roms or custom rom (like cm 11) cause for the latter you need to unlock bootloader first
Sent from my LG-P769 using XDA Free mobile app
Click to expand...
Click to collapse
I have the cm 11 rom file and the gapps file. I just can't find the correct recovery on Rom manager to reboot into so I can install the files
You will first have to unlock your boot loader in that case, follow all the instructions from the first ONLY: http://forum.xda-developers.com/showthread.php?t=2601480
Then, do the follwong:
1. Have one of the recoveries from here: http://forum.xda-developers.com/optimus-l9/development/p769-recoveries-p769-mirror-issues-t2879854, CM11 and the required G.Apps on your SD card.
2. Navigate (use a mirror if needed) through cwm, restore your choice of #1, and reboot into recovery again from the cwm (Under "advanced")
3. The new recovery should look different and not be mirrored, but the touch will be wonky, don't worry. Flash the CM11 and G.Apps. Do NOT reboot yet.
4. Then flash "cwm_ts_fix_p769.zip". reboot
Done!
I might get to writing a guide after my experience doing the exact same and getting my head around it for the past 2-3 days, but I have a very busy schedule, so I cna't promise anything. Besides, kuma82's guide is excellent.
mohitgarg said:
You will first have to unlock your boot loader in that case, follow all the instructions from the first ONLY: http://forum.xda-developers.com/showthread.php?t=2601480
Then, do the follwong:
1. Have one of the recoveries from here: http://forum.xda-developers.com/optimus-l9/development/p769-recoveries-p769-mirror-issues-t2879854, CM11 and the required G.Apps on your SD card.
2. Navigate (use a mirror if needed) through cwm, restore your choice of #1, and reboot into recovery again from the cwm (Under "advanced")
3. The new recovery should look different and not be mirrored, but the touch will be wonky, don't worry. Flash the CM11 and G.Apps. Do NOT reboot yet.
4. Then flash "cwm_ts_fix_p769.zip". reboot
Done!
I might get to writing a guide after my experience doing the exact same and getting my head around it for the past 2-3 days, but I have a very busy schedule, so I cna't promise anything. Besides, kuma82's guide is excellent.
Click to expand...
Click to collapse
Thank you soooo much. But unfortunately, I have one more question. How do I perform an offline flash?
Here you go: http://forum.xda-developers.com/showthread.php?t=2085344
mohitgarg said:
You will first have to unlock your boot loader in that case, follow all the instructions from the first ONLY: http://forum.xda-developers.com/showthread.php?t=2601480
2. Navigate (use a mirror if needed) through cwm, restore your choice of #1, and reboot into recovery again from the cwm (Under "advanced")
Click to expand...
Click to collapse
First off, thank you sooo much. I got this far but right now I'm super confused. How do I restore? Is there an option to restore? Can you explain it to me a bit more specifically if you can?
Also, I didn't know I needed a literal mirror lol.
Ownage516 said:
First off, thank you sooo much. I got this far but right now I'm super confused. How do I restore? Is there an option to restore? Can you explain it to me a bit more specifically if you can?
Also, I didn't know I needed a literal mirror lol.
Click to expand...
Click to collapse
Sorry for the vague instructions, first, let me ask, is your phone successfully unlocked? Got that fastboot menu on the phone somewhere along the process? Or you can try connect in SW DL mode (Power off phone, hold Vol+ and plug in USB, should see "Unlocked bootloader").
If yes, then you should be on the European 20B with mirror screen and wonky touchscreen, follow the below instructions:
1. Have one of the recoveries from the link I posted AND CM11 (I am using dhiru's version) AND G.Apps AND cwm_ts_fix_p769.zip on to your external SD.
2. Run Start.cmd, push files (Fix_Touch-V20F.zip & MetroPCS-V10E-Radio.zip) to External SD using kuma82's tool
3. Install BusyBox and reboot into the inverted CWM recovery
4. Navigate (use a mirror if needed) through CWM, flash the recovery of your choice AND choose to reboot to recovery from within the recovery
5. (CWM should not be inverted now). Install the files in the given order without a reboot in between:
a. CM11
b. G.Apps
c. Fix_Touch-V20F.zip
d. Recovery you flashed in step 4 - This is critical, as Fix_Touch-V20F.zip installs an older recovery which may cause soft-brick, thus you need to install the recovery again
e. cwm_ts_fix_p769.zip[/INDENT]
6. Reboot
mohitgarg said:
Sorry for the vague instructions, first, let me ask, is your phone successfully unlocked? Got that fastboot menu on the phone somewhere along the process? Or you can try connect in SW DL mode (Power off phone, hold Vol+ and plug in USB, should see "Unlocked bootloader").
If yes, then you should be on the European 20B with mirror screen and wonky touchscreen, follow the below instructions:
1. Have one of the recoveries from the link I posted AND CM11 (I am using dhiru's version) AND G.Apps AND cwm_ts_fix_p769.zip on to your external SD.
2. Run Start.cmd, push files (Fix_Touch-V20F.zip & MetroPCS-V10E-Radio.zip) to External SD using kuma82's tool
3. Install BusyBox and reboot into the inverted CWM recovery
4. Navigate (use a mirror if needed) through CWM, flash the recovery of your choice AND choose to reboot to recovery from within the recovery
5. (CWM should not be inverted now). Install the files in the given order without a reboot in between:
a. CM11
b. G.Apps
c. Fix_Touch-V20F.zip
d. Recovery you flashed in step 4 - This is critical, as Fix_Touch-V20F.zip installs an older recovery which may cause soft-brick, thus you need to install the recovery again
e. cwm_ts_fix_p769.zip[/INDENT]
6. Reboot
Click to expand...
Click to collapse
Alright, I kinda softbricked on step 4. I believe my bootloader is unlocked since I'm in CWM, right? I'm going to start from the top again, but I have a bit more confidence this time around.
On step 4 of flashed "CWM 6.0.4.8 No-Touch for P769" and then rebooted in recovery, the option under advance and got a secruity error, or a soft brick...same thing I believe. I dunno what I did wrong.
Check if your are unlocked, try going into software download mode.
Alright, when I go into SW DL, it doesn't say unlocked bootloader, it just shows what it normally shows. But I have the mirror screen and wonky touchscreen...did I miss a step or something? I did everything I believe.
Ownage516 said:
Alright, when I go into SW DL, it doesn't say unlocked bootloader, it just shows what it normally shows. But I have the mirror screen and wonky touchscreen...did I miss a step or something? I did everything I believe.
Click to expand...
Click to collapse
There are steps missing after step 3 you need to flash radio in the inverted recovery and then reboot and the tool and run the unlock command after 45 minutes and press vol + to unlock and then flash a recovery while you're phone is still in fastboot mode (this is the mode your phone is in after you press the vol + to unlock) by using the command fastboot flash recovery (insertrecoveryname).img
Alright, after I push both files to the sd card, I try to install the radio zip, but it fails. Does the problem lie there in?
Wait, did you follow everything from the first post in this thread as I mentioned earlier: http://forum.xda-developers.com/showthread.php?t=2601480
If yes, then what happened after step 8?
Once you do that, THEN you have to do what is outlined in this post: http://forum.xda-developers.com/optimus-l9/general/noob-little-guidance-t2878048/post55588776
mohitgarg said:
Wait, did you follow everything from the first post in this thread as I mentioned earlier: http://forum.xda-developers.com/showthread.php?t=2601480
If yes, then what happened after step 8?
Once you do that, THEN you have to do what is outlined in this post: http://forum.xda-developers.com/optimus-l9/general/noob-little-guidance-t2878048/post55588776
Click to expand...
Click to collapse
Is there honestly something that should be different? Because, when I press the option to unlock the bootloader, it just reboots and what...almost identical with the results of step 6.
Am I playing with my phone wrong? What am I really supposed to do to it for 45 minutes...I want to say there in lies my problem.
Excuse me as I head to class with super inverted phone, lol.
Yes, you have to wait about 45 mins as mentioned in the step, that is why we said follow it to the T.
so.. i have an Lg d618 rooted and running official L 5.0.2
i wanted to flash a custom recovery so i started with patching bootloader using this thread
http://forum.xda-developers.com/g2-mini/development/bootloader-d620-d618-t3127819
then i installed TWRP using this thread
http://forum.xda-developers.com/g2-mini/development/recovery-lg-g2-mini-d618-v10c-t2854493
by flashing the img file with Flashify
the the phone rebooted and i got the TWRP interface
http://img.wonderhowto.com/img/39/2...only-custom-recovery-youll-ever-need.w654.jpg
and when i press reboot i got this
http://img.wonderhowto.com/img/38/1...only-custom-recovery-youll-ever-need.w654.jpg
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I got that android logo like i have no recovery installed
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
i tried this solution http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ and it didn't help
dibik said:
so.. i have an Lg d618 rooted and running official L 5.0.2
i wanted to flash a custom recovery so i started with patching bootloader using this thread
http://forum.xda-developers.com/g2-mini/development/bootloader-d620-d618-t3127819
then i installed TWRP using this thread
http://forum.xda-developers.com/g2-mini/development/recovery-lg-g2-mini-d618-v10c-t2854493
by flashing the img file with Flashify
the the phone rebooted and i got the TWRP interface
http://img.wonderhowto.com/img/39/2...only-custom-recovery-youll-ever-need.w654.jpg
and when i press reboot i got this
http://img.wonderhowto.com/img/38/1...only-custom-recovery-youll-ever-need.w654.jpg
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I got that android logo like i have no recovery installed
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
i tried this solution http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ and it didn't help
Click to expand...
Click to collapse
Followed you from the other spot...
It sounds like Flashify plunked recovery on your boot/kernel partition (assuming your recovery you described is still stock - that is - Andy laying down with the front panel open). So, I would suggest to ADB push your official L 5.0.2 boot.img while in TWRP and flash that (to boot), and you should be golden.
Also, from my perspective it's hard for me to say your bootloader is acting up, as I have a different LG device and it's bootloader does not have fastboot. It's front-end is only a shim that makes you factory reset to get into recovery mode (it's only function).
Hope this helps.
OfficerJimLahey said:
Followed you from the other spot...
It sounds like Flashify plunked recovery on your boot/kernel partition (assuming your recovery you described is still stock - that is - Andy laying down with the front panel open). So, I would suggest to ADB push your official L 5.0.2 boot.img while in TWRP and flash that (to boot), and you should be golden.
Also, from my perspective it's hard for me to say your bootloader is acting up, as I have a different LG device and it's bootloader does not have fastboot. It's front-end is only a shim that makes you factory reset to get into recovery mode (it's only function).
Hope this helps.
Click to expand...
Click to collapse
thank you Jim for the reply
well my problem is solved.. i just flashed my device with the Official KDZ file using LG flash tool in "normal flash mode not CSE"
my phone turned on normally and everything (apps, pictures, files, messages.... ) and all my data were still there so i did'nt loose a thing
i just lost the root acces and that won't be a prblm cause i can root it all over again
thanks again Jim ^^
dibik said:
thank you Jim for the reply
well my problem is solved.. i just flashed my device with the Official KDZ file using LG flash tool in "normal flash mode not CSE"
my phone turned on normally and everything (apps, pictures, files, messages.... ) and all my data were still there so i did'nt loose a thing
i just lost the root acces and that won't be a prblm cause i can root it all over again
thanks again Jim ^^
Click to expand...
Click to collapse
Did you still have TWRP installed after flashing the KDZ file normal mode? Is your bootloader still unlocked?
ShadowBlade_20 said:
Did you still have TWRP installed after flashing the KDZ file normal mode? Is your bootloader still unlocked?
Click to expand...
Click to collapse
no i didn't
i re-unlocked the bootloader and installed TWRP 2.8.7.0 and it worked like a charm and now i'm on CM 13
Having sanw problem. Been stuck here on att lg gflex for 3 months. Can u help me please? [email protected]
Sent from my C6740N using Tapatalk
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
hey all!
So this is a first for me... I've been rooting and playing with android for a very long time (going back to the g1 days) and this is the first time I've ever seen this.
So I was on an old version of CM and decided it was time to update finally. I had unrooted a long time ago, but was still running cm perfectly fine. I went to install a new version of recovery (so I could update) and now when I try to boot into recovery I just get the oneplus logo. Here's the strange part, the phone isn't soft bricked... I can still boot into android no problem.
Anyone else every seen this problem? Do I need to start over (unlock bootloader, root, recovery, rom)?
Anyone else ever seen this happen on Oneplus One or any other phone for that matter?
Thanks in advance!
Same Problem Here
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Click to expand...
Click to collapse
I tried it and I got the following error:
/system/bin/sh: wipe_misc: not found
Click to expand...
Click to collapse
I don't know what else to do now. Please help.
janc_z said:
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
I tried it and I got the following error:
I don't know what else to do now. Please help.
Click to expand...
Click to collapse
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
zbt1985 said:
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
Click to expand...
Click to collapse
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
janc_z said:
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
Click to expand...
Click to collapse
Lucky you!
I on the other hand can't connect via adb, only fastboot...