[Q] Low RAM Problem - Atrix 4G General

Heres my story,
So I have had my Atrix since November, and I still would consider myself a noob when it comes to all this crazy unlocking stuff.
Last week I got the genius idea that I wanted to unlock the bootloader and followed a tutorial on doing it. In doing so, I think I missed a step and essentially gave up. Luckily for me, I never bricked the phone or anything. When I booted it back up, my phone began running slowly, lagging into apps and switching screens, so I factory reset it.
Ever since then, I have been getting extremely low RAM, like 200MB used with basic apps open, with only 20MB available. I tried contacting motorola for help, but they are certainly no help.
Just wondering if anyone here can help, as my phone is still way too slow to be bearable.
Thanks in advance

Looks like your Atrix is not AT&T version. Those international version of Atrix will have RAM issue after unlock. The RAM size will reduce from 1G to 350MB after the bootloader unlock process. Try search for RAM fix thread or proceed with the unlock process, install CWM and flash other ROM like CM7. Those ROM had RAM fix built in.
Sent from my MB860 using xda app-developers app

Sounds like you need the so-called "froyo RAM fix". I don't know how will you ever get it on there though, not having an unlocked BL or custom recovery. In fact I don't even know how did your phone even get messed up like that without these. It would be immensely useful if you could remember as much as you can about what you did and what was the result.

First off, "Q's" go in Q&A.
Are you sure you didn't unlock your bootloader? Do you see the word "unlocked" on the Motorola splash screen?
If you are not unlocked, this should be possible (in theory):
Get the ramfix zip, then extract the files and updater.script
Use a root level file explorer to put the files in the correct place and set permissions correctly
Run the script to enable the ramfix
Use updater.script as a guide to tell you where to place the files, what the permissions are, and which script to run.

upndwn4par said:
First off, "Q's" go in Q&A.
Are you sure you didn't unlock your bootloader? Do you see the word "unlocked" on the Motorola splash screen?
If you are not unlocked, this should be possible (in theory):
Get the ramfix zip, then extract the files and updater.script
Use a root level file explorer to put the files in the correct place and set permissions correctly
Run the script to enable the ramfix
Use updater.script as a guide to tell you where to place the files, what the permissions are, and which script to run.
Click to expand...
Click to collapse
It does not appear, no. I attempted to unlock it again today and got to the point where I typed in fastboot oem unlock or whatever, then I got the message << waiting for device >> but nothing further from there. I just unplugged and restarted my phone, and gave up once again.
Can you elaborate on the above? I am getting so frustrated with this low RAM because I can't even open a game or high RAM app without it lagging like crazy.

Trying typing "adb devices" instead and see if it shows your device. Maybe you are without the fastboot driver
Sent from my MB860 using xda app-developers app

Related

Nexus S4G might be bricked, please help

