Hello!
I rooted my Xianomi Redmi Note 8 PRO with Magisk. I also installed the Pixel Experience ROM without a problem. Afterward, it worked really well without any stability issues. Then a new version of Pixel Experience ROM was released and I decided to update the ROM. But I must have done something wrong, despite reading the instructions. Afterward, the phone started to reboot randomly, which disturbed me greatly. Because of this, I flashed the Stockrom hoping that would repair the stability issues. But then it turned worse...
Now the phone crashes repeatedly and often! During the install, the phone crashed even before I could enter the WIFI password. But I managed finally to finish the setup after multiple crashes. Since then I have tried to repair my phone in all ways I can come up with.
1. I have installed TWRP. Wiped everything: Cache, Dalvik, System, Data, Internal storage.
2. Have also repaired the filesystem in all partitions where it's possible.
3. Installed Pixel Experience again
4. Tried to root the phone again with Magis v23, which I failed:
"Failed to mount 'system_root' (Device or resource busy)
"Failed to mount 'vendor' (Device or resource busy).
Right now, Pixel Experience ROM is installed. Now the phone crashes during the "The Phone is prepared... This can take a couple of minutes". It seems that it doesn't matter which steps I take to solve this. In this state, the phone is not better than a hard-bricked one.
Can anything be done to solve this mess?
Related
Okay so,
I feel like this one's on the medium level of emergency here,
The issue is I flashed my cache, dalvick, factory reset, and (not sure) system to install Simple CM9, everything rolled along nicely except......
After booting into my promising new life, I noticed several issues:
KFU no longer recognized it, though the drivers still read "Android ADB Interface" in my computer
Google Apps would not sync my data, but still allows me to download apps from the play store
The sd Card partition no longer is shown by the OS, but still shows up when connected with usb (i'll be downloading a file manager soon, so this may answer itself to whether or not I can still access it)
TWRP will not boot by means of pressing the power button during initial boot
I understand I could solve my GAPPS sync problem by flashing them, and all my other problems wouldn't matter then. but I still have no means to flash'em.
Any and all help is GREATLY appreciated!
-a lowly noob
P.S. Everything about the ROM is fantastic except for those issues, (which are probably my fault) so many thanks on that end
P.P.S. (I do have a nandroid of my stock os before I wiped so If all else fails I can just go back to that if TWRP can be accessed and start over)
I seen a similar issue earlier and the guy fixed it by reinstalling the twrp
but u can always try going to reboot and select recovery and see if that works
gracci
That's a step in the right direction, thank you
no problem glad I could help
HI,
I used to be more active in this forum, but honestly nowadays I can't found any reason to since everything has been smooth sailing for me without any problems—until this day, at least. Somehow I got my internal sdcard busted, it was pretty spontaneous, all I can recall is suddenly the system starts to reboot itself. Nothing much, I thought to myself, problem is the system keeps rebooting, it doesn't even last a minute. Naturally when faced with this problem one would do the usual procedure, namely completely format the thing to stock the rule out any possibility on the user side of things, but then this is the part when it starts to get interesting...
The thing refused to be formatted, seriously, it baffles me at first but it does
Things I've tried:
Fastboot, it hangs at writing system, whether I was doing it line per line manually or via the flash_all.sh script, I haven't tried the toolkit but I think it's safe to assume that It'll do the same thing. Even if it does go on (which it did, once) it doesn't do any sort of changes whatsoever to the system.
ADB, nope, not this one either. And since the system reboots faster before I can do anything worthwhile it's pretty much out of the question.
Recovery, multiple times I've tried nuking everything via CWM, nada. I've tried TWRP too, I have to boot it from fastboot since it apparently doesn't allow me to flash a new recovery either, it reverts back to CWM every time. Also tried to flash a different ROM (CM), that didn't work, it spits out an error message regarding some failure in changing metadata, thought it was a corrupted file or something, so I re-downloaded it, that doesn't work. Still convinced that it's corrupted I tried 4 different version of it without any luck. Even the one I had successfully flashed before. Interestingly enough, flashing the exact same ROM I'm currently using (ShinyROM) works, not that it seems to do anything.
Built-in data format from settings, now this doesn't work because I assume that it needs the stock recovery to work, which I couldn't flash because it wouldn't let me—in a sense that it flashes just fine on the command line—fastboot doesn't show up any error or anything—but it defaults back to CWM as soon as I reboot it.
Manually via terminal emulator/file manager, still nothing, curiously enough, Terminal Emulator indicates that the whole system is read-only (I tried making a file with it, it shows that exact message).
Grit my teeth, clench my fist and screams out every curse word that I know of, this somewhat reduced my stress levels, but ultimately yields nothing.
Which led to be believe that either my phone was either a) Haunted or b) Has a serious hardware problem, I'm leaning on the latter. A few quick lookup with my limited amount of Google-fu and I've found several threads that described the exact same issue:
http://forums.androidcentral.com/go...-factory-settings-no-matter-method-i-try.html
http://forums.androidcentral.com/go...eset-nexus-7-2102-using-multiple-methods.html
Both of which hints at it being a hardware problem. Which was my biggest fear since I can't really revert the phone back to stock now can I? Locking the bootloader doesn't seem to work either (the 'fastboot oem lock' command works just fine but just like every single thing I've tried, reverts back to my previous setup as soon as I did a reboot), plus this means I have to send it back with my private data still on it, and I can't say I trust Samsung, Google (or anyone really) with my private data. Not to mention some of the stories I've heard/read about Samsung and their policy regarding rooted devices (much less ones with an unlocked bootloader).
In case it helps, here's a few more details:
What state the device is currently in:
It boots up just fine, but nor for long, apps starts to hang and ends up with a cold reboot (sorry if it's not the right jargon, but it starts right from the Google screen).
Everything that doesn't require you to access the filesystem works fine.
Apps doesn't seem to be able to write anything to the filesystem, I tried backing it up with Titanium Backup, much to my surprise the backup files weren't made (although TiBu seems to indicate that they were).
What the device is running:
Variant: Maguro 16GB
ROM: ShinyROM 4.4.2
Kernel: franco.Kernel r395
Baseband: XXLJ1
Bootloader: PRIMED04
Also I don't know if this will affect things but for the record I'm running the latest Ubuntu and Debian.
So this post is pretty much a shot in the dark, since I think I know what I'm dealing with already; if anyone had this problem before in the past, or has it now and somehow managed to fixed it, please do tell. Or if anyone has any experiences RMA-ing your device with a condition like this I'd love to know.
Yep your EMMC is fried. Sorry man.. But you can go to warranty. They *should* accept it since it is a developers phone but they could make a lot of hassle about it being rooted..
Sent from my Galaxy Nexus using XDA Premium HD app
Hi,
I recently updated my Z1c (rooted, Kingroot) using the Xperia Companion because I got annoyed by the constant update notification. After updating to Build 14.6.A.236, I re-rooted using Kingroot again, however, with a couple of issues:
-AdAway reports that it fails to replace the host-file to block ads despite having root authorization.
-Link2SD reports that the secondary partition on my SD card (which worked fine so far) was mounted after bootup, and gave me the choice between a fast reboot (which didn't solve it) and creating a new mount-script, which results in a "can't unmount /data/sdext2: Invalid argument mount: Operation not permitted" message.
Titanium Backup on the other hand works fine.
Unrelated to the Update I also noticed that the point on the screen where the touch was recognized would randomly jump around the width of where I touched the screen while charging, and only while charging.
I apologize for anything imcomprehensive my non-native English may have caused and thank you in advance for any help.
Kind regards,
Skysoarer
Skysoarer said:
Hi,
I recently updated my Z1c (rooted, Kingroot) using the Xperia Companion because I got annoyed by the constant update notification. After updating to Build 14.6.A.236, I re-rooted using Kingroot again, however, with a couple of issues:
-AdAway reports that it fails to replace the host-file to block ads despite having root authorization.
-Link2SD reports that the secondary partition on my SD card (which worked fine so far) was mounted after bootup, and gave me the choice between a fast reboot (which didn't solve it) and creating a new mount-script, which results in a "can't unmount /data/sdext2: Invalid argument mount: Operation not permitted" message.
Titanium Backup on the other hand works fine.
Unrelated to the Update I also noticed that the point on the screen where the touch was recognized would randomly jump around the width of where I touched the screen while charging, and only while charging.
I apologize for anything imcomprehensive my non-native English may have caused and thank you in advance for any help.
Kind regards,
Skysoarer
Click to expand...
Click to collapse
For the first 2, sounds like rw access, known to be an issue on newer lp builds. Flashing Nut's dual recovery usually takes care of it Also, check this - http://forum.xda-developers.com/showpost.php?p=67828175&postcount=1610 Also, try setting SELinux to permissive.
Other issue seems like random display bug. Might go away after reboot, or maybe cache wipe or something, not sure...
Alright, hello everyone,
I'm having a pretty weird issue here. I've flashed my DUK-L09 and the C432B183 EU Firmware, everything was running fine.
I couldn't make a backup of the /data/ partition though, someone told me to wipe the data to decrypt it, but nothing came good after this.
So I tried to flash back the old recovery image by extracting it, flashing it via fastboot, as I would normally do; enter the factory reset, run it.
Everything is good, it goes up to 100% pretty fast, less than 2 minutes. I then enter the setup wizard the NFC is acting weird. It keeps activating
and deactivating illogically. So, ignoring this issue, I kept up configuring the phone then once I'm logged in Google and sync'd, pops a Huawei ID
logging page really really fast then goes back to the EMUI menu at the beginning of the Setup, in an infinite loop.
Useful information to let you help me better:
- Many firmwares. Currently trying to flash back to B120a and NoCheck from OldDroid and Morph. (Edit: Didn't work)
- Phone unlocked, TWRP accessible.
- Getting a weird "Error 9" when trying to run Update.zip from TWRP.
- Sideload working, but not transferring anything.
- Cannot find any B182 or B130 stock firmware. Everything seems to be gone from Huawei's servers.
- The loading logo isn't Honor anymore but Android, for a reason I can't yet understand.
- Restoring a clean backup (without /data/, since I couldn't back it up) did not fix the problem.
- Trying to update with the 3 buttons do not work, even with the right firmware (C432B183) (Software install failed)
- Factory reset works with the right ROM, but gets me to the setup loop issue.
- The loop occurs when I am supposed to see the Huawei ID setup page. If I do not put any SIM card, or WiFi
I am prompted to choose which way to restore data; if I skip this step, it blinks and doesn't do anything.
- I tried to restore via WiFi (Google's cloud stored data from my account), but it does the same thing as mentioned
earlier. It blinks multiple times rapidly the "Huawei ID" setup page then goes back to the first Setup screen w/o
me being able to do anything about that.
I'll be glad if you knew the answer to this, because I'm all lost right now.
Greetings, Kameyuu.
UP !
After many tries and a LOT of hard work, and spent an entire night (was about to spend the second night on this), I found the culprit and now I know what the issue is, it sounds completely legitimate.
So here are the reason and the solution to this issue:
Actually, my CUST was somehow broken. I never flashed it back because no one told me to flash the CUST.img back. They told me to flash BOOT, SYSTEM, and RECOVERY only.
So, after I downloaded a software called HUAWEI Multi-Tool (From hwmt.ru) I noticed they were also asking for the CUST.img and USERDATA.img (<- this one was apparently optional)
So, trying my luck I flashed it. Did a factory reset, and all, it acted weird and failed, then I tried again and it succeeded. So, with all my hope I booted the phone to the system, started configuring... And it worked !
I was able to set up the phone. For a -yet- unknown reason, some apps look missing and the NFC is still blinking on and off repeatedly and randomly, but I'm investigating that.
If you have any question on the precise steps feel free to send me a PM or ask in the thread directly I'll be glad to sort your issue out.
[EDIT]
Sorry, double post I don't know why my message was posted twice. Feel free to delete this message @moderators
Good morning, afternoon or evening depending on where you are reading me from. As the title says, it seems that my LG G8 Verizon has become a paperweight since it remains in a recovery loop. My LG G8 has the bootloader unlocked with Firehose and QFIL (https://forum.xda-developers.com/t/...nlock-and-magisk-root-using-firehose.4221793/), I followed the guide (https://forum.xda-developers.com/t/...wos-12-1-for-lg-g8-alphaplus-alphalm.4354847/) months ago to install the Arrow OS rom and everything worked correctly.
Now the matter in question, days before this week most of my accounts were tried to be violated by a hacker, I don't know where I could have caught the ware but it's done already. Today after several hours in front of the laptop I moved all my accounts, changed passwords and started with one and only gmail and outlook account. To finish everything I decided to factory reset my device, everything seemed to be going well until I saw that it started in the recovery and not in the typical screen after a factory reset. I have little experience in flashing custom roms, the previous times I've flashed everything went as it should and I lived without any problem so right now I don't know what to do.
Every time I enter recovery I get a message on the bottom log saying
"E:failed to clear bcb message: failed to open /dev/block/bootdevice/by-name/misc: no such file in directory".
When I try to make a factory reset from the recovery it says
"Wiping data...
Formatting /data...
E:/system/bin/mke2fs failed with status 1
E:format_volume: Failed to make ext4 on /dev/block/bootdevice/by-name/userdata
Success
Formatting /metadata
E:/system/bin/mke2fs failed with status 1
E:format_volume: Failed to make ext4 on /dev/block/bootdevice/by-name/metadata
Success
Data wipe failed.
E: failed to clear bcb message: failed to open /dev/block/bootdevice/by-name/misc: no such file in directory".
I really don't know what the problem could be, I already tried to use LGUP to try to go back to my original rom but it stops at 4% and the executable closes. Days before, I deactivated the developer options since it was a requirement of the Malwarebytes app and I know that it is partly my fault for not having activated it again. I can go into download mode by pressing volume up but to the best of my knowledge without debugging and oem unlocked I can't do much. [Edit: Reading the firehose and qfil guide hours later I discovered that the Verizon variant doesn't mention as necessary to turn the oem unlock so maybe a little hope?]
If it helps, I still have the backups of sysnand_00.bin, essential.exefs and some others I made before unlocking the bootloader with firehose and qfil, as well as a zip called "Arrow36backup1647621938922" with a .bak named "launcher_backup_main".
Right now I have no way to upload images of the recovery log that is in the advanced settings of the arrow recovery, I will try to do it later but notice that it is quite long.
I sincerely hope that someone has the slightest idea that it could be happening and I will gladly read it and appreciate your time for giving me a hand.
At the end of it all it wasn't that hard to solve my problem, it was just that I was afraid of messing it up even more.
After rereading the guides that I had followed months ago and also the various comments, I came to the conclusion that LGUP could solve it, only that I had done it wrong before. It was thanks to this thread that I was able to download a better version of the tool (https://forum.xda-developers.com/t/lgup-1-16-3-patched-found-and-works-with-lg-wing.4357211/) and after following the instructions everything was like new on my device.
If someone else is going through the same problem as me, you can write to me and I will help you with what worked for me.