I am a noob with all of this android modding/hacking/flashing stuff and would like some guidance. Right now, my nexus 7 is in a state that cannot boot. When powering on, it remains on the Google logo and does not progress. I am able to get the the bootloader and recovery screen though. I do not have USB Debug enabled. I would like to return to the stock image or the previous version I was on. This all happened when trying to upgrade manually to the Android 5.0 update. Is there anybody that can help me with this? I would gladly appreciate it. I have been struggling to find an answer but its hard to understand what some people are saying.
Again, I cannot turn on the USB Debug option because I guess its "soft bricked" or something.
Also the bootloader state is locked.
Related
I have two A500s and have rooted and flashed them both successfully.
One day my main tab, the other is for the family, was working then it just stopped. It would boot to the "Acer" logo and go no further. I left it like that all night with no result.
So, I figure that I'll just flash a new rom to fix it. I tried 6 or 8 different roms; all booted only partially like before. I did a factory reset, flipping the screen lock back and forth. Still would only boot part way and hold. I continued to look for different roms (what do they say when you keep trying the same thing expecting different results?).
Now the tab doesn't seem to come on at all; that is the screen stays dark. The light on the power button comes on and I can turn it off by holding for 10 seconds and turn it on again. I connected to my PC and it requested a driver which I installed. the PC makes the "new hardware" sound but I don't find it in "My Computer".
I have tried to access it via “adb devices”, but no devices are detected.
This is the extent of my efforts and knowledge. If anyone is able to help please email me at [email protected]. I have been reading the blogs and am posting this to several blogs so I might not find your answer if it is to the blog only.
Btw,
I did find a post that describes something like this on an A200 at this blog:
http://www.acertabletforum.com/forum/acer-iconia-a200-help/5895-solved-my-a200-wont-turn.html
I'm tempted to attempt it if I don't find an answer specific to the A500.
THANKS IN ADVANCE FOR ANY HELP!!!
==================================================
edit: I tried the A200 solution to no affect.
bricked a500
I have the exact same issue, does not go past acer logo screen and Win 7 does not show the device when connected. I can hear the sound when you plug the usb cable but nothing visible or no icon on the screen.
Any help would be greatly appreciated.
Thanks
Santosh
Bricked .. and clueless ...
ok have an Iconia tab a500 here from a friend, he tells me he put in wrong adapter.
I think its bricked ..
ALready read alot of stuff here and did try some things but cant seem to find the correct solution .
I can connect in apx or fastboot, i dont have uiid and the thing is locked also
Bootloader = V0.0312-ics
if i start up i get " boot veriefied failed"
i found some downgrading method on here "method 2" but when i do it and he reboots i get the message "abort illegal blabla"
I would really appreciate if someone could help me point me in the right direction to start.
Using win7
Grtz
Don't know how but I broke my Nexus 7 (2013 LTE) using wugfresh toolkit. I had it rooted and unlocked using the toolkit then decided I wanted to go back to stock. So I used the flash stock + unroot (device on) and oem lock.
Now my Nexus when powered on comes to the bootloader (fastboot mode) screen that has START at the top in green. If I press power to select start it shows Google in white with nothing else on the screen. It will stay like that forever (at least a few hours that I've verified). I also just noticed while it is on the "Google" screen I can press the up/down volume buttons and it gives me the option to start, power off, etc. just like it's still in the bootloader. I'm not really sure what all that means... just trying to give as much information as possible.
I've had no luck finding a solution already on this forum. I haven't even found someone who describes this exact same problem with this particular model Nexus.
In addition to trying to use the Wug toolkit to fix my Nexus I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2381582
I tried following the instructions exactly and the output seemed to report fixing my Nexus but it did not. I'm referring to the output you get when you run the dead nexus bat file. The only bad output it gave me was several messages "FAILED (remote: Bootloader is locked)" However, at the bottom of the output it said my "Nexus has been restored!"
So in summary these two solutions I've tried (wug toolkit and the thread mentioned above) seem to report fixing my Nexus but didn't actually do anything. Also noticed now with the WUG toolkit the driver test fails. I followed all the steps and removed all drivers and did a fresh install. It mentions needing USB debugging enabled but how can I do that since I can't get past the bootloader/google screen?
Any help appreciated!
One other thing I forgot to mention. When it was working after I had rooted/unlocked I installed that multirom app from the app store. I don't see how that could have broken anything.
One last thing I recall. The last thing I did was do a factory reset under settings when everything was working.
I've been trying all these various toolkits and following videos but nothing seems to fix it. One thing about all these help guides out there they all tell you to make sure you're in usb debugging mode... but that isn't possible for me since I can't get past the Google loader. I haven't had much luck finding out what to do in my case.
and I think I just fixed it! I will post what I did if this works...
So all I had to do was unlock my bootloader then do the factory/stock restore. When I tried following every single recovery guide out there none of them mentioned unlocking before doing the 1 click restore/fix. Strange I had to do it this way I guess, but every tool would error out saying the Nexus was locked.
Hello,
I had installed the Franco Kernel on my N4 some months back. I recently got the 5.0 Lollipop OTA update but i could not install it. I read somewhere that i needed to install the stock kernel to get Lollipop installed. So i got the factory image of 5.0 for N4 from google and manually tried to flash with some Kernel flasher app i dont recall the name. THAT WAS THE WORST DECISION I EVER TOOK.
Now my phone is stuck in fastboot mode. I can go to recovery and all. Whwn i try to start up my phone i can only see a black screen.. i downloaded adb but the problem is I HAD NOT TURNED ON USB DEBUGGING. I searched the net for a week,asked my friends who all said that i should throw away my old( i dont consider it old) phone and get a new one. I have come here with a lot of hope. I bought the N4 so as to use it for atleast another year .
Adb doesnt recognize my phone. Pc says "Android Device". Please help me. Im saving for getting my sister a laptop and i just cant afford another decent reliable phone.
You do not need USB debugging for fastboot mode. when cionnected is should say android device and some serial number.
USB debug mode is when the android OS is running not fastboot mode
if it does not when connected at the prompt type fastboot devices
follow the install instructions here and it should get you device back. (in the commands remember to replace the file names with the lollipop names)
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
I have brought back at least 10 devices from my own doing and from people that screw up their phone and not know what they are doing.
Good luck
Ok i will follow it. I currently have the 4.2.2 image file. Yes in fastboot mode PC recognizes it as Android Device. Lets hope i can do it I dont need USB debugging right ?:silly:
I dont know how i should thank you and this forum. I love you guys, you helped me when i had lost all hopes of getting my phone back i love you guys <333333333333333333333333333333333333333333333333333333333333333333
Glad it worked. Just spread the love on the forums.
I learned by reading here and glad to help others.
I changed a cracked screen on a Nexus 4. I have done this before with no problems. It is not rooted and locked to a carrier. Now it is stuck in bootloop.
Now the real problem is that even though the phone will take a charge, when I connect it to a PC it the PV doesnt see the phone and it doesn't show up in file folders or in Nexus Toolkit.
So I cannot access ADB either since the PC doesn't see the device and same with Nexus Toolkit.
I can boot into recovery mode but it goes to Android man on back with red flag and "No Command Found" message.
I have spent a week on this. Who out there knows what the hell I can do. I have thought about swapping out the charger port to see if thats why the pc isnt seeing the phone...I am stumped. Help would be very appreciated folks.
Thanks
Wallstud44 said:
I changed a cracked screen on a Nexus 4. I have done this before with no problems. It is not rooted and locked to a carrier. Now it is stuck in bootloop.
Now the real problem is that even though the phone will take a charge, when I connect it to a PC it the PV doesnt see the phone and it doesn't show up in file folders or in Nexus Toolkit.
So I cannot access ADB either since the PC doesn't see the device and same with Nexus Toolkit.
I can boot into recovery mode but it goes to Android man on back with red flag and "No Command Found" message.
I have spent a week on this. Who out there knows what the hell I can do. I have thought about swapping out the charger port to see if thats why the pc isnt seeing the phone...I am stumped. Help would be very appreciated folks.
Thanks
Click to expand...
Click to collapse
What happened to this? I have the same damn issue. Although I managed to get fastboot and adb functionality with great difficulty. But the device doesn't seem to be able to boot into anything. I've tried every single thing software by the book, and by the forums too. I suspect it might be hardware.
Any luck?
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
lejars1 said:
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
Click to expand...
Click to collapse
It is possible that your system and/or boot partitions have become corrupted.
If that is the case, you'll need to reinstall the ROM. The best way to do this is to install a custom recovery like twrp or clockworkmod, reformat your partitions, and proceed from there.
Hi - thanks for this.
I got it sorted in the end.
Here's a link to what happened.
http://forum.xda-developers.com/showpost.php?p=60970017&postcount=1597