[Q] Custom Recovery or Stock Recovery? - Nexus 4 Q&A, Help & Troubleshooting

I just used an automated program to root my phone. I was sick of running into websites on a daily basis that used flash, and hated every other browser out there so I rooted my Nexus 4 to get the stock browser from the Gnex. I am new at this though, and didn't realize rooting my phone could potentially interfere with OTA updates. How can I check to see if the automatic rooting tool I used kept the stock recovery, or changed it to a custom one?

This is exactly why I hate these toolkits...
Boot into recovery, check what it says. If it only shows you an android with a triangle, it's probably stock. If it's anything else (eg TWRP or Clockwork Recovery) then it's a custom.

You can be on Stock Rom with No Mods Unlocked Rooted with a Custom Recovery and you will get the ota update and it will install fine.
The ota update link will be posted here before you get on your device so it's good to have a custom recovery so you can just flash it. It will also protect you from losing root and your custom recovery
To check if you have a custom recovery with the phone off press and hold power and volume down then when in bootloader press volume down till you see recovery press power button if you get a android laying down that's stock recovery
Sent from my Nexus 4

ryfly65 said:
I just used an automated program to root my phone. I was sick of running into websites on a daily basis that used flash, and hated every other browser out there so I rooted my Nexus 4 to get the stock browser from the Gnex. I am new at this though, and didn't realize rooting my phone could potentially interfere with OTA updates. How can I check to see if the automatic rooting tool I used kept the stock recovery, or changed it to a custom one?
Click to expand...
Click to collapse
Rooting doesn't interfere with OTA updates. You are still able to update even with a custom recovery, and it actually makes things easier because you don't have to flash a custom recovery and then root after each update if you have a custom recovery. Custom recoveries offer many more options than regular as well.
For your original question, just power down your phone and turn it back on by holding both volume up and down while holding the power button. This will bring you to the bootloader. From there, navigate to recovery using the arrow keys and push power. If it's a custom recovery you'll know, and if it's stock, you'll just see an android.
It's recommended not to use automated programs to root because you don't learn anything, by the way, although it makes things much easier.
Sent from my Nexus 4 using xda app-developers app

^^^^^ that's what I said
Sent from my Nexus 4

spaceman860 said:
^^^^^ that's what I said
Sent from my Nexus 4
Click to expand...
Click to collapse
Haha, I thought I was the first reply
You need to hold volume up and down along with the power button to boot into the bootloader with this phone though
Sent from my Nexus 4 using xda app-developers app

hoponpop said:
Haha, I thought I was the first reply
You need to hold volume up and down along with the power button to boot into the bootloader with this phone though
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No you don't that's for galaxy nexus for the n4 its just the down button
Sent from my Nexus 4

spaceman860 said:
No you don't that's for galaxy nexus for the n4 its just the down button
Sent from my Nexus 4
Click to expand...
Click to collapse
You're right. My bad, lol
Sent from my Nexus 4 using xda app-developers app

I went into Recovery Mode and it is showing a dead Android with a red triangle. I'm not quite sure what that means.

ryfly65 said:
I went into Recovery Mode and it is showing a dead Android with a red triangle. I'm not quite sure what that means.
Click to expand...
Click to collapse
That's the stock recovery. You have to press volume up and power to see the menu.

El Daddy said:
That's the stock recovery. You have to press volume up and power to see the menu.
Click to expand...
Click to collapse
Do you mean when it shows the dead Android with the triangle? Or before that?

ryfly65 said:
Do you mean when it shows the dead Android with the triangle? Or before that?
Click to expand...
Click to collapse
When it is showing. You can't do much with stock recovery though. Wipe data, clear cache, adb sideload. That's about it.

El Daddy said:
When it is showing. You can't do much with stock recovery though. Wipe data, clear cache, adb sideload. That's about it.
Click to expand...
Click to collapse
Ah, okay gotcha. The reason I asked if I have stock is because I read an article that not having the stock recovery, or altering files in the /system folder may interfere with OTA updates if the checksum fails. I did change the browser in the /system folder though. I renamed two files to get the stock browser in there and working. I just hope that won't affect the OTAs.

