[Rom] [AT&T] 139.12.54.ghost_att.ATT.en.US Flashable Zip - Moto X Android Development

Moto X Flashable zip of AT&T 139.12.54.ghost_att.ATT.en.US build​
Code:
#include <std_disclaimer.h>
/*
* I am 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 me for messing up your device, I will laugh at you.
*/
It is the same build as after installing recent OTA update for AT&T with improved camera.
This is a flashable zip of the system and boot.img. All other partitions (bootloader, modem, logo etc.) will NOT be modified.
It have to be installed (flashed) in CWM or TRWP - this mean that unlocked bootloader is required.
How to install:
1. Make full backup in CWM or TRWP of your current ROM
2. Wipe dalvik cache and cache in recovery
3. Flash in CWM or TRWP
4. Reboot
What is doing during installations:
1. Format system partition
2. Copy system files to system partition
3. Flash boot.img
This means that your data, bootloader, modem, logo etc. remain not modified
Download: 139.12.54.ghost_att.ATT.en.US.zip (427.3 MB)
Deodexed ROM (thanks to skiwong20): https://docs.google.com/file/d/0B9qC3vvamytkbjB4N0hDTTlBQXM/edit?usp=sharing
md5: 5d614b8fd02fcd6862ca24fcfde14e59

Al936 said:
Moto X Flashable zip of AT&T 139.12.54.ghost_att.ATT.en.US build​
Code:
#include <std_disclaimer.h>
/*
* I am 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 me for messing up your device, I will laugh at you.
*/
It is the same build as after installing recent OTA update for AT&T with improved camera.
This is a flashable zip of the system and boot.img. All other partitions (bootloader, modem, logo etc.) will NOT be modified.
It have to be installed (flashed) in CWM or TRWP - this mean that unlocked bootloader is required.
How to install:
1. Make full backup in CWM or TRWP of your current ROM
2. Wipe dalvik cache and cache in recovery
3. Flash in CWM or TRWP
4. Reboot
What is doing during installations:
1. Format system partition
2. Copy system files to system partition
3. Flash boot.img
This means that your data, bootloader, modem, logo etc. remain not modified
Download: 139.12.54.ghost_att.ATT.en.US.zip (427.3 MB)
Click to expand...
Click to collapse
Thanks! So we can flash this on top of our existing rooted AT&T phone using Safe Strap after clearing cache and dalvik cache?

just created a slot and installed. I assume this will not be rooted and can't be since the patch was applied to block pwnmymoto.
I can't get wifi to work though. going to disable wifi on stock slot to see if that works the next time.
so the second flash on rom slot 1 with wifi disabled on stock before flashing didn't change the outcome. Looks like it would work great if wifi would work but the rooting thing i'm concerned about. What would be the outcome to install this over the stock rom?

mj0528 said:
just created a slot and installed. I assume this will not be rooted and can't be since the patch was applied to block pwnmymoto.
I can't get wifi to work though. going to disable wifi on stock slot to see if that works the next time.
so the second flash on rom slot 1 with wifi disabled on stock before flashing didn't change the outcome. Looks like it would work great if wifi would work but the rooting thing i'm concerned about. What would be the outcome to install this over the stock rom?
Click to expand...
Click to collapse
all u need to do is flash a SuperSu zip..i would google for one. i am sorry i got no link for u
---------- Post added at 07:34 PM ---------- Previous post was at 06:35 PM ----------
Alright i have deodexed this ATT stock rom as promised. please op can you add to your post..thanks.
rom: https://docs.google.com/file/d/0B9qC3vvamytkbjB4N0hDTTlBQXM/edit?usp=sharing
md5: 5d614b8fd02fcd6862ca24fcfde14e59
here is SupserSu zip thanks to Chainfire
http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip?retrieve_file=1

Still no wifi
Sent from my XT1058 using XDA Premium 4 mobile app

Finally got it with the steps from the T-Mobile ROM but it runs a little on the laggy side
Sent from my XT1058 using XDA Premium 4 mobile app
---------- Post added at 03:52 AM ---------- Previous post was at 03:15 AM ----------
I guess being the test subject doesn't pay off. What a mess I keep having! After several reboots on customizing, I got the normal boot loops. 30 min later after erasing user data and restoring from a twrp backup and it failing. It surprisingly booted. Safe strap is beta for a reason I suppose. I'm staying away for now!
Sent from my XT1058 using XDA Premium 4 mobile app
---------- Post added at 04:26 AM ---------- Previous post was at 03:52 AM ----------
Just read that unlocked bootloader is required. Poop! Can we get one cooked for safestrap?
Sent from my XT1058 using XDA Premium 4 mobile app
---------- Post added at 04:35 AM ---------- Previous post was at 04:26 AM ----------
Can I get a hookup of a AT&T safestrap rom?
Sent from my XT1058 using XDA Premium 4 mobile app

WiFi still doesn't work, so I guess it is a problem with the ROM and not SS. SS has been updated to fix WiFi, and I tested it to be sure WiFi worked.
On the bright side, flashing the SuperUser zip does give you root, so once WiFi is fixed, this will be an easy way to get the upgrade and still have root. Messing with OTA RootKeeper is too iffy, IMO.

Related

[ROM][PORT][Player4] AOKP milestone 6

