Hey guys
I got root, but then I changed the build prop to the one given in this thread: http://forum.xda-developers.com/showthread.php?t=2782159
However it didn't boot properly,i.e. only the grey logo showed up, then black screen. No bootloop.
Then I thought factory reset would fix it?
no. now the pc doesn't recognise it. Please help! Same grey logo stuff but no PC recognition.
Edit:
No luck yet, but I remember a way I did before.It's not quite the same situation but...
I left the kindle on for a long time, and pressed the power button beyond the point from where it showed out of battery screen. It had like no batterypower at ALL. Yhen i plugged back up to PC and...
I'm trying it out now, if anyone is in the same position as me do the same!
Remember,charge only about 1-2%,if it doesn't work!
Thank you guys a LOT for support! I am in process of getting adb and stuff to work on linux...
let's see how it goes...
ferrouskid said:
Hey guys
I got root, but then I changed the build prop to the one given in this thread: http://forum.xda-developers.com/showthread.php?t=2782159
However it didn't boot properly,i.e. only the grey logo showed up, then black screen. No bootloop.
Then I thought factory reset would fix it?
no. now the pc doesn't recognise it. Please help! Same grey logo stuff but no PC recognition.
Click to expand...
Click to collapse
Does adb work ?
Patrick4 said:
Does adb work ?
Click to expand...
Click to collapse
No, unfortunately!
Patrick4 said:
Does adb work ?
Click to expand...
Click to collapse
No,
well
ferrouskid said:
No,
Click to expand...
Click to collapse
That sucks..I didnt try to swap my whole prop build though.. I just modified my mine..I did it with rommanager lite...I do remember a permission problem if u did swap files or used file manager instead of propbuild editer...has any one got brave enough to try the fastboot option one row under the root option in chinese app?
jimyv said:
That sucks..I didnt try to swap my whole prop build though.. I just modified my mine..I did it with rommanager lite...I do remember a permission problem if u did swap files or used file manager instead of propbuild editer...has any one got brave enough to try the fastboot option one row under the root option in chinese app?
Click to expand...
Click to collapse
Man any ideas?
Thanks
Hashcode and I have talked about it. There IS a working fastboot, but you can't get to it with a fastboot cable, and it's very buggy and not too useful. So it sounds like you are SOL. Sorry. :/
Sent from my Amazon Tate using Tapatalk
?
ferrouskid said:
Man any ideas?
Thanks
Click to expand...
Click to collapse
Fastboot system files?
jimyv said:
Fastboot system files?
Click to expand...
Click to collapse
Wait I know android cowboy had the same problem some time ago. I'll ask him.
ferrouskid said:
Wait I know android cowboy had the same problem some time ago. I'll ask him.
Click to expand...
Click to collapse
If anyone is in the same situation as me,I'm trying stuff out. First things first,I remember I bricked the kindle a while back. I made sure it was out of battery and then charged it a LITTLE and tried. doing that now.
http://forum.xda-developers.com/showthread.php?t=2588608 QUOTE=ferrouskid;53393803]If anyone is in the same situation as me,I'm trying stuff out. First things first,I remember I bricked the kindle a while back. I made sure it was out of battery and then charged it a LITTLE and tried. doing that now.[/QUOTE]
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
HI, you did the factory reset, too?
ARUSTORI said:
HI, you did the factory reset, too?
Click to expand...
Click to collapse
I didn't, though you should try my solution (I'd got a black screen after the grey logo).
I'm sorry but I won't try the factory reset to see if it works
I have the same problem currently, I'll use ubuntu and see if my kindle can get recognized, the cable I'm using also has a light on it so atleast we know its not dead lol.
Ause said:
I have the same problem currently, I'll use ubuntu and see if my kindle can get recognized, the cable I'm using also has a light on it so atleast we know its not dead lol.
Click to expand...
Click to collapse
I'll be over the moon if this works, adb is installed, now waiting for flat kindle to charge...
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
Please expand on that. Thank you so much.
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
Can you please give the commands that you used?
That would be very helpful...
Thanks a lot for the help though
ferrouskid said:
Can you please give the commands that you used?
That would be very helpful...
Thanks a lot for the help though
Click to expand...
Click to collapse
Connect your device to your computer.
By typing "adb devices", you should get this output :
Code:
List of devices attached
???????????? no permissions
Then type "lsusb" and note the ID of the Google Device (Should be 18d1:0001, but I'm not sure you will get the same).
Edit the file "/etc/udev/rules.d/51-android.rules" and add the following lines (If the file doesn't exists create it). Replace 18d1 and 0001 with the values you get in lsusb :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="0001",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="0001",SYMLINK+="android_fastboot"
Run "sudo chmod a+r /etc/udev/rules.d/51-android.rules".
Restart your computer and you should be access your device using "adb shell".
Follow this post to restore your device : http://forum.xda-developers.com/showpost.php?p=53388919&postcount=23
Crap. I dont have access to a linux OS..ill have to call amazon i think.
Sent from my LG-D800 using XDA Premium 4 mobile app
Related
Hi all,
This issue is a little bit different. I already searched for any thread that might fix my issue but no luck yet.
Issue started when trying to reformat the internal partition to 4096mb using Tenfar's CWM recovery. After that I rebooted the Atrix and got RSD err 1?? or something. I searched for solutions and tried to flash using the [GUIDE] Flash SBF to Motorola Atrix 4G from "kennethpenn. It failed half-way and stuck @ "swith BF mode failed" and giving the failed message.
Now the phone is out of battery and it's not charging at all. Not sure if RSD mode isn't allowed to charge or something.
When I connected AC Adapter to the phone and these are messages i have:
"Modem did not power up (2)"
"Starting RSD protocol support"
and with M logo in the center.
It will not do anything if i connected the Atrix the computer. Anyone knows how to fix this issue, please show me. I really really appreciate it. thanks in advance.
Daniel T
after 3 tries, I finally flashed the Atrix and got it working again. But i got odd screen issues. The Menu, Home, Back, and Search buttons are not working anymore. When I tap on something (button or letter from keyboard), I have to tap below the actual position (about 0.2 inch below) to work. Any suggestions on to how to fix it. thanks very much in advance.
danieldtien said:
after 3 tries, I finally flashed the Atrix and got it working again. But i got odd screen issues. The Menu, Home, Back, and Search buttons are not working anymore. When I tap on something (button or letter from keyboard), I have to tap below the actual position (about 0.2 inch below) to work. Any suggestions on to how to fix it. thanks very much in advance.
Click to expand...
Click to collapse
Re-flash on different computer? Im not entirely sure....
Good Luck.
Magoodigan said:
Re-flash on different computer? Im not entirely sure....
Good Luck.
Click to expand...
Click to collapse
I also tried that too but it's same issue. I think the issue is the screen itself. Got it replaced at AT&T store.
danieldtien said:
I also tried that too but it's same issue. I think the issue is the screen itself. Got it replaced at AT&T store.
Click to expand...
Click to collapse
which sbf did you try to flash?
I heard of this happening with reformatting of the internal memory, but sadly I didn't see a resolution....
bongd <------- contact him, his is the only one that seems has a solution for the screen issue
Sent from my MB860 using XDA App
help
mramirezusa said:
bongd <------- contact him, his is the only one that seems has a solution for the screen issue
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
hey man how do i contact him cause im having the same issue
Lol I think tenfar should update hes thread underline that partition option will brick your phone...
Anyway you formatted your psd partition, so no buttons and no screencalibration.
Search the thread used tenfar recovery...
You need the psd.img dumped from github and push in your phone using adb dd command.
http://dev.gitbrew.org/~dasmoover/android/atrix/atrix-devkit-fs.tar.gz
Just take mmcblk0p3.img from atrix engeneering dump and push it
from a terminal (win or linux commands are the same, just remember usb debuggin on and that you are typing commands from the adb folder, place the file in the same folder)
adb push mmcblk0p3.img /data/local/tmp
adb shell
su
chmod 777 /data/local/tmp/mmcblk0p3.img
dd if=/data/local/tmp/mmcblk0p3.img of=/dev/block/mmcblk0p3
Reboot
I learnt it the hard way...
KeRmiT80 said:
Lol I think tenfar should update hes thread underline that partition option will brick your phone...
Anyway you formatted your psd partition, so no buttons and no screencalibration.
Search the thread used tenfar recovery...
You need the psd.img dumped from github and push in your phone using adb dd command.
http://dev.gitbrew.org/~dasmoover/android/atrix/atrix-devkit-fs.tar.gz
Just take mmcblk0p3.img from atrix engeneering dump and push it
from a terminal (win or linux commands are the same, just remember usb debuggin on and that you are typing commands from the adb folder, place the file in the same folder)
adb push mmcblk0p3.img /data/local/tmp
adb shell
su
chmod 777 /data/local/tmp/mmcblk0p3.img
dd if=/data/local/tmp/mmcblk0p3.img of=/dev/block/mmcblk0p3
Reboot
I learnt it the hard way...
Click to expand...
Click to collapse
Can you please re-upload the file, I'm having screen miss-calibration and from what I've read this file helps?
Nevermind I don't need'em no more.
I have changed the build.prop of my rooted TF201 to play the gameloft games.
After changing the TF201 got stuck in a bootloop. I tried the hard reset but it is still not starting.
I read that it is possible to push the orginal build.prop to the TF201 via APX-Mode but i dont now how to do it.
My computer recognizes the TF201 as a Asus Transformer Prime APX mode or in MTP when i start it regular. Unfortunatly i can not get any access to the Data of my TF201.
Is Asus able to see the root and that i changed the build.prop if i sent it to RMA?
Would be so happy if anybody could help me.
Thank you.
(And i know it was stupid to change the build.prop but didnt expected to brick it http://media.xda-developers.com/images/icons/icon9.gif)
Hi there.
I had a week of the same problem. I hadn't deleted anything but mine was in the boot loop too. After trying everything I managed to reinstall the OS by:
1. Downloading firmware from Asus site (it must be same or later version as installed already and must be the one for your region - if you don't know your current version, the small text described in step 4 below will tell you and step 4 can be done multiple times)
2. Freshly formatting a micro SD card with FAT
3. Placing the ZIP file (the zip inside the zip that Asus provide) in the root of SD CARD
4. Restarting the tablet by holding power and volume down until small text appears at top of screen at which point press volume up
Your tablet will boot from the SD card and reinstall your OS.
ALL DATA WILL BE LOST but you'll have a working tablet.
Cheers.
Sent from my Transformer Prime TF201 using xda premium
stf996 said:
Hi there.
I had a week of the same problem. I hadn't deleted anything but mine was in the boot loop too. After trying everything I managed to reinstall the OS by:
1. Downloading firmware from Asus site (it must be same or later version as installed already and must be the one for your region - if you don't know your current version, the small text described in step 4 below will tell you and step 4 can be done multiple times)
2. Freshly formatting a micro SD card with FAT
3. Placing the ZIP file (the zip inside the zip that Asus provide) in the root of SD CARD
4. Restarting the tablet by holding power and volume down until small text appears at top of screen at which point press volume up
Your tablet will boot from the SD card and reinstall your OS.
ALL DATA WILL BE LOST but you'll have a working tablet.
Cheers.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Thank you for answering!
Unfortunatly did not work for me.
The androidfigure showed up with a red triangle on it and after a minute it restarted into the bootloop.
Any other ideas?
clmz88 said:
Thank you for answering!
Unfortunatly did not work for me.
The androidfigure showed up with a red triangle on it and after a minute it restarted into the bootloop.
Any other ideas?
Click to expand...
Click to collapse
Can't you push the original build.prop via ADB Shell when it's almost booted up?
Code:
adb mount -o ro,remount /dev/block/mmcblk0p1 /system
adb push c:\...\build.prop /system/
Turge said:
Can't you push the original build.prop via ADB Shell when it's almost booted up?
Code:
adb mount -o ro,remount /dev/block/mmcblk0p1 /system
adb push c:\...\build.prop /system/
Click to expand...
Click to collapse
I tried it and got the message "can not find device" although my systems shows Android MTP Device in the device manager...
clmz88 said:
I tried it and got the message "can not find device" although my systems shows Android MTP Device in the device manager...
Click to expand...
Click to collapse
Mine shows up, but only when "Camera (PTP)" is selected instead of "Media device (MTP)" in the "Settings >> Storage >> USB computer connection" section.
But of course, that won't help you in this case since you can't change this setting.
I can't find anything about having to switch to PTP for ADB to work so you may want to post a question about it in the Q&A forum.
A guy had the exact same problem here last week after changing the build.prop for the exact same reason. He was able to recover his problem using the same method that the root scripts use for writing to data. Let me try and find the thread and you can try to contact him.
EDIT: Here you go.
http://forum.xda-developers.com/showthread.php?t=1480428&highlight=bricked
Now don't go doing such stupid things again.
Turge said:
Mine shows up, but only when "Camera (PTP)" is selected instead of "Media device (MTP)" in the "Settings >> Storage >> USB computer connection" section.
But of course, that won't help you in this case since you can't change this setting.
I can't find anything about having to switch to PTP for ADB to work so you may want to post a question about it in the Q&A forum.
Click to expand...
Click to collapse
Ok. Thanks though.
I would be happy about some other ideas
Doktaphex said:
A guy had the exact same problem here last week after changing the build.prop for the exact same reason. He was able to recover his problem using the same method that the root scripts use for writing to data. Let me try and find the thread and you can try to contact him.
Click to expand...
Click to collapse
I already got that thread and asked for his solution.
Im unfortunatly not able to sent him a private message because i am a new member.
clmz88 said:
Ok. Thanks though.
I would be happy about some other ideas
Click to expand...
Click to collapse
EDIT: I'll see what I can do for you, give me some time.
Doktaphex said:
EDIT: I'll see what I can do for you, give me some time.
Click to expand...
Click to collapse
Thank you!!!
clmz88 said:
Thank you!!!
Click to expand...
Click to collapse
I've sent him a PM for you asking for his solution. I've linked him to this thread.
What software version are you on? .11 .13 or something else.
EDIT:
Do you know how to use ADB?
Does ADB see your device?
Doktaphex said:
I've sent him a PM for you asking for his solution. I've linked him to this thread.
What software version are you on? .11 .13 or something else.
EDIT:
Do you know how to use ADB?
Does ADB see your device?
Click to expand...
Click to collapse
I actually dont know what version is on my Prime. I did the official update two weeks ago. So it is probably V9.4.2.11.
I have a app called "adb made easy" on my pc and this on can not find my device.
Does your device constantly reboot or does it stay at the boot animation?
Doktaphex said:
Does your device constantly reboot or does it stay at the boot animation?
Click to expand...
Click to collapse
It stays constantly in the boot animation.
and adb made easy doesn't have your device listed?
What if you "open CMD for ADB commands" and then in that window type "adb devices" without the quotation marks?
Also what does windows device manager show with regards to android devices?
EDIT: unplug and plug back in a couple of times, does windows make it's usual connection noises?
Doktaphex said:
and adb made easy doesn't have your device listed?
What if you "open CMD for ADB commands" and then in that window type "adb devices" without the quotation marks?
Also what does windows device manager show with regards to android devices?
Click to expand...
Click to collapse
adb made easy and cmd dont show any adb devices.
the devices manager shows
mobile devices: Asus Android MTB Device (could not be started)
windows is always making the pluggingsound
Wierd, ADB should still see the device as it seemed to when the other guy screwed his build.prop
If I reboot, ADB picks up the device during the boot animation and lets me start interacting straight away.
EDIT: Unfortunately, without ADB, I'm not gonna be able to help any further. Hopefully the guy how recovered his from this state will pop in and be able to help you out.
When and where did you get the device from. If you're still in your return window and feel like being dishonest, then you could take it back to the shop and ask for a replacement. However, if it has to go back to ASUS, I'm fairly certain that they would pick this up straight away, I could be wrong though. They may just look at it see it doesn't boot, reflash it and then test it and send it back.
Doktaphex said:
Wierd, ADB should still see the device as it seemed to when the other guy screwed his build.prop
If I reboot, ADB picks up the device during the boot animation and lets me start interacting straight away.
EDIT: Unfortunately, without ADB, I'm not gonna be able to help any further. Hopefully the guy how recovered his from this state will pop in and be able to help you out.
When and where did you get the device from. If you're still in your return window and feel like being dishonest, then you could take it back to the shop and ask for a replacement. However, if it has to go back to ASUS, I'm fairly certain that they would pick this up straight away, I could be wrong though. They may just look at it see it doesn't boot, reflash it and then test it and send it back.
Click to expand...
Click to collapse
Is yours setup for PTP or MTP?
Sent from my Transformer Prime TF201 using xda premium
Turge said:
Is yours setup for PTP or MTP?
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
I think it is setup for MTP but im not sure about it...
I didnt find a way yet to get access to the prime via usb.
Already tried different drivers, adb, apx but nothing is working.
Hello,
My galaxy S2 fell and my digitizer is apparently non-working - I can see the screen sort of, but there is no touch response.
Anyway, I can't let just about anyone who I take it to have access to my data, since my contacts are stored on the google cloud, I have them all anyway, but I either need to:
1. Access the phone via PC and wipe the data by emulating the screen on my PC.
I tried using Kies air to do it - it recognizes the phone, but I can't open it through it because my phone is locked and it won't give me access otherwise. Of course I can't unlock it since the digitizer is dead.
I tried using software like droid-at-screen, installing the proper SDK components, BUT the phone never got recognized. It is my deduction that I have to enable USB debugging, which, again, I can't do since I don't have the touch interface.
2. The other solution would be to wipe all data manually, which I assumed was done holding the 2 volume buttons + power button, but all that ever got me to was the lock screen along with a "safe mode" in the corner.
I posted this in the android Q&A, since I feel this is more of an android rather than model related issue. Thank you.
If you can still see the screen enough, I think with USB OTG you can connect a computer mouse and use that to navigate to the wipe data screen
Sent from my DROID2 using xda premium
gagdude said:
If you can still see the screen enough, I think with USB OTG you can connect a computer mouse and use that to navigate to the wipe data screen
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
Thanks for the reply.. I don't think any of those are available where I can get them though :/
Posklapenzi said:
Thanks for the reply.. I don't think any of those are available where I can get them though :/
Click to expand...
Click to collapse
use adb
adb pull
adb pull /sdcard/ or pull /data and datadata
xsenman said:
use adb
adb pull
adb pull /sdcard/ or pull /data and datadata
Click to expand...
Click to collapse
Thank you. I assume this is some kind of cmd that I run from adb.exe once I install it through the SDK?
Posklapenzi said:
Thank you. I assume this is some kind of cmd that I run from adb.exe once I install it through the SDK?
Click to expand...
Click to collapse
yup, you can get a guide from My Guides and Manuals for ADB knowledge and just use a adb.exe
xsenman said:
yup, you can get a guide from My Guides and Manuals for ADB knowledge and just use a adb.exe
Click to expand...
Click to collapse
Thank you, just one question - do I need degugging turned on for this as well? Because like I said, I am unable to do that.
Posklapenzi said:
Thank you, just one question - do I need degugging turned on for this as well? Because like I said, I am unable to do that.
Click to expand...
Click to collapse
yup, adb will only work with debugging enabled, just try you might have left it enabled
xsenman said:
yup, adb will only work with debugging enabled, just try you might have left it enabled
Click to expand...
Click to collapse
Turns out I do not.. is there any hope for me left? Somehow wipe the entire memory manually?
Posklapenzi said:
Turns out I do not.. is there any hope for me left? Somehow wipe the entire memory manually?
Click to expand...
Click to collapse
I'm in the same position, so I'll be watching to see if there is hope
loopism said:
I'm in the same position, so I'll be watching to see if there is hope
Click to expand...
Click to collapse
Bumping this, I've yet to find a solution..
Posklapenzi said:
Bumping this, I've yet to find a solution..
Click to expand...
Click to collapse
Are you sure there are no USB OTG cables available for you? They're like $5 online
Sent from my DROID2 using xda premium
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