No OS Nexus 7 (flo) Bootloop. - Nexus 7 (2013) Q&A

Hi everyone,
I really need help since i found no solutions to my problem.
I wiped all my data with TWRP and even my OS. I have nothing installed and when i try to boot the Nexus it just goes in a bootloop. I can't flash anything from TWRP and when i try to copy a ROM to my Nexus via my PC, the PC just doesn't recognize the Nexus, thus i can't see the internal storage. Flashing stock doesn't work ever because of unrecognized device. What should I do ? is there any solutions to my issue ?
Thank you for reading.

Nexuuss17 said:
Hi everyone,
I really need help since i found no solutions to my problem.
I wiped all my data with TWRP and even my OS. I have nothing installed and when i try to boot the Nexus it just goes in a bootloop. I can't flash anything from TWRP and when i try to copy a ROM to my Nexus via my PC, the PC just doesn't recognize the Nexus, thus i can't see the internal storage. Flashing stock doesn't work ever because of unrecognized device. What should I do ? is there any solutions to my issue ?
Thank you for reading.
Click to expand...
Click to collapse
I got the same issue. Since I couldn't find a solution anywhere, I replaced the device yesterday. I tried everything you have. No solution. The display on mine was partially damaged. Don't know if that was related to the issue or not.

I just did what you did moments ago (deleting OS by accident) and I have no way of installing a new ROM on there since the computer stopped recognizing my nexus 7 after rooting it for a few hours a few months back..

