Can someone kindly tell me what the file name is for the two files above and below the host file in /system/etc/, in my drunkin stupor I renamed the wrong file to host.txt and now it boot loops. I'd like to try to rename that file before flashing back to stock or restoring backups that never boot for me. Thank you.
Fe Mike said:
Can someone kindly tell me what the file name is for the two files above and below the host file in /system/etc/, in my drunkin stupor I renamed the wrong file to host.txt and now it boot loops. I'd like to try to rename that file before flashing back to stock or restoring backups that never boot for me. Thank you.
Click to expand...
Click to collapse
Here you go
Thank you me too. My only fear is that the file I renamed got moved in abc order and I think it's the files above it below host. Thanks again
Fe Mike said:
I'd like to try to rename that file before flashing back to stock...
Click to expand...
Click to collapse
Just so you are aware, removing the -w flag from flash-all.bat in a stock ROM download preserves your data. Custom ROMs do not automatically wipe data in TWRP: you have to select it, and thus your data should be preserved there.
Where you cannot recall which file you edited, flashing a stock ROM with the -w flag removed is probably the best bet. I know it's not what you want to do, so let's hope you rename the right file.
Related
Hey!
I was wondering, is there a way of adding apps to a rom... theres a few apk's i practially have to have installed, so i was wondering is there a way to add these files to a zipped rom so they install within the the system folder on the phone takin up dedicated rom space instead of dedicated phone storage....
been searching for a while about this, an theres a few close threads but they stopped before it was answered.
Also i have tried unzipping the rom, adding the apks, then rezipping an it didnt work, it started installing an finished within 2 seconds so obviously it didnt install the rom.
Thanks in advance!
You should just be able to add them to the /system/app folder. You just have to use a custom recovery to flash it, because the original zip is signed, where yours isn't. So if you turn the check for signature off in the recovery it should work just fine.
Alternatively you can learn how to sign your zip file, but that's far more time consuming.
i tried doing that, toggled it off in clockworkmod and still does the same thing. so not entirely sure wat i'm doing wrong, all i'm doing is rezipping it to a zip file using winrar.... should i try somethin else?
and yeah i made sure it did it to a zip file an not a rar file
360nitrous said:
i tried doing that, toggled it off in clockworkmod and still does the same thing. so not entirely sure wat i'm doing wrong, all i'm doing is rezipping it to a zip file using winrar.... should i try somethin else?
and yeah i made sure it did it to a zip file an not a rar file
Click to expand...
Click to collapse
I had a similar problem like yours.
Here is where we were wrong. We unzipped the .zip, added whatever we did, and then selected the folder and added to zip, which is wrong. You have to select ALL the folders and files WITHIN the folder unzipped and add it to archive.
Meaning, I have for ex. update-OD4.0.10.zip, after I unzip it it gets a folder containing all the files and folders of the ROM. You have to go one level in, select them all (files and folders in there) and add it to zip. Et voila!
Hope you understand my English!
mi3x said:
I had a similar problem like yours.
Here is where we were wrong. We unzipped the .zip, added whatever we did, and then selected the folder and added to zip, which is wrong. You have to select ALL the folders and files WITHIN the folder unzipped and add it to archive.
Meaning, I have for ex. update-OD4.0.10.zip, after I unzip it it gets a folder containing all the files and folders of the ROM. You have to go one level in, select them all (files and folders in there) and add it to zip. Et voila!
Hope you understand my English!
Click to expand...
Click to collapse
Now that makes me feel stupid haha!!! your totally right, that sorted out the problem, thanks a lot!!! sometimes its the simplest things that you forget about
Yes you will of course have to add the folders in the same structure as before, as the update script are telling the recovery which folders to flash where, and you are leaving that script unchanged.
360nitrous said:
Now that makes me feel stupid haha!!! your totally right, that sorted out the problem, thanks a lot!!! sometimes its the simplest things that you forget about
Click to expand...
Click to collapse
My pleasure I loled as well! At least I went deeper in my feeling stupid, changing RAR tools, different compression types etc... and the answer was there all along.
I've learned to mount while in recovery and put a ROM in the root folder, but when i go to "flash zip from sdcard" i can't select anything?
Was there something i forgot? I see that the ROM is a img file, do i mount it and extract the files within it and then put those into the root folder? (Just tried it, and nothing happens when i mount the img?)
Are there other things i have to do all over again b4 i can even flash a rom?
*I wiped everything b/c i was trying to re-flash the rom i had in order to see if that would solve my Wi-Fi problems.
It needs to be a zip file in order to flash through recovery.
So how do i get it to be a zip file instead of img?
Hmm i assume i need to download winzip then?
Got WinZip, put the rom back in the root folder as a zip file, still nothing showing up.
Jut redownload the rom from wherever u got it from. Make sure its a zip file then try that
Sent from my PC36100 using xda premium
Wow, this whole time i've been extracting the downloaded file and then putting the files into the root folder. I'm supposed to just put the downloaded zip directly into the root huh?
Lets see if it works now.
Ugh, okay. Got it to work. Installed new ROM. But, the reason i tried all of this was b/c my Wi-Fi was not working. It still isn't.
Well that totally depends on the rom. Some custom Rom's might not have wifi set up yet, which does seem strange because that is a basic. But go over the simple things first such as :Is wifi enabled. I know it sounds stupid but it could be a fix lol!
I rooted my phone today and did a CWM backup - I then flashed CM10 and then tried to do a restore but when I try it I get the following error "Couldn't open directory, No files found"
Yet when I browse my files I can see the back up I made in the CWM folder - why won't it restore this?
Any thoughts?
Thanks in advance!
jackryan57 said:
I rooted my phone today and did a CWM backup - I then flashed CM10 and then tried to do a restore but when I try it I get the following error "Couldn't open directory, No files found"
Yet when I browse my files I can see the back up I made in the CWM folder - why won't it restore this?
Any thoughts?
Thanks in advance!
Click to expand...
Click to collapse
Hmm...not sure if it's related, but the only time my CWM backup didn't restore was some MD5 mismatch error. I renamed the backup to "backup.tar" (if you're using *.tar and not /blobs) after I read that worked on a thread, and wala, it worked! Unsure if that's what your issue is, though.
ikjadoon said:
Hmm...not sure if it's related, but the only time my CWM backup didn't restore was some MD5 mismatch error. I renamed the backup to "backup.tar" (if you're using *.tar and not /blobs) after I read that worked on a thread, and wala, it worked! Unsure if that's what your issue is, though.
Click to expand...
Click to collapse
I just tried what you said and it still doesn't work - I did notice that my backup is a file folder not just a file - so I don't think renaming the folder to a .tar will actually do anything to it?
Is there any other way to restore from a back up I have on my phone but that CWM doesn't seem to see??
You could try moving the file with a file manager or make sure permissions are good.
Sent from my SAMSUNG-SGH-I747 using xda premium
Push it with Odin? Or just grab the stock rooted file from the stickies and push that with Odin.
Sent from my SGH-I747 using xda app-developers app
What would I be looking for as far as permissions go?
jackryan57 said:
I just tried what you said and it still doesn't work - I did notice that my backup is a file folder not just a file - so I don't think renaming the folder to a .tar will actually do anything to it?
Click to expand...
Click to collapse
Hmm..it's been a while since CWM--do you have any folder called blobs? If so, then my tip to rename to "backup.tar" won't work. Basically, you're right. If you don't have a *.tar backup, then I got nothing. CWM used to be *.tar only, then defaulted to /blobs, and now is defaulting back to *.tar with the option of /blobs.
join the club...
http://forum.xda-developers.com/showthread.php?t=2101424
No idea what's going on with this crap. I've lost every backup now for two weeks, the worst of which was my stock backup.
i may have ended up finding a solution to the problem here, if yours is similar enough to mine.
http://forum.xda-developers.com/showthread.php?t=2101424
Hey guys
I've gone through all the steps as instructed, but can't install HD RSL15 successfully. I downloaded the installation file from a mac which then automatically unzips the folder. Zipped it back up with 7zip and threw it on the phone. I went through all the prescribed steps using TWRP 2.6 and AndroidUnite's video on youtube (How To Install TWRP Recovery And Flash Custom ROM) as example. This is the 2nd time Ive downloaded the file and I switched over from CWM based on advice in these threads.
When it comes to installing the ROM the window ends up looking like this:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip...
Updating partition files...
FAILED
Have I done something wrong during the previous steps (flashing, installing recovery) or does it have something to do with the method of zipping the files (tried fastest and store as compression options, doing store makes the file unreadable by the phone during recovery mode)?
I've read there is supposed to be an md5 file in the installation files, but mine didn't have any. Can someone let me know about the contents of the zip file so that I can zip it up as intended or something. Please help
PS. I know this is a copy of another reply i posted, but i cannot delete those and i haven't received any help in the other threads
I'm having a similar issue, only I run the checksum before I flash and the md5 is never the same. Has anyone fixed this?
Sent from my SGH-I747 using xda app-developers app
KissyLynn said:
I'm having a similar issue, only I run the checksum before I flash and the md5 is never the same. Has anyone fixed this?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
KissyLynn, can u send me a screen shot of ur zip file's contents please
Don't let your Mac unzip the file. There is probably a problem when unzipping or rezipping. Just leave the file the way it is, don't unzip it.
Sent from my Nexus 7
stelv said:
Don't let your Mac unzip the file. There is probably a problem when unzipping or rezipping. Just leave the file the way it is, don't unzip it.
Sent from my Nexus 7
Click to expand...
Click to collapse
No choice in the matter. Can u let me know what the zip contents should look like so i can try and solve the problem
Rhetorical said:
No choice in the matter. Can u let me know what the zip contents should look like so i can try and solve the problem
Click to expand...
Click to collapse
Here is a screenshot of the contents, I really don't think it is going to work if you unzip and zip the file. You usually can't just rezip a rom file. The md5 will be different and it will give you an error. Not sure what you are using on your mac to download, but maybe try with chrome. The file should not automatically unzip, and if it does there should be a zip file intact still somewhere on your mac. You need to flash the original zip file.
stelv said:
Here is a screenshot of the contents, I really don't think it is going to work if you unzip and zip the file. You usually can't just rezip a rom file. The md5 will be different and it will give you an error. Not sure what you are using on your mac to download, but maybe try with chrome. The file should not automatically unzip, and if it does there should be a zip file intact still somewhere on your mac. You need to flash the original zip file.
Click to expand...
Click to collapse
Hey Stelv, i did a screen share and am busy copying what i hope is the original zip file (hyperdrive rsl15 universal s3.zip.download), but we'll have to see, files are still being copied over individually so not sure it's right. I don't see an md5 file in that main directory, where is it situated??
Md5 is achieved by opening terminal on your mac and typing Md5 and then a space and then drag and drop your zip file into terminal and hit enter. If it doesn't match the md5 number in the hyperdrive thread its not going to install correctly. There are also md5 checker apps on the market.
Sent from my SAMSUNG-SGH-I747
redownloaded and it works like a charm, thanx for the assist
My phone is GT-N7105 (Samsung Note 2)
=============SHORT STORY=============
TWRP can't recognize my backup folder name which I am trying to restore
=====================================
=============LONG STORY=============
I had a nandroid backup before, then I copied the backup to PC, still have it. Then I flashed lineage 13. I deleted the nandroid backup on the phone storage. Now I want to restore the backup so I copied the backup files from the PC.
Now when I go to TWRP Restore mode, no backups are found.
I already searched through the internet and found the renaming method but there's a problem:
this is my original backup:
TWRP/backups/42f7491d7b409fc7/2017-03-01--05-28-34_JZO54K.N7105XXDMB
I tried to make a new backup of my current lineage (just to see if the folder name changed based on the new folder the backup process will create), here is what the resulting folder was:
TWRP/backups/42f7491d7b409fc7/2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
As you can see, only the innermost folder name changed. So from what I found through searching, it said to rename the old backup folder to the new backup folder's name, meaning :
I changed
2017-03-01--05-28-34_JZO54K.N7105XXDMB
to
2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
TWRP still can't see the original backup.
So what should I rename the original backup folder for TWRP to recognize it and make it appear?
EDIT:
I already updated my TWRP but problem still exists.
Create a new backup with your current rom, then remove it and add the old one instead.
futchy4u said:
Create a new backup with your current rom, then remove it and add the old one instead.
Click to expand...
Click to collapse
Sorry not really a developer type of guy and I regret tinkering with these stuff on my phone.
What you meant was to make a backup with current rom just to get the folder name that TWRP will recognize and then swap the old stock backup into the folder?
If I just rename the stock backup folder name to 2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c it's the same as what you said right?
and it should still run smoothly (stock rom should be restored without errors)?
Sorry just asking out of caution.
It's ok, we're all helping each others here. And we all had lots of mistakes and we still do.
Anyways, yes renaming it could do the trick but you don't need to rename the backup name directly. Instead, you need to rename the folder containing the backup.
TWRP path is going to be similar to that
/TWRP/BACKUPS/4d00475b004150de/2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
Click to expand...
Click to collapse
All you need to get is that folder name "4d00475b004150de" because it's auto generated by twrp, that's why I asked you to create another backup even if you just backed up your boot file to generate the folder.
Once you did the backup you can then move your old backup to that folder or rename that old similar folder to the newly created one (not the rom backup folder itself).
sgn15 said:
Sorry not really a developer type of guy and I regret tinkering with these stuff on my phone.
What you meant was to make a backup with current rom just to get the folder name that TWRP will recognize and then swap the old stock backup into the folder?
If I just rename the stock backup folder name to 2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c it's the same as what you said right?
and it should still run smoothly (stock rom should be restored without errors)?
Sorry just asking out of caution.
Click to expand...
Click to collapse
futchy4u said:
It's ok, we're all helping each others here. And we all had lots of mistakes and we still do.
Anyways, yes renaming it could do the trick but you don't need to rename the backup name directly. Instead, you need to rename the folder containing the backup.
TWRP path is going to be similar to that
All you need to get is that folder name "4d00475b004150de" because it's auto generated by twrp, that's why I asked you to create another backup even if you just backed up your boot file to generate the folder.
Once you did the backup you can then move your old backup to that folder or rename that old similar folder to the newly created one (not the rom backup folder itself).
Click to expand...
Click to collapse
Oh, the folder name code you're referring to was 42f7491d7b409fc7 for me. Thanks. I tried it and everything worked (done restoring and it looks like everything is working so far). Thanks a lot again!
To moderators, this topic's problem is solved. Not sure if the topic needs to be locked after being solved, but yeah just a heads up. Not very active here.
Cheers.
sgn15 said:
Oh, the folder name code you're referring to was 42f7491d7b409fc7 for me. Thanks. I tried it and everything worked (done restoring and it looks like everything is working so far). Thanks a lot again!
To moderators, this topic's problem is solved. Not sure if the topic needs to be locked after being solved, but yeah just a heads up. Not very active here.
Cheers.
Click to expand...
Click to collapse
You're welcome. I think it's ok to be left here so that it could help others.