I followed this guide on F2FS for N7. After a few hours I managed to unlock and root my N7. The first time I got Slimkat to work except for the fact I was missing Play store. I was forced to reset to stock using Nexus Toolkit after I soft bricked it during my attempt to fix it.
During my 2nd attempt to install a custom ROM I ended up getting the black google screen despite all no errors during flashing or installation of the files. I attempted to fix this in Recovery Mode which lead to a looping boot screen of Teamwin atm. This logo keeps flashing time to time and will continue to do so until I shut off.
OS
Win7 Pro x64
unlocked Nexus 7 2012 16BG
Stock 4.4.4. Kitkat
I have installed the correct drivers and my PC does recognize the N7 connected via USB. However, during the process of fixing the problem it will disconnect and I'll get the ADB device not connected error. I can see it listed in Device Manager but it will immediately disconnect when I try to unbrick it.
I can access the Fastboot window but when I click for Recovery Mode it'll start the Teamwin looping. Resetting the device will return it to the google black screen with no change. Any help or advice would be great. Thanks.
Related
Hi, first of all I love this forum, this is my first time posting here but I found it indispensable when I was doing Android development-related stuff. However I've now managed to do some damage to my phone and need some expert advice!
So I was following the instructions on the CM wiki (I can't post external links yet but the address of the page is /w/Install_CM_for_i9100) for installing CM (I'm using a Mac). I got my phone into download mode and used Heimdall to flash ClockworkMod Recovery. This is where I think I went wrong: Heimdall found the phone fine and transferred everything, however the progress bar held at 'full' for about 5 minutes. After a while I thought it must be done and just doesn't have a confirmation once it's done, so I unplugged the phone and rebooted into ClockworkMod Recovery. Recovery boots up fine but when I try to connect using ADB the phone can't be found. When trying to boot up normally I now get the warning triangle below the Samsung Galaxy logo and the phone just turns off. Booting into download mode, Heimdall can no longer find the phone when it's connected. So, since I can't boot into my stock OS, and I can't transfer a new OS or re-flash CMR, does this mean my phone's bricked? Or is this a known issue with a fix? I've tried the search function on this board but can't find this exact issue.
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
yoda254 said:
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
Click to expand...
Click to collapse
My guess is that when you rooted with CASUAL, it changed the Samsung device driver on your computer and you need to reinstall the Samsung driver to get the computer to recognize the phone again in download mode.
Underneath step 7 of section 1b on Droidstyle's restore guide, he discusses issue with CASUAL replacing the Samsung driver... and he gives a link to Jeremy Loper's fix... "If odin no longer recognizes your device, most likely Casual killed the driver for odin!! follow this tutorial for restoring the driver: http://www.youtube.com/watch?v=zzghcV8HVVk"
Once the computer recognizes the phone again, you should be able to use ODIN to restore back to 4.1.2 so you can root/unlock again with CASUAL. After you get the phone restored with Odin, I would recommend booting into Stock Recovery and wiping cache/doing factory reset before running Casual again... this would enure you are starting over with a totally clean slate.
If the above doesn't work, then here's a thread where I tried to help someone else who couldn't get their computer to recognize the phone.... maybe some of those ideas will help - http://forum.xda-developers.com/showthread.php?p=55833998
Good luck!!
1 step forward two steps back. I got my pc /odin to recognizes my note 2(changed usb cords). Then tried to odin back to stock 4.1.2. At first odin kept saying (odin not responding) and would ask to close the program,after several attemps i final got it to flash the 4.1.2 file. When i flashed the file and was at the point where it reboots, it would not get past the samsung note 2 logo and continued to flicker and not boot up even when i tried to put it into download mode like it said to in this thread. http://forum.xda-developers.com/showthread.php?t=2024207. When i tried to reflash the file it failed. when i attempted again it just hangs at setupconnection. Tried again and it failed. Btw thanks for the help mattnmag.
Got it working! i simply forgot to place the sch-i605 pit. into the pit section of odin when i flashed the 4.1.2 rom.
Similar problems
I was running AllianceROM 26. My phone had been spontaneously rebooting for a bit recently. Today, it started to spontaneously reboot again, but this time, it never got past the Galaxy Note 2 screen. After pulling the battery, I tried to boot into TWRP. It just hangs on the twrp boot screen for a few minutes but never goes into twrp.
I figured I would try taking it back to stock. So, I used ODIN to try and put 4.1.2 on it and a new PIT file. That appeared to work fine. I got no errors in ODIN. However, I still cannot get this thing to get past these boot screens, either the Galaxy Note 2 one or TWRP when I try that there. I have tried this twice now, once with re-partition checked and another time with re-partition unchecked (saw conflicting instructions on that so I figured I would try it both ways). I still am not getting past the boot screen.
Any help or ideas are appreciated as right now, my phone appears to be bricked and I am out of ideas.
so what was the solution to the teamwin flashing on and off after a factory reset? this is certainly not a solution, having to reflash the phone...
Hello,
I have a tablet that looks similar to Q88 A13. CPU is wm8801, OS - Android 4.1. So I had stopped using it and left it sit for like 1 year. Now I charged it and tried to turn on, but it wouldn't get past first logo(the one that appears first, not the os loading one) and would attempt to go into recovery itself, but then the android with exclamation mark would appear for a while and then device would reboot and so on and so on...
Then I triggered a hard reset with a button combo, but it didn't really help. Tablet stopped trying to go into recovery and simply kept getting stuck at logo.
I can't access recovery, and neither ADB nor fastboot is working. PC with win 7 reports it as unrecognized device and other PC with win xp doesn't even see that anything is connected to it.
I've tried unsoldering the battery, completely discharging tablet without it, soldered it back on, but didn't help.
Help?
bump
Try Livesuit 1.11.
I've used it to load several ROM's
I'm currently running FaaastJB v2.5 found at http://forum.xda-developers.com/showthread.php?t=2447819
I am having an issue. Updated kindle fire 6 hd 4th gen to 5.0, downgraded to 4.5.3. Installed king root, rooted device, installed flashify, flashed openrecovery-twrp-2.8.6.0-ariel.img, rebooted. Now I am stuck rebooting . If plugged into a computer loads to the amazon logo, shuts down, loads to the logo repeat.
I have tried to fast boot by correcting drivers in device manager for the mtp whatever and constantly spamming the fast boot string.
I have used adb to see if a device ever loads and it doesn't.
Windows makes the sound that a new device is connected for about 15 seconds then will make the noise that a device has been disconnected as the fire reboots. I want to say it is a soft brick since it attempts to load and is communicating with windows to some degree. I have searched for two days and tried KFFA and an assortment of other tools. Any thoughts or assistance is greatly appreciated. It was only 60 bucks so not really worth sending it in to someone for repair. Also since it was brand new amazon is sending a replacement so this thing is now simply a toy to learn on.
When it can't get past the Amazon logo, there is no hope. OS 4.5.3 should be able to boot TWRP after OS 5.0. Where did you get the 5.0 file? Is it possible you got updated at some point?
ardorcalenture said:
I am having an issue. Updated kindle fire 6 hd 4th gen to 5.0, downgraded to 4.5.3. Installed king root, rooted device, installed flashify, flashed openrecovery-twrp-2.8.6.0-ariel.img, rebooted. Now I am stuck rebooting . If plugged into a computer loads to the amazon logo, shuts down, loads to the logo repeat.
I have tried to fast boot by correcting drivers in device manager for the mtp whatever and constantly spamming the fast boot string.
I have used adb to see if a device ever loads and it doesn't.
Windows makes the sound that a new device is connected for about 15 seconds then will make the noise that a device has been disconnected as the fire reboots. I want to say it is a soft brick since it attempts to load and is communicating with windows to some degree. I have searched for two days and tried KFFA and an assortment of other tools. Any thoughts or assistance is greatly appreciated. It was only 60 bucks so not really worth sending it in to someone for repair. Also since it was brand new amazon is sending a replacement so this thing is now simply a toy to learn on.
Click to expand...
Click to collapse
You probably Flashified TWRP into your boot partition (instead of recovery). Since TWRP not signed, it will not boot. You can probably get into 4.5.3 recovery by pressing Pwr + Vol+ during boot, but that's not going to do you much good. Anyway, if Amazon can get you a replacement, go for it!
DoLooper said:
When it can't get past the Amazon logo, there is no hope. OS 4.5.3 should be able to boot TWRP after OS 5.0. Where did you get the 5.0 file? Is it possible you got updated at some point?
Click to expand...
Click to collapse
When I say 5.0 I am talking generic. I updated it to that version in order to downgrade the OS.
bibikalka said:
You probably Flashified TWRP into your boot partition (instead of recovery). Since TWRP not signed, it will not boot. You can probably get into 4.5.3 recovery by pressing Pwr + Vol+ during boot, but that's not going to do you much good. Anyway, if Amazon can get you a replacement, go for it!
Click to expand...
Click to collapse
Yeah I tried that. I get reboot or erase everything and restart. Neither works.
Hey guys,
So really in need of a little help. My OnePlus X started acting strange when it refused to take charge when it was booted into OS (Lineage). However, I noticed that if the phone was off, it would boot immediately upon connecting a cable. So it seemed as if nothing was wrong with the port or the cable (tried various cables and chargers). A little more digging revealed that the phone charges in Fastboot mode. Anyway, I decided to factory reset it and for some reason it was stuck in a boot loop.
I then tried to restore back to stock using Mega Unbrick Guide which worked in the past. Now my problem is that its stuck in fastboot, wont boot into the OS. I can boot to the recovery and fastboot. In recovery when I choose Install from local, i get no browser to search the SD for zip files, nor does the phone detect for me to use adb sideload.
Any ideas as to why this is so?
Thanks!