MiKaiiEL said:
I just did what you did moments ago (deleting OS by accident) and I have no way of installing a new ROM on there since the computer stopped recognizing my nexus 7 after rooting it for a few hours a few months back..
Click to expand...
Click to collapse
Here is a new tip!
A few moments ago I found a workaround that fixed the problem, at least for me!
First, I charged the tablet up to 8%;
then, I booted into bootloader mode.
By the way, my bootloader was unlocked.
Becuase I had no OS installed, nor a custom recovery, I had little hope that the computer would recognize my device.
HOWEVER, when I used an identical cable (one that came with a different Nexus 7 2013,
The program "Nexus Root Toolkit" recognized the tablet, automatically flashed the stock firmware!
To ANYONE who has had this problem, TRY MAKING THESE SMALL CHANGES.

Boot into TWRP and start the adb sideload. Simply run adb sideload 'file name' from the ROM directory on your pc. Either that or flash stock with fastboot.
Make sure you have installed adb drivers properly otherwise your device wont be found. I have several problems with MTP from recovery, so use the sideload function.

Related

[Q] Help w/ semi-bricked device (please)

I bought this Verizon Galaxy Nexus a while back to use as a media player on a trip.
It already had Paranoid Android on it.
After the trip, I messed around with it, and stupidly wiped everything but TWRP v2.3.2.1.
Now I have a device that boots into TWRP, but thats it. There is nothing to Restore or Install.
I have downloaded updated ROMs, but when I plug into my PC, the phone isn't visible.
Any advice would be appreciated.
scottfish said:
I bought this Verizon Galaxy Nexus a while back to use as a media player on a trip.
It already had Paranoid Android on it.
After the trip, I messed around with it, and stupidly wiped everything but TWRP v2.3.2.1.
Now I have a device that boots into TWRP, but thats it. There is nothing to Restore or Install.
I have downloaded updated ROMs, but when I plug into my PC, the phone isn't visible.
Any advice would be appreciated.
Click to expand...
Click to collapse
load a rom into memory card.put it onto nexus.if twrp has file manager to copy from memory to internal.or flash by browsing there.and flash.....tada
scottfish said:
I bought this Verizon Galaxy Nexus a while back to use as a media player on a trip.
It already had Paranoid Android on it.
After the trip, I messed around with it, and stupidly wiped everything but TWRP v2.3.2.1.
Now I have a device that boots into TWRP, but thats it. There is nothing to Restore or Install.
I have downloaded updated ROMs, but when I plug into my PC, the phone isn't visible.
Any advice would be appreciated.
Click to expand...
Click to collapse
I have a good feeling that your pc is detecting your phone because of the twrp. This happened to me. I would download the latest TWRP and flash it using fastboot.
Once I updated to TWRP 2.8.0.x, I was able to use adb again in recovery which it seems like you know how to do. If you have any questions about anything, let us know though. Hope this helps man.
INSTRUCTIONS
-Get to the bootloader with volume up + volume down + power.
-Connect the phone to the PC. Enter at the command "fastboot devices" to see it show up.
-Now locate your newly downloaded TWRP.img. Enter:
Code:
fastboot flash recovery <path_to_recovery.img>
Thank you for this.
I actually got a crash course in ADB last night. I was able to pushe several ROMs into memory, but nothing stuck. They all kept failing.
The phone was rooted and had Paranoid Android on it when I got it. i never had success running anything else on it.
I think your instructions will help me get TWRP updated which should help. So far, I pushed the new TWRP image with adb, but didn't know what to do with it.
I will mess around with it more tonight.

[Q] Nexus 7 2013 Stuck with two errors

Hello guys,
I had my Nexus 7 2013 (Wi-fi) for almost an year running stock rom and I decided to install CM12+ElementalX. It was all good untill yesterday when I returned it back to stock 5.0.2. When i started the tablet a message popped about 5.1 update and I started the update, but in the middle of the process it said "ERROR". I rebooted the device and now its stuck on the screen where you have to choose your language, with two errors constantly popping up - "PHONE HAS STOPPED WORKING" and "NFC Service has stopped working". I press OK like mad trying to skip some of the steps,but the "touch and go" (i think thats the name) is as far as i can go.
Is there any way I can flash the stock 5.1 without USB Debug Mode. There is no way i can get in the tablet's menu. I also saw some of the othere topics with this kind of problems, but i didn't find the answer.
You don't need USB Debugging to flash the factory images... use fastboot.
Telyx said:
You don't need USB Debugging to flash the factory images... use fastboot.
Click to expand...
Click to collapse
Can you please explain with few steps. I tried everything and i don't know what am I missing
P.s. I dont have custom recovery and i cant turn debug mode on
Ramirezz27 said:
Can you please explain with few steps. I tried everything and i don't know what am I missing
P.s. I dont have custom recovery and i cant turn debug mode on
Click to expand...
Click to collapse
I have installed ADB i Android SDK. Everythink is working fine on my Nexus 5 , but i cant do anything with my Nexus 7 which is now constantly rebooting after i managed to go through all the starting steps , when it started to install my 36 apps it rebooted by itself and now it keeps doing it.
i am having similar issue. i have tried the root tool several times with no success. ive been rooting devices since the samsung moment and i cannot get this tablet going at all. with the root tool i am able to flash twrp recovery, but for some reason it will not mount to put a rom on the internal memory. i have even tried pushing a stock rooted rom through adb fastboot and it just hangs. what else can i possibly do? could it be hardware related? this all happened after i was prompted for the latest 5.1.1 update. any tips or suggestions would be greatly appreciated. tia

Bootloop after Installing Nethunter 2.0 (Nexus 7 2013 Wifi)

Hello everybody,
i hope the xdadevs can help me with my problem.
Since two Days i try to recover my Nexus 7 form a bootloop.
A week ago i flashed Kali Nethunter 2.0 via TWRP on my Device (Nexus 7 2003 Wifi) - Everything worked fine till yesterday.
My device run out of energy so i loaded it and startet it shortly after that.
Then i regognized the bootloop. I tried to restart the device but it had no effect.
After that i tried to boot into the Recovery Mode with TWRP to restore my working backup. But it got stucked on the loading screen of TWRP too.
Now i tried to recover some images and fix the problem with some manuals which seemed promising. - no success
After a while i did something incredible stupid and locked my bootloader again (i wanted to try to lock and unlock it since some tools couldnt flash the stock rom).
The situation right now:
I cant boot up normaly: Stuck while "Google" is displayed
I cant boot in Recovery Mode (TWRP): Stuck on the blue TWRP Logo
If i try to use the Skipsoft Toolkit or something else it fails - or do i miss something
Recover the Stock rom by using the "flash-all.bat" fails because of this (pastebin. c0m/ie0dBv1D). I used the stock rom of Android 4.4.4(razor-ktu84p) because every other stockrom says this (pastebin. c0m/Dz31k8qu).
I wonder why the stock rom needs to get the bootloader unlocked... ive red so much about it that it just works out of the box..... am i doing something wrong ?
If i try to unlock again, the selection screen on the tablet shows up. I choose yes and hit the Power button. At the console the output <bootloader> erasing userdata" shows up and "freezes?!"... nothing happens afterwards.
Thats about it and this is where i am stuck. I would really appreciate if someone could help me ! I would even reward or spend some money on help.
I try to fix it meanwhile and update this post if something new happens.
I had to alternate the links because im a new member, im sorry for that !
Thanks in advanced and sorry for the spelling
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
diehard2013 said:
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
Click to expand...
Click to collapse
Yeah i tried it but it couldnt fix my problems. Returning to Stock Rom will always tell me that i need the bootloader unlocked... and i cant unlock it.
My PC and Linux Notebook where recognizing before it was bricked. Now it only gets detected in fastboot because it wont start anymore.

Please help guys my phone died.... :(

Hello guys i need help with my galaxy nexus. I'll explain what happened - I was running zmod 5.1.1 since quite some time without any problems, but the phone had become slow due to loads of apps on it so i decided to do a fresh install of zmd 5.1.1 again. I did the fresh install and the phone was working absolutely fine for 2 days, but yesterday the phone restarted randomly and since then the whenever i try to boot the phone it restarts when it reaches the lock screen. Some times it doesnt restart and stays on but it becomes highly unresponsive and eventually restarts. I have twrp recovery and sadly i forgot to do a backup after the fresh install of the zmod rom. I am able to boot into recovery and the phone is recognized by my pc when i connect with the usb cable. I tried to place the rom and gapps again into folder when i connected my nexus to pc but when i go into recovery the files are gone.
Then i tried to troubleshoot with nexus root toolkit but it says some drivers are missing and for complete driver installation i need my phone to work which isnt working so i left it. Then i tried to manually flash stock rom with help of adb and fastboot. Every command worked perfectly with adb and fastboot and i managed to flash stock rom 4.3 yakju jwr66y factory image, but as soon as i booted the phone it began booting with the zmod animation and restarted at lock screen. I am clueless as to what has happened and need experts to please help me out as this is my only phone.
P.S i do not post here regularly so if i have made mistakes posting this query please forgive me.
patelsuneesh said:
Hello guys i need help with my galaxy nexus. I'll explain what happened - I was running zmod 5.1.1 since quite some time without any problems, but the phone had become slow due to loads of apps on it so i decided to do a fresh install of zmd 5.1.1 again. I did the fresh install and the phone was working absolutely fine for 2 days, but yesterday the phone restarted randomly and since then the whenever i try to boot the phone it restarts when it reaches the lock screen. Some times it doesnt restart and stays on but it becomes highly unresponsive and eventually restarts. I have twrp recovery and sadly i forgot to do a backup after the fresh install of the zmod rom. I am able to boot into recovery and the phone is recognized by my pc when i connect with the usb cable. I tried to place the rom and gapps again into folder when i connected my nexus to pc but when i go into recovery the files are gone.
Then i tried to troubleshoot with nexus root toolkit but it says some drivers are missing and for complete driver installation i need my phone to work which isnt working so i left it. Then i tried to manually flash stock rom with help of adb and fastboot. Every command worked perfectly with adb and fastboot and i managed to flash stock rom 4.3 yakju jwr66y factory image, but as soon as i booted the phone it began booting with the zmod animation and restarted at lock screen. I am clueless as to what has happened and need experts to please help me out as this is my only phone.
P.S i do not post here regularly so if i have made mistakes posting this query please forgive me.
Click to expand...
Click to collapse
Your eMMC chip may be beginning to fail .One little sign of it is when you said you copied files to it but they weren''t there . Here's what I mean . You copy 20 files to the phone and place them in downloads . You then boot to recovery but you don't see the files . In comparison you delete 10 files using the pc . You boot into recovery and the 10 files are still there . So you hook it to the pc with a toolkit and successfully restore it to a factory image and when you reboot it's not the factory image but the old rom . That' is a clear indicator that the eMMC chip has likely failed or is failing . The chip is sort of locked in a snapshot , or last picture of the phones state before it failed . No matter what you do nothing changes . Google bad eMMC to learn and get a better explanation than I'm giving . I have one nexus with a bad eMMC . Mine won't boot at all , and can finally get into twrp after about a 15 minute wait . Then if I click on anything in twrp it's another 5 minute or more wait . I tried everything . My suggestion to find out is get wugfresh nexus toolkit . Follow all the directions on restoring the factory image to a bricked phone . If you are successful in restoring and you reboot and you see the zmod animation you might as well toss the phone in a drawer and get yourself another phone . The reality of it as best i can tell is you really are adding and deleteing files and you really are restoring the image but through the eye of the eMMC you haven't changed a thing . It has to function and see the changes . Compare it to looking at a webpage . Everything you click actually works but all you see is the same damn page . The connection is broken between whats displayed and what's really happening in the background . Hope this helps . It's the understanding I have of it and some of it might not be exactly right . If anyone with the knowledge disagrees with any part please feel free to correct and explain any part of it . Thanks
patelsuneesh said:
Hello guys i need help with my galaxy nexus. I'll explain what happened - I was running zmod 5.1.1 since quite some time without any problems, but the phone had become slow due to loads of apps on it so i decided to do a fresh install of zmd 5.1.1 again. I did the fresh install and the phone was working absolutely fine for 2 days, but yesterday the phone restarted randomly and since then the whenever i try to boot the phone it restarts when it reaches the lock screen. Some times it doesnt restart and stays on but it becomes highly unresponsive and eventually restarts. I have twrp recovery and sadly i forgot to do a backup after the fresh install of the zmod rom. I am able to boot into recovery and the phone is recognized by my pc when i connect with the usb cable. I tried to place the rom and gapps again into folder when i connected my nexus to pc but when i go into recovery the files are gone.
Then i tried to troubleshoot with nexus root toolkit but it says some drivers are missing and for complete driver installation i need my phone to work which isnt working so i left it. Then i tried to manually flash stock rom with help of adb and fastboot. Every command worked perfectly with adb and fastboot and i managed to flash stock rom 4.3 yakju jwr66y factory image, but as soon as i booted the phone it began booting with the zmod animation and restarted at lock screen. I am clueless as to what has happened and need experts to please help me out as this is my only phone.
P.S i do not post here regularly so if i have made mistakes posting this query please forgive me.
Click to expand...
Click to collapse
Faulty motherboard. Try to find a second hand one on eBay. I had the exact same problem and a "new" motherboard solved it
Sent from my Galaxy Nexus using XDA-Developers mobile app

Find 7a won't boot to recovery, not recognised in USB at all

Hi all,
I'm turning to forums now because I'm desperately in need of help.
I have an Oppo Find 7a which I bought about 9 months ago. When I first got it I tried flashing Cyanogenmod to it (unsuccessfully), and then tried rooting the phone. I have since unrooted the phone, and am running Color OS v 1.2.5i and really really need to update. Problem is, I cannot seem to update the operating system. Here's what happens:
Phone fails to boot to recovery
In my attempts to install Cyanogenmod, I installed a custom recovery. However I couldn't get Cyanogenmod to flash properly, so I tried reverting to the stock recovery. Did that, which seemed to work fine. However, since rooting and unrooting my phone, I cannot boot into reocovery at all. When turning off the phone and then pressing power+volume down to try and boot in, the "OPPO" logo comes up as if trying to boot into recovery, then the phone just turns off and boots into normal OS. Have tried many things but can't seem to get into recovery at all. This means that when an OS update is detected (which it is), the phone tries to reboot into recovery to install the update and cannot. So I'm stuck on a very buggy OS and can't do anything to update. Before you suggest adb+fastboot solutions, please read below:
Phone not recognised in PC at all
When plugging the phone into a PC via usb cable literally nothing happens (aside from the phone detecting it is charging). The phone does not mount as a volume in Windows, the phone is not detected as a device in device manager, as far as the computer is concerned, the phone is not even there. I have tried having the phone plugged in and installing all the proper adb drivers, but this has still yielded no results. And yes USB debugging is definitely enabled on the phone. I don't know why, but for some reason I literally cannot plug my phone into a PC anymore which limits me a LOT in terms of fixing the problem above.
Basically I really need to update the OS on this phone and am compeltely stuck: nothing seems to work. Can anyone help me out here. What do I need to do?? Any help is greatly appreciated.
seem adb device in windows device manager when the phone plug USB at bootloader?
if yes, you can use adb+fastboot solution

Categories

Resources