Database Info

[Q] Help! Rooted phone with Custom Mode, ROM Manager Bricked

Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!

mortified21 said:
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
Click to expand...
Click to collapse
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.

If you have 4.3 stock firmware you can root and that's it, no custom recovery, no custom rom, kernel, nothing, and just a heads up there are like 10 threads where people don't read and have done what you have, you need to flash the Odin 4.3 image for you phone to work again, never take an ota, enjoy your locked down device now
Sent from my SCH-I535 using XDA Premium 4 mobile app

SlimSnoopOS said:
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
Click to expand...
Click to collapse
Worked perfectly! Thank you so much!

mortified21 said:
Worked perfectly! Thank you so much!
Click to expand...
Click to collapse
My pleasure but all the thanks is owed to ThePagel, make sure to post your success in his thread. The more people that report their success with that method, then the less fear someone else may have in using that should they suffer the same experiences. :victory::good::good:
If you need any updates on the state of TW 4.3 then keep this discussion thread bookmarked.

I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.

AURMEND said:
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
Click to expand...
Click to collapse
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.

buhohitr said:
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
Click to expand...
Click to collapse
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...

AURMEND said:
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
Click to expand...
Click to collapse
Yep! sucks big time!!

Need help un-bricking my soft-bricked GS3

First off, I have a Verizon GS3 (SCH-I535). As of this morning, it was running the new 4.3 standard (no root, no unlocked bootloader, no custom recovery). I didn't like some of the UI changes in 4.3, and since I wanted to try custom ROMs out anyways, I figured now would be as good a time as any.
After doing hours of research, I was able to successfully get my phone rooted and TWRP installed (using the GooManager app). I had the AOKP d2vzw rom (milestone 1) downloaded and on my phone. I then tried to use GooManager to install the ROM. The phone rebooted into download mode, then gave an error message. I think I didn't properly unlock the bootloader.
After that, the phone wouldn't boot to a ROM at all. I've been trying to install stock ROMs using ODIN and was able to get the stock recovery back, but now all I can get to is the stock recovery and the Download Mode. Whenever the phone boots normally, I get the message, "System software not authorized by Verizon Wireless has been found on your phone . . ."
The biggest issue I've had is that it seem like nothing will install properly using ODIN. When trying to flash TWRP, it fails after NAND Write Start!!. When trying to flash a bootloader, it'll give a write/fail after aboot.
At this point, I'll be happy just getting it back to a working ROM. Any help would be appreciated.

WhiteRabbit44 said:
First off, I have a Verizon GS3 (SCH-I535). As of this morning, it was running the new 4.3 standard (no root, no unlocked bootloader, no custom recovery). I didn't like some of the UI changes in 4.3, and since I wanted to try custom ROMs out anyways, I figured now would be as good a time as any.
After doing hours of research, I was able to successfully get my phone rooted and TWRP installed (using the GooManager app). I had the AOKP d2vzw rom (milestone 1) downloaded and on my phone. I then tried to use GooManager to install the ROM. The phone rebooted into download mode, then gave an error message. I think I didn't properly unlock the bootloader.
After that, the phone wouldn't boot to a ROM at all. I've been trying to install stock ROMs using ODIN and was able to get the stock recovery back, but now all I can get to is the stock recovery and the Download Mode. Whenever the phone boots normally, I get the message, "System software not authorized by Verizon Wireless has been found on your phone . . ."
The biggest issue I've had is that it seem like nothing will install properly using ODIN. When trying to flash TWRP, it fails after NAND Write Start!!. When trying to flash a bootloader, it'll give a write/fail after aboot.
At this point, I'll be happy just getting it back to a working ROM. Any help would be appreciated.
Click to expand...
Click to collapse
When you are on 4.3, you can't unlock your phone anymore. That means no AOSP roms, but you can still use custom touchwiz roms based on 4.3. You're softbricked and you have to use this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=2586319
After that completes, you can use this to root.
http://forum.xda-developers.com/showthread.php?t=2565758
Once you're rooted, this is the only recovery you can install, don't flash any other recovery.
http://forum.xda-developers.com/showthread.php?t=2605648
Read up on all the threads, 4.3 is completely different then 4.1 was.
Sent from my SCH-I535 using Tapatalk 2

