Hi All,
was very happy with P2 and decided to go for Nougat update, phone was great, no issue after, no errors, I was impressed, then updated to 233, and again phone was just fine, battery life was even better, Bluetooth was working better, very happy, but after one week phone gone crazy, sim management, android system and media keep eating battery, tried wipe cache in recovery, no help, decided to do hard reset, no help, but now phone can't find any music on sd card, and even better, there in no any tones, alarms, anything left on the phone, any advise please?? many thanks..
I'm sorry this happened to you. Did you do a hard reset after upgrading to s233?
Hard reset on this model basically means you wiped the whole internal memory clean. Are you sure the phone is supposed to find any files when it's not?
Yes, I done it, tried reflash 232 but always fail on 50%, when I reflash 233 let me do it, but is only small ota 78mb, not changing anything, and factory reset again, not repairing anything..
You're on custom ROM? I've read about the SIM-managment drain on some of them.
NO, I am on stock Nougat Rom S232 and had OTA update S233, and after week phone for some reason gone crazy, and I am trying to work out why, and if someone somwhere got Full S233 rom, not just OTA, which I could reflash in Lenovo recovery...
When I reinstalled full stock S233 , and problem was fixed, it must be something with sd card, and I finded problem, it was corrupted photos and video file on sd card. all back to normal SOT 12-13 hour per charge..
i had no issues what so ever as i wiped everything before and after the update if you look on the forum there is a way to downgrade to mm (thats what i think you should do then wipe everything hard reset through recovery) leave your device for a couple days then re-upgrade to N do another wipe through the recovery option and it should fix any issues (i know its a lot of hastle but its the best way to stop issues)
Related
Hi,
Im really hoping someone can help me here.
Yesterday my phone threw a wobbly and started to loop boot to the htc logo, it had happened before but i payed little attention. When i removed the battery to reset it i found that it had corrupted my whole sd card, stange file names etc was everywhere.
i decided it was time for a clean start and super wiped the lot then installed arhd,
everything went fine until i went to use bluetooth, nothing i say or do will enable it.
Ive since have wiped and flashed leedroid, arhd, and runny but cant get this little but one of the most used features on my phone to activate.
Ive also reflashed the radio, does it sound like a hard ware failure to you guys?
is there anything that i could have missed, i would also like to add that i havent re installed any previous apps etc and bluetooth still fails to activate.
thanks
sorry to reply to my own thread, but i think i just worked it out. After reading my own post i though about the sd card, i decided to remove the card and reboot, voilia!! the bluetooth is now functioning!!, totally confused now as to why an sd card can affect the running of a seperate piece of hardware!!
ok, it happened again a few time since i posted this thread.
it happened again yesterday and no matter what i done it wouldnt come back.
So i decided to do a nandroid backup and wipe, install a new rom then recover my nandroid backup.
this solved the problem, im not sure what is causing the bluetooth to just die like it does but now i have to keep another rom on my card and a nandroid back up just to get the bluetooth to work- seems strange as the backup is the same drivers etc and stops working. must be hardware...
this dosnt seem to be rom specific as well as its happened now on leedroid, runny, 3dmix, and anotherone i forget the name.
roll on htc edge as im pretty sure i may have a impending hardware failure on the bluetooth radio
Short version:
Use CWM or TWRP to (1) format sdcard, (2) erase dalvik cache, (3) erase cache and (4) factory reset. This seems to resolve at least one source of random reboots. If installing a new ROM, do that first and then followed by the four steps, then boot into the new ROM. Step (1) may be the important one (in which case it might, in principle, be possible to solve the problem while saving userdata), but I don't know.
UPDATE: It was working fine and I had to spoil it all by installing MIUI, just for kicks. Now, the old problem is back and the solution above doesn't seem to work. Looks like this is not a completely reliable solution...
* * * * *
Long version:
My wife's GNex was in a very bad way. It is entirely stable in Android 4.0.2. But if either upgraded or flashed to anything else, will randomly reboot. Actually, it's not even that random--it will reboot on its own within a couple of minutes of idle with the screen off. I tried all sorts of things--flashed different ROMs, radios, etc.--factory reset multiple times. Googling turns up lots of chatter about random reboots but little by way of viable solution. I figured that the problem may be hardware related. But all Samsung's servicing did for me is to return the unit to 4.0.2. At that time, 4.0.4 was just released and the local servicing centre hadn't even received their copy of the ROM (for yakjuwx). In the end, I 'solved' the problem by rooting and disabling the OTA update notification. (My wife wasn't bothered by the fact that she wasn't running the latest Android version. And the phone works fine in 4.0.2 otherwise.) Work and life caught up and I didn't think much of the matter after that.
That was about a year ago.
Recently, I migrated my wife to a brand new GNex, and took the opportunity to try my hand at solving the problem again. I flashed the latest 4.3 ROM, the latest stable CM10.1, Paranoidandroid, etc. But no matter what I tried, somehow, the phone is stable only with Android 4.0.2 (ICL53F). A chance find online mentioned something about data corruption on the sdcard as a source of problem, and that the usual factory reset doesn't actually reformat the sdcard (it only marks it as empty). Putting 1 and 1 together, I used CWM to do the things listed above (see "short version") and now, the phone is running stock 4.3 (JWR66V), stable CM10.1 and Paranoidandroid without random reboots so far. So now, I am a happy camper, though with one extra, fully functional white GNex.
Footnote: If you don't understand what I said in the short version, it's best you don't try doing anything yourself without first reading up on fastboot commands. This is one place to start. I am not responsible for anyone bricking their device fooling around.
Thanks for reading.
Update to my adventure.
Just about resigned to the fact that the phone is back to its old ways. The old tricks no longer work. What happened next?
1. Left off for more than a day (I gave up).
2. Installed AOSPA PARANOIDANDROID 3.96--using CWM, installed ROM, GApps, wipe dalvik, wipe cache, format sdcard.
Weirdly, the phone now seems fine. It hasn't rebooted by itself after 30+min in sleep. The old problem was that it will invariably reboot by itself in within 2 minutes from screen off so even if there are other problems, the old one is not there anyway.
Something in the steps above seems to have made a difference.
Still monitoring.
I have read around regarding this problem without luck, and hope that someone can advise if I have missed anything.
I used to use this phone and as I liked to tweak it was running a custom rom (think it was Wanams). Anyway I got an upgrade ages ago, and my wife carried on using the phone for a while. As she just needs a standard rom I recently decided to factory reset and use Odin to flash the newest stock rom (N7100XXUFNE1 - UK). This is when the problems started. Initially the Wifi wouldn't come on, but after factory resetting and using the Samsung Updater in Kies I finally managed to get Wifi back. Then, while setting it up and installing apps from the Play store it started freezing and had to be rebooted every 5 or 10 mins. Finally after doing this a couple of times, all the apps were installed and after leaving it to "settle" it seemed to be better. Now however, 2 or 3 times a day, when playing games or using other apps, it will just reboot.
What I have tried is:
* I have tried clearing cache through the stock recovery
* Tried a number of Factory Resets
* After reading about the SDS problem I have tried running the "dummy file generator" to fill the internal memory and this completes ok. I guess this means that although I have memory that is/was susceptible I applied the original SDS fix early enough with the custom rom that all the memory is still ok?
As I have the newest bootloader I can't downgrade that, but as I don't care about triggering Knox I was thinking of rooting and installing a custom rom to see if any of the other Kernels help?
Has anyone got any idea's what could be causing this and what I can do to fix it?
Thanks.
Hello,
It seems that my G925T has some problems with soft reboots. I don't know exactly what the problem might be, maybe you can help me troubleshot.
So I have followed up all the things a normal user might do like:
soft reset, hard reset, odin stock rom flashing, smart switch disaster recovery, disabling certain apps, going to safe mode, cleaning cache, resetting cache and dalvik, but nothing. Flashing a different custom rom, custom kernel but still problem remains.
Even after following up with all these steps, my phone still reboots unexpectedly while I use it and even i don't use it. An average is that my phone gets these unexpected reboots like everyday. Maybe 3 time a day, or maybe next day. It seems like soft reboot.
For an some addition information my phone is IMEI repair, but everything is fine, i can get updates as i am currently on the official stock ROM.
Currently I am on latest update DOJC.
What do you think it might be the problem ?
Has soft reboots to do with IMEI repair ?
Is there anyway i can troubleshot this ?
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!