First off I have done some research on the subject amd have come to the conclusion that I borked this thing beyond my ability to fix it. The thread that makes me think I have a hard brick is http://forum.xda-developers.com/showthread.php?p=22897771 Brick 2.
Basically what happened is I flashed the us .29 update how I thought were the directions. By getting the update from Asus, then extracting it once (from the launcher.zip) to get the one ending In .29.zip. Then I put it on the internal sdcard and went into CWM and flashed it. As soon as it was done I rebooted and it went to the Asus splash with a loading bar so I figured I would do its thing. the bar was filled and disappeared but it went no further.
Now it's stuck at the Asus splash with the Tegra logo in the bottom right. If I reboot it goes straight back to that screen, and does NOT say "this device is unlocked" anywhere. I can NOT access fastboot from that screen (says waiting from device) and I do believe I can't access ADB, I think it displays a blank when I type adb devices. Just for clarity I was using ADB in CWM right before this happened, as well as fastboot as I had to put CWM on it. So I don't think it's drivers not letting me connect but I am going to check the when I get home.
So with all that said I'm pretty sure it's hard brick and I will most likely have too send it in for fixing. Anyone Had this problem yet? Is there a way to fix it that I have missed? when I get home from work I'm going to try some more.
Happened to me also..but had ADB while stuck at the logo and managed t push blob .17. That fixed it
Sent using Chanook 300
ricardowec said:
Happened to me also..but had ADB while stuck at the logo and managed t push blob .17. That fixed it
Sent using Chanook 300
Click to expand...
Click to collapse
You push that to the root of the internal sdcard? And what did you name the file? I would assume whatever it's named I'm the last zip. Assuming I have access to adb of course.
Sent from my ADR6300 using Tapatalk 2
enomele said:
You push that to the root of the internal sdcard? And what did you name the file? I would assume whatever it's named I'm the last zip. Assuming I have access to adb of course.
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
same procedure and related shell commands posted in the downgrade thread
Sent using Chanook 300
follow step 3 and on under : Flashed TF201 Recovery in ROM Manager?
http://forum.xda-developers.com/showthread.php?p=26925775
The issue I'm having though it's that when booted while connected to my computers is that there is no USB notification when it starts up and I can't find it in device manager.
Are the drivers to connect adb to CWM recovery different than the drivers I use while the tablets on and stuff. Be cause I did pull a file from CWM right before I bricked it, just a log file, nothing pertinent. And I might have had to install new driver for CWM
Sent from my ADR6300 using Tapatalk 2
Can you power+vol down and get into the bootloader? Can you use adb?
Sent from my Incredible 2 using Tapatalk 2 Beta-5
prototype7 said:
Can you power+vol down and get into the bootloader? Can you use adb?
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
no I can't get into bout loader. It just brings me to the same Asus splash screen. And I'm fairly certain adb doesn't work. I'm going to try uninstalling my drivers and start from scratch but I'm not hopeful since I used adb before it happened.
Sent from my ADR6300 using Tapatalk 2
Related
Okay so i'm trying to root using Odin i'm no noob at rooting but Samsung always gives me trouble do here is my isse I've tried every possible way to get into download mode and my phone just won't do it Adb does see my phone and I do have the drivers installed so here is my question wtf do I do lol please help i've never came across an issue like this
Sent from my SGH-T959V using Tapatalk 2 Beta-2
Title says adb wont recognize, post says it will I'm : confused:
If it does I assume you tried adb reboot download?
Sorry auto correct posting from my phone I ment that ADB DOES NOT recognize my phone sorry for the confusion
Sent from my SGH-T959V using Tapatalk 2 Beta-2
Got debugging turned on?
Yes it us turned on
Sent from my SGH-T959V using Tapatalk 2 Beta-2
Weird. Battery pull, button combo (as stated in the wiki) not working either? Try uninstalling and reinstalling the drivers.
followed every button combo I could think of including battery pull but when i'm home I'll try a different port someone told me that the port closest to the mother board and CPU words best
Sent from my SGH-T959V using Tapatalk 2 Beta-2
Do you think Samsung would lock someone out like that?
Sent from my SGH-T959V using Tapatalk 2 Beta-2
Check this out just incase you haven't tried How to get into download mode
Actually that's the first way I tried because most Samsung phones I've had that was the easiest way lol Idk what to do maybe I'll have to try a different computer
Sent from my SGH-T959V using Tapatalk 2 Beta-2
Franzferdinan51 said:
Okay so i'm trying to root using Odin i'm no noob at rooting but Samsung always gives me trouble do here is my isse I've tried every possible way to get into download mode and my phone just won't do it Adb does see my phone and I do have the drivers installed so here is my question wtf do I do lol please help i've never came across an issue like this
Sent from my SGH-T959V using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
Ok. Yank the battery. put battery in phone. Hold vol + and -. Plug Phone into USB. DL mode. YAY!
tried that it only takes me to recovery i got the computer recognising it the problem is only ODIN and ADB and The Non Existance Of a Download mode or so it seems thus Far and wont know for sure until i can get ADB working Any idea if their is Seperate ADB drivers that i can download
If you are doing what was posted above - what does the screen look like that you are calling recovery? And I assume you ARE only holding both volume buttons and NOT the power button?
Problem solved aparently it had something to do with my sim card and SD card i took them both out and odin came around to the dark side
I have a G2X from Wind Mobile, and I've rooted it (using this), and flashed the CM9 SK3 build by arcee on it. After the reboot, my phone is now stuck on the LG splash screen, and it remained frozen there for the past 40 minutes.
I couldn't get it to respond, so I pulled out the battery and rebooted it. Still stuck at the LG logo. Also, I can't seem to boot into recovery. I held down the "volume down" button and power button until the recovery icon appeared, but then it looped back to the LG splash screen and remained stuck.
I'm not sure what to do right now, can anyone please help me out?
Thanks!
otamega said:
I have a G2X from Wind Mobile, and I've rooted it (using this), and flashed the CM9 SK3 build by arcee on it. After the reboot, my phone is now stuck on the LG splash screen, and it remained frozen there for the past 40 minutes.
I couldn't get it to respond, so I pulled out the battery and rebooted it. Still stuck at the LG logo. Also, I can't seem to boot into recovery. I held down the "volume down" button and power button until the recovery icon appeared, but then it looped back to the LG splash screen and remained stuck.
I'm not sure what to do right now, can anyone please help me out?
Thanks!
Click to expand...
Click to collapse
Here you can try this: http://forum.xda-developers.com/showthread.php?t=1590523
Sent from my LG-P999 using XDA
mansa_noob said:
Here you can try this: http://forum.xda-developers.com/showthread.php?t=1590523
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Thanks, but I have one question.
Should I remove the micro SD card inside the phone first in order not to erase my NANDroid backup that's stored on it?
otamega said:
Thanks, but I have one question.
Should I remove the micro SD card inside the phone first in order not to erase my NANDroid backup that's stored on it?
Click to expand...
Click to collapse
External sd card is safe, however you can remove it just to be on the safe side. Internal sd card (5.5GB) WILL BE ERASED with this procedure.
Sent from my LG-P999 using XDA
mansa_noob said:
External sd card is safe, however you can remove it just to be on the safe side. Internal sd card (5.5GB) WILL BE ERASED with this procedure.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
I've tried it, but I can't seem to get my phone recognized by the PC. I've tried installing the APX drivers, but still no luck.
I have a wind g2x also though I've never had that problem but its easily recoverbale, you have soft brick I believe, I've heard that its almost impossible to brick a g2x anyways this thread should help
http://forum.xda-developers.com/showthread.php?t=1590523
Sent from my LG-P999 using Tapatalk 2 Beta-5
you could try a different cable, that has worked for other people
Sent from my LG-P999 using Tapatalk 2 Beta-5
otamega said:
I've tried it, but I can't seem to get my phone recognized by the PC. I've tried installing the APX drivers, but still no luck.
Click to expand...
Click to collapse
What do you mean? You were able to install the apx drivers or not?
Remember you have to hold both vol +/- buttons while connecting the device with battery removed. First time you will have to tell the os where the drivers are. Once the drivers are installed you can let go of the buttons.
Sent from my LG-P999 using XDA
mansa_noob said:
What do you mean? You were able to install the apx drivers or not?
Remember you have to hold both vol +/- buttons while connecting the device with battery removed. First time you will have to tell the os where the drivers are. Once the drivers are installed you can let go of the buttons.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
I got the APX drivers from this thread: http://forum.xda-developers.com/showthread.php?t=1566681
I opened the drivers to install them, and then I plugged in my phone just as you have said. However, there's no device recognized in the Device Manager, the only new thing that shows up is "APX" under "other devices", and it says that there's no drivers for it even though i've installed them.
otamega said:
I got the APX drivers from this thread: http://forum.xda-developers.com/showthread.php?t=1566681
I opened the drivers to install them, and then I plugged in my phone just as you have said. However, there's no device recognized in the Device Manager, the only new thing that shows up is "APX" under "other devices", and it says that there's no drivers for it even though i've installed them.
Click to expand...
Click to collapse
Right click that device, update driver, tell it you know where the driver is, point to that folder where you extracted it. Once the driver is installed you can connect the phone and run the tool.
Sent from my LG-P999 using XDA
Reading the op it pretty much seems like the flash didn't stick and then while booting into recovery he held it too long pretty simple I know but that's what I'm taking from skimming this subject lol... hole power and down volume until you see the 2nd lg logo.
Sent from my LG-P999 using xda premium
mansa_noob said:
Right click that device, update driver, tell it you know where the driver is, point to that folder where you extracted it. Once the driver is installed you can connect the phone and run the tool.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
I followed your instructions and managed to boot into CWM and re-flash ICS SK3 from my micro SD card. So far so good, and I've managed to boot into ICS successfully!
Thank-you very much sir for your time and help, I really appreciate it.
otamega said:
I followed your instructions and managed to boot into CWM and re-flash ICS SK3 from my micro SD card. So far so good, and I've managed to boot into ICS successfully!
Thank-you very much sir for your time and help, I really appreciate it.
Click to expand...
Click to collapse
No problem. Glad it worked out.
Sent from my LG-P999 using XDA
Hey guys,
I hope I'm not missing something obvious because I spent the last 2 hours searching for a solution.
Today I decided to unlock and root my Motorola Xoom 3G (EU-version, stock-android 4.x).
I unlocked it using fastboot and flashed the CWM recovery. But when I try to enter the recovery menu by pressing volume down when the Motorola logo apperas, it just says "Reading ODM fuse: 1". After that, it shows me a picture with an red exclamation mark.
I have no idea what to do now. Since I have no ADB access, I'm not able to do a "adb reboot bootloader" to flash CWM again.
Do you guys have any clue what's the matter? Thanks in advance
prisoner627
im assuming your xoom still boots up? if so youll still be able to get adb to work, just try flashing cwm again , you can also get fastboot working by turning the xoom on once you see the motorola logo count to 3 then press volume up and itll start fastboot protocol support
Sent from my Xoom using XDA Premium App
Right, I forgot. It still boots up but I can't get through the lockscreen. There's a message saying "device not ready. please enter a valid sim card".
right unfortunately i cant help with regards to sim card error as i own the wifi only model but someone a bit more knowledge able will see this and may have the answer
have you tried putting a sim card in? what does it say if you put one in?
Sent from my Xoom using XDA Premium App
Alright, I didn't mind the branding. With a T-Mobile card, I am able to enter the PIN and use the Xoom as usual.
Before I really mess up, can you tell me what to do next? Unfortunately, I don't have a micro sd card here so I am not able to do the "Universal Xoom Root" ( http://forum.xda-developers.com/showthread.php?t=1242241 ).
ok so youve unlocked the bootloader using fastboot oem unlock?
Sent from my Xoom using XDA Premium App
Yup, unlocked it is.
ok next step is to push recovery via adb have you tried doing that again?
Sent from my Xoom using XDA Premium App
recovery via ADB? I tried the CWM recovery image via fastboot last time ( http://forum.xda-developers.com/showthread.php?t=1074979 ).
yea you connect your xoom to pc let it connect etc etc, then open a command prompt in same folder where your adb files are located then type
adb reboot bootloader
once rebooted into bootloader
fastboot flash recovery recovery ( name of recovery here)
make sure youve downloaded the recovery image and not the zip file
Sent from my Xoom using XDA Premium App
Alright I did everything, no errors. But when I boot into the recovery, I still get "Reading ODM fuse: 1" and the exclamation mark...
try a different recovery perhaps? theres a few on here ill see if i can find one i used and post link
Sent from my Xoom using XDA Premium App
Yes I already thought of using the recovery of Team Rogue but it comes as a zip file, so I can't flash it, right?
cant flash it without entering recovery, im not sure what cauaing the problem , when you hold the power button and you get shutdown reboot etc if you press reboot do you get a second set of option ?? reboot,recovery bootloader etc?
Sent from my Xoom using XDA Premium App
You mean pressing the power button in normal usage, on the homescreen? I only get to decide whether I want to shut down the device or not. But this wasn't different before I started "flashing".
aah ok must be the rom im on thats got it , im not really sure where to go from here maybe do a factory reset and try again youve unlocked your bootloader though so dnt need to do that again
Sent from my Xoom using XDA Premium App
Same error with a factory reset... damn whats going on?
i honestly domt know i never had any probs doing mine and i asked my friendmwho has same xoom as you and he never had any trouble so kinda got me stumped lol
Sent from my Xoom using XDA Premium App
Guess I'll have to wait until someones bringing the big hint But I really thank you for your time. Since I know now that my device isn't completely bricked, you helped me a lot.
not a problem glad i could help even if a little lol
Sent from my Xoom using XDA Premium App
So i have a big problem, i acidentally downloaded the wrong kernel for my Nexus 5 (acidenttly got the nexus 4 versionb of Hells-core instead of the N5 version.) and flashed it, Now my phone wont boot nor can i access recovery or the bootloader. BUT when i plug it into my computer it tries to install drivers but fails because it cant find them, So im pretty sure its not a paper weight. Im running windows xp and was using carbon. If ANYONE can help please let me know.
http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
Check this thread out it will probably help. If you can get into it you should be able to fastboot flash your phone back to working condition
Sent from my Google Nexus 5 using Tapatalk
grim489 said:
http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
Check this thread out it will probably help. If you can get into it you should be able to fastboot flash your phone back to working condition
Sent from my Google Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i managed to get it into recovery as well as fastboot. but now when i try to do my recovery backup it causes the same error i was having i.e it would be detected by my laptop but i cant see anything. i may have to do a complete factory restore and see what happenes. Its kinda sad my GF with really NO android experience helped me get it into bootloader WHICH for anyone that has an issue similar to mine where your PC detects your device but you cant see anything on the screen hold down both up and down + power to get into bootloader. if it doesnt work at first hold down down + power (while its still connected to your pc so you can hear it feject) as soon as you hear the eject noise press and up down+up+power and you will be in bootloader
This guy had the same problem
http://forum.xda-developers.com/showthread.php?t=2746343
He dd'd his messed up partition back. I guess it's the bootloader that was overwritten but you can dd the secondary bootloader to the primary bootloader partition and it'd fix it hopefully.
Sent from my Nexus 5 using Tapatalk
grim489 said:
This guy had the same problem
http://forum.xda-developers.com/showthread.php?t=2746343
He dd'd his messed up partition back. I guess it's the bootloader that was overwritten but you can dd the secondary bootloader to the primary bootloader partition and it'd fix it hopefully.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
but i cant access adb shell because it tells me adb not found. so i dont know how to fix it.
NVM just went into recovered and then entered that command. Booted Right back up. Im going to make this a thread and HOPEFULLY it can get stickied. Thanks for all your help
No problem [emoji2] would you mind pressing the thanks button though? I'd appreciate it!
Sent from my Nexus 5 using Tapatalk
So I accidentally dropped my nexus 5 and I need to replace my display but unfortunately I haven't backed up my data (mostly pictures I'm worrying about the most). So is there a way to pull the storage from it? I've tried with adb and it doesn't work because it doesn't list my device.
I really hope there is a way to do it.
If USB works and its not detecting adb, then its set up wrong. Adb is the only way if both touch and display are broken.
Please click the link in my signature and read the adb and fastboot thread. It will tell you how to set it up properly
Sent from my Nexus 5 using Tapatalk
Does it matter if I had an unlock code for my lockscreen?
dndwanted said:
Does it matter if I had an unlock code for my lockscreen?
Click to expand...
Click to collapse
Yes it does.
Don't suppose you have a custom recovery do you?
Sent from my Nexus 5 using Tapatalk
My phone was rooted and I had latest TWRP with latest Paranoid Android,
dndwanted said:
My phone was rooted and I had latest TWRP with latest Paranoid Android,
Click to expand...
Click to collapse
Adb in recovery then. See the thread i previously told you about
Sent from my Nexus 5 using Tapatalk
I can't seem to make it work.
In "adb devices", it shows a device listed but in "fastboot devices" it doesn't show any device. When I tried to boot into fastboot mode I couldn't tell if I booted correctly because it shows the same thing as when I boot it normally.
I tried using the command "adb pull data/media/0 C:\adb\sdcard_25082014" and it gave me the error "remote object data/media/0 does not exist".
What should I do?
dndwanted said:
I can't seem to make it work.
In "adb devices", it shows a device listed but in "fastboot devices" it doesn't show any device. When I tried to boot into fastboot mode I couldn't tell if I booted correctly because it shows the same thing as when I boot it normally.
I tried using the command "adb pull data/media/0 C:\adb\sdcard_25082014" and it gave me the error "remote object data/media/0 does not exist".
What should I do?
Click to expand...
Click to collapse
You've not read my thread properly. Try again
Sent from my Nexus 5 using Tapatalk
I installed the adb in 15 seconds thing and then I followed this thread http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
Please tell me what have I done wrong because I can't seem to figure it out.
Unfortunately I don't know a solution to your problem, but your data shouldn't get lost when you replace the screen.
I replaced mine a week ago. Actually it was very easy. The most difficult part was removing the backcover.
The parts inside of the device are fixed with a little bit of glue which is not strong at all.
The whole replacement took me around 20 Minutes and I have never done something like that before.
After that everything was still on my phone.
And if your device doesn't get recognized from your computer in fastboot mode you should try the universal adb driver. This works perfectly for my Nexus 5.
@rootSU
I get this: http://imgur.com/ccw4lJ6
:/
ChickenNugget said:
Unfortunately I don't know a solution to your problem, but your data shouldn't get lost when you replace the screen.
I replaced mine a week ago. Actually it was very easy. The most difficult part was removing the backcover.
The parts inside of the device are fixed with a little bit of glue which is not strong at all.
The whole replacement took me around 20 Minutes and I have never done something like that before.
After that everything was still on my phone.
And if your device doesn't get recognized from your computer in fastboot mode you should try the universal adb driver. This works perfectly for my Nexus 5.
Click to expand...
Click to collapse
He doesn't need fastboot mode, only recovery and adb seems to be working fine.
OP, try adb pull /data/media/0/ c:\blah blah
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
He doesn't need fastboot mode, only recovery and adb seems to be working fine.
OP, try adb pull /data/media/0/ c:\blah blah
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately I get the same error.
dndwanted said:
Unfortunately I get the same error.
Click to expand...
Click to collapse
Are you SURE you're in recovery?
You got an error when you mounted data
Edit, well you got 2 errors...
The first error you got was the "usage" line. That means it thinks you typed "mount data" as an incomplete command. It IS incomplete if you're booted into android. Its not incomplete if you're in recovery. So I dont think you're in recovery.
The second error is "remote object doesnt exist". That's because you haven't mounted data.
To ensure youre in recovery, either:
1) Boot into android and then "adb reboot recovery"
2) From off, hold vol down and press power to get to bootloader. Press vol up TWICE then press power
Sent from my Nexus 5 using Tapatalk
rootSU said:
Are you SURE you're in recovery?
You got an error when you mounted data
Edit, well you got 2 errors...
The first error you got was the "usage" line. That means it thinks you typed "mount data" as an incomplete command. It IS incomplete if you're booted into android. Its not incomplete if you're in recovery. So I dont think you're in recovery.
The second error is "remote object doesnt exist". That's because you haven't mounted data.
To ensure youre in recovery, either:
1) Boot into android and then "adb reboot recovery"
2) From off, hold vol down and press power to get to bootloader. Press vol up TWICE then press power
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
http://imgur.com/KCoHxg8
dndwanted said:
http://imgur.com/KCoHxg8
Click to expand...
Click to collapse
Unless you can get recovery to show up, you're screwed.
I don't know anything about twrp so I can't help there.
Sent from my Nexus 5 using Tapatalk
Looking at my phone, I can't tell whether I'm in recovery or just booting normally or whatever because it doesn't show anything.
I guess I'll just have to wait until someone who knows TWRP can help me.
But thank you anyways
dndwanted said:
Looking at my phone, I can't tell whether I'm in recovery or just booting normally or whatever because it doesn't show anything.
I guess I'll just have to wait until someone who knows TWRP can help me.
But thank you anyways
Click to expand...
Click to collapse
Try manually option 2
Otherwise you can fastboot flash philz recovery - which is a recovery I know.
Sent from my Nexus 5 using Tapatalk
Doesn't work.
dndwanted said:
Doesn't work.
Click to expand...
Click to collapse
In more descriptive terms please
Sent from my Nexus 5 using Tapatalk