I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Go look in the developer section, one of the stickies, the one that talks about the nexus s 4g cdma. You might have flashed something that was meant for the gsm nexus s. It has links to correct files and guides for the sprint version of the nexus.
Pm me and I will help u over the I'm client of your choice.
Basically, I have no service, and no card, so since I can access Fastboot Mode, and unlocked, is there a way to push a rom direct onto Sprint phone.
I looked in Developers Forums, I am not ready to jump in with custom rom yet (I have used extensively on other phones) but would like to start with stock, go with root and programs as needed.
So how would I push to phone via computer? and what programs, again, no idea of commands to use.
Have you flashed CWM yet? You can use that to reflash the stock ROM. Worst case you can use this thread:
http://forum.xda-developers.com/showthread.php?t=1072698
That will bring you to 100% out of the box factory settings
If you can get into fastboot, then you didn't brick it. You'll be fine, you just need to get in touch with someone that can walk you through the process of fixing it. Or search around, read, and take your time to figure out what to do.
It's not hard. The worse thing you can do is panic or rush to fix it.
Basically what you did when using superboot was you actually installed a boot.img file not meant for your device on your phone. What you should do is, go through the guide for your specific phone...you will have to install a recovery image and then install a custom rom or stock rom.
I do not know if you know your way around with fastboot....basically you could also ask a dev to send you the original boot.img and flash it using fastboot but the first stepi described is easier.
Sent from my Nexus S using Tapatalk
nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse
If you are going to waste your brand new phone by being stupid how about giving it to me instead! Ill take good care of it.
Sent from my PC36100 using XDA App
Here Try this and let me know if it work:
1.Download this platform-tools.zip and extract it to your desktop
2.Connect your phone to the PC and enter bootloader mode
3.Press and hold Shift while right-clicking the folder you extracted 'platform-tools'
4.Click 'Open command window here' from the pop-up menu. cmd.exe window will open.
5.If the Bootloader is Unlocked continue to the next step. Type in the cmd.exe window 'Fastboot oem unlock' and follow the steps on the phone screen.
6.Type in the cmd.exe window 'fastboot flash boot boot.img'.
7.Type in the cmd.exe window 'fastboot reboot'.
nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse
THANK YOU, for answer, but it didn't work.
I downloaded, opened, opened cmd from there.
My phone is unlocked, setting there with unlock screen, put it in bootloader mode, but when I type in instructions, it comes back "not recognized as internal, external command, program, batch file"
This is the problem I had when trying to unlock, so reading, used Superboot, probably wrong phone, so now it is wiped and empty.
I also read another thread suggesting Odin in this situation. Have downloaded that, SamsungSimpleDL, followed those directions, that doesn't work either. I have hacked and rommed Epic, very familiar with that, if it works, but cannot point to proper files (pda, pit, or bootloader).
So any other ideas, I am very good at directions, that is how I learned
My Phone is Fixed - YEAH
This did not work, but this link did
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
Basically used Odin (my old backup from Samsung Epic) and it worked when all these suggestions wouldn't.
I couldn't unlock easily, like all of these, therefore used Superboot. Would recommend no one touches that!!
I couldn't run any of the commands before this, and still couldn't use these.
So the instructions to dig thru the Developers section is correct, but so hard with so many customs, phones, carriers, to choose from. Makes it difficult
So use this link if stuck like me, I am just glad I con't have a brick, and I'm still pushing the Thanks button for all who helped, that's what will make this fun.

Getting BootManager!

