NOTE: I have searched and reviewed the existing threads on items with similar wording. Several on how to recover corrupted files within the backup etc.. Although the questions and issues are similar none describe the issue that I am experiencing.
Samsung Galaxy Note
Rooted on AOSP xXx FJ,(Flappjaxxx) / FJ Mod of ICS UCLF6
Currently on CWM Recovery 5.8.4.3
Situation:
No prior issues experience with nandroid backup, had 2 other backups plus the one I'm referring to (one of AOSP xXx and FJ Modded)
Performed a nandroid backup to try out CM09 from FJ AOSP. All went well... including the CM09 install and apps.
Missed the S-pen functionality and wanted to flip back to FJ Modded ROM.
Attempted to restore the most recent backup... Failed. Booted into CM09 and went to Root Explorer and looked into the backup file. I noticed that the file has a lot of what appears to be random ASCII characters for file names etc... (indicated to me that this file was corrupted).
Since I had other backups, I went to one of the older ones and restored.
Problem: this corrupted backup is taking up about 1.9 GB and I want to delete but it will not allow me. Looked at permissions and it has RW
Question: how the heck do I delete this thing without having to take my SD card out and formatting the sucker?
Thanks in advance
You should be able to plug in your phone to your computer via USB and open folder to view files on the /sdcard. Make sure USB connection is set to "USB Mass Storage" option when connected. Once you opened the folder to view files, you can navigate to the clockworkmod folder, open, and find the backups within that folder and delete that way...
Sent from my MB865 using xda's premium carrier pigeon service
Did you try to delete it in recovery (sorry if there is no such option, never looked for it...) or in root explorer? You could always get a terminal like https://play.google.com/store/apps/details?id=jackpal.androidterm and do like this:
su (if you're rooted)
cd /sdcard/clockworkmod/backup
rm -r 2012-07-12.13.37
Same commands should work in adb as well
Try. Android Commander.
jje
Sent from my GT-I9300 using xda premium
I think that plugging the USB charger into your computer and manually deleting it should do the trick :fingers-crossed:
OK...
Thanks guys for your responses...
- did try connecting to a PC in mass storage mode and tried to delete... did not work
- use Root Explorer to do a delete as well... did not work
- looked to see if there was a delete option in recovery (first thing I looked for) did not find it
I'll try the other options and see where that goes.
JohnnyQ1964 said:
Thanks guys for your responses...
- did try connecting to a PC in mass storage mode and tried to delete... did not work
- use Root Explorer to do a delete as well... did not work
- looked to see if there was a delete option in recovery (first thing I looked for) did not find it
I'll try the other options and see where that goes.
Click to expand...
Click to collapse
If you download clockwork mod (rom manager) you can delete it in the android application in manage and restore backups.
Empty recycle bin on PC sometimes helps when deleted stuff sticks, make sure do this when plugged in ofc
If you're using Windows, run chkdsk ("Scan this drive for errors" in drive's properties) when connected as a mass storage device.
That should help.
If it won't, the guaranteed method is to copy the files you need somewhere else, format the card and put those files back.
to clairfy, you were able to locate the back up files in the folder "clockwork mod-backup" but then it would not delete when you tried?"
Thanks again for all your input.
PC crapped out this past weekend... new hdd installed and re-building with Windows 7 pro-64 (hmmm... maybe I should dual boot to Ubuntu), will need to reinstall some of the linux/android tools.
@frdd... already had terminal installed tried the commands but no luck... it reports back I'm missing files and i get a lot of errors. I guess I'm gonna have to learn Linux/Android
@icomrade... I've got the purchase ver of ROM Manager and haven't fully gone down that rabbit hole but will investigate
@NeverGone\RU... will leave that as a last resort as i've got a 32GB SD card (sucks up time)
@mankows5... yes did find all the directories and files as it should be... just can't delete that 1 backup
Yeah, try Rom manager. Manage and Restore Backups>Select the one you want to delete, then delete it.
Related
I been playing with my phone for a few days now trying to get it to work and I haven't had much success although I have been learning a hole bunch and now able to load any rom onto my phone easily and flash kernels and such with ease...
The situation is that I received a phone from a friend SGSII I have never had a rooted phone and it came pre rooted, never knew much about it as it is my first Android phone and now love it
never knowing I had to do these things like "backup EFS directory" and such as I know now... anyhow, a few days ago what has happened is I have a stock rom + CF-Root and my phone all a sudden started telling me there is no IMEI and no SIM card present.. after much research, flashing of roms, kernels, bricking the phone, re flashing and so on and so foth....... xda-developers is a FANTASTICK site full of useful information btw now I'm still at the same point but a lot more knowledgeable, I have learned that the problem lies with my efs folder and have found a .nv_data.bak file that is dated dec 31 of last year, at this point it is my only so called backup and hope that it will restore proper functions of the phone, as per some of the guides and other posts and questions I have learned to do this.. so what I have done was copy using ADB my files to my sdcard folder renamed my nv_data.bin to nv_data.bak and my .nv_data.bak to nv_data.bin
also I have used root explorer to copy the hole efs folder to a location on my external sd card and used HC-kTool to make a backup of my efs folder
now I have been trying to use the command to copy my nv_data.bin file in the sdcard folder to my efs folder and it is not working as it gives me msges of write protected file or file exist canot copy... the commands I have been trying to use are
cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/
I have tried also
rm command to remove the file but nothing has been working...
one thing I should mention is that I have been connecting withough usb cable as I can't seem to connect with that I keep getting device not found so I been using the wireless adb function
abd connect "ip addressort"
I have tried installing the kies driver for usb and the google sdk drivers and none seem to work, in fact kies doesn't reconize my phone aswell... but Odin seems to function through my USB just fine.... not sure if that matters or not but trying to give as much info as possible
Thank you in advance for the help.... this is a great site with very knowledgeable ppl
permissions have to be reset as the back up does not copy the permissions. Use cwm recovery to reset the permissions.
Thank you very much for you quick response, however I have just tried that, booted into cwm recovery, went to advanced and reset permissions, rebooted my hone and still cannot copy the file
Try using a Root Explorer from the market.Connect via wifi obviously if your phone cant detect sim.Phone needs to be rooted.Give Root Explorer root permission and set to R/W from R/O and copy paste the nv.data files and IMEI to the efs folder in the root of your phone,reboot,boot to recovery and "fix permissions" and boot again.
sorry I guess I should of mentioned that aswell but thank you very much for the suggestion... I have tried to edit the file weather just delet it or overwrite or change permissions with Root Explorer and to no success.. also when I push the mount r/w button in the efs folder... nothing happens and the button stays as mount r/w
I found this.Maybe it will help.
http://forum.xda-developers.com/showthread.php?t=1258734
http://forum.xda-developers.com/showthread.php?t=1261948
http://forum.xda-developers.com/showthread.php?t=1085374
and if you manage to get it back then use this:
http://forum.xda-developers.com/showthread.php?t=1308546
Thank, I havent had time to read through them all but I will try tonight and see if I can come up with a solution... I will post here my findings weather they are good or bad..... but thank you very much for the info
I have read and tried and seen all those post, thankyou for the info the problem is still that I cannot modify my nv_data.bin file in any way... I cannot overwrite to it or anything using rootexplorer or adb or any other program... does anyone know of any other programs or command lines to strip the read only permissions on this file as it seems stuck on this and it's driving me insane lol
Gave up
I gave up and had it done professionally, they couldn't figure it out either and had to replace the phone.... Thank you all for the great help, even tho we didn't get it figured out it was great that help was provided
Thank you XDA-Developers your awesome!!
ive the same issue,got a rooted s2 with cwm all the forums cay copy the efe data but i cant find a way,anyone know how to do it?,i need to eddit it to unlock my phone:ie the simlock.
thanks
thank you for sharing your ideas
So I've made a couple Nandroid Backups and I am unable to find them in any of my directories. The reason I ask is because I'd like to rename a couple of them before I forget what I was running. I usually use ROM Manager (i know.. this is the only thing i use it for) to rename my backup files. It's just easy that way. RM isn't seeing my recent backups.. I dl'd CWM Manager app and it sees the backups if I go into "restore".. but there is no way to rename them. Also.. when i go into my phones files and into clockworkmod folder.. i still only see a couple old backups.. none of my new ones are anywhere to be found.
So i guess I'm wondering wtf the backups went to, and how do i find them in my directory? Thanks, appreciate any info I get
also if someone has a good alternative to ROM Manager for renaming backup files.. I would appreciate that as well, thanks guys!
I get the option of backing up to either sd or ex_sd. I don't suppose that gotcha?
As far as renaming, I use the ancient method of keeping a separate .txt file with the nandroid name appended with ROM and kernel. I have to edit the text file when I change ROMs or kernels, but all un-appended backups subsequent to the last appended ROM/kernel are still from that preceding combination.
Capiche?
geomax45 said:
I get the option of backing up to either sd or ex_sd. I don't suppose that gotcha?
As far as renaming, I use the ancient method of keeping a separate .txt file with the nandroid name appended with ROM and kernel. I have to edit the text file when I change ROMs or kernels, but all un-appended backups subsequent to the last appended ROM/kernel are still from that preceding combination.
Capiche?
Click to expand...
Click to collapse
I've haven't gotten the option to where my backups are kept. Regardless I'm still unable to find the backups anywhere I'm my directory.
sent from my Galaxy SII
Backups are in clockworkMod folder. in /sdcard or sdcard/external_sd/ depending on your kernal. the newer kernals have external sdcard as an option.
Strange that you cant find them. Delete the CWM folder and take another backup?
Maybe sdcard is full and backups arent getting saved?
MotoMudder77 said:
Backups are in clockworkMod folder. in /sdcard or sdcard/external_sd/ depending on your kernal. the newer kernals have external sdcard as an option.
Strange that you cant find them. Delete the CWM folder and take another backup?
Maybe sdcard is full and backups arent getting saved?
Click to expand...
Click to collapse
It is strange. Both my SD cards have plenty of space. The part that bugs me is that the app CWM Manager see's the backups if I choose restore, but yet I cannot find those files ANYWHERE in my phone. Believe me I've opened my clockworkmod folder countless times hoping to see them. When I boot into recovery and choose restore.. I only see the two new ones... then to get the old backups in recovery I have to choose restore from external SD. So My backups are there on the phone. They are just hiding somewhere and I have no idea where else to look. I'm really just trying to rename them. I know where to find em in recovery if I need to.. but it's bugging me I don't know where to find em in my phone directory.
Have you tried another file manager?
Sent from my GT-I9100 using xda premium
geomax45 said:
Have you tried another file manager?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I've tried using RootExploer as well as the stock file manager app. Even when I plug the phone into my PC via USB and search that way I cannot find the backups. Its driving me mad LOL
Not sure it should make too much of a difference but 1 of the two "missing" backups was taken with stock illusion kernel, the other backup I'm missing was taken with the new Siyah kernel 2.6.11.
sent via Galaxy SII
Backups SHOULD be in:
/sdcard/clockworkmod/backup
or
/emmcs/clockworkmod/backup (which is /sdcard/external_sd/clockworkmod/backup on Samsung firmwares - when in CWM itself it's /emmc, same for CM7)
So.. after days of confusion I found the files.. thanks to everyone for replying. There was another "clockworkmod" folder in my external SD card. I didn't realize that as I kept opening up the first clockworkmod folder I saw... at the very bottom. Below my music, with a couple other zips, was the other clockworkmod folder... same as the one on my SD card- clockworkmod> backup> ..zips!
FINALLY!
thank for all the replies!
THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
IF YOU DON'T WANT THAT TO HAPPEN, MOVE ALONG, THIS AIN'T FOR YOU!!!
AS WITH ANY FLASHING PROCESS, SOMETHING COULD GO WRONG!!!
NEITHER I NOR XDA SHALL BE HELD RESPONSIBLE FOR ANY DAMAGE
THAT YOU CAUSE BY FLASHING THIS ZIP!!!
Now that's out of the way, let me explain the reasons for this zip's existence.
I personally do not like having things left hanging around on my phone's SDcard
after I flash a new ROM onto it, I usually back up my data and format the card too.
It struck me that due to the nature of having an internal SDcard in the Prime
There most surely be stuff hanging around in there from all the flashing I've done.
I also find that hunting down application folders for apps that I have since deleted
can be rather tiresome as they are not always labelled as expected.
Maybe I'm just lazy, but there you go.
Now you can simply install this Zip and all of your partitions will be fresh and clean.
So that's why this zip was born unto the world.
ONCE AGAIN, THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
BEFORE STARTING, MAKE SURE YOU CAN ACCESS YOUR PRIME THROUGH ADB IN RECOVERY!!!!
INSTRUCTIONS: (THIS GUIDE ASSUMES YOU KNOW HOW TO SETUP AND USE ADB)
1. Download prime-full-wipe.zip to your Prime.
2. Backup everything from your internal SDcard to a location that exists outside of your Prime. USB Hard drive, flash drive or another SDcard.
3. After making certain that your data is safe, reboot your Prime to recovery. (zip will work in both CWM and TWRP)
4. flash the zip.
5. Once complete, you will need to reboot to recovery manually otherwise ADB push will not behave correctly.
6. After a successful reboot to recovery, open up Terminal or Command Prompt.
7. Push a new ROM.zip to your Prime via the command
Code:
adb push /path/to/rom.zip /sdcard/
If "/sdcard/" doesn't work, which sometimes happens use
Code:
adb push path/to/rom.zip /data/media/
for some reason it seems that "/sdcard/" is not seen all the time. So far seems to be a windows issue only.
8. Install your new ROM and enjoy that factory fresh taste.
I hope that these instructions are clear enough. If anyone needs help I or someone else will be happy to assist.
I STRESS AGAIN, THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
Credits to mero01 for the original idea and Team Virtuous for some sexy code used in the zip file.
KOUSH for CWM and Team Win for TWRP
Big thanks to swiss-prime and anthonyexmouth for being patient men/windows guinea pigs!
Thanks to Nandrew for pointing out that users may need to reflash CWM if experiencing ROM Manager errors after flashing this ZIP!.
UPDATE: 31/05/12
OK, so to anyone that has had problems pushing a new rom to the SD card after using this zip file. I have found some rather odd behaviour that sometimes occurs when formatting the Prime.
After many hours of testing yesterday, I found that when using CWM I simply couldn't push a file to the sdcard no matter whether I was pushing to "/sdcard/" or "/data/media/"
The only way I was able to get a rom onto the sd card was to eventually flash TWRP using fastboot and push the file after booting into TWRP. However after doing so and then getting a rom installed on the Prime, when looking through the file structure with Root explorer I found that the sdcard symlink had not actually been re-created properly, the file was there, but it was not showing as a folder, and as such, I believe that this is where the problem some people are having stems from.
The only solution that I found was to re-flash the full-wipe.zip again in TWRP and then push a rom onto the sdcard again. After successfully getting back into a working rom, I checked out the file structure and the alias had been properly re-created this time.
The behaviour is very weird and there seems to be no rhyme or reason to it. However, if you have had issues pushing to the sd card after using my zip, I can only apologise for your worry.
I hope that the above makes sense and helps people out who feel that they are now up sh*t creak without a paddle.
To be clear I do not believe this to be an issue caused by CWM, I believe it to be a Prime issue.
Update 01/06/12
Nandrew pointed out to me that you will receive non-critical error messages from CWM about a missing log file after using this ZIP. Once you have made a backup, a log file will be created and these error messages will cease.
You may also need to reflash CWM if you experience rom manager errors.
I think I should give it a shot!
john9 said:
I think I should give it a shot!
Click to expand...
Click to collapse
I'm heading out for about 20 minutes, but I'll be around after that. If you run into any issues.
This looks really helpful Dok - thanks! I seem to have accumulated a mass of crap on my SD card and I was wondering what to do with it...
I do have one question (not directly related to your zip). I have all this stuff on my SD card but I don't know which folders contain app user data and what can be safely deleted. Will TiBu restore all necessary user data to /sdcard after using this (obviously after copying the TiBu folder back to /sdcard ) or do I need to figure out what user data I need to keep for each of my apps before I wipe?
Hope that makes sense! Thanks again for this.
paddycr said:
This looks really helpful Dok - thanks! I seem to have accumulated a mass of crap on my SD card and I was wondering what to do with it...
I do have one question (not directly related to your zip). I have all this stuff on my SD card but I don't know which folders contain app user data and what can be safely deleted. Will TiBu restore all necessary user data to /sdcard after using this (obviously after copying the TiBu folder back to /sdcard ) or do I need to figure out what user data I need to keep for each of my apps before I wipe?
Hope that makes sense! Thanks again for this.
Click to expand...
Click to collapse
I haven't used TiBU yet, I made this zip and flashed it last night, then just flashed it again earlier, so I am currently with a Prime with no ROM.
I think though that TiBU should behave as normal, You may need to re-download app data for some of the biggies like games that have a separate download after the install.
Before I flashed it last night, I backed up the entire contents of the card to a USB hard drive, to make certain that I didn't lose anything at all.
<Edit> Nevermind... I read the whole post!
Doktaphex said:
I haven't used TiBU yet, I made this zip and flashed it last night, then just flashed it again earlier, so I am currently with a Prime with no ROM.
I think though that TiBU should behave as normal, You may need to re-download app data for some of the biggies like games that have a separate download after the install.
Before I flashed it last night, I backed up the entire contents of the card to a USB hard drive, to make certain that I didn't lose anything at all.
Click to expand...
Click to collapse
Thanks. I guess I am just not quite sure how TiBu works. When you do an normal factory reset thru CWM and leave /sdcard intact does TiBu restore a link to app user data located on /sdcard or does it completely rewrite it based on whats in /sdcard/TitaniumBackup/?
Doesn't really matter. I will just back everything up before I use this. I know I need to clean up /sdcard but am a bit chicken to use this
paddycr said:
Thanks. I guess I am just not quite sure how TiBu works. When you do an normal factory reset thru CWM and leave /sdcard intact does TiBu restore a link to app user data located on /sdcard or does it completely rewrite it based on whats in /sdcard/TitaniumBackup/?
Doesn't really matter. I will just back everything up before I use this. I know I need to clean up /sdcard but am a bit chicken to use this
Click to expand...
Click to collapse
Just finished restoring my TiBU and all my apps and relevant data are intact after only copying across the TiBU folder.
Im glad someone finally made this for everyone else. I had once had a problem with my prime that no matter how many times i wiped and reflashed my status bar was not working and when i tried to return to my back up of stock it was giving me read errors restoring the data section and would stop. I had to modify a zip to format what this does and then reflash and then everything worked again. Wiped my tf201 clean but hay it worked again and thats what mattered.
I would love to try this out but I am absolutely too scared of this ADB thing to work on pushing the Zip to the Prime...I figure I will brick it..
acdcking12345 said:
I would love to try this out but I am absolutely too scared of this ADB thing to work on pushing the Zip to the Prime...I figure I will brick it..
Click to expand...
Click to collapse
What operating system do you use on your computer?
adb is easier on Linux and Mac than on windows.
Doktaphex said:
What operating system do you use on your computer?
adb is easier on Linux and Mac than on windows.
Click to expand...
Click to collapse
It is windows. :-(
acdcking12345 said:
It is windows. :-(
Click to expand...
Click to collapse
I would have a look at the naked ADB driver thread here very useful for windows users and should help put some of those fears to rest.
Yes and if you follow this guide to install ADB it will be easy:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
ok, when you say reboot into recovery do you mean "fastboot"
cant find device in adb. using win7 with naked drivers.
Yeah, I dont think I am that gutsy to take this risk. But Ill keep researching it. I would like to start fresh as possible..
anthonyexmouth said:
ok, when you say reboot into recovery do you mean "fastboot"
cant find device in adb. using win7 with naked drivers.
Click to expand...
Click to collapse
No I mean exactly as I said. After flashing in recovery, you have to reboot back into recovery. It is a funny quirk that I may need to look into further.
No then, to your problem. Do you have an irc client on your computer? If so, come over to #asus-transformer on freenode irc and we can talk in real time.
If not, then I will endeavour to assist you here.
Gonna take the zip down for a moment until we can sort this out.
ok, rebooted into recovery and it now sees it in adb. i get a load of E: cant open lines but i guess thats cuz they aint there.
adb push "rom" /sdcard
all looks like its doing it but been stuck there for 20 mins.
leaving it just in case.
anthonyexmouth said:
ok, rebooted into recovery and it now sees it in adb. i get a load of E: cant open lines but i guess thats cuz they aint there.
adb push "rom" /sdcard
all looks like its doing it but been stuck there for 20 mins.
leaving it just in case.
Click to expand...
Click to collapse
I assume that you are abbreviating when you say adb push "rom" /sdcard
It should take no more than 3 minutes to push the rom
yeah full path is adb push c:\android\virtuousprime.zip \sdcard
Hi folks
I hope I am not breaking any rules. I tried my best to read up on the problem and see if it's already been fixed. So far I haven't encountered anything which is specific to my needs, but I learned enough to pose a well-formed question.
Phone: Samsung Galaxy SIII International (GT-I9300)
ROM: Stock Samsung, version 4.1.2, the update with Multi-window. Do not have the exact build number unfortunately.
Root status: Rooted
Recovery: Stock recovery. (I JUST rooted the phone, nothing else.)
So the problem is:
1. I used ES File Explorer in root mode, mounted /system as writable, and made an edit to build.prop (added "qemu.hw.mainkeys=0" to the end of the file to enable navbar) and saved the file. I rebooted the phone and now it is stuck with a looping Samsung logo.
2. I have made a backup of build.prop and placed it in /sdcard/ but unfortunately I haven't made a copy on my PC. Also note that I don't have an external SD card, I am using the 16GB space that came with the phone. So the build.prop backup is on the phone.
3. I do not have a USB cable (I have one that has a loose connection somewhere and my phone is not detected 99% of the times I've used that cable)
What I have found after 2 hours of searching online:
1. Factory Reset through recovery (I am able to boot into stock recovery by doing Vol Up + Home + Power) will not restore /system partition so that won't fix this.
2. ES File Explorer might have messed up the file permissions of the build.prop file.
3. I can use PC ODIN to flash the stock firmware (I might lose data but at least the phone would be back to normal).
4. I can use adb to push a good build.prop file and set the correct permissions (my most fav. set of instructions are from here: http://forum.xda-developers.com/showthread.php?t=1660596 Of course I got the idea from several other threads)
5. I can sideload a good build.prop file that someone might be generous to provide me using adb.
I don't have a data cable, so you can see how that Might be a problem. What I DO have is a USB OTG cable and a pen drive. Now, in the stock recovery, I noticed an option "apply update from external storage". Assuming I have an update.zip with the proper build.prop in it, can I load the update.zip into a usb pen drive (formatted to fat32)? Does "apply update" here work for such zip files or is it only meant to be used for full firmware images? If so, can I just download the latest stock firmware and apply it from here without wiping the /data partition?
If I can get this resolved tonight I can get my phone up and running before tomorrow's work week. I will buy an USB cable ASAP (it's 12 AM here so going out to get it is not an option now). But even if I do, I still have 5 months worth warranty left and I'd like to stick with the stock recovery and avoid incrementing the flash counter altogether, despite Triangle Away.
Thank you very much for the help in advance.
Adb pull your backup» then push it back?
slaphead20 said:
Adb pull your backup» then push it back?
Click to expand...
Click to collapse
I don't have a working data cable, so I cannot connect to the PC. That was my first idea, though, thanks! I am currently reading about making an Update.zip. It's very unfortunate that I didn't note my firmware details after the OTA...
Just set permissions - use Properties in ES FE in root mode. RW. R.. R.. should work.
LenAsh said:
Just set permissions - use Properties in ES FE in root mode. RW. R.. R.. should work. If not try 777 for giggles.
Click to expand...
Click to collapse
I am unable to boot into the phone, it is stuck in a bootloop
I don't have a USB cable to use ADB. I don't even have a custom recovery. All I have is the stock recovery and the option to "apply update from external storage". I now remembered that I also have an SD card on which I can put an update.zip or the stock firmware. Unfortunately I didn't note down the firmware details after the last OTA from 4.1.1 to 4.1.2, so I don't know which one to download.
Can I use the option "apply update from external storage" to flash an update.zip or is that only meant for full firmwares? Thanks!
Oops - silly me.
You are running stock recovery - never use it but does it have a fix permissions option?
Failing that you may have to reflash the ROM. Stock recovery is very restrictive on what you can flash.
LenAsh said:
Oops - silly me.
You are running stock recovery - never use it but does it have a fix permissions option?
Failing that you may have to reflash the ROM. Stock recovery is very restrictive on what you can flash.
Click to expand...
Click to collapse
Fix permission option on the stock recovery? I don't think so, haven't been able to find it. Here are the options I have:
reboot system now
apply update from adb
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Interestingly, when I selected the last option, it had these 3 folders:
fota/
lost+found/
recovery/
I was hoping fota/ had the files from my last OTA update but nope.
I guess you are not sure whether I can flash an update.zip through stock recovery... so I just have to wait till I get my USB cable and try out some adb magic?
EDIT: I'm retiring for the day. Thanks for the suggestions @LenAsh and @slaphead20. I'm gonna buy a cable next week and try to set the permission to 644 (RW-R-R) using this thread as my reference (http://forum.xda-developers.com/showthread.php?t=1660596). Thanks for your suggestions, I will post back when this is all resolved.
In the meanwhile, please keep the ideas coming
PS: Oh wait, I am still curious. What is the worst thing that could happen if I try to flash an update.zip through stock recovery? I am very curious to see if it will work.
You could flash a later custom recovery (this one works well http://forum.xda-developers.com/showthread.php?t=2002953) via Odin and then fix permissions that way. Even if that doesn't work, you could then flash anything you like without having issues that the stock recovery presents.
EDit: still need a cable though...
Trouble is he hasn't got a cable, I had same thinking, that he could use the aroma file manager in philz but he's stuffed without a cable!
Possible to make an update.zip with just the build.prop in it. Copy it to a memory card and use recovery to flash it?
I would try that first.
Edit: i just remembered i have done that a few times with my htc desire. Was running clockwork mod though.
Its really easy, find a small flashable mod in zip format and delete all the mod files and copy your build prop in. Edit the updater script to just write your /system/build.prop.
Copy the zip to you mem card. Use a usb adapter in a pc, stick it in your phone and use recovery to flash from external sd.
And after typing all that i reread your post and your running stock recovery and i think you would need a signature or something on the zip so it would not work. Ooops.
Sent from my GT-I9300 using xda premium
Stock recovery won't let you flash anything much... so perhaps his only option is Odin. When he has a cable.
On a side-note, how can someone not have a USB cable of any kind kicking around??
LenAsh said:
Stock recovery won't let you flash anything much... so perhaps his only option is Odin. When he has a cable.
On a side-note, how can someone not have a USB cable of any kind kicking around??
Click to expand...
Click to collapse
Just edited my post
Sent from my GT-I9300 using xda premium
@LenAsh, @slaphead20, @ficti0n851
Hehe, yeah, I'm stuffed without a cable I lost it recently and I'm the only one with a recent phone. All my family members' phones use different cables.
Anyway, I managed to borrow a friend's cable and am currently downloading drivers for the S3. Once that's done I will use ADB to set the file permission and try rebooting my phone, failing which I will restore the backup build.prop, set permissions and reboot the phone. Failing which... well, maybe I'll reflash the stock firmware (I managed to find out the exact build details btw! )
I'll keep you posted, thanks for taking the time guys
--
EDIT:
ADB was a success! I got in and changed the permission to 644 and rebooted, done! Funny thing was that /system/build.prop file was not even there, there was only /system/build.prop.bak. I was not able to find my original backup on the sd card, but I copied the .bak file (probably generated by ES FE) and set its permissions and that worked. And now I have also have the software keys!
Thanks for your comments guys. This was fun!
----
EDIT 2:
For anybody else who has the same problem, I did it using the commands in these great ADB guides:
http://forum.xda-developers.com/showthread.php?t=1660596
and
http://forum.xda-developers.com/showthread.php?t=879701
Also, how do I edit the title of the topic? Want to add a [Solved] tag.
ficti0n851 said:
Possible to make an update.zip with just the build.prop in it. Copy it to a memory card and use recovery to flash it?
I would try that first.
Edit: i just remembered i have done that a few times with my htc desire. Was running clockwork mod though.
Its really easy, find a small flashable mod in zip format and delete all the mod files and copy your build prop in. Edit the updater script to just write your /system/build.prop.
Copy the zip to you mem card. Use a usb adapter in a pc, stick it in your phone and use recovery to flash from external sd.
And after typing all that i reread your post and your running stock recovery and i think you would need a signature or something on the zip so it would not work. Ooops.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hey, I know this post is from forever ago, but is there a chance you could explain this step by step for a noob?
I have got my phone stuck in a bootloop by fiddling with build.prop, and I have the original file before playing with it. I have a rooted device with custom recovery, so how I could I use minimal ADB to push the original build.prop located on my device (sdcard) to root/system??
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
gautham_y said:
@LenAsh, @slaphead20, @ficti0n851
Hehe, yeah, I'm stuffed without a cable I lost it recently and I'm the only one with a recent phone. All my family members' phones use different cables.
Anyway, I managed to borrow a friend's cable and am currently downloading drivers for the S3. Once that's done I will use ADB to set the file permission and try rebooting my phone, failing which I will restore the backup build.prop, set permissions and reboot the phone. Failing which... well, maybe I'll reflash the stock firmware (I managed to find out the exact build details btw! )
I'll keep you posted, thanks for taking the time guys
--
EDIT:
ADB was a success! I got in and changed the permission to 644 and rebooted, done! Funny thing was that /system/build.prop file was not even there, there was only /system/build.prop.bak. I was not able to find my original backup on the sd card, but I copied the .bak file (probably generated by ES FE) and set its permissions and that worked. And now I have also have the software keys!
Thanks for your comments guys. This was fun!
----
EDIT 2:
For anybody else who has the same problem, I did it using the commands in these great ADB guides:
http://forum.xda-developers.com/showthread.php?t=1660596
and
http://forum.xda-developers.com/showthread.php?t=879701
Also, how do I edit the title of the topic? Want to add a [Solved] tag.
Click to expand...
Click to collapse
Bro, I got the same problem as you had, except that I have a custom recovery, and the original build.prop file, and a USB cable, but I still haven't figured out what to do completly. Can you please take a minute to explain this for a complete noob? You have probably forgot all about this, but I am shooting for this chance. :/
black_hawk1990 said:
Hey, I know this post is from forever ago, but is there a chance you could explain this step by step for a noob?
I have got my phone stuck in a bootloop by fiddling with build.prop, and I have the original file before playing with it. I have a rooted device with custom recovery, so how I could I use minimal ADB to push the original build.prop located on my device (sdcard) to root/system??
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
Bro, I got the same problem as you had, except that I have a custom recovery, and the original build.prop file, and a USB cable, but I still haven't figured out what to do completly. Can you please take a minute to explain this for a complete noob? You have probably forgot all about this, but I am shooting for this chance. :/
Click to expand...
Click to collapse
Hey, are you still having problems or did you solve it yourself? Anyway... If you still don't know what to do, describe best what you did to end up in a bootloop. As far as I understand what your problem is, you should use your recovery to move the backup of the original build.prop file to the system folder.
I changed my phones build.prop and when rebooted it does not started and ended up in bootloop and when I searched for how to fix this problem it showed that clear all the data from the phone but nothing happened and when I tried to install custom ROM in my phone my pc is not detecteing my phone .so what should i do ?
@Rajsh90: pull out battery for some minutes, put it in, reboot into downloadmode. Connect with PC, start Odin and hope that a COM-flag colours. Flash latest firmware.
I recently decided to explore custom ROMs. I installed ARHD for my one but recently decided to try out the GPe ROM. However after I downloaded the ROM and moved it to my phone, it wouldn't appear in CWM recovery. Is there any reason for it? I've copied it multiple times to multiple directories but it won't show up
Sent from my HTC One using xda premium
Try directory '0'
Sent from my HTC One using xda premium
I have the exact same issue? Rooted, twrp installed, the directories show up when I usb to my laptop but created Rom folder is non existent in recovery. Tried downloading Cleanrom straight from the device as well into the "downloads" directory. Downloads shows up in twrp but the Rom isn't there. But browsing "my files" on the device shows that it's there?
Reflash a 4.1.2 rom, copy all your stuff off the device to computer, delete all but rom zip on internal storage flash rom then copy back content
Keep it in the root of you memory. Should show up :thumbup:
Tried putting the .zip file in the root of the internal storage. To no avail. It is invisible. Nothing there at all. What gives?
I also have no such thing as a directory "0"?
Use a different SD?
TeeJay!! said:
Use a different SD?
Click to expand...
Click to collapse
a different SD? The one has internal storage only...am I missing something?
cadorette said:
a different SD? The one has internal storage only...am I missing something?
Click to expand...
Click to collapse
Opps sorry... my bad reflash your phone clean out everything and then try
TeeJay!! said:
Opps sorry... my bad reflash your phone clean out everything and then try
Click to expand...
Click to collapse
another post said that..im gonna re-flash my current rom (at&t stock rooted) and try again...kinda strange ive been flashing since the HTC HD2 through the Galaxy S4 and everything in between and have never seen this...I'll try a re-flash and check in tomorrow
TeeJay!! said:
Opps sorry... my bad reflash your phone clean out everything and then try
Click to expand...
Click to collapse
Sorry..been away from HTC for a while..as in reflash my current ROM?
Did that...went in, wiped EVERYTHING...re-flashed current ROM (just a stock rooted ATT deodex) and its the same thing...the current ROM I'm running shows in TWRP..
But any ROM I've transferred via PC into internal memory, or downloaded straight from the device, is completely non existent...
the "ROMs" folder I created on my PC to the external memory (where I store the ROMs for easy access) is not there either.
Should I search GooManager for an updated TWRP or something?
Update: Wiped again and reinstalled TWRP fresh. Still have exact same issue. everything shows on the phones memory when i connect to PC, but loading up TWRP recovery they are not there. In any directory i select. I'm lost. I want to ROM this thing like crazy but I can't lol!!
OK...fixed it!!!
After a lot of digging it seems when I connect to the PC and look at the storage I DO have a "0" directory (only through the PC though, not in recovery). I opened the "0" folder, moved my ROM to a directory in that via PC, and voila! Now the ROMs show up in wherever I saved them as long as I open the "0" area first through the PC..
Now I just navigate to wherever I saved them (anywhere after double clicking "0" when connected to PC) and the zips are there and present and I can flash. Not exactly sure why this is but it worked for me!
so...in a nutshell...
1. Connect your One to PC.
2. choose "open to view files" (or if youre on a mac like me, android file transfer)
3. find the "0" folder/directory and open it
4. copy the .zip file of your desired ROM there
5. reboot into recovery and it should be there.
6. flash and enjoy!
Keep in mind this is for TWRP based recovery. I am not sure about anyone using CWM that has this problem.
cadorette said:
Sorry..been away from HTC for a while..as in reflash my current ROM?
Did that...went in, wiped EVERYTHING...re-flashed current ROM (just a stock rooted ATT deodex) and its the same thing...the current ROM I'm running shows in TWRP..
But any ROM I've transferred via PC into internal memory, or downloaded straight from the device, is completely non existent...
the "ROMs" folder I created on my PC to the external memory (where I store the ROMs for easy access) is not there either.
Should I search GooManager for an updated TWRP or something?
Update: Wiped again and reinstalled TWRP fresh. Still have exact same issue. everything shows on the phones memory when i connect to PC, but loading up TWRP recovery they are not there. In any directory i select. I'm lost. I want to ROM this thing like crazy but I can't lol!!
Click to expand...
Click to collapse
I'm having the same issue. If you find a fix please PM me.