Develop Bugs

What is 1.34.405.5_PC10IMG.zip?

I mean, I have this file on my SD card from when I rooted (downgrading from 1.72)
If I flash this ROM, it will just flash stock 1.34 (which I'm running at the moment) right?
I think I left it on my SD card as "backup" because it can be installed from the bootloader, but now I'm wondering whether this is necessary, and whether I can delete it
Cheers
Edit: Also, I have some other files backed up, not sure if I need them
part7backup
part17backup
su
superuser.apk

make a backup dir on sdcard and move the zip file into this dir.

LooieENG said:
I mean, I have this file on my SD card from when I rooted (downgrading from 1.72)
If I flash this ROM, it will just flash stock 1.34 (which I'm running at the moment) right?
I think I left it on my SD card as "backup" because it can be installed from the bootloader, but now I'm wondering whether this is necessary, and whether I can delete it
Cheers
Edit: Also, I have some other files backed up, not sure if I need them
part7backup
part17backup
su
superuser.apk
Click to expand...
Click to collapse
Yes that is going to be a stock rom, no root.
As for the other files the part files you should copy to your PC the su and superuser files are not needed as long as you only flash roms that are pre-rooted.

LooieENG said:
part7backup
part17backup
Click to expand...
Click to collapse
Copy these two to your computer, as (I think?) one of them is a backup of the /misc partition before running gfree to S-OFF, not sure about the other though

Thanks for the replies
So I should keep the part backup files on my computer, and if I keep that ROM on there, that should mean that if I mess up and can't get to recovery, as long as I can get to the default bootloader, I can flash it from there, right?

Rename backup files - CWM

On my old Magic, I was running CM6 and I thought CWM - but I don't remember now, I'm thinking possibly it was another recovery, because I had the ability then to name my backup files before starting the backup, so I could give them more meaningful names than just the date.
Can I rename my backup files on my SD card? Just use Astro for this, or what?
Or will this cause CWM to no longer see the files as valid backup files?
Additionally, I had been rooted prior on GB - now that I'm on ICS, I'm not sure I want those on my SD card in the (hopefully) unlikely event that I accidentally pick one of those nandroids to restore when I meant to restore back to a prior ICS version. Seems like there could be risk of bricking my phone, so can I copy and delete these off my phone?
Is it as simple as knowing where to look on the SD card and using Astro to rename them, or Kies (or Windows) to move them/delete them?

I dont think you can do that because then it will give you an MD5 mismatch. I think in the new version of TWRP recovery coming out, you can name and rename backups though.

slick_rick said:
I dont think you can do that because then it will give you an MD5 mismatch. I think in the new version of TWRP recovery coming out, you can name and rename backups though.
Click to expand...
Click to collapse
You can rename them as long as you don't put any spaces when you rename it. For example - blazer 4.1 gb- would not work you would have to us blazer.4.1.gb and it would work fine.

albertouresti said:
You can rename them as long as you don't put any spaces when you rename it. For example - blazer 4.1 gb- would not work you would have to us blazer.4.1.gb and it would work fine.
Click to expand...
Click to collapse
There's your answer then.

[Q] Problem with nand bakcup

Hello
My problem is that I downloaded the nand stock rom from the thread and extracted it and tried to put it in the clockworkmod\backups folder and I think it was ok (not sure) but by mistake I deleted all of backups (the stock and the one i created) and I tried to copy it again and create another one but I noticed that there never 2 backups.
The one that I created I can see only from the restore option in recovery and not in the folder ( I used to see it in the folder ..) and the stock one I can see in the folders but not in the restore option.
Should it be like this ? Am I doing something wrong ?
How can I restore that stock backup if I cant see it ?
I'm on ordroid 9 with TWRP recovery.
And the stock one gets in ZIP but i extracted it and copied as folder.
Thanks in advance , I'm afraid to flash new version.

That's because you didn't put it into clockworkmod>backup folder in the sd card and btw you don't extract anything .....every nandroid backup must have 5 zip files in it (don't extract it) and should be named as the date and time it was created

The folder should be like this
Clockworkmod\backup\date & time folder\backup files

donhashem.dh said:
That's because you didn't put it into clockworkmod>backup folder in the sd card and btw you don't extract anything .....every nandroid backup must have 5 zip files in it (don't extract it) and should be named as the date and time it was created
Click to expand...
Click to collapse
I know :\
I extracted the stock backup folder from the zip . not the content in backup.
Forgot the part about renaming, that actually might be the case.
Thanks both of you, I'll try it.

Screwed up my M8, trying to remove the Carrier IQ. HELP!!

Tried to remove the tmobile Carrier IQ from my device, last week. I used Solid explorer, to do it. This is the list:
/system/app
QXDM2SD.apk
QXDM2SD.odex
HtcResetNotify.apk
HtcResetNotify.odex
Htcloglevel.apk
Htcloglevel.odex
Smith.apk
Smith.odex
Udove.apk
Udove.odex
/system/priv-app
IQ-tmobile-release-signed.apk ???????
IQ-tmobile-release-signed.odex ???????
IQToggle.signed.apk
IQToggle.signed.odex
MyBreeze.apk
MyBreeze.odex
/system/lib
system/lib/libiq_service_tmobile_2.2.so
/data/data
com.carrieriq.tmobile
com.carrieriq.tmobile.IQToggle
The two questionable files above were slightly different, on my device. They read:
IQ-tmobile-release-unsigned.signed.apk
IQ-tmobile-release-unsigned.signed.odex
Against my better judgment, I continued to delete all of those files. Now, I can't even get past the banner on the home screen. It says, "Unfortunately, System Manager Application has stopped." I went to my bootloader and did a factory reset. Then, went to TWRP and did another factory reset and wiped the cache, dalvik & data. I used Firewater to unlock, root & S-OFF from KitKat Stock 4.4.2 and would prefer to keep it if possible. I had absolutely no problems with that version. The pictures are below.
As you can see, everything seems to be perfectly unaffected. I get calls, texts, voicemails, and every notification. It won't let me go beyond the home screen. If anyone can find KitKat 4.4.2 Stock Rom for Tmobile USA, I'd greatly appreciate it.

I am guessing you didn't do a backup before hand?

bradley_e_smith said:
I am guessing you didn't do a backup before hand?
Click to expand...
Click to collapse
Actually, I did a Titanium & NAND backup. But I didn't keep a copy of the NAND, in the internal storage. I just got an OTG Adapter. Gonna see if I can push the NAND onto the internal storage. Hopefully, it'll work. If not, I could definitely use your expertise.

Well then, all you need to do is to unpack the nand backup on your PC, and find the missing files and using TRWP mount / as rw and push the files back to your phone.

bradley_e_smith said:
Well then, all you need to do is to unpack the nand backup on your PC, and find the missing files and using TRWP mount / as rw and push the files back to your phone.
Click to expand...
Click to collapse
So, how do I do that?

Take your backup. the files that end in .win000, win001, win002, etc are tar files. So the easiest way would be to get a 'tar' program (cygwin has one built into it), and looking at each file look (tar -vtf [filename] -> will list the contents of the archive) for your missing files. By using -xvf option you can extract the file(s) you need.
BTW: On my lollipop backup of my M8 phone I didn't see any file that "IQ" in the filename, so kitkat must be different than lollipop.
-brad

TWRP can't recognize backup folder name

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.