Alright i have been keeping an eye out on a few things and came across BootManager which is a newer app that allows you to easily flash between several roms! Which of course is awesome if you want to try new ones out without reflashing as often. Unfortunately im am not quite as wise in the Android scene yet as i like, new to it with my Acer Iconia as i am, BUT i have been corresponding with the developers for BootManager and they have given me a link so we can submit the Acer Iconia to be added to the devices that can use Bootmanager!
I just don't know how to give them the variables they need!
Could someone that does know how to get the variables needed, (through adb shell or whatever) kindly submit it to them? Here is the link they gave me for submitting new devices, if you do do this, please post it here, so they don't get a bunch of repeat submissions on it, also, so i can keep an eye on the app and get it when they update it accordingly! Thanks very much!
Edit: I can't post links yet, cause i have not posted often enough. Please send me a message and i can give you the link that way! Or just close the space below and use it.
init2winitapps. com/submit_device.html
I'll do it in the morning.
Make damn sure they know they have to run "itsmagic" before/after ANY flash operation (I can never remember which, that's CWM's job!)
I did it too and i sent also a mail to the developers about itsmagic script!
good luck
If you read the information about this program.how it works and the phones that it supports will tell you it will most likely work on our device.THEY SAY WORKS ON PHONES ONLY.and only those WITHOUT LOCKED OR SECURE BOOTLOADERS
But you never know. They might put the efforts to write a new bootloader for this device.the program works by moving the bootloader.well no fifteenth then any other boot manager.
if im wrong and they make it works. I would buy it first.
Goddess erica.
This was posted a while ago and it doesn't appear that the a500 has been added to the supported device list. Has anyone been successful in getting this to work? I want to try it but I'm not sure what issues I might run into if it doesn't work. I need to make sure a Nandroid restore can fix whatever issues might be caused before to try it.
IF i remember right it says on there site this can ONLY WORK WITH UNLOCKED and not encrypted BOOT LOADER DEVICES. I TO Talked to the dev way way long ago..as for this to work they change the boot target in the boot loader to look at there software . then it will boot from there..
kinda like grub to a normal pc.. with the bios being the primary boot . If this makes any sense..
so i think it cant happen.. in the linux thread in our dev area .. someone in the first few pages it talkes about this very app and the flashing the bootloader out.. Dont think they ever figurerd a way around the security..
sorry simple answer is ABSOLUTELY NO WILL NOT WORK
THANKS ACER
I'm confused. My a500 doesn't have a locked boot loader. Thats the reason I got it. I have Thor's recovery loaded on it and I have been able to flash Roms without issue. To boot into recovery I just hold down the volume button and boot the device. I can load custom kernels or pretty much anything else I want. Am I misunderstanding what an unlocked bootloader is?
I had a Razr previously which had a locked bootloader and the only way to flash was to use a bootstrap because it had a locked bootloader. I had loads of problems with it which is why I swapped it out for the Galaxy Nexus when it came out. Both my a500 and Gnex are flashing like champs.
Where there later version of the a500 that had a locked boot loader? I don't think mine does.
trevoryour said:
I'm confused. My a500 doesn't have a locked boot loader. Thats the reason I got it. I have Thor's recovery loaded on it and I have been able to flash Roms without issue. To boot into recovery I just hold down the volume button and boot the device. I can load custom kernels or pretty much anything else I want. Am I misunderstanding what an unlocked bootloader is?
I had a Razr previously which had a locked bootloader and the only way to flash was to use a bootstrap because it had a locked bootloader. I had loads of problems with it which is why I swapped it out for the Galaxy Nexus when it came out. Both my a500 and Gnex are flashing like champs.
Where there later version of the a500 that had a locked boot loader? I don't think mine does.
Click to expand...
Click to collapse
Not locked, but encrypted, we use a magic script called itsmagic to bypass the encryption.
daveid said:
Not locked, but encrypted, we use a magic script called itsmagic to bypass the encryption.
Click to expand...
Click to collapse
Ah. I always wondered what itsmagic did. I get it now. Damn. Is there currently any tablets out there that do not have encrypted or locked boot loaders?
Not any good ones.. welcome to the new communist Tech generation...
they want our devices to be disposable.

1 Click root brick?!

