Hey all,
I'm a little in a pickle, but first some background I have a nice phone, a Samsung Galaxy Note 2, running Android 12 (not actually relevant, but like mentioning it regardless ). A while ago, I had to replace the motherboard, because the modem wasn't working anymore. I had a spare motherboard that I bought off of Ebay some time ago (to do some experimentation/hacking with) and used that as the modem was actually still working.
Last week, my phone just started to bootloop all of a sudden, sometimes stuck on the logo, but often just the Lineage logo looping forever. Looking at adb shell just showed zygote crashing and restarting, not important, but after some experimentation from within twrp and memtester, it might seem that the RAM was bad, or so I thought.
A factory reset (e.g. wiping USERDATA), made the phone boot somewhat, but it was almost impossible to get through the setup wizard, very slow, lots of crashes.
Anyway, I dd-ed the USERDATA partition into a file (can mount it just fine on my desktop), fsck says its fine), and put it on my old motherboard (which after lots of cleaning of the whole phone, like an engine overhaul the modem works again!), the same linegae failing to boot/zygote crashing came back. Strange, wiping the userimage partition and setting up the phone makes everything work fine.
Right, so now, I want to move over some apps from the old partition to the new. I can't boot the old phone, not in safe mode, just twrp (though it's dissasembled, so is not really easy atm) and access the old partitions. Particularly, I want to move over Signal, as it contains my chat history and media. I can copy some folders around, but I'm sure the user permissions will be off. So my thinking right now is, install signal, note uid/gid, copy over files from old phone with proper permissions and be done. First thing I noticed though; is that Android 12 stores app and (secure?) app data with some ~prefix~, do I need to worry about that? Are the other gotcha's.
In the end I figure, if all the data is exactly there as on the old phone, it should 'just work (tm)' (in theory) but with signal particularly, there's some crypto magic of course (I don't mind factory resetting stuff and copying more stuff, but I have a dark feeling, that the bad ram caused some bits to be rotten in some 'slightly more important' files making my dump less prestine as I would have hoped.).
Thank you,
Related
As I suspected early on the issues boil down to corruption within the User Data or Cache partitions, less often on the system partition due to an unexpected shutdown of the device. Shut on these devices need to follow the proper shutdown routine as any linux environment. Following this best practice will ensure that all data is written out to its corresponding file system by flushing all cache, unmounting the file system, etc..
Here are the culprits of why we see so frequent random Force Closes, Market Resetting, etc. ultimately resulting in an unclean shutdown, corrupting some data.
1. The button we use is also a forced off button. Typically if you hold it down too long you are powering off the device.
2. Some times when in sleep mode you see the Viewsonic logo upon starting - that means that the system shutdown (most likely crashed).
3. If your running Vegan your hitting the reboot.. I dont know for sure but I suspect this is NOT performing a clean shutdown... (I dont have a copy of the source)
Anyway... wanted to pass this on... as last night my data partition became corrupt after using the Reboot function on the Poweroff menu of Vega 5.1..
shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing
My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.
roebeet said:
My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.
Click to expand...
Click to collapse
I have been on stock since I got the device just moving to the newer versions when they come as OTAs and have never ever had to mess with my partition, so I don't THINK the issue is in the stock software. In fact, the only problems I've ever encountered were when I used the enhancement pack, in which case my screen started to become unresponsive and the calibration.ini I was told to try did not work. Since then I went back to 3389 and the device has been perfect ever since.
I could be wrong though and just very, very lucky....here's to hoping. Another thing to consider is maybe the memory is going bonkers for some reason. I've had flash memory that lasted forever and I've had flash memory that has gone wacky over a period of 6 months....even a wipe by the utility designed to do it doesn't fix it properly. I don't know how CWM wipes or partitions the memory, I do know there's supposed to be a special way to do it.
If it's not faulty memory off the bat, then that leaves something in the 'extras' being put into these ROMs. Maybe some of the newer tegra drivers or some coding to make the ROMs faster - I'm just saying, can't leave any stone unturned.
Has anyone that has stayed loyal to stock encountered these issues? We have to ask that question I think. Then we ask how many of the people playing with ROMs are seeing the issues, this would include people that have used CWM to partition and mess with their mounts initially.
I can say I've never seen data disappear from my internal memory or my SD and I can also say I've never seen multiple FCs except after putting in the enh. pack (keep in mind I got my tab on Dec 20something, so I had 3053 and then 3389 soon after).
The first sign of anything being 'corrupted' on it's own at stock and I'll be sending mine back. As an owner of Android since Android's been around, I've never had my G1 or MT4G (or any smartphone before it) become corrupted due to not being shutdown or reboot properly and while this is a tablet I think the fundamentals should be the same. Pampering 'faulty' memory is a risk. You can wipe and re-do all you want, but if it's faulty it's going to stay that way.
Ive done that but I guess you can say unfortunately I have had only clean shutdowns since then... The last corruption I had I formatted my data and cache partitions before I ran logcat.... Of course thought of that afterward....
Generally if any has FCs, etc. etc. run a logcat and post it here... we will be able to confirm this...
We could change the way the partitions are created and add a sync which will further reduce chances BUT will take a performance hit...
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I reviewed the out of the box framework source on the google GIT and technically if a reboot command is given a clean shutdown is performed via the framework... but the widget on the shutdown screen I suspect is not calling the method properly or is not being called at all... All speculation at this point... But for sure there is corruption occurring..
Since the last corruption I switch over to pershoots kernel... Even though his kernel seems to be a little slower he seems to have included the latest drivers which other items relate to data integrity (im reading into the release notes).
NEO: The first thing I did when I got my device install CW, Vegan... Updated Kernels also... Never had an issue until the first time (yes about a day ago) I used the reboot feature of Vegan. That corrupted my user data. I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
But again.. between the wrongly placed power switch, the unprovoked reboots (ie viewsonic screen showing when trying to wake up the device) and the reboot button possibly not performing a proper shutdown will sure increase the chances in a wider distribution of users. So it may not be a CW issue and just some poor design.
When I have time today I will verify if the reboot function performs a clean shutdown... if anyone has the time please post the logcat... Im going to be running around today and will try to get to it..
watson540 said:
shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing
Click to expand...
Click to collapse
stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
Click to expand...
Click to collapse
AFAIK they're running yaffs ATM. Next move is to ext4...
Read some articles about this several weeks ago, apparently many apps do not properly flush file caches. One of the articles was a Google developer post about file corruption along with their API method which did a cache flush prior to a close, then a bit later was the Google indication that they were planning to move to ext4 FS to further help alleviate the problem.
stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
Click to expand...
Click to collapse
That's my point. How many times since we've had our Android and smart phones have we had situations where they are turned off or rebooted without the proper procedures? Power drains till they die, they drop and reboot, we clog them up with stuff or some app drives them nuts and they reboot or shut off....Yet you rarely if ever hear about a phone's data being 'corrupted' with stock software. Sure it may happen with official OTAs etc, but never just off-the-bat like what's happening with the G-Tab. But it's not happening to everyone either so I'm just looking to see if there's a pattern.
Even since the G1 and newer phones, you don't really hear about or see file corruption issues on stock software with these phones. It's when users start going to ROMs that you hear of issues cropping up. That's not to say it doesn't happen at all at stock, I just think we're seeing it in a more concentrated fashion here because of all the formatting, re-partitioning, etc. At first you hear, 4GB is a great partition size, then you hear there are problems so move to 2048, then you hear 256MB swap, then no swap since Android doesn't use it. Then dataloop for speed, then no dataloop because of critical issues. Rules and instructions change almost on a daily basis. I think it's more than these poor flash drives can take I find sometimes it's good to keep it simple.
I owned a Vibrant for a while...decided it was a PoS when at stock I was seeing bad lag (because of Sam's terrible FS). People said...do the speedhack, it'll be fast!, but what was the caveat? Having to reboot the phone almost weekly, sometimes several times a week, and people were seeing what? Data corruption. That's not for me. Give me something that is lag free (doesn't have to be a bullet train, just don't skip on video or audio and make sure my live wallpaper and drawer animation is fluid and I'm happy!). Point being....keeping it simple may help to alleviate some of the issues. If people are seeing these problems with stock, then you're absolutely right and it would be a point of contention that the failsafe isn't working right.
Otherwise it seems the stock OS on these things are able to self correct in most situations and it may just be some of the many tweaked features in these ROMs doing something it shouldn't - or, I may just be very lucky indeed.
I'm still dying to get the OTA - I haven't seen one since 3899 yet.
I rooted my Samsung galaxy core prime g-360v using king root and didn't make any backup using titanium or anything since I didn't have enough phone space. Now I was trying to clear up system memory that took 4.5gb of storage for whatever reason. So I messed around a bit and managed to accidentally factory reset my phone.
Now I am apperently stuck in a loop where setup wizard stopped responding after 2slides. It stopped working right after i rooted it. But I dismissed it as no big deal since I wasn't going to factory reset my phone... Until I managed to do so accidentally. Rip all my pr0n but anyways how do fix this. (Note I can get into Odin mode and every that doesn't require me to actually setting up my phone.)
Is there a way I could possibly kill 2 birds with 1 stone since before rooting I didn't want to factory reset cause I didn't want to lose anything. But now the situation I am in, is there a way I can get passed this loop and or possibly reduce the size of the system memory.
Qpò0
Inviato dal mio SM-G935F utilizzando Tapatalk
Just to make certain, you were deleting system apps (Verizon/Samsung bloatware presumably)? Three things:
1. Don't do that.
2. Your phone's system partition is a set size, and deleting stuff won't free up any space that you can use for other things.
3. Once you delete something from the system partition, it's gone. Doing a factory reset won't put it back, because all doing a factory reset does is delete the data, storage, and cache partitions, leaving the system partition (which is what boots when you do a factory partition) untouched. When something's gone, it's gone.
I think your only option is to take it in and pretend like it's defective. Assuming King Root doesn't trip KNOX.
Next time, do your reading and research, and ASK FIRST! Trust me, we'd rather you pester us with what might seem like silly questions than have you screw up your device. If it sounds like I'm scolding you, I assure you I'm not. Because I did basically the same thing with my first rooted phone. Got too clever (not as clever as I thought I was), and tried reinstalling the Play Store because I was getting install errors. Play Store would crash immediately. So I did a factory reset, and BAM, no Play Store. I eventually realized how to fix it (and by eventually, I mean on the way home after getting a replacement ordered at the store). We all do dumb things.
How are you finding the Core Prime, apart from this mishap? I'm kinda sorta contemplating getting one from T-Mobile (but not yet) since we're supposedly getting Band 12 here some time this year, and my current internet "mule" (USB and wifi tethering) doesn't have Band 12.
Planterz said:
Just to make certain, you were deleting system apps (Verizon/Samsung bloatware presumably)? Three things:
1. Don't do that.
2. Your phone's system partition is a set size, and deleting stuff won't free up any space that you can use for other things.
3. Once you delete something from the system partition, it's gone. Doing a factory reset won't put it back, because all doing a factory reset does is delete the data, storage, and cache partitions, leaving the system partition (which is what boots when you do a factory partition) untouched. When something's gone, it's gone.
I think your only option is to take it in and pretend like it's defective. Assuming King Root doesn't trip KNOX.
Next time, do your reading and research, and ASK FIRST! Trust me, we'd rather you pester us with what might seem like silly questions than have you screw up your device. If it sounds like I'm scolding you, I assure you I'm not. Because I did basically the same thing with my first rooted phone. Got too clever (not as clever as I thought I was), and tried reinstalling the Play Store because I was getting install errors. Play Store would crash immediately. So I did a factory reset, and BAM, no Play Store. I eventually realized how to fix it (and by eventually, I mean on the way home after getting a replacement ordered at the store). We all do dumb things.
How are you finding the Core Prime, apart from this mishap? I'm kinda sorta contemplating getting one from T-Mobile (but not yet) since we're supposedly getting Band 12 here some time this year, and my current internet "mule" (USB and wifi tethering) doesn't have Band 12.
Click to expand...
Click to collapse
Ok so like what should I do? I think if I can either get setup wizard fixed or like should I use a different ROM. If so would it take more system memory? Also how would I allocate the memory rather than Delete it all.
Also I fairly like my galexy core not a bad price for it and it basically does everything I need it to just the only problem is the low memory.
uhhh how do i flash a rom like Cyanogen
(Edit:attempted to try to flash a ROM almost f'ed my computer...)
Im new to all this so pay no attention if its nonsence...
My S5 G900f has a qualcomm snapdragon chipset, that doesn't support monitor mode, which i believe means that it doesnt support packet injections or packet capturing (driver related?)
using the dsploit.apk for things like session hijacking, replacing web page images of a target and using script 'injection' to inject custom java script into a target web page, all sounds like things you'd need monitor mode to do. and if it is then i was able to do it with my S5.
I dont know a lot about coding or how it all fits together and communicates with the hardware, so i may sound completely stupid, but this has done my head in for ages, so why not get it out there.
1. when i attempted to upgrade from my first custom rom, i had a bit of trouble, softbricked my phone and then flashed the two roms in various, alternate, wipe, format and install combinations until it finally booted to set up, and i stopped panicking. but this caused features from the first rom to appear within the second rom.
ie: 3minute battery mod was installed through a add-on zip along with the first rom and nothing to do with the second at all.
2. inconsistencies within the file system, like file names that were apps included with the first rom.
3. dsploit.apk was bugged and crashed every 5 or 10 minutes. then would seem to glitch or stutter for a couple seconds before correcting its self and accomplishing its pen test.
4. i also remember watching green text in the terminal as it failed to connect or ID some part of the system but continued to retry in quick succession until it glitched and worked. (i think this was a similar type of app i was trying out at the same time but instead of GUI stutters, i could see the text rapidly stuttering and glitching.)
4. the dsploit.apk worked for me back then, even though it was temperamental. ive downloaded the apk a couple times since with various roms and ive got no where with it...
was thinking maybe different aspects of the two roms had been filed or grouped together and created unstable triggers within the software, allowing it to briefly communicate with the chipset. i may be way off, but ive been sat here waiting for someone to solve this issue forever, i thought id share my thoughts, on the off chance it turns out to be something and i can finally get my S5 into monitor mode without OTG cables and other unwanted auxiliary components.
thanks in advance
G Carter
Do a clean install of you ROM, and please, don't panick. If you want to have a good time flashing ROMs and stuff, panicking is the last thing you want to do, it will cause stress and stress can lead to not being careful enough so stuff like this happens, well, always, if you are experiencing issues do a clean install. Just boot into recovery (I recommend TWRP) and wipe everything except external sd. Open ADB and sideload the ROM (or, if you have enough memory on a flash drive, plug it into your android and flash it from there) and then Google Apps.
Hey all,
I admit, I'm new to this whole android os thing, and this is only the second smart phone I've ever had. so far I gotta say, I'm not impressed with these things.
I've been banging my head against various bricks in this wall for the past three nights, and could really use some help before I decide to incinerate this Xperia.
Im trying to load and run Aosp 10 for this thing, but the few times I've had it stable, I've found It was really rather barren and honestly useless beyond strictly phone calls and texting.
over the course of these past three days, I've encountered; mounting errors (failed to mount oem/system/vendor,) issues with twrp becoming inaccessible (requiring a re-flash) after any successful operation of the Aosp 10 rom, at which point I may or may not be able to get the rom to boot again. Perhaps my assumption that they can coexist (basically a dual boot) is incorrect.
I've tried both the most recent & relevant standard twrp, and the Kagura version of twrp, to no avail. I'm still currently fighting "failed to mount /OEM". this has only ever resolved randomly (seemingly) in the past, only to crop back up again. I've formatted everything (short of the sd-card) 6 ways from sunday (getting the "failed to mount /OEM" the whole while during this operation).
I've tried older versions of roms, twrp, etc..
I'm burnt out on this trouble, and perhaps my choice of rom or phone was a mistake. All I'm after here is a rom (or phone, or hell, maybe a PDA) that works reliably, doesn't glitch a ton, have its screen adhesive fail, or suffer encryption so deep and aggravating its useless for simple and plain operations (looking at you APPLE). A "set it and forget it for a while, works when I need it and doesn't glitch out when needed,
well thought out and designed device.
Point me in the right direction here guys. My programming days are years behind me and the rest of the world, and I've not got the time or patience to learn & write a new rom/os from scratch.
sincerely-Psykora
I couldn't find this online, or it seems the method no longer applies, and I couldn't get it to appear in a search here.
The last time I upgraded was from an S9 to the Note 20 Ultra. When I did, it asked me if I wanted to copy from the old phone, and everything was moved over, including all of the apps. The only things missing were the older texts from my side and some of the data inside some apps.
This time is used Smart Switch, and it only transferred data and a few of the apps. It was better before!
Is there a way to get everything or almost everything moved over?
I just want to get switched over quickly.
Thanks!
A clean load is best for stock phones. Do it right the first time...
SmartSwitch can screw up bad. A different device and OS version can cause issues. Potential data loss is also a possibility.
Never use SmartSwitch as the only backup... keep at least 2 copies on hdds that are physically and electronically isolated from each other and the PC.
Copy/paste critical data, then verify size, file count and if readable. If you have an SD card it should already be there on the old phone.
Otherwise develop a plan/organize your data so you can reload as quickly, accurately and painlessly as possible with zero critical data loss.
After 2 back to back boot loops in 3 days I learned that lesson
Clean Load? Do you mean don't use SmartSwitch, and just set up the new phone manually?
Maybe this device is too different for SW to work? Are there any alternatives?
Myk_Myk said:
Clean Load? Do you mean don't use SmartSwitch, and just set up the new phone manually?
Maybe this device is too different for SW to work? Are there any alternatives?
Click to expand...
Click to collapse
Yeap. Always the best option. A good load can last for years if you don't do firmware upgrades/updates. This stock Note 10+'s load will be 3 yo this June, still fast, very stable with minimal maintenance. Still running on Android 9. Android loads can be very long lived, a great OS.
A clean load means when you do find issues (and you will) you won't be wondering if you imported the problem with SmartSwitch. The last thing you want to do is a factory reset because the issue is likely to reoccur*. Instead find the root cause. Knowing you have a good base load helps with troubleshooting.
If SmartSwitch screws it up a factory reset maybe the only realistic solution. It may be lagging, system instability or subtle issues. My second N10+ may need this done because I inadvertently used more SmartSwitch options than I had wanted. So are the issues from SmartSwitch or because of Android 10? Only one way to know for sure... You get the idea.
*a boot loop or malware that can't be eradicated are the exceptions. With a boot loop you still need to track down the root cause, usually a buggy 3rd party app.