Extra Info:
With Odin, I have made sure Kies is uninstalled. I've also tried multiple USB cables, including the ones the phone came with, and I've tried almost every USB port on my computer. Whenever Odin fails, it's in the exact same spot every time, which makes me think it's a software issue, not a hardware issue.
EDIT:
I was actually able to get the stock.vzw-root66 ROM installed by Odin without any errors. The phone rebooted immediately, then showed the android robot with the blue spinny thing in his chest, then the phone went back to the same Verizon error message.

BadUsername said:
When you are on 4.3, you can't unlock your phone anymore. That means no AOSP roms, but you can still use custom touchwiz roms based on 4.3. You're softbricked and you have to use this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=2586319
After that completes, you can use this to root.
http://forum.xda-developers.com/showthread.php?t=2565758
Once you're rooted, this is the only recovery you can install, don't flash any other recovery.
http://forum.xda-developers.com/showthread.php?t=2605648
Read up on all the threads, 4.3 is completely different then 4.1 was.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This worked like a charm! Thank you. I admit I am fairly new at all of this and did a ton of research beforehand, but I apparently did not research the differences between 4.1 and 4.3. You saved my butt!

WhiteRabbit44 said:
This worked like a charm! Thank you. I admit I am fairly new at all of this and did a ton of research beforehand, but I apparently did not research the differences between 4.1 and 4.3. You saved my butt!
Click to expand...
Click to collapse
TW 4.3 discussion thread has most info consolidated in one place:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4

[ROM] Tab 3 7.0 SM-T210/R Stock 4.4.2 KitKat Update

This is the stock US KitKat ROM for The Galaxy Tab 3 7" Tablet. Finally found it after a bunch of hassle online, and figured I'd post it here to make things easier for everyone.
When I Odin'd this ROM, it actually upgraded my tablet, and left all my items installed (not guaranteeing this will work the same for everyone else).
Afterwards, I just Odin'd TWRP to reroot using Chainfire's SuperSU (no other Superuser would work) and called it good.
Caution: if you are using a custom ROM, this may not work without reflashing stock 4.1.2 since the 4.4.2 ROM appears to be an update, rather than a full ROM.
Rooted devices and custom kernels that are otherwise stock should be fine.
The cache, and if possible dalvik-cache should be cleared before flashing. Some of those files can sometimes interfere with upgrades.
It might be necessary to pinpoint apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
If that fails, it might be necessary to factory reset the device.
The Stock 4.1.2 ROM for the T210R is available here: http://forum.xda-developers.com/gal...-stock-sm-t210r-4-1-2-jellybean-odin-t2958676
The T210R...XAR file is for the 210R:
https://drive.google.com/open?id=0B2iEgzRTFjrQTmI0ZjRBbWtOajQ&authuser=0
The ITV file is for the T210 (no R)
To download these ROMs, a torrent client is required (such as utorrent).
Anyone who wishes to contribute, please seed if you can after downloading ("Force Starting" the torrent will seed it indefinitely.)

Can I flash this on the SM-T210?

john410 said:
Can I flash this on the SM-T210?
Click to expand...
Click to collapse
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.

Greaper88 said:
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.
Click to expand...
Click to collapse
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?

