我的Android设备是否启动到“隐身”分区? -- rom-flashing 领域 和 factory-reset 领域 和 boot 领域 和 bootloader 领域 和 partitions 领域 android 相关 的问题

Is my Android device booting into a “stealth” partition?


简体版||繁體版
4
vote

问题

中文

好的,这是一个奇怪的问题我遇到了一个我在几年内没有问题的Android系统遇到过......而且我几乎没有关于如何潜在修复它的想法。

让我们从一开始就描述问题以及我过去12个小时的尝试。

我今天早上醒来,今天早上看到最近安装的应用程序(通过Google Play商店)已经崩溃了,而且显然是其他应用程序和服务的卡车也展示了一个HICKUP。

  1. 我决定简单地卸载它并重新启动我的手机(清除Dalvik缓存,而我避免任何HICKUP)。系统像往常一样启动,但我注意到我刚卸载的应用程序仍然存在。再次尝试,结果。

  2. 知道我有一个5天的TWRP备份,我决定恢复恢复我的旧系统状态。完成,擦拭dalvik缓存并重新启动。没有成功,旧系统(使用不应该有的应用程序)靴子。因此,TWRP备份不是解决方案。

  3. 哭泣一个沉默的眼泪,我决定通过TWRP提醒所有分区,只需从头开始刷新rom。重新启动......以及我的惊喜旧系统出现(包括壁纸,设置和那个奇怪的app等)。)

  4. 不想放弃,我甚至试图安装另一个rom。 TWRP确认这成功。但重新启动再次忽略了DARN旧操作系统的每个系统更改和靴子(包括设置和应用程序 - 由于出厂重置而不存在。)

  5. 所有这一切都对自己说了有点不满 - 好的,我会擦除所有分区并重新启动。没有操作系统,设备根本不应该启动,确认我摆脱了我的设备搞砸了。启动到TWRP,鞭打列出的所有分区(包括外部SD)。我通过使用TWRP文件管理器确认了这项工作,以检查每个可用分区的内容。他们都是空的。我确信这是为了工作,我的设备由于缺少的操作系统而跳起。所以,我重新启动了......和哎呀,设备再次靴子进入系统(使用该应用程序,旧壁纸等)逻辑说,这不能 - 因为所有分区都是空的。

长话短说:我同时尝试了我包里的每个技巧来摆脱旧的操作系统,但无论我做什么 - 我都不能。闪烁,闪烁等似乎没有改变手机愉快地靴子的事实 - 根据TWRP文件管理器 - 不存在。

现在,我没有关于如何解决它的想法。它几乎就好像我正在战斗一些被启动的"隐藏/隐形" 分区。如上所述:这甚至发生在我对所有分区的情况下发生( System + Cache + Data + Internal Storage + <代码> Micro SD card )后跟一个 Format Data ),然后重启。

与此同时,我开始怀疑我通过Google Play商店安装的最后一个应用程序可能是恶意软件。但是,在完整的设备Whipe之后,不应该导致可引导的操作系统。

  • 可以是我的Android设备靴子进入"隐身" 分区?如果,当我无法通过TWRP看到它时,我如何摆脱它?
  • 是否有任何方法来实现硬形式并重新分区内部SDS并重新创建除TWRP功能之外的分区? (如果其中一个分区存在一些问题,TWRP实际上并不是如此。)
  • 或(真正让我的一天)有没有人经历过的东西,并且有一个解决方案,它可以通过摆脱设备似乎检测到的旧操作系统来帮助我解决这个问题 - 知道 - 其中/ em>幸福的靴子?

编辑

因为发表评论要求某些版本详细信息等:

  • 设备是三星GT-P3100,AKA ABCDefghijklmnabcdefghijklmn6
  • Twrp 3.2.1-0
  • ROM(让我们只给它打电话)"不可删除" 是SLIMKAT。更具体的

      Slim-4.4.4.build.9.0-OFFICIAL-8293   

一次又一次地看着事情,似乎TWRP无法正确提醒一个或多个分区(系统,数据),即使在这样做时没有单个错误消息或警告。

我还尝试擦除所有分区以及内部存储和闪存 lineage-13.0-20180211-nightly-espresso3g-signed ,这导致错误7(重新启动相同的DARN"不可删除的" SLIMKAT)。

同样用于尝试擦除所有分区以及内部存储和闪存 abcdefghijklmnabcdefghijk MN9 ,它导致错误7(重新启动相同的DARN"不可用于" SLIMKAT)。

