Database Users

[Q] Nexus 7 Problem with root/ bricked Tablet

Hello , im new in this forum so sorry if i did something wrong...
about a month ago i rooted my Nexus 7 4.2.1 and everything went good ... until two days ago i couldnt connect to the google playstore and i had an update at the same day ... so what i did was kind of stupid ... i kept the root and upgraded to 4.2.2 hopefully it would fix the google playstore, but what happend is that the root is not activated but i still have the SU .. BUT busybox was gone and google playstore still wasnt conneting...
after a while i tried to unroot my tablet with nexus toolkit with version 4.2.1 (because there was no option for 4.2.2 yet) i did it and now my tablet nexus 7 is stuck in the google logo with a unlocked key underneath it ..... PLEASE HELP I HAVE TRIED EVERY THING YOU ARE MY LAST HOPE PLEASE PLEASE PLEASE :crying: :crying::crying:

Did you try downloading the official 4.2.2 factory images, and flashing them one by one via fastboot? http://forum.xda-developers.com/showthread.php?t=1907796
Hopefully you have a backup of /sdcard. This will bring you back to unrooted stock. You will then have to flash a recovery using fastboot, and then you can flash a Superuser or SuperSU zip to get root back.
I don't use toolkits. So I will be of no help there.

Hello , thank you very much for answering but im new in this rooting system so if you could please explain to me what to do ....
and no , i didnt backup anything....
my tablet now can go to the recovery mod i think (pressing the close button + volume UP + volume DOWN for 10 seconds) without a problem...

RMarkwald said:
Did you try downloading the official 4.2.2 factory images, and flashing them one by one via fastboot? http://forum.xda-developers.com/showthread.php?t=1907796
Hopefully you have a backup of /sdcard. This will bring you back to unrooted stock. You will then have to flash a recovery using fastboot, and then you can flash a Superuser or SuperSU zip to get root back.
I don't use toolkits. So I will be of no help there.
Click to expand...
Click to collapse
hello , i tried doing what you posted there but it says in the driver installation that you need to enable developer options... i cant do it because i cant turn on the tablet.... any help ? please ?

yashke22 said:
hello , i tried doing what you posted there but it says in the driver installation that you need to enable developer options... i cant do it because i cant turn on the tablet.... any help ? please ?
Click to expand...
Click to collapse
You dont need usb debugging when you flash things in fastboot mode. as for drivers, if you can see your device in device manager, right click on it then chose update driver, then navigate to the google_usb driver folder found in the sdk extras or on wugs toolkit raw driver install option.

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

No OS. PLEASE HELP!!

I have an LG G2 vs980. I can get into fastboot and TWRP but for some reason the touch screen is really wonky and when i boot into download mode it takes me to fastboot. Right now im running Ubuntu but i can re install windows if i have to. Any help would be muchly appreciated.

shaggy9585 said:
I have an LG G2 vs980. I can get into fastboot and TWRP but for some reason the touch screen is really wonky and when i boot into download mode it takes me to fastboot. Right now im running Ubuntu but i can re install windows if i have to. Any help would be muchly appreciated.
Click to expand...
Click to collapse
we need a story, for starters what did you do/happened before you got into fastboot?

XxZombiePikachu said:
we need a story, for starters what did you do/happened before you got into fastboot?
Click to expand...
Click to collapse
Well im kinda new to the rooting thing but I believe my phone was only soft rooted. I was trying to install twrp but I got a dead android with a explanation mark or it would go to a black screen after the lg logo.i didn't know I was soft rooted when I was trying this. so after awhile I gave up. my phone still booted normally without trying to go into recovery. recently an update for android came out ( kitkat 4.4.2) so I decided to see if it would work. it restarted the phone to install the update and it got stuck in fastboot mode. i managed to find a way to install twrp using fastboot and adb. i did it but the touch screen was all funked up and i ended up wiping the system i think. just cant win. twrp wont mount the drive eiher. maybe because i have Ubuntu?

shaggy9585 said:
Well im kinda new to the rooting thing but I believe my phone was only soft rooted. I was trying to install twrp but I got a dead android with a explanation mark or it would go to a black screen after the lg logo.i didn't know I was soft rooted when I was trying this. so after awhile I gave up. my phone still booted normally without trying to go into recovery. recently an update for android came out ( kitkat 4.4.2) so I decided to see if it would work. it restarted the phone to install the update and it got stuck in fastboot mode. i managed to find a way to install twrp using fastboot and adb. i did it but the touch screen was all funked up and i ended up wiping the system i think. just cant win. twrp wont mount the drive eiher. maybe because i have Ubuntu?
Click to expand...
Click to collapse
well first the reason your phone died is because of the update you did after you had broken your stock recovery, if you have twrp currently there are two things you need to do:
1)get rid of the update using this
2)adb push/sideload a rom and try to flash or try and get in download mode to restore to stock

XxZombiePikachu said:
well first the reason your phone died is because of the update you did after you had broken your stock recovery, if you have twrp currently there are two things you need to do:
1)get rid of the update using this
2)adb push/sideload a rom and try to flash or try and get in download mode to restore to stock
Click to expand...
Click to collapse
is there a way to flash a rom using adb while in twrp or fastboot?

shaggy9585 said:
is there a way to flash a rom using adb while in twrp or fastboot?
Click to expand...
Click to collapse
no fastboot is only for restoring the phones stock partitions but if you use twrp sideload feature it should flash it once it's done copying it(I know that's how it works with philz)

XxZombiePikachu said:
no fastboot is only for restoring the phones stock partitions but if you use twrp sideload feature it should flash it once it's done copying it(I know that's how it works with philz)
Click to expand...
Click to collapse
now i just need to figure out whats going on with the touch sensor. idk if its the phone or just twrp

Lost TWRP

Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.

Danokan said:
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Click to expand...
Click to collapse
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232

Amro90 said:
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Click to expand...
Click to collapse
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.

Danokan said:
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Click to expand...
Click to collapse
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.

Amro90 said:
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Click to expand...
Click to collapse
YIKES.
Well.. it got the TWRP recovery loaded alright.
But it won't boot into anything else...light is flashing but screen is black.

HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP

Danokan said:
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Click to expand...
Click to collapse
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.

Hartendief said:
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Click to expand...
Click to collapse
How do you propose I flash it?

SOLVED
FIXED
http://forum.xda-developers.com/showthread.php?t=2448960

Cannot boot into recovery

hi guys,
I tried to flashing twrp recovery 2.*** (3.0 was already installed) using flashify on my already rooted op2 (running on SkyDragon-H2OS-v2). And now I'm unable to boot into recovery.
things i tried:
# flashing recovery using fastboot (both twrp and stock). flashing was successful, still no luck.
#tried flashing via flashify again, still no luck
# tried unbricking method, but when I connect my phone holding volume+, windows recognizes something, but nothing visible anywhere in device manager.
Please guys, any way out will be helpful.
PS- I can boot normally to SkyDragon, phone is rooted and oem unlocked

Know it doesn't all apply to you but you could try running the firstaid file
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967

matt_simpson said:
Know it doesn't all apply to you but you could try running the firstaid file
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967
Click to expand...
Click to collapse
Thanks for the reply mate.... The issue is resolved now. Using mm tools I recovered the recovery and then installed oxygen as an ota using stock recovery.
All is well now.