I'm not sure if this is considered a boot loop but when turned on, after the logo it turns into a blank screen.
Anyway, I was stupid enough to install 3D chainfire when it's not compatible (I neglected the description since it worked on my previous galaxy ace) ... Soooo can anyone help me on this?
I've tried going to recovery mode to:
- wipe data/factory reset
- wipe cache partition (but shows error)
Not sure what else can I do anymore. I'm noob at these. Since Ace 3 is fairly new, it's quite hard to find a solution with google haha.. Also, I have zero knowledge about flashing ROM or of the sort..
Extra info in case it helps:
- My phone is Samsung Galaxy Ace 3 GT - S7275R
- Rooted with a Chinese universal rooting program
- When entering recovery mode, it shows "no command" for a few seconds before entering the menu.
Thanks in advance for helping!
try
try 1 goto recovery and wipe cache/data
try 2 download adb shell install kies in pc
goto recovery mode and connect phone to pc
type in adb shell remove your.apk in aystem app
gohel.vishal said:
try 1 goto recovery and wipe cache/data
try 2 download adb shell install kies in pc
goto recovery mode and connect phone to pc
type in adb shell remove your.apk in aystem app
Click to expand...
Click to collapse
For try 1, it's not working
For try 2, I don't really understand the way to do it. I'd downloaded adb, installed kies. Other than that, I'm not sure what to do.
Sorry, really a noob here.
try
xahjun said:
For try 1, it's not working
For try 2, I don't really understand the way to do it. I'd downloaded adb, installed kies. Other than that, I'm not sure what to do.
Sorry, really a noob here.
Click to expand...
Click to collapse
.
goto recovery & connect to pc
open folder where is adb
press shift+right click
open command prompt here
type adb shell
in adb shell
type su
goto system/app
ls
look at your chainfire app and delete type rm xxx.apk
gohel.vishal said:
.
goto recovery & connect to pc
open folder where is adb
press shift+right click
open command prompt here
type adb shell
in adb shell
type su
goto system/app
ls
look at your chainfire app and delete type rm xxx.apk
Click to expand...
Click to collapse
This is embarrassing, but I don't really know if I'm even doing it right or wrong. After all, I don't fully understand how adb work(even after reading about it).
Anyway, this is what I get after typing adb shell.
h t t p ://s18 .postimg .org/ov55a21pz/Untitled .png (sorry can't post image cause I'm a new user)
Though I think I'm actually doing it wrong.
never
xahjun said:
This is embarrassing, but I don't really know if I'm even doing it right or wrong. After all, I don't fully understand how adb work(even after reading about it).
Anyway, this is what I get after typing adb shell.
h t t p ://s18 .postimg .org/ov55a21pz/Untitled .png (sorry can't post image cause I'm a new user)
Though I think I'm actually doing it wrong.
Click to expand...
Click to collapse
i have never seen error like that i cant help you
gohel.vishal said:
i have never seen error like that i cant help you
Click to expand...
Click to collapse
Ahh I see... Thanks anyway for those quick reply :good: Appreciate it.
Anyone else can give me a helping hand?
so
xahjun said:
Ahh I see... Thanks anyway for those quick reply :good: Appreciate it.
Anyone else can give me a helping hand?
Click to expand...
Click to collapse
goto samsung service center ...
or try to flash stock rom google it
gohel.vishal said:
goto samsung service center ...
or try to flash stock rom google it
Click to expand...
Click to collapse
Can't find Ace 3's stock rom...
go to here and choose your country and download
xahjun said:
Can't find Ace 3's stock rom...
Click to expand...
Click to collapse
http://samsung-updates.com/device/?id=GT-S7275R
Thaaaaaaaanks!
gohel.vishal said:
http://samsung-updates.com/device/?id=GT-S7275R
Click to expand...
Click to collapse
Thanks a lot!! It worked! I took long to try because the file size is huge and my internet connection is unstable. Regardless, thanks for the help! Really appreciate it! :good:
Related
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
Hello everybody
at first I installed Ultimate Dynamic Navbar through this:
http://forum.xda-developers.com/showthread.php?t=2270198
after that I enabled it and it rebooted my device with no problem, but it didnt hide the navbar, so I disabled it to remove it later,
then my device rebooted and it's bricked!!!
Now:
1- Start the device
2- Sony logo
3- Black screen (the screen is on)
From recovery:
ADB shell : error: closed
ADB is working fine except the shell
Device: Sony tablet s
ROM: R5A OTA rooted
Region : US
Any help???
Thanx in advance
Make a factory reset.And use S.onyTablet.S flasher if you can.
Sent from my Sony Tablet S using xda app-developers app
Thanx for your reply
but this is what I get:
[*] Press enter to begin...
[*] Firmware data ready...
[*] Waiting for device...
and nothing happens after that
although I can use adb normally but when trying "adb shell", I get "error: closed"
mstfyounis said:
Thanx for your reply
but this is what I get:
[*] Press enter to begin...
[*] Firmware data ready...
[*] Waiting for device...
and nothing happens after that
although I can use adb normally but when trying "adb shell", I get "error: closed"
Click to expand...
Click to collapse
The reason you are getting the "error: closed" message is because System Recovery installed with Android 4.0.3r5a inhibits use of ADB Shell.
I will post the hack recovery which enables adb shell in the recovery when i find it.
Sent from my Sony Tablet S using xda app-developers app
the _hack_recovery.zip is also not working, tried it before
it has a low incremental value
Same problem but with sony tablet p
same problem. im missing region.zip, vendor.prop, build.prop and a whole lot of other files. :crying: . adb shows closed. tried to push with adb shows permission denied. can only access recovery. maybe root cant tell. any help appreciated. and also mstfyounis, go to adb and try this command. "adb pull / C:\android\backup" and then wait and check which files you have and then post theme here.
@techkrayken, here attached
mstfyounis said:
the _hack_recovery.zip is also not working, tried it before
it has a low incremental value
Click to expand...
Click to collapse
It should throw error, it gets adb working in recovery
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
It should throw error, it gets adb working in recovery
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
It's not the "Error: 7 ........." , it says "Prohibit update as a result of checking version or base sku"
and the shell is still closed
thnx
mstfyounis said:
@techkrayken, here attached
Click to expand...
Click to collapse
thnx but cant download. sorry. but check in configs folder if u hav region.zip.
also check in vendors in u hav vendor.prop.
techkrayken said:
thnx but cant download. sorry. but check in configs folder if u hav region.zip.
also check in vendors in u hav vendor.prop.
Click to expand...
Click to collapse
nothing found
also, if you could get them, how would u put them back in the device??
depends
mstfyounis said:
nothing found
also, if you could get them, how would u put them back in the device??
Click to expand...
Click to collapse
Depends. i dont have root anymore so i cant.
but if you get adb (google it) and the drivers for your phone,
you might be able to push the files with root access with "adb root" (i think anyway)
but if youve got the same problem as me and when you try anything in the aio tool it shows " "su" binary not found no root " (something like that)
than unluckily i cant help you anymore.
ive ordered a pickup from sony since i realised i had warranty with it.
fingers crossed they cant find out its been rooted.
sorry for any dissapointment. if you bought this of someone then phone sony and give theme the serial no. . theyll check if you have warranty
(dont tell them anything about the aio or rooting it. say it was an ota update)
Hi all, it's my first post here
My Galaxy S II (stock ROM/recovery) has fallen into a reboot loop while I was texting and I'm positive I didn't install new apps recently, so I can't really tell it's an app bug. Last thing I did before texting was disabling Swype.
All I know is that TouchWiz now crashes after boot displaying its usual dialog window.
In addition to that, I've just broken the display, so I can't see anything going on screen...
How can I recover pictures from the internal storage? How can I stop the reboot loop long enough to back up everything with Kies?
I've tried booting in safe mode but the phone keeps on rebooting and I have no visual feedback of successful activation of safe mode. Prior to breaking the screen I could access the stock recovery, so I guess I can still do it, if needed.
TIA,
Andrea
Recovery should be enough if it works. So try getting into recovery and connecting it via ADB. Then you can get data with "adb pull <location-on-phone>"
Explorer23 said:
Recovery should be enough if it works. So try getting into recovery and connecting it via ADB. Then you can get data with "adb pull <location-on-phone>"
Click to expand...
Click to collapse
Thank you for your reply!
When you say "recovery", you mean stock recovery or a more advanced one (CWM, etc.)?
I've never used ADB, I'll try to set it up as per these instructions: http://forum.xda-developers.com/showthread.php?t=1917237
EDIT: Do I need to enable debugging on the phone? It's currently disabled and I can't do anything about it because of the reboot loop...
don't know
I don't think that it's possible to recover the data on your device's internal storage now. Rest if anything works do post your experience here with respective procedure or snapshots.
For more attractive deals "Just Dial":- +1 516 515 9871
lo_Spocchioso said:
Thank you for your reply!
When you say "recovery", you mean stock recovery or a more advanced one (CWM, etc.)?
I've never used ADB, I'll try to set it up as per these instructions: http://forum.xda-developers.com/showthread.php?t=1917237
EDIT: Do I need to enable debugging on the phone? It's currently disabled and I can't do anything about it because of the reboot loop...
Click to expand...
Click to collapse
Oh crap ... yes, i think you need to have debugging ON (never actually tried without it). Well, you can still check it. So set up ADB (hope those instructions are good, I can't help you there as I don't know how things work on Mac) and type in "adb devices". If everything's OK, you should get one device listed (some weird number). Then type in "adb pull <location on phone> <location on computer (optionally)>. If you want more info about commands, just type "adb" and you'll get everything listed. That should be it ... if it works in first place :fingers-crossed:
EDIT: Stock recovery should do fine.
Explorer23 said:
Oh crap ... yes, i think you need to have debugging ON (never actually tried without it). Well, you can still check it. So set up ADB (hope those instructions are good, I can't help you there as I don't know how things work on Mac) and type in "adb devices". If everything's OK, you should get one device listed (some weird number).
Click to expand...
Click to collapse
Yeah, I've tried with another (working) S II and it seems you really need debugging turned on...
Is it possibile to use a custom recovery to copy data from internal memory to the SD? I could try to do it blindfolded :cyclops:
lo_Spocchioso said:
Yeah, I've tried with another (working) S II and it seems you really need debugging turned on...
Is it possibile to use a custom recovery to copy data from internal memory to the SD? I could try to do it blindfolded :cyclops:
Click to expand...
Click to collapse
Possible ... maybe. But that would mean you need a recovery with file manager - and file managers are usually touch-based. So you can't do much if your screen is broken. I suggested ADB because it was the only option that would work for sure and you don't need screen for it ...
But ... maybe there still is a way ... You could try reinstalling ROM via ODIN and syncing with Kies. Download stock ROM for your country and carrier from www.sammobile.com/firmwares, get your phone into download mode and insatall via Odin. This should work. You're not doing any factory resets, wipes or anything - just "dirty flashing" the ROM over existing one, so data and (most) apps remain untouched. Then you can try connecting with Kies. From there I don't know exactly how stuff works (don't have a Samsung device), but hope it can launch without touching anything on the phone.
I suggest removing the SIM card before trying, so it doesn't get stuck on PIN unlock screen.
This is really your last chance ...
Your next option is changing the screen
Good luck
Explorer23 said:
Possible ... maybe. But that would mean you need a recovery with file manager - and file managers are usually touch-based.
Click to expand...
Click to collapse
You're right but, if I'm not mistaken, CWM "touch" file manager can also be used with the physical buttons. I've never tried that, can anybody please confirm?
You could try reinstalling ROM via ODIN and syncing with Kies.
Click to expand...
Click to collapse
That's actually an excellent idea! Now, I only need to be sure that, after re-flashing, the device will be immeditely accessible by Kies straight after boot without further intervention...
Your next option is changing the screen
Click to expand...
Click to collapse
True, but I'd rather grow brain cells than shell out money
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