[email protected] said:
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?
Click to expand...
Click to collapse
I did not have this problem, but I didn't have much on my Tab either. (Some apps don't play well with KitKat upgrades.)
Torrents have multiple segmented hashchecks to make sure you get an uncorrupted download, but it might still be possible. I'm reasonably sure my file is OK since I've used it (can't speak for the non R file though).
Did you clear your cache, and if possible your dalvik cache? I've read that some of those files interfere with upgrades.
If you can pinpoint the apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
Other option would be to try a factory reset and see if that fixes it. (I understand not wanting to do that though.)
One more thing, if your ROM isn't stock, or stock rooted (custom kernel should be ok too), you may have to flash 4.2 before the 4.4 ROM will work on the device.

Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught

void.naught said:
Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught
Click to expand...
Click to collapse
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.

thank you for finding and posting the correct files for this tab

hi i have a galaxy tab kid t2105 rooted, is it possible to install any other rom after 4.1.2?

Greaper88 said:
Rooted devices and custom kernels that are otherwise stock should be fine.
Click to expand...
Click to collapse
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J

ubuntujason said:
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J
Click to expand...
Click to collapse
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.

Greaper88 said:
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.
Click to expand...
Click to collapse
Awesome, thanks!
~J

Could you upload the T210 ITV file? This torrent is going to take 10 hours

No system file
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.

Sorry, m'y post an error

ragnaroksangel said:
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.
Click to expand...
Click to collapse
Are you looking for the Stock Rom?

Darthlord064 said:
Are you looking for the Stock Rom?
Click to expand...
Click to collapse
I am, can you help?

Greaper88 said:
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.
Click to expand...
Click to collapse
For some (unknown) reason, Odin3 nor JOdin3 doesn't seem to work for flashing my Samsung Galaxy Tab3 device. For that reason I tried Heimdall-Frontend, but to make that work you need to extract the content of a stock ROM first.
Anyways, it still didn't lead to get my device into factory reset yet.
But that's another story on which I still have not yet found the answers needed to get the device successfully back into factory reset.
My guess is that the 'system.img' file, of Android 4.4.2, successfully has been loaded from Heimdall-Frontend, yet by going into reboot right away after Heimdall-Frontend releases the connected device, the download may be deleted.
I read that the cause of that may lie in the fact that Android 4.4.2 is only an update and no full ROM.

(ROM) (VZW PORT) 9/17/2015 Stock Rooted 5.1 GPE LMY47O.H9

Stock M8 GPE 5.1 LMY47O.H9 ported for the Verizon variant of the M8​
Modifications made to this ROM are for Verizon network stability, stock boot.img device tree binary was modified to work on CDMA devices, init.d support, selinux permissive and you should not receive any official OTA notifications.
Its recommended to be on the latest Verizon firmware 4.17.605.9
Install: TWRP is recommended
1. Reboot to recovery
2. Wipe/Factory reset if coming from another ROM
3. Flash ROM
4. Reboot
5. Enjoy, First boot will take 5 to 10 minutes
Special notes:
1. If you were using the partition f2fs, you must switch back to ext4 first.
2. Insert Sim when going through the setup wizard. Just hit skip and continue on with the setup.
3. Unknown phone number will show in settings under Sim Status. You can still make and receive calls and your number automatically populates after first reboot.
4. If you have issues with 3g/LTE data hand off, please call Verizon and have them reset/refresh your SIM or signal whatever they do. Maybe even get a new SIM card.
DOWNLOAD:
AFH: https://www.androidfilehost.com/?w=files&flid=39415
Google Drive: https://drive.google.com/open?id=0B_2pYqG5OJVYMkx0bXB4UTRyd00
DevDB: http://forum.xda-developers.com/devdb/project/dl/?id=14457
MD5: d51a76b9c3e0c94e89d48054f4b91a6e
XDA:DevDB Information
Verizon M8 Stock GPE Rom, ROM for the Verizon HTC One (M8)
Contributors
undarated, enewman17
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.17.605.9
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2015-09-17
Created 2015-09-18
Last Updated 2015-09-27

Hey, thanks for porting this over for us!! I've been saying for a while I want pure stock Android. Well, GPE/Nexus, not, you know, AOSP without Google. I like DH's GPE port, but it's got a ton of tweaks and whatnot. I wonder if I will truly enjoy a pure stock experience.
I will test this tomorrow night. Have you had any problems with GPS? Typically, ROMs that are not Sense have a tendency to lose it.

This ROM won't boot on the verizon htc one m8 with latest firmware. I waited twenty minutes to boot. I felt my phone, and it was hot to the core. I turned the phone off and ran another gpe. However, the other worked seamlessly.
I honestly don't understand why this problem happened with my device.
Thank you for this build. I never got the chance to try full stock.

dragontology said:
Hey, thanks for porting this over for us!! I've been saying for a while I want pure stock Android. Well, GPE/Nexus, not, you know, AOSP without Google. I like DH's GPE port, but it's got a ton of tweaks and whatnot. I wonder if I will truly enjoy a pure stock experience.
I will test this tomorrow night. Have you had any problems with GPS? Typically, ROMs that are not Sense have a tendency to lose it.
Click to expand...
Click to collapse
I haven't had any issues with gps dropping out all all. I travel a lot for my job and have been running the same version as posted for the past 5 days straight.
Check out and let me know if you have any issues

Robby_Rimal said:
This ROM won't boot on the verizon htc one m8 with latest firmware. I waited twenty minutes to boot. I felt my phone, and it was hot to the core. I turned the phone off and ran another gpe. However, the other worked seamlessly.
I honestly don't understand why this problem happened with my device.
Thank you for this build. I never got the chance to try full stock.
Click to expand...
Click to collapse
I'm not sure what went wrong. The rom does boot on the Verizon M8. If you check out the screenshots, those are screenshots taken from my phone. The only thing that comes to mind is if you have you have switched to f2fs instead of ext4 which this rom needs. Maybe bad download?!?!? I'm not sure but the rom does boot and run. It does take a while for the rom to boot. It's too early to tell whats going on just yet.

Bootloops on VZW

grislieber said:
Bootloops on VZW
Click to expand...
Click to collapse
What you mean to say is that it bootloops for you. I'm on Verizon as the screenshots clearly show. It takes at least 10 mins before the spinning circles roll into Android and the phone finshes booting. I'm replying to this post by using the same rom.

undarated said:
The only thing that comes to mind is if you have you have switched to f2fs instead of ext4 which this rom needs.
Click to expand...
Click to collapse
Probably be good to point this out in the OP since people using DH's GPE have the ability to use F2FS, albeit his latest release having some issues with it.

whaevr said:
Probably be good to point this out in the OP since people using DH's GPE have the ability to use F2FS, albeit his latest release having some issues with it.
Click to expand...
Click to collapse
undarated said:
What you mean to say is that it bootloops for you. I'm on Verizon as the screenshots clearly show. It takes at least 10 mins before the spinning circles roll into Android and the phone finshes booting. I'm replying to this post by using the same rom.
Click to expand...
Click to collapse
Any chance you might need to be supercid as well, haven't tried to boot this yet but thought I might bring it up as I remember a lot of people were having problems trying to boot DH's lollipop when he first released it because of that.

mattyd3 said:
Any chance you might need to be supercid as well, haven't tried to boot this yet but thought I might bring it up as I remember a lot of people were having problems trying to boot DH's lollipop when he first released it because of that.
Click to expand...
Click to collapse
I didn't supercid myself. I changed everything in the build.prop to match Verizon by removing any other cid and replacing it with our own. I haven't done anything special to get this to boot on my end. I have the usual set of characters. S-off unlocked, bootloader, latest firmware, latest TWRP, and root. Nothing else special at all.
This rom has no mods or anything else that would make it prone to any issues as far as booting up and running on our M8's. It's the same rom the Google put out except with everything needed for Verizon.

There may be some people who are using DH's 5.1 firmware as well which might be causing issues. You recommend being on the 5.0.1 firmware for this, right?
I want to check this out!

Div033 said:
There may be some people who are using DH's 5.1 firmware as well which might be causing issues. You recommend being on the 5.0.1 firmware for this, right?
I want to check this out!
Click to expand...
Click to collapse
I'm using his 5.1 firmware also. I was running his rom prior to porting this over with no issues

Just to clarify, bootloops and endless boot are very different animals. A boot loop loads the Android OS and then reboots automatically, usually instantly. (I once had a bootloop, on another device, that gave me about a minute.) Endless boot means it just doesn't boot. If this is anything like DH's GPE, first boot will take 8 minutes and change. Maybe less as it has fewer apps to optimise for. Legit 20 minutes is endless boot. I'd say to give up after 12-15.
I wonder if maybe using another kernel might work? I don't know what all needs to be changed to get an international ROM to work on an American phone, but I'd guess the kernel would be one of them.
Just speculating as I haven't tried it yet.

Sorry for late response.
But in my case, I have the latest fw for the verizon htc one m8.
I was NOT saying it does not boot on "THE" HTC One M8. I was trying to say it didn't boot on MY phone. Sorry for the confusion.
The Rom would not boot, as dragontology said, I have the endless boot. The phone was hot and wasn't responding. The boot animation was working but was on for about twenty to thirty minutes until I stopped it.
I clean flashed the rom. I am not running digital high's 5.1 firmware.
Please, I hope that I did something wrong because I really want to try stock GPE.
Thank you DEV for your hard work.
EDIT: I am also not supercid.
---------- Post added at 11:45 PM ---------- Previous post was at 11:28 PM ----------
Actually the reported download size exceeds 577mbs. I will try to flash within the next two hours.
Sorry...

Is there any way to get Hotspot working? I have unlimited and need it.
Thanks

Robby_Rimal said:
Sorry for late response.
But in my case, I have the latest fw for the verizon htc one m8.
I was NOT saying it does not boot on "THE" HTC One M8. I was trying to say it didn't boot on MY phone. Sorry for the confusion.
The Rom would not boot, as dragontology said, I have the endless boot. The phone was hot and wasn't responding. The boot animation was working but was on for about twenty to thirty minutes until I stopped it.
I clean flashed the rom. I am not running digital high's 5.1 firmware.
Please, I hope that I did something wrong because I really want to try stock GPE.
Thank you DEV for your hard work.
EDIT: I am also not supercid.
---------- Post added at 11:45 PM ---------- Previous post was at 11:28 PM ----------
Actually the reported download size exceeds 577mbs. I will try to flash within the next two hours.
Sorry...
Click to expand...
Click to collapse
I honestly have no idea why the rom isn't booting for you guys other than whats been mentioned. The kernel is the exact same one that came in the original rom. I didn't change it either. Honestly, when testing the rom before porting it, all I did was make the changes in the build.prop for Verizon. It's actually a straight forward port. It was a lot easier than it was coming for older JTC devices that i ported roms for.
cuban11182 said:
Is there any way to get Hotspot working? I have unlimited and need it.
Thanks
Click to expand...
Click to collapse
Hotspot is already unlocked by default. It is under Settings, More and Tethering & portable hotspot.

Maybe someone who has successfully flashed the rom will chime in. I can't be the only one!!

undarated said:
Maybe someone who has successfully flashed the rom will chime in. I can't be the only one!!
Click to expand...
Click to collapse
I just flashed it successfully this afternoon, still setting things up (I've never had to install xposed on 5.1 before, had to figure it out). VZW, DH's 5.1 firmware (came from his Rom), ext4 everything. First boot took about 6 min and I haven't had a problem yet.
My only question so far is does this come with a camera? Maybe I'm blind. If so, does it work with duo effects?

cntryby429 said:
I just flashed it successfully this afternoon, still setting things up (I've never had to install xposed on 5.1 before, had to figure it out). VZW, DH's 5.1 firmware (came from his Rom), ext4 everything. First boot took about 6 min and I haven't had a problem yet.
My only question so far is does this come with a camera? Maybe I'm blind. If so, does it work with duo effects?
Click to expand...
Click to collapse
Whew, Glad you got it to work brother. Duo camera? Im not sure. there is a camera app. It's the stock google camera. Should be on the bottom right of the launcher. I'll check on duo camera.
UPDATE: Just took a picture and went to edit it. it had the option of HTC photo edit and photos. I picked HTC photo edit and it had the options for UFocus and Dimension Plus under effects. Hope thats what your looking for.

Alright, sorry I just got back. Yes, the Rom booted perfectly. It is running buttery smooth!!! Sorry man...
I never get good downloads with MEGA. It always looks better but does something weird.
Downloaded the second time with Google Drive. This time the Rom flashed.
Hey undarated, don't worry man. This thing works perfectly!

[BS_FREE_Lollipop_5.0_Rom_BOK3_Based]

This is a modified version of @jrkruse stock BOK3 deodexed ROM with all(or most) of the stock BS removed.
This BS_free ROM does not have two different versions like his previous build. I left only the Samsung apps needed for UPSM and HD calling to work.
INSTRUCTIONS:
I've included the links needed if you want to use xposed and Viper4Android. If you chose not to use these features, then skip them in the flashing process.
I personally prefer using safestrap when clean flashing a ROM, but you can use flashfire if you must.
1) WIPE EVERYTHING!
2) Flash No_BS ROM
3) Flash Extra toggles
4) Flash No_Bootloader_Rooting_Tools_For_S5_Lollipop_V3.zip
5) Flash xposed-v75-sdk21-arm-arter97-snapdragon.zip
6) Flash Viper Policy
7) Flash Viper4Android
8) Flash BOK3 Firmware without bootloader
9) After first boot, open up Viper4Android and install the driver. Note: Sometimes it takes 2-3 times before the driver will install.
I have confirmed that @jrkruse 5-way reboot with Safestrap works on this ROM!!! If you want to use it, add it to the end of the flashing list. 5Way_Safestrap_Reboot_PM. As a side note, if you use 4-way reboot in Wanam Xposed, then that feature needs to be disabled for 5-way reboot to work.
The ROM should boot in about 8 minutes. The music app will force close everytime the device reboots, but it does work normally.
Forgive my lack of knowing how to make a build thread, since this is my first one, so I'm still learning lol.
NO_BS_BOK3_ROM_DEODEXED.zip
Update: NO_BS_BOK3_ROM_DEODEXED_V2 is now available. The flashing process is the same. I encountered an intermittent bug with SuperSU beta with some apps. I downgraded to the latest stable SuperSU with the latest app. I updated all other apps and got rid of the bright/ugly Verizon boot animation. The music app has not force closed since I started using this version.
Update: NO_BS_BOK3_ROM_DEODEXED_V3.zip is now available. The flashing process is the same. I updated busybox and removed SBrowser. I also implemented the signature verification fix by @jrkruse, along with default animation scales set to 0.5x.
Update: NO_BS_BOK3_ROM_DEODEXED_V4 is now available. The flashing process is the same. I updated all apps, except for YouTube(xposed purposes). I added the missing VPN apk as well. Let me know if there is any other issues with VPN related settings.
Update: NO_BS_BOK3_ROM_DEODEXED_V5 is now available. The flashing process is the same. I updated all apps. I added the headphone app notification, voicenote, and SPrintSpooler. I don't use voicenote or SPrint, so let me know if there are any issues with these apps.
Note: Don't pay attention to the 1- prefix in front of some of the ROM versions. I prefix all my flashables in my ROM folder with a 1-, 2-, 3-, ect, so that I have them all in order when I flash them instead of having to remember the order every time lol. I forgot to remove those prefixes when I uploaded the ROMs.

