Hey everyone,
I have this issue with my device hopefully you know something about it: a while ago I rooted it, got Magisk on it all that. The device was just out so updates were still coming strong--or maybe I payed more attention to them than I do now, IDK--the case is that I accepted one of them and it undid the root and updated MIUI to something-something, regardless, since then I'm unable to flash a recovery image.
I thought the partitions got messed up or something and flashed the official system with the official Xiaomi spyware/adware suite "tools" hoping it would rewrite what needed rewriting then I tried flashing the recovery (TWRP) but no luck.
I'm using the XiaomiADBFastbootTools Java applet. It seemingly flashes the thing successfuly then it boots right into the system again, not in recovery. If I use force a recovery reboot through adb or with the buttons (which I've already forgot which were) the recovery the comes up is the official one, not TWRP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Every time finishes "successfully", then the device reboots taking just tiny bit longer then I see the MIUI logo with the sort of paint-spill animation covering it and then I'm back on stupid Mars again (the stock pseudo-interactive wallpaper). Not even my information is lost--not that I'd want to, but at least it'd be something.
Since I removed most bloat the phone became pretty much useless and I wasn't even thorough because there's stuff that just can't be removed. Rooting would allow me to get some utility back out of it. Can it be fixed at all??
Related
Hi,
A few months back, I unrooted my NS4G in order update to the official ICS release. Initially, I was content with the official ICS on my phone, however, I've come to miss the fun mods and features that are available with custom ROMs. Now, I can't seem to re-root my phone.
The bootloader is still unlocked so I tried going into recovery like old times but received a blank screen with an image of the android bot face down with its back door open and an exclamation point (pictured below).
Please help. Although I've rooted a few phones, including this one, I still feel like a rookie and may be missing something very simple.
Thanks!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need to snag a custom recovery and get the current superuser. After that, you will need to make sure you either edit the script or delete the script in the system so it doesn't overwrit CWM.
Recovery fix: http://forum.xda-developers.com/showpost.php?p=27027436&postcount=8
Superuser:http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
CWM
The recovery needs to be pushed while in the bootloader via fastboot
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo4g.img
Recovery first, superuser flash 2nd, fix the recovery last once you've fully booted up.
When the faced down android appears , try pressing volume up button once . Helped me one time.
Sent from my Nexus S using xda app-developers app
So how about an update? How are you going with it?
I have had intermittent problems in the past similar to yours, and I was able to solve it - where are you up to?
You should go into a command prompt on your computer then do a fastboot oem lock then unlock. (This will erase all data)
Tell me if this works
Screenshot shows the phone is already unlocked-
I purchased an unlocked LG Optimus T P509 phone off eBay. Phone works fine as it was purchased. It has the stock ROM from T-Mobile and I was interested in loading a different ROM.
I'm attempting to load the kernel found in this thread but I'm having difficulty getting into recovery mode.
I'm aware of the steps leading up to recovery mode. Install z4root to root the phone, install a terminal emulator, and run the reboot recovery command. The problem I'm having happens after I type that command and the phone reboots.
I'm supposed to get this screen here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But instead I get this:
The screen that I'm getting stays there for about 10 seconds, then the phone reboots itself again and loads right back up completely wiped to factory default.
What gives? I'm I completely stuck and can't do jack with this phone?
Thanks in advance for your help.
Alright, so I figured it out.
This phone has a two-step process to loading a cooked ROM from this place.
I'm compelled to post a write-up of my experience since the information in this forum is all over the place for this phone. Once I'm all finished playing with the phone, I'll work on it.
I ended up installing a stock ROM without overclocking abilities since I couldn't figure out what was the best route to go. Later on I'll tinker with it.
This place, as always, is a great source of information. Thanks again.
I had My HTC One S working fine with an unlocked bootloader, CWM Recovery, and CyanogenMod 10.2. One day, I get a notice that there's a system update, so I thought, hey that's cool, over the air updates for CyanogenMod. So I do it and now when it boots it looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With some difficulty, I was able to get into the bootloader then into CWM. I cleared everything and re-flashed the original CyanogenMod ROM, but it still does this when it boots. It also does not appear to turn on properly. Does anybody know what's going on here?
polybius said:
I had My HTC One S working fine with an unlocked bootloader, CWM Recovery, and CyanogenMod 10.2. One day, I get a notice that there's a system update, so I thought, hey that's cool, over the air updates for CyanogenMod. So I do it and now when it boots it looks like this:
With some difficulty, I was able to get into the bootloader then into CWM. I cleared everything and re-flashed the original CyanogenMod ROM, but it still does this when it boots. It also does not appear to turn on properly. Does anybody know what's going on here?
Click to expand...
Click to collapse
Your link doesn't work.
I also cannot see any picture of your screen, but I think you mean freaky colours on your screen.
This is due to updated display drivers some time ago on CMs side.
Which means if you use a newer ROM, you also have to use a newer kernel to get the correct colours back.
If you are S-On your kernel won`t be updated by just flashing the firmware, you have to fastboot the kernel afterwards.
So yeah, I've rooted my Xperia a long time ago and today I was deleting some apps when I accidentally deleted the theme I was using, Sapphire iirc, and the phone instantly became as what I've described in the title. I can only scroll the quick settings down (and then go to settings and such), but the rest of the screen is all black, no menu, no apps, no nothing. Locked screen works, it shows the lock screen image as usual but as soon I unlock the phone it's back at it.
I've tried some stuff out, like downloading new themes but I can't move them to a folder which would made them recognazible as a theme, can't seem to boot in recovery mode either.
I'm a bit stuck here, any help? Here's how it looks:
Locked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unlocked:
Bro, I believe that you have been also deleted the Xperia(TM) Home.apk Because there is no launcher presenting, you need to flash again the rom or custom rom.
try to open Settings. Should be able to open????
yeah, I might've done that, dunno
Is flashing the rom the only option tho? I really cba to do it...
and yes I can access settings
btw my bootloader is locked, so it makes things harder
solved it
if in the future anyone as dumb as me has the same problem, here's what I did:
This tutorial using this ROM
However, did you unlocked the bootloader???
Hello everyone,
Some years ago i had an S7 as my phone, but it broke, and i bought an S10e now.
Until now, I didn't have problems with stock fw, but now I want to root the device.
I've read some articles about it, and it seems really really complicated.
I have looked at the Magisk website, why is installing through Custom Recovery not recommended? It's so much more complicated the way they describe it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It also says, this is only possible if i have "boot ramdisk". What is that? Why is it required? And why do i not have it? (according to the Magisk App)
I remember it being as simple as putting TWRP on the phone and flashing Magisk on my S7.
Easy, fast, done with 3 clicks or something. (Same thing with new Operating System).
Why did everything become so complicated?
And is installing TWRP on it's own even possible? And is it even worth it if you can't install anything with it?
Thanks in advance, to anyone kind enough to take their time to explain.
I'm thinking of buying a used S7 again now
I use Lygisk root on my SM-G970F, but I first changed to a custom operating system (LineageOS). With a custom operating system, installation of Lygisk.ZIP is simply done in the Lineage custom recovery (and installing the client app Lygisk.APK to manage it)
If you use Google apps, you might want to try LineageOS+MicroG instead and then root that.
I haven't tried getting root with Samsung's original operating system, but I think it requires patching the boot image and is more complicated like you said.