I accidently wiped my ROM in twrp while trying to install a new one. I tried to use ADB to push the the file into my nexus 7 but it does not work (I've gone through hours of troubleshooting and nothing worked). So I purchased a OTG cable which twrp noticed but when I tried to install various roms I either get to the google logo and a reboot back into recovery or I get a loop of the starting animation. I have no idea what to do considering none of my computers can notice the device and none of the roms seem to work.
NotARobot91 said:
I accidently wiped my ROM in twrp while trying to install a new one. I tried to use ADB to push the the file into my nexus 7 but it does not work (I've gone through hours of troubleshooting and nothing worked). So I purchased a OTG cable which twrp noticed but when I tried to install various roms I either get to the google logo and a reboot back into recovery or I get a loop of the starting animation. I have no idea what to do considering none of my computers can notice the device and none of the roms seem to work.
Click to expand...
Click to collapse
Have you tried flashing a Factory Image through the bootloader?
Can you try install some custom rom via TWRP?
Related
I'm kind of stuck here. I'm not big into flashing roms and stuff.....but had issues with the one ROM I flashed 2 years agao so I thought I'd upgrade to CM10 finally. I flashed it properly using CWM and had a working rom....but forgot todarkside super wipe and to install the gapps.zip. So I thought I'd just do it over again. Everything seemed fine in the reinstallations of all 3.....but when I started the phone up it got stuck on a boot loop on the Cyanogen animation. No big deal....I'll just flash it again. Go into recovery mode.....wipe the data/cache.....it freezes on the cache. Try to flash the rom, cWM , the old rom, anything.......it gets stuck on the first "Installing....." . Not good. Can't do anything in CWM.
So I read a million webpages trying to figure out what to do next......someone else had to have had this problem. Seems like my only option is to go through Odin and flash it there. I make sure I get the USB drivers from Samsung and install those first. The installation goes through no problem......I reboot....and then try to plug in my phone via Download Mode. I make sure I use the USB cable that came with my phone and use a powered port on the back of my computer (XP btw). Windows recognizes it with its usual bull**** fanfare of 3 different notifications......"Found New Hardware!" then it says Found! "MSM8x60" then it says Windows failed to fully install new hardware. In the Device Manager its shown as the "Samsung Mobile USB CDC Composite Device" with the dreaded yellow exclamation mark on it. I tried uninstalling the drivers....rebooting.....and then reinstalling. No luck. Tried an older driver package.....no luck. I've spent hours trying every combination with no luck. I can't get Windows to recognize it....or more importantly.....Odin to recognize it. Any thoughts? Thanks.
Sorry for my English.
A lot of different things can happen if you are not using the correct version of recovery. The latest recovery doesn't always mean it will flash properly. For example I had to use TWRP 2.6 for 4.3 based ROM and had to roll back to TWRP 2.5 for some other versions of a rom. I don't know which version of CM you are using but maybe try TWRP or another version of CM.
Sent from my SGH-T989D using Tapatalk
Yeah....that makes sense. But how do I flash a different version of CWM? I can't get the phone detected by Odin.
Resolved.....tried a couple of other PCs....found one that worked
Hi there,
I've been trying to fix this issue for a while now and I haven't seen any guides on my particular issue.
Basically what's going on is I tried doing a factory reset on the phone while having cyanogenmod flashed and when it booted, it would keep booting up in the recovery.
There seem to be no backups or roms on the phone.
Now here's the kicker, when I try using the Nexus root toolkit, it doesn't recognize my device whatsoever. I've uninstalled the drivers fully and reinstalled them and still nothing.
When I plug the phone in, it doesn't show up as an external source (other than in the device manager with a "!" by 'galaxy nexus'), so I can't just put a ROM on there and try flashing that.
I'm stuck. I have no idea what I can do to get this back up & running.
It's a GSM phone, being from Canada I believe it to be Yakju...
Anybody have any ideas? I really need this phone to start working!!
Have you tried the method in this tutorial?
you may bring ti back to samsung customer service.
Hey XDA,
I am stuck here trying to get my Galaxy S 6 to boot after installing TWRP. I cannot use ADB sideload because I did not link the device to my computer prior to installing the bootloader. I thought the device would boot normally but here we are...
First I used pingpong to root my device.
Then I went into the TWRP app from the Play Store to install 2.8.6.0 (the 2.8.6.2 version did not show up as an option unfortunately and I wasn't aware it was released).
The phone rebooted into recovery just fine (knox was not tripped).
Once I tried to reboot normally, the phone just loops after the yellow Sprint spark loading screen.
I have tried to use adb sideload which won't work because it shows in offline mode.
I need to somehow get a stock zip to show up in TWRP I would be fine but I am not sure how to do this... USB OTG seems like it should work and I have a new cable coming in the mail.
Anyone have an idea?!
Thanks in advance
Honestly the best way would be to ODIN back to stock and start fresh. This way you won't have to wait for the OTG cable to come in the mail.
For your next root and TWRP flash attempt, try to use flashify and the provided TWRP image in the Original development section of this forum.
Keep me posted. @ me if you reply so I can see the comment!
Good luck soldier!
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.
Hi there,
To those reading this, many thanks. I've used this site for tons of advice on modding my phone but I'm still a relative noob to it all. I recently tried to flash a custom rom (CM13) to my Nexus 5X bullhead but upon installation, it get's stuck on the Google Logo. Now, I've tried my best to research this issue online but I just can't seem to find a solution.
Initially, I flashed TWRP Recovery and then installed CM13. No dice. It got stuck at the Google logo. I've since tried several releases of CM including a few nightly. I tried to change the Recovery image to CM Recovery but it didn't help. Other things I've tried:
Revert my phone back to Stock using the stock ROMs provided by Google for 'bullhead'. I get the error "Could not find 'META-INF/com/google/android/update-binary'".
Flash a stock Nexus 5X ROM I found here on xda but it still froze at the Google logo.
I tried to diagnose it as a persistent partition via this guide. Still no luck. The guide prompted my phone would acknowledge my commands from adb shell but shell doesn't seem to recognize the commands I give here.
Currently, my phone is just cycling through boots and stopping at the Google logo. I want to be clear that this not the animated 4 circles you see when starting up the stock nexus ROM. My phone was doing that as well at some point.
I'd appreciate any assistance. I'll try my best to respond promptly.
Many thanks.
http://forum.xda-developers.com/nexus-5x/help/nexus-5x-stuck-google-screen-wont-boot-t3457981
http://forum.xda-developers.com/nexus-5x/help/nexus-5x-bricked-solutions-t3464569
According to Google, its a hardware issue.