How do I flash google apps onto cm12 on fire 5? - Fire Q&A, Help & Troubleshooting

I rooted my fire 5.3.1 using Root Junkies supertool, then used flashfire to flash cm12. The Gapps I told it to flash didnt show up and I have been trying since.
Trying fastboot TWRP I get hung on waiting for device.
Pushing the apk from super tool gets no connection error. Probably because of wrong versions.
Flashfire app says I am not rooted.
TWRP or Clockwork app needs their own recovery installed.
Flashing from adb sideload in amazon recovery I get E: signature verification failed
What can I do to get play store working!

robbiefowler said:
I rooted my fire 5.3.1 using Root Junkies supertool, then used flashfire to flash cm12. The Gapps I told it to flash didnt show up and I have been trying since.
Trying fastboot TWRP I get hung on waiting for device.
Pushing the apk from super tool gets no connection error. Probably because of wrong versions.
Flashfire app says I am not rooted.
TWRP or Clockwork app needs their own recovery installed.
Flashing from adb sideload in amazon recovery I get E: signature verification failed
What can I do to get play store working!
Click to expand...
Click to collapse
what model 7in, 8, 10...
Sent from my XT1254 using XDA Labs

sd_shadow said:
what model 7in, 8, 10...
Sent from my XT1254 using XDA Labs
Click to expand...
Click to collapse
7" (The cheapest one)

robbiefowler said:
7" (The cheapest one)
Click to expand...
Click to collapse
twrp doesn't work with system versions over 5.01
Sent from my XT1254 using XDA Labs
---------- Post added at 02:11 PM ---------- Previous post was at 02:06 PM ----------
see FlashFire instructions in the Cm12 thread
Sent from my XT1254 using XDA Labs

ok that was just one of many things I tried. How can I get the google apps working on the 7" fire running cm12?

robbiefowler said:
ok that was just one of many things I tried. How can I get the google apps working on the 7" fire running cm12?
Click to expand...
Click to collapse
which build versions of cm and GApps?
Could install a different version of Google framework and play store from
Apk Mirror
or try a different build of cm
http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416

robbiefowler said:
I rooted my fire 5.3.1 using Root Junkies supertool, then used flashfire to flash cm12. The Gapps I told it to flash didnt show up and I have been trying since.
Trying fastboot TWRP I get hung on waiting for device.
Pushing the apk from super tool gets no connection error. Probably because of wrong versions.
Flashfire app says I am not rooted.
TWRP or Clockwork app needs their own recovery installed.
Flashing from adb sideload in amazon recovery I get E: signature verification failed
What can I do to get play store working!
Click to expand...
Click to collapse
robbiefowler said:
7" (The cheapest one)
Click to expand...
Click to collapse
Solution:
- stop trying to use methods and tools not applicable to this device
- reload FireOS 5.3.1 from the stock recovery menu
- root and install SuperSU via the SuperTool
- install the latest build of FkashFire from here
- use arm/5.1/nano GAaps from here
- follow flashing instructions in CM 12.1 OP
It's possible the Play Store still won't work when CM first boots. If that happens reinstall FlashFire on CM and reflash both ROM and GAaps packages from above including a full system wipe at the top of the operations sequence. Don't just try to flash GAaps; rarely works. Must be concurrent with CM flash.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go to http://opengapps.org download exactly like in the screenshot and flash it just like you flashed cm.
Sent from my MotoG3 using Tapatalk

robot_head said:
Go to http://opengapps.org download exactly like in the screenshot and flash it just like you flashed cm.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Wrong! 5.0 is incompatible with CM 12.1. Go with arm/5.1 (suggest nano over pico; hover over build for explanation).

Davey126 said:
- reload FireOS 5.3.1 from the stock recovery menu .
Click to expand...
Click to collapse
I do not have that option. I did a factory reset and it reset to CM12
My stock options are:
reboot
apply update from ADB
wipe data/factory rest (did this one)
wipe cache
reboot to bootloader
power down
view logs

robbiefowler said:
I do not have that option. I did a factory reset and it reset to CM12
My stock options are:
reboot
apply update from ADB
wipe data/factory rest (did this one)
wipe cache
reboot to bootloader
power down
view logs
Click to expand...
Click to collapse
Outcome as expected. Third option ("apply update from ADB") is what you're looking for. See below for further guidance.
http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

Davey126 said:
Wrong! 5.0 is incompatible with CM 12.1. Go with arm/5.1 (suggest nano over pico; hover over build for explanation).
Click to expand...
Click to collapse
Excuse me?!?! Op says cm 12.... NOT 12.1
Sent from my MotoG3 using Tapatalk

robot_head said:
Excuse me?!?! Op says cm 12.... NOT 12.1
Click to expand...
Click to collapse
Not sure which thread OP is being referenced; official CM 12.1 thread in this forum does not indicate a specific version. Bottom line: GAaps 5.0 will NOT work for any custom rom developed for this device. Arm/5.1/[pico/nano/micro] is the appropriate build.

