Hi all
After my son was 'playing' with my Nexus 7 - it now always stops at the boot menu on start-up and if 'Start' is selected, it only boots into Safe Mode.
I have flashed the original ROM and it has made no difference.
Does anybody know what I need to flash?
Thank-you in advance.
Sanxion said:
Hi all
After my son was 'playing' with my Nexus 7 - it now always stops at the boot menu on start-up and if 'Start' is selected, it only boots into Safe Mode.
I have flashed the original ROM and it has made no difference.
Does anybody know what I need to flash?
Thank-you in advance.
Click to expand...
Click to collapse
Please somebody help
Related
Well what happened was my nexus 7 started boot-looping so i turned it off then held the power button volume up and down.
i went into fastboot mode it says... i tried going into recovery mode and all it stays at is the (Google) boot. does anyone know what i can do to fix this its really making me scared cause im a noob at this stuff.
nexus7owner said:
Well what happened was my nexus 7 started boot-looping so i turned it off then held the power button volume up and down.
i went into fastboot mode it says... i tried going into recovery mode and all it stays at is the (Google) boot. does anyone know what i can do to fix this its really making me scared cause im a noob at this stuff.
Click to expand...
Click to collapse
Connect your nexus 7 to a computer with the usb and use the Nexus 7 toolkit v2.0 to load a recovery
Infliciton said:
Connect your nexus 7 to a computer with the usb and use the Nexus 7 toolkit v2.0 to load a recovery
Click to expand...
Click to collapse
Ok I'll try and I'll get back with the results
nexus7owner said:
Ok I'll try and I'll get back with the results
Click to expand...
Click to collapse
im actually doing it right now also lol. Make you install the drivers for windows with option 1 !
I keep getting an error when i install drivers and im trying to restore from a backup i have and says invalid file directory when i put the right directory in...
Thanks man i got it to finally boot into recovery and i restored it... now it works great
Hi there,
I have been running my TF101 rooted with TWRP recovery and Rayman's JB rom. I wanted to revert to a stock rom and tried this earlier today by flashing the stock ASUS ICS image zip from TWRP. I used the Version V9.2.1.27(WW) file which I am 100% sure is correct for my hardware.
This appeared to complete the install okay, but has left me with a system that won't boot and just sits at the ASUS boot screen with the spinning circle below the logo.
If I power up with the volume button down held I now don't have TWRP recovery and get the Android on its back screen. I've tried powering on with volume held up and have chosen the cold boot option but that is no different.
I have seen the easyflasher tool and thought that might help, but I am on OSX and Ubuntu without a Win 7 machine accessible!
Please can anyone point me in the direction of a solution? I have a backup file that I could restore if I could get back to having TWRP / CWM available
Sorry for a classic newbie question...
Thanks
Dont think you can install Original Firmware through Twrp or CMW... you need to be in APX mode to flash Org Firmware...
mlpinto said:
Hi there,
I have been running my TF101 rooted with TWRP recovery and Rayman's JB rom. I wanted to revert to a stock rom and tried this earlier today by flashing the stock ASUS ICS image zip from TWRP. I used the Version V9.2.1.27(WW) file which I am 100% sure is correct for my hardware.
Click to expand...
Click to collapse
If your using the USA version the WW version is NOT going to work and will cause this exact issue. Also is yours with the 3G capability or not?
mlpinto said:
This appeared to complete the install okay, but has left me with a system that won't boot and just sits at the ASUS boot screen with the spinning circle below the logo.
Click to expand...
Click to collapse
How much time did you let it "settle."
mlpinto said:
If I power up with the volume button down held I now don't have TWRP recovery and get the Android on its back screen. I've tried powering on with volume held up and have chosen the cold boot option but that is no different.
Click to expand...
Click to collapse
To enter into recovery it is Power + Volume Down, then when the tiny text shows up it's volume up.
mlpinto said:
I have seen the easyflasher tool and thought that might help, but I am on OSX and Ubuntu without a Win 7 machine accessible!
Click to expand...
Click to collapse
I would find a way to get to either machine and use Easyflasher, that worked for me when I installed the WW version on my TF101 US Variant.
mlpinto said:
Please can anyone point me in the direction of a solution? I have a backup file that I could restore if I could get back to having TWRP / CWM available
Sorry for a classic newbie question...
Thanks
Click to expand...
Click to collapse
I hope that this helps.
MasterDecker said:
If your using the USA version the WW version is NOT going to work and will cause this exact issue. Also is yours with the 3G capability or not?
How much time did you let it "settle."
To enter into recovery it is Power + Volume Down, then when the tiny text shows up it's volume up.
I would find a way to get to either machine and use Easyflasher, that worked for me when I installed the WW version on my TF101 US Variant.
I hope that this helps.
Click to expand...
Click to collapse
Hi,
Okay problem solved, but I'm not sure how. I originally left the machine with the spinning circle for a couple of hours. Later in the day I did a cold boot and after 5 mins it boted into the stock ICS.
Thanks for the suggestions and help!
Hi guys. My nexus 4 is rooted. Everything was perfect. I just wanted to do a fresh start. I did factory reset. Then it rebooted. Came to language selection. I selected English and than suddenly screen was black and nothing happened. I restarted again and it stuck on nexus logo. I did downloaded root toolkit 1.63 and it found my model and its selected 4.2.2 automatically. Then it downloaded stock image file and said my device adb error saying need to select USB debugging mode. I can't cause its stuck. Now about the rom it was liquidsmooth rom. Please help me how to go back to stock android 4.2.2. Thanks.
hi,
did u try to wipe cache/dalvik?
Bro I do not know what happened but I did volume up and power for 20 secs and power button again. It showed boot loader mood and switched off the device.
fahad2mail said:
Bro I do not know what happened but I did volume up and power for 20 secs and power button again. It showed boot loader mood and switched off the device.
Click to expand...
Click to collapse
sorry, but for the stock img flash isn't needed just the bootloader mod? The deb mod is useless for this!
Throw it in the trash.
dont use a toolkit, they can create more issues than they are worth. boot into the bootloader, then flash the stock image via fastboot. thats all.
Thanks a lot. I sold it. My bad. Dn wanna use custom rom again.
Sent from my GT-N7100 using xda app-developers app
fahad2mail said:
Thanks a lot. I sold it. My bad. Dn wanna use custom rom again.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Or read up so the next time you won`t get into trouble or at least know how to solve it if you do
My Nexus 10 has been acting up recently...the battery seemed to be draining A LOT quicker then it normally would.....the tablet would just shutdown in the middle of doing something. Fast forward a week or two, now when I turn it on it vibrates for a second, shows the "GOOGLE" logo and starts the boot animation for 4.4, vibrates and repeats the same. I manually formatted and flashed 4.4 (fastboot flash boot ...etc...) and still am getting the same issues...Any suggestions on what to try next?
Flash the newest factory image automatically via fastboot.
Sent from my Galaxy Nexus using XDA Free mobile app
Just did that to no avail....same issue as before...Anything else to try?
It almost seems like it is not charging but I would assume I could still get it to boot up while connected to the charger....correct?
Update....I flashed CWM and sideloaded gapps and a ROM...and tried that...still the result..."GOOGLE" logo comes up and then a vibration...then it goes back to "charging" (the white battery with the lightning bolt through it)
Nobody has anything? Damn...lol
cirenj said:
Nobody has anything? Damn...lol
Click to expand...
Click to collapse
Sounds like it may be a hardware issue, since flashing the factory image didn't even help. I would say trying flashing the factory image using the flash-all method, and wiping data/factory reset right after. Couldn't hurt.
cirenj said:
Nobody has anything? Damn...lol
Click to expand...
Click to collapse
You said you installed cwm -- I assume you mean the recovery rom... If I'm wrong ignore the rest.
I too have had this issue and it was not hardware. To fix this I booted into cwm (the recovery rom I use on my N10) and reinstalled a stock factory boot rom. Just for those that don't know to boot into the recovery rom, power off the tablet, then press and hold the power, volume up AND volume down simultaneously --- finally, use the volume button to scroll to the recovery menu.
uDude
texascwby1836 said:
You said you installed cwm -- I assume you mean the recovery rom... If I'm wrong ignore the rest.
I too have had this issue and it was not hardware. To fix this I booted into cwm (the recovery rom I use on my N10) and reinstalled a stock factory boot rom. Just for those that don't know to boot into the recovery rom, power off the tablet, then press and hold the power, volume up AND volume down simultaneously --- finally, use the volume button to scroll to the recovery menu.
uDude
Click to expand...
Click to collapse
I have tried that as well...I am thinking it is a hardware issue as previously stated....amazing...spend $500 for a piece of hardware only to have it die a little over 12 months later....talk about pissed off....
cirenj said:
I have tried that as well...I am thinking it is a hardware issue as previously stated....amazing...spend $500 for a piece of hardware only to have it die a little over 12 months later....talk about pissed off....
Click to expand...
Click to collapse
No shoot me a PM ..
Lets see if we can get you up and running again ..
If we do we can post what we did back here from all XDA users ..
Thx Josh
I am having the same exact issues. I too force flashed stock 4.4.4 and it still does not boot up. Any ideas on how to remedy this would be greatly appreciated.
Thank you!
Hoping to hear something as well...but doesn't look good...
Can you access adb? To check logcat while it's booting (and possibly find out why it's bootlooping)?
What did you use to format the partitions?
Sent from my Nexus 10 using Tapatalk
I can access adb on my laptop...and I used the "fastboot format" and "fastboot flash"
How would I check the logcat file?
http://forum.xda-developers.com/showthread.php?t=2274119
beekay201 said:
Can you access adb? To check logcat while it's booting (and possibly find out why it's bootlooping)?
What did you use to format the partitions?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I am unable to get my Nexus to show up in command prompt when I run "adb devices". Not sure what to do.
Any ideas? I've tried reflashing stock images and still have the same problems..
michaelearth said:
Any ideas? I've tried reflashing stock images and still have the same problems..
Click to expand...
Click to collapse
Can you give more details about your issue? If its still about not connecting PC and tablet see this guide for help
http://forum.xda-developers.com/showthread.php?t=2277112
demkantor said:
Can you give more details about your issue? If its still about not connecting PC and tablet see this guide for help
http://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
The problem is that my tablet will reboot constantly and it shows my battery being fully drained even after charging it overnight. I'm able to force flash stock images to my tablet and this has not fixed the issue. So at the moment my nexus 10 is an expensive paperweight.
What happens when booted to bootloader or recovery? Does it act normal or loop?
demkantor said:
What happens when booted to bootloader or recovery? Does it act normal or loop?
Click to expand...
Click to collapse
When I boot into the bootloader it acts normal.
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
redbay1 said:
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
Click to expand...
Click to collapse
That is the norm for fastboot, it doesn't go past that screen.
It may not make a difference, did you try to boot to recovery via Power+Volume Down buttons?
Greetings Khaos64,
Yes, I've tried booting with Vol-Down+Power but the phone does not start.
With volume-up+power, I get the Fastboot splash screen but the phone does not respond to any input.
I tried selecting "bootloader" from the reboot menu but I get the same thing: Reboots and after a second, the phone reboots again normaly and into OxygenOS.
Is there a way to verify if the bootloader or recovery is corrupt and maybe reflash the stock recovery onto the phone?
Thanks for your input!
You may just want to go straight to oneplus support since everything is stock and only 2 weeks they should be able to get you updated or replace it.
If you'd like to be more hands on... maybe something below can help.
So your phone isn't recognized/no commands acceptred from your computer when booted to fastboot?
Such as unlocking your bootloader and booting into twrp... "fastboot boot yourfilename.img" or maybe flashing it.
Make sure OEM unlocking is selected in Developer options.
If you can't do that then this may not work but is worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
These may also be something to look into:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
I did try to contact Oneplus for support but I am not the one who purchased the phone. Long story short, it was a gift from my girlfriend that she bought off of someone. The phone was new in box and was a warranty replacement. I would have to contact the seller and go trough him for support unfortunately.
Thanks for the different suggestions!, I will fiddle around with it this afternoon while the kids are having their mid-day nap and I'll get back with the results
Thanks again for the help, it's greatly appreciated!
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Congratulations hope you enjoy the phone
Sent from my ONE A2005 using Tapatalk
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
Glad one was able to help you do it. :good:
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
HI there,
I am having the exact same issue with my oneplus 2. Unfortunately i know almost nothing regarding these android thingy. I know it has been almost 2 years, would you mind guide me through the steps? I would appreciate it so much.
Thanks.