Your warranty is now void.
I am 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 me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
AOKP ported from Galaxy Player 5.0 using Hanthesolo's linaro rom as a base
Download Links
Rom
Screenshots
(Coming soon)
Credits
Android Open Kang Project
Cyanogenmod
Hanthesolo + Team Supernova
Gmillz
Bugs
can't remove nav-bar
can't mount usb storage - i think it's a build.prop error
superuser goes crazy at times - will replace with supersu
usual teamsupernova bugs
Installation instructions - same as LINics
Unzip rom and have the boot.img handy
Put the rom zip into the root of the sdcard.
Flash the rom using CWM. If you don't have it, please flash a custom kernel. (I recommend terrasilent)
When you're in CWM6, reflash the rom again.
After the second flash, flash the gapps zip.
Wipe your data.
Reboot into download mode and flash a GB kernel. (preferably the one you had before)
Reboot again into download mode after getting into CWM5.
Flash the boot.img with heimdall at the KERNEL partition
Note: If you're switching between versions or builds, there are simpler installation instructions:
flash this kernel with heimdall
boot into recovery
wipe cache + dalvik
install rom and gapps
Enjoy!
Release history
Release 1
initial release
Coming soon
supersu
ota app
you tell me
Thank you for posting this. This frees me up to work on other projects faster, and I now don't have to resolve my syncing issues .
hanthesolo said:
Thank you for posting this. This frees me up to work on other projects faster, and I now don't have to resolve my syncing issues .
Click to expand...
Click to collapse
no problem hopefully you'll be able to help me maintain my two ports
i was thinking of rebasing the rom using aokp from the samsung captivate - any objections/opinions?
theraf said:
Bugs
can't remove nav-bar
can't mount usb storage - i think it's a build.prop error
superuser goes crazy at times - will replace with supersu
usual teamsupernova bugs
Installation instructions - same as LINics
Unzip rom and have the boot.img handy
Put the rom zip into the root of the sdcard.
Flash the rom using CWM. If you don't have it, please flash a custom kernel. (I recommend terrasilent)
When you're in CWM6, reflash the rom again.
After the second flash, flash the gapps zip.
Wipe your data.
Reboot into download mode and flash a GB kernel. (preferably the one you had before)
Reboot again into download mode after getting into CWM5.
Flash the boot.img with heimdall at the KERNEL partition
Note: If you're switching between versions or builds, there are simpler installation instructions:
flash this kernel with heimdall
boot into recovery
wipe cache + dalvik
install rom and gapps
Enjoy!
Click to expand...
Click to collapse
For the Navy bar you can download an app called virtual navigation bar (trial or paid)
soultaker123 said:
For the Navy bar you can download an app called virtual navigation bar (trial or paid)
Click to expand...
Click to collapse
i need to remove the nav bar, not add it
in future releases can you try to make it only CWM flashable?
the playa! said:
in future releases can you try to make it only CWM flashable?
Click to expand...
Click to collapse
Once team supernova figures out how to deal with the recovery. If it were so easy, than wouldn't you think we'd already have cwm flashable packages?
Sent from my SPH-D710
theraf said:
Bugs
can't remove nav-bar
can't mount usb storage - i think it's a build.prop error
superuser goes crazy at times - will replace with supersu
usual teamsupernova bugs
Installation instructions - same as LINics
Unzip rom and have the boot.img handy
Put the rom zip into the root of the sdcard.
Flash the rom using CWM. If you don't have it, please flash a custom kernel. (I recommend terrasilent)
When you're in CWM6, reflash the rom again.
After the second flash, flash the gapps zip.
Wipe your data.
Reboot into download mode and flash a GB kernel. (preferably the one you had before)
Reboot again into download mode after getting into CWM5.
Flash the boot.img with heimdall at the KERNEL partition
Note: If you're switching between versions or builds, there are simpler installation instructions:
flash this kernel with heimdall
boot into recovery
wipe cache + dalvik
install rom and gapps
Enjoy!
Click to expand...
Click to collapse
FYI, Theraf you may have figured this out already but just incase and so everyone else knows if you flash the CM9 or LinICS and set the setting for USB storage then flash the way you described in the quoted post (NOT doing a wipe data/factory reset) you retain the use of the USB storage.
So here are the fixes for the nav bar and usb storage, just copy and paste into the build.prop
# Softkeys
qemu.hw.mainkeys=1
# Mass Storage. You can change to mtp
persist.sys.usb.config=mass_storage

[Rom] [Rogers] 139.12.36.ghost_row.RCI.en.CA Flashable Zip

Moto X Flashable zip of Rogers (Canada) 139.12.36.ghost_row.RCI.en.CA build​
Code:
#include <std_disclaimer.h>
/*
* I am 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 me for messing up your device, I will laugh at you.
*/
It is the same build as after installing OTA update for Rogers (Canada) with improved camera.
This is a flashable zip of the system and boot.img. All other partitions (bootloader, modem, logo etc.) will NOT be modified.
It have to be installed (flashed) in CWM or TRWP - this mean that unlocked bootloader is required.
How to install:
1. Make full backup in CWM or TRWP of your current ROM
2. Wipe dalvik cache and cache in recovery
3. Flash 139.12.36.ghost_row.RCI.en.CA.zip in CWM or TRWP
4. Flash Patch-139.12.36.ghost_row.RCI.en.CA.zip in CWM or TRWP
5. Reboot
What is doing during installations:
1. Format system partition
2. Copy system files to system partition
3. Flash boot.img
This means that your data, bootloader, modem, logo etc. remain not modified
Download:
139.12.36.ghost_row.RCI.en.CA.zip (432.1 MB)
Patch-139.12.36.ghost_row.RCI.en.CA.zip (6.8 MB)
Deodexed ROM (thanks to skiwong20): https://docs.google.com/file/d/0B9qC3vvamytkd3ZoZUs1RlRTUkU/edit?usp=sharing
md5: ec2a0c6229a5ed7270d5df36acc2881c
Al936 said:
Moto X Flashable zip of Rogers (Canada) 139.12.36.ghost_row.RCI.en.CA build​
Code:
#include <std_disclaimer.h>
/*
* I am 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 me for messing up your device, I will laugh at you.
*/
It is the same build as after installing OTA update for Rogers (Canada) with improved camera.
This is a flashable zip of the system and boot.img. All other partitions (bootloader, modem, logo etc.) will NOT be modified.
It have to be installed (flashed) in CWM or TRWP - this mean that unlocked bootloader is required.
How to install:
1. Make full backup in CWM or TRWP of your current ROM
2. Wipe dalvik cache and cache in recovery
3. Flash in CWM or TRWP
4. Reboot
What is doing during installations:
1. Format system partition
2. Copy system files to system partition
3. Flash boot.img
This means that your data, bootloader, modem, logo etc. remain not modified
Download: 139.12.36.ghost_row.RCI.en.CA.zip (432.1 MB)
Click to expand...
Click to collapse
Thumb up!
I have rooted and do I need to do the unroot before flashing it? Is it any way to keep root after flashing?
chrisjenho said:
I have rooted and do I need to do the unroot before flashing it? Is it any way to keep root after flashing?
Click to expand...
Click to collapse
You do not need to unroot before flashing. If you have CWM or TRWP it is easy to root after flashing.
chrisjenho said:
Thumb up!
I have rooted and do I need to do the unroot before flashing it? Is it any way to keep root after flashing?
Click to expand...
Click to collapse
If you have twrp, it asks after flashing if you want to root and install su
Al936 said:
You do not need to unroot before flashing. If you have CWM or TRWP it is easy to root after flashing.
Click to expand...
Click to collapse
I try this but wifi doesn't work, home key doesn't work. Do I wipe all helps? Or you can make a rom has full wipe Script?
Send from my Moto X
chrisjenho said:
I try this but wifi doesn't work, home key doesn't work.
Click to expand...
Click to collapse
Sorry, looks like there is mistake in the rom - I will post update soon.
Al936 said:
Sorry, looks like there is mistake in the rom - I will post update soon.
Click to expand...
Click to collapse
I have a working home key, but WIFI fails to start as well.
A quick logcat view:
Wifistatemachine: Failed to load driver!
Wifistatemachine: DriverFailedState
Al936 said:
Sorry, looks like there is mistake in the rom - I will post update soon.
Click to expand...
Click to collapse
Please try to flash this patch (just after rom flashing): Patch-139.12.36.ghost_row.RCI.en.CA.zip (6.8 MB). And report here
I flashed this rom and then the patch, and everything works great.
FligMupple said:
I flashed this rom and then the patch, and everything works great.
Click to expand...
Click to collapse
Thanks! OP updated.
Sorry guys, i know that this isnt the place, but can anyone help how to update mine using this update: fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz and files as attached? Dunno more where to look or who to asks!Thanks!
Nice job , flashed it and it works perfect , wifi work , camera quality IS better ...but the auto focus take longer to adjust now
The voice call is so much better
Sa sens le Rooting icite !!
Al936 said:
Sorry, looks like there is mistake in the rom - I will post update soon.
Click to expand...
Click to collapse
Hey buddy, any ideas to remove the carrier's name on left top?
here is a deodex version of this for you guys
rom: https://docs.google.com/file/d/0B9qC3vvamytkd3ZoZUs1RlRTUkU/edit?usp=sharing
md5: ec2a0c6229a5ed7270d5df36acc2881c
Al936 said:
Sorry, looks like there is mistake in the rom - I will post update soon.
Click to expand...
Click to collapse
Do you update the original rom or just update the patch?
I download the patch and it doesn't solve the problem.
Home key/control panel are not working.
---------- Post added at 02:04 AM ---------- Previous post was at 01:43 AM ----------
chrisjenho said:
Do you update the original rom or just update the patch?
I download the patch and it doesn't solve the problem.
Home key/control panel are not working.
Click to expand...
Click to collapse
Active display/Twist camera are not working.
chrisjenho said:
Do you update the original rom or just update the patch?
I download the patch and it doesn't solve the problem.
Home key/control panel are not working.
---------- Post added at 02:04 AM ---------- Previous post was at 01:43 AM ----------
Active display/Twist camera are not working.
Click to expand...
Click to collapse
Yes it was fixed but are you restoring your data after you flash the ROM? Had the same issue when I flashes the T-Mobile ROM and restored my data through recovery. If so, do a clean install
Sent on my Moto X
flashallthetime said:
Yes it was fixed but are you restoring your data after you flash the ROM? Had the same issue when I flashes the T-Mobile ROM and restored my data through recovery. If so, do a clean install
Sent on my Moto X
Click to expand...
Click to collapse
the flashable rom is out and I downloaded once and wifi/control panel/etc. do not work.
I just follow the instruction to do this and have't restored my data. Even I flashed the patch.
So I wonder if the flashable zip is modified because I am using the original one from this post.
Maybe I need a zip same as the XML.kind but it can be flashable. All I need to do is full wipe and flash the zip.
Don't know why my computer can't use rsd to do this with "1/16 usb error while reading/writing".
Camera update seems great and stability is all I need.
chrisjenho said:
the flashable rom is out and I downloaded once and wifi/control panel/etc. do not work.
I just follow the instruction to do this and have't restored my data. Even I flashed the patch.
So I wonder if the flashable zip is modified because I am using the original one from this post.
Maybe I need a zip same as the XML.kind but it can be flashable. All I need to do is full wipe and flash the zip.
Don't know why my computer can't use rsd to do this with "1/16 usb error while reading/writing".
Camera update seems great and stability is all I need.
Click to expand...
Click to collapse
I assume your boot loader is unlocked and you're not using pwnmymoto? Factory reset, wipe dalvik and cache and flash again, problem could be is there's minor differences between each carriers ROM which causes frozen and non working apps and settings. To restore your data just use either titanium or ROM toolbox
Sent on my Moto X
Deleted
skiwong20 said:
he has a locked bootloader.
Click to expand...
Click to collapse
Well that explains everything
Sent on my Moto X

