Need help with 2012 N7 that is kind of bricked! - Nexus 7 Q&A, Help & Troubleshooting

OK so I know there is A TON of info on these forums.
I searched around but I did not see anything similar to my situation.
If there is a thread, please just link it and ill delete this thread.
Basically I had rooted my N7 back earlier this year and had a custom rom as the 5.0 OTA made my N7 run like crap.
It was fine until the last few months, it got REALLY slow. I didnt update it, or mod it other then flashing the roms.
So I set out to get a new rom. I figured id try the 6.0 AOSP rom.
DL it, as well as the GAPPS and tried to install it. All I ever got was a continuous error saying, "setup wizard has stopped".
Searched some more and saw that someone fixed it by installing a bare bones GAPPS and then WIPING Dalvik and cache immediately after flashing GAPPS.
I did this and no change. Still an error.
So I noticed that when I was in Windows, my N7 showed as having 5+/- gigs free out of 13gb.
So I figured let me wipe this whole thing clean and start fresh.
BTW- this has all been done with Wugfresh toolkit.
So I went ahead and erased/ formatted and planned to return to stock and then re-root and flash a 4.44 rom as I saw that on the grouper nothing over 4.44 works great and all I want is a stockish N7 that stays fast and works 100%.
Well now all I get is the Google scree with the Unlock icon and a green start icon and when you try to go into bootloader it says booting failed in upper left corner.
Any ideas hahaha.
Thanks!

I never used Wugfresh ......Are you able to get to recovery? If so what recovery do you have?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Check this out I use it on my 2012 N7.......http://forum.xda-developers.com/showthread.php?t=2533035
[ROM][4.4.4 STOCK KTU84P][BSZKitKat v1.6][SuperSU|ZipAlign|DEODEX|ODEX][20/06/14]
Sent from my Nexus 6 using Tapatalk

twics said:
I never used Wugfresh ......Are you able to get to recovery? If so what recovery do you have?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Check this out I use it on my 2012 N7.......http://forum.xda-developers.com/showthread.php?t=2533035
[ROM][4.4.4 STOCK KTU84P][BSZKitKat v1.6][SuperSU|ZipAlign|DEODEX|ODEX][20/06/14]
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I had the latest twrp recovery, I think 2.08 ?
I can't seem to get to the recovery screen.....only the bootload screen.

Well your bootloader is unlocked so you should be able to flash recovery again via ADB...when you are pressing the volume buttons to select recovery or bootloader is there an option for recovery? If so what does it say or do why you can't get to recovery.
Sent from my Nexus 6 using Tapatalk

twics said:
Well your bootloader is unlocked so you should be able to flash recovery again via ADB...when you are pressing the volume buttons to select recovery or bootloader is there an option for recovery? If so what does it say or do why you can't get to recovery.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?

1993cb7 said:
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
Click to expand...
Click to collapse
NO!! Your device is not toast if it powers on then it should be recoverable, my advice forget WugFresh check out this page on how to get TWRP installed> https://twrp.me/devices/asusnexus72012wifi.html for latest twrp recovery, on this page you will find info how to get ADB running properly, once you have Twrp recovery installed try this Rom it is stock Lolliopop and runs great better than previous ones http://forum.xda-developers.com/nexus-7/development/rom-t2931064
---------- Post added at 02:00 PM ---------- Previous post was at 01:54 PM ----------
Please let me know how you get on. also if you get TWRP installed wipe everything apart from internal storage before install Rom.

1993cb7 said:
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
Click to expand...
Click to collapse
Hi there and a happy new year .....well guess what iv got the same issue as well now and I'm also using WugFresh I can reboot bootloader from NRT but that's it can't get to recovery can't write to recovery can't flash recovery all I can do is to TWRP temporary via NRT ,but still can't write to it, I read somewhere that the internal SD is fried which is why I can't write to system which means can't flash Recovery or Rom which mean can't reboot system so unfortunately for us its looking like a new motherboard or new tablet.
Sent from my HTC One using Tapatalk

twics said:
Hi there and a happy new year .....well guess what iv got the same issue as well now and I'm also using WugFresh I can reboot bootloader from NRT but that's it can't get to recovery can't write to recovery can't flash recovery all I can do is to TWRP temporary via NRT ,but still can't write to it, I read somewhere that the internal SD is fried which is why I can't write to system which means can't flash Recovery or Rom which mean can't reboot system so unfortunately for us its looking like a new motherboard or new tablet.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Did you ever get it sorted out?
Im trying to fix mine because someone wants to buy it so Im going to spend all night working on it. If I get anywhere ill let you know.

