Can you let us know if your out there using tmobile UK atrix, please!
Swyped from 'mount' Olympus
Bump
Swyped from 'mount' Olympus
nitrox1 said:
Can you let us know if your out there using tmobile atrix, please!
Swyped from 'mount' Olympus
Click to expand...
Click to collapse
i just ordered a unlock code for my atrix from cellunlock.net. its been 2 days as of now. i have tmobile us, still tmobile though lol
stratax said:
i just ordered a unlock code for my atrix from cellunlock.net. its been 2 days as of now. i have tmobile us, still tmobile though lol
Click to expand...
Click to collapse
Thank you for your reply. But I'm really looking for the UK Tmobile, sbf, or understanding of it.
Ps check out our uk orange thread, for a much cheaper unlock, and within 10 min!
Swyped from 'mount' Olympus
Bump
Swyped from 'mount' Olympus
im using a t-mobile uk atrix, got it yesterday
karl0ss said:
im using a t-mobile uk atrix, got it yesterday
Click to expand...
Click to collapse
Have a look in the about phone part and post up if you can
system version
Baseband version
Build number
system version - Version.4.2.23.MB860.T-Mobile.en.GB
Baseband version - N_01.92.00R
Build number - OLYEM_U4_2.2.3
any idea how i can root it? side loading apps seems to work without any hacks, as I was able to install some apks I had laying around on my dropbox, and I have installed some using Android Commander...but I can't work out how to root it, does GingerBreak NEED a real sd card inserted to work?
karl0ss said:
system version - Version.4.2.23.MB860.T-Mobile.en.GB
Baseband version - N_01.92.00R
Build number - OLYEM_U4_2.2.3
any idea how i can root it? side loading apps seems to work without any hacks, as I was able to install some apks I had laying around on my dropbox, and I have installed some using Android Commander...but I can't work out how to root it, does GingerBreak NEED a real sd card inserted to work?
Click to expand...
Click to collapse
Yep, it's worked on all the orange roms, and devices. Give it a whirl.
But before you flash a new rom over your stock tmobile, could you help us get you original sbf up on the forum. You will need to be rooted to do it.
It will help you in the long run, so if you have a problem you can return to your stock
Swyped from 'mount' Olympus
nitrox1 said:
Yep, it's worked on all the orange roms, and devices. Give it a whirl.
But before you flash a new rom over your stock tmobile, could you help us get you original sbf up on the forum. You will need to be rooted to do it.
It will help you in the long run, so if you have a problem you can return to your stock
Swyped from 'mount' Olympus
Click to expand...
Click to collapse
I have no problem doing that atall, i'm glad to help as much as I can...
so just to confirm, GingerBreak will only work with a sd card inserted, as I have tried it and it doesn't seem to do anything, but I don't have a sd card inserted atm..
how would i go about backing up the sbf afterwards? also what does sbf stand for?
thanks.
edit - just redone GingerBreak with a sd card and i can confirm I am now rooted..
can i not do any of the hacks around at the moment? as they all report versions im not on? e.g.
1.42_deodex_OlympusCamera.zip
1.57_deodex_OlympusCamera.zip
1.83_deodex_OlympusCamera.zip
also, what is deodex?
Strange, it's running a newer rom than the orange atrix, being as both orange and t-mobile are one of the same now, you would have thought orange would have had a update to the 2.2.3?
SBF means system binary file. basically its a completely stock system image. Flashing it thru RSDlite (software flashing application from motorola), will completely return your phone to stock.
Deodex: Basically, Android uses a a java based virtual machine as the bases for running programs. This virtual machine is called Dalvik. A .dex file contains the cache used by the Dalvik VM (called Dalvik-cache) for a program and is stored inside the .apk. A .odex file is an optimized version of the .dex file which gets stored next to the .apk as opposed to inside the .apk. This process is done by default to system apps. Deodexing is the process of converting the .odex files back into .dex to be stored inside the .apk so that things can be more easily modified. So a deodexed rom is one that has been through the deodexing process. Deodex can just as easily be called Unodex or any other pre-fix you wish to use.
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
For rooting check here.
http://forum.xda-developers.com/showthread.php?t=1046626
should be very easy, but you must have a sd card.
We are then after a couple of files off your phone, and a little information? Are you game?
Do you have any knowledge of using ADB?
If not have a look here to start, but goggle will be your friend on this.
http://android-dls.com/wiki/index.php?title=ADB
We're after a request for a firmware, we need to submit the following files (using adb pull):
/system/default.prop
/system/build.prop
/system/etc/motorola/bp_nvm_default/File_GSM
about phone > weptop version
Then we can hopefully grab your sbf, so we can use it for restoring the phone, if there's mistakes made.
Have to say I don't know about modding your phone, you'll have to try.
But that's why sbf, is important.
As devs have got around bootloader, I would get used to your phone, while roms like vanilla android, miui, and cm7, get ported over.
lonegunman said:
Strange, it's running a newer rom than the orange atrix, being as both orange and t-mobile are one of the same now, you would have thought orange would have had a update to the 2.2.3?
Click to expand...
Click to collapse
True but have you seen how much more the phone is to TMO renewal customers, compared to Orange renewal.
But looks like it could be a very good sbf to grab.....
Bump
Swyped from 'mount' Olympus
This guy was able to get our orange sbf in minutes so take a look: http://modmymobile.com/forums/659-motorola-atrix-4g-general/562049-atrix-firmwares-superthread.html
Edit didnt see u already posted about pulling those files woops
Hey guys, attached is the build.prop and default.prop file, the third folder you listed doesn't exist, or at least I can't see it...
www(.)mediafire(.)com/?1ducdwtg246qz57
webtop version -OSHWT_U1_6.54.0
so once you guys help me make a SBF, I can somehow then put Clockwork recovery on there and flash one of the custom roms?
thanks
karl0ss said:
Hey guys, attached is the build.prop and default.prop file, the third folder you listed doesn't exist, or at least I can't see it...
www(.)mediafire(.)com/?1ducdwtg246qz57
webtop version -OSHWT_U1_6.54.0
so once you guys help me make a SBF, I can somehow then put Clockwork recovery on there and flash one of the custom roms?
thanks
Click to expand...
Click to collapse
Yep you should be clear to go forward, just remember no way to rerun to stock at the moment.
I've forwarded this information to daywalker04 who seems to be able to find these sbf's, and it could take a while, the web site he uses is a couple of posts up.
flashing at the moment is mainly themes at the moment rather than roms
Will post sbf on the orange uk thread in general.
Plus pm you a copy, if and when we get it.
Swyped from 'mount' Olympus
karl0ss said:
Hey guys, attached is the build.prop and default.prop file, the third folder you listed doesn't exist, or at least I can't see it...
www(.)mediafire(.)com/?1ducdwtg246qz57
webtop version -OSHWT_U1_6.54.0
so once you guys help me make a SBF, I can somehow then put Clockwork recovery on there and flash one of the custom roms?
thanks
Click to expand...
Click to collapse
I wish I had that flex version.
It doesn't appear to be on Motorola's system yet. Sometimes they take a while to catch up.
Here is an alternate method to find flex file.
Be sure to set Android USB debugging mode on your device to OFF. Then make sure you have the latest Moto drivers installed on your machine. If you can connect to Motorola Software Update using Windows OS and try to run a software update--- it will not succeed because there is no update for T-Mobile UK.
When it searches for an update it will store the necessary info in a file called MSU.txt (this is the file needed) in the Motorola Software Update program directory. Then you can find the flex version.
That file is on your computers directory, rather than your phone.
Swyped from 'mount' Olympus
nitrox1 said:
Thank you for your reply. But I'm really looking for the UK Tmobile, sbf, or understanding of it.
Ps check out our uk orange thread, for a much cheaper unlock, and within 10 min!
Swyped from 'mount' Olympus
Click to expand...
Click to collapse
oh haha sorry. just recived mine and it took 3 days for $20
Related
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!!
Hey guys,
I'm extremely nervous about rooting since I can't really afford to replace my phone with anything at the moment.
The reason I really want to root is for screenshots and a full hdmi mirroring without the dumb 60 dollar dock.
I've read all the threads about rooting on and etc, but I'm still confused.
If possible, can someone give me a simple answer of which way of rooting is best for me, possible side effects, and what I can do with it?
I'm pretty tech savvy, thing is, is that I've never had an android phone, and really want to make sure I don't kill such a nice phone
Sorry about this, I just REALLY don't want my phone to get bricked.
Phone Information: Bell Motorola Atrix
System Version: Blur_Version.0.37.23.MB860.BellMobility.en.CA
Model Number: MB860
Android Version: 2.2.2
Baseband version: n_01.77.15p
Motorola webtop version:OSHWT_U1_5.32.13
Kernel Version: 2.6.32.9
I think that's all that could matter.
I have not tried to mod the phone as of yet. Only things I've done is install snes and psx emulators
Any help is GREATLY appreciated.
shaimedio said:
Hey guys,
I'm extremely nervous about rooting since I can't really afford to replace my phone with anything at the moment.
The reason I really want to root is for screenshots and a full hdmi mirroring without the dumb 60 dollar dock.
I've read all the threads about rooting on and etc, but I'm still confused.
If possible, can someone give me a simple answer of which way of rooting is best for me, possible side effects, and what I can do with it?
I'm pretty tech savvy, thing is, is that I've never had an android phone, and really want to make sure I don't kill such a nice phone
Sorry about this, I just REALLY don't want my phone to get bricked.
Phone Information: Bell Motorola Atrix
System Version: Blur_Version.0.37.23.MB860.BellMobility.en.CA
Model Number: MB860
Android Version: 2.2.2
Baseband version: n_01.77.15p
Motorola webtop version:OSHWT_U1_5.32.13
Kernel Version: 2.6.32.9
I think that's all that could matter.
I have not tried to mod the phone as of yet. Only things I've done is install snes and psx emulators
Any help is GREATLY appreciated.
Click to expand...
Click to collapse
If you search for gingerbreak, its a downloadable apk file that you install on your phone. Make sure you have an sd card installed, and then just open the application and click root. It's very simple, i've used that program many times on my bell atrix. I will see if i can find the link
You can find the app here
Will I need to reformat my SD card?
Also, is there some sort of backup I can make just in case it fails or something?
Not entirely sure what my options are in case it fails.
Same situation as OP. Really new to this Android stuff! Been doing tons of reading on this forum before I attempt anything and I have to say all this weird naming convention and such is throwing me off lol (whats with pudding and fruitcakes??).
Anyways thanks nate for the link! I've read about Gingerbreak but there is also GladRoot. Any differences b/w the two? Pro's/Con's?
Also to OP or any new people to android just in case you haven't seen this thread: http://forum.xda-developers.com/showthread.php?t=1154600. Its really helpful. Answers your question about what root allows you to do briefly and some of the problems you may run into.
edit: Just re-read the GladRoot thread and it looks like that method is a no go for Bell users after the OTA (0.37.23).
@Bump: Can someone help me in regards to my second post?
Thanks again!
Best way is to download the Gingerbreak apk like the first guy said and just push that to your phone, or if you're a lazy bum (like me!) and you have a PC, then use this. Also, I've run this on my phone with no problems to any of my SD cards (both internal and external), but since it does touch that area, BACK UP BOTH. If anything, it's a bit more time but so much more worth it. Besides, don't you want a backup of those embarrassing videos you took of your friends? *cough cough* >.>
Also, know that if it doesn't work or something, pull the battery and try again. It took me a few tries, but i finally got it to work. =] Let me know how it goes.
Happy rooting!
~jojojohnson7410~
"When attempting this on my bell phone
(same stats as shaimedio) I get the error from gingerbreak "could not extract assets !" this is a freshly purchased phone.
I've followed steps from various threads on how to do this (being I've managed to use adb and get gingerbreak onto my phone i figured that was a start.) Any tips?"
Fixed my own problem
"adb shell rm /data/local/tmp/*
adb shell rmdir /data/local/tmp
adb shell mkdir /data/local/tmp"
Looks like the temp cache prevented access
+1 for the gingerbreak. I've used it a few times without any issues.
I always plug my phone in, mount my internal memory and copy it over to the computer, then take out my SD card. Install & run gingerbreak, then put the sd card back in and copy all my data back over to the phone from the computer.
Can't really say what your options are if it fails as I've never had that happen with mine the 3-4 times I've used it.
Hope that helps a bit.
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've got a Sprint Galaxy S2 and I'd like to get root access to modify a few files. The thing is, I don't want to bring out the big guns and root it and put a bunch of extras on it (all these one click rooting programs always come with something more than just root access). All I want to do is get root access to my phone for a few minutes so I can modify a few system files. After that, I don't need root access, and would even prefer not to have it. I tried zergRush, but it doesn't seam to work for Android 2.3.6 (it told me there were "Hellions with BLUE flames!" ).
I've searched and can't find anything out there that'll grant me root access to my phone without also installing various ROMs/programs/kernels that I don't want. I want everything to be the same on my phone when I'm done except for a system text file or two that I modify. Is there anything like zergRush that works for Android 2.3.6?
(P.S. I'm a programmer by trade so you can speak tech if you like)
Cornstalks said:
I've got a Spring Galaxy S2 and I'd like to get root access to modify a few files.
Click to expand...
Click to collapse
I don't know what a Spring Galaxy S 2 is. Do you mean Sprint? i.e. http://forum.xda-developers.com/forumdisplay.php?f=1281 If so, you're in the wrong place. I'm saying this, because someone will helpfully post instructions on how to root an I9100 otherwise.
oinkylicious said:
I don't know what a Spring Galaxy S 2 is. Do you mean Sprint? i.e. http://forum.xda-developers.com/forumdisplay.php?f=1281 If so, you're in the wrong place. I'm saying this, because someone will helpfully post instructions on how to root an I9100 otherwise.
Click to expand...
Click to collapse
Blasted, you caught the error right before I fixed the post (if only I didn't have to wait 5 minutes to edit a post as a new user...). Yes, I meant Sprint. My fat finger hit 'g' instead.
Thank you for directing me to the right place. I'll go post over there.
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