Hello,
I have updated my AT&T Dell Streak to 2.1 and now I am in need of the original stock bootanimation.zip file. Can someone with a Dell Streak, with build 6601, run this command:
Code:
adb pull /system/media/bootanimation.zip ./
and post it to this forum or provide a link?
I will use this to replace the 2.1 boot animation (O2). Thanks in advance!!!
Last but not least, does anyone know how to remove the default RSS Widgets? Thanks again!!
More info on how to use the adb command:
http://forum.xda-developers.com/showthread.php?t=502010
http://www.youtube.com/watch?v=1UF5w1dKe2U
http://www.youtube.com/watch?v=A1SOSXwkc_8
If you can give me a little more detail and a step by step on how to exactly do this, I will do it for you.
Is everything still working ok with the Root you did last night? I am thinking of doing this tonight.
Everything is Fine!!!
Hey @mjaverto, thanks for willing to help! And yes, everything is fine; root worked perfectly!! It is what allowed me to update to 2.1 :-D
As a matter of fact I have modified my 2.1 ROM quite a bit:
- Removed O2 boot animation
- Disabled the black popup window that replaced the standard menu bar. I am back to using the 2.1 grey menubar
- Removed/disabled bloatware:
Twitter
Facebook
Getting started guide
Outlook task and notes
RSS Widgets
AmazonMP3 (Replaced with US Version from my Nexus One)
Also modify the build prop to boot US Locale by default and other minor changes. Now all that's left is to change H symbol to 3G symbol and add stock US bootaninmation.zip. That's where you come in. LOL!
Anyways, I am not sure how familiar you are with the Android SDK, but it comes with a tool called "adb." This tool allows you to do all sorts of debugging. It also give you the ability to push and pull files from the Android device's file system.
What I need someone to do is install/download adb and the command from my earlier post. If its done correctly, you will be able to pull files from the Streak's filesystem.
The file I need is:
bootanimation.zip (adb pull /system/media/bootanimation.zip)
I am not sure what OS you use, but here is some more info on adb (Windows specific): http://www.youtube.com/watch?v=1UF5w1dKe2U
http://www.youtube.com/watch?v=A1SOSXwkc_8
Not super familiar but I think I can do this for you. I'm guessing I will need the root done first to be able to use "adb"? Maybe you can share your 2.1 Rom with me after you change these last few things as I'd love to upgrade.
*Windows 7 64x by the way. Should that work ok?
If I have any questions I'll shoot you a PM.
Actually...
No, root isn't necessary. You will only be pulling (copying) files from the filesystem; root is only needed when you want to write to the filesystem and run root system apps.
...And there is one problem with sharing my ROM... I have no idea how to package it. Dell uses, as far as I can tell, a proprietary ROM package (.pkg) format. The best I could do is walk you through the process of getting 2.1 installed. I am basically modifying the ROM on the device.
Hopefully, someone will develop some neat way to backup, modify, and package ROMs for easy installation. Heck, a way may exist... Maybe someone could chime in and enlighten me.
I am not sure about Windows 7, I run Linux. My guess is that you shouldn't have any problems. PM me if you have any more questions or concerns.
***Edit: Is that path you have above correct for sure? I keep getting remote object does not exist.
Upload: I attached tools.zip. *Note the two files inside are the only two files I could find named BootAnimation on my phone which is stock 1.6 ATT US.
Please let me know if I can help with anything else.
Try this...
Try this:
Code:
adb shell ls /system/
and post the output
I posted two "BootAnimation" files I found above
See output:
Cool!
Now type:
Code:
adb shell ls /system/media/
Let see what this produces. Hopefully we will see the file:
Code:
bootanimation.zip
listed.
Nope
Nope sorry. I did a search of the whole device with Astro File manager and it searched all these folders. The above two are the only ones with boot animation.
A search for "boot" yielded these 4. There is no bootanimation.zip:
system/bin/reboot/
system/bin/bootanimation/ (attached in above post)
system/customization/BootAnimation/BootAnimation.xml (attached in above post)
system/bootpriority.xml
sorry.
Private msg...
@mjaverto, check your private messages...
Here ya go mate
I zipped up the bootanimation folder for you from my US Dell Streak Build 6601
Enjoy!
mistadman said:
Hello,
I have updated my AT&T Dell Streak to 2.1 and now I am in need of the original stock bootanimation.zip file. Can someone with a Dell Streak, with build 6601, run this command:
Code:
adb pull /system/media/bootanimation.zip ./
and post it to this forum or provide a link?
I will use this to replace the 2.1 boot animation (O2). Thanks in advance!!!
Last but not least, does anyone know how to remove the default RSS Widgets? Thanks again!!
More info on how to use the adb command:
http://forum.xda-developers.com/showthread.php?t=502010
http://www.youtube.com/watch?v=1UF5w1dKe2U
http://www.youtube.com/watch?v=A1SOSXwkc_8
Click to expand...
Click to collapse
What steps did you take to update to 2.1?
Which steps did you take to update the 2.1 rom?
I was alble to flash the clockwork recovery rom but could not boot it when the device rebooted...
mistadman said:
No, root isn't necessary. You will only be pulling (copying) files from the filesystem; root is only needed when you want to write to the filesystem and run root system apps.
...And there is one problem with sharing my ROM... I have no idea how to package it. Dell uses, as far as I can tell, a proprietary ROM package (.pkg) format. The best I could do is walk you through the process of getting 2.1 installed. I am basically modifying the ROM on the device.
Hopefully, someone will develop some neat way to backup, modify, and package ROMs for easy installation. Heck, a way may exist... Maybe someone could chime in and enlighten me.
I am not sure about Windows 7, I run Linux. My guess is that you shouldn't have any problems. PM me if you have any more questions or concerns.
Click to expand...
Click to collapse
You Are Man!! Thanks!
Thanks! You even grabbed the images! Awesome!!
Anyways, looks like you missed a step with getting 2.1. You need to install the stock UK recovery image: http://www.romraid.com/paul/streak/recovery.stock.img
This will get your recovery image to accept UK ROMS. From here, you should be able to flash 2.1 directly.
See @Greenarcher707's excellent post (http://forum.xda-developers.com/showpost.php?p=7668927&postcount=6) on this forum for detailed guide. Since you have already installed the clockwork recovery image, you should be able to skip steps 1 and 2.
Once you have downloaded the image: (update-6941-21.pkg | http://www.mediafire.com/?bb9cvm5uaap2z8k), save it to the root of your SD as "Update.pkg."
The last step will be rebooting the phone into the recovery mode by holding "volume up" + "volume down" simultaneous and pressing the power key. From here it should be self explanatory.
Good luck and let me know how it goes. Hit me up if you have any more questions and thanks again for your help!!!
US Stock ROM Build 6601?
Awesome!! well I see you have to flash the UK stock rom which has a lower build than ours...Is there anywhere you can download the stock US Rom Build 6601 in case we want to go back to stock? Since the nandroid backup is not working in clockwork..I cannot do a a rom backup
mistadman said:
Thanks! You even grabbed the images! Awesome!!
Anyways, looks like you missed a step with getting 2.1. You need to install the stock UK recovery image: http://www.romraid.com/paul/streak/recovery.stock.img
This will get your recovery image to accept UK ROMS. From here, you should be able to flash 2.1 directly.
See @Greenarcher707's excellent post (http://forum.xda-developers.com/showpost.php?p=7668927&postcount=6) on this forum for detailed guide. Since you have already installed the clockwork recovery image, you should be able to skip steps 1 and 2.
Once you have downloaded the image: (update-6941-21.pkg | http://www.mediafire.com/?bb9cvm5uaap2z8k), save it to the root of your SD as "Update.pkg."
The last step will be rebooting the phone into the recovery mode by holding "volume up" + "volume down" simultaneous and pressing the power key. From here it should be self explanatory.
Good luck and let me know how it goes. Hit me up if you have any more questions and thanks again for your help!!!
Click to expand...
Click to collapse
Unfortunately, I don't know if a stock 6601 ROM exist. I figured that at some point the internets would produce one :-D But for now, those of us that took the plunge are stuck with 2.1 for now.
Thanks cemian!!
FYI...
I just completed the port of the stock boot animation to the 2.1 image. See: http://forum.xda-developers.com/showthread.php?p=7681745#post7681745 for more information.
Thanks again @cemian for your assistance!!
I'm thinking really hard of upgrading to 2.1. but a lil scared but no stranger to flashing.how is this flashing compared to wm flashing.
eastside770 said:
I'm thinking really hard of upgrading to 2.1. but a lil scared but no stranger to flashing.how is this flashing compared to wm flashing.
Click to expand...
Click to collapse
I find it is alot easier than WM once you get the hang of it. I also find that Android phones are harder to brick than WM phone, but not impossible. Just make sure you do plenty of research before you take the plunge. Good luck!!
I've flashed pre-update SBF and am only able to aqquire root while using SuperOneClick. Before that, when I try using files such as Adeo or GingerBlur I keep getting an error that says either device cannot be found or unable to chmod psneuter such as when i'm trying to use the retain root files. Am I missing something? I've checked environment variables to ensure that they're working, that usb debug is on, and thaty connections are good. What stumps me the most is that my first attempt at installing Gingerblur and Webtop MOD worked with no issues. I only restored back to SBF because i wanted the update with root but right after flashing to SBF, I tried bat files and i get an error message. I've yet to see any post on here that has an answer to this issue please help because if I can't get this to work there'll be no reason for me to keep the Atrix. Thanks to everyone in advance!
I've had SO many problems hacking my atrix.. and have managed to fix them all through this forum so I completly understand your frustration. The main thing I did that fixed everything, was to delete all previously downloaded mod files, then re download them all and place them at the root of your C drive. I'm assuming your using Windows.. None of the install.bat files worked for me until I moved them there..
Hello, friend. Thanks for the quick response. I tried what you recommended but am having the same issue. It doesn't make sense right now. I haven't added anything new to my PC nor have I installed any new programs. All i did was flash SBF to attempt to utilize retain root and then update to new version however my device cannot be detected. If anyone can help out it would be much appreciated.
Try putting the USB connection in mass storage mode. If your computer wants to find drivers, let it. Then give the script a whirl.
Sent from my MB860 using XDA App
I have been searching all morning for the answer to my issue, but evidently I am not using the correct words in my search. Either that or I am the first person to need to do this:
In an effort to try to get Netflix working on my Gtab running Vegan 5.1.1, I have been trying differing edits of the build.prop file. Since Netflix is working on my original version Droid, I have been using it as a model. All to no avail. So, last evening, fully aware that I might brick the gtab and willing to pay the price of a reflash if necessary, I copied the entire build.prop file from my Droid to my gtab and rebooted. Sure enough, won't boot.
I have backups of the original working build.prop but cannot access it by connecting my gtab to my pc through usb. I can access the files on the sdcard but cannot figure out how to get into the system folder so that I can replace the offending file with a good one. I thought that nvflash might be my friend, but after reading everything I can find on that tool it seems that it will just reflash to stock.
I can reflash my Vegan install, and may have to do so....but is it possible to just access the files in the system folder? If so, all I would have to do is to delete the current build.prop file and rename my backup file back to build.prop.
Anyone know how I can do this?
Joe
You can us ADB to push (or pull) files as well as accessing the command line on your gTab. ADB is a development tool, and is part of the Android development kit. You need to install the driver that comes with it, but first you need to edit the .INF file with a couple lines referencing the gTab. You can find additional information about ADB in other posts.
If recovery is working ok then you could reflash your ROM or craft a custom update to replace build.prop.
You could also nvflash just the system partition if you have an image for your ROM.
Lots of options.
Edit: Just looked at the Vegan 5.1.1 supplement update and it has a build.prop file in it. Reinstalling it would likely get you running again as long as you haven't made any other significant changes to the system files. It might revert a few system applications to older versions.
If you have adb set up and working, restoring your backed up build.prop would be trivial job. Let us know if you have adb working and then we can give you the commands you need to use.
As of right now, I do not have adb setup and working. Well, that's not quite true....I did set it up quite some time ago and used it on my Droid. Guess I need to reconfigure it for the gtab and then proceed from there?
Joe
Well, I resolved my issue by reflashing the VegaN rom, all is good now.
Joe
Hey, apparently I can't post in the dev forums yet so here is my question. I have after a week of experimentation gotten webtop2sd to work with a few different set ups on my Atrix with lapdock. However, here is the issue:
I have the latest and greatest Aura ROM Debloated version installed on my (obviously) rooted and unlocked Atrix. I have the webtopmod installed. I have busybox in the correct location. I have a working webtop with working configurator and lxterminal and all that goodness. Problem is when I run the webtop2sd program so I can move the image to the sdcard, the program does the partition part just fine, but consistently fails the file copy portion of the process and aborts. I have no idea what to do. Is it possible to manually copy the webtop image to the section of the sdcard set up for it and if so how?
Thanks ahead guys. Oh and Kudos to Sogarth for making this possible!
well the problem seems to have fixed itself. Though I have no idea why. I kept rebooting and trying and eventually the copying worked. Now have an unlocked jauntu desktop Thanks so much to everyone who posts in this forum regularly. now off to figure out the next part...
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
duuude im baked said:
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
Click to expand...
Click to collapse
Thought I would share some info I found when I ran into the wifi problem on my daughter's nabi. I did some searches on the internet and the typical answer I found for solving the wifi issue was "reset the device" or "unroot and return to stock rom - flash all updates and reroot". Being a glutton for punishment, and the fact I didn't want to reset the device, I searched and searched and was able to fix my daughter's wifi without doing a reset or unroot/reroot. Before I get into it I wanted to mention that wifi failures can happen for a number of reasons so while this worked for myself, it may not work for you.
Some prerequisites:
Most importantly; you need a rooted device. If you do not have root access you will not be able to write files or access the commands to fix the issue I am about to outline.
Some knowledge of linux would be helpful, but not necessarily required.
Lets get started:
Warning! It goes without saying but I will say it anyways - you can mess up your nabi by rooting it. Some of the commands below could mess up your nabi bad. If this scares you then you probably should not proceed any further. I am not responsible for any damage you do to your nabi.
Commands are listed between ' and ' - do not use the ' when inputing the commands.
Note: The first two/three steps are not necessary but they do give you insight as to how I was able to determine my problem. If following this doesn't fix the problem for you the logcat output may give you some important info that you can google that may help you fix your particular problem.
Note: Steps 5 and on can be skipped if you have a text editor (vi or nano) on your device. If you have a text editor loaded simply edit the conf file directly.
1. You will need to run the command 'adb logcat' in a command-line window and in your appropriate directory. Adb is available as part of the android sdk but can also be found stand alone since most people do not need the sdk.
2. Try to turn on the wifi. You should see the output of your adb logcat window scroll some data. If the wifi is not attempting to turn on at all sometimes you can move between the settings options then go back to the wifi settings and move the slider. If you cannot get your wifi to turn on you can scroll the window up and attmept to find the data from when the device started up. In the output you should see lines that talk about wlan0 and probably something that says "failed" somewhere. In my case I could see where the wlan0 enabled but then a few lines down it said something about "Line: 25 failed" and "failed to parse file".
3. The file is actually a configuration file used by the wifi kernal module/driver. In my case this file had become corrupted.
4. Set adb in root mode (won't work if the device does not have root access) by running 'adb root' at the command-line. You may need to click on an "allow root permission" window on the actual device after running this command.
5. Run 'adb pull /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb shell' from command line.
b. 'su'
c. 'cat /data/misc/wifi/wpa_supplicant.conf' - copy the output from the command and paste into a text editor (see note in step 6 on why NOT to use notepad).
d. Save the file as wpa_supplicant.conf, preferrably in the same diretory as adb.
e. 'exit' twice should exit you from the adb shell and return you to your command-line. If all else failes a "ctrl-c" should drop you out of adb.
6. Use a text editor to open wpa_supplicant.conf. The file should be located int he same directory as adb. If you are using Windows I would strongly suggest you NOT use notepad. Notepad will typically change all the EOLs (End Of Line) from \n to \r\n which will really mess things up worse.
7. In the file you should see "network={" entries. There maybe one entry, there maybe many entries. You can remove all lines between "network={" and "}" including the latter themselves. If you see your 'home' network listed you can leave it as the only entry and make sure its priority is set to 1 but it maybe better to remove it as well just in case it contains part of the corrupted data.
8. Save the file.
9. Do 'adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb push wpa_supplicant.conf /sdcard/wpa_supplicant.conf' from command-line.
b. Run 'adb shell'
c. 'su'
d. 'dd if=/sdcard/wpa_supplicant.conf of=/data/misc/wifi/wpa_supplicant.conf'
e. Do 'exit' twice to exit the adb shell. If all else fails then a "ctrl-c" should drop you ot of adb.
10. If the wpa_supplicant file was corrupted then the wifi should now be able to enable and you should now be able to connect to a network.
I hope this is helpful to at least a few people.