I've been lumbered with an original Nexus 7 (ME370T) that's in a bad state. The device has been attempted to have a factory reset done, by using the 4th button under the plastic casing, (under the volume down button). Its now stuck in the "Erasing" screen. It did have stock OS and bootloader.
I have tried accessing the bootloader using volume down and power buttons, but it only ever reboots into the factory reset mode, where I'm greeted with the green android wiggling its ears with the caption "Erasing", and I've left it doing that for several hours, with no sign of any progress. I've pressed some combination of volume buttons, and managed to get it to display the text under that splash screen, where all it says is "Formatting /data..."
I don't know whether I could use ADB or fastboot with the device in this state as I'm sure it needs to be booted into the bootloader for USB communication to work, and the bootloader was still stock/locked anyway.
Any ideas? It would be a shame to bin the whole thing, as I was sure that they are always recoverable in some fashion, perhaps JTAG, although I have no experience of that.
Same issue, exactly the same... Probably another broken EMMC - I know the OP is 3 years old but maybe someone reads it who found something I missed
Related
Apologies in advance for my newbie-ism with the Hero/HTC android devices... I'm trying to get my father's Hero running for him.
The story is that a small amount of water was spilled on the phone and now it won't boot past the "htc" boot screen. My experience with phones + water is that either they dry out and they're fine or they refuse to ever boot at all ever again so I'm hoping the fact that I can get the boot screen at all is a good sign.
I've tried the home-back-end call clear storage and the volumedown-action-end call fastboot. Everything I've tried just gets me back to the htc boot screen. When I plug into USB a mass storage drive pops up in windows explorer but when I try to click into it it gives me the "please insert a disc" message.
The diagnostic screen at the top states:
"HERO XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-fail
RADIO-1.04.01.01.21"
The touch panel fail message scares me, but is there any hope of getting this thing running again?
Thanks,
Kevin
Try asking the Impaler on his thread he might b able to help you
Root-Hack-Mod-Always™
Is the phone rooted? If so, try booting into recovery. May be a coincidence that water got to the phone and something with the phone's software got broken.
pull battery from phone, reinstall, then hold the volume down button and the power on button at the same time. hold until you see recovery screen pop up, this will work with or without root
The phone is 100% stock.
When I boot into the recovery mode (volume down + power on), I would hit the home button for "Recovery", correct? When I do that the phone restarts and goes back to the "htc" boot screen and hangs there.
Any ideas?
Holding the Volume down and powering on the phone will boot you into hboot. You can boot into recovery from hboot but you can boot directly to recovery as well. Hold the Home button and power on the device. However, to be honest I don't know if you can boot into recovery with a stock (unrooted) phone but it's worth a shot.
Looks like a direct boot into recovery is a no-go...
I downloaded the ROM update utility from the HTC website and was able to get the upgrade to load through FastBoot USB. The phone booted up and actually loaded past the boot screen into the Android setup screens, but the touch screen was completely non-responsive and every second or so an "acore" something or other error kept popping up. I wasn't able to get past the setup since I couldn't access the keyboard so I tried to restart and now I'm stuck at the (now updated) htc boot screen again.
It seems to me that the touch screen is fried and that the phone is probably no good... someone tell me if I'm wrong
Thanks for all of your help!
That's rotten luck. Hopefully you can get it fixed or replaced.
So I have had this US beta streak since around January, the one that says 'Dell Confidential' at boot up, but it's never really worked correctly. I purchased it from a person that I know that got it through some sort of beta testing; the details weren't provided and I didn't press him for them. Anyways, I am currently trying to get the clockwork recovery flashed and able to be booted into, although the streak is giving me every possible problem I can imagine. I'll try to provide as much background info as I possibly can.
Firmware: 1.5
Baseband Version AUS_090716_01_BOSS_EVT2_3135
Kernel Version 2.6.27
Build Number QTC_3135
OEM Version: AustinBuild_090724_03_boss_evt2_3135_FixTouchSuspend
Under About Phone > Status
IMEI 011954000020995
IMEI SV 00
Service Tag FF8R6K1 (which dell.com cannot find)
The Problems:
When I try to get into bootloader to get into fastboot, by holding the camera button down while hitting the power button, rather than going into the screen that is shown in all of the different tutorial threads, I instead go into some sort of a diagnostic menu that doesn't have an option for fastboot, as much as I have seen. There is a picture attached below.
I (think) that I can get the phone recognized by adb, although I am not totally positive. When in cmd in windows, and I type adb devices, instead of getting the proper serial number of my devices, it shows instead 0123456789ABCDE (I may not have that exact, but it does start at 0 and ends in hex at E or F, I can't remember right now and don't have it connected at the moment.)
There was one time where I was able to flash recovery.clockwork.img to where it said that it successfully flashed the img, but when I go to try and boot into recovery by holding both volume up and down at the same time, and then hitting power, the phone just hangs at a blank, black screen. It will stay there for 30 minutes and not do a thing, I can't see it via adb or fastboot.
So I then gave recovery.alt.img a shot, was able to successfully flash that, or so it told me that it was successful, but still the same problem: just a black screen.
The reason that I think that it actually was working was that after flashing the recovery image both times, I sent the command adb reboot recovery, and the phone reboots, but not into recovery, just into android. adb reboot-bootloader doesn't work at all and returns an error or nothing, I can't remember.
I then focused my attention on trying to get fastboot to work, assuming that adb was not working at all. This is where fastboot gets strange. The only way for me to get the command 'fastboot devices' to show anything at all is by holding the volume down button prior and then hitting the power button to start it. This puts the phone into essentially a 'soft brick', which my friend calls 'safe mode', where it gets totally stuck at the 'Dell Confidential' screen and will not progress past it no matter what.
So, once I am in 'safe mode', I am able to then issue a 'fastboot devices' command, which ... partially works? I hope that my totally unsure tone of voice was able to be conveyed through that message, because the info returned once that command is sent is totally confusing to me. Unlike before, where I feel as though the Streak is just lying to me by saying 0123...DEF for the device ID, for fastboot devices it just gives me a question mark .. yes, simply a ?
The weird thing is that it will follow commands. I was able to flash recovery.clockwork.img to the streak, it gave me a read out that said successful, and I got very excited. And then I pulled the battery, put it back in, held both the volume buttons, and .... the same result, the black screen. So, not allowing myself to be deterred, I got right back into fastboot, or at least my quasi working version of fastboot which may not be working at all, and flashed recovery.alt.img, which turned around and told me that it was successful as well. This time, not allowing myself to get excited, I pulled the battery and, with both volume buttons held down, hit power to try to get into recovery.
Again, I was let down and found only a blank screen. At this point, I have no idea what else to try. With the bootloader not being where it's suppose to be, not really being able to get into fastboot or adb (I think), I turn to xda to try and find some answers. Does anyone have a suggestion as to what I am doing wrong or might be missing. I am hoping that it is something that is really obvious that I feel very stupid, like I'm hitting the wrong set of volume buttons, but ... I don't think it's that easy.
Again, I feel as though the phone was getting the commands from fastboot because I sent fastboot reboot recovery, and the phone rebooted, just not into recovery but android. Same thing for bootloader, it just didn't work at all
Also, as for android 1.5 itself, almost nothing works. This appears to be running a very early edition of android where most apps just end up with: Sorry! No applicatons can perform this action, so the One touch root is kind of out of the question.
I was able to do the dialer unlock method to get EMList, but the similarities end there. I don't have the Unknown sources option or anything else after leaving dialer.
Any and all suggestions are appreciated and will be accepted and followed (within reason). I'm just at the point where I'm hoping that it's not totally broken and that with determination and hard work and some critical thinking I (we) will be able to get it working again. Hopefully it isn't a paperweight.
Thanks,
Thursday
Posted recently as my Nexus 7 seemed to be bricked. It seemed hopeless as it was a competition prize and i had no receipt of purchase and it seemed that the factory warranty had run out. nVidia the competition sponsor I guess bought a shed load of them and then handed them out later.
Anyhow, after seeing repeated demands that I use the original charger (which was a US charger and as such not compatible with 240V power in the UK) I finally decided to try it. I remembered that i had bought a transformer for a guitar effects pedal so I plugged that in and the charger into that and then the Nexus 7. Still no joy. However I decided to leave it connected and let it charge over night and the whole of the following day.
This evening I forlornly tried to boot the unit and HURRAH! I got the Google logo.
I waited for the animation to start for Android....
And I waited.....
And I waited a bit more....
Nothing. It seems stuck. I then powered it off by holding the power button and it turned off, only to immediately turn on and stop at the Google Logo. The only way to stop this was to get into fastboot mode (Power and volume down pressed) and cycling to power off and hitting power again to execute.
So I thought I could get somewhere.
However I cannot get it to go properly into recovery mode. I get the bootloaded screen where I can restart the bootloader (which does just that), power off (which also works correctly), Start (locks at Google Logo) or recovery mode (which also locks at the Google Logo)
I cannot get to the screen with the image of the Android with the red triangle and the exclamation mark.
The bootloaded screed says the following:
FASTBOOT MODE (red text)
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.23
BASEBAND VERSION - N/A
SERIAL NUMBER - 015d2d422357f20b
SIGNING - not defined yet
LOCK STATE - LOCKED
I have the SDK loaded and I cannot get the "Fastboot devices" to work. I previously sideloaded KitKat onto it so all the drivers are installed. I cannot get my PC to see that there is anything plugged in to the USB port. I think i need to get to this screen so that I can initiate a total system restore don't I?
Also the system heats up like an oven when it is locked at the Google logo.
I have repeatedly tried to get the drivers installed and have yet to get the PC to recognize the device. This is really wierd as I had used the adb to sideload KitKat onto the device.
Shortly after the sideload and a small 1.5Mb OTA update it went on the fritz. It would do absolutely nothing. After an extensive charge on the original 2A charger I can get it into Fastboot. However the fastboot sometimes freezes and I cannot get into Recovery Mode. Whenever I try to hit the power for recovery I get the Google logo and that's it. Have tried numerous presses of Vol-up and Power but no use.
It seems that there is something that the unit is trying to process and cannot get past that point. What can I do? I seem to be in driver hell. I am totally Stock. When the system was last operational USB Debugging was switched on. I don't care if I have to wipe it flat, I just want it working again.
Help please!!!!!!
Having replaced my Nexus 7 not too long ago with the Lenovo Thinkpad Tablet, I have found it to be quite the sturdy and reliable device despite its older technical specifications. However, after taking it with me to campus today, upon trying to turn it on from off (not sure what caused it to go off to begin with), the device is stuck on the Lenovo logo, and I cannot seem to enter recovery mode (unless I'm doing something wrong). My only speculation for the cause of this odd phenomenon is that the device somehow drained its battery to 0, causing some memory fault. I have not recently tried to do anything regarding system files or anything of the sort.
RinDunois said:
Having replaced my Nexus 7 not too long ago with the Lenovo Thinkpad Tablet, I have found it to be quite the sturdy and reliable device despite its older technical specifications. However, after taking it with me to campus today, upon trying to turn it on from off (not sure what caused it to go off to begin with), the device is stuck on the Lenovo logo, and I cannot seem to enter recovery mode (unless I'm doing something wrong). My only speculation for the cause of this odd phenomenon is that the device somehow drained its battery to 0, causing some memory fault. I have not recently tried to do anything regarding system files or anything of the sort.
Click to expand...
Click to collapse
You did not describe how you were attempting to enter Recovery so can't say if you are "doing something wrong". However, to boot into Recovery, immediately after pressing and briefly holding the power button to commence booting up, repeatedly press and release the Volume Up button a few times (~4) and you should see the single line message indicating its booting into recovery.
Do you have stock or custom Recovery? If the latter, after entering Recovery, see if folders can be mounted with read-write privilege. If not, the memory probably failed and your best option for repair is a motherboard replacement. I did this about a year ago but would move on to a higher spec'd device at this time...
eKeith said:
You did not describe how you were attempting to enter Recovery so can't say if you are "doing something wrong". However, to boot into Recovery, immediately after pressing and briefly holding the power button to commence booting up, repeatedly press and release the Volume Up button a few times (~4) and you should see the single line message indicating its booting into recovery.
Do you have stock or custom Recovery? If the latter, after entering Recovery, see if folders can be mounted with read-write privilege. If not, the memory probably failed and your best option for repair is a motherboard replacement. I did this about a year ago but would move on to a higher spec'd device at this time...
Click to expand...
Click to collapse
I get the "booting recovery kernal image" on the top left corner after doing that, but then I get a black screen afterward, which is why I think I am doing something wrong when trying to access recovery. I am currently in the process of installing the Android SDK and see what I can do via opening a command prompt in that while my tablet is connected.
Good plan. Sounds like you are initiating the boot correctly but the Recovery image may be corrupted or the memory failed. Let us know what you find out...
eKeith said:
Good plan. Sounds like you are initiating the boot correctly but the Recovery image may be corrupted or the memory failed. Let us know what you find out...
Click to expand...
Click to collapse
Ok, it looks like I can indeed enter recovery (CWM). I was just being a bit too impatient and not give enough time for the tablet to boot into recovery before saying what I said in my previous post. That said, what should I do before I just decide to go with the "wipe data/factory reset" option?
Context
I was attempting to root my nothing phone (1). I initially got stuck into a boot loop after Flashing the patched boot image & rebooting the phone. I was following the tutorial here. I then followed this guide to attempt to get my phone out of the bootloop. I was able to access the adb & fastboot commands but the phone would keep restarting. I then started "STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands" and failed to flash the odm partition. I stupidly ignored the very important warning to not exit the process halfway. I fastboot rebooted and then was greeted with a screen with: the nothing logo in the middle unmoving, the "powered by android" phrase, and nestled into the top left corner in very small font, "--any key to continue". The front of the text was cut off from the rounded corner of the screen.
Now:
When I press any of the buttons on the phone, the phone will go black and then immediately do a short vibration and turn right back on to that screen. If I hold the power and volume down buttons, the same thing happens even after holding it for almost 5 minutes. I can shut off the screen by holding just the power button for a few seconds but the phone will only turn on with the original error I had. When accessing the console on both my windows 10 PC and Linux laptop, the adb and fastboot commands are no longer able to detect a device. Neither of my computers can detect that the phone is even plugged in.
What I've tried:
I tried using a USB 3.0 fix: but failed
Running the commands on Linux: failed
nothing phone(1) fastboot flash by @sh4tteredd: failed
a slew of others that I've forgotten by now.
A common theme between the failures of all of my fixes is that the phone will not be detected by my computers. This was not a problem before I bricked the phone.
What are some solutions that might help me here?
Don't blame yourself. The phone hard bricks if you look at it wrong. This forum has several posts about the issue. Only solution is to send it to a support center.
coomac said:
Don't blame yourself. The phone hard bricks if you look at it wrong. This forum has several posts about the issue. Only solution is to send it to a support center.
Click to expand...
Click to collapse
no, this isnt hard brick. hard brick= no recovery, no fastboot, only edl
Gamer_Mida said:
no, this isnt hard brick. hard brick= no recovery, no fastboot, only edl
Click to expand...
Click to collapse
Did you read the post? There is no recovery or fastboot in this state. There are several posts and videos of this on this forum. I even posted one myself.
coomac said:
Did you read the post? There is no recovery or fastboot in this state. There are several posts and videos of this on this forum. I even posted one myself.
Click to expand...
Click to collapse
if it appears on the screen in fastboot press any button to turn off, it means that the bootloader is accessible, even if attached to the pc it does this thing, it is always accessible, therefore, it is not in hard brick
anyway it happened to me too, I know you also tried the usb 3.0 port, but this thing happened to me on another phone, I just changed the port and it worked (on the same pc)
It doesn't appear on the screen in fastboot. It's not the same as what you got on your Xiaomi phone even though the text is the same. Here you go. I don't mean to be rude but a quick search would have saved us this discussion.