Related
alright i've searched and reset till I can't see straight anymore. Is there a way to change the first 2 boot screens on startup,without flashing a new rom? I can change the 3rd by changing the welcomehead.96. image, but all the ones I've tried for the 1st 2 either don't work or freeze my phone on boot screen,resulting in a hard reset ( good thing I have all my cabs on my storage card).would prefer a cab file ,but a rar or zip with some instructions will work. sorry if it's been posted somewhere else already, but I can't find it. thanks in advance
Sorry, there's a good reason your searches came up fruitless... splash screens are embedded in the rom, and just "replacing a file" using file exporer will not change it since it is Read Only. Very often the splash screen is displayed before the OS even has a chance to load the file system.
Basically, you need to learn how to embed images into the rom and re-flash. I'm pretty sure there's no way around this.
illtemper said:
alright i've searched and reset till I can't see straight anymore. Is there a way to change the first 2 boot screens on startup,without flashing a new rom? I can change the 3rd by changing the welcomehead.96. image, but all the ones I've tried for the 1st 2 either don't work or freeze my phone on boot screen,resulting in a hard reset ( good thing I have all my cabs on my storage card).would prefer a cab file ,but a rar or zip with some instructions will work. sorry if it's been posted somewhere else already, but I can't find it. thanks in advance
Click to expand...
Click to collapse
You can change the second screen on the Mogul by replacing the SPCS_startup.gif Since this file is a read-only, you'll have to change the attributes using Resco Explorer or some other file manager program (except the built in one). Then you can replace it with any gif or animated gif image and ofcourse have the name the same SPCS_startup.gif. The first boot screen is something that's only done by embeding an image into the ROM and flashing.
ok thats kinda what I thought
well I was afraid of that. really don't know anything about flashing or dumping rom. can I flash just the boot screens like other models,,and where do I find how to do that? my device is qwest with a rom 213. which is different than sprints 209 or 216 . so I,m not sure about getting the rom back if I mess it up. any help would be appreciated . thanx
I am not sure about Qwest either...as I am with Sprint. I don't think there is a download for the Qwest ROM since there hasn't been any udpates to it but you might try looking at PPCGeeks in the ftp://ftp.ppcgeeks.com/titan/users/
you might be able to find the Qwest ROM extracted by IMCOKEMAN.
Also, you can flash the boot screen (1st screen). That nbh file use to be in DCD's folder at PPCGeeks but its not there anymore. I'll have to go home and look to see if I still have it on my home PC.
was wondering if someone could tell me where to find the nk.nbf from dcd's 2.2.x roms...want to cook up some custom boot screens, but have NO idea where to find it (or get it from). thanks
You need to extract the nbh from the installer (you can use procmon from sysinternals.exe to find out where the installer extracts it).
After that you need to decompile the NBH using various tools, in which will present you with a 00_OS.nb.
After doing that, you need to extract the splash images from other roms, or create your own, then recompile the NBH.
EDIT: wow first post since 2006, you can tell ive been a leech, glad to give back to the community lol...
I was going to post the contents of the readme file that i'm trying to understand...in order for you to see what i'm being told to do, but I really can't decipher it all that well, so i'm going to attach it. This is what I'm being told to do...
Have you looked in to this: http://forum.ppcgeeks.com/showthread.php?t=16939
Yeah I read through that...
Thing is...with dcd's latest roms, the only file you get when you extract his nbh is 00_OS.nb
I have my splash.nb already made from the image i chose, but I'm not sure what to do with 00_OS.nb and splash.nb
Make an NBH from them.
You can use Dutty's NBH Tool patched for the Titan.
Since I can't find the original thread where I got it (took me forever to find in the first place) I uploaded it to fileshex.
Download here
I don't have to name my splash.nb something specific when creating the new nbh? It will just know that it's the splash?
Edit: nevermind, after opening duttys tool it's clear on how it works...thanks
Ahhh..one more question...
Is it possible to just take my splash.nb and make an nbh out of that. Then put it into the RUU and flash just the splash? Or must it be merged with the entire rom and flashed?
I have no idea.. I never did it. I want the original Verizon splash screen back instead of the static Verizon logo.
Try it and let us know if it works.
Can someone upload VZW_Startup.gif from \Windows somewhere I can download it?
I'd appreciate it very much
Confirmed.
Just took splash.nb and created an nbh just including the splash fields. I then inserted it into the RUU, flashed, and worked like a charm, no need to include any other part of the OS or anything.
Looks badass...for any help let me know...now that I know what I'm doing
P.S. It WILL hard reset the phone though upon flashing...
I put all the necessary files in a zip and I'm working on an easy step by step readme...so if anyone wants to change their bootscreen send me a pm.
Can't post in the Dev section yet. That's what I get for trolling around since you guys showed me how to root my OG Droid. Thanks, btw.
Now, I'm trying to root my Tbolt, and when I click on the downgrade RUU file to see the contents it says the file is invalid. So, then I tried to extract it, to see what would happen, but same message.
I also downloaded the exploits.zip and the final PG05IMG.zip and was able to view both their contents. Plus, I had to extract the exploits file to the SDK directory, and it worked fine.
So, I then downloaded from all three mirrors, but same result. And then I went to the rom.galaxysense.com site and downloaded from there, but same result. Am I the only one having retarditis? Is the file jacked, or just run-of-the-mill incompetence on my part???
Thanks to whomever takes the time to help out. And thanks for all the help everyone puts out there for the rest of us.
I am confused by your massive amount of words in this post. You need to say maybe, 20 things total.
First, you don't need to open anything, you simply need to put the ZIP onto your SD card and reboot into Hboot.
The only ZIP you need to unzip is the exploit.zip.
I don't need to extract them, I get that. I was looking in the zip files out of curiosity, but when the one file said it was an invalid file type I didn't want to put it on my SD card. That's closer to 20 words, hope that makes sense.
drweltman said:
I don't need to extract them, I get that. I was looking in the zip files out of curiosity, but when the one file said it was an invalid file type I didn't want to put it on my SD card. That's closer to 20 words, hope that makes sense.
Click to expand...
Click to collapse
haha, I was feeling like being a smart ass. The RUU needs to be renamed to PG05IMG.ZIP and put on the sd card, then you need to reboot into bootloader.
Also to add, I came into the problem where I renamed to PG05IMG.zip It was already zipped so just had to name it PG05IMG Then it worked for me.
Thanks for the help. I guess no one understood what I was saying, but since no one else has mentioned the file being corrupted I guess I'll use it and hope for the best.
That's why I mentioned that the other two zip files would let me look at their contents, but the third one said invalid file type. I thought it was clear, but my bad...
Either way, here's another post towards getting out of noob post restrictions!
drweltman said:
Thanks for the help. I guess no one understood what I was saying, but since no one else has mentioned the file being corrupted I guess I'll use it and hope for the best.
That's why I mentioned that the other two zip files would let me look at their contents, but the third one said invalid file type. I thought it was clear, but my bad...
Either way, here's another post towards getting out of noob post restrictions!
Click to expand...
Click to collapse
I'm pretty sure that the RUU downgrade is not something you can open. Just make sure the checksum is valid and you're good to go.
I had tried to flash the RUU after I first rooted becuase I was having location issues. It would check the PG05IMG.ZIP and go back to the Hboot screen. I had flashed another rom so I didn't mess with it any further.
drweltman said:
Thanks for the help. I guess no one understood what I was saying, but since no one else has mentioned the file being corrupted I guess I'll use it and hope for the best.
That's why I mentioned that the other two zip files would let me look at their contents, but the third one said invalid file type. I thought it was clear, but my bad...
Either way, here's another post towards getting out of noob post restrictions!
Click to expand...
Click to collapse
Finally! I've been looking through threads forever in search of this very issue. I was all set on rooting last night, and just like you, the Mecha_RUU file wouldn't unzip, said it was invalid, etc. I stopped right there out of fear that I'd get burned pressing on with one of the key files "broken." Have you rooted since with no trouble?
The best thing to always do is get an MD5 sum for the file and compare it to the root post. I have rooted my thunderbolt twice now and never had a problem.
If the md5sum is correct then you should be fine. Also remember in Windows, it hides the extensions. So when you rename your files do not add the extension as it is already there.
You can show the extensions by changing the folder settings.
Downgrade wont flash
1) Power down phone
2) Power up phone holding volume down
3)No option to upgrade just starts checking files
4) Third check is the downgrade file, starts loading
5) Fails because the file is Older than the main
Ive seen other threads touch on this but no one answer it. Any help with this would be greatly appreciated. Also I have already updated to the 7/8/11 OTA.
Thanks,
JDBSC1 said:
1) Power down phone
2) Power up phone holding volume down
3)No option to upgrade just starts checking files
4) Third check is the downgrade file, starts loading
5) Fails because the file is Older than the main
Ive seen other threads touch on this but no one answer it. Any help with this would be greatly appreciated. Also I have already updated to the 7/8/11 OTA.
Thanks,
Click to expand...
Click to collapse
as in "MAIN VERSION HIGHER" error while flashing?
Not sure what exactly you are trying to do but read this post where it discusses about getting that error.
http://forum.xda-developers.com/showthread.php?t=1008824
Absolute_Zero said:
as in "MAIN VERSION HIGHER" error while flashing?
Not sure what exactly you are trying to do but read this post where it discusses about getting that error.
http://forum.xda-developers.com/showthread.php?t=1008824
Click to expand...
Click to collapse
I appreciate the thread link. That's exactly the error I'm getting. Problem is I'm supposed to downgrade to obtain root ( or at least that's one of the steps). I have downloaded this downgrade file from multiple links and verified its the correct one to use in this step and I always receive the "main version higher" issue. Should I be using a different file to downgrade or is this no longer an option for root since the 7/8/11 ota?
Sent from my ADR6400L using Tapatalk
Interesting..
I wiped everything ADB and Thunderbolt related from my PC.
Then I downloaded the easy root from this link
http://forum.xda-developers.com/showthread.php?t=1005292&highlight=easyroot
Then I downloaded and opened the pdf instructions on the same page.
Then I followed the written directions to a T!
Worked like a charm. Steps 1, 2, and 3 hung up and had to be done multiple times but I finally got through it. Some other links if found with this same method were misleading as to doing the steps over again but he accounted for this in his pdf instructions and if you follow it to the letter you should be good.
Enable Copy & Paste on the Nook Tablet
Background
The lack of copy & paste functionality on the Nook Tablet is one of the most annoying "features" of the B&N firmware and it affects not just geeks like me but also the average user. This thread and this thread are two of many, many threads complaining about the missing copy & paste. This thread proposes a "fix" by combining the Hacker's Keyboard and Swype, but is still really lame.
The method I will describe here solves the problem by replacing /system/framework/framework.jar which contains the code for Android widgets like text fields. I have merged into the stock /syste/framework/framework.jar the code responsible for copy & paste from the Android source code.
Instructions
Video walkthrough: http://www.youtube.com/watch?v=7V70a3FYbt4
0. Before you proceed, know that THIS IS EXPERIMENTAL SOFTWARE THAT PROBABLY VOIDS YOUR WARRANTY AND MAY PERMANENTLY OR TEMPORARILY BRICK YOUR TABLET. Even though it worked for me, it may not work for you, and worse, it is quite possible that it could cause your tablet to boot-loop or die. I AM NOT RESPONSIBLE FOR ANY POSSIBLE DAMAGES TO YOUR TABLET / ANYTHING ELSE CAUSED BY THIS METHOD. BY USING IT YOU AGREE TO ASSUME ALL RESPONSIBILITY FOR YOUR ACTIONS.
1. Your tablet needs to be rooted for this to work. If you have not rooted it yet, search this forum for instructions.
2. Since we will be copying files to /system, you will need to install ES File Explorer or Root Explorer or whatever other app that allows you to do that.
3. Download the file that corresponds to your OS version from below:
1.4.2 (16GB/8GB): http://www.mediafire.com/?5pf2aegq02194lq MD5: ef35d35daffd0d9574f48a43ccc4b58c1.4.0 (16GB): http://www.mediafire.com/?es6gd31wzr7yk8a MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
The 1.4.0 version has been reported to cause boot loops for some people, while it has worked for others. You have been warned.If you're on a different OS version, post the file /system/framework/framework.jar form your tablet and I will make a package for it.
4. Extract file contents to microSD card, and insert microSD card into the tablet.
5. Using ES File Explorer / Root Explorer, copy the extracted file framework.jar.new to the directory /system/framework/. (If you're using ES File Explorer, make sure "Up to Root", "Root Explorer", and "Mount File System" are checked in settings.)
6. Copy the extracted file uim-sysfs to /system/bin/.
7. Go to /system/bin/, and change the permissions of the file uim-sysfs to executable. (If using ES File Explorer, long press -> Properties -> Change -> Check everything under "execute".)
8. Power off tablet and power on again. The tablet should take much longer to boot this time than normally, so no need to worry. When the tablet boots up, you will most likely see lots of force close dialogs. This is normal.
9. Wait one minute. You could be stuck in a boot loop if you don't wait.
10. Power off tablet and power on yet again. This time it should also take much longer to boot; the boot times will return to normal after several reboots.
11. Profit.
Force close issues
The first time you run some (read most) apps after applying this hack would likely result in force closes. While annoying, there is no way to get around it due to how the Dalvik VM caches references to /system/framework/framework.jar. In addition, every time you install new apps or update apps, you will have to reboot the machine before those apps are usable; you will get a force close when you try to use those apps until you reboot.
The solution is simply to reboot your tablet each time you get a force close error from an app that worked fine before this hack. The force close error for that particular app should go away following a reboot. If you get a force close from another app after that, just reboot again.
How it works
The information below is for people interested in understanding how this stuff works. If you just wanted to enable copy and paste on your tablet, you can stop reading.
This hack is based on the exploit explained at http://forum.xda-developers.com/showthread.php?t=1534518. The uim-sysfs script in the attached file saves the stock /system/framework/framework.jar, copies over my modified framework.jar.new, and restarts the zygote process. After the zygote process has loaded my framework.jar.new, the uim-sysfs script restores the stock /system/framework/framework.jar so that /init will not bail on the next boot.
To enable copy & paste in /system/framework/framework.jar, I decompiled the stock implementation and merged in related code from AOSP. The two classes I changed are android.widget.TextView and android.widget.EditText. For android.widget.EditText, I simply used the AOSP implementation because the only difference between the two was in the enabling of copy & paste. I manually merged android.widget.TextView because there appears to be B&N enhancements in it in addition to disabling copy & paste.
The exact steps I took as well as a diff of my modifications are documented in post #12.
Disclaimer
Again, this is experimental software. That it worked for me does not mean it will work for you, or that it won't brick your tablet. I am not responsible for any possible damages resulting from using this method.
Here i post framework.jar from stock 1.4.0 rooted
~ Veronica
lavero.burgos said:
Here i post framework.jar from stock 1.4.0 rooted
Click to expand...
Click to collapse
OK. Looks like the framework.jar from 1.4.0 is different from 1.4.2; I've merged in the same changes. If you're feeling brave, the package I've made for 1.4.0 is here.
MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
Can you confirm whether this works?
16gb Nootlet with 1.4.0 rom, rooted, OTA blocked yada yada.
Stayed at the "read forever" screen almost forever, then finally started up. Fellow victims take note, it isn't dead so be patient.
Lots of FC, the last persistent one was the launcher (ADW ipaidforthis version)
Powered off and on again after waiting way longer than 1 minute.
Second boot forever at "read forever" screen so far.
If it comes back to life I'll try the 1.4.0 version & let you know.
[Edited to add}
... time passes ...
Any way out of the "ADWLauncherEX" force-close loop? Does Android have a "safe mode" boot option like Windows? (sorry)
No, I haven't installed CWM recovery yet. Remind me to do that if this thing ever gets over its mental breakdown.
jichuan89 said:
OK. Looks like the framework.jar from 1.4.0 is different from 1.4.2; I've merged in the same changes. If you're feeling brave, the package I've made for 1.4.0 is here.
MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
Can you confirm whether this works?
Click to expand...
Click to collapse
Thanks can't test right now 'cause im finishing another project and then i have to test the tun.ko module for CM9 busy bee .
~ Veronica
cellhead said:
Stayed at the "read forever" screen almost forever, then finally started up. Fellow victims take note, it isn't dead so be patient.
...
Second boot forever at "read forever" screen so far.
Click to expand...
Click to collapse
Thanks for mentioning this. Will add to instructions.
cellhead said:
Any way out of the "ADWLauncherEX" force-close loop?
Click to expand...
Click to collapse
Getting FC's is normal - as the instructions state you probably have to reboot a number of times before all FC's disappear. Any luck so far? If not, please let me know and I will post a recovery SD card image that will allow you to undo this hack.
Also - as I said clearly in the instructions (Compatibility section), before you try this out on your 16GB, you should post your /system/framework/framework.jar so I can verify that this works on the 16GB. I don't have the 16GB tablet so I don't know if this works on it at all. Anyone?
Thanks. You may want to feature the version info prominently in the OP. I got my issue solved in a roundabout way when it finally went into a boot loop and triggered the factory reset. That got me back to 1.4.0 unrooted, and without the FC problems. Reran indirect's rooting script and I'm back to some semblance of normality.
Ain't complaining, I took on the risk of trying your copy/paste fix and went on an unplanned adventure. Such is life as a RL software tester ;-)
I'll wait and see how things shake out. You're onto something good here, so once it's a little safer for the normals to apply it, I'll give another go.
For the record, 16g Nook tablet, rooted via indirect, OTA blocked, v1.4.0
cellhead said:
You may want to feature the version info prominently in the OP.
Click to expand...
Click to collapse
You're right...really sorry about that.
On the other hand, did you try the files in the original post, or did you use the files for 1.4.0 I posted in the 3rd post?
The ones in the original post. Then I read the third post, but was unable to get it to boot far enough that I could replace the files and try again.
Sent from my BNTV250 using xda premium
cellhead said:
The ones in the original post. Then I read the third post, but was unable to get it to boot far enough that I could replace the files and try again.
Click to expand...
Click to collapse
The files in the original post are modified from 1.4.2 and would most certainly not have worked on 1.4.0...I should have made that clearer. Sorry.
The files in the 3rd post though are modified from 1.4.0 (thanks to lavero.burgos) and should work for you. Any chance you could test them out?
--- EDIT ---
Also - I've made a bootable SD card that will remove this hack and fix the tablet even if something goes wrong and you cannot boot into the system to remove the files directly. I can post it if someone needs it.
Cool hack, but why all these doubts and asks for 16gb's framework.jar ? What users have on devices comes from vendor firmware package(s), and you can see at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/ that there's no separate versions for 8gb vs 16gb. That page (and pages for other releases) should be also the authoritative place for getting framework.jar .
On the related note, would you care to provide exact instructions how to make framework.jar with c&p functionality? That would help to keep it updated across vendor upgrades, and also for making sure that new framework.jar contains only changes related to c&p and nothing else ;-). Granted, such instructions would be long and boring, so writing them in the shell script language rather than English would be a good idea ;-).
pfalcon said:
Cool hack, but why all these doubts and asks for 16gb's framework.jar ? What users have on devices comes from vendor firmware package(s), and you can see at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/ that there's no separate versions for 8gb vs 16gb. That page (and pages for other releases) should be also the authoritative place for getting framework.jar .
Click to expand...
Click to collapse
Thanks for the link! I went and downloaded the update archive and extracted it, and can confirm that the /system/framework/framework.jar in that archive (which I'd assume is the same as on the NT 16GB/1.4.2) is different from the same file on my NT 8GB/1.4.2., which confirms my hypothesis in posts #11 and #14 in http://forum.xda-developers.com/showthread.php?t=1517513&page=2. The bizarre thing is that if you unzip the files they produce the exact same content; it looks like they differ only in some sort of signature. But this means that my framework.jar will work on both the 8GB and 16GB on 1.4.2. So thanks again for the link!
pfalcon said:
On the related note, would you care to provide exact instructions how to make framework.jar with c&p functionality? That would help to keep it updated across vendor upgrades, and also for making sure that new framework.jar contains only changes related to c&p and nothing else ;-). Granted, such instructions would be long and boring, so writing them in the shell script language rather than English would be a good idea ;-).
Click to expand...
Click to collapse
What I did was this. You need zip, unzip and a tool called apktool. I'm assuming the framework.jar from the Nook is called ~/framework.jar.nook and the framework.jar from vanilla Android (AOSP) is ~/framework.jar.aosp.
1. Extract framework.jar into a directory z:
Code:
$ unzip framework.jar -d z
2. Use apktool to disassemble framework.jar.nook:
Code:
$ apktool d ~/framework.jar.nook
3. Disassemble framework.jar from AOSP.
Code:
$ apktool d ~/framework.jar.aosp
4. Compare and modify framework.jar.nook.out/smali/android/widget/{TextView,EditText}.smali against framework.jar.aosp.out/smali/android/widget/{TextView,EditText}.smali. My diff file can be downloaded here. Apply diff with
Code:
$ cd framework.jar.nook.out; patch -Np1 < jichuan89_nook_text_hack.diff; cd ..
5. Recompile Nook's framework.jar:
Code:
$ apktool b framework.jar.nook.out
6. Repackage modified Nook's framework.jar into ~/framework.jar.new
Code:
$ cp framework.jar.nook.out/build/apk/classes.dex z/classes.dex
$ cd z; zip -r ~/framework.jar.new META-INF classes.dex preloaded-classes; cd ..
framework.jar in that archive (which I'd assume is the same as on the NT 16GB/1.4.2) is different from the same file on my NT 8GB/1.4.2
Click to expand...
Click to collapse
I just tried to compare framework.jar I have on my device after 1.4.2 OTA update vs downloaded from B&N site - they turned out to be the same, md5sum is 795ae49e2b05b05c999a424a7d84b36b. Anyway, good news that contents were the same in your case too. It might be that 8Gb's initial in-flash 1.4.2 indeed was packaged differently than 16Gb's 1.4.2 update (that's idea somehow backed by the fact that 16Gb's initial in-flash 1.4.0 is not available on B&N site). Again, good to know that actual contents are the same, so 1.4.3 would be common either (which makes full sense, otherwise B&N just makes it harder on themselves).
What I did was this.
Click to expand...
Click to collapse
Thanks for the instructions and the diff! I with that all hacks posted on the forum came in such form ;-)
pfalcon said:
I just tried to compare framework.jar I have on my device after 1.4.2 OTA update vs downloaded from B&N site - they turned out to be the same, md5sum is 795ae49e2b05b05c999a424a7d84b36b.
Click to expand...
Click to collapse
Nice - thanks for confirming this. That's really helpful to know.
pfalcon said:
It might be that 8Gb's initial in-flash 1.4.2 indeed was packaged differently than 16Gb's 1.4.2 update (that's idea somehow backed by the fact that 16Gb's initial in-flash 1.4.0 is not available on B&N site). Again, good to know that actual contents are the same, so 1.4.3 would be common either (which makes full sense, otherwise B&N just makes it harder on themselves).
Click to expand...
Click to collapse
Right - it would make economic sense for B&N to make the software on the two tablet models to be as close as possible. I do hope they'll make their and our lives easier by just using the same version of the same damn files in the next update for the two models, as you said.
Sent from my Nook Tablet using XDA
I can make CWM flashable zip with original framework.jar for the ones having troubles until is fully tested. Tomorrow i'll jump back to stock 1.4.0 to test this hack and report back.
~ Veronica
A flashable zip would be cool if for no other reason than simplicity and reduced panic on the part of newcomers and when re-flashing the stock ROM.
I'm going to try this, so with me luck, but first: Do I need to boot into CWM to do this?
CRE said:
A flashable zip would be cool if for no other reason than simplicity and reduced panic on the part of newcomers and when re-flashing the stock ROM.
I'm going to try this, so with me luck, but first: Do I need to boot into CWM to do this?
Click to expand...
Click to collapse
No - this is for the stock firmware. CWM should have copy & paste already because it doesn't use B & N's framework.jar.
CWM as in ClockWorkMod not CM7 as in CyanogenMod v7.
EDIT:
To clarify, I didn't know if I could do this while the NT was booted normally or if I needed to boot with ClockWorkMod to ensure that the OS didn't try to access that file.
CRE said:
CWM as in ClockWorkMod not CM7 as in CyanogenMod v7.
EDIT:
To clarify, I didn't know if I could do this while the NT was booted normally or if I needed to boot with ClockWorkMod to ensure that the OS didn't try to access that file.
Click to expand...
Click to collapse
No. If there were requirements I would have put them in the instructions. It doesn't matter how you boot.
Sent from my Nook Tablet using XDA
Thank you. I guess I'll repartition first then get this out of the way too.
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
waldojim said:
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
Click to expand...
Click to collapse
Well, I found a solution for now. Fire up Linux, use cat to combine all three files, then use tar to extract the contents. Not sure why this needed split in the first place, but at least the files can be extracted.
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
waldojim said:
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
waldojim said:
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
Click to expand...
Click to collapse
I guess what I meant to say by "zipped" was just in general they are compressed by the recovery in a way that it knows how to go and use them to restore data to the device.