Related
Hello, guys this is my first post but i am quite sure that my methods work.If there any problems then u can surely ask in the section below. This thread will be a GUIDE TO ROOT AND INSTALL CUSTOM RECOVERY FOR MOTO G 1st Gen users.
Some prerequisites are:
1. Motorola drives (https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481)
2.Fastboot and recovery files (https://www.dropbox.com/sh/9jf2va51ffg0pzq/AAAxDT-ETf7AESIcHGnfEgv7a?dl=0)
[ Let these files be downloaded and kept in Cdrive of ur pc and and place them on the desktop.. Please name this folder MOTO FILES]
3. SuperSu files https://download.chainfire.eu/696/supersu/ and[/url] paste it in ur phones internal memory and please do this after unlocking the bootloader cause bootloader unlocking will delete everything so its better to do it after unlocking bootloader
Download these files and ur done... Now lets continue to the fun part
This process involves three very simple steps :
1. Unlocking the Bootloader:-
This process is infact very easy to do. There are several guides on the internet regarding this process but the one that i suggest is by High On Android/ Max Lee . Follow his method and u can very easily unlock ur bootlader. Copy this url and see it for urself fellow guys...http://highonandroid.com/android-smartphones/how-to-unlock-bootloader-on-motorola-android-smartphone
2. Erasing ur previous recovery and installing a new one and rooting ur phone all in one process
Some users have been reporting that even after installing custom recovery , whenever they go into recovery they enter into stock recovery. The actual problem is that the stock rom of the Moto G rewrites over the new custom recovery installed.
So we have to install the recovery actually twice but it only takes a few minutes
i) Firstly be sure to have lots of juice in your phone
ii) Boot ur phone into the bootloader by power offing ur device and then pressing the volume down and power button together for 10 seconds and then leaving both of them together.
iii) Now connect ur device to ur pc/laptop
iv) Now open a cmd and enter the following commands(press enter after every command)
- cd Desktop
-cd MOTO FILES
-fastboot flash recovery Recovery2.img
-fastboot reboot-bootloader
[MAKE SURE NOT TO REBOOT UR DEVICE ]
v) Now ur phone has custom recovery installed in it and u shud now enter into recovery mode by choosing the option from the bootloader, by pressing volume down and then volume up while in bootloader mode.
vi) This will open the Philz recovery that i have provided with. I prefer the philz recovery over the cwm one. Now go on and install the SuperSu update zip file. And BOOM ur Device is now rooted !!!!.
vii) Now reboot ur phone and u must install
-ROOT CHECKER (to check root)
- and most importantly ROOT EXPLORER
viii) After following step (vii), now if u try to go into recovery, u will be booted to stock recovery. So to prevent that use the ROOT EXPLORER app and go to the root \system\etc and delete the file named install-recovery.sh .
ix) After deleting the file u will once again have to follow step (iv) and install custom recovery this will ensure u having custom recovery even after rebooting ur device and u will have ROOT access as well
On which android version , were you on before rooting . 5.01 or 5.1 .
This method works for both 5.1 and 5.01
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Is the first post too heavy for you?!
Follow the steps and be happy.
Gesendet von meinem Moto G mit Tapatalk
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Andus1988 said:
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Click to expand...
Click to collapse
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Ajay P said:
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Click to expand...
Click to collapse
whats the problem u facing ?
sanilch99 said:
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Click to expand...
Click to collapse
It could cumber the inbuilt root!
sanilch99 said:
whats the problem u facing ?
Click to expand...
Click to collapse
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Ajay P said:
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Click to expand...
Click to collapse
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
sanilch99 said:
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
Click to expand...
Click to collapse
Thank you
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
notuger said:
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
Click to expand...
Click to collapse
I will recheck that super su. file and make sure its perfect... Thanks for the response:good:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Works but could be simplified
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
issam029 said:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
i have edited the previous link and given the new one. You can use this SU file. It will solve ur prob.
pcgardner said:
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
Click to expand...
Click to collapse
Reinstallation of custom recovery is not must its just for safety precautions and I have finally updated the SuperSu link. As far as Busybox u will have to install it customly only.
issam029 said:
once i finished steps all, when i open supersu, popup window says, "there is no su binary installed, and supersu cannot install in it. This is the problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
If i check with root checker,
sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
use the new su files i updated the link
facing problem after unlock bootloader mood for moto g 1st gen
Thanks a lot for your information...:good:
Bro!! I have already unlock bootloader mood.. Before rooting is it necessary to clear all data & app...??
I was following guide from this thread.
"http://forum.xda-developers.com/moto-x-play/general/untested-how-to-root-moto-x-play-t3211941"
I did everything step by step, bootloader unlocked and once phone get started too then after flashing twrp i was not getting anything when i tried to reboot twrp asked to install supersu and i installed it.
THen i read somewhere don't install supersu when twrp asked ?
then i did process all again, but can't go through warning message of bootloader.
Please help i just want to root, don't want custom rom or anything.
did you take a backup ??? if you did restore it. otherwise do a factory wipe from twrp if it does not help Then download twrp flashable marshmallow stock firmware and flash it.
bablu048 said:
did you take a backup ??? if you did restore it. otherwise do a factory wipe from twrp if it does not help Then download twrp flashable marshmallow stock firmware and flash it.
Click to expand...
Click to collapse
I can get into recovery twrp, but i can't get into phone.
I flashed twrp-lux-2.8.7-r6 & then flashed super su 2.46 ?
is there any solution without flashing stock firmware ? i can get root and override this problem.
Can anyone give me link to stock firmware ? Indian version i was on Marshmallow. & how to flash stock firmware
heartthrob.harsh said:
Can anyone give me link to stock firmware ? Indian version i was on Marshmallow. & how to flash stock firmware
Click to expand...
Click to collapse
download from here forum.xda-developers.com/moto-x-play/general/rom-xt1563-brasil-stock-6-0-twrp-t3272979
if twrp doesn't detect the backup then connect the device to a PC in fast boot mode and type command "adb devices" it will show you your device id . now take out your external sdcard go to twrp backup folder and make another folder inside backup of the name of your device id and keep the backup there and then restore from twrp.
bablu048 said:
download from here forum.xda-developers.com/moto-x-play/general/rom-xt1563-brasil-stock-6-0-twrp-t3272979
if twrp doesn't detect the backup then connect the device to a PC in fast boot mode and type command "adb devices" it will show you your device id . now take out your external sdcard go to two backup folder and make another folder of the name of your device id and keep the backup there and then restore from twrp.
Click to expand...
Click to collapse
Right now i flashed supersu 2.61 now i am on moto animation that warning message gone and get into that moto animation i think it was problem of supersu which i flash was 2.42 as mentioned in that thread.
Don't know now i am stuck on moto logo.
heartthrob.harsh said:
Right now i flashed supersu 2.61 now i am on moto animation that warning message gone and get into that moto animation i think it was problem of supersu which i flash was 2.42 as mentioned in that thread.
Don't know now i am stuck on moto logo.
Click to expand...
Click to collapse
same happened to me clearing cache solved it.
heartthrob.harsh said:
Right now i flashed supersu 2.61 now i am on moto animation that warning message gone and get into that moto animation i think it was problem of supersu which i flash was 2.42 as mentioned in that thread.
Don't know now i am stuck on moto logo.
Click to expand...
Click to collapse
It takes good 15-20 Mins at Moto Logo; Wait patiently and if it refuses to boot after that then do this :
Download latest TWRP and flash it. DONT FLASH SUPERSU from TWRP when prompted at boot.
If this does not solve either, download Android 6.0 + TWRP from this Link
Save it to TWRP \ Backup and then boot to TWRP, Restore and Boot as per instructions in that forum.
If this also fails, then simply flash FULL STOCK FIRMWARE from here and follow instructions given at here.
Hello guys.
I have successfully ported TWRP 3.0.0-0 for our Smart Prime 6.
It's 100% working !!
There are NO BUGS !! :good:
DOWNLOAD
NEW LINK: DOWNLOAD
________________________________________
How to install
Via app:
1) Download TWRP 3.0.0-0 from the link above and place it on internal storage of your phone.
2) Download Flashify app from Google Play Store.
3) Open Flashify app.
4) Grant root permissions.
5) Click "Recovery image" and then click "Choose a file"
6) Navigate to the folder where you placed TWRP 3.0.0-0 and choose the .IMG file.
7) Press "Yup!" button and wait.
8) After a while the phone will require reboot. So click "reboot" button.
9) Phone will reboot and automatically boot into TWRP, so you can press reboot to system.
10) Enjoy!
Special thanks to Oneb1t for modded .fstab file! :highfive:
edit: you can use Flashfire app too instead of Flashify, but it's not recommended, because the latest version of the Flashfire app is not flashing properly.
Brilliant! Thank you so much! Do you know any custom ROM what is better than the factory ROM?
There is no custom ROM for this phone yet.
But I'm trying to make LITE ROM.
Adreno306™ said:
There is no custom ROM for this phone yet.
But I'm trying to make LITE ROM.
Click to expand...
Click to collapse
Do you think it's easier/possible to adapt a ROM from a similar device like say, the Alcatel
Pop 2 (5) Premium ? I don't know if there's any ROM for that phone tho, but since it's branded as Alcatel you might get more support from the community here than by using Vodafone's name.
Hello, Demonlord6.
I have tried to make a stock flashable ROM via dumping the system folder and the boot.img file, but without success.
It does not boot properly.. when I tried to flash it without dalvik/system wipe everything was as before.
When I tried to wipe /system and dalvik first and then flash the ROM, it causes bootloop.
So now I'm trying to fix this issue..
I don't know where the problem is.
So when this issue will be solved I will try to build a ROM from Alcatel phones with same specs.
Adreno306™ said:
Hello, Demonlord6.
I have tried to make a stock flashable ROM via dumping the system folder and the boot.img file, but without success.
It does not boot properly.. when I tried to flash it without dalvik/system wipe everything was as before.
When I tried to wipe /system and dalvik first and then flash the ROM, it causes bootloop.
So now I'm trying to fix this issue..
I don't know where the problem is.
So when this issue will be solved I will try to build a ROM from Alcatel phones with same specs.
Click to expand...
Click to collapse
Hey, Andreno306
I don't know much about Rom's in that level of expertise I'm afraid :/ but I did some digging and came across this simple tutorial on XDA:
http://forum.xda-developers.com/showthread.php?t=2387941
I imagine it does not work for every single device out there, at least not with modifying stuff after, but it might be a good starting point I think, in fact I would try to actually make one myself had I a working PC currently at home. But even if I did I had no way of testing it because this is currently my daily driver phone.
Just wanted to say that I'm also very interested in getting a slim ROM for this device. I can't offer any expertise I'm afraid! Just wanted to show that there are people interested in your project.
:highfive:
Stock Kernel
Thanks, it works great.
This is little off-topic but does anyone has the stock kernel, i flashed NeoKernel but it is not that good and i forgot to make a backup do can anyone please link me to the stock kernel?
vojta_horanek said:
Thanks, it works great.
This is little off-topic but does anyone has the stock kernel, i flashed NeoKernel but it is not that good and i forgot to make a backup do can anyone please link me to the stock kernel?
Click to expand...
Click to collapse
I have one
https://mega.nz/#!tMJD3B4T!f6m2ELYCVupqGCcN2aGbkrNzEqijLu7au-7usEfeVL0
But I recommend to restore it with the flashify app, because that's how the backup was made.
If, for some reason, you don't/can't restore it, then you can always try Sugar on the PC which basically restores everything to factory settings (recovery, kernel, etc, it all gets reset)
Demonlord6 said:
I have one
But I recommend to restore it with the flashify app, because that's how the backup was made.
If, for some reason, you don't/can't restore it, then you can always try Sugar on the PC which basically restores everything to factory settings (recovery, kernel, etc, it all gets reset)
Click to expand...
Click to collapse
Restored and my phone keeps turning off after boot(once i saw the turn off screen, other times it just vibrates at boot screen), isnt it the wrong file? (flashed wia flashify)
I was able to restore the boot from TWRP (lucky i made a backup this time)
vojta_horanek said:
Restored and my phone keeps turning off after boot(once i saw the turn off screen, other times it just vibrates at boot screen), isnt it the wrong file? (flashed wia flashify)
I was able to restore the boot from TWRP (lucky i made a backup this time)
Click to expand...
Click to collapse
Sorry there about the bootloop but glad u could restore it from TWRP, maybe it was because we have different ROM versions ?
Demonlord6 said:
Sorry there about the bootloop but glad u could restore it from TWRP, maybe it was because we have different ROM versions ?
Click to expand...
Click to collapse
I got this one: http://www.needrom.com/download/vodafone-smart-prime-6-vf-895n-debloatedclean-stock/#
vojta_horanek said:
I got this one: http://www.needrom.com/download/vodafone-smart-prime-6-vf-895n-debloatedclean-stock/#
Click to expand...
Click to collapse
Yeap, that's not the same version as my ROM, mine is not 130FNN etc. Maybe that's why it didn't work
Enviado do meu GT-S5280 através de Tapatalk
Sorry for the stupid question but... does it works on Smart Prime 7 too?
Has anyone installed that linked ROM? It seems to be what we are looking for... a slim debloated rom.
I presume we need to be rooted, install this TWRP, then flash that ROM?
It mentions unlocking the bootloader, I dont think I've seen any info anywhere about unlocking the bootloader.
Can anyone give a quick lowdown on all the steps required to install that ROM please?
Hi everyone, I discovered that Elephone Trunk and Smart Prime 6 have (almost) identical specs: https://www.devicespecifications.com...ison/c584481c6
So it would be great to "port" (or build ?) the official Nougat-OmniROM for Trunk to VF-895N: http://dl.omnirom.org/trunk/
Last but not least, here's official Vodafone Smart Prime 6 sources: Vodafone_Smart_prime_6_20150413.tar.xz
TWRP for vodafone smart max 4 990N (coolpad 8890u).
I tried this recovery image for vodafone smart max 4 990N (coolpad 8890u).
The phone is in a bootloop state. I think i have usb debugging enabled already.
So, in fastboot mode i can see the device in my pc in adb fastboot cmd.
Im trying to ''fastboot boot recovery.img" but it stops in ''booting..''.
Dont know whats the problem but for sure i can not find a specific twrp image for this device.
If i enter fastboot oem device-info it says ''(bootloader) Device unlocked: true''.
Any ideas ?
hi i was wondering if you could share how you did this or if you can make one for the Vodafone smart n9 (VFD720) it would help a lot of people out looking for this
Needed to root a Vodafone Smart Prime 6 (VF 895N) (got it from a friend because it became unresponsive from all the updated google play stuff ) to get linux-deploy running. Just wanted to leave a big thank you here for Adreno306 for his TRWP 3.0.0-0. it did the job very well!
Only the procedure to get it installed differed quite a bit for me, since Flashify is no longer available.
I wanted to preserve boot and just flash trwp to recover, what worked quite well.
The first thing I did was to boot the phone manually in recovery mode (Power+Vol up) and reset it to factory settings from there. It takes a little while. Then follow the setup, go to phone settings, enable developer mode and set usb debugging. If "unlock oem" is not available there, reboot into recovery again, set unlock there and reboot into bootloader.
The prerequisites are adb and fastboot, both must work. Means adb devices and fastboot devices must show the phone. What can make problems under win10 as it sometimes does not detect the phone in bootloader mode. An actual google usb driver is needed, as provided by google.
For me adb worked well, but when rebooted into bootloader with adb reboot bootloader, fastboot didnt detect the phone. With the phone still connected, the windows device manager showed an unknown device with and exclamation mark (!). Right click, install driver, select driver manually, select driver from device list, mark all devices (first entry) and click "disk", then point to the usb driver director and select "ADB fastboot driver". ( A more comprehensive description is available here )
Once adb and fastboot detect the device, it is time to prepare it. Boot to system (normal operation) first. Make sure that the TRWP 3.0.0-0.img is renamed to trwp.img and then
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot boot trwp.img
Now the phone should show the trwp menu, set it up to root the phone and install SuperSU. Reboot into bootloader and
fastboot flash recovery trwp.img
fastboot reboot
Verify with adb reboot recovery, you should see trwp now. Reboot to system.
Now finally go into the app selector, start SuperSU, and root the phone. SuperSu uses trwp recovery mode to install its image and root is done.
Again, big thanks for providing the TRWP image!
Adreno306™ said:
Hello guys.
I have successfully ported TWRP 3.0.0-0 for our Smart Prime 6.
It's 100% working !!
There are NO BUGS !! :good:
DOWNLOAD
NEW LINK: DOWNLOAD
________________________________________
How to install
Via app:
1) Download TWRP 3.0.0-0 from the link above and place it on internal storage of your phone.
2) Download Flashify app from Google Play Store.
3) Open Flashify app.
4) Grant root permissions.
5) Click "Recovery image" and then click "Choose a file"
6) Navigate to the folder where you placed TWRP 3.0.0-0 and choose the .IMG file.
7) Press "Yup!" button and wait.
8) After a while the phone will require reboot. So click "reboot" button.
9) Phone will reboot and automatically boot into TWRP, so you can press reboot to system.
10) Enjoy!
Special thanks to Oneb1t for modded .fstab file! :highfive:
edit: you can use Flashfire app too instead of Flashify, but it's not recommended, because the latest version of the Flashfire app is not flashing properly.
Click to expand...
Click to collapse
Hi, I would like to try your tutorial but I can't root this phone (which is an important step in the tutorial), is there any way someone could help me??
Thanks
Android N Preview npc56p (flashable & image with no encryption and dm verification)
This thread is for the first Android N Preview.
For Android N Preview 2 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **** The following are instruction for installing Android N Preview image released by Google on 3/9/2016. After the installation you will have TWRP recovery 3.0.0-1 and the data partition will be erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery
1- You need to have TWRP installed on your phone.
2- Download this flashable zip.
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N. If your internal storage is unencrypted before flashing it remains unencrypted. Your TWRP is also upgraded to 3.0.0-1.
Method 2: Flash update using a computer
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.0-1.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root
To obtain root after installing this update you should flash SuperSU 2.70 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726. Note that at least at the moment (as of SuperSU 2.70) the root method is a hack solution which requires a lot of further refinement. Many programs are still unable to acquire root and mount the system partition for R/W. However, it is possible to install the android terminal emulator, do an su, mount /system as rw, and do all the modifications within the terminal emulator. Of course you can always use TWRP to modify the system, for which you don't even need to root the device.
Hot dog! First for once... Thanks!
Sent from my Nexus 6 using Tapatalk
#2
will this wipe internal storage ? or only data partition?
For anyone interested...
I enrolled in the Developer Beta program and the OTA worked for me even though I was rooted with SuperSU v2.68.
However, despite installing TWRP 3.0.1 and then SuperSU v2.68 again, root doesn't stick. Fortunately the only critical previously-root-only app I want is a firewall, and Netguard doesn't need root. I can live for a while without Double Tap To Wake, Wakelock detector, Quick Reboot, etc. And the only app that seems to crash is BBC Radio Player, though BBC News and iPlayer still seem ok (warning about libraries, but still plays). And Battery Bot Pro seems to have lost its status bar display...
So it does pretty much what the warnings say - it's stable but not everything will work.
so if i flash this i will still have twrp once rebooted?
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
It would be nice moving forward if Google just made SuperSU/root part of their factory image under developer options. So once you enable developer option, there's a little toggle next to OEM unlock that says "root/SuperSU".
Would make life much easier.
simms22 said:
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
Click to expand...
Click to collapse
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
The zip doesn't include stock recovery so if you flash everything according to the instructions you will have twrp at the first reboot.
This kernel worked great thanks. I'm still decrypted and didn't have to wipe internal storage. I didn't run the .bat I manually flashed the img files. Wiped data with TWRP.
so can we flash this via twrp?
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
no, those are IMG format, flash via fastboot.
I'd wait for root ready then flash...
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
It literally says right next to the link, "Note that it is NOT a flashable zip."
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
it says twrp recovery in title, so I was wondering....
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
chapelfreak said:
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
Click to expand...
Click to collapse
I flashed that boot img and now i am encrypted and boot-looping. No access to SD card.
Does this build have new bootloader and radio? If so, is it backward compatible to Marshmallow roms or do we need to flash back M bootloader and radio to get M roms work?
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
I lold at this. :laugh::laugh::laugh::laugh:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
kclive said:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
Click to expand...
Click to collapse
Toggle on and off airplane mode. Turn off wifi and see if it works. I was at work and had to do this a few times
Flashed phh kernel (su-noverity - 3rd one) and installed this superuser. I now have root working.
Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Worked !!!
Thank you dear. Its worked for mine in p585 oreo android....
Anyone can search mcmilk 7zip in google and download program to extract boot.img.lz4 and get boot.img :good:
use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:
Latest twrp dose not worked on my device but this solution work fine
I can confirm that this method does work. I used it on my SM-P580 yesterday. I would suggest that you first backup your all of your apps, contacts, photos, etc using SmartSwitch. You will need to restore everything after the tablet tells you that it needs to be reset because it wipes everything. After the restore, you will need to enter all of your accounts and passwords again but at least all of the data will be back.
amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse
Im not sure if this post belongs here, you link to the T580 TWRP, not the P580.
Is that one compatible with P580?
nill3bor said:
use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:
Click to expand...
Click to collapse
If I do this, will I be able to mount my SD Card as internal storage? 16gb just isnt enough on this tablet.
Do you have to be on oreo already for this to work I'm still on 7.0 and with my system modified I can't upgrade normally
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
This one worked for me on a P585Y. You just have to skip the steps below.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
Click to expand...
Click to collapse
It will also show on the Device Maintenance, just ignore the warning.
You can freeze some of the system apps to prevent it from showing on the notification again.
amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!
Hello Gyus,
I managed to root the device with the method posted by @amosdinh (Thank you so much). Now I'm trying to configure adoptable storage. So far I didn't achieve this goal. ADB commands doesn't work and I can't install the ASPlugin.zip needed by Root Essentials to set adoptable storage by the app.
TWRP for P585 is corrupted, gives blue/red lines screen. The dev that maintains the code is absent since march. I'm out of luck on this. If anyone have a idea to get adoptable storage on this device while using Oreo, please comment.
Thanks!
---------- Post added at 11:17 AM ---------- Previous post was at 11:11 AM ----------
artaeun said:
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!
Click to expand...
Click to collapse
Just renaming magisk_patched.img to boot.img and adding to .tar file by 7zip worked for me.
We should ask a dev to update twrp for android 8.1
khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
Same freeze for me with the Omni - can't do anything outside of access download mode
Same Problem
cmzizi said:
Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!
Click to expand...
Click to collapse
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
Really wish this wasn't the case. I'd actually keep this thing if it had a working TWRP.
On my SM-P580 I used Odin and TWRP I don't get the black screen but when I reboot to get into TWRP recovery mode it shows the padlock and says swipe to unlock. Tried many times bit cannot swipe and cannot get past this. All I want is to be able to use the SD card as internal storage. HELP???? Thanks!!
luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
thanks in advanced
where can i find stock firmware?
I've just installed magisk using TWRP via command line. P580
I've just installed magisk using TWRP via command line.
Read the entire post before trying this yourself.
I installed the latest TWRP, the one that bugs and doesn't display anything, this allows to root without wiping data. I'm running the latest korean firmware for P580.
Just do this:
1. Launch TWRP and INMEDIATELY LOCK YOUR SCREEN. (I got ghost stripes that disappeared after 2 days when testing this, work with low light so you can notice your screen whenever it tuens on) Please don't forget this point, don't [temporarily] damage your screen as I did.
2. adb push Magisk-v[Current version].zip external_sd
3. adb shell
4. twrp install external_sd/Magisk-v[Current version].zip
After this you just need to install MagiskManager-v[Current version].apk and you will be all done.
But there is one thing...
If you ever get into recovery mode, there is no way out without using adb as far as I know. You can launch download mode and cancel it but you'll boot back to TWRP.
When in twrp touching your screen or any button will wake the device up and will start burning the ghost image to your screen.
So if you know of a method for rebooting to system without using adb, please let me know.
Also a solution for this would be to flash back the stock recovery, wich may or may not force to wipe system, that something that needs to be tested tho.
Update: Ok so, you can use a handy tool called MTKroot on recovery.img.lz4 to get recovery.img, then use 7z to pack it into a tar file and flash that tar file with odin (AP, same as TWRP)
This way you will not have a 0.001% chance of random boot into recovery mode and damage your screen