Related
Hey there, I have a question which seems to have been addressed at http://forum.xda-developers.com/showthread.php?t=1256708 , but would like to confirm: can I create an app partition on my SD card without having anything other than a stock ROM on my Desire? They seem to have done it simply with a rooted device...mine is not rooted, would I have to root it? If so, would that be it?
Thanks in advance for any advice!
You need root to use sd-ext partition. Not really sure, but I think you can't use any way of a2sd (meaning apps 2 sd-ext, not the "official" a2sd, that moves apps to fat32 sd) with stock ROM.
You need to flash a custom ROM, and if you want something as "stock rom but with a2sd" install SuperNova, or any other ROM from droidzone.
You also have lots of different options, with a higher ustomization, very different from HTC Desire stock ROMs, with Sense 2.1, 3.0. 3.5, or AOSP (without Sense) etc.
I see...thanks a lot for the info, Supernova seems to be my best bet, I want a ROM that is essentially unchanged so that I won't have bugs, etc.
Blackhawk is right, to be able to use a2sd (to sd-ext) you require root and a folder called init.d in the system partition which is not present in stock roms.
Sent from my HTC Original Desire with Beats Audio using Tapatalk
what if??
what if i were rooted, and created that folder in the system folder, would it then be possible to do this on stock 2.3.3??
i practically fell in love with not ever seeing that damn low phone memory notification, and now i switched back to a stock rom because of the 2.3.3 update for my lg
edit: so your saying there is no system partition in stock "ROMs"? only in custom roms? im quiet confused when it comes to factory ROMs because ive never really messed with them, i normally only used it a a fallback if i mess anything up beyond control
---------- Post added at 07:59 PM ---------- Previous post was at 07:09 PM ----------
i went to the previously mentioned thread and and basically re-asked the question, i am trying to get one solitary answer from both parties before i go messing with anything lol
once again thanks
ShawnnKushh said:
what if i were rooted, and created that folder in the system folder, would it then be possible to do this on stock 2.3.3??
i practically fell in love with not ever seeing that damn low phone memory notification, and now i switched back to a stock rom because of the 2.3.3 update for my lg
edit: so your saying there is no system partition in stock "ROMs"? only in custom roms? im quiet confused when it comes to factory ROMs because ive never really messed with them, i normally only used it a a fallback if i mess anything up
Click to expand...
Click to collapse
No. Even if you created it in the system partition, you will also need to have a modified boot.img than enables the usage of the init.d folder which is provided by all roms that uses that folder. Or you can search if anyone has hacked the boot.img to support it.
The system partition is just a protected sector of the NAND memory that stores all of the system files. It is present even in stock roms.
Sent from my HTC Original Desire with Beats Audio using Tapatalk
Hey guys, I am new to the android os (just switched from ios) and I have read most of the tuts and have been successful flashing a few roms testing them out getting a feel for the one I want. However after my third flash I began to see a "0" directory show up on my internal sd root and inside that directory it contains all the folders that are in the same root directory as "0". Has anyone else had this occurance and if so what can I do to eliminate the unnecessary directory? I make sure to do a complete wipe of my phone between flash and follow the instructions to the T. If anyone could help me out I would greatly appreciate it. Thanks guys
Lukkaz said:
Hey guys, I am new to the android os (just switched from ios) and I have read most of the tuts and have been successful flashing a few roms testing them out getting a feel for the one I want. However after my third flash I began to see a "0" directory show up on my internal sd root and inside that directory it contains all the folders that are in the same root directory as "0". Has anyone else had this occurance and if so what can I do to eliminate the unnecessary directory? I make sure to do a complete wipe of my phone between flash and follow the instructions to the T. If anyone could help me out I would greatly appreciate it. Thanks guys
Click to expand...
Click to collapse
The "0" is a part of Android 4.2's file system setup, so if your current ROM is 4.2-based, leave it alone.
If you're not currently running 4.2, you can safely move the entire contents of the /0 directory up a level (i.e. to wherever the 0 directory is located) and remove the /0 directory.
smelenchuk said:
The "0" is a part of Android 4.2's file system setup, so if your current ROM is 4.2-based, leave it alone.
If you're not currently running 4.2, you can safely move the entire contents of the /0 directory up a level (i.e. to wherever the 0 directory is located) and remove the /0 directory.
Click to expand...
Click to collapse
Thank you for the quick response, yeah I have messed with a couple 4.2 roms so I have a few levels. I'm debating flashing a 4.1 just to clean it up I have about 3 levels lol
Lukkaz said:
Thank you for the quick response, yeah I have messed with a couple 4.2 roms so I have a few levels. I'm debating flashing a 4.1 just to clean it up I have about 3 levels lol
Click to expand...
Click to collapse
Just flashing a 4.1 ROM won't solve the problem.
If you're going to stick to 4.2, you can move everything up to the top "level" of /0 and delete the other /0s.
Incidentally, the stacked /0s is caused by repeatedly flashing 4.2 ROMs with a recovery that isn't designed to handle them. I know TWRP 2.3.2.0 and newer handle 4.2 properly - can't speak for anything else.
Updating your recovery will eliminate problems with the creation of /0 folders when flashing 4.2 ROMs.
I currently use cwm not sure the version but not entirely sure if it is up to date, what recovery do you guys personally recommend?
Lukkaz said:
I currently use cwm not sure the version but not entirely sure if it is up to date, what recovery do you guys personally recommend?
Click to expand...
Click to collapse
TWRP (which I mentioned earlier) is available over in this thread.
Lukkaz said:
I currently use cwm not sure the version but not entirely sure if it is up to date, what recovery do you guys personally recommend?
Click to expand...
Click to collapse
I strongly prefer TWRP. I don't recall the exact version number but it been be easily downloaded by downloading the app entitled "goo manager." Once in the app, tap the capacitive menu button and select install recovery script. TWRP is easy to use, completely touch based, and even themable.
Thanks guys, I'm at work now but I'll take a look and see what I got to do to get that recovery straightened out. Thanks again
CWM 6.0.2.3 is now 4.2 capablie just flas with that version and copy the 0 directorys to the root directory and remove the 0 directorys afterword
pe4nut6666 said:
CWM 6.0.2.3 is now 4.2 capablie just flas with that version and copy the 0 directorys to the root directory and remove the 0 directorys afterword
Click to expand...
Click to collapse
Some poking suggests the 4.2 issues with CWM were fixed as of 6.0.1.6.
I think I might fo the TWRP route you guys suggested earlier looks pretty stable nice UI and few added features that I look foward to using, I dont have much time atm being at work but does anyone have a quick and easy way to remove the old recovery and add the new? I know there are prob tuts I'm just short of time and would like to get it flashed at the office. It's fine if not I'll just do some reseach tomorrow
Lukkaz said:
I think I might fo the TWRP route you guys suggested earlier looks pretty stable nice UI and few added features that I look foward to using, I dont have much time atm being at work but does anyone have a quick and easy way to remove the old recovery and add the new? I know there are prob tuts I'm just short of time and would like to get it flashed at the office. It's fine if not I'll just do some reseach tomorrow
Click to expand...
Click to collapse
Just install the new recovery normally; it'll replace whatever was there before.
Hi All,
I am currently running the Jellybeer v3.52 ROM which is CM10.1 / JB 4.2.+ based and I was having an issue with the CWM that I was using not being able to restore my NAND backups which I have since fixed but my biggest issue now is apparently the way that CM10.1 / JB 4.2.+ manages files... Let me explain...
After every time I flash a new ROM or restore a NAND backup there is a new "folder" being created that shows as /0 and ALL of my information continuously gets "buried".
I now have THREE /0 folders apparently which are viewable via CWM, File Explorers and when I connect my device to my computer and I just don't know what to do with them to get rid of them and to stop this from continuing as it keeps adding a new folder EVERYTIME I flash something. I don't know if I should be deleting them or trying to merge them all together as I have pictures and data in 2 of the 3 folders that show and in the gallery for example, all pictures and things show up but there are double folders that say "saved" and "downloaded", etc because it is saving them to different /0 folders.
Can anyone PLEASE give me some advice on what to do.
Thanks in advance...
Flash twrp and restore with it.
Or copy the backup to pc and restore via toolkit
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Flash twrp and restore with it.
Or copy the backup to pc and restore via toolkit
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
This will somehow fix my issue with having all of these /0 folders? I have already fixed my NAND restore issue by flashing an up to date CWM that supports CM10.1 / JB 4.2.+ ROMS but now I want to get rid of these /0 folders. Can you clarify on this and also... is TWRP compatible with 4.2.+ / CM10.1 ROMS?
You wanna restore your nandroid don't you?
Just copy over the backup to your computer and restore via toolkit
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
You wanna restore your nandroid don't you?
Just copy over the backup to your computer and restore via toolkit
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
No my friend... If you read the post, I have already FIXED my NAND issue by flashing a CM10.1 / JB 4.2.+ supported CWM recovers so now I am ABLE to restore my NAND's. What I want to find out now is how to get rid of / stop all of these new /0 folders from being created on my device after I flash ANYTHING.
Example... I flash a ROM and a new /0 folder is created. I restore my NAND and a new /0 folder is created. I flash a NEW ROM and yet another /0 folder is created, etc, etc, etc... All of these /0 folders are messing up where apps store their data, where my files and pictures are being saved to, etc and I want to know how to get rid of all of these /0 folders and how to STOP them from creating every time I flash something.
Flash stock rom. 4.2 will make a 0 folder every time.
Flash stock rom and recover data from 0 folder.
If you are talking about re flashing fresher nightly, you gotta wipe sdcard every time.
Also if you want to use phone for normal usage, don't use cm.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Flash stock rom. 4.2 will make a 0 folder every time.
Flash stock rom and recover data from 0 folder.
If you are talking about re flashing fresher nightly, you gotta wipe sdcard every time.
Also if you want to use phone for normal usage, don't use cm.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
This is not true my friend. See below for a reply I received from the "porter" of the ROM I am using right now - JellyBeer which is CM10.1 / JB4.2.+ based and he does NOT have this issue - nor do a lot of other people... See below...
Originally Posted by [vertigo]
I can say that it doesn't happen with me, I only have one '0' folder and have only ever had one, and when I use CM file explorer on the new version 3.53 (which I'm testing now) it doesn't show any '0' folders up (look at attached image, thats what I get when I first open it up), it just shows what is in that folder. I've now flashed about 6 different versions of 3.53 and never had those extra '0' folders. I even have a backup of the MIUI rom which is 4.1.1 which I restored used for a while and then restored Jellybeer again and still didn't get any extra folders.
What version of CWM are you on? Mine is 6.0.2.1
Click to expand...
Click to collapse
SOLVED!!!
yiannisthegreek said:
This is not true my friend. See below for a reply I received from the "porter" of the ROM I am using right now - JellyBeer which is CM10.1 / JB4.2.+ based and he does NOT have this issue - nor do a lot of other people... See below...
Click to expand...
Click to collapse
Well HOLY MOLY I almost dont believe it... FINALLY I have a proper flash with NO extra / random /0 folders being created on my device!!!
So... What I've learned here and what I can recommend to anyone else who may be experiencing the issue I had is to ensure you update to the newest CWM that says it supports JB 4.2.+ ROMS like the one from here... http://forum.xda-developers.com/showthread.php?t=2000138 and then what I did was go to Settings> Storage> Misc Files and delete anything there that says "0". From there in the Settings Menu go to Personal> Backup and Reset> Reset all data and Format the device (yes you will lose info from your device so BACKUP before you do this). Now reboot to CWM and do a wipe cache, wipe dalvik and then wipe data/factory reset.
You will now have a FRESH starting point with NO traces of any 4.1.2 ROMS on the device and you can / should NOW be able to do as I did and flash as normal without these /0 folders being created any longer!
I believe after all of this that the issue was / is caused by trying to flash from 4.1.2 ROMS to 4.2.+ ROMS using an incompatible CWM like the chenglu v6.0.1.5 which is the one I used to ODIN Root and add CWM in one step so the real key here is to ensure you have a compatible CWM as I mentioned above.
Hope this may help others who are suffering with this issue!!!
yiannisthegreek said:
Well HOLY MOLY I almost dont believe it... FINALLY I have a proper flash with NO extra / random /0 folders being created on my device!!!
So... What I've learned here and what I can recommend to anyone else who may be experiencing the issue I had is to ensure you update to the newest CWM that says it supports JB 4.2.+ ROMS like the one from here... http://forum.xda-developers.com/showthread.php?t=2000138 and then what I did was go to Settings> Storage> Misc Files and delete anything there that says "0". From there in the Settings Menu go to Personal> Backup and Reset> Reset all data and Format the device (yes you will lose info from your device so BACKUP before you do this). Now reboot to CWM and do a wipe cache, wipe dalvik and then wipe data/factory reset.
You will now have a FRESH starting point with NO traces of any 4.1.2 ROMS on the device and you can / should NOW be able to do as I did and flash as normal without these /0 folders being created any longer!
I believe after all of this that the issue was / is caused by trying to flash from 4.1.2 ROMS to 4.2.+ ROMS using an incompatible CWM like the chenglu v6.0.1.5 which is the one I used to ODIN Root and add CWM in one step so the real key here is to ensure you have a compatible CWM as I mentioned above.
Hope this may help others who are suffering with this issue!!!
Click to expand...
Click to collapse
Thanx for reporting back.
That should help many :good:
yiannisthegreek said:
Well HOLY MOLY I almost dont believe it... FINALLY I have a proper flash with NO extra / random /0 folders being created on my device!!!
So... What I've learned here and what I can recommend to anyone else who may be experiencing the issue I had is to ensure you update to the newest CWM that says it supports JB 4.2.+ ROMS like the one from here... http://forum.xda-developers.com/showthread.php?t=2000138 and then what I did was go to Settings> Storage> Misc Files and delete anything there that says "0". From there in the Settings Menu go to Personal> Backup and Reset> Reset all data and Format the device (yes you will lose info from your device so BACKUP before you do this). Now reboot to CWM and do a wipe cache, wipe dalvik and then wipe data/factory reset.
You will now have a FRESH starting point with NO traces of any 4.1.2 ROMS on the device and you can / should NOW be able to do as I did and flash as normal without these /0 folders being created any longer!
I believe after all of this that the issue was / is caused by trying to flash from 4.1.2 ROMS to 4.2.+ ROMS using an incompatible CWM like the chenglu v6.0.1.5 which is the one I used to ODIN Root and add CWM in one step so the real key here is to ensure you have a compatible CWM as I mentioned above.
Hope this may help others who are suffering with this issue!!!
Click to expand...
Click to collapse
Hi I have exactly the same issue. Ive read how you solved it and have followed the same link but it seems to be for N7100. I am using GT-I9300 and am running Omega rom (latest version, 46.1). I have flashed a few roms today and have come back to omega since I like the samsung rom, but oh dear now there are a sh*tload of /0 folders just like you described. each time i flash it makes a new one ontop and uses it instead to store data etc. Do you think the CWM from your link will do the trick for me, or do I need one for I9300?
---------- Post added at 08:50 PM ---------- Previous post was at 08:09 PM ----------
yiannisthegreek said:
Well HOLY MOLY I almost dont believe it... FINALLY I have a proper flash with NO extra / random /0 folders being created on my device!!!
So... What I've learned here and what I can recommend to anyone else who may be experiencing the issue I had is to ensure you update to the newest CWM that says it supports JB 4.2.+ ROMS like the one from here... http://forum.xda-developers.com/showthread.php?t=2000138 and then what I did was go to Settings> Storage> Misc Files and delete anything there that says "0". From there in the Settings Menu go to Personal> Backup and Reset> Reset all data and Format the device (yes you will lose info from your device so BACKUP before you do this). Now reboot to CWM and do a wipe cache, wipe dalvik and then wipe data/factory reset.
You will now have a FRESH starting point with NO traces of any 4.1.2 ROMS on the device and you can / should NOW be able to do as I did and flash as normal without these /0 folders being created any longer!
I believe after all of this that the issue was / is caused by trying to flash from 4.1.2 ROMS to 4.2.+ ROMS using an incompatible CWM like the chenglu v6.0.1.5 which is the one I used to ODIN Root and add CWM in one step so the real key here is to ensure you have a compatible CWM as I mentioned above.
Hope this may help others who are suffering with this issue!!!
Click to expand...
Click to collapse
HAHA omw...i cannot believe this...I did exactly what you did to get it away...and it MADE ANOTHER /0 folder set! ive got 4 now...omw
yiannisthegreek said:
Well HOLY MOLY I almost dont believe it... FINALLY I have a proper flash with NO extra / random /0 folders being created on my device!!!
So... What I've learned here and what I can recommend to anyone else who may be experiencing the issue I had is to ensure you update to the newest CWM that says it supports JB 4.2.+ ROMS like the one from here... http://forum.xda-developers.com/showthread.php?t=2000138 and then what I did was go to Settings> Storage> Misc Files and delete anything there that says "0". From there in the Settings Menu go to Personal> Backup and Reset> Reset all data and Format the device (yes you will lose info from your device so BACKUP before you do this). Now reboot to CWM and do a wipe cache, wipe dalvik and then wipe data/factory reset.
You will now have a FRESH starting point with NO traces of any 4.1.2 ROMS on the device and you can / should NOW be able to do as I did and flash as normal without these /0 folders being created any longer!
I believe after all of this that the issue was / is caused by trying to flash from 4.1.2 ROMS to 4.2.+ ROMS using an incompatible CWM like the chenglu v6.0.1.5 which is the one I used to ODIN Root and add CWM in one step so the real key here is to ensure you have a compatible CWM as I mentioned above.
Hope this may help others who are suffering with this issue!!!
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I did the same and not sure but are you supposed to have two 0/ folder. I had three but now after running your fix above I only show one 0 folder under the emulated folder.. I also see a legacy folder with a 0 folder under it.. Is this normal. I'm using a TF101 Asus Transformer Tablet.
/0 folder after flashing!
Does anybody know how to make it so that the ROM flashes without making a /0 subfolder? Data form my previous ROM stays on the SD Card root, while the new ROM gets flashed into the /0 folder. The stuff on the root menu takes up space, so I'd like to install Paranoid Android on the root of my HTC One's SD Card. Any suggestion?
M-Dawg said:
Hi I have exactly the same issue. Ive read how you solved it and have followed the same link but it seems to be for N7100. I am using GT-I9300 and am running Omega rom (latest version, 46.1). I have flashed a few roms today and have come back to omega since I like the samsung rom, but oh dear now there are a sh*tload of /0 folders just like you described. each time i flash it makes a new one ontop and uses it instead to store data etc. Do you think the CWM from your link will do the trick for me, or do I need one for I9300?
---------- Post added at 08:50 PM ---------- Previous post was at 08:09 PM ----------
HAHA omw...i cannot believe this...I did exactly what you did to get it away...and it MADE ANOTHER /0 folder set! ive got 4 now...om
How could you have 4 when the directions clearly stated to manualy delete anything with a 0 before the Cwm wipes?
Click to expand...
Click to collapse
How can ZendroKat be got run without needing an SD card? Even in NAND version, kernel is loaded from sd (maybe recovery, too) - how can everything be transfered to internal memory and run from there?
Maheshwara said:
How can ZendroKat be got run without needing an SD card? Even in NAND version, kernel is loaded from sd (maybe recovery, too) - how can everything be transfered to internal memory and run from there?
Click to expand...
Click to collapse
Impossible without modifying FOTA or partition table (need to rebuild kernel).
And you'll get no external storage, not sure android can run without external storage.
Uhhhh, this means there is not any "real" NAND version of Android for Samsung Wave??? What do I need a NAND ROM, if I need a SD card anyway? Do not understand that...
Maheshwara said:
Uhhhh, this means there is not any "real" NAND version of Android for Samsung Wave??? What do I need a NAND ROM, if I need a SD card anyway? Do not understand that...
Click to expand...
Click to collapse
Full nand, nope, except if you change some lines of code, not a big deal but it need sources.
Loop rom (virtual partition on Nand), don't need sdcard (look at Badadroid.)
Does this loop ROM need Bada? Or is it independent?
Maheshwara said:
Does this loop ROM need Bada? Or is it independent?
Click to expand...
Click to collapse
Yes, it need bada 2. But, its dual boot, so you can run both android and bada side by side.
Maheshwara said:
Does this loop ROM need Bada? Or is it independent?
Click to expand...
Click to collapse
TheBasterd said:
Yes, it need bada 2. But, its dual boot, so you can run both android and bada side by side.
Click to expand...
Click to collapse
In fact, it don't really "need" bada (at least what is in nand), but it just need bada partition layout. You can install badadroid if your nand is formated with 3 fat partition, like in bada, you can also install it with any partition scheme if you change some lines of code in kernel. (It doesn't improve anything but you can have badadroid without bada on your phone, useless i know )
BenzoX said:
In fact, it don't really "need" bada (at least what is in nand), but it just need bada partition layout. You can install badadroid if your nand is formated with 3 fat partition, like in bada, you can also install it with any partition scheme if you change some lines of code in kernel. (It doesn't improve anything but you can have badadroid without bada on your phone, useless i know )
Click to expand...
Click to collapse
But, I think it is much better to have bada 2 as well, because the alpha android ROMS are not optimised to be daily drivers and hence it is much better to have dual boot. Dont you agree? SD Roms and Badroid are really cool for that reason.
TheBasterd said:
But, I think it is much better to have bada 2 as well, because the alpha android ROMS are not optimised to be daily drivers and hence it is much better to have dual boot. Dont you agree? SD Roms and Badroid are really cool for that reason.
Click to expand...
Click to collapse
Android is ready for daily use except it has crappy battery life. But it's of course better to have bada as a backup system.
You can have badadroid only but it's (almost) pointless.
BenzoX said:
Android is ready for daily use except it has crappy battery life. But it's of course better to have bada as a backup system.
You can have badadroid only but it's (almost) pointless.
Click to expand...
Click to collapse
True, the battery life is very poor, and installing apps takes ages!
You can have badadroid only but it's (almost) pointless.
Click to expand...
Click to collapse
Hmm.., then which ROM are you using? The other one that cannot be named?
TheBasterd said:
True, the battery life is very poor, and installing apps takes ages!
Hmm.., then which ROM are you using? The other one that cannot be named?
Click to expand...
Click to collapse
ICZen SD, Badadroid v4.4 and Bada Turko v10.2. Maybe i'll try android 4.4.3 rom by nima.yavari (it's badadroid based)
BenzoX said:
ICZen SD, Badadroid v4.4 and Bada Turko v10.2. Maybe i'll try android 4.4.3 rom by nima.yavari (it's badadroid based)
Click to expand...
Click to collapse
I thought ICZen SD and Badadroid v4.4 did not have compatible FOTA and bootfiles with each other .
TheBasterd said:
I thought ICZen SD and Badadroid v4.4 did not have compatible FOTA and bootfiles with each other .
Click to expand...
Click to collapse
Bootfiles are the same, and Fota just change kernel location, default boot and key combination.
Running converted GPE 4.4.4, stock rooted (recently followed steps to un-root), S-off (sunshine), Unlocked stock bootloader with CID: GOOGL001.
I received the OTA for 5.0.1 last week and received an error. Is there a way for me to install the OTA without wiping my phone?
I've spent the last week looking over the forums and haven't found an answer. Any help will be appreciated as I really want to avoid wiping to get the update if possible. Thanks!
Are you on stock recovery? I realize if you did the full conversion, it would have installed stock recovery. But just wanted to make sure you didn't flash a custom recovery after that.
Also, on the topic of wiping the phone, I would recommend backing up any important data in any case, if you don't already. There is never a guarantee against data loss even with an OTA; or just losing data from day to day usage for that matter.
Yea, I'm on stock recovery still. I was hoping to be done with too much modding and wanted to stay completely stock after the conversion, with the exception of root.
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?
Jamister989 said:
Yea, I'm on stock recovery still. I was hoping to be done with too much modding and wanted to stay completely stock after the conversion, with the exception of root.
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?
Click to expand...
Click to collapse
a recovery.log would be useful here to see where the ota fails.
pure guessing : I think if you've messed with the system partition (SDfix) it is likely what is causing your problem (infamous "unexpected content" error in recovery while installing ota).
I'll post one this evening. Where is a quick explaniation of how to the report?
Jamister989 said:
I'll post one this evening. Where is a quick explaniation of how to the report?
Click to expand...
Click to collapse
what do you mean by 'how to the report?' ?
Jamister989 said:
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?
Click to expand...
Click to collapse
If any system files have been altered by root, the OTA will fail. You either need to return the files to the exact "stock" condition, or re-install the stock ROM.
Sorry, what I meant was, how do I view the Recovery.log? I did a search in root browser and turned up nothing. Cache folder is empty.
The SD fix app should have made a back up copy of the original look in /etc/permissions and it's platform.xml the original will have original pre sdfix in the file name..
I had a failed attempt of OTA and it stated that my "platform.xml " was the reason.
Like @graffixnyc said only you you will have to rename the platform.xml to platform.bak and the platform.presdfix to platform.xml as it's the unmodified xml you need.
Jamister989 said:
Sorry, what I meant was, how do I view the Recovery.log? I did a search in root browser and turned up nothing. Cache folder is empty.
Click to expand...
Click to collapse
you can :
- reboot in recovery, try to apply ota, view the recovery.log in recovery menu, adb pull it and eventually post it....
- or assuming your issue is because of the modification of platform.xml as @graffixnyc and @jball stated, switch it with its backup (same dir) and then retry the ota.