ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
AT&T Samsung Galaxy Note 3 Safestrap
CURRENT PROJECT STATUS:
STABLE v3.71 (JB) / BETA v3.75 (NC2/KK)
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.7.1.x (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (2 on the N3 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for different sizes of /system, /data and /cache partitions. The defaults *SHOULD* be good enough for flashing the stock-based ROMs.
NOTE: The bigger you make these partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
[NEW FOR v3.72+ KK Safestrap] Requirement: busybox. If your stock ROM doesn't have it built-in you need to grab "Busybox" from the Play Store and run the installer.
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
INSTALL VIDEO by DMX (For VZW Device): https://www.youtube.com/watch?v=_RZIyeUMK-Y&feature=youtube_gdata_player
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
[NEW 2013-12-19]Go into your old Safestrap app and use the "Uninstall Recovery" button
THEN, open a "file explorer" of some sort (even TW "My Files" will work)
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK
Grant SU access
Use the "Install Recovery" button
All set, now you can reboot and re-activate whatever rom-slot you were using
KNOWN ISSUES:
[v3.75] If you install Safestrap on a rom-slot it will show "not installed". *DO NOT INSTALL SAFESTRAP ON A ROM-SLOT*
[v3.72] Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again. (DEBUGGING THIS AS I GET TIME)
[v3.72] If you installed the custom-safestrap APK by @drakeymcmb please use "Uninstall Recovery" and then uninstall that APK before installing a new one. They have different signatures and you will end up with 2 Safestraps and 2 hijacks.. which is very NOT good.
[v3.72] Busybox is now required for the Safestrap APK to work correctly
[v3.72] ROM-SLOTs aren't supported yet
[v3.72] "Reboot Recovery" doesn't work in the APK
If you don't see files on "Micro SDcard" for some reason try tapping that area and swapping to "Internal Storage" and then back again.
No Aroma installer support. This is due to the stock Note 3 kernel framebuffer. To build a recovery which worked, it needed QCOM patches. So will Aroma.
If you try a .zip file with an Aroma installer, it will most likely just hang.
If you use the "4way reboot" mod, then "Reboot Recovery" button in the Safestrap APK won't work correctly.
NEW TO v3.75:
TWRP 2.7.1.x update for the base recovery.
ROM-SLOTs now have a 16gb size limit (vs 4gb previously) [THEY DON'T WORK YET IN KK THO SO BE PATIENT]
DOWNLOADS:
CONFIRM THAT YOU ARE USING AN AT&T SAMSUNG GALAXY NOTE 3
FIND YOUR STOCK OPERATING SYSTEM VERSION BELOW AND USE THAT FILENAME:
[KITKAT:MLG/NB4/NC2]
LATEST FILE: Safestrap-HLTEATT-NC2-3.75-B03.apk
[JELLYBEAN BUILDS]
LATEST FILE: Safestrap-HLTEATT-3.71.apk
XDA Downloads
Mirror 2 (Crackflasher)
As of version 3.75, Safestrap Recovery is now based on TWRP 2.7.1.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
For the purposes of direct user testing I've established a channel on freenode.net IRC: #safestrap
I'm in the channel mostly all the time, but may not be active for discussion.
Special Thanks To
DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery. If you are considering a donation, then please have a look at the Team WIN website: http://teamw.in/project/twrp2
XDA:DevDB Information
Safestrap Recovery v3.71 (JB) / v3.75_B03 (NC2/KK), Tool/Utility for the AT&T Samsung Galaxy Note 3
Contributors
Hashcode, DeesTroy & TeamWin
Version Information
Status: Beta
Current Stable Version: 3.71
Stable Release Date: 2013-12-27
Current Beta Version: 3.75 B03
Beta Release Date: 2014-06-29
Created 2013-12-17
Last Updated 2014-08-12
Reserved
CHANGE LOG:
[2013/12/27] (v3.71) Fixed EXFAT support
If you don't see files on "Micro SDcard" for some reason try tapping that area and swapping to "Internal Storage" and then back again.
[2013/12/19] (v3.70) Fixed rom-slot boot scripts
[2013/12/19] Added support for new rom-slot system partition creation method to pass verification checks (THANKS @evilpotatoman for sharing the verification check info!)
[2013/12/17] Added "Instant Stock" button support during the Safestrap Splashscreen. If you press the "HOME" button you will instantly boot to stock without having to go into Safestrap. NOTE: This is a temporary selection. The next reboot will go back into the current "active" slot.
[2013/12/17] Added hijack rules for skipping in recovery and charge only modes
[2013/12/16] v3.65 ALPHA
[2013/12/16] New hijack to support safestrap under SElinux!
WARNING: This version is fairly stable, BUT you should know how to use ODIN.
Unbrick thread:
http://forum.xda-developers.com/showthread.php?t=2476353
Reserved
reserved
Let the games begin! thanks hash!
Sent from my SAMSUNG-SM-N900A
Hell yes! Downloading to test.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks for your hard work. Really happy....Note 3 is alive. ATT
Helllz yeah!!!! THANKYOU. DL now
Installed fine. Installled recovery as intended. Reboots into recovery: Good. Able to get into Recovery on normal boot: Good. Backup: Good.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Should Safe System be active?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Have to manually reboot into recovery, will no do it from SS app. But, manual reboot brings up slash screen
Sent from my SM-N900T using Tapatalk
wally3614 said:
Have to manually reboot into recovery, will no do it from SS app. But, manual reboot brings up slash screen
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Hmm. Mine worked from the app.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
installed fine. running a back up so far so good. took 289sec rebooted fine. rom toolbox shows back up. but it says its from march 14th 1970.
Boraltis said:
Hmm. Mine worked from the app.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have System Push fc come up and the Hangouts started fc also. i was on the Dirty Flash option we have had running TMO Jedi...i think that is causing problems, I am going to Restore back to fresh MI9 root de la vega and start from scratch.
Edit:
I ran OnceClickBin in DL Mode and went to reboot to continue THEN the full SS Recovery activated. So i continued reboot into system hangouts and other FCs stopped but still wont reboot from SS App...going to Odin stock. report back
Are you able to use roms such as x-note that use aroma installers? I tried and it got hung up at the starting aroma step
Sent from my SAMSUNG-SM-N900A using Tapatalk HD
I was just wondering the same thing
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Update:
If you are N900A and have ROMd using the method by Drakey, I recommend Odin back fresh before installing SS. No problems now and finally see the awesomeness that is SS. Thank u Hashcode....!
Sent from my SAMSUNG-SM-N900A using Tapatalk
Can u use ext-sdcard with this? It dosnt seem to work.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
drakeymcmb said:
Can u use ext-sdcard with this? It dosnt seem to work.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Inside recovery you can use sd card for backup / restore.
To change location by pressing on the storage button.
For rom-slots they stay on the internal storage only at this time.
Sent from my XT926 using Tapatalk
Can't wait to start using this, thank you very much hashcode!
Sent from my SM-N900T using XDA Premium 4 mobile app
CorleReeFer said:
Are you able to use roms such as x-note that use aroma installers? I tried and it got hung up at the starting aroma step
Sent from my SAMSUNG-SM-N900A using Tapatalk HD
Click to expand...
Click to collapse
this is for testing right now. i do not believe you can flash roms yet
also does this affect the knox counter at all?
Related
Stock LG Leaked Build KOT49I.V50018a + BusyBox + Root
for LG G Pad 8.3 V500 ONLY!
Android 4.4.2 KitKat
Disclaimer:
Use this at your own risk. I have personally flashed and tested this build on my own device successfully.
I am not responsible for any damage or data loss encountered due whatever reason.
Please ensure that you make a full backup of your system before flashing anything.
Features:
Stock 4.4.2 LG Leaked Build KOT49I.V50018a + Stock 4.4.2 Kernel
Doesn't Wipe Data partition.. (although I'd suggest you do a factory reset from TWRP if you encounter any issues)
Doesn't flash over existing Recovery, ABOOT, or BootLoaders (means you can keep TWRP and retain loki_patch capabilities)
SuperSU 1.93 + su binary Installed
BusyBox 1.22.1-Stericson Installed
build.prop changed to reflect US region (this build had default region EU)
Wipes Dalvik-Cache and Cache partition
Downloads:
LG-V500_KOT49I.V50018a_Stock-BB-Rooted.zip
Mirror (please use main download link above when possible):
LG-V500_KOT49I.V50018a_Stock-BB-Rooted.zip (hosted on id10terror.net)
md5:
73ddd78d135a0cd64e562913b001fa42 LG-V500_KOT49I.V50018a_Stock-BB-Rooted.zip
Prerequisites:
TWRP 2.7.0.0 Installed and working (not tested on CWM recovery)
FULL nandroid Backup
At least 3GB free space on internal memory (not including ZIP file)
Install:
Boot into TWRP recovery.
*** Make a Full backup before proceeding. ***
Flash .zip file in TWRP recovery.
Go take a walk, make some coffee, pace around nervously. Keep Calm... this will take a while! Be patient!!
Flash TWRP 2.7.0.1 for 4.4.2 in recovery (if not already installed)
Reboot device.
Enjoy!!
NEW! Great Install Tutorial Video by @Tomsgt !
Many Thanks to
@Aeras76 - for providing leaked TOT file
@Jessooca - for posting the links and mirrors
@Chainfire - for SuperSU and install script
@jazzruby - BusyBox install script
@Tomsgt - for his cool install tuturial video
Goodies & Add-ons:
LG OSP (On-Screen Phone) for Windows
LG On-Screen Phone is the service that allows you to view and manipulate your phone remotely via a PC, with the keyboard/mouse input from
the PC. You can also easily exchange data between the PC and your phone
Features
1. You can write, send and receive messages(SMS or other messengers) via PC.
2. You can transfer file contents in Gallery, Music, Video Player, Office Viewer in your phone to the PC by drag & drop.
3. You can easily transfer files from the PC to your phone by dragging & dropping.
4. You can get real-time event notification from the phone.
5. You can see the whole pages of Home Screens in Panorama View. (Only with LG Home)
6. Multi-touch input using keyboard/mouse.
Download:
LG OSP v4.0.004.130823 for Windows
Click to expand...
Click to collapse
Known Issues & Fixes:
Boot loop when booting into TWRP with USB plugged in
FIX: Install TWRP 2.7.0.1 for 4.4.2, this fixes bootloop while USB plugged in, and also fixes screen dimming issue.
Workaround: If running TWRP 2.7.0.0 for 4.2.2 - Unplug USB after device reboots. It should boot into Recovery without issue. Replug USB after TWRP has booted.
Click to expand...
Click to collapse
LG Update Center Force Closes when trying to update LG Apps
FIX:
Method 1:
Use Flashable zip to toggle between EU and US build.prop
It will detect what build.prop you currently have and swap it.
Note: If you have made any other changes to your build.prop, they will be lost using this. Use the other manual method instead.
Download and Flash LG-V500_KOT49I.V50018a_buildprop-toggle.zip in TWRP Recovery
Reboot
Update All LG Apps in LG Update Center
Flash the same LG-V500_KOT49I.V50018a_buildprop-toggle.zip in Recovery again to revert to US
Reboot
Method 2:
Using Root Explorer or BuildProp Editor from Play Store, change the following properties:
Code:
ro.product.locale.region=EU
ro.build.target_country=CIS
ro.build.target_region=EU
Reboot
Update All LG Apps in LG Update Center
Using Root Explorer or BuildProp Editor from Play Store, change the following entries back:
Code:
ro.product.locale.region=US
ro.build.target_country=NA
ro.build.target_region=NA
Reboot
Click to expand...
Click to collapse
Waiting in line
Waiting to flash! How long in percentage is the upload in? Sorry for my English.
Sent from my LG-V500 using Tapatalk
djcody said:
Waiting in line
Click to expand...
Click to collapse
Same.
thank you, i was waiting for this!
Inviato dal mio Nexus 5 utilizzando Tapatalk
Download Link is up, get it while it's hot!
Also, please let me know if you guys find any more bugs\issues so I can add them to "Known Issues".
Trying to downgrade and flash this now
how do i downgrade it? 1st time using lg product
I can simple install this in my room Mahdi I am using now. Remote control work in this room?
m.mcrespo said:
I can simple install this in my room Mahdi I am using now. Remote control work in this room?
Click to expand...
Click to collapse
Yes and yes.
Sent from my LG-D801 using XDA Premium 4 mobile app
chris85e said:
how do i downgrade it? 1st time using lg product
Click to expand...
Click to collapse
Still figuring out
Just noticed LG Update Center force closes.. Weird because it updated a few apps first, now it refuses to open.
Doesn't seem to affect any of the LG apps though... they are running just fine.
If i'm not the only one seeing this behavior I'll add it to the list of Known Issues and try and find a fix.
id10terror said:
Just noticed LG Update Center force closes.. Weird because it updated a few apps first, now it refuses to open.
Doesn't seem to affect any of the LG apps though... they are running just fine.
If i'm not the only one seeing this behavior I'll add it to the list of Known Issues and try and find a fix.
Click to expand...
Click to collapse
OK.. figured this out.. looks like changing the region settings in build.prop breaks the updater..
I used the original unmodified EU build.prop and was able to update all the apps.. then I just switched back to the US build.prop from my zip and all is good. :good:
Dude, you are the freaking man. Thanks a lot for this.:good:
id10terror said:
OK.. figured this out.. looks like changing the region settings in build.prop breaks the updater..
I used the original unmodified EU build.prop and was able to update all the apps.. then I just switched back to the US build.prop from my zip and all is good. :good:
Click to expand...
Click to collapse
Same here. My update center keeps force closing. I changed the build prop ro.product.locale.region to EU and rebooted but no luck. Do you have the build prop you replaced it with?
Sent from my LG-D801 using XDA Premium 4 mobile app
When I try installing it keeps failing at the end
sent from Moto X
stratus1011 said:
Same here. My update center keeps force closing. I changed the build prop ro.product.locale.region to EU and rebooted but no luck. Do you have the build prop you replaced it with?
Sent from my LG-D801 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just posted some instructions on 2nd post. Let me know if that works out for you.
http://forum.xda-developers.com/showthread.php?p=51374589#post51374589
Thanks op! What are the advantages with 4.4 over 4.2? What I really want is to get a better remote app working!
Sent from my LG-V500 using Tapatalk
fgcchevy said:
Thanks op! What are the advantages with 4.4 over 4.2? What I really want is to get a better remote app working!
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Feels a lot smoother, new Kitkat features etc... LG upped the brightness much brighter now at %75 than it was at %90 . Gamma also seems to have been corrected. Some users reported better batter life.
---------- Post added at 11:13 PM ---------- Previous post was at 11:01 PM ----------
Is it just me or Wifi isn't working on this build. I'm literally less 2 feet away from my router and wifi shows full signal yet nothing is loading. I can't even access the market. Turned airplane on and off a few times, rebooted my device, still no internet service
Thanks to @chenxiaolong DualBoot is possible on OnePlus 2
Original thread for DualBoot patcher is located here:
http://forum.xda-developers.com/showthread.php?t=2447534
Bugs report or questions to developer post in original thread.
Questions about how to use DualBoot you can ask here.
Download newest patcher from here:
https://snapshots.noobdev.io/
OnePlus 2 support is added to ver. 8.0.0.r1775.gccb8192
DualBoot Patcher is still under development, expect bugs!
I'm not responsible for bricked phones and your wife/girlfriend pregnancy!
You have been warned!
How to:
First make nandroid backup in TWRP!
1. Install DualBoot patcher apk, open an app and go to ROMs section
2. Set the current running kernel as kernel for Primary ROM (app will ask you to do so)
3. Download CM12.1 or any different AOSP ROM, Gapps and go to "Patch zip file" section.
Use minimal Gapps if you installing on stripped /system partition.
4. Patch the ROM (for OnePlus 2 choose "Data Slot") and patch Gapps ("Data slot").
a) Primary ROM upgrade (you can patch zip for Primary ROM if you want to flash primary and don't destroy second system.
b) Secondary (Patched ROM will be installed in /system partition), to use it you need at least 1GB free space in /system partition, you can for example delete from /system all apps that can be downloaded from GooglePlay eg. Youtube, Maps, GMail.
c) Multislot1, 2 , 3 - will install ROM in /cache partition (not usable in OnePlus 2 because /cache partition is too small).
d) Data slot - use it if you don't want to touch /system partition.
e) Extsd slot - Not usable in OnePlus 2.
5. Flash patched ROM and Gapps in TWRP or ROMs section in DualBoot app, click red button to do it.
6. Reboot
You second system should start.
How to switch between ROMs:
1. Both ROMs needs DualBoot patcher installed, in "ROMs" section you should see ROMs list.
2. To switch the ROM simply tap Primary or Secondary, tick indicator should appear on ROM.
3. Reboot
To check partition sizes and free space, go to "Free space" section.
App sharing probably still don't work, I didn't try it but most likely after you try it you will need to restore your nandroid.
Testes on OnePlus 2 A2003, I'm running OxygenOS 2.1.0 as Primary and CM12.1 as Secondary (installed on /system partition)
Kudos, love and donations goes to developer, I'm only the Messenger:
@chenxiaolong
DONATE
Wow me first.
Gonna try it tomorrow.
Will report back.
Sent from my ONE A2003 using Tapatalk
Thanks thanks thanks
Great weekend assured.....
Sent from my ONE A2003 using Tapatalk
Nice.. Thanks will try it over the weekend
Thanks a lot !!!
Sent from my ONE A2003 using Tapatalk
lukas77 said:
Thanks to @chenxiaolong DualBoot is possible on OnePlus 2
Download newest patcher from here:
https://snapshots.noobdev.io/
OnePlus 2 support is added to ver. 8.0.0.r1775.gccb8192
Click to expand...
Click to collapse
is this the only version which supports our device or we can use the latest version as well?
hunhool said:
is this the only version which supports our device or we can use the latest version as well?
Click to expand...
Click to collapse
Use latest, in version I mentioned support were added.
Awesome!
Similar features like multi-rom from @tassadar for Nexus devices?
vergilbt said:
Similar features like multi-rom from @tassadar for Nexus devices?
Click to expand...
Click to collapse
TBH I've never used MultiROM and as far as I know MR needs special recovery and kernel. DualBoot needs only root to work
Sent from my ONE A2003 using Tapatalk
That's right MR need a modified twrp and a kernel with kexec-hardboot
Seems like dual boot is easier to handle
lukas77 said:
TBH I've never used MultiROM and as far as I know MR needs special recovery and kernel. DualBoot needs only root to work
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Dualboot could run more than two ROM or OS?
I'd anybody running dual boot? Isn't working for me...
1. Install room
2. Set kernel of primary
3. patch rom to data slot
4. Zip patched rom without changing location (superSU grant permission)
5. Reboot
But after reboot it loads every time twrp recovery and not secondary rom...
Where is my fault?
vergilbt said:
I'd anybody running dual boot? Isn't working for me...
1. Install room
2. Set kernel of primary
3. patch rom to data slot
4. Zip patched rom without changing location (superSU grant permission)
5. Reboot
But after reboot it loads every time twrp recovery and not secondary rom...
Where is my fault?
Click to expand...
Click to collapse
No idea, ask the developer @chenxiaolong in his thread provided in OP.
Also attach multiboot.log file created in /sdcard
Sent from my ONE A2003 using Tapatalk
vergilbt said:
I'd anybody running dual boot? Isn't working for me...
1. Install room
2. Set kernel of primary
3. patch rom to data slot
4. Zip patched rom without changing location (superSU grant permission)
5. Reboot
But after reboot it loads every time twrp recovery and not secondary rom...
Where is my fault?
Click to expand...
Click to collapse
You didn't install the ROM via. TWRP recovery. There might be an issue with the way the ROM patcher flashes the files via an Online Flash (with you booted into your Primary ROM) vs. an offline flash (in TWRP, pre-boot).
work fine for me with oxygen 2.1 in primary and cm12.1 in/data ,
sadly my favorite rom : mookee seems doesb't support this patcher, flash fail everytime in twrp
Thank you very much for this great port!
Is there any chance of getting MultiROM support for the 2? I loved MR in both my Nexus 5 and OnePlus One.
jmazzamj said:
Thank you very much for this great port!
Is there any chance of getting MultiROM support for the 2? I loved MR in both my Nexus 5 and OnePlus One.
Click to expand...
Click to collapse
Don't you think you should ask this question MultiROM developer? This is completely different app, not related to MultiROM.
Sent from my ONE A2003 using Tapatalk
Great to have this on our device! Always used multirom on my OPO but to be honest, this is a better solution! Usually I had to reboot to TWRP and being offline for 15 minutes or more. Now I can just patch&flash a rom while staying online.
The only thing is... Why is it called dual boot? It's multi boot actually.
READ CAREFULLY
Ok people are having issues with the original thread which can be found HERE the thread is just so cluttered, and instead of it being cleaned I'll just make a new one for people with the correct information so its not as cluttered. I have been running this rom now for little over 4 days no issues following the help of JRunRun and njdan30 ( So give them thanks )
I can confirm SMS/MMS/BT/GPS all work with no issues ( or with Fixes )
This is JRunRun's installation information that allows the ROM to work flawlessly and worked for me with minor tweaks ( I always try the path of least resistance first before taking the hard way )
TWRP 2.8.7.0 seems to work without issues.
EASY WAY ( TRY FIRST BEFORE YOU TRY THE MANUAL MANIPULATION OF FILES )
1. downloaded - ROM 3.3 DarkLord S7E APEK
2. downloaded - SLIM_APNs SLIM_APNs
3. downloaded - SU SuperSU 2.74
4. placed ROM and APN.zip and Supersu on my external sdcard
5. booted recovery (twrp 2.7.8.0), (I used 3.0.2 )
6. WIPE - Dalivk/Cache/System/Data (Then for good measure I factory reset)
7. Install -- loaded flashable zips from external sd to install
a. ROM 3.3 --> add more zips
b. Slim APN zip
c. Supersu --> started the flash
8. Flashed ROM --> chose sprint phone version, chose "SPR" as my csc in Aroma, DID NOT reboot on finish ( This is where people may be getting confused..)
Select SPRINT MODEL N9xxx then select SPR as the Sales Code ALSO there is another option that is showed here that DID give me issues there is 3 of them. 2 of them are WIPE options the 3rd is NO WIPE keep settings and app data I choose the 3rd option cause I noticed when I tried the first 2 my SMS would not work, and my WIFI would constantly diconnect
9. Allowed twrp to finish installing flashable apn and supersu zips
10. wiped cache/dalvik, reboot to system (10-20 min reboot).
8. Did not restore anything on system setup. Entered wi-fi info but turned it off afterwards. ( I just skipped this all together until the phone was completely ready to go )
Once loaded you will pick your language, and a option will show up wanting you to consent to sending usage data, uncheck mark that and continue setup
11. Loaded new kernel -- darkera 1.9 lte vzw (doubt this step is necessary but easy to find with a google search samsungvn) ( If you need the kernel link you can ask for it here and we will send it too you in a PM ) ( I am running the SPRINT kernel which seems to be very stable )
VIDEOS
Video 1
Video 2
Video 3
Video 4
MANUAL FIX FOR SMS/MMS
1. Backed up stock OF1 apns-conf.xml to computer
2. downloaded - ROM 3.3 DarkLord S7E APEK
downloaded - SLIM_APNs SLIM_APNs
downloaded - SU SuperSU 2.74
3. Replaced apns-conf.xml file in SLIM_APNs.zip with the stock apns-conf.xml file saved in step 1, rezipped and saved with new zip name "stock_APNs_modded.zip" Some people are just flashing the slim apn without adjusting it and having succes.
4. placed ROM and APN.zip and Supersu on my external sdcard
5. booted recovery (twrp 2.7.8.0)
6. WIPE - Dalivk/Cache/System/Data [/COLOR] (Then for good measure I factory reset)
7. Install -- loaded flashable zips from external sd to install
a. ROM 3.3 --> add more zips
b. modded Slim APN zip
c. Supersu --> started the flash
5. Flashed ROM --> chose sprint phone version, chose "SPR" as my csc in Aroma DID NOT reboot on finish ( This is where people may be getting confused..)
Select SPRINT MODEL N9xxx then select SPR as the Sales Code ALSO there is another option that is showed here that DID give me issues there is 3 of them. 2 of them are WIPE options the 3rd is NO WIPE keep settings and app data I choose the 3rd option cause I noticed when I tried the first 2 my SMS would not work, and my WIFI would constantly diconnect
6. Allowed twrp to finish installing flashable apn and supersu zips
7. wiped cache/dalvik, reboot to system (10-20 min reboot).
8. Did not restore anything on system setup. Entered wi-fi info but turned it off afterwards. ( I just skipped this all together until the phone was completely ready to go )
Once loaded you will pick your language, and a option will show up wanting you to consent to sending usage data, uncheck mark that and continue setup
9. change /efs/imei/mps_code to "vzw" via ES File app <-- vzw must be lower case
10. build prop changes:
Code:
ro.product.name “cm_hltevzw”
ro.product.device “hltevzw”
telephony.lteOnCdmaDevice="1"
ro.telephony.default_network="8"
Added the following lines after the ro.telephony.default_network line:
Code:
ro.cdma.home.operator.numeric=311480
ro.cdma.home.operator.alpha="Verizon Wireless”
ro.cdma.homesystem=64, 65, 76, 77, 78, 79, 80, 81, 82, 83
gsm.sim.operator.numeric=311480
gsm.operator.numeric=311480
gsm.sim.operator.alpha=Verizon
gsm.operator.alpha=Verizon
ro.net.apnwhitelist=fota,ims,supl,verizon,cbs,mms
ro.net.apnroamingwhitelist=ims
ro.net.apnpolicywhitelist=fota,ims,verizon,verizon 800
ro.net.apnroamingblacklist=fota,verizon800
11. used Galaxy Tools to make sure mps_code and sales_code is set to "vzw"
12. Loaded new kernel -- darkera 1.9 lte vzw (doubt this step is necessary but easy to find with a google search samsungvn) ( If you need the kernel link you can ask for it here and we will send it too you in a PM ) ( I am running the SPRINT kernel which seems to be very stable )
Again thanks to JRunRun and njdan30 for all the helpful information and always trying to give helping hand to those that need it! and those that want to learn!! :highfive::highfive:
Your links don't work.
[email protected] said:
Your links don't work.
Click to expand...
Click to collapse
It looks like it was either deleted or possibly moved I will try and upload the files
Is it a necessity to be on OF1? Im still on NC4. Just curious.
wdcspurs said:
Is it a necessity to be on OF1? Im still on NC4. Just curious.
Click to expand...
Click to collapse
Honestly I do not have a answer to that, since I was already OF1 when I unlocked the bootloader. You can always try and let people know here, I was not the creator of this ROM I was just making a new thread for people who were having issues, due to the original thread being so cluttered with 5 billion different, ways to make it work..
As far as the files go I am currently uploading to google drive to share. I should have everything ready in a few more hours, and will post links
Links fixed at the moment, looking for other hosts for mirrors
wdcspurs said:
Is it a necessity to be on OF1? Im still on NC4. Just curious.
Click to expand...
Click to collapse
In loading this rom everything will change but the modem. I'm still using OF1 modem for example and have a totally functioning rom. That being said, yes I would upgrade and flash a new OF1 rom clean before doing the install. This rom takes quite a bit too get working but when you get use to it, it's no big deal. I wish folks good luck on following the instructions. They did not include any apn settings which I needed to get it going but what do I know.
Hello I am a bit confused with the rom 3.3 ---> add more zips did you mean you installed the rom then installed slim zip then you reinstalled the rom again?
Sent from my SM-N900V using XDA-Developers mobile app
---------- Post added at 03:12 PM ---------- Previous post was at 03:09 PM ----------
And did you modify slim apn with your apns.conf.xml?
Sent from my SM-N900V using XDA-Developers mobile app
armus said:
In loading this rom everything will change but the modem. I'm still using OF1 modem for example and have a totally functioning rom. That being said, yes I would upgrade and flash a new OF1 rom clean before doing the install. This rom takes quite a bit too get working but when you get use to it, it's no big deal. I wish folks good luck on following the instructions. They did not include any apn settings which I needed to get it going but what do I know.
Click to expand...
Click to collapse
Which is why you download the SLIMS_APN
seanbwoi said:
Hello I am a bit confused with the rom 3.3 ---> add more zips did you mean you installed the rom then installed slim zip then you reinstalled the rom again?
Sent from my SM-N900V using XDA-Developers mobile app
---------- Post added at 03:12 PM ---------- Previous post was at 03:09 PM ----------
And did you modify slim apn with your apns.conf.xml?
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Add Zips means in TWRP you select the ROM, then select ADD more ZIPS which in turn you add 3.3 SLIM_APN, and SU then flash..
and no I didn't modify anything, my install method is highlighted in RED.
Thanks will definitely try it later
Sent from my SM-N900V using XDA-Developers mobile app
I can't seem to save my apn due to the fact that at apn option it says user restricted any idea how to fix this? can't get data with this
Sent from my SM-G935F using XDA-Developers mobile app
---------- Post added at 03:15 AM ---------- Previous post was at 02:26 AM ----------
I also can't get the signal to stop cutting off
Sent from my SM-G935F using XDA-Developers mobile app
seanbwoi said:
I can't seem to save my apn due to the fact that at apn option it says user restricted any idea how to fix this? can't get data with this
Sent from my SM-G935F using XDA-Developers mobile app
---------- Post added at 03:15 AM ---------- Previous post was at 02:26 AM ----------
I also can't get the signal to stop cutting off
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Then you probably didn't uncheck mark the, "send data" option while setting up your phone... and if you used my way in red ( I didn't have to use the FULL how to ) then you shouldn't have to edit the APN at all, you just flash the rom APN and SU that's all you have to do.
ONLY use the full installation if the easy way doesn't work...
The pics I just uploaded will kinda help, in TWRP. make sure you ADD all 3 files ROM - SLIM APN - SU then you start the flash
2nd pic is install of rom, you choose what is circled, I didn't get one of the next screen but you scroll down till you find the code "SPR"
Next pic again the option needed here is whats circled.
4th pic, MAKE sure you leave this ALONE don't select it, just finish out of it, and it will take you back to TWRP and the flash/install of SLIMS APN and SU will begin once those are done reboot
Can't mount extsd.
Nvm. I figured it out.
You have to flash the Kernel for the SD to work
Sent from my SM-G935F using XDA-Developers mobile app
ExiaGN said:
You have to flash the Kernel for the SD to work
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Can someone send me the kernel by PM? Thanks
i was able to get the rom up and running but noticed i am unable to access the internal sd or external sd through my phone. I am also unable to boot to twrp.
which means I cannot flash the kernel that allows access to the sd card.
I tried reinstalling twrp through odin, it was supposedly successful but just get pushed back into system when booting to recovery.
any help would be appreciated
thanks,
Edit: was able to access twrp through restart option instead of shutting off and using hardware button combo
MMS
I just got this installed and all seems working fine. Except MMS. Im sure Im just missing something. When I send an mms messgae, it fails and says invalid address entered. What gives?
could someone send me the link to the darkera 1.9 lte vzw kernel please
I made the mistake of changing the Access Point Names without copying them first. Would someone be as so kind to list the correct settings, that has everything working. Thanks
jbxr1992 said:
i was able to get the rom up and running but noticed i am unable to access the internal sd or external sd through my phone. I am also unable to boot to twrp.
which means I cannot flash the kernel that allows access to the sd card.
I tried reinstalling twrp through odin, it was supposedly successful but just get pushed back into system when booting to recovery.
any help would be appreciated
thanks,
Edit: was able to access twrp through restart option instead of shutting off and using hardware button combo
Click to expand...
Click to collapse
Shouldn't be having any issues with getting back into TWRP, using the buttons.. Did you use the full install or my work around?
wdcspurs said:
I just got this installed and all seems working fine. Except MMS. Im sure Im just missing something. When I send an mms messgae, it fails and says invalid address entered. What gives?
Click to expand...
Click to collapse
Did you use the full flash guide? or my work around ? ( work around was in red )
JEFFSGTP said:
could someone send me the link to the darkera 1.9 lte vzw kernel please
Click to expand...
Click to collapse
Sent
TheHanz said:
I made the mistake of changing the Access Point Names without copying them first. Would someone be as so kind to list the correct settings, that has everything working. Thanks
Click to expand...
Click to collapse
Did you try using the quick way or did you use the full step by step ?
DualBootPatcher
A big thanks to @chenxiaolong for originally creating this wonderful utility.
What is dual booting?
It is like having 2 ROMs installed at once, and you can switch to other ROM without flashing it all over again, your data, stuff everything is preserved.
How to use the patcher?
A quote from the author himself:
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Click to expand...
Click to collapse
For now we dont have Windows executable, so only prefer to use the android app.
How to dual boot?
Before doing anything, download the App from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
Click to expand...
Click to collapse
App and data sharing?
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
(Hope my analogy didn't suck too much )
How do I?
Switch the ROM if something doesn't work properly ?
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Click to expand...
Click to collapse
Downloads
App - Here
Credits
@chenxiaolong and to all the contributors in this project
XDA:DevDB Information
DualBootPatcher for Lenovo Vibe K5 & K5 Plus , Tool/Utility for the Android General
Contributors
Dreamstar, chenxiaolong
Version Information
Status: Beta
Created 2016-12-19
Last Updated 2016-12-25
Reserved
Thanks for this!
Can anyone confirm this working?
Can confirm this is working in Lenovo Vibe K5 a6020a40 device thanx for this you are awesome
This is truly awesome!!
First I flash stock then vegito then dual boot patcher apk and make dual boot flashable zip and when flashing through twrp it fails to flash and this error. On apk
Device a46 2gb
netship said:
First I flash stock then vegito then dual boot patcher apk and make dual boot flashable zip and when flashing through twrp it fails to flash and this error. On apk
Device a46 2gb
Click to expand...
Click to collapse
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Dreamstar said:
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Click to expand...
Click to collapse
Wow man just wow!
Dreamstar said:
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Click to expand...
Click to collapse
Thank you Very much!!
Recieved error message while installing secondary rom.
Guys any solution?
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
You may try this.
netship said:
You may try this.
Click to expand...
Click to collapse
I tried bro still same problem...
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
Upload that log file here
Error log
App sharing not working.. or I'm doing something wrong.. don't know but not working for me.
What about efidroid manager
Can anybody try to port it to lenovo k5??
Last I checked with 10/4 aicp nightly, it's not working. Needs some fixes.
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
Same here tried changing name no success
Samsung Galaxy Note 8 (Snapdragon)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.09-B01 [Nougat:7.1.1]
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
APK install:
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
APK:
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
- Busybox is now required for the Safestrap APK to work correctly
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY Note 8 (Snapdragon) [Nougat:7.1.1]
LATEST ZIP: Safestrap-4.09-B01-GREATQLTE-SS-FF-flashable.zip
LATEST APK: Safestrap-4.09-B01-GREATQLTE.apk
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
@jrkruse for pointing me that S8 has permissive root. @partcyborg for getting root on S8.
@me2151 for testing and getting the right configs in place.
CHANGELOG:
4.09-B01 [2019-04-19]
- TWRP updated to 3.3.0.
- Fix reboot function
- Add reboot to safestrap button in reboot menu
- Add Edl button in reboot menu
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
4.08-B01 [2019-03-01]
- TWRP updated to 3.2.3.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up.
4.07-B01 [2018-07-16]
- Fix CHARGER_BOOT detection.
- TWRP updated to 3.2.2.
- Update safestrap portrait theme.
- Update safestrap app to use topjohnwu's libsu & internal busybox (busybox app not needed anymore).
4.06-B02 [2018-04-10]
- Fix taskset cpus to 8 cores (thanks to Hashcode).
- Add exfat support for recovery (ext-sdcard fix).
- Blacklist mouse cursor in recovery (thanks to me2151).
- Fix MTP (thanks to me2151).
4.06-B01 [2018-04-03]
- Initial release.
BUGS:
- ROM-slots not working for now.
Mine
Awesome to see this. We might have true development after all.
I hope we can get the rom part of safestrap fixed! Great work
Wahhhh just when i oreo is released for the unlocked note 8. Haha guess i wont be taking oreo update anytime soon and may actually want to root dispite the 80% battery.
I really hope there are still developers that will cook roms or ports of internation version like dr ketans.
Thanks. Cant wait for ur rom portion of safestrap.
I can confirm this is legit guys. backups and restores work. For the moment full custom roms like lineage will not be possible. but ill be working on that
I'd love to see me some Darthstalker ROM's those were my favorite on the Note 5. I don't know if Jovy still makes ROM's though.
Best I can tell I can't Backup or access the external SDCard ... Only the internal
Is that the same for you guys?
jcrompton said:
Best I can tell I can't Backup or access the external SDCard ... Only the internal
Is that the same for you guys?
Click to expand...
Click to collapse
i can access external fine.
why would you back it up though
me2151 said:
i can access external fine.
why would you back it up though
Click to expand...
Click to collapse
Lol
I guess I should have wrote "backup to" ext sd
When I click on microsd in recovery it won't activate
---------- Post added at 12:31 AM ---------- Previous post was at 12:23 AM ----------
I went back into safestrap recovery (for some reason my screenshot didn't save)
But when I tried to mount the microsd or external SDCard I got an error
Invalid argument ..... Blah blah can't mount ext sd
Im running a backup to my sdcard as i type this. Works perfectly. I am however not using the build in this thread. just my own.
me2151 said:
Im running a backup to my sdcard as i type this. Works perfectly. I am however not using the build in this thread. just my own.
Click to expand...
Click to collapse
?
Well maybe that's why
jcrompton said:
Well maybe that's why
Click to expand...
Click to collapse
Doubt it i ha ent changed any mounts on mine
me2151 said:
Doubt it i ha ent changed any mounts on mine
Click to expand...
Click to collapse
Well it's gotta be something since I can't access it
I started a thread a long time ago saying this is possible and someone should start on it, and everyone said I was dumb and didn't know ehat I was talking about. Me121 or what ever his name is said he worked on the fish a little its like safestrap but couldn't get it to work.
So glad someone got it working and am very Happy to be a note 8 owner now my next paycheck I will donate a beer to ya
DroidisLINUX said:
I started a thread a long time ago saying this is possible and someone should start on it, and everyone said I was dumb and didn't know ehat I was talking about. Me121 or what ever his name is said he worked on the fish a little its like safestrap but couldn't get it to work.
So glad someone got it working and am very Happy to be a note 8 owner now my next paycheck I will donate a beer to ya
Click to expand...
Click to collapse
Yup FiSH had the same issue this had with it inits not launchng but this guy figured it out
You guys are simply amazing I just had to say that
jcrompton said:
Best I can tell I can't Backup or access the external SDCard ... Only the internal
Is that the same for you guys?
Click to expand...
Click to collapse
Lets make it clear, jrkruse tested 16GB and 32GB ext-sd and it works on S8+, 64GB and above not working.
I have tested 16GB on my S8 and works.
What size is yours?
afaneh92 said:
Lets make it clear, jrkruse tested 16GB and 32GB ext-sd and it works on S8+, 64GB and above not working.
I have tested 16GB on my S8 and works.
What size is yours?
Click to expand...
Click to collapse
128
I didn't know it mattered .... I guess size does matter ,,eh?