Related
I've seen a few threads about 16GB version phones losing half their storage after flashing.
Here are the steps to fix it:
As dellenrules mentioned in post #48 there appears to be an easier way to fix the problem:
-Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
-Clear cache
-Factory reset
If for some reason that doesn't work, you can try this method:
First, you'll need fastboot.exe on your computer. If this happened to you, you should have fastboot installed If not, see section A of efrant's "back-to-stock" guide.
Next, You'll want the latest occam image. https://developers.google.com/android/nexus/images#occam
Finally, boot into the bootloader and run these commands...
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz10o.img
fastboot reboot-bootloader
fastboot -w update image-occam-jdq39.zip
Enjoy your 16GB again.
Note #1 If you encounter a boot loop after this procedure boot into stock recovery (use volume up and power to open the recovery menu) then wipe cache and factory reset.
Note #2 erikieperikie tested restoring a Nandroid backup after completing this process. The backup applied successfully and they still had 16GB user space. Details here.
UPDATED 3/13/13 for 4.2.2
not sure if i fall into this category, but my 16gb has only 8.46gb available (out of 12.92gb). I did unlock and root earlier. For the life of me, I can't seem to find the "missing" space. I'll try the above here in a bit.
RussianBear said:
not sure if i fall into this category, but my 16gb has only 8.46gb available (out of 12.92gb). I did unlock and root earlier. For the life of me, I can't seem to find the "missing" space. I'll try the above here in a bit.
Click to expand...
Click to collapse
Did you make any nandroid backups? Those usually won't be reported in storage.
Sent from my Nexus 7 using xda premium
El Daddy said:
Did you make any nandroid backups? Those usually won't be reported in storage.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
sure did. didn't think it would take "that" much space
RussianBear said:
sure did. didn't think it would take "that" much space
Click to expand...
Click to collapse
This guide is to recover the full user space after a bad flash. (Not quite sure what is causing it exactly)
In your situation your user space is fine. The nandroid blob just isn't being reported within the built in utility. If you delete the blob that storage used should be reported again.
Sent from my Nexus 7 using xda premium
El Daddy said:
This guide is to recover the full user space after a bad flash. (Not quite sure what is causing it exactly)
In your situation your user space is fine. The nandroid blob just isn't being reported within the built in utility. If you delete the blob that storage used should be reported again.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
figured it out. /data/media had a folder called "0" that mounts when i plug the phone in, but it also had the nandroid backup in the cwm folder along with some of my files i tried to restore. not sure how they got there, but they were causing the reporting issues.
I've just added this guide to the Nexus 4 Complete Index
Sent from my Nexus 7 using xda premium
RussianBear said:
figured it out. /data/media had a folder called "0" that mounts when i plug the phone in, but it also had the nandroid backup in the cwm folder along with some of my files i tried to restore. not sure how they got there, but they were causing the reporting issues.
Click to expand...
Click to collapse
I am having the same problem and also deleted these files.
Might be a noob like question but,
How do I use the commands listed at the beginning?
gmanb said:
I am having the same problem and also deleted these files.
Might be a noob like question but,
How do I use the commands listed at the beginning?
Click to expand...
Click to collapse
You'll need to download adb for those. Have you restarted after deleting the files?
El Daddy said:
I've seen a few threads about 16GB version phones losing half their storage after flashing.
Here are the steps to fix it.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz10l
fastboot reboot-bootloader
fastboot -w update image-occam-jop40d
Enjoy your 16GB again.
Click to expand...
Click to collapse
i fail to perform this command fastboot -w update image-occam-jop40d.
it said can not read
robert_gan said:
i fail to perform this command fastboot -w update image-occam-jop40d.
it said can not read
Click to expand...
Click to collapse
I apologize. There should be a .zip at the end of that command. I will update the OP.
El Daddy said:
I apologize. There should be a .zip at the end of that command. I will update the OP.
Click to expand...
Click to collapse
EDITED: Noob in the house. Nevermind. Thanks!
El Daddy said:
I apologize. There should be a .zip at the end of that command. I will update the OP.
Click to expand...
Click to collapse
thanks very much for u reply!!
and sry for the n00b question again, so when i follow u guide,is it means i will flash a new system?
cuz i stuck at X logo soo many times,and every time i need to follow every single steps of back to stock guide exactly,then wipe the cache and factory reset to get pass it.but there is a problem, the storage only shows 5.7G.
once again thank u !!
robert_gan said:
thanks very much for u reply!!
and sry for the n00b question again, so when i follow u guide,is it means i will flash a new system?
cuz i stuck at X logo soo many times,and every time i need to follow every single steps of back to stock guide exactly,then wipe the cache and factory reset to get pass it.but there is a problem, the storage only shows 5.7G.
once again thank u !!
Click to expand...
Click to collapse
I guess I'm not following exactly what you are asking.
Yes it re-flashes the system. If you follow the steps in the original post your phone should show 16GB again if that is the version you have.
Sent from my Nexus 7 using Tapatalk HD
gmanb said:
I am having the same problem and also deleted these files.
Might be a noob like question but,
How do I use the commands listed at the beginning?
Click to expand...
Click to collapse
It wasn't actually a problem
See here
http://forum.xda-developers.com/showthread.php?t=2067293
I keep getting the same error with the last command.
error: failed to load 'image-occam-jop40d.zip': No error
I have directed it to the right place, but still nothing's happening.
Caumen said:
I keep getting the same error with the last command.
error: failed to load 'image-occam-jop40d.zip': No error
I have directed it to the right place, but still nothing's happening.
Click to expand...
Click to collapse
Try rebooting your computer. I had that error once trying to flash recovery on my gnex. Rebooting my PC fixed it.
Sent from my Nexus 4
El Daddy said:
Try rebooting your computer. I had that error once trying to flash recovery on my gnex. Rebooting my PC fixed it.
Sent from my Nexus 4
Click to expand...
Click to collapse
Oh ****, the classic, let's see if it helps.
---------- Post added at 10:22 PM ---------- Previous post was at 09:59 PM ----------
It didn't help rebooting the computer.
What could it be?
I actually own prototype device with 6GB of memory and "NOT FOR SALE" text on the back
Amount of memory does not changed after reflash
But inside occam-jop40d-factory-ca7602f0.tgz i found update for radio hardware which fix WiFi connection issues.
So, in case that your phone see APs but cannot connect to them you may use radio firmware from given archive.
Code:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img
t3h.Dr01d said:
I actually own prototype device with 6GB of memory and "NOT FOR SALE" text on the back
Amount of memory does not changed after reflash
But inside occam-jop40d-factory-ca7602f0.tgz i found update for radio hardware which fix WiFi connection issues.
So, in case that your phone see APs but cannot connect to them you may use radio firmware from given archive.
Code:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img
Click to expand...
Click to collapse
5.67GB is the formatted size of the 8GB version.
Sent from my Nexus 4
i rooted my htc vivid yesterday and i wanted to get a custom rom do i downloaded it and flashed it on my phone but when i rebooted my phone all that comes up is the cyanogenmod startup screen with the spinning circle and nothing else happens i deleted my recovery by mistake and now im stuck like this can anybody help?
tpaina380 said:
i rooted my htc vivid yesterday and i wanted to get a custom rom do i downloaded it and flashed it on my phone but when i rebooted my phone all that comes up is the cyanogenmod startup screen with the spinning circle and nothing else happens i deleted my recovery by mistake and now im stuck like this can anybody help?
Click to expand...
Click to collapse
Have you wiped data and both cache as well..??
Also have your flashed latest Gapps..?
i need to correst apps
i was hoping to flash it back to the stock Rogers [ICS] 4.0.3 ruu do you know where i can get that ruu?
Yes
Yes ive done that and it still shows the cyanogenmod screen when i start up the phone it wont load past that
If its your first time installing... you need to wipe data as well
Sent from my Vivid 4G using Tapatalk 2
Did you fastboot flash the boot.img
Sent from my HTC PH39100 using xda app-developers app
No
i dont know where the boot.img is
tpaina380 said:
i dont know where the boot.img is
Click to expand...
Click to collapse
It's in the Rom zip, assuming your not s-off it must be flashed separately
You can check if your s-off by going to hboot, toward the top it will say s-off or s-on...which basically means security off/on - its another level of security HTC added on above the bootloader
Sent from my HTC PH39100 using Tapatalk 2
It says s-on
so what do i do from here?
Put your boot.img into the folder which your fastboot and adb are and then open a terminal to the folder. Then put your phone into fastboot by entering the bootloader. Then type fastboot devices to see if your device is connected to the computer. If it comes up with your serial number continue if not try again. Then type fastboot flash boot.img and then go to recovery and reflash the rom.
---------- Post added at 11:13 AM ---------- Previous post was at 11:10 AM ----------
If you need help with a better guide try
http://forum.xda-developers.com/showthread.php?t=1416836
and read the flash custom kernel/recovery the third option
Didnt work
all is says is
C:\Fastboot Command Folder>fastboot devices
MB201VJ21706 fastboot
C:\Fastboot Command Folder>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
I worked!!!!!!!!!!! DDDDDD
When i typed in "fastboot flash boot.img" it didn't work so i tried "fastboot flash boot boot.img" and it worked i flashed cm-10 afterwards and then i flashed the ics gapps and it loaded up my holiday is now running android 4.1.2 and it is awsome!!!!!!!!!!!!!!!!!!!!! thank you for the help much appreciated
You figured out what you where doing wrong before i could tell you. Well done glad to help.
tpaina380 said:
i rooted my htc vivid yesterday and i wanted to get a custom rom do i downloaded it and flashed it on my phone but when i rebooted my phone all that comes up is the cyanogenmod startup screen with the spinning circle and nothing else happens i deleted my recovery by mistake and now im stuck like this can anybody help?
Click to expand...
Click to collapse
yea bro i had the same issue. first thing redownload the cm10 rom. sometimes you can get a bad dl. second you have to take the boot.img and flash it using fastboot. once you do that perform the wipes. then immediantly flash the cm10 rom from recovery. that should work. if you deleted the recovery witch is hard to do lol. u will have to use odin. hope i help
Bigc13 said:
yea bro i had the same issue. first thing redownload the cm10 rom. sometimes you can get a bad dl. second you have to take the boot.img and flash it using fastboot. once you do that perform the wipes. then immediantly flash the cm10 rom from recovery. that should work. if you deleted the recovery witch is hard to do lol. u will have to use odin. hope i help
Click to expand...
Click to collapse
No no... bad advice... ODIN is for Samsung...
Sent from my Vivid 4G using Tapatalk 4 Beta
Download either TWRP or WCX recovery. As long as your phone can get to the bootloader, you can get into Fastboot and flash the recovery again. Make sure the recovery is in the same folder where you have the adb.exe and fastboot.exe. Open up a command prompt, then change directory to where your fastboot and adb are. Type in fastboot flash recovery "recovery".img where "recovery" would be the name of the recovery file you download. This will flash pretty quickly. Once you get to that point, you probably are S-On so you need to make sure to extract the boot.img from the ROM you downloaded. Use either winrar or 7zip to extract the boot.img to the same location where you have the fastboot.exe and adb.exe. Then go to the command prompt again and change directories to the same folder where you have fastboot and adb. Type in fastboot flash boot boot.img. I usually would run this 3 times to make sure it loads properly. Once that is done reboot the phone again.
Sorry I used it on the HTC evolution 4g and it worked so I figured it would work for vivid
Sent from my Vivid 4G using xda app-developers app
Bigc13 said:
Sorry I used it on the HTC evolution 4g and it worked so I figured it would work for vivid
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
?
How...
I've never heard of using ODIN on anything other than Samsung?
Anyone else?
Sent from my Vivid 4G using Tapatalk 4 Beta
Man I used a jig to put in dl mode to flash a file I can't remember exactly it was a couple years ago lol but sorry I shouldn't have said nt
rignfool said:
?
How...
I've never heard of using ODIN on anything other than Samsung?
Anyone else?
Sent from my Vivid 4G using Tapatalk 4 Beta
Click to expand...
Click to collapse
That would be a no for me as well... but these Springdale-ians... never know what they will come up with. JK.
Hello guys, I really messed up my phone.
I was trying to relock, and unroot my phone but it didnt go as planned.
Long story short, I cannot flash ANYTHING through CWM or TWRP (latest versions) and none of my files shows up in either of these recoveries. When i push a file through adb i get an error code on both. I believe that CWM said it cannot mount E:/SD Card.
I also have nothing to bootup to (bootloop)
I really need my phone and any help would be greatly appreciated!
mymonkeyballs said:
Hello guys, I really messed up my phone.
I was trying to relock, and unroot my phone but it didnt go as planned.
Long story short, I cannot flash ANYTHING through CWM or TWRP (latest versions) and none of my files shows up in either of these recoveries. When i push a file through adb i get an error code on both. I believe that CWM said it cannot mount E:/SD Card.
I also have nothing to bootup to (bootloop)
I really need my phone and any help would be greatly appreciated!
There will be a cash reward for the person to help me get this working. (paypal)
Click to expand...
Click to collapse
Just calm down buddy... This is the second thread you've made so far. Now I'm going to help you and I dont want any of your money. I just want you to agree on one term and that is to not make another thread about this.
That sucks balls MyMonkeyBalls..
Yeah, has happened to me too, I had to send in to get fixed, been 3 weeks so far.
Have a read over the forums for mine and others same issue, there are tips on how to fix but this is becoming very common at the moment, I can not offer any suggestions because everything i did did not work
Good luck
Tw1tchy said:
Just calm down buddy... This is the second thread you've made so far. Now I'm going to help you and I dont want any of your money. I just want you to agree on one term and that is to not make another thread about this.
Click to expand...
Click to collapse
Sorry bro , just freaking out. Agreed.
twerg said:
That sucks balls MyMonkeyBalls..
Click to expand...
Click to collapse
LOL!!
anyways...
what build of CM10.2 was it (example: cm-10.2-20130809-UNOFFICIAL-m7ul.zip)?
Kernel?
Firmware? (or Hboot#)
Do you have nandroid?
have you tried to go to stock?
S-OFF?
locked/relocked/unlocked?
logcats? (twrp or cwm)
ATT, TMO, Sprint, GPE, etc?
Any other info?
Tw1tchy said:
LOL!!
anyways...
what build of CM10.2 was it (example: cm-10.2-20130809-UNOFFICIAL-m7ul.zip)?
Kernel?
Firmware? (or Hboot#)
Do you have nandroid?
have you tried to go to stock?
S-OFF?
locked/relocked/unlocked?
logcats? (twrp or cwm)
ATT, TMO, Sprint, GPE, etc?
Any other info?
Click to expand...
Click to collapse
cm-10.2-20130815-UNOFFICIAL-m7ul_doubleTap.zip
Kernel that came with the ROM
1.44.0000
I dont believe I have a nandroid anymore, if i do it would be TWRP's.
I cant get back to stock
S-On
Unlocked
No
Bell (unlocked)
Nothing is showing up in Twrp or CWM its like i have nothing installed on my device. I have a constant bootloop with the cm10.2 boot animation.
I believe it all started going crazy when i tried to go back to stock and wipe the data (i did a factory reset from hboot as well as cwm)
mymonkeyballs said:
cm-10.2-20130815-UNOFFICIAL-m7ul_doubleTap.zip
Kernel that came with the ROM
1.44.0000
I dont believe I have a nandroid anymore, if i do it would be TWRP's.
I cant get back to stock
S-On
Unlocked
No
Bell (unlocked)
Nothing is showing up in Twrp or CWM its like i have nothing installed on my device. I have a constant bootloop with the cm10.2 boot animation.
Click to expand...
Click to collapse
Before LC's CM10.2 were you running a 4.1.2 rom?
Tw1tchy said:
Before LC's CM10.2 were you running a 4.1.2 rom?
Click to expand...
Click to collapse
No. 4.2.2
mymonkeyballs said:
No. 4.2.2
Click to expand...
Click to collapse
Okay well that rules out the simple.
Now lets see if i understand the situation correctly. If you try to boot into system all you get is a CM bootloop and custom recovery's show an empty sdcard? You say adb commands dont work but have you tried fastboot commands in fastboot mode yet?
Try:
fastboot devices
fastboot erase cache
fastboot reboot-recovery
Dude - he's done a factory reset from the bootloader which has wiped his virtual sd card. You basically need to format it back into a fat32 partition so the adb side load will work.
Sent from my HTC One using XDA Premium 4 mobile app
Tw1tchy said:
Okay well that rules out the simple.
Now lets see if i understand the situation correctly. If you try to boot into system all you get is a CM bootloop and custom recovery's show an empty sdcard? You say adb commands dont work but have you tried fastboot commands in fastboot mode yet?
Try:
fastboot devices
fastboot erase cache
fastboot reboot-recovery
Click to expand...
Click to collapse
Yes. Fastboot commands work but doesnt resolve my issue.
thejosh86 said:
Dude - he's done a factory reset from the bootloader which has wiped his virtual sd card. You basically need to format it back into a fat32 partition so the adb side load will work.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So what do I have to do sorry
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Click to expand...
Click to collapse
I would highly appreciate that. Thanks bro
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
Thanks ! Testing it now. Will update.
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
HALLELUJAH !! She is working ! Words cannot describe how happy i am ! i thought i was done! THANK YOU!
hahaha no worries mate, it's all part of the learning process.
Now just remember when you've got a custom recovery you don't need to use the factory reset in bootloader!
We saved mymonkeyballs =D
Sent from my One using xda app-developers app
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
thejosh86 said:
hahaha no worries mate, it's all part of the learning process.
Now just remember when you've got a custom recovery you don't need to use the factory reset in bootloader!
Click to expand...
Click to collapse
Haha, that was kinda stupid now that i look back on it. I cannot say thank you enough!
mymonkeyballs said:
Haha, that was kinda stupid now that i look back on it. I cannot say thank you enough!
Click to expand...
Click to collapse
Hey dude, don't forget to put [Resolved] in the thread title.
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
As far as I can figure, the only way would to use an app to backup the data, flash back to factory, re-root and restore the data. The OTA update will remove root access. I would do a backup with CWM first if possible.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
if you know what you actually changed with root permissions then you can just flash stock recovery onto the phone then remove all things root and put everything back to normal stock (like unfreezing things out of tibu or whatever) then take the ota. if you are not sure what you changed, you can flash recovery and system then take the ota (assuming you didn't flash new kernals or anything else major).
And if you just want to keep data then you can flash stock ota with rsdlite and remove the two entries that erase data and cache in the xml file. Then take the ota. or flash the fxz and remove the same data erasing entries in the xml
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Schaweet said:
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Click to expand...
Click to collapse
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
robwege said:
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Schaweet said:
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Click to expand...
Click to collapse
I kept the old boot animation file so I can just move it back.
Sent from my XT1060 using XDA Premium 4 mobile app
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Schaweet said:
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
OK. I think I will do your method instead. I will unfreeze the apps, install old boot logo and disable xposed just to be safe. Then I will do your method. Wish me luck.
Sent from my XT1060 using XDA Premium 4 mobile app
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
You don't even need an unlocked bootloader, you can still flash stock images on a locked bootloader. Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
eksasol said:
Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
Click to expand...
Click to collapse
You are correct. You can only flash a custom recovery if your bootloader is unlocked. That is what unlocking your bootloader allows you to do - flash unsigned recovery files (i.e., custom recoveries) and obviously, TWRP is not signed by motorola. Then once you have a custom recovery, the custom recovery allows you to flash unsigned operating systems.
If your bootloader is locked, you cannot flash an unsigned recovery.
Schaweet said:
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I meant step 7.
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Click to expand...
Click to collapse
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
NightThyme said:
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
Click to expand...
Click to collapse
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Sent from my Dev Edition Moto X
Schaweet said:
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Click to expand...
Click to collapse
This.
If I wanted to go back to stock from an aosp based ROM could I use the mfastboot recovery and system method or do I ha e to rsd.... I'm unlocked btw
Sent from my Moto X using Tapatalk
https://developers.google.com/android/nexus/images#nakasi
Factory Images for 4.4.3 in the link.
Ohgami_Ichiro said:
https://developers.google.com/android/nexus/images#nakasi
Factory Images for 4.4.3 in the link.
Click to expand...
Click to collapse
How do I flash this?
Sent from my Nexus 7 using XDA Premium 4 mobile app
What is the kernel version for this update? I know nvidia released source code for a 3.4 kernel
Sent from my Nexus 7 using XDA Free mobile app
a2r3f said:
How do I flash this?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Linux Quick and simple(this is what I do with a high degree of success, your results might vary. use caution) :
1) Download the factory image for your device.
2) $ tar -xvf nakasig-ktu84l-factory-8ce3d5ea.tgz
3) $ cd /path/to/extracted/nakasig-ktu84l
4) $ adb reboot bootloader
4) $ ./flash-all.sh
This will completely wipe your tablet and install 4.4.3. Be sure this is what you want to do. ./falsh-all.sh is just a shell script that executes the following in order:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasig-ktu84l.zip
So in theory you could comment out the line "fastboot erase userdata" if you wanted to preserve your data, but I usually just sync my photos off somewhere, and restore my apps when i'm done.
You will need to have "adb" and "fastboot" installed and in your PATH.
Cheers and may the force be with you.
*attention*: nakasig and taliapia are for the GSM version only, *not* for the WIFI version. If you flash those images to your WIFI-Nexus you'll create a brick.
Btw.: I would unpack the zip and flash boot.img and system.img only. In that case a smooth update without any data loss should be possible ...
AndDiSa said:
*attention*: nakasig and taliapia are for the GSM version only, *not* for the WIFI version. If you flash those images to your WIFI-Nexus you'll create a brick.
Btw.: I would unpack the zip and flash boot.img and system.img only. In that case a smooth update without any data loss should be possible ...
Click to expand...
Click to collapse
Just read the whole page for your appropriate D/L:
4.4.3 Factory Images "nakasi" for Nexus 7 (Wi-Fi) https://dl.google.com/dl/android/aosp/nakasi-ktu84l-factory-0e21238f.tgz
4.4.3 Factory Images "nakasig" for Nexus 7 (Mobile) https://dl.google.com/dl/android/aosp/nakasig-ktu84l-factory-8ce3d5ea.tgz
Can someone make a zip that's flashable for multirom? Grouper? Please?
Sent from my Nexus 7 using Tapatalk
Full flashable zip from Tasssadar, thanks to him...
http://forum.xda-developers.com/showpost.php?p=53125741&postcount=2680
dmwarren said:
Linux Quick and simple(this is what I do with a high degree of success, your results might vary. use caution) :
1) Download the factory image for your device.
2) $ tar -xvf nakasig-ktu84l-factory-8ce3d5ea.tgz
3) $ cd /path/to/extracted/nakasig-ktu84l
4) $ adb reboot bootloader
4) $ ./flash-all.sh
This will completely wipe your tablet and install 4.4.3. Be sure this is what you want to do. ./falsh-all.sh is just a shell script that executes the following in order:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasig-ktu84l.zip
So in theory you could comment out the line "fastboot erase userdata" if you wanted to preserve your data, but I usually just sync my photos off somewhere, and restore my apps when i'm done.
You will need to have "adb" and "fastboot" installed and in your PATH.
Cheers and may the force be with you.
Click to expand...
Click to collapse
Hi, guys...
It might be a also good idea to comment out this line anyway ... fastboot flash bootloader bootloader-tilapia (or grouper)-4.23.img, if you already have the v4.23 bootloader installed, as I suspect most have...
...as it fails to fastboot flash without error, in much the same way as previous versions of the v4.23 bootloader did.
Specific details here... and on that associated thread generally.
------------------------------------------------
Not quite sure what's going on with Google and Nexus 7 bootloaders... there seem to be more variants of v4.23 floating around than I have odd socks.... and only one seems to flash without problems.
------------------------------------------------
Anyhow... I've just done a full fastboot flash (minus v4.23 bootloader) of Android 4.4.3-KTU84L (I needed to backup my data anyway... it's been a while).
All seems fine so far... the ironic thing about this supposedly **new** factory image from Google, is that even after flashing it, there are **still** 19 Google apps that require updating from PlayStore... Chrome, Gmail, Google+, Google Keyboard, Hangouts, Maps, YouTube to name just a few.
Now to restore my data from my laptop... flash TWRP, make a Nandroid backup, re-root and re-install my apps via Titanium.
Good luck everybody.
Rgrds,
Ged.
When installing, will it wipe out previous downloaded apps?
Sent from my Nexus 10 using XDA Free mobile app
Laugher19 said:
What is the kernel version for this update? I know nvidia released source code for a 3.4 kernel
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
In Fact, it is: "3.1.10-g1e42d16". On 4.4.2 it was: "3.1.10-g4776c68". So no 3.4. But a "new" version of the kernel!
Unfortunately, Google "forgot" the "kitkat-mr2-release" Branch in kernel/tegra:
https://android.googlesource.com/kernel/tegra/+refs (flo-kernel has the branch)
Stupid Google, we want the new source!
Edit: Google opened the Branch :victory:
https://android.googlesource.com/kernel/tegra/+/android-tegra3-grouper-3.1-kitkat-mr2
striker59 said:
When installing, will it wipe out previous downloaded apps?
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
If you flash only boot.img and system.img you will keep everything. I just updated in this way half an hour ago without any problems.
Sent from my Nexus 7 using XDA Free mobile app
Yay
Anyone who installed it is it fast or stay with f2fs slim?
Sent from my HTC One_M8 using Tapatalk
Lag
Holy crap, I hope this eliminates the lag I have been experiencing since "upgrading" to Kit Kat in the first place.
timberdc said:
Holy crap, I hope this eliminates the lag I have been experiencing since "upgrading" to Kit Kat in the first place.
Click to expand...
Click to collapse
It feels a little smoother but while downloading apps from the Play Store, it can be unresponsive.
DroidOnRoids said:
It feels a little smoother but while downloading apps from the Play Store, it can be unresponsive.
Click to expand...
Click to collapse
Yeah I had that problem since 4.1. Since then I just hit update and then let it do it's thing and then get back to what I was doing. Really can't expect to have Google fix that since this will probably be our last update.
vorcers said:
In Fact, it is: "3.1.10-g1e42d16". On 4.4.2 it was: "3.1.10-g4776c68". So no 3.4. But a "new" version of the kernel!
Unfortunately, Google "forgot" the "kitkat-mr2-release" Branch in kernel/tegra:
https://android.googlesource.com/kernel/tegra/+refs (flo-kernel has the branch)
Stupid Google, we want the new source!
Click to expand...
Click to collapse
Well that stinks
Sent from my Nexus 7 using XDA Free mobile app
I am on latest AOKP with latest CWM, bootloader 4.23 unlocked, and rooted of course. I dont have anything on this tablet that I cant recover from google servers.
I need to do a clean install and go back to locked BL, unrooted, new stock rom. which way to go?
Thanks
hormosapiens said:
I am on latest AOKP with latest CWM, bootloader 4.23 unlocked, and rooted of course. I dont have anything on this tablet that I cant recover from google servers.
I need to do a clean install and go back to locked BL, unrooted, new stock rom. which way to go?
Thanks
Click to expand...
Click to collapse
Hi, hormosapiens...
The way I'd do it, is to use fastboot...
Fastboot flash the latest Google factory stock image (Android 4.4.3, build KTU84L) for your specific Nexus 7 type... this will completely wipe the device, and return it to it's 'official' state, running factory stock Android.
Root will be lost, as will any Custom Recovery (CWM or TWRP) you may currently have installed.
The only thing remaining to do aftwards, is to relock the bootloader, with the command fastboot oem lock.
Rgrds,
Ged.
I put this on my nexus 5 and the nexus 7.1
On N5 its great a lot of improvements. like the new phone app
N7.1 though it feels like they took a step back in in the direction of separate tablet and phone interface. Performance wise it feels a little faster.
Only gripe i have over all is quick settings go to the setting instead of just toggling and hold for settings. ( maybe i have been off stock for to long and that is how stock is ?)