Hi,
There's something weird with CMupdater. It runs pretty good but the same problem occured to me twice so I'm documenting it as someone may help me.
I was in Nighlty build 20130103.
I wanted to upgrade to the nightly build 20130105. Then I've been to CMupdater in the settings and ask to download. There was a progress bar that was not making any progress at all. In fact, it was like if my phone was stuck in the connection phase with the server. So I restarted to download (back, then download again). I was surprised to see that my phone started a new thread for the same file (so 2 download for the same file now at the same time). This last one downloaded successfuly. Well, I then rebooted. It installed the upgrade successfuly and restarted the phone as usual.
What a surprise when I' discovered that my phone was still trying to download the package (while it's already installed). In CMupdater, I have 2 lines for the same 20131205 build : first line says : "installed". 2nd line says it's trying to download. I long pressed the first line to remove file. I've been to cmupdater folder to check that. Ok, the folder is empty.
So I rebooted in Recovery mode and wiped the cache as well as the Dalvik cache. No change. My phone is trying to download a file with cmupdater for days now.
I've also been to settings/applications/Cmupdater : force close, then delete data. It stops for about a minute and then restart trying to download the file.
How can I ask CMupdater to stop downloading the 20130105 nightly build ?
Help would be greatly appreciated.
R.
Same issue, u find a solution?
raticide said:
Hi,
There's something weird with CMupdater. It runs pretty good but the same problem occured to me twice so I'm documenting it as someone may help me.
I was in Nighlty build 20130103.
I wanted to upgrade to the nightly build 20130105. Then I've been to CMupdater in the settings and ask to download. There was a progress bar that was not making any progress at all. In fact, it was like if my phone was stuck in the connection phase with the server. So I restarted to download (back, then download again). I was surprised to see that my phone started a new thread for the same file (so 2 download for the same file now at the same time). This last one downloaded successfuly. Well, I then rebooted. It installed the upgrade successfuly and restarted the phone as usual.
What a surprise when I' discovered that my phone was still trying to download the package (while it's already installed). In CMupdater, I have 2 lines for the same 20131205 build : first line says : "installed". 2nd line says it's trying to download. I long pressed the first line to remove file. I've been to cmupdater folder to check that. Ok, the folder is empty.
So I rebooted in Recovery mode and wiped the cache as well as the Dalvik cache. No change. My phone is trying to download a file with cmupdater for days now.
I've also been to settings/applications/Cmupdater : force close, then delete data. It stops for about a minute and then restart trying to download the file.
How can I ask CMupdater to stop downloading the 20130105 nightly build ?
Help would be greatly appreciated.
R.
Click to expand...
Click to collapse
App info > clear data did work for me
Turned on my Wi-Fi
Samsung account asked to make update, and install push service
Play store forced to make updates
Facebook app section expired
Then the phone starts to be super slow, then the screen's touch stopped responding and everything was going crazy and lagging and not working.
I was successfully able to stop the PLAY Store updates and turned off my Wi-Fi
then I removed the battery only to force restart
The phone was stuck at the message of ( SAMSUNG Galaxy Note N7000 ) and nothing, after several seconds the processor area is super HOT
Sometimes I was able to see the BootAnimation with the whole music played.
I can successfully enter the download mode and Recovery mode
A message in red is written in Recovery mode:
E:Error in /data/log/recovery_kernel_log.txt (read-only file system)
I am currently using PhliZ
I don't want any format of any type please, the device contains important information especially the SNote app
any way I can recover my phone back, and if possible without formatting ?
By the way I downloaded Odin, rooted the phone with the right matching version, updated to official German jellybean, then downloaded the UAE version to support Arabic language and the system just went updating and all the information was not erased, then the whole things I mentioned above happened.
One of the apps that was always crashing (Root Toolbox PRO), caused the system to hang for several seconds then a message appear saying it stopped responding
mido_ameer said:
Turned on my Wi-Fi
Samsung account asked to make update, and install push service
Play store forced to make updates
Facebook app section expired
Then the phone starts to be super slow, then the screen's touch stopped responding and everything was going crazy and lagging and not working.
I was successfully able to stop the PLAY Store updates and turned off my Wi-Fi
then I removed the battery only to force restart
The phone was stuck at the message of ( SAMSUNG Galaxy Note N7000 ) and nothing, after several seconds the processor area is super HOT
Sometimes I was able to see the BootAnimation with the whole music played.
I can successfully enter the download mode and Recovery mode
A message in red is written in Recovery mode:
E:Error in /data/log/recovery_kernel_log.txt (read-only file system)
I am currently using PhliZ
I don't want any format of any type please, the device contains important information especially the SNote app
any way I can recover my phone back, and if possible without formatting ?
By the way I downloaded Odin, rooted the phone with the right matching version, updated to official German jellybean, then downloaded the UAE version to support Arabic language and the system just went updating and all the information was not erased, then the whole things I mentioned above happened.
One of the apps that was always crashing (Root Toolbox PRO), caused the system to hang for several seconds then a message appear saying it stopped responding
Click to expand...
Click to collapse
I got that error message too E:Error in /data/log/recovery_kernel_log.txt this morning while trying to reflash JB but it was something odd i was trying and i think i got it due to that, as you can enter recovery you will have to format data in order to fix this or format everything to reflash firmware but before you do that, go to philz recovery and then to mounts/Storage go to last option mount USB (while it is connected to the computer ofcourse) you should see both the internal and external card on computer after that with all your data. Back it up on computer. Unmount once you are done and then do all the wipes and reflash JB.
Cheers!!!
Mounting failed
I am currently working on PhilZ-cwm6-JPLSB-UAE-4.93.6-signed
then I coped recovery CWM-6.0.1.2-n7000.zip to the external sd card
I booted in recovery mode, and installed update
then I followed your instructions but no mobiles where detected by the windows 7, a unknown Samsung android is detected in control panel > printers & devices
every time I restart the phone it returns back to PhilZ
Is there is a windows drivers problem ?
mido_ameer said:
I am currently working on PhilZ-cwm6-JPLSB-UAE-4.93.6-signed
then I coped recovery CWM-6.0.1.2-n7000.zip to the external sd card
I booted in recovery mode, and installed update
then I followed your instructions but no mobiles where detected by the windows 7, a unknown Samsung android is detected in control panel > printers & devices
every time I restart the phone it returns back to PhilZ
Is there is a windows drivers problem ?
Click to expand...
Click to collapse
Download from http://forum.xda-developers.com/showthread.php?t=1901191
this:
Code:
<< 12.05.2013 - PhilZ-cwm6 v5.03.0 with CWM 6.0.3.2 based recovery >>
DDLSC - DXLSE - JPLSB - XXLT5 - ZSLO2 Fixed for bootloop
go to recovery and choose install zip and choose the file i mentioned above (zip file) and go the location where you have saved it (external SD) and reboot into recovery, mount storage.
Go to Dr. Ketan's thread for latest samsung drivers install them and see if it shows up your internal and external storage on computer. Backup and go to dowload mode and flash JB again.
Thanks so much
I installed PhliZ 5.0.3.0 updated and installed succussfully
I was able to mount the sdcard and copied all the folders was there to my PC
Then I downloaded a new LSB jellybean UAE edition and worked like sharm
Now my note is working
Thanks for your support
Noise Cancelling is not working
It seems that the phone noise cancelling feature is not working any more, whatever I do in the options while call in progress
Mobile GT-N7000
Android 4.1.2
Baseband N7000XXLSO
Kernel 3.0.31-906407
Build number JZ054.N7000JPLSB
When the first N preview was released I signed up for the beta. Then decided it wasn't for me and went back to playing with other ROMs.
Fast forward about a month. I noticed my device is no longer appearing in Android Device Manager (where you can find lost phones), nor is it appearing as an available device on the N Beta Sign-up page. It has always showed up in the Google Play Store though.
I've seen others have this issue and the solution has been to add another Google Account. Which I did and then the device appears in Android Device Manager & N Beta Sign-up on that account, but not my primary.
This hasn't been a huge issue until recently when I decided to go back to the stock August security release. Now my phone has a constant System Update Available icon, notifying me of the Beta Program availability.
The problem is my device does not show up on the Beta Program listing anymore, so I am unable to un-enroll. When I run 3rd party stock ROMs that have the System Update removed, the device stays awake 100% of the time, trying to look for System Updates.
Anybody else have this issue or have tips for a possible solution?
I suppose you used 2 different accounts on 1 phone.
Secondly I suppose you installed several Roms without formatting the system partition.
My idea is to delete the second account and flash a custom recovery. Use Twrp-recovery to wipe/format all partitions and clear alarm caches.
Download a prerooted stock rom in 'zip-format' to the internal memory and flash that zip with TWRP.
In short:
Download a prerooted rom.
Install Twrp-recovery.
Remove second account.
In TWRP: Wipe system-, data partition and caches.
Flash prerooted stock rom.
http://forum.xda-developers.com/showthread.php?t=3059493/
Hi,
I changed the software of my Mi Mix 6 months ago to lineage os - after the change of the os, the sound was not running properly anymore. In the forum someone did help me out with software for a firmware update. Now I updated on Lineage os 15.1 and the soundproblems are there again. Can someone tell me, if I have to update the firmware again, respectively where I can find the relevant software. Thanks for helping!
H0707 said:
Hi,
I changed the software of my Mi Mix 6 months ago to lineage os - after the change of the os, the sound was not running properly anymore. In the forum someone did help me out with software for a firmware update. Now I updated on Lineage os 15.1 and the soundproblems are there again. Can someone tell me, if I have to update the firmware again, respectively where I can find the relevant software. Thanks for helping!
Click to expand...
Click to collapse
how people gonna help you if you're not describing your problem with more details.
what is exactly the sound problem.
heindrix said:
how people gonna help you if you're not describing your problem with more details.
what is exactly the sound problem.
Click to expand...
Click to collapse
I am sorry - I have been not very precise. The sound itself is still working. But my device especially has problems to connect to myBluetooth Speaker. Maybe thats more a connection issue. There are further a bunch of small problems, I cannot explain. For example - I cannot download maps of different regions in my map app anymore. As well - I am using the yalp store to download certain apps I need - downloads or updates are not possible anymore. Half a year ago someone gave me this link for firmware updates: https://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw Is it useful to update the firmware on a newer version?
Best
First you do not need to use a firmware for LoS 15.1, just the latest nightly which is here: https://download.lineageos.org/lithium
*Second.... Do NOT use any app store beside Google Play. Because it may cause problems to your phone. Use Google Play only... Any the apps can harm your device.... I would suggest to do a full wipe on the advance wipe option in TWRP... That means everything except for USB OTG.. Make sure you are done... Make sure all data partitions (DATA, Caches) is on EXT 4 before installing. See the info below near the photo.
If your phone still have problems.....I would suggest go back to Stock Firmware by using Mi Flash (make sure you click "Clean All" without locking your phone on the bottom right of Mi-Flash) when you boot your phone to to **bootloader**. You can use Mi Flash and flash the current Global Stable or Global Developer for the Mi Mix which is on en.miui.com/a-234.html then check to see if the problem still happens on either firmwares. If there is no problem, then by all means go back to LoS 15.1. The Miui Rom Flashing tool link is right above the list of the Miui Rom Version. And again i warn you before flashing the stock firmware to click the "Clean All" only.. not "Clean All and Lock" because it will lock your bootloader. Then after your done, check for any problems.. If the phone is ok.. Then go back to LoS 15.1 to determine if these problems still happen.. If it works fine.. Then you know why your phone had problems in the first place.
The photo is for you to see what to wipe when doing a clean installation of LoS 15.1.. Wipe all except for the USB OTG before flashing anything. Repair and Change system file is to check to see if all of your partitions is on EXT 4. Just to make sure you have no errors of any kind before installing.
H0707 said:
I am sorry - I have been not very precise. The sound itself is still working. But my device especially has problems to connect to myBluetooth Speaker. Maybe thats more a connection issue. There are further a bunch of small problems, I cannot explain. For example - I cannot download maps of different regions in my map app anymore. As well - I am using the yalp store to download certain apps I need - downloads or updates are not possible anymore. Half a year ago someone gave me this link for firmware updates: https://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw Is it useful to update the firmware on a newer version?
Best
Click to expand...
Click to collapse
download and flash the latest firmware i cooked from my google drive : https://drive.google.com/drive/mobile/folders/1PGmzEcmgG0XhRB7110CDDTgMwmw4N3MM
if the issue still there, it's not firmware problem, maybe it's the ROM problem.
you can try CrDroid : https://forum.xda-developers.com/mi-mix/development/rom-crdroid-t3758726
or AICP : https://forum.xda-developers.com/mi-mix/development/rom-aicp-13-1-t3746648
or Resurrection Remix : https://forum.xda-developers.com/mi-mix/development/rom-resurrection-remix-t3751314
heindrix said:
download and flash the latest firmware i cooked from my google drive : https://drive.google.com/drive/mobile/folders/1PGmzEcmgG0XhRB7110CDDTgMwmw4N3MM
if the issue still there, it's not firmware problem, maybe it's the ROM problem.
you can try CrDroid : https://forum.xda-developers.com/mi-mix/development/rom-crdroid-t3758726
or AICP : https://forum.xda-developers.com/mi-mix/development/rom-aicp-13-1-t3746648
or Resurrection Remix : https://forum.xda-developers.com/mi-mix/development/rom-resurrection-remix-t3751314
Click to expand...
Click to collapse
Thanks a lot for your extensive response.
One thing - out of some reason I cannot start TWRP manually (maybe cause I encrypted my hard-drive). I only can start it using adb. Once, my recovery is started, I can not connect to the phones hard-drive via my computer anymore. Am I not deleting the complete hard-drive plus OS, when I am performing an extended wipe - as you are suggesting. My problem is, that I am afraid, that I am not able to install a new OS after a wipe (since I will delete all data stored on the hard-drive and to enter my hard-drive again, I would have to start the phone...).
Ps. I never heard that it might cause problems to install apps from apps like the yalp store. Since I am not interested to have all the google surveillance software on my phone, using a costum rom without gapps seemed a good way for me till now.
H0707 said:
Thanks a lot for your extensive response.
One thing - out of some reason I cannot start TWRP manually (maybe cause I encrypted my hard-drive). I only can start it using adb. Once, my recovery is started, I can not connect to the phones hard-drive via my computer anymore. Am I not deleting the complete hard-drive plus OS, when I am performing an extended wipe - as you are suggesting. My problem is, that I am afraid, that I am not able to install a new OS after a wipe (since I will delete all data stored on the hard-drive and to enter my hard-drive again, I would have to start the phone...).
Ps. I never heard that it might cause problems to install apps from apps like the yalp store. Since I am not interested to have all the google surveillance software on my phone, using a costum rom without gapps seemed a good way for me till now.
Click to expand...
Click to collapse
Something weird happened - TWRP is not accepting my password anymore at the start. Thats strange cause my password is accepted, when I start the phone. Bad development
H0707 said:
Something weird happened - TWRP is not accepting my password anymore at the start. Thats strange cause my password is accepted, when I start the phone. Bad development
Click to expand...
Click to collapse
sorry for judging, but reading your details, i suppose you haven't learn a lot about customizing device.
if this suggestion didn't help you, i don't know anymore what will.
Flash TWRP (twrp-3.2.1-raupe-blunden-15.1-updated.img) -> Boot into TWRP -> Swipe to Allow Modifications -> Cancel when TWRP asks for password -> Go To Wipe -> Press Format Data button and type YES and press enter -> Go To Wipe -> Press Advanced Wipe button -> Select all partitions except USB OTG and swipe to wipe -> Go to Mount -> Press Select Storage button and choose Internal Storage and press OK -> Press Mount USB Storage button -> Plug phone to PC -> Copy all files you want to flash from PC -> Unmount and unplug from PC -> Go to Mount -> Mount all partitions except USB OTG -> Flash files you want to flash
heindrix said:
sorry for judging, but reading your details, i suppose you haven't learn a lot about customizing device.
if this suggestion didn't help you, i don't know anymore what will.
Flash TWRP (twrp-3.2.1-raupe-blunden-15.1-updated.img) -> Boot into TWRP -> Swipe to Allow Modifications -> Cancel when TWRP asks for password -> Go To Wipe -> Press Format Data button and type YES and press enter -> Go To Wipe -> Press Advanced Wipe button -> Select all partitions except USB OTG and swipe to wipe -> Go to Mount -> Press Select Storage button and choose Internal Storage and press OK -> Press Mount USB Storage button -> Plug phone to PC -> Copy all files you want to flash from PC -> Unmount and unplug from PC -> Go to Mount -> Mount all partitions except USB OTG -> Flash files you want to flash
Click to expand...
Click to collapse
Dear Hendrix, I am not a pro just an interested person trying to emancipate myself dealing with smartphonetechnology. Thanks a lot for your guideline. I will try your advice as soon as I find the time. Will let you know, if everything worked out! Best wishes
For what it's worth, flashing the firmware provided by hendrix fixed my lineageos 15.1 problems.
I recently moved into LineageOS coming from latest MIUI 10 by Xiaomi.eu. Initially everything worked fine except for sound when playing media files (notification sound works). The firmware flash fixed everything.
heindrix said:
sorry for judging, but reading your details, i suppose you haven't learn a lot about customizing device.
if this suggestion didn't help you, i don't know anymore what will.
Flash TWRP (twrp-3.2.1-raupe-blunden-15.1-updated.img) -> Boot into TWRP -> Swipe to Allow Modifications -> Cancel when TWRP asks for password -> Go To Wipe -> Press Format Data button and type YES and press enter -> Go To Wipe -> Press Advanced Wipe button -> Select all partitions except USB OTG and swipe to wipe -> Go to Mount -> Press Select Storage button and choose Internal Storage and press OK -> Press Mount USB Storage button -> Plug phone to PC -> Copy all files you want to flash from PC -> Unmount and unplug from PC -> Go to Mount -> Mount all partitions except USB OTG -> Flash files you want to flash
Click to expand...
Click to collapse
Dear Hendrix,
everything worked fine - the device feels like new - thanks!
If you have questions on cultural sciences (am holding a PHD in this area) you can always ask me - I for sure will not start judging you in your unprofessional first moves
H0707 said:
Dear Hendrix,
everything worked fine - the device feels like new - thanks!
If you have questions on cultural sciences (am holding a PHD in this area) you can always ask me - I for sure will not start judging you in your unprofessional first moves
Click to expand...
Click to collapse
Me too, Phone itself worked great, had NO sound from Google Assistant, no sound from headphones, no sound from speakers, but did have ring/notifications and some sound. Video was laggy and intermittent on youtube and the net..... I tried many different Roms, Many newer firmwares and the ONLY ONLY thing that worked was the suggestion to try firmware 8.1.4
After that all is working great...…………..
garythompson said:
Me too, Phone itself worked great, had NO sound from Google Assistant, no sound from headphones, no sound from speakers, but did have ring/notifications and some sound. Video was laggy and intermittent on youtube and the net..... I tried many different Roms, Many newer firmwares and the ONLY ONLY thing that worked was the suggestion to try firmware 8.1.4
After that all is working great...…………..
Click to expand...
Click to collapse
Some users said that there are problems on firmware more than 8.8.2 version, 8.8.2 still works fine. but i don't know if it will works for you too.
For various reasons I don't want to update to pie on my tmobile galaxy note 8. There is a pending update that I have postponed but it is still there and taking up space and I could accidentally tap on it in notifications.
Let's be clear. I am not downgrading. The update is NOT installed. The firmware image or whatever is downloaded but not flashed.
I want to:
1. Disable the updater so it won't keep nagging me or keep downloading the 1.7gb update file.
2. Delete the update file that is taking up space.
Factory reset the phone Download bk package disabler and disable all updates.ive done this android pie is trash on the note 8.also go into developer mode and to turn off auto update