Hi all. I did try to find an answer before posting, guess I just didn't find what I was looking for
A few years ago I rooted my Dell Venu 8 tablet. It ran fine, I stopped using it for a long time and it just sat. A couple months ago I charged it up and booted into it. I booted up, but was VERY slow to respond to anything. I let it sit again for several months. This time however, it won't boot up.
When I try to do a factory restore by holding down the power button and volume down button, it will put me in the factory restore option. I use the volume keys to change the boot option to RECOVERY MODE. When the recovery boot screen is up, I see this list of things showing at the bottom of the screen.
FASTBOOT MODE
PRODCUTE _NAME - BB
VARIAT - Venu 8 7840
HW_VERSION - Unknown
BOOTLOADER VERSION - Unknown
IFWI VERSION - 0004.FD1F
SERIAL NUMBER - ….
SIGNING - unknown
SECURE_BOOT - unknown
DEVICE STATE - locked
FASTBOOT CMD WAITING
I hit the power button to tell it to start the process of restoring. It reboots shows a little android with it's chest cover open with a little red warning triangle. It sits there for a while doing nothing visible on the screen, then after a few minutes, reboots, tries to load, and then just hangs again where it always hangs.
At this point I really don't know if my device is hanging because of the rooting software or possible hardware issue. Also, not sure if the restore is really restoring it or not because of the DEVICE STATE - locked message .
Any help will be greatly appreciated!!!
Thanks
Rick
Related
Thanks in advance for reading this and for any suggestions you might have!
I have a Archos Home Connect 35 Gen 8 device. I had it rooted on 2.4.82 firmware just fine. I wanted to update to 2.8.83 to get rid of the update notification I kept getting. I wanted to do it from a fresh clean slate as I wanted to reset my device anyway. First I used the Recovery Menu (White Menu) to restore back to default, then removed the SDE menu via the option to remove it in the SDE menu.
I then followed the guide that chrulri posted that I followed last time, but with 2.8.83 files. http://forum.xda-developers.com/showthread.php?t=930197 (Note for Archos 35's you have to hold the power button for ~6 seconds, then double tap it to get to recovery instead of holding Volume Down like on other Gen8's). I was doing this on my MacBook Air at the time. (I rooted it before from my Windows PC). I went to 'Update Firmware" on the recovery menu, then took the SDE firmware file, and copied it over USB to the drive and safely removed the drive, then hit "OK" on the device. It proceeded to do the update it seems but only took 2-3 seconds so I'm fairly sure something didn't go right as it usually takes longer. It then said press ok to Reboot so I did.
After the reboot from that, the device turns on but I get a White screen. No Archos logo or anything. Usually this white screen comes on for a few seconds, then I would get the Archos Logo even if I was booting recovery. No luck. I tried resetting the device by holding power button for 20 seconds, waiting 10 seconds and turning it on, same issue. Recovery will not work either, I tried two dozen times to try and get it to load by doing the usual ~6 seconds holding power button then double tapping and no luck.
I tried hooking the device up USB and in Windows all I get "Unknown Device" in device manager, with DeviceId of USB\Unknown. I attempted to force both Archos' ADB driver and the Universal ADB drive onto it with no success. (I'm pretty sure its my device since normally when a device shows up and its capable of ADB you will get a difference device ID in Device manager like USB\ADBDEV1 or something. On my Mac, when I plug it in, all USB devices (Multitouch pad mouse included) will lock up for ~5 seconds, then in dmesg I can see it has a error on USB device and it disabled the device.
So something weird is going on with my Home Connect for sure. Any suggestions on what to try? I'm thinking somehow the filesystem or firmware on it got screwed up during the SDE flash and it can't boot anything even the recovery now. I have a MicroSD card I can use if there's some recovery feature built into it to get it to boot from the MicroSD slot or something to do a firmware recovery.
My only other option if there is no way to try and get it back would be to try and send it back to Archos for repair simply stating it was updating firmware and this happened. (No actual modified firmware is on it now as well, and i was flashing the Archos approved SDE firmware, so they should be okay with it).
Also the battery was fully charged when doing this. It seems different that the White Screen bug the Archos 101 and others get when the battery accidentally runs too low with older firmware.
Thank you again for your replied!
If you can't get into recovery anymore, then it is over. I would suggest to RMA the device.
divx118
From all my searches through Archos forums and here that seems right.
I'm shocked there's no failsafe recovery mode for Archos. My Asus Transformer TF101 had one, where even if the firmware was screwed and you couldn't get to recovery, a special key combo would boot it up and you'd load some special recovery driver for it (Not adb something with nVidia in it, has to do with Tegra2 chipset i suppose) and upload the firmware to it and it recovered. Even iPhone's have DFU fallback mode as well for when things are totally forked and iTunes will restore the firmware.
Just an update. I did RMA the unit and Archos sent me a brand new boxed up one back. (I have an extra charger and cable now since they said not to include them ). Have my new 35 setup rooted with .83 now.
I think I figured out what happened. After I installed the SDE, before I flashed the new kernel and such, if I booted the Developer Edition option from recovery, it would get stuck at a blank white screen until I power cycled. On my old 35 I had removed the option to boot regular so it booted the Developer Edition that was rooted every time. I think when I restored the original firmware, it of course removes the Developer Edition kernel I had flashed before, but it somehow didn't set the menu back and was trying to boot Developer Edition every time, which it lacked the kernel for, and went to the white screen. Not sure if it explains recovery not working though.
To make sure it doesn't happen again i've left the options all in tact and left it so I manually have to go to recovery if I reboot the system to boot the developer kernel for root. Since the device goes weeks and months without the need to reboot since it's just an Alarm Clock really that's fine with me.
How the problem occurred
So a year or two ago I bought a Jiayu G4A/T/Whatever they're calling it and safely got it here. I've used the stock ROM for a bit but I wanted to get rid of the bloatware that was still on it, so I eventually ended up with a properly rooted phone with a ROM from Jiayu.es (Everything worked, have ClockworkMod as recovery, accessible via Mobileuncle Tools), which was essentially a stock Kitkat rom made to work for the phone. Now I got sick of the ROM and recently saw the new EMUI version on Huawei's P8 Lite, so I figured I'd look around for a tailored ROM running that, and ended up at "jiayu-emui-3-0-stable" from Needrom.
What I did
1. I downloaded a ROM from Needrom with identifier "jiayu-emui-3-0-stable" (I can't post external links)
2. Backed up my important files following a guide from androidcentral titled "[Guide] How to Backup and Restore Apps and Data when installing new ROMs" that I can't link,and did a full backup using CWM
3. Placed the ZIP on my internal SD card, went into recovery, wiped data/cache (not dalvik, since it wasn't described in the instructions, I think this might be a probable cause) and installed the new ROM from ZIP
4. Rebooted the phone and now it's stuck in the boot loop I mentioned.
What the problem is
Bootloops aren't that much of a problem usually, except this one is... I can't get into recovery mode. From there on it'd be cake, since I made the right preparations, but I can't get into it. While connected to my PC it keeps powering on, showing a splash screen from Jiayu.es briefly (which shouldn't be present anymore) and powering off after 10 seconds, only to come back to the splash screen.
What I've tried
I've unplugged it, removed the battery, waited to get a full power cycle and tried to hold my buttons in these combinations: [power button + volume up], [power button + volume down] - but neither work. It just keeps going with the boot loop. I can succesfully power it down, and when I plug it in from there it shows the low battery image. At the moment of seeing that I thought I could connect to it using ADB / Fastboot, but no luck there either. It keeps saying no devices found, and with fastboot it keeps on <waiting for device>.
My questions
What exactly can I do if there is no way for me to get into recovery mode? Are there any alternatives? How can I get my device to be recognized by ADB? Is that even possible? Why is this bootloop any different from others?
Update from the massive Q&A thread:
ZipAddict said:
Is it booting up on its own too after being off? This happened to wifes phone and it turned out the power button was stuck. I took a pencil and hit the power button with the eraser a few times and it worked then. Her case mustve dislogded it. I will keep my fingers crossed for u. If not send me a private message and i will look for an answer tomorrow and get back with u
Click to expand...
Click to collapse
Thank you for the reply!
Yes, it does. I took the battery out and let it lay disassembled for a night, after which I cleaned it a little and re-inserted the battery. With the case back on, nothing happened, so the power button wasn't stuck for sure. When I powered it back on with the power button (no USB attached) it showed the emblem for ~8 seconds and powered off. It then buzzes to show it's powered on again and up comes the splash screen again. Could it be that the ROM was just a rebooting falsehood? Why would it disallow me getting into recovery mode? I really hope there is something that can still force the device into recovery mode / interact with it somehow while in this state.
Oh, I also tried to see if the volume down button was broken but all the contacts seem intact, plus, they worked an hour before I started switching roms.
Hi there,
I've tried everything and my phone is not responding,
A while ago (2 months) I unlocked the bootloader (right term?) and installed Android M Preview and over the following weeks updated to Preview 2.
However, last night I tried to root it using some software via my laptop and it ended up 'corrupting' my phone, that is if I try to power on my phone it loads up the Google start up screen with the unlocked padlock at the bottom of the screen and goes black and tries again, and then the screen changes to 'Your device is corrupt. It cannot be trusted and may not work properly' it then has a link to a page which suggests using a factory reset. However, I have reset my phone countless times, after selecting 'recovery mode' in the bootloader it takes me to a 'dead green man(?)' and says no command when I'm connected to my laptop, after that I held the power button and pressed volume up which led me to menu with the 'reboot system now' and 'reboot to bootloader' etc. along with the option to 'wipe data/factory reset and 'wipe cache partition', I have tried both of these and tried booting the device with no luck, the screen does the same as before ^^.
I have downloaded ADB, CF-Auto-Root-shamu-shamu-nexus6, WugFreshDevelopment (NRT_v2.0.5.sfx) (I think it was after I used this that it all went wrong), Elite_Shamu_LP-06_17_2015, UPDATE-SuperSU-v2.37.
I'm sure if any of that is helpful or not though.
Any questions about my current situation I'd be happy to answer, I'm really stuck! I just want to go back to stock Android and wait for the real Android M release!
I realise now that I'm a total noob and shouldn't have been messing around without knowing what I was doing.
Thanks in advance.
joespencer98 said:
Hi there,
I've tried everything and my phone is not responding,
A while ago (2 months) I unlocked the bootloader (right term?) and installed Android M Preview and over the following weeks updated to Preview 2.
However, last night I tried to root it using some software via my laptop and it ended up 'corrupting' my phone, that is if I try to power on my phone it loads up the Google start up screen with the unlocked padlock at the bottom of the screen and goes black and tries again, and then the screen changes to 'Your device is corrupt. It cannot be trusted and may not work properly' it then has a link to a page which suggests using a factory reset. However, I have reset my phone countless times, after selecting 'recovery mode' in the bootloader it takes me to a 'dead green man(?)' and says no command when I'm connected to my laptop, after that I held the power button and pressed volume up which led me to menu with the 'reboot system now' and 'reboot to bootloader' etc. along with the option to 'wipe data/factory reset and 'wipe cache partition', I have tried both of these and tried booting the device with no luck, the screen does the same as before ^^.
I have downloaded ADB, CF-Auto-Root-shamu-shamu-nexus6, WugFreshDevelopment (NRT_v2.0.5.sfx) (I think it was after I used this that it all went wrong), Elite_Shamu_LP-06_17_2015, UPDATE-SuperSU-v2.37.
I'm sure if any of that is helpful or not though.
Any questions about my current situation I'd be happy to answer, I'm really stuck! I just want to go back to stock Android and wait for the real Android M release!
I realise now that I'm a total noob and shouldn't have been messing around without knowing what I was doing.
Thanks in advance.
Click to expand...
Click to collapse
Hi, I would suggest flashing a factory image for 5.1.1 and starting fresh. Also, I suggest taking any further questions here:
http://forum.xda-developers.com/nexus-6/help/noob-friendly-qa-help-thread-t3068327
That's a friendly help thread in the nexus 6 forums, where everyone is happy to assist. I have the nexus 6 myself, and I'm sure we can get you fixed up.
I have Lenovo TAB S8-50F that is currently stuck in a boot loop. It shows the white Lenovo and "android" text on black background boot screen for 30 to 60 seconds, then shuts off, vibrates and the screen flickers some white color and then goes back into the Lenovo and "android" text boot screen and repeats.
After some investigation on these forums and Google, I have tried the following:
Hold down Power + Volume Up + Volume Down until I see "fastboot starting...". I wait 5 - 10 minutes and it still says "fastboot starting...", nothing else. I try to connect to my Windows 8 laptop but it doesn't recognize the device.
Hold down Power + Volume Down until I see the boot screen, then let go of Power (keeping Volume Down pressed). Apparently this should boot into a Recovery menu, but nothing happens and it continues to just turn off after about a minute and boot loop
Hold down Power + Volume Up until I see the boot screen, then let go of Power (keeping Volume Up pressed). Same result as above, it still goes into boot loop.
During any of the 3 scenarios above, I can turn off the tablet by holding Power + Volume Up. Also I never saw any other messages like "EFI failed" or "No mounted drive" that other users had problems with.
Is there anyone out there that can help me restore this tablet back to functional state? I'm not sure what happened that caused this to happen.
bump
bump
bump
Your question has been answered on my thread
drop a like on all my past comments to encourage me to help you.
TAP ON THE BOX BELOW TO CONTINUE
x.ak**** said:
like all my comments above to encourage me to help you.
Okay so first of all i will let you know why a phone gets bricked-
>corrupted rom
>some system files got deleted
>rooting
>modding
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
my case
i always keep two phones with me like one for my experiments and one as a backup. In this case i'll be talking about my lyf wind 3 that got bricked.
>actually i was trying to install twrp onto that phone but first i had to root it, and due to the upgraded android security, i wasn't able to do via kingoroot so i tried i-root and it did the job but instead of kingo-superuser i got some ****ty superuser so i tried granting permission to the actual superuser and while doing so i accidentally double rooted my phone (first with i-root and then with kingoroot), which was kinda stupid, so it just deleted some system files and my phone wouldn't boot after that. It just got stuck on the boot logo.
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Click to expand...
Click to collapse
Hi everyone,
Looking for some help on my phone which is the only one I have unfortunately
So basically the Honor 9 is showing only the logo then just a black screen. One time it vibrated afterwards when pressing the volume buttons and made the camera sound. So it seems it might have booted but nothing is showing?
Phone did fall before, but worked afterwards.
I cannot access Emui recovery (when pressing volume up+power, it just shows the logo and black screen), but I can access fastboot.
If I plug it to charge, it shows the charging logo fine.
Bootloader is not unlocked. Nothing custom has been installed.
I already tried Hisuite recovery mode, but it said the device is not supported.
Any advice on what I could try? I searched the forums but couldn't figure out what to do. Any suggestion would be much appreciated.
Thank you!
bleepop said:
Hi everyone,
Looking for some help on my phone which is the only one I have unfortunately
So basically the Honor 9 is showing only the logo then just a black screen. One time it vibrated afterwards when pressing the volume buttons and made the camera sound. So it seems it might have booted but nothing is showing?
Phone did fall before, but worked afterwards.
I cannot access Emui recovery (when pressing volume up+power, it just shows the logo and black screen), but I can access fastboot.
If I plug it to charge, it shows the charging logo fine.
Bootloader is not unlocked. Nothing custom has been installed.
I already tried Hisuite recovery mode, but it said the device is not supported.
Any advice on what I could try? I searched the forums but couldn't figure out what to do. Any suggestion would be much appreciated.
Thank you!
Click to expand...
Click to collapse
Hello.
I know it is close to a year now, but just in case there is someone else out there looking to solve something like this. Just make sure to have a wifi connection through which you can download your firmware and recovery through the eRecovery panel. The downloads should be around a total of 4GB, so bear that in mind.
When you are set with your wifi access do the following (feedback will be appreciated):
- plug your phone to your computer and hold down the vol up + power button to boot into eRecovery
- in the eRecovery panel, choose to download firmware and recovery and it will launch a wifi connection
- connect to your wifi
- download the firmware and recovery accordingly
- once completed, you can proceed to update/upgrade (basically to install) it via the eRecovery
- once the upgrade/update/installations are complete, you can reboot.
- just know that everything on your device will be lost - full system and sdcard wipe will be made.
I hope you find the above helpful for you.