ryfly65 said:
Ah, okay gotcha. The reason I asked if I have stock is because I read an article that not having the stock recovery, or altering files in the /system folder may interfere with OTA updates if the checksum fails. I did change the browser in the /system folder though. I renamed two files to get the stock browser in there and working. I just hope that won't affect the OTAs.
Click to expand...
Click to collapse
That will definitely affect OTA's. Anything modified in /system will abort the OTA. You can read more info in my OTA help-desk thread in my signature.

El Daddy said:
That will definitely affect OTA's. Anything modified in /system will abort the OTA. You can read more info in my OTA help-desk thread in my signature.
Click to expand...
Click to collapse
I am completely stock with stock recovery; unlocked, and rooted. The only two things I did was put browser.apk, and ChromeBookmarksSyncAdapter.apk into the /systems folder, and then I renamed BrowserProviderProxy.apk, and BrowserProviderProxy.odex. I just just put a "1" in front of both names. It was part of the instructions to install the stock browser from the Galaxy Nexus phone onto my Nexus 4.
In order to receive the update, would I just have to name those two apps back to their original name? Or would I also have to remove the apps I put in there as well?

ryfly65 said:
So I am completely stock with stock recovery, unlocked, and rooted. The only two things I did was put browser.apk, and ChromeBookmarksSyncAdapter.apk into the /systems folder, and then I renamed BrowserProviderProxy.apk, and BrowserProviderProxy.odex. I just just put a "1" in front of both names. It was part of the instructions to install the stock browser from the Galaxy Nexus phone onto my Nexus 4.
In order to receive the update, would I just have to name those two apps back to their original name? Or would I also have to remove the apps I put in there as well?
Click to expand...
Click to collapse
You should be OK just changing them back. Additions to /system are fine too. If it does end up falling you can just flash the system image with fastboot
Sent from my Nexus 10 using Tapatalk 4 Beta

Related

[Q] Which rooting method?

I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Nate2 said:
I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Click to expand...
Click to collapse
fastboot oem unlock, fastboot flash cmm recovery, flash the su binaries, reboot and profit.
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
frozenspark said:
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
AndDiSa said:
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
frozenspark said:
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
then you should br helping out all the people that mess up their devices afyer using toolkits and dont know how to fix it. i havent seen you help out, yet you are still recommending toolkits. why is that?
I used the steps outlined at http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/ to guide me.
I must say it might not be trivial for the non-software-developer types.
I was a Java developer for many years, so I didn't have much problems setting up Java,
Android-sdk, etc.
My N7 was recognized by adb when booted normally, but after I flashed cwm, I could not do 'adb shell' to mount the /system partition and rename the recovery-from-boot.p file to prevent the recovery from getting reset to stock each time.
I ended up installing the ROM Manager app to enable me to boot into cwm recovery.
I have done the obligatory cwm backup. I believe this is the nandroid backup?
Edit:
I used my Linux box to re-flash the bootloader and cwm recovery images to the Nexus 7, and I could 'adb shell' and rename the recovery-from-boot.p file. So I'm all set now.
I just needed to run 'adb start-server' and 'fastboot' using sudo, so it might have been a permissions issue on my Windows box.
Sent from my unrooted DroidX using Tapatalk
I used Wug's Root Toolkit. Both of the toolkits seem good, but that was just the first one I saw. The Wug's Toolkit is an application and the other one is in a CMD.
Sent from my SGH-T989 using xda premium
Linexus said:
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
Click to expand...
Click to collapse
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Use the fastboot commands
Good to see you alright!
This is like asking "Should I get an automatic or manual car?"
veeman said:
This is like asking "Should I get an automatic or manual car?"
Click to expand...
Click to collapse
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Look at these lazy people..
Beamed from my Grouper.
Nate2 said:
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes there was a bootloader bug on the nexus 7 and most people could not boot into CWM recovery without plugging it into their computer.
I however used TWRP back then [have since switched back to CWM touch, now that the bug is fixed] and had no issues. Now I have no issues with CWM touch, I can boot it directly from fastboot menu, or "reboot -> recovery" when booted.
Nate2 said:
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Click to expand...
Click to collapse
exactly what I would have done! sounds like you're getting the hang of it. and yes, I definitely recommend manual rooting/fastbooting to a toolkit.
Wilks3y said:
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Click to expand...
Click to collapse
Yes that's my favorite too. It does it all and more. It slices, it dices, it'll even cut a can!
Nate2 said:
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Click to expand...
Click to collapse
Yeah, that's what I'm saying. They both have their ups and downs. If you're willing to learn a little about how Android works and learn some adb and fast boot commands then you should definitely do it manually.
If you just want to be a "1337 Haxorz" and aren't willing to learn then just use a toolkit.
OK, just one sub-question on rooting. I see no real reason to root except maybe to get more tablet interface than nexus has. Kinda like when the wifi indicator is at the bottom, since there are those !$#$$ back/home buttons already and a lot of wasted space Anyways, the question.
I bougth N7 16Gb and upgraded via forced OTA to 4.1.2. Do all these root methods work with 4.1.2?
Thanx,
D.