So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Motorola published the factory files for Xoom awhile back so if you still have fastboot, you can recover from it.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Stop using one click crap. If you don't know what you're then you should not be messing with your device.
Sent from my DROIDX using XDA App
I can. Just won't.
Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
albundy2010 said:
I can. Just won't.
Click to expand...
Click to collapse
And this is rude and uncalled for
The OP stated he read quides etc and none of it made sense to him etc. So instead of asking for help a explanation he tries a one click method. Which is stupid. He than softbricks the device and asked for help here.
Then he is told that moto released the factory images and use fastboot if he still has it to recover the device. He then decides to ignore that entirely and go back and try to unroot/restore with the one click BS again. Then he tries to use it again to go back to where he was. Just flat out stupid. He did something when he had no idea wtf he was doing. Was told what to do. Did not do it. He even said it is like Chinese to him.
So I told him to stop messing with one click crap. Which is correct. I told him to stop messing with the ****ing thing. Which is also correct. He needs to learn/understand wtf he is doing. Instead of basically button mashing/trying crap and hoping it will basically fix itself.
On top of that this posted in the wrong section. Uncalled for my ass. He is the one that was rude when told to not mess with the one click or the device. Now this part is rude. **** his stupid ass.
csseale said:
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
Click to expand...
Click to collapse
How do i get to that ..and where do i type it at ..i looked in device manager & does recognize the xoom..it says "Motorola USB Device:Motorola Flash Interface"..In properties under "Driver" it has options for driver details..update driver..disable & uninstall.Can i do anything with them?
I tried opening SDK manager but it never lets me type anything in the box as it's always trying to do some kind of update in another window so when i close the window it closes all of the windows.
Sent from my DROIDX using XDA App
Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If they didnt make sense to you in the first place you probably shoud not be attempting to root... U went straight to an old method that even the developer has marked in hs thread can full brick you and should not be used. The xoom costs like 600 bucks... Why wouldnt you do extensive research on how to root? If you did not understand the terms why didn't you research the methods and learn it?
I hope you can flash the factory imagines back through fastboot and adb, but i just do not understand why people attempt this stuff when they have no idea what the terms even mean...
You need to have sdk, hook up to usb on your computer, and follow one of the unlock guides posted on this site... A real one using adb... Then you need to follow a root one...
Sorry that is not more helpful, but half of this experience is that you need to learn what you are doing and the instructions are out there. If they do not make sense at this point im afraid you are stuck. Now the way your device is you have to figure it out...
Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Please check out this thread.It is called Root heaven for a reason. Just about every viable rooting guide, all the files and explanations you will need are here.
http://forum.xda-developers.com/showthread.php?t=1209341
I urge you to just calm down, read about what is the sdk, what is adb, how to recover from a soft brick and so on. The xda xoom forum is all about learning and teaching. We were all noobies once. The Xoom is a very complex device with many models and vesions and one clicks just don't cut it. There are rooting methods that are relatively simple but you really need to be prepared before you get started.
Good luck and don't despair. You'll get there.
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Arun01 said:
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
at first, make sure you install android sdk correctly. then go to android sdk-folder in your computer, u will find a folder named platform-tool. Press shift+ right click on it, then choose open command window here. After that, type in "adb devices" or "fastboot devives" to check if your xoom is connected. If yes,you good to go. If no, check your android sdk installed process
After i type in abd devices it says list of devices attached but shows nothing..i did copy the sdk tools folder to the c drive like i was told.
@OP
If you can't do it yourself, getting somebody to help you (in person) is always an option. If you live in a major city, advertise on Craigslist or some equivalent. Offer $50 for debricking + some tutorial.
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
That's good advice...no reason to re-lock. But get back to square one so that you're functional and then when you're ready to try again, do it the right way.
Again, good luck!
albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
Thanks a lot.I was able to unlock it then it rebooted & stopped at the Motorola screen then i started the 1st command: fastboot flash boot boot.img & it says waiting on device..but nothing happens so far.Should i move on to the next step or retry?

[Q] First Post!...with a ton of help needed.

