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.
Related
Hi everyone,
Yesterday I made a Radio update to version 63.18.55.06_6.35.07.08. I made it putting the update.zip (radio rom) file in the SD Card.
All worked fine until the htc hero restarted (after appears the box with the orange arrow). Thereafter the Hero only shows the Hero logo when I turn on.
I tried to init the fastboot pressing home+power and home+back+power buttons (without SD Card and without SIM card) but always the result is the same, the logo appears and nothing happens.
The computer doesn't detects the Hero's USB connection and I can't run adb commands because it raises the "device not found" error.
Someone can help me?
Thanks in advance!
Did you let the screen with the box run its course?
Did the recovery console come back up saying formatting cache?
Have you tryed holding just back+power? ive never heard of using back+home+power
And also, i think your supposed to enter recovery with the sd in.
If that works then in that state is should be found by adb.
But yes, as the poster before me said, it should show the "unpacking" image, and then it should reboot. It should then go straight back into the recovery and the recovery will format the cache. If you tryed to turn it off at any point then, then something is badly mucked up. But it isnt bricked, and probably can be saved. Its only bricked when no logos at all come up on boot. If you managed to get it reconised by adb, you could probs format the cache manualy, though i dont know the command
All the previous steps after the breack are as you say, but after the "unpacking" image, the htc hero restarted and showed the hero logo instead the correct menu.
The problem with the adb is that the computer doesn't recognize the htc hero across usb. When I write the adb command ("adb devices") doesn't displays any device, and I can't run any adb shell for the same reason. How can I run any adb command if the device isn't recognized by the computer?
Have you tryed just taking the battery out, waiting 30 seconds, putting it back in, then booting the phone holding back+power?
And adb is very strange i find... Sometimes it reconises a phone, sometimes it doesnt, for no apparent reason. Have you tryed leaving it on the hero logo for a while then running adb commands?
If he has flashed, wouldnt the USB Debugging setting be reset also, wouldnt this be why he cannot access via adb.
Hi.
I habe exactly the same problem. I have updated radion.
Now ther come only the T-Mobile Logo and that's all.
I can not enter neither Recovery Mode nor fasbtoot does do something.
Any suggestions?
Lado
this problem shud be fixed asap because i think its a threat for all hero modders and owners as our phones get killed at anytime with this process. so guys lets try to find a solution for this problem. cheers
Updated Radio to 63.18.55.06JU_6.35.09.26 and it killed my hero.
first the box with the orange arrow came up and then the whole phone died... now it wont even turn on the screen.
please fix?????????????????
I had the box with the orange arrow yesterday after flashing radio.
The phone isn't dead, I think it's just working.
I kinda paniced also when it happend but I got into recovery eventually.
When you flash a radio it does not actually install that image until your first boot (when you see that phone out the box image).
At this point DO NOT DO ANYTHING WITH THE PHONE just wait and it will install the image and reboot for you. IT CAN TAKE UP TO 10 MINUTES.
If you turn it off or otherwise interrupt this process it can really mess up your phone. however the general rule is so long as you can see the HTC logo when you turn on i.e. it still turns on you can in theory always recover, its just a matter of finding the way that works.
The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
WidePants said:
The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
Click to expand...
Click to collapse
I'm having the same problem. I downgraded from 1.4.3 to 1.4.0. I was able to boot it once and then shut it back down so I could root it. Now it won't start up at all and I have tried everything that I can find to boot it to no avail.
The NT can sometimes get stuck in limbo while booting up, especially with SD-based boot. To get out of it, hold down the power button for 20-30 sec to turn it off then power it on again. Also remove any "bootable" SD card from the card slot; if it boots then the card was not bootable and its non-bootability was the problem.
It's also possible that the NT battery is completely drained (battery readings on some CM builds can be quite off, sometimes as much as 20 points) in which case you'd need to use the BN wall-charger and charge it for 8-12 hours.
I attempted to root a denver tac-70061 tablet in order to be able to switch the mounting of the internal and the external sdcards. I have only rooted once before; a denver tac-70031 tablet which was extremely easy to root by simply installing and running the superuser app. Unfortunately, it seemed that it was not as simple on the 70061.
As I am a novice, I followed the instructions blindly and read them through a number of times before attempting.
I followed a set of instructions which described downloading a zip file which contained adb for windows and some img and zip files to transfer to the sdcard.
I am using ubuntu, so I assumed that the adb which was installed along with android sdk would suffice.
I copied the required files to the root of the tablet's internal sd card and installed recovery via adb.
I unplugged the tablet and rebooted in recovery holding down volume-up while powering on.
When in recovery, the instructions told me to install superuser 3.1.3.zip from the sdcard but this file was not present.
When selecting 'reboot', the tablet kept rebooting to recovery and now seems to be stuck in a loop.
I hope that someone can help.
Factory Default reset?
How do you even get into the recovery menu. W/o I try, I get to the screen with the stupid robot laying down, and a ! inside a triangle showing. What buttons do you press to open recovery menu? On that page, no lists of stuff appear, and I want to reset the android tablet I used, also a TAC-70061, b/c it just keeps loading on the 3rd boot screen, and never gets passed it. Lame Denver product is not worth 2 cents. Apart from how annoyed I am, can you explain to me how to get into the factory reset and reset it/fix it?
Unfortunately, I've managed to brick (sort of) my Huawei Mediapad 7 Youth (s7-701u), and I need some help unbricking it.
Complete log of events before and leading up to the brick:
1)Flashed an alpha release of a CWM port than I'm working on, using terminal emulator. It doesn't work, unfortunately. and now I may never get it to work.
2)Had a few xposed modules running:
-Monster UI 4.0
-Permission master
-Guesture Navigation (or something like that)
All xposed modules were working fine together, rebooted quite a few times with them active. So I don't think they're the problem.
3)Removed everything located in the /cust folder. Again, I've rebooted enough times to conclude that this may not be the root of the problem.
4)Changed a few apps into system apps, either to replace those I deleted, or just to ensure they run at boot namely:
-Nova Launcher (to replace Huawei launcher)
-Google Keyboard (to replace Huawei Keyboard)
-Titanium Backup (to replace Backup)
-SD Booster (to change SD card read speeds at boot)
-Monster UI (I figured It may work better as a system app)
-SuperSU (Why not?)
5)I put in a custom boot animation.
I found a lollipop boot animation on OnHax, downloaded the bootanimation.zip, placed it in my /system/media and changed appropriate permissions.
When I rebooted, it worked, but hang halfway. The device booted as normal though. I took apart the bootanimation.zip, messed around with the desc.txt, recompressed it, and once again placed it in /system/media.
Upon rebooting, it didn't work, giving me a blank screen with only the backlight on. However, it vibrated, as it usually does, to indicate that the boot was completing, and it did indeed boot up.
A couple of tweaks to the desc.txt and two bootanimation.zips later, I rebooted, confident I'd at last solved the problem.
Huawei Logo shows up, as usual. Blank screen with only backlight (figured I must still have messed up the desc.txt), the vibration happens, as usual, Then, nothing.
Analysis of current situation
Here's a quick rundown of my tab's current situation:
1) Normal booting
It will show the Huawei logo it shows first, but instead of the boot animation, there's nothing but the backlight. The vibration that happens just before the boot completes still happens, at around the normal time, and after that, the backlight goes on/off if I press the power button.
2) SD Upgrade recovery method
If I copy the update folder (the one named dload) form the official firmware to the SD card, as per the instructions, nothing happens. Probably because I replaced the recovery. It shows the huawei logo, same as when a normal boot happens.
3) Bootloader mode
I can, in fact, boot the tablet into bootloader mode. This is the only reason I haven't given up on this tab. Applications such as RKAndroid and rkflash recognise it, so i think it's just a matter of getting the correct config files and/or proper .img files to use with such apps
4) ADB
Generally, no. ADB will not work. I believe USB Debugging was deactivated. Not too certain though
It did detect the tab once, and only once. Unfortunately, it didn't occur to me then to just delete the offending bootanimation using ADB shell. Never got it to work since. Maybe there is a special order of keys to press to get it to work, I dunno.
Things I have tried
1) Reflashing the stock recovery using RKAndroid
My logic behind this is, if I can get the original recovery back in, I can then get the SD upgrade to work, fixing everything.
2) Getting ADB to recognise it
If I can get ADB to recognise it, I can delete the bootanimation.zip, and maybe reflash the stock recovery using ADB shell
3) Using the SD Upgrade
If this works, then all my problems are solved, right?
Any and all help in this situation will be greatly appreciated. Looking forward to working with you guys to breath life back into this tablet.
Kris the wizz 15 said:
Unfortunately, I've managed to brick (sort of) my Huawei Mediapad 7 Youth (s7-701u), and I need some help unbricking it.
Complete log of events before and leading up to the brick:
1)Flashed an alpha release of a CWM port than I'm working on, using terminal emulator. It doesn't work, unfortunately. and now I may never get it to work.
2)Had a few xposed modules running:
-Monster UI 4.0
-Permission master
-Guesture Navigation (or something like that)
All xposed modules were working fine together, rebooted quite a few times with them active. So I don't think they're the problem.
3)Removed everything located in the /cust folder. Again, I've rebooted enough times to conclude that this may not be the root of the problem.
4)Changed a few apps into system apps, either to replace those I deleted, or just to ensure they run at boot namely:
-Nova Launcher (to replace Huawei launcher)
-Google Keyboard (to replace Huawei Keyboard)
-Titanium Backup (to replace Backup)
-SD Booster (to change SD card read speeds at boot)
-Monster UI (I figured It may work better as a system app)
-SuperSU (Why not?)
5)I put in a custom boot animation.
I found a lollipop boot animation on OnHax, downloaded the bootanimation.zip, placed it in my /system/media and changed appropriate permissions.
When I rebooted, it worked, but hang halfway. The device booted as normal though. I took apart the bootanimation.zip, messed around with the desc.txt, recompressed it, and once again placed it in /system/media.
Upon rebooting, it didn't work, giving me a blank screen with only the backlight on. However, it vibrated, as it usually does, to indicate that the boot was completing, and it did indeed boot up.
A couple of tweaks to the desc.txt and two bootanimation.zips later, I rebooted, confident I'd at last solved the problem.
Huawei Logo shows up, as usual. Blank screen with only backlight (figured I must still have messed up the desc.txt), the vibration happens, as usual, Then, nothing.
Analysis of current situation
Here's a quick rundown of my tab's current situation:
1) Normal booting
It will show the Huawei logo it shows first, but instead of the boot animation, there's nothing but the backlight. The vibration that happens just before the boot completes still happens, at around the normal time, and after that, the backlight goes on/off if I press the power button.
2) SD Upgrade recovery method
If I copy the update folder (the one named dload) form the official firmware to the SD card, as per the instructions, nothing happens. Probably because I replaced the recovery. It shows the huawei logo, same as when a normal boot happens.
3) Bootloader mode
I can, in fact, boot the tablet into bootloader mode. This is the only reason I haven't given up on this tab. Applications such as RKAndroid and rkflash recognise it, so i think it's just a matter of getting the correct config files and/or proper .img files to use with such apps
4) ADB
Generally, no. ADB will not work. I believe USB Debugging was deactivated. Not too certain though
It did detect the tab once, and only once. Unfortunately, it didn't occur to me then to just delete the offending bootanimation using ADB shell. Never got it to work since. Maybe there is a special order of keys to press to get it to work, I dunno.
Things I have tried
1) Reflashing the stock recovery using RKAndroid
My logic behind this is, if I can get the original recovery back in, I can then get the SD upgrade to work, fixing everything.
2) Getting ADB to recognise it
If I can get ADB to recognise it, I can delete the bootanimation.zip, and maybe reflash the stock recovery using ADB shell
3) Using the SD Upgrade
If this works, then all my problems are solved, right?
Any and all help in this situation will be greatly appreciated. Looking forward to working with you guys to breath life back into this tablet.
Click to expand...
Click to collapse
and Now you have another brick in the wall... i'm really sorry for you.
puntoazul said:
and Now you have another brick in the wall... i'm really sorry for you.
Click to expand...
Click to collapse
I haven't given up yet. The way I see it, the only option I have is to figure this out, as it will prove invaluable for others. If I figure this out, then it will be impossible to completely brick this device, a critical factor in this time of development. Inevitably, someone else will brick their device, and if we can find out how to fix it, then it will be of great benefit to all, don't you think?
I also need some help... my huawei mediapad 7 youth (no sim) is on bootloop.... no recovery mode working ... but I can update firmware .. every time I updat3 it ..showing sd fails.. any help..
My wife was using her phone (completely stock, no mods whatsoever) and it started shutting down processes (contacts, calendar, etc). She held the power button down to manually shutdown and then rebooted shortly after. The next day, it started to do it again, so she did the same thing only this time it stuck on the "M" logo screen. When she brought it home, I held the power & vol down buttons in for 2 minutes and the phone began to reboot but still stuck on the "M" logo screen.
I began searching vigorously online for a solution and have tried everything. **NOTE** - I am completely unsure what version of software the phone was running before this happened. The first thing I tried was RSD Lite with the JB Stock file from Team US Cellular. The flashing fails during certain lines of the .XML file. I took suggestions from other users to delete the lines it fails on and let the file continue the flash. Once it reboots, it is still stuck on the "M" logo screen. I then tried all the other stock firmware files I could and the same result each time.
Next, I tried using ADB and Fastboot tools. My PC recognizes the phone when plugged in and running command "adb devices" shows the phone listed, but whenever I try to run a pull or other command, I get error:closed. I've tried all the solutions of making sure ADB files are updated, running the list of commands to get the daemon connection reset, etc. I can't push/pull anything using adb. I tried using mFastboot with no luck either.
I tried the above steps over and over for 3 days straight, hoping I missed something simple. My final option was to boot into Recovery Mode and run Wipe Data/Factory Reset. When I select that option, about 3 lines of command begin to run and the phone reboots and goes back to being stuck on the "M" logo screen. The command lines and reboot literally happen within 2 seconds. That tells me Factory Reset is corrupted, but I'm not 100% at this point.
Does anyone have any insight on if there is anything I can do at this point? It wouldn't be such a big deal to lose the phone, but we have pics/videos of our 2 year old that we never got backed up at home or in the cloud and they're very important to us. Unfortunately, the phone did not have and SD card. I'm honestly out of ideas at this point and have never felt so defeated.
I got brave and decided to just unlock the phone and attempt to install TWRP on it and that doesn't even work. It says it flashed it, but whenever I choose Recovery, it never boots to TWRP. It continues to use the stock recovery screen. I'm assuming this thing is just completely done for?