Hey everyone!
It's been a while since I've done a ROM and I had a hankering to play around and have some fun again. This build is nothing super special but it is a base for me to work with and I figured I would share it with anyone who is interested.
This build is an almost 100% stock odexed ROM. The only difference from this and flashing a stock TAR is that this can be flashed through recovery and comes pre-rooted.
I'm currently working on a deodexed ROM for devs and themers to use as a base if they are so inclined but I'm having issues with my Java environment.
REQUIREMENTS:You MUST be on a Lollipop bootloader in order for this ROM to work. I recommend flashing the OG1 Stock TAR and then Philz Recovery through Odin prior to flashing the ROM.
ROM FLASHING:- Boot to your custom recovery (recommended recovery is Philz Touch v6.41.6).
- Wipe Cache.
- Wipe Dalvik Cache.
- Wipe System and Data (Under "Wipe Data/Factory Reset" and then "Clean to Install a New ROM" in Philz Touch).
- Flash ROM!
- Enjoy!
As a side-note I would strongly recommend flashing Tdunham's Debloat tool before running the ROM for the first time. It comes with a TON of bloat (thank you Sprint and Samsung!). You can get the Debloat tool in the attachments on this post: http://forum.xda-developers.com/spr...ent/stock-rom-od3-android-l-deodexed-t3128908
CHANGELOG:OG1 Stock Rooted Odexed v1.2 - (Released 11/18/15)
- Changed root method to be consistent with changes in my Mostly Stock OG1 ROM
OG1 Stock Rooted Odexed v1.1 - (Released 10/7/15)
- Fixed issue with root access not sticking
OG1 Stock Rooted Odexed v1.0 - Initial Release (Released 10/6/15)
- Added Root to Stock Odexed ROM
DOWNLOADS: Odexed OG1 ROM
OG1 Stock Restore TAR
Philz Touch Recovery v6.41.6
Enjoy!
It says it comes pre-rooted.. It doesn't seem to be pre-rooted. I followed the instructions precisely even running the Dbloat right after flashing the firmware. What did I do wrong? Super SU won't function. Busybox won't install. What gives?
fbarcenas said:
It says it comes pre-rooted.. It doesn't seem to be pre-rooted. I followed the instructions precisely even running the Dbloat right after flashing the firmware. What did I do wrong? Super SU won't function. Busybox won't install. What gives?
Click to expand...
Click to collapse
Good question... Can you do me a favor and download Root Check from the Play Store and see if it shows you as rooted?
rwilco12 said:
Good question... Can you do me a favor and download Root Check from the Play Store and see if it shows you as rooted?
Click to expand...
Click to collapse
Root Checker responds "Sorry! Root access is not properly installed on this device." Do ya think the Dbloat nerfed it?
---------- Post added at 04:13 AM ---------- Previous post was at 04:10 AM ----------
I don't think the debloat nerfed it the script does not contain a line for deleting busybox nor Super SU.
Code:
delete_recursive("/system/app/Blurb");
delete_recursive("/system/app/Books");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/DriveLink");
delete_recursive("/system/app/DriveLinkRemote");
delete_recursive("/system/app/Flipboard");
delete_recursive("/system/app/GeoLookout");
delete_recursive("/system/app/Headlines");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/SamsungAppsWidget_Phone_Carrier");
delete_recursive("/system/app/SecKidsModeInstaller");
delete_recursive("/system/app/Videos");
delete_recursive("/system/priv-app/ConnectionManager");
delete_recursive("/system/priv-app/ID");
delete_recursive("/system/priv-app/SamsungApps_K");
delete_recursive("/system/priv-app/SamsungBilling");
delete_recursive("/system/app/SecurityLogAgent");
delete_recursive("/system/priv-app/SNS");
delete_recursive("/system/priv-app/Zone");
delete_recursive("/data/app/com.google.android.apps.books-1");
delete_recursive("/data/app/com.google.android.apps.books-2");
delete_recursive("/data/app/com.google.android.apps.magazines-1");
delete_recursive("/data/app/com.google.android.apps.magazines-2");
delete_recursive("/data/app/com.google.android.play.games-1");
delete_recursive("/data/app/com.google.android.play.games-2");
delete_recursive("/data/app/com.lookout-1");
delete_recursive("/data/app/com.lookout-2");
delete_recursive("/data/app/com.nascar.nascarmobile-1");
delete_recursive("/data/app/com.nascar.nascarmobile-2");
delete_recursive("/data/app/com.nbadigital.gametimelite-1");
delete_recursive("/data/app/com.nbadigital.gametimelite-2");
delete_recursive("/data/app/com.pinsight.eureka.offers-1");
delete_recursive("/data/app/com.pinsight.eureka.offers-2");
delete_recursive("/data/app/com.pinsightmedia.vpl.Amazon-1");
delete_recursive("/data/app/com.pinsightmedia.vpl.Amazon-2");
delete_recursive("/data/app/com.sprint.android.musicplus2033-1");
delete_recursive("/data/app/com.sprint.android.musicplus2033-2");
delete_recursive("/data/app/com.wipit.sprintmoneyexpress-1");
delete_recursive("/data/app/com.wipit.sprintmoneyexpress-2");
delete_recursive("/data/app/flipboard.app-1");
delete_recursive("/data/app/flipboard.app-2");
delete_recursive("/data/app/com.mobiroo.xgen-1");
delete_recursive("/data/app/com.mobiroo.xgen-2");
delete_recursive("/data/app/com.google.android.apps.docs-1");
delete_recursive("/data/app/com.google.android.apps.docs-2");
delete_recursive("/data/app/com.telenav.app.android.scout_us-1");
delete_recursive("/data/app/com.telenav.app.android.scout_us-2");
delete_recursive("/data/app/com.sprint.w.v8-1");
delete_recursive("/data/app/com.sprint.w.v8-2");
delete_recursive("/data/app/com.sprint.international.message-1");
delete_recursive("/data/app/com.sprint.international.message-2");
delete_recursive("/data/app/com.google.android.videos-1");
delete_recursive("/data/app/com.google.android.videos-2");
delete_recursive("/data/app/com.google.android.music-1");
delete_recursive("/data/app/com.google.android.music-2");
fbarcenas said:
Root Checker responds "Sorry! Root access is not properly installed on this device." Do ya think the Dbloat nerfed it?
---------- Post added at 04:13 AM ---------- Previous post was at 04:10 AM ----------
I don't think the debloat nerfed it the script does not contain a line for deleting busybox nor Super SU.
Code:
delete_recursive("/system/app/Blurb");
delete_recursive("/system/app/Books");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/DriveLink");
delete_recursive("/system/app/DriveLinkRemote");
delete_recursive("/system/app/Flipboard");
delete_recursive("/system/app/GeoLookout");
delete_recursive("/system/app/Headlines");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/SamsungAppsWidget_Phone_Carrier");
delete_recursive("/system/app/SecKidsModeInstaller");
delete_recursive("/system/app/Videos");
delete_recursive("/system/priv-app/ConnectionManager");
delete_recursive("/system/priv-app/ID");
delete_recursive("/system/priv-app/SamsungApps_K");
delete_recursive("/system/priv-app/SamsungBilling");
delete_recursive("/system/app/SecurityLogAgent");
delete_recursive("/system/priv-app/SNS");
delete_recursive("/system/priv-app/Zone");
delete_recursive("/data/app/com.google.android.apps.books-1");
delete_recursive("/data/app/com.google.android.apps.books-2");
delete_recursive("/data/app/com.google.android.apps.magazines-1");
delete_recursive("/data/app/com.google.android.apps.magazines-2");
delete_recursive("/data/app/com.google.android.play.games-1");
delete_recursive("/data/app/com.google.android.play.games-2");
delete_recursive("/data/app/com.lookout-1");
delete_recursive("/data/app/com.lookout-2");
delete_recursive("/data/app/com.nascar.nascarmobile-1");
delete_recursive("/data/app/com.nascar.nascarmobile-2");
delete_recursive("/data/app/com.nbadigital.gametimelite-1");
delete_recursive("/data/app/com.nbadigital.gametimelite-2");
delete_recursive("/data/app/com.pinsight.eureka.offers-1");
delete_recursive("/data/app/com.pinsight.eureka.offers-2");
delete_recursive("/data/app/com.pinsightmedia.vpl.Amazon-1");
delete_recursive("/data/app/com.pinsightmedia.vpl.Amazon-2");
delete_recursive("/data/app/com.sprint.android.musicplus2033-1");
delete_recursive("/data/app/com.sprint.android.musicplus2033-2");
delete_recursive("/data/app/com.wipit.sprintmoneyexpress-1");
delete_recursive("/data/app/com.wipit.sprintmoneyexpress-2");
delete_recursive("/data/app/flipboard.app-1");
delete_recursive("/data/app/flipboard.app-2");
delete_recursive("/data/app/com.mobiroo.xgen-1");
delete_recursive("/data/app/com.mobiroo.xgen-2");
delete_recursive("/data/app/com.google.android.apps.docs-1");
delete_recursive("/data/app/com.google.android.apps.docs-2");
delete_recursive("/data/app/com.telenav.app.android.scout_us-1");
delete_recursive("/data/app/com.telenav.app.android.scout_us-2");
delete_recursive("/data/app/com.sprint.w.v8-1");
delete_recursive("/data/app/com.sprint.w.v8-2");
delete_recursive("/data/app/com.sprint.international.message-1");
delete_recursive("/data/app/com.sprint.international.message-2");
delete_recursive("/data/app/com.google.android.videos-1");
delete_recursive("/data/app/com.google.android.videos-2");
delete_recursive("/data/app/com.google.android.music-1");
delete_recursive("/data/app/com.google.android.music-2");
Click to expand...
Click to collapse
I'm 99% positive it wasn't the debloat script. My guess is that for some reason root didn't stick when it was flashed. Can you try flashing the ROM again without wiping first? See if maybe flashing over it fixes it for you? If that doesn't let's try a clean slate with a full wipe and flash again. When I flashed it earlier I got root with each flash, I did it three times just to be sure prior to posting.
no root
I'm also having issues with root. Root checker says the device is rooted, but no root dependent apps will function and I never get the prompt to grant rights. Dirty flashing the rom again to see if it helps.
---------- Post added at 09:09 AM ---------- Previous post was at 08:16 AM ----------
Cubit33 said:
I'm also having issues with root. Root checker says the device is rooted, but no root dependent apps will function and I never get the prompt to grant rights. Dirty flashing the rom again to see if it helps.
Click to expand...
Click to collapse
When I first did a wipe and flashed this rom, before rebooting my Philz recovery prompted a warning that the rom might flash stock recovery, do I want to allow this? The first time I said no, following the dirty flash just now I said yes and root appears to be working now. Possibly just a weird recovery bug?
rwilco12 said:
I'm 99% positive it wasn't the debloat script. My guess is that for some reason root didn't stick when it was flashed. Can you try flashing the ROM again without wiping first? See if maybe flashing over it fixes it for you? If that doesn't let's try a clean slate with a full wipe and flash again. When I flashed it earlier I got root with each flash, I did it three times just to be sure prior to posting.
Click to expand...
Click to collapse
I don´t think you're doing a full wipe before you install. the remnant files are giving you root. Try formatting system before doing your install. I'm going to try formatting system before trying it again.
Cubit33 said:
When I first did a wipe and flashed this rom, before rebooting my Philz recovery prompted a warning that the rom might flash stock recovery, do I want to allow this? The first time I said no, following the dirty flash just now I said yes and root appears to be working now. Possibly just a weird recovery bug?
Click to expand...
Click to collapse
fbarcenas said:
I don´t think you're doing a full wipe before you install. the remnant files are giving you root. Try formatting system before doing your install. I'm going to try formatting system before trying it again.
Click to expand...
Click to collapse
I found the source of the issue and have uploaded a fix!
Let's just say its not a good idea to work on two projects at once.
v1.1 is now available via the links in the OP. Thank you for your patience!
OK I've done the dirty flash twice now. Once were I hit DISABLE and the other time I hit NO. Both times I ran Root Checker and both times it said it was not rooted.
Any Ideas?
---------- Post added 8th October 2015 at 12:25 AM ---------- Previous post was 7th October 2015 at 11:36 PM ----------
What root method are you using? maybe we should just run the root script you used. Towelroot, doomlord?
fbarcenas said:
OK I've done the dirty flash twice now. Once were I hit DISABLE and the other time I hit NO. Both times I ran Root Checker and both times it said it was not rooted.
Any Ideas?
Click to expand...
Click to collapse
I uploaded an updated build a few hours ago that should fix the issue. Have you tried that new build?
rwilco12 said:
I uploaded an updated build a few hours ago that should fix the issue. Have you tried that new build?
Click to expand...
Click to collapse
Nope. I will give that a shot.
Thanks flashing it now and putting the phone back in the drawer, its my backup phone now that I got an S6. I do get it out time to time to play with it and see what's new lol
I did the ROM INSTALL WIPE. I ran the installer twice one saying NO after the reboot prompt and one saying yes. In both instances I did not have root and busybox was not installed.
fbarcenas said:
I did the ROM INSTALL WIPE. I ran the installer twice one saying NO after the reboot prompt and one saying yes. In both instances I did not have root and busybox was not installed.
Click to expand...
Click to collapse
Did you try it with the new upload? Version 1.1?
rwilco12 said:
Did you try it with the new upload? Version 1.1?
Click to expand...
Click to collapse
Yeah That is what I was talking about. V1 installs busybox and supersu, but does not give root. V1.1 does not install busybox, nor does it give root.
I'm tempted to revert to pure stock and use the SKIPSOFT UNIFIED ANDROID TOOLKIT to acquire root and make my own ROM distro. Nothing seems to be working right with these ROM. How are you testing your ROMs before deployment? Are you doing a full nandroid backup of your phone and a full wipe before testing these? Or are we the guinea pigs?
---------- Post added at 06:21 PM ---------- Previous post was at 06:13 PM ----------
I would like to suggest that you publish the MD5 hash of your file next to the download link, so the we can verify that we have a good copy and that the downloaded file is not corrupt.
fbarcenas said:
Yeah That is what I was talking about. V1 installs busybox and supersu, but does not give root. V1.1 does not install busybox, nor does it give root.
I'm tempted to revert to pure stock and use the SKIPSOFT UNIFIED ANDROID TOOLKIT to acquire root and make my own ROM distro. Nothing seems to be working right with these ROM. How are you testing your ROMs before deployment? Are you doing a full nandroid backup of your phone and a full wipe before testing these? Or are we the guinea pigs?
---------- Post added at 06:21 PM ---------- Previous post was at 06:13 PM ----------
I would like to suggest that you publish the MD5 hash of your file next to the download link, so the we can verify that we have a good copy and that the downloaded file is not corrupt.
Click to expand...
Click to collapse
You're definitely not the guinea pigs.
When I do my testing I will revert back to a 100% stock ROM by flashing one of my one-click Odin packages and then flash recovery. I then flash the ROM and test it out. While doing the testing I don't actually make a Nandroid, all I do is a TB backup that is then moved to my PC to avoid any cross contamination. I repeat the process a minimum of three times before posting.
To clarify a point - Busybox is installed when you flash the ROM. You don't need the app to install it. The app you normally see is a Busybox Installer. It adds the functionality to the system files the same way the updaterscript can (and in this case does) when flashing a ROM. Busybox is really just a bunch of fancy symlinks that create a "toolbox" in system\bin.
I'm not sure why you are having the issues with root, but myself and several others (I show the ROM has been downloaded 68 times) have had success with it. Where you are continuing to have issues, even with the updated version, I would maybe recommend you hold off on flashing this one and wait either for my Mostly Stock ROM I am working on or for another ROM that you like.
fbarcenas said:
Yeah That is what I was talking about. V1 installs busybox and supersu, but does not give root. V1.1 does not install busybox, nor does it give root.
I'm tempted to revert to pure stock and use the SKIPSOFT UNIFIED ANDROID TOOLKIT to acquire root and make my own ROM distro. [emoji14] Nothing seems to be working right with these ROM. How are you testing your ROMs before deployment? Are you doing a full nandroid backup of your phone and a full wipe before testing these? Or are we the guinea pigs?
---------- Post added at 06:21 PM ---------- Previous post was at 06:13 PM ----------
I would like to suggest that you publish the MD5 hash of your file next to the download link, so the we can verify that we have a good copy and that the downloaded file is not corrupt.
Click to expand...
Click to collapse
The rom works...the idea of an MD5 isn't a bad one, and I'm sure that the OP could add it...the dev provided a pre-rooted, stock rom that works as advertised...it's free for you to avail or no; however, the suggestion that he is deploying the users of this forum as test subjects for his own, untested work is untrue.
You want to not use it? Fine, they don't. You wish to make your own? Please, have at it.
But to come into a man's thread and announce that you'll build your own hewn from a toolkit, then distribute it, because his didn't work for you, when it's working for others, seems unwarranted at best.
#WhiteUIsMustDie, #EndDarkAppOppression
fbarcenas said:
Yeah That is what I was talking about. V1 installs busybox and supersu, but does not give root. V1.1 does not install busybox, nor does it give root.
I'm tempted to revert to pure stock and use the SKIPSOFT UNIFIED ANDROID TOOLKIT to acquire root and make my own ROM distro. Nothing seems to be working right with these ROM. How are you testing your ROMs before deployment? Are you doing a full nandroid backup of your phone and a full wipe before testing these? Or are we the guinea pigs?
---------- Post added at 06:21 PM ---------- Previous post was at 06:13 PM ----------
I would like to suggest that you publish the MD5 hash of your file next to the download link, so the we can verify that we have a good copy and that the downloaded file is not corrupt.
Click to expand...
Click to collapse
micmars said:
The rom works...the idea of an MD5 isn't a bad one, and I'm sure that the OP could add it...the dev provided a pre-rooted, stock rom that works as advertised...it's free for you to avail or no; however, the suggestion that he is using the users of this forum as test subjects for his own, untested work is unwarranted.
You want to not use it? Fine, they don't. You wish to make your own? Please, have at it.
But to come into a man's thread and announce that you'll build your own hewn from a toolkit, then distribute it, because his didn't work for you, when it's working for others, seems unwarranted at best.
#WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
^ I cannot agree more with this. Use it or don't, but do not come into a developers thread and discuss making your own ROM, it's rude, disrespectful and completely unwarranted. Good luck on these forums with an attitude like that...
rwilco12 said:
You're definitely not the guinea pigs.
When I do my testing I will revert back to a 100% stock ROM by flashing one of my one-click Odin packages and then flash recovery. I then flash the ROM and test it out. While doing the testing I don't actually make a Nandroid, all I do is a TB backup that is then moved to my PC to avoid any cross contamination. I repeat the process a minimum of three times before posting.
To clarify a point - Busybox is installed when you flash the ROM. You don't need the app to install it. The app you normally see is a Busybox Installer. It adds the functionality to the system files the same way the updaterscript can (and in this case does) when flashing a ROM. Busybox is really just a bunch of fancy symlinks that create a "toolbox" in system\bin.
I'm not sure why you are having the issues with root, but myself and several others (I show the ROM has been downloaded 68 times) have had success with it. Where you are continuing to have issues, even with the updated version, I would maybe recommend you hold off on flashing this one and wait either for my Mostly Stock ROM I am working on or for another ROM that you like.
Click to expand...
Click to collapse
Thanks I got desperate and reverted to stock and rooted it with the Unified Android Tookit, and ran the D bloat script. I just couldn't wait any longer. Thank you for your hard work and patience anyways.
And to all the haters.
Does this have all the boatware?
Sent from my SM-G900P using XDA Free mobile app
Related
Following the instructions here - http://forum.xda-developers.com/showthread.php?t=2737497 - I managed to successfully install and use CM 11 on my old HTC Aria. And except for the lack of space, it works beautifully.
(The CyanogenMod version installed on my phone is currently 11-20140614-EXPERIMENTAL-liberty ).
I decided to check for updates and got a notification that a new update was available. I downloaded it through the updater. But when I tried to install it, the installation stopped after the progress bar moved to maybe around 15-20% with the message - "Signature verification failed". I thought maybe the updater messed up the file and downloaded and transferred the file to the phone from my computer and manually tried to install it. But it again failed with the same error. (I downloaded the latest nightly build - cm-11-20140724-NIGHTLY-liberty.zip - from http://download.androidarmv6.org/_builds/liberty/ )
Is it an issue with the build or am I doing something wrong?
Yes I think it's an issue, read this http://forum.xda-developers.com/showpost.php?p=54339665&postcount=53
Djon_ said:
Yes I think it's an issue, read this http://forum.xda-developers.com/showpost.php?p=54339665&postcount=53
Click to expand...
Click to collapse
Thanks for bringing that to my attention. I did try downloading directly from the website and updating, but got the same error.
I've actually found that you can install nightly builds from androidarmv6/_builds/liberty by using the recovery-liberty.img located there, but that recovery will not allow you to install gapps - but you CAN "downgrade" that version of cwm back to 6.0.2.8 in order to install gapps.
System is a little flaky, and it looks like some things have been broken in the nightlies....
---------- Post added at 10:32 AM ---------- Previous post was at 10:24 AM ----------
Sorry, realizing my last post isn't very clear. Basically put, it seems as if the nightlies require the current version of CWM in order to install correctly, whereas gapps requires an older version (6.0.2.8) to install.
I have no idea what the implications of this are, and as I said above, you can change out CWM versions to make it work, but I'm guessing that is going to cause some issues down the line....
PrplHaz4 said:
I've actually found that you can install nightly builds from androidarmv6/_builds/liberty by using the recovery-liberty.img located there, but that recovery will not allow you to install gapps - but you CAN "downgrade" that version of cwm back to 6.0.2.8 in order to install gapps.
System is a little flaky, and it looks like some things have been broken in the nightlies....
---------- Post added at 10:32 AM ---------- Previous post was at 10:24 AM ----------
Sorry, realizing my last post isn't very clear. Basically put, it seems as if the nightlies require the current version of CWM in order to install correctly, whereas gapps requires an older version (6.0.2.8) to install.
I have no idea what the implications of this are, and as I said above, you can change out CWM versions to make it work, but I'm guessing that is going to cause some issues down the line....
Click to expand...
Click to collapse
Here's some more clarification from Winsuk on the recovery versions:
http://forum.xda-developers.com/showpost.php?p=55268492&postcount=66
I haven't gotten around to updating the OP with a recovery, mostly because it still has some bugs and changes I don't like.
Click to expand...
Click to collapse
Hi Guys,
I have an HTC M8 International (Australia), and I was attempting to Root and S-Off my device to allow me to install the GPE Rom. Following a tutorial I found on XDA, I was able to root, and install the InsertCoin Rom, but it wouldn't allow me to run Firewater as my device is too new.
It also seems that because I am running InsertCoin, I cannot run SunShine as it doesn't recognise it as a stock ROM.
I realise I shouldn't have mucked around with it unless I knew exactly what I was doing, but I thought the tutorial would have held me in good stead.
Stupidity aside, can anyone help me get my M8 back to stock. As it stands, I now have no Wi-Fi, and charging is sporadical, needing to have permissions reset through TWRP every time I connect to USB.
I am running a Mac, and have TWRP installed on my device. Happy to provide any more information needed, I would just love someone to be able to help get my phone back into a working state!
Any way you can get a stock backup on your phone would be ideal. I know with the ATT variant I found a posted stock zip I had to extract and place in my TWRP backup folder.it can be as simple as that unless you made a stock backup than restore it and run Sunshine again
Below is a link to most all backups
Just fallow the instructions.
http://forum.xda-developers.com/showthread.php?t=2701376
jball said:
Any way you can get a stock backup on your phone would be ideal. I know with the ATT variant I found a posted stock zip I had to extract and place in my TWRP backup folder.it can be as simple as that unless you made a stock backup than restore it and run Sunshine again
Below is a link to most all backups
Just fallow the instructions.
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
I have a friend who is in the same situation. These posts should be cleaned up and made easier to understand/comprehend. I am a systems engineer responsible for XaaS integration and code heavily in Ruby and Python and even these instruction seem complicated to me.....
jball said:
Any way you can get a stock backup on your phone would be ideal. I know with the ATT variant I found a posted stock zip I had to extract and place in my TWRP backup folder.it can be as simple as that unless you made a stock backup than restore it and run Sunshine again
Below is a link to most all backups
Just fallow the instructions.
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Unfortunately, there doesn't seem to be a recovery available for my version (2.23.841.1). If I download a copy of the stock rom from Android Revolution, would I be able to flash it through TWRP, or would it still require S-Off?
ngerasimatos said:
I have a friend who is in the same situation. These posts should be cleaned up and made easier to understand/comprehend. I am a systems engineer responsible for XaaS integration and code heavily in Ruby and Python and even these instruction seem complicated to me.....
Click to expand...
Click to collapse
It's HTC for you man.I find it fun
---------- Post added at 01:34 AM ---------- Previous post was at 01:32 AM ----------
drewcaddy said:
Unfortunately, there doesn't seem to be a recovery available for my version (2.23.841.1). If I download a copy of the stock rom from Android Revolution, would I be able to flash it through TWRP, or would it still require S-Off?
Click to expand...
Click to collapse
If it states that the stock ROM can be installed using TWRP than I would think you could.I'm at work so I can't research it right now
jball said:
It's HTC for you man.I find it fun
---------- Post added at 01:34 AM ---------- Previous post was at 01:32 AM ----------
If it states that the stock ROM can be installed using TWRP than I would think you could.I'm at work so I can't research it right now
Click to expand...
Click to collapse
My mistake - it wasn't a stock ROM, only based upon one. Through a lot of playing around and flashing, I have managed to get a functioning device back up and running. I flashed with Android Revolution ROM, and that allowed me to install SunShine to gain S-Off. Also had to re-flash the firmware, as it knocked out my Wi-Fi. Following these steps was really helpful:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
For now, it's running well. I used to have a Samsung S5, and I don't recall there being as many issues as this, but it's all a learning curve
drewcaddy said:
My mistake - it wasn't a stock ROM, only based upon one. Through a lot of playing around and flashing, I have managed to get a functioning device back up and running. I flashed with Android Revolution ROM, and that allowed me to install SunShine to gain S-Off. Also had to re-flash the firmware, as it knocked out my Wi-Fi. Following these steps was really helpful:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
For now, it's running well. I used to have a Samsung S5, and I don't recall there being as many issues as this, but it's all a learning curve
Click to expand...
Click to collapse
I to have had Samsung S2,S2 Skyrocket,S4,S4 Active and the easiest of them all was my beloved Nexus 5 .now I will say it's definitely a bit more to stay on top of but is a good challenge [emoji122]
A friend of mibe wanted me to update my phone so i could have advanced calling. But its an update and do notwont to risk losing root and recovery or worst face brick. I would love to have this update so im hoping is there a work around. Is there a way to root the phone again if it does wipe it out. Is there a way to download it and have my custom recovery install it. Please and thank you
If you're already on 12b, you already have advanced calling. Otherwise, go here
http://forum.xda-developers.com/showthread.php?p=57360121
It's like the second sticky down in the general section. Read, read, and read again before attempting to update your G3. Although it's pretty easy to fix if you mess something up, it's also pretty easy to softbrick.
Sent from my VS985 4G using Tapatalk 2
Johneedoe said:
If you're already on 12b, you already have advanced calling. Otherwise, go here
http://forum.xda-developers.com/showthread.php?p=57360121
It's like the second sticky down in the general section. Read, read, and read again before attempting to update your G3. Although it's pretty easy to fix if you mess something up, it's also pretty easy to softbrick.
Sent from my VS985 4G using Tapatalk 2
Click to expand...
Click to collapse
I hope i did the quote right. I got more info to what i have this is whati have
Hope u see the pic
LASERWOLF452 said:
I hope i did the quote right. I got more info to what i have this is whati have
Hope u see the pic
Click to expand...
Click to collapse
The number at the end of the build number is 10B. You need to be on 12B or higher in order to use Advanced Calling. Also would have to enable it on your Verizon account. MIght be under "HD Calling".
roirraW "edor" ehT said:
The number at the end of the build number is 10B. You need to be on 12B or higher in order to use Advanced Calling. Also would have to enable it on your Verizon account. MIght be under "HD Calling".
Click to expand...
Click to collapse
Thanks but one thing. I hate to sound like a noob but doing this ive never done before. Is there a guide that can walk me threw it to get to 12b
LASERWOLF452 said:
Thanks but one thing. I hate to sound like a noob but doing this ive never done before. Is there a guide that can walk me threw it to get to 12b
Click to expand...
Click to collapse
If you're wanting to be rooted and update to 12B...
1. Root using Stump apk brute force method. Reboot.
2. Install SuperSU from Play Store, reboot, launch SuperSU, update binary, reboot again.
3. Install TWRP Manager from the Play Store, launch it and grant it root permissions.
4. Use TWRP Manager's option in the upper right corner to download and install the latest TWRP custom recovery for the VS985. It's already bump'd, I've verified.
5. Use the link @Johneedoe provided, download the 12B boot, modem and system.img files. Extract system.img from the system.zip.
6. There's a link in that first post, after all the download links to @autoprime 's Flash2 method. Use that through TWRP with the 12B img files you downloaded.
Sent from my VK810 4G
You can just take the OTA to 11c and then 12b. You won't lose root on the way.
siriusgamer said:
You can just take the OTA to 11c and then 12b. You won't lose root on the way.
Click to expand...
Click to collapse
he has custom recovery installed. do not take ota's or it will not boot until you flush the fota folder, and the ota wont install.
bweN diorD said:
he has custom recovery installed. do not take ota's or it will not boot until you flush the fota folder, and the ota wont install.
Click to expand...
Click to collapse
Thanks for letting them know. I was already told not to update with custom recovery by a friend. I have not done the update a friend is going to help me threw it cause i dont wont to take a chance and mess it up if i cone access sonthing i dont u derstand. Im more in learning stages of rooting. And new with ota updates as im new to that lol
update failed. need help to 12b
Me and my friend was working on my phone but we had an issue.
I'm running twrp latest version, and we followed this post as is
http://forum.xda-developers.com/showpost.php?p=56100153&postcount=1
And I,ended up with an error . all,passes and succeeds but I get
E: Unable to mount ' /system'
just wanted to put this but i found my error, i had no computer at the time and was using on my cellphone to extract the files, i got my laptop fixed and was able to get 12b installed thanks for the help
bweN diorD said:
he has custom recovery installed. do not take ota's or it will not boot until you flush the fota folder, and the ota wont install.
Click to expand...
Click to collapse
so.. i've made this mistake. where can i find info on flushing the fota folder? and the steps to take after that..? plz and thank you in advance
killerskincanoe said:
so.. i've made this mistake. where can i find info on flushing the fota folder? and the steps to take after that..? plz and thank you in advance
Click to expand...
Click to collapse
I'm not in a position to grab the link right now. Check my Reference post in general, or look for the original post by autoprime. It's a twrp flashable zip.
Sent from my N6
Ok, ive bricked and started fresh all over again, the problems with the file rhat im suppose to rename and take out the number, well when i down loaded that file it reads system 12B rar. If i change the name i brick, if i leave it as is i get error on system dwnload??, 1st two times was an error, 3rd time i changed the name and bricked it. Took me 3 hrs to get back to 19b,little help here!!!
Sent from my VS985 4G using XDA-Developers mobile app
jlb1959.01 said:
Ok, ive bricked and started fresh all over again, the problems with the file rhat im suppose to rename and take out the number, well when i down loaded that file it reads system 12B rar. If i change the name i brick, if i leave it as is i get error on system dwnload??, 1st two times was an error, 3rd time i changed the name and bricked it. Took me 3 hrs to get back to 19b,little help here!!!
Click to expand...
Click to collapse
I'm not positive what you want your end result to be, but if you want root and TWRP on any version of the stock ROM, the easiest method is to use the built in LG Backup to backup your user apps, user data and limited system data to your MicroSD card, move anything else you want to keep from your internal storage, flash the 10B TOT using the .DLL that's extracted from the 35B KDZ, root using the Stump app on XDA, put TWRP on with TWRP Manager from the Play Store, reboot to TWRP, wipe Cache, Dalvik/ART and Data, flash whatever ROM you want and appropriate Bootstack. Bootstacks are in @xdabbeb 's VS985 v2.0 ROM thread in the Development (non-original) section. 12B Bootstack for KitKat, 24B for Lollipop 5.0.x and 35B for Lollipop 5.1.x and Marshmallow 6.0.
If you flashed a stock-based ROM, then you can use the built-in LG Backup to restore your backup from previously. Not much, if any (depending on what version of the stock ROM you come from, and what you flash) system data will be restored.
Sorry road warrior, you helped me a ton, don't know if you remember me, I had 5.1 but did an Ota to 6.0, I wanted to start fresh do I followed you and laser wolf, I downgraded to 10b,now when trying to follow laser wolf a
---------- Post added at 05:08 PM ---------- Previous post was at 05:02 PM ----------
Sorry got cut off on the above, so when I downloaded the files and made flash folder for the files, on flash it came up error on system imaging, that's file read system 12B rar now when I changed the name by removing the number, as directed, I bricked on flashing. So it has to do with that file.??im at a loss. I thank you a ton for the downgrade to 10b tho.
---------- Post added at 05:09 PM ---------- Previous post was at 05:08 PM ----------
And yes I'm rooted etc as direct with your downgrade.
---------- Post added at 05:13 PM ---------- Previous post was at 05:09 PM ----------
I have since unbridled by returning to stock, which is 10b again. Just don't want to mess up again, so trying to figure out why that system file(System12B rar) cannot or will not work. If left alone, that files flashes as an error, if I change the name, by taking out the number(12B) it bricks.
Correct spell is killing me, after I bricked trying to flash I dug around xda and managed to replace to 10b exactly like laser wolf has in this post(his picture matches my phone exactly), my problem now is not the zipped files, the other files are the problem, there all suppose to go into a file named flash, however on the download the system file had system12b. rar... According to the direction it should read system12b I'm, and directions say rename to system.img,,thats what I changed the name of the file to and it bricked, if I leave it as downloaded it flashes error on system img, I don't want to trial and error as I'm new to flashing files etc. Was wandering if anyone else downloads those files and gets a file named system12b. rar instead of system12b. img , and if so what am I suppose to do. Again sorry roadway warrior for not posting in the proper place, however this was where people were trying to go from 10b to 12b...ang help is appreciated!!!!
I didn't read all that. Sorry. I guess I don't understand what the purpose of a 12B rar is. If you want to be on 12B, root and put TWRP on 10B, then wipe and flash a 12B-based ROM like JasmineROM I think v2 or v3, or SkyDragon - probably the same, v2 or so.
By your description it sounds like this is some more difficult method.
Ok, thanks mate, been driving me crazy because that particular file means changing the name etc, but I will try your way.... Greatly appreciated my friend... Thanx
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
Dang it, where will I find those rooms?, under your work??
Update, [email protected] guided thru the process step by step, much thanks to [email protected] and a special thanks to roadwarrior, used your method and guidance from laserwolf452, thanks guys I'm now on 12b and rooted
Mods delete.
Unfortunately this won't happen. Had alot of trouble compiling the rom and deciding to sell it. Not much going on for my particular model anyway (G530T) and no guarantee the rom would work for other devices anyway.
On to the next one. Sorry guys and good luck
whats the catch? we need one to start custom roms and stuff.. and would it work for an SM-S920l Grand Prime?
I just want a custom recovery for the SM-S920L. I did manage to get adb shell working on the stock recovery but haven't figured out how to get an insecure adb binary to be picked up and used so no root.
xSpartacusx said:
whats the catch? we need one to start custom roms and stuff.. and would it work for an SM-S920l Grand Prime?
Click to expand...
Click to collapse
Not sure what you mean by "catch". In theory, the software should be the same for all Galaxy Grand Prime models? This is the only thing I would be modifying. I understand the kernel/baseband is different between devices (whether through reason of network, region or chipset variences) but the base software should be almost exactly the same across devices and therefore no kernels or basebands would be altered. I would obviously need willing participants to test on their personal devices throughout the development process and be able to provide logs and feedback on bug reports, but as this is supposed to only modify the software and applications I can't really forsee many issues.
That being said, I only own the 530T variant of the Grand Prime and cannot guarantee that EVERY model will accept the rom upon initial release. My team and I will valiantly make every effort to support as many Primes as possible so long as appropriate feedback from the community is gathered.
As I mentioned in the OP, I can just as well provide a tutorial of sorts to guide users along the path to modifying their device on their own. If a full blown rom isn't of much interest since all of the modifications can be done at will, we won't bother. We only look to simplify the process and hope to gain a reputation for doing so
bfoos said:
I just want a custom recovery for the SM-S920L. I did manage to get adb shell working on the stock recovery but haven't figured out how to get an insecure adb binary to be picked up and used so no root.
Click to expand...
Click to collapse
Unfortunate as flashing a custom rom (be it modified stock or otherwise) would require both root and a custom recovery. One of our members has experience building and porting recoveries, but only to devices they have had on hand
My device is rooted, I'm speaking of getting adb root working on the stock recovery which only supports adb sideload. I did manage to get adb shell working, but like I said, if I try and replace the stock adbd binary with an insecure version, the recovery won't pick it up.
by catch, i mean will it cost us anything to get it? etc. etc. and can i contribute to the developement of my grand prime? of like a stock rom or whatever..?
yes please!!!!
xSpartacusx said:
by catch, i mean will it cost us anything to get it? etc. etc. and can i contribute to the developement of my grand prime? of like a stock rom or whatever..?
Click to expand...
Click to collapse
This development is entirely on our own time with our own resources. We will never openly ask for money to make something happen. This is a passion, not a business prospect. We do this because we want to. If you'd like to support to the cause by means of monetary or physical device donations so that we may continue to expand our list of supported devices, we won't say no. It's of your own will to do so
i dont have money to send nor a device to give.. would giving you my kernel help in any way to make a stock rom for SM-S920l? or a stock recovery?
xSpartacusx said:
i dont have money to send nor a device to give.. would giving you my kernel help in any way to make a stock rom for SM-S920l? or a stock recovery?
Click to expand...
Click to collapse
It wouldn't hurt. It would also be useful to have something like a TWRP/CWM backup of ONLY the stock system, kernel, data partitions and stock recovery of as many variants as possible so we can ensure support for specific models where needed, provided you have the means to do so (root and custom recovery obviously). This would require a factory reset of your device or an Odin restore. We don't want or need any personal information you have on your phone. It's absolutely imperative that we get a fresh untouched image of the device. Its kind of a backdoor way of getting the information we need pertaining to each device, but obviously it does require some sort of recovery to get even that far. I can attempt to build from my current personal setup and that would allow feedback from others on the stability of flashing and report any and all issues.
Sound complicated? You have no idea lol
bfoos said:
My device is rooted, I'm speaking of getting adb root working on the stock recovery which only supports adb sideload. I did manage to get adb shell working, but like I said, if I try and replace the stock adbd binary with an insecure version, the recovery won't pick it up.
Click to expand...
Click to collapse
I personally don't have much experience in recovery modifications or obtaining such permissions from them but we do have a team member who may. How far his knowledge extends into the subject is beyond me. I just build the roms and do most of the PR stuff on the forums
dragonhart6505 said:
It wouldn't hurt. It would also be useful to have something like a TWRP/CWM backup of ONLY the stock system, kernel, data partitions and stock recovery of as many variants as possible so we can ensure support for specific models where needed, provided you have the means to do so (root and custom recovery obviously). This would require a factory reset of your device or an Odin restore. We don't want or need any personal information you have on your phone. It's absolutely imperative that we get a fresh untouched image of the device. Its kind of a backdoor way of getting the information we need pertaining to each device, but obviously it does require some sort of recovery to get even that far. I can attempt to build from my current personal setup and that would allow feedback from others on the stability of flashing and report any and all issues.
Sound complicated? You have no idea lol
Click to expand...
Click to collapse
ok um TWRP doesnt support the grand prime,, only the grand prime VE, which is completely different, and the CWM doesnt support the grand prime at all, either variants. i tried downloading odin.. and it wouldnt work (likeit wouldnt install)
but heres my kernel: https://www.dropbox.com/s/pv96mgsp9uqgo27/kernel-from-24-11-2015-4-18.img?dl=0
and STock recovery..: https://www.dropbox.com/s/hmdgsot6x6aybcl/stock recovery.img?dl=0
and if im wrong about the suppot for this device on either of those, please tell me and show me how to get a custom recovery from them...
xSpartacusx said:
ok um TWRP doesnt support the grand prime,, only the grand prime VE, which is completely different, and the CWM doesnt support the grand prime at all, either variants. i tried downloading odin.. and it wouldnt work (likeit wouldnt install)
but heres my kernel: https://www.dropbox.com/s/pv96mgsp9uqgo27/kernel-from-24-11-2015-4-18.img?dl=0
and STock recovery..: https://www.dropbox.com/s/hmdgsot6x6aybcl/stock recovery.img?dl=0
and if im wrong about the suppot for this device on either of those, please tell me and show me how to get a custom recovery from them...
Click to expand...
Click to collapse
Doesn't support the Grand Prime at all? I've flashed both CWM and TWRP with no issues. I have currently TWRP installed on my device (530T) but I'm not entirely sure it will support your device. It's not my development so no guarantees
Here's the thread I used:
http://forum.xda-developers.com/grand-prime/development/custom-recovery-twrp-2-8-7-0for-lollipop-t3190351
It says only for 530H, I know. But have you tried? I used RASHR from the Play Store to get it on mine. RASHR will also allow you to backup your current recovery in case the flash doesn't take. I recommend doing that first
dragonhart6505 said:
Doesn't support the Grand Prime at all? I've flashed both CWM and TWRP with no issues. I have currently TWRP installed on my device (530T) but I'm not entirely sure it will support your device. It's not my development so no guarantees
Here's the thread I used:
http://forum.xda-developers.com/grand-prime/development/custom-recovery-twrp-2-8-7-0for-lollipop-t3190351
It says only for 530H, I know. But have you tried? I used RASHR from the Play Store to get it on mine. RASHR will also allow you to backup your current recovery in case the flash doesn't take. I recommend doing that first
Click to expand...
Click to collapse
i used rashr to get those two files but i got rom manager by CWM and TWRP manager and both didnt have the normal grand prime in them
xSpartacusx said:
i used rashr to get those two files but i got rom manager by CWM and TWRP manager and both didnt have the normal grand prime in them
Click to expand...
Click to collapse
It won't because its not "officially" supported. But neither is my 530T and I got off just fine. Try to flash the file in RASHR from the thread I linked. If it doesn't take, you've got your backup so no harm no foul
ok so i extracted the tar file using 7zip, and moved the img file into my SD card storage. i used flashify and i opened it up and cicked flash and it said successfully flashed.. and i rebooted and the phone works completely fine.. now what?
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
wait wait wait no, it doesnt.. i did it again and hitreboot, and it says Custom Binary Blocked by reactivation lock.?
---------- Post added at 06:04 AM ---------- Previous post was at 06:01 AM ----------
help?
xSpartacusx said:
ok so i extracted the tar file using 7zip, and moved the img file into my SD card storage. i used flashify and i opened it up and cicked flash and it said successfully flashed.. and i rebooted and the phone works completely fine.. now what?
Click to expand...
Click to collapse
Have you booted into the custom recovery or did you simply reboot the phone back to the system? I ask because Flashify also told me it was successful but in reality did nothing. That's why I suggested RASHR. Flashify is hit or miss in my experience
idfk what i did.. i hit chhoose file, selected the img it says successful and i hit the reboot option it gave me, and then that came up... i never rooted a phone before i never de any flashing **** before..
---------- Post added at 06:07 AM ---------- Previous post was at 06:06 AM ----------
it says custom binary blocked by reactivation lock with a big yellow triangle on the screen
xSpartacusx said:
ok so i extracted the tar file using 7zip, and moved the img file into my SD card storage. i used flashify and i opened it up and cicked flash and it said successfully flashed.. and i rebooted and the phone works completely fine.. now what?
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
wait wait wait no, it doesnt.. i did it again and hitreboot, and it says Custom Binary Blocked by reactivation lock.?
---------- Post added at 06:04 AM ---------- Previous post was at 06:01 AM ----------
help?
Click to expand...
Click to collapse
Try booting into download mode (vol - home and power) then select no (vol -) and should boot you into the OS?
I didn't think this warranted a development thread at this point, Mods may disagree and move it. Since a few people, myself included, need some TouchWiz features and want something closer to a stock rom than Jasmine but debloated, deodexed with the Verizon wifi tether provisioning disabled, I threw this together. I'll try to answer any questions and fix any issues that pop up but I cant make any promises due to work and other projects. If I do move forward with anything I may try to port the stock Verizon Note 4/5, but that's getting ahead of myself.
Now the usual warning about your warranty being voided (as if any Note 3s are under warranty and you didn't void it rooting/flashing recovery) and me not being responsible for you bricking your device because I was stoned when I packaged this.
Download the rom here.
So far the only changes to the stock OF1 are:
Deodexed
Moderatly debloated
Wifi tether provisioning disabled
Start up sound disabled
Rooted*
Busybox added*
*SuperSu and Busybox packages are installed during rom installation.
A list of debloated files can be found here.
Coming soon
Some files were left because they are too integrated into TouchWiz. I don't want people confused by orphaned menu items or get FCs. Some stuff I left because people I know use them. If you want anything back you'll have to get it yourself for now, sorry. I'm open to suggestions on stuff to keep and stuff to remove, but I'll want a good description of their functions before I remove anything. I'm funny about not deleting stuff I don't know what it does.
For those looking for Xposed, I'm using the latest Snapdragon requestConcurrentGC version from here.
Flashing instructions are pretty simple. Boot to TWRP, make a backup, wipe system/data/dalvik/cache, flash the rom and reboot system.
All thanks go to the Yemen rooters and @beaups and @ryanbg for liberating our devices.
thanks i tried it out and its working great! however one of the apps i like is S-Note and you debloated it :/ along with galaxy store. which i cannot find a download source for either, and its needed to reinstall s-note. anyway its a crucial app for the S-pen launcher and s-pen features.
if you could share the apks or upload a full but deodexed superSu/busybox version of this Rom it'd be a real winner.
also im not sure if its just me but i noticed the task manager is a little strange and is missing the ram clear button. ill take a screen shot and upload later
doombuger said:
if you could share the apks or upload a full but deodexed superSu/busybox version of this Rom it'd be a real winner.
Click to expand...
Click to collapse
All of the stock apps are in the system.img files in the Stock Odin tar bundles (available from sammobile.com for instance)
The only trick to getting them out of there is that those (system.img) image files are "sparse" ext4 files. The Android development environment has a tool called "simg2img" which allows you to create an uncompressed image file, which can then be mounted as an ext4 filesytem (loopback mount), and you can browse through there and copy out anything you want.
All of this is more convenient to do in a Linux environment (get yourself VirtualBox and install Ubuntu), but there are workarounds using Windows too, and there are even tutorials here on XDA on how to do this both ways. (Use searches for "sparse image" or "simg2img")
An even easier way is to simply pull them out of TWRP backup files of your rooted-stock ROMs; those "system.ext4.win00x" are just tar files. Heck, you could probably even use 7-zip for that.
You do make backups, right?
Ask your devs to do things that are interesting for the dev and difficult for almost any anybody else to do; not the simple stuff like "go get me some freely available files".
as some people like the stock image, you should do a non-debloated version, like beans did for 4.4.2 NC2/4: http://forum.xda-developers.com/showthread.php?t=2787627 Its just a minor thing, and i can add those apps back in.
How would i enable the startup sound that you disabled?
I'm running the deodexed version of NC4 (with an NC2 bootloader) that i linked above, and finally want to upgrade. I'm assuming that safestrap (which is currently installed) isn't compatible, so do have a link for a version of TWRP that is compatible?
also, can i upgrade from NC4 (with an NC2 bootloader) directly? or is there a step in between that i should do first?
Morlok8k said:
as some people like the stock image, you should do a non-debloated version, like beans did for 4.4.2 NC2/4: http://forum.xda-developers.com/showthread.php?t=2787627 Its just a minor thing, and i can add those apps back in.
How would i enable the startup sound that you disabled?
I'm running the deodexed version of NC4 (with an NC2 bootloader) that i linked above, and finally want to upgrade. I'm assuming that safestrap (which is currently installed) isn't compatible, so do have a link for a version of TWRP that is compatible?
also, can i upgrade from NC4 (with an NC2 bootloader) directly? or is there a step in between that i should do first?
Click to expand...
Click to collapse
i updated to of1 then rooted and bootloader unlocked then used flashify to flash recovery (back up stock recovery if u like) then no more safe strap or worries. but to each their own.
Very cool, thank you!
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
njdan30 said:
i updated to of1 then rooted and bootloader unlocked then used flashify to flash recovery (back up stock recovery if u like) then no more safe strap or worries. but to each their own.
Click to expand...
Click to collapse
How did you bootloader unlock after rooted? Were you able to install custom recovery? If so, do you mind sharing how you did that as well?
Thank you!!
Neo3D said:
Very cool, thank you!
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
How did you bootloader unlock after rooted? Were you able to install custom recovery? If so, do you mind sharing how you did that as well?
Thank you!!
Click to expand...
Click to collapse
yes you need to root 1st in order to get bootloader unlocked then head to play store for flashify the take the 1st(newest recovery)and thats it.check the yemen root http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 for of1 use that then the retail to dev unlock and enjoy,for unlock i did the adb method but think theres a 1 click unlock now also http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Problems with data
I appreciate all of your hard work. I do have a question though. Every single 5.0 and newer rom I have tried I have problems getting my data to work reliably. I get 4G after reboot but as soon as I send/receive a SMS message it reverts to 3g until the next reboot. This was a clean install and I've also tried reinstalling sim, done factory reset, cleared all data, everything under the sun I can think of. Nobody else seems to have this problem. Any ideas? Other than that this is exactly what I'm looking for.
May I ask somebody create a .tar version to use with odin.
I has no custom recovery .
Tried peazip software to convert .zip to .tar but odin always hangs when i use file
Long time first boot. thoght i made a brick Thanks mate
Quick question. I have kit Kat 4.4.2 with safe strap on mine. How would I be able to upgrade to this?
nitroevo said:
Quick question. I have kit Kat 4.4.2 with safe strap on mine. How would I be able to upgrade to this?
Click to expand...
Click to collapse
I am also looking for advice. My Note 3 is in a similar position with NC2 and Baja ROM in the stock slot of safestrap.