Related
Razr HD Maxx on Verizon.
I am rooted, unlocked bootloader, Team Win recovery, stock OS.
3 times I attempted to install the latest update (9.18.79.en.US). Each time it reboots into Team Win recovery. I then reboot the system and once the desktop loads, it reboots immediately into Team Win recovery. I can never get into the OS anymore because it immediately displays "Powering off" and loads the Team Win recovery screen. So, each of the 3 times I attempted to install, I ended up reverting back to my backup.
What am I doing wrong? Do I need to remove Team Win? Is the update not compatible with my current setup? Or, do I need to do it manually? i.e. download the update and install it using Team Win recovery.
Thoughts? Thank you in advance for reading and attempting a resolution. If I end up figuring it out, I'll post an update. :good:
Fix for Reboots
Too Fix Just go on Teamwin Recovery and select wipe Data>Advance Wipe Data> and only wipe cache and dalvik cache..
that should fix y;our reboots..
as for the update.... no sure yet
Your phone has to be stock with all apps in tack to take a ota. So yes you need to be using the stock recovery and preserve and remove root with voodoo.
Sent from my PACMAN MATRIX HD MAXX
thanks to both responses.
quick update: i located the downloaded update via /cache. i attempted to install it when TWRP came up. "Failed". I wiped cache/dalvik, and that did not work either. It fixed the boot problem initially, but then it just prompted for the update again and the reboot cycle repeated. except I was in a factory state with my apps. (i.e. i had to go through the initial prompts of setting up my phone.)
So, I will attempt to do the following:
deeje00 said:
Your phone has to be stock with all apps in tack to take a ota. So yes you need to be using the stock recovery and preserve and remove root with voodoo.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
and see what happens.
Thanks again.
Installing new Razr HD Verizon update
The update must be installed using stock recovery. I did this just today by temp unrooting using voodoo, installing stock recovery using razr hd utility, and then downloading and installing the update, which will boot the phone into the stock recovery to automatically finish the installation after you click install. After the phone reboots, I verified that the update installed, re-rooted using voodoo, and re-installed TWRP using the razr hd utility. After this, all is working well. :good:
I did everything except root recovery with voodoo now I have ota update to 9.18.926 bootloader unlocked but can't get root... Do I have to start over with rsd?
Sent from my DROID RAZR HD using xda app-developers app
Andrewl62 said:
I did everything except root recovery with voodoo now I have ota update to 9.18.926 bootloader unlocked but can't get root... Do I have to start over with rsd?
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
If you still have custom recovery with and unlocked bootloader you should be able to flash the UPDATE-SuperSU-v1.41.zip... If you do not have custom recovery install TWRP/CWM so you can install the zip..
http://forum.xda-developers.com/showthread.php?t=1538053
Mr-Glass said:
If you still have custom recovery with and unlocked bootloader you should be able to flash the UPDATE-SuperSU-v1.41.zip... If you do not have custom recovery install TWRP/CWM so you can install the zip..
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
I have stock recovery on my phone, re-enabled/unfroze all stock apps, temp unrooted with voodoo and it still won't install
Any thoughts?
woodjc01 said:
The update must be installed using stock recovery. I did this just today by temp unrooting using voodoo, installing stock recovery using razr hd utility, and then downloading and installing the update, which will boot the phone into the stock recovery to automatically finish the installation after you click install. After the phone reboots, I verified that the update installed, re-rooted using voodoo, and re-installed TWRP using the razr hd utility. After this, all is working well. :good:
Click to expand...
Click to collapse
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
by3times1minus1 said:
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
Click to expand...
Click to collapse
Your welcome. Glad I could help.
forgot to give an update. i got the update to work with the stock recovery. i'm on newest stock os build with unlocked bootloader, root, and stock recovery. :good:
by3times1minus1 said:
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
Click to expand...
Click to collapse
My dad is getting a message to update to 9.18.x every 24 hours.
Sometimes he accidentally hits the OK/ update button and has to go back in TWRP to wipe cache and dalvik.
So, how does one freeze the Verizon update application? We have unlocked bootloader and running 9.16.x and TWRP installed along with the Voodo thing for securing root.
My update failed to install as well. I'm rooted but NOT unlocked. Can someone point me in the right direction regarding how to restore bloatware apps? I made the rookie mistake of completely removing some of them a while back. I sincerely apologize if a solution has been posted already, as I was not able to find one so far.
s_u_n said:
My dad is getting a message to update to 9.18.x every 24 hours.
Sometimes he accidentally hits the OK/ update button and has to go back in TWRP to wipe cache and dalvik.
So, how does one freeze the Verizon update application? We have unlocked bootloader and running 9.16.x and TWRP installed along with the Voodo thing for securing root.
Click to expand...
Click to collapse
Why do you not want the update? Your bootloader is unlocked so you're safe to go all the way to Kit Kat.
iBolski said:
Why do you not want the update? Your bootloader is unlocked so you're safe to go all the way to Kit Kat.
Click to expand...
Click to collapse
Well, I had asked to hold on till 4.4 is made available and that was supposed to come out in January.
But yesterday I upgraded the phone to 4.4.2 following Samurai's thread on DroidRzr forum.
s_u_n said:
Well, I had asked to hold on till 4.4 is made available and that was supposed to come out in January.
But yesterday I upgraded the phone to 4.4.2 following Samurai's thread on DroidRzr forum.
Click to expand...
Click to collapse
But that's what this OTA was - the 4.4 upgrade. I guess I'm a little confused on what you were asking exactly.
Glad you are on KK now, though. And, you can go back to JB if you want to since your bootloader is unlocked.
Wondering if anybody else is having this problem? If I install a custom rom like cm11 unofficial I just get stuck on the boot animation. It happens on any custom rom I installed and I followed all instructions. Any ideas? Running 1034 16gb on kit kat.
imprzwv said:
Wondering if anybody else is having this problem? If I install a custom rom like cm11 unofficial I just get stuck on the boot animation. It happens on any custom rom I installed and I followed all instructions. Any ideas? Running 1034 16gb on kit kat.
Click to expand...
Click to collapse
Make sure your bootloader is unlocked and your device is rooted. In addition your recovery must be installed correctly.
eddvys said:
Make sure your bootloader is unlocked and your device is rooted. In addition your recovery must be installed correctly.
Click to expand...
Click to collapse
i have the same problem on my xt1032 unlocked and rooted.
how i know if my recovery is installed correctly?
(i can only flash stock rom)
yoyococo said:
i have the same problem on my xt1032 unlocked and rooted.
how i know if my recovery is installed correctly?
(i can only flash stock rom)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2563599 Flash CWM in fastboot
Push ROM files to your /sdcard/
Install using your recovery xxx.zip
Instruction are there just follow them right.
I had this problem yesterday. Here is how I fixed it:
Install stock firmware. I installed a 4.4 one. http://forum.xda-developers.com/showthread.php?t=2542219
Then rooted using superboot
Finally, I installed TWRP
It took like three tries to get superboot and twrp to work properly. That's how I fixed it. Goodluck
Sent from my XT1032 using Tapatalk
Worked great thank you
x-Wooboost-x said:
I had this problem yesterday. Here is how I fixed it:
Install stock firmware. I installed a 4.4 one. http://forum.xda-developers.com/showthread.php?t=2542219
Then rooted using superboot
Finally, I installed TWRP
It took like three tries to get superboot and twrp to work properly. That's how I fixed it. Goodluck
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Works great now on my XT 1034.
x-Wooboost-x said:
I had this problem yesterday. Here is how I fixed it:
Install stock firmware. I installed a 4.4 one. http://forum.xda-developers.com/showthread.php?t=2542219
Then rooted using superboot
Finally, I installed TWRP
It took like three tries to get superboot and twrp to work properly. That's how I fixed it. Goodluck
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Had the same problem with a xt1032 retail.DE version, but didn't work.
I flashed the US umts4.4.2 version, was able to install root using superboot (at 2nd of 3rd try) and installed TWRP. Tried to Cm11 and gapps installed good, but still got stuck on bootanimation.
Losing faith here.
well this just happened on my phone again. the way I fixed it last time isn't working now I have no idea what to do
Why is no one helping with this issue. Ive experienced this a lot and I always have to restore it stock. I have never been able to install a custom ROM no matter how many times I root.
Sent from my XT1034 using xda app-developers app
I have this issues also on 4.4 us global rom. Rooted and recovery cwm
Sent from my XT1032 using Tapatalk
There are two ways to get this fixed:
Fix permissions through TWPR recovery (not available on CWM recovery);
Restore to stock firmware (you can find 4.4.2 firmware here: http://forum.xda-developers.com/showpost.php?p=49861244&postcount=101), flash CWM recovery (or TWRP) and flash CM11 again. This worked for me.
Let me know!
Can anyone confirm these methods? (at least the first one)
Done the 2nd multiple times, same result.
i have same problem , and don't know what to do ?
i flashed 3 different ROMs all stuck on bootanimation .
I'm curious. Did this happen the first time you flashed a rom? When I bought my Moto G (tesco version) it had 4.3 on it, I upgraded to 4.4 via OTA. Unlocked the bootloader, flashed CWM for 4.4 kernel, made backup and flashed various CM builds, booted with no problems.
Now I restored to backup, because of the non-working GPS.
It stucks on CM (the flashed rom) boot screen or the bootloader warning screen?
BBOXPT said:
Can anyone confirm these methods? (at least the first one)
Done the 2nd multiple times, same result.
Click to expand...
Click to collapse
After trying the second one 3 times, I used the TWRP/Fix Permissions method and successfully flashed CM11.
kellerman40 said:
I'm curious. Did this happen the first time you flashed a rom? When I bought my Moto G (tesco version) it had 4.3 on it, I upgraded to 4.4 via OTA. Unlocked the bootloader, flashed CWM for 4.4 kernel, made backup and flashed various CM builds, booted with no problems.
Now I restored to backup, because of the non-working GPS.
It stucks on CM (the flashed rom) boot screen or the bootloader warning screen?
Click to expand...
Click to collapse
I got CM 11 to boot the first time on a dirty flash, but forgot to flash gapps, so got a load of FCs when it loaded up. Since then, any sort of flash, clean or dirty gives me a bootloop.
Even directly flashing boot.img via fastboot doesn't fix it. Reinstalling the stock firmware and starting from scratch doesn't do it either.
Hey guys,
I have followed many tutorials (video and text) on how to flash ROMs on the Moto G, but to no avail.
I followed all the steps correctly, and my Moto G is stuck in a boot loop after 10 minutes. This happens every time I want to flash a ROM, and it has happened with many different ROMs, what am I doing wrong?
I have wiped all the wipey stuff and whatnot, I just don't know why it isn't working!
This is my first post, so please call me out if i missed any details I need to write down
Custom ROMs I have tried:
CyanogenMOD (Nightly)
Paranoid Android (unoffical)
C-Rom
Any help at all is much appreciated
Regards,
barky02
barky02 said:
Hey guys,
I have followed many tutorials (video and text) on how to flash ROMs on the Moto G, but to no avail.
I followed all the steps correctly, and my Moto G is stuck in a boot loop after 10 minutes. This happens every time I want to flash a ROM, and it has happened with many different ROMs, what am I doing wrong?
I have wiped all the wipey stuff and whatnot, I just don't know why it isn't working!
This is my first post, so please call me out if i missed any details I need to write down
Custom ROMs I have tried:
CyanogenMOD (Nightly)
Paranoid Android (unoffical)
C-Rom
Any help at all is much appreciated
Regards,
barky02
Click to expand...
Click to collapse
Happened to me at first too, when i had 4.4.2 stock in my Moto G, CM11 gets stuck in the bootanimation forever, what i did is downgrade to 4.3 (including the recovery) and then installed CM11.
Z-WolF said:
Happened to me at first too, when i had 4.4.2 stock in my Moto G, CM11 gets stuck in the bootanimation forever, what i did is downgrade to 4.3 (including the recovery) and then installed CM11.
Click to expand...
Click to collapse
Thanks a lot so how do I downgrade? and where can I find the 4.3 CWM recovery?
Edit: also, isnt 4.3 the upgrade? or is that a typo
barky02 said:
Thanks a lot so how do I downgrade? and where can I find the 4.3 CWM recovery?
Edit: also, isnt 4.3 the upgrade? or is that a typo
Click to expand...
Click to collapse
What i meant was that you need to flash the 4.3 stock recovery, along the 4.3 rom. those files normally come together.
Then you flash the custom recovery of your choice (i used CWM 6.0.4.7 touch) and CM11.
Look Here
4.3 = Jelly Bean Android
4.4 = KitKat Android
alezardstar said:
Dude, I completely understand you but I want to be very sure about what I will do foot try another time.
I back to 4.3 image downloading it here ( http://sbf.droid-developers.org/phone.php?device=14) and it already has the 4.3 recovery inside or I must to download it (from where?). Can you share the thread where you found the CWM recovery, please? Just to do it identical as you.
Thanks in advance.
Click to expand...
Click to collapse
let me see...
the guide to downgrade to 4.3 is this one
the guide to install CMW and CM11 is in cyanogenmod's wiki, you can find it here
as far as i know every (or at least most) stock ROM zip or tar file out there comes with a "recovery.img"
Yup downgrade to 4.3 needed then you'll have no problems
Sent from my Moto G using xda app-developers app
Happened to me as well (mine was rooted too), I followed the exact same steps Z-Wolf mentioned after searching and this seems to be a common problem.
I bought my device already upgraded to 4.4.2. I was able to install c-rom with no issue. I'm using tweaky ROM right now.
I'm curious as to why some devices need to downgrade and some don't?
Sent from my XT1032 using Tapatalk
What I did was installing cm11 from GPE and then wipe all cache and wipe system data or something like that (it deletes everything un your infernal sd), it worked for me after having bootloop with every ROM I tried. Ask the guys for those wipes ( I think it was format system/data but I don't remember very well).
ATRIXXIRTA said:
I bought my device already upgraded to 4.4.2. I was able to install c-rom with no issue. I'm using tweaky ROM right now.
I'm curious as to why some devices need to downgrade and some don't?
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
How did you do that man? I tried almost every found on this forum and I wasn't abble to get this done, always the same problem with encrypted partition comes up
---------- Post added at 02:00 PM ---------- Previous post was at 01:58 PM ----------
Z-WolF said:
Happened to me at first too, when i had 4.4.2 stock in my Moto G, CM11 gets stuck in the bootanimation forever, what i did is downgrade to 4.3 (including the recovery) and then installed CM11.
Click to expand...
Click to collapse
Did you get the downgrade version from here, which one did you use? I tried several and without success. I have a Moto G GPE
I will share my history with my phone since it can be useful for someone... Well I got the phone about a month ago, since i ordered from amazon, there's no way im going to return it for garanty if it broke, flashed cwm and rooted the same night, but when i was going to flash cm, l encountered a bootloop, since i didn't make a backup... i was at lost, my computer doesn't detect the phone in cwm, so I was with bootloop and not able to flash anything... Tried fastboot... Yes! so I downloaded stock and flashed away in fastboot, then i tried again with cm11, and this time it booted fine! I guess something prevented us to flash anything directly over stock, dunno what
I was stuck on boot loop for the past 24h, trying to flash a Lego ROM.
After a few factory resets and stock ROM flashes, I came across the solution of downgrading from KitKat 4.4.2 to Jelly Bean 4.3, then flash Lego again, and now all is well and good !
Here's the guide : http://forum.xda-developers.com/showthread.php?t=2542219
Flash Radios and New Kernel.
1031_Boost_US_CDMA_390.81.01P.zip
https://www.androidfilehost.com/?fid=23681161096070097
1031_Boost_US_CDMA_Kernel_3.4.42-gb89c9dd.zip
https://www.androidfilehost.com/?fid=23681161096070111
in my case I was flashing a Falcon, Boost Moto G, keep getting bootloops.
This is the first time in years I have ever had to sideload the Kernal and Radio, but non the less it stopped my bootloop.
Now if I get the error 16 voice mail message taken care of and input my MSL......
https://www.androidfilehost.com/?fid=23681161096070097
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
A lot of users report issues not being able to flash rom's on 4.4.2 kitkat.
A fix is to downgrade to 4.3, then flash roms.
I dont know why. I bought my device upgraded to 4.4.2 already, and i can flash roms with no issues.
Search the forum for the topic and you will find the info you need.
Roshi69 said:
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It wont backup saying what error?
Twrp just said 'failed' in red writing after the data backup I think. And philz touch said something along the lines of Not being able to write a file into the \clockworkmod folder.
I bought the device with 4.4.2 on it and followed the guides after reading up about the problems etc but TWRP 2.7.0.0 had a lot of reports that everything was working on it so went ahead with it
Sent from my Nexus 5 using Tapatalk
Ya that's strange because philz works great for me. Do you have a USB otg to try an external backup?
Sent from my XT1032 using Tapatalk
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Roshi69 said:
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Click to expand...
Click to collapse
Why dont you use Clockwork mod recovery for flashing Rom. I have flashed 10 Roms with that and all are backed up with out any problems. TWRP has no official support for moto g, and instead of all that why don't you try Cyanogenmod ?
(sorry if my english is not perfect)
Hello,
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
I never had such problems on my Nexus..
Please help me, I don't know what's going on
TheSkweed said:
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
Click to expand...
Click to collapse
Same here. It may be possible to downgrade to 4.3 (see here), but would it then be possible to flash a 4.4.2-based custom ROM ? I'm not sure.
Heres the steps I took.
*******Before device was stuck at bootloop*******
1. Bought phone (XT1032)
2. unlocked boot loader
3. Rooted
4. Flashed Philz Recovery (wouldn't backup rom)
5. Flashed TWRP and CWM with same issue.
6. Flashed 2 ROMs to try it (TweakyOne + C-Rom, Both wouldn't boot. and tried on all recoveries.
********Steps after being stuck at bootloop*******
1. Followed this amazing guide here (https://www.youtube.com/watch?v=laU6NQ0LxR0)
2. Set up the stock ROM again
3. Flashed TWRP 2.7.0.0 via Fastboot
4. Backup worked successfully
5. installed CM11 and setup successfully
6. installed Lego rom just to assure myself (currently running this ROM)
I know this is no solution at all but just wanted to share my steps to see what maybe fixed my phone. possibly the stock 4.2.2 rom I flashed was the solution. Maybe the original factory ROM that came on the phone was the issue?
Got a replacement phone today. I went to install the ROM that I liked I'm stuck in a bootloop and not sure how to recover. Would really appreciate some help as I'm bricked otherwise.
1. Rooted via Odin. Easy.
2. Went to install TWRP via Odin. I *think* it worked. I took these instructions from TWRP's site and tried to interpret as best as I could because this didn't seem to be English to me (Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.)
I booted into recovery, and it went into TWRP so I assumed I was good.
3. I installed Alliance ROM via ROM Customizer as instructed in the Alliance thread. I have done this many times before.
4. I thought it installed, and it started booting up (Alliance splash screen came up, etc) but then it looped back into a reboot.
5. Tried flashing another ROM via TWRP I had on my card and it did the same thing.
6. Tried Odin and it's doing nothing.
Not sure what to do now...please help!
I seem to have gotten back to stock somehow. Big relief.
I would appreciate any advice as to where I might have gone wrong.
First thing that comes to mind is firmware compatibility. If your phone is still using kit-kat firmware and you try to flash a lollipop rom it will not boot, and vice versa.
---------- Post added at 06:19 AM ---------- Previous post was at 06:18 AM ----------
Also, are you going into download mode from a powered off state?
Thanks for the reply. I did verify 5.0 first. And yes, was going into download from a powered off state.
My best guess was that I didn't follow those directions from TWRP I pasted above correctly because I didn't understand them. But like I said, TWRP did install, so I figured I was good. Maybe it just didn't install correctly?
I'm not sure, I've never had a recovery NOT install correctly before.
---------- Post added at 06:56 AM ---------- Previous post was at 06:54 AM ----------
What roms are you flashing? Have you tried those specifically for sprint phones?
I tried Alliance and MOAR. I had both on my SD card from my previous S5 before it broke. They are definitely the Sprint versions.
Here was the verbiage that confused me in the TWRP instructions "After typing fastboot reboot"
In the set of instructions below I'm not sure exactly what it means. I found the key combo, and at some point during reboot I held it to go to recovery mode, and TWRP launched. I am just wondering if I pressed it at the wrong time? Or maybe I'm getting hung up on the wrong thing.
(Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.)
metalfan78 said:
First thing that comes to mind is firmware compatibility. If your phone is still using kit-kat firmware and you try to flash a lollipop rom it will not boot, and vice versa.
Click to expand...
Click to collapse
I think this is the issue the more I contemplate it. I DID verify that I was on Lollipop. However, my mistake was assuming that my old phone was also on Lollipop when I flashed it, and assuming that the roms I was trying to flash were also lollipop roms. They are based on 4.4.
Going to try again, I restored the phone to 4.4. Thanks again for this.
Price is Right failhorn.
Another boot loop. Going to restore again. Ugh.
https://www.dropbox.com/s/16zl5f4dchh1k4m/Root files.zip?dl=0
These are the files I used to root after updating. It's the version of TWRP I'm still using. Just make sure when flashing TWRP with Odin that you have reboot UNCHECKED and boot into recovery manually.
Just wanted to circle back and say thanks metal, for trying to help.
Thanks to all of the awesome members/tutorials here I was able to use Odin to flash back to a stock unrooted kit kat ROM without issue every time. Because I was having troubles loading Alliance with kit kat but I was dead set on getting away from stock, I followed the tutorial for MOAR for 5.0 down to first flashing Lollipop and then flashing the ROM. The instructions in that thread were crystal clear for upgrading and then flashing and they worked like a charm.
Y'all are doin' work here, and I thank everyone for putting up with newbie tweakers like myself.