robbiefowler said:
I do not have that option. I did a factory reset and it reset to CM12
My stock options are:
reboot
apply update from ADB
wipe data/factory rest (did this one)
wipe cache
reboot to bootloader
power down
view logs
Click to expand...
Click to collapse
apply update from adb
http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
Sent from my XT1254 using XDA Labs

Reroot with Kingroot and get SuperSu with Supersume again. Then flash the correct Gapps with Flashfire. I tried flashing the wrong Gapps by mistake but doing this worked for me

VTCruzer said:
Reroot with Kingroot and get SuperSu with Supersume again. Then flash the correct Gapps with Flashfire. I tried flashing the wrong Gapps by mistake but doing this worked for me
Click to expand...
Click to collapse
Strongly suggest using the SuperTool to root and transition to SuperSU as SuperSume can soft-brick device if rebooted before flashing a new custom rom. Also retain all FlashFire flashing (zip file) defaults. Seems some folks are twiddling mount options yielding bad outcomes.
If you are talking about rooting CM 12.1 with KingRoot I wouldn't go there. ROM comes pre-rooted. If root was lost it suggests a bigger problem that is best remedied by refreshing CM+GAaps. No need to wipe the app/data/user partition in this scenario; most (usually all) personal apps and data will be retained. 5 min fix with limited risk.

Davey126 said:
Strongly suggest using the SuperTool to root and transition to SuperSU as SuperSume can soft-brick device if rebooted before flashing a new custom rom. Also retain all FlashFire flashing (zip file) defaults. Seems some folks are twiddling mount options yielding bad outcomes.
If you are talking about rooting CM 12.1 with KingRoot I wouldn't go there. ROM comes pre-rooted. If root was lost it suggests a bigger problem that is best remedied by refreshing CM+GAaps. No need to wipe the app/data/user partition in this scenario; most (usually all) personal apps and data will be retained. 5 min fix with limited risk.
Click to expand...
Click to collapse
Yep I was talking about CM12.1. The only way to flash anything without TWRP is FlashFire, and FlashFire only works with SuperSu and I couldn't think of a better way to get SuperSu back on it did work though so I guess I got lucky

Related

[Q] Sideload 5.1 on nexus 6

