[Q] Error while restoring /system - CWM problem - Samsung Galaxy Nexus

To begin, let me assure you I've read through every forum post I can find regarding this issue and none seem related, or are too old to apply at this time. If I am mistaken I apologize and would appreciate someone pointing me in the correct direction.
I upgraded to 4.2.1 (Shiny). I have some issues so I want to restore my CWM backup of CM10. Since I upgraded and apparently did CWM as well, it is not letting me restore the old backup, giving me the "error while restoring /system" message.
It appears from researching here that the solution is to downgrade CWM, but I am unable to find a download site to get older versions of CWM anywhere. All links that have been posted here are no longer valid ("Forbidden 403"). Any ideas would really be appreciated.
Another possible cause is I updated the bootloader when I went to 4.2.1, is it possible that is causing the problem? If so, which bootloader should I replace it with?
Any help would be appreciated. Thank you very much.

Related

Stuck in fastboot after downgrade to 2.1 from stock 2.2

I've customized gadgets and electronics before but phones are rather new to me but I'm a very technical person that makes dumb mistakes apparently. Now I seek someone more experienced to put me on the right path.
I'm unable to post links however I followed the directions floating around
directions and now I'm not stuck in the hboot 0.77/fastboot every time it starts. I know my phones not bricked but it's in a very annoying state. I tried a hard reset but this changed nothing.
Currently it's at S-ON and radio 1.00.03 so it seems that downgraded fine. It did get though the whole process fine without error only 2.1 didn't boot up.
I was attempting to do a downgrade so I could root. I had nothing special on the phone so I didn't bother with a backup (besides my sdcard.)
When I run bootloader it tells me "No Images" and "No image or wrong image!" PB31IMG.zip I assume this may have something to do with my problem and I think it's a permissions issue because I didn't re-set them when I backed up my files to format to fat32.
I think this is my problem because I know the files would have lost permissions when I copied. I haven't tried to update again because I assume it will have the same result (that and I've read nasty stories about re-flashing the same version, not that this would do that). I'm unsure on how to get to a shell with the phone in this state or if there is some other way to get it running again. I tried clearing everything and did a hard reset with no luck.
Any help would be much appreciated.
-Blake
Ok I got it working by doing a reinstall. Not sure why it didn't work the first time.
blakeem said:
Ok I got it working by doing a reinstall. Not sure why it didn't work the first time.
Click to expand...
Click to collapse
Reinstall of what? I get the same errors when trying to get any PB31IMG.zip file to load.
dj-anakin said:
Reinstall of what? I get the same errors when trying to get any PB31IMG.zip file to load.
Click to expand...
Click to collapse
I just reinstalled the .zip
What errors?
Ah.
Here's my new thread on my problem.. http://forum.xda-developers.com/showthread.php?t=783123 Been working on it since last night.

status 7 and logwrapper help?

