Database Users

[Q] Iam not able to install a custom recovery

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.

Stock Recovery

I flashed TWRP to make backups and am finding I want to revert to stock recovery for whenever the next OTA is pushed. I'm on stock 4.2.2. Is there a repository to flash the stock recovery specific to the version of android I'm on or other way to backup/re-flash stock android prior to installing custom recovery?

ravenofdoom said:
I flashed TWRP to make backups and am finding I want to revert to stock recovery for whenever the next OTA is pushed. I'm on stock 4.2.2. Is there a repository to flash the stock recovery specific to the version of android I'm on or other way to backup/re-flash stock android prior to installing custom recovery?
Click to expand...
Click to collapse
The stock Android recovery cannot make entire system (NANDROID) backups like TWRP or CWMR can. If your looking to re-install stock Android 4.2.2 for the Nexus 10 you can download and flash the Nexus 10 factory image from here (I would recommend taking a look at this great guide if your are unfamiliar with how to flash factory images). If you just want to reflash the Nexus 10 stock recovery you can download it from here, boot into fastboot mode and then flash it with the following command:
Code:
fastboot flash recovery path/to/recovery-stock-manta.img
After it completes you can reboot into recovery mode and you should now have the stock Nexus 10 recovery image installed. For flashing the stock recovery you should try and match it to the Android version so if your on Android 4.2.2 try and flash the recovery.img that was pulled from the Android 4.2.2 factory image. However usually you can get away with flashing 4.2 or 4.2.1 version of the stock recovery.img as it is unlikely that anything major changed with the stock recovery image in those small incremental Android updates.

Is there a repo or other way to make a backup of stock recovery before flashing custom (TWRP/CWMR). If I'm on the go and want to interchange between custom recovery and previous stock recovery without the aid of a computer nearby, how would I do that? Is there an app that can save/snapshot my current stock recovery before flashing custom recovery (and then can later let me re-flash that saved recovery)?

Flashing stock recovery wont make me lose any data will it? because 4.3 was released for s4 google edition so im sure nexus 10 is close and i want to be ready.

abdel12345 said:
Flashing stock recovery wont make me lose any data will it? because 4.3 was released for s4 google edition so im sure nexus 10 is close and i want to be ready.
Click to expand...
Click to collapse
Correct flashing stock recovery won't make you loose any data. But as always when your flashing anything and if you have even the slightest hesitation backup any data you wouldn't want to loose.
Sent from my SCH-I535 using xda premium

Alright thanks man. I already used my 8 for today but ill thank you tomorrow and ill back up my apps with titanium backup

OK what is the command to use to flash because the one from the previous page didn't work it said something about not finding it or something are there any drivers that need to be installed or something I'm missing? I connected it to my CPU and turned it on while holding power and volume and it went menu where you see tablet info? Any help please
Sent from my Xperia Play (r800x)

ravenofdoom said:
Is there a repo or other way to make a backup of stock recovery before flashing custom (TWRP/CWMR). If I'm on the go and want to interchange between custom recovery and previous stock recovery without the aid of a computer nearby, how would I do that? Is there an app that can save/snapshot my current stock recovery before flashing custom recovery (and then can later let me re-flash that saved recovery)?
Click to expand...
Click to collapse
Don't know if you still need this info, but you can use flash_image to flash recoveries without having to connect to a PC. So if you save the recovery image files, you can switch easily. Have a look here:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I haven't done this on my N10, but I've used the method several times on my HTC Vivid phone.
Sent from my Nexus 10 using Tapatalk HD

bruce7373 said:
Don't know if you still need this info, but you can use flash_image to flash recoveries without having to connect to a PC. So if you save the recovery image files, you can switch easily. Have a look here:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I haven't done this on my N10, but I've used the method several times on my HTC Vivid phone.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That actually helped me out with my problem thanks because I couldn't get it to flash from cpu
Sent from my Xperia Play (r800x)

abdel12345 said:
That actually helped me out with my problem thanks because I couldn't get it to flash from cpu
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Cool. :thumbup:
Sent from my Nexus 10 using Tapatalk HD

@bruce7373 it didnt work it just tells me flash_image not found when i put in the command and i checked and its there on the sd card

