base rom is the deodex posted earlier
debloated everything you can get from the playstore, then removed much much more., too much to even try to list.
cherry picked and scavenged pieces and parts from various roms. even resampled a few ringtones, to bring you the smallest, simplest, most lightweight rom I possibly could....well over 800mb of free ram!
i dont think i broke any menu options, but if you find any issues let me know and ill see what i can do
Install via flashfire and wipe everythig including third party apps
Initial startup is only around 2-3 minutes
DOWNLOAD LINK
If for whatever reason you want to go back to stock i put together a prerooted zip you can find here
(or go back to stock via kies/odin)
Enjoy
-D
Crap, I guess I broke the camera somehow...I'll try for a fix later on today
AZ version is with 1.5GB RAM? Seriously!?
Has.007 said:
AZ version is with 1.5GB RAM? Seriously!?
Click to expand...
Click to collapse
Here's a screenshot
Hey, link is not work.
OP updated
Fixed camera
Fixed dialer
Added non animated boot animation to speed up loading time
DamienMc said:
OP updated
Fixed camera
Fixed dialer
Added non animated boot animation to speed up loading time
Click to expand...
Click to collapse
I know may be wrong thread but having troubles installing xposed. .using wanams version 86...any ideas why..first time installed this Rom i used the normal xposed and it was stuck on cricket load screen so had to go back to stock and start over...
Rayizme said:
I know may be wrong thread but having troubles installing xposed. .using wanams version 86...any ideas why..first time installed this Rom i used the normal xposed and it was stuck on cricket load screen so had to go back to stock and start over...
Click to expand...
Click to collapse
Which Lollipop you used? If it's 5.1.1, it shouldn't have problems, but if it's 5.0.2, of course it wouldn't work, because 5.1.1 and 5.0.2 have different sdk, if that's the problem, try search xposed samsung odexed at xda.
D.R-Ult.Googler said:
Which Lollipop you used? If it's 5.1.1, it shouldn't have problems, but if it's 5.0.2, of course it wouldn't work, because 5.1.1 and 5.0.2 have different sdk, if that's the problem, try search xposed samsung odexed at xda.
Click to expand...
Click to collapse
Yea I got it thanks tho... It's 5.1. 1....im not sure why but I for some reason thought a deodexed Rom would use regular xposed and not need the Wanam... I went and installed that version and everything is working great... Anyone having luck with the Bootloader on this?
If I flash the prerooted stock will the custom status be shown? Thanks
Tested on Sm-g530h xxu (sounds crazy)
I wanted a smooth and small rom so i tested this one , i flashed it then i booted ,but i was stuck on cricket logo for about 12min then i rebooted to recovery (twrp)and restored "boot" from my stock backup then it booted .
system ui has stopped shows up every 2 sec, phone stops too , camera if focused the flash doesnt turn off even after closing camera and no status bar , everything was missed up . its a small question but is there a chance to make a mini rom for this model(most used model)?
recovery problem
hi, is there a custom recovery specifically for this model?, cause i want to flash this rom, but whenever i use flashify it reboots on the stock recovery and nothing happens.
Is it necessary to wipe everything after flashing?
Also, will flashing this remove root and/or Xposed?
DamienMc said:
base rom is the deodex posted earlier
debloated everything you can get from the playstore, then removed much much more., too much to even try to list.
cherry picked and scavenged pieces and parts from various roms. even resampled a few ringtones, to bring you the smallest, simplest, most lightweight rom I possibly could....well over 800mb of free ram!
i dont think i broke any menu options, but if you find any issues let me know and ill see what i can do
Install via flashfire and wipe everythig including third party apps
Initial startup is only around 2-3 minutes
DOWNLOAD LINK
If for whatever reason you want to go back to stock i put together a prerooted zip you can find here
(or go back to stock via kies/odin)
Enjoy
-D
Click to expand...
Click to collapse
How did you wipe everything?
Wowwwww
There is a version of grand prime with 1.5gb ram
If I I had 500 free ram with my G530H I become very happy ????
You are lucky with this 800 free ??
How did you flash it bro????
I dont have this device anymore, And i dont have the rom either ...but install like the attached screenshot
DamienMc said:
I dont have this device anymore, And i dont have the rom either ...but install like the attached screenshot
Click to expand...
Click to collapse
What app is that?
pikagunmike2 said:
What app is that?
Click to expand...
Click to collapse
FlashFire app
I have not gotten the phone unbridled can you help?
Related
Affected devices:
- G4 all versions
- ? (More LG phones updated to 6.0 comming)
Affected ROMs
- Stock 6.0
It seems that some deodexed ROMs have Xposed working
We'd like to know how users can help on this, We can provide you with stock files so you, developers, can work.
Typical case:
Yakandu said:
Xposed SDK 23 for LG G4 is not working, the phone gets stuck in bootlogo. Lot of people is reporting this
"More info:"
Stock LG G4 6.0 ROM, international 20A variant. (The common one), Rooted and Bootloader unlocked.
xposed-v78-sdk23-arm64.zip isntalled with TWRP after flashing the firmware.
After flashing and wiping cache and dalvik, the phone boots and gets stuck on the bootlogo (LG logo shining and LED pulsating).
So i rebooted to TWRP and flashed "unistall Xposed" by rovo and it booted again.
Here you have people with the same problem: http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593/page43
Maybe LG did the same as samsung and touched ARM or ODEX files?
Click to expand...
Click to collapse
Hell yeah! Good idea to start a thread I have exactly the same problems (Stuck on LG-Logo Screen with LED flashing blue).
Didn't even try the uninstaller zip from rovo89 (restored backup within twrp). Would be so nice if somebody found a solution or a workaround until rovo maybe fixes it. Would be nice if help is gathered here
I don't own a G4 to test, but you guys tried this?
http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593
fabio000 said:
I don't own a G4 to test, but you guys tried this?
http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593
Click to expand...
Click to collapse
Thats just the way to flash xposed without an unlocked bootloader, doesnt work on MM as with unlocked boots
Follow_and_Feel said:
Hell yeah! Good idea to start a thread I have exactly the same problems (Stuck on LG-Logo Screen with LED flashing blue).
Didn't even try the uninstaller zip from rovo89 (restored backup within twrp). Would be so nice if somebody found a solution or a workaround until rovo maybe fixes it. Would be nice if help is gathered here
Click to expand...
Click to collapse
The uninstaller works
Yakandu said:
Thats just the way to flash xposed without an unlocked bootloader, doesnt work on MM as with unlocked boots
The uninstaller works
Click to expand...
Click to collapse
Ok thank you. Good to know. I think we might just need to wait for another version of the xposed.zip. Maybe the next one will work for us. Just be patient But if somebody finds a way I wouldn't say no to it
The only working version i've seen so far is this rom http://forum.xda-developers.com/g4/development/h815-genisys-rom-1-0-classic-v10g-t3192649
I backed up and then dirty installed over my previous stock MM 20a
I had some memories app force closing but other than that it seems to work well
Yakandu said:
Affected devices:
- G4 all versions
- ? (More LG phones updated to 6.0 comming)
Affected ROMs
- Stock 6.0
It seems that some deodexed ROMs have Xposed working
We'd like to know how users can help on this, We can provide you with stock files so you, developers, can work.
Typical case:
Click to expand...
Click to collapse
Hey. Just stumbled over this thread. Maybe this works for you? I'm too scared to try it myself Don't wanna brick it. But I think I'll try it later. I'll report if it's working or not. Cheers
EDIT: Flashed it, but had many fc's like bluetooth not working, several apps and smart notice and restored backup. Think I'll wait until official version is running on our phones. But anybody who wants to try it - go ahead! In the thread there are several posts about how to get everything to work I just don't want to mess up things and will wait for the official part
so it is the odex files... not good for us
anyone tried the new v79?
Yakandu said:
anyone tried the new v79?
Click to expand...
Click to collapse
Yes, i tried the v79, not working.
Stuck on LG life's good logo blinking blue light, coukdn't flashed uninstaller and back to normal without exposed
at least i'm not the only one....
Hello all! I would like to finally present to you the prerooted flashable zip of the latest 5.1.1, which also includes the patch fix for the Messages problem. I have also included into the zip a Torch flashlight boost and Z5 sound enhancements!
To flash this, be sure you have TWRP recovery installed. If you need to know how to have recovery, follow my guide in the link below to get your phone started.
This is the latest build straight from Xperifirm, that includes the patch for Messaging issues. This is not based off of anyone else's customized builds. This is stock being prerooted with some helpful mods.
Credits to:
@androidexpert35 for the Z5 enhancements
@[NUT] for XZdualrecovery
@olokos for the Flashlight boost mod
@zxz0O0 for the PRFcreator
Please hit thanks when I've helped you with everything you need for the best of your Z3v!
https://mega.nz/#!S5U0kL7L!DQvTvQjTnWXY-858Dr8WvjeeHdRgR-Kxfv2SFzpjqGY
Note: For those who want to get Xposed, go here http://forum.xda-developers.com/showthread.php?t=3034811. Be sure to grab the >>xposed-v80-sdk22-arm.zip<< as this is the one best compatible for our ROM.
The download is asking for a decryption key?
pvcdroid said:
The download is asking for a decryption key?
Click to expand...
Click to collapse
Same here
decryption key?
Same here
Sorry abut that guys, I fixed the link just now!
Thanks and thanked, nice job. Dirty flashed, no problems.
Afterwards, flashed the xposed-v80-sdk22-arm.zip to get xposed and greeted by lovely black screen. Bummer, not sure what happened. I used sdk21 back with 5.0.2 naturally. Also, don't recall why but never updated past v74 either
I had xposed and dirty fleshed then reinstalled and it was being weird. Rebooted a few times and finally got it all back. Apex launcher here, so I'm not sure what happened.
Edit: Thanks for the upload gigaspx.
Which xposed version did you end up using?
I rebooted several times before giving up and reflashing 5.1.1 ftf. I'm leaving xposed alone for now. This is my only phone, and the reboot after flashing xposed or the ftf takes way too long for me try brute force without any confirmation
Giga your zip is working great, sorry to derail
darker_slayer said:
Which xposed version did you end up using?
I rebooted several times before giving up and reflashing 5.1.1 ftf. I'm leaving xposed alone for now. This is my only phone, and the reboot after flashing xposed or the ftf takes way too long for me try brute force without any confirmation
Giga your zip is working great, sorry to derail
Click to expand...
Click to collapse
Sdk22 build 80 with apk 3 build 4 and gravitybox, blacklist, bubble upnp, xtether.
thanks for this, any plans to deodex this in the future?
darker_slayer said:
Which xposed version did you end up using?
I rebooted several times before giving up and reflashing 5.1.1 ftf. I'm leaving xposed alone for now. This is my only phone, and the reboot after flashing xposed or the ftf takes way too long for me try brute force without any confirmation
Giga your zip is working great, sorry to derail
Click to expand...
Click to collapse
direct link framework : http://forum.xda-developers.com/attachment.php?attachmentid=3631562&d=1454436745
Installer : http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
Everything's good now, grabbed the wrong framework before
shakan09 said:
thanks for this, any plans to deodex this in the future?
Click to expand...
Click to collapse
That will be entirely up to @Tigerhoods to do this, alonng with whatever modifications he wants to make. I just make things easier for people by attaching along some goodies that can make the ROM more special.
How do you dirty flash this phone?
Great job many times over @GigaSPX!
Great job
Thanks for sharing this with us
clearionr said:
Can I just flash this via recovery? It's not showing up in flashmode
Click to expand...
Click to collapse
The best way to flash is through TWRP recovery.
Can someone try screen mirroring with this build? I'm having problems with the one tigershark made with which causes a forced reboot. Drm key issue? From the comments here it looks like this build started from the other current one he built in the dev section. It's a huge pita to try to debug because after every reboot it takes 20 minutes for apps to rebuild.
pvcdroid said:
Can someone try screen mirroring with this build? I'm having problems with the one tigershark made with which causes a forced reboot. Drm key issue? From the comments here it looks like this build started from the other current one he built in the dev section. It's a huge pita to try to debug because after every reboot it takes 20 minutes for apps to rebuild.
Click to expand...
Click to collapse
What? No! Mine isn't based off of his and it's the most current build with his not having the new patch that fixes messaging problem. I grabbed mine straight from Xperifirm.
I have searched a lot on the web and xda but cannot find any solutions. As far as I know I have correctly installed the Xposed framework using TWRP but when rebooting I get stuck on the Samsung logo screen and have to recover to fix. I have tried various versions of the framework and always get the same issue.
Android version - 5.0.2
Installed ROM (stock or custom ROM) - Stock ROM (Would install custom if it helps but cant decide which one yet)
Names of the file you tried to flash - I tried 3 - xposed-v67-sdk21-arm.zip, xposed-v72-sdk21-arm.zip, xposed-v86-sdk21-arm.zip
Error messages - none, but gets stuck at the samsung logo on boot
I really wanted to install the custom ROM Acheron, but dont think its compatible with my device so if anyone can recommend a good custom ROM I am all ears
DJRenegade88 said:
I have searched a lot on the web and xda but cannot find any solutions. As far as I know I have correctly installed the Xposed framework using TWRP but when rebooting I get stuck on the Samsung logo screen and have to recover to fix. I have tried various versions of the framework and always get the same issue.
Android version - 5.0.2
Installed ROM (stock or custom ROM) - Stock ROM (Would install custom if it helps but cant decide which one yet)
Names of the file you tried to flash - I tried 3 - xposed-v67-sdk21-arm.zip, xposed-v72-sdk21-arm.zip, xposed-v86-sdk21-arm.zip
Error messages - none, but gets stuck at the samsung logo on boot
I really wanted to install the custom ROM Acheron, but dont think its compatible with my device so if anyone can recommend a good custom ROM I am all ears
Click to expand...
Click to collapse
https://mega.nz/#!yMQ0ABIb!X_FrC0Uds2By-liblHEa9TTdy5v0wWIb76Jxr2JzKRo try this
Sent from my SM-A9100 using Tapatalk
Not sure I'd blindly follow a mega-upload...but maybe I'm paranoid. @DJRenegade88 I know you say you searched the web, but it sounds like you're trying to use the official xPosed. There's a huge red sign stating that if you try that on Samsung you will boot loop. For Android 5'0.x you need arter's xPosed
http://forum.xda-developers.com/showthread.php?t=3113463
If you update to 5.1 or 6 you'll need to get the Wanam version instead (I'd link, but don't wish to confuse you as you have 5.0.x (sdk21)
Nergal di Cuthah said:
Not sure I'd blindly follow a mega-upload...but maybe I'm paranoid. @DJRenegade88 I know you say you searched the web, but it sounds like you're trying to use the official xPosed. There's a huge red sign stating that if you try that on Samsung you will boot loop. For Android 5'0.x you need arter's xPosed
http://forum.xda-developers.com/showthread.php?t=3113463
If you update to 5.1 or 6 you'll need to get the Wanam version instead (I'd link, but don't wish to confuse you as you have 5.0.x (sdk21)
Click to expand...
Click to collapse
yea I was trying the official and I have seen that red text about samsung bootloops lol, dunno how I missed that the first time, thanks for the clarification. Is there a specific version I should download? I see he lists a few, I am guessing the most recent (xposed-v75-sdk21-arm-arter97-snapdragon.zip) is the correct one?
The number "75" "86" etc is the version number so everything you typed is correct 21 arter arm but you want whatever is the highest, with one caveat: if there is an 86 a few modules will not work (in short they will be forbidden from running by xPosed for bad coding); I'm guessing quite a few of the 5'0'x specific modules may get caught by this. If you find a module you can't live without that doesn't work (and gives a very specific, noticeable error in the xPosed log) you might want to stick with 85
Doesn't work
It took 5 minutes to boot and now it's optimizing all my apps. I don't think it works.
FyrestoneROM T113The simplicity of TouchWiz system without superfluous
Code:
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
Introduction:
This Rom is the stock samsung without annoying apps and with some tweaks made to make your life easier.
I have a lot to do for make it better, but I hope you appreciate my work, if you don't thanks for giving me a chance.
Features:
Based on T113XXU0ARB1
Debolated - Samsung and Google apps (350 MB of useless apps)
Deodexed
Zipaligned
Faster animation scale
Knox Free
Removed boot sound
Rooted with SuperSu
Busybox
Sony System signature - Feel free to install sony apps from play store!
AOSP Keyboard
Removed Samsung Update
Allow apps access to external storage
Removed Loud volume warning
Cyanogen/LineageOS UI sounds
Tweaks:
Battery Tweaks
Better scrolling
Video acceleration and HW debugging
Better RAM management
Google DNS
Download Link:
DOWNLOADMD5: b7694314c6cfe88f013522b86319210d
Old version [4 Feb 2017]: DOWNLOAD
MD5: 283aa300c00ae227b4362945925db4b4
Old version [4 Jan 2017]: DOWNLOAD
MD5: 6f97e788b0b2571742b256e6fcaf1e86
How to install The Rom:
Update your bootloader and baseband to XXU0ARB1 before flash!
1. Flash TWRP 2.8.7.0.tar with Odin 3.12.10.
2. Flash TWRP 3.0.2-0.img inside the recovery (Select Install image and choose Recovery partition).
3. Reboot into TWRP 3.0.2-0.
4. Copy FyrestoneROM_T113_XXXXX.zip in your SD Card.
5. Wipe: System, Data, Cache and Dalvik.
6. Optional – Wipe Internal Storage.
7. Install FyrestoneROM_T113_XXXXX.
8. Reboot and wait about 10 minutes.
How to install The Firmware:
1. Download and extract a zip file containing your desired firmware.
2. Open Odin Tool.
3. Boot your device in the "Download Mode":
(Press Volume Down, Power and Home buttons at same time for 5-8 seconds until download mode is active.)
4. Connect your device to PC via the USB cable while in download mode.
5. Next, check the "Auto Reboot" and "F. Reset Time" options in Odin Tool.
6. Hit the AP/PDA button then browse and select a tar.md5 file from the extracted folder.
7. Finally press the start button to begin flashing the firmware update on your device.
Credits:
Google for Android OS
Samsung for FW and source
Sony for System signature
Cyanogenmod for File manager
@SuperR for the kitchen
@bravonova for Build.prop Tweaks
@Chainfire for SuperSu
@mrRobinson for AdAway
XDA:DevDB Information
FyrestoneROM, ROM for the Samsung Galaxy Tab 3
Contributors
Jimbus369
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: T113XXU0AQA1
Based On: STOCK Samsung
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2017-02-04
Created 2017-01-04
Last Updated 2018-08-18
Reserved
Changelog:
27 July 2018:
Updated to XXU0ARB1
Fixed all previous issues
Removed Cyanogen File manager and Adawey
Now Thunderoar Kernel v5.0 is fully compatible
Updated Busybox and SuperSu
4 Feb 2017:
Updated to XXU0AQA1
Removed some Bloatware
Deodexed
Zipaligned
Faster animation scale
Allow apps access to external storage
Loud volume warning removed
Cyanogen/LineageOS UI sounds
Battery Tweaks
Increase Quality Of Media Streaming
Fixed Google DNS
Fixed Calendar Sync
Various build.prop changes
Various fix
4 Jan 2017:
Initial release
Known issues:
Calendar doesn't synchronize --> Calendar_sync_fix.zip
Tablet doesn't support vpn functionality --> VPN_FIX.zip
Print spooler does not works --> PrintSpooler_FIX.zip
Fantastic! Finally we've got a rom of our very own, for which you've got my immense thanks. I'm very much looking forward to trying it out.
Unfortunately when I flashed it there was a loooong wait on the Samsung logo, and then... Well, after an hour I booted back to recovery to start over.
I honestly don't think your rom was the problem though, because from some point last night everything I tried - custom rom flashing and nandroid backup restores - wound up the same way. Odin + stock + root got a usable system at least, and today's been too busy to try again. But when I do I'll post back about how it goes.
(Sadly, I can't go back in time to see what order I did things and look for a pattern if this happens again. In case it might be useful to anyone, I know for sure I'd gotten stock set up comfortably and made a complete backup before giving thunderoar's T113 kernel a whirl, and that went swimmingly. Even had mounts2sd properly recognizing external sd set up after a long struggle, though not actually enabled yet. Don't know what else i did between making that backup and trying to flash this, but it's likely I just screwed something up somehow.)
PushyPhoenix said:
Fantastic! Finally we've got a rom of our very own, for which you've got my immense thanks. I'm very much looking forward to trying it out.
Unfortunately when I flashed it there was a loooong wait on the Samsung logo, and then... Well, after an hour I booted back to recovery to start over.
I honestly don't think your rom was the problem though, because from some point last night everything I tried - custom rom flashing and nandroid backup restores - wound up the same way. Odin + stock + root got a usable system at least, and today's been too busy to try again. But when I do I'll post back about how it goes.
(Sadly, I can't go back in time to see what order I did things and look for a pattern if this happens again. In case it might be useful to anyone, I know for sure I'd gotten stock set up comfortably and made a complete backup before giving thunderoar's T113 kernel a whirl, and that went swimmingly. Even had mounts2sd properly recognizing external sd set up after a long struggle, though not actually enabled yet. Don't know what else i did between making that backup and trying to flash this, but it's likely I just screwed something up somehow.)
Click to expand...
Click to collapse
Upgrade your firmware to PH5 before flash and use TWRP 3.0.2-0.
Firmware: http://samsung-updates.com/device/?id=SM-T113
TWRP: https://dl.twrp.me/goyave/
Wipe all partition in TWRP:
System, Cache, Dalvik and if you can internal Storage.
Thunderoar Kernel isn't compatible with PH5 firmware for the moment.
Let me know how it goes
Thanks so much for responding even though I didn't specifically ask.
Pretty much all my knowledge comes from following instructions in these forums and piecing little bits of information together, so I've got a few questions - trying to understand the "why" behind these things in order to be more self-sufficient. Please feel free to point me towards resources where I can learn more!
Jimbus369 said:
Upgrade your firmware to PH5 before flash and use TWRP 3.0.2-0.
Click to expand...
Click to collapse
This is a surprise to me - I'd always thought that when flashing a new ROM, everything gets replaced. I never would have figured this part out on my own!
Firmware: http://samsung-updates.com/device/?id=SM-T113
Click to expand...
Click to collapse
There's no Canadian version - but should I presume that, since this is a Wi-Fi only device, the CSC isn't too important?
How much does this matter even when using a device with a network connection?
TWRP: https://dl.twrp.me/goyave/
Click to expand...
Click to collapse
(Ooops, forgot to do this right off the bat. My bad!)
Does recovery version generally make a big difference?
Wipe all partition in TWRP:
System, Cache, Dalvik and if you can internal Storage.
Click to expand...
Click to collapse
I've been wiping Data as well - is that not necessary?
Does wiping Internal Storage have a big effect? I suppose there's a fair bit of app-specific stuff in there that could cause issues?
Thunderoar Kernel isn't compatible with PH5 firmware for the moment.
Click to expand...
Click to collapse
Ah well, soon enough!
Let me know how it goes
Click to expand...
Click to collapse
Of course! You're investing time in putting this together, and helping out users; the very least I can do is let you know what's going on with that time you've invested!
Okay, about to check on the firmware installation!
PushyPhoenix said:
This is a surprise to me - I'd always thought that when flashing a new ROM, everything gets replaced. I never would have figured this part out on my own!
Click to expand...
Click to collapse
When you install a rom, especially a TW one, in most case you need a specific Bootloader to cause it to start and work smoothly.
Wikipedia:
A boot loader is a computer program that loads an operating system or some other system software for the computer after completion of the power-on self-tests; it is the loader for the operating system itself. Within the hard reboot process, it runs after completion of the self-tests, then loads and runs the software. A boot loader is loaded into main memory from persistent memory, such as a hard disk drive or, in some older computers, from a medium such as punched cards, punched tape, or magnetic tape. The boot loader then loads and executes the processes that finalize the boot. Like POST processes, the boot loader code comes from a "hard-wired" and persistent location; if that location is too limited for some reason, that primary boot loader calls a second-stage boot loader or a secondary program loader.
The bootloader runs your rom with specific instructions, if the rom does not support an older bootloader simply does not boot. My rom does not support the older bootloader. A zip flash in this case cannot upgrade a delicate part like the bootloader. You need to flash the newer one with Odin.
There's no Canadian version - but should I presume that, since this is a Wi-Fi only device, the CSC isn't too important?
How much does this matter even when using a device with a network connection?
Click to expand...
Click to collapse
The latest update for your country is PA5. Try with THIS.
Your country code is XAC.
The CSC (Sale Country Code) Is that part of the firmware that contains all the telephone operator customizations (e.g. WAP, MMS) for the intended country. As far as i know, It is not important for us.
(Ooops, forgot to do this right off the bat. My bad!)
Does recovery version generally make a big difference?
Click to expand...
Click to collapse
Yes, the Recovery can make the difference.
I've been wiping Data as well - is that not necessary?
Does wiping Internal Storage have a big effect? I suppose there's a fair bit of app-specific stuff in there that could cause issues?
Click to expand...
Click to collapse
I forgot to write data, my bad! But i wrote it in the instructions in the first topic. For personal experience i had different issues when I didn't formatted the Internal Storage. The Android folder, .thumbnails and others, can create issues.
Ah well, soon enough!
Click to expand...
Click to collapse
I hope that in the next update we could use this kernel. :fingers-crossed:
Of course! You're investing time in putting this together, and helping out users; the very least I can do is let you know what's going on with that time you've invested!
Okay, about to check on the firmware installation!
Click to expand...
Click to collapse
I want to give my best support at all users in difficulty, if you have a problem just ask. :good: :good:
Sorry for my english
Jimbus369 said:
Sorry for my english
Click to expand...
Click to collapse
You're doing just fine!
I'll reply more later, but wanted to report that it's installed and running very smoothly! Haven't played around much but will do at home later.
If you've got any tips for getting mounts2sd up and running I'd really appreciate it!
PushyPhoenix said:
You're doing just fine!
I'll reply more later, but wanted to report that it's installed and running very smoothly! Haven't played around much but will do at home later.
If you've got any tips for getting mounts2sd up and running I'd really appreciate it!
Click to expand...
Click to collapse
I'm happy to hear it. Anyway, I don't know how mounts2sd works. Have you already tried HERE?
Jimbus369 said:
I'm happy to hear it. Anyway, I don't know how mounts2sd works. Have you already tried HERE?
Click to expand...
Click to collapse
Yup, that's the app I'm using, but haven't been able to get my external partition mounted properly. I did manage it once, think it was with thunderoar's kernel though.
Sent from my SM-G900W8 using XDA Labs
Jimbus369 said:
I'm happy to hear it.
Click to expand...
Click to collapse
Life has gotten in the way of playing around with this, but thought I'd send you an update as I said I would...
Your rom is running really nicely on my tablet as I use it daily. It's smooth and small, with no unexpected reboots or fc's on installed apps. Didn't wipe internal SD but it hasn't given me any issues with existing data (probably because there wasn't much to start with).
One thing that has caused a problem is calendar sync. It looks like you've taken out the actual syncing service, so when I try to access my calendars through any app I'm asked to add a new Google account, even though everything's already set up in "Accounts" under Settings. I haven't tried running the "calendars.providers.apk" from my other phone, that should fix the problem - but I don't want to use the wrong version and break something!
Also, I've confirmed that the only time I got mounts2sd working, it was with thunderoar's kernel. So guess that's going to have to wait.
A few adjustments I made to the setup were to uninstall all "unnecessary" system apps (not needed to run the device), and re-install them from the store. This way I've got 676mb free on /system and still over 1.5GB free on internal storage.
I've also added a multi-reboot menu to make getting into recovery or download mode simpler, and this is loading more quickly on your rom than stock. I've also had to modify permissions.xml to allow apps to access external storage by default, and made another tweak to disable the "loud volume warning" (don't remember quite what it was offhand).
Would you consider adding these to a future version?
Again, thanks SO much for putting this together, answering questions, and doing your thing. It's greatly appreciated!
PushyPhoenix said:
Life has gotten in the way of playing around with this, but thought I'd send you an update as I said I would...
Your rom is running really nicely on my tablet as I use it daily. It's smooth and small, with no unexpected reboots or fc's on installed apps. Didn't wipe internal SD but it hasn't given me any issues with existing data (probably because there wasn't much to start with).
One thing that has caused a problem is calendar sync. It looks like you've taken out the actual syncing service, so when I try to access my calendars through any app I'm asked to add a new Google account, even though everything's already set up in "Accounts" under Settings. I haven't tried running the "calendars.providers.apk" from my other phone, that should fix the problem - but I don't want to use the wrong version and break something!
Also, I've confirmed that the only time I got mounts2sd working, it was with thunderoar's kernel. So guess that's going to have to wait.
A few adjustments I made to the setup were to uninstall all "unnecessary" system apps (not needed to run the device), and re-install them from the store. This way I've got 676mb free on /system and still over 1.5GB free on internal storage.
I've also added a multi-reboot menu to make getting into recovery or download mode simpler, and this is loading more quickly on your rom than stock. I've also had to modify permissions.xml to allow apps to access external storage by default, and made another tweak to disable the "loud volume warning" (don't remember quite what it was offhand).
Would you consider adding these to a future version?
Again, thanks SO much for putting this together, answering questions, and doing your thing. It's greatly appreciated!
Click to expand...
Click to collapse
The calendar sync issue should be fixed in the next update.
Anyway, If I have enough time, the next update should contain a lot of new features. Your suggestions are already planned :good:
Jimbus369 said:
When you install a rom, especially a TW one, in most case you need a specific Bootloader to cause it to start and work smoothly.
....
The bootloader runs your rom with specific instructions, if the rom does not support an older bootloader simply does not boot. My rom does not support the older bootloader. A zip flash in this case cannot upgrade a delicate part like the bootloader. You need to flash the newer one with Odin.
Click to expand...
Click to collapse
One more question about this: The way you've worded the second paragraph seems to imply only that older bootloaders don't work with newer roms, so are newer bootloaders backwards compatible? Say I've got the PH5 bootloader installed and I want to restore a backup of the previous firmware, do I have to flash that firmware first?
Sorry if it seems obvious, this is how we learn!
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
One more question about this: The way you've worded the second paragraph seems to imply only that older bootloaders don't work with newer roms, so are newer bootloaders backwards compatible? Say I've got the PH5 bootloader installed and I want to restore a backup of the previous firmware, do I have to flash that firmware first?
Sorry if it seems obvious, this is how we learn!
Sent from my SM-G900W8 using XDA Labs
Click to expand...
Click to collapse
Absolutely it isn't obvious, don't worry . The Bootloader, for my personal experience, are backwards compatible. I don't have a scientific knowledge about this, but for what I did with other device it can work. Just try :fingers-crossed:, don't forget a full backup.
Calendar_sync_fix.zip
Here is a fix for calendar sync.
@PushyPhoenix Thanks for reporting this issue
Jimbus369 said:
Calendar_sync_fix.zip
Here is a fix for calendar sync.
@PushyPhoenix Thanks for reporting this issue
Click to expand...
Click to collapse
This is a huge help, as one reason for getting this tablet was to use the calendar on a bigger screen.... Thanks so much!
---------- Post added at 10:58 PM ---------- Previous post was at 10:50 PM ----------
Jimbus369 said:
The Bootloader, for my personal experience, are backwards compatible. I don't have a scientific knowledge about this, but for what I did with other device it can work. Just try :fingers-crossed:
Click to expand...
Click to collapse
Fantastic - it worked on my S5 (had to restore a backup to retrieve some data).
don't forget a full backup.
Click to expand...
Click to collapse
Never! The most important thing, along with wiping.
When is coming to FyrestoneROM V2 ?
And thank you very much. So love...
Does this work on sm-t116ny ?
Because no development for sm-t116ny .
dhruvpatel_9880 said:
Does this work on sm-t116ny ?
Because no development for sm-t116ny .
Click to expand...
Click to collapse
I don't think it can work. If your device codename is Goyave you can try. Let me know if it works
Jimbus369 said:
I don't think it can work. If your device codename is Goyave you can try. Let me know if it works
Click to expand...
Click to collapse
First of all thanks for replying
My device codename is Goyave3g5m probably .
Can you please tell me which all models have same codename "Goyave"?
And cm 11 for sm-t116 works well on my sm-t116ny.
I will try and let you know does it boots .
---------- Post added at 01:55 PM ---------- Previous post was at 01:40 PM ----------
It is working on sm-t116ny
But wifi hotspot not working
Please help
dhruvpatel_9880 said:
First of all thanks for replying
My device codename is Goyave3g5m probably .
Can you please tell me which all models have same codename "Goyave"?
And cm 11 for sm-t116 works well on my sm-t116ny.
I will try and let you know does it boots .
---------- Post added at 01:55 PM ---------- Previous post was at 01:40 PM ----------
It is working on sm-t116ny
But wifi hotspot not working
Click to expand...
Click to collapse
T113/T113nu and T116/T116ny have a similar codename and hardware (The recovery have goyave codename, therefore any rom with goyave codename can be flashed). For the hotspot, maybe some missing libraries, a different driver or a different kernel makes hotspot broken. Try to restore your kernel from a previous backup.
This is an early release, but just like the other it's fully functional as a daily driver.
Note:
Still no root method for our device on Nougat
Features:
Pixel 2 emoji
Pixel 2 fonts
Pixel 2 wallpapers (live and still)
Pixel 2 sounds and notifications
Google Assistant
Google Lens
Unlimited Google photo storage (Pixel feature)
Round icons (uses apps native icons, not masks)
Daydreams enabled on battery power (screensaver can be used like always on display, until 15% battery)
360° rotation, everywhere
Power menu from sleep
All quick settings enabled (including mobile data toggle)
Hotspot activation bypass
System menu translated into every language
To do:
Lower the 15% screensaver limit
Add Pixel 2 logo and startup animation
Lockscreen background
Lockscreen default widgets (phone & camera)
What else do you want?
Bugs:
Selfie video doesn't record (prolly not fixable until we get an updated app)
Anything else?
Installation:
From 6.0.1:
Flash with Flashfire and do full wipe
From 7.1.1:
*Must use PC*
Method A
1. Unzip ROM.
2. Flash the included eng_root kernel with Odin.
3. Double click the included "Install.bat"
The script will wipe your data for you (and not touch the internal sd)
Method B
Use Odin to downgrade to 6.0.1 then flash zip with flashfire.
Download
I'll add more screenshots tomorrow
As of right now, even with the custom ROM, there is no root, correct?
I installed it, and every time I boot, I get a System UI has stopped error.
@NateDogg1232
Did you wipe?
... Correct no root yet, until we get a permissive kernel
DamienMc said:
@NateDogg1232
Did you wipe?
... Correct no root yet, until we get a permissive kernel
Click to expand...
Click to collapse
Yes, I did wipe.
I even did it again using the default recovery just to make sure.
More screenshots
Please, upload more screenshots, I would like to install this rom but I do not know if I really have any problems when using it, as it is in terms of speed, can it really be used now?
@RaghebAlama
Sorry I am having problems uploading more screenshots (used all my data this month)
I'll be sure to do it this evening when I'm on wifi.
I've been running this for a week now and haven't had any issues yet
But after the above comment you might want to grab full Odin updates as well, just in case you need to recover
@NateDogg1232
What method did you use to install?
What device do you have?
I would recommend going back to stock and giving it another try.
I apologise tho, I tried to get a few testers this time but never find any. It's hard to test every scenario with just one device
I used FlashFire from actually your first GPE ROM.
I have the J320A
I will reset from stock and try again as soon as I can and try again.
Whether it works or not, though. Thank you for your work on this phone
I bet that's it, I'm not sure I tried to install from v1.
Can't think of why it would fail except maybe if goodlock has files on your sd and this systemui is trying to use them... If you want to test that just pull your sd, because wipe already did your internal sd
I'll test it later this evening
[EDIT]
Nah wasn't that, it was a mistake by me. Two actually.
Testing a quick fix now. And I'll upload a full fixed Rom while I sleep
[/EDIT]
DamienMc said:
@RaghebAlama
Sorry I am having problems uploading more screenshots (used all my data this month)
I'll be sure to do it this evening when I'm on wifi.
try to explain in detail the installation process since 7.1.1 the eng_root does not detect it ODIN if it is not in .tar format, after installing the Eng_root, you have to start the normal cell phone and then the second.pass with the Install.bat ?
Click to expand...
Click to collapse
I fixed the systemui error and another popped up, sigh... ill let you know when it's fixed.
The only way to install this currently is from 7.1.1
@RaghebAlama
Eng_root is a tar. Flash it with Odin.
Your phone will stay on the logo the entire time.
Then just run the bat...The script waits for your phone, copies the required files, then it flashes the original kernel back and reboots.
easy peasy
... and it really does work installing this way
Sorry for the delay. Uploaded fixed version, OP updated
Alright, this looks AWESOME. Will try it when I get time. But about the root problem: I don't know if nobody's thought of this, or if I don't know something you do, but to get root for this, couldn't you add Magisk-14.zip (or another root method) to the queue in Flashfire, or include it in the install.bat? Flash the ROM then root, then reboot to system? I've tried to install Magisk before on stock Nougat with its new way of installing, which is flashing a boot.img that Magisk Manager patched, but Odin always failed on Operation: Write. I was going to go back to Marshmallow to try flashing a ROM and Magisk with Flashfire.
Hello. Can I get permission to make a version for j320fn/f/g
DJJosephJumper said:
Alright, this looks AWESOME. Will try it when I get time. But about the root problem: I don't know if nobody's thought of this, or if I don't know something you do, but to get root for this, couldn't you add Magisk-14.zip (or another root method) to the queue in Flashfire, or include it in the install.bat? Flash the ROM then root, then reboot to system? I've tried to install Magisk before on stock Nougat with its new way of installing, which is flashing a boot.img that Magisk Manager patched, but Odin always failed on Operation: Write. I was going to go back to Marshmallow to try flashing a ROM and Magisk with Flashfire.
Click to expand...
Click to collapse
Odin will not install a custom boot image on our device.
There are other ways to install the custom kernel, but our bootloader will not allow it to boot.
I can install SuperSU, but our selinux policy will not let the system load. The way I know it's rooted tho is that I can get a root shell thru adb, but that's useless since the system will not fully load... We need a new permissive boot image (engboot)
borksek said:
Hello. Can I get permission to make a version for j320fn/f/g
Click to expand...
Click to collapse
All yours bud
DamienMc said:
Odin will not install a custom boot image on our device.
There are other ways to install the custom kernel, but our bootloader will not allow it to boot.
I can install SuperSU, but our selinux policy will not let the system load. The way I know it's rooted tho is that I can get a root shell thru adb, but that's useless since the system will not fully load... We need a new permissive boot image (engboot)
Click to expand...
Click to collapse
Got it. Again, I was without the experience. Thanks for clearing it up.
Can i use this rom on my j320f
Does it work on the SM-J320m?
@aR_aNiK & @lithoy
Sorry guys, no.