I am currently on 5.0.1 and as you all probably all know, the OTA links for 5.1 are available. I am trying to sideload this OTA to my nexus 6. To do this I am using wugfresh's NRT and I have gotten as far as the stock recovery menu. My adb drivers are configured properly which is why I made it this far. Now that I am in stock recovery, NRT says that ADB Sideload device not found. I am not sure what to do from here becuase my phone is not recognized by the computer which means I cannot update any drivers if necessary. Can anyone please guide me from here?
I had the same problem and NRT walked me through the fix. You have to open the device menu on your PC and choose your N6, it will have a yellow triangle on it. Right click and choose update driver from a file on your PC. Then choose the ADB driver to update. Mine connected and sideload was successful after that.
Even after that it may still not recognize (at least for me it did) and a simple unplug and plug in worked fined
Sent from my Nexus 6 using XDA Free mobile app
A2CKilla said:
Even after that it may still not recognize (at least for me it did) and a simple unplug and plug in worked fined
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, so I got it to flash, but then it aborts. It says
e: Footer is wrong
e: signature validation failed
Installation aborted
flamingtiger said:
Ok, so I got it to flash, but then it aborts. It says
e: Footer is wrong
e: signature validation failed
Installation aborted
Click to expand...
Click to collapse
I had the same issue, was able to get it to work using method #2 on this post.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
shadow321337 said:
I had the same issue, was able to get it to work using method #2 on this post.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
But wont that method completely wipe all data? I guess that is what I am going to have to do
flamingtiger said:
But wont that method completely wipe all data? I guess that is what I am going to have to do
Click to expand...
Click to collapse
Yeah, it will. That's what I had to do, too. Just keep in mind it will also wipe your /sdcard. So if you have any nandroid backups, etc back them up to your computer first. I was able to do that, then restore just the data portion of a 5.0.1 nandroid backup to the 5.1 ROM with no issues. An extra step but it kept my info.
flamingtiger said:
But wont that method completely wipe all data? I guess that is what I am going to have to do
Click to expand...
Click to collapse
You can manually flash the recovery, boot, and system through fastboot without wiping data. Then the adb sideload should work.
All I did was
1. flash stock recovery image from 5.0.1 (may be able to just use 5.1 now that the factory image is out)
2. flash stock system image (same as step 1)
3. sideload ota zip
4. profited!!!
Doing all this, my data was still in tact and this acted just like a regular ota
sub steps
5. add build.prop changes back for tethering
6.change dpi back to 480
ajjames01 said:
You can manually flash the recovery, boot, and system through fastboot without wiping data. Then the adb sideload should work.
Click to expand...
Click to collapse
so in NRT, I should just flash those specific ones and then press sideload update and go through the process again?
flamingtiger said:
so in NRT, I should just flash those specific ones and then press sideload update and go through the process again?
Click to expand...
Click to collapse
basically, unless you're doing it by hand with adb commands, under the advanced option in nrt, you'll see the manual flash buttons towards the middle I believe, your main focus is recovery and system if you want to keep your data
A2CKilla said:
All I did was
1. flash stock recovery image from 5.0.1 (may be able to just use 5.1 now that the factory image is out)
2. flash stock system image (same as step 1)
3. sideload ota zip
4. profited!!!
Doing all this, my data was still in tact and this acted just like a regular ota
sub steps
5. add build.prop changes back for tethering
6.change dpi back to 480
Click to expand...
Click to collapse
Just to make sure, I am supposed to exptract the zip that is found in the original zip that i downloaded from google right? Because NRT wont let me sideload the entire zip from google, so i extracted the one inside that zip and it let me go through. But i ended up with that error. What am i doing wrong?
flamingtiger said:
Just to make sure, I am supposed to exptract the zip that is found in the original zip that i downloaded from google right? Because NRT wont let me sideload the entire zip from google, so i extracted the one inside that zip and it let me go through. But i ended up with that error. What am i doing wrong?
Click to expand...
Click to collapse
you can see the directories, but yes, the factory image straight from google is where you get the .img files you need
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A2CKilla said:
you can see the directories, but yes, the factory image straight from google is where you get the .img files you need
Click to expand...
Click to collapse
Thanks bruh, I finally got it to work and lost no data at all. I really appreciate all help and advice that yall gave.
flamingtiger said:
Just to make sure, I am supposed to exptract the zip that is found in the original zip that i downloaded from google right? Because NRT wont let me sideload the entire zip from google, so i extracted the one inside that zip and it let me go through. But i ended up with that error. What am i doing wrong?
Click to expand...
Click to collapse
flamingtiger said:
Thanks bruh, I finally got it to work and lost no data at all. I really appreciate all help and advice that yall gave.
Click to expand...
Click to collapse
A2CKilla said:
All I did was
1. flash stock recovery image from 5.0.1 (may be able to just use 5.1 now that the factory image is out)
2. flash stock system image (same as step 1)
3. sideload ota zip
4. profited!!!
Doing all this, my data was still in tact and this acted just like a regular ota
sub steps
5. add build.prop changes back for tethering
6.change dpi back to 480
Click to expand...
Click to collapse
I'm a noob and want to make sure I do this right, are these following steps correct? i am currently unencrypted, rooted on franco kernel on 5.0.1!
1) flash stock recovery image first
2) flash stock system image second
3) what's the OTA zip? is that within the .tgz file that i downloaded from google?
4) what's build.prop.. ?
5) what's dpi?
Sorry for the noob questions... just don't want to brick my nexus
I got you
wilson289 said:
I'm a noob and want to make sure I do this right, are these following steps correct? i am currently unencrypted, rooted on franco kernel on 5.0.1!
1) flash stock recovery image first
2) flash stock system image second
3) what's the OTA zip? is that within the .tgz file that i downloaded from google?
4) what's build.prop.. ?
5) what's dpi?
Sorry for the noob questions... just don't want to brick my nexus
Click to expand...
Click to collapse
Alright... This is what I did and it should probably work for you:
Because u are on Franco kernel, I recomend that you flash the stock boot.img for 5.01 before begenning
1. Download wugfresh's NRT: this tool is very helpful for all things rooting
2. Make sure fastboot and adb are configured properly
2. I originally downloaded the zip directly from google (900≈ mb)...and it did not work
So I searched on google "nexus 6 5.1 ota zip"... On any website... The Downoad should be around 410 mb - this zip worked for me and give me no errors at all. Do not extract or mess with that zip.
3. Go on the toolkit and launch the advanced options
4. Around the middle of the page, you will see sideload update
5. Go through the prompts and select the 410 mb zip that u downloaded.
This should flash and reboot you to android 5.1
This method will install stock recovery and remove root so afterword go ahead and reroot using the toolkit.
Don't flash anything before besides the original 5.01 stock boot.img. dont worry about DPI or anything: at least that's not what I did, and I got it to work perfectly
If any steps did not make sense or you are not sure what to do.. Don't be afraid to ask me or anyone
?
Although I am not sure about the stock boot.img, it might work with Franco kernel. Anyone else know? Sideload could work with Franco kernel.

[GAPPS][AROMA]64bit Gapps for Mi Note Pro(Android 5.0.x & 5.1.x)(Choose Apps to Keep)

