Hi guys,
I was about to flash the resurrection rom on my S10 and somewhere in the process with Magisk when rooting it caused an error so that I wasn't able to get into boot menus with the hardware buttons anymore. I thought this would be fixed when flashing the resurrection rom, but now the rom apparently was an old version leading to the "rev. check fail" error.
I know I could fix this by flashing back to the default, but due to the other issue I am not able to get back into the boot menus and cannot connect the device to my pc.
Do you know whether there are any other options to get into boot menus aside from the typical button combinations (with USB connected device) or adb/pc based solutions?
I fear I caused a hard brick here, but would hope there maybe is a secret button I haven't found yet to fix this.
Any help is greatly appriciated!!!
Related
one of the tablets roms was haveing sound issuses with dead trigger 2 so i decided to install another rom (cm12) and it seems to be in a boot lap and cant get into fire os recovery by holding switches is there fix for that?
Nightmare-Rex420 said:
one of the tablets roms was haveing sound issuses with dead trigger 2 so i decided to install another rom (cm12) and it seems to be in a boot lap and cant get into fire os recovery by holding switches is there fix for that?
Click to expand...
Click to collapse
Likely not. If CM 12.1 was installed incorrectly it can bork access to stock recovery. If so there is no known recovery at this time.
Quick test:
- untether device
- long press power (20+ sec) to insure device is powered off
- press and hold key closest to headphone jack (vol-up)
- while continuing to hold <vol-up> press and hold <power>
- release both buttons when screen comes on
What happens next?
ah dang that sucks and i think it was the xposed framwork that bricked it becuase i did it to the other tablet and it bricked but was able to recover and start fresh, howcome dose cm12 screw recovery while other firmwares don't and how do you get xposed installed without it causeing a brick?
now i was able to get into recovery and flash 5.1.2 back but now i cant seem to be able to get root back with kingroot giveng error 592 once and then other error (chinese text) i tried re-installing the 5.1.2 again an additional like suggested if kingroot fails.
Nightmare-Rex420 said:
now i was able to get into recovery and flash 5.1.2 back but now i cant seem to be able to get root back with kingroot giveng error 592 once and then other error (chinese text) i tried re-installing the 5.1.2 again an additional like suggested if kingroot fails.
Click to expand...
Click to collapse
- assuming you didn't register with Amazon when device initialized
- try different builds of KingRoot, in particular 4.8.5, 4.9.2 and 4.9.6
- avoid version 5.x; difficult to uninstall and/or replace KingUser with SuperSU
- patience is a virtue: http://forum.xda-developers.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/post70077755
- some individuals report trying "dozens of times" before finding joy
Im at a loss here so I come to you guys in desperation. The home button and power button work fine in TWRP but do nothing in the actual operating system. Also the capacitive buttons dont light up or work for that matter. I havent succesfully flashed a custom rom yet as I kept having boot loop issues but I did a fresh install with kies and still no go. Anybody seen anything like this? Its a T-813 if that matters...
Hi guys,
I got a G5S+, which got stuck the other day.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me.
I decided to run with that tutorial here:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
Which seemed to be the right one.
Said so, booted into bootloader, installed the driver on my Win10 PC and ran through the steps.
I gut stuck on 'fastboot flash system system.img_sparsechunk.3' (15mins waiting..... after the steps before required about 12 Sec each) and needed to disconnect and connect the phone again.
Started with the same command and it worked.
Anyway when I got to the command 'fastboot flash system system.img_sparsechunk.5' I realized in the Potter Retail, there is no such file (neither there is 6 or 7).
I skipped the commands and continued.
When it came to rebooting the phone disconnected and thats it.
Since then I am not able to turn my phone back on.
Sometimes there seems to be a small notofication led showing up when trying to turn on the phone.
And you can hear the USB connect sound when I connect it to my computer.
Did anyone of you guys experience the same issue or has an idea what to do?
I have no idea what I shall so.
Best regards,
Matt
Which stock ROM did you flash? I'm hoping that following that guide, you flashed a stock ROM for sanders (i.e. the codename for Moto G5S Plus) and not for potter (codename for G5 Plus), which appear to be not compatible with each other.
Your original issue appears to be your device is booting into the stock recovery (which the start of is the 'no recovery' screen).
Do you know what model number or retail software channel, or the software build you had on your device before it failed? If so, we may be able to flash the correct sanders stock ROM to your device and get it going again. Another user appears to have gotten their device working when they incorrectly flashed the potter stock ROM and not sanders. https://forum.xda-developers.com/moto-g5s-plus/help/bricked-moto-g5s-plus-t3747064 Ideally you will want to flash the correct stock ROM for your device.
Oha damn you are right.
I am an idiot and tried to flash Potter to a G5S Plus.
Oh boy. I should not flash a cellphone after a long day at work.
I had the latest safety update installed and the latest release.
I am not sure though which software that used to be.
Unbelievable.....
Anyway, so my screen does not show anything anymore.
I guess the display driver dows not work or something like that.
The cellphone is still working I think, as the USB sound still appears.
Does anyone have an idea what to do if the screen stays black.
I still cannot believe it.....
Thanks though for your help!
EDIT: fastboot still reckognizes the phone. I guess this is good.
But the command 'fastboot oem fb_mode_set' runs into an error.
Edit2:
I skipped the first command and everything ran through (with some error messages though).
I hope it works now.
Device is currently rebooting and showing the blue motorola screen.
Lucky me.....
Okay, at least your device is booting now (ish)... I saw your other post and was wondering if you were able to boot from the bootloader.
1)Boot to fastboot (probably easiest by powering off your device, then hold down power and volume down keys until your device boots).
2)Once in the fastboot menu (with details about your device, like bootloader version), check that 'Start' is selected, and press the Power button to select. If 'Start' is not showing, use the volume keys to scroll through the options until 'Start' appears. Sometimes, this booting via fastboot bypasses an auto-boot to recovery mode.
Failing that, if you're on the 'no command' screen, then hold down the power button and tap the volume up key. Release both and it should let you into the recovery menu. Then, you can try to reboot to system.
Hi there,
I ran through all the steps you said.
But I ended up having the same issue. I always get back to the broken droid.
Is there a way to flash a completely new ROM to the device in its current condition?
I don't mind having a customrom, but I want to get it working again.
Thanks!
Matt
I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!
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.
Resetting the phone wasn't the solution and it got worser. It just doesnt detect any type of Wi-Fi connection and i can't continue till i had one. I don't have any sim on me to get any data.
I will really appreciate anyone that helps me.
I recently rooted my phone and unfortunately the wi-fi and bluetooth doesnt work at all,
I found some tutorials to this but they say i need the exact boot.img for my realme.
Unfortunately though, i can't find any for C.17 update.
Can anybody help me up please?
I know, my phone is different. But theres only a few people online in my phone's category. And i need quick help for it!
Realme C25s (RMX3195)
my phone is on bootloop, i tried to root it for 4 days, it was successful but rebooting to fastboot just ruined everything and it just started a bootloop (edited)
anybody here to help me?
first thing i've tried to get rid of it just being power and volume up, i also tried it while its charging (edited)
third one is different, held down all the buttons at the same time while realme logo shown up, it just turns off the phone.
but theres a problem now, when i charge it. the bootloop continues. same as holding down power button too. same result as power, volume down buttons held down.
for rooting one have to patch boot.img with Magisk, so obviously you already have had the boot.img - just flash the stock boot.img back to phone.