Related
Hey all,
I have installed the transparent notification bar before this update had come out. I reinstalled all this ****ty bloatware and copied the original framework.apk and services.jar back to the phone yet I am still unable to comeplete the 2.2 upgrade. I get the following
..........................installing update...
Verifying current system...
assert failed: apply_patch_check
any ideas?
You must have changed something while it was rooted... cuz my stock droid not messed with at all went through the update perfect.
Sent from my DROIDX using XDA App
I'm getting this same error.
Don't have phone yet, but have been keeping up with the issues others have been having for when I do... Your best bet:
-- Load stock .sbf (search for thread on this, or pretty much any other DX forum for info)
-- Root (optional, if you want root in froyo, you need to root in 2.1)
-- Re-Run the update.
Note: There have been reported problems by some that have done this of getting the "M" (boot) screen upon boot. They fixed by entering debug screen (power + home), and factory reset (clears /data, and /cache).
HTH.
So I used Oneclickroot 2.3.0 a while back, which did NOT remove asphalt or nascar or anything else that I know of and i did check the run.bat file...saw nothing regarding any removal of files.
I undid the root in order to apply the update and I still get an error...does anyone know what can be wrong? Here is the error:
Verifying current system...
assert failed: apply_patch_check ("/system/build.prop", "6d74575d0a7391c3578d907fc43f9485f8d93032", "68a96e00d1e9b40bad1491dbf63822e7be86fca6")
E:error in /sdcard/update.zip
(status 7)
Installation aborted.
Ideas, anyone?
Thanks
Try renaming the file to just "update" and not update.zip
Please update us about whether this solution works and good luck. Pretty sure I'm going to be in the same situation.
Unfortunately this did not work. It is looking for update.zip. not update.
Anyone else? Please throw some ideas!
OdIN > DI18
Odin
Odin back to stock Di18 and reapply the update zip it will work fine from there.
Top Nurse said:
OdIN > DI18
Click to expand...
Click to collapse
The oneclickroot didnt delete anything though. The error is saying that it is the update.zip...or is that normal? Is there any way to figure this out so that I do not have to start from scratch with everything on my phone?
Redownload the zip. That was a problem I had, and I rooted with cwm 2.5...
Sent from my SPH-D700 using XDA App
damicrobe said:
Redownload the zip. That was a problem I had, and I rooted with cwm 2.5...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I did this many times, I even downloaded it straight from my phone browser to single out any problems with a usb cable...still nothing.
Anyone have an alternative link to it, besides that thread thats entitled direct google download?
Check for the existance of /system/build.prop
Lcstyle said:
Check for the existance of /system/build.prop
Click to expand...
Click to collapse
You may be on to something. I once DID modify
windowsmgr.support_rotation_270=false
to true, using root explorer. I just changed it back.
Can someone please copy/paste the contents of this file to me?
Also, if there's a build.prop.bak file in the /system directory, would that make a difference?
Elixis said:
You may be on to something. I once DID modify
windowsmgr.support_rotation_270=false
to true, using root explorer. I just changed it back.
Can someone please copy/paste the contents of this file to me?
Also, if there's a build.prop.bak file in the /system directory, would that make a difference?
Click to expand...
Click to collapse
The plot thickens! Even though I've never made such a change, I'm still interested to see how you do so I'm going to try and help you out when I get to a real computer shortly. EDIT: here it is, stock dated 9/18/10 attached.
Were you at least able to use your phone even after these failed upgrades? It'd help settle things in my mind if the answer's yes.
I did the same thing and the DI18 -> EB13 update failed on my phone 'til I reverted the build.prop file back to original ( you did save build.prop.orig didn't you )
After I restored the file ot original the update completed and now I'm on EB13 waiting for EC05.
JDotScott said:
I did the same thing and the DI18 -> EB13 update failed on my phone 'til I reverted the build.prop file back to original ( you did save build.prop.orig didn't you )
After I restored the file ot original the update completed and now I'm on EB13 waiting for EC05.
Click to expand...
Click to collapse
Excellent news! That means I hopefully stand a good chance of success. Anyway, the file's above for Elixis.
Thanks! How exactly do I apply this file and get rid of the old one? Do I need to root again?
Elixis said:
Thanks! How exactly do I apply this file and get rid of the old one? Do I need to root again?
Click to expand...
Click to collapse
I'm far from the biggest expert here but I think you probably would, yes, then do a copy/paste with the right file explorer. I use AndExplorer and it can see the root of the phone FS (that's how I got the file actually).
My questions to you and others are:
1) is the phone still OK after a failed update.zip process
and
2) is it really necessary to UN-root in order to make the update work? (whether or not you have to root again after it's done)
Yes, the phone DOES still work after a failed update process. It never started to fully undo the file....the verifications failed.
DroidApprentice, thanks so much for the build.props file...that definately helped something =]
however, I now face a NEW error when trying to install the update:
"BML:Boot: (then a bunch of random numbers and letters)
Status 7.
Any ideas on what this is?
Phone still works after this error.
I tried this both while rooted and unrooted.
Edit: I found a thread on sdx, where Firon says that you need a stock kernel to flash a stock update. The oneclickroot said something about the kernel when it installed, but doesnt it put everything back to normal when you undo it? Is there an easy fix for this, if this is the cause?
Whew, this just gets more interesting if not frustrating, but at least you're not "soft bricking" your phone.
It's funny but I never thought One Click Root did ANYTHING to the kernel. I guess my reading about it or knowledge of it isn't as comprehensive as I thought.
I'd like to continue helping you research this issue because, like you, I would prefer not to use Odin unless I have no other choice.
Elixis, I just realized! You may have been on EB13, the first "official" Froyo update, or another ROM entirely.
I am on DI18 and that's where my build.prop file came from, a rooted with OCR DI18/Eclair phone. That may matter and just wanted to make sure you were clear on that since I'm guessing other versions may have different build.prop files which could affect the update process.
I'm a noob but not that much of a noob....lol. I'm on DI18, not EB13..
All,
I got a notification of update this morning (June 29, 2011) on my HTC EVO 4G (rooted/with netarchy toast mod) but when I tried to apply the update I get:
assert failed: apply_patch_check ("/system/lib/modules/bcm4329.ko". "78fE:unknown command [c535f323ef3a5c8304b32f514c23ea458132b".]
E:unknown command [9"0]
E: Error in /cache/OTA-Supersonic_4.24.651.1-3.70.651.1_release404yzkft23eop520.zip (Status 7)
Installation aborted.
Android system recover is open and the prompts are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Mounts
- Other
- Power off
What do I do next? How do I get this update? Thanks!
guidecca said:
All,
I got a notification of update this morning (June 29, 2011) on my HTC EVO 4G (rooted/with netarchy toast mod) but when I tried to apply the update I get:
assert failed: apply_patch_check ("/system/lib/modules/bcm4329.ko". "78fE:unknown command [c535f323ef3a5c8304b32f514c23ea458132b".]
E:unknown command [9"0]
E: Error in /cache/OTA-Supersonic_4.24.651.1-3.70.651.1_release404yzkft23eop520.zip (Status 7)
Installation aborted.
Android system recover is open and the prompts are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Mounts
- Other
- Power off
What do I do next? How do I get this update? Thanks!
Click to expand...
Click to collapse
Anyone, anyone? Don't everyone rush down. There's room for everyone.
Is your recovery old (ie not Clockworkmod 3)
Have you tried to backup your apps with titanium and just starting all over with a new updated full rom?
Have you edited the filesystem to cause the update to say this? If you edit any of the filesystem, the update fails.
You need to download a new rom and just start all over it seems.
How are we to figure things out if you dont give any background?
Try unrooting and put a stock rom and then do an update. Hope that helps
Sent from my HTC EVO phone, shouldn't we all have one?
If you want to keep root, then you never take the update. Otherwise you will most likely lose root, and will have to wait until a Dev finds an exploit to reroot. If you want to just update the radio(s) then there are flashable updates in the Dev section that you can flash.
I Think I Did/Didn't
mattrb said:
Is your recovery old (ie not Clockworkmod 3)
Have you tried to backup your apps with titanium and just starting all over with a new updated full rom?
Have you edited the filesystem to cause the update to say this? If you edit any of the filesystem, the update fails.
You need to download a new rom and just start all over it seems.
How are we to figure things out if you dont give any background?
Click to expand...
Click to collapse
Not sure what clockworkmod I have. I could backup app with titanium and which "full rom" would you recommend? I have netarchy-toastmod-4.3.4-cfs-havs-less-nosbc-uni installed and in zip format. I rooted the phone and applied the toastmod so I modified the stock HTC EVO 4G file system. The next comment suggests unrooting the phone and starting over. Why so much work for a "smart" phone? Any specifics would be appreciated on how to proceed.
kf2m said:
If you want to keep root, then you never take the update. Otherwise you will most likely lose root, and will have to wait until a Dev finds an exploit to reroot. If you want to just update the radio(s) then there are flashable updates in the Dev section that you can flash.
Click to expand...
Click to collapse
Seems to be a rule never to take an update of the original after modifying any gadget. Maybe my rooted phone is better off/more advanced without the update but I haven't found anyone that has said it yet. Since the update failed I think I have root but I will check it. My wife's unrooted phone took the update easily.
guidecca said:
Seems to be a rule never to take an update of the original after modifying any gadget. Maybe my rooted phone is better off/more advanced without the update but I haven't found anyone that has said it yet. Since the update failed I think I have root but I will check it.
Click to expand...
Click to collapse
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
If you would like to keep the stock rom but update to the newest release you can download Rom Manager from the market and flash the newest stock rom. Quite easy and only takes a few clicks. Next time you see an update from sprint, just wait until Rom Manager gets a rooted rom of that release and go nuts. If you don't feel like dealing with Rom Manager you can manually flash the roms you find in this forum. Hope this helps.
This has worked rather well for me for the past few updates, including the most recent one:
forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/90582-guide-updating-rooted-gingerbread-without-flashing-new-rom-wiping-your-phone.html
Also, the error you see is likely due to you changing the Broadcom file in that location to enable Wifi-N speeds on your EVO. Is that something you remember doing? When installing updates, it needs the original unchanged version of "\system" files to be there to verify against, including this one.
I just went through the process, and got the same error before I remembered to change bcm4329.ko back to the original. Also, don't forget to unfreeze any bloatware if it is frozen, or it won't proceed past the verification process (as it changes "\system" files. Additionally, clearing the Davlik cache is always a good idea when updating.
I forgot to mention- If I remember correctly, the instructions are elaborated on in post #44 of that page.
tgruendler said:
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
Click to expand...
Click to collapse
You say a rooted version was ready to be flashed within hours.
This is what I read on Android Forums:
There is no exploit yet to allow unrevoked to root the new hboot(2.16). They will find it but how long is unknown.
You can apply the update by flashing the rooted rom and the updated radios found here: [ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers and here: [ Radios ][ 6-3 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
The only thing that would not happen by flashing those it that your hboot would not be upgraded which you don't want anyway so that you can retain root.
If Haux has an exploit would it work on netachy toastmod rooted EVO 4G?
guidecca said:
You say a rooted version was ready to be flashed within hours.
This is what I read on Android Forums:
There is no exploit yet to allow unrevoked to root the new hboot(2.16). They will find it but how long is unknown.
You can apply the update by flashing the rooted rom and the updated radios found here: [ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers and here: [ Radios ][ 6-3 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
The only thing that would not happen by flashing those it that your hboot would not be upgraded which you don't want anyway so that you can retain root.
If Haux has an exploit would it work on netachy toastmod rooted EVO 4G?
Click to expand...
Click to collapse
To be technical because I am a jerk, Hehe, you don't root the hboot. You unlock it via making it s off. You root the Rom by applying super user privileges from within. Hboot s off means you can easily flash different recovety images, radios, and any ruu considering you have supported radios. Tomatoes tomahtoes.
Sent from my PC36100 using XDA Premium App
Thanks
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
I just thought that maybe there was an exploit for gingerbread 2.3 (OTA) that someone had found within hours of Google's release. I wanted to definitely make sure there was or wasn't a way to update my phone. Thanks for your clarification on hboot, etc. Mattlock over on Android Forums has a good guide for rooting and he is good at step-by-step 'how to do it' and some explanation why for us newbies. My rooted phone works fine but my wife's stock phone with the update seems to get a lot of network failures. She has a lot apps and a stock SD card - she refuses to let me root her phone - superstitious kind.
When I try it bombs on /system/framework/android.policy.jar and stops.
Now, I have not been using OTAs except maybe when I first unboxed it and let it do its think 6 months ago, because I put TWRP 2.6.0.0 on as soon as I could. I went from JO40D to JDQ39 in a ROM from someone here, then JWR66V from another ROM. These were (mostly) stock ROMs, I just didn't want to wait for OTA.
Well now my system says an update is available. It's only 1.7mb and sitting in /cache. But it won't install. I've tried through recovery (TWRP), letting it do it on its own, and ADB sideloading. all fail same place.
Now, I recently installed Advanced Power Menu for JWR66V. I suspect it may have changed the files. Or, it could be any of the other ROMs along the way, I've saved them and opened them and saw no android.policy.jar in /system/framework, so I assume it's a file that has not changed for many versions.
OR, I'm getting confused, and I'm not certain WHICH JWR66V I have, so maybe didn't save it. I recall having issues with one 4.3 so I tried another - which one I'm on now I'm not sure but I think it's AOSP-4.3-JWR66V-grouper-rooted_Androguide...and now that I look, it does have a full /system/framework. Is the OTA choking on that?
I tried downloading a factory image and discovered after opening them up they are just .img files and I'm not sure how I can get individual files out..or if I even should, or which version, lest I render my Nexus 7 unbootable.
I just want to get my system back to a functional state (without losing my data or files or setup or recovyer), from which it can update to JWR66Y.
Or should I just wait for someone to roll up a full ROM of JWR66Y since I've strayed so far from the OTA path?
Either flash the image files using fastboot or loop-mount the system.IMG on your PC and extract the files you need. After that you can push them to the tablet and apply the OTA ...
Nevertheless I think the first opportunity is more easy, isn't it?
Edit: the new ROM images are already available on the Google developer site.
Sent from my Nexus 7 using xda app-developers app
Oops, thought I'd already posted. I solved it. I found the ROM I was using, took the 3 files out and replaced the APM zip files with them. Flashed that, and was happily on my way. From now on I'll be sticking to quick reboot rather than modifying my framework-res.apk and anrdoid.policy.jar
Hello XDA members,
I seem to have borked something on my new SM-T530NU (GALAXY TAB 4 10.1 WI-FI) when I attempted to root the device (to get rid of all the bloatware).
I followed the instructions I found online (can't insert links yet) and everything seemed to have worked fine (Odin giving me a PASS). Once I got into the OS I noticed I was unable to connect to my WIFI. I reread the instructions and this time noticed my build id was different than the writer's (I have KOT49H.T530NUUEU1AOA2 and he had KOT49H.T530NUUEU1AND4). I checked the CF-Auto-Root Repository and noticed they don't have one for mine
Finally I decided I would download Kies 3 from Samsung and do a Firmware Upgrade and Initialization but that accomplished nothing.
Can anyone help me solve this?
hi, it sounds like you have a mismatch between your kernel and your kernel's modules, instead of an upgrade you may need to do a full reflash of
the current rom version you upgraded from/to i'm guessing ND4 all the way. Alternately you could try one of the repacked stock roms that are available, otherwise you could attempt a custom kernel build so your modules match up , package it and flash it, note that this is not as simple as an odin flash and problem solved. You would need to pack that custom kernel build for recovery flashing instead, meaning the package would have to write the boot.img to it's proper location and the modules to their proper location /system/lib/modules.
check /system/lib/modules on the rom you are running right now and see if wlan.ko is present. If there is a folder in /system/lib/modules named pronto then see if in that directory the modules pronto_wlan.ko exists and if it is symlinked one directory up to wlan.ko
you should always inspect fota's and firmwares before flashing. if you have the firmwares still and/or you managed to capture the upgrade, inspect them to see what was written/overwritten and you'll have an idea of what your issue might be.
also in terminal su and enter the command after toggling wifi on
lsmod
if wlan.ko does not show up, try
modprobe -f /system/lib/modules/wlan.ko
alternately try entering in terminal as su
svc wifi enable
moonbutt74 said:
hi, it sounds like you have a mismatch between your kernel and your kernel's modules, instead of an upgrade you may need to do a full reflash of
the current rom version you upgraded from/to i'm guessing ND4 all the way. Alternately you could try one of the repacked stock roms that are available, otherwise you could attempt a custom kernel build so your modules match up , package it and flash it, note that this is not as simple as an odin flash and problem solved. You would need to pack that custom kernel build for recovery flashing instead, meaning the package would have to write the boot.img to it's proper location and the modules to their proper location /system/lib/modules.
check /system/lib/modules on the rom you are running right now and see if wlan.ko is present. If there is a folder in /system/lib/modules named pronto then see if in that directory the modules pronto_wlan.ko exists and if it is symlinked one directory up to wlan.ko
you should always inspect fota's and firmwares before flashing. if you have the firmwares still and/or you managed to capture the upgrade, inspect them to see what was written/overwritten and you'll have an idea of what your issue might be.
also in terminal su and enter the command after toggling wifi on
lsmod
if wlan.ko does not show up, try
modprobe -f /system/lib/modules/wlan.ko
alternately try entering in terminal as su
svc wifi enable
Click to expand...
Click to collapse
Thanks for the info moonbutt74,
I don't feel comfortable playing with the Kernel / commands (besides I seem to have lost the Super User when I flashed to the latest firmware using Kies3) so I decided to try some old firmware like you recommended (PDA T530NUUEU1AND4 / CSC T530NUXAC1AND4) on sammobile and flashed my device with Odin using the default options. Wifi/bluetooth works now but now I have a new problem; Google Play services keep stopping and giving me errors. I clicked ok a few times and the error is no longer appearing however I can't seem to login to Google (Can't establish a reliable connection to the server) . If I try to access gmail.com from Chrome it tells me something is interfering with your secure connection to gmail.
Any ideas?
SulfurMDK said:
Thanks for the info moonbutt74,
I don't feel comfortable playing with the Kernel / commands (besides I seem to have lost the Super User when I flashed to the latest firmware using Kies3) so I decided to try some old firmware like you recommended (PDA T530NUUEU1AND4 / CSC T530NUXAC1AND4) on sammobile and flashed my device with Odin using the default options. Wifi/bluetooth works now but now I have a new problem; Google Play services keep stopping and giving me errors. I clicked ok a few times and the error is no longer appearing however I can't seem to login to Google (Can't establish a reliable connection to the server) . If I try to access gmail.com from Chrome it tells me something is interfering with your secure connection to gmail.
Any ideas?
Click to expand...
Click to collapse
Disregard, turns out the time/date was off by a few months and setting it to the current time/date fixed the SSL issue but Google Play Services are going nuts / stopped.
SulfurMDK said:
Disregard, turns out the time/date was off by a few months and setting it to the current time/date fixed the SSL issue but Google Play Services are going nuts / stopped.
Click to expand...
Click to collapse
okay cool, sub77 and i both have recoveries available for the sm-t530nu pick whichever,
when a device has a custom recovery available you don't need to go the long way around for root anymore.
search google for supersu update zip
and download and flash the latest version and flash in recovery and your root should be solved.
m
SulfurMDK said:
Disregard, turns out the time/date was off by a few months and setting it to the current time/date fixed the SSL issue but Google Play Services are going nuts / stopped.
Click to expand...
Click to collapse
And a factory reset fixed the Google services but I'm still getting some weird issues with the Play store. I'll do some digging and see what I come up with.
In the mean time, do you have any recommendations on how to proceed to properly root my tablet? I really want to get rid of some of the bloatware on this thing...
SulfurMDK said:
And a factory reset fixed the Google services but I'm still getting some weird issues with the Play store. I'll do some digging and see what I come up with.
In the mean time, do you have any recommendations on how to proceed to properly root my tablet? I really want to get rid of some of the bloatware on this thing...
Click to expand...
Click to collapse
hi,
see my previous post, and remember to make the full backup of your rom before debloating attempt.
And after you satisfied whith your results make another full backup of your debloated rom.
keep both versions.
m
moonbutt74 said:
okay cool, sub77 and i both have recoveries available for the sm-t530nu pick whichever,
when a device has a custom recovery available you don't need to go the long way around for root anymore.
search google for supersu update zip
and download and flash the latest version and flash in recovery and your root should be solved.
m
Click to expand...
Click to collapse
Alright, I'll give it a shot. Thanks alot for all your help!
On a side note, is there a good ROM out there for the Tab 4 ? It seems the support for this device is really slim ... Preferably something based off Lollipop?
SulfurMDK said:
Alright, I'll give it a shot. Thanks alot for all your help!
On a side note, is there a good ROM out there for the Tab 4 ? It seems the support for this device is really slim ...
Click to expand...
Click to collapse
see sub77's threads for rom builds all beta or alpha
see repey6's threads for modded stock roms.
i have a rough slimrom build [not release] with no camera and battery issues.
developement takes time and is done for free and largely on a hobby basis.
sub77's is coming along nicely as to progress on cm12
m
moonbutt74 said:
see sub77's threads for rom builds all beta or alpha
see repey6's threads for modded stock roms.
i have a rough slimrom build [not release] with no camera and battery issues.
developement takes time and is done for free and largely on a hobby basis.
sub77's is coming along nicely as to progress on cm12
m
Click to expand...
Click to collapse
Stupid thing ... the tablet decided to update itself and I'm back to square one (wifi not working). Sigh.
What do you recommend? Should I reflash NAD4 and and turn off updates? Or is there a better solution?
SulfurMDK said:
Stupid thing ... the tablet decided to update itself and I'm back to square one (wifi not working). Sigh.
What do you recommend? Should I reflash NAD4 and and turn off updates? Or is there a better solution?
Click to expand...
Click to collapse
repeat your previous steps and shut off your router. then disable your updates.
moonbutt74 said:
repeat your previous steps and shut off your router. then disable your updates.
Click to expand...
Click to collapse
I tried installing your recovery a couple of times but I keep getting the following:
Install from package...
Finding update...
Opening Update...
Verifying update...
E: failed to verify whole-file signature
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
Is there a way to turn off verification on the stock recovery?
SulfurMDK said:
I tried installing your recovery a couple of times but I keep getting the following:
Is there a way to turn off verification on the stock recovery?
Click to expand...
Click to collapse
ahh okay, you need to install your chosen custom recovery with odin.
read the entire OP [original post].
I have to cut you off here to give you the push you need to make the most
of XDA. Within the tab 4 section you will find full instruction to accomplish
your mission but, you must search for it. That and i have a few projects
in front of me at the moment. Just keep a level/focused head and you'll
get things sorted. :good:
m
SulfurMDK said:
I tried installing your recovery a couple of times but I keep getting the following:
Is there a way to turn off verification on the stock recovery?
Click to expand...
Click to collapse
You can't install a custom recovery from stock recovery, I would recommend downloading the img file and installing it with the flashify app from the play store, that's how I got a custom recovery on my tablet and I have the same model as you. As far as Roms, both metallica's cm 11 and sub77's cm12 are great, just depends if you want Kit Kat or lollipop
moonbutt74 said:
ahh okay, you need to install your chosen custom recovery with odin.
read the entire OP [original post].
I have to cut you off here to give you the push you need to make the most
of XDA. Within the tab 4 section you will find full instruction to accomplish
your mission but, you must search for it. That and i have a few projects
in front of me at the moment. Just keep a level/focused head and you'll
get things sorted. :good:
m
Click to expand...
Click to collapse
Understood m
Thanks again for all your help and good luck on your projects!!
Regards
Just wanted to thank you both for your invaluable help. I'm now running a custom rom by repey6 and everything is working all minus all the Samsung bloat.
Cheers