[GAPPS][AROMA]64bit Gapps for Mi Note Pro(Android 5.0.x & 5.1.x)(Choose Apps to Keep)
So have you got your amazing Mi Note Pro but you are missing Google Apps? No problem! It's quite simple all you need to do is flash Google Apps on your phone. Please follow this guide to successfully install Google Appps.
This is for Mi Note Pro (leo)
Disclaimer:
I'm not responsible for any devices being bricked, your device blowing up or world war 3 starting! You are doing this at your own risk.
Click to expand...
Click to collapse
Download Links:
Gapps for 5.0.x
Click Here to Download
Gapps for 5.1.x
Click Here to Download
INSTALLING GAPPS USING STOCK MI-RECOVERY WILL NOT WORK PLEASE INSTALL TWRP TEMPORARLY OR PERMANENTLY
If you already have TWRP installed you know what to do..
Download the following file:
twrp.img - https://mega.nz/#!nR0jHZqL!2cksl ... 5H76ut8UVtnu97HHAEo
HOW TO INSTALL TWRP TEMPORARLY
1. Save the file on your PC.
2. Power off your device and turn it back on by holding Power button and Volume Down at the same time. This will get you into fastboot menu.
3. Now what you will have to do is plug your phone to your PC using a usb cable.
4. Open up the Command Promt and navigate to the location of your fastboot driver. Mine is C:/adb so I would type cd C:/adb in the command promt
5. Now type in fastboot devices just to make sure that your device is listed correctly.
6. Place the twrp.img inside same folder as fastboot.
7. Type fastboot boot twrp.img (TO FLASH PERMANENTLY USE ''fastboot flash recovery twrp.img'')
8. Now your phone should boot into TWRP!! Click on the Install button and then navigate to where you have saved the Gapps package
9. Reboot and you are should have Gapps correctly installed.
Kahun said:
As the link on the other thread is now dead I'm posting this one.. This link gets updated so it's always most up to date gapps.
Click Here to Download GAPPS
Just flash using TWRP or Stock Recovery.
Click to expand...
Click to collapse
Which one is 64 bit, none of them indicate it, 64 is required unless you want a brick
Woops, just realised I did post the wrong link. Use the updated one
Kahun said:
Woops, just realised I did post the wrong link. Use the updated one
Click to expand...
Click to collapse
Still not sure which one arm64?
jazz452 said:
Still not sure which one arm64?
Click to expand...
Click to collapse
The one that says ARM64?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got some install error, had to use older version.
Did you use twrp?
Kahun said:
Did you use twrp?
Click to expand...
Click to collapse
Yea but didn't factory reset, maybe I got bad download.
How to flash it into stock recovery? I just received my phone and when booting into 2.0.1 recovery it doesnt work
---------- Post added at 10:55 PM ---------- Previous post was at 10:30 PM ----------
It says file is corrupt
Is it compatible with miui 7
---------- Post added at 04:08 PM ---------- Previous post was at 03:54 PM ----------
Do have to rename it to update.zip and put it to the root directory?
.
Updated with links for 5.0.x. & 5.1.x and also added instructions.
I just want to solve a gps issue occurring only with google maps, can I flash it over existing google apps?
EMJI79 said:
I just want to solve a gps issue occurring only with google maps, can I flash it over existing google apps?
Click to expand...
Click to collapse
No you can't flash over current gapps you will just get an error. Use a root uninstaller app to remove any Google apps and then flash it.
I have tried it with both the newest 5.1 ROM and Beta - Flashing through the Mi-PC Suite. When I install the smaller package GAPPS or when i select only the MAPS, etc. I get an error with the Dialer and the Contacts and it forces me to reflash the ROM again to recover. No other way so far.
I used TWRP as a temp and loaded the 5.1 on the card and installed it from TWRP - no luck. Am I missing something pretty obvious? It's been a while since I have flashed, etc. If I can't get any higher speeds on the AT&T HSPA+ than 1.5Mb then I might sell this thing. I didn't read fully the LTE bands on it and made the mistake before I caught it - the device was on its way. So now I keep it and make the most of it or sell it if its a hassle to make right. Mostly want a Global ROM with working GAPPS.
Thanks for any help!
mrmomoman said:
I have tried it with both the newest 5.1 ROM and Beta - Flashing through the Mi-PC Suite. When I install the smaller package GAPPS or when i select only the MAPS, etc. I get an error with the Dialer and the Contacts and it forces me to reflash the ROM again to recover. No other way so far.
I used TWRP as a temp and loaded the 5.1 on the card and installed it from TWRP - no luck. Am I missing something pretty obvious? It's been a while since I have flashed, etc. If I can't get any higher speeds on the AT&T HSPA+ than 1.5Mb then I might sell this thing. I didn't read fully the LTE bands on it and made the mistake before I caught it - the device was on its way. So now I keep it and make the most of it or sell it if its a hassle to make right. Mostly want a Global ROM with working GAPPS.
Thanks for any help!
Click to expand...
Click to collapse
Try manually removing all Gapps using a Root system unistaller app then wipe cache and try again.
mrmomoman said:
Mostly want a Global ROM with working GAPPS.
Thanks for any help!
Click to expand...
Click to collapse
Flash the Xiaomi.eu ROM, it already includes minimal GApps, and the rest you can get from the Play Store. That's the most convenient way.
There's no Global ROM for Note Pro as it's only sold in China but even if there were, you don't really want to use it anyway. Always use the latest China Developer ROM and modify it accordingly (or let someone do the work for you - hence the Xiaomi.eu suggestion). Since you don't need the translations to other European languages, you can also try the Russian-made MIUIPro, which includes GApps too.
I'm having all sorts of problems I can no longer get gapps to work, not sure what I have done. Since I went back to stable nothing seems to work. Play store just closes even the mi app store don't work.
jazz452 said:
I'm having all sorts of problems I can no longer get gapps to work, not sure what I have done. Since I went back to stable nothing seems to work. Play store just closes even the mi app store don't work.
Click to expand...
Click to collapse
Use root unistaller to completely remove any traces of Gapps, wipe dalvik and download the right gapps package for your android version.
https://www.androidfilehost.com/?fid=24352994023706867
How did I miss this nice 1 Aqq123
worked straight away with Gapps already included.
So this looks like the only option for the lucky ones who haven't locked their bootloader.
http://xiaomi.eu/community/threads/and-now-what-to-do.29571/