I am looking forward in seeing how this Rom is doing.

Question Do i need to install all items list in OP or can i just install first and last as that is all i am needing?

Snoopy679 said:
Question Do i need to install all items list in OP or can i just install first and last as that is all i am needing?
Click to expand...
Click to collapse
First and last will do just fine.

Works like a charm! Just wish someone could get Quick Glance working. I've seen it work in MOAR, but the 3minit mod that's included is a complete turnoff for me.

jjdavis699 said:
Works like a charm! Just wish someone could get Quick Glance working. I've seen it work in MOAR, but the 3minit mod that's included is a complete turnoff for me.
Click to expand...
Click to collapse
Do you mind elaborating on what Quick Glance is? Are you referring to where you wave your hand and it wakes up the display to show notifications?

CVertigo1 said:
Do you mind elaborating on what Quick Glance is? Are you referring to where you wave your hand and it wakes up the display to show notifications?
Click to expand...
Click to collapse
That's the one.

I've used this in the past and I wasn't a big fan, but I didn't spend a lot of time trying to get it properly configured. I only tried it to see what it did. I personally don't like motion features.
http://repo.xposed.info/module/com.dvd.android.xposed.enableambientdisplay

CVertigo1 said:
First and last will do just fine.
Click to expand...
Click to collapse
do i need to do a clean install or just flash over @jrkruse work that i am currently using?
[VZW_Stock Based TW Rom][5.0 Lollipop BOK3 Build Deodexed] by @jrkruse ?

