I recently got my replacement EVO3D, rooted it, and flashed SteelRom 1.04. I noticed that my phone randomly "crashed" (for lack of a better word) and, while trying to reboot, became trapped in a never-ending boot loop cycle. Only temp solution was to do a battery pull, which allowed me to boot back into the ROM.
Assuming that it was a problem with the ROM, I tried flashing CleanROM 1.3. The same problem occurred (esp. when I was browsing the web). Worse, even, because even a battery pull didn't fix it.
I nandroided back to Stock rooted to see if the problem remains.
So, besides the simple sharing of my problem, I'd like to know if
Can I reroot after "Complete Stock and S-ON"?
Is this problem stemming from ROM bugs, or maybe is it a hardware defect?
I am still within the 30 days, but I have already had it exchanged once. What should I do?
Thanks will be given to those who help
EDIT: I went back to Stock/S-ON and rerooted. Problem fixed for now
Did you notice this problem before you rooted? If not, then something probably went wrong during the ROM flashing process.
I doubt its the ROM itself otherwise I'm sure there would be plenty of folks posting the issue in the ROM's thread. Likewise, if you didn't have the problem before you rooted, its not a hardware issue either.
A couple of questions:
1. Did you wipe your caches before flashing the ROM?
2. Did you try performing a factory reset after you flashed the ROM and started
having this issue?
mvansomeren said:
Did you notice this problem before you rooted? If not, then something probably went wrong during the ROM flashing process.
I doubt its the ROM itself otherwise I'm sure there would be plenty of folks posting the issue in the ROM's thread. Likewise, if you didn't have the problem before you rooted, its not a hardware issue either.
A couple of questions:
1. Did you wipe your caches before flashing the ROM?
2. Did you try performing a factory reset after you flashed the ROM and started
having this issue?
Click to expand...
Click to collapse
Hi, and thanks for your reply.
I rooted the phone as soon as I got it (maybe stock for 15 minutes) so I didnt have a chance to observe this problem then.
I rooted using Revolutionary 0.4a I flashed SteelRom and CleanROM, both of which showed this problem. I finally flashed ShooterRewind 3D, which hadn't shown this problem until I tried to reply to this thread, ironically.
and to answer your questions:
I do. Actually I always use t3_superwipe_1.3.zip before flashing.
I also tried to "Wipe Data/Factory Reset" after I experienced the problem. No change.
Finally, can you tell me if I can go back to stock using one of the guides and reroot using Revolutionary?
Yes you can go back to stock and back to S-ON. There is a thread in the dev section that will guide you.
http://forum.xda-developers.com/showthread.php?t=1194053
nevermind, did not read OP fully.
mvansomeren said:
Did you notice this problem before you rooted? If not, then something probably went wrong during the ROM flashing process.
I doubt its the ROM itself otherwise I'm sure there would be plenty of folks posting the issue in the ROM's thread. Likewise, if you didn't have the problem before you rooted, its not a hardware issue either.
A couple of questions:
1. Did you wipe your caches before flashing the ROM?
2. Did you try performing a factory reset after you flashed the ROM and started
having this issue?
Click to expand...
Click to collapse
mvansomeren said:
Yes you can go back to stock and back to S-ON. There is a thread in the dev section that will guide you.
http://forum.xda-developers.com/showthread.php?t=1194053
Click to expand...
Click to collapse
tatnai said:
nevermind, did not read OP fully.
Click to expand...
Click to collapse
Thanks Everyone for you're replies. I went back to Stock S-ON, talked with Sprint, they did a ##786# Reset, and then I rerooted with Revolutionary. No problems so far, although Revolutionary did an odd root sequence:
Code:
Rebooting to fastboot
Rebooting to fastboot (again)
Rebooting to fastbook (yet again)
Communications with the device were interrupted, try again
Anyway, I am all set now, so thank you all. Appreciate it.
Related
I was running the Spike Pure ICS on my SGS2, before which I had the ICS version of MIUI. I tried flashing Lite'ning Rom 3.6 through Odin, but was unsuccessful. Also, that's time I noticed the 7.2 version of CM and decided to flash that and that's when the problem occurred.
Although I could flash CM 7.2 properly and could also install the GApps through CWM, on rebboting it through the CWM, my phone got stuck and it wouldn't go into Recovery any more.
Luckily, it would boot into Download Mode and I could flash the stock rom through Odin and get my phone back to stock, thereby losing the Root and CWM.
I wanna know as to what could cause such an issue to arise. so that I can prevent it later!
Your help and time are appreciated!!
Why start a 2nd thread ?
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
And you couldn't make another post to your initial post along the lines of 'Why did this occur in the first place ?' You could even easily change the title of your initial thread to reflect your desire to know the answer to this question.
One of the main rules of XDA is don't spam.
I'm extremely sorry if I've spammed as it wasn't my intention at all!
This thread was and still is a genuine question which I want to know!!
Also, could you please tell me about the occurrence of such a problem on my phone??
gadgyfreak said:
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
Click to expand...
Click to collapse
I think answer was there but might be not clear......
When you flash gb over ICS you have to wipe, when you mix stuff after that, meaning trying different kernels to fix the issue it might get worse.
Because recovery is somewhat linked to kernel in s2, you won't get recovery in a messed up system.
So when you flash a complete firmware using Odin and then do data cache wipe, it get fixed.
Hope this helps.
But then how is it possible that my phone didn't get all messed up when I flashed CM 9(Nightly) over my pre-existing CM 7.1, while it happened when I tried it vice versa?
already told you, when you go from ICS newer kernel to GB older kernel, wipe is necessary. Going from GB to ICS will work but wipe is better there too.
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Flash a GB rom.
gadgyfreak said:
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Click to expand...
Click to collapse
save data
Wipe dial *2767*3855#
Flash GB Rom, preferably stock using Odin.
Should boot now, if not go into recovery and wipe data cache.
It will boot now.
To summarize:
Rogers EVO 3D GSM
No SIM Card currently in the phone
Had Stock ICS Update
Rooted the phone, causing it to become stuck in an irreversible restarting pattern
Phone (if left alone for a while) will turn itself off within 4-6 minutes, and restart. It will repeat. If it is plugged-in and charging, it (occasionally) does not turn off. If the music player is playing in the background, it will not turn off.
Problem will persist even if the SD Card is not present.
Have tried multiple solutions (see page 2) which haven't worked.
Could really use some help!
Hi there, I was hoping that the more experienced phone users here could help me with my problem.
My phone is an EVO 3D (Rogers GSM). A while back, I decided to try and root my phone (I had the ICS update at the time). I managed to S-OFF it and later unlock it, but I had a lot of trouble rooting the phone through conventional guides.
In trying to root my phone, it became stuck in a boot loop that would cause it to turn on, flash the HTC logo, but then turn off and repeat the process. This was a really annoying issue for me, that I couldn't resolve until as a last-ditch effort, I managed to install a stock RUU and fix the problem.
Finally, I was able to root the phone last week. But as soon as I did so, it began performing erratically again. This time, the phone would turn itself off and turn back on (and repeat the process infinitely) if I left it alone for 5-7 minutes.
I tried everything I could think of to fix the problem, even wiping the partition caches/dalvik drives and factory resetting it multiple times. But even with all that, it wouldn't resolve the issue. I heard that the SD card could've been the root of the problem, but even after taking it out the problem still occurs. I've also tried factory resetting it without the SD card, but to no avail.
So I decided to install my first ROM; Viper3D (1.0.0-Multi-8_14).
I was successful in installing it, and the new software was great, but unfortunately, the issue still carried over. Unless I was constantly doing something on my phone, the phone would shut reboot after 5-7 minutes. And it would keep repeating without end. More factory resets would not do anything, and I find myself unable to install Stock ROMs now.
A sort of "temporary" fix (when I want to keep the phone on for a bit) is to keep the music player playing. As long as a song is playing (even if the volume's off), the phone won't reboot.
Nothing else works.
I'm really at my wits' end here, and I hope that someone can help me with my problem. If you have any further questions you need answered before you can help me, by all means ask.
(Also, I'm not sure if this has any bearing on the issue, but my HBOOT downgraded after the root from 1.58 to 1.49. Could that be related to my problem at all?)
Thank you very much for your time.
ReversaI said:
Hi there, I'm relatively new in terms of anything phone-related, so I was hoping that the more experienced people here could try to help me with my issue.
My phone is an EVO 3D (Rogers GSM). A while back, I decided to try and root my phone (I had the ICS update at the time). I managed to S-OFF it and later unlock it, but I had a lot of trouble rooting the phone through conventional guides.
In trying to root my phone, it became stuck in a boot loop that would cause it to turn on, flash the HTC logo, but then turn off and repeat the process. This was a really annoying issue for me, that I couldn't resolve until as a last-ditch effort, I managed to install a stock RUU and fix the problem.
Finally, I was able to root the phone last week. But as soon as I did so, it began performing erratically again. This time, the phone would turn itself off and turn back on (and repeat the process infinitely) if I left it alone for 5-7 minutes.
I tried everything I could think of to fix the problem, even wiping the partition caches/dalvik drives and factory resetting it multiple times. But even with all that, it wouldn't resolve the issue. I heard that the SD card could've been the root of the problem, but even after taking it out the problem still occurs. I've also tried factory resetting it without the SD card, but to no avail.
So I decided to install my first ROM; Viper3D (1.0.0-Multi-8_14).
I was successful in installing it, and the new software was great, but unfortunately, the issue still carried over. Unless I was constantly doing something on my phone, the phone would shut reboot after 5-7 minutes. And it would keep repeating without end. More factory resets would not do anything, and I find myself unable to install Stock ROMs now.
A sort of "temporary" fix (when I want to keep the phone on for a bit) is to keep the music player playing. As long as a song is playing (even if the volume's off), the phone won't reboot.
Nothing else works.
To summarize:
Rogers EVO 3D GSM
Had ICS installed before root
Rooted, now phone is stuck in irreversible restarting pattern
Problem persists even without SD Card
Now using Viper3D ROM, but the problem remains
Could really use some help
I'm really at my wits' end here, and I hope that some of you can help me with my problem. If you have any further questions you need answered before you can help me, by all means ask.
(Also, I'm not sure if this has any bearing on the issue, but my HBOOT downgraded after the root from 1.58 to 1.49. Could that be related to my problem at all?)
Thank you very much for your time.
Click to expand...
Click to collapse
Sounds like a possible bad flash, you are obviously using the stock kernel, did you flash the new firmware, check setting about phone and will see baseband etc, that will tell if you have flashed the correct firmware, I too am with rogers. also using viper rom multi, hboot is the same and I have no such problem, here a screeny baseband, never mind the kernel
Please don't quote an op of that size next time but I'm on the correct firmware on my CDMA device and reboots happen occasionally it is most likely the ics update in general or just the kernel try a different one
Sent from my PG86100 using xda premium
No, mistake using tapatalk on my phone, anyways as I am a gsm phone and you already have a thread opened, wait for an answer from someone as I have no experience with cdma evo's, I would advice you to put more info as what rom you are using, hboot, firmware and service provider
sent on my Evil Evo running the special sauce kernel
It says:
UNLOCKED
SHOOTER_U PVT SHIP S-OFF RL
HBOOT-1.49.0008
RADIO-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
Jul 15 2011, 14:39:25
Kernal Version
3.0.16-ge733189
[email protected] #1
SMP PREEMPT
(everything else is identical to yours, I think)
Baseband Version
11.77.3504.00U_11.25.3504.06_M
Build Number
1.11.401.110 CL68035 release-keys
Browser Version
WebKit/534.30
Yes, new firmware, what I would try is in recovery wipe all partitions except sdcard, wioe dalvik and cashe and factory wipe, then reflash the rom, I do have a custom kernel which might interest you, I do know that some people have had issue's with the viper rom, pm me if you want more info
sent on my Evil Evo running the special sauce kernel
Could you please help provide some step-by-step instructions, assuming you can remember them? Sorry. D:
Ok, 4ext recovery is hopefully what you have installed on your rooted phone? Have you made a nandroid back up of your existing rom?Boot into recovery you will see wipe and format, press that and you should see down near the bottom format all partitions except sdcard, press that also on that screen you will also see wipe dalvik & cashe and factory wipe. Then install zip from sd card and find the rom zip and flash, and wait, now just to let you know all your data will be erased, so contacts should be back up with gmail
sent on my Evil Evo running the special sauce kernel
I have ClockworkMod, actually. o-o
Should I get 4ext instead?
ReversaI said:
I have ClockworkMod, actually. o-o
Should I get 4ext instead?
Click to expand...
Click to collapse
yes that could be why you have an issue, 4ext is much better and prefered
Is there a way to get rid of one and add the other? Like, flash a new recovery or something?
Since your phone is rooted, you can just use the 4ext app to install the recovery. See my Web signature for a link to the free version.
Read, Search, Read again, ... Then Ask with Tapatalk 2
ReversaI said:
Is there a way to get rid of one and add the other? Like, flash a new recovery or something?
Click to expand...
Click to collapse
I believe if you install 4ext it over rides cwm but it was months ago since i did the upgrade, viper rom has an aroma installer which works much better with 4ext recovery, who rooted your phone?
flashallthetime said:
I believe if you install 4ext it over rides cwm but it was months ago since i did the upgrade, viper rom has an aroma installer which works much better with 4ext recovery, who rooted your phone?
Click to expand...
Click to collapse
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Still working on it...
ReversaI said:
Still working on it...
Click to expand...
Click to collapse
yap it;s so easy just read the recovery b4 you make any selection and take your time
---------- Post added at 11:50 PM ---------- Previous post was at 11:47 PM ----------
coal686 said:
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
us old folks forget things:laugh: first sign of dementia :laugh::laugh::laugh::laugh::laugh::laugh:
---------- Post added at 11:57 PM ---------- Previous post was at 11:50 PM ----------
coal686 said:
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
flashallthetime said:
yap it;s so easy just read the recovery b4 you make any selection and take your time
---------- Post added at 11:50 PM ---------- Previous post was at 11:47 PM ----------
us old folks forget things:laugh: first sign of dementia :laugh::laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
i'll give you the apn's for rogers as I remember them by heart
Name rogers
apn rogers-core-appl1.apn
mmsc http://mms.gprs.rogers.com
mms proxy 10.128.1.69
mms port 80
apn types default,supl,mms
those are the settings for mobile and mms
Ok here is the deal you flashed Vipers ics rom unless you flash the latest kernel from that other guy you are going to experience random reboots.
So my suggestion is go download that other guy's kernel and install it.
spirithandler said:
Ok here is the deal you flashed Vipers ics rom unless you flash the latest kernel from that other guy you are going to experience random reboots.
So my suggestion is go download that other guy's kernel and install it.
Click to expand...
Click to collapse
gave him it already:good:
List of attempted solutions that have not worked:
Wiping everything (and formatting it) except for SD Card.
Wiping (and formatting) the SD Card
Installing a new ROM
Flashing a different kernel
Factory Resets
Wiping Dalvik & Cache
Wiping Dalvik/Cache BEFORE & AFTER installing a ROM
Stuff I haven't tried:
Re-locking the Phone
Reinstalling a stock RUU (not ROM)
Unrooting
Welcome to the world of the EVO 3D. Hate to be the one to say this but it's just one of those 3ds. Mine had random reboot problems and lockups no matter what ROM, kernel, firmware, root access, anything. Just happens to a lot of them. Some people report success with relocking and unlocking the bootloader and making sure you're S-Off but I've tried it all.
Maybe that's not the case for you but it seems to be for a lot of people.
You can follow me on Twitter - @NotSo1nter3stin
I've been searching all morning to find another thread to see if this has been answered before. I was trying to install a GSM Rom onto my Rezound. The install failed at around 2 %. I'm almost positive I thought I was on the correct ICS firmware, when apparently I wasn't. So instead of trying to fight installing the rom over and over again. I had a back up rom that I installed instead. My problem I think is that I didn't go back and re wipe everything after the failed install.
Which I could slap myself for, but my problem is this. The phone can go into Hboot, which gives me hope not all is lost. But I can't go into recovery or boot up. The phone will only load the white HTC screen then just reboots over and over again. I've seen where it tries to load recovery but then just reboots. I'm not sure if I have to reload the RUU or what I have to do. If anyone has had this problem or knows of a thread on how to fix it I would greatly appreciate it.
Edit: Just a little about my phone if it helps.
Vigor Pvt S-OFF RL
HBOOT - 2.25.0000
Radio - 1.22.10.0421r/1.22.10.0424r
OpenDSP- v13.6.0.7611.00.0104
eMMC-boot
Since you can't get to recovery it might be time to just put an RUU on you card and let hboot install it. Then you can install a recovery and then one of your backups.
Or just reinstall recovery
Sent from my Vivid 4G using Tapatalk 2
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
stfumate said:
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
Click to expand...
Click to collapse
I prefer CWM touch myself but the one from here not the official
stfumate said:
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
Click to expand...
Click to collapse
If you plan to do a restore, stick to the same recovery.
Not sure how restoring over a previous rom borked your recovery though, that is weird.
mjones73 said:
If you plan to do a restore, stick to the same recovery.
Not sure how restoring over a previous rom borked your recovery though, that is weird.
Click to expand...
Click to collapse
Well I started off as I normally would, wiping data, wiping cache, wiping davlik, then installing. I tried one of the new JB roms Tron. But I couldn't get the GPS to work at all. So I stumbled across a GSM rom and went to install, it booted into it's own installation touch screen. I kept it simple not choosing many extras, then the last option was. Are you on ICS firmware? Which to my noobness, I've been running ICS roms since I acheived S-OFF. So I was pretty positive that I upgraded my firmware whenever I did that. So I chose Yes and it started to install, got to 2% and said it was done. Again I assumed the install had just failed and after having tried installing a GSM rom once before I had to go through and do it multiple times. I was tired and didn't feel like messing with it. So instead of rebooting, I went back into recovery and flashed another rom I had set on my SD card in case I didn't like the GSM. To which I think that my mistake came when I didn't either
A) Re-wipe my data, cache, davlik.
or
B) Restore my previous Rom from before.
So after the new rom installed and looked as everything went smooth. I selected reboot, the HTC white screen came up and the phone shut off. Then would power back up and display the HTC white screen and shut off again. So far the only thing I've been able to get it to do is the power cycle with the white screen and boot up in Hboot. But none of the options will work as the only thing it will do is power cycle. That's pretty much where I'm at until I can try reinstalling the RUU and flash the new(same) recovery.
The problem is nothing you've done there should have touched the recovery, that's why I find it weird.
I'd assume the rom asked which firmware you were on so it could installed the old firmware patch if needed.
Anyway, hopefully the RUU should straighten it out.
Well good news, re-installing the RUU fixed the phone. It re-locked my hboot, so I just finished unlocking that and re-flashing recovery. Thanks a bunch for all of your help. I greatly appreciate it !
Hey guys, had a Note for a little while now and was running stock AT&T GB. I tried upgrading to ICS a couple of times using other threads in this forum, but I'd keep getting stuck in a boot loop and had to revert back to stock AT&T GB to recover my device per Da_G's method here: http://forum.xda-developers.com/showthread.php?t=1506330, and it worked fine.
However, I recently tried one more time to upgrade to ICS, failed and reverted back to stock AT&T GB per Da_G's method, and while my phone turns on, it has become sluggish to the point of being absolutely unusable. Screen touches work fine in some cases, and then take forever to register in the same spot later. The on screen keyboard cannot be invoked - it almost always hangs the phone. And the phone randomly reboots.
I did forget to wipe cache and dalvik cache the last time around while doing the install, and that probably caused this problem. But sine then I've wiped both caches and retried flashing, and also reinstalled a stock AT&T radio in case that was the problem, and also reset the flash counter per braway's methode here: http://forum.xda-developers.com/showthread.php?t=1569206, but to no avail...
My Note is pretty much useless at this time, so any light you guys can shed or any other tack you can suggest is going to help me immensely!
Thanks for the help!
Sid.
Wiping caches is not enough. You need to to a full data wipe/factory reset. At this point why not just flash your phone with Odin.
http://www.samsdroid.com/2012/07/i717uclf6-android-404-usa-at-stock-rom.html
This will fully wipe your phone and install the UCLF6 ICS ROM with matching radio.
Agoattamer said:
Wiping caches is not enough. You need to to a full data wipe/factory reset. At this point why not just flash your phone with Odin.
Click to expand...
Click to collapse
Sorry, I didn't mention - I DID do a factory wipe/data reset and I've been flashing the stock GB ROM via ODIN itself. But thanks for the link to the ICS ROM - I'll try installing this and report back.
Okay, I downloaded the UCLF6 ROM from the samsdroid site (took like 3 hours to download!), performed several factory data resets, cache wipes and dalvik cache wipes on my phone, and then flashed the ICS ROM via Odin. Odin showed "Passed", but the phone rebooted into recovery with a message "failed to mount /system" and "failed to mount /data". I then hit "reboot system now" and am stuck at boot loop. Booted back into recovery, got the same message about not being able to mount system and data. Hit "reboot system" again and back to boot loop...
What the heck am I doing wrong???
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
You do have an ATT i717 and not a canadian version? But I think your phone has other issues.
It is an AT&T SGH-i717. I've used it for 6 months now and it worked fine - it just never let me upgrade it to anything beyond GB... and now it is unusable even with GB.
Do you think it might be a hardware issue? Although, how could flashing and reflashing ROMs impact the hardware?
If the odin flashing did not straighten things out then I have to believe that there are other issues.
sid.asu said:
It is an AT&T SGH-i717. I've used it for 6 months now and it worked fine - it just never let me upgrade it to anything beyond GB... and now it is unusable even with GB.
Do you think it might be a hardware issue? Although, how could flashing and reflashing ROMs impact the hardware?
Click to expand...
Click to collapse
Did you try to flash ICS with Samsung Kies? If that doesn't work, your phone may have developed a hardware problem.
i have had the same issues as well, i am unsure if its me or what but everytime i have tried to flash a tmobile rom on my note which should work it slows down to a crawl i cannot even go through the setup process. I have tried via odin and through cwm touch. the next thing i flashed was t879uvlg3 modem and i was wondering if that was the issue and if so what modem should i flash that way i dont have to use kies for recovery cause man..........thats slow. I even made a nandroid backup and it was slow as well so if anyone has had this issue or any ideas please help me
oort cloud said:
Did you try to flash ICS with Samsung Kies? If that doesn't work, your phone may have developed a hardware problem.
Click to expand...
Click to collapse
My problem is that the phone does not stay on long enough for Kies to detect it - it keeps rebooting on GB. Well, guess it's cooked! Thanks for the help!
Hey guys,
Just rooted my phone today, and have had a pretty bumpy time. I've made it through most of it, but am having trouble getting a new ROM installed (NilsP's Business ICS Sense 6.4). Basically, install is going fine, but when I make it to the ROM, I get no cell signal, no data, and gps won't turn on.
I'm running S-on, and the install will complete and it will automatically reboot to hboot for the kernel. However, nothing happens that indicates that the kernel installed. Upon reboot, the ROM will open, I'll skip through the setup wizard, and once out cell, data, and gps fail to turn on.
I tried placing the kernel's zip file directly onto my SD card's root drive. Once booted to hboot, the kernel will install. However, problem will persist. I updated to 6.4 OTA with no change. I tried disabling the Fast Boot option and cycled various settings, as suggested in NilsP's original thread. Prior to rooting, I had the most current update from Verizon (pushed through about a week or two ago). I even tried installing with the s-off option, which gave the same result.
I spent about five hours today searching these forums, as well as others, for a similar issue but was unable to find one. Until I figure out a way forward. I feel like I'm missing something simple, since I'm almost there! As I said, I'm a newbie, so forgive me if I misused any terms. Any and all help would be greatly appreciated!
flash stock recovery and do factory reset.
Damasterjj said:
flash stock recovery and do factory reset.
Click to expand...
Click to collapse
from the HBOOT
But first... did you put the back cover on again? The antennas are in there so you won't get any service without it on.
feralicious said:
But first... did you put the back cover on again? The antennas are in there so you won't get any service without it on.
Click to expand...
Click to collapse
Yup, tried with the lid back on, too. Figured there must have been an important circuit with all those contacts in there.
I'll try the reset from HBoot later this evening. I wiped every time I tried to reflash the OS, though only from the recovery menu. I'll let you know how it goes.
Thanks for the help guys, it ended up installing just fine after a factory reset from Hboot. Now I'm running into the same Play Services issue as everyone else using this ROM. Go figure. I'll monitor NilsP's original ROM thread for a solution. Looks like he's working on it already.