[RECOVERY] TWRP 2.8.7.0 (pollux/pollux_windy)

Since there aren't any (recent) TWRP builds any more for our devices, I built an new image by using the binaries from [NUT]'s XZDualRecovery and the kernel from CyanogenMod 's latest Recovery. Additionally, I added some features and wrote an automated installer, for easy and foolproof installation.
It should work with all custom built ROMs, like Cyanogen, Omni, PAC, etc., but won't work with unmodified stock-kernels.
WARNING: Installing this and especially (mis)using TWRP has the potential to brick your device and/or causing a complete loss of your data! No guarantee, use your common sense! You have been warned..
Automatic installation (easier and safer): Just download the proper the zip-file for your device, boot into the current recovery (e.g. CyanogenMod Recovery from nightly builds, old TWRP or CWM) and install it!
Manual installation (only needed if no recovery is installed yet, or automated installation fails):
download the proper zip-file for your device
open a terminal/console
type (and allow):
Code:
su
goto the download directory, probably:
Code:
cd /sdcard/Download
unzip the installer (or use a file-manger):
Code:
unzip TWRP-*.zip
run (this is the dangerous part, make sure it's written correctly!):
Code:
dd if=twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Special thanks to [NUT] for allowing me to use his binaries and the TeamWin Recovery Project for creating this great tool!
ADB (conditions for access in TWRP): Make sure that you have enabled "Android debugging" and "Root access" for ADB in the Developer options of your ROM. Additionally, you need to connect your tablet once while Android is running and authorise ADB first, in order to be able to use it later in TWRP!
Changelog:
2015-08-23:
based on TWRP 2.8.7.0 and latest XZDualRecovery/CyanogenMod Recovery
added automated zip-installer
added CM's mkfs.f2fs (allows to format/create F2FS partitions)
added support for flashing and backing up recovery images
XDA:DevDB Information
[RECOVERY] TWRP (pollux/pollux_windy), Tool/Utility for the Sony Xperia Tablet Z
Contributors
BlackAfghan, [NUT], Dees_Troy, TeamWin Recovery Project, CyanogenMod
Source Code: https://github.com/TeamWin/Team-Win-Recovery-Project
Version Information
Status: Stable
Current Stable Version: 2.8.7.0
Stable Release Date: 2015-06-22
Created 2015-08-27
Last Updated 2015-08-27
Thank you, looks great with @z31s1g's reworked stock theme!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tapatalked that shiznit.
Thanks! Is working perfectly on my pollux! (and finally we have something dedicated to this model)
Sent from my A0001 using XDA Free mobile app
CyanogenMod Recovery installation works now!
Sorry, I found a bug in the installation procedure, which prevented automated flashing when CyanogenMod Recovery was used..
So if you are still with bare CyanogenMod Recovery, and haven't performed a manual installation yet, please download it again!
Thanks a Million for the fix
BlackAfghan said:
Sorry, I found a bug in the installation procedure, which prevented automated flashing when CyanogenMod Recovery was used..
So if you are still with bare CyanogenMod Recovery, and haven't performed a manual installation yet, please download it again!
Click to expand...
Click to collapse
It works!!! At last i got twrp on my cyanogenmod 12.1. Thanks a lot @BlackAfghan :highfive: :laugh: :highfive:
Keep getting 'error: device unauthorized. Please check the confirmation dialog on your device.' whenever I try to send anything through adb from my computer. I have updated to the latest adb, as older ones seemed to show me the device as being offline when using this version of TWRP.
Any ideas?
georgecarstoiu said:
Keep getting 'error: device unauthorized. Please check the confirmation dialog on your device.' whenever I try to send anything through adb from my computer. I have updated to the latest adb, as older ones seemed to show me the device as being offline when using this version of TWRP.
Any ideas?
Click to expand...
Click to collapse
Did you enable "Android debugging" AND "Root access" for ADB in the Developer options?
BlackAfghan said:
Did you enable "Android debugging" AND "Root access" for ADB in the Developer options?
Click to expand...
Click to collapse
Yes, but this happens while being in TWRP. The first time I am seeing this type of message when trying to push files from my computer to a device that is in recovery mode.
georgecarstoiu said:
Yes, but this happens while being in TWRP. The first time I am seeing this type of message when trying to push files from my computer to a device that is in recovery mode.
Click to expand...
Click to collapse
OK, I solved it. It's no bug, it's a feature..
You have to connect and authorise it first, while the ROM is running. Than it also works in TWRP next time!
I don't know if that behaviour really makes sense, but I guess Google or CyanogenMod intended it that way.. That would also explain why you needed a more recent version of ADB.
This recovery is based on Android 5.1.1, unlike the older TWRP builds which were based on 4.3 or even 4.2.
Maybe the TWRP-team can add that authorization dialogue in a future release.
BlackAfghan said:
OK, I solved it. It's no bug, it's a feature..
You have to connect and authorise it first, while the ROM is running. Than it also works in TWRP next time!
I don't know if that behaviour really makes sense, but I guess Google or CyanogenMod intended it that way.. That would also explain why you needed a more recent version of ADB.
This recovery is based on Android 5.1.1, unlike the older TWRP builds which were based on 4.3 or even 4.2.
Maybe the TWRP-team can add that authorization dialogue in a future release.
Click to expand...
Click to collapse
Thought so too eventually, although it doesn't make perfect sense. It is especially bad when you realize this after you have wiped the system clean in preparation for a clean install of a new ROM. Good that I had a USB stick and OTG adapter cable around, otherwise it would have been impossible.
The more interesting thing is how exactly does TWRP know that a computer is authorized or not and does this information actually survive a wipe of the system before the actual flash of a new one?
edit....
Just signed up to say thank you for this! Excellent work!
Any change this will be updated to the latest version?
Verstuurd vanaf mijn LG-H815 met Tapatalk
*justintime* said:
Any change this will be updated to the latest version?
Verstuurd vanaf mijn LG-H815 met Tapatalk
Click to expand...
Click to collapse
https://dl.twrp.me/pollux_windy/ - Seems you need to be on a MM rom for 3.x versions
scoobyjenkins said:
https://dl.twrp.me/pollux_windy/ - Seems you need to be on a MM rom for 3.x versions
Click to expand...
Click to collapse
No that's not working on Pollux (tablet LTE) when updating in Cyandelta twrp thinks it's a pollux_windy device.
And won't update. Because of Pollux update file.
*justintime* said:
No that's not working on Pollux (tablet LTE) when updating in Cyandelta twrp thinks it's a pollux_windy device.
And won't update. Because of Pollux update file.
Click to expand...
Click to collapse
Why not use a pollux one for pollux https://dl.twrp.me/pollux/ ? 3.0.2.0 works perfectly on CM13.1.
Rootk1t said:
Why not use a pollux one for pollux https://dl.twrp.me/pollux/ ? 3.0.2.0 works perfectly on CM13.1.
Click to expand...
Click to collapse
Haha nice..... Strange thing is on twrp.me Pollux is not mentioned in the device list. That's why I thought it was not available.
Thanks.
Can someone help me? I am unable to flash this recovery.
First i tried to root my Tablet Z (WiFi) with the Kingsroot and SuperSU Me method but i got stuck in a bootloop after the reboot.
But now i have rooted my device but i am unable to flash this recovery to use cm13.
My bootloader is unlocked and i gave the manual installation a try with the android terminal and it said it copied some files but nothing is happening.
I am unable to boot into TWRP
checks0n said:
Can someone help me? I am unable to flash this recovery.
First i tried to root my Tablet Z (WiFi) with the Kingsroot and SuperSU Me method but i got stuck in a bootloop after the reboot.
But now i have rooted my device but i am unable to flash this recovery to use cm13.
My bootloader is unlocked and i gave the manual installation a try with the android terminal and it said it copied some files but nothing is happening.
I am unable to boot into TWRP
Click to expand...
Click to collapse
for cm13 you need to use 3.x.x twrp.img.
Rootk1t said:
for cm13 you need to use 3.x.x twrp.img.
Click to expand...
Click to collapse
No, CM13 works fine with TWRP 2.8.7.0, as long as you don't use Adopted Storage!

[Unofficial] SuperSU v2.68 on Android N Preview (fixed)

Hello everyone
I believe many people cannot wait to use the latest Android N Preview on their Nexus devices, but found out that root still isn't available. The first root method appears HERE, done by @phhusson.
If people wanted to use SuperSU for some reason, I created this small flashable zip.
Based on nearly the same thoughts but combined with @Chainfire systemless method, this root is also done by setting SELinux to PERMISSIVE.
SuperSU-v2.68-Android-N (fixed)
The zip comes with aroma installer, so you can choose your device within the menu.
Instructions:
(TWRP is working and you're not encrypted) Flash the zip with TWRP directly
(Your device is encrypted, and want to stay encrypted) TWRP will enter a loop. Wait for a while and it will boot eventually, then use adb sideload to flash the zip.
(Your device is encrypted, and you want to decrypt, or TWRP is not working for you) Extract the zip, flash the boot.img for your device through fastboot, then revert to stock recovery. Then do a "Factory Reset" to wipe everything. Now you are decrypted can use TWRP normally.
Features:
Supports Nexus 9, 6P, 6, and 5X
Disabled force-encryption (encrypted users can still use it with no problems)
BusyBox is pre-installed as well.
Tested on my Nexus 9, Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How can i flash zip? How to choose my device please specify
Sent from my Nexus 6 using Tapatalk
ohad129 said:
How can i flash zip? How to choose my device please specify
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Download zip, flash in TWRP.
If encrypted, then use OTG or USB Sideload.
I cant go into my twrp i get the android with red triangle
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:47 PM ---------- Previous post was at 10:32 PM ----------
Ok i think i remember its like was in android m
Sent from my Nexus 6 using Tapatalk
---------- Post added at 11:06 PM ---------- Previous post was at 10:47 PM ----------
Ok i should revert to marashmellow and root then through bera tester get the update so my twrp will stay is it right?
Sent from my Nexus 6 using Tapatalk
I got erorr binary is not install help please
Sent from my Nexus 6 using Tapatalk
I'd love to use this, but I don't have TWRP installed. Is there a working TWRP for the N Preview? TWRP 3.0.0-1 apparently causes bootloops.
anuraj1 said:
I'd love to use this, but I don't have TWRP installed. Is there a working TWRP for the N Preview? TWRP 3.0.0-1 apparently causes bootloops.
Click to expand...
Click to collapse
It will boot up eventually
Wait for a while, TWRP will give up trying to decrypt data after multiple retries.
It will prompt to enter password, press cancel and use adb sideload to flash the zip.
this completely broke the phone for me. cant get through a boot, stuck on boot animation.
couldnt get into recovery. had to reflash a different boot.img to get anything working
not sure what this modified that broke
installing it from TWRP does not work
minieod said:
this completely broke the phone for me. cant get through a boot, stuck on boot animation.
couldnt get into recovery. had to reflash a different boot.img to get anything working
not sure what this modified that broke
Click to expand...
Click to collapse
AJ said:
installing it from TWRP does not work
Click to expand...
Click to collapse
Would you report what models are you using? I'll check if things are messed up. For me on the Nexus 9 it's working good.
You need to rewrite your aroma script, it flashes all of the kernels right after another so the selection doesn't work right. It just causes it not to boot. I edited out everything except for the Nexus 6p from the script and got it to work fine for me.
themustached said:
You need to rewrite your aroma script, it flashes all of the kernels right after another so the selection doesn't work right. It just causes it not to boot. I edited out everything except for the Nexus 6p from the script and got it to work fine for me.
Click to expand...
Click to collapse
Thanks
Super stupid mistake, fixed
I wanted to try N, and at the same time, this post reignited my desire to try without encryption.
How can we keep our nexus updated with encryption off? If i google arround, i just see info from octover 2015, and no newer boot images made (i am currently running stock).
topjohnwu said:
Thanks
Super stupid mistake, fixed
Click to expand...
Click to collapse
I forgot to say, thanks for the installer to begin with. It took a minute to figure out what was happening. It was maddening for a minute.
cocchiararo said:
I wanted to try N, and at the same time, this post reignited my desire to try without encryption.
How can we keep our nexus updated with encryption off? If i google arround, i just see info from octover 2015, and no newer boot images made (i am currently running stock).
Click to expand...
Click to collapse
I fastboot flash bootloader, reboot bootloader,fastboot flas radio,reboot bootloader, fastboot flash boot.IMG,system.IMG, then reboot directly into recovery ,factory reset and flash this
http://forum.xda-developers.com/showthread.php?t=3000788
Then boot up
Sent from my Nexus 6 using XDA Free mobile app
It's boot looping on N6. I manually flashed boot-shamu.img to verify that it wasn't an aroma issue, and it boot looped. I had to flash the original boot.img to get it back.
cjkacz said:
I fastboot flash bootloader, reboot bootloader,fastboot flas radio,reboot bootloader, fastboot flash boot.IMG,system.IMG, then reboot directly into recovery ,factory reset and flash this
http://forum.xda-developers.com/showthread.php?t=3000788
Then boot up
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ups, never mentioned I am no Nexus 6p
Enviado desde mi Nexus 6P mediante Tapatalk
How do you guys got twrp working on your nexus 9 android N? I tried to flash/boot but it just stucks on twrp logo and restarts to twrp logo bootloop. How can I make twrp work? Thanks
Note - Im still on Android N letting you guys know that I can boot to system from twrp bootloop, all I want is twrp to work so I can restore back to marshmallow. Thanks
cocchiararo said:
Ups, never mentioned I am no Nexus 6p
Enviado desde mi Nexus 6P mediante Tapatalk
Click to expand...
Click to collapse
There is a no encrypt mod for 6p. I'm trying to find it
Edit
http://forum.xda-developers.com/and...-fed-patcher-v8-forceencrypt-disable-t3234422
Sent from my Nexus 6 using Tapatalk
abakash9 said:
How do you guys got twrp working on your nexus 9 android N? I tried to flash/boot but it just stucks on twrp logo and restarts to twrp logo bootloop. How can I make twrp work? Thanks
Note - Im still on Android N letting you guys know that I can boot to system from twrp bootloop, all I want is twrp to work so I can restore back to marshmallow. Thanks
Click to expand...
Click to collapse
I mentioned it in the OP.
Just let it loop a while , it will boot eventually

[TOOL][OP5] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the OnePlus 5's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​
Thaaaanks but has anyone rooted there op5 with this yet? Does it actually work? Probably does but just would like to make 110% sure
icem8n said:
Thaaaanks but has anyone rooted there op5 with this yet? Does it actually work? Probably does but just would like to make 110% sure
Click to expand...
Click to collapse
This tool cant directly root your phone, but it can unlock your bootloader and help you to flash a twrp. If you want to root your phone you can flash twrp and then flash the root zip through twrp
Bootloader successfully unlocked
I´ve also flashed this Chinese TWRP with your tool due to my eagerness
and finally rooted with Magisk
@mauronofrio your efforts are really appreciated
Deacon-Frost said:
Bootloader successfully unlocked
Click to expand...
Click to collapse
Perfect:good:
Awesome looking tool. I'll be downloading and donating as soon as I get my OP5 on Monday.
I plan on running stock software for awhile but can I simply unlock, flash TWRP, and flash the same SuperSU I always use for custom ROMs?
biglilsteve said:
Awesome looking tool. I'll be downloading and donating as soon as I get my OP5 on Monday.
I plan on running stock software for awhile but can I simply unlock, flash TWRP, and flash the same SuperSU I always use for custom ROMs?
Click to expand...
Click to collapse
Yes, i don't know if there are a supersu specific version must be flashed, but yes, unlock the bootloader, flash the twrp and then flash supersu or magisk. I don't know if you need to disable dm-verity before reboot but i think yes
was impatient... and got everything working... unlocked, TWRP recovery, and then Magisk rooted. woot woot.!!
now hopefully there is a working xposed
AznMTboy said:
was impatient... and got everything working... unlocked, TWRP recovery, and then Magisk rooted. woot woot.!!
now hopefully there is a working xposed
Click to expand...
Click to collapse
Perfect:good:
Made a backup before flash xposed
perfect!thank you!
Which version of magisk 13 you use?
Gesendet von meinem Nexus 6P mit Tapatalk
cant install twrp
i cant install twrp and also cant root the phone, some one can help me? i try all i can to get it work....
this is what i get always..
hounter17 said:
i cant install twrp and also cant root the phone, some one can help me? i try all i can to get it work....
this is what i get always..
View attachment 4192075 View attachment 4192076
Click to expand...
Click to collapse
When you flash the twrp select the options "And boot it" and you will rebooted directly to the twrp, someone say that the TWRP survive for only 1 reboot
Craxx said:
Which version of magisk 13 you use?
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
I have not tested it, i think the last should work
mauronofrio said:
When you flash the twrp select the options "And boot it" and you will rebooted directly to the twrp, someone say that the TWRP survive for only 1 reboot
the problem is that i can get it flashed
Click to expand...
Click to collapse
hounter17 said:
mauronofrio said:
When you flash the twrp select the options "And boot it" and you will rebooted directly to the twrp, someone say that the TWRP survive for only 1 reboot
the problem is that i can get it flashed
Click to expand...
Click to collapse
You are the first until now. To flash the twrp you need to have an internet connection, because the tool before download the recovery and then flash it. If you have made all of this try to delete the downloaded recovery and flash it again (maybe the download has failed). To delete the downloaded recovery you need to go in the advanced options and use the "Delete Files" (top right of the page) button to delete what you want (in this case you need only to delete TWRP recoveries). Tell me if you solve
Click to expand...
Click to collapse
Someone said that TWRP will only survive for one reboot. I've flashed yesterday that Chinese TWRP and rooted with Magisk. My experience is that TWRP will stay. I've booted today three times into TWRP. Everything seems to be as normal as it should be.
Deacon-Frost said:
Someone said that TWRP will only survive for one reboot. I've flashed yesterday that Chinese TWRP and rooted with Magisk. My experience is that TWRP will stay. I've booted today three times into TWRP. Everything seems to be as normal as it should be.
Click to expand...
Click to collapse
Perfect so the problem is another one. When the twrp is booted for the first time it automatically delete or hide the stock recovery so if you flash the twrp and you boot directly from fastboot to twrp, the twrp will survive but if you flash the twrp and power one normally the phone the stock recovery will be restored. So when you flash the twrp, directly boot in it, from the tool you need to check "And boot it" option to boot it directly after flash.
mauronofrio said:
hounter17 said:
You are the first until now. To flash the twrp you need to have an internet connection, because the tool before download the recovery and then flash it. If you have made all of this try to delete the downloaded recovery and flash it again (maybe the download has failed). To delete the downloaded recovery you need to go in the advanced options and use the "Delete Files" (top right of the page) button to delete what you want (in this case you need only to delete TWRP recoveries). Tell me if you solve
Click to expand...
Click to collapse
i try all and it tucks here:
View attachment 4192182
Click to expand...
Click to collapse
hounter17 said:
mauronofrio said:
i try all and it tucks here:
View attachment 4192182
Click to expand...
Click to collapse
i'm unable to load this image and please be more specific, when you got this problem?
Click to expand...
Click to collapse
mauronofrio said:
hounter17 said:
i'm unable to load this image and please be more specific, when you got this problem
Click to expand...
Click to collapse
im sorry about the troubles... i unlock the bootloader i enable usb debuging and i reboot it in fastboot mode. them i use the tool to flash the recovery but when the cmd screen gets on it stucks and doesnt finish the process...
i dont know what to do in this point
i also see that in fastboot mode screen appear that the product name was "QC_reference_phone" and the bootloader and the baseband brands are empty.
the device state was "unlocked"
Click to expand...
Click to collapse

Categories

Resources