Related
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)
Hey guys I was trying to boot into the latest CWM image to install superSU in the oficial android 4.3 image, however I got stock in the bootscreen, I tried manually typing the commands as always did and using a toolkit... Maybe is it broken?
Regards
I can't get super su working,
Sent from my Nexus 4 LTE @1.728 GHz on Stock 4.2.2
IRX120 said:
I can't get super su working,
Sent from my Nexus 4 LTE @1.728 GHz on Stock 4.2.2
Click to expand...
Click to collapse
But you were able to boot into recovery?
rootusr said:
But you were able to boot into recovery?
Click to expand...
Click to collapse
Yeah just no root
Sent from my Nexus 4 LTE @1.728 GHz on Stock 4.2.2
rootusr said:
Hey guys I was trying to boot into the latest CWM image to install superSU in the oficial android 4.3 image, however I got stock in the bootscreen, I tried manually typing the commands as always did and using a toolkit... Maybe is it broken?
Regards
Click to expand...
Click to collapse
Working fine here. Installed latest TWRP then super su and root works fine.
cwm recovery boot into a blank screen...not able to see anything.
22sl22 said:
Working fine here. Installed latest TWRP then super su and root works fine.
Click to expand...
Click to collapse
This is my game plan as well....Make sure I have the latest TWRP and Super SU before I attempt to re-root.
EDIT: I forgot, I switched from the Super SU app to the superuser app from clockworkmod a while back.
TWRP updated to 2.6.0.0
Superuser already at 1.0.1.8
re-downloaded superuser.zip (unknown version)
Ready for the 4.3 OTA.
22sl22 said:
Working fine here. Installed latest TWRP then super su and root works fine.
Click to expand...
Click to collapse
Can you upload the SuperSu zip file you used to root?
I have exactly the same problem. Before updating to 4.3 I've booted CWM and did a nand backup.
After updating I can't boot into CWM or TWRP to flash the root zip. I get a blank screen instead of the recovery menu.
I don't want to flash a recovery, just boot like thousands times before to flash the root.zip from chainfire that works.
Same problem : I get a blank screen when booting CWM
I can connect with adb, backlights turns off after some time, and on again if I press a key.
I can boot in the recovery after flashing it !
So booting a flashed recovery from the bootloader works, but booting it with "fastboot boot" don't...
blitzzz3434 said:
Can you upload the SuperSu zip file you used to root?
Click to expand...
Click to collapse
Read here. Make sure you read the bit about Titanium Backup if you use it:
https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
22sl22 said:
Read here. Make sure you read the bit about Titanium Backup if you use it:
https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Click to expand...
Click to collapse
Are you by any chance experiencing that high cpu usage which causes horrible battery drain?
Sent from my Nexus 4 using xda premium
Coming back to the subject of this thread, I was NOT able to boot into TWRP from fastboot using the command:
fastboot boot openrecovery-twrp-2.6.0.0-mako.img
the n4 was starting but I was just getting a black screen.
I had to flash the recovery to my nexus 4 with:
fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img
and after that I was able to boot as usual to the recovery and install chainfire modified .zip to gain root in android 4.3
Any other is experiencing this problem with booting into recovery on N4 ?
On my nexus 7 I was able to boot as usual into the recovery, without flashing it
@bagl0312 How I wrote, I have exactly the same problem. I will going to flash twrp, flash root zip and flash back the stock recovery for now.
Never the less fastboot boot recovery.img does not work atm
I apologize for the noob question but I've never found myself in this particular situation...
I've decided to stick with the 4.3 JWR66V factory image while I wait for a working rooted version to be released or even an updated SuperSU or Superuser zip (that doesn't drain the battery or lose root with certain apps).
I used the factory image found HERE and followed the detailed instructions found HERE. I followed the instructions under section "D" vigorously which meant that I installed the stock recovery image as well. Everything is running as it should. However, I was curious if it was safe to flash TWRP 2.6.0.0 recovery through fastboot with my current setup. I'd like to use that recovery to wipe cache/dalvik and possibly fix permissions. However, I'm not sure if this will break something so I am hesitant to try it.
I have made sure the bootloader is unlocked. But I am curious if it's safe to flash and use TWRP while I am not rooted.
You can install recovery with no problem, root has nothing to do with it. however i think upon a reboot your recovery will be replaced with factory.
Interesting. I wonder why/how the system would flash back to stock recovery if I've pushed the TWRP recovery image over the factory image?
I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app
otariq said:
I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Without root would there be any functionality within TWRP that I shouldn't touch? Or does recovery functionality have no dependency on root?
What is there you wanna do? I just replaced stock with twrp so I can just flash the su zip when its out because I don't always have access to a PC. Also, Franco released his initial 4.3 kernel which I'm thinking about flashing.
When rebooting from twrp it'll ask if you wanna flash the su.apk because you don't have root I chose no because it wouldn't do anything for us right now without the binaries
Sent from my Nexus 4 using xda app-developers app
Good point. As of right now I guess I don't have a huge need for it. I'll just leave everything as is until a proper SuperSU is released. At which point I'll install the latest TWRP and root.
Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.
skinniezinho said:
Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.
Click to expand...
Click to collapse
No idea. I use a Mac and flash back to stock via Fastboot. You should just learn to do that anyway so you have a better sense of exactly what is going on and if something fails you'll know exactly which step is failing in order to correct it. Relying on a toolkit is like never taking the training wheels off your bike.
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.
hey all,
I'm a complete noob when it comes to rooting
I've been searching online on how to root a nexus 4 using a mac.. every single guide is different, some skip the unlocking bootloader part, some skip other parts, and most guides are just outdated.
I'm running on absolute stock, 4.4.2.
What's the best (and most current) guide out there? I'm interested in rooting my phone mainly so I can get LTE access.. do no care too much for non stock ROMS (not yet at least)
I think this is the easiest for noobs: http://forum.xda-developers.com/showthread.php?t=1999065 . It's a tool that will do all the work for you.
Sent from my Nexus 4 using Tapatalk
update:
I set up adb on my mac and unlocked bootloader, that was easy.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
so now I'm confused about the whole Rom part.. which one do I download? There's a ROMs column, a stock recovery, and stock touch recovery. What are those?
You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk
Yuoko5 said:
You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?
If you're device is rooted I think you won't be able to install OTA updates from google anymore. But, you can flash these stock roms easily. I'm sure people make flashable zips of every new version of Android. About the columns: ROMs=you can download custom roms (you don't need that); Recovery and recovery touch is basically the same thing. The difference is one recovery can be controlled with the touchscreen and the over with the volume and power button. It's just what you like best.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
beegbear said:
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?
Click to expand...
Click to collapse
Get it?
Sent from my Nexus 4 using Tapatalk
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
Cwm(clockworkmod recovery) is a side load which helps u to flash different ROMs and zip files. It also helps u to wipe battery stats, partition sd card(not with case of n4)
Factory image is the stock ROM that Google provide that u r having in your nexus 4
Sent from my Nexus 4 using xda app-developers app
beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.
Lt.Win said:
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.
Click to expand...
Click to collapse
So let me make sure I'm following this..(sorry, I'm sure you saw such questions countless times before)
CWM (or TWRP) is a custom recovery instead of the stock 'recovery' option that's found in the bootloader. If I choose to go with either CWM or TWRP, how much of an issue is it to flash back to stock recovery? would it be done through ADB the same way the custom recovery was flashed in the first place?
As I understand.. the first thing I should do after unlocking the bootloader (already done) and flashing a custom recovery (not done yet) is to create a backup through the custom recovery. Does that back up the radios as well? If I decide to flash the all in one LTE zip and it doesn't work or what not.. will using that recovery flash back the old radios?
Now to the actual rooting..
so flashing super su is what actually does the root? How would I go about returning to complete stock if I ever need to? (stock recovery, remove root, lock bootloader)
When flashing a different ROM, how come I need to make a backup of my apps? what if I want to start completely fresh? Would I not be able to go to the playstore after flashing a custom rom and downloading everything I need? or there is not going to be a play store after flashing? (that's why GAPPS are needed?)
so I rooted and flashed the hybrid radio, works like charm!
I answered most of my own questions in the post above just by going through the process.
What happens if I decide to factory reset through settings? will CWM stay? will the root stay? will the lte fix stay?
Yes...yes...yes.....you really should take advantage of the countless guides people have written explaining all of your questions.
Sent from my Nexus 4 using XDA Premium 4 mobile app