Kernel source and factory images were released by Razer a few hours ago
https://developer.razer.com/razer-phone-dev-tools/
Excellent can't wait for root
Alright. Can't wait to get root and maybe even twrp
Related
Hey Guys,
I had CWM installed on my nakaski since forever and used it to flash KK/PA before switching to Official Stock Lollipop which I'm currently on. I'm getting good performance for now and really not looking forward for any custom kernel or L based ROM.
But I'm definitely looking to root my N7, which I've read is not as simple as flashing the 'Update-SuperSU.zip' in custom recovery due to some kernel limitations on SELinux resulting in bootloops.
So right now, I'm wondering what should I do to root the thing, I can see the two options:
1. Flash a custom kernel which supports root and then flash the SuperSU zip in recovery.
2. Wait for CF to make the 'zygote' service method stable in the 2.27B build and flash on stock recovery.
I'm really looking to avoid bootloops at all if possible. I don't have the stock Lollipop image on me anymore and I'm stuck on a slow internet connection.
Can anyone suggest me what should I do?
If you think custom kernel is the way to go, please give a link to the thread of the custom kernel for stock L. (franco seems to be stuck on KK, right?)
PS: Can anyone give me a working mirror to TWRP based recovery for grouper. Their web portal seems down.
amangupta53 said:
Hey Guys,
I had CWM installed on my nakaski since forever and used it to flash KK/PA before switching to Official Stock Lollipop which I'm currently on. I'm getting good performance for now and really not looking forward for any custom kernel or L based ROM.
But I'm definitely looking to root my N7, which I've read is not as simple as flashing the 'Update-SuperSU.zip' in custom recovery due to some kernel limitations on SELinux resulting in bootloops.
So right now, I'm wondering what should I do to root the thing, I can see the two options:
1. Flash a custom kernel which supports root and then flash the SuperSU zip in recovery.
2. Wait for CF to make the 'zygote' service method stable in the 2.27B build and flash on stock recovery.
I'm really looking to avoid bootloops at all if possible. I don't have the stock Lollipop image on me anymore and I'm stuck on a slow internet connection.
Can anyone suggest me what should I do?
If you think custom kernel is the way to go, please give a link to the thread of the custom kernel for stock L. (franco seems to be stuck on KK, right?)
PS: Can anyone give me a working mirror to TWRP based recovery for grouper. Their web portal seems down.
Click to expand...
Click to collapse
Hi, amangupta53...
You're correct in that rooting lollipop is no longer just a simple matter of flashing a root update package via TWRP or CWM...
A modified kernel (boot.img) also need's to be flashed as well.
---
Probably the easiest way of 'pushing' the usual files, (su binary & SuperSU app) AND flashing a modified root compliant kernel/boot.img... all at the same time, and conveniently... is via Chainfire's CF-Auto-Root method.
This is the method I've used to root both my Nexus 7 and my Nexus 9, both running Lollipop.
---
Download to your PC, the CF-Auto-Root-grouper-nakasi-nexus7.zip from Chainfire..
Unzip it to some folder location on your computer/PC.
Boot the Nexus 7 into it's bootloader... and USB connect it to your PC.
Inside the folder containing the CF-Auto-Root file's you've just unzipped... run the CF-Auto-Root script appropriate to your PC... one of these, root-windows.bat, root-linux.sh or root-mac.sh.
---
If your Nexus 7's bootloader is NOT already unlocked, it will unlock it... AND IT WILL WIPE EVERYTHING ON THE DEVICE, essentially performing a factory reset... so, do be careful, and ensure you have everything that matters backed up elsewhere before you begin.
---
Once completed, reboot your Nexus 7, and you should be rooted.
Good luck, and hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, amangupta53...
You're correct in that rooting lollipop is no longer just a simple matter of flashing a root update package via TWRP or CWM...
A modified kernel (boot.img) also need's to be flashed as well.
---
Probably the easiest way of 'pushing' the usual files, (su binary & SuperSU app) AND flashing a modified root compliant kernel/boot.img... all at the same time, and conveniently... is via Chainfire's CF-Auto-Root method.
This is the method I've used to root both my Nexus 7 and my Nexus 9, both running Lollipop.
---
Download to your PC, the CF-Auto-Root-grouper-nakasi-nexus7.zip from Chainfire..
Unzip it to some folder location on your computer/PC.
Boot the Nexus 7 into it's bootloader... and USB connect it to your PC.
Inside the folder containing the CF-Auto-Root file's you've just unzipped... run the CF-Auto-Root script appropriate to your PC... one of these, root-windows.bat, root-linux.sh or root-mac.sh.
---
If your Nexus 7's bootloader is NOT already unlocked, it will unlock it... AND IT WILL WIPE EVERYTHING ON THE DEVICE, essentially performing a factory reset... so, do be careful, and ensure you have everything that matters backed up elsewhere before you begin.
---
Once completed, reboot your Nexus 7, and you should be rooted.
Good luck, and hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks Ged.
Seems like I missed CF-Auto Root Method in my list. But I guess it's essentially the automated format of option 1 I listed above. I've already switched to SlimROM 0.8 F2FS which included the M-Kernel and thus easy to root. (A friend pointed it out to me, I took the plunge for F2FS)
Thanks again for the detailed solution. I'm sure it'll be useful for anyone looking to root Stock Lollipop with Stock Kernel.
Cheers!
I am not a programmer and have little knowledge about flashing the ROM so to make sure I understand what I need to do and the order it needs to be done.
My Nexus 10 works great still, I have not had a security update for 2 some years and am concerned about this. Last October I tried to upgrade to 6.0 but it would not recognize the new rom and I ended up going back to the original 5.1 rom.
What I need to know is how to do it in a way I can understand. I have seen a utube video of someone that has been able to do it. So I know it can be done. Just need to know how.
Thanks,
Mike B.
Assuming you have a PC use this tool to unlock then root and install a custom recovery
Next download a Nougat rom like Lineage
Also download gapps and SuperSU
Copy the rom, gapps, and supersu into a folder on your tablet
Now reboot the tablet into recovery and do a full wipe then from recovery
Flash the rom
Flash gapps
Flash SuperSu
Reboot to system and give it a few minutes on the first boot
Moved to:
https://forum.xda-developers.com/showthread.php?t=3609358
Hello
This is a place holder for the Device tree I'm about to submit for our device.
Currently, I'm in the middle of testing restore, but I totally did a cannibal install of 3.1.1 straight to my recovery partition, while I had Rootkernel 5.23 Boot.img TWRP 3.0.2 installed... and I had dual boot.
So I'm fairly confident, I have and can get the other versions of Android working for the E5823.
You all should just be able to pull the specific device branch, download the TWRP source, and then build using your prebuilt binary that Sony supplies, or use Flashtool to extract the ELF of the FOTA-Kernel.
I'll update this as the project progresses
Adios.
https://github.com/NeoBeum/XpeRicoverE5823
EDIT: Yep, just did a full restore. I will test encryption this week. I can go back and forth from the other boot image too. DRM Keys intact too, if you have your DK.ftf.
I'll get it working with Rootkernel & Magisk next.
Test Passed:
Complete Backup & Restore
Restore TA Partition to revert lost DRM Keys on Bootloader Unlock
Current issues:
Install from Zip/Image Permissions - 16/5/2017
Enlighten me please, what is this? Source code for recovery or rom?
MakeHav0 said:
Enlighten me please, what is this? Source code for recovery or rom?
Click to expand...
Click to collapse
TWRP Recovery Source for vanilla Sony AOSP. So no need for CM or Omnirom.
Team Win says they should be able to review the build in about a fortnight
Not even a month ago my Nexus 6P went to bootloop. After a few days of failed attempts and all hopes lost I finally managed to install the fix that deactivates the A-57.
To be able to do all this I downloaded and installed the factory image from the Google site, then launched the command "Flash-All.bat" followed by the installation via ADB of the fix and the recovery TWRP.
Before all this mess I used the LineageOS ROM, while now I'm on official firmware, which among other things I can't even update by installing the latest security patches because the modified boot image is overwritten with the one that requires the use of the whole SoC, A-57 included, with the inevitable return of the bootloop.
I was wondering if there is any modified version of the LineageOS ROM that allows unlucky Nexus 6P users like me to be able to easily use and update the aforementioned ROM, without the risk of finding the phone in bootloop at every start.
I also wondered if after installing the XDA fix that disables the A-57 you can update the device with the latest patches, since maybe I may also have something wrong too.
My question is if a 6P with the BSD fix installed is condemned to remain "as is" forever or if can still receive updates.
You dont have to bother with the terrible stock os. Just use further lineage os.
Howto in short:
1. flash twrp 4 cores from here: https://basketbuild.com/devs/osm0sis/osmods
2. flash latest lineageos from official lineage download site with twrp
3. after flashing now every single time a linegage os image, you have to run N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip from the link above
Thats all. Just use the N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip to configure every single time your lineageos to use 4 instead of 8 cores.
More detailed howto: https://forum.xda-developers.com/nexus-6p/general/bootloop-death-blod-workaround-zip-t3819515
Amazon has finally released FireOS 7 for the Amazon Fire 7 2019! What does this mean?
This means that developers have newer blobs and kernel to work with for Mustang roms! This could be good for development. I don't know if ggow will come back to this device, but I'll personally be trying to get LineageOS 16.0 working on here. I have mirrored the kernel on Github for convenience's sake. https://github.com/turtleletortue/android_kernel_amazon_mustang
One thing to note, do not install FireOS 7 if you want to continue using custom roms. I'm not sure, but it'll likely break amonet and leave you stuck on stock. So until we get an ok either way, just stay on the version you are on.
That being said, have a great day all of y'all! Hopefully something good comes out of this.
Karnak's Pie Source Code (mirror) here: https://github.com/R0rt1z2/android_kernel_amazon_karnak
I've downloaded the bin file, hoping it might be simple to extract the separate boot, recovery and system images from it but alas it's beyond the scope of my knowledge.
I'll try poking it later with binwalk or some other unpacking tools (I've got some amlogic tools on my laptop too) in case they provide me some hints but if anyone reading this can offer suggestions, I'd be happy to experiment
After re-reading the original post re: downgrade and root FireOS, I have bitten the bullet and am currently in process of flashing this.
I have pushed the .bin to device, renamed as .zip.
I've flashed zip, then flashed TWRP before rebooting to recovery and flashing magisk.
I am now looking at the "Amazon" logo whilst the device does its first-boot. Wish me luck!
I will report back as soon as I have more news
edit after 10 mins.
No change. Still looking at the amazon logo
30 mins - still no boot. rebooting to twrp to try again, but without magisk
45minutes - bootloop. amazon logo for a few seconds, black screen, looping indefinitely
Have flashed LOS14.1 as it's the only OS zip file I had sitting on internal storage. Waiting for it to do its first boot
No joy
In the end, the only way o could get device to boot up again was to flash fireos 6, from the original root guide
At this time, the link on the Amazon website for the current version of OS7 is wrong. It will download OS6 (6.3.1.5) instead. The correct link is below.
OS7 for Fire 7 (Mustang):
https://fireos-tablet-src.s3.amazon..._7_9th_Gen-PS7315_user_1958_0018354775684.bin
Click the link for a direct download.
MontysEvilTwin said:
At this time, the link on the Amazon website for the current version of OS7 is wrong. It will download OS6 (6.3.1.5) instead. The correct link is below.
OS7 for Fire 7 (Mustang):
https://fireos-tablet-src.s3.amazon..._7_9th_Gen-PS7315_user_1958_0018354775684.bin
Click the link for a direct download.
Click to expand...
Click to collapse
Have you had success in installing it? Rooting it, etc?
wodgey said:
Have you had success in installing it? Rooting it, etc?
Click to expand...
Click to collapse
If you have a stock tablet and copy the update.bin to '/sdcard' and reboot it can be installed by instigating a system update check. Even with a stock set up though the tablet won't boot if you flash OS6 bootloader files (TZ and LK). If you try and unlock with a modified version of amonet (keeping the OS7 bootloader files) you get a bootloop.
Unlocking and rooting may yet be possible but it is 'above my pay grade'.
MontysEvilTwin said:
If you have a stock tablet and copy the update.bin to '/sdcard' and reboot it can be installed by instigating a system update check. Even with a stock set up though the tablet won't boot if you flash OS6 bootloader files (TZ and LK). If you try and unlock with a modified version of amonet (keeping the OS7 bootloader files) you get a bootloop.
Unlocking and rooting may yet be possible but it is 'above my pay grade'.
Click to expand...
Click to collapse
Ah ok. I see. That makes sense. Thank you for explaining so concisely, yet in words I can understand