Hello Fellows
I have a PadFone X, T00D without access to recovery and cannot boot into home or safe mode. As a result, I'm currently unable to authorize ADB access.
I have researched for days and every solution either requires RECOVERY working or ADB authorized. If you know any other way to get this back to factory/stock, please point it my direction!
This brick has occured after I installed a custom bootload animation with an adjusted background color (which i'm sure is the reason for this softbrick) to make things slightly worse, the Recovery IMG may be corrupt.
Please advise!
:good:
Related
So upon trying to root and install a custom GPE rom, http://forum.xda-developers.com/showthread.php?t=2716306 to be exact, I had succeeded and successfully gotten the rom on, however from the get-go it was stuck in a bootloop on the 4 circles animation. after around 20 minutes of a laggy boot animation (I showered in wait.) I knew something went wrong. I am able to get into the recovery screen, but not into recovery. the device will not turn off (attempts will only lead to the phone powering up by itself and going back into the 4 circles) nor will it go into recovery mode. my computer is still able to pick it up via USB and adb. If I choose the fastboot option will tell me the device is connected when entering the remount command - however I am not able to browse my phone's files via windows. I also do not have a Micro-SD so the rom/root files are stored internally. I did make a Nandroid back up. I used this [http://theunlockr.com/2014/04/19/root-htc-one-m8-all-in-one-toolkit-method-video/ toolkit and tutorial for my rooting, and their adjacent S-Off tutorial to perform that action. This was my first ROM, and I have not flashed any kernels.
Is there any redemption for me, or have I unfortunately bricked my phone? Is there any possibility AT&T will take pity on me and charge me just a smaller-than-new fee for a replacement?
Please help..?
I apologize if this is in the wrong place, and I've really tried searching around, but nothing seems to work/ is tailored to the m8.
So, I just got an M8 new out of the box, rooted it and successfully installed cyanogenmod. Problem is, I was playing around with it, trying to get the GApp store and somehow (did what i think was) deleted my roms completely. Now upon booting up the phone I just get the "This build is for dev..." screen, and with the volume down+Power button to access recovery mode I constantly get put back to the fastboot screen. I tried flashing a custom recovery as in "Phone arena CWM flash recovery" guide, but no luck because my computer is reading the device as offline. I honestly have no idea what to do, and if anyone could help me I would be so greatful...
TL;DR: Stuck on boot screen, can't enter recovery mode, think i deleted all my roms, help please
On a scale of 1 - bricked, how bricked is my phone?
HUGE DEVELOPMENTS, GUYS! I've been able to access recovery mode again by re-flashing ClockWorkMod.
ctran1 said:
On a scale of 1 - bricked, how bricked is my phone?
Click to expand...
Click to collapse
On that scale, you are zero. If the screen comes on, you aren't bricked.
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.
Hi all.
I have an Asus TF103C that had been updated to lollipop that is currently (soft?) Bricked
I've been through pretty much all the threads and tried all of the fixes. Still unable to boot into android. I am unsure what step to take next. I cant apply official firmware updates via SD card nor sideload via ADB
Currently I can get it to boot up to a UEFI BIOS screen(where I can only scroll up and down via volume keys on the first page and nothing else.) or a fast boot screen showing firmware version ( 209.05 just incase its needed.) I can get it back to a droidboot screen, but I still cant flash any system img. If it's important this tablet uses an Intel Z3745.
Just a quick bump. Still only have access to the fastboot screen and recovery. I attempted flashing images again, and while it eventually goes through after breaking the image down into smaller parts, upon reboot I'm stuck at the android screen.
Open to any help what so ever.
It should also be noted that upon flashing via fastboot, after the system image goes through, I get the error " Flash Capsule Failed." And then it reboots to just the android screen.
Mine also bricked
Hi cronus2
Did you manage to solve this problems? I gather from your second post that you managed to get past uefi... I'm still stuck there: how did you do that?
Thanks to anyone who can give me some help here...
Bootloop,no way out: MT8735, 8", Android 5.1 (Archos 80b Helium), need general advice
Hello,
While trying to root my tablet (MT8735, 8", Android 5.1 (Archos 80b Helium)) I messed up, and trying to fix it made it probably worse. The device is stuck in a bootloop, but I can still get into the bootloader (I guess that's the right term) by powering up with Volume+ pressed after force power down (10s power button). I have the alternatives "Recovery Mode", "Normal Boot" - which result in a bootloop again if chosen - and "Fastboot Mode". Fastboot works, and I can connect the device with fastboot.
I'm afraid there's nothing else functional left on the tablet.
Unfortunately there is no stock rom and recovery available. All I have is an "update.zip" which contains a "boot.img", but no "recovery.img". So I tried to port a recovery image for a similar device (or rather deviceS so far) by replacing the kernel and some binaries from the boot.img.
Didn't help, still boot loop. Since I have bricked the device anyway, I decided to take the opportunity to learn more about these android devices (which in the end might help me getting the tablet running again), and here are my questions:
- Is the device able to boot into recovery mode if the recovery.img is ok, but there is nothing at all or nothing working in the "normal boot" section?
- Is there any way in the current situation to find out what is going wrong during the boot process? I can't connect with adb, so is there any way to get some logfiles or so with fastboot?
- As I understand the boot process, the bootloader initializes the memory and loads a kernel, either from the boot section or the recovery section. Am I right to assume that this part is still working on my device? Since I am able to get into the menu where I can chose between normal or recovery mode and fastboot, I don't think that the bootloader itself is broken.
- Assuming that this is right, is it possible to flash a minimal kernel and system into the recovery section, for example? Which does nothing else than show a message and then sits there and waits for power off? What I want to find out this way is whether the basic functionality (bootloader -> kernel -> initialize) is still there.
- If such a thing is possible, are there any suggestions to where to find such a minimal system? As said, I have a kernel for my device, can I build something around it to just give a sign of life?
Thank you for any hints and tips. Though it is annoying to have a bricked device, it is also exciting to be able to learn something new, if possible
Hello,
ummm, no offence meant, please, but isn't this here supposed to be a developers' forum? But still there is noone who can give me any advice about how to find the information I need and requested?
First of all I would need a minimal system - or a way to create one - which can be booted into as (fake) recovery, and which just gives any sign of life, like some message on the screen or an output through the interface, or even a text-line in some file, which I then could extract through fastboot. Or if not possible, I might find on the SD-Card, which I then could read on my PC.
Thanks and kind regards