i had upgraded my mexi-maxx to lollipop a few months ago and could no longer stand it. outside of being picky with my phone, the GPS didn't work as I had hoped.
i reverted back to kitkat by means of a TWRP backup I had. Had some issues with doing so. some of my images would not work, but a stock on of KK did. could not use any of @ChazzMatt images either; nor factory images as RSD pinged a FAIL. started getting worried, but just about all good now.
the phone now boots directly to bootloader mode and i have to choose 'start' to boot into system.
is there a way to change this? thanks all.
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Semseddin said:
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Click to expand...
Click to collapse
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
snowboardwcu said:
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
Click to expand...
Click to collapse
You need to downgrade to 4.4.4 with stock images except gpt.bin or else, it is normal having issues like you're facing. Lollipop bootloader is meant to work on lollipop system. Anyway, just flash 4.4.4 full images with mfastboot except gpt.bin, then flash your twrp recovery and restore your kitkat nandroid. It will be fine.
I downgraded my xt1225 back in time with the same tutorial and it works fine.
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
snowboardwcu said:
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
Click to expand...
Click to collapse
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Semseddin said:
India firmware is as bogus as a software can get
Click to expand...
Click to collapse
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Semseddin said:
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Click to expand...
Click to collapse
snowboardwcu said:
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Click to expand...
Click to collapse
If you were just running stock LP -- which you say you do not want to do -- then @Semseddin is correct that Brazil and Mexico factory images are better than India. Just because they both have newer updates India was never given.
In my images thread you can see,
Brazil: QUARK_RETBR_5.0.2_LXG22.33-12.13_cid12_subsidy-DEFAULT_CFC.xml.zip
vs
India: QUARK_RETEU_INDIA_5.0.2_LXG22.33-12.11_cid7_subsidy-DEFAULT_CFC.xml.zip
Then, @Jaocagomez has an OTA which takes it to:
OTA to 22.34.16 Brasil Retail Stock Lollipop 5.0.2 /// Blur_Version.22.34.16.quark_retbr.retbr.en.BR.zip
But CM12.1 beats all that by having 5.1.1.
Yes, CM 12.1 (5.1.1) is still using the stock 5.0.2 kernel source -- because Motorola has not yet released 5.1 kernel source they gave to the XT1254 Droid Turbo back at the beginning of July. But it's still 5.1.1 with 5.02 kernel source, NOT 5.0.2. with 5.02 kernel source. It's a vast improvement! Stock 5.0.2 was too laggy for me.
So, for me running CM12.1 (or another 5.1.1 custom ROM) gives me the best of both worlds. I have the latest kernel source/radio that Motorola has released for our phones, while still having 5.1.1.
_________
Now having said all that, my wife and I have two XT1225.
I flashed both to India LP 5.0.2, then flashed CM.
I also re-flashed the India radio and bootloader (5.0.2) found in the CM12.1 op post just to make sure.
I have no problem with GPS. I use GPS every day. But I use TopNTP. See this post:
http://forum.xda-developers.com/showpost.php?p=62320192&postcount=624
_____
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Fixed this issue. See here:
http://forum.xda-developers.com/showpost.php?p=63048064&postcount=696
ChazzMatt said:
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Click to expand...
Click to collapse
Related
I'm currently on rooted 4.4 (19.5.3), and I'm debating whether to flash to 4.4.4 or wait till Android L is released. I'm still on locked bootloader and I'm not in a hurry to unlock it via Sunshine if I'm staying with 4.4. Sunshine is great BTW, unlocked the wife's Moto X with it. But even with her phone, I kept it on 4.4.2 to stay on the older bootloader because the way I understand it, once you upgrade to 4.4.4, you will not be able to downgrade to anything lower. So, my logic is, keep it on 4.4, locked, until the landscape is clear unless there are real compelling reasons to unlock and upgrade now. So that is the question, are there any advantages to upgrading other than security and other small improvements? I've flashed the 4.4.4 radios and it didn't improve my reception at all, if anything, it made it worse! It switches to 3G at the house a lot where it used to stay at 4G but I don't care since I'm on wifi. The only thing I really want is the KK dialer which 4.4.4 does not have. I've also switched to the AOSP email apks which I love. Other little interface changes were applied with GravityBox and other Xposed modules. I'm pretty happy where the phone is, what are you guys' thoughts?
Here is the change log you should weight against; https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/100660
I know the bluetooth issue was enough for me to upgrade, finally fixed that issue. Not sure but don't you have to upgrade to this version before upgrading to the next version, if it is L or not?
Thanks for that link. What was the Bluetooth issue in your case? I've Bluetooth'd to my cars just fine. I don't know if 4.4.4 is an prerequisite for Android L, but I've read that it has a new boot loader that can't be downgraded. So if I felt like trying a JB ROM capable of overclocking, I'm out of luck. Not that I would go that route, I really like KK. Just wished it was closer to stock like the Moto X. Which as Topsnake pointed out is a good reason to unlock boot loader to flash his ROM. LOL. I think the bottom line is, I want to wait so I don't close off doors like the guys that upgraded to 4.4.4 before Sunshine came out did.
Johnny Wong said:
Thanks for that link. What was the Bluetooth issue in your case? I've Bluetooth'd to my cars just fine. I don't know if 4.4.4 is an prerequisite for Android L, but I've read that it has a new boot loader that can't be downgraded. So if I felt like trying a JB ROM capable of overclocking, I'm out of luck. Not that I would go that route, I really like KK. Just wished it was closer to stock like the Moto X. Which as Topsnake pointed out is a good reason to unlock boot loader to flash his ROM. LOL. I think the bottom line is, I want to wait so I don't close off doors like the guys that upgraded to 4.4.4 before Sunshine came out did.
Click to expand...
Click to collapse
Well if you unlock your guaranteed root regardless of any updates
IMHO, I would just hang off updating to 4.4.4. Here's why:
1. If you change your mind, you can unlock the bootloader and that is rarely a negative thing.
2. You can root your phone and flash custom recoveries. Having root permissions gives you unbelievable control and customization. Custom recoveries will definitely save you some unnecessary grief in case you make a mistake. It's very hard to brick your phone with a good recovery like TWRP or CWM.
3. You can flash Android L based ROMS which I'm sure will be coming out soon. ASOP, AOKP and stock unbloated ROMS give your phone a brand new life and a bit more battery life.
You can just unlock your phone's BL and stay in 4.4, just like now...
Johnny Wong said:
Thanks for that link. What was the Bluetooth issue in your case? I've Bluetooth'd to my cars just fine. I don't know if 4.4.4 is an prerequisite for Android L, but I've read that it has a new boot loader that can't be downgraded. So if I felt like trying a JB ROM capable of overclocking, I'm out of luck. Not that I would go that route, I really like KK. Just wished it was closer to stock like the Moto X. Which as Topsnake pointed out is a good reason to unlock boot loader to flash his ROM. LOL. I think the bottom line is, I want to wait so I don't close off doors like the guys that upgraded to 4.4.4 before Sunshine came out did.
Click to expand...
Click to collapse
Yes you are correct, once you move to 4.4.4 you cannot go back due to the new boot-loader not being backwards compatible. My Bluetooth issues were with any Bluetooth device it would constantly blip randomly via my car or anything connected via Bluetooth. Moto pushes out the updates to devices in order (i.e. you have to go from 4.2 to 4.4 to 4.4.4 to L), but if you obtain the update files manually you may be able to skip 4.4.4 and go straight to the next one (if that even is L or not), but that is a big maybe.
General Lollipop Information Thread
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
LastStandingDroid said:
General Lollipop Information Thread
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
Click to expand...
Click to collapse
Can u port soundcamp to s4 ?
i've flashed cf autoroot and it works perfectly
i did a completly downgrade,also bootloader and no issues
Sent from my GT-I9505 using XDA Free mobile app
i have installed official lollipop 5.0.1. If I root my phone, I will be able to flash official updates from samsung in the future? or I won't because of triggered knox
ViPER4Android
I managed to install Viper as system app but problem is How do I Activate it? In Sound settings there is No Music fx, (although it's installed), so I don't have the option switch Viper on, let only see Adapted Sound and in custom profile doesn't select it either. Am I missing something or is it because this update is so terrible
great info Droid! saw this thread in your signature
Revert from LL 5.0.1 to KK 4.4.2 is possible even if you flashed the Bootloader!
Personaly tested and working like charm!
No IMEI lost, no issues soo far found....
re
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Xain47 said:
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Click to expand...
Click to collapse
yeah..they are the same but i don t know if modems are diferent. i think you should not flash i9506 on E330s
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!
Ok,,,,here is my plight...
about 6 months ago my s5 became unusable due to the fact that concrete and GS5's dont play well together...becoming more and more frustrated having to use an older phone (HTC ONE M7) i went ahead and threw caution to the wind and bought a new LCD digitizer for my GS5 and hoped for the best...
replaced my digitizer and VIOLA !! my phone booted and was exactly the same as it was the day before concrete and LCD collided..
after booting it up went in to check everything and all seems well....root was still good,,,just had to upgrade everything and move on..
my problem is that since it has been a while there have been so many changes as far as updates,,ROMs,,and other techniques i need to find out the steps to take and what would be my best plan of attack..
i am on MOAR v2.2 NE5 and when i installed that back when i first got the phone tripped KNOX,,but i dont think that is too much of a concern at this point...or is it ??
i have read alot of things about going to Lollipop but am not sure if i need to do anything except find a Firmware and flash it with Kies or if ODIN is a better way to go....it would be great if i were able to just jump right to MM but i know the chances of that happening are <0....
any help would be appreciated
thank you in advance
Well the latest version for this phone currently is Marshmallow, and there is a great mm n5 rom that is still a work in progress, but i reccomend downloading the full marshmallow restore tar file and using odin to update, then flash recovery, and then a rom of your choosing (currently the n5 rom or a version of cm13). But to flash a lollipop rom download the OK4 lollipop restore file (last version of lollipop 5.0) and do the same process.
hadn't heard much so i went ahead and downloaded an OK4 firmware and flashed with ODIN....works flawlessly setting up now
surprisingly enough,,,it kept all of my settings from MOAR.....hafta say that i am shocked.....gotta love Android
I was running Mokee 7.1.1 just fine on PB1 firmware... which was probably my first mistake. (not 100% sure) as of now
phone is currently G900V Kltevzw bootloader unlocked, TWRP recovery, updated bootloader to PL1 w/SS
I'm having issues getting service when I flash a new rom most of them have no service i've messed with APN settings.
I felt I was a pretty competent user, i've come from flashing and rooting back from the original Moto Droid, I'd like to know what i'm doing wrong
as of now my phone is useless :crying: with no service so i reverted to my S4 lol
I'd appreciate any help and guidance to bring service back to my phone on MM or Nougat firmware which i have been running for a month or so
i don't really know how to help you but I have the same same s5 as your and running mookee 7.1.1 and my cell service still works i dont know if its a problem with the latest update and i have not updated to pl1....so maybe that may give a hint.
bdawwgg said:
I was running Mokee 7.1.1 just fine on PB1 firmware... which was probably my first mistake. (not 100% sure) as of now
phone is currently G900V Kltevzw bootloader unlocked, TWRP recovery, updated bootloader to PL1 w/SS
I'm having issues getting service when I flash a new rom most of them have no service i've messed with APN settings.
I felt I was a pretty competent user, i've come from flashing and rooting back from the original Moto Droid, I'd like to know what i'm doing wrong
as of now my phone is useless :crying: with no service so i reverted to my S4 lol
I'd appreciate any help and guidance to bring service back to my phone on MM or Nougat firmware which i have been running for a month or so
Click to expand...
Click to collapse
I ran across this once.. not from 7.1 (forget what I did actually) .. no spc / min / etc.. Odin flashed back to stock, problem fixed itself.. flashing through TWRP wouldn't do it.. after that had to go through the steps of unlocking bl / etc again.. on CID 15
travioso said:
I ran across this once.. not from 7.1 (forget what I did actually) .. no spc / min / etc.. Odin flashed back to stock, problem fixed itself.. flashing through TWRP wouldn't do it.. after that had to go through the steps of unlocking bl / etc again.. on CID 15
Click to expand...
Click to collapse
Interesting... I may have to set aside some time to do that. What stock version did you flash? Since I'm on PL1 firmware would you think that make a difference as to what stock youre going to?
I'll have to do some more research as to how I should go about flashing stock then unlocking the BL again. Not sure if I can because of my updated bootloader..
I experienced similar issues with my g900v but mine was with texts being severly delayed and crappy service.. but atleast I still had service. I just finally fixed it this morning by completely flashing back to stock (PB1) and rerooting. I used this guide and started at the very beginning: https://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/
Follow it and you should have your problems fixed.
Clayton993 said:
I experienced similar issues with my g900v but mine was with texts being severly delayed and crappy service.. but atleast I still had service. I just finally fixed it this morning by completely flashing back to stock (PB1) and rerooting. I used this guide and started at the very beginning: https://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/
Follow it and you should have your problems fixed.
Click to expand...
Click to collapse
Thanks!!! I'll Slowly start doing this after I post this. Hope to have a good outcome.
If you haven't started yet, I found an easier "how to" here: https://forum.xda-developers.com/ve...ewbies-guide-to-install-pb1-rom-root-t3481826
It includes all the info from the link I posted yesterday but also includes the steps to update to PF4, which I'm about to do right now. Hopefully the delayed text and crap service problems don't return with updating, if so I will post the outcome.
Clayton993 said:
If you haven't started yet, I found an easier "how to" here: https://forum.xda-developers.com/ve...ewbies-guide-to-install-pb1-rom-root-t3481826
It includes all the info from the link I posted yesterday but also includes the steps to update to PF4, which I'm about to do right now. Hopefully the delayed text and crap service problems don't return with updating, if so I will post the outcome.
Click to expand...
Click to collapse
Thanks for that. Just finished that. Gonna look try installing some custom roms. Ideally im looking to use a Nougat rom, but dont mind the MM at all...
What custom roms are you looking into.
bdawwgg said:
Thanks for that. Just finished that. Gonna look try installing some custom roms. Ideally im looking to use a Nougat rom, but dont mind the MM at all...
What custom roms are you looking into.
Click to expand...
Click to collapse
I've already ran a few different roms but haven't really found one I liked enough to stick with. I used Phoenix v15 for a few months then switched to the new 7.1 resurrection remix nougat ROM a few weeks ago. I'll probably go back to nougat unless I start having service issues again. Good luck
I'm still not getting either or one of the two data and cell service. SMS/MMS wont work. Still dont know what is wrong exactly. PF4 updated BL
Not sure if i need to flash a radio or something in odin to get service to work....