Clockworkmod 6.x.x.x Flash Touch Recovery for Free - LG Nitro HD

CWM offers the volume rocker/sleep wake UI for the Nitro for free, available through ROM Manager. You can upgrade through ROM Manager for $1.99 to the touch interface (I had the touch interface in 5.8.x.x recovery).
But Clockworkmod offers the Touch Recovery .IMG for free here: http://goo.gl/iC5rz AS long as you're willing to download and do a couple lines of code, it is FREE.
Following the instructions here (http://goo.gl/X0Xwh) I got CWM Touch Recovery 6.0.1.5 working on my rooted AT&T Nitro HD (P930).
Code:
Backup your existing recovery:
1) [COLOR="Magenta"]cat /dev/block/mmcblk0p13 > /sdcard/recovery-backup.img[/COLOR]
Flash the new recovery by:
1) Download the recovery .img and rename it "recovery.img"
2) Copy the recovery.img to your /sdcard
3) Via terminal emulator or adb shell execute:
[COLOR="Magenta"]
su
cd /sdcard
cat recovery.img > /dev/block/mmcblk0p13[/COLOR]
All Done!
Now to Boot into recovery , press the vol down+pwr button , when it asks you to factory reset , tap twice the pwr button to confirm (dont worry it wont format your device)

Alright, so I know drumist brought this up in another thread, but I think it'd be better to continue the discussion here. 6.0.1.5 appears to have deficiencies in terms of backups. drumist said they actually completed for him after a long wait, but they weren't even finishing for me. He also stated that he was left with a large "blobs" folder about 400mb which I observed as well. So I did some research into things. I found that I was able to get a successful backup by rebooting to CWM, changing the backup type from dup to tar, and then initiating the backup. Afterward there was no residual blobs folder and it still took a damn long time, but I think that's probably because of the amount of data I have. It's been a long time since I've done a backup and I remember it taking quite a while before as well. If anybody discovers anything else interesting, feel free to post it here
I haven't worked up the courage to wipe my phone and restore the backup to see if that operation works properly.

Thanks for the note. I ran a backup and it seemed SLOW, but did complete. Looking in Astro File Manager the folder it produced under CWM Backups was very small 27 MB, compared to my last backup of 1.37 GB.
I hope to have time tomorrow morning and I will run a comparison. I'll run a backup using 6.0 Touch, 6.0 Recovery, and 5.8 Touch. I'll look at Time it takes, Battery it consumes, and File size of the Backup Folder.
Sent from my LG-P930 using xda app-developers app

ShadowOf said:
Thanks for the note. I ran a backup and it seemed SLOW, but did complete. Looking in Astro File Manager the folder it produced under CWM Backups was very small 27 MB, compared to my last backup of 1.37 GB.
I hope to have time tomorrow morning and I will run a comparison. I'll run a backup using 6.0 Touch, 6.0 Recovery, and 5.8 Touch. I'll look at Time it takes, Battery it consumes, and File size of the Backup Folder.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Not that small if you look at the "blobs" folder

noemtfj said:
Not that small if you look at the "blobs" folder
Click to expand...
Click to collapse
Forgive my ignorance. Is the BLOBS folder new to the 6.0 backups? Or was it around in 5.8?

ShadowOf said:
Forgive my ignorance. Is the BLOBS folder new to the 6.0 backups? Or was it around in 5.8?
Click to expand...
Click to collapse
It's new in 6.0.
If my understanding is correct, the blobs folder is a deliberate way to reduce the size of multiple backups on the SD card. It's actually a good idea IMO, and the problem isn't that it uses the blobs. The problem is that the backup just takes forever and, in Malnilion's case, didn't work at all.
Personally I'd just recommend people who already have 5.8.2.0 installed to just leave it for the time being.

drumist said:
Personally I'd just recommend people who already have 5.8.2.0 installed to just leave it for the time being.
Click to expand...
Click to collapse
I agree. I upgraded to 6.0 Touch yesterday and performed a backup, which created a Backup folder and the Blobs folder. Deleting the backup in CWM does not delete the Blobs folder, so if you downgrade from 6.0 to 5.8 you can manually delete the Blobs folder to free up space.
To compare, in order, I cleaned cache, fixed permissions, flashed new recovery, cleaned cache, fixed permissions, booted to recovery and created a new backup, which I deleted after measuring (then I repeated this procedure for the next recovery). And here are my results:
5.8.2.0 Touch Recovery
Backup Folder Size - 1.43GB
Blobs Folder Size - N/A (0MB)
Battery Usage - 6%
Time Elapsed - 11 minutes
6.0.1.5 Touch Recovery
Backup Folder Size - 30MB
Blobs Folder Size - 1.33GB
Battery Usage - 19%
Time Elapsed - 42 minutes
6.0.1.5 Recovery
Backup Folder Size - 30MB
Blobs Folder Size - 1.32GB
Battery Usage - 19%
Time Elapsed - 38 minutes
The folder size totals in 6.0 are smaller than in 5.8, 1.36GB compared to 1.43GB. I did not do multiple back ups, so I don't know how the filesize would grow, but it sounds like two backups would be 2x the size, but with 6.0 it would be significantly smaller, depending how much of the system/data changed. For me the smaller filesize does not make it worth waiting 30 extra minutes. I'll stay with 5.8.2.0 as well.

