Related
And HERE it Is!!!! I'm too tired to make a long thread.. I need to sleep hahah I'll make a proper thread tomorrow if he doesn't..
quickist way... be bootloader unlocked and then boot the image in the image folder of the zip
Unzip the zip to your computer.
fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
Make sure it's fastboot boot.. not fastboot flash.
It will reboot, reboot again and then you're good
Now go buy chainfire a beer
http://download.chainfire.eu/596/CF-Root/CF-Auto-Root/CF-Auto-Root-victara-victaratmo-xt1095.zip
This is not a flashable zip
What state does the phone have to be in to fastboot? I get waiting for device in normal phone OS and in recovery.
I can adb reboot to recovery, so I know everything is set up PC wise.
From bootloader I get "cannot load _______.img : no error"
---------- Post added at 01:10 PM ---------- Previous post was at 01:04 PM ----------
Got it I think. Your command in the OP has it ending in .img not .zip
EDIT....still getting binary not installed. I've got to go to work, but idk why this is the first phone I've ever struggled with so many things. Could be because we still don't have ANY working official images.
---------- Post added at 01:13 PM ---------- Previous post was at 01:10 PM ----------
Got it. Had to unzip the file and flash the image like you said.... I read wrong my bad.
Thanks
graffixnyc said:
And HERE it Is!!!! I'm too tired to make a long thread.. I need to sleep hahah I'll make a proper thread tomorrow if he doesn't..
quickist way... be bootloader unlocked and then boot the image in the image folder of the zip
Unzip the zip to your computer.
fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
Make sure it's fastboot boot.. not fastboot flash.
It will reboot, reboot again and then you're good
Now go buy chainfire a beer
http://download.chainfire.eu/596/CF-Root/CF-Auto-Root/CF-Auto-Root-victara-victaratmo-xt1095.zip
This is not a flashable zip
Click to expand...
Click to collapse
Is the boot.img for Lollipop based on the .5 or .6 release?
BrokenWall said:
Is the boot.img for Lollipop based on the .5 or .6 release?
Click to expand...
Click to collapse
It's boot img agnostic.. meaning you boot this boot.img, it actually takes the current boot.img on the device and injects root into it. So it uses whatever boot.img is currently on the device. So if you are on the .5 kernel it should work, if you're on the .6 kernel it works
graffixnyc said:
It's boot img agnostic.. meaning you boot this boot.img, it actually takes the current boot.img on the device and injects root into it. So it uses whatever boot.img is currently on the device. So if you are on the .5 kernel it should work, if you're on the .6 kernel it works
Click to expand...
Click to collapse
Awesome, and I will make sure I give Chainfire some money, I will probably just pickup SU Pro
Didn't want to run into boot loop because it was meant for a particular kernel
Is it just for xt1095 or will also work with 1092?
Sent from my XT1092 using Tapatalk
blinkin said:
Is it just for xt1095 or will also work with 1092?
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
It was made for the 1095. You can give it a try and let us know. If it fails it doesn't screw up anything (I don't think, since in testing it failed for me many times before he got the bugs worked out) Theoretically it should work as I said it's boot.img
graffixnyc said:
It was made for the 1095. You can give it a try and let us know. If it fails it doesn't screw up anything (I don't think, since in testing it failed for me many times before he got the bugs worked out) Theoretically it should work as I said it's boot.img
Click to expand...
Click to collapse
Running Lollipop on XT1097, and rooted with this. Everything going good.
Thx u all
beelzebu said:
Running Lollipop on XT1097, and rooted with this. Everything going good.
Thx u all
Click to expand...
Click to collapse
Can confirm on XT1097. Man this is amazing!
Anyone has flashed twrp?
Anyway thank you all!
Thanks.
Is there a step-by-step for this? I never rooted any of my Note series phones, so it's been a while.
1. unlock bootloader from moto site (follow instructions there) ALL OF YOUR DATA WILL BE WIPED - BACKUP EVERYTHING FROM INTERNAL STORAGE
2. ensure that you have fastboot / mfastboot / android SDK installed and setup (including PATH)
3. enable usb debugging on your phone
4. ensure that you have the appropriate drivers for your device installed
5. reboot to bootloader
6. check to make sure you have the correct drivers installed
7. type fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
8. phone will reboot.
All of this is in the OP. good luck
Disclaimer
you alone are responsible for the health of your device, if you are at any point worried about causing damage, do not proceed. I will not buy you a new phone if you break yours.
byt3b0mb said:
1. unlock bootloader from moto site (follow instructions there) ALL OF YOUR DATA WILL BE WIPED - BACKUP EVERYTHING FROM INTERNAL STORAGE
2. ensure that you have fastboot / mfastboot / android SDK installed and setup (including PATH)
3. enable usb debugging on your phone
4. ensure that you have the appropriate drivers for your device installed
5. reboot to bootloader
6. check to make sure you have the correct drivers installed
7. type fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
8. phone will reboot.
All of this is in the OP. good luck
Disclaimer
you alone are responsible for the health of your device, if you are at any point worried about causing damage, do not proceed. I will not buy you a new phone if you break yours.
Click to expand...
Click to collapse
Muchas gracias! Here we go. I saw others had success with XT1097, so I'm going for it.
Working on XT1092 with XT1095 5.0 firmware
Any Canadians with a Telus model try this out? I believe Telus Moto X (2014) is XT1097 as well.
graffixnyc said:
And HERE it Is!!!! I'm too tired to make a long thread.. I need to sleep hahah I'll make a proper thread tomorrow if he doesn't..
quickist way... be bootloader unlocked and then boot the image in the image folder of the zip
Unzip the zip to your computer.
fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
Make sure it's fastboot boot.. not fastboot flash.
It will reboot, reboot again and then you're good
Now go buy chainfire a beer
http://download.chainfire.eu/596/CF-Root/CF-Auto-Root/CF-Auto-Root-victara-victaratmo-xt1095.zip
This is not a flashable zip
Click to expand...
Click to collapse
Thank u... It is working perfectly
We now need to wait for Exposed and the fun begins with a lollipop taste....
beelzebu said:
Running Lollipop on XT1097, and rooted with this. Everything going good.
Thx u all
Click to expand...
Click to collapse
You just ran these steps and good to go? no problems with modem/radio and or imei? I also have an xt1097 but I'm afraid to brick my beloved X in the process haha
JoaoGuiPan said:
You just ran these steps and good to go? no problems with modem/radio and or imei? I also have an xt1097 but I'm afraid to brick my beloved X in the process haha
Click to expand...
Click to collapse
Just need to backup modem fsb and pds and then flash tmo factory images, after that sideload de OTA, refresh your modem an from there you are good to go.
blyndfyre said:
Any Canadians with a Telus model try this out? I believe Telus Moto X (2014) is XT1097 as well.
Click to expand...
Click to collapse
Did you get lollipop running on your telus moto x? If so what process did you follow.
Jesus, will non unlocked ever get root?
Background
This is a list of radios for the Nexus 6 (shamu). With the new OTA release, some people may have better signals with the old radio or want to tinker with the new one so here is a list that will be updated to allow users to switch to their preferred radio/modem.
Radios are independent of Android version, use the radio that provides you the best signal. It varies from user to user, there is no best radio/modem Why? Different carriers, different locations, and more. There are so many factors that play into cellular signal so just because a particular radio is the best for someone doesn't mean its the best for you. We can obtain a consensus on which radio performs the "best" for the largest % of users though.
How to Flash?
1) Fastboot: Download the .img file below then flash it using Fastboot.
Code:
fastboot flash radio radio.img
Download (newest on top)
MPZ79M ("M" Developer Preview 2 - 07/10/2015)
MDM9625_104651.11.05.17R - flashable zip
Download: https://www.androidfilehost.com/?fid=24052804347771581
MPZ44Q ("M" Developer Preview - 05/28/2015)
MDM9625_104651.11.05.16R - flashable zip
Download: https://www.androidfilehost.com/?fid=23991606952615113
LYZ48E (5.1.1 T-Mobile - Extracted from OTA - 05/23/2015)
MDM9625_104649.09.05.14R - flashable zip
Download: https://www.androidfilehost.com/?fid=23991606952608807
LMY47D (5.1.0 Verizon - Extracted from factory image)
MDM9625_104446.01.02.98R -- fastboot
Download: https://www.androidfilehost.com/?fid=95916177934543195
LMY47D (5.1.0 OTA - 03/11/2015):
MDM9625_104446.01.02.95R -- flash in TWRP
Download: https://www.androidfilehost.com/?fid=95916177934540317
LRX22C (5.0.1 OTA - 12/10/2014): MDM9625_104335.118.02.55.04R
Download: https://www.androidfilehost.com/?fid=95851939534733360
LRX21O (5.0.0 OTA - XX/XX/2014): MDM9625_104335.118.02.55.03R
Download: https://www.androidfilehost.com/?fid=95851939534733359
great, needed, thread :good:
Nice job zephik
Sent from my NEXUS 6
Can you do fastboot method with terminal emulator...just broke pc lol
cwalker0906 said:
Can you do fastboot method with terminal emulator...just broke pc lol
Click to expand...
Click to collapse
No. Fastboot is only for the computer.
I'll have to do flashable zips later, if someone beats me to it I'll include it in OP and give credits.
Currently preparing for finals and this is all the time I have for now.
You'd need to write the radio to /dev/block/platform/msm_sdcc.1/by-name/modem via updater-script.
I thought it was "fastboot flash radio radio.img" ? (that's what I used)
Neejay said:
I thought it was "fastboot flash radio radio.img" ? (that's what I used)
Click to expand...
Click to collapse
Rename the file you downloaded from OP to "radio.img" (ensure its not actually radio.img.img).
Or type fastboot flash radio the-whole-radio-name.img. I personally rename to radio as its easier for me to type.
zephiK said:
Rename the file you downloaded from OP to "radio.img" (ensure its not actually radio.img.img).
Or type fastboot flash radio the-whole-radio-name.img. I personally rename to radio as its easier for me to type.
Click to expand...
Click to collapse
Yeah, I did the whole location+name, but in the OP you have "fastboot flash modem <name-of-modem>.bin" I wasn't sure if I was missing something, as I've never seen a .bin referenced. Hopefully this doesn't come off as being an asshole, I was just genuinely curious.
Neejay said:
Yeah, I did the whole location+name, but in the OP you have "fastboot flash modem <name-of-modem>.bin" I wasn't sure if I was missing something, as I've never seen a .bin referenced. Hopefully this doesn't come off as being an ******, I was just genuinely curious.
Click to expand...
Click to collapse
Oh you're right, I copy pasted the modem collection OP i had from the OnePlus One which they use .bin. I changed the extension to .img.
Sorry about that! its fixed now. And you're not being a... "you know", no need for me to say it as XDA doesn't appreciate that language
But yeah for <name-of-modem> is just a placeholder for depending what the user selects as a radio.
zephiK said:
Oh you're right, I copy pasted the modem collection OP i had from the OnePlus One which they use .bin. I changed the extension to .img.
Sorry about that! its fixed now. And you're not being a... "you know", no need for me to say it as XDA doesn't appreciate that language
But yeah for <name-of-modem> is just a placeholder for depending what the user selects as a radio.
Click to expand...
Click to collapse
Well I'm now soft bricked and don't know what to do. I used the "fastboot flash modem [modem name].img" command. I now realized from reading other threads I'm supposed to use "fastboot flash radio [radio name].img".
What do I do? The image fully flashed and now when I reboot it stick on the four colors swirling around splash screen just before boot up. I'm guessing there isn't a "modem" section for shamu? Just radio...
I tried going into TWRP and wiping cache. It says "E: Unable to mount '/firmware'".
xidium said:
Well I'm now soft bricked and don't know what to do. I used the "fastboot flash modem [modem name].img" command. I now realized from reading other threads I'm supposed to use "fastboot flash radio [radio name].img".
What do I do? The image fully flashed and now when I reboot it stick on the four colors swirling around splash screen just before boot up. I'm guessing there isn't a "modem" section for shamu? Just radio...
I tried going into TWRP and wiping cache. It says "E: Unable to mount '/firmware'".
Click to expand...
Click to collapse
I had the same problem with /firmware. I seem to just ignore it.
Go into fastboot and then just reflash the radio using fastboot flash radio radio.img and then reboot. If that doesn't work go back into TWRP and wipe Cache and Dalvik and then your phone should start up as it rebuilds the cache.
So far the flashable zips in the typical method I use are not sticking when it comes to the flashable zips.
xidium said:
Well I'm now soft bricked and don't know what to do. I used the "fastboot flash modem [modem name].img" command. I now realized from reading other threads I'm supposed to use "fastboot flash radio [radio name].img".
What do I do? The image fully flashed and now when I reboot it stick on the four colors swirling around splash screen just before boot up. I'm guessing there isn't a "modem" section for shamu? Just radio...
I tried going into TWRP and wiping cache. It says "E: Unable to mount '/firmware'".
Click to expand...
Click to collapse
try reflashing twrp
zephiK said:
Oh you're right, I copy pasted the modem collection OP i had from the OnePlus One which they use .bin. I changed the extension to .img.
Sorry about that! its fixed now. And you're not being a... "you know", no need for me to say it as XDA doesn't appreciate that language
But yeah for <name-of-modem> is just a placeholder for depending what the user selects as a radio.
Click to expand...
Click to collapse
zephiK said:
I had the same problem with /firmware. I seem to just ignore it.
Go into fastboot and then just reflash the radio using fastboot flash radio radio.img and then reboot. If that doesn't work go back into TWRP and wipe Cache and Dalvik and then your phone should start up as it rebuilds the cache.
So far the flashable zips in the typical method I use are not sticking when it comes to the flashable zips.
Click to expand...
Click to collapse
simms22 said:
try reflashing twrp
Click to expand...
Click to collapse
Hmm not sure which one worked but I think flashing TWRP again fixed it. I'm booted back up again and with the new modem. Thanks guys
Can we use Flashify to flash the modem image? Thanks.
slick4mitch said:
Can we use Flashify to flash the modem image? Thanks.
Click to expand...
Click to collapse
I tried thst but not sure if it worked. Can someone tell me the baseband version of the new radio please?
chris6278 said:
I tried thst but not sure if it worked. Can someone tell me the baseband version of the new radio please?
Click to expand...
Click to collapse
This is the 5.0 (LRX210) Radio
MDM9625_104335.118.02.55.03R
slick4mitch said:
Can we use Flashify to flash the modem image? Thanks.
Click to expand...
Click to collapse
Don't think you can use Flashify, that's for Zips, Recoveries and Boot Images ( Kernels )
You can use Fastboot, or if you're not comfortable with that you could use Wug's Toolkit and just download the latest modem to your PC and select Flash Modem under Advanced settings.... Select your downloaded modem file and within 1 minute the Toolkit will do it all for you.
chris6278 said:
I tried thst but not sure if it worked. Can someone tell me the baseband version of the new radio please?
Click to expand...
Click to collapse
You can't flash the radio using flashify.
The new base band ends with. 04R if it says that then you're on the newest radio.
Sent from my Nexus 6 using Tapatalk
zephiK said:
You can't flash the radio using flashify.
The new base band ends with. 04R if it says that then you're on the newest radio.
Sent from my Nexus 6 using Tapatalk[/QUOTE
Yea i know thanx
Click to expand...
Click to collapse
chris6278 said:
zephiK said:
You can't flash the radio using flashify.
The new base band ends with. 04R if it says that then you're on the newest radio.
Sent from my Nexus 6 using Tapatalk[/QUOTE
Yea i know thanx
Click to expand...
Click to collapse
Not seeing .04r , I flashed full build from Google website. Compared the 5.00 and 5.01 modems they are the same. May have done something wrong. Can anyone post a screenshot of the latest modem# .?
Click to expand...
Click to collapse
Due to this phone lacking support I believe users like me, Titokhan and Paul O'brian at MoDaCo need to consolodate knowledge in a single thread. Titokhan has been posting OTA links into the "How to root zuk z1" thread and they're dotted all over the place.
I discovered today that any one who followed his guide to install the CyanogenOS test build will not be able to install any OTA if you have flashed a ZIP like SuperSU through my TWRP image. I was attempting to flash an OTA zip and returned an error saying because System was modified by SuperSU and Avast Anti-Theft OTA updates are disabled.
We need to step back and look back at how this is going to be rectified having all this knowledge placed all over the forum is making work hard for ourselves.
heres the fix- 1) using twrp flash cm recovery (if you need if find it in full fastboot zip) 2)download the full signed version of cm not fastboot version 3)boot to cm recovery and select apply update and update from internal storage 4)reboot, otas will be accepted and work
radii said:
heres the fix- 1) using twrp flash cm recovery (if you need if find it in full fastboot zip) 2)download the full signed version of cm not fastboot version 3)boot to cm recovery and select apply update and update from internal storage 4)reboot, otas will be accepted and work
Click to expand...
Click to collapse
Nice, I just got your Hangouts message. I will write up and comprise all the OTA links into a Google Sheet.
data not lost, root is
radii said:
heres the fix- 1) using twrp flash cm recovery (if you need if find it in full fastboot zip) 2)download the full signed version of cm not fastboot version 3)boot to cm recovery and select apply update and update from internal storage 4)reboot, otas will be accepted and work
Click to expand...
Click to collapse
Where I can download full CM (fastboot & not fastboot version)?
thanks
damsolu said:
Where I can download full CM (fastboot & not fastboot version)?
thanks
Click to expand...
Click to collapse
Radii and I have comprised a spreadsheet containing all links to image downloads. Link will be here soon.
Sent from my Z1 using Tapatalk
Breadcrust said:
Radii and I have comprised a spreadsheet containing all links to image downloads. Link will be here soon.
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
perfect! thank so much for your attention and help
http://forum.xda-developers.com/zuk-z1/help/how-to-root-lenovo-zuk-z1-t3186978/page5
post 201 if you need it right now
Solution to OTA is live in the Android Development thread
radii said:
http://forum.xda-developers.com/zuk-z1/help/how-to-root-lenovo-zuk-z1-t3186978/page5
post 201 if you need it right now
Click to expand...
Click to collapse
Breadcrust said:
Solution to OTA is live in the Android Development thread
Click to expand...
Click to collapse
Thanks!
DISCLAIMER
I'm not responsible for any damage, bootloop, bricked or broken handsets.
Notice
The recovery can't be flashed to the handset with locked bootloader! Unlock it first!
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom and stock (with some remarks) ROMs to your device, repair broken file systems, and root your device.
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Update 29.03.2016
It's alive! First experimental working build published at internal 4pda Russian board.
Download
TWRP 3.0 M86 fastboot flashable image
TWRP 3.0 M86 flashable zip
Stock Recovery flashable zip
Unlocked BL flashable zip
Install
With BL unlocked reboot into fastboot mode and flash:
Code:
fastboot flash recovery TWRP_3.0_m86.img
Cautions
Before flashing stock rom with TWRP replace bootloader file with unlocked one inside rom archive!!!!
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)
JUST IN CASE this is an April fools.... I'll wait ?
Great mate, u've stolen my idea in the end, right ?!
Gooooood work, thank u very much ! Testing wip :highfive:
---------- Post added at 09:09 AM ---------- Previous post was at 09:04 AM ----------
Nein, first step doesn't work
Flashing unlocked BL through stock recovery, I get always the same result :
FIRMWARE CORRUPT
Click to expand...
Click to collapse
faust93 said:
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Click to expand...
Click to collapse
*Working fine
PYCON said:
Nein, first step doesn't work
Click to expand...
Click to collapse
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...
toms157 said:
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...
Click to expand...
Click to collapse
Ahahah yes yes but the purpose of BL_UNLOCKED.ZIP is to unlock bootloader. But in order to flash it correctly... we've to have the bootloader already unlocked
Damn it, it's really stupid, right ?
PYCON said:
Damn it, it's really stupid, right ?
Click to expand...
Click to collapse
Filename could lead to confusion, sure... It's needed for this :
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)"
Click to expand...
Click to collapse
Meanning flash 3 files from custom recovery without rebooting
Anyway this is not a catch-22, leaked beta from tutorial is the entry point
Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...
showofdeth said:
Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...
Click to expand...
Click to collapse
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked
naboleo said:
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked
Click to expand...
Click to collapse
Oh man that's great to hear! Thanks. Bought myself a laptop specifically to get my PRO 5 all TWRP'd up.
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?
showofdeth said:
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?
Click to expand...
Click to collapse
Never had troubles to downgrade to leaked beta
naboleo said:
Never had troubles to downgrade to leaked beta
Click to expand...
Click to collapse
Brilliant. Thanks a lot. Can't wait to hear people's experiences with this.
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
That TWRP works perfectly for me, backup nandroid, restore it, flash ZIP rom and ZIP other ( Xposed, etc ), no problem at all :highfive:
Good job !!! Great, thx !!!
Thank you so much for this!!! could i ask you how you managed to create a recovery for the pro5?
Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
I assume youare still on 5.6.1.19: Thats an error with this version.... put the updatefile manually (in the PC) on the external sd and flash via TWRP... you should later update your modified Pro 5 to 5.1.3.0, the error ist gone then...
Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
Copy UPDATE.ZIP from PC to phone BUT CONNECTING THE PHONE WHEN IT'S OPENED TWRP
MTP mode works great, even u'r on 5.6.1.19 :highfive:
Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!
PYCON said:
Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!
Click to expand...
Click to collapse
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:
cedric3 said:
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:
Click to expand...
Click to collapse
Uh I didn't know that a new version was released... Maybe, I could be. I download it again and try... Thx man ! :highfive:
The last version can't read the micro sd.
So I just noticed there's a new TWRP build up for us! Just thought I'd throw this out there, not sure what's different.
https://dl.twrp.me/shamu/
the only change is "Bring back /misc"
you should update if you are using cm14.1, cmupdater can cause bootloop with twrp 3.0.2.0 or older
8zabi said:
you should update if you are using cm14.1, cmupdater can cause bootloop with twrp 3.0.2.0 or older
Click to expand...
Click to collapse
I was struggling with this this morning. I was stuck in Recovery but managed to get back into System by doing a Reboot Bootloader, then Start. Then I downloaded the new TWRP and flashed it, all is well now. Would have been easier if I had access to a computer this morning.
psycho_asylum said:
I was struggling with this this morning. I was stuck in Recovery but managed to get back into System by doing a Reboot Bootloader, then Start. Then I downloaded the new TWRP and flashed it, all is well now. Would have been easier if I had access to a computer this morning.
Click to expand...
Click to collapse
Flashify is usually good for that!
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
Boot into recovery
Select install
Select near the bottom IMG button
Select IMG file
Select type of IMG ( boot, recovery)
Slide to start once finished reboot to recovery and check version
Reboot to O's
Profit
Sent from my Nexus 6 using XDA Labs
Read several posts about bad download. Before flashing check the size of TWRP version 3.0.2.1. The file size is 11,3 Mb.
https://dl.twrp.me/shamu/
tsjanda said:
Boot into recovery
Select install
Select near the bottom IMG button
Select IMG file
Select type of IMG ( boot, recovery)
Slide to start once finished reboot to recovery and check version
Reboot to O's
Profit
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Put phone into bootloader mode. Hold shift and right click to "Open command window here" where you have ADB and your TWRP file (assuming Windows PC). Type "fastboot flash recovery twrp-3.0.2-1-shamu.img". Easier, quicker, and potentially safer IMO.
Dopamin3 said:
..... "fastboot flash recovery twrp-3.0.2-1-shamu.img". Easier, quicker, and potentially safer IMO.
Click to expand...
Click to collapse
That's the most basic method, but with the app FlashFire you don't need a PC.
NLBeev said:
Read several posts about bad download. Before flashing check the size of TWRP version 3.0.2.1. The file size is 11,3 Mb.
https://dl.twrp.me/shamu/
Click to expand...
Click to collapse
Thank you for this. If you are using Tapatalk latest app it opens the link in its own browser and the download is only 6.92k. Opening in chrome beta and downloading gets the whole file downloaded.
Sent from my Pixel XL using Tapatalk
NLBeev said:
That's the most basic method, but with the app FlashFire you don't need a PC.
Click to expand...
Click to collapse
Depending on version you don't even need FlashFire. TWRP can flash the updated image.
Strephon Alkhalikoi said:
Depending on version you don't even need FlashFire. TWRP can flash the updated image.
Click to expand...
Click to collapse
In this case not possible, because the flashed version of TWRP-recovery was corrupt.
NLBeev said:
In this case not possible, because the flashed version of TWRP-recovery was corrupt.
Click to expand...
Click to collapse
I guess I took your post out of context, since your post didn't mention a corrupt download, but earlier posts did.
Strephon Alkhalikoi said:
I guess I took your post out of context, since your post didn't mention a corrupt download, but earlier posts did.
Click to expand...
Click to collapse
That's imaginable, because I had to edit the post.
I have made a mistake; didn't check the file size. After reboot to recovery, I noticed that a corrupt IMG was flashed.
EDIT
Version 3.0.3-0 available see next post.
TWRP-recovery version 3.0.3-0 for Nexus 6 available.
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img.html
3.1.0-0
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img.html
What's new:
https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/
Installed version 3.1.0-0. With all the changes themes need to be reworked. Also, there are rumblings in the XDA article discussion thread that Aroma does not work on this recovery. I'll have to check that.
EDIT: Aroma working perfectly here, as far as I can tell.
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
chaibaby said:
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
Click to expand...
Click to collapse
only one way to know, so try it and report back
wase4711 said:
only one way to know, so try it and report back
Click to expand...
Click to collapse
Will do when I am home later on tonight then report back.
chaibaby said:
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
Click to expand...
Click to collapse
Usually, yes. I would backup up personal data onto PC before trying.