Related
Hi folks i don't what i did to my phone! I was trying to apply some
updates, test other builds, but after applying a 1.1 radio image i
can't access recovery mode (using HOME+POWER) or fastboot (tried using
BACK+POWER and CAMERA+POWER).
When i press power the phones shows up the ANDROID logo and the robot,
and stays there forever!
Did i bricked my phone? That is nothing i can do to get i back to
work?
Thanks for anyone that can help me!
Hugs
Antonio
as much as i believe this to be a redundant thread you seem to be at a different point than the other "bricks" you claim to be at the android screen with the flashing robot. at that screen you SHOULD be able to access adb as long as you have it set up correctly on your computer. try it and post your results
EDIT if adb works then try this after placing the JF recovery.img onto your sdcard
Code:
adb shell flash_image recovery /sdcard/recovery.img
if it works great if not someone else might be able to help with any other errors
Hi Tuba and other experienced members, in fact, i don't know what are the singnals that i have a brick!
My G1 won't pass the very first screen, not the flashing droid. Mine get stucked at the first screen that goes on.
ADB won't connect to my ADP!
Is there any way to save my phone? I heard about the G1 Serial Cable (http://www.instructables.com/id/Android_G1_Serial_Cable/) could it done any good?
Will be my G1 like this forever?
Thanks again!
Hello forum so here is another request for help.
Last night I charged my Xoom. This morning I shut it down and took it with me to class as I knew I wasn't going to use it until that afternoon. When I powered up this afternoon I get the Moto logo then the pulsing tiles. Then the screen will eventually time out and "go to sleep". When I push the power button the screen comes on and the pulsing tiles are still being displayed. The system will still play the notification sound when emails are received so I think that it is somewhat alive.
Tried to talk to Moto tech support but was disconnected when being transfered from a lvl 1 tech to a lvl 2 tech. Unfortunately I didn't have time to sit on hold again so I will have to try them again tomorrow.
Adb works.
Vol up + power reboots
Vol down just brings me to a screen that says "Starting Fastboot protocol support." and sits there.
adb reboot recovery brings me to and android with a yellow caution sign in him.
The only "unusual programs/activity" I have loaded is this launcher which was set as default. http://forum.xda-developers.com/showthread.php?t=1017451
Any Ideas?
PS NOTE: This is a Xoom Wifi.
Thanks,
ChanceM
Just an update in case anyone else has this just talked with Moto and they are sending me a new Xoom.
ChanceM
Same thing happened to me
Hey dude, same thing happened to me, although I had not enabled usb debugging before hand. I still had access to fastboot so doing a 'fastboot oem unlock' formatted the device and returned it to stock.
VTL-launcher will not work for the xoom, as you and I both painfully found out.
Since you have adb still working during the animation, couldnt you just:
'adb reboot recovery'
and recover stock?
I'm by no means an expert, just trying to help out... if anyone else has anything to add on this, this dude will surely appreciate it.
If you can get adb access its easier to just remove the offending application
Code:
adb shell rm /data/app/packagenamehere.apk
Where packagenamehere.apk is the name of the APK you installed.
Reboot and you're good to go.
Sent from my GT-P1000
alias_neo said:
If you can get adb access its easier to just remove the offending application
Code:
adb shell rm /data/app/packagenamehere.apk
Where packagenamehere.apk is the name of the APK you installed.
Reboot and you're good to go.
Sent from my GT-P1000
Click to expand...
Click to collapse
Excellent! That's even better. Still trying to learn all this stuff.... Thanks dude.
I had the same problem with ADW Launcher but, oddly, not with ADW Launcher EX. Removing the package was the only way I could solve it, too. besides removing, you can adb uninstall packagename.
EDIT: BTW, you can comment directly to the author of VTL-Launcher in his thread here on XDA: http://forum.xda-developers.com/showthread.php?t=1017451. Gojimi's a great guy and anxious to get to the bottom of any problem.
Okay I tried removing it but I get permission denied.
Edit: Thanks guys I was able to do a factory reset.
ChanceM
put it in fastboot mode by holding down the volume down key during power up
do:
fastboot erase cache
fastboot erase userdata
be aware that if you do this, everything that you have in your xoom will be erased, but it will boot up fine, will ask you to go through the activation again and you are ready to put your stuff back in.
Times like these is when I wished the sdcard was working, so my content wouldn't be wiped out
HazeT said:
put it in fastboot mode by holding down the volume down key during power up
do:
fastboot erase cache
fastboot erase userdata
be aware that if you do this, everything that you have in your xoom will be erased, but it will boot up fine, will ask you to go through the activation again and you are ready to put your stuff back in.
Times like these is when I wished the sdcard was working, so my content wouldn't be wiped out
Click to expand...
Click to collapse
We should add to this that he must be have an unlocked boot loader to issue these commands, I tried just that when I had this problem.
However, unlocking forced a system format anyways.
[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!
KF won't start, charge, or connect to PC
Absurd1 said:
[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!
Click to expand...
Click to collapse
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex
JohninLex said:
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex
Click to expand...
Click to collapse
Well, like I said, I don't know much about any of this stuff, but here's what I can tell you:
I don't have FIREFIREFIRE. Not really sure what that is, but it's certainly never been on my Kindle.
What I did try doing was following those steps in Kindle Fire Utility anyway. I can get it to the point where it says:
ADB Status: Online
ADB Rooted: No
Boot Status Unknown
If from there I hit 5 (to "install latets TWRP recovery"), I get a whole bunch of
"The system cannot find the path specified." for each step it goes through, until finally it gets here:
"If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait..."
To reiterate again -- I don't know what any of this ADB stuff is, where to find it, etc.
We are in the same boat. Was messing around w/ someone's Bare Bones CM7, and as per instructions, clicked wipe SYSTEM, and since then my device has been with screen "on" but black; non response to power button weather plugged on AC adapter or USB. Will have to research the forums tomorrow (cant find search function now) and let you know if I find a fix and please do the same if you find something first.
Sincerely,
-RM
---------- Post added at 08:49 AM ---------- Previous post was at 08:37 AM ----------
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.
theartofbone said:
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.
Click to expand...
Click to collapse
Nope, that's not doing anything for me. My kindle won't power on. All it does is display "Kindle Fire" for one second, then go dead.
Does anyone have ANY advice?
oundsde good
Try a different charger and plug into the wall for a little while.
_Justin said:
Try a different charger and plug into the wall for a little while.
Click to expand...
Click to collapse
Tried that. No luck.
Do you have a chat program, or google talk? I'll help you out.
_Justin said:
Do you have a chat program, or google talk? I'll help you out.
Click to expand...
Click to collapse
..........
My device has the same issue, it powers down as soon as I connect it to a PC or charger. The interesting thing, that it is charging, but the led is dark. When I take it off the charger the next day, it boots up and fully charged. (when I connect a cable again it shuts down immediately)
If you find out something I would be also interester. (I've also rooted before 6.2, than I've lost root, than after I while I've faced these issues)
Alright, unless any folks have any other advice, I'm gonna go ahead and contact Amazon for a return.
try to charge it with the wall charger for some hours - check the charger - should have ~1.8A - maybe the orange light is showing up after half an hour
try to power it off by holding pwr ~20sec to allow better charging - if you can't let it on the charger - try to power it off later (eg after an hour)
look here about charger spec and contact problems:
http://forum.xda-developers.com/showthread.php?p=23035482#post23035482
some had success with a factory cable:
http://forum.xda-developers.com/showthread.php?p=23034046#post23034046
Hi All, as the title states, I'm currently stuck in a CWM bootloop after trying to applying the new OTA update on my rooted transformer.
I know it was kinda stupid of it.
I tried following the steps posted here, but i can't seem to get adb to push the file through.
I must admit that I'm not very good with using command prompts and i have no idea if I'm doing it right.
Steps I'm sure i'm doing right so far.
I opened up my cmd and cd C:\android-sdk\platform-tools
When typing adb devices, my transformer is successfully recognized as 0123456789ABCDEF OFFLINE
However, the next part got me slightly confused.
I had typed in C:\android-sdk\platform-tools>adb push C:\cwm_recovery-5027_rogue_rburrow-tf101-r1.zip /sdcard/download.
However, i kept encountering the error that the device is offline.
I had also set up a marco to press the up arrow+enter key with a 10ms pause in between followed by a 1 second pause before repeating.
However, the file was still unable to be pushed to the device despite countless tries.
I'm not sure if it's because the line i had entered was wrong or was it due to some other factor.
Would someone be kind enough to help me take a look and see if i had done something wrong?
Thank you very much for your help!
lunzi88 said:
Hi All, as the title states, I'm currently stuck in a CWM bootloop after trying to applying the new OTA update on my rooted transformer.
I know it was kinda stupid of it.
I tried following the steps posted here, but i can't seem to get adb to push the file through.
I must admit that I'm not very good with using command prompts and i have no idea if I'm doing it right.
Steps I'm sure i'm doing right so far.
I opened up my cmd and cd C:\android-sdk\platform-tools
When typing adb devices, my transformer is successfully recognized as 0123456789ABCDEF OFFLINE
However, the next part got me slightly confused.
I had typed in C:\android-sdk\platform-tools>adb push C:\cwm_recovery-5027_rogue_rburrow-tf101-r1.zip /sdcard/download.
However, i kept encountering the error that the device is offline.
I had also set up a marco to press the up arrow+enter key with a 10ms pause in between followed by a 1 second pause before repeating.
However, the file was still unable to be pushed to the device despite countless tries.
I'm not sure if it's because the line i had entered was wrong or was it due to some other factor.
Would someone be kind enough to help me take a look and see if i had done something wrong?
Thank you very much for your help!
Click to expand...
Click to collapse
Damn man sorry to hear that. Def should have flashed stock recovery before applying the OTA. Im sure one of these guys can help you out though good luck!
Sent from my Transformer TF101 using xda premium
pierrekid said:
Damn man sorry to hear that. Def should have flashed stock recovery before applying the OTA. Im sure one of these guys can help you out though good luck!
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
yeah dude, i realised that after i googled for a fix.
prior to this my experience with OTA updates on rooted+CWM phones had never encounter such problem.
The most that had happened previously was that the update failed to be installed.
I had no idea it could get stuck in a loop i couldnt get out of.
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
thanks for the tip.
I can't try it right now as I left the tablet at home when I left for work today.
I'll update once I get back home to try it.
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
The words are not even popping up for me, it just shows the asus logo and then goes straight into recovery. I go into adb devices and it shows OFFLINE aswell.
:S
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
That's what I did when it happened to me. Worked like a charm.
I did the same thing and I'm stuck too.
Sent from my Kindle Fire using xda premium
Same problem here for the same reason...flash ota update on my root tablet....I'm always on cwm recovery when reboot. I'm able to cold boot it when holding.vol down and power but I do I get around this cwm ecovwry bootloop? Thanks
Envoyé depuis mon HTC Glacier avec Tapatalk
lamaqc said:
Same problem here for the same reason...flash ota update on my root tablet....I'm always on cwm recovery when reboot. I'm able to cold boot it when holding.vol down and power but I do I get around this cwm ecovwry bootloop? Thanks
Envoyé depuis mon HTC Glacier avec Tapatalk
Click to expand...
Click to collapse
Same here. The only way I can boot now is VolDown + Power. Another thread recommended flashing some stock-like ROM, but I'd rather not.
Has someone found out how to boot normally?
I have to cold boot everytime my device reboots or it shuts off, which is quite often.
The cold boot method is becoming really annoying.
Thanks!
Found a way!
Hi guys! This is my first post helping somebody
So I found a way to make it boot normally...
What you need to do is to cold boot your device.
Then download from the store Android Terminal Emulator.
Open it up and type in:
Code:
su
Allow SuperUser if prompted.
If you get # then you are good to go!
Now you need to type in:
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Once it's done, reboot your tablet and you should see a progress bar.
Let it load and once it's done, you have your tablet back!
Hope it works!
Hi guys I'm in trouble!! I have continuos bootloops in recovery. I tryed to flash a rom as usual but always bootlooping adn when I tryed to make a cold boot it remain in the same " colod booting linux ".. I can't restore my backup cause I move it on my memory card and cant restore it! Can I do something? I can't boot anymore... Any suggestions? I can only install the rom I have put in the internal memory..
I have a rooted NSTG that I forgot to make a backup of before I rooted it. I want to unroot it since there really isn't any work being done on this device to make it worth being rooted. I'd like to go back to the factory settings. I have tried the 8 failed boots method, but I can't seem to get it right. I can get about 5 failed boots and then somehow it always ends up on the loading screen! Quite frustrating. Any suggestions on how to unroot this device or perhaps get the 8 failed boots to work?
I use this to get back to stock.
When you boot up the Nook, as soon as the screen changes,
just hold down the bottom left & right side keys until recovery comes up.
The 8 boot thing is really designed for when the Nook is veged and reboots itself continuously.
If you have ADB or a shell going:
Code:
echo 000 > /rom/devconf/BootCnt
Renate NST said:
When you boot up the Nook, as soon as the screen changes,
just hold down the bottom left & right side keys until recovery comes up.
The 8 boot thing is really designed for when the Nook is veged and reboots itself continuously.
If you have ADB or a shell going:
Code:
echo 000 > /rom/devconf/BootCnt
Click to expand...
Click to collapse
Thank you! This is exactly what I needed to know!
I had this problem and it was worse .
Pressing power button had effect and I used :
http://forum.xda-developers.com/showthread.php?t=1475613
And after that I updated it to 1.1.12 .
Now it is OK.
Caution nstg is not the same firmware as nts ...
Envoyé depuis mon HTC EVO 3D X515m avec Tapatalk