[Q] Completely Wiped, Fix?

I'm starting to really feel displeased about not having an external memory slot. My phone is entirely wiped. While in recovery, EVERYTHING was wiped. The custom recovery is still there, but when booting up the phone, it's stuck on the Google logo. Is there fix? When I plug it into my PC, I can't move filed to the phone for the recovery to flash a rom. I've tried using option 9 in the Toolkit, but it doesn't work.
Fast boot the stock image.
Sent from my Nexus 4 using xda app-developers app
You can use adb sideload if your custom recovery supports it to push a stock ROM and jump off from that point. The stock images are still gone, for what ever reason, so there's no way right now to officially jump back to stock.
nicatronTg said:
You can use adb sideload if your custom recovery supports it to push a stock ROM and jump off from that point. The stock images are still gone, for what ever reason, so there's no way right now to officially jump back to stock.
Click to expand...
Click to collapse
Yes, it does support it. Not sure how it works exatl. I guess I should finally install the SDK lol.
So what did you wipe in recovery to achieve this?
Someone will come along with the stock images if you keep bumping long enough.
Sent from my Nexus 4 using Tapatalk 2
Put your phone in to fastboot mode (hold down both volume buttons while you turn it on).
Stock 4.2.1 image; flash that with This.
joshnichols189 said:
So what did you wipe in recovery to achieve this?
Someone will come along with the stock images if you keep bumping long enough.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Well I think I found the Stock 4.2.1 ROM deodexed, I was going to try and flash this in the meantime. I tried fastboot flash RomName.zip but it's a nogo. And I wipsed data/factory reset, cache partition, dilvik cache, and system and SD card.
XanSama said:
Put your phone in to fastboot mode (hold down both volume buttons while you turn it on).
Stock 4.2.1 image; flash that with This.
Click to expand...
Click to collapse
Oh wow, it seems your stock rom was the key. I've tried that toolkit before, and it never worked with the stock rom it supplies, but for some reason I replaced it with the one you supplied and it seems to be going through now. Flashing as I type this, keeping fingers crossed.
EDIT: FIXED! YAY! I thanked you all for your input. I'm very greatful.
For future reference never wipe /system in recovery.

I rooted my cell after updating it to jb but my internal memory has turned permanentl