此外,知道我有另一个可用的eSpresso3G设备可能会有所帮助,这没有显示任何类似的问题。 在该其他设备上,我可以按预期闪光,提示,备份,恢复,并成功启动到相关的ROM中。

因此,我怀疑一个或多个分区有问题,这也防止TWRP与其索赔相反。 甚至使用TWRP终端并足够疯狂尝试<代码> ABCDEFGHIJKLMNABCDEFGHIJKLMN10 和 ABCDEFGHIJKLMNABCDEFGHIJKLMN11 似乎在第一次瞥见时工作。 然而,分区内容只需在重新启动时显示,就像任何事情发生一样。 另一个指示灯它可能是一些分区hickup是 - 在引导中的任何设置甚至在引导中开始的任何应用程序的任何更改都会在整个操作系统中折叠,直到设备重新启动到恢复之前。

english

OK, this is a weird problem Ixe2x80x99m encountering with an Android system Ixe2x80x99ve been using without problems for several years nowxe2x80xa6 and Ixe2x80x99m practically out of ideas on how to potentially fix it.

Letxe2x80x99s start at the beginning to describe the problem and what Ixe2x80x99ve been trying for the past 12 hours.

I woke up to my device this morning seeing that a recently installed app (via Google Play store) had crashed, and obviously a truckload of other apps and services also showed a hickup too.

  1. I decided to simply uninstall it and reboot my phone (clearing the Dalvik cache while I was at it to avoid any hickups). The system booted as usual, but I noticed the app I just uninstalled is still there. Tried again, same result.

  2. Knowing I have a 5-day old TWRP backup, I decided to restore that to get back to my old system state. Done, wiped Dalvik cache and rebooted. No success, the old system (with the app that shouldnxe2x80x99t be there) boots up. So, that TWRP backup wasnxe2x80x99t a solution.

  3. Crying a silent tear, I decided to whipe all partitions via TWRP and simply reflash the ROM from scratch. Rebootedxe2x80xa6 and to my surprise the old system showed up (incl. wallpaper, settings, and that one weird app et al.)

  4. Not wanting to give up, I even tried to install another ROM. TWRP confirms this succeeds. But rebooting again ignores every system change and boots that darn old OS (incl. settings and apps xe2x80x93 which shouldnxe2x80x99t exist due to a factory reset.)

  5. Getting a bit upset by all this I said to myself xe2x80x93 OK, Ixe2x80x99ll wipe all partitions and reboot. Having no OS the device should not boot at all, confirming I got rid of whatever messed up my device. Booted into TWRP, whiped ALL partitions listed (including the external SD). I confirmed this worked by using the TWRP file manager to check on the contents of every partition available. They are all empty. I was convinced this was going to work and my device would hickup due to a missing OS. So, I rebootedxe2x80xa6 and whoops, the device again boots into the system (with that app, the old wallpaper, etc.) Logic says this canxe2x80x99t be xe2x80x93 since all partitions are empty.

Long story short: I meanwhile tried about every trick in my bag to get rid of the old OS, but no matter what I do xe2x80x93 I canxe2x80x99t. Whiping, flashing, etc. doesnxe2x80x99t seem to change the fact the phone happily boots into an OS that xe2x80x93 according to the TWRP file manager xe2x80x93 doesnxe2x80x99t exist.

Now, Ixe2x80x99m out of ideas on how to fix it. Itxe2x80x99s almost as if Ixe2x80x99m fighting some "hidden/stealth" partition which gets booted into. As said: this even happens when I whipe all partitions (System + Cache + Data + Internal Storage + Micro SD card) followed by a Format Data) and then reboot.

Meanwhile, Ixe2x80x99m starting to suspect the last app I installed via the Google Play store might have been malware. But that shouldnxe2x80x99t result in a bootable OS after a complete device whipe.

  • Can it nevertheless be that my Android device boots into a "stealth" partition? If, how can I get rid of it when I canxe2x80x99t see it via TWRP?
  • Is there any way to hard-format and repartition the internal SDs and recreate the partitions besides TWRPxe2x80x99s functionality? (In case therexe2x80x99s some problem with one of the partitions, which TWRP doesnxe2x80x99t actually whipe.)
  • Or (which would really make my day) has anyone ever experienced something alike and has a solution which might help me fix this by getting rid of the old OS which the device seems to detect who-knows-where and happily boots up?

EDIT

Since a comment asked for some version details et al:

  • Device is a Samsung GT-P3100, aka espresso3g
  • TWRP 3.2.1-0
  • Rom that is (letxe2x80x99s just call it) xe2x80x9cnon-killablexe2x80x9d is SlimKat. To be more specific

    Slim-4.4.4.build.9.0-OFFICIAL-8293 

