Man this is weird.
Here is the series of events as they transpired:
1. Changed lcd density to 140 in my build.prop file and rebooted.
2. Tablet boot looped.
3. Pulled build.prop and changed lcd back to 160 and tried to push it back to /system/ using adb.
4. Would not push. Received "permission denied" error.
5. Could not get past that error no matter what I did so just ODIN'd back to original root injected firmware as described here: http://rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1/
6. Tablet then rebooted fine.
7. Touch works perfectly.
8. S-Pen does NOTHING. Tried changing tips, Tried yelling at it. Tried making soft nurturing sounds. Nothing.
9. If I insert the S-Pen into it's dock and remove it the Tablet freezes completely.
10. Went back and completely formatted the SD Card (in case there was anything weird in there causing trouble).
11. Factory wiped, system wiped, wiped everything you can wipe.
12. ODIN'd back to the root injected original firmware.
Still no s-pen.
I thought that maybe by originally changing the lcd density to 140 I had screwed something else. But that build.prop seems to have been replaced with the correct one as seen here:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D.N8013UEALGB
ro.build.version.incremental=N8013UEALGB
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Wed Jul 18 16:53:36 KST 2012
ro.build.date.utc=1342598016
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-101
ro.build.tags=release-keys
ro.product.model=GT-N8013
ro.product.brand=samsung
ro.product.name=p4notewifiue
ro.product.device=p4notewifi
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product_ship=true
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=p4notewifi
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=p4notewifiue-user 4.0.4 IMM76D N8013UEALGB release-keys
ro.build.fingerprint=samsung/p4notewifiue/p4notewifi:4.0.4/IMM76D/N8013UEALGB:user/release-keys
ro.build.characteristics=tablet
# Samsung Specific Properties
ro.build.PDA=N8013UEALGB
ro.build.hidden_ver=N8013UEALGB
ro.build.changelist=897512
# end build properties
#
# system.prop for smdk4x12
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=160
#@SS1 2012-02-10 add property to set max_events_per_sec for model with pen
windowsmgr.max_events_per_sec=60
persist.sys.storage_preload=1
#
##System property for qemu
##
ro.kernel.qemu=0
# System property for Default Brightness
ro.lcd_brightness=140
# Multimedia prop for Smart View
media.enable-commonsource=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
hwui.render_dirty_regions=false
ro.sec.fle.encryption=true
ro.secwvk=220
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.error.receiver.default=com.samsung.receiver.error
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.google.clientidbase=android-samsung
drm.service.enable=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.com.google.gmsversion=4.0_r2
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
As you can see, everything appears to be in order.
So, anyway, I'm stuck on this. Have no idea why S-Pen will not function.
One other weird wrinkle.
Touch seems to work fine. However, if I reboot touch no longer works. Then if I reboot again, touch is working.
** Also, if screen goes to sleep and I click the power button to wake it, touch no longer works.
I'm lost.
This just keeps getting weirder.
If I insert the pen in it's dock and remove it, the little quick launch menu pops up and the screen freezes. Have to reboot. What the hell?
Try to put a clean stock ROM and then return the tablet for warranty... :cyclops:
Well my issue is I bought this at BestBuy.
The problem with BestBuy is that their products are so often defective you must return them 2 or 3 times to get one that works. I buy a lot of tech so that means a lot of returns, no fault of my own.
So when I bought this tablet they issued me one of those "No returns for 90 days" notices - complete BS - maybe this is why BestBuy is going broke - terrible policies? Anyway, I should have told them to shove it and bought the tablet off Amazon but I was there and I wanted to it I threw caution to the wind and accepted their silly agreement.
So now I can't return my tablet to BestBuy even if it is defective, which it may be. And I can't turn it into Samsung for repair because it is rooted and as far as I know, no one has created an unroot method yet.
You know, the fact that the pen stopped working at the same time the lcd snafu took place may be pure coincidence. It could just be a hardware failure of some sort in the wacom digitizer.
The first thing I would Adonis an emergency recovery through Samsung Kies.
Then I would call Best Buy corporate and explain the situation. Go to the store and talk with the manager. I think you'll be able to return it. Then NEVER buy anything from BB again. Write their corporate a letter why.
Order from Amazon.
I don't understand laypeople mess with these devices. Especially this one with the complicated digitizer pen.
Sent from my Galaxy Note 10.1
cmunho said:
The first thing I would Adonis an emergency recovery through Samsung Kies.
Then I would call Best Buy corporate and explain the situation. Go to the store and talk with the manager. I think you'll be able to return it. Then NEVER buy anything from BB again. Write their corporate a letter why.
Order from Amazon.
I don't understand laypeople mess with these devices. Especially this one with the complicated digitizer pen.
Sent from my Galaxy Note 10.1
Click to expand...
Click to collapse
Lol, xda-developers exists so that lay people can mess with these devices
Ok, just KIES'd the latest firmware update. STILL no pen. Friggin bizarre.
These are the biggest clues so far:
1. Removing the pen from it's dock causes the tablet to freeze.
2. Awakening the tablet from sleep causes the tablet to freeze.
3. Touch works fine unless do one of the two above actions.
4. Pen never works.
mitchellvii said:
Lol, xda-developers exists so that lay people can mess with these devices
Ok, just KIES'd the latest firmware update. STILL no pen. Friggin bizarre.
These are the biggest clues so far:
1. Removing the pen from it's dock causes the tablet to freeze.
2. Awakening the tablet from sleep causes the tablet to freeze.
3. Touch works fine unless do one of the two above actions.
4. Pen never works.
Click to expand...
Click to collapse
There is an option in kies to do an emergency restore (not the firmware upgrade). I would try that. Its likely something is sticking that shouldn't be and that reverts completely back to stock.
I agree for some messing is just fine. Me personally, I need reliable and my experience with ROMS has been anything but that so far. I've learned to be happy with what I got stock.
Sent from my Galaxy Note
mitchellvii said:
Lol, xda-developers exists so that lay people can mess with these devices
Ok, just KIES'd the latest firmware update. STILL no pen. Friggin bizarre.
These are the biggest clues so far:
1. Removing the pen from it's dock causes the tablet to freeze.
2. Awakening the tablet from sleep causes the tablet to freeze.
3. Touch works fine unless do one of the two above actions.
4. Pen never works.
Click to expand...
Click to collapse
This seems to be a pretty common issue with the latest OTA update for rooted users with no fix yet. Even if you flash back to UEALGB it seems that touch will still freeze once the tablet goes to sleep or the s pen is removed.
Whats interesting is the touch itself becomes unresponsive, not the tablet. I have live widgets on my home screen that still update/move while the touch is unresponsive. So until someone comes up with a fix, sounds like your tablet is useless.
I initially ran the update through Kies and the pen worked fine afterwards.
cmunho said:
There is an option in kies to do an emergency restore (not the firmware upgrade). I would try that. Its likely something is sticking that shouldn't be and that reverts completely back to stock.
I agree for some messing is just fine. Me personally, I need reliable and my experience with ROMS has been anything but that so far. I've learned to be happy with what I got stock.
Sent from my Galaxy Note
Click to expand...
Click to collapse
Tried running Emergency Restore but the box that says, "List of devices requiring emergency recover" is empty.
I can write with my finger just fine in S-Notes.
GaresTaylan said:
This seems to be a pretty common issue with the latest OTA update for rooted users with no fix yet. Even if you flash back to UEALGB it seems that touch will still freeze once the tablet goes to sleep or the s pen is removed.
Whats interesting is the touch itself becomes unresponsive, not the tablet. I have live widgets on my home screen that still update/move while the touch is unresponsive. So until someone comes up with a fix, sounds like your tablet is useless.
Click to expand...
Click to collapse
The odd thing is that this behavior began after I ODIN'd back to the original root injected firmware. So it doesn't seem to be the update causing the problem - or if it is, it is causing something permanent that mere wiping does not solve.
That's what I get for running an upgrade before the Devs have cleaned it up for root
mitchellvii said:
Tried running Emergency Restore but the box that says, "List of devices requiring emergency recover" is empty.
Click to expand...
Click to collapse
It might only work if you're in "forced download mode" - On phones that's the Phone<->PC screen, happens when an attempt to load something in Odin fails.
Using Heimdall 1.3.3 to write /system is guaranteed to put you here.
I'm uploading a complete UEALH2 prerooted package but it's going to take a while - and not complete until I'm at work which means I can't post a link until this evening.
This assumes the upload doesn't bomb like the last attempt did.
Entropy512 said:
It might only work if you're in "forced download mode" - On phones that's the Phone<->PC screen, happens when an attempt to load something in Odin fails.
Using Heimdall 1.3.3 to write /system is guaranteed to put you here.
I'm uploading a complete UEALH2 prerooted package but it's going to take a while - and not complete until I'm at work which means I can't post a link until this evening.
This assumes the upload doesn't bomb like the last attempt did.
Click to expand...
Click to collapse
Yay! My pen is working again!
Trying to figure out what I did to fix it.
1. Wiped everything that was wipeable.
2. Rebooted my computer.
3. ODIN'd back to root-injected original firmware.
4. Kies'd upgrade.
5. ODIN'd cwm (with F. Reset Time checked).
6. Flashed SuperUser.
7. Rebooted.
Pen works!
Hell if I know?
Glad to hear you got it working again.
Sent from my Galaxy Note
cmunho said:
Glad to hear you got it working again.
Sent from my Galaxy Note
Click to expand...
Click to collapse
Me too brother. Don't know why it stopped and don't know why it started again. Just happy it did. :fingers-crossed:
mitchellvii said:
Me too brother. Don't know why it stopped and don't know why it started again. Just happy it did. :fingers-crossed:
Click to expand...
Click to collapse
A few of us experienced the same issues last night. A combination of the stock kernel/recovery and root injected system will give u a working pen and touch but the problem two of us are having is S-Note force closing. I was not able to re-kies the update I guess I will look over your steps again, some of them are un-unnecessary.
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/showpost.php?p=30450339&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip mirror: http://downloadandroidrom.com/file/.../StockROMs.net-GT-N8013RootInjectedSystem.zip
3. Re-kies to new firmware via WINDOWS
vanillanesquik said:
A few of us experienced the same issues last night. A combination of the stock kernel/recovery and root injected system will give u a working pen and touch but the problem two of us are having is S-Note force closing. I was not able to re-kies the update I guess I will look over your steps again, some of them are un-unnecessary.
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/showpost.php?p=30450339&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip mirror: http://downloadandroidrom.com/file/.../StockROMs.net-GT-N8013RootInjectedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
Blah, wish I had seen this before I just rooted and lost S Pen. Pretty annoying because my work requires Linux so having to boot into Windows for ODIN is pretty rare. Anyone know if Heimdall works with this stuff?
Edit: I did wipe data/cache and flash the original root injected image but I still don't have S Pen working. Is the Kies firmware update needed to get it working again? Going to try that now.
iofthestorm said:
Blah, wish I had seen this before I just rooted and lost S Pen. Pretty annoying because my work requires Linux so having to boot into Windows for ODIN is pretty rare. Anyone know if Heimdall works with this stuff?
Edit: I did wipe data/cache and flash the original root injected image but I still don't have S Pen working. Is the Kies firmware update needed to get it working again? Going to try that now.
Click to expand...
Click to collapse
I highly recommend you thoroughly wipe your data/system/dalvik, flash the update through Kies then ODIN Clockwork again and flash Superuser again.
This should solve all problems.
Sent from my GT-N8013 using Tapatalk 2
Related
My Atrix 2 is a 2.3.5 firmware version. ATT 110921_0913
From previous 2 to 3 days my phone is in complete freeze mode...meaning whatever I do to my phone install any app uninstall any app...when I restart the phone it just gets back to the same state....
I have tried factory reset from the settings I didn't worked..... then I tried the hard reset method but that didn't worked too...
After that I tries reloading the stock fxz using the rsd lite but it failed at step 3 saying mbmloader cannot be flashed....
Then I tried the script method...http://forum.xda-developers.com/showthread.php?t=1539167
In that it said that the bootloader is restricted and it cannot write it it wrote the rest of the things but still my phone is in the same state it was with same apps and everything.....
I tried booting into the CWM recovery mode but when I try to run the AtrixBOOtloader.apk it reboots and the restarts normally....
Please I really need som help....
just to let you know I have Go launcher installed I know its absurd to thing that it can be causing the problem...but just in casee....
Please let me know if you need any other information.....
Any help will be greatly appreciated....
Thanks....
More info is always nice:
Are you rooted? Were you running a special ROM? If rooted, did you make any changes to your system? If rooted, do you have a backup made (cause you should)? What did you do (system wise) before this started?
And are you SURE you are 2.3.5? Because all A2's are 2.3.5 out of the box but have since been upgraded to 2.3.6, which is the stock norm for A2's.
PS: From now on please post things like this in the Q&A forum. We're kinda letting this slide so far since it's still new and not everyone is aware of it.
Fall of Enosis said:
More info is always nice:
Are you rooted? Were you running a special ROM? If rooted, did you make any changes to your system? If rooted, do you have a backup made (cause you should)? What did you do (system wise) before this started?
And are you SURE you are 2.3.5? Because all A2's are 2.3.5 out of the box but have since been upgraded to 2.3.6, which is the stock norm for A2's.
PS: From now on please post things like this in the Q&A forum. We're kinda letting this slide so far since it's still new and not everyone is aware of it.
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
Here are the answers:
Are you rooted? Yes!
Were you running a special ROM? No I did nothing that could mess up my rom or anything...
If rooted, did you make any changes to your system? If rooted, do you have a backup made (cause you should)? What did you do (system wise) before this started? No to above all...this started happening 2-3 days ago after some of my apps were updated...and I dont have any backup
And are you SURE you are 2.3.5? Because all A2's are 2.3.5 out of the box but have since been upgraded to 2.3.6, which is the stock norm for A2's........
I am sure that I am at 2.3.5 because I was not able to install the 2.3.6 update I kept on failing on me while installing on halfway.....
Again I have not done anything related to my system that I could cause this...only thing I can think of is because of some rogue app or something!!!!
Ok now that we have the basics down, one other question, what EXACTLY do you mean by "freeze mode"? What exactly is the phone doing that you don't want it to do? Force closing all the time? If so, what apps?
I'm still a little confused as to what EXACTLY the phone is doing.
The more info the better.
I agree with you Fall of Enosis, we need some more exacted information regarding the OP's issue here.
OP: You say you tried a factory reset, but now are concerned that it is a "rogue app", but unless you've re-installed apps you previously had installed, this is not likely.
What is your location, and do you have access to WiFi or network connectivity to enable the update from 2.3.5 to 2.3.6?
Sounds to me as if you have tried to do something that we're not entirely clear of (and perhaps you are not either) and as result you've borked the boot image, but I can't convincingly determine that is the case here. If the phone is still booting into Android, but simply "freezes", then you may have a bad flash of the FXZ.
If you are experiencing "freezing" of the UI or system itself, it could be application-related or a handful of other things.
You really need to be as precise as you possibly can, describing in detail everything you have done, tried, and are experiencing here for us to be of any real help. Otherwise, we're left to 'fishing' for information from you, which wastes everyone's time here.
Fall of Enosis said:
Ok now that we have the basics down, one other question, what EXACTLY do you mean by "freeze mode"? What exactly is the phone doing that you don't want it to do? Force closing all the time? If so, what apps?
I'm still a little confused as to what EXACTLY the phone is doing.
The more info the better.
Click to expand...
Click to collapse
Yes all of my apps are force closing like motorola.service.....facebook rebtel and many others...sometimes one crashes on other restart some other.....
NOTHING IS ACTUALLY FREEZING
By freeze mode I mean like the deep freeze effect on the PC...I cannot uninstall any app or install a new one cannot make any changes ot my system settings or anything......
So sometimes critical processes closes like contacts process and then no contacts are shown.....I am able to use the phone and the apps which are not closing for that time works prefectly fine....
Apex_Strider said:
I agree with you Fall of Enosis, we need some more exacted information regarding the OP's issue here.
OP: You say you tried a factory reset, but now are concerned that it is a "rogue app", but unless you've re-installed apps you previously had installed, this is not likely.
What is your location, and do you have access to WiFi or network connectivity to enable the update from 2.3.5 to 2.3.6?
Sounds to me as if you have tried to do something that we're not entirely clear of (and perhaps you are not either) and as result you've borked the boot image, but I can't convincingly determine that is the case here. If the phone is still booting into Android, but simply "freezes", then you may have a bad flash of the FXZ.
If you are experiencing "freezing" of the UI or system itself, it could be application-related or a handful of other things.
You really need to be as precise as you possibly can, describing in detail everything you have done, tried, and are experiencing here for us to be of any real help. Otherwise, we're left to 'fishing' for information from you, which wastes everyone's time here.
Click to expand...
Click to collapse
I am really sorry for not being much more clearer with my problem.....!!
I am currently in US LA and yes I do have wifi connectivity I have tried update several times but I just fails...I think may be I rooted it incorrectly....
I HAVE NOT TRIED TO DO ANYTHING WITH MY SYSTEM
The phone still boots up normally and works fine I mean nothing is freezing ....by freeze mode I mean the whole of the phone memory is frozen like deep freeze on the PC so I cannot make any changes to the settings or install uninstall any apps....moreover on each restart many of the processes keeps on closing...
So agian I will try to make it as clearer as possible.....I have not tried to install any custom rom or make any os or system related changes to my atrix 2....
What is actually happening is I cannot make any changes to my phone memory....I cannot change any settings or install or uninstall anything since as soon as I restart my phone ANY CHANGES WILL DISAPPEAR and it will be back to the exact same state as it was before.....
Please help I am not able to fix this thing....
Ok, thanks for being clearer. It helps.
I have had something like this happen to me, constant moto apps fc'ing.
For me it was an app causing my headache. However the only way i could take care of it was to restore one of my backups.
I think you possibly have an app causing your headache as well. And i think that somehow (whether you know it or not) you accidentally borked the system UI. So before we go to the extreme of fxz'ing back (since you don't have a backup) what kind of rooted apps are you using?
I know YOU didn't personally change anything but rooted apps will make all sorts of changes that you are unaware of.
What rooted apps are you running and more importantly which apps (rooted or not) were most recently installed before this happened?
Don't fret man, we'll work this out for ya.
Sent from my MB865 using xda premium
Maybe.. the flash memory cannot be written?
Is it possible to post "adb logcat" when your apps are force closing or you are trying to do an install? And if you could make adb work, then grab a shell and paste the o/p of the commands "mount", "df" ... Also you may want to try command like "adb install <package.apk>", and check what's the error code returned.
Fall of Enosis said:
Ok, thanks for being clearer. It helps.
I have had something like this happen to me, constant moto apps fc'ing.
For me it was an app causing my headache. However the only way i could take care of it was to restore one of my backups.
I think you possibly have an app causing your headache as well. And i think that somehow (whether you know it or not) you accidentally borked the system UI. So before we go to the extreme of fxz'ing back (since you don't have a backup) what kind of rooted apps are you using?
I know YOU didn't personally change anything but rooted apps will make all sorts of changes that you are unaware of.
What rooted apps are you running and more importantly which apps (rooted or not) were most recently installed before this happened?
Don't fret man, we'll work this out for ya.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Okay, so I have been playing with the phone form last two days and I have figured out what the problem is...ITS A ROGUE APP...HOW??!!!!
Well, I started my phone in safe mode and I was out of the WIFI reach so no network access then to my surprise everything worked fine like a charm no process was closing and the phone was perfectly fine as it should but as soon as I went into wifi connectivity around 12 of my apps got automatic updates and my phone started f*king again.....
As soon as the updates were installed all my apps started force closing and it was absolutely like a what a virus does on the PC my apps were starting trying to load and then were kill in about 3-4 seconds......
So, it has to be a rogue app nothing else.....I am not sure which app is causing the problem and I don't even remember which app I recently installed but it has to be one of the app which is getting updated...right??
Just for reference these many apps gets the update after which my phone starts messing up....
Line Runner
Words with friends
Foursquare
Facebook
3D Matrix Vol.2 (its a live wallpaper)
TuneIn Radio
Skype
GO Keyboard
Nexus Pro Live wallpaper
GO Locker
(this only these got updated....it can the live wallpaper app I ma not sure)
So, now we know what the problem is...what am I supposed to do now...I have tried uninstalling my apps in the safe mode also but as usuale after the restart I gets back to the same exact state it was.....
Any suggestions will be really helpful....
Also what I am wondreing about is if the app has somehow restricted the mbmbootloader writing isn't there any other way we can write it or change the permission...??
Also thanks for staying with me on this till now
PhoenixNghi said:
Maybe.. the flash memory cannot be written?
Click to expand...
Click to collapse
Are you referring to mbmloader.bin???
black_panther10 said:
Okay, so I have been playing with the phone form last two days and I have figured out what the problem is...ITS A ROGUE APP...HOW??!!!!
Well, I started my phone in safe mode and I was out of the WIFI reach so no network access then to my surprise everything worked fine like a charm no process was closing and the phone was perfectly fine as it should but as soon as I went into wifi connectivity around 12 of my apps got automatic updates and my phone started f*king again.....
As soon as the updates were installed all my apps started force closing and it was absolutely like a what a virus does on the PC my apps were starting trying to load and then were kill in about 3-4 seconds......
So, it has to be a rogue app nothing else.....I am not sure which app is causing the problem and I don't even remember which app I recently installed but it has to be one of the app which is getting updated...right??
Just for reference these many apps gets the update after which my phone starts messing up....
Line Runner
Words with friends
Foursquare
Facebook
3D Matrix Vol.2 (its a live wallpaper)
TuneIn Radio
Skype
GO Keyboard
Nexus Pro Live wallpaper
GO Locker
(this only these got updated....it can the live wallpaper app I ma not sure)
So, now we know what the problem is...what am I supposed to do now...I have tried uninstalling my apps in the safe mode also but as usuale after the restart I gets back to the same exact state it was.....
Any suggestions will be really helpful....
Also what I am wondreing about is if the app has somehow restricted the mbmbootloader writing isn't there any other way we can write it or change the permission...??
Also thanks for staying with me on this till now
Click to expand...
Click to collapse
Ok, I am going weigh in here now....
All of this has absolutley NOTHING to do with the Bootloader/mbmloader, not sure where that came from.
My advice is disable all the updates in the playstore, or well the auto update feature, then those apps that you mentioned that are getting updated. After you restore the fxz, this time make sure that the auto update is off, and then update each of the noted problem apps ONE AT A TIME, then when the issue starts you know which one is the problem app, most likely the last app installed or updated, and I would not install that one again. Simple solution here.
Yes this will be painful, because you might have to do the fxz more than once, but it is the best way to know you are back to 100% stock again.
kousik said:
Is it possible to post "adb logcat" when your apps are force closing or you are trying to do an install? And if you could make adb work, then grab a shell and paste the o/p of the commands "mount", "df" ... Also you may want to try command like "adb install <package.apk>", and check what's the error code returned.
Click to expand...
Click to collapse
Okay here I was doing adb logcat and when I tried play music it got killed and this was the adb logcat output
09-03 11:56:33.054 1362 1362 D dalvikvm: GC_EXPLICIT freed <1K, 48% free 2839K
/5379K, external 2357K/2773K, paused 52ms
09-03 11:56:35.750 521 538 W ActivityManager: Activity destroy timeout for H
istoryRecord{406001e0 com.google.android.music/com.android.music.activitymanagem
ent.TopLevelActivity}
09-03 11:56:38.070 1414 1414 D dalvikvm: GC_EXPLICIT freed 6K, 47% free 2892K/
5447K, external 2357K/2773K, paused 69ms
09-03 11:56:42.710 521 605 V AlarmManager: sending alarm Alarm{40b32c60 type
2 android}
09-03 11:56:42.726 4335 4471 I Gmail : MainSyncRequestProto: lowestBkwdConvo
Id: 0, highestHandledServerOp: 924491, normalSync: true
Let me know if you can make any sense out of it.....
And I am able to install and uninstall apps it is not like I wont be allowed to install them its like when I restart all the changes that I make are lost system setting any apps the I installed/uninstalled.....??
Is there anything else you want me to do??
jimbridgman said:
Ok, I am going weigh in here now....
All of this has absolutley NOTHING to do with the Bootloader/mbmloader, not sure where that came from.
My advice is disable all the updates in the playstore, or well the auto update feature, then those apps that you mentioned that are getting updated. After you restore the fxz, this time make sure that the auto update is off, and then update each of the noted problem apps ONE AT A TIME, then when the issue starts you know which one is the problem app, most likely the last app installed or updated, and I would not install that one again. Simple solution here.
Yes this will be painful, because you might have to do the fxz more than once, but it is the best way to know you are back to 100% stock again.
Click to expand...
Click to collapse
But, I am not able to an fxz completely thats what I said...when I try to do fxz back to stock while trying with rsd lite it failed at step 3 saying cannot write mbmloader
then I tried the script method and it said that mbmloader is restricted and it cannot write to it and it did rest of e things which were in the script.....so not matter how many times I fxz it when I start my phone it just gets back to where I left it...??
All I want is that I can just flush everything my phone nad get it back to as it was new....no apps nothing...
black_panther10 said:
But, I am not able to an fxz completely thats what I said...when I try to do fxz back to stock while trying with rsd lite it failed at step 3 saying cannot write mbmloader
then I tried the script method and it said that mbmloader is restricted and it cannot write to it and it did rest of e things which were in the script.....so not matter how many times I fxz it when I start my phone it just gets back to where I left it...??
All I want is that I can just flush everything my phone nad get it back to as it was new....no apps nothing...
Click to expand...
Click to collapse
You have a corrupt install, since it did not flash the correct BL, and most likely other files from the fxz. Your issue is that being in that state will make your phone completely unstable as it is. You are most likely partly on 2.3.5 and 2.3.6 at this point.
Did you EVER install the ICS leak?
Did you apply the corerct fxz patch? which version of firmware are you on, and where do you live (what country), and are you using an AT&T phone outside the US?
If you can answer all of that, I am sure I can get you all fixed with a good fxz.
jimbridgman said:
You have a corrupt install, since it did not flash the correct BL, and most likely other files from the fxz. You issue is that being in that state will make your phone completely unstable as it is. You are most likely partly on 2.3.5 and 2.3.6 at this point.
Did you EVER install the ICS leak?
Did you apply the corerct fxz patch? which version of firmware are you on, and where do you live (what country), and are you using an AT&T phone outside the US?
If you can answer all of that, I am sure I can get you all fixed with a good fxz.
Click to expand...
Click to collapse
Did you EVER install the ICS leak? No I never tried the ICS leak!!
Did you apply the corerct fxz patch? which version of firmware are you on, and where do you live (what country), and are you using an AT&T phone outside the US? Yeah I applied the correcty fxz patch.....I am currently on 2.3.5 and I used the 2.3.5 fxz patch only......I purchased my atrix 2 from LA and I am using the phone in LA only
Well to your doubt that I can be partially on 2.3.5 and 2.3.6 .....well that is somehow possible since when the 2.3.6 update came out I tried to install it but it always failed in the halfway...but that never seemed to cause the problem...I tried that a couple of times when the update came out and then I gave up on it ....I thought it may be because I rooted my phone incorrectly.....but still my phone was working perfectly fine after that....
black_panther10 said:
Did you EVER install the ICS leak? No I never tried the ICS leak!!
Did you apply the corerct fxz patch? which version of firmware are you on, and where do you live (what country), and are you using an AT&T phone outside the US? Yeah I applied the correcty fxz patch.....I am currently on 2.3.5 and I used the 2.3.5 fxz patch only......I purchased my atrix 2 from LA and I am using the phone in LA only
Well to your doubt that I can be partially on 2.3.5 and 2.3.6 .....well that is somehow possible since when the 2.3.6 update came out I tried to install it but it always failed in the halfway...but that never seemed to cause the problem...I tried that a couple of times when the update came out and then I gave up on it ....I thought it may be because I rooted my phone incorrectly.....but still my phone was working perfectly fine after that....
Click to expand...
Click to collapse
Ok, now you still did not answer the exact firmware version your on... please do this:
Settings --> About phone, now give me the long string of numbers and letters under the following things:
System Version:
Android Version:
Kernel Version:
Build number:
Once I have all of those, I will know how to patch the fxz for you. If you are truely on 2.3.5 there would be no need at all for any fxz patching by the way, that only applies if the 2.3.6 OTA actually took.
jimbridgman said:
Ok, now you still did not answer the exact firmware version your on... please do this:
Settings --> About phone, now give me the long string of numbers and letters under the following things:
System Version: 55.11.16.MB865.ATT.en.US
Android Version:2.3.5
Kernel Version: 2011-09-21 09:42 off.Bld LUD_EDISON_RLD7_PATCH_27_110921_0913
Build number:5.5.1-175 EDEFW1-16
Once I have all of those, I will know how to patch the fxz for you. If you are truely on 2.3.5 there would be no need at all for any fxz patching by the way, that only applies if the 2.3.6 OTA actually took.
Click to expand...
Click to collapse
I have used the exact same version of fxz as the kernel version.....
black_panther10 said:
Line Runner
Words with friends
Foursquare
Facebook
3D Matrix Vol.2 (its a live wallpaper)
TuneIn Radio
Skype
GO Keyboard
Nexus Pro Live wallpaper
GO Locker
(this only these got updated....it can the live wallpaper app I ma not sure)
Click to expand...
Click to collapse
Once you uninstall these apps, is everything fine? And if so, uninstall them all, and update them ONE at a time to see which one is borking everything.
**POSSIBLE SOLUTION** Please post below if it works for you.
You may be here because you are getting random reboots, maybe you installed TWRP and your cache took forever to wipe or maybe your phone is just rebooting for god knows what reason, maybe these will help you!
After contacting a developer and having them look at some logs I found, I am determined it is something with the kernel in the N5 which probably runs ONDEMAND and is causing this issue with some devices which I see as more sensitive to higher clocks.
Follow the instructions EXACTLY and configure the kernel exactly as below! This could work with any custom rom as long as you use a custom kernel or you can change the way the kernel in that rom behaves. The kernel from my experiences works best as follows:
Best Kernel Settings
Mode: INTERACTIVE
Min: 300 Mhz
Max: 1985 Mhz (or closest below 2000 Mhz)
CUSTOM ROM & KERNEL | Flash CM11 & Franco Kernel
I will provide you the steps but you need to full restore your phone to an RMA ready standpoint, that means running the google supplied files, and relocking. At that point you can then flash Clockworkmod (DO NOT flash TWRP, I love TWRP but their recovery I believe started my issue) after you unlock, flash CM11 & Franco Kernel. Leave the kernel settings stock.
***Reason - When I originally installed TWRP, it took about 5 minutes just to wipe cache, after that the reboots began, I use CWM on this device but TWRP is on my other devices. CM11 is super smooth, im running the nightlies, and the Franco Kernel I believe relieves some of the stress that is causing the kernel panics if you use the default clocks which are lower than the stock ones.
Steps: **MUST BE BOOTLOADER UNLOCKED TO DO THIS**
1) Flash ClockworkMod Recovery (latest version), no matter your current state (fastboot flash recovery filename.img)
2) Wipe & Format the entire device and all partitions that are safe to do so from the custom recovery (including the internal storage)
*Device should be unbootable at this point, there is no OS
3) Download google's method of returning to stock here https://developers.google.com/android/nexus/images#hammerhead (I used 4.4 then sideloaded 4.4.1 & 4.4.2 but get 4.4.2 if link works)
4) Unzip googles file
5) Put your device in the Bootloader (Turn off, hold power + vol down)
6) Connect to your computer securely, run flash-all.bat
*once its done, your device will reboot and be completely stock
7) Put your device back in the Bootloader
8) Relock your device (fastboot oem lock)
9) Reboot your device
10) Go into the device & go into Settings > Backup & reset and do a Factory data reset.
11) Put device back in the Bootloader
12) Unlock your device (fastboot oem unlock)
13) Device will reboot and be stock once again
14) Put your device back in the Bootloader
15) Flash ClockworkMod Recovery (make sure its the latest one)
16) Boot into Recovery (Wipe data/cache/dalvik)
17) Reboot device
18) Download CM11 & gapps as well as Franco Kernel.
CM11: http://download.cyanogenmod.org/?device=hammerhead (get the nightlies!)
GAPPS: http://wiki.cyanogenmod.org/w/Gapps (I guess the latest one for CM11)
Kernel: http://forum.xda-developers.com/showthread.php?t=2508284 (get at least r20 if its not still the latest)
19) Place zip files on device
20) Reboot into recovery
21) Do another Data wipe/cache
22) Flash CM11 & GAPPS
23) Reboot device
24) Reboot into recovery again
25) Finally flash Franco Kernel (ONLY if your on 4.4.1, if your 4.4.2 use CM kernel but use INTERACTIVE Min: 300 | Max: 1985 (or so).
It may sound redundant and there may seem to be waaaayyyyy too many steps but these are the exact steps I took and I no longer have the issue. *Fingers Crossed* It may not work for everybody and I cannot be held responsible if something was to happen to your device from following these instructions.
Now my cache wipes super quick with CWM
**UPDATED**
So my Nexus 5 worked fine for awhile and now it is rebooting randomly at several different times without notice. I originally had it on AT&T then swapped it to Sprint, and another user below chimed in having similar issues with T-Mobile. The device seems to work just fine in your hands and will not restart, unless your using an application that will freeze, Hangouts, GPS, Google Play etc. The device almost always will reboot during GPS navigation, but the strange part is the device will be just sitting on the table next to me, no one touching it, no applications running and it will just start rebooting. If I leave it be and not touch it, the device will contain to reboot several times. Google applications hang up a lot and cause reboots when actually in use and I've been rebooted during calls several times.
Info on the reboots:
These reboots do not seem to be the normal "hard reboot" its more like a "soft reboot" whereas the phone cuts off, you see google, then the animation for a split second and its back up within seconds bypassing any lock screen you may have in place.
Things I've tried:
1) Factory reset using the zip file provided on the google site (e.g. running flash_all.bat) which restored any and all partitions, and stock recovery
2) I've tried rooted, unrooted, custom roms, stock roms, unlocked bootloader, locked bootloader, it doesn't matter, nothing changes
3) When I did the last attempt at a factory reset (yes as crazy as it sounds I did this several times thinking I was crazy lol) I left out the sim, didn't log into google and purposely left off ALL 3rd Party applications, therefore only running GOOGLE installed default apps (updated of course), and STILL reboots.
It seems sort of a lost cause, I am almost sure it is hardware related and have already put in my RMA, the phone should be here shortly. In the meantime if anyone has any ideas or is experiencing this same thing please chime in.
Video of single reboot:
http://youtu.be/Ss_zDxnD6jc
Correction it will randomly reboot regardless of the carrier and I am unsure maybe it is when it is losing coverage or something but it is either a bug or possibly a hardware issue. I have even used the Google method of restoring the phone to factory settings which also removes the custom recovery so the next thing that I will try is to relock the bootloader after another factory refresh.
Sent from my Nexus 5 using xda app-developers app
ssconceptz said:
Correction it will randomly reboot regardless of the carrier and I am unsure maybe it is when it is losing coverage or something but it is either a bug or possibly a hardware issue. I have even used the Google method of restoring the phone to factory settings which also removes the custom recovery so the next thing that I will try is to relock the bootloader after another factory refresh.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I've got the same problem using T-Mobile. Can't figure out any common cause behind it and it seems to be completely random. Further it seems to not be a full reboot. My phone's data is encrypted so I have to enter my password on phone start-up but it never prompts me to do so whenever I experience these reboots. I was running logcat overnight to see if I could catch it rebooting, but it never did ... until a few hours after I unplugged my phone.
As an FYI, I'm running the stock ROM, rooted
I even reset my phone completely and had no 3rd party apps, still having the issue. I am having mine replaced. I am not factory ROM unrooted and locked bootloader, still having the issue.
Sent from my Nexus 5 using xda app-developers app
ssconceptz said:
Correction it will randomly reboot regardless of the carrier and I am unsure maybe it is when it is losing coverage or something but it is either a bug or possibly a hardware issue. I have even used the Google method of restoring the phone to factory settings which also removes the custom recovery so the next thing that I will try is to relock the bootloader after another factory refresh.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I agree when the reboots happen it comes back up really really quickly.
Sent from my Nexus 5 using xda app-developers app
ssconceptz said:
I agree when the reboots happen it comes back up really really quickly.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Sounds like a service or app is hanging in the background and causing the phone to do a hot reboot.
ssconceptz said:
I even reset my phone completely and had no 3rd party apps, still having the issue. I am having mine replaced. I am not factory ROM unrooted and locked bootloader, still having the issue.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Since you're RMAing it you should probably see if you can run some hardware stress tests to force it to reboot, if it turns out to not be the hardware you'll just run into the same problems with the new one
ssconceptz said:
I agree when the reboots happen it comes back up really really quickly.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
My original thought but how do you explain after having it RMA ready and then no 3rd party apps installed just straight up out of the box nexus 5 and still getting the reboots?
Sent from my Nexus 5 using xda app-developers app
dabbill said:
Sounds like a service or app is hanging in the background and causing the phone to do a hot reboot.
Click to expand...
Click to collapse
What do you recommend. I'm almost sure its hardware. The thing freezes on various apps and I've had the phone reset several times with no apps installed other than the ones that come on the device and it still does it. Even the guys at sprint reset it, laid it down and it just starts rebooting without anyone touching it or opening an app. I will make a video to have a but of proof to work from.
Sent from my Nexus 5 using xda app-developers app
Maybe it has something to do with what apps your freezing. Maybe even ART if your using ART?
Sent from my Nexus 5 using Tapatalk 2
Not using ART. Im not even rooted. I literally went to the Google site, downloaded the zip file, went to the boot loader, ran the flash all .bat file which completely restores the device. I then proceeded to wipe the device, relock the boot loader and even the internal storage was cleared.
After all was said and done, I booted the phone, didn't log in with my Google, went back into gmail and logged in and only updated the Google apps, did not install a single 3rd party app at all. I left the phone alone for awhile then the reboots started.
I went to the sprint store and on the way there (10 min drive) the phone was untouched and rebooted several times. I sat at sprint for maybe an hr, they reset it again and let it sit, same happened, they ordered a new one.
I wish I had a solution, I really do.
Sent from my Nexus 5 using xda app-developers app
I can say it happens during Google apps mainly so Maps during GPS every single time, Google Music, and Hangouts are the primary apps it occurs in and they freeze become unresponsive then it hot reboots.
Sent from my Nexus 5 using xda app-developers app
You have Sprint T-Mobile and At&t all at once?
Sent from my Nexus 5
LMAO good point. Phone was purchased and activated on AT&T simply by inserting my Sim card. I used it for awhile and this issue occurred. I then moved the device to Sprint by going into the store and getting a Sim. Issue still occurred and I've even tried swapping back between the 2. I thought it was sprint related but not the case. As for T-Mobile someone else chimed in and had an issue with that carrier. I could potentially remove that from the title.
Sent from my Nexus 5 using xda app-developers app
When you mean you downloaded the Google zip file, you mean the full android image installed through the bootloader?
Do you know how to format, install the android image from fastboot and replacing the recovery?
If not, just RMA the device. Probably physical, just wanted to factor out any possible software issues.
Sent from my Nexus 5 using Tapatalk
You say it reboots on T-Mobile and Sprint but not AT&T.
Are you in LTE coverage for all three? T-Mobile and Sprint both use higher frequency LTE (AWS & PCS). AT&T, in most areas, uses 700 MHz LTE. I wonder, then, if the culprit is some sort of hardware defect in just your unit, tied to higher LTE frequencies?
Sanity check: Try disabling LTE the moment the phone boots up. Lock it to 3G. Can you still get the reboots to happen now?
I remember way way back in the Nexus One days, I had the AWS model of the Nexus One and was running it on Rogers Canada. Whenever it was on 2G/EDGE and using data, it would behave as if I was slowly moving the trackball to the left. Some sort of funky electrical crosstalk. Faulty unit. With RMA I got one without the issue.
So I installed catlog so I could track down a reboot right after it happened and according to the log, Binder is segfaulting ... while trying to garbage collect ( or at least garbage collection got called by a malloc).
Code:
12-04 06:38:38.272 F/libc (7847): Fatal signal 11 (SIGSEGV) at 0x00000020 (code=1), thread 7857 (Binder_2)
Code:
12-04 06:38:38.472 I/DEBUG (13195): backtrace:
12-04 06:38:38.472 I/DEBUG (13195): #00 pc 000372d8 /system/lib/libdvm.so
12-04 06:38:38.472 I/DEBUG (13195): #01 pc 00028ef8 /system/lib/libdvm.so (dvmHeapBitmapScanWalk(HeapBitmap*, void (*)(Object*, void*, void*), void*)+100)
12-04 06:38:38.472 I/DEBUG (13195): #02 pc 00037784 /system/lib/libdvm.so (dvmHeapScanMarkedObjects()+44)
12-04 06:38:38.472 I/DEBUG (13195): #03 pc 000293dc /system/lib/libdvm.so (dvmCollectGarbageInternal(GcSpec const*)+348)
12-04 06:38:38.472 I/DEBUG (13195): #04 pc 00029e94 /system/lib/libdvm.so (dvmMalloc(unsigned int, int)+180)
The only thing I've modified on this device that should affect such low level components is using TWRP to add root capabilties (which I assume just installs an su binary somewhere)
Not sure this is the same problem as ssconceptz but assuming the code itself isn't faulty, it could be a memory problem, after all, the Dalvik VM is the thing that's crashing. This is probably why it's a hot reboot and not a full system crash since 'only' the java process is crashing.
I ran StabilityTest v2 for 15 minutes and nothing popped up -- I'll probably have to run it for longer to find any errors.
Does anyone know of any method of testing the RAM of a phone? I'm guessing there's no port of Memtest lying around somewhere.
At this point, it might not be a bad idea to assume it's the phone and begin the RMA process. It's a pity that I'm outside the 15-day return window as I might be tempted to just return it and get a Moto X.
ssconceptz said:
LMAO good point. Phone was purchased and activated on AT&T simply by inserting my Sim card. I used it for awhile and this issue occurred. I then moved the device to Sprint by going into the store and getting a Sim. Issue still occurred and I've even tried swapping back between the 2. I thought it was sprint related but not the case. As for T-Mobile someone else chimed in and had an issue with that carrier. I could potentially remove that from the title.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, it pretty much does it all for you but I know how to do it.
Sent from my Nexus 5 using xda app-developers app
chrisinsocalif said:
When you mean you downloaded the Google zip file, you mean the full android image installed through the bootloader?
Do you know how to format, install the android image from fastboot and replacing the recovery?
If not, just RMA the device. Probably physical, just wanted to factor out any possible software issues.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I need to update my original post. It happens on any carrier I've tried. I see what your saying but with sprint you don't set it to LTE you set it to Global.
Sent from my Nexus 5 using xda app-developers app
cmstlist said:
You say it reboots on T-Mobile and Sprint but not AT&T.
Are you in LTE coverage for all three? T-Mobile and Sprint both use higher frequency LTE (AWS & PCS). AT&T, in most areas, uses 700 MHz LTE. I wonder, then, if the culprit is some sort of hardware defect in just your unit, tied to higher LTE frequencies?
Sanity check: Try disabling LTE the moment the phone boots up. Lock it to 3G. Can you still get the reboots to happen now?
I remember way way back in the Nexus One days, I had the AWS model of the Nexus One and was running it on Rogers Canada. Whenever it was on 2G/EDGE and using data, it would behave as if I was slowly moving the trackball to the left. Some sort of funky electrical crosstalk. Faulty unit. With RMA I got one without the issue.
Click to expand...
Click to collapse
I tried several tests myself with no luck. I'd recommend doing what I did and go all the way back to stock and see if it occurs, it does for me and its a hot reboot as the phone comes back up fast bypassing the lock screen. Happens most often when I'm not using the device or during Google application use. Most if the time if its in my hand and it doesn't freeze there's no issue. Its very annoying though. I may root today to get a logcat before I return it.
Sent from my Nexus 5 using xda app-developers app
Moto G 16GB, bought off Amazon.co.uk. Rooted and flashed 4.4.2 before it was pushed to the device (I think it was an image off US version, found it in these forums back when I got the phone). I've been getting a prompt to install some Motorola US update for a few weeks, it pops up every now and then, has gone away when I tapped "No, thanks" option. All was fine until this morning...this is a really weird problem.
I don't know if the phone updated itself overnight, but when I dismissed the alarm this morning I couldn't get past the lockscreen. I put in my lock code and the phone had the stock wallpaper, then cycled to black background, then back to stock wallpaper and then I got a pop up saying "Unfortunately, the process com.android.systemui has stopped." and I was bumped back to the PIN lockscreen. Tried again, same thing. Now it doesn't even say anything about androidui, just cycles between black background and stock wallpaper and kicks me out.
Tried hooking it up to a PC and Mac, but neither recognized it and the phone appeared to be just charging. Power cycled it a dozen times by holding down the power button for about 6 seconds and I always end up with the same problem of not getting past the lockscreen. Every time I boot the phone now it says "Android is upgrading... Optimizing app 1 of 1". This is why I thought maybe I was pushed some incompatible US update?
Underneath it all the phone works fine, got the alarm this morning, received an SMS, answered a phone call. I can even get to the camera from the lockscreen. Is there any other options besides complete wipe and starting from the beginning again?
Probably OT, but I've always had trouble with the launcher quitting, no matter what launcher I'm using, on Moto G and the previous GNex.
Any help is appreciated, I'm bummed.
Hi,
i've today the same, exactly the same problem. It's strange, because i can't reset my phone to factory default, i went to the recovery menu, then "factory", but it only rebooted...
My "solution":
I reinstalled the original firmware:
http://forum.xda-developers.com/showthread.php?t=2542219
Then all works fine.. No matter why this error occurs.. an automatic firmware update? ..i don't know...
the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!
Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.
hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
electrictimes said:
Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.
Click to expand...
Click to collapse
my phone wasn't even rooted, pure stock kitkat, i'm taking my heavy ass old notebook with me and will spend my days off trying to fix this **** it seems
a.monteiro said:
hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
Click to expand...
Click to collapse
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!
a.monteiro said:
the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!
Click to expand...
Click to collapse
Same situation....
ifishy said:
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
Click to expand...
Click to collapse
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
zofari said:
I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!
Click to expand...
Click to collapse
Just reminded me that my phone is still within warranty, doing this restore may void it?
a.monteiro said:
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
Just reminded me that my phone is still within warranty, doing this restore may void it?
Click to expand...
Click to collapse
My phone is back working..at the cost of wiping out all my data.
zofari said:
My phone is back working..at the cost of wiping out all my data.
Click to expand...
Click to collapse
Guess this is the only way out of this, then. What a mystery... I wonder if this is the "Welcome to Lenovo" update 1.0 lol.
i'm getting a "missing AdbWinApi.dll" although i've installed all the applications required, any help?
edit: guess i also need the android sdk, right?
edit2: got it, just copy the dlls from the minimal adb directory into the firmware directory and it's good to go, just configuring my newly restored device, thanks all
I wonder why this happened? I was using google play store at the moment, updating the flipboard app...
a.monteiro said:
I wonder why this happened? I was using google play store at the moment, updating the flipboard app...
Click to expand...
Click to collapse
I guess It's the problem of flipboard app!
My father's phone is also experiencing this issue, I can't even reset the phone to factory settings.
This occurred when I was also updating the flipboard app... seriously I'll have to RMA this...
----------------------
So I also have an issue where when you unlock the screen, it just locks back up (no android dialogue saying that com.android.systemui has crashed, but the same result).
I'm also unable to go into bootloader -> Recovery to factory reset the phone.
I stupidly tried to uninstall the flipboard app and reinstall it and it killed the phone... it's now stuck and quite annoying.
I'm 99% sure it's Flipboard.
Looks like others are having issues with Flipboard too
http://forums.androidcentral.com/moto-g/391289-something-seriously-wrong-my-moto-g.html
----------------
I solved the issue by following the instructions here:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
how could a flipboard update screw android so badly? what a strange day
edit: they seemed to have pulled the update back or fixed it though, during my restore flipboard installed without issues
Holy S*** I'm in the same situation. It's definitely the Flipboard update that caused everything. Support just acknowledged me but never gave me any solution. I'm running ART and I think that was contributing the problem. It's terrifying knowing how a single app can completely ruin your phone!!
Anyway guys, is there anyway I can save my pics and stuff before I wipe my data?
Good detective work, I now remember updating the Flipboard app w/ bunch of others as well when things were still all good. Could this be remedied if Flipboard would manage to push a working update? I really don't wanna wipe everything, and I'm not sure I can.
Word from Flipboard (via Twitter):
"Flipboard does not support the experimental OS ART at this time."
Hi, I recently downloaded Flashify and the TWRP img and used it. However, when I booted the .img into Flashify, my touchscreens input (the action when you tap your phone screen), not the touchscreen orientation. The Input has flipped left-right or horizontally. So lets say there are 4 apps on the dock. If i clicked the 1st one, I get the 4th. 2nd = 3rd, 3rd = 2nd, and 4th = 1st.
Please tell me how to fix this. If there is an easy way like using build.pro to somehow flip the touchscreens input because the hwrotation=180 only changed the orientation.
Any help is appreciated, thank you.
I have rebooted, Settings>Restore, Cleared cache dav cache internal storage, advanced clean through recovery
Reflash with stock 5.1.1 ROM via odin.
Can't Ive been trying. It keeps getting stuck at "Complete(Write) operation failed"
I used Odin successfully before this to update to 5.1.1 from 5.0.2
It's also recognizing my S6 as the S6 Edge
I Dl'd the driver already
Should I also be using the G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_HOME.tar or the G920TUVUCOF6-20150615115627.tar?
Okay it finally worked. It didnt fix it and it removed my root. So even worse than before.
phongle123 said:
Okay it finally worked. It didnt fix it and it removed my root. So even worse than before.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=3167666
I believe this will help. It'll tell you how to manually fix it and also how to get the correct version of twrp for your phone
drock212 said:
Look here http://forum.xda-developers.com/showthread.php?t=3167666
I believe this will help. It'll tell you how to manually fix it and also how to get the correct version of twrp for your phone
Click to expand...
Click to collapse
HAHAHHAHAHA!!! I looked at the one that said T-Mobile and instantly clicked it instead of actually looking at the name. It WAS indeed for the Edge, the left - right inverse does not happen anymore. This isn't fixed with a reflash or reboot or changing to correct TWRP. You need to refix it in phone>*#2663#
EDIT: To any others that have this happen. Even if you fix it with the phone>*#2663#, if you go back into the EDGE Variant TWRP it will make it back to left - right inverse. You need to change it to the right TWRP variant first otherwise going back to the wrong TWRP will mess it up again.
Thanks for that, I overlooked it.
So I've "successfully" updated to v8.0 using the above method. I'm currently on build 2CQL1. I updated from AQH7 to 2BQJA and then to CRA4 using the Samsung Firmware Science downloads. My phone is stock AT&T (not unlocked), and is not rooted. When going to CRA4, I encountered a pretty significant error which continues to plague me. I've searched through the forums and haven't read anything on similar to this issue. I cannot use Always on Display. It has to be turned off, and..I cannot take the update in Google play for the Always on Display app. If I try and take the update, the phone goes into this weird state: Screen dark except for the edge indicator. Phone will vibrate three times, but screen will remain dark. Only options I have is to try and restart or turn off. I was able to get into the recovery menu, and do a reset to factory settings. However, upon doing that I noticed that I was running build 2CQL1. After doing this a couple of times, I finally figured it out it was the AOD that was giving me issues. So I disabled it in the phone settings, and will not take the update in Google Play.
Update: Now, I'm getting the vibrations randomly, even with AOD turned off. The phone is still functional, but I fear I may have to reboot and do a reset at any moment.
Anybody have any thoughts on how I can get back to a stock version of ATT software? Again, I don't need to root or even unlock my phone. Just looking for the stock software so I can have a functional device.
Thanks in advance
Lavman72 said:
So I've "successfully" updated to v8.0 using the above method. I'm currently on build 2CQL1. I updated from AQH7 to 2BQJA and then to CRA4 using the Samsung Firmware Science downloads. My phone is stock AT&T (not unlocked), and is not rooted. When going to CRA4, I encountered a pretty significant error which continues to plague me. I've searched through the forums and haven't read anything on similar to this issue. I cannot use Always on Display. It has to be turned off, and..I cannot take the update in Google play for the Always on Display app. If I try and take the update, the phone goes into this weird state: Screen dark except for the edge indicator. Phone will vibrate three times, but screen will remain dark. Only options I have is to try and restart or turn off. I was able to get into the recovery menu, and do a reset to factory settings. However, upon doing that I noticed that I was running build 2CQL1. After doing this a couple of times, I finally figured it out it was the AOD that was giving me issues. So I disabled it in the phone settings, and will not take the update in Google Play.
Update: Now, I'm getting the vibrations randomly, even with AOD turned off. The phone is still functional, but I fear I may have to reboot and do a reset at any moment.
Anybody have any thoughts on how I can get back to a stock version of ATT software? Again, I don't need to root or even unlock my phone. Just looking for the stock software so I can have a functional device.
Thanks in advance
Click to expand...
Click to collapse
//N950U ATT\\ Stock Odin Files Firmware N950USQU3CRC2
https://r.tapatalk.com/shareLink?sh...ers.com/showthread.php?t=3783711&share_type=t
Sent from my iPhone using Tapatalk
jerrycoffman45 said:
//N950U ATT\\ Stock Odin Files Firmware N950USQU3CRC2
https://r.tapatalk.com/shareLink?sh...ers.com/showthread.php?t=3783711&share_type=t
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Thank you for the response. Can I just download the .zip file to my phone's SD care from the link and install it from the Recovery menu?
Lavman72 said:
Thank you for the response. Can I just download the .zip file to my phone's SD care from the link and install it from the Recovery menu?
Click to expand...
Click to collapse
no you need a computer
This is all set. I downloaded the latest official AT&T update, and installed using ODIN. Thanks to everyone for the assistance. It had been a while since I had done anything like that. Back to the Samsung Infuse days.