Related
I'm so mad right now. I had Gingerbread VeggieTab RC1 installed and it was working fine. I selected the reboot option since it was acting kind of wonky what with the market crashing constantly. Upon Startup, I got those 3 frickin' birds looking at me. I've been in this situation before, where I can't access the birds. So I instantly turn to this tutorial here: http://viewsonic-gtablet-for-dummies><.webs><.com/nvflash.htm (remove '><'s)
I've already installed APX drivers so I thought, no big deal, right? Wrong. You see, when I plugin the gTablet, in "devices and printers", it's under 'unspecified' at the bottom, looking like an idiot labeled "APX." Clearly I'm infuriated here. When I try and access nothing happens. You cannot see the gTablet as a storage device.
Then, I thought, "Well, what if I installed the APX Drivers again?" So I opened up device manager, uninstalled 'NVIDIA USB Boot-recovery driver for mobile devices', and then restarted. Good, so now APX is showing up as unsuccessful and looks like it should in the guide. Was I in the clear? Noooo. I installed the USB driver software, ez pz etcetera. It basically got me in a full loop. "NVIDIA USB Boot-recovery driver for mobile devices" shows up again, and it's still displayed as APX.
I'm sorry if I'm acting REALLY distressed but it's very urgent that I fix this in the next 3 hours. I am also aware that it could probably work if I used another computer but this is the only one I got. SO PLEASE, PLEASE, XDA, HELP ME!
I take no responsibility for people deviating from my the procedures I listed. I'll explore some options and will get back to you later.
Have you powered down completely? Sometimes it in apx mode and the tab looks like its off. Hold power for 20 seconds and then plug into computer and then hold power volume down(-). This will insure your PC is reading apx as it becomes available. Good luck
goodintentions said:
I take no responsibility for people deviating from my the procedures I listed. I'll explore some options and will get back to you later.
Click to expand...
Click to collapse
I never said your procedure didn't work, it did. What I am saying is that in your procedure the driver only works the first time you use it and not any time after that. The same driver didn't allow me to use it a second time and the resulting times after that.
Uh...common sense dictates that you only need to install the driver once.
Actually, let me edit my website.
Here is a quick fix for you.
Download virtualbox and run a linux virtual machine on your system. Nvflash actually works better in linux.
Added by edit.
Oh, I see what's wrong. That driver is for apx mode, not the storage device. Goodness. The page even said for nvflash.
If you want your pc to recognize your gtab's internal storage device, you need to have the right kernel. Again, this is all explained on my website.
goodintentions said:
Uh...common sense dictates that you only need to install the driver once.
Actually, let me edit my website.
Here is a quick fix for you.
Download virtualbox and run a linux virtual machine on your system. Nvflash actually works better in linux.
Added by edit.
Oh, I see what's wrong. That driver is for apx mode, not the storage device. Goodness. The page even said for nvflash.
If you want your pc to recognize your gtab's internal storage device, you need to have the right kernel. Again, this is all explained on my website.
Click to expand...
Click to collapse
Oh my god, I was like "what the hell does he mean "you only need to install it once...it's already installed and--" and then I realized it...****. Wow, I feel stupid.
Can I say a few things?
1. Instead of flashing "You only need to update driver once!" can you say "If this is the 2nd time you are doing this, skip to step 3 and then skip to Part II".
2. I realize this is the 2nd time you've corrected me with this, but still. It makes me really frustrated when you talk so condescendingly. I would be happy if you talked to me person to person, thank you. If there weren't dummies like me, your site wouldn't get any traffic
Now then. I ran everything the same. When I boot up, though, the screen gets stuck at the "N" part of tapntap where its loading. Then it just runs for a while, repeats the TAPNTAP screen, and does this several times before it just turns off. Does this mean I really have to repartition
(1) I'll change my website to your words. Thanks for the advice.
(2) This is the way I talk in real life all the time. I've been described as the king of sarcasm. My "girl friend" is a therapist. She's working with me on this issue.
(3) You have brickage. You've bricked your gtab. You need to follow my code red to get out of brickary.
Added by edit.
You should have seen the original version of my site. It sounded exactly like me in real life. After some emails suggesting I change a few things before I face a class action lawsuit for upsetting a whole class of people (mainly dummies) I started doing some major overhauls based on their suggestions.
3 birds only; NO cwm, NO nvflash!
This is the closest forum I have found to my "issue"
I recently used nvflash to "update" to 1.2 branch with cwm. Worked fine and I installed cyanogenmod 7.0.3 (yes, the one that is meant for 1.2 branch). THAT started up seemingly fine.
Then I did a complete shut down and now I only get to the 3 bird screen. Won't acknowledge anything when I hold the Power and volume + button; when I try to connect to the PC it recognizes the device, but as soon as I try to do the nvflash to either 1.1 or 1.2 builds (I have successfully done both builds with this device; soft bricked before I understood what version I had, I'm a noob) it opens momentarily on the computer screen and shuts down. I have tried this on two different computers. I haven't seen anything that quite addresses this issue; it seems like most people can get into cwm. So... Help?
Couple sidenotes: the 1.1 and 1.2 nvflash folders I have had on my computer DO have cwm included. Also, I am currently following the recommendation to leave the tablet on until the battery is completely dead (and until it won't even begin to start up anymore) if all else fails, then start it up again. It didn't specifically say what that would accomplish... I'm giving it a shot though. Thanks for your help in advance!
drigg07 said:
This is the closest forum I have found to my "issue"
I recently used nvflash to "update" to 1.2 branch with cwm. Worked fine and I installed cyanogenmod 7.0.3 (yes, the one that is meant for 1.2 branch). THAT started up seemingly fine.
Then I did a complete shut down and now I only get to the 3 bird screen. Won't acknowledge anything when I hold the Power and volume + button; when I try to connect to the PC it recognizes the device, but as soon as I try to do the nvflash to either 1.1 or 1.2 builds (I have successfully done both builds with this device; soft bricked before I understood what version I had, I'm a noob) it opens momentarily on the computer screen and shuts down. I have tried this on two different computers. I haven't seen anything that quite addresses this issue; it seems like most people can get into cwm. So... Help?
Couple sidenotes: the 1.1 and 1.2 nvflash folders I have had on my computer DO have cwm included. Also, I am currently following the recommendation to leave the tablet on until the battery is completely dead (and until it won't even begin to start up anymore) if all else fails, then start it up again. It didn't specifically say what that would accomplish... I'm giving it a shot though. Thanks for your help in advance!
Click to expand...
Click to collapse
I have flashed my Gtab more times then I can think of, and also installed many custom mods. The only best solution that I can give you is if you can get into CWM you need to partition the drive (2048-0). Then after that is complete Fix Permissions and mount USB. Connect USB to computer and transfer the mod you are trying to install. Remember that when using a 1.2 mod you have to be using CWM v.3.0.2.8. That's the only one that I would trust in. You can download it off the web.
I hate humble pie... thank you for your hard work, your site helped an old man stop his hair from getting grayer...
Thanks for the "for Dummies" site!
goodintentions said:
(3) You have brickage. You've bricked your gtab. You need to follow my code red to get out of brickary.
Click to expand...
Click to collapse
I bricked my gtab good, but [code red] pulled me thru. GRACIAS!
"OMG THIS IS SO GREAT!"
"WOW! YOU ROCK AND I WANT TO HAVE YOUR BABIES!"
"THIS IS THE BEST THING EVER!"
"THANKS FOR THIS!"
You saved my a$$.
Thank you SO much
goodintentions said:
(1) I'll change my website to your words. Thanks for the advice.
(2) This is the way I talk in real life all the time. I've been described as the king of sarcasm. My "girl friend" is a therapist. She's working with me on this issue.
(3) You have brickage. You've bricked your gtab. You need to follow my code red to get out of brickary.
Added by edit.
You should have seen the original version of my site. It sounded exactly like me in real life. After some emails suggesting I change a few things before I face a class action lawsuit for upsetting a whole class of people (mainly dummies) I started doing some major overhauls based on their suggestions.
Click to expand...
Click to collapse
THANK YOU!
Thank you thank you thank you thank you.
I can't say thank you enough for your awesome work.
I've created many step-by-step tutorials for dummies on other subjects, so I know it's very time consuming, etc.
Thank you SO much.
my boss bought us new g tablets to use for work, and i brick it the same day i got it!
your code red procedure just saved my butt.
(now, going to try flashing cyanogenMod again! lol)
*edit*
*edit2*
i guess i wasnt holding down the volume button long enough.
once i held it down longer, recovery mode started ok.
i think i have bricked mine new P 7500
but there is nothing wrong i did with this device
tab is now in only conecting in APX
NVIDIA USB Boot-recovery driver for Mobile devices
no sign of charging and no light on display
is there any way to recover it back??????????
What exactly did you do? Nothing? You did try to hold the power button for 15 seconds, right?
yes exactly
when no luck in powering on
is this hard bricked on semi??
do i need Jtag for this??????
What did you try to do that caused this problem?
trying rooting
messed up with commands
so my tab is bricked ???????????????
If you really want some help from here, you'd better exactly describe (step by step) what you were doing when things went wrong. Fisrt post you say you did nothing wrong, 6th post you say you messed up commands. I would be jumpy too if my tab was bricked, but your short replies don't add to the possible solution.
a very good answer
thanks
but i have messed up with commands now
not while it was working fine
when nothing happened nothing shown on screen
then i started using commans of those rooting procedure mentioned in devlepment forum for 10.1
all i wanted to reboot it with commands
so i thought may be i have done something wrong with commands
thats why i wrote now that
messed up with commands now
only obove mentioned device is shown on my device manager
thats all happened
Ok, so we have apx mode for stock GT-P7500. I thougt that only was for that Google I/O version. But then you should be able to nvflash a firmmware on to your tab. APX mode is the same as nvflash. Do a search for NVflash on the tab and see if you come up with answers. Good luck
And by the way, whhat kind of rooting process where you doing? you should just download the root zip and flash thru stock recovery
Edit: Heres a link that might help http://forum.xda-developers.com/showthread.php?t=1130574
yes i was trying rooting exactly this procedure
http://forum.xda-developers.com/showthread.php?t=1130574
ok i have nvflash command software and stock firmware too
but the problem is, my tab does'nt recognised by odin
then how to flash it
thanks for your help but would you plz tell me how can i flash in apx mode??
Im not sure how its done on Galaxy tab. but in the download package there should be all that is needed for nvflash and you should ad the .img files for system and boot and recovery of the firmware version you want. And there should be a .bat file in the package i think. you should run it from there. But you need to google and collect info about this yourself as i have not done this myself on the Tab. Good Luck
can you boot into recovery? ! Holding volume down and power at the same time?
attu90 said:
can you boot into recovery? ! Holding volume down and power at the same time?
Click to expand...
Click to collapse
no not at all
wish it could boot in recovery so that i would able to install stock from odin
only black screen while apx found in device manager
nickwarn said:
Im not sure how its done on Galaxy tab. but in the download package there should be all that is needed for nvflash and you should ad the .img files for system and boot and recovery of the firmware version you want. And there should be a .bat file in the package i think. you should run it from there. But you need to google and collect info about this yourself as i have not done this myself on the Tab. Good Luck
Click to expand...
Click to collapse
thanks for your answer i have stock firmware
but its tar file not img file
searched on google too
how to flash firmware using nvflash
but could'nt found any useful post
all flash procedures on google are with odin or hemdell
still looking for help
ok after reading lot of pages
its clear that mine is not completly bricked
hope it will alive again
Sheeda Talli said:
ok after reading lot of pages
its clear that mine is not completly bricked
hope it will alive again
Click to expand...
Click to collapse
Good luck, go to this place and ask for help. http://tabletroms.com/forums/forum.php#major-devices-android They have very good guys for nvflash on other devices. And as nvflash is something within tegra2 it should be the same rules that apply for our TAB. Check in Asuus Transformer forum.
well i have checked that forum too
and there are only 10 or 15 threads in every section of samsung 10.1
it clearly shows repo of that forum
anyway i have posted there too, thanks for your advise
no one can ??????????
No luck? If i were you i would PM one of the Devs and see if one of them is in a good mood.
Edit: I was thinking, the nvflash mode is nothing to do with Samsung. Its a tegra2 thing so you should be able to follw the guide from Transformer forum. Just put Tab .img files in there. because the one for Transformer(nvflash package) comes with a .bat file that runs the install process. it goes thru all partions and installs all .img files. but you need to chek with the Dev for Transformer so that there is no partion map for Transformer or something in there.
Is anyone working on a way to use nvflash to go back to an original firmware (like what was available for many tegra 2 devices)?
The reason I ask is I have a prime that won't boot but is apparently stuck in APX mode. It shows up in my windows device manager as APX. No matter what button combination / time press combination I try, I can't get it to boot. It came this way out of the box, it never once has booted. The charge LED's in the power button work and I can feel it vibe when I hold the power button for a few sec. I also get a long vibe after holding the power button for 10 or 15 sec. Sometimes it shows up in the device manager as MTP device, but I can't get it to take the asus drivers. I always get an error saying the device could not be started.
It looks like there is a nvflash that supports tegra 3 floating around (but only for linux) and the official firmwares are available on the asus website. I have never used nvflash and don't have linux installed, but I'm going to try booting off an ubuntu live CD and see what I can figure out.
look in the Prime Android developement section. answers to your questions are in there as people working on that right now. there's a thread on what u mentioned.
unxconformed said:
Is anyone working on a way to use nvflash to go back to an original firmware (like what was available for many tegra 2 devices)?
The reason I ask is I have a prime that won't boot but is apparently stuck in APX mode. It shows up in my windows device manager as APX. No matter what button combination / time press combination I try, I can't get it to boot. It came this way out of the box, it never once has booted. The charge LED's in the power button work and I can feel it vibe when I hold the power button for a few sec. I also get a long vibe after holding the power button for 10 or 15 sec. Sometimes it shows up in the device manager as MTP device, but I can't get it to take the asus drivers. I always get an error saying the device could not be started.
It looks like there is a nvflash that supports tegra 3 floating around (but only for linux) and the official firmwares are available on the asus website. I have never used nvflash and don't have linux installed, but I'm going to try booting off an ubuntu live CD and see what I can figure out.
Click to expand...
Click to collapse
my advice to you, dont even TOUCH NVFLASH.
if you don't know how to use the search button, dear god, you don't know how to use nvflash. its difficult, and i finally have a solid grip on it.. and i AM a dev
biggem001 said:
my advice to you, dont even TOUCH NVFLASH.
if you don't know how to use the search button, dear god, you don't know how to use nvflash. its difficult, and i finally have a solid grip on it.. and i AM a dev
Click to expand...
Click to collapse
You don't need to be so hostile, this is a friendly forum.
I've seen the thread in the dev section on nvflash. After page 2 the whole thread devolved into people rambling about trying to brute force the encryption key for the bootloader. The only person who had the linux build of nvflash that had tegra 3 support was already pm'd before posting here. Since that thread fell apart into people trying to figure out a way around the encryption key, I figured I'd ask if anyone was looking into flashing original firmware and not modified or rootable firmware. Since I had nothing to contribute yet, I put it in general and not in development.
The part I didn't understand is if flashing an original ASUS firmware was not possible with bootloader encryption.
unxconformed said:
You don't need to be so hostile, this is a friendly forum.
I've seen the thread in the dev section on nvflash. After page 2 the whole thread devolved into people rambling about trying to brute force the encryption key for the bootloader. The only person who had the linux build of nvflash that had tegra 3 support was already pm'd before posting here. Since that thread fell apart into people trying to figure out a way around the encryption key, I figured I'd ask if anyone was looking into flashing original firmware and not modified or rootable firmware. Since I had nothing to contribute yet, I put it in general and not in development.
Click to expand...
Click to collapse
Um maybe that's because you can't use the nvflash without the unlocked bootloader
Sent from my Inspire 4G with ICS!
dsmitty166 said:
Um maybe that's because you can't use the nvflash without the unlocked bootloader
Sent from my Inspire 4G with ICS!
Click to expand...
Click to collapse
Ok, well that is part I wasn't aware of. I wasn't sure if the it was similar to my HTC devices that had locked bootloaders but could be flashed with official firmwares using a zip on the SD. I realized the nvflash method was entirely different but I didn't know if the firmwares that asus provides on their site had the key in them and were possibly usable. But it sounds like that isn't the case.
unxconformed said:
Ok, well that is part I wasn't aware of. I wasn't sure if the it was similar to my HTC devices that had locked bootloaders but could be flashed with official firmwares using a zip on the SD. I realized the nvflash method was entirely different but I didn't know if the firmwares that asus provides on their site had the key in them and were possibly usable. But it sounds like that isn't the case.
Click to expand...
Click to collapse
Unfortunatly, we are at the mercy of Asus right now...
Hello everyone,
I was trying to launch fastboot but instead of that (I'm not the smartest I guess), I did a full destroy of the system (I think I pressed the power button more than 3 times then got a message telling me to press POW+VOL DOWN to destroy the system, which I did )
Now, when I try to start the tablet, I get nothing but a the red button on. Under windows, it's not detected and the drivers don't install, all I have is :
"other devices ==> APX" in my device manager.
Can someone help me revive the tablet (if it's still possible)?
Thanks!!!
Josefon said:
Hello everyone,
I was trying to launch fastboot but instead of that (I'm not the smartest I guess), I did a full destroy of the system (I think I pressed the power button more than 3 times then got a message telling me to press POW+VOL DOWN to destroy the system, which I did )
Now, when I try to start the tablet, I get nothing but a the red button on. Under windows, it's not detected and the drivers don't install, all I have is :
"other devices ==> APX" in my device manager.
Can someone help me revive the tablet (if it's still possible)?
Thanks!!!
Click to expand...
Click to collapse
Same happened to me and I panicked. I solved it with this guide
http://forum.xda-developers.com/showthread.php?t=1458876
After that, you can do all the necessary pugrades, etc, for CM10 A4 and get your folio working again
yellowumbrella said:
Same happened to me and I panicked. I solved it with this guide
http://forum.xda-developers.com/showthread.php?t=1458876
After that, you can do all the necessary pugrades, etc, for CM10 A4 and get your folio working again
Click to expand...
Click to collapse
Thanks for your help, I have read the whole post and have managed to revive the tablet thanks to NVflash. I used the 16g version as the tablet is a 16g, but I'm stuck to CWM v0.3 and it seems there's nothing I can install under there. Where did you go from there, did you use fastboot to load another rom? Nothing will install under CWM which is making me confused...
Thanks again for your help!!
Josefon said:
Thanks for your help, I have read the whole post and have managed to revive the tablet thanks to NVflash. I used the 16g version as the tablet is a 16g, but I'm stuck to CWM v0.3 and it seems there's nothing I can install under there. Where did you go from there, did you use fastboot to load another rom? Nothing will install under CWM which is making me confused...
Thanks again for your help!!
Click to expand...
Click to collapse
As long as your tablet is out of APX, you should be able to just go ahead and follow this
http://forum.xda-developers.com/showthread.php?t=1864774
to get updated to the latest CM10
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
uberiyer1 said:
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
Click to expand...
Click to collapse
If you can reboot into the bootloader again, it might be worth it to try the same commands, but with the boot.img pulled from 14.3.2.2.
S_transform said:
... but with the boot.img pulled from 14.3.2.2.
Click to expand...
Click to collapse
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
tl3 said:
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
Click to expand...
Click to collapse
I was not aware, thanks for the heads up!
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
how can you help fix with a fastboot cable??
jjrizzelcincy said:
how can you help fix with a fastboot cable??
Click to expand...
Click to collapse
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
jjrizzelcincy said:
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
Click to expand...
Click to collapse
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
jjrizzelcincy said:
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
Click to expand...
Click to collapse
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry for the trouble.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry. For the trouble.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
NOPE you are stuck helping me now lol
jjrizzelcincy said:
NOPE you are stuck helping me now lol
Click to expand...
Click to collapse
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
the only way i see a fix for mine since the fastboot cable did not help me get into fastboot mode is if we some how manage to get some devs over here which seems unlikely at this point but i still have hope one falls on a devs lap sometime soon