Hey there folks,
Today morning I have looked into the Magisk app, I think it was in version 24.3, and it said it has an update.
I have pressed on the update, it opened the shell, and patched the relevant ROM, nothing unusual.
Then it rebooted.
Here comes the hassle.
The stock oneplus boot image came in (my phone has a boot animation and an 1+ and android splashscreen before) and I was like waiting.
After 30 secs I thought that it is taking an unusually long time, but maybe its the new module.
A few minutes later I considered that there is something wrong with it, and tried to hardware reboot it, maybe it would solve my problem.
Still nothing
Current situation : My guess is that it got bricked, it is not in bootloop, but probably my patch has failed as it does not boot in
nor adb nor fastboot (while the device is in fastboot mode) detects it from a Win10 powershell/cmd, from which I have had no problem connecting before
Any idea how can I fix it and recover the data from it at least?
Related
Dear xdadevelopers members,
I have anHTC One m7 (GSM Version Unlocked without Providerlock)
It is rootet and Bootloader unlocked and at the moment is TWRP v.2.8.1.0 Recovery installed (before it wasCWM Touch).
It is the Stock ROM it got with which I bought it, not completely ... before rooting I did one OTA update . So it is now 4.2.2 with normal sense edition.
I am trying to resolve the problem, but with no success. So the phone starts normally until I have to enter the PIN, if I'm quick enough I can enter it successfully. Then everything looks quite normal, then only after about 5-10 seconds it goes black and reboots again, this happens all the time.
Booting into Save Mode has the exact same issue!
Recovery is working normally.
Does anyone have any idea why this might be and how I could fix it?
My guess is that it has occurred because I installed a root uninstaller tool to uninstall/disabled some of HTC's own apps, so maybe I have deleted too many of them. But that's a long time ago, it worked for weeks even after the erase with the tool (I did never a restart after), only when I then made a reboot weeks later the problem occured.
Saturos said:
Dear xdadevelopers members,
I have anHTC One m7 (GSM Version Unlocked without Providerlock)
It is rootet and Bootloader unlocked and at the moment is TWRP v.2.8.1.0 Recovery installed (before it wasCWM Touch).
It is the Stock ROM it got with which I bought it, not completely ... before rooting I did one OTA update . So it is now 4.2.2 with normal sense edition.
I am trying to resolve the problem, but with no success. So the phone starts normally until I have to enter the PIN, if I'm quick enough I can enter it successfully. Then everything looks quite normal, then only after about 5-10 seconds it goes black and reboots again, this happens all the time.
Booting into Save Mode has the exact same issue!
Recovery is working normally.
Does anyone have any idea why this might be and how I could fix it?
My guess is that it has occurred because I installed a root uninstaller tool to uninstall/disabled some of HTC's own apps, so maybe I have deleted too many of them. But that's a long time ago, it worked for weeks even after the erase with the tool (I did never a restart after), only when I then made a reboot weeks later the problem occured.
Click to expand...
Click to collapse
First thing you should do is a factory reset and see if its still rebooting
then return to return to 100% stock
what is your fastboot getvar all?
alray said:
First thing you should do is a factory reset and see if its still rebooting
then return to return to 100% stock
what is your fastboot getvar all?
Click to expand...
Click to collapse
THanks for your help. I tried a few things now in the 10 sec I had , moved the phone to air plane mode rebooted again and since then its working normally again. I even diabled airplane mode and everything is up to normal again its running like a charm since 30 minutes. I Also got a HTC message that the phone was recovered from a problem and it would like me to send an error report (I did). But I am a bit afraid now to reboot it again, so I think I can not make the fastboot getvar all command or can I place this command without restarting and booting into the bootloader?
Saturos said:
THanks for your help. I tried a few things now in the 10 sec I had , moved the phone to air plane mode rebooted again and since then its working normally again. I even diabled airplane mode and everything is up to normal again its running like a charm since 30 minutes. I Also got a HTC message that the phone was recovered from a problem and it would like me to send an error report (I did). But I am a bit afraid now to reboot it again, so I think I can not make the fastboot getvar all command or can I place this command without restarting and booting into the bootloader?
Click to expand...
Click to collapse
this command must be entered when in bootloader/fastboot mode
I have a Moto G XT1072. I had unlocked the bootloader, installed TWRP and rooted it a while ago. I did not install any custom rom.
I was completely unaware of TWRP's lack of support for OTA upgrades, so when my phone notified me that there was an update available, I was like "oh, cool, okay" and downloaded it.
a) The download finished, the phone rebooted and TWRP recovery popped up.
b)"Mh, I guess I have to find the update file and flash it, probably"
c) Of course I didn't find it, so I googled and found out that if I want to install an OTA update I have to flash back the stock recovery and I might lose root. "Not worth it, thanks, maybe when 6.0 comes out"
d) So I rebooted the phone. Boot screen with motorola logo shows up, phone boots normally, I insert my sim card pin, set the alarm for tomorrow morning (6:00 am, fml) and *poof*, phone shuts down and reboots in TWRP.
e) back to point d.
Recap: I downloaded the update but I didn't install it, phone boots normally (I can even go in settings), but after 30 seconds it shuts down and reboots in TWRP. I do not care about the update, I just hope I can avoid re-rooting or even wiping.
I've got the exact same problem as you. Stupid to not have thought this could've happened with TWRP installed. Additional problem is, I have removed everything ''root-related'' (adb, fastboot), because I thought I wouldn't need it anymore. TWRP is obviously still on my mobile, but that's about it. I have already made a backup in TWRP (don't think it will help, because I'm afraid it will backup as boot trap), but who knows if it may help.
Back to the point, I'm a noob with rooting, I don't even know how I've managed to root it in the first place, but I'm stuck with the same problem as you are but without the required tools (at least, that's what I think)...
UPDATE: So my phone finished the backup, I turned it off to charge my battery, I fired it back up after an hour (normal way, not TWRP way), and it all of the sudden works again. It doesn't boot trap anymore and it seems like I'm able to use every function properly again. After those 30 seconds (where it usually rebooted), I now got the message that the installation had failed and that I should try again later. I don't know if there's any logical explanation for this or if this is pure luck, but I'm glad it's working again! I don't know if this will help for you as well ricvail, but I think it's at least worth a shot!
So since I didn't read anything of xposed being "BAD" for the new CM beta, i figured i'd give it a shot.
The current gist is this:
Powers on, can't get into TWRP, if I get into the Download Mode and go to "Send_Command.exe \\.\COM4" and do "#id" it just comes back with "#" or it may take a long time, then it'll just come back with "#". Fastboot devices, shows nothing. ADB Devices same thing. I'd love to do a HardReset, or anything that could be done, but the only button config that works is Pressing Up when plugging the phone in.
Any ideas?
Yes I've seen others are having bootloops, noone seems to be having them due to what I've done (xposed + CM).
UPDATE: Problem solved. http://forum.xda-developers.com/showpost.php?p=63674157&postcount=3
Got a bit further thanks (i'll probably regret that word) to the LG Flash Tool.
Followed the instructions, flashed the KDZ, then I guess the flash tool error'd out because the Download Mode still showed 0% but the tool had a **** ton of ????? ??????
Needless to say, TWRP is booting up now!....but "unable to mount '/system'.
Attempted the H81110N Bootstack and Image, but that didn't work. due to the /system.
Retrying again with the LGTool, this time choosing English -_-
Looks like im at 52%, that error message i received i guess should have ben ignored.
\
Edit: wasn't looking good with LGTool crashing. but I've successfully gotten the phone back to stock it looks like. Just going through some reboots. I did get a glimpse of the LG setup screen
Hello everyone,
First I would like to mention i tried almost everything i can think of but a while back I lost root via incorect ota update from magisk (i guess i accidentally rebooted)
And cant seem to get it back ever since.
I tried reflashing 10.14 from orangefox, and it boots but as soon as i turn off or reboot it is stuck on splash screen. I heard that Xiaomi did botch several security updates so people tried full roms, not incremental and solved their problems, so i flashed 10.17 same story, boots and on shoutdown stuck on splash screen on the next boot
Problem is it wont even boot if i do a full recovery.zip install, only if i flash the OTA right after fastboot boot, i presumed i messed something in A/B partitions, so i installed recovery to ramdisk, twrp recommends doing a recovery bootloop fix after, which i cannot do since i get ERROR 1 something hex kernel
Also it seems to be a problem that i can flash from fastboot, but not miflash since error appears that the critical partition is locked, which i am sure i unlocked before, after all i couldn' tb
I would really like to fix it and not lose data of apps. I tried flashing 10.17 from orange fox, and doing a magisk flash from the fox addons, and again it gets stuck on splash. If I could just somehow get into te os while root so i can backup app data and run over to a Rom away from emmc bugs and the like. Really a shame that they abandoned this beautiful looking phone with mid range specs, even in its prime.
I would also like to patch boot.img from 10.17, but it seems it is not needed since i did that with 10.14, which also stuck on android welcome screen when i flashed magisk. In addition it seems boot.img is not modified at all since all files are date of creation 2008. for all firmware on that phone
Please, any suggestions, I need to do more clearer scans (which Gcams allow), and after even touching fastboot i am getting software errors all over (i am really hoping those are user errors)
Thank you for reading.
Somehow it solved itself. I know I should explain what I did but i really don't know.
Edl over adb or fastboot wasn't working so i entered it in https://androidfilehost.com/?fid=24591000424940129
the script worked, but it was not made for Xiaomi mi a2.
Then i did a miflash, but it did an infinite flashing which after 1000 seconds i aborted, then i trid it and it booted.
Few notes it wont boot when connected to a usb, and it sometimes gets into fastboot splashscreen combo if i hold fastboot while on flashscreen, after that it booted.
Maybe it is a trick for soft brick i dont know, after that i was able to reflash magisk.
I now it isn't much, but hopefully it helps someone, i was hanging onto threads, searching one error after another.
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Matsilagi said:
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Click to expand...
Click to collapse
Vbmeta means Android Verified Boot.
Vbmeta is default for all android devices and it was made by Google.
It is not specific made by Xiaomi.
Android Verified Boot 2.0
https://source.android.com/security/verifiedboot/avb
What changes did you do when you fixed the app issue?
Couldn't do any, just tried to boot into recovery, then got into that bootlooop cycle, couldn't reach anything.
Managed to get into EDL and SP Flash Tool mode, however, im a bit confused on what i need to flash to get it back to life with stock MIUI or atleast boot to main system to use ADB.
My IMEI is fixed on the phone stickers so i can reasily recover that aswell, any help is appreciated.
EDIT: Now i just need help flashing as it seems, what do i need to do to properly re-flash / re-boot the phone without losing IMEI and that sorta stuff? I plan on switching back to Pixel Plus UI again so, it isn't an issue.
EDIT2: Completely fixed, followed VD's guide on EDL/Mediatek Bypass method and flashed a normal GLOBAL rom, all was fixed, no IMEI lost.