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.
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.
Hello, I have a problem, I have and always open bootloader and installed without problems cyanogenmod, carbon AOSP, etc ... Yesterday install AOKP and I have no wifi signal, no mac address appears to me, went back to the 4.2 meter by flastool. 2 version .17 and I started the process again, doing the dalvik cache and format system / format.
Probe with thunder and phantom and kernels either.
I never had this before last as long probe many roms.
Someone tell me would know that there is solution for this? 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"
}
lokura72 said:
Hello, I have a problem, I have and always open bootloader and installed without problems cyanogenmod, carbon AOSP, etc ... Yesterday install AOKP and I have no wifi signal, no mac address appears to me, went back to the 4.2 meter by flastool. 2 version .17 and I started the process again, doing the dalvik cache and format system / format.
Probe with thunder and phantom and kernels either.
I never had this before last as long probe many roms.
Someone tell me would know that there is solution for this? Thanks
View attachment 2824850
Click to expand...
Click to collapse
By saying 17fw,are you sure you're flashing latest one...or maybe you're flashing the older one that is 4.1.2?
faizalotai said:
By saying 17fw,are you sure you're flashing latest one...or maybe you're flashing the older one that is 4.1.2?
Click to expand...
Click to collapse
No,got the .17 4.2.2, and the truth I'm going crazy trying everything
Ok, solved, you were right but was getting the .17 4.1.2
Happened in beginning of December- Okay, I have a XT1028 (it's the same thing as a XT1031) and tried to upgrade to CM13 using TWRP (also, I have bootloader 41.19). Unfortunately, I did not make a backup (stupid me!), because CM13 does not support CDMA devices on the Moto G because they are fixing LTE issues or something like that. So, I restored my phone using the 4.4.2 firmware. I used the guide right here: http://forum.xda-developers.com/showthread.php?t=2542219 But, there were lines going up the screen and stuff like that so I kept on trying it again. Oh yeah, after five minutes there's a boot loop. Then I read somewhere that the firmware has to be 4.4.4 or higher to get it to work on the 41.19 bootloader. Well, I flashed it, forgot the link but it involved MotoBoot and running some bat file. Then, when I boot it up, it has a black screen, and it's stuck on it. Well, I did something and it is now stuck on the Motorola logo, 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"
}
So help me.
I also downgrade from CM13, but to a 5.1 firm, and it didn't work too.
Reading some post, I decided to try a 4.4.4 firm, and yes, when I flash boot.img by fastboot the phone reboot and stuck on that Motorola logo. When I flashed againg 5.1, just for try, I've stuck on the bootloader messege.
Good luck, I'll follow this theard, maybe I found my solution here.
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??