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
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!
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.
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
I apologize for my English: I'm using google translator!
installed cmw recovery [delos3geur]][CWM Advanced Edition] Philz Touch (6.27.3) [4/20/2014] on my galaxy gt grand quattro - i8552b using terminal emulator with the following eating
$ su
# dd if = / sdcard / recovery.img of = / dev/block/mmcblk0p6
more discovered I made a mistake in the following line:
$ su
# dd if = / sdcard / recovery.img of = / dev/block/mmcblk0p13
after it rebooted the phone it just did not connect more no sign of anything at all!
help me please!
bobdiegoesponja said:
installed cmw recovery[delos3geur]][CWM Advanced Edition] Philz Touch (6.27.3) [4/20/2014] on my galaxy gt grand quattro - i8552b using terminal emulator
after it rebooted the phone it just did not connect more no sign of anything at all!
help me please!
Click to expand...
Click to collapse
It was for GT-I8552, not for GT-I8552B.
Check if it turns on in download mode.
Vol. down + power + home
If yes, then download the official firmware for GT-I8552B
http://nasirtech.blogspot.in/2014/02/i8552bdcuana1-android-412-jelly-bean.html
flash it via Odin
unfortunately he does not care in download mode or in recovery mode, there is the possibility of this process have burned the motherboard? or other method to revive the phone as JTAG?
Then it's probably a hard-brick.
id74em8 said:
It was for GT-I8552, not for GT-I8552B.
Click to expand...
Click to collapse
GT-I8552 and GT-I8552B are the same. It has the 'B' in countries such as Brazil, Panama and others.
bobdiegoesponja said:
unfortunately he does not care in download mode or in recovery mode, there is the possibility of this process have burned the motherboard? or other method to revive the phone as JTAG?
Click to expand...
Click to collapse
If you can't boot into download mode, I think you should contact a service center for assistance to your device.
Use ur warranty in this case
Sent from my Xperia Z1 Compact (D5503)
May this serve as a lesson for people messing around with DD command. I don't mean to be harsh on OP but, messing around with the console it's extremely dangerous for inexpert hands.
EDIT: I'll post a thread with the Partition Information Table for the Grand Quattro / Win, that will shed a bit more light on what partitions to use when DD'ing files.
El_Dark said:
May this serve as a lesson for people messing around with DD command. I don't mean to be harsh on OP but, messing around with the console it's extremely dangerous for inexpert hands.
EDIT: I'll post a thread with the Partition Information Table for the Grand Quattro / Win, that will shed a bit more light on what partitions to use when DD'ing files.
Click to expand...
Click to collapse
Thanks for sincerity friend, I made a mistake and I'm paying for it :crying: more like to know if using RIFF JTAG BOX I have a chance to fix this bug
bobdiegoesponja said:
Thanks for sincerity friend, I made a mistake and I'm paying for it :crying: more like to know if using RIFF JTAG BOX I have a chance to fix this bug
Click to expand...
Click to collapse
I'd rather recommend taking your phone to Samsung Service Center, or to a professional, buying a box just for fixing your phone one time or two, doesn't pay out, they're usually expensive enough for an individual who will use them occasionally.
However, you might want to try first googling how to build a USB Jig, this *might probably* work out for you, if the Mainboard is not dead at all, an USB Jig will allow you to enter directly to download mode.
There are guides here in XDA on how to build one, they're inexpensive and easy to build. You might also want to buy a pre-built one, but it'll be a lil more expensive and I wouldn't pay that much for a resistor and a Micro-USB connector
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