I've had the great misfortune of bricking my phone within the first few hours of owning it. I should have known something was up, it wouldn't reboot when I changed the language to English, and I'd have to hard reset it (delete everything) and then let it load in Chinese again. Well, in an attempt to fix what I thought was a rom issue, I went through the song and dance of trying to root my phone.
I'm still not fully clear on how to do it, as it seems there's more to it than just what the tutorials say.
Anyway, like the title of this thread says, there's a pretty good way to figure out if your phone is really bricked, no need to ask or wonder anymore.
If your phone only boots to the htc magic screen (and then stops), and is unable to load bootloader, fastboot, usb connections, or anything else, it's bricked. 100%. You have to take it back. Don't bother searching the forums for the answer, I've wasted hours going through every related thread and trying every possible solution. Without the ability to access the fastboot screen, you're out of possibilities. Untill someone comes out with an unbricker which goes deeper than fastboot, there is absolutely no way to fix it.
A semi brick is much better on the other hand. There are plenty of ways to fix your phone, provided you're only semi bricked. I would define semi bricked as being able to enter fastboot, but being unable to boot the phone as normal. This can happen with a bad flash, or a mis step during a tutorial. I'm not exactly sure how easy it is to change a semi brick to a full brick, but my full bricking happened after semi bricking it while loading a new rom on it.
So. to summarize, if your phone WON'T go into the boot menu by pressing vol-down+power, you're in need of a new phone.
If you can still get into the boot menu, and access your phone through usb, you're ok, just get help (via a tutorial) before going any further, unless you're completely certain of what to do next.
Tis a shame to send a device, which is physically undamaged, to the digital graveyard. But such is life.
Caid.
444.
EDIT
on a side note, before my phone reset itself into it's endless loop of unloading, I noticed the screen flash an image of a box with what looked like a red arrow coming out of it. It was right in the center of the screen. This was in the recovery-RAv1.0H.img menu. What's that all about?
Did you try other key combinations such as Home+Power, or Back+Power?
I'm sorry but I think you're misunderstanding it all a little bit...
Caid444 said:
I've had the great misfortune of bricking my phone within the first few hours of owning it. I should have known something was up, it wouldn't reboot when I changed the language to English, and I'd have to hard reset it (delete everything) and then let it load in Chinese again. Well, in an attempt to fix what I thought was a rom issue, I went through the song and dance of trying to root my phone.
I'm still not fully clear on how to do it, as it seems there's more to it than just what the tutorials say.
Anyway, like the title of this thread says, there's a pretty good way to figure out if your phone is really bricked, no need to ask or wonder anymore.
Click to expand...
Click to collapse
It's easy if you follow the guides... I did it in two different phones with no problem at all in any of them... Anyway, let's stay on topìc
Caid444 said:
If your phone only boots to the htc magic screen (and then stops), and is unable to load bootloader, fastboot, usb connections, or anything else, it's bricked. 100%. You have to take it back. Don't bother searching the forums for the answer, I've wasted hours going through every related thread and trying every possible solution. Without the ability to access the fastboot screen, you're out of possibilities. Untill someone comes out with an unbricker which goes deeper than fastboot, there is absolutely no way to fix it.
Click to expand...
Click to collapse
Wrong. If your phone boots to the HTC Magic screen, the bootloader is doing it's job. The bootloader just takes you there. The linux kernel and ramdisk takes you to the boot animation, and there is where android really starts.
If your phone shows the first htc logo, or the Vodafone branded screen, you can start in bootloader mode. To make that you just have to remove the battery, put it back, and press and hold BACK + END KEY. From that, you can fastboot.
Also, and unless you destroyed the recovery partition, you can also boot in recovery mode, by pressing END KEY while holding HOME (no need to keep them both hold, just home button)
Caid444 said:
A semi brick is much better on the other hand. There are plenty of ways to fix your phone, provided you're only semi bricked. I would define semi bricked as being able to enter fastboot, but being unable to boot the phone as normal. This can happen with a bad flash, or a mis step during a tutorial. I'm not exactly sure how easy it is to change a semi brick to a full brick, but my full bricking happened after semi bricking it while loading a new rom on it.
Click to expand...
Click to collapse
I would call a semi brick this:
Your phone goes into an endless loop while booting.
Your phone gets stucked on the first boot logo.
You can't get access to the recovery partition.
Your phone boots all the way but then gets stucked.
Your phone gone bad during a software update.
That, all, can be solved by reflashing the affected region. There are tutorials for everything but if you need I can write some hints on each case (I suffered them all ).
Caid444 said:
So. to summarize, if your phone WON'T go into the boot menu by pressing vol-down+power, you're in need of a new phone.
Click to expand...
Click to collapse
Actually, VOLDOWN+POWER starts in Hboot mode. From there you can go back to fastboot mode, but hboot is used to make a software upgrade using complete images or running htc diagnostic images (SAPPDIAG.IMG, SAPP*.IMG /NBH).
Caid444 said:
If you can still get into the boot menu, and access your phone through usb, you're ok, just get help (via a tutorial) before going any further, unless you're completely certain of what to do next.
Tis a shame to send a device, which is physically undamaged, to the digital graveyard. But such is life.
Click to expand...
Click to collapse
If you can't get USB working on fastboot mode, or on recovery mode, your phone has probably a hardware fault. It happened with some of the first revisions of the Vodafone branded magic, don't know about htc branded ones though..
NOTE: Not talking about missing drivers, if you don't have drivers, that's another problem, but the computer should at least detect the device. Also, if your phone is off, and you connect the charger (or usb) and the orange led lights up, the bootloader should be ok.
Caid444 said:
on a side note, before my phone reset itself into it's endless loop of unloading, I noticed the screen flash an image of a box with what looked like a red arrow coming out of it. It was right in the center of the screen. This was in the recovery-RAv1.0H.img menu. What's that all about?
Click to expand...
Click to collapse
That's the recovery mode. With that you can unbrick your phone
Also, as another hint, if you're new to linux OSes, you might want to take a look at some manual on terminal commands. If your main software is bricked, it's possible that your SDCard doesn't get mounted on recovery mode, depending on wich recovery image you're running. Provided you have an update.zip on the sdcard you need to run, you might have to mount it manually.
To do that, you have to start the phone in recovery mode, and run an "adb shell" on the PC.
When you have a shell opened, you'll have to mount the sdcard manually:
mount /dev/block/mmcblk0p1 /sdcard
Then, on the phone you can use the option to run sdcard update.zip to restart the software upgrade procedure.
Regards!
Before I reply, I'd just like to say thank you very much for your extremely in depth reply.
biktor_gj said:
I'm sorry but I think you're misunderstanding it all a little bit...
It's easy if you follow the guides... I did it in two different phones with no problem at all in any of them... Anyway, let's stay on topìc
Wrong. If your phone boots to the HTC Magic screen, the bootloader is doing it's job. The bootloader just takes you there. The linux kernel and ramdisk takes you to the boot animation, and there is where android really starts.
If your phone shows the first htc logo, or the Vodafone branded screen, you can start in bootloader mode. To make that you just have to remove the battery, put it back, and press and hold BACK + END KEY. From that, you can fastboot.
Also, and unless you destroyed the recovery partition, you can also boot in recovery mode, by pressing END KEY while holding HOME (no need to keep them both hold, just home button)
I would call a semi brick this:
Your phone goes into an endless loop while booting.
Your phone gets stucked on the first boot logo.
You can't get access to the recovery partition.
Your phone boots all the way but then gets stucked.
Your phone gone bad during a software update.
That, all, can be solved by reflashing the affected region. There are tutorials for everything but if you need I can write some hints on each case (I suffered them all ).
Actually, VOLDOWN+POWER starts in Hboot mode. From there you can go back to fastboot mode, but hboot is used to make a software upgrade using complete images or running htc diagnostic images (SAPPDIAG.IMG, SAPP*.IMG /NBH).
If you can't get USB working on fastboot mode, or on recovery mode, your phone has probably a hardware fault. It happened with some of the first revisions of the Vodafone branded magic, don't know about htc branded ones though..
NOTE: Not talking about missing drivers, if you don't have drivers, that's another problem, but the computer should at least detect the device. Also, if your phone is off, and you connect the charger (or usb) and the orange led lights up, the bootloader should be ok.
That's the recovery mode. With that you can unbrick your phone
Also, as another hint, if you're new to linux OSes, you might want to take a look at some manual on terminal commands. If your main software is bricked, it's possible that your SDCard doesn't get mounted on recovery mode, depending on wich recovery image you're running. Provided you have an update.zip on the sdcard you need to run, you might have to mount it manually.
To do that, you have to start the phone in recovery mode, and run an "adb shell" on the PC.
When you have a shell opened, you'll have to mount the sdcard manually:
mount /dev/block/mmcblk0p1 /sdcard
Then, on the phone you can use the option to run sdcard update.zip to restart the software upgrade procedure.
Regards!
Click to expand...
Click to collapse
To the first answer.
It's not THAT easy, the guides are kinda (you should already know what you're doing at this point) in nature. It's confusing for newcomers, as we've no idea what to expect, that and there are a multitude of variations. More specification as to which guide works with which model, and which updates would be nice.
As for the second part, I could not get the phone working with any button variation pressed. I'm sorry I was not more clear in my description, to begin with. I could press (and hold) any button (or buttons) + power (end key) and the phone would just vibrate (briefly) and then display the original screen "htc magic"(endlessly). The orange light does come on when plugged into the usb or computer, but only while it is off, as soon as the device turns on, the light turns off.
Another thing of note is that, after bricking it, I had to remove the battery to turn it off (every time if it was on), and if I put the battery back in while it's plugged into the usb port of the computer, the phone would turn back on without pressing any buttons. It's also completely unresponsive or detectable by my computer after bricking it. The only other thing I can get it to do is make the orange light blue by holding the action button and turning on the device. That way the light on top of the device is blue when it turns on. Still unresponsive at that point.
This is my first android device, but not my first htc device (I've had MANY MANY different ones.) so I'm a bit familiar with trying different combinations to get a response.
I am not the first person who's had this happen, unfortunately. There have been a couple others, who've described the exact same encounter. Perhaps it's a mistake that I made, and perhaps they also made it themselves. I would like to figure out how it's happening, though, and perhaps write a tutorial for people like us unlucky few.
Again, a really big thanks. I've sent my phone back and am getting a new one soon. I much appreciate your reply, however, as it's probably the most understanding and considerate reply I've seen on these forums.
Cheers.
Caid.
444
One more quick question out of curiosity, when you press and hold back and press end to turn on the device (it still goes to the htc magic screen) SHOULD it go to a different screen, other than the "htc magic" screen? Or is that a process that runs without some sort of visual notification on the device itself?
The usb was completely unresponsive after this happened, but in the event that bootloader may have been running, (only possible if it runs without any visual notification on the device itself), I'll go pick up the device and see if my usb drivers on my computer just became unresponsive after being accessed too many times. Sometimes windows does that, right? Perhaps a reboot would have allowed fastboot and the drivers to connect again, if the device was trying to talk to the computer, but I just didn't know on account of not having any notification.
So, again, should pressing back and power bring me to a different screen? or would it also look like it was hanging on htc magic screen?
Caid.
444
p.s. Sorry for the confusing wording, I'm tired and trying very hard to be as specific as possible.
back+end/power should lead you to the fastboot screen right after it shows the HTC Magic screen or whatever splash screen you have installed.
Home+end/power should lead you to the recovery screen.
ok, it was bricked. Thanks for the answer.
Caid.
444
Caid444 said:
Before I reply, I'd just like to say thank you very much for your extremely in depth reply.
To the first answer.
It's not THAT easy, the guides are kinda (you should already know what you're doing at this point) in nature. It's confusing for newcomers, as we've no idea what to expect, that and there are a multitude of variations. More specification as to which guide works with which model, and which updates would be nice.
Click to expand...
Click to collapse
No problem, we all should be here to learn, and to help (except for the trolls)
This is the guide I followed for both Vodafone branded Magics: http://android-dls.com/wiki/index.php?title=Magic_Rooting
Maybe not for now, but for the next magic you get it may come handy
Caid444 said:
As for the second part, I could not get the phone working with any button variation pressed. I'm sorry I was not more clear in my description, to begin with. I could press (and hold) any button (or buttons) + power (end key) and the phone would just vibrate (briefly) and then display the original screen "htc magic"(endlessly). The orange light does come on when plugged into the usb or computer, but only while it is off, as soon as the device turns on, the light turns off.
Click to expand...
Click to collapse
When the phone is off with the charger connected and you press the power button, the light goes off, as for the others, you really should be able to enter the SPL if it could the magic bootlogo and vibrated upon boot...
Maybe you didn't try enough or maybe your bootloader behaved differently than mine... I should be more clear anyway, to get to the bootloader, the best way to make it go to the bootloader is press and hold back key, then while holding it, hold the power button too. It should take about a second or two before showing the three skater droids.
Caid444 said:
Another thing of note is that, after bricking it, I had to remove the battery to turn it off (every time if it was on), and if I put the battery back in while it's plugged into the usb port of the computer, the phone would turn back on without pressing any buttons. It's also completely unresponsive or detectable by my computer after bricking it. The only other thing I can get it to do is make the orange light blue by holding the action button and turning on the device. That way the light on top of the device is blue when it turns on. Still unresponsive at that point.
Click to expand...
Click to collapse
When you put the battery while USB or charger is connected, the phone boots up, that's the normal behaviour. About the blue led, that's the Radio bootloader. That's quite dangerous to play with, but it gives a lot of other functions. Another sign that your phone wasn't completely dead Even if you wipe the SPL (the three skater droids), you may be able to boot into the Radio bootloader and write or boot another one to fix it. But that's waaaay harder
Caid444 said:
This is my first android device, but not my first htc device (I've had MANY MANY different ones.) so I'm a bit familiar with trying different combinations to get a response.
I am not the first person who's had this happen, unfortunately. There have been a couple others, who've described the exact same encounter. Perhaps it's a mistake that I made, and perhaps they also made it themselves. I would like to figure out how it's happening, though, and perhaps write a tutorial for people like us unlucky few.
Click to expand...
Click to collapse
I guess the first advice when you start tricking with a phone is be careful with what you're doing. That's the good thing of fastboot.
When booting on fastboot mode, you can pick, for example a recovery image, and boot it without overwriting the original rom:
Code:
fastboot boot [recovery_image]
Then, when you see it's working, you can flash it:
Code:
fastboot flash recovery [recovery_image]
fastboot flash boot [boot_image]
fastboot flash system [system_image]
fastboot flash data [data_image]
You can't do that with the system.img since it's too big, but you can do it also with a boot.img
About the key combinations on the phone, it goes like this:
Code:
BACK + END KEY -> Fastboot mode (you shouldn't see the boot logo)
VOLDOWN + END KEY -> Hboot mode (you shouldn't see the boot logo)
ACTION (trackball center) + END KEY -> Radio Bootloader (you shouldn't see the boot logo)
HOME + END KEY -> Recovery mode (you should see the boot logo, then get the recovery menu)
SEND + MENU + END -> Reboot the phone (while the phone is on)
Maybe there are more (android has kind of 'safe mode' but I don't know it it goes there automatically if there's a problem or if it has to be called manually)
Anyway, I hope these things will be useful for the next phone, and for anybody who's a bit lost on this
Regards!
Let us know where you live , so maybe one can help you , I live in Sweden and will be glad to help you if you are near ;-)
Hey! Thanks again for all the help, and the offer to come help. Unfortunately, I'm in China. Coming here from Sweden (although it's a single large landmass) would take quite a bit of time
I appreciate all the support, though. Very cool community we're building here for the magic.
Caid.
444
htc semi-brick?
Hi to all. I'm in the same condition described in this tread; after installing SPL i get the htc block in Vodafone brand red screen.
None keys combination bring me to the boot menù. Only Action(trackball) + power have effect, but with a black screen...
Any suggest?
What do you do if you can boot into fastboot but can't flash anything because absolutely everything gives the error "FAILED (remote: signature verify fail)"?
I have a card reader and have tried just about every sappimg.zip, every boot.img, every recovery.img i could find. I can't even boot a recovery img because the screen just hangs at the HTC Magic logo.
I don't know what kind of warranty i have on this thing, but i might take it in tomorrow and see if i can get it replaced. I've only had it for just under two weeks.
Newbie need help
ok so i can still go to recovery mode but everytime i reboot my phone the mytouch 3g logo never goes away im new to Android but not htc can somebody plz help me out.
gruppler said:
What do you do if you can boot into fastboot but can't flash anything because absolutely everything gives the error "FAILED (remote: signature verify fail)"?
I have a card reader and have tried just about every sappimg.zip, every boot.img, every recovery.img i could find. I can't even boot a recovery img because the screen just hangs at the HTC Magic logo.
I don't know what kind of warranty i have on this thing, but i might take it in tomorrow and see if i can get it replaced. I've only had it for just under two weeks.
Click to expand...
Click to collapse
Instead of flashing something, you boot a recovery image, and then, from there, you flash whatever you need (using adb & flash_image for example)
PS: Be a little patient, if fastboot is letting you boot a recovery image, the recovery needs to boot, and that takes a little while, and while it's booting, you see the bootlogo until the menu appears. Also, you can try running adb shell after boot process started to try to get an error message (or at least to know if the thing is booting in some way)
I couldn't boot any recovery images. I had tried a few different Hero ROMs but decided i wanted to use Cupcake again because i have a 32B board and it just doesn't have enough RAM, though Swapper makes it usable at least. I don't know what exactly i did, but i've learned a lot from my mistakes. Everything i tried failed the signature check because the hboot version didn't match. If i could just flash the 1.33.2005 hboot again, i would have been in business, but no matter which recovery image i tried, it just sat there doing nothing. And believe me, i waited.
Fortunately, T-Mobile gave me a new device after i took it in and played dumb. And I just rooted it =]
Caid444 said:
ok, it was bricked. Thanks for the answer.
Caid.
444
Click to expand...
Click to collapse
Why not flashing it with an RUU from HTC. Not sure that would work but it is worth trying.
Hi there, people!
First of all, thanks because while I was reading ur posts I realized that my phone had been bricked, 100 %
I tried official ROM upgrade to Android 1.6 using the folowing steps
1. Copied radio zip to my sd card by renaming it in update.zip
2. Recovery screen was started by pressing HOME+END key
3.Applied update.zip, process was going on: Opening package, verifing package, installing radio...and message about success was shown and phone restarted
4. Phone stucked on HTC Magic logo screen...15 minutes
5. I removed a battery, put it back and tried to reach recovery or boot mode again
6.Unsuccessfully! Phone vibrates and turns on...but always stucks on the HTC Magic screen
7. USB does not recognize my phone is connected (I tried any adb and fastboot commands)
8. So, I just pray to give me a new phone if my warranty will be accepted
iivanovic said:
Hi there, people!
First of all, thanks because while I was reading ur posts I realized that my phone had been bricked, 100 %
I tried official ROM upgrade to Android 1.6 using the folowing steps
1. Copied radio zip to my sd card by renaming it in update.zip
2. Recovery screen was started by pressing HOME+END key
3.Applied update.zip, process was going on: Opening package, verifing package, installing radio...and message about success was shown and phone restarted
4. Phone stucked on HTC Magic logo screen...15 minutes
5. I removed a battery, put it back and tried to reach recovery or boot mode again
6.Unsuccessfully! Phone vibrates and turns on...but always stucks on the HTC Magic screen
7. USB does not recognize my phone is connected (I tried any adb and fastboot commands)
8. So, I just pray to give me a new phone if my warranty will be accepted
Click to expand...
Click to collapse
I have the same problem. I get up hboot and fast boot menus can not get it in recovery. try to add in sappimg but no luck
I'm having the exact same problem...
Any solution yet?
Hello! I can assure you that your phone is not fully bricked! Awhile ago I flashed a new radio only to discover that I hadn't done my research and was a complete and total idiot. I flashed the 1.76.xxxx on a 32B. It didn't like it. I got a quick HTC logo that disappeared then the phone never responded again. When I say never responded it was dead. no combination of buttons would get any response. If you can get into fastboot you have options. All that's necessary is to make sure you have the appropriate sappimg file. Try the Unlockr's gold card method file. He has a .zip file that may work for you. Just make sure that you find an image that is compatible with your board (32A or 32B). Hope this helps!
Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.
From bad to WORSE!
I discovered the dcom222 thread that describes my problem and details a solution. I followed it to the letter, changing the command and using my microSD as a secondary boot to reinstall the vanilla tnt ROM.
But then it just stuck on the tnt logo, faded in and out 3-4 times, and went dark! The device won't turn on or off (had a full charge when I pulled it from the wall socket a few moments ago)
Please tell me I haven't bricked this thing!
still no luck...
I was able to power the unit back up, but I've tried to recover and flash all three setup files I have (vanilla tnt, ota update tnt and tnt lite 2) but nothing works!
All of them create a loop of some sort, whether it's the viewsonic screen, gtablet screen loop, or the tnt logo screen blinking on and off, NOTHING boots to the desktop.
Going to bed before I drive my self insane. Hopefully someone in the know will reply by the time I check this at work.
thanks in advance
You have not bricked it, don't worry. This device is very hard to truly brick. If all else fails there is nvflash or the apx mode fallback. But I don't think you need that if you are still able to boot to clockwork recovery.
In clockwork go to advanced - mounts and try mounting and unmounting your partitions. I suspect your user partition may be screwed. This seems to happen fairly frequently especially the first time you flash a ROM. It happenend on my first flash and not again since. Clockwork lets you repartition though. Search the forum for partition fix, its not too big a deal.
If that fails try roebeet's thread on nvflash recovery for TNT lite. If that fails, search for APX mode.
As far as I know there are zero bricks from ROM flashing so far.
Sent from my SMB-A1002-3G using Tapatalk
Life in LA said:
Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.
Click to expand...
Click to collapse
Scroll down to post number #869 http://forum.xda-developers.com/showthread.php?t=842004&page=87
feeling better
Thanks for the assurances that I didn't wreck the device, and pointing me to some solutions. I have a few questions:
what is clockwork mod? If I am able to recovery boot from my micro SD card, do I already have it? (I downloaded a bunch of recovery images to start, per instructions)
If it's something I still need to download, is it a PC application? How am I supposed to change settings in it (manage partitions, etc) if I can't get the tablet to boot?
-- stuck at work and dying to get home to fix this thing...
Ok, more detailed instructions:
If you press and hold down Volume + when you are pressing the Power button to boot up, and keep holding the Volume + key until you see a message that says "Detect a Recovery Key Pressed", that should get you to a text menu from which you can navigate using the volume +/- keys and the Home soft button to flash ZIP files and do other things. That menu is ClockworkMod Recovery. Since you remember installing a recovery.img, it sounds like you probably (hopefully) have ClockworkMod Recovery on there.
If you get to ClockwordMod Recovery, you can go down to the Mounts and Storage option, then you will find the "Mount USB storage" option at the end of that list. That lets you plug in and mount your internal memory area as a standard USB drive to your Windows or Mac computer to copy over new ZIP files and the like to your G Tablet.
You can also check that partitions are all mounting and unmounting successfully in that menu. If you go instead into the Advanced menu, you will see Partition SD Card, which I believe is what you might need to do at this point.
If booting with the Volume + button held down doesn't get you anywhere and you see nothing about Recovery Key Detected and don't see any text menu, then you don't seem to have a working recovery. At that point you'll have to do what phfaty suggested, read the post he referenced, and follow the link therein to the tegratab forum post to get the NVidia Tegra SDK installed on your Windows desktop and use the NVFlash tool and APK mode (where you hold the Volume - key down while booting instead of the Volume + key) to reflash your tablet.
still not working...
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.
Life in LA said:
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.
Click to expand...
Click to collapse
1)Boot into clockwork.
2)Navigate to Advanced menu
3)Choose partition sdcard
4)Choose data partition desired size(1024=1GB)
5)Choose 0GB for the next selection(swap not used)
6)Do a factory reset from main menu
7)Reboot
8)If that doesn't work, then reinstall ROM, then reboot
UPDATE
partitioning the drive and wiping the user data did the trick. I'm up and running again. thanks to all who chimed in to help.
Kit Kat 4.4.2
Would provide add'l info but can't even boot it up right now.........
Long and short....... phone was not rooted or modified on any way (for once). Only issue I noticed before it died was that the display would "freak out" with some colored lines once in a while....only for a few seconds. Last night, when I went to go into an email app....... everything crashed. All apps put up not responding messages, the UI crashed and the phone shut off before I had a chance to shut down correctly.
Now all I get is the red Motorola logo. I can get to the diagnostic menu (vol down, power, then vol up when the logo disappears). Recovery results in the dead android icon. All other options EXCEPT AP Fastboot Flash result in going back to the red Motorola logo. The phone is recognized in device manager when I plug into laptop, and the phone says connected to USB, and "device is locked". It does not show up as a drive, however (I did not have USB debug set to on if that's the reason).
I'd obviously like to save the phone, but more important are the pictures, which like an idiot I didn't back up. So, what I've tried:
1. Downloaded Moto drivers and made sure phone shows up as Mot Single ADB Interface (Fastboot Vanquish S driver)
2. Downloaded RSD Lite 6.1.6 and installed. Seems to recognize phone, as it lists USB port. Phone info, however, all says N/A
3. Downloaded KitKat stock ROM, which included the XML file, the recovery image and one or two more images. forgive me, but i left the file at work so i can't be specific.
4. When trying to flash that file with RSD, I get a "getvar" error and the flash fails.
Any ideas? Please keep it as simple as possible...... I'm no pro at this. I'll get the exact ROM filename tomorrow, since that might be the issue................
Question...... my pics are obviously on the internal storage, not the external SD card (dumb again)....... is there a chance that this process will not delete those files? I think the internal is considered SD0 on this phone (and maybe on all android platforms), and I read that the internal SD might not be overwritten.
UPDATE: I just read a post that said to delete all the lines with "getvar" from the XML file. I will try that, but in the meantime, if I'm doing anything completely idiotic, I'd like to know.
SECOND UPDATE: Found another site to download the ROM from.......... this time is gets by the "getvar" but fails at the first "flash" command....... see attachment
Thanks
Were you on the .15 update? It looks you're getting that fail because you're trying to downgrade to .10. .15 is linked in the general section.
Sent from my HTC6525LVW using Tapatalk
re:XT926 (mostly) dead
RikRong said:
Were you on the .15 update? It looks you're getting that fail because you're trying to downgrade to .10. .15 is linked in the general section.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I'm not sure if I was on .15.............. but the file i was trying to flash is 10.1.........so i'll try to find the file you suggest. thanks.
The "dead android" logo is normal, you have to press a combination of keys to "unlock" recovery:
When you see it, hold both volume keys, then quickly press power button, and you should have options.
From stock recovery you can try either clearing cache, or clearing cache and data (if you dont mind losing your files) to try and see if it comes back.
Seen a similar issue (stuck on boot logo) on a xt925 and a moto G before, and simply clearing cache solved it.
Hope you can recover your beloved device, and make sure to report your results here
EDIT: So, I reread your post and seems like you cant go into recovery anymore, so reflashing seems to be the best option. Usually seeing the red logo is a good sign. Dunno about the specifics on flashing a xt926, but yeah, you have to edit the xml file.
Re: almost dead
Thanks........yes i think the recovery option is shot. And for the life of me I can't find version .15 as suggested in another post above. I just searched the general forum for over an hour and only see .10
UPDATE: Damn.......... that sequence worked. saw the dead android and hit your key combo. now have options to:
reboot system
apply update from SD
apply update from ADB
wipe data/factory reset
wipe cache partition
remember, i'd really like to save my media. any idea what the best selection would be?
UPDATE 2
Tried "Wipe Cache Partition". Seemed to complete the function (android icon came alive with electric).........but did not help phone to reboot
thanks so much, even if it doesn't save my data. Progress at least.