After I updated my N7 from 4.4.4 to 5.1.1, it got so slow that it's unusable. Can I go back to 4.4.4 somehow?
Or should I install a custom ROM? And if so, is there a good guide for that?
sure... well... before I say for certain, it all depends on if Google still hosts the AOSP images. I suspect they do. Grab whatever official release you want to fall back on and fastboot install it per their instructions.
Any other feedback anyone?
Hi, I was in the middle of downgrading my N7 from 5.1.1 to 4.4.4
It failed to take the flash and now I can't turn it on, (tried the button thing) also now the PC and adb won't connect. Looking on this forum for someone who knows there way around the N7 and can get my 7" brick back to life. p.s. also tried unplugging the battery trick, no luck here either.
Related
Hello all,
This is yet another bootloop story, although I haven't found anything quite like it yet, hence the idea to post it here for reference and in case some of you have interesting ideas to explore...
This is gonna be a bit long, but TL;DR: After my phone got "spontaneously" stuck into a bootloop, I find that only the stock 4.2.2 rom works, and no other.
So, tuesday I get back home with an empty battery and a Nexus 4 (running latest OTA) that has switched itself of after a day of somehow intense usage. No worries, I plug the AC adapter, let it charge for a bit and switch it back on. Booting seems a bit long, but I have to take care of a few home chores so I let it do its thing before coming back to it a few hours later. Only to find it still displaying the animated nexus logo. After a few switch off/switch on cycles, I understand its pretty stuck and I need to be more radical about it. So I enter the bootloader menu, and OEM unlock the phone (I had never needed to do that) hoping the full wipe associated with that will clear things up.
Well, it didn't. So I guess I'll need to flash a stock rom, and so I do. Since 4.4 is available on Google's stock roms page I try that, the animated logo changes but the end result is the same. So I try again with the latest JB (4.3) and still the same result. I get more than a bit frustrated but it's late and I need some sleep.
The next day, I call Google's warranty desk in France. They tell me that since the phone fell a few month ago, they cannot take it under the warranty program, and so I have to ask LG. Knowing there's no reasoning that will get me past the clerk that answered the phone I hang up after saying I'll get back to them via snail mail. Which I'll probably do soon, because I'm very disappointed with the way that warranty desk works.
Once at work, everytime I have a few spare minutes, I try to reflash with a new tool just in case it does more than automate what I did manually (nexus root toolkit being the one I tried most). It doesn't change a thing and my phone is still a nice animated paperweight.
I don't know why I ended up trying that, but I finally tried flashing the original 4.2.2 rom, and lo and behold, my phone finally got to the SIM code screen ! Everything worked nice after that, so once back at home, I go for the offered OTA upgrade to 4.3. Well, guess what, back to paperweight. Before reflashing 4.2.2, I took the time to flash CWM and activate adb by modifying /system/build.prop in the 4.3 image. This showed a recurrent problem with "system_server" segfaulting at launch (and it might have been caused by hal_sensors_get_list not returning anything, I have no clue). Trying the same on 4.4 yielded the same result.
Back to 4.2.2 and everything works fine, but I get nagged by the OTA notification, and more than that I'm wondering if there's any hope I might understand and fix the problem with my phone.
So, ladies and gentlemen, any clue that would help me is very welcome !
I plan to try a CM rom this week-end to see if it has the same problems as the stock one, but I have little confidence it doesn't. My guess is I have a hardware problem that's non-critical except it triggers a bug in 4.3+...
Thanks for reading !
--
Alain Perry
Same case, mi phone is totally stock and stuck on logo
KRT16S: no luck
I only had the time to try KRT16S this week-end, and this latest update doesn't change a thing. Same symptoms. So I guess I'm stuck on JB 4.2 for the coming week...
This all started with the 4.4.4 update, I had dead keys, no notifications coming in, just various problems. My nexus is /was rooted and running CM11. I wanted to go back 4.4.2 since it was fully functional, tried flashing back to 4.4.2 and my settings said it was 4.4.2 but it still had all the same problems of 4.4.4. I tried to flash back to stock and unroot and now all I get is either the white google screen or the fallen android, but if I try to restart bootloader or restart recovery it just goes back to the fallen android and start at the top. I searched the forums here and google and everything I try doesn't work. I cant get into it to enable usb debugging or anything all I can do is turn it off and on but nothing else.
Im new at this and I don't think I need spoonfed but I sure could use some help. Can anyone help me please
Tim
I have an At&t (though no at&t mobile service currently) Samsung tab 4 8inch. In the last few days it has started freezing SEVERAL times a day. it doesnot matter what app, its likely to freeze on any of them. I would say it probably happens most when Im backing out/exiting an app. When it freezes I can stilll shut screen off but when I turn it back on I am just where it froze -not lock screen, it wont acknowledge plugging charger in, and cant click restart. Touchwiz has stopped message may or may not come up, but I cannot click on it even if it does. The ONLY way I can shut it down then is down vol +power for about 15seconds. Then it restarts and may do it 5 minutes later or 5hours later.
It just started this suddenly. I also had not just installed anything.
If a custom ROM or something would fix it, I wouldnt mind doing that if someone could possibly give me the link(s) to 1 that works for this model and links to how to do so/what I need.
I dont know if it is related or not, but about 3 or 4 days before this started, by battery life & battery charging went suddenly TOTALLY to hell.
Please help me fix this irritating &aggravating problem. Thank you very much for your time &assistance!
There are no custom ROMs for the SM-T337A unfortunately. Is your tablet on KitKat or Lollipop and are you rooted?
You should back up your internal storage and then factory reset and wipe cache in stock recovery. If you are rooted, you should remove system apps that you don't need with titanium backup or something similar. If you are on KitKat you might want to consider either updating to lollipop or factory resetting and reflashing the stock KitKat firmware with Odin.
No im not rooted. However i would like to, but didnt know there was a method of rooting the t337a.
I cant seem to fins out how to find whether its lollipop or kitkat or what?
gdownloads said:
I cant seem to fins out how to find whether its lollipop or kitkat or what?
Click to expand...
Click to collapse
Settings > About device > Android version. If it says 4.4.2 it's kitkat, if it says 5.1.1 it's lollipop
Thanks for the help.
Yes its kitkat then because it says 4.4.2 . I think 1st I'll go ahead and search how to update it to Lollipop then go from there... Does that sound like a wise decision to you??
STOOPID Question: I went to the posts at bottom of your posts (granted, I didnt go thru all 59 pages, lol) but I have a brain-fart question... would I try to root and then update to lollipop or vice-versa??
I have found temp root for lollipop. Just look in the general section. As you wouldn't be able to ota lollipop while rooted anyways.
Just got the OTA update for nougat, every time I go to install it my phone crashes and switches off.
Anyone else having this problem?
Also, how to I flash stock recovery, I think it's to do with that STUPID twrp recovery that doesn't even work.
Megacamz said:
Just got the OTA update for nougat, every time I go to install it my phone crashes and switches off.
Anyone else having this problem?
Also, how to I flash stock recovery, I think it's to do with that STUPID twrp recovery that doesn't even work.
Click to expand...
Click to collapse
You need to flash back stock recovery. You can NOT update OTA updates when you have TWRP, it will crash, just what happened to you.
Use SPFT and flash back stock recovery for the current rom you are on. You can extract it from the scatter file. (If you don't know what that is, GOOGLE IT!!!!!!!!!!!!!!!!!!!!!!)
Btw I would avoid the update for now. It's buggy to say the least and you will loose fast charging.
Yea this OTA still needs improvement. Fast charging gone, fingerprint STILL not working, battery drain. Practically, latest Marshmallow is better then this OTA.I regret upgrading. If you gonna need downgrade use SPFT, their is a simple guide in umi community.
I did install iit and now I can not phone out or receive a call on Bluetooth phone Buzzzes loudly and the net work closes out, I use the bluetooth because of my hearing aids as the volume of the UMI super isn't very loud. I don't know how to fix this short of resetting back to origional except that way I loose all my info and have to start again. waiting for an answer.
Hello,
I want to know if it is possible to root the stock rom, and keep OTA.
Actually, my objective is to use screen mirroring (miracast), and I heard rooted devices can achieve that by changing build.prop. I didn't want to switch from stock rom, since I like it and like updating OTA.
Maybe if I adb boot twrp and install supersu, but keep regular revovery, I can still get OTA?
If there's another solution to screen mirroring, I'd be glad to know, too.
Thanks in advance!
I've tried to root stock rom and keep the system unmodified through Magisk. For whatever reason OTA always fails even though I have stock recovery, supposedly unmodified system, and rolling back to stock boot image prior to trying the OTA.
The only thing that works is to flash the stock firmware and then taking OTA. The only problem is that the stock firmware is tough to come by, but I read that someone got their hands on the latest 93-10 firmware image. So that's good.
I've since moved onto Pixel Experience 8.1 rom without any regrets. The camera works really well and battery is nearly up to par with stock Nougat.
No, unfortunately these things still modify the the system and boot partition and the upgrade script knows it and causes the update to fail. We don't know exactly everything the OTA update scripts check (it's not just a simple text file) but it is obviously something that it knows you are rooted even when nothing else does. :/
You must be completely stock to take an OTA update... the only exception is your bootloader lock state doesn't matter at this time, we do know that it is capable of detecting that as well.
I have done that and I got Bootloop! So don't Try!
else
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175