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!
Related
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.
Hi all.
I'll start by saying I have gotten in way over my head. I rooted my Evo with unrEVOked's one-click method, and then began to experience some problems with my 3g. Thinking I had somehow botched the rooting process, I tried to unroot using the two-step method I also found on xda (cannot post link.. further proof I am a noob ). More problems sprang up, one thing led to another, various fixes were tried (HUGE thanks to everyone in the IRC channel last night that tried to help my sorry ass..) but to no avail.
Here is where my phone is at now: booting using vol down+power shows me S-ON. Trying to flash mtd-eng.zip results in an error, so I am seemingly stuck with S-ON. Normally I would be happy about this (that's one step closer to unrooted, right?) but I notice I still have Superuser in my apps. My 3g is working again for whatever reason (no complaints here! maybe it was a Sprint-side problem in my area.. what timing!) but I'm confused as to whether my phone is rooted or not.
Ideally, I would like to go back to unrooted, since I have made it abundantly clear to myself that I am not yet prepared to embark in rooting. If anyone could guide me in the right direction, I would be very thankful.
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Jim M said:
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Click to expand...
Click to collapse
I did this, and my phone is now in RA-evo-v1.8.0 (it rebooted into recovery). Should I reboot the system now? I find it strange that it took me here in the first place.
The current PC36IMG that is flashed to the Evo is one with Amon Ra built into it.
The only RUU program that I am allowed to run (from the list that was given out in one of the unrooting evo threads) gives me the 170 error before anything happens.
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Jim M said:
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Click to expand...
Click to collapse
With a little digging and poking and reading, I found the proper RUU, ran it, and I believe I am now back to fully unrooted. Thank you very much for your help!
Got the OTA today. Bog stock not rooted. update failed. After about 30 minutes a retry download button appeared. Pushing it doesn't do anything. Is there a minimum wait between update attempts? Any other ideas?
Same thing happened to me. I have waited 3 days for a repeat but to no avail. I rooted it and installed a custom ROM with the volume fix update in.
http://twitpic.com/7oody4 this?
Mine failed too... mine was just rooted; nothing else
I got the little Android logo with a !
Rebooted again, no update appears; so I decided to just put the update myself.
Twitpik link is broke. Didn't fail during reboot though. Error msg is right in the system update page. The dowload progress bar is grayed out and it says dowload failed instead a percent progress and there is Retry Download button lower right but it doesnt seem to do anything.
texiandave said:
Twitpik link is broke. Didn't fail during reboot though. Error msg is right in the system update page. The dowload progress bar is grayed out and it says dowload failed instead a percent progress and there is Retry Download button lower right but it doesnt seem to do anything.
Click to expand...
Click to collapse
Mine downloaded automatically over night, and asked if I wanted to apply it when I woke up at 6am. Twitpic should work btw, I just looked at it
Mine even said it was downloaded AND verified, but still failed
Rooted on stock rom with CWM.... Without the stock recovery it can't install. Just jumped to a new Rom with the update....I have always hated the auto updates..lol
Is there a way for me to apply this update by itself? Even if I don't have stock recovery? Is it possible to re-set recovery to original without wiping the entire device?
Mine is rooted, stock ROM, CWM recovery.
OTA re-set itself and installed correctly overnight without me doing anything. Not sure why it failed or how it resolved it but it's done.
If you're still having issues try this
http://www.coolsmartphone.com/2011/12/01/galaxy-nexus-ota-patch
Basically its links to the patch (OTA) and how to root/return to stock with a link to the guide on xda
Sent from my Galaxy Nexus using Tapatalk
I eventually received the update. It downloaded and asked for a reboot. I agreed and the phone counted down, then shutdown, but didn't startup. I waited and waited, the power button would not respond, so I removed the battery, and put it back in. It then started up, but still on the old ITL41D software. What did I do wrong? And what do I do now? Is it normal for it to fail to start up aftrr the reboot? Will I get another opportunity?
Sorry for all the questions, but I'm super frustrated
mirilo said:
I eventually received the update. It downloaded and asked for a reboot. I agreed and the phone counted down, then shutdown, but didn't startup. I waited and waited, the power button would not respond, so I removed the battery, and put it back in. It then started up, but still on the old ITL41D software. What did I do wrong? And what do I do now? Is it normal for it to fail to start up aftrr the reboot? Will I get another opportunity?
Sorry for all the questions, but I'm super frustrated
Click to expand...
Click to collapse
Is your phone rooted? If so, I would look at the comment above yours with the link to the patch (and instructions) to flash it manually. If it is not, it will likely allow you to retry in a day or two.
Hope it all works out for you.
EDIT: I just tried flashing the patch manually as per the prior instructions posted and it didn't work. It gave me "Error (Status 7)" and aborted the installation. Although, right when it rebooted back into the home screen, it came up with the official OTA update again. I'm hesitant on trying it again, since it's likely to fail due to whatever reason caused it to fail the first time.
Either way, this is getting aggravating. I really wish there was an easier way to get this patch without needing to lose root and having to re-do things all over again. I have done a TiBu batch run of all of the stuff I need, but still...oh well.
FlareHeart said:
Either way, this is getting aggravating. I really wish there was an easier way to get this patch without needing to lose root and having to re-do things all over again. I have done a TiBu batch run of all of the stuff I need, but still...oh well.
Click to expand...
Click to collapse
Don't think I've ever seen an OTA which left root intact. This occurs when the OTA sets the permissions recursive for the whole directory /system/bin to 755 removing the setuid attribute on the /system/bin/su binary.
The binary will still be there, but will have to have the setuid attribute added back, chdmod 4755, which will then return root.
Does seem odd Google allows the device to be unlocked, but yet unlocked devices get root access wiped. If they claim to want open source and open devices, perhaps they could script an exception for root access and not remove it with every OTA.
Normally, when Error status 7, or any other recovery error, we're in a custom recovery with adb access and can pull the log at /tmp/recovery.log or /cache/recovery.log and examine what caused the issue as more output is stored there than presented on the screen to the user.
Perhaps googling this recovery error code or grabbing the open source from AOSP will show generally what causes it.
Does seem odd the issues other users have had *automatically* cleared themselves after waiting a while.
First idea which comes to mind is perhaps the original OTA had a bug in the scripting and they were slowly replacing and pushing out the updated OTA.
Keep us updated! I'm on the samsung version of ics so I'll probably have to manually push over all the images...but good to keep up with the *official* route.
When trying to install my update, I get signature verification failed in recovery.
Any ideas?
EDIT: Flashed the recovery posted in the Image on Googles site.
Fixed the problem for me.
joeykrim said:
Keep us updated! I'm on the samsung version of ics so I'll probably have to manually push over all the images...but good to keep up with the *official* route.
Click to expand...
Click to collapse
Not technically official, but a MUCH easier way to get the patch and keep all of your settings and root can be done using the slightly modified stock ROM from bigxie (link: http://forum.xda-developers.com/showthread.php?t=1372376)
If you clear just the cache and dalvik, then flash this. You get the patch, SU, and busybox, without losing all of your settings or data.
Worked great for me. Hope that helps!
Hi guys,
I have a problem upgrading my nexus to the latest 4.1.2 update.
My device found an update, downloaded it and rebooted to CWR.
It's starting to install and then I get error status 7. Installation failed.
I also tried to donload the update manually but same results.
My devices is rooted with an open bootloader.
TAKJU.
I've tried to seach the forum/stickies but couldn't find a solution.
can anyone please advise?
Thanks in advanced,
Do you have modified system files? Like did you modify your build.prop?
Having the su and superuser.apk does not matter, OTA will still go through.
Most likely because OP altered something within the /system/ or is using another radio other than the one supplied from OTA.
This is why I always say if you're going to root, don't "half-a.." it. Go for the whole thing. Rooting is a gateway drug to flashing
I did not modify system files etc..at least not on purpose..
zephiK - I'm not sure what you meant there. I don't remember how I rooted, but do you think the root was corrupted?
Can you help me fix this somehow?
I don't care to wipe if needed.
thanks!
Got the same situation as you, the update won't proceed as it can't pass the check to ensure the rom in your Nexus is the one valid for update. Search the thread and web, and the message that follow the error 7 code hint you what's the thing that's not match.
You scenario should not be the same as mine since everyone of us mess with our own Nexus in our liking. But I'll share my case to see if it get's you some insight.
First OTA and manual flash won't work, stop almost immediately as shown by the CWM progress bar. I saw the screen said something about system/calculator - Then I remember that I have use TB to backup and uninstall the stock calculator, image, and email.
Restore those 3 using TB, and try again.
This time, the progress bar moves, and it actually check and stop halfway in between before showing the Status 7 msg.
Then do some web search, someone said about the radio version, and I got bad battery drain anyway, so flashed the radio version, restart and reflash again.
This time progress a little bit longer, and still no dice. Status 7 msg says something about system/build.prop
Check my system folder on the Nexus, and find build.prop.bak, then remember I have messed around with build.prop before, trying to change the device name shown on the DHCP table on wifi routers.
Revert the change. Try flash again, and viola, it work. And now got my 4.1.2 running nice and smooth.
So pay an attention at what the string said in the status 7 msg, and you know why it won't start the update.
Hey, you mentioned you have a unlocked bootloader.
If you still can boot into android, download TitaniumBackup and backup all user apps and data, then pull the TitaniumBackup folder to your computer.
Then use fastboot to flash 4.1.2 image from Google.
Then finally use Titanium Backup to restore your stuff.
28907126 - Thanks for the info! It might help to others. I really didn't play with radio or system files.
Mach3.2 - Can you please direct me to a guide on how to flash the image?
Thanks for the help everyone.
naorca said:
Mach3.2 - Can you please direct me to a guide on how to flash the image?
Click to expand...
Click to collapse
There's a sticky at the top of this forum.
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