Hello all,
Here's my situation; I have two rooted Razr M XT907s on Verizon. These are my kids' phones, and I haven't touched them in over a year. One was prompted for the OTA KitKat update, which was accepted (before I remember it was rooted). It appeared to be going well, then went into the recovery mode (Android on back with exclamation point over him). Now it continues to cycle through showing the red Moto logo for about 2 minutes, the black screen for 30 or so seconds, then the Moto logo again, then black screen, then Android on his back with exclamation point above him. It stays on the recovery screen for about 5 minutes then starts the cycle all over again.
I can get into the Recovery menu, and have tried to reinstall firmware from the SD card. The most recent attempt was the Blur_Version.98.18.94.XT907.Verizon.en.US (downloaded from link on XDA). This showed the most promise, but aborted after the Amazon Market app came back with "unexpected" contents. All other Recover menu items fail as well and return to the (failed) boot sequence I described above.
I have tried using RSD 6.1.5, but apparently it can't see the phone, plus the AP Fastboot menu/screen only responds by going into the boot loop regardless of what is selected.
I've updated the Motorola drivers, and can hear the phone connecting and disconnecting to my computer as it cycles the failed booting up. Interestingly, my computer is connecting to the phone only during the black screen segments; when the Moto logo or recover screen is displayed, the phone disconnects from my computer.
I'm no expert with this, but through XDA's forum's instructions over the years, I've been able to successfully root multiple Razrs and tablets, and Galaxy S4s, including updating them as newer firmware has been released (I've decided to stay away from the 4.4.2 update on my rooted S4 for now). However, for the life of me I can't figure out how to either return to the firmware this XT907 had yesterday, or plow through and update to the 4.4.2 update Verizon wants on the phone.... BTW, if I remember correctly this phone had debugging active before the OTA attempt.
Here's the info regarding the locked-up phone (taken from the identical rooted XT907, since I can no longer get into this phone):
{
"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"
}
Any help is much appreciated; this phone is about 18 months old, so warranty is out of the question...
DISREGARD...
I was able to get into AP Fastmode (finally) and able to flash the VRZ_XT907_9.8.1Q-94-1_CFC xml file via RSD Lite (after removing the "getvar" line). The phone was restored to it's factory state with Android 4.1.2 with System Version 98.30.1.XT907.Verizon.en.US (unrooted) installed.
The best part of this exercise is that anyone that had a rooted Razr M XT907 (with Verizon) and mistakenly attempted the recent OTA to 4.4.2 which resulted in a frozen or boot loop, now fully knows there is a safe way out of the mess...
Related
I have a rooted LG G2 running Kit Kat 4.4.2 that will no longer turn on past the LG logo screen or enter TWRP recovery.
I had been rejecting the OTA update for Lollipop that came up yesterday, but it came up again when I was doing something and it started to install. I panicked and powered the phone off, then the next time I turned it back on, it was in TWRP recovery.
I tried a few things like restoring to the backup made when initially rooted, the factory wipe that it says "most of the time, this is the only wipe you need," etc. I also tried entering "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota" at the terminal.
Everything either sent my phone right back into the TWRP recovery screen, or, like it is now, it will only go to the LG logo screen and doesn't want to turn off. Holding the power with either the volume down or up buttons turns it off for a second and it goes right back to the LG logo.
Is there anything I can do to get this phone working in any capacity? I'm honestly not super familiar with rooting things (have never flashed a custom rom, done backup/restoring). So any detailed help or ideas in simple, newbie terms would really help.
Any help is extremely appreciated, I really loved this phone and the little modifications from things like G2 Tweaksbox and Gravitybox really put it above and beyond for me.. really hope it can get back into action.
Thanks.
I am in the same boat and have been scouring the forum looking for a fix. It appears that it is stuck in download mode when all you see is the LG logo screen. I can get to TWRP but it will not install and roms or .zip.
This is the link to flashing it to stock:
http://forum.xda-developers.com/showthread.php?t=2432476
It does not work for me, but it may work for you. If anyone has any suggestions to get past this error:
{
"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"
}
Please let me know.
I've probably used the LG Flash Tool 10 times the past week on both my home and work computer with no problems. Last night I flashed the KK bootloader and a stock 5.0.2 ROM (after tot'ing back to 4.4.2, rooting, etc).
It hangs at the LG logo and that's where I'm stuck. I tried going into Download Mode, but suddenly both of my computers won't see the phone and give me an error in Device Manager. I've tried uninstalling / reinstalling the drivers as well. Why in the world would that happen unless somehow Download Mode was corrupted, possibly? But it goes into Download Mode fine, and appears to look right...
I've tried getting into recovery but can't. When it should load up TWRP (after telling the G2's "stock" recovery screen I do want to reset), I get the green spinning Android (not the red exclamation) for a second, then it tries to boot up.
{
"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"
}
Any advice would be appreciated as I've never run into this before.
So when the green Android popped up, I tried to hit a combination of the volume and power keys and WAS able to get into recovery. Unfortunately, it appears, somehow, TWRP was overwritten by the stock recovery. I have no idea how that could've happened. Or does stock recovery technically stay in place since this is "loki'd" and not actually unlocked? And if so, is there some way to get back to TWRP that I'm unaware of?
To add to the weirdness, when I plug it in to charge, it doesn't pull up the battery like it usually does when powered off, it just tries to boot up again...
If I could just get the computers to recognize it again...
Installing the LG PC Suite got my drivers to a point where it could recognize it while in Download Mode. MTP still didn't work, but that didn't matter for Download Mode. Not sure what happened, but at least I was able to flash it back again.
Hi
I managed to screw up by flashing a Nougat-to-Marshmallow downgrade (1st of two) update.app whilst still on Marshmallow.
M3 now shows Huawei logo in a loop.
Entered fastboot & rescue mode using Vol-/Power, and saw AP_S_ABNORMAL.
HiSuite system recovery procedure led to "Your device is not supported for system recovery".
Since my M3 bootloader is locked, I guess there is nothing more that can be done.
Still, if an experienced user has any angle, it would be most welcome!
Thanks in advance.
sam10000 said:
Hi
I managed to screw up by flashing a Nougat-to-Marshmallow downgrade (1st of two) update.app whilst still on Marshmallow.
M3 now shows Huawei logo in a loop.
Entered fastboot & rescue mode using Vol-/Power, and saw AP_S_ABNORMAL.
HiSuite system recovery procedure led to "Your device is not supported for system recovery".
Since my M3 bootloader is locked, I guess there is nothing more that can be done.
Still, if an experienced user has any angle, it would be most welcome!
Thanks in advance.
Click to expand...
Click to collapse
I have the same issue. My wife dropped her phone in some water so i disassembled the phone. It was also trying to upgrade the firmware as i was taking it apart but i pulled the battery from the device (I panicked). So i have got everything working again. but i can't boot into the device. It only displays the time after startup. I have tried factory resetting, dowloading firmware and putting it on the sdcard in the dload folder but, alas, so far no luck getting it going. I also entered the fastboot & rescue mode using Vol-/Power, and saw AP_S_ABNORMAL message. In addition to that it also said PHONE_LOCK and FRP_LOCK.
{
"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's a pretty delicate device. I bricked mine with an unlocked bootloader. There's no low level chipset utilities like there is for the qualcomm chips. I'm so stupid I got the M5; won't be piddling with this one. If someone normal would only make a decent LTE TAB I'd gladly run screaming from huawei.
Try the "dload" method. Create a "dload" folder on the sdcard and put the second "update.app" into it. Now boot into recovery by shutting the device off and starting it with all 3 hardware buttons pressed.
Calibaan said:
Try the "dload" method. Create a "dload" folder on the sdcard and put the second "update.app" into it. Now boot into recovery by shutting the device off and starting it with all 3 hardware buttons pressed.
Click to expand...
Click to collapse
I did this but it says update failed.
Hi everyone. While I was attempting to root my tablet I ran in to a problem. It turned out since I had updated to 8.1 it had an RMM state that's prenormal, which makes it impossible to root. I found a guide to use Miracle Box to downgrade it to 7.1 where I'd be able to root. However in this process when I saw Miracle Box was done I decided to unplug the tablet. Well it turns out the tablet was still loading it, so unplugging it caused an error. Now whenever it boots up I'm stuck on the error screen which says to use the emergency recovery mode on smart switch. Well, smart switch won't find my device. Neither will kies. I've tried downloading 2 different stock roms for my exact device and using odin to install them, but I get an error on odin and it fails. I have tried two different versions of odin too, 3.12 and 3.13.
{
"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"
}
Here's the log and error I'm getting.
Here's my tablet screen.
I have no idea what else to do here to get my device back in usable state. Please help!
Smasher39 said:
Hi everyone. While I was attempting to root my tablet I ran in to a problem. It turned out since I had updated to 8.1 it had an RMM state that's prenormal, which makes it impossible to root. I found a guide to use Miracle Box to downgrade it to 7.1 where I'd be able to root. However in this process when I saw Miracle Box was done I decided to unplug the tablet. Well it turns out the tablet was still loading it, so unplugging it caused an error. Now whenever it boots up I'm stuck on the error screen which says to use the emergency recovery mode on smart switch. Well, smart switch won't find my device. Neither will kies. I've tried downloading 2 different stock roms for my exact device and using odin to install them, but I get an error on odin and it fails. I have tried two different versions of odin too, 3.12 and 3.13.
Here's the log and error I'm getting.
Here's my tablet screen.
I have no idea what else to do here to get my device back in usable state. Please help!
Click to expand...
Click to collapse
What error are you getting? There is no picture of your tablet or the error. Also did you try patched Odin? If SmartSwitch won't recognize it do you have the samsung USB drivers installed from here? https://developer.samsung.com/mobile/android-usb-driver.html
Howdy everyone...
OnePlus 7t Pro McLaren edition (International Edition **NOT T-MOBILE**)
Model: HD1913
Current Software Build: Oxygen OS 10.0.5.HD01AA (OTA update when I first unboxed).
I am having issues trying to return to stock. I rooted the phone with a combination of a couple guides found here (https://forum.xda-developers.com/7t-pro/how-to/10-0-3-patched-boot-image-oneplus-7t-pro-t3986351 and . I noticed after doing that I was missing the stock Oxygen apps and my build information was missing data. Not a huge deal, but I need to wipe the phone and start from scratch anyway, for other reasons. I decided to go back to stock if I have to redo everything anywhere.
First thing I tried, I got the stock firmwares (https://forum.xda-developers.com/7t-pro/how-to/oneplus-7t-pro-repo-oxygen-os-builds-t4003455). And this is where my issues started. My software build is weird... I have the HD1913, however my software build is HD01AA. Per that post, I should have HD01BA. I grabbed both of them for giggles, put them on my storage and booted into TWRP. Tried to flash the HD01AA (since that was what I have now), and it failed. Tried the other one, same issue. I'm getting a bunch of errors while trying to mount the system ("System unable to mount: invalid argument").
Second thing I tried, was to use the built in software update that OnePlus says to use (through the system update). It wouldn't install them (surprise).
Third attempt... Using the MsmDownloadTool (https://forum.xda-developers.com/7t-pro/how-to/op7tpro-unbrick-tool-to-restore-device-t4002909) I downloaded both versions cause I don't know which to use, and followed the instructions to get the phone into the mode. Turn the phone off, hold the vol up button and plug the cable in (very simple). It shows up connected in the software. Exactly 5 seconds later, the phone reboots and boots normally... I repeat this process aprox. 2.3 million more times. It does not matter what USB-C cable I use, the port on my computer, or how long I hold the buttons. The phone will boot into the download mode (or whatever it's called) show up as connected in MsmDownload and then reboot.
The phone works. I am still able to boot it up.... All I want to do is get this phone back to stock. I don't HAVE to, but now that it's fighting me, I have to beat it...
imgur.com/a/KhBGwao
{
"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"
}
Okay - After sacrificing an iPhone to the Android God, I got it.
Instead of using the button combination to get into EDL Mode, I found an article that gave an adb command (adb reboot edl) to get to it. It did not reboot this time, and I was able to flash HD01BA to it, which matches what the phone should have...