Related
i lost my root i have the state unlock boht no root i tray to get root and nothing i tray do evaryting from 0 and still what happen i used ubuntu
Try flashing the stock nandroid zip and start the whole rooting process over that's in the guide
Sent from my Nexus S using XDA App
tsalate said:
Try flashing the stock nandroid zip and start the whole rooting process over that's in the guide
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That will wipe all the data off your phone, of course. Make sure you have a backup of your apps and data.
I don't really understand what state your phone is in. If you haven't done anything like re-do the oem unlock, you should just be able to flash/boot to Clockwork Recovery and then flash the superuser zip again. Try this method.
That happened to me too when i updated to 2.3.2. What I did is use the superboot for 2.3.2. Its in the android development section. Just look for it.
Sent from my Nexus S using XDA App
This will work without a pc only if you are on ec05 modem, if not get your ass there
So since I'm in the process of moving without my desktop and have no acess to a pc. I updated to gb fairly easily with cwm and root.
This can be done with any rom.
if you mess up and let it boot at the 2 points I tell you not to, then you can get stuck with stock GB without root or cwm.
You will have the modem on the bright side!
I stated off with RandomRom, but you can be on any as long as you have the ec05 modem.
1. Download what you are goingto need,(the acs cwm is your choice.) Thanks to thoes who orginaly posted these files.
1a. the stock ec05 rom with the green cwm 3.1.0.1 found here: http://forum.xda-developers.com/showthread.php?t=1027904
1b. EXTtoRFS found here: http://dl.dropbox.com/u/9992367/gotorfs.zip
1c. The ec05 to ei22 update zip found here: http://android.clients.google.com/p...a5ff039a0c97.SPH-D700_update_EC05_to_EI22.zip
1d. Su.zip found here: http://downloads.androidsu.com/superuser/su-3.0-efgh-signed.zip
1e. Acs cwm (optional) found here: http://chris41g.devphone.org/index.php?dir=Epic/ACSRecovery/
2. After the files are on your phone make sure your on ec05 modem.
3. Boot into cwm doesn't matter I believe what one you have I started with acs's cwm.
4. if you are not on Rfs flash the zip to get there.
5. wipe everything 3x.
6. Flash the stock rfs ec05 rom.
7. Once finished reboot, as soon as you select reboot use the 3 finger to get back to recovery (do not let it fully boot). You should be back to the green cwm 3.1.0.1
8. Install the ec05 to ei22 zip just like any rom, I didn't wipe **** this time.
9. When finished flash the acs cwm or any flashable version you want.
Rebot the phone in cwm while holding the 3 buttons to go back to cwm(do not let it fully boot).
10. Once in cwm either acs's or any you flashed, flash the su.zip to obtain root.
11. Reboot and let your phone power up. You should now have ei22 with modem, cwm, and root.
Hope this helps somene or makes updating easier for you!
Sent from my Rooted, ACS CWM, stock EI22 Epic using XDA App
Most clear and concise guide so far. Well done!
Thanks I live in B.F.E. Ohio and didn't want to wait to have GB with root and cwm, and without a pc I was lucky it worked!
404 error on acs cwm link
Sent from my SPH-D700 using Tapatalk
**** thanks let me find another flashable link, or if anyone can share I would be thankful.
Edit: updated the link for the acs cwm
toypaj said:
**** thanks let me find another flashable link, or if anyone can share I would be thankful.
Click to expand...
Click to collapse
http://chris41g.devphone.org/index.php?dir=Epic/ACSRecovery/
Thank you very much.
tmspyder said:
http://chris41g.devphone.org/index.php?dir=Epic/ACSRecovery/
Click to expand...
Click to collapse
perfect guide, thanks so much
Lol answered all my questions. Great guide!
Sent from my SPH-D700 using XDA Premium App
No problem just thought id share.
Sent from my SPH-D700 using XDA App
Crap... i rebooted my phone after the update and now im unrooted >_>
Yeah, I'm a retard. Rebooted without installing su. Now I have stock recovery and can't root.
Tried renaming su to update.zip but it failed.
Am I out-of-luck until I can get to a pc? Maybe I'll go home "sick"...
Sent from my SPH-D700 using Tapatalk
I would assume so. I ll update main post warning a little more about not letting it fuly reboot at the 2 points.
Sent from my SPH-D700 using XDA App
I tried gingerbreak on the nanoid version of ei22 yesterday and couldn't get it to root. Might be my phone, but that's the only other way I know to root then use cwm app to install cwm 3.1.0.1
Worth a try
Sent from my SPH-D700 using XDA App
Man, thank you soooo much for taking the time to do this write up! The instructions worked perfectly for me.
No problem
Smuuv said:
Man, thank you soooo much for taking the time to do this write up! The instructions worked perfectly for me.
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA App
toypaj said:
I tried gingerbreak on the nanoid version of ei22 yesterday and couldn't get it to root. Might be my phone, but that's the only other way I know to root then use cwm app to install cwm 3.1.0.1
Worth a try
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Gingerbreak's exploit apparently has been blocked since 2.3.3, so it isn't your phone, it's the rom. You'll have to odin cwm when you can get to your pc, then boot into recovery and flash nubernel or a comparable slightly modified custom kernel *before* normal booting for the first time - otherwise, you'll lose cwm due to a script in the stock kernel that reflashes stock recovery.
For root, I'd recommend flashing the su zip in recovery, may as well do that after flashing the custom kernel. You can find the necessary downloads in one of the how-to threads that have popped up today, I'm sure they'll be easy to find for at least a few weeks
I hope this helps clear up some confusion
Sent from my SPH-D700 using XDA App
Just realized cwm is gone after first boot, that blows
Sent from my SPH-D700 using XDA App
This worked for the ROM and root, but now all I have is stock recovery. Can someone point me in the right direction on how to get CWM back?
Ok, after a subsequent battery pull, I lost root. It was all an easy fix after doing some research. Basically, I used ODIN to flash the keyfix kernel. After a re-boot, I used ODIN to flash the ACS recovery. After booting into recovery, I flashed the su.zip. I now have root and ACS recovery. I even did a battery pull and it still works.
I am using Froyo stock and rooted right now (my phone is not stable on any roms for some reason). So should i just put my phone back to stock and update then reroot? Or is there a better way? I cant seem to find the stock rom to flash.
You can remove the root and then go to GB and then re-root.
Sent from my SPH-D700 using XDA App
Just remove the root? do you mean flash back to stock using odin? I dont know how else to do it.
Sent from Epic 4g on XDA Premium
NissanNick said:
Just remove the root? do you mean flash back to stock using odin? I dont know how else to do it.
Sent from Epic 4g on XDA Premium
Click to expand...
Click to collapse
That's what I did, I used Odin to flash back to stock EC05 and am waiting for the OTA, then I'll probably reroot when a reliable method has been worked out. It seems right now there's a lot of workarounds to get root and CWM to stay.
Here is how I did it:
Odin to stock EC05
Download update.zip to SD Card and install through samsung stock recovery
Odin mkasic's kernel followed by CWM 3.1.0.1 Purple
Flash SU.zip, GPS-Fix.zip, EC05AdFree.zip
Advanced Restore of /Data through CWM
Up and running with all my existing settings, has been solid for 24hrs with no fc's.
If he's stock EC05 and rooted then you can just use the one click root windows application and remove the root. Then apply the EI22 update.zip and then do the current root method for EI22. He doesn't have to lose everything if he's on stock froyo.
Sent from my SPH-D700 using XDA App
steveo314 said:
If he's stock EC05 and rooted then you can just use the one click root windows application and remove the root. Then apply the EI22 update.zip and then do the current root method for EI22. He doesn't have to lose everything if he's on stock froyo.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Never heard of this before...how can one click root remove root? I used it to put root on!
rando991 said:
That's what I did, I used Odin to flash back to stock EC05 and am waiting for the OTA, then I'll probably reroot when a reliable method has been worked out. It seems right now there's a lot of workarounds to get root and CWM to stay.
Click to expand...
Click to collapse
It will ALWAYS be a workaround solution. So there is no need to wait for that specific aspect... since the wait would be infinite. The problem with recovery not sticking has to do with the new stock kernel. The "workarounds" require a modified kernel.
rando991 said:
Never heard of this before...how can one click root remove root? I used it to put root on!
Click to expand...
Click to collapse
1st use this, there is an un-root option:
http://forum.xda-developers.com/showthread.php?t=803682
then you can load the update.zip in stock recovery
then to get back on root do this:
http://forum.xda-developers.com/showthread.php?t=1339478
I am on stock with bloat removed. Will this work as well or will I have to odin to EC05 and lose everything? I figured I would have to odin back first.
steveo314 said:
If he's stock EC05 and rooted then you can just use the one click root windows application and remove the root. Then apply the EI22 update.zip and then do the current root method for EI22. He doesn't have to lose everything if he's on stock froyo.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
bgreiwe said:
I am on stock with bloat removed. Will this work as well or will I have to odin to EC05 and lose everything? I figured I would have to odin back first.
Click to expand...
Click to collapse
If all you've done is rooted and removed the bloat it'll work so you don't have to loose everything.
Sent from my SPH-D700 using XDA App
jat255 said:
The easiest way to do it, I think, is to do the manual update from stock EC05 to stock EI22. I did this procedure and have had zero problems. I used heimdall personally because I run Linux.
Once you have your stock GB up and running, odin/heimdall your cwm or acs recovery.bin and hold down the three button combo while it auto-reboots.
You'll get into the custom recovery, and you can flash su.zip and anything else you'd like while you're there.
Reboot the phone, and you should see that you're rooted just fine. The problem now is that there is a script that gets run on every startup called "/system/etc/install-recovery.sh" that re-installs the stock recovery on every boot. Now that you're rooted, use whatever means you'd like (file expert, terminal emulator, etc.) to get into /system/etc/ and delete that file.
You'll have to do one final odin/heimdall of the custom recovery.bin, but after that, you should be rooted and have a permanent custom recovery on stock EI22!
Sure, it's a workaround, but it's not that hard, and it works! It's easy to let the devs do everything for us, but every now and again it's good to get into your device and figure out the way things work on your own.
Good luck!
Click to expand...
Click to collapse
Thanks followed this guide made cwm 3.1.0.1 and root sticked. I am like many others likes to have everything as stock and as little changes so i didnt want to flash any custom kernel. This method will retain everything from stock just minus 1 script.
This is my revised method which only need to flash cwm 3.1.0.1 in odin 2 times and it will stick there forever.
Comming from a bone stock EI22
1. flash cwm 3.1.0.1 with reboot checked off (nothing check), put file in pda.
http://drockstar.devphone.org/EpicTar/cwm3.1.0.1.tar.md5
2. when its done, unplug data cable and pull out battery.
without rebooting system.
3. vol down, camera, power, to get into cwm recovery
4. install su.zip and reboot the phone (now you have root)
http://downloads.androidsu.com/superuser/su-3.0-efgh-signed.zip
5. install es explorer from market
5a. under menu/setting check the box root explorer and mount file system
5b. browse into phone /system/etc/install-recovery.sh
delete "install-recovery.sh" script or move it to your sd card if you want to retain a copy.
(long press into that file and delete option will come out)
6. shut off your phone
7. odin cwm 3.1.0.1 again with reboot checked
8. restart, cwm and root will be stick forever.
credit to jat255
rando991 said:
That's what I did, I used Odin to flash back to stock EC05 and am waiting for the OTA, then I'll probably reroot when a reliable method has been worked out. It seems right now there's a lot of workarounds to get root and CWM to stay.
Click to expand...
Click to collapse
Odin back to DG27. It should force the update.
lbe said:
Thanks followed this guide made cwm 3.1.0.1 and root sticked. I am like many others likes to have everything as stock and as little changes so i didnt want to flash any custom kernel. This method will retain everything from stock just minus 1 script.
This is my revised method which only need to flash cwm 3.1.0.1 in odin 2 times and it will stick there forever.
Comming from a bone stock EI22
1. flash cwm 3.1.0.1 with reboot checked off (nothing check), put file in pda.
http://drockstar.devphone.org/EpicTar/cwm3.1.0.1.tar.md5
2. when its done, unplug data cable and pull out battery.
3. vol down, camera, power, to get into cwm recovery
4. install su.zip and reboot the phone (now you have root)
http://downloads.androidsu.com/superuser/su-3.0-efgh-signed.zip
5. install es explorer from market
5a. under menu/setting check the box root explorer and mount file system
5b. browse into phone /system/etc/install-recovery.sh
delete "install-recovery.sh script"
(long press into that file and delete option will come out)
6. shut off your phone
7. odin cwm 3.1.0.1 again
8. restart, cwm and root will be stick forever.
credit to jat255
Click to expand...
Click to collapse
I think it would be a good idea to copy that script and put it somewhere instead of deleting it just in case you want to go back to bone stock in the future (who knows an ICS update LOL). Once copied, then delete the file.
Sent from my SPH-D700 using XDA App
adelmundo said:
I think it would be a good idea to copy that script and put it somewhere instead of deleting it just in case you want to go back to bone stock in the future (who knows an ICS update LOL). Once copied, then delete the file.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
you can odin the ec05 stock rom and update to ei22 and it will put that file back in. doesnt hurt to move that file to your sd card i guess.
Here is the stock EC05 ROM you are looking for. It formats your phone back to the RFS file system, but keeps your phone rooted and with CWM3.1.0.1
There is also a link on that page if you want to make your recovery go back to stock as well.
If you want to just ODIN and get onto EI22 stock, check this out. It's still RFS but it's deodexed, so a little faster. Comes with EC05 modem, which seems to still be more stable than the EI22, especially when it comes to Wifi.
EDIT: I take that back, that EI22 isn't so stock anymore, but it's closest you're going to get to a stock-ish EI22 that actually functions.
Odin back to stock EC05, update.zip, modified kernel patch and cwm the su.zip worked for me.
One question though.. stock OTA/update.zip is ODEXED, correct? Can I deodex what I have or do I need to re-flash a deodex stock rom and would I do it before or after uninstalling bloat?
jfg69 said:
Odin back to stock EC05, update.zip, modified kernel patch and cwm the su.zip worked for me.
One question though.. stock OTA/update.zip is ODEXED, correct? Can I deodex what I have or do I need to re-flash a deodex stock rom and would I do it before or after uninstalling bloat?
Click to expand...
Click to collapse
OTA stock is Odexed, correct. Deodexing yourself takes some time... it's not just removing files, you'll have to edit quite a few things. If you're going to deodex your system using the ROM, you just ODIN it from wherever you are now. It will erase everything, like starting from scratch. But you can restore your data on top of it if you backed it up first.
Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox
matrox00612 said:
Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox
Click to expand...
Click to collapse
In the absence of a stock flashable ROM, and if you can still get into CWM, you can do the following:
1. Mount system in recovery
2. Pull the build.prop via ADB (I believe it's adb pull /system/build.prop) on your computer
3. Revert/fix whatever tweaks you jacked up when messing with it earlier (on your PC)
4. ADB push it back
5. ADB reboot
If build.prop is all that was wrong, hopefully this may get you back in business.
pinoymutt said:
In the absence of a stock flashable ROM, and if you can still get into CWM, you can do the following:
1. Mount system in recovery
2. Pull the build.prop via ADB (I believe it's adb pull /system/build.prop) on your computer
3. Revert/fix whatever tweaks you jacked up when messing with it earlier (on your PC)
4. ADB push it back
5. ADB reboot
If build.prop is all that was wrong, hopefully this may get you back in business.
Click to expand...
Click to collapse
Under CWM mount system, adb show error device nor found, its look that my only hope is a stock odin rom.
Thanks
Ouch, sounds like bad news. Hopefully someone will post something you can use to revert soon.
Sent from my GT-P3113 using Tapatalk 2
matrox00612 said:
Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox
Click to expand...
Click to collapse
Go to the att android dev section there is a root method posted that also has a unbrick fixboot.tar file for Odin, that will put you back in business.
http://forum.xda-developers.com/sho...ick your phone from flashing a gsm boot image
Sent from my SAMSUNG-SGH-I747
stan.s said:
Go to the att android dev section there is a root method posted that also has a unbrick fixboot.tar file for Odin, that will put you back in business.
http://forum.xda-developers.com/sho...ick your phone from flashing a gsm boot image
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Thanks for the info, but thats the boot.img I need the system.img packed into an Odin tar.
matrox00612 said:
Thanks for the info, but thats the boot.img I need the system.img packed into an Odin tar.
Click to expand...
Click to collapse
There is no system.img released yet..Many of us are waiting for that system.img file. Its not leaked, released or created yet... But should be released, created soon. I am pretty sure the developers are working on it.
Till then we can just wait!!
masonjoe69 said:
There is no system.img released yet..Many of us are waiting for that system.img file. Its not leaked, released or created yet... But should be released, created soon. I am pretty sure the developers are working on it.
Till then we can just wait!!
Click to expand...
Click to collapse
Yes it is like that, we have to wait a little, but lets get the first dev to throw a working odin flashable file some motivation, i will donate 50 beers.
Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium
Jms122589 said:
Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You will need the stock kernel and your /system partition must be completely unmodified. Bootloader state and recovery don't matter. After accepting an update you will lose your custom recovery and root, so you will have to reflash but that's no big deal.
Sent from my Nexus 7 using Tapatalk HD
Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium
Jms122589 said:
Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2
oldblue910 said:
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!
udimars30 said:
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!
Click to expand...
Click to collapse
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium
Jms122589 said:
OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Correct. Just extract system.img and boot.img from the package you download, then plug your tablet into USB, boot it into the bootloader, and do the following two commands:
fastboot flash boot boot.img
fastboot flash system system.img
If you want to wipe data, also do:
fastboot erase cache
fastboot erase userdata
That'll get you back to complete stock.
OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium
Jms122589 said:
OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Extract them to your desktop somewhere, then do fastboot from the command prompt.
oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
sorry but i didn't get this part 'As long as you do that and you don't let root apps modify files on your /system partition' and to flash all that i need unlock bootloader??
oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:
udimars30 said:
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:
Click to expand...
Click to collapse
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.
oldblue910 said:
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.
Click to expand...
Click to collapse
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??
udimars30 said:
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??
Click to expand...
Click to collapse
I'm on Twitter and G+. Just click on my name over on the left of this post and you can find links to my profiles.