I dirty flashed this over his stock BOK3 and it worked, so you should be good.

CVertigo1 said:
I've used this in the past and I wasn't a big fan, but I didn't spend a lot of time trying to get it properly configured. I only tried it to see what it did. I personally don't like motion features.
http://repo.xposed.info/module/com.dvd.android.xposed.enableambientdisplay
Click to expand...
Click to collapse
I actually tried that already. It's honestly not great. Oh well. Maybe if I could figure out a way to strip 3minit...
I fell in love with motion features when someone stole my moto g and I had to pick up a Lumia 640. Great phone, but not an android

I'm on BS_FREE_BOG5_GOOGLE_V2_Deodexed and just updated with @jkruse New Root Tools For S5 Lollipop V6. Already enabled Lollipop Safestrap Recovery again and Flashed Most Current OG5 Firmware_No_Bootloader and current OG5_Kernel. Can I just use that and wipe everything flash this aside from 3Minit Battery without losing Root?
Sent from my SM-G900V using Tapatalk

Just to be clear, are you asking if you can run this on BOG5 firmware?

CVertigo1 said:
Just to be clear, are you asking if you can run this on BOG5 firmware?
Click to expand...
Click to collapse
No, I mean using the V6 Root Tools instead of the V3 as indicated in your directions...
Also, I'm hoping that with a new install I will regain ability to work with Accessibility Options in Settings.
Idk if it makes a difference but I have Original GS5 Rooted, never taken OTA, always ONLY used XDA sources for ROM/Firmware/Kernels.
Sent from my SM-G900V using Tapatalk