Sent from my GT-I9100 using xda premium
Uh if it's rooted thendownload root explorer and then open internal memory and press mount as r/w not sure if it will work also I don't take responcibility of your device so do it on your own risk best of luck :thumbup:
Sent from my ST26i using xda premium
more info
what do you mean internal memory has turned permanentl?
Need help too please!
I recently rooted my S3 i747 and then installed cyanogenmod 10. Keep in mind I am not a wiz at doing these things, however it did work. Here in lies my problems. 1. I hate this OS with a passion. Its just not what i thought it would be so I would love nothing more than to figure out how to remove it and return to stock firmware or another custom rom. 2. If i stay with this rom (for not being able to figure out how to remove it and install another) I am running out of storage internally. Its a great possibility I could have done something wrong. so with that being said, can anyone help me? I have tried more websites than I care to. thanks so much!
backup?
RicciLeigha said:
I recently rooted my S3 i747 and then installed cyanogenmod 10. Keep in mind I am not a wiz at doing these things, however it did work. Here in lies my problems. 1. I hate this OS with a passion. Its just not what i thought it would be so I would love nothing more than to figure out how to remove it and return to stock firmware or another custom rom. 2. If i stay with this rom (for not being able to figure out how to remove it and install another) I am running out of storage internally. Its a great possibility I could have done something wrong. so with that being said, can anyone help me? I have tried more websites than I care to. thanks so much!
Click to expand...
Click to collapse
did u make a backup before flashing cm?? did u flashed a custom recovery like cwm or twrp then flashed cm10?
Hmmmm
ironhide602 said:
did u make a backup before flashing cm?? did u flashed a custom recovery like cwm or twrp then flashed cm10?
Click to expand...
Click to collapse
Well what I did was follow along a youtube video... Which in turn may not have been the best idea. I remember doing some sort of back up on clockwork or something like that. I tried to go to recovery mode and restore but that didnt help. Im not sure what all I did to be honest. :/
RicciLeigha said:
Well what I did was follow along a youtube video... Which in turn may not have been the best idea. I remember doing some sort of back up on clockwork or something like that. I tried to go to recovery mode and restore but that didnt help. Im not sure what all I did to be honest. :/
Click to expand...
Click to collapse
edit... Pull the battery on your phone and put it back in. Hold up vol, home button and Power till you see the little words in the top left corner. It should say booting recovery really small. at that point take your finger off of the power button only and it will boot into Recovery.
If you have CWM recovery or TWRP you are golden...
Or else... see below
Find your phone in it's section you should be able to find a method using Odin to flash it back to stock and then you can read up and find the way to do everything you want.
Just do your research and look through the forum for your phone type/carrier and you should be able to find all of the information that you are looking for.
Search and you shall succeed!
:victory:
Sewrizer said:
why do you guys make things so complicated? the guy wants his phone back to stock.
The only thing you have to do is to go to www.sammobile.com/firmwares. Then put your phone number i9100 in the search box and choose any of the roms below. They are all stock, 2.3/4.x.x etc. The rom is in a zip file, however, you have to extract the tar file inside it.
Power off your phone then, while holding vol down, press and hold power.
Open odin in your pc then connect the phone to pc while being in download mode. press the pda button in odin and insert the .tar rom whoch you have just extracted. press start and you are done.
Sent from Area 51 using my GT-P1000
Click to expand...
Click to collapse
Way to jump in 5 days later and after a ton of pm's... and he only wanted more memory to run aps not stock.
Sent from my SCH-I545 using Tapatalk 2
Sewrizer said:
Sorry, I didn't look at the date, but that would have been a good fix.
Sent from Area 51 using my i9100p
Click to expand...
Click to collapse
Well returning to stock is just as easy as finding a stock ROM in his phones thread and flashing it, it'll be better in the long run that way as well because maybe he'll learn something.
Sent from my SCH-I605 using XDA Premium HD app

Greed lead to Brick!

Hey guys
I thought I'd just let you all know that my ambition to get 4.3 and lack of knowledge, led to my phone getting bricked today. I'm so devastated. I was following efrant's guide and flashed everything correctly and then as usual I lost half my storage and I followed the other guide to restoring the lost storage, once again i followed everything but i didn't get the storage back, then i did some cmd commands like the guide did. Next thing you know I may have done something wrong and I was at the bootloader screen and I couldn't reboot or go to recovery. Read and read nothing helped, called Google and they couldn't help me. I am now getting a replacement. SO there you go guys, just the greed of getting 4.3 caused me to brick my phone as well as my lack of knowledge I guess. Can't complain. Thought I'd share this with you all.
Div
P.S Moderators if this isn't suitable you guys can delete it no harsh feelings
Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta
Just flash the stock android image again, after all you have access to the bootloader, everything is fine
teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
fabrizziop said:
Just flash the stock android image again, after all you have access to the bootloader, everything is fine
Click to expand...
Click to collapse
This. You're totally not bricked.
Please follow the instructions in this thread:
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus⁴ using Tapatalk 4 Beta
Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?
Fataldesain said:
Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
it's totally worth it
nqk said:
Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?
Click to expand...
Click to collapse
Perhaps
Code:
# dd if=/dev/zero of=/dev/block/mmcblk0
Thats not greedy, your just too excited for 4.3
teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Click to expand...
Click to collapse
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....
Dvash27 said:
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....
Click to expand...
Click to collapse
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.
miniAndroidian said:
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone
Dvash27 said:
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone
Click to expand...
Click to collapse
Glad to know that it helped you mate
What about content on phone
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta
TToivanen said:
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
---------- Post added at 10:45 AM ---------- Previous post was at 09:46 AM ----------
leiftorem said:
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
Click to expand...
Click to collapse
I can see my phone listet under "Advanced Utility, but I cannot seem to pull the files from my phone!
I am getting really frustrated here now!
Anyone??
leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.
Mr. Kostik said:
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.
Click to expand...
Click to collapse
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)
leiftorem said:
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)
Click to expand...
Click to collapse
Oh well you should look in one of those threads on how to root and so on, flashing a recovery using a toolkit should also work. Texts will be gone.
Or from this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
Click to expand...
Click to collapse
But at some point you'd need a custom recovery anyway.