1993cb7 said:
Did you ever get it sorted out?
Im trying to fix mine because someone wants to buy it so Im going to spend all night working on it. If I get anywhere ill let you know.
Click to expand...
Click to collapse
OK Im back. Roughly an hour and a half. Not bad.
So what I did(if you're stuck on the bootloader screen like me)
Updated to the latest version of Wugfresh.
Made sure it updated all of the files it needed etc.
I then went through the process of uninstalling and reinstalling the drivers for ADB etc. I actually had an issue with it not detecting my device so it recommended installing the generic Google drivers....I did that.
Even after doing that, when I would check ADB connectivity it would say no devices found. I remembered that sometimes it would still communicate with the device even though it said nothing was found. I decided to do a fastboot format under advanced utilities because I knew that i erased it previously and I think that is where I ran into problems.
Sure enough adb found my device and formatted the bootloader no problem. I then continued with the restore to stock/w boot loop function and had patience...it took FOREVER to load the system image and then it took like 10 minutes to reboot but it did and I have a fully functional device right now.
I logged in and turned USB debugging on and re-locked the device. I then did a system wipe from inside the system and will sell it tomorrow.
So have faith, its not over till its over.
and p.s. I changed the USB port that I was plugged into. I have a USB hub that I usually connect too but I figured id connect directly to a USB port on the machine. Not sure if that helped, but people recommend it anyway.

Related

Unable to boot to CWM

So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Okaay said:
So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Click to expand...
Click to collapse
root the tablet
then install ROM manager and flash the official recovery from there
works perfect
The bug is that you cannot boot into any recovery (cwm/twrp/stock) from bootloader unless you are plugged into you computer via a usb cable. The only other way to boot is to use a script but that requires a working system partition.
Sent from my Nexus 7
I have the same problem and I flashed the official CWM from Rom Manager. I made a nandroid before I messed with it and when I went to change the LCD Density, I don't know what happened but now it won't boot. I can't get into CWM either. I figure I'll use ADB when I get home to try and reboot into recovery, if not I'll search the forums for the stock image and reflash. If there is a HW workaround to get booted into it from the device itself that would be awesome. I had to do a battery pull to keep it from rebooting itself and killing the battery.
I've always had Rom Manager Pro and immediately after rooting, used it to flash backups, update to 6.0 cwm, etc. If your rooted you must have that or Goo Manager for TWRP flashing anyway. Might as well start immediately.
There is a thread somewhere here dealing with changing density. The Nexus7 has problems when you simply use a density changing app.. You must change density by modifying prop.build. You can do this using a root explorer app, or by using Rom Toolbox Pro. I use Rom Toolbox and it worked perfect.
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
jmhalder said:
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
Click to expand...
Click to collapse
Will that command allow me to access recovery to restore my backup?
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
yeahthatsme said:
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
Click to expand...
Click to collapse
I believe you need to be on the bootloader screen? I haven't flashed anything from Asus in a while, not since my original Transformer.
chrisjm00 said:
Will that command allow me to access recovery to restore my backup?
Click to expand...
Click to collapse
Code:
fastboot boot recovery.img
where recovery.img is a CWM image, should allow you to get into the recovery to fix whatever you messed up. Note that ADB is only functional if you already have CWM or Android booted... in the bootloader, fastboot is all that's available.
I have the same issue. Stuck at the Google logo with a padlock at the bottom. I didn't flash anything with ROM Manager just the recovery.img through fastboot, then did a fastboot reboot. Now I'm lucky if I can get the thing to stay off when I hold the power button it just pops back up to the padlock with Google logo.
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
CooLoserTech said:
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
Click to expand...
Click to collapse
Has anyone figured a way to access recovery using the buttons only? I've tried TWRP 2.2 and the newest cwm, and on a cold start from power off, it sticks at the Google logo. During a bootloop you are screwed unless you have a laptop within arms reach. Until this is rectified I'm leery of flashing anything. The whole point is being able to restore a nandroid in a crisis. I haven't found that ability yet. If anyone knows a way, please educate me!
Guess we can just wait. Besides there's not much development yet anyways. Would love to use AdFree and root explorer though.
Sent from my Nexus 7
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
Recommend downloading quickboot. It is a paid app but it boots you to recovery no hassles with the buttons
Sent from my Nexus 7 using Tapatalk 2
Ya i have tried several version of CWM and TWRP and manually reinstalled cwm via adb. but all of them don't let me boot from the bootloader, i get the google logo like everyone else. Not sure what else to try, need to not take any risks until there is a fix i guess ^_^ hope someone gets some ideas

[Q] Completely Bricked Nexus 7

Okay I'm a noob when it comes to flashing and all this custom rom stuff. I wanted to flash a tablet ui rom from this website
at wonderhowto.com
They said I needed to be at 4.2.2 and so I checked my tablet's settings and it stated that I was at 4.2. Being the noob that I am I thought 4.2 was the same as 4.2.2 (not knowing it was 4.2.0) so I flashed it anyway using WugFresh's Nexus tool kit and it immediately got bricked at the google x screen. So after some research and a few downloaded files later, I found the stock 4.2 nexus 3G zip. So I did a stock recovery with that and everything was restored. Yay! I still wanted that tablet UI so the next step was to update to 4.2.2. I was able to upgrade to 4.2.2 using the nexus system update check in the About Tablet settings. Now that I had the 4.2.2, I flashed the Tablet UI patch to my device and it worked fine. Device booted up with the tablet UI and everything but the landscape mode was a little buggy. So, I decided to go back to the stock rom in which he provided in his blog under "Restoring Back to Stock UI". I downloaded that to my device and installed using the TWRP. Now this is where the problem started. When I booted up my device it got stuck on the google X screen. So I rebooted the device over and over again and the same problem persisted. I went to Wugfresh's toolkit and decided to stock recover using the original nakasig J0P40C 4.2.0 build and now the device won't turn on, stays stuck on the Google logo screen, and no matter how many times I stock recover it just stays in the Google logo screen.
- I've completely wiped the cache and formated the data, sd card through the TWRP. I'm able to reach the TWRP using WugFresh's tool kit under "temporary custom recovery".
- Not sure but I have a feeling that it's not working because I'm essentially downgrading from 4.2.2 to 4.2.0. If this is the case how can I get a stock 4.2.2
- Please any help is wanted. My device is my life right now.
Can you get into bootloader mode?
If so:
Get your restore image from here:https://developers.google.com/android/nexus/images
In wugfresh' toolkit select 'soft brick / boot loop' at device state, under the flash stock button.
Connect your Nexus to your PC and get it into bootloader mode.
Click the flash stock button.
Select the option to choose your own image and click the original one from Google.
Now flash and hope it's booting again!
If not so:
Sorry, I can't help you :-[
Sent from my Nexus 7 using xda premium
It's kinda common problem. The reason is not your downgreading. I't something else. As you are using NRT(one of my fev) you are too close to the solve. Heres the steps you need to take.
* Reboot into bootloader,
- Advance->reboot recovery in NRT
- or if you don't wanna use NRT turn off your device(hold the power button for about 10sec) now hold the power and volume down butto untill the google logo shows up
- than you should be in the fastboot mode
* Now click Flash Stock + Unroot in NRT(Can't boot up) go through the process(I'd recomment 4.2.2 stock)
* You got your devece into 4.2.2stock
If you wanna get a custom rom with Tablet UI you can skip the uper part.
* Reboot your device in TWRP
* Get an USB flash drive with the custom ROM( Smooth ROM is my personal fev.
* Connect the USB flast to your tablet via a OTG cable.
* Select install from TWRP select USB otg (or something like that)
* Now Select the custom rom from the Files and Swipe to install.
* Go through the installation process.
* After the installation is done wipe cach & devlock.
* Turn off the device from TWRP.(Sometimes direct rebooting form TWRP causes a problem).
* Power it on and you got a custom rom that has an Tablet UI.
* As far as I remember Smooth ROM is previously rooted. Though I rooted it using NRT(4.2.2 stock worked for me).
* As you are using a custom rom you should use a custom recovery.
Hope this is gonna work let me know if doesn't.
_____________________________________________
Don't just say thank you there is a button for thanking.
---------- Post added at 02:33 PM ---------- Previous post was at 02:26 PM ----------
sdelange99 said:
Can you get into bootloader mode?
If so:
Get your restore image from here:https://developers.google.com/android/nexus/images
In wugfresh' toolkit select 'soft brick / boot loop' at device state, under the flash stock button.
Connect your Nexus to your PC and get it into bootloader mode.
Click the flash stock button.
Select the option to choose your own image and click the original one from Google.
Now flash and hope it's booting again!
If not so:
Sorry, I can't help you :-[
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
That is supposed to be wokring. But I never could get the "Other/Brows" working in NRT. Think this is a bug.
---------- Post added at 02:36 PM ---------- Previous post was at 02:33 PM ----------
And @slimsoul I think this is not a situation which can be called as "Completely Bricked Nexus 7"
Can't you click the flash button, choose other / browse in the upper section and choose "I downloaded one mysef..." in the lower section?
Otherwise just try installing if you ever need it.
sdelange99 said:
Can't you click the flash button, choose other / browse in the upper section and choose "I downloaded one mysef..." in the lower section?
Otherwise just try installing if you ever need it.
Click to expand...
Click to collapse
I know how that works. but may be ther is a bug. The flash is never complete. Did you tried to read the lines on the console?? It just jump to press any key to continue. There was suppoed to be many steps before it. And the process was supposed to take a little more time. And the result is no change to your device at all.
Please try to Quote when you post about another post, or it get untressable.
-----------------------------------------------------------------------------
Please press the thanks button if you find this helpful.
ashik992 said:
I know how that works. but may be ther is a bug. The flash is never complete. Did you tried to read the lines on the console?? It just jump to press any key to continue. There was suppoed to be many steps before it. And the process was supposed to take a little more time. And the result is no change to your device at all.
Please try to Quote when you post about another post, or it get untressable.
-----------------------------------------------------------------------------
Please press the thanks button if you find this helpful.
Click to expand...
Click to collapse
I'll make a PrintScreen when flasing again. My tablet works AWESOME now with SmoothROM so I don't even want to flash stock
sdelange99 said:
I'll make a PrintScreen when flasing again. My tablet works AWESOME now with SmoothROM so I don't even want to flash stock
Click to expand...
Click to collapse
Thanks but no need to struggle for me.
I'll try myself any other time. and +1 fro SmoothROM. It's really cool. :highfive:

[Q] Baffled, Confused, Stuck... sniffing KitKats

Hello guys
For some reason I decided to test out the CM and Slim 4.4 roms, but did not see that there were issues flashing with TWRP... so flashing failed with both these ROMS. I did not read the ops on Slim and did not see any warning about TWRP on the CM, so began wiping stuff to try make the flash happen, eventually wiped too much, and now I cannot boot the tablet. Worse is I have also wiped the zip files from the tablet so now I have PhilZ Touch CMW recovery but nothing to flash and this Recovery does not suppot OTG memory, so I have nothing to flash.
SO, tried my full version of Nexus 10 Toolkit to sideload the zip, but Toolkit never gets past "Toolkit Waiting for ADB mode".
I don't know the manual commands to try flash one of these roms, but at this point, I would be happy to just go back to stock, and cant figure how to get to Download mode, there is no home button on an N10.
It seems my safest bet, if possible, would be to get to download and flash a rom there.
Any ideas, much appreciated,
Mark.
fredphoesh said:
Hello guys
For some reason I decided to test out the CM and Slim 4.4 roms, but did not see that there were issues flashing with TWRP... so flashing failed with both these ROMS. I did not read the ops on Slim and did not see any warning about TWRP on the CM, so began wiping stuff to try make the flash happen, eventually wiped too much, and now I cannot boot the tablet. Worse is I have also wiped the zip files from the tablet so now I have PhilZ Touch CMW recovery but nothing to flash and this Recovery does not suppot OTG memory, so I have nothing to flash.
SO, tried my full version of Nexus 10 Toolkit to sideload the zip, but Toolkit never gets past "Toolkit Waiting for ADB mode".
I don't know the manual commands to try flash one of these roms, but at this point, I would be happy to just go back to stock, and cant figure how to get to Download mode, there is no home button on an N10.
It seems my safest bet, if possible, would be to get to download and flash a rom there.
Any ideas, much appreciated,
Mark.
Click to expand...
Click to collapse
From recovery power down your tablet and get into fastboot by holding volume buttons and power buttons at the same time. If this works then you'll be fine because from there you can get back to stock. Download wugfreshs nexus toolkit. Use the option to return to stock and check the one that says stuck in bootloop but can access fastboot (or something like that) then plug your tablet in while its in fastboot mode and go through the steps. It'll have to download stock factory image unless you already have it and browse to it but the toolkit will do everything and get your tablet working again. Don't worry too much its usually not as bad as it seems. The same thing happened to me and I panicked and it turned out to be an easy fix. If you need any more help or more detail on what to do just ask
Sent from my Nexus 10 using xda app-developers app
Thanks Abdel, that worked fine... though I did spend about an hour on Wugfresh last night, it kept on starting to do stuff, then got to recovery mode and it stopped with wufgresh saying waiting for device or something... maybe shutting computer helped too... anyway, thanks for the advice, somehow it worked!
Cheers
Mark.
abdel12345 said:
From recovery power down your tablet and get into fastboot by holding volume buttons and power buttons at the same time. If this works then you'll be fine because from there you can get back to stock. Download wugfreshs nexus toolkit. Use the option to return to stock and check the one that says stuck in bootloop but can access fastboot (or something like that) then plug your tablet in while its in fastboot mode and go through the steps. It'll have to download stock factory image unless you already have it and browse to it but the toolkit will do everything and get your tablet working again. Don't worry too much its usually not as bad as it seems. The same thing happened to me and I panicked and it turned out to be an easy fix. If you need any more help or more detail on what to do just ask
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
fredphoesh said:
Thanks Abdel, that worked fine... though I did spend about an hour on Wugfresh last night, it kept on starting to do stuff, then got to recovery mode and it stopped with wufgresh saying waiting for device or something... maybe shutting computer helped too... anyway, thanks for the advice, somehow it worked!
Cheers
Mark.
Click to expand...
Click to collapse
Your welcome I'm glad you got it working. Make sure to that k wugfresh as well for his awesome tool
Sent from my Nexus 10 using xda app-developers app

Need to copy over a nandroid backup but I can only boot to recovery!

Ok guys, I'm in deep trouble here. Kind of extremely desperate.
Please bare with my wall of text!
So I had just backed up my ROM, copied over the previous nandroid over to my computer and deleted it to make space for the new one. Made the new one, copied over the kernel I wanted to flash. Rebooted into recovery and simply flashed the kernel. That's where the screw-up started.
Wiped my cache and rebooted to a flashing purple and blue screen. Turned my phone off immediately and went to restore the backup I had just made. Not even midway through, I got "error while restoring /system". Nandroid is apparently no good?!
Now, I don't have anything on my SD to flash, not even a clean CM, another backup, nothing. I can only boot to recovery, if I try to reboot, I just get the google logo, then it goes off and back on, and so on. If I connect the phone to my PC, it obviously isn't detecting it.
I need a way to push or copy another nandroid backup or just a ROM over to my SD to flash something! I can't have bricked my phone!
Not too familiar with adb commands, haven't used them in ages!
I appreciate any help you can give me!!
EonHawk said:
Ok guys, I'm in deep trouble here. Kind of extremely desperate.
Please bare with my wall of text!
So I had just backed up my ROM, copied over the previous nandroid over to my computer and deleted it to make space for the new one. Made the new one, copied over the kernel I wanted to flash. Rebooted into recovery and simply flashed the kernel. That's where the screw-up started.
Wiped my cache and rebooted to a flashing purple and blue screen. Turned my phone off immediately and went to restore the backup I had just made. Not even midway through, I got "error while restoring /system". Nandroid is apparently no good?!
Now, I don't have anything on my SD to flash, not even a clean CM, another backup, nothing. I can only boot to recovery, if I try to reboot, I just get the google logo, then it goes off and back on, and so on. If I connect the phone to my PC, it obviously isn't detecting it.
I need a way to push or copy another nandroid backup or just a ROM over to my SD to flash something! I can't have bricked my phone!
Not too familiar with adb commands, haven't used them in ages!
I appreciate any help you can give me!!
Click to expand...
Click to collapse
Have you thought of using a toolkit like WugFresh NRT?
Sent from my Nexus 7 (2013)
---------- Post added at 06:05 AM ---------- Previous post was at 06:04 AM ----------
http://forum.xda-developers.com/showthread.php?t=1766475
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Have you thought of using a toolkit like WugFresh NRT?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
If you're talking about this one, reading the thread right now. About to download the windows version and try to flash stock and unroot, then root again.
Do you recommend anything else? I didn't want to lose root.
EonHawk said:
If you're talking about this one, reading the thread right now. About to download the windows version and try to flash stock and unroot, then root again.
Do you recommend anything else? I didn't want to lose root.
Click to expand...
Click to collapse
As far as losing root, you shouldn't lose it, and there's no reason to believe that you might have already lost it, but if you are planning on flashing stock and unrooting then it wouldn't matter anyway.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
As far as losing root, you shouldn't lose it, and there's no reason to believe that you might have already lost it, but if you are planning on flashing stock and unrooting then it wouldn't matter anyway.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I'm stuck!!!
I tried flashing stock and unrooting, but I had issues with what it said could be either my drives not being installed, or my USB Debugging not being enabled. I don't think I ever enabled USB debugging after this last time I flashed CM. I tried going through full driver installation, but I still hit the same wall with USB debugging not being enabled!!
What should/can I do?
Boot into recovery and connect your USB cable on it. Download an ADB standalone and place the files you want to transfer there, open it and type:
adb push (local of the rom/kernel/wharever) (path to sd/internal storage). it would be something like that
adb push rom.zip /sdcard/0/
this will transfer the file to the root of the internal storage.
EonHawk said:
I'm stuck!!!
I tried flashing stock and unrooting, but I had issues with what it said could be either my drives not being installed, or my USB Debugging not being enabled. I don't think I ever enabled USB debugging after this last time I flashed CM. I tried going through full driver installation, but I still hit the same wall with USB debugging not being enabled!!
What should/can I do?
Click to expand...
Click to collapse
Did you go through the steps in the Full Driver Configuration Guide?
Sent from my Nexus 7 (2013)
sky0165 said:
Boot into recovery and connect your USB cable on it. Download an ADB standalone and place the files you want to transfer there, open it and type:
adb push (local of the rom/kernel/wharever) (path to sd/internal storage). it would be something like that
adb push rom.zip /sdcard/0/
this will transfer the file to the root of the internal storage.
Click to expand...
Click to collapse
Tried sideloading, sideloaded CM over. Seemed to work, but when I rebooted, got through to the CM logo and got stuck in a bootloop.
Rebooted into recovery and wiped device again.
Berrydroidcafe said:
Did you go through the steps in the Full Driver Configuration Guide?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I tried, but I got stuck because I couldn't do Step 1 without having USB Debugging enabled!
EonHawk said:
Tried sideloading, sideloaded CM over. Seemed to work, but when I rebooted, got through to the CM logo and got stuck in a bootloop.
Rebooted into recovery and wiped device again.
Click to expand...
Click to collapse
Just a thought, have you considered using TWRP? Are you sure it was actually a bootloop and not a boot that is just taking a little longer than usual to finish?
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Just a thought, have you considered using TWRP? Are you sure it was actually a bootloop and not a boot that is just taking a little longer than usual to finish?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I waited for over 5 minutes, turned it off, and tried booting it up. After another 3 minutes of nothing, I gave up.
Tried sideloading an old backup but wasn't able to sideload anymore..
Currently trying to do the driver things in the toolkit..
I may have screwed this up even more.
While doing Step 1, I again couldn't do the whole USB Debugging enable/disable, so I just went and did everything else that I could. Step 2 installed, Step 3 couldn't recognize my phone, just went back to Google bootloop.
I don't think I can even try sideloading stuff anymore.
I may have screwed this up even more.
While doing Step 1, I again couldn't do the whole USB Debugging enable/disable, so I just went and did everything else that I could. Step 2 installed, Step 3 couldn't recognize my phone, just went back to Google bootloop.
I don't think I can even try sideloading stuff anymore.
EDIT:
Ok, sideloading CM again. Currently at 70%. I'll keep you guys posted.
Sorry to post 4 times in a row, but still stuck in the CM bootloop.
Is there anything better I should try sideloading? Maybe a factory image?
Something that would completely restore everything?
Sorry to post 5 (FIVE) times in a row!
FIXED IT! **** YES! I was running out of time too, have to wake up in four hours for work, hahahah.
I really don't know what happened this time. Tried running the Flash Stock + Unroot again, and it went through!
Going to enjoy stock for a while, this scared me way more than my previous adventures with rooting have, and I'm not entirely (but mostly) new to this!
Thank you so much for your help man, couldn't have done it without some support. Really feel indebt to the guy that made the toolkit, though. Thanks all around!
EonHawk said:
Sorry to post 5 (FIVE) times in a row!
FIXED IT! **** YES! I was running out of time too, have to wake up in four hours for work, hahahah.
I really don't know what happened this time. Tried running the Flash Stock + Unroot again, and it went through!
Going to enjoy stock for a while, this scared me way more than my previous adventures with rooting have, and I'm not entirely (but mostly) new to this!
Thank you so much for your help man, couldn't have done it without some support. Really feel indebt to the guy that made the toolkit, though. Thanks all around!
Click to expand...
Click to collapse
Great! :thumbup:
Sent from my Nexus 7 (2013)

[q] possible brick? Error loop

Hi guys!
Yesterday, i used towelroot to root my phone, and installed Safestrap with TWRP as my recovery.
I booted my phone after everything was done, and it worked fine. This is where i screw up... I installed Softkeyz (I thought it might work for the Note 3, but...)
After i installed Softkeyz, and rebooted the phone, my status bar was gone, the background was blue and my task manager didnt work. I went back into the softkeyz app and clicked the "backup" button, wich is said to revert everything back to normal. It didnt.
When i booted my phone after the backup, I still had the same problem.
I then did a Titanium Backup, and went into recovery to factory-reset. it seemed to work, but when my phone boots, I get to the languane selection screen, and then this pops up: "KeyguardTestActivity has stopped". If I click 'OK', the same message pops up and im unable to click "next" or select a language.
I went back into recovey, wiped dalvik, wiped cache, I event formated /data in case there was any virus or anything I had downloaded, did a factory reset, and it stil doesnt work....
I had a ROM on my phone, but it used AROMA so that doesnt work with Safetrap... Now my memory is clean, my phone wont boot, and I cant move any files to the SD-card through regular MTP. I guess I have to use ADB (safetrap can sideload ADB) but I have no idea how to use that, and I have no idea what ROM to use, to get my phone up and running.
I use my phone for work and for studies, and the only reason I wanted to root was for AD-blocker and better batterylife...Now I've messed up..
I've tried searching google and the forums, but cant seem to find any fix. Can anyone out there help me? Please?
EDIT: If i boot the phone WITHOUT the simcard, the error message is gone, but if the screen locks, then in wont unlock. Taskmanager still doesnt work. I managed to get to phone running though, but without taskamanager and a working lock-button.... any help?
EDIT2: after rebooting without the simcard, the same error shows...
ipwngeek said:
Hi guys!
Yesterday, i used towelroot to root my phone, and installed Safestrap with TWRP as my recovery.
I booted my phone after everything was done, and it worked fine. This is where i screw up... I installed Softkeyz (I thought it might work for the Note 3, but...)
After i installed Softkeyz, and rebooted the phone, my status bar was gone, the background was blue and my task manager didnt work. I went back into the softkeyz app and clicked the "backup" button, wich is said to revert everything back to normal. It didnt.
When i booted my phone after the backup, I still had the same problem.
I then did a Titanium Backup, and went into recovery to factory-reset. it seemed to work, but when my phone boots, I get to the languane selection screen, and then this pops up: "KeyguardTestActivity has stopped". If I click 'OK', the same message pops up and im unable to click "next" or select a language.
I went back into recovey, wiped dalvik, wiped cache, I event formated /data in case there was any virus or anything I had downloaded, did a factory reset, and it stil doesnt work....
I had a ROM on my phone, but it used AROMA so that doesnt work with Safetrap... Now my memory is clean, my phone wont boot, and I cant move any files to the SD-card through regular MTP. I guess I have to use ADB (safetrap can sideload ADB) but I have no idea how to use that, and I have no idea what ROM to use, to get my phone up and running.
I use my phone for work and for studies, and the only reason I wanted to root was for AD-blocker and better batterylife...Now I've messed up..
I've tried searching google and the forums, but cant seem to find any fix. Can anyone out there help me? Please?
EDIT: If i boot the phone WITHOUT the simcard, the error message is gone, but if the screen locks, then in wont unlock. Taskmanager still doesnt work. I managed to get to phone running though, but without taskamanager and a working lock-button.... any help?
EDIT2: after rebooting without the simcard, the same error shows...
Click to expand...
Click to collapse
Hello again ok so I don't know a great deal about the note 3 or safestrap. But you have a few options here.
if I'm not mistaken the note 3 takes an external SDcard? can you not copy a compatible Rom using a card reader and install from recovery?
I also believe Fastboot works with note3 but not sure how. you could use this to flash a recovery that will work with the Rom on the phone.
or as drastic measure you could adb pull your data and flash it with Odin. flashing with Odin will wipe everything and return you note3 to out of the box condition.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Danny201281 said:
Hello again ok so I don't know a great deal about the note 3 or safestrap. But you have a few options here.
if I'm not mistaken the note 3 takes an external SDcard? can you not copy a compatible Rom using a card reader and install from recovery?
I also believe Fastboot works with note3 but not sure how. you could use this to flash a recovery that will work with the Rom on the phone.
or as drastic measure you could adb pull your data and flash it with Odin. flashing with Odin will wipe everything and return you note3 to out of the box condition.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
Hey man!
I'm so embarassed I didn't think of the SD card... Now my only problem is that I cant seem to find a ROM that will work... I tried the heisenberg one, but it says "failed" when trying to flash it...
EDIT2: It seems as its my lockscreen that is broken. would that be assosiated with the Kernal? I got a ROM, and it worked, but the same error still occurs..I'm thinking that the Softkeyz-app messed with my kernel, and now killed the phoes lockscreen/kernal. Need a new kernel I guess... but thats messing with something I've never done... any stock kernel?
Danny201281 said:
Hello again ok so I don't know a great deal about the note 3 or safestrap. But you have a few options here.
if I'm not mistaken the note 3 takes an external SDcard? can you not copy a compatible Rom using a card reader and install from recovery?
I also believe Fastboot works with note3 but not sure how. you could use this to flash a recovery that will work with the Rom on the phone.
or as drastic measure you could adb pull your data and flash it with Odin. flashing with Odin will wipe everything and return you note3 to out of the box condition.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
Greeeat... I tried flashing the Pacman rom, everything seemed ok, but now i can only boot into the safestrap recovery, and when trying to boot into the system, both with pacman and after trying to wipe everything, it just goes into a black screen...
ipwngeek said:
Greeeat... I tried flashing the Pacman rom, everything seemed ok, but now i can only boot into the safestrap recovery, and when trying to boot into the system, both with pacman and after trying to wipe everything, it just goes into a black screen...
Click to expand...
Click to collapse
sorry dude don't know what to suggest, I don't know safestrap, is it necessary to use or can you use a normal recovery? Safestrap seems very different compared with a normal recovery as it bypasses locked bootloaders and allows for multibooting roms. Are you sure you set it up correctly? Did you make a recovery backup before you started flashing anything?
personally best answer I can give you right now is flash an ruu with Odin to get your phone working, then try rooting again after you've researched it a bit.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
---------- Post added at 01:22 PM ---------- Previous post was at 01:06 PM ----------
The link below has a list of stock firmware. Find the correct one for your phone model and download it. At the bottom of the page there is also a link to download Odin and the phone drivers if you need them. As long as you can boot to download mode you can unbrick from pritty much anything with this.
http://www.androidrootz.com/p/galaxy-note-3-stock-firmwares.html?m=1
You can also use Odin to root and install CWM recovery. There's a guide in the link below for this
http://wccftech.com/how-to-root-and-install-cwm-on-galaxy-note-3-sm-900/
Good luck man
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Danny201281 said:
sorry dude don't know what to suggest, I don't know safestrap, is it necessary to use or can you use a normal recovery? Safestrap seems very different compared with a normal recovery as it bypasses locked bootloaders and allows for multibooting roms. Are you sure you set it up correctly? Did you make a recovery backup before you started flashing anything?
personally best answer I can give you right now is flash an ruu with Odin to get your phone working, then try rooting again after you've researched it a bit.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
---------- Post added at 01:22 PM ---------- Previous post was at 01:06 PM ----------
The link below has a list of stock firmware. Find the correct one for your phone model and download it. At the bottom of the page there is also a link to download Odin and the phone drivers if you need them. As long as you can boot to download mode you can unbrick from pritty much anything with this.
http://www.androidrootz.com/p/galaxy-note-3-stock-firmwares.html?m=1
You can also use Odin to root and install CWM recovery. There's a guide in the link below for this
http://wccftech.com/how-to-root-and-install-cwm-on-galaxy-note-3-sm-900/
Good luck man
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
I'm working on a Odin now... lets hope it works... ghaa...
ipwngeek said:
I'm working on a Odin now... lets hope it works... ghaa...
Click to expand...
Click to collapse
As long as you have correct firmware should be fine, wrong firmware won't flash though so don't panick about that
also make sure you run Odin as administrator and use default options don't tick any boxes manually
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
ipwngeek said:
I'm working on a Odin now... lets hope it works... ghaa...
Click to expand...
Click to collapse
and the verdict?
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Danny201281 said:
and the verdict?
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
I'm the worst guy ever,... totally forgot to answer (to be honest, I thought I replied, but my phone didnt actually send the message!)
It worked well! I now just got a LG G3 though, so yaay!

Categories

Resources