My rooting tools has the newest firmware, I just forgot to change the version number at the end, but it does say no bootloader.
I wish you luck on the accessibility apps. I never use them, so I don't specifically look for them to work.

CVertigo1 said:
My rooting tools has the newest firmware, I just forgot to change the version number at the end, but it does say no bootloader.
I wish you luck on the accessibility apps. I never use them, so I don't specifically look for them to work.
Click to expand...
Click to collapse
Ok but all the same, I'm trying to avoid another 300mb DL if I can. As long as it is the same stuff then that's all I need to know.
Sent from my SM-G900V using Tapatalk

Version 2 is now available in the OP.

Universal BS ROM
i would like to know if this BS rom is able to be used on any S5 Carriers or would you consider it in the near future making this a universal rom for other carriers to please. my wife is a T-mobile person and she love the work that you have done here. and is asking me to ask this question. i thank you in advance for your reply.:good:

Forgive my lack of knowing how to make a build thread, since this is my first one, so I'm still learning lol.
Update: NO_BS_BOK3_ROM_DEODEXED_V2 is now available. The flashing process is the same. I encountered an intermittent bug with SuperSU beta with some apps. I downgraded to the latest stable SuperSU with the latest app. I updated all other apps and got rid of the bright/ugly Verizon boot animation. The music app has not force closed since I started using this version.[/QUOTE]
How did you remove the verizon boot animation? id rather not flash this again cause i just got my stuff all installed.

CVertigo1 said:
Version 2 is now available in the OP.
Click to expand...
Click to collapse
I Flashed it last night with @jkruse's No Bootloader V6 Tools and it worked just fine. I also, noticed that my Accessibility Settings works now and a couple other things were fixed as well. I did have a hard time Restoring Poweramp Music Player - I had to reinstall from Play Store but otherwise seems to be working great!
Sent from my SM-G900V using Tapatalk