So I attempted to upgrade my girlfriend's Galaxy Nexus from 4.1.2 to 4.2.2 (this is on Verizon. Was using a Xenon HD version from last August and attempted to update to the newest version).
Well, since I'm an idiot, I didn't read up on the file system changes and now I can't figure out how to get everything working properly. I have the sdcard/0 now and haven't been able to move the files over from sdcard/0 to the sdcard.
All I want to do at this point is just restore a nandroid backup and start over from scratch. Any help would be greatly appreciated.... I'm also having driver issues, so if there's any way to do this without using ADB, that would help immensely.
Thanks in advance.
The SDcard/0 is supposed to exist. Take 10 minutes to do the tiniest bit of searching and all your problems will solve themselves.
can you boot into recovery? what do you mean you cant get things working properly
slimb9 said:
can you boot into recovery? what do you mean you cant get things working properly
Click to expand...
Click to collapse
Yeah I can get into recovery but when I try to restore nandroid it says there are no files, and I know there is a backup.
I did a half hour of searching, but thanks for the help. I must not be searching for the right thing....
so can the phone turn on? or can you only boot into recovery
slimb9 said:
so can the phone turn on? or can you only boot into recovery
Click to expand...
Click to collapse
Yeah I can turn it on. Gapps didn't install, though, so I don't have a keyboard and can't install goomanager from the play store to update recovery. I also can't move files in the file manager because it times out very time.
if you still have the old xenon rom .zip file on the phone you could just flash that after wiping/clearing everything. then from there boot into recovery and see if you can see your nandroid backup of the old xenon she was on. not sure if this will help but worth a try. looks like the new xenon rom required a full wipe so something may be messed up that you could fix by flashing an older version
Asterdroid said:
Well, since I'm an idiot, I didn't read up on the file system changes and now I can't figure out how to get everything working properly. I have the sdcard/0 now and haven't been able to move the files over from sdcard/0 to the sdcard.
Click to expand...
Click to collapse
063_XOBX said:
The SDcard/0 is supposed to exist. Take 10 minutes to do the tiniest bit of searching and all your problems will solve themselves.
Click to expand...
Click to collapse
As 063_XOBX said, sdcard/0 is supposed to exist. Considering your comment later in the thread about not being able to find old backups, it sounds like you have an outdated recovery that doesn't understand the new file structure. Update your recovery rather than screwing with Google's intended file structure.
Asterdroid said:
I'm also having driver issues, so if there's any way to do this without using ADB, that would help immensely.
Click to expand...
Click to collapse
What driver issues? You haven't been overly clear with the actual problems that you're having. You said you had a problem with Gapps. Why not download and flash a Gapps package?
i p.m. him without a response. im sure he figured out he was doing something wrong. it helps to read instructions
Related
Hey guys,
glad to say that ive been able to debrick my phone like 5 times in a row successfully which is a weight off my shoulders.
however, once im debricked, rooted, cwm installed, and all .img's pushed i try to flash a custom rom. i've tried every one and i get bootloops every time... they seem to install just fine. very normal timing and everything, no errors. any ideas?
Don't format /data. Are you doing that? Link the steps you're taking when you are in cwm to flash over the rom. Maybe something is amiss.
nope not formatting data. ive been doing wipe cache, wipe dalvik, and format /system.
Man I was in the same boat as you but was finally able to get it sorted this morning. What I highly, highly recommend is starting as fresh and as clean as you possibly can. That is before you do CWM or anything like that restore your phone with the Korean kdz, push all the images (system being last) then make sure you have a bootable, working phone. Also I would recommend using different/new/fresh .img files...I downloaded ones from the unbricking thread and only used a copy of my baseband.img. I had a feeling one of my files wasn't quite right so starting with all new ones may have helped.
Don't try anything from a backup or do a restore or anything-start fresh and make sure everything works as it should. From there do CWM and then do your ROMS. I know you're almost there and its a headache to keep starting from the bottom but do it all one step at a time, in order and you will find success.
Good luck!
good call. i havent been pushing all the .img's. just the three he mentioned above. let me try this for the 80th time. ill let you know how it goes. just curious, do you use the v10f or v10i kdz?
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
If i was you i would install the new CWM, once it installs the new CWM it'll work.
gte460z said:
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
Click to expand...
Click to collapse
yep i know that part. thanks
Revolution said:
If i was you i would install the new CWM, once it installs the new CWM it'll work.
Click to expand...
Click to collapse
new cwm?? as in the newest version available?does it work on the nitro?
[CWM][24/01] ClockworkMod 5 Recovery For LG Nitro HD
http://forum.xda-developers.com/forumdisplay.php?f=1448
Follow instruction's then try flashing a ROM it should fix your problem.
ive been using cwm... doesnt get rid of the bootloops
mic.mayorga said:
ive been using cwm... doesnt get rid of the bootloops
Click to expand...
Click to collapse
I'm not sure you understand bro, there is a NEW UPDATE
Update your CWM and it'll fix this issue.
I had the same problem for awhile. Had to use the Unbricker:http://forum.xda-developers.com/showthread.php?t=1412367
Followed ALL instructions, including "Restoring Nitro HD partition images" before flashing CWM. After that, no more bootloops and installed Revolutions rom w/out issue. Reboots just fine after.
I used the V10i-the direct download from LG...I think all the other recommendations are spot on but first and foremost get everything squared away with a fresh install of the kdz, all the images (in the proper order), the new version of CWM and then your rom of choice...Hope you're making some progress!
I'm on the new CWM and still have a loop if I reboot. Then I need to restore from CWM to get going again.
The soft brick boot loop I got was caused solely by format /system. I did not format /data.
I went through the whole deal last night and this morning and was able to get a fresh start on everything and am now running the HD ROM and haven't had a boot loop since I got everything back up and running...
I really think starting with the freshest install and making sure everything is functional step by step is where you'll be able to get through all that mess...just stay away from and restores or using any .img files that may have any software glitches as you'll get back to square one every time.
Hope you get it sorted out!
nah bro, i had the new update. no worries tho i pushed all the images in the debrick and fixed it. thanks for all the help guys B)
Tight work-glad you were able to get it straight! Now once you get it where you want make a new backup with Nandroid and CWM and you'll be golden in case anything else happens.
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
huydq5000 said:
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
Click to expand...
Click to collapse
Go look at the thread "[Solved] Unbricking solution...". Follow it to the T, however, i'd recommend using v10i.kdz rather than v10f.kdz. Definitely try the f version first but if it doesn't work try i. That's what I did. Basically what you're going to want to do is:
1. Restore the phone to a korean image using the v10i (or f) file and the LG software provided and referenced in the unblocking thread.
2. Once booted, root the phone. (specific instructions for v10i are in a thread somewhere linked by [email protected] v10f use either SuperOneClick root or DoomLord v4. Make sure you have adb installed for doomlord.
3. Once rooted use adb to push over stock .img files in this order: boot, recovery, firmware, baseband, system.
4. after the files are pushed boot into phone and root again (optional).
5. Install CWM5 through adb or terminal emulator.
Good luck, let me know if you have any questions and I can go into more detail.
Here is a stock rom backup for the Sprint G S III. I made the backup after doing a data wipe, so the rom is pure, no lingering data, ect.
Instructions:
-unzip the .zip file
-move the backup folder into your existing CWM folder on the S III internal memory
-restore in recovery
Again, this is a stock backup as some people need it.
https://dl.dropbox.com/u/19699565/fresh_GSIII_backup.zip
From my dropbox, so hit it easy.
Nice, know of some that will appreciate this.
bizdady said:
Nice, know of some that will appreciate this.
Click to expand...
Click to collapse
Me too
Sent from my SPH-D700 using XDA Premium App
<3
Warning: if you flash this make sure you clear Google wallets data as shown in a qbking77 video so you don't brick the secure element
Sent from my SPH-L710
How is this in any way a stock rom?
nabbed said:
How is this in any way a stock rom?
Click to expand...
Click to collapse
Give him a break. At least this isn't in development.
And he at least did something that could be useful until we get a real stock rom .zip or .tar
~E.R.A.
nabbed said:
How is this in any way a stock rom?
Click to expand...
Click to collapse
You have been in every thread criticizing everyone else s contributions...what the hell have you contributed?
nabbed said:
How is this in any way a stock rom?
Click to expand...
Click to collapse
It's not, it's a backup. That's not the point, it's still useful to many users that have possibly screwed their device but still have access to recovery. Especially until something official comes out.
will there be a stock package on odin different than just the stock boot image? my phone is bricked for no apparent reason(see my thread here http://forum.xda-developers.com/showthread.php?t=1731416) and flashing the stock boot image in odin does nothing. i Also cant get into CWM to flash my backup...
pizzlewizzle said:
will there be a stock package on odin different than just the stock boot image? my phone is bricked for no apparent reason(see my thread here http://forum.xda-developers.com/showthread.php?t=1731416) and flashing the stock boot image in odin does nothing. i Also cant get into CWM to flash my backup...
Click to expand...
Click to collapse
Eventually there will be, but a lot of people [to include major developers] still don't have the phone yet, so we'll have to be patient. I looked over it, though currently are you able to get into recovery still or no? Additionally did you try re-flashing the cwm recovery in odin?
I can get into download mode but not into CWMR. The only thing i have tried flashing since it bricked is boot-stock-sprint-sph-l710.tar (which sort of worked the first time). I'm at work and don't have my phone on me so i guess i could try flashing CWMR again later but this is really weird. Thanks for the reply. This is my first Sprint phone, but on my Droid X we had a program similar to Odin where you could push a .sbf file that included everything stock and basically just reset your phone to stock. Do these exist for Sprint phones? The . SBF files were usually rather large(around 350mb or so) but the boot-stock-sprint-sph-l710.tar is around 10 or 15 mb so i know it doesn't include all the system files...
Thanks again
teh roxxorz said:
Eventually there will be, but a lot of people [to include major developers] still don't have the phone yet, so we'll have to be patient. I looked over it, though currently are you able to get into recovery still or no? Additionally did you try re-flashing the cwm recovery in odin?
Click to expand...
Click to collapse
Lol i just replied the same thing over on another thread he posted in. Stop jumping around pizzle! if you can get into Odin chances are good you can flash cwm and then restore the backup
hahaha sorry about that. When I try and boot into recovery it looks like its about to go to Recovery and then freezes on the Galaxy S III screen. I'll try reflashing CWMR when I get home...Thanks for the advice
So is a back up a nandriod?
I have made a few but never resorted one, you just flash it same as a ROM and your done?
I misplaced my stock nandroid when I flashed CM10 build 2 and my extFs SD card had to be formatted to use again, I was sure I had in on PC but can't find it.
Thanks!
My vzw nexus has been running mRom version x.x for sometime. I went to install the upgraded 4.2 rom via clockworkmod, (wipe cache and dalvik, flash over current rom) and it appeared to install successfully. However, when I rebooted I saw the lock screen for a split second and it just started to boot loop. I rebooted back into recovery and wiped all data and tried to reinstall the rom via through the new 0 partition, but I get the error symlink: some symlinks failed
E: Error in /sdcard/0/mRom_v3.0_JOP40C.zip (status 7)
I think that this may have something to do with the multiple users in 4.2, but don't quote me on it. I cannot get my computer to recognize my phone, when I go to mounts in cwm I can mount everything except the sdcard, although I think this problem was evident before I flashed. Any suggestions? I could try to restore to stock using galaxynexusrestore-- http://forum.xda-developers.com/showthread.php?t=1743939 but I have not tried it before so I cannot speak to weither it will work or not.
HELP!
Always always wipe data when changing an Android version. Unless it comes via OTA, which is specifically designed to fix all the little problems that will arise.
As to how to fix the problem, flashing a factory image
http://forum.xda-developers.com/showthread.php?t=1626895 will probably work. Just follow the rules for Toro. The toolkit you linked may work, but it's generally a better idea to not use them and actually familiarize yourself with how to fix things yourself, you'll be less likely to make mistakes in the future.
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Misread OP.
ironerd said:
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Click to expand...
Click to collapse
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
same problem, stuck at JB logo
Marisa said:
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
Click to expand...
Click to collapse
I was running stock JRO03O with Clockwork Recovery Mod and decided to flash the JB 4.2 ROM from Grouper (http://forum.xda-developers.com/showthread.php?t=1993545 - I can't post there since I'm too new).
The update must have succeeded, because I can see the new 0/ partition on my phone, but it won't boot past the "X" logo. I can boot into CWM and try various things, but of course because of the data structure changes, I can't actually recover to my last save. When I'm home, I'm hoping I can get the CWM backup off my phone to restore later, but without a terminal in CWM, I can't try to fix the path.
It's nice to hear that CW is working on a fix - I hope it's retroactive (I mean, helpful to those of use who already screwed up). Also, I've never flashed anything but OTA, so I didn't realize I needed to wipe data before flashing something that's supposed to be almost stock. I guess it matters how different from stock the ROM actually is.
What's next? I'll try to interface with my PC at home. If others have this problem, I'd be happy to hear your success (or fail) stories. I'll share mine once I've tried it.
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Koush
When trying to restore CWM backup move previous backups AND blobs folder to /data/media/clockworkmod if the folder does not exist simply create one or if unsure just go to recovery and make new backup, it will create necessary folders for you then move (or copy to be safe) files to location.... The blobs folder is what I was missing and why I kept getting error while trying to restore.
Click to expand...
Click to collapse
This should help your problem solving for the moment, if you're familiar enough with ADB to move the files that way it shouldn't take very long at all
thanks, and update of my status
Marisa said:
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Click to expand...
Click to collapse
Thanks for the extra insight. I wrestled with my phone all night and finally got it back to 4.1.1 (JRO030). Along the way I screwed up my adb or fastboot drivers, and for all my efforts I couldn't get any of my nexus toolkits to recognize the phone as in fastboot mode. Adb was fine, but fastboot was a no-go. I moved to a fresh computer after someone else had success with that, and read up on how to do a manual (adb command line) flash to factory image.
Now that that's done, I'm hoping I can restore from CWM to get back to where I was. If not, then yuck, but I'm optimistic.
I flashed the latest CWM so I should not get the sdcard/0 anymore after wipes and after flashing new ROMs, but I still need to get rids of the sdcard/0 in my current ROM, besides moving everything to the root of the sdcard, is there a way to fix this issue?
Moving everything to the root of the sdcard takes forever, and I don't know if its my computer or just that MTP sucks but I ratehr not do it that way.
THANKS
You don't need to get rid of it. It's supposed to be there.
063_XOBX said:
You don't need to get rid of it. It's supposed to be there.
Click to expand...
Click to collapse
Wait what??? seriously? I thought it was a bug having an older version of a recovery and flashing a 4.2 ROM. Or is the bug when there are multiple sdcard/0 folders.
Well in any case its still a bother because my backups are in the wrong pathway.
If there are endless or multiple /0 it's a bug. Otherwise it's the admin for multiuser.
So I tried installing a status bar icon replacement on Cyanogenmod and ended up getting stuck on boot loop somehow...
I went into recovery and wiped data, wiped my cache and dalvik cache and it's still stuck on boot loop...
help?
reflash rom
the rom isn't on the root of my device anymore and I can't exactly set it there without it turning on.
Causes a slight issue I imagine?
Aerolith514 said:
the rom isn't on the root of my device anymore and I can't exactly set it there without it turning on.
Causes a slight issue I imagine?
Click to expand...
Click to collapse
it doesnt have to be on the root of your device, as long as its in your storage. if its in the storage, find that location amd flash it. now what do you mean you cant exactly set it there without it turning on? you lost me there.
The rom isn't on my phone whatsoever.
I meant I need to be able to have the phone fully turned on in order to move the zip over to it.
Aerolith514 said:
The rom isn't on my phone whatsoever.
I meant I need to be able to have the phone fully turned on in order to move the zip over to it.
Click to expand...
Click to collapse
what recovery are you using? twrp has an adb sideload option, cwm might have something similar.
Just push another nightly zip over with adb, while in recovery. Simple! Don't understand what the fuss is all about.
Sent from my i9250
Using cwm.
adb? Sorry I've never bricked my device before, I have no idea what that is XD
Aerolith514 said:
Using cwm.
adb? Sorry I've never bricked my device before, I have no idea what that is XD
Click to expand...
Click to collapse
if u made a backup for ur stock rom, then restore it.
if not, the easiest way is to reflash factory image using fastboot mode. or see my thread in signature
Pardon my noobishness, but I really would rather not unroot my phone and set it back to stock 4.1.1 unless it's my only option.
Either way, I created a backup last night but it doesn't work. When I tell it to install it says "no file found".
At this point, I'm willing to let somebody take over via viewfinder if it'll help >_>
Flash new custom rom
And every modification SYSTEMUI.apk make sure permision each others
Aerolith514 said:
Pardon my noobishness, but I really would rather not unroot my phone and set it back to stock 4.1.1 unless it's my only option.
Either way, I created a backup last night but it doesn't work. When I tell it to install it says "no file found".
At this point, I'm willing to let somebody take over via viewfinder if it'll help >_>
Click to expand...
Click to collapse
so flash google image 4.2.1 using fastboot http://forum.xda-developers.com/showthread.php?t=1626895.
If u flash 4.1.1 i think u will receive update before rooting.
any way what cwm u are using??
Sigh...crisis averted.
I dug deep into my files (which are a friggen mess) and found a the December 21st nightly laying around somewhere odd. Everything's back to working order -- Just gotta set everything up again >_>
Although, it seems like i have nothing on my screen...
Nothing whatsoever
Aerolith514 said:
Using cwm.
adb? Sorry I've never bricked my device before, I have no idea what that is XD
Click to expand...
Click to collapse
that's the attitude that... nevermind.
http://forum.xda-developers.com/showthread.php?t=1812959
this is the thread you should have read BEFORE "bricking" your device. Which you didn't by the way. You don't want to know what a REAL brick is. Don't use the word lightly.
Sigh, one last question I guess -- even though I've asked a ton.
Now that I've flashed CM and my gapps, everything on the phone works except it shows that I have no installed apps...my messaging app, app tab..phone... nothing is there...
Aerolith514 said:
Sigh, one last question I guess -- even though I've asked a ton.
Now that I've flashed CM and my gapps, everything on the phone works except it shows that I have no installed apps...my messaging app, app tab..phone... nothing is there...
Click to expand...
Click to collapse
did you flash the right gapps?
gapps 20121212
Unless there's a newer one now?
Aerolith514 said:
gapps 20121212
Unless there's a newer one now?
Click to expand...
Click to collapse
in latest cm 10.1 there is a lot of bugs no icon for drawer, no long press on desktop, flash the previous one
Aerolith514 said:
gapps 20121212
Unless there's a newer one now?
Click to expand...
Click to collapse
that version is working fine here under custom aosp, so it must be cm problem like previous poster said.