Related
Hello, I am in a bit of a jam and am trying to find the best way out.
My device is encrypted using the native Android feature. I have Lean Kernel and CleanROM on the device. So it is rooted/unlocked. I was trying to clean the device further by uninstalling some useless apps with Titanium Backup. Turns out I messed up on something..
When the phone boots to the encrypted device screen, the keyboard doesn't show up! I am not able to get into the phone to do anything!
I have the latest CWM recovery installed. I tried a factory reset and such, but it says it fails to mount the internal SD card. /:
Anyone know how I can fix this and flash a new CleanROM? Data wiping is not a problem for me, but CWM refuses to mount the SD card to do it..
Any advice? I am relatively new to the Android scene, so try not to make things too complicated.
Odin?
EatonZ said:
Hello, I am in a bit of a jam and am trying to find the best way out.
My device is encrypted using the native Android feature. I have Lean Kernel and CleanROM on the device. So it is rooted/unlocked. I was trying to clean the device further by uninstalling some useless apps with Titanium Backup. Turns out I messed up on something..
When the phone boots to the encrypted device screen, the keyboard doesn't show up! I am not able to get into the phone to do anything!
I have the latest CWM recovery installed. I tried a factory reset and such, but it says it fails to mount the internal SD card. /:
Anyone know how I can fix this and flash a new CleanROM? Data wiping is not a problem for me, but CWM refuses to mount the SD card to do it..
Any advice? I am relatively new to the Android scene, so try not to make things too complicated.
Click to expand...
Click to collapse
This probably wouldn't work, but have you tried reflashing with Odin?
budzylikessoup said:
This probably wouldn't work, but have you tried reflashing with Odin?
Click to expand...
Click to collapse
I am looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
I am downloading the very first package. Since that seems to wipe everything, which is what I want at this point.
Will flashing that work?
I'm not sure if it will work, as I don't encrypt my device. What it will do is wipe your system, data, etc. partitions, but it won't touch your internal SD. This will probably be fine; it will install a keyboard and you should be able to enter your password, that is, if it can flash the ROM properly.
flanks vidsguir
budzylikessoup said:
I'm not sure if it will work, as I don't encrypt my device. What it will do is wipe your system, data, etc. partitions, but it won't touch your internal SD. This will probably be fine; it will install a keyboard and you should be able to enter your password, that is, if it can flash the ROM properly.
Click to expand...
Click to collapse
I'm still trying to understand how Android storage works, so I may sound like a noob here haha..
All I have is an internal SD card. I don't have an external one or anything. Are system, data located on another internal flash chip or something? If they are on the internal SD, I would imagine everything would be formatted and reset once this is flashed.
Sorry, I read the linked post wrong...So this will wipe everything, system, data, and internal SD.
As for the difference, the system and data are different partitions than the internal SD.. so normally when you factory reset in CWM, it just wipes the data, not your internal SD or system. What this means is that it won't touch some files, like ones you download from the internet, but it will get rid of all of your apps and appdata, as you know, and these are stored in the data partition.
I got it sorted. Thanks for the help.
Glad I could help!
EatonZ said:
I am looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
I am downloading the very first package. Since that seems to wipe everything, which is what I want at this point.
Will flashing that work?
Click to expand...
Click to collapse
Just wanna say this thread was a lifesaver, and I'll just leave my experience here for fellow noobs, like myself, stumbling into this issue.
I CMod'd my S3 with Clockwork (following very detailed instructions) and tried out encryption (knowing ahead of time that a factory reset would be in order if I didn't like it). As you all know Clockwork has trouble mounting the encrypted /sdcard/ directory, and won't do the factory reset. I was afraid that since Clockwork couldn't deal with the encrypted data, so too might Odin, leading to the risk of bricking. This thread gave me enough courage to give it a go. Following the above linked instructions solved the problem. Odin had no problem wiping and writing over the encrypted data. after I was back to stock I ran through installing Clockwork and CMod again. And just like that, the problem's fixed.
Thanks a bunch everyone!
EDIT:
I just got a response on twitter from a friend who ran into the same issue with clockwork. According to him, apparently TWRP doesn't have this flaw. My phone's working now and I don't want to monkey around with it anymore, but maybe a more experienced user out there could comment on/confirm this, and maybe add the info to the tutorials (if it's correct).
Thanks again!
SpoonlessCorey said:
Just wanna say this post was a lifesaver, and I'll just leave my experience here for fellow noobs, like myself, stumbling into this issue.
I CMod'd my S3 with Clockwork (following very detailed instructions) and tried out encryption (knowing ahead of time that a factory reset would be in order if I didn't like it). As you all know Clockwork has trouble mounting the encrypted /sdcard/ directory, and won't do the factory reset. I was afraid that since Clockwork couldn't deal with the encrypted data, so too might Odin, leading to the risk of bricking. This thread gave me enough courage to give it a go. Following the above linked instructions solved the problem. Odin had no problem wiping and writing over the encrypted data. after I was back to stock I ran through installing Clockwork and CMod again. And just like that, the problem's fixed.
Thanks a bunch everyone!
Click to expand...
Click to collapse
Yeah, I was worried I might have created a $200 paper-weight!
I'm glad that my question ended up helping you as well!:good:
Hello,
This is going to be kinda long, I want to give all details I can remember in case it helps.
I decided this morning that I was going to try out the unofficial CM11 rom for Galaxy Nexus GSM. So, first thing I do is a backup from Clockwork Recovery (latest touch recovery flashed).
After that, I flash the rom, and the gapps. I reboot to see if it works, and after 5 minutes of use everything looks pretty sucessful.
So, adb pull my backup and offload it to my computer in the case that something goes really wrong, because I'd like to get a clean start. So, I wipe the device as completely as I can in Clockworkmod Recovery. I then adb push the cm11 rom and the gapps roms referenced above. I use Clockworkmod Recovery to flash those onto the device, reboot and start playing around then realize that I have no cell service. Try manually registering on my T-mobile to no avail.
I think this is a baseband problem, so I fastboot flash radio (stock nexus radio rom from 4.3), reboot into the system and still no service.
Then I begin thinking my phone radio has completely failed, so I take a simcard from my girlfriend's phone pop it into mine, reboot and still no service. Reinstall my original sim card.
Then I am REALLY thinking my radio has failed, so I figure I'll just flash the full 4.3 stock suite in case I'm missing something small because I don't understand how something works. Still no service.
So, as a last resort, I push the Clockworkmod Recovery backup back into the /sdcard/0 directory, restore in Clockworkmod Recovery, reboot and it works(!).
Now I start wondering what I'm failing to understand about this problem, so I go ahead and do a factory reset in Clockworkmod Recovery and back to no service(!).
I really thought I understood how it worked, but I must be missing something here, or maybe Clockworkmod Recovery is wiping something it shouldn't be? The final thing I can add is each time I fail to get service in the installation, the service bars light up for 1/2 second to 2 seconds during boot. Maybe someone could help me spitball what's happening here?
Thank you very much in advance.
I think all yu must do is download the latest stock firmware ment for for your device.. from internet.. and install that properly on yur device.. this will do every thing right.. see I too am not at all good with using programme stuff and so.. therefore I keep the copy of firmware with me always.. that helps when I almost destroy my phone
tc and good luck..
---------- Post added at 04:01 AM ---------- Previous post was at 03:56 AM ----------
and it might be possible thet the rom which yu are trying is not ment for your device version.. chack that too correctly..
Problem found (not yet solved, but that's another question)
OK, I found the problem. My non volatile memory got corrupted. I pulled an image from the EFS nv memory partition devfs file, mounted it as loop on my localhost and got nothing but a lost+found directory. It's not a terrible thing, but from now on when I wipe this phone, I will need to adb push my /data/radio backup to the EFS nv memory partition. That is, at least until I find out exactly what I need to do to reconstruct the memory partition. Shouldn't be that hard, but I really need a good description of what is in all the EFS memory partition files for the Galaxy Nexus. :good: I'll dig around the forums a bit, maybe ask someone for the directory structure, maybe I'll be able to, at least, partially restructure that memory partition with a good old dd'ing. Maybe I'll root my girlfriend's Galaxy Nexus so I can get the structure proper.
Hope this helps someone else!
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
CafeKampuchia said:
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
Click to expand...
Click to collapse
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
dreamerguy00 said:
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
Click to expand...
Click to collapse
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
blackbird5308 said:
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
Click to expand...
Click to collapse
Sorry wrong thread
Sent from E.P.D.Center
I had the same weird problem last night.....
Except my recovery was also reverted to stock.
it happened after i got notifed about an update available couple days in a row which i canceled.
I even have Droidwall and everything but a few apps are blocked from data usage.
What i would suggest is to freeze the ""system update" system app.
I kinda have a feeling the OTA updates have something to do with it.
This happend to me 1 other time a while back with an HTC One X device. Same pattern, System update notifications then couple days of ignoring .... then pooffff...
blackbird5308 said:
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Click to expand...
Click to collapse
Hi all,
As you all know Android rolled out the new 9 pie Update on all xiaomi devices.
After updating my mi a2 lite became the crappiest phone on earth as all the bugs started appearing(phone was rebooting multiple times, image was broken, sd xcard not recognised and battery life draining fast as hell).
Because of that I decided to root my phone and install Havoc 2.0. Fair enough, I used the rom for a bit but honestly I am not really happy about it too as doesn't seem really stable at all (many functions are there but not working, the camera app is crap, the volume bar appears every time I touch the fingerprint sensor and the fingerprint lock isn't working as well). At this point I wanted to revert and get back to the stock oreo 8.1 so I booted the recovery twrp to restore the firmware backup that I did at the beginning before installing havoc but this disappeared!!!!!
Reading again the procedure i followed I noticed that one of the steps was to wipe the caches and, as the procedure was saying, the system as well(I know.... I am an idiot for relying on what the procedure said)!
Obviously this deleted my previous backup completely leaving me empty hands without any stock firmware/rom.
Is there any chance to revert back to the stock (maybe downloading all the pieces and then force flashing them?) or I am screwed?
I know, I should have followed one of your tutorial (and I am sorry for asking now for your assistance) but now I think you are the only one that can actually help me.
Best regards,
D.
manna.davide87 said:
Hi all,
As you all know Android rolled out the new 9 pie Update on all xiaomi devices.
After updating my mi a2 lite became the crappiest phone on earth as all the bugs started appearing(phone was rebooting multiple times, image was broken, sd xcard not recognised and battery life draining fast as hell).
Because of that I decided to root my phone and install Havoc 2.0. Fair enough, I used the rom for a bit but honestly I am not really happy about it too as doesn't seem really stable at all (many functions are there but not working, the camera app is crap, the volume bar appears every time I touch the fingerprint sensor and the fingerprint lock isn't working as well). At this point I wanted to revert and get back to the stock oreo 8.1 so I booted the recovery twrp to restore the firmware backup that I did at the beginning before installing havoc but this disappeared!!!!!
Reading again the procedure i followed I noticed that one of the steps was to wipe the caches and, as the procedure was saying, the system as well(I know.... I am an idiot for relying on what the procedure said)!
Obviously this deleted my previous backup completely leaving me empty hands without any stock firmware/rom.
Is there any chance to revert back to the stock (maybe downloading all the pieces and then force flashing them?) or I am screwed?
I know, I should have followed one of your tutorial (and I am sorry for asking now for your assistance) but now I think you are the only one that can actually help me.
Best regards,
D.
Click to expand...
Click to collapse
Wiping system is not what wiped your backup, your backup was stored on internal storage or on external sdcard, it does not get stored in system. The only you could have wiped the backup is if you also chose the option to wipe the internal storage when you wiped cache and system.
Factory reset and the normal wipes in TWRP do not wipe /data/media, /data/media is where your user data is stored. Only specifically choosing the option to wipe internal storage can wipe /data/media.
And you aren't an idiot for following instructions, you're an idiot for following instructions incorrectly. If you had wiped cache and system but left internal storage alone, you wouldn't be in the mess you're in.
Have you tried doing a Google search for:
"Return to stock (your model number)"
If it's available, that should find the instructions, tools and files you need.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Wiping system is not what wiped your backup, your backup was stored on internal storage or on external sdcard, it does not get stored in system. The only you could have wiped the backup is if you also chose the option to wipe the internal storage when you wiped cache and system.
Factory reset and the normal wipes in TWRP do not wipe /data/media, /data/media is where your user data is stored. Only specifically choosing the option to wipe internal storage can wipe /data/media.
And you aren't an idiot for following instructions, you're an idiot for following instructions incorrectly. If you had wiped cache and system but left internal storage alone, you wouldn't be in the mess you're in.
Have you tried doing a Google search for:
"Return to stock (your model number)"
If it's available, that should find the instructions, tools and files you need.
Click to expand...
Click to collapse
Hi, first of all thanks for replying.
Interbal storage hasn't been wiped out, i am sure about it as the proceedure was saying not to do it. (I've selected just the first 3 options and internalbstorage is the 4th so I am def8nitely sure about it). Might be somewhere else then?
I did a second back up now and I see it so at this point I am not really sure where this could be!
Is 12 hours that I am searching proceedures but everything is very confusing.
manna.davide87 said:
Hi, first of all thanks for replying.
Interbal storage hasn't been wiped out, i am sure about it as the proceedure was saying not to do it. (I've selected just the first 3 options and internalbstorage is the 4th so I am def8nitely sure about it). Might be somewhere else then?
I did a second back up now and I see it so at this point I am not really sure where this could be!
Is 12 hours that I am searching proceedures but everything is very confusing.
Click to expand...
Click to collapse
Mate @Droidriven you're a monster!
I found it in data/media in the internal storage! thanks a lot mate!
I'll run it and see if all comes back as usual.
Infinite thanks!
Good to go.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Good to go.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Do you mind me asking you one last thing?
At this point, having the original backup, I can try another custom Rom before reverting everything to Oreo.
My question are 2:
-Because you seem very driven, do you know any stable custom rom that I can run on this Xiaomi MI A2 lite?
-Do you know if I can Install the old Havoc on and purge this pie version?
Thanks again,
Davide
manna.davide87 said:
Do you mind me asking you one last thing?
At this point, having the original backup, I can try another custom Rom before reverting everything to Oreo.
My question are 2:
-Because you seem very driven, do you know any stable custom rom that I can run on this Xiaomi MI A2 lite?
-Do you know if I can Install the old Havoc on and purge this pie version?
Thanks again,
Davide
Click to expand...
Click to collapse
I don't know anything about any of the ROMs for your device, I don't have your device.
Sent from my LGL84VL using Tapatalk
Hi,
All sensors are disabled on my A525F (undetected on test apps, screen rotation not working, etc).
I upgraded my phone, then I flashed TWRP 3.6/multidisabler/disable-dm-verity and rooted from TWRP with Magisk 24.3, but I don't know if sensors were disabled before or after TWRP/Magisk.
I have backups from TWRP before flashing Magisk.
Do you know what I can do to recover my sensors?
I've seen similar issues on forums for Pixel phones and Android 10, it had to do with a corrupt "persist" partition where calibration files are stored, and new versions of android disable sensors if this partition is corrupt (was not the case on older android versions).
But I've seen nothing on forums with Android 12 / Samsung A52.
TWRP was storing log data on the persist partition which seemed to caused the issue. But it was patched by the time...
Thanks in advance for any feedback/help.
Problem is solved by restoring "persist" and "persist image" partitions from TWRP!
So maybe a warning if you want to root your A52 phone: make sure to backup those partitions beforehand!!
rousselmanu said:
Problem is solved by restoring "persist" and "persist image" partitions from TWRP!
So maybe a warning if you want to root your A52 phone: make sure to backup those partitions beforehand!!
Click to expand...
Click to collapse
Please can you share the twrp baçkup? My sensors arent working. I even tried reinstalling but nothing. Please help.
Ryzen5950XT said:
Please can you share the twrp baçkup? My sensors arent working. I even tried reinstalling but nothing. Please help.
Click to expand...
Click to collapse
It contains sensor calibration data that are specific for each phone... I think you may ruin your sensors.
Besides, as far as I understand it also contains security related files, BT/Wifi chips mac adresses, certificates... so I am not sure it is a good idea.