Sprint 4.4.2 is here.

Before downloading the OTA from the below link, please take note:
1. This is an OTA update (not the full firmware). This means that...
2. You should read the whole OP of this thread: http://forum.xda-developers.com/show....php?t=2639102
3. I am not taking responsibility for bricked devices.
4. This ZIP is not flashable via TWRP/CWM/PhilZ...stock recovery is required.
Here is the download link: http://goo.gl/D14Q5X
Thanks to nomad 64 for this.
I went through the update on my device. As it has been noted before, stock recovery is required. However, I did keep root through the process...woot!
Can I flash just stock recovery without flashing anything else, and if yes were can I find it
Sent from my XT1056 using xda app-developers app
nomad64 said:
Ditto. I am putting it on my server now to help mirror.
I went through the update on my device. As it has been noted before, stock recovery is required. However, I did keep root through the process...woot!
Click to expand...
Click to collapse
Just curious... how did you root? unlock your bootloader and use customer recovery and SuperUS? or did you use SlapMyMoto? if Slap... I've seen reports of still having root, but write protection being enabled again so you can't do anything with /system and the like..
I'm on Verizon not Sprint but I still consider this progress, happy and a little jealous of you guys!
Sent from my XT1060 using Tapatalk
charlie-n said:
Can I flash just stock recovery without flashing anything else, and if yes were can I find it
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
Yes. Reference the "Returning to Stock" section of this thread: http://forum.xda-developers.com/showthread.php?t=2603358. You have to download the whole firmware package for sprint, which sucks because you only need one file. After you have done what you need to do with TWRP/CWM, reboot your phone into the bootloader, then simply run
Code:
fastboot flash recovery recovery.img
fastboot reboot
KidJoe said:
Just curious... how did you root? unlock your bootloader and use customer recovery and SuperUS? or did you use SlapMyMoto? if Slap... I've seen reports of still having root, but write protection being enabled again so you can't do anything with /system and the like..
Click to expand...
Click to collapse
I unlocked my bootloader and flashed SuperSU. I live life on the edge!
At the time of the upgrade, I had flashed stock recovery and unfrozen Sprint Zone. I had also completely removed Xposed (uninstalled modules, disabled Xposed, and flashed Xposed-disaper.zip). I still had other root apps installed when I took the upgrade (TitaniumBackup and ROM Toolbox Pro). I have verified that they still work post-upgrade without additional work on my end.
If someone gets a copy of the ota zip faster than i upload it please message me a copy of your link and i will update the original post with it.
Dang it! Where's the AT&T one! First to get the phone, last to get the update.
jeffgt14 said:
Dang it! Where's the AT&T one! First to get the phone, last to get the update.
Click to expand...
Click to collapse
You won't be the last Verizon will haha
Sent from my XT1060 using Tapatalk
nomad64 said:
I unlocked my bootloader and flashed SuperSU. I live life on the edge! .
Click to expand...
Click to collapse
Cool. That is what I expected, and even if you lost root, you can just redo the custom recovery & SuperSU to get root back.
nomad64 said:
Yes. Reference the "Returning to Stock" section of this thread: http://forum.xda-developers.com/showthread.php?t=2603358. You have to download the whole firmware package for sprint, which sucks because you only need one file. After you have done what you need to do with TWRP/CWM, reboot your phone into the bootloader, then simply run
Code:
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
Just to confirm, this won't delete anything from the phone, just go back to stock recovery, correct?
Thanks for posting this just updated my phone
Sent from my XT1056 using Tapatalk
At the risk of sounding like a newbie, what are the steps to perform the update. I am coming from a Galaxy S4 and have only did OTA updates as they came. I just got this Moto X about 3 weeks ago during the $299 off contract price (couldn't resist). I would love to go ahead and do the update. My Moto X is stock, unrooted. Thanks
kbboykin said:
At the risk of sounding like a newbie, what are the steps to perform the update. I am coming from a Galaxy S4 and have only did OTA updates as they came. I just got this Moto X about 3 weeks ago during the $299 off contract price (couldn't resist). I would love to go ahead and do the update. My Moto X is stock, unrooted. Thanks
Click to expand...
Click to collapse
Settings - about phone - software update
MOTO X Slapped
[email protected] said:
Settings - about phone - software update
MOTO X Slapped
Click to expand...
Click to collapse
That, I know. I am asking about this file in the OP initial post, manually updating.
shaya4207 said:
Just to confirm, this won't delete anything from the phone, just go back to stock recovery, correct?
Click to expand...
Click to collapse
Correct. It will put you back on stock recovery and reboot your phone. Nothing in your /system or /sdcard will be touched. This is what I did to get back to stock recovery.
kbboykin said:
That, I know. I am asking about this file in the OP initial post, manually updating.
Click to expand...
Click to collapse
You need to have a completely stock system and the stock recovery installed. I manually flashed with super user still installed just fine but everything has to be completely stock straight out the box. To manually update you just download the zip in the OP.
1 boot into boot loader by holding volume down and power button
2 use volume key to scroll down to recovery press volume key up will put you into stock recovery with the red triangle.
3 to get to the menu screen in stock recovery you must hold volume key up then press power
4 choose to install from SD card and navigate to where the zip downloaded in this screen power button is used to select your choice. I moved the zip to the root of my SD but it usually will be found in downloads.
5 push power button to install ota manually. Be patient it will take a minute
I had it abort on me first try cause I forgot to change my fonts back to stock so be sure you are bone stock no tweaks or even V4A installed with STOCK RECOVERY.
Sent from my XT1056 using Tapatalk
dandan2980 said:
You need to have a completely stock system and the stock recovery installed. I manually flashed with super user still installed just fine but everything has to be completely stock straight out the box. To manually update you just download the zip in the OP.
1 boot into boot loader by holding volume down and power button
2 use volume key to scroll down to recovery press volume key up will put you into stock recovery with the red triangle.
3 to get to the menu screen in stock recovery you must hold volume key up then press power
4 choose to install from SD card and navigate to where the zip downloaded in this screen power button is used to select your choice. I moved the zip to the root of my SD but it usually will be found in downloads.
5 push power button to install ota manually. Be patient it will take a minute
I had it abort on me first try cause I forgot to change my fonts back to stock so be sure you are bone stock no tweaks or even V4A installed with STOCK RECOVERY.
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Thanks, this is what I was looking for. I am completely stock except for apps dl'd from Play Store and Amazon.
kbboykin said:
Thanks, this is what I was looking for. I am completely stock except for apps dl'd from Play Store and Amazon.
Click to expand...
Click to collapse
That's OK with the apps from the play store and amazon just things like exposed modules and viper 4 android have to be uninstalled basically anything that modifies your system cannot be installed. I did have Super user installed when I applied the ota with no problems though
Sent from my XT1056 using Tapatalk
dandan2980 said:
That's OK with the apps from the play store and amazon just things like exposed modules and viper 4 android have to be uninstalled basically anything that modifies your system cannot be installed. I did have Super user installed when I applied the ota with no problems though
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
SuperSU or Superuser, and what version if SuperSU. Last time I checked, SuperSU installed another system file incase the daemon method needed to be used.

Categories

Resources