HellllOOooOoOo!!
Ok, here goes. First off, I searched. A lot. There is so much conflicting information and opinions out there. I hate to annoy you pros with noob-ness but I have to. Sorry!
Here is the quick version:
Friend gave me an Atrix 4G. He is big on experimenting, rooting, custom ROMs and all that. I am not. At all. I want to use it on t-mobile. I DO get a signal and can text. MMS doesn't work and motoblur wont let me set up an account. This results in no access to email other then Gmail. Basically, I want to bring the phone back to its original (or close as possible) state. Hopefully, that will solve some of my issues.
-Android Version
2.3.4
-Unlocked
-Rooted
-Build Number
olympus_hktw-userdebug 2.3.4 4.5.2A-5_OLH-3110614 test-keys
-Clockwork recovery mod installed (if that matters)
I am not THAT tech savvy but can follow instructions well. I've already been messing around but cant seem to get RSD Lite to actually flash properly. I dont care for customs ROMS, hacking and tinkering. I just want this phone to work as well as possible.
Can anyone give me some personal assistance? Please? Step by step would be great. I'll be refreshing this page often in hopes of responses.
Vul said:
HellllOOooOoOo!!
Ok, here goes. First off, I searched. A lot. There is so much conflicting information and opinions out there. I hate to annoy you pros with noob-ness but I have to. Sorry!
Here is the quick version:
Friend gave me an Atrix 4G. He is big on experimenting, rooting, custom ROMs and all that. I am not. At all. I want to use it on t-mobile. I DO get a signal and can text. MMS doesn't work and motoblur wont let me set up an account. This results in no access to email other then Gmail. Basically, I want to bring the phone back to its original (or close as possible) state. Hopefully, that will solve some of my issues.
-Android Version
2.3.4
-Unlocked
-Rooted
-Build Number
olympus_hktw-userdebug 2.3.4 4.5.2A-5_OLH-3110614 test-keys
-Clockwork recovery mod installed (if that matters)
I am not THAT tech savvy but can follow instructions well. I've already been messing around but cant seem to get RSD Lite to actually flash properly. I dont care for customs ROMS, hacking and tinkering. I just want this phone to work as well as possible.
Can anyone give me some personal assistance? Please? Step by step would be great. I'll be refreshing this page often in hopes of responses.
Click to expand...
Click to collapse
It sounds like you need to set up a proper T-Mobile APN. (you have a T-Mobile SIM card currently installed?)
If you can get on Wifi, try to go the the Play store and download Tweakker or other APN utilities that enter the APN for your based on your carrier.
co.ag.2005 said:
It sounds like you need to set up a proper T-Mobile APN. (you have a T-Mobile SIM card currently installed?)
Click to expand...
Click to collapse
Yes. I have a t-mobile SIM card installed. My concern is what the previous owner may have done and whatever ROM is loaded on this phone. Can I somehow bring it back to stock or get a super stable, close to stock as possible ROM first and then start addressing the quirks I have?
Is this an AT&T branded phone? I'm not sure if getting back to stock is necessary, and if you do get back to stock, you might be SIM locked to AT&T (I could be wrong however). If you want to flash a fresh, stock ROM but still be rooted, SIM unlocked, etc., find a 2.3.6 Fruitcake in this forum or try NottachTrix 4G ROM.
however, I'd wait till others weighed in before doing anything. Honestly, I'd try getting your APN (download Tweakker app and walk through the steps) going now and if that solves your issue, your ROM might be working fine for you... my $0.02
oh, and welcome to XDA!
Vul said:
Yes. I have a t-mobile SIM card installed. My concern is what the previous owner may have done and whatever ROM is loaded on this phone. Can I somehow bring it back to stock or get a super stable, close to stock as possible ROM first and then start addressing the quirks I have?
Click to expand...
Click to collapse
1. Download the fruitcake .zip you want (webtop also, if you want it)
2. Do a full wipe with fastboot (search if you're unsure how to)
3. Boot into recovery and flash the .zip you downloaded from step 1
4. Reboot and you're done
This will put you back to stock. I can't remember if fruitcakes are pre-rooted, but if not you can easily root again.
Alright, now we're getting somewhere.
co.ag
The phone itself says "unlocked" upon startup. I got the network unlock code direct from AT&T because at first the phone wouldn't even recognize my t-mo SIM. Phone is now network unlocked.
Ghost
gonna search now for fruitcake and see what thats all about. Do I need webtop?
Then going to get fastboot. Guess I dont need RSD Lite anymore?
Im doing this because I dont know what the previous owner has done and would like a clean slate. Kind of like changing the oil on a used car you buy, even if the PO says it was done.
Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
**am I supposed to be saving these files to the phone itself? If so, where? Internal storage? SD card?
Vul said:
Alright, now we're getting somewhere.
co.ag
The phone itself says "unlocked" upon startup. I got the network unlock code direct from AT&T because at first the phone wouldn't even recognize my t-mo SIM. Phone is now network unlocked.
Ghost
gonna search now for fruitcake and see what thats all about. Do I need webtop?
Then going to get fastboot. Guess I dont need RSD Lite anymore?
Im doing this because I dont know what the previous owner has done and would like a clean slate. Kind of like changing the oil on a used car you buy, even if the PO says it was done.
Click to expand...
Click to collapse
that "unlocked" bit on start up means your bootloader is unlocked, doesn't have anything to do with the SIM card. All this means is that you can flash a ROM since the phone is "unlocked"
Vul said:
Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
**am I supposed to be saving these files to the phone itself? If so, where? Internal storage? SD card?
Click to expand...
Click to collapse
the fruitcake .zip goes on your internal sdcard. BUT, before you start doing anything, please go through the stickied threads in this section and read up on how to flash ROMs to your phone. This will include how to wipe your phone using the fastboot commands and how to flash the fruitcake .zip.
start here, read this post
http://forum.xda-developers.com/showthread.php?t=1154600
then follow guides to
"HOW TO INSTALL FRUITCAKES ON 2.3.4 (GREAT SBF/RSD ALTERNATIVE!!!)"
and
"ROMs & Kernels:
FYI:
Before installing any ROM or Kernel I suggest you do the following to help prevent error, boot-loops, etc. Also, it's a good idea to flash a new ROM or Kernel on a fully charged device:
1) Download which ever ROM or Kernel you plan on flashing and have the .zip on your device ready to flash.
2) Backup your apps (not system data), contacts, etc. Also consider making a CWM backup of your device, just in case.
3) Boot into CWM Recovery
4) Wipe Dalvik Cache (under advanced in CWM)
5) Wipe Cache Partition
6) Wipe data/factory reset
6a) If you're using ROM Manager/CWM you will need to reboot the device after step 5, and upon reboot enter fastboot mode and enter the command: "fastboot -w" or "moto-fastboot -w" if you prefer using moto-fastboot. Then type "fastboot reboot" and upon reboot make sure to enter Android Recovery again, so that you can flash the ROM/Kernel.
7) Install .zip from SD Card (choose the .zip you wish to install)
8) If you installing a radio, theme, kernel, etc. on top of a ROM, I would suggest redoing the whole wipe process again between flashes.
9) Reboot the Device
- If you get a boot loop, try entering Android recovery and re-wiping the chace and data, and perhaps try reflashing the ROM/Kernel. Or if you made a CWM backup, you can always restore that."
Vul said:
Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
Click to expand...
Click to collapse
Ok, sorry I wasn't that detailed in my other post and assumed you were on your phone (my bad). First things first, read the N00b guide.
1. Anytime you download CWM .zips, put them on the root of your phone's sdcard. You'll need them there in order access them from recovery. ( note: sdcard=internal sd card & sdcard-ext=external sd card for blur ROMS )
2. Fastboot commands are executed from the command line. Open a command prompt and navigate to the directory containing fastboot.exe in order to use it. The Noob guide should have links to all the fastboot commands you'll need.
3. With the Atrix's unlocked BL, holding Volume Down when turning the phone on will bring up a series of bootmodes to choose from. This is how you get into fastboot, recovery, RSD, etc. Navigate through the choices with Volume Down. Select one by pressing Volume Up. You should only ever really need Fastboot and Android Recovery.
4. CWM is used to flash .zips (ROMS, kernels, apps) while in recovery mode. Use romracer's to make things easier on yourself later.
Read through the N00b guide and this will all make perfect sense.
I have no idea what Im doing. I think because this phone has been tampered with so much already, it's making it extra tough to work with.
I managed to install CM7. Its the only ZIP file that actually seemed to take. I still dont understand fastboot , in the sense that I don;t know when Im supposed to see a command prompt. Also, now, CM7 is asking me to upgrade to premium and I have to pay for it. There doesnt seem to be a free way of installing it so that I can sync all my info through my google account. Ugh. Im not cut out for this but Ive been screwing with this literally since 730 this morning.
**CM7 with google apps packet installed. So far, so good. Im happy with this considering its pretty close to stock gingerbread, kinda like my G2. Now, Im hopefully done messing around. Would be nice if they release a solution for the fingerprint scanner or if I can get my gmail to auto sync but at least I can stop obsessing for the time being. Great help guys, thanks so much!!!!