abdel12345 said:
@bruce7373 it didnt work it just tells me flash_image not found when i put in the command and i checked and its there on the sd card
Click to expand...
Click to collapse
The IMG file is not found or flash_image itself isn't there? If you don't have flash_image, you can download it (I think there's a link on that page I referenced, or just Google it). If the former, you need to first navigate to the folder flash_image is in (/system/bin with the ROM I have on my N10), then run the command, making sure the IMG file is in the root of /sdcard.
Sent from my Nexus 10 using Tapatalk HD

bruce7373 said:
The IMG file is not found or flash_image itself isn't there? If you don't have flash_image, you can download it (I think there's a link on that page I referenced, or just Google it). If the former, you need to first navigate to the folder flash_image is in (/system/bin with the ROM I have on my N10), then run the command, making sure the IMG file is in the root of /sdcard.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
OK I'll try yhat
Sent from my Xperia Play (r800x)

Recovery won't flash

I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4

Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4

T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps

Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.

Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.

OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.

Back to Factory with no computer access.

I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:

you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.

Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time

c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.

mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?

c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.

efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??

c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2

efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset

c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.

Problem Recovery

Suddenly my recovery has stopped working whenever i want to go to recovery is shows me that image with a dead android robot.
Is there any way to flash TWRP again without ADB because i can't get it working,
I tryed twrp manager but it needs root and i lost it.

RootNightmareX said:
Suddenly my recovery has stopped working whenever i want to go to recovery is shows me that image with a dead android robot.
Is there any way to flash TWRP again without ADB because i can't get it working,
I tryed twrp manager but it needs root and i lost it.
Click to expand...
Click to collapse
Try using a toolkit.. for example wugsfresh nexus root toolkit! There's an option to flash the last twrp version..

RootNightmareX said:
Suddenly my recovery has stopped working whenever i want to go to recovery is shows me that image with a dead android robot.
Is there any way to flash TWRP again without ADB because i can't get it working,
I tryed twrp manager but it needs root and i lost it.
Click to expand...
Click to collapse
Without root you would need ADB to flash it...
Your recovery will get over-ridden on each boot unless you rename/delete /system/recovery-from-boot.p to recovery-from-boot.bak or something.
You will need to use fastboot to flash recovery again, then boot TWRP and go into the file manager and rename the file I mentioned above. Sorry, no way to flash recovery without working adb or root.

acejavelin said:
Without root you would need ADB to flash it...
Your recovery will get over-ridden on each boot unless you rename/delete /system/recovery-from-boot.p to recovery-from-boot.bak or something.
You will need to use fastboot to flash recovery again, then boot TWRP and go into the file manager and rename the file I mentioned above. Sorry, no way to flash recovery without working adb or root.
Click to expand...
Click to collapse
I solved with an easy root based on adb program
I rooted the phone and reflashed with twrp from play store. Is there anything I must delete now ?
But whatcould have caused this problem. I was using art clean flashed this morning..... It Never happened for me on any device this problem its first time

RootNightmareX said:
I solved with an easy root based on adb program
I rooted the phone and reflashed with twrp from play store. Is there anything I must delete now ?
But whatcould have caused this problem. I was using art clean flashed this morning..... It Never happened for me on any device this problem its first time
Click to expand...
Click to collapse
You must rename/delete the file I mentioned above if it is a stock ROM, otherwise it reflash the stock recovery on the next boot.
Sent from my Nexus 4 using Tapatalk

acejavelin said:
You must rename/delete the file I mentioned above if it is a stock ROM, otherwise it reflash the stock recovery on the next boot.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I rebooted and still I have twrp. Should I still search the file n delete it?

RootNightmareX said:
I rebooted and still I have twrp. Should I still search the file n delete it?
Click to expand...
Click to collapse
It flashes it on boot, so the next time it might be gone. Most AIO tools take care of it for you.
Your call I guess, is the file there?
Sent from my Nexus 4 using Tapatalk

acejavelin said:
It flashes it on boot, so the next time it might be gone. Most AIO tools take care of it for you.
Your call I guess, is the file there?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I have that recovery bak file. What should i do with it ?

RootNightmareX said:
I have that recovery bak file. What should i do with it ?
Click to expand...
Click to collapse
Personally, I just added a .bak extension to the file, but you could delete it. The nice part about keeping it is if you are basically stock and want to get an OTA, you can just take off the .bak extension, reboot, have stock recovery back, then take the OTA... but I haven't been stock for some time, and returning to stock is fairly simple anyway.

acejavelin said:
Personally, I just added a .bak extension to the file, but you could delete it. The nice part about keeping it is if you are basically stock and want to get an OTA, you can just take off the .bak extension, reboot, have stock recovery back, then take the OTA... but I haven't been stock for some time, and returning to stock is fairly simple anyway.
Click to expand...
Click to collapse
That image can actually lock bootloader back too ?

No, just reflash recovery... It can't relock boot loader, that doesn't have to be locked to take an OTA.
Sent from my Nexus 4 using Tapatalk

RootNightmareX said:
I solved with an easy root based on adb program
I rooted the phone and reflashed with twrp from play store. Is there anything I must delete now ?
But whatcould have caused this problem. I was using art clean flashed this morning..... It Never happened for me on any device this problem its first time
Click to expand...
Click to collapse
what program did you use to root?
Sent from my Nexus 4 using xda app-developers app