I installed the root, then delete important system applications, and got brick device. Inscription appears only when loading "Kindle". Is there any way via fastboot (adb) to flash the stock firmware 13.3.1 (HDX 7")?
Sorry for my bad English.
I have same problem, we hope that you can solve
Have you tried factory reset via adb? It should work. http://forum.xda-developers.com/showthread.php?t=2530623
johnnydowngrief said:
Have you tried factory reset via adb? It should work. http://forum.xda-developers.com/showthread.php?t=2530623
Click to expand...
Click to collapse
does not work because getting stuck on the word "kindle fire" adb does not work for me most of installing the following drivers: http://i.imgur.com/jxq9EKI.png but does not work
sorry for by bad english t.t
This was a big problem with the last gen device. you will not be able unbrick your device until you get a backup of the system img then flash it through fastboot. or you could possibly pull a system image from the update.bin file from amazons kindle software page. I am downloading it now but do not own this device yet so no way of testing it. Also not sure if you can use a factory cable to get into fastboot on this model. anyone know or done this?
onemeila said:
This was a big problem with the last gen device. you will not be able unbrick your device until you get a backup of the system img then flash it through fastboot. or you could possibly pull a system image from the update.bin file from amazons kindle software page. I am downloading it now but do not own this device yet so no way of testing it. Also not sure if you can use a factory cable to get into fastboot on this model. anyone know or done this?
Click to expand...
Click to collapse
I'm bricked as well. The problem was that I got into recovery mode and did factory reset which was a bad idea. It totally killed adb and now I can't get pc to recognize at all. Therefore do no recommend factory reset to others.I have ordered the factory cable from the previous KF HD and will test to see if that works. If so I'll need someone to get a system.img to flash though.
I just talked to an amazon rep and will be sent a replacement. I wonder if they will notice it was rooted.
Does anyone know if an unrooted HDX will brick on factory reset and latest firmware?
Moronig said:
I just talked to an amazon rep and will be sent a replacement. I wonder if they will notice it was rooted.
Does anyone know if an unrooted HDX will brick on factory reset and latest firmware?
Click to expand...
Click to collapse
I will try and recover first as an experiment to also help others having same issues. Otherwise if I can't recover I'll contact Amazon as well.
Sent from my Nexus 5 using Tapatalk
Android Cowboy said:
I will try and recover first as an experiment to also help others having same issues. Otherwise if I can't recover I'll contact Amazon as well.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My brother has the hdx7. Ill see if I can pull a system.img from it when I see him. possibly tom. I'll pm you if I manage to get it done.
onemeila said:
My brother has the hdx7. Ill see if I can pull a system.img from it when I see him. possibly tom. I'll pm you if I manage to get it done.
Click to expand...
Click to collapse
Thanks. I'll work on getting ADB to recognize for now.
Android Cowboy said:
I will try and recover first as an experiment to also help others having same issues. Otherwise if I can't recover I'll contact Amazon as well.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The funny thing is that I deleted all apps I installed in /system/app before trying the factory reset (except superuser.apk and the su binary in /system/xbin. I had installed busybox before, so I'm suspecting that was what caused the problem with the factory reset. A different fdisk or something than the reset script expected... or maybe it does a checksum of some sort on the system partition and bricks it if it's not as expected?
Moronig said:
I just talked to an amazon rep and will be sent a replacement. I wonder if they will notice it was rooted.
Does anyone know if an unrooted HDX will brick on factory reset and latest firmware?
Click to expand...
Click to collapse
Amazon says they won't send me a replacement, so I'll see what else I can try. Let me know if you discover anything.
Moronig said:
Amazon says they won't send me a replacement, so I'll see what else I can try. Let me know if you discover anything.
Click to expand...
Click to collapse
I got one from the Amazon Ads free tablet promotion, and apparently i get no warrenty because it was a "gift". I'll order a factory cable and try poking around in fastboot. Has anyone tried a factory cable yet?
JordanRulz said:
I got one from the Amazon Ads free tablet promotion, and apparently i get no warrenty because it was a "gift". I'll order a factory cable and try poking around in fastboot. Has anyone tried a factory cable yet?
Click to expand...
Click to collapse
I don't think anyone has tried it, I'll try to find a cable I can cut and make one next week. I haven't had much experience with fastboot before, though. Should we be able to flash the /system partition from the latest update image?
Moronig said:
Amazon says they won't send me a replacement, so I'll see what else I can try. Let me know if you discover anything.
Click to expand...
Click to collapse
Why wouldn't they send you a replacement? Did you tell them it bricked while you were trying to root?
Major General said:
Why wouldn't they send you a replacement? Did you tell them it bricked while you were trying to root?
Click to expand...
Click to collapse
No, because I'm in Brazil and they don't sell this model of the Kindle to Brazil. I might try to get them to ship the replacement to my brother in the US.
Moronig said:
I don't think anyone has tried it, I'll try to find a cable I can cut and make one next week. I haven't had much experience with fastboot before, though. Should we be able to flash the /system partition from the latest update image?
Click to expand...
Click to collapse
I have a factory cable that I bought for kindle hd when i bricked that unit but sent the hd back before i ever used it.
I just powered off hdx 7 and plugged in cable but powers on as normal and its charging unit. Mine is rooted with google play not working of course..Is it suppose to boot into fastboot?
davekaz said:
I have a factory cable that I bought for kindle hd when i bricked that unit but sent the hd back before i ever used it.
I just powered off hdx 7 and plugged in cable but powers on as normal and its charging unit. Mine is rooted with google play not working of course..Is it suppose to boot into fastboot?
Click to expand...
Click to collapse
I thought so. Maybe if you hold either volume up, volume down, or both when plugging the cable?
Moronig said:
I thought so. Maybe if you hold either volume up, volume down, or both when plugging the cable?
Click to expand...
Click to collapse
I had wrong cable in sorry..I powered off kindle and plugged correct cable in and windows 7 asked for QHSUSB driver.and kindle stayed off as far as screen is concerned.I hunted down driver http://forum.xda-developers.com/showthread.php?t=1468791 I didnt try fastboot yet as I have a few things to do..Let me know if i could help as android cowboy is in same predicament and would like to help. After unplugged kindle boots up as normal after holding power for awhile
davekaz said:
I had wrong cable in sorry..I powered off kindle and plugged correct cable in and windows 7 asked for QHSUSB driver.and kindle stayed off as far as screen is concerned.I hunted down driver http://forum.xda-developers.com/showthread.php?t=1468791 I didnt try fastboot yet as I have a few things to do..Let me know if i could help as android cowboy is in same predicament and would like to help. After unplugged kindle boots up as normal after holding power for awhile
Click to expand...
Click to collapse
I will have the fastboot cable by tomorrow or Tuesday. Then I can test on my bricked Kindle if it goes into fastboot and if I still have root.
Sent from my Nexus 5 using Tapatalk
Related
I tried rooted my next book premium 8 and then it give me a error message said couldn't find the picture then turned off i charge it the try turned it on and nothing it wont turn on also i tried rest ,power+vol nothing happen it drive me crazy so pleeeeeeeeeeeeeease
what Should i do ? :crying: :crying: :crying:
wapp said:
I tried rooted my next book premium 8 and then it give me a error message said couldn't find the picture then turned off i charge it the try turned it on and nothing it wont turn on also i tried rest ,power+vol nothing happen it drive me crazy so pleeeeeeeeeeeeeease
what Should i do ? :crying: :crying: :crying:
Click to expand...
Click to collapse
First off try doing a battery pull and seeing if turns on after you've done that. Also what guide did you follow to try and root your device because if you show me what guide you tried using I might be able to figure out what you did wrong.
thank you shimp208
i tried doing a battery pull but nothing change.
about the
what guide did you follow to try and root your device because if you show me what guide you tried using I might be able to figure out what you did wrong.
Click to expand...
Click to collapse
this is the link i get the guide from i hope you can find a way to help me after looking at it
http://forum.xda-developers.com/showthread.php?t=1374742
any Suggestions :crying:
Hey, I have the same problem, have you found a solution yet?
FrOz3n said:
Hey, I have the same problem, have you found a solution yet?
Click to expand...
Click to collapse
Just so I can try and keep the details of your problem straight just like wapp the rooting procedure didn't complete successfully and now the device doesn't power on at all?
shimp208 said:
Just so I can try and keep the details of your problem straight just like wapp the rooting procedure didn't complete successfully and now the device doesn't power on at all?
Click to expand...
Click to collapse
Exactly! I can't get it into flash mode too. All that works is the LED.. I connect the charger it does nothing. Tried connecting the usb, still no luck. Can't turn the tablet on. Can't get into recovery mod. Can't get into flash mode (the state I need to flash stock firmware with RKAndroidTool.exe)
FrOz3n said:
Exactly! I can't get it into flash mode too. All that works is the LED.. I connect the charger it does nothing. Tried connecting the usb, still no luck. Can't turn the tablet on. Can't get into recovery mod. Can't get into flash mode (the state I need to flash stock firmware with RKAndroidTool.exe)
Click to expand...
Click to collapse
If the LED still works that's at least a sign that the tablet isn't completely bricked. Have you installed the USB drivers for your tablet?
shimp208 said:
If the LED still works that's at least a sign that the tablet isn't completely bricked. Have you installed the USB drivers for your tablet?
Click to expand...
Click to collapse
Yes, successfully rooted before. But then I got to stock, and on the next root try i got that...
FrOz3n said:
Yes, successfully rooted before. But then I got to stock, and on the next root try i got that...
Click to expand...
Click to collapse
Unfortunately if you can't even get in to flash mode, then warranty may be your only option I'm afraid. No matter what you try driver wise, different computer, different usb port, you can't access flash mode?
shimp208 said:
Unfortunately if you can't even get in to flash mode, then warranty may be your only option I'm afraid. No matter what you try driver wise, different computer, different usb port, you can't access flash mode?
Click to expand...
Click to collapse
Yeah I tried on my 3 PCs and the laptop, can't get nothing...
FrOz3n said:
Yeah I tried on my 3 PCs and the laptop, can't get nothing...
Click to expand...
Click to collapse
The other option besides warranty would be to take it to a repair center and see what they can do.
shimp208 said:
The other option besides warranty would be to take it to a repair center and see what they can do.
Click to expand...
Click to collapse
Ok, thanks for the support, I'm gonna try with the warranty today I just can't accept that it's a brick... I have flashed my android phones over 200+ times with different kernels/ROMs etc... and none of them bricked ... But that's it... Can't get the tablet to start :S
Thanks again.
It got bricked after trying to update through FLASHER 2.1 The ADB Shell on Sony AIO Tool not work. Option 6 Run Shell does nothing. Tablet gets stuck on the S.O.N.Y logo and I can enter the recovery screen, however no access through the USB to my files, already try the factory reset and still nothing. I would even consider installing the official firmware even if a lose root. I don't have the_hack_recovery.zip or any key. What can I do? I've been looking for solutions for over two days now.
I tried running the signed-nbx03_016-ota-120803071.zip and it didn't work, I'm looking everywhere for the signed-nbx03_001-ota-120803002.zip which should work for me, since my tablet was bought in the U.S. but it isn't available anywhere. I can't access the tablet through the ADB Shell, I press option 6 on the main menu and it does nothing. When I'm in the recovery mode I can see windows asking for drivers for a device named Sony, but none of the adb drivers work. If I go to the Sony logo I have it recognizes the MTP USB device and it looks ok for about 40 sec. and then it puts the yellow exclamation mark. I really need to get this tablet fix,
I'm willing to donate $40.00 through paypal to the person that helps me restore it.
You have to reinstall your firmware and wipe ure tab there is a thread on here that has all firmware from every country
Sent from my LT28i using xda app-developers app
psxpetey said:
You have to reinstall your firmware and wipe ure tab there is a thread on here that has all firmware from every country
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply, I already tried it with all the U.S. firmwares available in that threat. The one I think should work is the signed-nbx03_001-ota-120803002.zip and I can't find it anywhere.
elwarriorpr said:
It got bricked after trying to update through FLASHER 2.1 The ADB Shell on Sony AIO Tool not work. Option 6 Run Shell does nothing. Tablet gets stuck on the S.O.N.Y logo and I can enter the recovery screen, however no access through the USB to my files, already try the factory reset and still nothing. I would even consider installing the official firmware even if a lose root. I don't have the_hack_recovery.zip or any key. What can I do? I've been looking for solutions for over two days now.
I tried running the signed-nbx03_016-ota-120803071.zip and it didn't work, I'm looking everywhere for the signed-nbx03_001-ota-120803002.zip which should work for me, since my tablet was bought in the U.S. but it isn't available anywhere. I can't access the tablet through the ADB Shell, I press option 6 on the main menu and it does nothing. When I'm in the recovery mode I can see windows asking for drivers for a device named Sony, but none of the adb drivers work. If I go to the Sony logo I have it recognizes the MTP USB device and it looks ok for about 40 sec. and then it puts the yellow exclamation mark. I really need to get this tablet fix,
I'm willing to donate $40.00 through paypal to the person that helps me restore it.
Click to expand...
Click to collapse
I am uploading that file as i type. Since you have done a factory reset..... USB debugging would have reset to default (off) so even if you manage to install the drivers, USB debugging will NOT work.
I had the same (well similar) issue, it was stuck on the boot animation and although it was caused by different things I could not fix it and had to send it to Sony. Good news though, they did not noo I messed with it and repaired it free and IT SHOULD BE BACK TODAY
I feel this file is your only hope. I will reply when I have the link
Stifilz
Edit: Upload complete see here
DEL
stifilz said:
I am uploading that file as i type. Since you have done a factory reset..... USB debugging would have reset to default (off) so even if you manage to install the drivers, USB debugging will NOT work.
I had the same (well similar) issue, it was stuck on the boot animation and although it was caused by different things I could not fix it and had to send it to Sony. Good news though, they did not noo I messed with it and repaired it free and IT SHOULD BE BACK TODAY
I feel this file is your only hope. I will reply when I have the link
Stifilz
Edit: Upload complete see here
Click to expand...
Click to collapse
Thanks for your reply and for uploading the firmware. Unfortunately it didn't work either, I'll have to call sony and see if they can fix it for me. :crying: +Rep for the upload
elwarriorpr said:
Thanks for your reply and for uploading the firmware. Unfortunately it didn't work either, I'll have to call sony and see if they can fix it for me. :crying: +Rep for the upload
Click to expand...
Click to collapse
Sad to hear that. Do a couple of resets before you send in to Sony
elwarriorpr said:
Thanks for your reply and for uploading the firmware. Unfortunately it didn't work either, I'll have to call sony and see if they can fix it for me. :crying: +Rep for the upload
Click to expand...
Click to collapse
Just send to Sony, others have no ideas.
I also bricked it, and Sony restored it through motherboard replacing(free).
---------- Post added at 02:01 AM ---------- Previous post was at 01:57 AM ----------
stifilz said:
I am uploading that file as i type. Since you have done a factory reset..... USB debugging would have reset to default (off) so even if you manage to install the drivers, USB debugging will NOT work.
I had the same (well similar) issue, it was stuck on the boot animation and although it was caused by different things I could not fix it and had to send it to Sony. Good news though, they did not noo I messed with it and repaired it free and IT SHOULD BE BACK TODAY
I feel this file is your only hope. I will reply when I have the link
Stifilz
Edit: Upload complete see here
Click to expand...
Click to collapse
YES, only Sony can fix it.
I also faced the similar trouble one month ago.
And they free for me to replace the motherboard without any inquiries but my device's situations.
When they asked what I did, I said, nothing was done just suddenly can not boot, and force to restore the factory can't be solved the problem in the recovery mode. Okay! They said, just waiting less than 3 days. 3 days later, they sent a text message, and told me to pick up Tablet.
But a little guilt in my heart because I rooted my device and deleted a system file without rescue-backdoor.
I and many others who have changed build.prop or other modifications after root then bricked have found that factory reset is the worst thing to do. It completely removed the PC from recognizing the tablet and ADB no longer works in any manner. Which pretty much means a total brick device. There is no real way to recover at the moment but if you have bricked with root then ADB should still be working. That still leaves some hope to fix the original damage. I have pulled the Amazon bin file and have access to original build.prop and system apk. That might allow some way to reverse the damage. I also have a fastboot cable coming to test if HDX will get into fastboot. For now hold off on any modifications after root since there is no real way to recover. But if you brick definitely don't factory reset.
Android Cowboy said:
I and many others who have changed build.prop or other modifications after root then bricked have found that factory reset is the worst thing to do. It completely removed the PC from recognizing the tablet and ADB no longer works in any manner. Which pretty much means a total brick device. There is no real way to recover at the moment but if you have bricked with root then ADB should still be working. That still leaves some hope to fix the original damage. I have pulled the Amazon bin file and have access to original build.prop and system apk. That might allow some way to reverse the damage. I also have a fastboot cable coming to test if HDX will get into fastboot. For now hold off on any modifications after root since there is no real way to recover. But if you brick definitely don't factory reset.
Click to expand...
Click to collapse
In Fastboot, It would be possible to recover if someone were to pull the system image and post it here on XDA.
r3pwn said:
In Fastboot, It would be possible to recover if someone were to pull the system image and post it here on XDA.
Click to expand...
Click to collapse
Yeah, we are desperate need of system image. I have the fastboot cable coming and new KF HDX being sent. If it's not done I should have it in a couple of days.
Android Cowboy said:
Yeah, we are desperate need of system image. I have the fastboot cable coming and new KF HDX being sent. If it's not done I should have it in a couple of days.
Click to expand...
Click to collapse
Has any progress been made on this? Unfortunately I didn't see your post until it was to late. Any assistance/advice would be much appreciated.
hi android cowboy plz help me
Android Cowboy said:
I and many others who have changed build.prop or other modifications after root then bricked have found that factory reset is the worst thing to do. It completely removed the PC from recognizing the tablet and ADB no longer works in any manner. Which pretty much means a total brick device. There is no real way to recover at the moment but if you have bricked with root then ADB should still be working. That still leaves some hope to fix the original damage. I have pulled the Amazon bin file and have access to original build.prop and system apk. That might allow some way to reverse the damage. I also have a fastboot cable coming to test if HDX will get into fastboot. For now hold off on any modifications after root since there is no real way to recover. But if you brick definitely don't factory reset.
Click to expand...
Click to collapse
My kindle hdx7" is bricked yesterday now only showing kindle fire boot logo so i have connected my laptop use factory.cable but not recognized my device would you help me? Sorry my poor english
bricked as well
cjdfyd2 said:
My kindle hdx7" is bricked yesterday now only showing kindle fire boot logo so i have connected my laptop use factory.cable but not recognized my device would you help me? Sorry my poor english
Click to expand...
Click to collapse
Same here Most likely going to return it which I really would rather not . But I went too far on that new Google play hack and it just booted up to welcome screen for google and never connected to servers and rebooted
after awhile.I did this on stock rom(bad bad) thinking it would be fine. Of course i reset to factory which everyone warned. Now just grey kindle logo and cable( Factory and non) to pc pulls up unrecognized usb that windows stopped from starting Done deal screwed im sure
davekaz said:
Same here Most likely going to return it which I really would rather not . But I went too far on that new Google play hack and it just booted up to welcome screen for google and never connected to servers and rebooted
after awhile.I did this on stock rom(bad bad) thinking it would be fine. Of course i reset to factory which everyone warned. Now just grey kindle logo and cable( Factory and non) to pc pulls up unrecognized usb that windows stopped from starting Done deal screwed im sure
Click to expand...
Click to collapse
I don't think anyone has figured out a recovery from this kind of brick. Safestrap is now the way to go. I had to get a replacement myself.
Sent from my Nexus 7 using Tapatalk
Android Cowboy said:
I don't think anyone has figured out a recovery from this kind of brick. Safestrap is now the way to go. I had to get a replacement myself.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Did the fastboot cable you ordered do anything?
daveman2123 said:
Did the fastboot cable you ordered do anything?
Click to expand...
Click to collapse
No I didn't have much luck with that either.
Sent from my Nexus 7 using Tapatalk
daveman2123 said:
Did the fastboot cable you ordered do anything?
Click to expand...
Click to collapse
it comes up as unrecognized usb device which windows stops
did you your device unbrick succese?
davekaz said:
it comes up as unrecognized usb device which windows stops
Click to expand...
Click to collapse
I had known your device.is.beicked right? Now yor device unbricked?
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
Is there any hope? I was trying to install LiquidSmooth Jellybean 4.1.2 RC8. I did a backup of the stock ROM before doing so using CWM 6.0. But now it won't even go into download mode. I plug it in via USB as the screen won't even turn on and it keeps flashing that it's plugged in, then it's not, then it is, etc.
I had used the files from AndroidJinn without reading the reviews at the bottom.
How screwed am I?
MoronDroid said:
Is there any hope? I was trying to install LiquidSmooth Jellybean 4.1.2 RC8. I did a backup of the stock ROM before doing so using CWM 6.0. But now it won't even go into download mode. I plug it in via USB as the screen won't even turn on and it keeps flashing that it's plugged in, then it's not, then it is, etc.
I had used the files from AndroidJinn without reading the reviews at the bottom.
How screwed am I?
Click to expand...
Click to collapse
How did you try to get into download mode? Power+volume down and then releasing the power button while still holding volume down?
Edit: Maybe this post will be helpful?
http://forum.xda-developers.com/showthread.php?p=24539068
Sent from my SAMSUNG-SGH-I717
developweb said:
How did you try to get into download mode? Power+volume down and then releasing the power button while still holding volume down?
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Yes, won't even do that. No samsung boot logo either.
developweb said:
How did you try to get into download mode? Power+volume down and then releasing the power button while still holding volume down?
Edit: Maybe this post will be helpful?
http://forum.xda-developers.com/showthread.php?p=24539068
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
I'm facing quite the hard brick. $1.60 for a jig won't kill me, now to buy it. But is there anything else I can try?
I would try to find out exactly what caused this before attempting to fix it. Has the recovery that you used been reliable and tested enough to ensure it didn't cause any troubles? I compiled twrp for this device and I can tell you that recovery is a pain to build correctly.
gimmeitorilltell said:
I would try to find out exactly what caused this before attempting to fix it. Has the recovery that you used been reliable and tested enough to ensure it didn't cause any troubles? I compiled twrp for this device and I can tell you that recovery is a pain to build correctly.
Click to expand...
Click to collapse
Yes it has. Haven't had issues yet. But it happened specifically with this ROM, and the page is full of brick warnings. Not even the samsung logo comes up. Booting to recovery or download doesn't work.
MoronDroid said:
Yes it has. Haven't had issues yet. But it happened specifically with this ROM, and the page is full of brick warnings. Not even the samsung logo comes up. Booting to recovery or download doesn't work.
Click to expand...
Click to collapse
I hope you can work it out. With my own I have not had any major problems to troubleshoot. Mostly things that a battery pull or an odin flash could fix. Although I have had a couple times that I was unable to get into recovery and simply removing my otterbox and retrying did the trick. ( Buttons getting worn out on the otterbox cover? )
Sent from my SAMSUNG-SGH-I717
developweb said:
I hope you can work it out. With my own I have not had any major problems to troubleshoot. Mostly things that a battery pull or an odin flash could fix. Although I have had a couple times that I was unable to get into recovery and simply removing my otterbox and retrying did the trick. ( Buttons getting worn out on the otterbox cover? )
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
I just want to let you know, for the sake of your galaxy note, do NOT flash the 4.1.2 Liquidsmooth Jellybean RC8 ROM from the androidjinn site. It permabricks phones, down to the recovery, and even blocks download mode.
MoronDroid said:
Yes it has. Haven't had issues yet. But it happened specifically with this ROM, and the page is full of brick warnings. Not even the samsung logo comes up. Booting to recovery or download doesn't work.
Click to expand...
Click to collapse
plug it into the computer and see what it is enumerated as in the device manager.. if it shows up as "Qualcomm HS-USB QDLoader" .. youre hard bricked . I have a riff box if you need a JTAG
sinasiadat said:
plug it into the computer and see what it is enumerated as in the device manager.. if it shows up as "Qualcomm HS-USB QDLoader" .. youre hard bricked . I have a riff box if you need a JTAG
Click to expand...
Click to collapse
It appears as Qualcomm CDMA Technologies MSM. Close enough. Lol.
Have you done jtag repairs on these before?
MoronDroid said:
It appears as Qualcomm CDMA Technologies MSM. Close enough. Lol.
Have you done jtag repairs on these before?
Click to expand...
Click to collapse
yea.. a couple. I own one. and have the i717 jig for the riff box so it snaps on no soldering
sinasiadat said:
yea.. a couple. I own one. and have the i717 jig for the riff box so it snaps on no soldering
Click to expand...
Click to collapse
I'm tempted to send it to you. I've been using a semi-broken droid 3 for a while.
I'll send you a private message.