Okay guys, this is another one of those unbrick threads. I have been installing roms and kernels quite a lot recently, but I recently came into a problem. I hit wipe sd card, and it wiped all of the roms, and apps from the device. I basically have nothing installed. I do have twrp, nexus root toolkit, and adb though, so what should I do? Thanks
Try returning to stock. That also happened to my friend who has TWRP. It seems like TWRP screws up a lot of peoples devices. He had an S2. He just returned to stock and reflashed CM10 and it was fine. Now he is a CWM user.
Sent from my SGH-T989 using xda premium
How would I re install those roms though, it even deleted the backups . I have adb but no fast boot
Adb push a rom.zip to /sdcard then install it from recovery
Sent from my Nexus 7
Don't I need fastboot for that?
Also left recovery and now the hardware keys don't work but adb still does, so I don't know if I can get back in to recovery
Download your stock ROM, and reflash it.
You will get a ton of thanks if you can walk me through it .
The keys probably don't work while in the bootloader because of the stupid bug, connect it via USB and it probably will. You can use adb while the device is booting up (or stuck halfway booting up) or you can use fast boot from the bootloader to bring it back to stock. Check the unbrick threads for instructions on how to do it.
Just get Wug's toolkit and click on the "Flash Stock And Unroot" Button.
---------- Post added at 04:46 PM ---------- Previous post was at 04:31 PM ----------
Just get Wug's toolkit and click on the "Flash Stock And Unroot" Button.
I'll try it thanks
Sent from my Galaxy Nexus using Tapatalk 2
Tried it, but at the end it said fastboot device not found. What should I do?
How should I go about using Odin ? Would it work? Thanks
Related
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?
Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?
Click to expand...
Click to collapse
What you are doing wrong is using a toolkit. Follow these instructions. http://forum.xda-developers.com/showthread.php?t=2018179
I use mskip's Nexus 4 Toolkit without any issues. So far I've used it to root, install clockworkmod recovery and flash the stock image after messing up a build prop edit. Saved me a lot of headaches as I haven't used adb or fastboot commands in over a year, don't even have the sdk installed any more. This is the first phone since I got my Incredible in 2010 that I actually wanted to put a custom recovery on and play with.
Here are some basic questions. Did you unlock your boot loader? Do you have usb debugging enabled? Does your device show up when when your plugged in and booted up into fastboot? Do you have the correct drivers installed? Which recovery are you trying to install and did you try the other one available? Did you use the toolkit to root and did it work?
Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?
Click to expand...
Click to collapse
After you root the device using the toolkit, it is easiest to download ROM Manager or Goo.im from the Play Store to install your custom recovery.
As Ed Daddy said, it's best to use ADB, however, it would save you some times and a few headache if you could just go ahead and download ROM Manager. Sometimes people forget there are *really easy* ways to do stuffs.
KyraOfFire said:
After you root the device using the toolkit, it is easiest to download ROM Manager or Goo.im from the Play Store to install your custom recovery.
As Ed Daddy said, it's best to use ADB, however, it would save you some times and a few headache if you could just go ahead and download ROM Manager. Sometimes people forget there are *really easy* ways to do stuffs.
Click to expand...
Click to collapse
While I agree there are "really easy" ways to do things, I was trying to point him in the direction of learning.
Obviously since they don't know how to flash a recovery, they probably aren't familiar with much else.
Learning how to do things properly never hurt anyone.
Sent from my Nexus 4
Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp...
...Am i doing anything wrong?
Click to expand...
Click to collapse
El Daddy is correct.
Toolkits are silly on Nexus devices, for Nexus the simplest way is flashing via faboot. At the very least take the time to learn from the guide that El Daddy provided a link to. With that knowledge you'll be able to resolve issues like this and help others who get stuck.
Actually I unlocked my bootloader, rooted the device. Using normal OTA 4.2.1
But it seems that every toolkit cannot flash the recovery.
I will try it now with using adb commands...
All the toolkits are are scripts that run the fastboot and adb commands for you, they're nothing complicated and IMO from someone with experience I prefer using them now as I no longer have the sdk installed. Gave up on custom ROMs, my own and others, a long time ago.
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
Toobie said:
Actually I unlocked my bootloader, rooted the device. Using normal OTA 4.2.1
But it seems that every toolkit cannot flash the recovery.
I will try it now with using adb commands...
Click to expand...
Click to collapse
Actually it's fastboot not adb that you use to flash recoveries, two different animals. and to the poster recommending ROM Manager, its kind of borked right now and I wouldn't use it to flash anything.
Edit: spoke too soon on ROM Manager looks like Koush updated it and it appears to be working properly. This was the first app I ever bought back in 2010 when I first rooted my Eris and couldn't get clockworkmod recovery to install, the moderators at the time recommended ROM Manager to me to get it installed as nothing else worked.
Yeah, but both didn't work.
I used now the adb commands on my one, still remembering them from my Nexus One, and see it works
For sure fastboot and adb will work. I used it very recently when my n4 updated. Just make sure to download the latest cwm. Had a boot loop the first time as I used an old one. Hehehe
Edit: actually not sure if it was the old fastboot files or cwm that caused the error. Anyway I updated my sdk so everything works well
Sent from my Nexus 4 using Tapatalk 2
Actually all the tools booted the phone fine in the fastboot mode, telling me flashing the recovery is fine.
But every time i wanted to reboot in the recovery i got this android roboter with the red alarm...
with the normal adb commands everything was really fine!
You're getting that because flashing custom recovery alone without modifying a file or two generates stock recovery every after a reboot. Go to your /system folder and look for recovery-from-boot.p and rename that to whatever you like then flash the custom recovery again
Sent from my Nexus 4 using Tapatalk 2
thephantom said:
You're getting that because flashing custom recovery alone without modifying a file or two generates stock recovery every after a reboot. Go to your /system folder and look for recovery-from-boot.p and rename that to whatever you like then flash the custom recovery again
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Sounds great, will try that.
Thank you.
I rooted my N7 using the Nexus 7 Toolkit. Dowloaded several ROMS straight from the device to try a few out and flashed them using CWR. After realizing I was not overly happy with any of the ROMS I decided to flash back to stock. I attempted to use Step 9 in the toolkit (download, extract and flash google factory stock rom) and when it asked me if i wanted to format the device before installing I selected yes. The install failed and now the device is stuck on the fastboot screen, but non of the options work. I am assuming usb debugging is not selected as I was wiping data before each install and was installing directly from the devices memory. As it sits adb will not even recognize the device and I am hoping I have not bricked my device. Please help if you have any advice to offer. I would appreciate replies being detailed. Thanks in advance.
mawilhoit said:
I rooted my N7 using the Nexus 7 Toolkit. Dowloaded several ROMS straight from the device to try a few out and flashed them using CWR. After realizing I was not overly happy with any of the ROMS I decided to flash back to stock. I attempted to use Step 9 in the toolkit (download, extract and flash google factory stock rom) and when it asked me if i wanted to format the device before installing I selected yes. The install failed and now the device is stuck on the fastboot screen, but non of the options work. I am assuming usb debugging is not selected as I was wiping data before each install and was installing directly from the devices memory. As it sits adb will not even recognize the device and I am hoping I have not bricked my device. Please help if you have any advice to offer. I would appreciate replies being detailed. Thanks in advance.
Click to expand...
Click to collapse
ok firstly you should have made a backup from clockworkmod before you flashed anything! as then you could have just reflashed it and been right back to square 1.
secondly stay calm your not bricked. adb does not work while your in fastboot mode. only fastboot mode does. i suspect that you had a bad download and its had an issue while flashing your stock rom.
so, download your prefered android version from here making sure to download the correct type for your n7 IE wifi for wifi and mobile or the 3g version. if you use the wrong type you can brick your tablet.
then simply follow this guide, changing the names of the files to match the one you download. if you follow this guide you will bet your device back to stock and bootl-able.
just make sure you have a working adb/fastboot folder and make sure you place the extracted files in that folder before you try to flash anything.
good luck pal
---------- Post added at 10:59 AM ---------- Previous post was at 09:59 AM ----------
http://forum.xda-developers.com/showthread.php?t=2199373 also see here, same issue seemingly...
Sent from my Nexus 7 using xda premium
Hello there
I have a Nexus tablet that somehow got bricked on the last update (will not boot the OS) but I can boot into recovery mode. I have tried using Nexus Toolkit and can see the device through adb. I have all the necessary drivers as well.
My problem is that I cannot put a new image onto the SD card using adb because USB debugging mode is not enabled which can only be enabled by the OS which wont boot.
What do I do?
Sorry if this isnt the right forum for this.
Thanks
Have you tried factory reset? Might be your only option.
Sent from my Nexus 7 using Tapatalk 4
iBolski said:
Have you tried factory reset? Might be your only option.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yeah I tried that many times
flash twrp. Twrp supports Adb
That reminds me when I flashed the rong
factory image lol.
1.download a factory image for your n7
2.get Nexus Root Toolkit and open it
3.in the toolkit go to back to stock
4.select Soft-bricked/bootloop
5.then select Flash stock + unroot
6.and everything else Is pretty much self-explanatory
I hope I helped
If you need more help just tell me.
---------- Post added at 08:45 AM ---------- Previous post was at 08:31 AM ----------
PS. you can get your factory image from herehttps://developers.google.com/android/nexus/images?csw=1
Hi, I used Timmy Deans tool on my Iconia 501 the at&t version and it put me on the A500 3.2.1 and rooted me with cwm recovery. I am looking to g o all the way up to Kit Kat and dont want to mess my tab up any one point me to info and steps? please?
Kit Kat? Acer only updated to our tab to ics. unlock the boot loader and flash a custom rom
Sent from my HTC_PN071 using Tapatalk
Hmmm, I guess I was not clear, I am rooted and have cwm. Do I not need to change my base and if I'm on hc 3.2.1 before I go to kit kat? I am pretty sure I read that I need to update some stuff? I can just flash kit kat straight from hc?
Sent from my A500 using XDA Free mobile app
I just read a recent post on what bits u needed for it...in dev forum I think
Sent from my HTC_PN071 using Tapatalk
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
http://forum.xda-developers.com/showthread.php?t=2723258
Sent from my HTC_PN071 using Tapatalk
---------- Post added at 07:09 PM ---------- Previous post was at 06:50 PM ----------
Here's a post from rg1003
Detailing his steps
http://forum.xda-developers.com/showthread.php?p=51861548
Thanks for this ROM - my install went very smoothly. In case it helps anyone here is what I did - none of it required fastboot or adb:
Stating Point: Skrilax's V8 Bootloader, Thor's 1.7.3 Recovery, Randomblame's 4.3 JellyTime Release 1 (great ROM BTW). All the needed files (new recovery, OmniIROM, gapps, SuperSU) downloaded to my external sd card.
Step 1: Reboot into existing recovery and flash Thor's TWRP rev 2.0 beta 1 recovery. Reboot and make sure I could load my existing JB ROM.
Step 2: Reboot into the new recovery, go to wipe menu and choose Factory Reset.
Step 3: Flash OmniROM from OP, reboot. I did not have the issues others are having and was able get into the new ROM in less than a minute.
Step 4: Enabled developer options so I could reboot from the power menu (not necessary but convenient), reboot into recovery and flash the minimal gapps from the link in the OP. Reboot and make sure I could still boot into OmniROM.
Step 5: Reboot into recovery one more time and flash SuperSU from the OP
I had some trouble getting into the play store at first, it seemed to hang but after two more reboots (after first reboot I was able to load the play store and after the second I was able to access my apps) I was able to install TB so I could reinstall the rest of my stuff.
Maybe this methodical install one thing, reboot and make sure everything is working ok before rebooting to install the next is overkill but in the end it all worked for me.
Looking forward to using this ROM on my A500. Thanks again for all your hard work and keeping this tab alive!
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
I just read a recent post on what bits u needed for it...in dev forum I think
Sent from my HTC_PN071 using Tapatalk
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
http://forum.xda-developers.com/showthread.php?t=2723258
Sent from my HTC_PN071 using Tapatalk
---------- Post added at 07:09 PM ---------- Previous post was at 06:50 PM ----------
Here's a post from rg1003
Detailing his steps
http://forum.xda-developers.com/showthread.php?p=51861548
Thanks for this ROM - my install went very smoothly. In case it helps anyone here is what I did - none of it required fastboot or adb:
Stating Point: Skrilax's V8 Bootloader, Thor's 1.7.3 Recovery, Randomblame's 4.3 JellyTime Release 1 (great ROM BTW). All the needed files (new recovery, OmniIROM, gapps, SuperSU) downloaded to my external sd card.
Step 1: Reboot into existing recovery and flash Thor's TWRP rev 2.0 beta 1 recovery. Reboot and make sure I could load my existing JB ROM.
Step 2: Reboot into the new recovery, go to wipe menu and choose Factory Reset.
Step 3: Flash OmniROM from OP, reboot. I did not have the issues others are having and was able get into the new ROM in less than a minute.
Step 4: Enabled developer options so I could reboot from the power menu (not necessary but convenient), reboot into recovery and flash the minimal gapps from the link in the OP. Reboot and make sure I could still boot into OmniROM.
Step 5: Reboot into recovery one more time and flash SuperSU from the OP
I had some trouble getting into the play store at first, it seemed to hang but after two more reboots (after first reboot I was able to load the play store and after the second I was able to access my apps) I was able to install TB so I could reinstall the rest of my stuff.
Maybe this methodical install one thing, reboot and make sure everything is working ok before rebooting to install the next is overkill but in the end it all worked for me.
Looking forward to using this ROM on my A500. Thanks again for all your hard work and keeping this tab alive!
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
So I found this thread last night and when I get to the nvflash it tells me its not an executable command? I am using V8 and running from the windows batch file in the folder, I am on windows 8 also, although I tried on my w7 machine also nothing!
that guy is also on JB I am on HC
Need adb and fastboot drivers installed on yr pc. These are in the android sdk or u can d/l them in a mini zip from my root guide.
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
Need adb and fastboot drivers installed on yr pc. These are in the android sdk or u can d/l them in a mini zip from my root guide.
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Well I reinstalled W7 and everything went great until, I didnt follow directions on the rom I was trying to flash. I am ICS bootloader unlocked now and I have V8 installed but now I cant get into recovery. I am able to get in to a different menu which says I can boot into recovery but all it does is says booting recovery kernel image. I went in to fastboot mode and used fastboot command fastboot reboot recovery and it didnt work, I do have the drivers installed for fastboot but I think I am missing something small probably. Any help would be appreciated. I wiped system in recovery and flashed Evil Alex rom, then read the directions like an idiot, this is way different than all the phones.
jhr5474 said:
Well I reinstalled W7 and everything went great until, I didnt follow directions on the rom I was trying to flash. I am ICS bootloader unlocked now and I have V8 installed but now I cant get into recovery. I am able to get in to a different menu which says I can boot into recovery but all it does is says booting recovery kernel image. I went in to fastboot mode and used fastboot command fastboot reboot recovery and it didnt work, I do have the drivers installed for fastboot but I think I am missing something small probably. Any help would be appreciated. I wiped system in recovery and flashed Evil Alex rom, then read the directions like an idiot, this is way different than all the phones.
Click to expand...
Click to collapse
GOT IT! duh, all I had to do was reboot into APX mode manually and run the flash tool again and then the most important part as ALWAYS READ THE OP of the rom you are flashing!
Hehe if all else fails reading the directions will do the trick...pleased u got it sorted
Sent from my HTC_PN071 using Tapatalk
Flashed TWRP. Went to reboot, and it asked me to flash Super SU to root.
So I did, now it's stuck in a boot loop.
Also when starting the phone I get a message saying 'your device is corrupt'.
Any ideas?
Can you still get into bootloader?
As always , not bricked , not even close .
Your bootloader is fine , flash the factory image
Sent from my Nexus 6P using Tapatalk
i did this same thing, i cant copy the stock rom over in twrp so i am stuck. guess i got a bunch more reading to do, i am trying to figure out how to flash the rom through adb.
edit: i used the skipsoft toolkit and reverted back to stock everything went smoothly.
Go to twrp format user data by wipe data and user data. Reboot recovery and install a kernel with out force encrypted or install the new twrp and should be OK
Sent from my Nexus 6P using XDA Free mobile app
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
Also might want need to flash a new ROM or fastboot the OEM tgz. There are couple fixed your not screwed!
Sent from my Nexus 6P using XDA Free mobile app
If you can't adb in recovery is a driver issue. Download the koush version and uninstall the Google drivers. It will work.