I have a Sero 7 Pro that has sero7pro-bld60220-dopa-v2.0 installed. It has been working fine for months until last night when I picked it up and it was powered off. It was plugged in to my PC usb port like I usually keep it so the battery should have been fully charged and I don't know why it powered itself off. Now it won't boot up. It sticks on the bootanimation screen. I tried to get into Fastboot using the volume/power button but it just hangs on the Fastboot screen and never goes any further. I am able to get into Recovery and have tried various options from just clearing cache and data to restoring the original OS using sideload and Adb on my PC. Nothing allows me to boot beyond the bootanimation. I have also tried to replace the bootanimation.zip file in the /system/media folder but it continues to try to boot with the same animation file. Is this somehow related or am I replacing the file in the wrong folder? Any ideas what might be wrong? How do I retrieve a log file to help diagnose the problem?
I attempted return to totally stock using XE-Sero7Pro-factory-4.2.1-stock_v2. I booted to Recovery and used adb sideload to install. No errors were reported during the wipe, format and install, but nothing actually got changed. Any ideas?
Related
I was trying to get my phone to make a nandroid backup, but for some reason it wouldn't let me. I searched on these forums and found a viable solution which was to download the update.zip and a new recovery file. I placed the update.zip into the folder called /external_sd, and then i put the recovery file into the SYSTEM/BIN folder. However, while using root browser lite, it said that the operation was unsuccessful, but there was a recovery file there. I then went into Rom Manager to see if it worked because there was a recovery file in there. When it booted up, the phone gets stuck at the lock screen. I really need urgent help. Even if I try to boot into recovery I don't think it works. I turn it off by holding the power button, but the phone turns on even if it moves. Anybody that can help, please help.
Edit: Nevermind, I got the phone working by removing the battery, then plugging it into the computer. I then plugged the battery back in, and the green charging bar showed up. Successfully booted and fixed using updated recovery file. Any mods can delete this.
I was trying to flash a ROM (not sure exactly which one - I did this like a month or two ago) but I did something wrong and the phone is now in a boot loop. It gets to HTC logo and reboots constantly. When I try booting into recovery, it show CWM on the screen for a split second and then reboots (back into the bootloop). I am, however, able to get into fastboot. It says "tampered" and "unlocked" at the top. It's hboot version 1.44. When I select the factory reset or recovery option, it goes back into the bootloop.
I have read several posts about connecting it to a computer and using adb to reset it while in fastboot but I can't do that. Whenever I connect it to a computer, the phone does not get recognized on the computer whatsoever. When I plug it in, it starts charging but nothing happens on the computer. I have tried installing the drivers on multiple PCs (both Windows 7 and 8) and I have tried using several different USB cables. This was the case long before it was stuck in the boot loop too so it's not a new issue. It just doesn't get recognized on a computer. I've tried going into device manager and everything, nothing shows up. Is there any way I can fix this issue since I seemingly can't use adb?
Thanks in advance for any help!
okay so here it is: (1) I changed a market sms app to a system file and changed to hw message app to user app
(2) Battery ran out this evening and I plugged phone up to charge
(3) Went to use phone, showed 93%, powered on while still plugged in, screen acted finnicky
(was using a different charge cable)
(4) Attempted to change system font with a market app and rebooted, screen froze, hard rebooted
(5) Tried several times to reboot, no go, finally resorted to booting to recovery and doing factory reset (successful)
(6) Even after factory reset phone won't boot. Does splash logo then goes black screen.
(7) Power button causes vibrate when touched, but screen doesn't come back on
(8) I can boot to fastboot or recovery but I'm not sure what else to try. I welcome any suggestions.
I'm freaking out.
Thanks to @xordos and @Modding.MyMind I'm back to enjoying the best device I've ever owned.
If anyone else runs into similar soft brick issues please see the thread xordos started to solve.
does anybody have the factory image from the HAM2 that I could try to flash from my SD card in recovery?
Help may be on the way tonight as TWRP might be released! If you can adb access these files might help:
P.S., regarding the System partition, I do have a system file uploaded, it is taken after it is rooted, it is file level zip, not dd image:
https://drive.google.com/file/d/0B-n...it?usp=
These were provided XORDOS who is helping with the TWRP project,
this was from this thread post 105 if the above link didn't work!
http://forum.xda-developers.com/asc...st-cwm-twrp-customer-recovery-t2868933/page11
Did you get this fixed? I have the same problem
good_apollo said:
Did you get this fixed? I have the same problem
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=55647061
I bought this tablet exactly a year ago, never modified or rooted it, and suddenly a lot of apps started having issues. Went to reinsall a few of them then suddenly the whole OS froze.
Rebooted and the Dopo splash would show, then the android logo showing movement like it is trying to boot but gets stuck there.
Tried going into recovery by holding the power and volume button, that *worked* but when selecting factory reset then it crashed again.
So I repeated the process and now it won't even boot into recovery using the power and volume button!
Tried running the battery dead and restarting, tried using the reset button pinhole. Nothing worked.
I installed adb and fastboot (I use linux) and went through most of the simpler procedures.
adb connects and I can run its shell and view my files that are on the tablets. Ran the command to see its debugging output and noticed that the boot loop was because the filesystem turned everything except userspace to read-only!
Now here is what is real odd.. when I try pushing a file onto the tablet using adb, it instantly becomes corrupted when reading it back.
Like if I make a simple text file called hello.txt with some text in it saying "Hi there!", when I push that file onto the tablet, then read its contents it is gibberish.
This leads me to believe the whole filesystem somehow became corrupted and can no longer write files properly.
There doesn't seem to be a way to run fsck or anything alike and I can not put any files on the tablet because they instantly become garbled.
No use in running fastboot when the tablet no longer can go into the recovery screen either by vol+power pressing or by adb reboot recovery. Both simply just try to boot the tablet normally now, unlike the first time I tried
Assuming I have the factory .img file is there any way I can fix this?
Or does this sound like the hardware got damaged?
I fear the worst at this point.
Hey guys,
So really in need of a little help. My OnePlus X started acting strange when it refused to take charge when it was booted into OS (Lineage). However, I noticed that if the phone was off, it would boot immediately upon connecting a cable. So it seemed as if nothing was wrong with the port or the cable (tried various cables and chargers). A little more digging revealed that the phone charges in Fastboot mode. Anyway, I decided to factory reset it and for some reason it was stuck in a boot loop.
I then tried to restore back to stock using Mega Unbrick Guide which worked in the past. Now my problem is that its stuck in fastboot, wont boot into the OS. I can boot to the recovery and fastboot. In recovery when I choose Install from local, i get no browser to search the SD for zip files, nor does the phone detect for me to use adb sideload.
Any ideas as to why this is so?
Thanks!