Hey all,
First a massive thank you to the XDA people out there! You guys have done some amazing work and I am humbled by your level of awesomeness!
I'm working on a friends XT1254 who's phone started coming up with an endless loop of "Unfortunately, System UI has stopped." I can never get into the OS as the error message repeatedly opens up immediately after tapping OK. We're not concerned with salvaging the phone, but his contacts and photos (and potentially other data) are my only concern and what I'm working on retrieving.
Bootloader is locked. Phone is on the latest version.
Stuff I've tried;
- RSD Lite. Cannot recognize the phone regardless of everything I've tried. (original cable, different cables, drivers, different computers, different OS's)
- Recovery -> Format cache. (Completed successfully, but same system ui has stopped comes up)
- Fastboot & ADB sideload. (I can get the device recognized but have been unsuccessful at flashing anything)
- Verizon Motorola Software Assistant (This does reload the firmware successfully, but doesn't fix anything)
I feel confident in that I know how to get the phone back to working condition by using Recovery to wipe all user data and reset to factory, then I could do some magic and get the bootloader unlocked and go from there... but that's not the goal. The goal is just to get all data off first. I've looked into adb push/pull but since I can only access adb sideload, those commands do not work.
The closest I've gotten to ever seeing a filesystem is in Recovery -> "Apply update from sd card".
I've read some users were able to access the filesystem when in fastboot or recovery. The device is recognized under fastboot, but no filesystem displays for me (tried multiple systems including a linux system). In recovery, the phone is not recognized by my computers until I enter adb sideload.
I might be out of options here... but since y'all are extraordinarily smart, I thought I'd reach out and see if anyone had suggestions of how I can get the data off or maybe fix the system ui has stopped error.
Thank you!
Related
I'm having problems connecting to my phone through ADB. I've flashed back and forth between 4.1.2 and 4.2.2 roms multiple times and had no problems with wiping everything (to ensure the proper file structure etc.) and then sideloading a zip to flash. However this time, I rebooted into recovery (TWRP 2.6.3.0), wiped everything (factory reset, then wiped data, then advanced wipe with the first 5 selected) and when I went to ADB sideload my new rom, I couldn't connect to my phone. I've followed multiple guides that attempt to establish a connection between the phone and Windows 7. I've installed multiple people's "updated USB drivers that fix the problem," but no go. While in recovery, the phone shows up in my device manager under "Other Devices > M7WLS" with the '!' icon under it. While in fastboot it connects under "Android Devices > My HTC" but no ADB commands will work here. And everything is already wiped so I currently can't use my phone until I get this fixed. Any help is greatly appreciated!! Fastboot will connect though so if I have to RUU, I can.
Solved!
If anyone else is having this problem, flash recovery back to TWRP 2.5.0.0 and then you will be able to connect to ADB through recovery. Hope this helps!
hamiltoes said:
I'm having problems connecting to my phone through ADB. I've flashed back and forth between 4.1.2 and 4.2.2 roms multiple times and had no problems with wiping everything (to ensure the proper file structure etc.) and then sideloading a zip to flash. However this time, I rebooted into recovery (TWRP 2.6.3.0), wiped everything (factory reset, then wiped data, then advanced wipe with the first 5 selected) and when I went to ADB sideload my new rom, I couldn't connect to my phone. I've followed multiple guides that attempt to establish a connection between the phone and Windows 7. I've installed multiple people's "updated USB drivers that fix the problem," but no go. While in recovery, the phone shows up in my device manager under "Other Devices > M7WLS" with the '!' icon under it. While in fastboot it connects under "Android Devices > My HTC" but no ADB commands will work here. And everything is already wiped so I currently can't use my phone until I get this fixed. Any help is greatly appreciated!! Fastboot will connect though so if I have to RUU, I can.
Click to expand...
Click to collapse
Use this
http://forum.xda-developers.com/showthread.php?t=2386956
Delete every other driver including HTC sync and set those as your drivers.
Do this by going to control panel, then to device management. Find your HTC and update drivers then find the folder you downloaded, and set it to that.
Sent from my HTCONE using XDA Premium 4 mobile app
twrp 2.5.0.0 unresponsive to touch
hamiltoes said:
If anyone else is having this problem, flash recovery back to TWRP 2.5.0.0 and then you will be able to connect to ADB through recovery. Hope this helps!
Click to expand...
Click to collapse
so i was having this same problem. i flashed 2.5 like you suggested, and it did read the adb, but now the recovery is unresponsive to touch... so close this time. any suggestions?
I had android GE 4.3 on it, rooted.
I have the original GE bootloader (that robot) installed.
I downloaded the official 4.4 update through android, rebooted for install.
Now after the install the phone does not boot up anymore, instead it goes into RECOVERY and shows that triangle robot.
I tried wipe of cache and data wipe.
Whatever i try I am not able to get this device into fastboot / bootloader anymore!
It takes longer than usual,, it is stuck in that HTC screen since I have unlocked the bootloader but it does not enter the usual menu.
Instead it just directly goes to the robot.
I tried about everything I could think about,
It seems the OTA really bricked my phone by damaging the bootloader so it does not load at all anymore.?!?!
The only USB accessible feature I see is that in the robot screen it registers a device through USB.
Sadly not ADB or fastboot, it is a volume. It even loads as volume but is inaccessible (like a CD without disk)
Windows recognizes it as WDP FileSystem.
I doubt this will help at all, just wanted to note it.
I am about to throw the phone into trash, if it had not been so expensive.. Anything that can be done to repair this brick ?
Lirezh said:
I had android GE 4.3 on it, rooted.
I have the original GE bootloader (that robot) installed.
I downloaded the official 4.4 update through android, rebooted for install.
Now after the install the phone does not boot up anymore, instead it goes into RECOVERY and shows that triangle robot.
I tried wipe of cache and data wipe.
Whatever i try I am not able to get this device into fastboot / bootloader anymore!
It takes longer than usual,, it is stuck in that HTC screen since I have unlocked the bootloader but it does not enter the usual menu.
Instead it just directly goes to the robot.
I tried about everything I could think about,
It seems the OTA really bricked my phone by damaging the bootloader so it does not load at all anymore.?!?!
The only USB accessible feature I see is that in the robot screen it registers a device through USB.
Sadly not ADB or fastboot, it is a volume. It even loads as volume but is inaccessible (like a CD without disk)
Windows recognizes it as WDP FileSystem.
I doubt this will help at all, just wanted to note it.
I am about to throw the phone into trash, if it had not been so expensive.. Anything that can be done to repair this brick ?
Click to expand...
Click to collapse
Now search for the right adb and fastboot driver. There is a .msi installer (adb + fastboot .msi) something like that. Than push the right recovery via fastboot. Voila
Alfa Kenny One said:
Now search for the right adb and fastboot driver. There is a .msi installer (adb + fastboot .msi) something like that. Than push the right recovery via fastboot. Voila
Click to expand...
Click to collapse
Hi,
I solved it.
It took about 30-50 reboots until the phone entered the fastboot menu.
The problem was that the phone kept skipping the whole fastboot menu and went into recovery instead.
A very strange firmware bug caused by the failed OTA
Yep, probably again a noob that bricked his phone.
As there was no info on my phone that wasn't on google servers or something I was so stupid to start installing the latest official CM12 built on my XT1068 without any decent backups.
- I think the moto/google service for lost devices encrypted my phone without me really noticing it. :crying:
- I was on Lollipop, the latest update I got here from in Benelux/Europe.
- I unlocked my device, worked fine. device also tells in bootloader
"Device is UNLOCKED. Status Code: 3"
- when than having installed TWRP 2.8.0.1, os started but gave problems installing superSU.
(no prob I thought, I go immediately forward with CM12 installation, so don't have to bother with the old ROM) :silly:
- wiping everything for clean install I already saw some messages coming up. on hindsight; Difficulties with opening /data folder etc...
- tried to install CM, and several other more stock roms, but never get through the message. All bad installs.
- maximum I got is CM12 booting up, preparing some apps and than a message describing the encryption problem, asking to reboot.
TRIED:
- install from usb drive (with OTG cable)
- erase and reinstall from TWRP 2.8.0.1 and other recoveries.
- fastboot flash a standard recovery again, to wipe data from there,
(from this standard recovery installers never got through even the verification to install, so tried than installing from other recoveries, same problem.)
Can still try but hesistant:
Unlock my mothers phone (same month, same model, same place, probably same encrypted) to try backup there in TWRP, recover this on my phone, and this way flash standard rom again. From there I could probably get rid of encryption. (as found already in several places)
I would afterward immediately try to lock my mothers phone again, don't know so much of how to get recovery to standard one again though. Can I backup this before. When I try now "adb backup - all" on my phone from my mac, I get "unable to connect for backup" message though. Even when phone is saying "phone connected".
Anyone an idea of how to get out this trouble?
Greetings
Otto
[email protected]: try "fastboot erase userdata"
have the feeling I'm getting there. Gapps still don't work but rom boots. Recovery has to be standard one to make encryption to work. Thats the key.
I flashed android m preview last night. i needed root so i flashed it and that flash failed, which seems to have corrupted the rom. Im hoping i can get my nexus back but im having some issues.
Recovery- i didnt flash twrp, its stock android m recovery
factory reset- all this does is erase and my rom still is corrupted
fastboot- computer reads it, i can see it in device manager as "android bootloader interface, however adb wont read. no devices in adb devices
ive uninstalled and reinstalled the google drivers several times to no avail. ive tried it on a different pc and same no dice.
ideas?
adb commands will not work in fastboot mode.
read this. it shall set you free
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
ingnore relock bootloader part!!
1. Boot into bootloader 2. fastboot flash system [system.img from preview 3 rom] 3. Wipe caches 4. Reboot
I admit i was trying to use adb to see if the phone was connected... bad habit i guess. The connect to adb in recovery option was not working at all. I blame this all on the MM bootloader. I have a bad taste in my mouth. In the end wugs saved me. I guess that day i needed the process simplified. Sorry for late response.
Anyway, phones fixed, this matter is complete. Both you folks are amazing. Im sending virtual hugs to all.
Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day
I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll