Ok im having issues installing up to date roms. They keep getting stuck in a boot loop. I rooted my phone using odin back when 5.1 was out. There was no 6.1 yet. Im wanting to run on updated software. But im not having any luck. Do i just need to unroot the device and take the ota then reroot.
Related
Just want to verify that I'm getting ready to do this the most efficient way..
I'm currently running a theory ROM and rooted using forever root... should I just use forever root to flash back to stock with root and then go into the stock recovery by powering off the phone and holding down power and volume down then flash the zip in that? Then hopefully I'll still have root and I can reinstall my theory ROM?
Thanks for the help, I'm well versed with other Android phones but this is my first locked boot loader and its making me a little skidish
Disregard on this.. Just grew some balls and I think im good to go (updating right now in stock recovery)..
in case anyone else had the some question.. I found a stock rom in development section but i just decided to use forever root, option 1, which formats back to 886 and re roots.. then i booted into stock recovery and flashed the offical OTA file. its currently booting back up right now so if I have any issues then I will report back but I don't forsee any problems.
Sent from my DROID BIONIC using XDA App
All sorted it seems
I recently reflashed stock 886 from 893 leak after i read some threads about maybe getting the ota but for some reason zumo and lets golf are gone. Any ansewers? I tried to flash the ota anyway through stock recovery and i get the error message tmp/sideload/package.zip error. I know that having the leaked kernel could keep me from doing the ota but any ansewers would help. Thanks!
just flash the system file from the fxz and they will come back. strange that didnt come back before when you flashed.
Yeah thats what i thought. The only thing is that ive had trouble with the fxz. I cant ever get it to work properly. It never makes it past the first step. Ill keep on tryn and see. Released always leaves them out. Thanks for the info!
OK it's been a while and I have screwed up some stuff.
I have the att note 3 and I"m rooted running 4.3 build NB4. I had some stuff frozen and xposed things setup. Been running fine and really haven't messed with anything for 6-7 months. I'm selling the phone and told the person buying it I would leave it on 4.3 stock rooted.
So I just did a factory reset / wipe cache. Now when it boots up I get a samsung keyboard force close error and can't do anything until I change to something else. I figure there will be other issues also, I realize now I should have undone things, but it's to late.
So what do people recommend. My first thought was to somehow flash the NB4 files, but i don't have custom recovery.
So any suggestions, steps or files would be much appreciated.
Can you not just odin to reflash it back to stock 4.3?
Maybe but i cant locate the files to odin and im not that famaliar with how to use odin. Can some provide a liitle guidance.
cd23murray said:
OK it's been a while and I have screwed up some stuff.
I have the att note 3 and I"m rooted running 4.3 build NB4. I had some stuff frozen and xposed things setup. Been running fine and really haven't messed with anything for 6-7 months. I'm selling the phone and told the person buying it I would leave it on 4.3 stock rooted.
So I just did a factory reset / wipe cache. Now when it boots up I get a samsung keyboard force close error and can't do anything until I change to something else. I figure there will be other issues also, I realize now I should have undone things, but it's to late.
So what do people recommend. My first thought was to somehow flash the NB4 files, but i don't have custom recovery.
So any suggestions, steps or files would be much appreciated.
Click to expand...
Click to collapse
I don't think you will find it NB4 build for odin. I was looking for firmware for some time and had no success. You need to get back to NI9 than find update NI9 to MJ5 and then MJ5 to NB4. So i will suggest find this updates so you can sideload after you get stock NI9. and i think you have all files you need to do this here : http://forum.xda-developers.com/showpost.php?p=51468226&postcount=10
They told me that there are definite plans to update the flex with lollipop.
Now as it seems there us no real android development for this on XDA, I'm wondering how I get my stock recovery back so I can take the OTA update when it finally comes. I'm running TWRP recovery now. I tried hard resetting the device already to no avail. I'm using the T-Mobile d959 flex if that helps
I've also heard similar news. Any info on this?
I was stuck on JB for months after KK came out, just did back to stock method, took all otas the re-rooted.
I'm pretty sure if the flex gets lolly then it would least get root lol.
But I'll prob have the flex 2 by then
Sent from my LG-LS995 using XDA Free mobile app
I took all the OTA's while rooted and with TWRP. The OTA's even used TWRP to update. Lmao. Found this out on accident but once it did the first update from D95920h to D95920m I went ahead and gave the D95920s update a shot. It worked to. But it would not do it from 4.2.2 to 4.4.2. So it may not going up android versions I.e. 5.0.2 lollipop. So if you want the stock recovery. Just use any of the flash back to stock threads. I'd use the "D'fuse's downgrade and flash back to stock the easy way" This way reflashes all partitions so everything will be back to stock out of the box. With stock factory reset / recovery if you will.
Personally I'll just plug up to my PC with PC suite and use the restore upgrade errors method I've been preaching about on here. If it due for the lollipop upgrade it'll do that automatically. Meaning it'll wipe all partitions and flash the latest update / version out for the flex. No worries
Here is the problem.
I updated my xt1058 to 5.0.1 , so my bootloader was updated to the 30.BC version. It still is unlocked and I've TWRP installed too working good. After the update, a few days later using the stock rom, my phone got stuck on a bootloop, even after I wiped everything using TWRP the bootloop continued. In order to continue using the phone I installled the official CM12.1 rom over the stock, did all the wipes and then I could boot and use the phone.
My problem is that CM12.1 isn't fully functional yet, and I get random reboots, signal loss, and some apps crashes the phone and I really wish to come back to stock rom since I miss some stock features. There is a way to do this or I have to wait for a 5.0.1 SBF appear? And there is really no way to go back to stock 4.4.4 because the bootloader update right?
Thanks in advance for the help!
There may be ways that some will suggest using part from one rom, and parts from another... HOWEVER while that might give you what appears to be a "working phone" you may find some features not working, or some bugs that weren't there before because you have mismatched "parts" on your phone. And you will be at great risk for bricking your phone should you take an OTA in the future.
And yes, there is no 100% safe, and "will never brick" way to downgrade, even with an unlocked bootloader. It is why I spent the time writing this -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 (which includes a collection of links to threads where people did brick trying to downgrade)
At this point, if you don't want to risk bricking your phone, and want to SAFELY get back to a Stock Motorola ROM, you need to wait until we see a leak of the Stock Moto SBF that is the same or newer build than the last update you flashed on your phone. It will bring all parts/pieces of your phone back into line.
So I'll have to wait the SBF, hope it doesn't take too long!
Thanks for the help.
blueflyingllama said:
So I'll have to wait the SBF, hope it doesn't take too long!
Thanks for the help.
Click to expand...
Click to collapse
It takes as long as it takes...
You wont see a 5.1 SBF util sometime after 5.1 starts pushing to ALL PHONES on all carriers, Moto has posted the Developer Images on their web site anywhere from a few weeks to a few months after the OTA update has been pushed. For all other carriers, since MOTO doesn't post/publish them, we are at the mercy of someone on the inside grabbing them and leaking them, so there is no telling how long that might take, and if it will definitely happen.