I just want to throw this out there to everyone and reiterate that it appears 6.x CWM introduced a new backup method called dup whereas previously tar was the only option. dup is set to be default and appears to be what is buggy for our devices, but if you manually reboot to CWM there's a setting to change your backup type back to tar. I just ran a backup initiated through Rom Manager and it did a tar backup that completed with no issues, so it appears that once you change the setting to tar, it's saved for future backups. You don't end up with a blobs folder either.
Edit, read this post from our man koush for more info.

Do not install CWM 6.0.1.5 or 6.0.1.4!!! It can't mount and format partitions so it can't install zip's - bootloop.

I bricked phone with 6.0.1.5 and 6.0.1.4 (cant mount partotions), but from 10F touch version installed fine. Also adb sideload does not work for me.

thanks alot
thanks alot for instructions code

Cannot go to recovery
Hey guys!
I'm a new-bie with LG Nitro HD. I cannot go to Recovery even though I do the same things as instruction. I search through Google and XDA but there's no help. Anyone help me! I feel nearly disappointed! :crying:
long time no see ~~~
su
cd /sdcard
cat bc64-recovery.img > /dev/block/mmcblk0p13

LeAnhTuan2505 said:
Hey guys!
I'm a new-bie with LG Nitro HD. I cannot go to Recovery even though I do the same things as instruction. I search through Google and XDA but there's no help. Anyone help me! I feel nearly disappointed! :crying:
long time no see ~~~
su
cd /sdcard
cat bc64-recovery.img > /dev/block/mmcblk0p13
Click to expand...
Click to collapse
What is the name of your .IMG? Is it "bc64-recovery.img" at the root of your sdcard? Remember to save the .IMG to the SDcard root, and rename it. I recommend "recovery.img" but anything is fine as long as your terminal command matches.
Sent from my LG-P930 using xda app-developers app
Update: The first backups where long ~40 minutes. Subsequent backups have been about half that at ~20 minutes. Still longer than 5.8xxx, at 11 minutes. But the total filesize is smaller if you keep multiple backups.

Related

Interesting Experience with CWM Recover 6.0.2.3

I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
solidhound said:
I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
Click to expand...
Click to collapse
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
milky1112 said:
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
Click to expand...
Click to collapse
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
solidhound said:
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
Click to expand...
Click to collapse
That is very possible, still odd that it will not let you delete even with R/W permissions set. But as long as everything is working.. Then i wouldn't fuss too much
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks for clarification Ed. I've been on TPR for a while so haven't flashed any 4.2 roms.
edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
hey edfunkycold,
thanks a ton for the response and clarification! i was thinking about swapping recoveries but i already reverted back to the original nandroid image i had at that point.
and you are correct. i was on 4.1 and not 4.2. i didn't know such changes were made but its great to see dual boot is coming up.
i will make sure to THANK both responses once i reach 10 posts. i'm trying hard to participate in these forums but haven't had time until recently.

I think CWM screwed me