Fool proof nexus 10 root

Hello there
Got myself a nexus 10 and to say I'm jealous of some of the homescreen posts is an understatement it really has me salivating when I see those custom icon packs coupled with a 2560x1600 resolution. I'm reasonably tech savvy myself but find the task of rooting my device a daunting one. I Find it difficult to follow all the steps and I'm afraid to mess it up and to be left with a device the won't even power on and as I live in Ireland it will prove difficult to send back for repair. Device still not available here officially. Anybody know an extremely easy reliable root?.just wanna run flash and customise the appearance a bit and maybe a little over clocking Any suggestions are welcome.
Thanks in advance
Thanks
Sent from my GT-I9300 using xda premium
rdsreference said:
Hello there
Got myself a nexus 10 and to say I'm jealous of some of the homescreen posts is an understatement it really has me salivating when I see those custom icon packs coupled with a 2560x1600 resolution. I'm reasonably tech savvy myself but find the task of rooting my device a daunting one. I Find it difficult to follow all the steps and I'm afraid to mess it up and to be left with a device the won't even power on and as I live in Ireland it will prove difficult to send back for repair. Device still not available here officially. Anybody know an extremely easy reliable root?.just wanna run flash and customise the appearance a bit and maybe a little over clocking Any suggestions are welcome.
Thanks in advance
Thanks
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Check the original android development section there's a nexus 10 toolkit that will unlock the bootloader and root along with a bunch of other features. Of course, learning how to use adb commands are best, but if you want a quick fix, use the toolkit.
If you mess up, as long as you managed to get as far as flashing a custom recovery you can fix just about any mistake. And even if you broke it all (which is HIGHLY unlikely) before you even flashed a custom recovery, you can still fix just about any problems you made. I actually just helped another guy who screwed up his tablet pretty bad if you want to read my post on how to get out of a jam:
http://forum.xda-developers.com/showpost.php?p=37019359&postcount=10
As for unlocking, if you follow the first few steps of my other post you will have the Android SDK downloaded and the files you need in an easy to access folder. From there you will just want to download a custom Recovery .img file, like this one here:
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.3.3.0-manta.img
and do the commands:
fastboot oem unlock
Then follow the couple steps on your tablet to confirm the unlock. Copy that recovery .img file you downloaded into your Android-SDK folder, and then use the command:
fastboot flash recovery blahblahblah.img (where blahblahblah is the actual file name of the recovery image you downloaded)
Once done then use the volume buttons to go down the fastboot menu on your tablet until it says "Recovery", press the power button to confirm booting into recovery.
Then download this file and place it in the Android-SDK-Windows directory:
http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip?retrieve_file=1
and use the command:
adb push CWM-SuperSU-v0.98.zip /data/media/0
Which will push the file to your tablet (or alternatively instead of pushing through ADB just start your tablet like normal and copy the file the normal way from your computer to your internal storage)
Once the file is copied/pushed then in your recovery go to the install menu and flash it. This will flash root to your current ROM. Then you should be dine, you are now unlocked on the stock ROM with root. Alternatively, instead of flashing root, you can just go straight away to flashing a custom ROM since those already have root access anyway.
It really is quite easy and simple. Should take 5-10 minutes tops. If you want to lock the tablet again then find a completely stock ROM (or google how to reset and flash the original RUU) and flash it to your tablet and then do the same thing as unlocking but use the command: "fastboot oem lock"
http://forum.xda-developers.com/showthread.php?t=2015467
Wugfresh has a toolkit that's foolproof. As long as you follow the directions and slowly go through each step, ensuring you're reading everything carefully, you'll be fine. In the OP of the link I provided is another link that takes to to a YouTube video of the Nexus 10 being unlocked and rooted using the toolkit. It goes step-by-step, so follow along with the video, do EXACTLY as he does, and you'll have no problems.
Just use cf-root, takes less than 10 sec and very straight forward
Sent from my Nexus 10 using Tapatalk HD
Does the name qbking77 mean anything to you??
Sent from my Galaxy Nexus using Tapatalk 2
Just use superboot, you won't loose data and won't need to unlock bootloader or install a custom recovey...
gmfeny said:
Does the name qbking77 mean anything to you??
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The link I provided has a link to qbking77's YouTube video showing the Nexus 10 being unlocked and rooted using Wugfresh's toolkit.
Rodeojones said:
The link I provided has a link to qbking77's YouTube video showing the Nexus 10 being unlocked and rooted using Wugfresh's toolkit.
Click to expand...
Click to collapse
Yea I know that's what I used when I rooted mines!
Sent from my Galaxy Nexus using Tapatalk 2

Categories

Resources