***How To ROOT 4.3 & NC4 OTA, Install Recovery & Roms - Verizon RETAIL Note 3***

***How To ROOT 4.3 & NC4 OTA, Install Recovery & Roms - Verizon RETAIL Note 3***
* * * What you do with your device is completely your choice and solely your responsibility! - If You READ These Instructions FIRST, THEN Follow Them, You Will Be Up And Running In No Time * * *
EVERYTHING You Need To Root, Install SafeStrap, Update SuperSU, Flash Custom 4.3 Roms, Flash In ODIN On 4.3 Jelly Bean RETAIL NOTE 3 ! ! !
To UPDATE from Custom 4.3 JB to 4.4.2 KK (NC2 Leak) go to
How To Update From JB 4.3 To KK 4.4.2 On Verizon RETAIL NOTE ​
To Root, Install Safestrap, Flash Cust Rom AFTER taking Official NC4 OTA:
Go To Bottom Of OP​
This is a compilation of instructions that I used on my SM-N900V Verizon Note 3... This process was BY FAR the EASIEST I've ever used!
* * *Verified Knox 0x0* * * developer option (click 'BASE Version' in 'About Phone' 7 times to UNHIDE Developer Option) also verify UNKNOWN SOURCES is CHECKED & Verify Apps is Unchecked in system settings>security[/B][/COLOR][/I].
On PC, go to CONTROL PANEL > Install/Uninstall Programs > uninstall ALL Samsung drivers
Download & Install Samsung Drivers To Your PC
Samsung USB drivers (click “see all downloads”)
* * * ATTN: PRIOR to flashing a Rom built on MJE update, you should be running MJE (take OTA update or install MJE tar via Odin) then reroot via Kingo/Vroot, install Safestrap * * *
EASY Steps To Update To MJE: (Factory Stock)
- Download MJE tar file from Beanstown106's Firmware Collection Thread
- Flash MJE tar in Odin (for added safety, REMOVE sdcard) For DETAILED Odin instructions click HERE
- Reboot
- Go To Install Kingo (Google Kingo root 1.1.5 or 1.1.6 download) or Vroot (Google Vroot)
FOR ROOT PRIVILEGES- Install KINGO/Vroot
***Kingo 1.2 is having issues Rooting MJE Firmware, Google Kingo 1.1.5 or .6 OR see HERE, OR use Vroot***
I used the Kingo root app - links to Kingo are not currently allowed on XDA but it's very easy to search and find. It's just like a "one click" toolkit - meaning it's a no-brain operation. Download the app and follow the instructions. Currently Kingo & Vroot are the only known methods to root the MJ7/MJE builds for the Verizon Note 3 so it's one of these or no root for you. IF ROOT FAILS, KEEP TRYING (it took me 3 attempts)
TIP- make sure display timeout is set for 10 minutes & temporarily disable PC anti-virus (thanks RypeDub for the catch)
***If Kingo fails to root your device after several attempts: Try Vroot (some users reported success with Vroot after Kingo failed ROOT)
INSTALL SAFESTRAP RECOVERY (NO LONGER SUPPORTED BY HASHCODE)
Once you're ROOTED head over here: [RECOVERY LOCKED] Safestrap Recovery & download the latest APK see BELOW for which version. Open the Safestrap app in your app drawer and install the app, then open Safestrap and click "install recovery" in the app (The following directions are from Safestrap OP).
Safestrap 3.65 is last STABLE 4.3 JB version, 3.72 is for KK w/o rom slot support, 3.75 is Beta and is for KK w/ rom slot support
HOW TO UPGRADE SAFESTRAP
*To REVERT from newer version to older version, follow same steps swapping old file for new file*
-Push the APK to your sdcard (get latest SS.apk HERE)-THX Hashcode!
-Boot back into the "stock" rom-slot.
-OPEN your old Safestrap app and hit the "Uninstall Recovery" button
-THEN, open a "file explorer" (even TW "My Files" will work)
-Browse to where you pushed the New / old APK
-Click on it and install like a normal app (if install not successful, UNINSTALL old Safestrap app like any other app, THEN install new SS.apk)
-Once installed, open the SS APK
-Grant SU access
-THEN hit "Install Recovery" button
All set, now you can reboot and re-activate whatever rom-slot you were using
INSTALLING CHAINFIRE'S SUPERSU OVER KINGO SUPERSU
Next install a trusted, open source SuperSU app on your device since the Kingo root method is closed source (optional, but highly recommended). Download the latest SuperSU zip - instructions in Chainfire's XDA Thread (download to sd card or from PLAY).
Reboot your device (DO NOT REBOOT INTO RECOVERY), at the Safestrap splash screen - choose "Recovery"... Once in Safestrap, go to your stock rom slot by clicking "Boot Options" and ensuring it says "stock slot" in RED at the top of the screen. If it says anything other than stock, tap the stock slot button and click "activate" on the following page. Hit back to return to the Recovery main menu. Once confirmed you're on your stock slot, tap install and flash the new SuperSU zip (no wipes necessary). Once that's done, tap reboot system.
ROOT Privileges ONLY
If you ONLY want root privileges and NOT the recovery or the ability to flash ROMS, you can UNINSTALL Safestrap after flashing SuperSU, you will ONLY have root privileges: ***NO recovery and NO ability to flash ROMS*** After flashing SuperSU, reboot, choose "Continue" at splash screen, find Safestrap app in App Drawer and uninstall like any other app.
You're now completely done updating to MJE, Rooting your device, adding a stable Recovery & installing a trusted SuperSU application. Now, enjoy installing ROMs using Safestrap [SS]
***NOTE: When rebooting your device, you have to option to CONTINUE to your current ROM, or enter RECOVERY (Safestrap) after several seconds CONTINUE is the default action. If you are booting to your STOCK Slot you will see SAFESTRAP DISABLED this is NORMAL. When booting to slots 1-4 you will see SAFESTRAP ENABLED this is also NORMAL***
CREATING VIRTUAL ROMS SLOTS *NOT SUPPORTED IN SS 3.72 YET*
1. Reboot Device
2. Select Recovery at SS splash screen
3. Select Boot Options
4. Select one of the rom slots [1-4]
5. Adjust partition sizes if necessary [The average user can leave the partitions as is, if you are an app intensive user, increase DATA partition up to 4 gb MAX]
*NOTE: the larger you make the partitions of a Rom Slot, the less room you will have for remaining slots)
6. Select the Create ROM button (takes a minute)
7. Once the ROM slot has been created, browse back to BOOT OPTIONS.
8. Ensure the Rom Slot you want to flash is highlighted in GREEN at top of screen
9. Select Install
10. Browse to the ROM .zip you downloaded
11. Reboot
SWITCHING BETWEEN ROM SLOTS
1. Reboot Device
2. Select Recovery at SS splash screen
3. Select Boot Options
4. Select the Rom Slot you want to activate
5. Select Activate
6. Confirm the Rom Slot you just Activated shows at top of screen (GREEN for slots 1-4, RED for Stock Slot)
7. Browse back to Menu
8. Select Reboot
How To Flash Daily Driver Into Stock Rom Slot
1. Back up Stock Rom in Stock Slot to sdcard (optional)
2. Restore back up Stock Rom to open ROM slot 1-4 (optional)
3. Boot from restored slot to ensure functionality (optional)
4. Factory Reset for a clean install OR if upgrading same Rom you can DIRTY FLASH by clicking ADVANCED WIPE: check dalvik, cache, system (remember no dev support for "dirty flash")
5. Flash/Restore Daily Driver Rom to Stock Slot (Read the warning about flashing onto Stock Rom Slot, then forget about it
To Have Access To ALL Your Device Storage (FREE UP STORAGE) Go To Step 6
6. Delete un-used ROM slots 1-4 (you can only delete a ROM from the activated slot, the empty, unactivated slot remains)
7. Boot into Rom on Stock slot
8. Enjoy.This will give you access to ALL of your device's storage capacity (remember when booting into stock slot, Safestrap will say DISABLED, this is normal)
A Few Things To Consider When Using Multiple Rom Slots:
You can flash roms in slots 1-4 and stock slot. Activate whichever slot you'd like to boot to the next time, and your specific rom to upgrade, test, whatever comes up at boot. Ready to switch back to another rom, activate THAT rom slot, reboot to your next rom...This is the TRUE MAGIC of Safestrap; Daily driver in stock slot, test Rom in slot 1, Stock Rom in slot 2, boot into ANY rom simply by activating THAT rom slot!
Realize each rom slot has a max limit for data partition and system partition. If you are an app intensive user or like seeing an accurate reading of your internal and ext storage, I'd reco putting your daily driver on the stock slot (backup stock rom, keep on sdcard, flash daily driver in stock slot)...
If you like running multiple roms (skip step 5 above), when you activate a rom on slots 1-4, your int and ext memory will NOT read accurately, and you will be limited on how much storage you have on each slot. Use File Manager (ES File Explorer) if you want/need an accurate reading of remaining storage
Flashing your DD on the stock slot gives you access to ALL the int and ext memory, and ALL memory is properly reported.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ​
IF YOU ARE ON NC4 (Official VZW OTA) Follow The Below Instructions​(courtesy of barrackobama)
WHAT YOU DO WITH YOUR DEVICE IS COMPLETELY YOUR OWN RESPONSIBILITY
Step- 1 - Root Device with TowelRoot courtesy of geohot
Step- 2 - Install Busybox from play store and install busybox itself
Step- 3 - Install Safestrap 3.75 courtesy of Hashcode (NO LONGER SUPPORTED BY HASHCODE)
Step- 4 - Boot into Safestrap, Select Stock Slot
Step- 5 - Wipe Data, Use Factory Reset Slider
Step- 6 - Install the latest Alliance ROM courtesy of the Alliance Crew
Step- 7 - Reboot into Download mode From Safestrap (DON'T hit reboot, hit back arrow twice, hit REBOOT, choose DOWNLOAD)
Step- 8 - Unzip & Install In ODIN This NC2 Kernel .tar courtesy of Beanstown106
XDA user barrackOBAMA confirmed these instructions work!
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ​
The Brilliant Magic That Allows Fast, Easy Access To Multiple Roms With A Simple Reboot
Hashcode's [RECOVERY LOCKED] SafeStrap:
Roms I've Had Great Experiences With
Beantown106's [ROM][4.3][MJE]Jelly 'Beans' AOSP/KitKat
Alliance Crew's [ROM] AllianceROM
nitroglycerine33's [ROM] Eclipse AOSP
sbreen94's [ROM][4.3] Hyperdrive
Brandonrz's [ROM]-N.E.O.N. R.O.M
Helps & Guides
DutchDogg54's Firmware / Guide
Beanstown106's [Firmware][Collection] Modems, kernels, Stock Tars​
Remember to SUPPORT THE DEVS who allow you to enjoy your ROOTED, Custom N3!
Please click THANKS and RATE this thread if it was helpful! Thanks!
az_biker said:
I couldn't find any links or threads with ALL the instructions in one place (ROOT, Safe Strap, Rom), so I compiled a list of instructions that I used on my SM-N900V Verizon MJ7 Note 3... This process was BY FAR the EASIEST I've ever used! * * *Verified Knox 0x0* * *
*** this is NOT my original work...(credit to DutchDogg54 and others)... IF any of this is YOUR work please let me know so I can give credit where it is due. Again, this is NOT my original work***
I used the Kingo root app - links to Kingo are not currently allowed on XDA but it's very easy to search and find. It's just like a "one click" toolkit - meaning it's a no-brain operation. Download the app and follow the instructions. Currently Kingo & vroot are the only known methods to root the MJ7 build for the Verizon Note 3 so it's one of these or no root for you. IF ROOT FAILS, KEEP TRYING (it took me 3 attempts)
Once that's done head over here: [RECOVERY LOCKED/MI9,MJ7] Safestrap Recovery v3.65 [2013-11-13 STABLE] & download the latest version of the APK then install it. Open the Safestrap app in your app drawer and install the recovery by clicking "install" within the app.
Next it's advisable to get a trusted & open source Super User app on your device after using the closed source Kingo root method (optional, but highly recommended). Download the latest SuperSU zip - Google search latest version. .
Reboot the phone and you'll come to the SafeStrap splash screen - choose "recovery." Once here, go to your stock rom slot by clicking "Boot Options" and ensuring it says "stock slot" in red at the top of the screen. If it says anything other than stock, tap the stock slot button and click "activate" on the following page. Hit back to return to the recoveries main menu. Once confirmed you're on your stock slot, tap install and flash the SuperSU zip (no wipes necessary). Once that's done, tap reboot system.
You're now completely done updating to MJ7, Rooting your device, adding a stable Recovery & installing a trusted Superuser application. Now, enjoy To install ROMs, you do that using SafeStrap [SS]
1. Reboot phone
2. Click Recovery Button when SS splash screen pops up
3. Click one of the rom slots [1-4] then click the Create ROM button [I left default values to test out the ROM. People say that its fine for most, but adjust date portion of partition if you use lots of apps]
4. Once the ROM slot has been created, browse back into the previously created slot.
5. Click Activate
6. Then click Install
7. Browse to whatever ROM .zip you download
8. Done
How to change your primary Stock ROM:
I made Beans my primary ROM.
1. Backed up Stock Slot
2. Restored back up to open ROM slot
3. Booted from restored slot to ensure functionality
4. Backed up Beans ROM
5. Restored Beans backup to Stock slot
6. Deleted un-used ROM slots [Stock and Beans in ROM slot 1-4] You can only delete a ROM from the slot, the empty slot remains
7. Booted into Beans on Stock slot
8. Re-installed SS
9. Enjoy.
Here Bean's Rom:
http://forum.xda-developers.com/show....php?t=2523159
Here's SafeStrap:
http://forum.xda-developers.com/show....php?t=2517610
Quick Google search will get you Kingo's app and the latest SuperSU...
SUPPORT THE DEVS! BEANSTOWN106 for ROM, and HASHCODE for Safe Strap. Also THANK DutchDogg54 for these instructions!
Click to expand...
Click to collapse
Why didn't you include hyperdrive? And the other 2 roms? And nice thread.
Sent from my SM-N900V using Tapatalk
Brandonrz said:
Why didn't you include hyperdrive? And the other 2 roms? And nice thread.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I only included what I personally tried so I could say I KNOW IT WORKS. But you are right, I should add the other threads to the ROMs for others to try. Thanks for the correction!
az_biker said:
I only included what I personally tried so I could say I KNOW IT WORKS. But you are right, I should add the other threads to the ROMs for others to try. Thanks for the correction!
Click to expand...
Click to collapse
Lol, np. I'm pretty sure you would know if any of those roms don't work. The genral section, yes I ment general, would be blown up with nubs saying. "Halp plz, phone no turn on." Haha
Sent from my SM-N900V using Tapatalk
ive been trying to root with kingo for about 3 days and still no root help me please!!
if the SS have password before launch would be better~~
eastside770 said:
ive been trying to root with kingo for about 3 days and still no root help me please!!
Click to expand...
Click to collapse
-I went to kingo site (Google it, no kingo links allowed on XDA) and downloaded their program (to put on your desktop)
- install kingo to your pc
-follow instructions in kingo app
-make sure you have (unknown sources) checked in SECURITY
-make sure you have (usb debugging) checked in DEVELOPER OPTIONS
-I set my display to not time out for 10 minutes after I failed to root the first three times with kingo thinking maybe the screen timing out was causing an issue, the fourth time was flawless (not sure if the display timeout was it or not)..
try these steps, let me know how it works out!
I really think it's my PC. It won't install all of the drivers. I plug it up and kingo tries to connect does sometimes and sometimes it don't.
Sent from my Nexus 7 using xda app-developers app
eastside770 said:
I really think it's my PC. It won't install all of the drivers. I plug it up and kingo tries to connect does sometimes and sometimes it don't.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Try going to Control Panel > Pograms find all Samsumg drivers and uninstall them, and try Kingo again.
If that still doesn't work, read through THIS forum:
http://forum.xda-developers.com/showthread.php?t=2484231
Good luck!
i can never get samsung_android driver to install.. and i dunno why
eastside770 said:
i can never get samsung_android driver to install.. and i dunno why
Click to expand...
Click to collapse
Just guessing here: 32bit vs 64bit issue? Maybe corrupt Samsung driver? Sorry I'm not much help...
Sent via Notorius 3
Where do you find developer options on the vzw note 3?
Sent from my SM-N900V using XDA Premium 4 mobile app
Mark.Y said:
Where do you find developer options on the vzw note 3?
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Settings>about phone>click BUILD NUMBER 7-8 times, then back to settings
I don't know why but this doesn't seem EASY to me. I am so used to ADB and ODIN to root. The other methods seem easier to me because I download the files and run what I need (GS4, Note2, Nexus, and Nexus 7). Now files need to be Googled and downloaded separately.
I never have problems with driver I usually manually make my pc find and install them. I need to root so I can stop using my S4 and sell it.
Sent from my SM-N900V using Tapatalk
Xirix12 said:
I don't know why but this doesn't seem EASY to me. I am so used to ADB and ODIN to root. The other methods seem easier to me because I download the files and run what I need (GS4, Note2, Nexus, and Nexus 7). Now files need to be Googled and downloaded separately.
I never have problems with driver I usually manually make my pc find and install them. I need to root so I can stop using my S4 and sell it.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
You from Yuma? I'm in the Foothills! This was super easy for me... Hardest part was I had to run Kingo three times before my Note 3 would successfully ROOT. The whole kingo app was basically clicking OK over and over and over..
The step by step in the OP is exactly what I followed, and I didn't know ANYTHING about flashing a rom this way OR safe strap... I'm used to downloading the rom, kernel, and add-ons and flashing them in TWRP...no rom slots, no creating or activating roms. Even as clueless as I was, these step by steps walked me right through the entire process without a hitch (except the Kingo part)...
What part are you getting stuck on? The only file you NEED to Google is the Kingo app because XDA won't allow the link... compared to pushing via adb, line by line commands and the old school way, this is a breeze!
az_biker said:
You from Yuma? I'm in the Foothills! This was super easy for me... Hardest part was I had to run Kingo three times before my Note 3 would successfully ROOT. The whole kingo app was basically clicking OK over and over and over..
The step by step in the OP is exactly what I followed, and I didn't know ANYTHING about flashing a rom this way OR safe strap... I'm used to downloading the rom, kernel, and add-ons and flashing them in TWRP...no rom slots, no creating or activating roms. Even as clueless as I was, these step by steps walked me right through the entire process without a hitch (except the Kingo part)...
What part are you getting stuck on? The only file you NEED to Google is the Kingo app because XDA won't allow the link... compared to pushing via adb, line by line commands and the old school way, this is a breeze!
Click to expand...
Click to collapse
Yea, Pacific and 24th. I didn't even notice that just. I just got home from work and said "I need to get root tonight!". I am not really getting stuck since I haven't even started. I am going to try this tonight. Thanks for the help and support. Also, good to know you're just down the street.
Xirix12 said:
Yea, Pacific and 24th. I didn't even notice that just. I just got home from work and said "I need to get root tonight!". I am not really getting stuck since I haven't even started. I am going to try this tonight. Thanks for the help and support. Also, good to know you're just down the street.
Click to expand...
Click to collapse
Cool. Whole process took me less than 30 minutes.
Yea it was actually VERY easy. I was just not sure or couldn't believe how easy it was. I am rooted and safe strapped. First time using safe strap and it seems very safe. Thanks
Edit: forgot to mention that Kingo said rooting failed. So I tried to unroot and it didn't work. I unplugged installed root checker. I was asked to grant root access and root checker confirmed that I had root access. Worked on the very first try even though it told me it didn't.
Also it installs SuperSu for you now so no need to look for it to install it.
Xirix12 said:
Yea it was actually VERY easy. I was just not sure or couldn't believe how easy it was. I am rooted and safe strapped. First time using safe strap and it seems very safe. Thanks
Edit: forgot to mention that Kingo said rooting failed. So I tried to unroot and it didn't work. I unplugged installed root checker. I was asked to grant root access and root checker confirmed that I had root access. Worked on the very first try even though it told me it didn't.
Also it installs SuperSu for you now so no need to look for it to install it.
Click to expand...
Click to collapse
It has always installed SuperSU. The purpose of flashing Chainfire's zip file is to overwrite the one that Kingo installs. Just in case there was something nefarious (sp?) going on with the one it installed.
Sent from my SM-N900V using Tapatalk
Is it safe to assume this doesn't interfere with Knox? If this was my personal phone I wouldn't care but it's my work phone so I need to make sure warranty stays intact.
Sent from my SM-N900V using XDA Premium 4 mobile app

[PORT] [FULLY WORKING] MIUI6 5.3.13

Code:
#include
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.*/
MIUI6 for Nexus 5
Download 5.3.13
Download fixbrowservideo.zip
What is working:
- Most functions (WI-Fi, GPS, mobile data, signal strength etc.)
- Blur
- MIUI Camera
- Web browser
- Webview
Known issues:
- Crash when attempting to manually set ISO in Camera
- Crash when selecting Dirac-option in Settings
- Crash when attempting to watch videos in Browser and other webview apps (Flash attached zip fixbrowservideo.zip)
How to fix GPS:
Push framework-res with fixed AGPS to /system/framework using adb or similar.
Remove AMAP network location (i don't remember exact name, but starts with AMAP) apk.
Enable GPS in Location settings
Download GPS Status app and choose "Download AGPS data"
This ROM comes with multiple languages and is one of the first ever non-Xiaomi MIUI6 ports to be released.
It fully supports MIUI Camera and blur.
Install instructions:
- Wipe data and cache
- Install MIUI zip
- Install fixbrowservideo.zip (To fix video in browser)
- Reboot to system
Based on:
Xiaomi.eu Mi3/Mi4 (cancro) ROM
Custom, source-built Omni 4.4 Kitkat
ElementalX-N5-1.13
XDA:DevDB Information
MIUI6 Nexus 5 port, ROM for the Google Nexus 5
Contributors
datagutt, Xiaomi, BurgerZ, Xiaomi.eu, pijulius
Source Code: http://github.com/flar2/ElementalX-N5/tree/ElementalX-1.00
ROM OS Version: 4.4.x KitKat
Based On: MIUI and Omni
Version Information
Status: Testing
Current Beta Version: 5.3.13
Created 2014-09-16
Last Updated 2015-04-01
Reserved
You are the man! Thank you [emoji2]
Sweet thanks
Pizzarrone said:
You are the man! Thank you [emoji2]
Click to expand...
Click to collapse
I tried to use my port as a daily driver, but the webview bug is too big of an issue to me personally.
Over the years I've watched this ROM reach new levels of gorgeousness. Will definitely check it out.
After flashing the ROM zip and Gapps, when I press reboot it goes to fastboot screen, then when I press START it just stay on a black screen. Did I did something wrong?
guigadourado said:
After flashing the ROM zip and Gapps, when I press reboot it goes to fastboot screen, then when I press START it just stay on a black screen. Did I did something wrong?
Click to expand...
Click to collapse
Same prob. here
guigadourado said:
After flashing the ROM zip and Gapps, when I press reboot it goes to fastboot screen, then when I press START it just stay on a black screen. Did I did something wrong?
Click to expand...
Click to collapse
Same here
The same without gaaps
mvha said:
Same here
The same without gaaps
Click to expand...
Click to collapse
I recommend you do full data reset.
Whip system,data,cach,
Sent from my Nexus 5 using xda premium
guigadourado said:
After flashing the ROM zip and Gapps, when I press reboot it goes to fastboot screen, then when I press START it just stay on a black screen. Did I did something wrong?
Click to expand...
Click to collapse
baggord said:
Same prob. here
Click to expand...
Click to collapse
You can try to install the rom and reboot and see if it works, then go back into recovery and flash the gapps ... might work....or has deep problems.
I did a clean flash without the gapps and then did another with the gapps, same thing happened
guigadourado said:
I did a clean flash without the gapps and then did another with the gapps, same thing happened
Click to expand...
Click to collapse
Ok, then there are problems to be solved, too bad ..
Flashed in multirom no problems
Only google search had stoppen after reboot
But thanx 4 ya works
in downloadgapp banks minimal?
Nice bro !
Can you post some screens ?
Cheers !
i did just install it from multirom and can't boot it up !
not main
TheDarkLegend said:
i did just install it from multirom and can't boot it up !
Click to expand...
Click to collapse
it can not be your internal rom it has to be add as one of extra roms
my question is how can you add gapps????????????????????
i have multirom!flash rom,rebot!recovery flash gapp nano rebot!all ok:good:
Looking forward to trying this, haven't flashed a ROM in a awhile, need to get back into flashing ROMs often again
Sent from my Nexus 5 using XDA Free mobile app

[ROM][UNOFFICIAL][LINEAGEOS 15.1][ANDROID 8.1][SM-T350]

[PLEASE READ BELOW]
Code:
*** Disclamer * Your warranty is now void. * *
We are 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.
[Sorry if this DevDB thread is ugly, I will organize is later]
Hi, this is Jiiro.
I have finally finished compiling and testing out this LineageOS custom ROM for the SM-T350.
You may have seen @andr0idfr3ak's post on LineageOS for the SM-T350 (mine is updated).
I am now going to announce that I am going to be the maintainer for the SM-T350 development of LineageOS for now.
More custom ROMs are coming through!
Specs:
Samsung Galaxy Tab A SM-T350 8-Inch Tablet (16 GB, Titanium)
SM-T350 XAR GT58WIFIXX/GT58WIFI
Known bugs:
External Audio not working
Camera
Things that work:
Internal Audio does work (For example, using headphones)
Bluetooth Audio does work
Download Links:
Latest as of August 1, 2018
Latest Updato Firmware
Latest Unofficial LineageOS
Latest TWRP from Ashyx
Latest ODIN
*Note: I don't know if ********** is trusted, I downloaded it and ran it and had no problems whatsoever
Steps:
1) Get ODIN
2) Go to Download mode on your Samsung device
3) Flash TWRP
4) In TWRP go to Wipe > Advanced Wipe and click on
a) Dalvik / ART Cache
b) System
c) Data
d) Internal Storage
e) Cache
5) Go to Download mode after that
6) Go back on your ODIN and flash the firmware from Updato
7) After that happens, go back to Download mode and flash TWRP again
8) Do Step 4 and after that move onto Step 9
9) Have ADB on your machine, be in TWRP while this happens
10) Go to Advanced > ADB Sideload
11) On your computer type
Code:
adb sideload [Destination of your LineageOS .zip]
12) You're done! It will take about 5 minutes to boot.
Sorry if the guide is confusing, I will try to rephrase them again later.
XDA:DevDB Information
[ROM][UNOFFICIAL][LINEAGEOS 15.1][ANDROID 8.1][SM-T350], ROM for the Samsung Galaxy Tab A series
Contributors
Jiiro, deadman96385, ashyx
Source Code: https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: T350XXU1CQJ5 | T350XAR1CQJ5
Version Information
Status: Beta
Created 2018-08-08
Last Updated 2018-09-06
lets get this thread started I been on your Rom a day or 2 now and i like it. Its gives me a picture in picture , and it saves on storage big time from all the apps Samsung puts on these tablets. Thanks for the work.
Thanks for keeping the tab A 8" alive!!! And working on a speaker fix!!
Any luck with the audio?
Please fix this soon
RebuffedRacer13 said:
Any luck with the audio?
Click to expand...
Click to collapse
Please fix this soon
I dont know what I'm doing wrong, but i cant get this to install or boot. I've followed every single step and after it's done, i get a black screen... Please help
ELProfeMcK said:
I dont know what I'm doing wrong, but i cant get this to install or boot. I've followed every single step and after it's done, i get a black screen... Please help
Click to expand...
Click to collapse
Well let's see if we can help you out. What ROM were you on first and what firmware were you also on. I'm on nougat firmware but I usually run ghost ROM Android 6 with with permissive kernel. Also I used twrp 3.2.1 from Android freak on XDA somewhere.
Here's what I did
Flash twrp 3.2.1 in twrp from smt355 3.1 extracted image and flashed image to recovery partition in twrp not Odin.
I was on nougat firmware but running ghost project marshmallow .
I wiped data , cache, system not internal.
Flashed lineage zip with pico open gapps 8.1 arm.
Let it boot up for 5 to 10 minutes and worked.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Let me add if you guys use twrp 3.2.1 make sure to not wipe your efs or restore it just use system, data, boot backup and restore if you do mess up the efs I have the fix on XDA if you get invalid mount and it won't boot up .
Do you have to sideload lineage OS or can you install via Twrp?
Also, is there a problem with the default camera app? Can you install like,open camera or Google camera? Or does it just not work at all? And internal/external audio. Do you mean headphones will or won't work? And would installing different audio drivers like Viper or something fix it?
Sorry, just want to know before I install. ?
Techguy777 said:
Well let's see if we can help you out. What ROM were you on first and what firmware were you also on. I'm on nougat firmware but I usually run ghost ROM Android 6 with with permissive kernel. Also I used twrp 3.2.1 from Android freak on XDA somewhere.
Here's what I did
Flash twrp 3.2.1 in twrp from smt355 3.1 extracted image and flashed image to recovery partition in twrp not Odin.
I was on nougat firmware but running ghost project marshmallow .
I wiped data , cache, system not internal.
Flashed lineage zip with pico open gapps 8.1 arm.
Let it boot up for 5 to 10 minutes and worked.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Let me add if you guys use twrp 3.2.1 make sure to not wipe your efs or restore it just use system, data, boot backup and restore if you do mess up the efs I have the fix on XDA if you get invalid mount and it won't boot up .
Click to expand...
Click to collapse
I was doing everything using Twrp 3.1 sm-t355. Im on stock nougat 7.1.1 CQJ5 8/1/17 security patch, so basically the latest official from Samsung.
I will try using your method to see if it works. I'll update twrp to 3.2.1and not wipe internal storage.
I appreciate the reply and help. Thanks :good:
Techguy777 said:
Well let's see if we can help you out. What ROM were you on first and what firmware were you also on. I'm on nougat firmware but I usually run ghost ROM Android 6 with with permissive kernel. Also I used twrp 3.2.1 from Android freak on XDA somewhere.
Here's what I did
Flash twrp 3.2.1 in twrp from smt355 3.1 extracted image and flashed image to recovery partition in twrp not Odin.
I was on nougat firmware but running ghost project marshmallow .
I wiped data , cache, system not internal.
Flashed lineage zip with pico open gapps 8.1 arm.
Let it boot up for 5 to 10 minutes and worked.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Let me add if you guys use twrp 3.2.1 make sure to not wipe your efs or restore it just use system, data, boot backup and restore if you do mess up the efs I have the fix on XDA if you get invalid mount and it won't boot up .
Click to expand...
Click to collapse
I can't find 3.2.1
Can you post a link?
lividhen said:
I can't find 3.2.1
Found it! But it says it's for oreo... Is it safe to install?
I'm on a rooted stock 7.1.1.
Never mind! ? I didn't see it!
Click to expand...
Click to collapse
Were you able to install twrp 3.2.1 it should work fine with stock nougat. Did you try flashing lineage again? Its really stable and boots right.
I recommend trying pico gapps first
---------- Post added at 10:55 PM ---------- Previous post was at 10:18 PM ----------
lividhen said:
Do you have to sideload lineage OS or can you install via Twrp?
Also, is there a problem with the default camera app? Can you install like,open camera or Google camera? Or does it just not work at all? And internal/external audio. Do you mean headphones will or won't work? And would installing different audio drivers like Viper or something fix it?
Sorry, just want to know before I install. ?
Click to expand...
Click to collapse
Bluetooth and headphones work no external speaker. I tried different audio mods viper and it works with Bluetooth or headphones wired but no external speaker. Camera I can't remember I don't ever use it.
---------- Post added at 11:31 PM ---------- Previous post was at 10:55 PM ----------
lividhen said:
I can't find 3.2.1
Can you post a link?
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=962339331458992706
ELProfeMcK said:
I was doing everything using Twrp 3.1 sm-t355. Im on stock nougat 7.1.1 CQJ5 8/1/17 security patch, so basically the latest official from Samsung.
I will try using your method to see if it works. I'll update twrp to 3.2.1and not wipe internal storage.
I appreciate the reply and help. Thanks :good:
Click to expand...
Click to collapse
I posted link to twrp 3.2.1 if you need it on this thread.
Flash twrp 3.2.1
Wipe dalvik/art cache, data, cache, and system in twrp
Flash lineage rom
Flash gapps reboot
Wait 10 minutes sometimes it's slow
I'm on nougat firmware 7.1.1 CQJ1.
But it should work on you're firmware if not downgrade to mine and try that.
I don't update firmware or security patches unless its a Android upgrade like nougat to Oreo. The reason why is because I notice the google security patches always close up rooting and other things and don't really offer anything.
Techguy777 said:
I posted link to twrp 3.2.1 if you need it on this thread.
Flash twrp 3.2.1
Wipe dalvik/art cache, data, cache, and system in twrp
Flash lineage rom
Flash gapps reboot
Wait 10 minutes sometimes it's slow
I'm on nougat firmware 7.1.1 CQJ1.
But it should work on you're firmware if not downgrade to mine and try that.
I don't update firmware or security patches unless its a Android upgrade like nougat to Oreo. The reason why is because I notice the google security patches always close up rooting and other things and don't really offer anything.
Click to expand...
Click to collapse
Nothing Man :crying: I tried your method and it didn't work. I flashed TWRP 3.2.1 on TWRP 3.1 and i keep getting the black screen. I downgraded the firmware and repeated all the steps and nothing. I'm running out of options... I also understand and know everything about the security patches but i got the tablet last weekend like that. My luck
I know TWRP 3.2.1 and lineage OS install correctly and I think they boot up because i can hear and see the tablet connecting to PC.... It's just that the screen is all black for some reason
ELProfeMcK said:
Nothing Man :crying: I tried your method and it didn't work. I flashed TWRP 3.2.1 on TWRP 3.1 and i keep getting the black screen. I downgraded the firmware and repeated all the steps and nothing. I'm running out of options... I also understand and know everything about the security patches but i got the tablet last weekend like that. My luck
I know TWRP 3.2.1 and lineage OS install correctly and I think they boot up because i can hear and see the tablet connecting to PC.... It's just that the screen is all black for some reason
Click to expand...
Click to collapse
yep. that is also my situation.
blackness, evrywhere.
ELProfeMcK said:
Nothing Man :crying: I tried your method and it didn't work. I flashed TWRP 3.2.1 on TWRP 3.1 and i keep getting the black screen. I downgraded the firmware and repeated all the steps and nothing. I'm running out of options... I also understand and know everything about the security patches but i got the tablet last weekend like that. My luck
I know TWRP 3.2.1 and lineage OS install correctly and I think they boot up because i can hear and see the tablet connecting to PC.... It's just that the screen is all black for some reason
Click to expand...
Click to collapse
Yes I've heard of that you need to shine a bright light on you're screen or turn up you're brightness on you're google account I've noticed that I shut of live display and adaptive lighting on all my phones and google saves my account information so when I load my ROM and account for the first time it automatically sets brightness. It did work you're right the screen brightness is the problem others have had this.
Techguy777 said:
Yes I've heard of that you need to shine a bright light on you're screen or turn up you're brightness on you're google account I've noticed that I shut of live display and adaptive lighting on all my phones and google saves my account information so when I load my ROM and account for the first time it automatically sets brightness. It did work you're right the screen brightness is the problem others have had this.
Click to expand...
Click to collapse
I put my phone's flashlight and i could see the lineage set up but I've tried everything to get it to light up to full and it won't. Same for TWRP. I don't know what to do.
ELProfeMcK said:
I put my phone's flashlight and i could see the lineage set up but I've tried everything to get it to light up to full and it won't. Same for TWRP. I don't know what to do.
Click to expand...
Click to collapse
You need to go into twrp setting's and you'll see a row of options at the top click the 3 rd option its brightness and screen time out. On the ROM you go into settings and turn off the automatic brightness and set it
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
If someone knows how to turn up brightness with adb or something please do share. I understand it's hard to work with if you can't see the screen options.
Techguy777 said:
I posted link to twrp 3.2.1 if you need it on this thread.
Flash twrp 3.2.1
Wipe dalvik/art cache, data, cache, and system in twrp
Flash lineage rom
Flash gapps reboot
Wait 10 minutes sometimes it's slow
I'm on nougat firmware 7.1.1 CQJ1.
But it should work on you're firmware if not downgrade to mine and try that.
I don't update firmware or security patches unless its a Android upgrade like nougat to Oreo. The reason why is because I notice the google security patches always close up rooting and other things and don't really offer anything.
Click to expand...
Click to collapse
Flash twrp with twrp or Odin?
And if it's twrp do you extract the .tar file?
Okay! I installed it! Now can someone please tell me how to turn on the backlight? I tried the brightness thing bit the backlight still stays off.
Would another kernal fix it?
Techguy777 said:
You need to go into twrp setting's and you'll see a row of options at the top click the 3 rd option its brightness and screen time out. On the ROM you go into settings and turn off the automatic brightness and set it
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
If someone knows how to turn up brightness with adb or something please do share. I understand it's hard to work with if you can't see the screen options.
Click to expand...
Click to collapse
I did this in both TWRP and lineage O.S, brightness won't change. My brother told it could be kernel related but i dont understand why it works for some and black screens for others

Categories

Resources