Good day all
I bought this device from a seller of eBay (from USA), I am in South Africa
I had to network unlock this device, and it all ran perfect, no issues whatsoever
Recently I have noticed my device doing random reboots, once every day(literally), it will reboot when I take it off from charging or when I press pwer button to wake up. After reboot, it will show the Glowing Samsung Logo, and just stay there continueously.
To fix this, I need to do a factory reset, or just clear the Data partition then it works fine again.
This happens at random, so every day I need to reinstall all the apps, it is such a pain, and obviously something is wrong...
Device: Samsung Galaxy Note LTE (i717)
ROM: Blackstar Blackjelly 4.1.2
Baseband: I717 UCMD3
Recovery: TWRP (latest v.)
Just for the record, ,it all started happening recently, the first time it happened, I was browsing 9gag using the app, then my device rebooted in my hand while scrolling, agter going to recovery, my sdcard and internal sdcard has been formated, and all internal partitions has been formated to....
I have no idea what is causing this but I am pretty sure it is not the rom, since I have had this rom for a while now...
What kernel do you use, and can you take a logcat?
(To take a logcat, enable ADB, plug in your device to your computer, and run adb logcat from the Android SDK. You can grab that here: http://developer.android.com/sdk/index.html?hl=sk )
BachMinuetInG said:
What kernel do you use, and can you take a logcat?
(To take a logcat, enable ADB, plug in your device to your computer, and run adb logcat from the Android SDK. You can grab that here: http://developer.android.com/sdk/index.html?hl=sk )
Click to expand...
Click to collapse
after running the logcat with "
Code:
adb logcat > logcat.txt
" for just more than 2 hours, i stopped it...it is 1250kb, see attached, it is compresssed in a zip file
p.s. Im quite positive it shouldnt take that long
any help would really help!!!
Related
I've had Cyanogenmod 9 nightlies on my SGS2 since April. I didn't install every single one, but pretty much only those with good ratings, specifically those that had no complains about battery drain and heating...
Currently on the 06-28-2012 nightly. This ran fine at first, but over time, it started to occasionally crash into Kernel Panic. I figured I'd just pick a new nightly, but then I ended up having to travel and installation of a new nightly got delayed.
Now I'm home, and I can't use the phone at all, cause it crashes into Kernel Panic almost as soon as I unlock the screen after Android finishes booting. The last thing I see up in the message bar is "WhatsApp error" and the screen goes dark. It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
I don't think its a problem with WhatsApp, cause WhatsApp used to run fine, while Kernel Panics originally mainly seemed to happen after I got a "storage full" message. In response, I deleted a load of pictures after rebooting, to make sure there's free space, but it kept crashing occasionally, till now, its just unusable.
I've tried to flash a stock Samsung ROM (I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar.md5) but that hasn't been working either.
Kies drivers are installed on my Laptop. Odin sees the phone too.
I followed the instructions from the rom page, changed no settings in Odin, just picked PDA and selected the ROM.
Odin goes "Added" when I plug in the phone, verifies the ROM, then the whole thing hangs on "setting up connection"
So I unplug, pull the battery and then reboot, which works fine, but once booted, it won't stay on longer than a few seconds.
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Tsais said:
It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
<snip>
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Click to expand...
Click to collapse
What's preventing you from factory resetting from recovery?
Lack of knowledge is preventing me!
How do you factory reset from the "Kernel Panic Download Mode"...?
Download Android Commander from here:
http://androidcommander.com/
Boot your phone, don't unlock.
Start Android Commander, navigate to /data/apps and delete WhatsApp's apk (com.whatsapp1.apk or something like that) or rename it to .apk.bak
Restart your phone without unlocking.
Hope the errors gone.
Here is an attempt to provide a definitive answer to what to do if your phone has the Bluetooth/Wifi hardware failure.
Note that some of the links don't seem to work with the xda-developer app or the Atrix built in browser. Please blame motorola, not me
Symptoms:
1) If your phone was set to try to use Wifi by default on boot:
Your phone boots into the OS but shortly afterwards freezes and reboots - and again and again.
2) If your phone boots with Wifi turned off:
Your phone boots into the OS and a few seconds after you enable the Wifi in settings or via a widget it shows "Error" and sometimes the phone reboots shortly afterwards. Bluetooth simply fails to work.
If you have warranty return it for a repair. If not the best you can get is to disable the Wifi and Bluetooth so the phone doesn't reboot and can be used with mobile data. Instructions for both are below:
Be sure it is the Bluetooth / Wifi hardware failure:
1) Are you running a custom ROM? - if yes go to 1.1, if no goto 2.
1.1) Reboot into recovery and make a backup.
1.2) Remove your SD card.
1.3) Reflash using RSD to stock - remember to get the right one for the right country!
Get RSD and drivers here:
http://forum.xda-developers.com/showthread.php?t=1136261
Search for your stock firmware using google
Use RSD to install the stock firmware file which will replace the bootloader, recovery and radio - takes about 20 minutes.
Goto 2.
2) Reboot into Stock Android Recovery and reset to factory defaults
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/60620
2.1) Reboot to Android and try enabling wifi from settings - if it reports "Error" after a few seconds and your phone may reboot shortly afterwards it is the hardware fault. Proceed to 3.
3) Check your remaining warranty here:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/82507/p/30,6720,7898
Bottom left - enter your IMEI.
Warranty left goto 3.1 else goto 4.
3.1) Return to Motorola for repair - be sure you flashed back to stock first using instructions in 1.3
4) Unpalatable options are all that is left. Either pay or do without Wi-Fi and Bluetooth. Have money and the desire to fix your Atrix ($110 in the USA)? Goto 4.1 else 5
4.1) Consider paying Motorola to repair the phone anyway. Schedule a repair here https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/82507/p/30,6720,7898
5) This is a complex process. Google is your friend. Unlock your phone using the instructions below. Note you have no warranty to lose (see 3)!
http://forum.xda-developers.com/showthread.php?t=1136261
5.1) Install romracers CWM custom recovery using moto-fastboot (or Android fastboot):
http://forum.xda-developers.com/showthread.php?t=1204500
5.2) Did you take a backup earlier? If yes go to 5.3. If no goto 6.
5.3) Reboot into CWM recovery and restore your backup. Note if you are stuck in a bootloop this will be ok in a bit. Goto 7.
6) Install your favourite ROM using CWM recovery from a SDCARD or by moto-fastboot. Goto 7.
7) Reboot into CWM recovery
7.1) Plug your phone into your PC (you might have to wait for the driver to enumerate the phone first)
7.2) Find or install adb on your computer (hint - it comes with the Android SDK and platform tools from earlier):
adb shell
mount /system
cd /system/lib/modules
mv dhd.ko dhd.ko2
reboot
8) When you install a new ROM or kernel goto 7. Every time.
This little setup moves the driver linux needs to try to talk to the wifi/bluetooth chip which has failed so it can't find it. If it can't find it then it doesn't try to talk to the dead Broadcom Bluetooth Wifi chip that prevents the reboot cycle happening.
The fix was pioneered by:
mvniekerk
http://forum.xda-developers.com/member.php?u=2353874
So go thank him!
In the hopes this helps,
Matthew
Good job. Well said.
Considering how many posts I have seen after posting this solution perhaps it could be sticky?
I promise to maintain it.
Matthew
Sent from my MB860 using xda app-developers app
Hmmm
I think I have done that correctly and flashed the 2.8 Neutrino GT. There was no reboot up to now. But I want to ask if there is a fix for WIFI 'ERROR' and BLUETOOTH error without 'ERROR' message?
Guys please. I can try anything I don't want to lose my phone Warranty is over. How can I find the Broadcom BCM4329 wireless and bluetooth chipset for atrix? So I can find a technician to change it with mine.
If you have the failure there isn't much to be done.
Ifixit has a teardown but the chip is a very small ball grid type thing which will be very hard to fix.
What are your symptoms precisely?
Sent from my MB860 using xda app-developers app
mattaw2001 said:
If you have the failure there isn't much to be done.
Ifixit has a teardown but the chip is a very small ball grid type thing which will be very hard to fix.
What are your symptoms precisely?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
When I click on 'Turn on Wifi' button, It says 'Turning on Wifi' for 10 seconds and then 'Error' message comes up under the Wifi button and when I click on 'turn on bluetooth' it says 'turning on' but does not turn on. Same as wifi but without the 'error' message.
How can I fix this? I can't use wifi and bluetooth!
Nothing to be done. There is some discussion as to why but a chip in your phone made by broadcom which handles both wifi and Bluetooth has failed.
Short of replacing it requiring sophisticated soldering tools you are stuck. See the $110 Motorola warranty repair.
Sorry,
Matthew
Sent from my MB860 using xda app-developers app
Im stuck.
I have applied the fix to NottachTrix4G rom. I still have the random reboots. I really need help.
Do you get the wifi error message or not?
Secondly does this happen with the normal, stock Motorola rom?
Matthew
Sent from my MB860 using xda app-developers app
When i check wifi does show error. I have not tried the stock moto rom yet.
The best thing to do is return to stock and do a factory reset
Carry out a full backup first (nandroid or using CWM recovery).
The best thing to do is return the atrix to stock and then do a factory rest.
If the problem persists then it is a hardware problem and you can now return it under warranty without them knowing (see the thread for instructions).
Otherwise you seem rather stuck. Perhaps buy an atrix with a smashed screen and transfer the motherboard?
Matthew
Noattachtrix rom was good, but not good enough.
little_man_3666 said:
I have applied the fix to NottachTrix4G rom. I still have the random reboots. I really need help.
Click to expand...
Click to collapse
I ended up using RomGb instead and that fix the bootloop after using NottachTrix4G Rom.
This happened to me Saturday November 17, 2012. Rebooting did not help. Did my searches and found this thread - and was bummed to read that it is due to a hardware issue. Fortunately, I persisted. With the WiFi widget endlessly spinning, I tried the Bluetooth, which would just fail and go to an off state. I elected to do a force close on any running applications one by one, testing Bluetooth after each. I found that BlueTooth and WiFi functionality would come back after force closing some apps. I stupidly left WiFi on and rebooted the phone - this put me in an endless reboot cycle. In the midst of one I managed to enable car dock mode which I have configured to disable WiFi and this got me out of the loop. I found my issue, which has the same symptoms as the above, was caused by a recent update to WeatherBug Elite. I uninstalled the program, and am back to normal operation. Hope this helps others.
Update - it appears my problems continue. Although I can now access BT & WiFi, the problem will re-occur. Force closing Weather version 2.2.2 usually will clear the issue, but I have had a good working WiFi sessions halt to Error. Still gotta think it's software rather than hardware.
Thanks I thought it was the ROM until I found this thread
Well, I was wrong. The issue is hardware not software. In my case pressing the volume down button would change the behavior sometimes, like get bluetooth to work, press volume down it stops or vice versa. Time for a replacement.
I mount the system successfully but when I type cd /system/lib/modules I get it cant find the directory, Please help. I need to do this to stop reboot!!
Definitely Software
I have atrix 4g. Running MROM 2013 2 13. I have the error on WIFI and NO Bluetooth. No reboot, but I rarely use the wifi enough to leave it on(conserve the batt). This is a software issue as far as I can tell as well.. I can fix it by killing the mrom service in "manage applications". If I get a chance I will look further but this seems like enough of a fix to not care.. MROM is pretty great besides this issue.(which appears to happen on multiple roms. My guess would be that it started with CM, but only because that is what the roms are based off of that get the problem.
bubba1993 said:
I mount the system successfully but when I type cd /system/lib/modules I get it cant find the directory, Please help. I need to do this to stop reboot!!
Click to expand...
Click to collapse
Having the same issue. Wifi died after the phone fell off my hands. I had the CM10 ROM by ephinter and everything worked great except the wifi (no reboots). Then I had the AMAZING idea of installing a new ROM and the reboot loop started. EIther with any stock or custom ROM it continues to happen. Tried everything without success.
Have anyone tried disabling wifi in the settings.sqlite and see what happens?
jaunis I found out why mine was doing the boot loop and it is funny but very weird. I wiped the phone and put my cm7 back on there and forgot to activate my gmail account or any account for that case. Now I have been running it with no problems for 40 hours. But of course still no wifi. I am fine with that. but at least I am not dealing with the reboots.
I have an unlocked AT&T Atrix 4G with a custom ROM (Cyan 9.x & ICS 4.x). I started having WiFi issues where the device would reboot anytime I tried to enable the WiFi. This all started at least 6mo after installing the custom rom so I dont think its software related. To try and fix the issue I tried doing a data wipe factory reset, at this point I couldn't get past the welcome screen because WiFi didn't work and I dont have a SIM in the phone (my kid has been using it for games). So from here I decided to try and flash the phone back to stock using RSD Lite;
Be sure it is the Bluetooth / Wifi hardware failure:
1) Are you running a custom ROM? - if yes go to 1.1, if no goto 2.
1.1) Reboot into recovery and make a backup.
1.2) Remove your SD card.
1.3) Reflash using RSD to stock - remember to get the right one for the right country!
Get RSD and drivers here:
http://forum.xda-developers.com/showthread.php?t=1136261
Search for your stock firmware using google
Use RSD to install the stock firmware file which will replace the bootloader, recovery and radio - takes about 20 minutes.
Goto 2.
2) Reboot into Stock Android Recovery and reset to factory defaults
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/60620
Click to expand...
Click to collapse
I downloaded the AT&T 2.3.4 / 4.5.91 Service SBF which looks like this in RSDLite: 1ff-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-att-us-gas_na_olpsgbattspe_p011.sbf
I started the flash and left my phone for 15m or so to do its thing. When I came back my phone was boot looping (shown in a video here: http://youtu.be/V9wtBNEWRPQ ).
I can't do a factory reset from Stock Android Recovery (step 2 above), I can't get the menu for it. Now what do I do? Did I grab the wrong SBF file? Currently the only place I can grab SBF files at is here: http://www.das8nt.com/sbffiles.html
Hi everyone:
I am attempting to boot AOSP 4.0.4 (r1) for the Galaxy Tab 10.1 wifi (GT-P7510). I have merged pershoot's CM9 3.1.10 kernel and been able to get through a few errors noticed in last_kmsg. However, I'm trying to figure out why servicemanager is now crashing and can't seem to get a hold of a logcat. I must be doing something stupidly simple incorrectly...have searched high and low and every example I have seen of someone complaining of a servicemanager crash with the same output has a logcat to provide.
Basically what's happening is I try to boot, see the Samsung Galaxy Tab logo, it sits for about 20 seconds and then auto-reboots back into recovery after the 4th servicemanager crash.
I edited the init.rc to increase loglevel to 8 which is showing me more detail, but not enough. I've attached my last_kmsg, init.rc and init.p3.rc to this thread in a zip file.
Here's what I'm doing to try and pull logcat:
1) Boot into recovery, wipe my device, install my rom/kernel + gapps
2) Run "adb logcat -v long > logcat.txt". I get the obvious "-waiting for device-" message
3) Attach device to computer
4) Reboot device and wait
When the device goes back into recovery after the failed boot, I check the output file and it's empty. What dumb thing am I forgetting? Or is it legit that the system is just not getting far enough into the boot sequence to start adbd?
Thanks all very much in advance for any assistance you can provide.
Never mind, worked it out on my own.
Sent from my Infamous Tab.
Yesterday I updated a nightly build (cm-13.0-20151222-NIGHTLY-mako.zip) and unfortunately the phone began to show a series of problems (ouldn't make calls,couldn't access the contacts,...).
Reading on the internet i found many people suggesting to downgrade to a working build, so i downloaded the last one that was working on my phone (3 days earlier 12/19): the nightmare began!
After the boot, the phone (nexus 4) shows repeatedly "Unfortunately the process com.android.phone has stopped" and when i click on "ok" it just pops up again and again, until it automatically reboots, and the whole thing goes on for ever.
If i don't touch the phone it reboots automatically until the batteries are completely dead.
I have tried to adb push from bootloader but the terminal (from ubuntu) hangs there without signs of life. If i open nautilus and I try to copy the new build, my ubuntu freezes, only the mouse works without any use.
Is there a way to miraculously solve this problem?
shared_joy said:
Yesterday I updated a nightly build (cm-13.0-20151222-NIGHTLY-mako.zip) and unfortunately the phone began to show a series of problems (ouldn't make calls,couldn't access the contacts,...).
Reading on the internet i found many people suggesting to downgrade to a working build, so i downloaded the last one that was working on my phone (3 days earlier 12/19): the nightmare began!
After the boot, the phone (nexus 4) shows repeatedly "Unfortunately the process com.android.phone has stopped" and when i click on "ok" it just pops up again and again, until it automatically reboots, and the whole thing goes on for ever.
If i don't touch the phone it reboots automatically until the batteries are completely dead.
I have tried to adb push from bootloader but the terminal (from ubuntu) hangs there without signs of life. If i open nautilus and I try to copy the new build, my ubuntu freezes, only the mouse works without any use.
Is there a way to miraculously solve this problem?
Click to expand...
Click to collapse
use fastboot to manually flash the stock partitions, then it will be clean stock, and you can start over.
search google for how to setup fastboot on your linux machine if you dont know how, i cant help with that.
[email protected],
just bought myself an Ulefone T1 from aliexpress and I am wondering if there is any lineageos development out there for this phone? Is anybody planning to develop for this?
cheers
JohnnyT
Stay tunned. The phone is new and development will yet. Dont worry is a great phone and Ulefone is better than yesterday.
https://www.needrom.com/category/ulefone/t1-ulefone/
It will hardly receive official updates, let alone custom ROMs (same fate as the 96% of MediaTek devices out there).
any update . i just bought this phone from banggood. my asus zenfone 3 wifi is failing. so needed something to fill the gap
Finally received my t1 after 11 weeks of waiting!!
Everything works fine apart from the battery usage which is a round 10% per hour on standby with no usage!!
FOLLOW-UP
Following lots of research found that Whatsapp was still trying to verify the phone thru SMS and was draining the battery. Uninstalled and re-installed Whatsapp and verified by manually entering SMS pin.
Now appears to running okay at just over 2% per hour battery drain with bluetooth and GPS set on.
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
I am very happy with my T1. High performance, loads of RAM and storage in a decent looking dual SIM package for a very reasonable price tag. First official OTA update yesterday. Also there are rumors about 8.0 upgrade till end of the year.
JohnnyT
Alicklee said:
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
Click to expand...
Click to collapse
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Pickles871 said:
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Click to expand...
Click to collapse
Do you have yours rooted and your bootloader unlocked? I am getting the update prompt but being unlocked and rooted I'm not sure it will take the update. Some phones tend to brick. Also all of a sudden I am having an issue with "android process.media has stopped" Can't figure out what's causing it but since it started the device has become quite laggy
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
by any chance any of you have gps problems in waze or maps????
Pickles871 said:
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
Click to expand...
Click to collapse
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
nieXas said:
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
Click to expand...
Click to collapse
Thats useful to know. Many thanks
Made Lineage 14.1 work on my Ulefone T1 (adb shell hacked)
Hi everyone,
i've been digging around for the last few weeks on my T1 and now i've finally made it boot. I dont know exactly what is working and what not but i can tell WLAN is NOT working for now! The kernel repo at my github was not working so i used the stock one. You may download it as well as the TWRP recovery i made alongside the ROM. But you need to wipe /data partition so all user data is lost in the process. Also while TWRP needs a reboot after wiping /data step 2 & 3 may need to be repeated once. For now i was not able to flash and boot the recovery (working on it) but it can be booted into as follows (when booted into the stock system):
UPDATE: Made it work - it's booting without hacking via ADB-Shell. The parts marked --- obsolete --- are not needed any more.
1.) Disable OEM-Lock in Developer-Options (google if necessary how to do that)
2.) Reboot and keep the upper volume button button pressed until it booted into recovery. If the "no command" screen is displayed, press the power and upper volume button together once again and you shuld reside in the stock recovery. Use it to reboot into fastboot (bootloader).
3.) In fastboot mode, while beeing in the same folder as the downloaded files, type the following:
Code:
fastboot boot recovery.img
4.) Wait for TWRP to boot up and enter the following (within the same folder):
Code:
adb push lineage-14.1-*-UNOFFICIAL-t1.zip /sdcard/
5.) Finally you may flash the Lineage zip file in TWRP (if you have wiped your /data partition at least i needed to)
----------------------------------- obsolete -----------------------------------
6.) Let it reboot into system and while displaying the Linage bootanimation (for now) i had to execute a few commands on adb shell. So, with adb installed, you need to enter the following commands in a common linux/windows shell:
adb shell /vendor/bin/nvram_daemon &
adb shell /system/bin/nvram_proximity &
adb shell /vendor/bin/nvram_agent_binder &
adb shell /system/bin/agoldnvram &
adb shell /system/bin/audioserver &
Click to expand...
Click to collapse
I'm not sure if they are all needed but afterwards my T1 bootet up correcty (more or less). Unfortunately a few drivers are missing as it seems while WLAN is not working for now.
http://d0ndroid.janeiskla.de/lineage-14.1-20180928-UNOFFICIAL-t1.zip
and the recovery
http://d0ndroid.janeiskla.de/recovery.img.
----------------------------------- obsolete -----------------------------------
After fixing another few things the only remaining things i found not working are fingerprint & RIL but I'm looking into that right now. The current builds will always be uploaded to:
http://d0ndroid.janeiskla.de/
The sources i used besides the default Lineage ones are on github:
https://github.com/d0n?tab=repositories
Have fun! And let me know if you make progress on your own
Greez,
d0n
Hi d0n22, are you still working with this rom?