Related
Xperia Tablet Z 4.4.4 KitKat Rom - Pre-rooted - Includes Recovery
For SGP311 and SGP312 - Wiping is optional​
** 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 **​
Requirements:
Flashtool 0.9.15.0 or higher
Rooted SGP31X (on any other previous Android version) with custom recovery (i.e. XZDualRecovery) installed.
Previous firmwares up to 4.4.2 can be rooted with towelroot.
If your current Rom doesn't have recovery, follow step 10 of this post: http://forum.xda-developers.com/showpost.php?p=53063218&postcount=14 with tablet in USB debugging mode (step 4 of the same post).
This works on locked or unlocked bootloaders and any customization.
This ROM is pre-rooted and comes with recovery. Other than that it is identical to stock rom.
Download links:
SGP311 US_CA_PR https://mega.co.nz/#F!dhMBkRpC!qAsRR7WXJlKwsUwBuv1vig
SGP311 EU1 https://mega.co.nz/#F!p4FzQaqQ!o88OJPX4SyAYOUM3PMb5_A
SGP312 US_CA_PR https://mega.co.nz/#F!El8QnQxC!BlkadNT5FWGF3dLfCbD4mA
Use the link that matches your tablet model. You only need the zip and ftf files. The txt file is just the checksum if you want to verify that your download is error-free.
Instructions:
0- Backup before you start messing with your tablet!
1- Put system.flashable.zip in /sdcard of your tablet.
2- Keep SGP31X_10.5.1.A.0.283_VMo US_CA_PR_NoSystem.ftf on your PC.
3- Disconnect any USB cable that may be attached to your tablet.
4- Reboot to recovery. Preferably to TWRP, but you can make CWM work too.
5- Do not wipe anything.
6- Once in recovery, flash system.flashable.zip.
7- It is important to TURN OFF the tablet after this step.
8- Find and use the Power Off option in the recovery and turn your tablet off. In CWM based PhilZ Touch it is under "Power Options" -> "Power Off". In TWRP it is under "Reboot" -> "Power Off". If you see your tablet rebooting, force it to turn off by pushing the power and volume up keys simultaneously (or however else you can!)
9- Open Flashtool 0.9.15.0 (or higher) and click on the flash icon. Choose flash mode.
10- Navigate to where you have saved SGP31X_10.5.1.A.0.283_VMo US_CA_PR_NoSystem.ftf
11- If you do not want your any of your current data to be wiped uncheck all the items under the "wipe" section. My recommendation however is to wipe.
12- Now flash this ftf with your tablet in flash mode. To put your tablet in flash mode, hold the volume down button when it is off and connect with the USB cable to the PC.
13- Reboot. You are now on rooted 4.4.4.
Credits:
I only put the files together. All the credit should go to XDA's [NUT] and DooMLoRD and many others...
Can I flash this on SGP312?
Kindly request if you could make also a flashable zip with any European rom
FiDra said:
Can I flash this on SGP312?
Click to expand...
Click to collapse
You can and it is not going to break your tablet but there are small differences between the two fimwares. I added a link for SPG312 too.
nick2crete said:
Kindly request if you could make also a flashable zip with any European rom
Click to expand...
Click to collapse
I can try when I have time. PM to me your model and your customization code.
Flashed and works good on SGP312
Thanks!
It worked perfect !
Thank you very much !
I wasn't going to update to 4.4.4 until you offered this solution. Swapping kernels,etc., re-rooting, reinstalling recovery was just more work than it was worth and had the potential to brick the device. Your approach is brilliant! Thank you very much.
However, I am not able to boot into recovery.
Thank you very much for the easy-to-follow instructions.
It worked perfectly on my SGP312. Fully rooted 4.4.4 Kitkat.
Working on 311
najoor said:
OP!!
Click to expand...
Click to collapse
Any chance that you can and will release a 10.5.1.A.0.283 deodex package for 311 / 312 versions / firmwares?
Shanliang- said:
Thank you very much for the easy-to-follow instructions.
It worked perfectly on my SGP312. Fully rooted 4.4.4 Kitkat.
Click to expand...
Click to collapse
How is it performing for you compared to omni rom?
cantenna said:
How is it performing for you compared to omni rom?
Click to expand...
Click to collapse
I wouldn't be able to compare it to Omni as I haven't used it. Actually, I havent used any AOSP 4.4.4 version. But I can say that 4.4.4 stock so far it has worked pretty well.
There's no lag anymore in the options menu.
Battery seems to last as much as it did on 4.4.2, but I'll update this info after some more testing.
Stock launcher feels smoother, although I use Nova Launcher Prime.
I haven't noticed any bugs for now. Perhaps the only thing is a quite short, recurrent distortion in the sound when playing music, but I had that issue in 4.4.2 as well. Haven't found any info on that.
I'll try to report more as I continue using it.
Shanliang- said:
I wouldn't be able to compare it to Omni as I haven't used it. Actually, I havent used any AOSP 4.4.4 version. But I can say that 4.4.4 stock so far it has worked pretty well.
There's no lag anymore in the options menu.
Battery seems to last as much as it did on 4.4.2, but I'll update this info after some more testing.
Stock launcher feels smoother, although I use Nova Launcher Prime.
I haven't noticed any bugs for now. Perhaps the only thing is a quite short, recurrent distortion in the sound when playing music, but I had that issue in 4.4.2 as well. Haven't found any info on that.
I'll try to report more as I continue using it.
Click to expand...
Click to collapse
Tanks man for the feedback. Will you be re-locking the boot loader for the DRM xperia engine, is that possible?
I am really glad that we have this option available to us now
cantenna said:
Tanks man for the feedback. Will you be re-locking the boot loader for the DRM xperia engine, is that possible?
I am really glad that we have this option available to us know
Click to expand...
Click to collapse
yep! it's possble with BackupTA.
I'm surprised to hear there is occasional static sound with a stock ROM from Sony. Can you pleas elaborate as to the problem?
Also, if I follow this tutorial will it automatically relock my boot loader? I'd prefer to keep an unlocked boot loader until I have had opportunity to test drive.
I'm very pleased with my Omnirom ATM. Am curious to try though.
Thanks
Destroyedbeauty said:
Any chance that you can and will release a 10.5.1.A.0.283 deodex package for 311 / 312 versions / firmwares?
Click to expand...
Click to collapse
I've make one for 311/312, you can grab it here :
http://forum.xda-developers.com/xpe...ent/stock-rom-xperia-tablet-z-sgp312-t2876245
Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?
tamasrepus said:
Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?
Click to expand...
Click to collapse
Sorry, I do not and I have not tried this ROM yet
tamasrepus said:
Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?
Click to expand...
Click to collapse
I got my stock 4.4.4 rooted, but unfortunately not with this ROM. Below are my thoughts on what the problem may be.
system.flashable.zip only includes TWRP 2.6.*, which apparently has issues mounting encrypted partitions. These issues are solved in TWRP 2.7; can the OP update system.flashable.zip to include 2.7?
For those who still want to use this ROM, after flashing system.flashable.zip, I'd immediately install dual recovery before rebooting. I've not tested it myself but it's my theory for what will work.
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about 14GB from flashing ROMS and such.Everything seems to have gone smoothly however when I try the oem unlock command I am told that the device is already unlocked.I proceeded to root and then I tried to flash TWRP but I get permission denied.
Also,my Play Store just crashed when I try and type in an app to search for.
The question is-how do I know which factory image is right for my device?
There are a number of 5.1.1 images,I selected the one marked for all carriers except T-Mobile.Could I have selected the wrong image to be causing some of these problems?
Or should I just go ahead and jump up to 6.0.1-there is only 1 image for that release.
I would't think the image mattered that much but something is wrong here.
I got the phone last week from the Amazon sale and I activated it no problem on Verizon and flashed several ROMS no issue.
Advice is much appreciated.
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
dahawthorne said:
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
Click to expand...
Click to collapse
Thanks for the detailed response. I was running 5.1 initially because that is what the phone booted with and I like full-featured ROMS like BlissPop. I guess I'll give 6.0.1 a whirl.It just seemed like it was too new to be rock solid. I had as many features on my old S3 running 4.4.2 as I have seen since then if not more actually. I am curious about Google Now On Tap however.
Hopefully this gets me fixed up.Cheers.
chiadrum said:
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about .......
Click to expand...
Click to collapse
It is possible that the issue is caused because you downgraded the bootloader by flashing 5.1.1.
Flash the complete latest stock 6.0.1 images.
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig. I am guessing that is normal?
The 5.1.1 started working fine after an update all but I still couldn't install TWRP fyi.
Let's see how Marshmallow tastes!
The "does not contain boot.sig and recovery.sig" is standard. I have no idea why it continues to appear version after version, but it has no effect on the installation.
chiadrum said:
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig.
Click to expand...
Click to collapse
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
NLBeev said:
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
Click to expand...
Click to collapse
Thanks guys.
chiadrum said:
Thanks guys.
Click to expand...
Click to collapse
Ok more strangeness.pPhone is working fine,no issues.However I am unable to unlock bootloader using the fastboot OEM unlock command.
The message is "Not supported command in current status".
Yes,OEM unlock is allowed in Dev Options.I tried turning that off in case the indicator was faulty and then I couldn't even attempt to unlock,immediate failure.
Tried this several times after reboots as well.
Build MMB29K.
Any ideas?
Would it be too simple an answer to say that it's because the phone is already unlocked? You couldn't install a new ROM with a locked bootloader.
I myself have been a bit surprised by the peremptory & derogatory comments of some of the very senior members in these forums when people ask what seem to be questions with obvious answers, and I'm beginning to see their point...
Still, I also recognise that an "easy" question is one that you know the answer to, and I don't want to put people off asking questions. Being knocked back myself several times hasn't stopped me asking.
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
chiadrum said:
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
Click to expand...
Click to collapse
Confirmed I am an idiot.Device is unlocked already. Wasn't expecting that.The people way smarter than me who prepared that image took care of it for me.
Not an idiot at all. Like I said, an easy question is one that you know the answer to. Experience counts...
It's not the image that is unlocked - it's the device. Once unlocked, you have to specifically lock it again, but it's neither simple nor a good idea. An unlocked device gives you a far better chance to recover from errors.
Hi
I have installed many of the Android 7.0 ROMS for Shamu and all of them have this annoying problem:
When I dial out I cannot hear the ring or the other person.
When I receive a call I don't often hear the other person but they may hear me.
Yes I've installed the N6 boot loader and radio and do not load any other mods, custom kernels.
I just can't figure this out. Any ideas? Is there a Android 7.0 firmware that I need to install to prepare my Shamu for Android 7?
Thanks
Aussie
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Flashing Stock 7.0
aroy97 said:
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Click to expand...
Click to collapse
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
aussie1234 said:
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
Click to expand...
Click to collapse
Flashing stock does not relock the bootloader.
Didn't work
Ok I flashed stock 7.0 using Wugfresh's tool.
But still when I use the phone I can't hear who is on the other end.
Really odd!
Anyone have any suggestions?
Thanks
Aussie
I'm having the same issue on a stock Nougat phone as well. The problem appeared a few days ago out of the blue. The only band aid fix I've found is the sound about app and force assigned the mic and earpiece functions.
Sadly, this doesn't address the main issue in the first place.
none
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
---------- Post added at 07:53 AM ---------- Previous post was at 07:50 AM ----------
USMC retired said:
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
Click to expand...
Click to collapse
If you need anything else you can PM me
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
stevew84 said:
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
Click to expand...
Click to collapse
have you tried reflashing your radio? Maybe try flashing a MM radio as well
Just wanted to chime in, I think this is actually more of a VoLTE/HD issue. It happens to my N6 that's still on MM. Sometimes the dialtone/ring is there, other times it's not. Would love to know of there's a fix!
Found a fix..
Hello all.
I found a fix to Shamu+Nougat ROM problem when I am called I do not hear the other person and vice versa.
To install Factory Nougat from Google: https://developers.google.com/android/nexus/images
FIRST backup your phone (contacts, files, pics, movies etc) as this will totally erase EVERYTHING!
When you are on the Factory Images for Nexus Devices page click "backed up to your Google Account" then go click 'back' on your browser and click on 'Acknowledge' to see the list of Factory Nougat ROMS for Shamu come up on the right.
Download the Android 7.0 Factory ROM for Shamu/Nexus 6.
Do not flash this stock ROM using Wugfresh's tool. Instead follow precisely the 'Flashing Instructions' on the page https://developers.google.com/android/nexus/images. Allow the phone to reboot and fully set up. Restart the phone again.
Then use Wugfresh to Root the phone and also to install custom recovery (I already have unlocked bootloader).
Now, nothing against Wugfresh Tool (I do not know why the flashing method above works better) as Wugfresh has saved my phone many times.. Its just that Googles recommended flashing instructions worked best.
Now I use the phone and not only do I hear the caller and they hear me I have much better reception (Australia). Yes I did previously flash latest radio but the above method seemed to improve my Shamu 100%.
What I have not done yet is flash a custom ROM in case the problem re-appears. But my phone is rooted and unlocked so I can install other mods that work with Nougat.
Hope this works for you.
Cheers
Aussie
Another Fix Part 2
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
aussie1234 said:
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
Click to expand...
Click to collapse
Has there been a listed fix for people who haven't rooted their nexus?
Not sure if anyone care or still want to go back to 5.0.1.
It is possible if you download COMBINATION_VZW_FA50_G925VVRU4AOJ1 (Google it yourself its free out there.)
After flashing combination file you can root it with kingroot then replace it with superuser ( https://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989 ), then you can use flashfire to flash 5.0.1 rom.
You will need to keep the sboot/bootloader from combination file i order to boot with 5.0.1 kernel.
Anyone know if theres good rom that will still work with this method? I tied some stock root rom ( https://forum.xda-developers.com/ve...ment/rom-stock-rooted-g925v-vru1aoc3-t3115121 ), it seems to be missing some file after flashing. It boots up gets signal, but it is buggy. If anyone know if bugs from flashing this way cannot be fixed then let me know so I can stop trying .
I flashed the COMBINATION_VZW_FA50_G925VVRU4AOJ1 tar file but how do it install apks so i can use kingroot. unless you have forum to share with me
I haven't used the XDA forums in over a year. I don't know if I have the courage to downgrade from 7.0 to 5.X
Snowby123 said:
I haven't used the XDA forums in over a year. I don't know if I have the courage to downgrade from 7.0 to 5.X
Click to expand...
Click to collapse
Something similar for me honestly. I just downloaded the firmware stated, did the steps and it seems to have worked fine. Even with root, I honestly liked 7.0 on this device. Dang locked BL. :/
3Cubed27 said:
I flashed the COMBINATION_VZW_FA50_G925VVRU4AOJ1 tar file but how do it install apks so i can use kingroot. unless you have forum to share with me
Click to expand...
Click to collapse
You can install apks using ADB -- I think you can get it from Android Studio or try https://www.xda-developers.com/install-adb-windows-macos-linux/
Once you have ADB installed, just connect your S6 to your PC, open terminal, and run "adb devices" to confirm your phone is visable
Then to install an apk, have it downloaded on your PC and run
"adb install {path/to/apk}"
Example:
adb install Downloads/NewKingrootV5.3.7_C197_B451_xda_release_2018_06_19_20180620193529_242043.apk
I don't really think there was a 5.0.1 ROM designed for the Revision 4 bootloader outside of the Combination Firmware. I think this may be a reason.
Delgoth said:
I don't really think there was a 5.0.1 ROM designed for the Revision 4 bootloader outside of the Combination Firmware. I think this may be a reason.
Click to expand...
Click to collapse
I know this is old. But I come from a s8. So we should be able to even though rev4 bootloader flash any 5 System IMG. The bootloader from the fa50 combination should suffice to boot any lolipop system since they are not incremented
TheMadScientist said:
I know this is old. But I come from a s8. So we should be able to even though rev4 bootloader flash any 5 System IMG. The bootloader from the fa50 combination should suffice to boot any lolipop system since they are not incremented
Click to expand...
Click to collapse
Correct, you just need the bootloader and kernel capable of booting the system up. This is how I was able to use any of the LP AP Build/System on my rev 3 Note5.
All the LP builds were rev 2. But I had a LP bootloader and kernel. Realistically someone should try, but you might need to root the combo firmware first and use flash fire/flashify/safestrap to flash the system image. Because ODIN might not let you.
Delgoth said:
Correct, you just need the bootloader and kernel capable of booting the system up. This is how I was able to use any of the LP AP Build/System on my rev 3 Note5.
All the LP builds were rev 2. But I had a LP bootloader and kernel. Realistically someone should try, but you might need to root the combo firmware first and use flash fire/flashify/safestrap to flash the system image. Because ODIN might not let you.
Click to expand...
Click to collapse
Yea Odin pushing the rooted firmware with combo boot was patched on s8 about the same time. But now where using edl to push a rooted combination file with su flash fire and safestrap.
My s8 is running a bit 5 nougat combo which that bootloader is reserved for Oreo and pie. But I'm running a rooted system IMG I made up from a equivalent rev2 nougat system and runs fine other than 80% charge limmit on the newer combos. Even my j3 limmits to 80 on combo. But I found a hack to charge to 100% I got posted in the s8 threads. I'm gonna try this over the next few days. If there's a eng bootloader with permissive kernel nougat should be able to be rooted too.
TheMadScientist said:
Yea Odin pushing the rooted firmware with combo boot was patched on s8 about the same time. But now where using edl to push a rooted combination file with su flash fire and safestrap.
My s8 is running a bit 5 nougat combo which that bootloader is reserved for Oreo and pie. But I'm running a rooted system IMG I made up from a equivalent rev2 nougat system and runs fine other than 80% charge limmit on the newer combos. Even my j3 limmits to 80 on combo. But I found a hack to charge to 100% I got posted in the s8 threads. I'm gonna try this over the next few days. If there's a eng bootloader with permissive kernel nougat should be able to be rooted too.
Click to expand...
Click to collapse
The question is, what did you do to.modify your stock rom to be able to boot on the combo bootloader? I'm still a little lost on that.
Delgoth said:
The question is, what did you do to.modify your stock rom to be able to boot on the combo bootloader? I'm still a little lost on that.
Click to expand...
Click to collapse
I didn't on the j3.
TheMadScientist said:
I didn't on the j3.
Click to expand...
Click to collapse
Maybe not on the j3 haha.
Delgoth said:
Maybe not on the j3 haha.
Click to expand...
Click to collapse
Wrong device ****. I got so many phones lying around. I haven't really messed with the s6 much. I got a few other on the front burner
TheMadScientist said:
Yea Odin pushing the rooted firmware with combo boot was patched on s8 about the same time. But now where using edl to push a rooted combination file with su flash fire and safestrap.
My s8 is running a bit 5 nougat combo which that bootloader is reserved for Oreo and pie. But I'm running a rooted system IMG I made up from a equivalent rev2 nougat system and runs fine other than 80% charge limmit on the newer combos. Even my j3 limmits to 80 on combo. But I found a hack to charge to 100% I got posted in the s8 threads. I'm gonna try this over the next few days. If there's a eng bootloader with permissive kernel nougat should be able to be rooted too.
Click to expand...
Click to collapse
This is what I was asking about though. I still can't get anyone to explain how to make the stock ROMs work on the newer more locked devices. It's like a big secret or something. But it is possible on the S6, Note5, and S8. Probably the S7 too.
But 5.0.1, 5.1.1, and 7.0 are built a lot differently and I imagine the method is different.
TheMadScientist said:
Wrong device ****. I got so many phones lying around. I haven't really messed with the s6 much. I got a few other on the front burner
Click to expand...
Click to collapse
Before the S9 Line most everything has been built pretty similarly.
So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.
SynGreis said:
So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.
Click to expand...
Click to collapse
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:
which one do you suggest? i dont see much of a selection.
SynGreis said:
which one do you suggest? i dont see much of a selection.
Click to expand...
Click to collapse
Right now there really aren't any, although there are a few in development, such as AOSP. I think the initial high price, specialized hardware & relative unpopularity has not helped attract any serious development.
I've noticed that ROM development has decreased significantly in the last few years. I remember the days of the Samsung Galaxy Nexus & the HTC Evo 4G where it seemed as if there was a new ROM released every week. I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult.
Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.
mattwheat said:
Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.
Click to expand...
Click to collapse
Mine showed as in rog 2 the last time I reloaded the OS. It's because it searches for "phone 2" and randomly guesses. No biggie, just fix it in the settings. No issues here from playstore, if you do it's common on every Android phone and fixable by clearing the data from the app. Maybe you should reflash the stock firmware? I don't see why you would call this phone ****ty. It's basically running AOSP stock except some theming from Razer. I fixed some freezing issues by reseating the Sim and SD card that I have. This thing rocks, just saying.
I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.
matt that might be just you i havent experienced any issues with this phone whatsoever.
"I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult."
can you provide more info on this A/B partition? id love to see what customizable stuff i can do with this.
mattwheat said:
I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.
Click to expand...
Click to collapse
The freezing is due to a bug in Google Chrome. All you have to do to fix this issue is roll back the app version to 72 because version 76 doesn't work on our RP2.
Edit: uncheck auto update
Only freeze I had so far was with the infamous switch switch to the tele lens. Not a single other issue with software.
Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?
MasterThiefGarrett said:
Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?
Click to expand...
Click to collapse
Take this with a grain of salt, as I just got the RP2, but its the most responsive, "sticky" feeling Android phone I've used. 120hz is like night and day to me.
On a related note, Firefox Fenix with webrender enabled feels significantly more responsive than Chromium atm, as it seemingly renders the whole page instead of stuttering as you scroll like Chrome.
JDBarlow said:
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:
Click to expand...
Click to collapse
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.
SynGreis said:
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.
Click to expand...
Click to collapse
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/
duplicate post
JDBarlow said:
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/
Click to expand...
Click to collapse
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/
SynGreis said:
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/
Click to expand...
Click to collapse
So are you on the global version? If so let it update to MR2 and fastboot flash boot arter97 r12 and you'll be just fine.
Which version are you running then to get stuck on boot logo?
Edit: if you want to stay on MR1 then flash arter97 r11
i tried updating to mr2 but says installation failed.
all i do is
faatboot flash boot kernal.img?
I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done
JDBarlow said:
I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done
Click to expand...
Click to collapse
My only question is, which version zip of magisk did you use in TWRP to flash? 20 or the latest beta? I'm rooted now with a modded boot.img that someone else used the canary/latest beta. Just don't want to screw myself and end up having to flash mr1 again then taking the update.