Bricked Moto G (maybe) - Moto G Q&A, Help & Troubleshooting

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.

Related

[Q] LG Optimus T P509 and loading a new kernel

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.

[Q] Scrambled Display

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.

[Completed] Update fail moto g3 xt1541

Hello everyone.
I have a moto g3 (see titel), but it won't update from android 6.0 to 6.0.1
Maybe you've already read my prev posts where i've had trouble rooting and soft-bricked my device.
{
"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"
}
I have unlocked my bootloader and after some bootloops i've flashed the costum rom again from xda (bootloader: system is MODIFIED,statuscode 3).
But right now, i have downloaded the update, clicked on install now and my phone powered off. It booted up into recovery and said: installing update...
And at the very end the robot felt end there apeared "Error!"
I've booted um my phone and got a screen:
Update failed, no changes applied on your moto g.
Doing a factory reset didn't solve the problem...
Help!
bomboem said:
Hello everyone.
I have a moto g3 (see titel), but it won't update from android 6.0 to 6.0.1
Maybe you've already read my prev posts where i've had trouble rooting and soft-bricked my device.
I have unlocked my bootloader and after some bootloops i've flashed the costum rom again from xda (bootloader: system is MODIFIED,statuscode 3).
But right now, i have downloaded the update, clicked on install now and my phone powered off. It booted up into recovery and said: installing update...
And at the very end the robot felt end there apeared "Error!"
I've booted um my phone and got a screen:
Update failed, no changes applied on your moto g.
Doing a factory reset didn't solve the problem...
Help!
Click to expand...
Click to collapse
Please do not create a thread or topic more than once.
http://forum.xda-developers.com/gen...g-3-xt1541-t3370101/post66640350#post66640350
Thread closed.

Noob in need of saviour - Z3 softbrick

Hi all,
Scoured the forum for a while but, to be honest, I didn't even know how to search for my issue. Please feel free to redirect me to another thread.
Two problems.
1.
Tried to flash Cyanogen to my Xperia Z3. Unlocked bootloader and tried to do something [enter technical word, flash maybe] a root img file. This soft bricked my phone, took it to a shop, they said it's dead, bought another one. Is this salvageable? More details: Followed instructions here, got to "fastboot reboot", (flashed a cyanogen nightly) then phone only made it to the Sony screen on startup. Then followed these instructions to flash moonwalker but the result was a soft brick (try to turn it on, one lifeless vibration and nothing). Didn't root it beforehand (yep, idiot). I've heard you could flash an older ROM, but this leads me to the problem below.
2.
New phone. Looking to root it. Using flashtool and an ftf (D6603_23.0.A.2.93) downloaded here, but when selecting firmware, the file ftf appears to be empty. I imagine flashtool has undergone cosmetic surgery (update) as it appears to be different than other pictures, or perhaps I'm missing something glaringly obvious?
If anybody with a bit of free time has a moment to help me out, I'd be very grateful. Many 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"
}
Not sure the image is working and not able to post external links. To explain it, the firmware appears (and is the correct model), but all other boxes (content, wipe etc.) are empty and the flash button is greyed out.

Sticky Recovery

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??

Categories

Resources