Related
Hello All,
I'm starting a new thread, because I am in a situation where I want to get my girlfriends phone back to stock so I can warranty it, and hopefully someone here will have the answer and people will have one place to look for putting their Roger's Samsung Captivate back to stock.
I'm hoping someone can tell everyone why we can't seem to get back to stock on these ROM's, here are the things I've tried:
Originally cleared everything rooted the phone through an update.zip, then put on the Clockworkmod Recovery and flashed Cognition v2.3b8, Trying to fix, battery life and lagging issues on her phone, (had a couple of random restarts the day before I flashed, so I was hoping it would fix that).
Then she started noticing the random restarts more often, so I tried:
clearing everything again through the recovery and tried restore from my backup to put things back, it looks like it extracted (or Installed) successfully then when it boots, it gets to the black, "Swipe" screen, then it freezes.
I tried to flash the Rogers_Stock.zip, same thing. Then I extracted the zip, and put it into the backup folder, hoping it will restore it like a normal restore, same thing.
So right now I'm stuck with a phone that says AT&T when it boots (I read one post on how to remove that) and cognition boot up.
Basically, I want to get this to look enough like stock to return.
I was thinking I can try to get rid of that AT&T popup, then flash the stock ROM, and say it just stopped booting for some reason. But then I still need to get rid of the Clockworkmod Recovery.
Wow that was a mouthful.
Thanks in advance for any help anyone can provide for use Roger's users (or their significant others).
AZ
try this: http://forum.xda-developers.com/showthread.php?t=867617
There are others like it too. Just don't try flashing the bootloader or sbl !
AbsoluteZero said:
Hello All,
I'm starting a new thread, because I am in a situation where I want to get my girlfriends phone back to stock so I can warranty it, and hopefully someone here will have the answer and people will have one place to look for putting their Roger's Samsung Captivate back to stock.
I'm hoping someone can tell everyone why we can't seem to get back to stock on these ROM's, here are the things I've tried:
Originally cleared everything rooted the phone through an update.zip, then put on the Clockworkmod Recovery and flashed Cognition v2.3b8, Trying to fix, battery life and lagging issues on her phone, (had a couple of random restarts the day before I flashed, so I was hoping it would fix that).
Then she started noticing the random restarts more often, so I tried:
clearing everything again through the recovery and tried restore from my backup to put things back, it looks like it extracted (or Installed) successfully then when it boots, it gets to the black, "Swipe" screen, then it freezes.
I tried to flash the Rogers_Stock.zip, same thing. Then I extracted the zip, and put it into the backup folder, hoping it will restore it like a normal restore, same thing.
So right now I'm stuck with a phone that says AT&T when it boots (I read one post on how to remove that) and cognition boot up.
Basically, I want to get this to look enough like stock to return.
I was thinking I can try to get rid of that AT&T popup, then flash the stock ROM, and say it just stopped booting for some reason. But then I still need to get rid of the Clockworkmod Recovery.
Wow that was a mouthful.
Thanks in advance for any help anyone can provide for use Roger's users (or their significant others).
AZ
Click to expand...
Click to collapse
Gin's got you on the right path for sure. A couple more items for you:
This post should help with removing the AT&T bootup logo: http://forum.xda-developers.com/showthread.php?t=849789
If you use Heimdall to flash the Rogers stock firmware that is in the post the Gin linked to then you will absolutely need to follow the instructions to use the Heimdall drivers for your captivate when it's connected or it won't see the device when you tell it to start. Like gin said, don't touch primary or secondary bootloader, leave those out and don't try to repartition it.
Restoring the stock firmware will remove the custom kernel that is installed with Cognition (at least it should) and so the Clockwork recovery should no longer be installed once the restore to stock is done. You can double-check once you are back to stock by powering off the phone and then hold both up and down volume + power, let the power button go after it restarts once and you see the I896 for the 2nd time. It should take you to the stock 2e recovery screen. If it does, you should be golden.
HTH
Wow, thanks all,
I used that method without the PIT file,
I just want to say thanks to everyone that offered help,
Goina try to send it for warranty now.
thanks again,
Joe / AZ
Hey guys.. My System Version is listed as being 6.13.215.XT894.Verizon.en.us. (This phone is about a week or 2 old for me) I have installed safetsrap recovery just to see how it works etc and have successfully installed the Eclipse port on the non-safe system. Now that I am done having fun with that, I would like to upgrade my system to newer leaked versions. My question is this: Should I uninstall safestrap before attempting to flash any of the leaked updates? How should I go about removing safestrap the "best" way? Also could someone please enlighten me with the correct "order" of these releases? EG: 6.11.200, 6.11.202, 206 etc. I guess I'm confused bc my system version starts with 6.13 instead of 6.11. Any help much appreciated!
I'm in the same boat as you, safestrap w/eclipse setup and I think I want to just switch to ICS 211
Pretty sure there are 2 methods, one with fastboot, and one with safestrap.
Fastboot method (droidforums.net/forum/droid-4-roms/212634-simplified-211-update-guide.html) definitely requires you to uninstall safestrap, but I think that automatically happens when you flash w/stock 219.
Safestrap method (droidforums.net/forum/search.php?searchid=4780372) allows you to just use a 211 ICS rom. But, I'm not sure if you already have to have done the fastboot ICS, I think you may have to fastboot ICS then install safestrap and safestrap into 211 ICS from 206 or 208 ICS.... Anyways, that's about where I am right now, trying to figure out if I safestrap to a 211 ICS rom from my current stock 219 GB, will it brick my phone. :/
---------- Post added at 12:46 PM ---------- Previous post was at 12:38 PM ----------
Oh also (droidforums.net/forum/droid-news/212864-another-ics-leak-here-droid-4-maybe-closer-ota.html) says that "212 ICS should be leaked soon". You may want to just hold tight, lots of new leaks means that something big (and easy to install for noobs like me ) may be coming soon .
The adventure continues...
Thanks for the quick response man... I'm glad to see I'm not the only one in this situation! I've been "creeping" on this board for 2 years now, (which I can't believe how fast that time went by) and thought it was about time that I start posting etc... you know what I mean, I see that was your 4th post so, that makes 2 situations where we are in the same boat! Thanks for the links brother I have actually read those, but need to checkup on them again... ALSO, my system downloaded an update the other day, (OTA) and was automatically going to install it (I clicked on download, thinking it would just download and wait for me to do the install manually like i have been used to in the past...) So, I tried to interrupt the download by throwing my phone into airplane mode really quick and then forcing a shutdown. Next time I turned on my phone I end up seeing the "Green Android with a triangle" screen, and a progress meter.. and I KNOW what that means. Something was flashed automatically by the phone. I got nervous, but my phone booted up perfectly, and I still had root, along with safestrap intact. I'm still a bit confused by what might've happened, but am relieved that my phone is still working perfectly... strangeness. I'll update this thread w any more info I can find. Thanks again!
Time out guys! First off, you cannot flash the ICS leaks in safestrap. The leaks are updates, not full ROMs. Second, you cannot flash a ROM based off the ICS leaks in safestrap unless you update you stock system to an ICS leak first. Well, you probably could, but it wouldn't boot. If you are on GB .215 you will need to update to .219 first. If you are on GB .219, and have not installed safestrap, you should be able to flash the an ICS leak via stock recovery without fastbooting. If you have installed safestrap, I believe you have to fastboot using the .219 file since safestrap changes something in the build.prop that will cause the leak update to fail.
The Optimizer said:
Thanks for the quick response man... I'm glad to see I'm not the only one in this situation! I've been "creeping" on this board for 2 years now, (which I can't believe how fast that time went by) and thought it was about time that I start posting etc... you know what I mean, I see that was your 4th post so, that makes 2 situations where we are in the same boat! Thanks for the links brother I have actually read those, but need to checkup on them again... ALSO, my system downloaded an update the other day, (OTA) and was automatically going to install it (I clicked on download, thinking it would just download and wait for me to do the install manually like i have been used to in the past...) So, I tried to interrupt the download by throwing my phone into airplane mode really quick and then forcing a shutdown. Next time I turned on my phone I end up seeing the "Green Android with a triangle" screen, and a progress meter.. and I KNOW what that means. Something was flashed automatically by the phone. I got nervous, but my phone booted up perfectly, and I still had root, along with safestrap intact. I'm still a bit confused by what might've happened, but am relieved that my phone is still working perfectly... strangeness. I'll update this thread w any more info I can find. Thanks again!
Click to expand...
Click to collapse
Yup, same here, I'm just taking as much info in right now as possible. I think our options are eclipse, stock 219 with frozen apps, or ICS. Oh if you use stock at all, I'd recommend upgrading to 219, I think that was a major update, my battery life has just about doubled... then again I only had my phone for about a week before upgrading, and about 3 weeks total now.
kwyrt said:
Time out guys! First off, you cannot flash the ICS leaks in safestrap. The leaks are updates, not full ROMs. Second, you cannot flash a ROM based off the ICS leaks in safestrap unless you update you stock system to an ICS leak first. Well, you probably could, but it wouldn't boot. If you are on GB .215 you will need to update to .219 first. If you are on GB .219, and have not installed safestrap, you should be able to flash the an ICS leak via stock recovery without fastbooting. If you have installed safestrap, I believe you have to fastboot using the .219 file since safestrap changes something in the build.prop that will cause the leak update to fail.
Click to expand...
Click to collapse
Thanks for clarifying that ^^, kwyrt, I've read some of your other posts they are always quite informative!
Glad I could help! There are a LOT of nice, helpful people in these forums. Just keep asking questions! Doing some of this stuff can be nerve wracking even if you know what your doing. I actually, finally, got up the nerve to jump on the ICS leak train last night. If you decide to take the leap, I highly recommend using jsnweitzel's Droid 4 Utility located here: http://forum.xda-developers.com/showthread.php?t=1714596. Made the process much easier than it has any right to be.
Android 4.0.4 flash Success! =)
So I decided to take the leap last night... first thing I did was every way of factory resetting I know how to do hehe. (Privacy, factory reset under settings, then a data and dalvik clear in recovery) Downloaded the GB219 file, put it on my SD, fired up the Droid 4 Utility (thanks to everyone who contributed!) and had no problems at all upgrading. I wasn't worried about root so I skipped the OTA rootkeeper process. Next I needed to get to an ICS build. Again, I used the Droid 4 utility.... only difference being that we had to flash the boot.img file first.. (ICSFIX.img). On my first go, I successfully flashed the new boot.img (ICSFIX), but then got a sig verification error when trying to flash the OTA zip. ****. Soft brick at 2AM... heh. at least I still had plenty of time. Re-DL the OTA file, copied it over again and repeated the entire procedure, this time with success. Really Glad I decided to upgrade! Thanks guys!
ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.
Hey guys,
Basically today I was getting tired of the android 5.0 install I had running on my S5 so I figured I would reinstall 4.4.2 via Odin - a process which I had done a few times previously. I didn't really think about the fact that I was going from one version of the OS to another, and whether this would create an issue, but it has. My phone now loads up the samsung logo, but doesn't finish the animation and then freezes. A few seconds later, the screen will go black and the LED on the top of the phone will just glow blue. The phone will sit like this forever, and never boot. I have tried re-installing the AP in Odin a few times, all of which show pass in Odin, but to no avail. I have also wiped all data and the cache within the recovery. I don't know where to go from here. Any suggestions?
Thanks
Philpro said:
Hey guys,
Basically today I was getting tired of the android 5.0 install I had running on my S5 so I figured I would reinstall 4.4.2 via Odin - a process which I had done a few times previously. I didn't really think about the fact that I was going from one version of the OS to another, and whether this would create an issue, but it has. My phone now loads up the samsung logo, but doesn't finish the animation and then freezes. A few seconds later, the screen will go black and the LED on the top of the phone will just glow blue. The phone will sit like this forever, and never boot. I have tried re-installing the AP in Odin a few times, all of which show pass in Odin, but to no avail. I have also wiped all data and the cache within the recovery. I don't know where to go from here. Any suggestions?
Thanks
Click to expand...
Click to collapse
I think you need to find the lollipop kernel. But I'm not 100 percent sure.
try opening kies with your phone connected and look for a menu option to the effect of restore/repair device
sent from my galaxy a5 (SM-G900AZ) on Cricket
I'm not sure if this helps you or not, but I did the same thing, trying to downgrade. I did not take the OTA update when I went from KitKat to Lollipop, instead I flashed one of the Lollipop ROMs, so be wary of that. If you took the OTA update, I don't know if this will work for you.
Anyways, I spent the better half of a day trying different kernels and stock ROMs using the factory recovery etc and nothing was working, each time I would either end up frozen at the Samsung screen or the initial splash screen when you power the phone on. I found this thread here:
http://forum.xda-developers.com/att...w-to-update-to-g900aoca-5-0-keeproot-t3076803
Under "notes", step 4 I downloaded the file G900A_Downgrade_to_NCE.tar and flashed through Odin. This is the file that got me out of this hole, so maybe it will work for you as well. After flashing, it rebooted and went past the Samsung screen to the initial first time setup screen. Looks like this put me back at stock UNrooted 4.4.2.
Good luck, hope this helps someone else out.
Wait, are you saying that you updated your phone using the stock recovery? Were you rooted? @mangomango
Its_Tim said:
Wait, are you saying that you updated your phone using the stock recovery? Were you rooted? @mangomango
Click to expand...
Click to collapse
I flashed through Odin, but yes I was rooted when I went from KK to LP.
I purchased an AT&T sm-g900a that was supposed to come with 4.4.2 according to info on site and sticker on the box indicated it originally had 4.4.2 on it too. I have no way of knowing if someone flashed it with the whole 5.0 file or just updated it. It was sold to me as a new and unlocked phone, and I got a good deal. The phone looks new with an AT&T screen cover attached, packaging, etc. and contents were still in sealed packaging. Will this work? https://www.androidpit.com/how-to-downgrade-galaxy-s5-from-lollipop-to-kitkat ? Is this the same file as the downgrade one referred to? Sammobile only has the 4.4.2 file. There is a significant cost difference in this model and the t-mobile version. Otherwise, I would just return it. I do not like the newer software at all.
I had the same thing happen today with my g870a. I tried 5.0, and 4.4.2 kernels, 4.4.2 firmware (which I knew wasn't corrupt) in Odin but nothing worked. The whole reason was to go redo my Alliance Rom and use FF beside Safestrap (the LP kernal would get rid of the SS). What I ended up doing was going into stock recovery and went to where it says "install update from ext SD". Then I went into my FF backup and found twrp.zip and selected it. It's did some things, said some stuff failed, then booted up enough to get me to FF to get it straight. One problem...my g870a thinks it's a 900, wtf?
Sent from my SAMSUNG-SM-G900A using Tapatalk
I do realize I am beating a dead horse but I'm having trouble finding the specific answer that I'm looking for. When I first flashed M Dev preview the day it was releaser I did not get the boot error. I rooted got the error, then it wouldn't boot until I flashed a custom kernel. We all know that this is what needs to be done.
However, I've flashed stock lollipop and gone back to M several times, stock recovery, correct boot loader and wiped all data and cache several times however I am still getting the boot error. Now all you have to do is wait the 5 seconds or however long it is and the device boots fine, but I've also noticed that ever since this began happening back when I first rooted, my LTE signal indicator goes away. I still have data and I can still use the device to get online and such. I wouldn't really are except there's one thing, when the LTE indicator goes away I can't make calls either. I am not set to LTE only or anything, I have the correct radios flashed and it doesn't matter what I do.
I can flash factory images manually or in NRT and I still get the boot error, and I still get the signal issue.
Don't worry so much about the LTE issue because I feel like it is caused by whatever is wrong and causing me not to be able to go back to complete stock.
I just need some advice on how go back to TOTAL stock, (UNrooted, stock recover, stock kernel, stock everything) so I will no longer get the boot error.
Thanks in advance to anyone who is willing to help.
jonzey231 said:
I do realize I am beating a dead horse but I'm having trouble finding the specific answer that I'm looking for. When I first flashed M Dev preview the day it was releaser I did not get the boot error. I rooted got the error, then it wouldn't boot until I flashed a custom kernel. We all know that this is what needs to be done.
However, I've flashed stock lollipop and gone back to M several times, stock recovery, correct boot loader and wiped all data and cache several times however I am still getting the boot error. Now all you have to do is wait the 5 seconds or however long it is and the device boots fine, but I've also noticed that ever since this began happening back when I first rooted, my LTE signal indicator goes away. I still have data and I can still use the device to get online and such. I wouldn't really are except there's one thing, when the LTE indicator goes away I can't make calls either. I am not set to LTE only or anything, I have the correct radios flashed and it doesn't matter what I do.
I can flash factory images manually or in NRT and I still get the boot error, and I still get the signal issue.
Don't worry so much about the LTE issue because I feel like it is caused by whatever is wrong and causing me not to be able to go back to complete stock.
I just need some advice on how go back to TOTAL stock, (UNrooted, stock recover, stock kernel, stock everything) so I will no longer get the boot error.
Thanks in advance to anyone who is willing to help.
Click to expand...
Click to collapse
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=2954008
Follow method #2.
Evolution_Tech said:
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=2954008
Follow method #2.
Click to expand...
Click to collapse
You, my friend, deserve a 4th of July beer. ?