i believe i need to unroot my defy. as i get the status 7 error and logwrapper error. can anyone help me solve this?
If you haven't already figured it out.... The logwrapper error is all too common and can easily be fixed. It is due the the fact that you have clockwork recovery installed. One fix is to delete the file logwrapper, NOT LOGWRAPPER.BIN, next step is to RENAME LOGWRAPPER.BIN TO LOGWRAPPER. Re run update and PRESTO!
DO NOT UNDER ANY CIRCUMSTANCES JUST DELETE LOGWRAPPER, YOU WILL BOOTLOOP AND BE STUCK FLASHING A SBF AND JUMPING THRU SOME HOOOPS!
Or simply use clockwork recovery and apply Beach_Head's edited update that he has so kindly posted on these forums.... Trust me it works. But only if you are coming from 3.6.360 otherwise you should try one of the alternative methods posted by Beach_Head.
Or you do the Nandroid method, if not already on 2.2 rom then you need to flash a 2.2 boot only sbf after nandroid restore
Just wanted to thank you and Runeblade for posting this and figuring out how to make the update work.I tried to uninstall CWM to no avail. The logwrapper was still the issue. So now i have to reinstall it and the whole deal. But at least I didn't have to spend my whole night figuring it out. Only part of it. So thanks again and keep it up. The "not so great at this but just good enough to mess it up" folks like me need all the help we can get. And a sticky with instruction may help all those who are about to have issues with this when Moto releases it to the masses. I had to fumble around figuring where to look for the .bin files. Might be a good idea for someone to post a guide about how to change the file name, verbatim, and what to use to do so. Would help so folks that are not so daring or trusting and mayhaps cut down on clutter on here. Just a thought.
wow it worked !
i got mine working, i re-rooted my phone again so i could delete "logwrapper" under \system\bin using root explorer app
and after deleting logwrapper i renamed logwrapper.bin to logwrapper. i un-rooted my phone again.
(some say that you can also delete: su busybox hijack, but i didn't saw them)
downloaded the update again and it'll ask you to reboot to update , viola it worked!
----------------------------------------------------------------------------
NOTE: this solved my logwrapper and status 7 error message
i don't know if it'll work on other error messages as well , try at your own risk!
----------------------------------------------------------------------------
maybe these files were leftovers when i un-installed clockwork recovery and super one click, after a day of reading forums i finally got me an updated phone!
welcome FROYO!

App Request (AT&T Software Update .apk)

So I'm not sure what's going on, but when trying to click "software update" in ny about phone settings, nothing happens. I'm not taken to a new screen or given a force close/failed attempt message. It's almost just there for show.
After hours of scavenging the internet for answers, I'm starting to think I might have accidentally deleted it with Titanium Backup by mistake not knowing it's importance. I've download many "stock" roms hoping to extract the apk from there but none seem to contain it.
I'm not an amateur to this and am completely aggravated by my dead end situation which has abandoned me with no option other than to plead for help via post. If anything could alleviate my situation and either provide the apk or a solution to my problem, I would be forever grateful.
FYI: I'm running out-of-box software with root and CWM recovery. I have stumbled upon the "apply 4.1.2 update manually" thread but the no wipe process requires a stock recovery as to allow /cache flashing (thus not forcing a wipe) and I'm hesitant to backtrack out of CWM.
Thank you for any help in advance.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
unlocatedfile said:
So I'm not sure what's going on, but when trying to click "software update" in ny about phone settings, nothing happens. I'm not taken to a new screen or given a force close/failed attempt message. It's almost just there for show.
After hours of scavenging the internet for answers, I'm starting to think I might have accidentally deleted it with Titanium Backup by mistake not knowing it's importance. I've download many "stock" roms hoping to extract the apk from there but none seem to contain it.
I'm not an amateur to this and am completely aggravated by my dead end situation which has abandoned me with no option other than to plead for help via post. If anything could alleviate my situation and either provide the apk or a solution to my problem, I would be forever grateful.
FYI: I'm running out-of-box software with root and CWM recovery. I have stumbled upon the "apply 4.1.2 update manually" thread but the no wipe process requires a stock recovery as to allow /cache flashing (thus not forcing a wipe) and I'm hesitant to backtrack out of CWM.
Thank you for any help in advance.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
I believe the expression is "you can't have your cake and eat it too" my friend.You can't get software updates the old fashioned way now even if you have the apk.The OTA checks your phone before it will push an update,if anything is out of place it won't push.If you were rooted only,you could probably still get the OTA but as you already said you have manipulated the file system and you have CWM .You will have to do updates thru zips or flash one of the awsome stock rooted updated roms.There are some roms with the newest updates close to stock or just plain stock rooted,I would try one of those bro,it might be easier,that way you can keep root and custom recovery always without having to go back and fourth.I think it is better that way anyway unless you have to send in the phone for warranty service.
Try this

[Q] Nano backup retore problems

I have the sigh-i747 withe the debloated factory 4.3 rom found on another thread here. However this seems to apply to both cwm recovery and twrp. When I restore a backup it boots to the AT&T screen and stays there. I've tried everything I can think of and no luck. Needless to say after four or five manual restores I'm hesitant to try anything else. I've googled it extensively and only found the problem mentioned once and no answers, lol. Any help would be appreciated.
Thanx

Sprint galaxy s3 e:failed to mount /es (invalid argument)

Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
timbow4 said:
Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
Click to expand...
Click to collapse
Odin will flash the factory firmware for you. Get firmware from sammobile. Look for sph L710 device, and firmware with NJ2 in the name. Put phone in download mode, (power off then hold power+home+volume down) plug in phone to pc. Wait till Odin says added. Click AP in odin, select firmware you downloaded, click start. When it's done, unplug phone, remove battery, put it back in and reboot.
This may not fix your efs partition, but it's the first thing to try.
Odin
I found the thread for nj2 firmware here
issue still persists
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
timbow4 said:
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
Click to expand...
Click to collapse
Sorry, I never had that issue. Maybe someone else will chime in with experience on the efs partition. That's not a triband s3 is it? (Sph l710t?) T at the end means triband. Second thought, I don't think the firmware would have flashed if it was triband.
How did you wipe your efs?
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
timbow4 said:
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
Click to expand...
Click to collapse
Backing up and restoring it won't help. You already installed a new operating system ( that's what the firmware is).the efs is part of your radios. If I remember correctly it contains your imei and other important things specific to your phone.
You may be out of luck there dude. Don't know how you wiped your efs.
Rooting this phone is simple. Just flash TWRP with Odin. Download the Twrp image from their site. Same as flashing the firmware, only you select recovery instead of AP in odin and select the Twrp image.tar instead of the firmware tar.
https://dl.twrp.me/d2spr/
Use the top on the page. (Newest)
And then use twrp to flash either SuperSU, or Magisk.
Done.
Flashing a custom rom will not fix your issue. You need a working efs. Flashing any operating system will not fix it (you already flashed the whole operating system).
Twrp can restore an efs, but only if you have a working one to backup first. You were right about backing up yours now and restoring will do nothing.
Has it ever been activated?
Prior to this, every once in awhile when i changed a battery out and turned the phone on it would have a pop-up screen tell me something was bad and the phone needed to be reset (something along those lines) and i always just turned the phone back off and on and it booted up fine each time. That may have been an indicator that something, file or system file maybe was corrupted. Then a few week ago when it booted up it started doing this whole thing. Prior to me factory restoring the phone here recently it was completely functional but since the restoration it will no longer connect me to the network. If you goto settings and click on some system features it will turn the network on for that specific function (temporarily) but does not give me any other access. It tells me that the network works but it being blocked (maybe because of the factory mode issue). The wifi works and i can make and receive calls. Still manageable but very annoying. Im going to try your instructions with installing TWRP. If i am successful then maybe i can also get into the system files and possibly restore the broken one.. Thanks again
update
So I have successfully rooted the phone by intstalling TWRP ver 3.2.1 and using TWRP to flash SuperSU ver 2.82. I also installed root explorer to get access to system files. I gained access to the EFS folder and it is empty. So now I'm not understanding if the folder is completely empty how does the phone still work at all? More research led me to a XDA developer that put together a program called EFS Professional which is supposed to backup and restore efs or imei data. Really slick program, basically takes the complication out of locating and backing up the EFS information yourself. (I would include a link but I still cant..) It includes an ADB shell and the ability to make some changes to the phone including directly turning off factory mode . It also had me install an application called BusyBox Pro which is also a very handy tool for getting access to system files. What I don't understand is that the EFS Professional program seems to locate the efs information on my phone and backups it up and then restores it from said backup however when I look at the efs folder its empty. Perhaps not all the efs information is located in the efs folder. And of course since that folder is empty the function of turning factory mode off fails because it cant find the files. I have found a few threads that has very simple instructions once you have super user access you can go right into the efs folder to factory mode and simply turn it off. Mine is empty.. So again the problem continues. Possibly with access to the ADB shell and more help from folks on here I can figure out a way to restore my efs information. I don't know if the efs information can be used from a another same model phone, I'm guessing not if it has a specific imei identification. Im working hard on this but still unsolved. I know way more at this point then I did but I think I still know just enough to be dangerous. Thankfully my phone is still functional at this point..

Categories

Resources