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.
Related
Hi all! My friend´ve a Hero and after radio update the phohe has bricked. See this video:
http://www.youtube.com/watch?v=R5ihQU7DoDU
How to fix this?
Thanks.
Nobody know?
It´s such!
Someone may be able to help you if you give us generous details. ie which radio rom did you intend to flash?
Lord Lucan said:
Someone may be able to help you if you give us generous details. ie which radio rom did you intend to flash?
Click to expand...
Click to collapse
Radio: 6.35.09.26
ROM: Modaco-3.1
Recovery: RAV-hero-v1.5.3.1
Thanks for u support.
Have you tried turning it on while the charger is plugged in?
Lennyuk said:
Have you tried turning it on while the charger is plugged in?
Click to expand...
Click to collapse
Yeah, but charger don´t works on flash image and the battery is fully!
:S
Thanks.
And you have tried to go back into the recovery?
Lennyuk said:
And you have tried to go back into the recovery?
Click to expand...
Click to collapse
Recovery and fastboot don´t work. The video show this.
It´s hard solved
Thanks.
fabioccoelho said:
Recovery and fastboot don´t work. The video show this.
It´s hard solved
Thanks.
Click to expand...
Click to collapse
Try turning it on with the power button and the second you see any life hold down home.
I don't think this will work but it might be worth a try.
its already in recovery,you have adb debugging enabled before update?
Try this in a CMD Window..
adb devices
if it works you could be ok
bonesy said:
its already in recovery,you have adb debugging enabled before update?
Try this in a CMD Window..
adb devices
if it works you could be ok
Click to expand...
Click to collapse
Yeah, adb debug is check! But, i can´t access fastboot or recovery mode.
Thanks.
copy ra_hero recovery onto the root of your sdcard
then...
adb shell flash_image recovery recovery-RA-hero-v1.5.3.1.img
oradb shell flash_image recovery-RA-hero-v1.5.3.1.img
I cant remember which soryy, but one should work!
device not found
Hi! I am in the same s..t so I tried it all
some people managed to do this and get it working again :
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
MINE IS EXACTLY LIKE THE YOUTUBE VIDEO and it didn't!
Any other sugestions?
[email protected]
yea i think u have different problems,his goes to recovery.yours is doing the same as my Sapphire which is being collected by HTC tomorrow for repair pressing HOME+POWER will not get to fastboot! it will take you too recovery
and finaly the FIX
finally some one knew how to fix my HERO!
a guy with a lot of electronics knowledge and a device that connected directly to the matherbord and wiped the rom and rewrote it!
rom gets stock if you are smart enough to flush it with the wrong update (CMDA ta a GSM phone)!
so that's the only solution for this kind of situations!
Thanks for all answers. But only kind to solved this is with JTAG to Motherboard.
Thanks!
same issue here
Hi everyone
I've got the same problem showed in that video. Could you guys help me out? Is JTAG the only way? My mobile simply can't be recognize on Windows and ADB just doesn't list the device...
I've tried every key button combination, but all I got is that Out of the Box image (seems like it's the background of the recovery mode or smthg)
I got my phone charged from USB (from my notebook) but windows doesn't recognize it, even if I dloaded the drivers for it.
Any suggestion would be of great help
Thx a bunch
TAG
same issu here
MESCU said:
finally some one knew how to fix my HERO!
a guy with a lot of electronics knowledge and a device that connected directly to the matherbord and wiped the rom and rewrote it!
rom gets stock if you are smart enough to flush it with the wrong update (CMDA ta a GSM phone)!
so that's the only solution for this kind of situations!
Click to expand...
Click to collapse
Hi MESCU
Could you tell us a little bit more about what happened to your phone and what procedure the guy who fixed your phone did? thx for your help
TAG
phone and the box image
sorry if this is a bit out of place but i had something similiar but not as major...i just tried flashing my radio update today and it went well till it said reboot press home and power...i pressed that then it got stuck in phone and box picture for a good 5 minutes..i didnt know how long to late because im new to this..thankfully when i pressed home and power and it came back to the recovery and i just reboot and it works fine now!
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.
Please I need your help!!!
Today i received my LG Nitro HD with 4.0.4 V21c then i downgrade to 4.0.3 V18c and root with TPSparkyRoot, so far so good until...
I tried to install CWM, first tried RomManager and not good then i download a Recovery.img and install via Terminal Emulator follow this command from this link
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
tips4droid "dot "com/how-to-install-clockworkmod-recovery-on-lg-nitro-hd/
After that i reboot the phone and never wake up... Tried some button combinations, remove and place battery but always stay black screen
When i connect to pc windows asking for QHSUSB_DLOAD driver but not found this
Please HELP!
Sorry if i dont explained so well and sorry for my bad english
Sorry to be the bearer of bad news but there's no recovering from this, I did the same thing to my Nitro a couple months ago. Only option is to get it warrntied out.
Sent from my LG-P930 using xda premium
tampaboy1984 said:
Sorry to be the bearer of bad news but there's no recovering from this, I did the same thing to my Nitro a couple months ago. Only option is to get it warrntied out.
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
I found this info for the HTC phones
forum.xda-developers.com/showthread.php?p=23078349
Is there any possibility to change the HTC files for the LG's one to restore Recovery.img ???
Ditto
Flamante said:
Please I need your help!!!
Today i received my LG Nitro HD with 4.0.4 V21c then i downgrade to 4.0.3 V18c and root with TPSparkyRoot, so far so good until...
I tried to install CWM, first tried RomManager and not good then i download a Recovery.img and install via Terminal Emulator follow this command from this link
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
tips4droid "dot "com/how-to-install-clockworkmod-recovery-on-lg-nitro-hd/
After that i reboot the phone and never wake up... Tried some button combinations, remove and place battery but always stay black screen
When i connect to pc windows asking for QHSUSB_DLOAD driver but not found this
Please HELP!
Sorry if i dont explained so well and sorry for my bad english
Click to expand...
Click to collapse
I feel your pain. I was suckered into the same site and did the same to my phone and "blam!" nothing after re-boot. I guess we need new phones?
Try to follow this: http://forum.xda-developers.com/showthread.php?t=1784709
As long as you can get into "Download" mode - it should do the trick.
johnsmyth_jr said:
Try to follow this: http://forum.xda-developers.com/showthread.php?t=1784709
As long as you can get into "Download" mode - it should do the trick.
Click to expand...
Click to collapse
Any news Black Screen dont show download mode?
It's likely that you overwrote the partition that contained the download mode firmware.
You will probably have to send the phone to LG to get it fixed.
I have tried to contact the author of that article with information to fix it and a warning about how he's caused a bunch of people to hard brick their phones, but who knows if he even cares.
Hard brick lg nitro hd solution!! mobiletechvideos
edwin.jesus18 said:
Any news Black Screen dont show download mode?
Click to expand...
Click to collapse
Really amazing, hard brick repair! lg nitro hd, mobiletechvideos.mybigcommerce.com
, too very quick !!! , I grateful, I waste more time searching in the net how repair , several technicians told me to throw my phone,did not have choice.
From the beginning it would have sent to you, thanks for all.
thoroughly recommended
I have read many times over now jcase method and have tried it twice now without success- clearly I am doing something wrong. I have working adb on my pc and all the prerequisite files in the correct directory. I seem to be going wrong at the "adb restore backup.ab" point- it says allow it to restore but in my terminal that process is very quick and the phone does nothing. Am I not waiting long enough?...and appears as if nothing else happens so I go to first terminal and stop it as directions say...but after that the next important 5 code steps say failed or file not found-is that what is supposed to happen?...I finish the remaining steps and then head to htc un unlock but it comes back FAILED Anyone with success have any tips?? I'm stumped...but not bricked...yet!
are you connected to the internet during that time ?
Allowing it to restore means to acknowledge it on the phone itself. Touch the appropriate button on the phone.
Sent from my HTC6435LVW using xda premium
Unlock your phone and click the allow button.
Sent from my GT-P7510 using xda app-developers app
And after touching the "allow" button,, be prepared to wait several minutes. That command is restoring a 300 mob for. It takes awhile.
Sent from my Nexus 7 using Tapatalk 2
more Q's
Appreciate the help guys! So I should see a message on my phone that requires me to allow? That I did not see or do...sounds hopefull. I have been thinking my adb version was not supporting restore as when I did the restore step all I see is like a help screen, with no direction to allow, or continue or yes/no.....and yes I was connected to internet...should I not be? Won't be able to try this again till tonight but really appreciate the help!
After using the adb restore command, you should turn your phone screen on, and there should be a message waiting that is asking you to confirm that you want to restore.
If you aren't seeing that message after turning your phone screen on, then it sounds like your adb might be too old, our you got a bad download of backup.ab
Sent from my HTC6435LVW using Tapatalk 2
rootntootn said:
Appreciate the help guys! So I should see a message on my phone that requires me to allow? That I did not see or do...sounds hopefull. I have been thinking my adb version was not supporting restore as when I did the restore step all I see is like a help screen, with no direction to allow, or continue or yes/no.....and yes I was connected to internet...should I not be? Won't be able to try this again till tonight but really appreciate the help!
Click to expand...
Click to collapse
I made this mistake last night
is the backup.ab file in the same folder as the adb command is?
I forgot to move the backup file and that is when you get the help screen..
munchy_cool said:
I made this mistake last night
is the backup.ab file in the same folder as the adb command is?
I forgot to move the backup file and that is when you get the help screen..
Click to expand...
Click to collapse
Will check all this stuff out, all sounds like it's pointing me in the right direction and I am a bit complsive so I will get there sooner or later, any other thoughts will be greatly appreciated and investigated...I think my files are where they are supposed to be BUT I will check and re-check
try it and let us know dude ..do not proceed until you are sure backup is done
Ok...some success, did it in win 8 but I think it was my version of adb that was the problem..not version of windows or files-however I had a zillion files and shortcuts on 7 and I was getting confused so I switched.
I did now get the backup to run, unlocked and allowed on phone...let it finish and all seemed great but last step before reboot...the "adb shell dd if=/sdcard/CIDBLOCK.img of=/dev/block/mmcblk0p5" code returned something like permission denied? Anyway I did reboot and did try for the hell of it, to unlock at HTC...but of course It FAILED. I did not factory reset this time so I am thinking maybe that's the problem and will try again later. Any other thoughts on this demise?
Maybe windows 8 is the problem
droid DNA \m/ √[π]¶~™
munchy_cool said:
Maybe windows 8 is the problem
droid DNA \m/ √[π]¶~™
Click to expand...
Click to collapse
Could be except that it did work up to that (almost) last step...I did read to factory reboot before trying again but I did not...mostly because I was lazy...but also because the image files were already in my phone storage anyway and that,s what the first few steps do...I started from backup.ab code part so I will do the whole deal over...later-burned at the moment.
Done Deal
rootntootn said:
Could be except that it did work up to that (almost) last step...I did read to factory reboot before trying again but I did not...mostly because I was lazy...but also because the image files were already in my phone storage anyway and that,s what the first few steps do...I started from backup.ab code part so I will do the whole deal over...later-burned at the moment.
Click to expand...
Click to collapse
Well...It all finally went well!! Can't thank members enough for all the help...I will pay it forward!!
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