Looking at things again and again it seems TWRP fails to correctly whipe one or more partitions (System, Data), even though there is not a single error message or warning when doing so.

I also tried erasing all partitions as well as the internal storage and flash lineage-13.0-20180211-nightly-espresso3g-signed, which results in an error 7 (rebooting the same darn xe2x80x9cnon-killablexe2x80x9d SlimKat).

Same goes for trying to erase all partitions as well as the internal storage and flash Slim_espresso3g-6.0.1-20180414-1959, which results in an error 7 (rebooting the same darn xe2x80x9cnon-killablexe2x80x9d SlimKat).

Also, it might be helpful to know I have another espresso3g device available, which doesnxe2x80x99t show any similar problems. On that other device, I can flash, whipe, backup, recover, and consequently successfully boot into the related ROM as expected.

Therefore, Ixe2x80x99m suspecting therexe2x80x99s something wrong with one or more partitions, which also prevents TWRP from correctly formatting in contrast to its claims. Even using the TWRP terminal and being crazy enough to try rm -rf /data/* and rm -rf /system/* seemed to work at first glimpse. Yet, the partition contents simply shows up on reboot as if nothing happened. Another indicator it might be some partition hickup is that xe2x80x93 any change to any setting or even starting any app in the booting xe2x80x9cnon-killablexe2x80x9d SlimKat results in the whole OS collapsing piece by piece until the device reboots into recovery.

              

回答列表

4
 
vote
vote
最佳答案
 
似乎我在 https://andi34.github.io/faq.html中找到了答案

quote:

我无法改变我的rom,擦除/格式不起作用。用奥丁闪现后没有任何改变。 16 GB标签2具有已知的故障EMMC(MAG2GA)。它可以发生,你的emmc得到"只读" ,所以你不能再现任何写作操作(你也不能格式化)。

从emmc数据表:

5.1.7寿命终点管理:

设备终结时间的结束是在设备中没有更具可用的保留块时定义的。当设备达到其寿命结束时,设备应将其状态更改为永久性写保护状态。在这种情况下,不再允许写操作,但仍然允许读取操作。

但是,在生命结束后不能保证操作的可靠性。

在一个错误的emmc固件上,它会更快地发生。

症状是什么?

  • 卸载的应用程序和删除的文件在重新启动
  • 后重新回归
  • 形成存储不起作用(重新启动旧ROM和应用程序后)
  • 你可以通过ocin
  • 闪光 它展示了"通过" 但在重新启动之后没有改变(例如,仍然没有畜牧粒或您之前安装过的旧恢复)

......可能还有更多,但只提到一些...

在大多数情况下,问题可以通过EMMC固件更新来修复,但是您需要一个能够执行此操作的人(可能通过ISP可能,您可以在家里自己做Esylie)。在一些不良案例中,您需要找到可以替换EMMC的人。

嗯,那就是那么。显然,我将不得不在早上第一件事给自己买一个新的设备,在哭泣的一条河流到银行,同时责备三星为其终身管理结束
 

Seems Ixe2x80x99ve found the answer at https://andi34.github.io/faq.html

Quote:

I can't change my rom, wipe / format doesn't work. Nothing changed after flashing with Odin. 16 GB Tab 2 have a known faulty EMMC (MAG2GA). It can happen, that your EMMC get xe2x80x9cread onlyxe2x80x9d, so you canxe2x80x99t perform any write actions (also you canxe2x80x99t format) anymore.

From the EMMC data sheet:

5.1.7 End of Life Management:

The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.

But, reliability of the operation can not be guaranteed after end of life.

On a faulty EMMC firmware it happens a lot faster.

What are the symptoms?

  • Uninstalled apps and deleted files are back after a reboot
  • Formating the storage doesnxe2x80x99t work (after reboot the old rom and apps are back)
  • You can flash whatever you like via Odin
  • it showes xe2x80x9cpassedxe2x80x9d but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)

xe2x80xa6 there might be some more, but only to mention some xe2x80xa6

In most cases, the issue can be fixed by a EMMC firmware update, but you need someone whoxe2x80x99s able to do it (possible via ISP, nothing you can do esylie at home yourself). In some bad cases you need to find someone who can replace your EMMC.

Well, thatxe2x80x99s that then. Obviously I will have to buy myself a new device first thing in the morning, after crying a river all the way to the bank while blaming Samsung for its End of Life Management.

 
 
     
     

相关问题

30  如何查看android内部分区表?  ( How can i view the android internal partition table ) 
我扎根了我的设备,把它放在恢复模式下,并将其链接到pc by adb shell < / a>。 如何查看存储设备和分区列表? 注意: fdisk 不起作用。 ...

2  TWRP:未能挂载'/ preload'(无效的参数)  ( Twrp failed to mount preload invalid argument ) 
使用twrp,几乎每个操作我得到 无法挂载'/ preload'(无效参数) 我的设备目前无法启动,这可能会与它有关, /preload 当前在 /etc/fstab 中,我可以在这里看到这里的条目 /dev/block/mmcblk0p16 /preload ext4 rw 0 0 当我尝试安装它时,...

0  交换分区不适用于华为U8160运行Cyanogenmod 7.2  ( Swap partition not working on huawei u8160 running cyanogenmod 7 2 ) 
我有一个Huawei U8160(也称为:沃达丰858智能),它正在运行Cyanogenmod 7.2(由Madteam于2012年2月7日发布)。 更新到2/7/2012更新后,我发现一个选项要使用交换分区而不是compcache(压缩缓存),因此我将SD卡重新分区,以使用 mini工具分区向导大小和主要(我有一个...

0  Android Factory重置是否清除缓存分区? [复制]  ( Does an android factory reset also clear the cache partition ) 
这个问题已经在这里有答案: 不是出厂重置与擦拭/数据完全相同和/缓存? (4个答案) ...

0  关于Link2SD和SD卡分区的问题  ( Questions about link2sd and sd card partitioning ) 
我有一个三星S3迷你,没有支持SD卡,所以我必须root它,并安装link2sd,花了最后3天,我的手机造成了更好的。 但我有问题,在网络上的所有教程中,他们说(我指的是这个博客,但还有许多其他博客文章和XDA帖子和YouTube视频,这些帖子和YouTube视频相同) 如果你有股票rom,请使用ext 2? (不...

4  FastBoot Recovery失败:分区'恢复'不支持Flash  ( Fastboot recovery failed partition recovery not support flash ) 
我的手机是联想S920运行官方Android OS 4.4.2。 我正在尝试通过fastboot安装cwm恢复。我尝试执行命令 fastboot flash recovery recovery.img 但我收到错误作为"恢复" 不支持Flash。请任何人帮我解决这个问题。我是否需要在恢复分区上更改任何内容?...

9  如何在SD卡上找到交换分区的路径名?  ( How to find the pathname of the swap partition on sd card ) 
作为 < / a>警告,你不应该在错误的分区上启用交换,或者您可以销毁您的手机: 在我们进一步进一步之前好的!之前的手机有一个分区布局,其中MMCBLCK0是SDCard(外部)我们的手机使用MMCB1CCK1用于外部SD。这很重要,因为如果使用应用程序,它可能会预设使用mmcblck0作为交换分区。使用此设置将导...

4  我的Android设备是否启动到“隐身”分区?  ( Is my android device booting into a stealth partition ) 
好的,这是一个奇怪的问题我遇到了一个我在几年内没有问题的Android系统遇到过......而且我几乎没有关于如何潜在修复它的想法。 让我们从一开始就描述问题以及我过去12个小时的尝试。 我今天早上醒来,今天早上看到最近安装的应用程序(通过Google Play商店)已经崩溃了,而且显然是其他应用程序和服务的卡车也展...

1  Android 4.2“Partition ......具有比其磁盘不同的主要专业!” logcat中的错误  ( Android 4 2 partition has a different major than its disk error in logcat ) 
我正在使用Samsung i9100运行Android 4.2.2,通过Sentinelrom_v4_75_I9100。没有更改内核外面的内核。 我尝试加密许多不同的4.2.2 roms,并且始终在几个重新启动之后sdcard0未安装。 在再次加密之前(并且可能具有相同的问题),我正在尝试在时间提前拍摄问题。 lo...

0  Samsung Galaxy J7 Pro 2017(SM-J730GM)似乎不支持分区SD卡  ( Samsung galaxy j7 pro 2017 sm j730gm doesnt seem to support partitioned sd ca ) 
我有一个三星Galaxy J7 Pro SM-J730GM在墨西哥的Sanborns商店购买,运行Telcel的股票ROM,植根于TWRP恢复和Link2SD。几周前,我重新分区了我的SD卡,以便使用Link2SD的应用程序链接功能。我记得要在拿起卡片之前重启我的手机几次,但目前我认为它终于工作了。然而,显然它只是一...




© 2022 it.wenda123.org All Rights Reserved. 问答之家 版权所有