I should be able to flash a backup I made with CWM recovery in CWM recovery, correct? Or would I have to adb push it?
I moved to 4.2.1 but not a fan of it at this point and want to go back using a backup (4.1.2) I made with CWM, but it won't flash. So at this point I'm trying to save my photos, notes, texts, and my titanium backup of apps and do a complete wipe using wugs (unroot/relock then reroot/unlock). Or should I be able to get away with just doing a format on my sdcard/system/cache/data and data/media (options in CWM)? Since going to 4.2.1 I have also lost a significant amount of free space.
BTW I have tried TWRP before and went back because I didn't like the layout but damn if your recovery can't even handle its own backups what the hell is it good for? TWRP here I come again.
you know it moves everything to a folder called 0 on the internal memory, right...?
A lot of the following is probably overkill but what I'd do is...
1. Backup everything I wanted to keep when in Android 4.2.1 onto my PC (Nandroid backups, photos, music, etc.)
2. Flash the factory 4.1.2 image
3. Boot up to make sure it's working
4. Restore nandroid in CWM
Chances are there are easier ways of doing this but I'd be happy knowing that is 100% right then have the potential for it going wrong
derekwilkinson said:
you know it moves everything to a folder called 0 on the internal memory, right...?
Click to expand...
Click to collapse
Bud I have tried to flash it out of every folder I have access to in CWM Recovery
The folder's I have tried, after choosing install zip from sdcard:
sdcard/0/clockworkmod/backup/ - 4 backups in here but wont flash any of them - says no files found when I try to flash one
sdcard/clockworkmod/backup/ - can actually see 2 backups in here (ones I don't want, just wanted to see where they were placed in 4.2)
sdcard/legacy/ - no files found
But stupid me did just realize the CWM backups I have been creating aren't zips? So I need to figure out how to get to sdcard/clockworkmod/backup and place my backup folders here. So I will be able to see them when I choose Backup and Restore - Restore
CWM can't see the backups in the '0' folder, it stores them on /data/media (or is it /media/data??) so unless you have a file manager with root access you won't get them back
EddyOS said:
CWM can't see the backups in the '0' folder, it stores them on /data/media (or is it /media/data??) so unless you have a file manager with root access you won't get them back
Click to expand...
Click to collapse
My my my you are the man. It looks like it is data/media/clockworkmod/backups.
I am going to try to Restore my latest 4.1.2 nandroid tonight, after I had a chance to back every thing up, but I'm guessing it's going to keep the current file structure though.
The best way to upgrade to 4.2.1 from 4.1.2 is
1.Flash all factory images from fastboot apart from recovery,@ recovery step flash twrp 2.3.3.0 and you are all set to no '/0' bug,
2. Downgrade to 4.1.2 ? Flash factory images of 4.1.2 , just keep the recovery as twrp 2.3.3.0, at present it is the best possible recovery for maguro for handling the '/0' bug , it doesnot delete the layout file.
And restoring nandroids in between the versions can make every file very clumsy, take some time and flash stock images to get rid of that.
BaMaDuDe87 said:
My my my you are the man. It looks like it is data/media/clockworkmod/backups.
I am going to try to Restore my latest 4.1.2 nandroid tonight, after I had a chance to back every thing up, but I'm guessing it's going to keep the current file structure though.
Click to expand...
Click to collapse
After downgrading you will still have the /0/ folder with all data. So many apps wont recognize that the backups are there available to be restored. You can just point to the "new" backup location that now exists in the /0/ directory.
Example: Titanium backup will tell you there is no restore data unless you go into preference and point it to the right folder in /0/.
Example 2: Nova launcher will not see the backups. Manually move them via Root explorer or similar from the /0/data/ to the /data/
..and so on.
I guess I will be flashing the factory image then.
1. Backup everything I need/want (photos, notes, sms, and grab latest copy of titanium backup folder)
2. Format system/cache/sdcard just because
3. fastboot - factory image (4.1.2)
4. Phone should still be unlocked/rooted (on current bootloader/radios correct?)
5. fastboot - twrp
5. Restore everything else
Or use Wugs to take back to stock, then fastboot unlock, root, add CWM recovery might be the easier way at this point. Restore nandroid and everything else. Then add TWRP and remove CWM.
Sorry trying to talk this out with you guys and wrap my head around what I am in for. I know it's not hard, just frustrating to think I could possibly lose some things.
Better Recovery TWRP
BaMaDuDe87 said:
I guess I will be flashing the factory image then.
1. Backup everything I need/want (photos, notes, sms, and grab latest copy of titanium backup folder)
2. Format system/cache/sdcard just because
3. fastboot - factory image (4.1.2)
4. Phone should still be unlocked/rooted (on current bootloader/radios correct?)
5. fastboot - twrp
5. Restore everything else
Click to expand...
Click to collapse
Not to be bossy but the latest version of TWRP seems to do a better job handling user folder /0. Its also touchscreen and [email protected]$$ so there is really no comparison....:highfive:
Yea I tried it, thought I was more comfortable with CWM and this bit me in the ass, so TWRP it is when I get everything straightened out

[RECOVERY] TWRP 2.6.0.0 touch recovery [2013-07-08]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Link: TWRP 2.6.0.0 LS970 FLASHABLE
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
OTHER DOWNLOAD METHODS:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client
THANKS TO :
Dees_Troy
TWRP TEAM
AutoPrime
not trying to jack posts but we didn't get any love... :crying:
Just an FYI/Headsup.
Encryption does not restore data. If you restore an encrypted backup, it'll fail. And when you bootup, you'll have system with no data. I just tried this.
---------- Post added at 02:22 PM ---------- Previous post was at 02:07 PM ----------
Compression seems to work now though.
I don't understand why after all these updates, it still labels the folders with the wrong date...from before the internet even existed lol. Now the button to change the name of the file right before you start the backup is gone, so I'll have to rename it later. Just curious, figured it would have been fixed a couple updates ago. But I do appreciate you doing what you do...makes life much easier for us who can't.
stealth919 said:
I don't understand why after all these updates, it still labels the folders with the wrong date...from before the internet even existed lol. Now the button to change the name of the file right before you start the backup is gone, so I'll have to rename it later. Just curious, figured it would have been fixed a couple updates ago. But I do appreciate you doing what you do...makes life much easier for us who can't.
Click to expand...
Click to collapse
Press the name button at the top. It got moved because of encryption, i think. As for the date, i get about 75% of the dates right. Very strange.
Sent from my LG-LS970 using xda premium
OK cool I'll try that next time I'm in there. Yeah mine likes 1970 lmao, before I was even born.
is there another way to install this? seems that all of a sudden my 2.5 wont even see the flash file, for this and even some kernels i tried to flash
Goomanager, says there is no recovery available for my device. Im currently on Dirty Unicorns.
How did you guys update from TWRP 2.5 to TWRP 2.6?
Did anybody use GooManager or did your flash the file above?
EFEXR said:
Goomanager, says there is no recovery available for my device. Im currently on Dirty Unicorns.
How did you guys update from TWRP 2.5 to TWRP 2.6?
Did anybody use GooManager or did your flash the file above?
Click to expand...
Click to collapse
I always noticed goo was behind the times for the lgog. so i just go to the twrp site and grab the file.
Help
Hello Guys, I by accident formatted the phone. I Have functioning TWRP, but I have no idea as to how get a flashable zip to the phone any pointers.
thanks
nemssn4cer said:
Hello Guys, I by accident formatted the phone. I Have functioning TWRP, but I have no idea as to how get a flashable zip to the phone any pointers.
thanks
Click to expand...
Click to collapse
Here is the help you seek. http://forum.xda-developers.com/showthread.php?p=36270473
Sent from my LG-LS970 using xda premium
Engine, thank you for the assist
Sent from my LG-LS970 using xda premium
nemssn4cer said:
Engine, thank you for the assist
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Anytime. Glad to help.
On another note, I think I found more flaws in 2.6.0.0
While it WILL make Backups, and Restore just fine, It WILL NOT save the TWRP files to your computer. It backs up boot.emmc.win and boot.emmc.win.md5, but nothing else.
I'm alittle paranoid with this phone for messing things up. So I back up EVERYTHING I can to my computer to save my as$.
Just another FYI
EDIT. Reinstalling 2.6.0.0 still has same problem.
Installing 2.5.0.0 works as it should. So back to 2.5.0.0 for me
Thanks!!
sent from my fingers to your face.
engine95 said:
Anytime. Glad to help.
On another note, I think I found more flaws in 2.6.0.0
While it WILL make Backups, and Restore just fine, It WILL NOT save the TWRP files to your computer. It backs up boot.emmc.win and boot.emmc.win.md5, but nothing else.
I'm alittle paranoid with this phone for messing things up. So I back up EVERYTHING I can to my computer to save my as$.
Just another FYI
EDIT. Reinstalling 2.6.0.0 still has same problem.
Installing 2.5.0.0 works as it should. So back to 2.5.0.0 for me
Click to expand...
Click to collapse
In addition to that, it seems that TWRP backups on 2.6.0.0 are saved somewhere other than where they are usually saved, i cant seem to even find the new backups on the sd card. but now that you mention it i should also start backing up to my computer on account of my battery recently got fried and i lost all my hard work when i had to get a new phone sucks not having a micro sd card or removable battery
kMogs17 said:
In addition to that, it seems that TWRP backups on 2.6.0.0 are saved somewhere other than where they are usually saved, i cant seem to even find the new backups on the sd card. but now that you mention it i should also start backing up to my computer on account of my battery recently got fried and i lost all my hard work when i had to get a new phone sucks not having a micro sd card or removable battery
Click to expand...
Click to collapse
It is a pain not having and sd, no doubt. All the more reason to copy to the computer also.
Anyway, do you have the"0" folder? My backups were in the same location. But I also run both Stockish and CM Roms. So TWRP always backs up to the same location. Have you recently started running CM Roms?
Sent from my LG-LS970 using xda premium
engine95 said:
It is a pain not having and sd, no doubt. All the more reason to copy to the computer also.
Anyway, do you have the"0" folder? My backups were in the same location. But I also run both Stockish and CM Roms. So TWRP always backs up to the same location. Have you recently started running CM Roms?
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
I do have the 0 folder but i run cm roms pretty exclusively only flash to stock if absolutely necessary. anyhow i finally found the backup location for 2.6 in /data/media/TWRP . hope this will help others looking for it as i was. on a side note i heard that if you adb pull the backup to your computer you may not get permission issues and it should copy all the files from the backup. i havent tried it tho

[Q] Hard to find stable ROMs...

Good morning. I registered in this forum some months back (don't remember when) when I was searching for some good ROMs for my GIO S5660.
I ultimately gave up because I couldn't find enough information about flashing (I think it was because the threads gave bad links to odin, or I could only find that specific odin version if I googled because the link's version were outdated/updated). Either way I gave up because smartphones and flashing were (and are) very new to me and I didn't want to risk bricking the phone (although I'm finishing my degree in Computer Science, so some concepts aren't alien to me).
I came back now, decided to find a STABLE and GOOD ROM, with the best battery life I can get. I usually check the screenshots thread and choose the ones that I like the most, normally CM9 or better. Problem is, I spent these past few hours on several of GIO sub-forums (http://forum.xda-developers.com/forumdisplay.php?f=1404), searching and scavenging for something I could use or like. It's been very hard, almost all of them have some kind of major problem, like in-call microphone, wireless, deep sleep, something like that.
Am I chasing wild gooses here? Should I be looking instead at CM7 and earlier versions?
On a closing note, I still have 2.3.3 Portuguese version that came with the phone. Can I update safely through the phone's preferences? Main reason I am looking to flash is because of its battery life: if i charge it to 100%, then proceed to use any kind of program/game with the lowest light settings, it can drop to 50% in a matter of minutes. Its speed isn't that great as well.
Thank you for your time, would be great if anyone could help me.
Flame86 said:
Good morning. I registered in this forum some months back (don't remember when) when I was searching for some good ROMs for my GIO S5660.
I ultimately gave up because I couldn't find enough information about flashing (I think it was because the threads gave bad links to odin, or I could only find that specific odin version if I googled because the link's version were outdated/updated). Either way I gave up because smartphones and flashing were (and are) very new to me and I didn't want to risk bricking the phone (although I'm finishing my degree in Computer Science, so some concepts aren't alien to me).
I came back now, decided to find a STABLE and GOOD ROM, with the best battery life I can get. I usually check the screenshots thread and choose the ones that I like the most, normally CM9 or better. Problem is, I spent these past few hours on several of GIO sub-forums (http://forum.xda-developers.com/forumdisplay.php?f=1404), searching and scavenging for something I could use or like. It's been very hard, almost all of them have some kind of major problem, like in-call microphone, wireless, deep sleep, something like that.
Am I chasing wild gooses here? Should I be looking instead at CM7 and earlier versions?
On a closing note, I still have 2.3.3 Portuguese version that came with the phone. Can I update safely through the phone's preferences? Main reason I am looking to flash is because of its battery life: if i charge it to 100%, then proceed to use any kind of program/game with the lowest light settings, it can drop to 50% in a matter of minutes. Its speed isn't that great as well.
Thank you for your time, would be great if anyone could help me.
Click to expand...
Click to collapse
Buy a new battery and try AOSP GINGERBREAD 2.3.7 :highfive:
Flame86 said:
Good morning. I registered in this forum some months back (don't remember when) when I was searching for some good ROMs for my GIO S5660.
I ultimately gave up because I couldn't find enough information about flashing (I think it was because the threads gave bad links to odin, or I could only find that specific odin version if I googled because the link's version were outdated/updated). Either way I gave up because smartphones and flashing were (and are) very new to me and I didn't want to risk bricking the phone (although I'm finishing my degree in Computer Science, so some concepts aren't alien to me).
I came back now, decided to find a STABLE and GOOD ROM, with the best battery life I can get. I usually check the screenshots thread and choose the ones that I like the most, normally CM9 or better. Problem is, I spent these past few hours on several of GIO sub-forums (http://forum.xda-developers.com/forumdisplay.php?f=1404), searching and scavenging for something I could use or like. It's been very hard, almost all of them have some kind of major problem, like in-call microphone, wireless, deep sleep, something like that.
Am I chasing wild gooses here? Should I be looking instead at CM7 and earlier versions?
On a closing note, I still have 2.3.3 Portuguese version that came with the phone. Can I update safely through the phone's preferences? Main reason I am looking to flash is because of its battery life: if i charge it to 100%, then proceed to use any kind of program/game with the lowest light settings, it can drop to 50% in a matter of minutes. Its speed isn't that great as well.
Thank you for your time, would be great if anyone could help me.
Click to expand...
Click to collapse
The most stable rom currently for our gio is the Enhanced236. I really recommend you reading as much as you can before doing anything, both about android and flashing, but also basic XDA stuff. Read these "threads", and you're good to go! 1. 2. 3. 4. 5. 6.
Phuuu.. All done? Let's flash that ROM! Wohoooooo.. :victory:
Wait! You need a backup before continuing. :good: Since you doesn't have root or custom recovery, you can't use CWM to make a nandroid. One way to backup your stuff is to use a program called Ultimate Backup Tool. This program doesn't need root or custom recovery. It works on Windows, Mac and Linux. :highfive:
Now we can flash the custom rom! :laugh:
If you wanna install Enhanced236 (the most bugfree one), you need to install install cwm, Clock Work Mod, first. How to:
1. Make sure that you have fully charged your battery.
2. You need to download the ext4only 5.0.2.7 cwm version, here http://forum.xda-developers.com/showthread.php?t=1421650.
3. After you have downloaded the zip, you go into recovery mode, in this case stock recovering. You do that by holding The Home Button + Power Button until the recovery gets visible.
4. Then you do click on the Apply update from sdcard, and select the cwm zip.
5. After you have flashed the zip, you should reboot your device. Here's a YouTube video on the installation process: www.youtube.com/watch?v=hxjxB8P9rSU
6. After you have done that, I recommend you to take a nandroid backup. The backup will be stored on your sdcard, so you can copy the backup to your computer if you want to, just in case.
Now you have installed CWM. Let's install the ROM!
7. Download the enhanced236 from this thread. Copy the zip to the root of your sd-card, and then go into CWM. Wipe data/factory reset. After that, wipe the cache partition. NOTE! This will erase everything you have done on your phone, so make sure that you have a backup ready! After that, click on the install zip from sd-card, choose the enhanced236_06.08.2012.zip and flash it. Just follow the instructions that pops up, and then restart your phone. Leave it booting/waiting for like 5 min, and then start touching/configure the device. After doing the necessary configuring, wait another minute. And reboot. And then it's done! :victory:
And if you have any questions, just ask! I'm glad to help! :laugh:
Regards,
X-Zone
Thank you guys! At the moment I can't, but later at home I will pay closer attention to X-zone's post (I'm @ work).
From what I've read, I'll need the USB cable, or some kind of microSD USB drive, right? I actually rooted the phone almost a year ago, since I found very good info in its thread
@PanDeGengibre
Do I really need a new battery? ;n;
Flame86 said:
Thank you guys! At the moment I can't, but later at home I will pay closer attention to X-zone's post (I'm @ work).
From what I've read, I'll need the USB cable, or some kind of microSD USB drive, right? I actually rooted the phone almost a year ago, since I found very good info in its thread
@PanDeGengibre
Do I really need a new battery? ;n;
Click to expand...
Click to collapse
I think yeah your battery drains very fast!
Flame86 said:
Thank you guys! At the moment I can't, but later at home I will pay closer attention to X-zone's post (I'm @ work).
From what I've read, I'll need the USB cable, or some kind of microSD USB drive, right? I actually rooted the phone almost a year ago, since I found very good info in its thread
@PanDeGengibre
Do I really need a new battery? ;n;
Click to expand...
Click to collapse
You need a usb cable to transfer the roms and that kind of stuff. You can also use a micro SD reader if you want.
BTW I don't think you need to buy a new battery, you must calibrate it once a month or so. Calibrate it and see if that works!
Sent from my GT-S5660
X-zone said:
The most stable rom currently for our gio is the Enhanced236. I really recommend you reading as much as you can before doing anything, both about android and flashing, but also basic XDA stuff. Read these "threads", and you're good to go! 1. 2. 3. 4. 5. 6.
Phuuu.. All done? Let's flash that ROM! Wohoooooo.. :victory:
Wait! You need a backup before continuing. :good: Since you doesn't have root or custom recovery, you can't use CWM to make a nandroid. One way to backup your stuff is to use a program called Ultimate Backup Tool. This program doesn't need root or custom recovery. It works on Windows, Mac and Linux. :highfive:
Now we can flash the custom rom! :laugh:
If you wanna install Enhanced236 (the most bugfree one), you need to install install cwm, Clock Work Mod, first. How to:
1. Make sure that you have fully charged your battery.
2. You need to download the ext4only 5.0.2.0 cwm version, here http://forum.xda-developers.com/showthread.php?t=1421650.
3. After you have downloaded the zip, you go into recovery mode, in this case stock recovering. You do that by holding The Home Button + Power Button until the recovery gets visible.
4. Then you do click on the Apply update from sdcard, and select the cwm zip.
5. After you have flashed the zip, you should reboot your device. Here's a YouTube video on the installation process: www.youtube.com/watch?v=hxjxB8P9rSU
6. After you have done that, I recommend you to take a nandroid backup. The backup will be stored on your sdcard, so you can copy the backup to your computer if you want to, just in case.
Now you have installed CWM. Let's install the ROM!
7. Download the enhanced236 from this thread. Copy the zip to the root of your sd-card, and then go into CWM. Wipe data/factory reset. After that, wipe the cache partition. NOTE! This will erase everything you have done on your phone, so make sure that you have a backup ready! After that, click on the install zip from sd-card, choose the enhanced236_06.08.2012.zip and flash it. Just follow the instructions that pops up, and then restart your phone. Leave it booting/waiting for like 5 min, and then start touching/configure the device. After doing the necessary configuring, wait another minute. And reboot. And then it's done! :victory:
And if you have any questions, just ask! I'm glad to help! :laugh:
Regards,
X-Zone
Click to expand...
Click to collapse
Great tutorial,
Followed but flashed 5.0.2.7 (didn't find 5.0.2.0), and now the recovery seems to be only partially working.
I can boot to it, but if I press "flash zip" it only appears the cwm logo, any idea?
skinniezinho said:
Great tutorial,
Followed but flashed 5.0.2.7 (didn't find 5.0.2.0), and now the recovery seems to be only partially working.
I can boot to it, but if I press "flash zip" it only appears the cwm logo, any idea?
Click to expand...
Click to collapse
Tap the menu button on gio
skinniezinho said:
Great tutorial,
Followed but flashed 5.0.2.7 (didn't find 5.0.2.0), and now the recovery seems to be only partially working.
I can boot to it, but if I press "flash zip" it only appears the cwm logo, any idea?
Click to expand...
Click to collapse
Sorry, typo. Meant 5.0.2.7. Fixed that now. When you click on something in cwm, like flash a zip, press the home button. Navigate up and down with the volume buttons.
Finally have the time to check it out.
X-zone said:
Wait! You need a backup before continuing. :good: Since you doesn't have root or custom recovery, you can't use CWM to make a nandroid. One way to backup your stuff is to use a program called Ultimate Backup Tool. This program doesn't need root or custom recovery. It works on Windows, Mac and Linux. :highfive:
Regards,
X-Zone
Click to expand...
Click to collapse
I have it rooted, but I don't have my USB cable, just a microSD adapter. Any other way to do the backup? maybe some application in Play Store that backups into the sdCard?
Flame86 said:
Finally have the time to check it out.
I have it rooted, but I don't have my USB cable, just a microSD adapter. Any other way to do the backup? maybe some application in Play Store that backups into the sdCard?
Click to expand...
Click to collapse
Titanium backup is a very powerful program on the google play store. The pro version (I recommend you buying it, it's worth it) backup things like your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card.
After you have installed CWM you can do a nandroid on your untouched system. You can always restore the nandroid if you don't like your new costum rom or if the installation crashes and "lite" bricks your phone.
X-zone said:
Titanium backup is a very powerful program on the google play store. The pro version (I recommend you buying it, it's worth it) backup things like your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card.
After you have installed CWM you can do a nandroid on your untouched system. You can always restore the nandroid if you don't like your new costum rom or if the installation crashes and "lite" bricks your phone.
Click to expand...
Click to collapse
Let me see if I understood:
1) Backup
This can be made before everything else, through Titanium backup (backs up my data into the sd card (probably in just one file that can be read after)), Ultimate Backup Tool (is installed in the computer, needs USB cable) or other similar programs
OR
Can also be made after CWM is installed, through something called "nandroid" <-(I read the pages you linked in this thread and didn't notice this name/concept, so I was confused)
2) Download ext4only 5.0.2.7 Clock Work Mod that is on page 1
3) Reach recovery mode, select apply update from sdcard, select the cwm.zip. This is "flashing" the phone
This here is where it started to get confusing to me; until I read several times your post, I thought that "apply update from sdcard" would actively install that zip, erasing everything else. What must happen instead is that, that zip installs the app inside, that will allow me to backup and format next.
4) Restart phone, run cwm.
This is where I can make the nandroid backup (as said previously, this got me confused because I thought that at this point the phone was already "empty", formatted)
5) Download the ROM I need/want/wtv, go to CWM then:
a) Wipe data/factory reset.
b) Wipe the cache partition. (note: this is the actual format)
c) Install zip from sd-card, choosing the ROM. (This is also flashing)
*easy part:*
6) Follow the instructions on screen and then restart phone
7) Wait some time for the boot then configure it. After that, wait a minute more then restart again. DONE!
Did I miss anything? If not and this is it, where is the risk in softbricking or hardbricking the phone? (yes, I'm actually scared, since this is my first time and I'm a noob at it, and I can't really risk screwing my smartphone, only in three months will I be able to replace it if anything happens)
Thank you for helping a (scared) noob!
Flame86 said:
Let me see if I understood:
1) Backup
This can be made before everything else, through Titanium backup (backs up my data into the sd card (probably in just one file that can be read after)), Ultimate Backup Tool (is installed in the computer, needs USB cable) or other similar programs
OR
Can also be made after CWM is installed, through something called "nandroid" <-(I read the pages you linked in this thread and didn't notice this name/concept, so I was confused)
2) Download ext4only 5.0.2.7 Clock Work Mod that is on page 1
3) Reach recovery mode, select apply update from sdcard, select the cwm.zip. This is "flashing" the phone
This here is where it started to get confusing to me; until I read several times your post, I thought that "apply update from sdcard" would actively install that zip, erasing everything else. What must happen instead is that, that zip installs the app inside, that will allow me to backup and format next.
4) Restart phone, run cwm.
This is where I can make the nandroid backup (as said previously, this got me confused because I thought that at this point the phone was already "empty", formatted)
5) Download the ROM I need/want/wtv, go to CWM then:
a) Wipe data/factory reset.
b) Wipe the cache partition. (note: this is the actual format)
c) Install zip from sd-card, choosing the ROM. (This is also flashing)
*easy part:*
6) Follow the instructions on screen and then restart phone
7) Wait some time for the boot then configure it. After that, wait a minute more then restart again. DONE!
Did I miss anything? If not and this is it, where is the risk in softbricking or hardbricking the phone? (yes, I'm actually scared, since this is my first time and I'm a noob at it, and I can't really risk screwing my smartphone, only in three months will I be able to replace it if anything happens)
Thank you for helping a (scared) noob!
Click to expand...
Click to collapse
When you install CWM your phone will not be completely wiped. Only the recovery "partition" will be replaced with CWM instead of the almost useless stock recovery. Here's some info about nandroid. 1.. The Ultimate Backup Tool/Titanium backup was just if the cwm installation goes wrong and and "soft" bricks your phone. This will most likely not happen. Note that there is several methods to unbrick the gio if this happens, so be calm! lol
X-zone said:
When you install CWM your phone will not be completely wiped. Only the recovery "partition" will be replaced with CWM instead of the almost useless stock recovery. Here's some info about nandroid. 1.. The Ultimate Backup Tool/Titanium backup was just if the cwm installation goes wrong and and "soft" bricks your phone. This will most likely not happen. Note that there is several methods to unbrick the gio if this happens, so be calm! lol
Click to expand...
Click to collapse
Yeah, hehe.
About titanium backup, how does it work exactly? Does it need a working ROM (preferably the same type as the backup was made on) so it can restore what was previously backed up? Or is like nandroid, it can be restored via CWM?
I read your link about nandroid; it seems pretty easy to grasp: recovery mode and restore backup. What about Titanium backup? It seems to me it is unable to backup the entire phone (it would also make sense since it runs on Android)
I've read about Titanium backup here: http://www.addictivetips.com/mobile/how-to-use-titanium-backup-for-android-complete-guide/
Flame86 said:
Yeah, hehe.
About titanium backup, it is the same as nandroid?
I read the link and it turns out I understand very well the concept; my question here, is then, what is the difference between the two? How can I use Titanium backup in case something goes wrong?
Nandroid seems pretty easy to grasp: recovery mode and restore backup. What about Titanium backup? It seems to me it is unable to backup the entire phone (it would also make sense since it runs on Android)
I've read about Titanium backup here: http://www.addictivetips.com/mobile/how-to-use-titanium-backup-for-android-complete-guide/
Click to expand...
Click to collapse
Titanium backup only backups your user-data, which means that it doesn't backup your kernel, libs and stuff like that. If something happens while you install cwm (you accidentally drops your phone and the battery flies away and soft bricks your phone) you still have your contacts, levels cleard on angrybrids and stuff like that.
CWM nandroid it is then
So, while trying to make a nandroid, CWM "backup" option gives this error:
SD Card space free: 1707 MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Can't mount /system!
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Is this normal? :|
Erase cache partition? Or unselect cache in advanced?
Flame86 said:
So, while trying to make a nandroid, CWM "backup" option gives this error:
SD Card space free: 1707 MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Can't mount /system!
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Is this normal? :|
Erase cache partition? Or unselect cache in advanced?
Click to expand...
Click to collapse
Ohh... Sorry. You have installed the ext4only version. The stock rom uses rfs. Try install CWM signed_cwm-5.0.2.7-flashablezip-ext4+rfs.zip and then do a bakcup and then install ext4only, the costum rom uses ext4. And no, ext4 + rfs doesn't work that good with ext4.
X-zone said:
Ohh... Sorry. You have installed the ext4only version. The stock rom uses rfs. Try install CWM signed_cwm-5.0.2.7-flashablezip-ext4+rfs.zip and then do a bakcup and then install ext4only, the costum rom uses ext4. And no, ext4 + rfs doesn't work that good with ext4.
Click to expand...
Click to collapse
So... when I'm at the cwm ext4only recovery mode and select apply update from the sdcard, it shows me a buttload of "no" options and only one "Yes - Install /sdcard/update.zip."
Like this
confirm install?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes - Install /sdcard/update.zip.
No
No
No
What the hell do I do?
Flame86 said:
So... when I'm at the cwm ext4only recovery mode and select apply update from the sdcard, it shows me a buttload of "no" options and only one "Yes - Install /sdcard/update.zip."
Like this
confirm install?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes - Install /sdcard/update.zip.
No
No
No
What the hell do I do?
Click to expand...
Click to collapse
Navigate with your volume buttons down to Yes - Install Bla bla and press the home button to confirm.

Damn you data! Problem with creating a backup.

Hello. As a happy owner of a DHD, I thought that I could try Kitkat, for one day or two, as I use my phone daily and a stable rom is a must.
For now I'm stuck with CM10.1, but I'm looking forward to the new release.
Anyway, I wanted to create a backup and neither CWM 5.8 Touch or TWRP 2.6.3 go past creating a backup of /data.
CWM just says Error: Could not back up image of /data or something like that, and TWRP says Backup Complete and Failed in red, below it.
Any ideas?
No, I don't have too much apps, TWRP says the ones I want to back up are as following:
Boot (4 MB)
Cache (76 MB)
Data (371 MB)
Android Secure (75 MB)
System (343 MB)
Over 10GB of free space on my microsd card (32GB, class 10), so it's not lack of space.
Help, I'd love to check out Kitkat and Ubuntu Touch...
Fix permissions
maltazar1 said:
Hello. As a happy owner of a DHD, I thought that I could try Kitkat, for one day or two, as I use my phone daily and a stable rom is a must.
For now I'm stuck with CM10.1, but I'm looking forward to the new release.
Anyway, I wanted to create a backup and neither CWM 5.8 Touch or TWRP 2.6.3 go past creating a backup of /data.
CWM just says Error: Could not back up image of /data or something like that, and TWRP says Backup Complete and Failed in red, below it.
Any ideas?
No, I don't have too much apps, TWRP says the ones I want to back up are as following:
Boot (4 MB)
Cache (76 MB)
Data (371 MB)
Android Secure (75 MB)
System (343 MB)
Over 10GB of free space on my microsd card (32GB, class 10), so it's not lack of space.
Help, I'd love to check out Kitkat and Ubuntu Touch...
Click to expand...
Click to collapse
First fix permissions in TWRP recovery advanced tab.. then try backing up again.. If u can boot use backup software like titanium backup to backup app data and settings... You can restore the settings too..
gkprashu said:
First fix permissions in TWRP recovery advanced tab.. then try backing up again.. If u can boot use backup software like titanium backup to backup app data and settings... You can restore the settings too..
Click to expand...
Click to collapse
I know about the possibility of using Titanium Backup, don't worry, the thing is that I wanted to see if I can just use the nand backup once, to make everything simpler.
I'll try the permissions and see, thanks for the tip
Edit:
Fixed permissions without problems, didn't work, same thing.

Categories

Resources