umm... I don't have much to say but anyway shortly.
Unlock the bootloader, root, install cyanogen custom ROM cm-11-20140205-NIGHTLY-flo, mess with kernels,
install the factory image, reset bootloader, re-root, reinstalled Cyanogen custom ROM, and now... my N7 storage only available 11.29 GB.
not sure, I think that factory image was for 16GB N7.
so I want to re-partition this to takeback my 26GB but I don't know how to do that.
or, if there any recovery solution?
add
Uh... mayby I installed Factory image for LTE Models...
You shouldn't have been able to flash LTE model, should have came up with an error.
Did you preform a complete wipe, cache wipe in custom recovery? Do that and then flash your ROM.
Sent from my Nexus 7 using xda app-developers app
Wow...
datallboy said:
You shouldn't have been able to flash LTE model, should have came up with an error.
Did you preform a complete wipe, cache wipe in custom recovery? Do that and then flash your ROM.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Oh, Thanks. problem solved:laugh:
All problems were comes from that wrong LTE Image
I just DL/installed right FI and check again my storage, done! lol.
and that means I was installing wrong image whole day... Ugh...
anyway I'm so happy about I can use this again
Really thanks!
Related
I was wondering if the radio could be the cause of this i upgraded to the fc04 /fc05 radios,i was under the impression that the framework was upgraded but not sure if i should flash back to the fa02 radios. I know stock radios have been a culprit in the past and was wondering if this still was the case . any input would be greatly appreciated. thanks in advance.Im on verizon lte by the way.
recovery, wipe cache/dalvik
if that doesnt do it:
recovery, format /system, reflash rom+gapps
if that still doesnt solve it
recovery, wipe data/factory reset, format /system, reflash rom+gapps
did you update radios with fastboot?
Yes to updating the radios, but I guess I'm wondering if the new radios are what are causing this I did a full wipe and actually a full restore. Right now I'm on the 5/10 will wait to get home to try new nightly in case I need the computer again.
Sent from my Galaxy Nexus using xda premium
jmk4412 said:
Yes to updating the radios, but I guess I'm wondering if the new radios are what are causing this I did a full wipe and actually a full restore. Right now I'm on the 5/10 will wait to get home to try new nightly in case I need the computer again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not likely
Sent from my Transformer Prime TF201
The first three or four roms I ever flashed on my G-Nex got caught in the bootloop after flashing with ROM manager. Turned out I was missing the wipe cache/dalvik step, and the same zips have since all worked fine.
OK well I'm getting ready to flash the latest nightly I'll let y'all know if I boot loop again. Thanks.
Sent from my Galaxy Nexus using xda premium
Im running rascream (aosp) and trinity kernel. Ive flashed alot of roms and kernels since i bought the phone. I know if i relock bootloader and unlock it everything gets wiped. Do i have to flash a stock image first or can i just stay on the custom rom?
Sent from my Galaxy Nexus using xda premium
If you stay on your current ROM and simply relock your bootloader, you won't lose any data. You will only lose data if you decide to unlock it again at a future date.
Smallsmx3 said:
Im running rascream (aosp) and trinity kernel. Ive flashed alot of roms and kernels since i bought the phone. I know if i relock bootloader and unlock it everything gets wiped. Do i have to flash a stock image first or can i just stay on the custom rom?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
if you lock and unlock, it wipes all the user data, but should leave the /system image alone.
so you would still have your custom rom, just no data including in the sd card folder.
If you want it to be stock, you have to flash the stock images. I wouldn't lock the bootloader unless you plan on sending it in for warranty work, as the next time you unlock it wipes the phone again.
Sent from my Galaxy Nexus using xda premium
Smallsmx3 said:
Im running rascream (aosp) and trinity kernel. Ive flashed alot of roms and kernels since i bought the phone. I know if i relock bootloader and unlock it everything gets wiped. Do i have to flash a stock image first or can i just stay on the custom rom?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
If you want to wipe boot into fastboot mode and type the following:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase cache
That will clear your ROM, kernel and all your data (including /sdcard).
You can also do it in recovery -- I'm pretty sure I saw a script floating around. I could also put one together for you, but it is really easy to wipe using fastboot.
Ok....so will it be like stock? I guess what im trying to say is im trying to clear out any junk thant might be left over from other roms. So unlocking the bootloader again would be like just like wiping all user data in clockwork?
Sent from my Galaxy Nexus using xda premium
Smallsmx3 said:
Ok....so will it be like stock? I guess what im trying to say is im trying to clear out any junk thant might be left over from other roms. So unlocking the bootloader again would be like just like wiping all user data in clockwork?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
it will not be stock if you just lock then unlock the bootloader.
it will be the custom rom, but with no user data including no user data on the /sdcard folder.
if you want stock, you have to flash the stock images.
Smallsmx3 said:
Ok....so will it be like stock? I guess what im trying to say is im trying to clear out any junk thant might be left over from other roms. So unlocking the bootloader again would be like just like wiping all user data in clockwork?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
What do you want to do: go back to stock, or wipe?
To wipe, do what I said above. To got back to stock, you need to flash the system, boot and userdata images from a stock ROM.
EDIT: Zepius iz faster.
efrant said:
EDIT: Zepius iz faster.
Click to expand...
Click to collapse
i r teh winnar!
The procedure is in my sig
I want to wipe....but i want it to wipe clean....like any junk cm9 or aokp might have left lying around....i want to stay on rascream.....just wondering what the best route is...thanks for all the quick responses
Sent from my Galaxy Nexus using xda premium
Smallsmx3 said:
I want to wipe....but i want it to wipe clean....like any junk cm9 or aokp might have left lying around....i want to stay on rascream.....just wondering what the best route is...thanks for all the quick responses
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Do what I mentioned in my first post and then re-flash rascream. But again, note that it will wipe EVERYTHING, including /sdcard.
Smallsmx3 said:
I want to wipe....but i want it to wipe clean....like any junk cm9 or aokp might have left lying around....i want to stay on rascream.....just wondering what the best route is...thanks for all the quick responses
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Data wipe, wipe dalvik, wipe battery stats and format system works for me
Take a paper towel, lightly dampen it and slowly wipe the surface of the phone. Take another paper towel and slowly dry the surface of the phone.
Wiping complete!
I want to flash CM9 on my Sprint Nexus and reading through the threads I cant' get the info I need.
Do i need to update any radios to do anything else before flashing this? I just rooted yesterday using the dev tool and I'm itching to flash. I came over from HTC EVO and SGS2 and the nexus is all new to me, but so far loving it. Thanks so much for the help! below is my build information:
Baseband Version:
L700.05.V.FD02/L700.FD02
Build Number:
IMM76D.L700FD02
Make sure you're running a custom recovery such as TWRP or Clockwork and you should be fine.
ROM and radios are completely separate.
Smokeey said:
Make sure you're running a custom recovery such as TWRP or Clockwork and you should be fine.
ROM and radios are completely separate.
Click to expand...
Click to collapse
Ok so I can flash without updating the Radios? I'm currently using CWM
cyaiphone said:
Ok so I can flash without updating the Radios? I'm currently using CWM
Click to expand...
Click to collapse
Yes.
You already have the most updated radios.
Sent from a phone...
Thanks guys!
Dammit sorry one last question.
My My EVO had an SD Card. So if i place the ROM on my Nexus and I wipe data in recovery I'm I deleting my ROM? The norm was to Flash Cache, Davlik Cache, Data, and Factory restore on my EVO. Not sure how that works now that this phone does not have an SD card. Do we not wipe data when flashing ROMs on the nexus?
when you wipe the 'sdcard' partition remains untouched so dont worry
Thank you! Here I go!! This file im downloading from http://jenkinsmanifest.clockworkmod.com/device/toroplus shows it's only 137 mb. Are ROMS on the Nexus usually this small or is there something wrong with my Download?
That's AOSP ICS for ya. Gingerbread AOSP was even smaller.
Sent from my Galaxy Nexus using XDA
Need some quick help here. I unlocked and rooted my gnex. I have done this several times before and with all my other android phones. As soon as I rooted it, I flashed the new 4.2 gapps package. Upon booting, the launcher would not respond and thusly I could not access my home screen or app drawer. I had to open my apps from the google now target on the lock screen. As I read more, I heard not to flash the 4.2 gapps unless you have flashed another rom.
So I went to chrome, dl'ed the cm10 m2 zip, went into rom manager and flashed the cm10 and 4.2 gapps again. Now upon booting, the cyanogenmod icon is bootlooping, and has been for the last ten minutes. I went back into recovery and tried the process again, this time wiping the cache and dalvik, to no avail...same bootloop.
Please help!
Install a stock ROM using fastboot.....
Beamed from my Maguro.
If it helps at all, it's a Verizon galaxy nexus. Please help! Also if it is at all possible to save pictures, please let me know. Wiping would be my last resort.
Thanks
Mach3.2 said:
Install a stock ROM using fastboot.....
Beamed from my Maguro.
Click to expand...
Click to collapse
Is there a way of flashing stock that does not require a wipe?
Also I did make a nandroid of the stock rooted rom, but for some reason, after flashing that, the cyanogenmod logo stilled appeared at boot...
swimman2867 said:
If it helps at all, it's a Verizon galaxy nexus. Please help! Also if it is at all possible to save pictures, please let me know. Wiping would be my last resort.
Thanks
Click to expand...
Click to collapse
U need to wipe cache/dalvik/factory reset/system(u need to do this every time before flashing a ROM) , do it like 3 times and re-flash ROM. Don't worry about ur photos, they r in the internal memory and u don't need to wipe it, so u won't lose them.
Sent from my Galaxy Nexus using xda premium
Which file did you flash? You could've used the 'maguro' (GSM) one instead of the 'toro' (Verizon) one
pr0xyw0rm said:
U need to wipe cache/dalvik/factory reset/system(u need to do this every time before flashing a ROM) , do it like 3 times and re-flash ROM. Don't worry about ur photos, they r in the internal memory and u don't need to wipe it, so u won't lose them.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
When you factory reset, the entire phone is wiped, no? And how can I factory reset from recovery?
EddyOS said:
Which file did you flash? You could've used the 'maguro' (GSM) one instead of the 'toro' (Verizon) one
Click to expand...
Click to collapse
I was sure to flash the toro file. I don't believe that is the problem.
swimman2867 said:
When you factory reset, the entire phone is wiped, no? And how can I factory reset from recovery?
.
Click to expand...
Click to collapse
Nope. Factory Reset doesn't wipe the internal SD. It should be located inside the wiping options(I'm using TWRP recovery). Anyways u should wipe cache/dalvik/factory reset/system before flashing a ROM not just factory reset.
Sent from my Galaxy Nexus using xda premium
adb pull /sdcard in recovery
download stock image from Google and flash
https://developers.google.com/android/nexus/images
fastboot oem lock
Got home from class, wiped cahce, dalvik, and data, flashed cm10 m2 and gapps 4.2. Everythings great and I still have my pics. Thanks guys
It was just taking that plunge of wiping data that was freaking me out. I had some pics that i absolutely could not lose, but after reading on it more, it makes sense that the wipe would not format the internal sd.
Thanks again!
swimman2867 said:
Got home from class, wiped cahce, dalvik, and data, flashed cm10 m2 and gapps 4.2. Everythings great and I still have my pics. Thanks guys
It was just taking that plunge of wiping data that was freaking me out. I had some pics that i absolutely could not lose, but after reading on it more, it makes sense that the wipe would not format the internal sd.
Thanks again!
Click to expand...
Click to collapse
U r welcome. I'm glad to hear that.
Sent from my Galaxy Nexus using xda premium
Okay, so I bought the n7 v2, went home, unlocked the boot loader, and rooted it. I've tried to flash versions of vanir I built my self, the betas that are posted here on the forums, and I also tried carbon ROM. Every time I flash a ROM, my device bootloops, so I just hold power + vol down to get to boot loader mode so I can boot into recovery. Any fix for this? I've tried flashing a stock IMG and re rooting to. No luck.
Bump
frap129 said:
Bump
Click to expand...
Click to collapse
Did you even wipe, and perform a factory reset before flashing a ROM?
Sent from my Nexus 7 using xda app-developers app
TheMrcool212 said:
Did you even wipe, and perform a factory reset before flashing a ROM?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I wiped data, cache, and dalvik every single time.
Bump? Anyone?
try redownloading the rom and install, could of been a bad download
Sent from my Nexus 7 using xda app-developers app
shortyboy said:
try redownloading the rom and install, could of been a bad download
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
With four different ROMs, 2 transfered via adb and 2 from different download hosts, I doubt its a bad download.
frap129 said:
With four different ROMs, 2 transfered via adb and 2 from different download hosts, I doubt its a bad download.
Click to expand...
Click to collapse
you should've mentioned that in your original post. id try to reflash to complete stock and start all over. it seems like something you modified in the first rom you've flash isn't being removed from another flash,so going back to stock,you can be sure everything is working first.hope this helps
shortyboy said:
you should've mentioned that in your original post. id try to reflash to complete stock and start all over. it seems like something you modified in the first rom you've flash isn't being removed from another flash,so going back to stock,you can be sure everything is working first.hope this helps
Click to expand...
Click to collapse
I did mention that in the original post, as well as the fact that ive flashed stock a few times already.
Did you boot into the tablet after unlocking the bootloader but before rooting it? If not, try formatting data (not factory resetting) in recovery. I had the same experience and my sdcard never got populated with the default folders and files, remaining at 0MB. Apparently, symptoms of this problem include being unable to factory reset from recovery, being stuck on the splash screen, and having TWRP demand a password.
bananagranola said:
Did you boot into the tablet after unlocking the bootloader but before rooting it? If not, try formatting data (not factory resetting) in recovery. I had the same experience and my sdcard never got populated with the default folders and files, remaining at 0MB. Apparently, symptoms of this problem include being unable to factory reset from recovery, being stuck on the splash screen, and having TWRP demand a password.
Click to expand...
Click to collapse
I'll try that, maybe its because I restore my data after I wipe it that this happens. Another thing I've found is that after I flash and the restore my system partition that I backed up, su says that no subject binary was found, even though I've flashed it a million times. And some root apps don't work because it says no binary is found.