I need help getting a logcat while my phone is shutting down and also while it is booting up.
Here is some history of my problems which will explain why I need to do this.
Note 3 sm-n900v
Currently running OF1 firmware and Alliance t-mobile rom
Rooted and unlocked bootloader TWRP recovery
I got this phone used for cheap and thought it would be an easy fix. I started with a clean odin of the stock OF1 firmware to put it in factory condition. Everything went great and had good signal and 4G LTE ran smooth and set up with no problems.
After the first time I rebooted the phone I had no signal. Checked About phone and my IMEI, baseband and serial number were gone.
I reflashed the phone in odin and everything was back. Another reboot and all is gone again.
I have tried different roms after rooting including some AOSP roms and always the same result.
I have checked to make sure that the phone wasen't a victim of the "NVbackup/restore" bomb and my NV partitions do not seem to be corrupted.
When I power off the phone it seems to take a long time to shut down (1-2 min.) so I suspect that something is being rewritten on the phone during a reboot. This is why I need to get the logcats so I can have some wizard/guru/hero/Android God read them for me and hopefully tell me what is happening to the phone and how to fix it.
I can work in ADB if someone would be kind enough to give me the commands needed to get the logs and where to post them or who to send them to for help.
I'm old but not stupid. Just an old fart that needs some help getting across the Android freeway.
Thanks in advance to anyone that can help.
Loaderboy
"got the phone for cheap" - did you call Verizon and inquire if the ESN was blacklisted?
If not, I would inquire before trying anything else.
(for shutdown; assumes you are rooted.)
Code:
adb shell
su
cd /data/local/tmp
cat > watcher.sh
#!/system/bin/sh
cd /data/local/tmp
logcat -c
logcat -v threadtime > watch_shutdown_logcat.txt 2>&1
^D
chmod 755 watcher.sh
./watcher.sh 2>>/dev/null &
exit
then reboot.
I know it's a pain in the butt to re-Odin the phone & re-root in order to run a single experiment, but you might also try the reboot cycle with the phone in airplane mode (or better yet in a location where you know you do not have a cell signal) to see if that has an effect.
Does the rooting process require a reboot? If so that would seem to be a chicken-and-egg problem - if your IMEI gets wiped on the first shutdown, then it would be hard to install a new ROM to find out whether it is carrier ROM software that is performing the changes.
Other possibilities: an intermittent hardware problem that is being mis-diagnosed as software behavior. If this were the case, occasionally the problem would appear even after a fresh Odin flash.
Other ideas include performing checksum (md5) signature comparisons on the stuff in /firmware and /firmware-modem before and after reboot to see if anything is changing, e.g.
find /firmware /firmware-modem -type f -exec md5sum {} \;
PS This advice doesn't mean I'm planning on helping you examine your logcats, but you should feel free to put them in a pastebin and provide the link here. You might want to scrub the file of any personal or device identifier information before you do that.
No the phone is not blacklisted, first thing I thought of. The problem happens on Verizon and Tmo roms alike.
The last time it lost the IMEI and baseband I got it back when I flashed Alliance rom but I havent rebooted since. The phone didn't lose root so I think I can experiment without odining the stock firmware and rerooting.
I will get the shutdown logcat and see if I can find anything before posting it.
Thanks so much for your quick reply.
The observation that it is ROM-independant is significant.
That would suggest that it is less likely to be due to a piece of application software unless all the ROMs carried the same application/code, or the functionality was coming from the TrustZone, or perhaps code in a kernel shared in common between ROMs exhibiting the behavior.
You seem to be suggesting that it can be corrected by simply flashing a new ROM. Normally that only involves the /system, /cache, and /data (when you wipe) partitions not the /firmware or /firmware-modem partitions.
It's just one hypothesis, but my money is on flaky hardware that causes a failed initialization during boot up. Evidence for that might be:
(1) boot the phone several times after you lose IMEI, both warm reboots as well as shutdown/boot and shutdown/battery pull&reinsert/boot. If it comes back up during any cycle... flaky hardware. (Note also that if you put the phone on the charger when it is "off" it actually performs a "silent boot"... I think the bootloader does this by providing the kernel with an alternate (skinny) ramdisk. In any event, many pieces of hardware could be fully powered up & kernel initialized when doing this, so potentially this could affect flaky hardware. Just be aware of it so you are correctly appraised of "how many time did I boot this thing?")
(2) Alternatively, NOT recovering service in a reproducible manner (e.g. flash & boot a ROM 4 or 5 times using the exact same procedure and one of those times service is not restored) also would be indicative of intermittent hardware troubles.
(3) if you have TWRP installed and the problem was due to some stateful behavior (e.g. something recorded into a file on the previous boot), performing a full wipe of /data might alter the behavior as that is the most likely place for it (esp. since you say that ROM flashing cures the problem). Try wiping & booting several times - does the problem come & go?
well I rebooted and lost signal. I then booted to TWRP and wiped data and still no signal.
I did this 3 times and no signal. Then I wiped dalvik /art cache and cache without wiping data and signal is back.
Getting closer. I will reboot to lose signal and then reboot to TWRP and wipe each one seperatly to see if I can narrow it down.
Stay tuned.
Wiped dalvik/art cache and signal is back. Tomorrow I will restore my stock backup and see if it works on that as well.
Thanks for giving me the tips on where to look. If it works on the stock rom I will then have to try to find out what is causing this to happen.
... and the result is?
.
bftb0 said:
... and the result is?
.
Click to expand...
Click to collapse
Flashed stock backup and everything was there. reboot and it's all gone. Boot to recovery and wipe dalvik cache and baseband IMEI etc. all back.
Sorry for the long break but spent the weekend moving a friend.
Sent from my SM-N910P using Tapatalk
loaderboy said:
Flashed stock backup and everything was there. reboot and it's all gone. Boot to recovery and wipe dalvik cache and baseband IMEI etc. all back.
Sorry for the long break but spent the weekend moving a friend.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Looks like you have your work cut out for you. Somehow I doubt you are going to find something meaningful inside of /cache, but I'd look there first since that is likely to be the simplest in terms of effort.
I suppose you could try a binary division method of manually deleting half of the .dex files and the corresponding entries in places like
/data/system/packages.xml
/data/system/packages.list
/data/system/install
/data/system/users/0/package-restrictions.xml
/data/system/users/0/runtime-permissions.xml
and then iterating (the divide the right group by half) but thats gonna get tedious fast - and possibly just cause bootloops or hangs.
Frankly, I still think there is an underlying bit of flaky hardware - if the ESN was clean, what would be the point of software being intentionally coded to "turn off the phone" on an otherwise clean ESN device, and a completely vanilla ROM (i.e. no personalization by initialization of a Google account credential, no market apps, etc).
If you decide to use logcat and you discover that you need to launch on boot because the logs are rolling over before you can manually run a logcat (very likely because of the long Dalvik rebuild times), you will either have to choose a ROM which has a hook for auto-starting a script (e.g. CM13 userinit.sh files), or you have to re-pack the boot image to execute a one-shot service during late boot (customizing init.rc), making sure to put the logcat invocation into the background so the service doesn't block init. In both those cases, make sure you write the log to someplace like /data/local/tmp - you can't use /sdcard as the automounter tends to mount it quite late in the boot.
good luck
Related
okay so after trying some other options i was able to solve this problem, here is the how to in case this has happened to anyone else. my original post is below the how to.
1.flash the sbf that returns your defy to stock eclair using a different T-Mobile sim, after it is done flashing you will seem to still have the problem, except it will say no sim emergency calls only.
2.power off the device and install your original sim from T-mobile.
3.reboot the device and you will not be prompted to setup motoblur, because you device is in soft brick limbo still, but you will have laggy touch responses, be patient with your device as you navigate to settings>privacy>factory reset and confirm. ( this process will take much longer than usual and the progress bar will not show any progress but it will shutdown and reboot as it normally would with a factory reset)
4. you will now be prompted to setup your motoblur account ( if you are not restart the steps until this happens, if it does not happen your device did not actually do a factory reset you will need to try again until it does ask you to setup blur, this is your sign from the moto gods that your device is no longer in softbrick limbo)
5. setup your blur account ( you will still have no recovery menu at this time so don't try and check or you will have to start back over at step one)
6. now navigate to settings>about phone> check for updates
7.download and install the update to froyo ( durring downloading you phone may shut off several times, however if you reboot it will automatically pick up the update where it left off as if your device never powered off to begin with)
8. once you have installed the update you device will be back to froyo stock and your recovery partition will no longer be bricked
9. enjoy your defy once again, and be more careful with your device in future ROOT mods and tweaks, cheers!
10. If this helped you recover your device please thank me for this solution.
okay so i am new to posting on XDA and i will try to organize my problem as best as possible, but i may need much guidance on if i am posting in the proper forum.
here are my details of my device and the problems i am facing with my device currently.
Motorola Defy
MB525
T-mobile US
stock Froyo rom 2.2.1 ROOTED overclocked with milestone overclock to 1224 mhz @ 85% voltage /V6 SUPERCHARGER SCRIPTS. MODDED BUILD.PROP TO REFLECT THE MAX HSUPA CATEGORY 34/MAX HSDPA CATEGORY 36/ GPRS CLASS 10/ HSXPA=2/RO.RIL.VIDEO_MODES=TRUE EVERYTHING ELSE IN BUILD.PROP WAS STOCK EXCEPT WHAT THE V6 SUPERCHARGER SCRIPTS CHANGES. I was running a custom bootscreen that i placed in the location of the old one using ES file explorer with root browsing rights, i had defy Recovery installed but only used it basically as a system restore app ( context of previous statement is relating to system restore if you were talking about a windows machine) used Avast anti virus as root installation w/antitheft installed used system tuner to manage startups down to core services or other services i did want to run at boot i.e. stuff like facebook and weather channel.
DEVICE WAS ALSO SUBSIDY UNLOCKED
SBF started with and reflashed to try to correct problems was JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.OR_JORDANTMO_PO22_HWp3_SERVICE1FF.sbf
****NOW TO THE PROBLEMS****
I was starting to think that maybe the v6 supercharger scripts were not really doing anything performance wise for me as it would disable my overclock settings at boot and i would have to manually invoke them after everything had requested its SU rights at boot. so i decided to get rid of the v6 supercharger scripts and all other softwares pertaining to managing and running the scripts, I decided the best way to do this was to do as i had always done in the past when wanting to re-tweak my phone and use the stock recovery to start fresh with 0 tweaks and only apply the ones i wanted after restoring to stock, when i used the stock recovery this time it didn't work, i booted the phone back up after wiping data/ factory data reset and to my surprise the recovery did nothing but delete the SU.apk the custom boot was still in tact, everything else listed above still in tact except for the phone was obviously throwing errors left and right because there was no SU for apps to request permissions from, so i reinstalled the SU.apk just to make sure i didn't have to deal with the device being slow while restarting the process of doing a full wipe. this time i used the DefySDrecovery.apk i mentioned above to do the same steps and while adding wiping the dalvik cache after wiping data and before invoking the recovery, it then gave me the same error i have always gotten when wiping the cache which is
e:\ cant mount cache partition
e:\ cant find /recovery/caller
e:\ cant find/recovery/cache
(this has never caused problems with the device once recovery was finished)
this time however I was only able to boot(loop) to the moto logo
so i reflashed The above mentioned SBF and the device booted normally i went through the entire setup like it was a new device with blur and google and it finished. when I got to the home screen it was frozen and would not respond to touch it also showed to have no cellular signal, i turned it of and back on and it made me go through blur and gmail setup again, went to home screen same thing frozen with no signal.
i reflashed the SBF again thinking maybe something went wrong as they do sometimes with RSD yet still finished and passed on everything
the above description repeated except for this time it responded to touch for the first few seconds before it froze completely ( oops! sorry one detail to add when i say it froze i mean froze like would respond to nothing, touch, hardware buttons, nothing) i had to pull the battery in both instances to try and start over, after many attempts of getting in the phone and trying to turn on usb debugging before it froze i finally was able to complete the finger olympics and get usb debugging turned on, i was able to root it using superoneclick so that i could have a look at the logcat in ADB. now in my experiences with ADB normally when you run a logcat command it will print to the screen for about two to three hundred lines and then slow down and only print one to six lines at a time as the server is calling actions when i ran a logcat on this device it runs two to three hundred lines slows down and then runs lines until you close the ADB window i let it run a logcat overnight and it was still running lines the next morning with no sign of stopping where you could freeze the window and read over all the crap it was calling to action, looking at the device durring this process i saw force close windows a few times saying the com.android.process has stopped but the home screen never crashed and the phone didn't do a random reboot. so to sum it all up ( so sorry for the lengthy explaination but i wanted you to have the whole problem fully explained in hopes you wouldn't have to ask for more detail)
it freezes and has no service with my T-mobile sim in it ( if i put my at&t sim in it has service but still freezes)
flashing a new SBF doesn't fix the problem as it should
and there is no way to enter the Recovery Menu now its gone, non existant, cant find it, cant fix it, i'm F***** right now Please help if you know how, and if i totally screwed the phone i'm cool with you saying so but it can still be in a respectful way i already feel like an idiot for not being able to correct this with all the knowledge i have of this phone, a negative attitude insinuated is not going to help me in either direction, thanks in advance for any help you may be able to provide.
I recently decided to take the oplunge and un-moto my Defy with a Quarkx CM 10.2 build (cm-10.2-20130801-NIGHTLY dev thread:http://forum.xda-developers.com/showthread.php?t=2385250).
I've been running it for 2 weeks or so without what much trouble until this morning, I forgot to plug it in, so it discharged over night (was working before i went to sleep). I had some trouble powering it up this morning, figured it was discharged, now it does not boot at all, and has not booted yet. It sticks to the CyanogenMod boot icon.
It's currently charging at 100% for a wile longer (as per these instructions http://forum.xda-developers.comhowthread.php?t=1778492), but i don't know what to do next without a re-install.
I have some other specific bugs to report but cannot post to the dev thread ( as i'm a Newb and this is my first post.
- Voice capture/use with BT Headset (known)
- BT on cannot use headset mic (known)
- Focus+Camera problems (Known)
- ~10hr battery life (known)
- Bare GPS without extra google assistance not working with Maps threshold to high? (?)
Backup data from recovery, reinstall cm10.2, don't wipe data, wipe cache. If it doesn't work then wipe data and cache. You should get it to boot, and then restore apps from backup using titanium backup
Look for the GPS thread in General, edit the file as given there. Should help with the GPS locks
Sent from my MB526 using Tapatalk 2
thekguy said:
Backup data from recovery, reinstall cm10.2, don't wipe data, wipe cache. If it doesn't work then wipe data and cache. You should get it to boot, and then restore apps from backup using titanium backup
Look for the GPS thread in General, edit the file as given there. Should help with the GPS locks
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
I used TWR to clear the davik cache, and the system booted, then did the davik byte compile ('Android upgrading apps screen) then went to starting apps anf failed there. I will as you say, but before i do, is there any way of tracking down what is happening? I'm mounting the various fileystems from the boot USB mount tools, and would like to know where to look for some logfiles or other.
I have been poking around, (using ls -alrt to see what was last accessed) and not come up with anything, so now i want to watch boot messages with adb logcat (as described here cyanogenmod.org/w/Doc:_debugging_with_logcat) , but i have no idea how to enable them. Its either that or try and figure out how topipe the kernel console over USB.
Which is redonkulous because if the davik is compiling, then its not a kernel problem, its something else later in the boot sequence, long after adb/logcat should be throwing out errors.
Any pointers? I would honestly like to fix this instead of wipe, because I have not got a Titanium backup knocking about of the phone prior to this failure. Or rather i do, but its a week or two old.
It's not a kernel issue. Most likely your data partition is corrupt, and there is really no easy fix for that. You should first take a backup of it, and then you could try to salvage it using titanium backup (if really lucky) or a Linux distro to try and recover some data(it's basically a ext4 partition image)
I don't think it can be fixed from the device end.
For boot logs: http://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging
Enable adb in boot menu before that
Also, kernel logs can be obtained via a UART cable. But I'm not sure how they can help you fix this issue
Sent from my MB526 using Tapatalk 2
Something in Data was the problem.
I had to do a complete reinstall and rebuild to get it working.
Is there any way to avoid/diagnose this kind of problem other than daily backups and making sure it never ever runs out of power (the battery reporting is all over the place!)
thekguy said:
It's not a kernel issue. Most likely your data partition is corrupt, and there is really no easy fix for that. You should first take a backup of it, and then you could try to salvage it using titanium backup (if really lucky) or a Linux distro to try and recover some data(it's basically a ext4 partition image)
I don't think it can be fixed from the device end.
For boot logs: http://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging
Enable adb in boot menu before that
Also, kernel logs can be obtained via a UART cable. But I'm not sure how they can help you fix this issue
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
I hack embedded linux as a day job, so know something about this already, though I'm a complete cyanogenmod/rom hacking newb.
I tried most of the things you suggested, at least to the point of booting with logcat. Nada.
The problem seemed to be that adb was not coming up. I used the bootloader adb shell to try and force adb to come up (changed an enable from disable in the init.rc) it seemed to make matters worse, so i went for the rebuild.
I performed a TWRP backup of the system and data partition before doing any of this. I know the backup was working because i restored the system partition and blew away the data partition, and it booted.
What i want to do now is restore some of the data from the data partition (call logs and SMS etc, everything else can be re-created). How, where would i look for that?
t1moc said:
I hack embedded linux as a day job, so know something about this already, though I'm a complete cyanogenmod/rom hacking newb.
I tried most of the things you suggested, at least to the point of booting with logcat. Nada.
The problem seemed to be that adb was not coming up. I used the bootloader adb shell to try and force adb to come up (changed an enable from disable in the init.rc) it seemed to make matters worse, so i went for the rebuild.
I performed a TWRP backup of the system and data partition before doing any of this. I know the backup was working because i restored the system partition and blew away the data partition, and it booted.
What i want to do now is restore some of the data from the data partition (call logs and SMS etc, everything else can be re-created). How, where would i look for that?
Click to expand...
Click to collapse
You can restore the call logs and stuff using nandroid manager.
hotdog125 said:
You can restore the call logs and stuff using nandroid manager.
Click to expand...
Click to collapse
Thanks! That worked.
Though before it did i had to do some cleanup of .comp.comp.comp.comp files - failed decompressions i guess.
nandroid is now going on my essential apps list
Well it happened again.
I was having trouble turning off bluetooth. MortPlayer Audiobook player had decided to keep hold of the BT connection after i stopped the player and turned off the headset. So i tried a reboot, and the phone has not come back up again. Which is annoying because it has been working fantastically until now.
The link to get the adb log does not work. adb does still not come up during the boot sequence.
again like last time I started up adb shell to have a poke around on a running system, and again after 10 minutes the system powered off, and would not power on. Even though it was/should be charging over USB. Now i plug it into the power, and the batter charge indicator comes up saying 5% power. So no idea about how to stop that happening. So far though the boot menu and TWRP works like a charm.
I really want to track down whatever this issue is, but so far hitting a wall. Is there some where i can splice in adb coming up? or get the dmesg/syslog/adblog written the the sd card so i can attempt to analyse the problem?
Hello,
I have a MB525 that I purchased retail in the United States so it was never locked to any carrier. Currently I'm a T-Mobile customer and have no interest in changing that. I have to say I love this phone, mainly because it seems indestructible. Even years later the battery life is still good, but the stock 2.2.2 Froyo has become something of a problem because many of the Apps I would like to use have started requiring newer versions of Android.
I can't stay in the past forever, but I'm not quite ready to give up on this device so I started looking around at my options, and would you believe I found lots of other people who have this device and have worked very hard to produce updated Android OSes for it, and who have reported reasonably good success updating the device. I figured, Its already out of warranty, so I can't void a warranty I don't have. I also figured I'm a reasonably intelligent individual and have enough experience with Unix like operating systems that even if I get in trouble, I'll be able to ask the right questions to get out of trouble. Guess what point I have gotten to?
I started following the guide wikiDOTcyanogenmodDOTorg/w/Install_CM_for_jordan The Framaroot Gimli exploit worked great. I installed bootmenu 6.1 and Clockwork Mod Recovery. Fantastic. At this point, I was able to enter CMR and backup my mostly still factory ROM. If I understand correctly this is a nandroid backup. I copied that backup off of my SD Card to my PC. From this point I felt reasonably confident I could try things and in a worst case scenario restore to this backup.
Now I happen to have a stock ROM that seems to be a bit rare online, Blur_Version.34.4.806.MB525.Latam.en.01, so I figured at this point I'd do a service and create a backup using CWM after having done a factory reset. So I booted into the stock recovery, did a factory reset, restarted, and the OS was in a like new state. Perfect. Rebooted into CWM, and made a second backup of the factory reset state. I copied this off the SD Card to the PC. Now I figured I was ready for real fun.
I figured, I might as well put the most recent Android version I could find that people were reporting success with. This appeared to be @quarkx Kitkat build. The thread is almost a year old and has 500+ replies and so I guessed that most of the major kinks would have been worked out by now. I followed the directions on quarx2kDOTru and installed cm-11-20141015-NIGHTLY-mb52x.zip from Quarx2k.ru, and low and behold it worked. CM11 booted and everything looked great. WiFi worked. Gapps worked. Play store started installing my apps.
There was one small problem. The phone refused to connect to T-Mobile at all. So I did the reasonable thing. I searched and learned about base band switching, and consulted T-Mobile on what would be the correct APN settings. Occasionally it would connect to AT&T for emergency calling, but it never connected to T-Mobile no matter what I did. From my home I was normally getting excellent signal on the stock ROM, so I am reasonably certain that the actual signal in the area was not the problem, and that this had to be some kind of configuration or software issue. A wiser person probably would have gotten on the forum and asked for help, but wisdom be damned, I wanted to do it for myself.
So more research and at some point I thought, Well, I'll go back to the Stock ROM so the phone will be usable again, and I'll take another crack at CM11 again later. It was at this point that I realized that CMR had been replaced with Team Win Recovery Project. This recovery looked to be more feature rich and easier to use, so I accepted that. I backed up my CM11 install. then went to restore my original backup. Well you might have guessed by now that TWRP and CMR don't use exactly the same backup formats. I saw no obvious way to get back to my backup and couldn't find information that would allow reinstalling CMR. This was the first warning signal I foolishly ignored.
At this point I started looking around for slightly earlier builds of CM11 that might not have had the the problem connecting to T-Mobile. Here is where things get fuzzy about how things got into this state, since the work was spread over two days at this point. Somehow between all the flashing backing up and restoring, the device got to a state where the OS never actually finished could do here is yank the battery and reboot into TFRP.
At this point, attempting to restore would just result in the messages 'E: Unable to mount '/cache' and 'E: Unable to mount '/data' in the terminal. So After searching around I learned that I probably needed to format /cache and /data because somehow they were broken. Terminal commands, I can handle this. I start reading up and find the correct command and parameters for the format, and I type into the terminal inside TWRP and low any behold format can't be found. I start looking around the directories in my file system from inside TWRP and I've got a complete directoty structure, but no files in any directories other than on /sdcard. Well fuuuu.
Not sure what made me even try, but copying any file from my sdcard into /data somehow put /data into a state where a TWRP restore would work. So at this point I was able to restore the CM11 backup, and my phone now boots into CM11, 11-20141007-NIGHTLY-mb526. But.... the cellular network still doesn't work.
But now I am wiser and I am back to the point where a wiser person would have asked for help. So... Help?
Is 11-20141007-Nightly-mb526 the best rom an appropriate rom for my device? I'm guessing I missed something because other discussions on this forum mention newer builds, and also, my device is definitely a 525 not a 526.
Is my baseband version EPU93_U_00.60.03 right? The baseband selector allows me to pick from three T-Mobile settings: 3.4.2.-107-4, 3.4.2.-107-9, and 6.xx.0, none of which seems to allow me to connect to the cell network.
Thanks in advance for any assistance offered.
Sorry for the long potato.
Here is what I did to fix my problem.
I started with the original backup of my stock rom, and I used the unyaffs.exe from this thread: http://forum.xda-developers.com/showthread.php?t=1199416 to convert my CMR backup into individual files. I then went into those files, and found \system\etc\motorola\bp_nvm_default\ and pulled out the original radio firmware from my device. From there I used advice from several pages to create my own update.zip, copied it to my SD card and I booted into TWRP and installed the zip there. Reboot and Voila, It connected right at startup to T-Mobile with the normal speeds I get from my home.
Bonus, I attached my zip in case anyone else comes across this and needs it.
My Device has an FCC ID of IHDP56LC1 if that helps anyone match their hardware.
Hey all,
First post here on XDA and I'm hoping someone with more experience than me will be able to give me a hand! Until last week or so, I was running an up-to-date version of Lollipop (5.1.1), when my tablet started randomly freezing up on me, requiring "soft resets" to get it going again, or simply shutting off on me. Thinking it was software related, I tried wiping the cache with no success, so ended up doing a full factory reset. The issues *seemed* to clear up for a day or so, but came back, and so figuring it was Lollipop related, I wiped out the OS and installed CM12.1 (which was my first experience working with ADB and fastboot, and first time installing a non-stock ROM) with a TWRP recovery. A few days later, the freezing and shutting down issues began popping up again, with the shutdowns *usually* happening during sleep, but the freezing happening at anytime from initial "Google" logo to boot animation, to the middle of running an app. I had made a backup on TWRP when I got CM12.1 configured the way I wanted it, so I performed a soft reset when it froze on me, and booted into the bootloader. The tab kept freezing in the TWRP window before I could select a restore, so out of desperation I tried just doing a factory reset from within TWRP. Long story short, something must have happened during that reset, because it kept hanging on the boot screen. I thought I may have unknowingly messed something up, so I tried downloading and flashing a stock KitKat (4.4) ROM from Google's site, but kept encountering bootloader errors during the flashing and ended up only being able to boot to the bootloader screen (apparently got a faulty 4.3 bootloader in that ROM, which gave me a headache until I was able to get straightened out). I have been able to get a stock bootloader (4.23) up and running now, along with a stock recovery (going with Lollipop now, so stock for LMY47V) going, but that's it. I've tried flashing the stock lollipop image via shell script (I'm running a Fedora 23 machine), via individual commands, and via "fastboot update -w factory_image.zip" without success. ADB sideload still works via recovery, but I wasn't able to sideload the OTA packages for 5.1 either. The common errors that pop up seem to indicate an error (corruption? fragmentation?) on the cache partition, but I'm not a dev when it comes to Android, so I'm at a loss here... I keep getting "E: failed to mount /cache (Invalid argument)", and other errors associated with accessing/opening files further down the /cache tree. Would this error be more likely to be a hardware issue, or would it be a software/firmware issue? I've had similar errors before with USB drives, when they would start to bad and partitions begin failing, but have always been able to rebuild them and get my data back. If something like this is happening on my N7 and the cache partition has indeed become somehow corrupted and failed (but not physically....), is it possible at all to rebuild partitions on Android in a similar manner? I've scoured the web, but haven't been able to find anything that can help me out with something like that, so I figured my best bet before condemning the N7 to the junk drawer was to see if any of the pros around here had any words of wisdom that *might* get me back up and running. Thoughts and advice much appreciated!!
Thanks!
(Oh, I apologize for the lengthy post, but I wanted to be sure to provide enough background info..... Sorry for the lengthy read!!)
Honestly that sounds more like a hardware problem than a software problem.
During the early stages of booting, everything that happens is extremely deterministic - meaning that it should be completely repeatable in terms of the order & timing in which activities occur.
So, for it to behave erratically during early boot suggests that it is not software, but marginal hardware. If hardware is barely meeting logic levels or timing requirements, a small amount of random noise (which is always present) can cause a fault to occur at any time - and that sounds approximately like what you are observing.
Further, you replaced your ROM entirely and the problem persists - again suggesting that the problem is hardware, not software.
The most cost effective way of dealing with repair of a $200 tablet is - unfortunately - disposing of it and buying a replacement.
Sorry.
Thanks for the reply!! Shoot, that's what I was leaning towards too. What is the life expectancy of these tablets? I mean, I got 3 good years of use out of it, so I'm not going to complain, but it seems like they should have lasted longer... Would it be worthwhile to maybe grab a cracked screen N7 off eBay for parts and try to get my tab working with those parts maybe? I'm hoping the rumors are true about Google coming out with a new tab this fall, but I'd love to get mine working before then lol...
I have Verizon Note 3, with Jasmine Rom and TWRP recovery.
I have posted a question about my phone started showing some sh** dialog over and over about facebook app not responding.
Till now i havent found any solution to it. So, seems as last resort, i will flash again with jasmine rom (if there is anyother better do tell me). But before that, i want everything (EVERYTHING) to be backed up, text messages, my games data, my installed softwares, cracked versions, everything. Is this possible???
Anyone coming to save the day????????
First you need to state whether you have a safestrap ROM or a unlocked bootloader and real custom recovery. Huge difference.
You should also bear in mind that if you are suffering from a corruption issue somewhere, a "complete" backup and restore merely records the corrupted data and restores the same corrupted data. What exactly would you gain that way?
Your hypothesis suggests you think a fix could be acheived by "refreshing" just the ROM (i.e. the /system mount). If you have any customizations in there, they will be lost unless you can identify them and re-create them after you have "refreshed" the /system mount. If you are unable to do that, you will lose them.
If you thought that you were unable to identify those changes and were going to plunge ahead and try anyway, theoretically you would get the same result by just flashing /system only and wipe the /cache mount without doing any backups at all. EXTREMELY RISKY MOVE THOUGH IF SOMETHING GOES SIDEWAYS. (You should always assume that something will go wrong and make backups... and get those backups off the phone in case the entire device needs to be wiped in a "start from scratch scenario)
Note that your apps have been under constant update all this time since Jasmine's release while it (Jasmine) has been standing still. There's no guarantee that what you are observing are not merely bugs in Jasmine uncovered by new application code.
A Herculean, careful and diligent backup & restore operation might fix nothing.