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!!
Related
I have spent days looking for threads so this neewb is about to break something. Well maybe not. I have my daughters Eris 2.1 and am trying to root it for her. I have tried several times with different methods. The issue is that I can get into recovery mode after every 1 click app but nothing I try will let me toggle to unzip to SD, or toggle to anything for that matter, volume wont do it and all track ball will do is let me select reboot. Man my DX was easy compared to the one click method.
HELP PLEASE,
If the trackball is having trouble scrolling, I'd install the trackball-optional custom recovery so you can use other buttons to scroll. There are instructions for doing this here:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
It sounds like you fall into "Scenario 2" which says you should follow the same method as "Scenario 1" to get rooted using the trackball-optional recovery.
I'll give it a shot, The help is much appreciated,
I am been trying to help him to get this thing to add the Custom Recovery, but every root format has not worked at all. Most are outdated or there are files missing. Specially on the link provided above. The download for the scripts no longer has Root_1 or Root_2, it has a bunch of other stuff there for gscript. Found an link on Droidforums for gscript for rooting and the scripts don't work.
Any complete instructions anywhere?
popfan said:
I am been trying to help him to get this thing to add the Custom Recovery, but every root format has not worked at all. Most are outdated or there are files missing. Specially on the link provided above. The download for the scripts no longer has Root_1 or Root_2, it has a bunch of other stuff there for gscript. Found an link on Droidforums for gscript for rooting and the scripts don't work.
Any complete instructions anywhere?
Click to expand...
Click to collapse
popfan,
I am not aware that any of the above links or files are missing... Can you point-out / tell me specifically which files you cannot access / download / link-to?
The root_part1 and root_part2 files are part of erisuser1's (bftb0's) Universal Root for Dummies! thread that I do reference in my AF thread, but these should still be up, active, and available.
So, I'm not sure if you are speaking about becoming rooted or installing a my trackball-optional custom recovery.
Let us know.
Cheers!
Im sure my kid has shuned me for leaving her Eris with someone so thanks to everyone for the help. Pop is helping me out and after moving file at the point where it says to open and look to see root 1 and root2 they are not there and there are a ton of other stuff. Also the pick look different than on the thread like the app has been updated. Also when doing the ball recovery there is no tools folder to be found. I'm sure pop wont touch it again till tomorrow so any other help / advice is more than welcome or it may cost me my Dx
malloneem said:
Im sure my kid has shuned me for leaving her Eris with someone so thanks to everyone for the help. Pop is helping me out and after moving file at the point where it says to open and look to see root 1 and root2 they are not there and there are a ton of other stuff. Also the pick look different than on the thread like the app has been updated. Also when doing the ball recovery there is no tools folder to be found. I'm sure pop wont touch it again till tomorrow so any other help / advice is more than welcome or it may cost me my Dx
Click to expand...
Click to collapse
LOL, sorry, didn't make/see the connection between your two posts .
Okay, let's try something new here...
Just a week or so ago, I re-packed jcase's 1-click rooting app to include my trackball-optional recovery image in lieu of the original recovery that his app includes.
So, let's have you re-root using the new 1-click app (all credit to jcase, both for his app and his threads both here http://forum.xda-developers.com/showthread.php?t=742228 and over at AF http://androidforums.com/eris-all-things-root/139178-universal-1-click-eris-app-apk-no-pcs-no-scripts-needed-easy.html).
Since you've already used the 1-click app before, then all you'll have to do is grab my new "trackball-optional" version:
https://sites.google.com/site/scaryalienware/downloads/one-click-tbo.apk
MD5 sum: 15763b51cf707c027cc73bc117e1fc39
(the "tbo" in the name stands for "trackball optional" ).
Just follow the same process you did before while running the 1-click app and you should end-up with my trackball-optional recovery installed.
Let me know how it goes (you'll be the first besides me that I know of that has tried it; the user that I created it for to test has not yet responded, LOL).
Cheers!
I tried this link below. It no longer has the root_1 and root_2 in it.
http://www.megaupload.com/?d=774XYFRA
I did use your "updated" 1-click app with tbo and it worked great.
Thanks!!
Too bad this phone was not as easy as my captivate.
popfan said:
I tried this link below. It no longer has the root_1 and root_2 in it.
http://www.megaupload.com/?d=774XYFRA
I did use your "updated" 1-click app with tbo and it worked great.
Thanks!!
Too bad this phone was not as easy as my captivate.
Click to expand...
Click to collapse
Glad that jcase's repackaged app worked for you. I'll update my documentation to make this available to others.
Also, re. the above Megaupload link...it works just fine for me (from my PC and from my Droid X) and includes all of the aforementioned root_part1/2 files.
I think you've fallen prey to a truncated download, which is not uncommon with Megaupload in my experience. This is also why is important to double-check the file sizes and MD5 checksums of files that you download so that you know you got the whole-shebang; notice that erisuser1 did include the MD5 in his thread for this file:
- Download gscript.zip (MD5 92796a8c6e61e8f1ee36e315c0acae7d)
I've often found it helpful to use a different browser other than the stock browser (like Opera Mini) when doing downloads via my Eris since the stock browser does seem to have more issues (timeouts perhaps) than it should.
Cheers!
Thanks to all this tuff till you hooked us up but now on to nightmare 2
I downloaded CyanogenMod7.1.0 RC1 [2.3.5 GingerBread NIGHTLY]
from this thread http://forum.xda-developers.com/showthread.php?t=944430&highlight=ROM
Got it up but it has no market so I can not get to titanium, boot loader or anything... It says to flash google apps after the rom but now Im back to the trackball / volume key issue because it's all in titanium. ??? I did a factory reset and it came back up as the new ROM, ???
EDIT UPDATE!!!!
Sorry for the hassle all, the "green" start call button works as the down after the download.. All is well.. I think..
Again thanks to you all, If I hear of any good deals on an Eris I will know why.
You need to download GAPPS to your sdcard. That is why you don't have market.
http://forum.xda-developers.com/showthread.php?t=944430&highlight=ROM
Its just below link for the rom and save it to your sdcard. Go ahead boot into recovery and wipe data, daliv-cache, cache; Flash Rom again, then flash gapps and reboot.
I'm a complete noob and I've searched the forums and can't find an answer to my questions. (I'm sure there's some answer in Japanese on a Japanese forum somewhere, but my Japanese is not up to that level.)
I have a Toshiba Regza IS04 from AU (in Japan).
Running Android 2.2.2
Baseband Version 5014.1907.39
Kernel Version 2.6.32.9-rel [email protected] #1
Build Number FFK300
I have been researching rooting on and off for months since I first got the phone and have decided I would like to root it. My reasons for rooting:
1. I want to get rid of all the apps that were pre-installed that I don't use.
2. I would like to have the latest version of Android 4.0 Ice Cream Sandwich. (I doubt that another authorized upgrade from au is ever going to happen, since the 2.1 to 2.2 upgrade.)
It seems from reading forums that there are special builds of an OS depending on the phone?
My questions:
1. What is the best way to backup my phone before rooting?
2. What would be the best rooting method for my phone (SuperOneClick?)?
3. How can I (or even can I) upgrade my Android to 4.0?
Thanks for any help!!
Sam
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Thank you so much for this response!
I have the same phone, and I've been wanting to root it for a long time. There were so many pre-installed applications that are just hogging room, especially since I can't read Japanese well enough (yet).
-T
I hope it works for you too!
I spent probably the equivalent of 2-3 days searching over the last few weeks, but couldn't find anything that I was comfortable with trying.
This morning, I finally got the nerve up to try superoneclick and was really disappointed when it wouldn't work. Then I started trying all kinds of methods, and about 8 hours later finally came across the method that worked!
It's probably the only thing frustrating sometimes about having a Japanese phone: lack of English support!
Now I'm just hoping I don't break it! I'm backing up all the apps with Titanium backup before I start deleting them one by one. I would hate to delete something that is crucial to the system and not be able to restore it. I'm also looking into other ways to backup the system.
One word of warning. Your au one market will not work unless you do one more step. It's mentioned in English in the readme file. I didn't bother because I never download from it anyway. (Although, I probably should just so I'll keep getting updates on some of the J apps that I do have.)
Deleted
Deleted
the rootkit d/l has been removed. anyone know where to get it?
The File
I'm not sure if this is against the forum rules, but I have a copy of the zip file (well, a zipped up copy of the folder) from my computer. If you pm me, and I can send you it.
-T
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
link die;
anyone help me another link for that file & help me root this device step by step?
Thanks
The post above dissolution said they had one, but good luck getting a reply. I'm emailed twice and nothing.
私はローボーボブ。 Haro！！
Latest rootkit for FFK300
Here is the latest rootkit,
IS04 root toolkit ver 4.0.1
http://www1.axfc.net/uploader/Ne/so/131631
DL key ; is04
And other informations;
- Custom kernel(overclock, compcache, +others)
http://marijuana.ddo.jp/is01/index.php?moddir=downloads&action=visit&cid=9&lid=47
- Custom kernel(CWM on ramdisk, ported from Xperia, modUI)
http://www.mediafire.com/?jkz5nek59y3hpaf (reported kernel unstable)
# FFK301 stock ROM update - (rootkit does not work, still can be rooted.)
http://spf.fmworld.net/sw_update/kddi/is04/update/
- scroll to bottom and click on blue rectangle.
# kernel source code
http://spf.fmworld.net/oss/is04f/index.html
- some files are missing, extract them from T-01C(DoCoMo).
http://www.fmworld.net/product/phone/sp/android/develop/t-01c_froyo_oss/
help! rooting regza inquiry..
[/COLOR]
samkk75 said:
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Click to expand...
Click to collapse
hi!
I am a newbie here and like you all, I would also like to root my regza phone. Can someone give a working auto_rootkit because the link above is not working. I have searched it as well on the net but still all will lead me to dead hotfile link. Or someone could send me the file instead to my yahoo mail [email protected] tnx in advance
And also i have downloaded this rootkit instead from IS04 and downloaded. After dowloading, I click the adb file and it appears a command screen with commands running so fast. Next i did click the root file and there appeared a command screen with all sorts of command running so fast. My question is, i did not received any confirmation that the rooting process was succesfull. And also i have read to other forums that one thing you will notice that rooting was successfull is that 'superuser" will be automatically installed.
Please help me on this one. To be honest I started exploring this process since i have this phone and there are apps that i wanted to uninstall not unless i root the phone.
Thank you in advance
marvz,
Dissolution said:
I'm not sure if this is against the forum rules, but I have a copy of the zip file (well, a zipped up copy of the folder) from my computer. If you pm me, and I can send you it.
-T
Click to expand...
Click to collapse
hi there!
Can you send to my e-mail [email protected] the said file so that i could root my regza phone?
thank you for your help> ^_^
Question to get root on phone regza
samkk75 said:
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Click to expand...
Click to collapse
Hi
I have this phone too. And I try to get root, you can send for me the link of you downloaded and explain for me how you made it.
Other question, I can use this phone to call in brasil?
Thank you.
:good:
My phone just had this phone and I'm trying to update it before rooting. It came with 2.1-update 1 OS version and I'm trying to update the phone to it's latest official 2.2.2.
I've downloaded the necessary 256mb file update but it didn't work. Even tried using the recovery but is still not working.
Based on my research about this phone, There's no way to update without the phone downloading the app from the official website, using the SIM and au logins.
We've lost the sim (UIM) card that came with the phone. So I guess its stuck on its current OS. I'm having trouble installing apks (Gingerbreak and even normal apps) as it always gives me the error "parsing error" or something.
Is there anyone could help?
EDIT:
I have successfully updated the phone from Android 2.1-update1 to Android 2.2.2.
Download all the necessary files here:
http://www.fmworld.net/product/phone/is04/
I have used the method of updating from the least upgrade and up to the latest. I have managed to download 3 separate files for the upgrade, namely:
IS04_RC2_RC3RE_DL.zip
IS04_RC_4.zip
IS04_TO_SP_FYRC_4.zip <- froyo update
I have extracted all the files on the sd card. make sure that the ".enc" file is found on the root of the SD Card and on the "prg" folder.
I have updated it using the recovery mode (power + volume up + camera button).
I am now currently trying to Root the device using Gingerbreak and seems that it's taking too long to root.
Also. I have able to root the 2.1-update OS using z4root.
help me
hi.. i didn't my phone plz send me ...................................................auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
thnxx.. in advance..
Root
I rooted mine with http://unlockroot.com/
root_toolkit_is04_v4.3.zip
www1[dot]axfc[dot]net
/uploader/Ne/so/135399
Password is "is04".
suhax
www[dot]4shared[dot]com
/zip/pHLT8kqe/suhax.html
Sent from my IS04 using xda premium
more detail please
samkk75 said:
.....
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
.....
.....
I hope this can help someone else.
Click to expand...
Click to collapse
Thx so much for your posts.
I am so glad to finally find someone with the same phone, the same problem and intentions
I do, however, need more info:
Did you extract the files into any particular folder? You obviously hooked up in de-bug mode, but did you command prompt anything?
I tried your steps but get nothing to 'hit enter' on. I have also tried the other (different version) toolkit.
You can IM me or email or post or come around and root my phone yourself - I will sell you my car, house, wife...
... as you can tell I am a little frustrated ...
lets just IM/email for now
Thx in advance,
Kaz
---------- Post added at 12:34 PM ---------- Previous post was at 12:29 PM ----------
orgia82 said:
I rooted mine with http:!!unlockroot*com/
Click to expand...
Click to collapse
Didn't get to try it - was too tied down with all the additional ^%$&#$ I had to download to get to it.
help
as everyone can see that link isnt working anymore,so im here asking someone whos still have it to upload :fingers-crossed: again．．．．
I live in UK, with a Streak 5, updated by Dell to 2.2.2. This is my first smartphone, but I soon stopped using it out of disgust with all the unremovable bloatware.
However, a few weeks ago I managed a successful root (GingerBreak), then used ADB via Win XP to remove the APKs for facebook, ooVoo, twitter, radio, Amazon and a zillion others. The phone became a delight to use, but then, emboldened by my new found power, I rashly assumed that if I removed Stage there would remain a basic default Android launcher. So I very stupildy removed (without backing up...!..) all .APKs with the word Stage in them.
Oh woe.
Phone was still fine, would turn off, reboot (into a blank screen), file system still naviable from my PC with ADB shell, but no way to launch apps or even access the menu from the phone.
So then I did the next silly thing -- factory reset, not realizing this does not restore apps. Now booting never completes after making it past sparkling DELL animation, and even if it finished booting into a blank screen, without root access I would no longer be able to reach the file system via ADB.
However, I successfully connected the phone to my Win XP PC in fastboot mode, but then didn't know what to do next.
I presume I need to get the missing .APKs with Stage in their name back into /system/app from where I so stupidly removed them. I have downloaded update-stageUI360-2.zip, which appears to contain some hopeful-looking .APKs that I presume are intended for /system/app. They don't have the filenames I vaguely recall as the things I deleted, but perhaps that's because they are an update.
But even if those .APKs are what I need, without being able to boot or access the file system via ADB, how do I restore them to their rightful place?
I've read clever how-to stuff in Android fora until my head hurts, but I still lack a proper understanding of how most suggested actions actually work. For example I remain unclear about the word 'flash'. In the Old Days, I understood that to mean burn new data into a firmware ROM, but in Android fora it appears to be more like my current understanding of 'copy' or 'push' to the internal R/W storage.
I've also read and re-read the excellent XDA 'Dell Streak 5/Flashing Guide' but it packs so much pithy info so tightly I'm left going in circles trying to get a rounded picture, because when I seek the meaning of one word or concept, it's often described in terms of other concepts that I also don't understand.
Also I'm confused by extensions like .img, .apk, pkg, .sh, and how Android deals with them.
In the Old Days, a 'ROM' was a lump of read-only hardware, but in Android parlance it seems to mean some kind of pre-formed image. What does it contain, and how is it transferred to where it needs to be in the phone?
What is a nandroid ? What is baseband ?
And what's the difference between .zip and .apk ? If none, why the different extensions? is it so Android's installation management knows how to treat them ?
I apologise for the length of this post. If someone would tell me how to proceed, and hopefully explain what is happening behind those proceedures, I would be most grateful.
I don't have time for an exhaustive post, but here's the basics of what you need.
Flash streakmod via fastboot (look at the wiki)
Boot into streakmod, connect to pc with usb and enter adb shell
type this command:
mount -t yaffs2 /dev/block/mtdblock6 /system
type exit and adb push your needed apks to /system/app
reboot
This should get you up and going. You could find any of the free launcher's apks and just push that instead of all the dell stage apks. VTL Launcher is the first one that comes to mind that can be downloaded from the xda forums, just search for it. (Its not in the Dell Streak subforum)
lordmorphous said:
I don't have time for an exhaustive post, but here's the basics of what you need.
Flash streakmod via fastboot (look at the wiki)
Boot into streakmod, connect to pc with usb and enter adb shell
type this command:
mount -t yaffs2 /dev/block/mtdblock6 /system
type exit and adb push your needed apks to /system/app
reboot
This should get you up and going. You could find any of the free launcher's apks and just push that instead of all the dell stage apks. VTL Launcher is the first one that comes to mind that can be downloaded from the xda forums, just search for it. (Its not in the Dell Streak subforum)
Click to expand...
Click to collapse
Can u give me the link of VTL Launcher, I 'd like to test a new launcher
Sent from my Dell Streak
http://www.lmgtfy.com/?q=vtl+launcher
Is it not more easy to flash a newer rom?
go to the Wiki of dell streak and download a rom (351 ore 360 I would reccomend)
http://forum.xda-developers.com/wiki/Dell_Streak_5#Official
Copy the rom to your sd card (use a usb device or somethinge else to acces it) name the rom Update.pkg
powerup the phone holding down de volumekeys option 2 is for software upgrade. Try that and the phone has a new complete rom.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Many thanks for solutions, but now rooting question
My problem has been that no way could I boot into Streakmod recovery as advised by LordMorphus.
However, after abel2007's advice I managed to flash the full stock 360 rom, after installing the appropriate recovery (via Fastboot).
Now I wish to root, but still cannot boot into Streakmod, which appears to install successfuly via Fastboot, but then however many different moments I choose to press the vol buttons, it always reboots into stock recovery screen.
The universal response to a similar problem in other forum posts is that there is no way to root 2.2.2 or later without a custom recovery like Clockwork (which I haven't tried because it's not recommended) or Streakmod, (which doesn't work for me); but Gingerbreak rooted my previous OTA 2.2.2 before I screwed up by rashly removing all APKs with Stage in the name.
However, I'm scared to try it again in case it was just some freak result, or perhaps contributed to my original problem. Why doesn't anyone seem to recommend Gingerbreak?
And if that works but I still can't boot to Streakmod, I presume I won't be able to employ Nandroid; so might there be any other way of backing up my modified Android system?
Ok so I'm what you guys would call a newbie with Android, I've been an iPhone user for years (switched from Verizon to AT&T to get the iPhone because at the time it was an AT&T exclusive). However I'm a really big Google enthusiasts so I have followed Android from inception. Growing tired of how bad AT&T's reception was in my house I recently switched back to Verizon and I purchased the GS4. I'm very happy that I can make calls without the use of a Micro Cell, truthfully reliable coverage was the biggest reason why I switched carriers. Else I would probably got the GS4 or HTC 1 on AT&T.
Being a newbie I made some noob mistakes, however I'm glad to report non of my mistakes bricked my phone. My phone works flawless it's only the stock recovery that is jacked up. So to start off I naively though all S4's were 100% open when rooted, by that I thought I could simply install any ROM I wanted to as long as I was rooted. However it appears that Verizon made Samsung lock the firmware with the OTA updates, from what I gather now after reading is the initial firmware was ok but the subsequent OTA downloads introduced the locked boot. Which sucks for me because I willingly took both updates which put the ME7 and now the MI1 builds on my device.
When I started to root process I had the MI1 build and I performed the De LaVega root method (thank you Tomsgt for your videos)! At the time of root and right after the root I was still not aware of the difference with builds. At that point I attempted to install TWRP via GooManager, since I had the MI1 build it did not work. GooManager kept telling me there was no file for my phone or something similar.
Now this should have been huge red flag for me but I was persistent and I looked on TWRP's website and found the file for my phone along with the manual install instructions. I'm familiar with using a Linux command line so followed the instructions to write TWRP into /dev/block/mmcblk0p21 on my device.
After reboot my device failed to get into stock recovery mode, instead it goes back into download mode but has an extra line of text that says "Could not do normal boot". Since I originally hosed my stock recovery I have read up on the different builds and I have also successfully installed the clockmod recovery option. That all works fine it's just factory recovery is still hosed up and it's annoying me!
I know that was a bit long winded but wanted to give a little background. Now I hope I'm not the only guy/girl who has jacked up the stock recovery section. I was hoping someone had some instructions to fix. Heck I think (but I'm not 100% sure) that if I can get someone who still has stock recovery to copy/export what they have in /dev/block/mmcblk0p21, then I can download that file put on my sd card and then write that back into my system using the same dd input/output command I did before.
May not be that easy but that's what I'm hoping for, or maybe some suggestions. :fingers-crossed:
Thx,
Joe
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
kennyglass123 said:
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
Click to expand...
Click to collapse
Thanks kennyglass123, sorry it was posted in the wrong area!
Again I don't know if this will work but it's worth a try. For anyone who has a rooted Verizon GS4 and can get into stock recovery with no issues can I have you copy and export what's in /dev/block/mmcblk0p21 to an external file? For those who may not be familiar with Linux I have a few commands you can run below.
1.) Using terminal emulate create a folder to store the file on external card, in my example below I named it "StockRecovery" but you can name it whatever you want.
2.) su
3.) mkdir -p /storage/extSdCard/StockRecovery
4.) dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/StockRecovery/mmcblk0p21
This should create a file named mmcblk0p21 under the StockRecovery folder of your external SD card. If you could then either attach that file here or maybe upload the file to a public dropbox, or even e-mail that file to me I would really appreciate it!
Not sure this will fix my problem but it's worth a shot!
Thx,
Joe
garzjoe said:
Thanks kennyglass123, sorry it was posted in the wrong area!
Again I don't know if this will work but it's worth a try. For anyone who has a rooted Verizon GS4 and can get into stock recovery with no issues can I have you copy and export what's in /dev/block/mmcblk0p21 to an external file? For those who may not be familiar with Linux I have a few commands you can run below.
1.) Using terminal emulate create a folder to store the file on external card, in my example below I named it "StockRecovery" but you can name it whatever you want.
2.) su
3.) mkdir -p /storage/extSdCard/StockRecovery
4.) dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/StockRecovery/mmcblk0p21
This should create a file named mmcblk0p21 under the StockRecovery folder of your external SD card. If you could then either attach that file here or maybe upload the file to a public dropbox, or even e-mail that file to me I would really appreciate it!
Not sure this will fix my problem but it's worth a shot!
Thx,
Joe
Click to expand...
Click to collapse
Bump....
Still hoping there is someone out there who can help me out.
garzjoe said:
Bump....
Still hoping there is someone out there who can help me out.
Click to expand...
Click to collapse
If your phone is bricked I would recommend the Verizon Repair Assistant.
THIS IS A LAST RESORT.
This will fully update your phone but it will fix any errors.
southpaw5271 said:
If your phone is bricked I would recommend the Verizon Repair Assistant.
THIS IS A LAST RESORT.
This will fully update your phone but it will fix any errors.
Click to expand...
Click to collapse
Hmm I can investigate that but my phone is not bricked. I'm using it now to reply to you. Stock recovery is hosed...so when I power off and then hold Vol+, Power, Home key and then let go of power and keep holding the other two buttons. That key sequence gets my phone into recovery mode. However I can't get into that with my phone anymore.
Thx,
Joe
Hi all,
EDIT
Thanks to techdudester on the second page, getting rid of the malware is now even easier!
Just flash the image he found here with the following procedure and you're good to go!
Instruction:
1. Flash the new ROM.
a. Get the ROM here . (Use this ROM only if you have a Venstar V140D tablet!)
b. Follow the linked tutorial to install the flash software and flash the new ROM on your device with: Phoenix Suit.
Voila, ready!
Enjoy your malware free tablet!
Tips and tricks. (or something...)
Get adb working (needed for all the other tricks down below):
1. Download the Google development tools (sdk) here and install them on your computer. I assume you have windows 7 installed during the rest of this tutorial.
2. Connect your device to your computer and make sure it is installed correctly.
a. Connect your device while its powered on via USB to your pc.
b. Go to Start, right click "My Computer" and select "Properties". Click "Device Manager".
c. Right click the Android device with the exclamation mark and select "Update Driver Software...".
d. Select "Browse my computer for driver software".
e. Select "Let me pick from a list of device drivers on my computer".
f. Keep "Show All Devices" selected and click Next.
g. Click "Have Disk..." and click "Browse..."
h. You can find the drivers in the "SDKInstallLocation"\sdk\extras\google\usb_driver directory and click OK. Replace SDKInstallLocation with the location that you selected during installation of the SDK.
i. Select the "Android ADB Interface" driver from the list and click Next.
j. Confirm installation by clicking on "Yes". Sometimes you also have to click on "Install" if a screen pops up to ask you again if you really want to install the driver...
k. Click "Close".
To use it:
Open a command prompt (in search type "cmd" followed by ENTER) and go to the following directory ""SDKInstallLocation"\sdk\platform-tools".
If you want a backup of your tablets system directory (highly recommended!) use:
"adb pull /system C:\system"
where C:\system is the target location on your local computer where you want the backup of the system directory.
Remove the update package (this doesn't work for updating the tablet, so, useless.)
adb remount
adb shell
cd system/app
rm Update.apk
exit
Remove the unwanted apps (dragonfire.apk etc)
adb remount
adb shell
cd system/preinstall
rm *
exit
If you would like to have your tablet in the correct time zone after factory reset, you will have to adjust the build.prop file.
First you need to get it to your pc so you can edit it:
in the command prompt window and at the same location as in the tutorial above type "adb pull /system/build.prop C:\temp\build.prop".
Just in case, make a copy of the build.prop in Windows Explorer so you always have the original file if something goes wrong.
Now you can edit the build.prop, but DON'T EDIT IT WITH THE WINDOWS NOTEPAD! Use Notepad++ or similar to edit the build.prop.
After you made the changes (and be careful here, you could end up with a tablet that does not want to boot up, solution further down below) you have to upload the file back to your tablet.
in the command prompt type:
adb remount
adb push C:\temp\build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
Don't forget the last line! If you do not chmod the file (set the correct permissions) your tablet will not boot up.
Changes in the build.prop:
Time zone:
Default time zone is "persist.sys.timezone=Europe/London"
you can change this to your locale time zone like "persist.sys.timezone=Europe/Amsterdam" (for the netherlands )
Search the internet for valid time zones.
Change the default language:
The default language is determined by these two values in the build.prop:
persist.sys.language=en
persist.sys.country=US
For dutch change them to:
persist.sys.language=nl
persist.sys.country=NL
and again, search the internet for valid language values.
Higher brightness after factory reset:
Add the following line to the build.prop file (at the top of the file)
ro.ph.def_brightness=225
You pushed the build.prop without changing the permissions:
No problem. Just connect your booting tablet to the PC, install the driver if its not installed correctly like explained in the tutorial, and then change the rights via adb. It's no problem that it's not fully booted!
in a command prompt in the adb directory:
adb remount
adb shell chmod 644 /system/build.prop
adb reboot
If you pushed a wrong non functioning build.prop, just use this method to push the original build.prop (you know, the copy you made ) back to the device (followed by setting the correct permissions of course).
Remove the (in my opinion) irritating boot sound:
adb remount
adb shell
cd system/media
rm boot.wav
exit
rom download
can you provide another way to download the rom file ,i cant seem to get the registration process to work
stevethesignguy865 said:
can you provide another way to download the rom file ,i cant seem to get the registration process to work
Click to expand...
Click to collapse
I have dropped it here. Hope this helps
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
1ce/ said:
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
Click to expand...
Click to collapse
Yes, all applications will be removed. As soon as you configure the tablet again with the same gmail account, it will probably start installing the applications and games automatically, but in game progress will be lost for most (not online) games.
I am re-uploading the file. Will update this post with the link as soon as it finishes
edit: upload finished, get it while its there LINK
BlueFlame said:
edit: upload finished, get it while its there LINK
Click to expand...
Click to collapse
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
1ce/ said:
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
Click to expand...
Click to collapse
Yes, thats correct. Once unpacked it will be around 520 MB.
Good luck!
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Maylar said:
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Click to expand...
Click to collapse
On request. You can find it here. (Adjusted link. Stored on Google Drive)
Thanking you. Very much appreciated.
Thank's for a fantastic procedure... Worked very well.
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Is that the firmware that I provided?
If not, try to download it again.
If so, I think that your tablet has a newer firmware than this one. You could contact the seller of your tablet for the current (latest) firmware for this tablet.
If you get a newer firmware, please share
Image file invalid
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
mcwheelz said:
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
Click to expand...
Click to collapse
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
BlueFlame said:
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
Click to expand...
Click to collapse
Uploaded again! same link (just made it a new version in Google Drive).
Open Firmware failed - possible solution
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Try to put the image file in a directory without special characters (i.e. c:\temp). Worked for me.
wundabua
Te real FIX is In!
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
The REAL answer is actually very quick and easy compared to all these other recommended methods.
In the first place, model V140d image is only used for these infected tablets. The actual model is V11 and once you use the quick restore method I discovered, you will have a malware free V11 model. The whole secret to this method, is the fact that these units were designed to be quickly, automatically and completely restored in less that 5 minutes through the use of their built in micro SD slot.
Imagine that!
If you check your tablet that came new in the box as something other than V140d, the method I used will most probably not work for you.
Anyway, the quick method I discovered, can be seen on my own tech support site. To find it, Google: Just Call Techdude
Then click on the support link at the top of the page on my site and all will be revealed.
techdudester said:
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
Click to expand...
Click to collapse
Hi techdudester,
The combination "pro tech with 25 years in the trenches" and "very complicated "solutions"" sounds a bit strange.
But either way, a THANK YOU is in order!
The ROM you found works on my tablet (flashed yesterday) and so far so good. No popups and no unwanted application downloads!
I will adjust my initial post to incorporate this image.