Database Users

[HOWTO] Flawless bell update

WELCOME
to the WINDOWS Bell Atrix 0.37.4 update guide on how to go from 2.2.1 to 2.2.2! (without problems )
===================================================================================================================================================
WARNING
Do not attempt any of these steps if you are on an international firmware. You will probably brick your phone. This guide was made to help people who are having trouble updating from 0.37.4 to the new bell 2.2.2.
Bell users:
Please note that flashing files to your phone and modifying system contents can brick your phone. However, the method I am sharing worked flawlessly for myself and others.
Before beginning:
You need root access on your phone. If you are not sure what root access is, you shouldn't be having problems updating, because you wouldn't have modified system files. Regardless, here is a thread on how to root a bell atrix.
Guide:
Step 1:
Download Titanium Backup from android marketplace, and back up all of your apps and games. This is necessary only if you want to have an easy reinstall of most of your apps and games, as we will be wiping data off of the phone. (if you have another backup program, it should work just fine. Make sure it saves the backup to a folder that you can copy onto your computer)
Step 2:
Remove the external microsd card from your phone (if you have one). This is simply for safety purposes, as we don't want any data being wiped off of this (we don't need the microsd any time during the process).
Now, copy (or cut) all of the data from your internal storage to your computer, just in case, and we are about to wipe data off of your phone.
Step 3:
Format your phone. This can be done two different ways.
The first method is the simplest:
Menu -> Settings -> Privacy -> Factory Data Reset.
The second method (if for some reason you can't do the first) is:
Turn off your phone. Turn it back on while holding the volume down key. It will show the word FastBoot. Keep pressing the volume down key until you reach android recovery. Press the volume up key. Wait patiently. Once a little man appears, there should be a menu. If there isn't, press both the bottom left and bottom right corners of the screen simultaneously. That should bring up the menu. (give it a few tries, it takes me 8-10 lol). From this menu, press volume down until you get to wipe data, then press ok on the bottom left corner (give this a few tries too).
Step 4:
Your phone should now be acting like you just bought it. It should, upon reboot, prompt you to enter your country.. etc. Make sure you either use your existing motoblur account, or create a new one. It is just important for you to have a blur account for the update process (my phone gave me hell when I didn't have one). Do what is necessary to get your phone up and running again.
Step 5:
This is where the fun begins. Reroot your phone usinggladroot(or any other root method you know how to use). Download Superuser, install it, then download Root Checker from android marketplace to confirm root access. Whenever a Superuser popup comes up, confirm / say yes (and make sure the remember box is checked).
Once you have confirmed root access, proceed to the next step.
Step 6:
Download Tenfar's CWM recovery, and install the apk on your phone. Follow the instructions inside of the app to install recovery and enable recovery mode.
Step 7:
Download these two files, and put them in the root of your internal storage. (By root, I mean in the very first directory, ie. F:/put file here)
http://dl.dropbox.com/u/23800522/Blur_Version.0.37.4.MB860.BellMobility.en.CA.zip
http://dl.dropbox.com/u/23800522/Blur_Version.0.37.4.MB860.BellMobility.en.CA.crc
Step 8:
We are now ready to start fixing up the phone, and preparing it for the update.
First of all, we need to make sure ADB (the program we will be using on our computer) has root access on our atrix when it is plugged into our computer via usb.
Before plugging in your atrix via usb, enable USB debugging via:
Menu-> Settings-> Applications -> Development -> Check USB Debugging.
Now plug the atrix into your computer, and set the USB connection to: None. Check to make sure USB Debugging is in your notification bar.
Download these files onto your computer if you do not have the adb files yet. Extract the files preferably into the root of your hard drive (ie C:/ ) is just makes things easier this way.
Now open up command prompt.
If it is not in the directory where the adb.exe file is, you will need to type:
cd C:/
into command prompt. This says "change directory to C:/" (or wherever you put the files, could be cd C:/Program Files/ could be anywhere. wherever you extracted them to.)
Once in this new directory, type this into command prompt and press enter:
adb devices
If a device pops up (mine said TY290380 or something like that) that means that it recognizes your atrix. That is great news. We now have to enable ADB root access on the phone.
If nothing pops up, or it says some sort of error, you are not in the directory where adb.exe is located. Navigate to the proper directory.
Now, type the following command:
adb shell
One of two things can happen here. It will either create a new line with a $, or a new like with a #.
blah blah C:/ adb shell
$
or
blah blah C:/ adb shell
#
If a $ came up, you need to prepare a command BUT DONT PRESS ENTER YET. Type in "su", but dont hit enter. Now go to your phone and unlock your screen. After you unlock your screen and can see your homepages, press enter on your keyboard doing the "su" command. Now look at your phone. A superuser request should appear. Hit yes, and make sure that "remember" is checked. If not, it is ok, as long as the su command went through on your screen. it should now show a # on your command line.
For those of you who had a # on your command line, type in shsu and hit enter, then type in su and hit enter (just to play it safe ).
We are now ready to flash the first files to our device. You can close the command window.
Step 9:
Download this file. It is the original unmodified system partitions and files (thank you NFHimself). Extract the file using winrar or 7zip.
Change your USB connection on your phone to: Mass Storage, wait a minute or so, and then put the extracted file "mmcblk0p12.bin" in your internal storage on your phone. (ie. F:/ )
Step 10:
Dismount the phone from your usb devices via windows hardware manager. Unplug your atrix from your usb. Reconnect it, and choose connection type: none. Make sure usb debugging is in your notification bar.
Now, re-open command prompt. Renavigate to the directory where your adb files are located using the "cd C:/" command (or wherever your files are). Once there, perform "adb devices". Make sure a device is there. Next, perform the command "adb shell". You should have a #. Type in shsu, hit enter, now su, hit enter (just to be sure).
Now copy this command and hit enter (you have to right click paste into cmd prompt):
dd if=/sdcard/mmcblk0p12.bin of=/dev/block/mmcblk0p12
This will begin the flashing process, which will restore all stock system partitions allowing us to update properly. However, it's not over yet .
Mine took a few mins, do not panic. Simply wait for it to say "Complete" in x amount of seconds or whatever. Your phone may crash, but it should boot up fine (if not, that is why we have installed Tenfar's CWM )
After it is complete, turn off your phone. Keep it connected to the computer.
Step 11:
Boot up your phone holding volume down. Navigate to android recovery using volume down. Volume up. Open up the menu with the bottom left bottom right press. Go to clear cache. Press OK. Now reboot your phone.
You can now update through settings and it should work properly. If not, respond in here and I will guide you a few more codes, but it should work.
The phone should now boot up, and it should be running android version 2.2.2.
Regard this thread for how to root the new bell update. Just a heads up, it wiped my internal storage and SD card, so remove and backup that stuff. Lol. But it did root.
Now reinstall your backup program, and get your phone going again!
If you have any questions or problems please post them here and I will reply ASAP, personal messages are hard to keep track of. Thanks again to NFHimself for supplying files and code.
Cheers!
PS: I just finished exams, yay!?
Please say if you notice anything misspelled, etc. Gratzi

You are the f***in man for posting this. Thumbs up to NFHimself for his contribution too!

Links
Crud, your links for the files in dropbox aren't working.

Silvercloak5098 said:
Crud, your links for the files in dropbox aren't working.
Click to expand...
Click to collapse
You sure? I clicked them both myself to make sure they work.
How don't they work?
FYI: I'm reuploading them to megaupload as we speak anyways

IrshaadH said:
You are the f***in man for posting this. Thumbs up to NFHimself for his contribution too!
Click to expand...
Click to collapse
When I got my phone to update to 2.2.2 it felt amazing.
I just wanted to spread the love

Thank you so much!! You don't know how frustrated I've been all day! The only problem I had was that my root was gone after I flashed it, but I just updated through settings and it worked flawlessly

tyrkk said:
Thank you so much!! You don't know how frustrated I've been all day! The only problem I had was that my root was gone after I flashed it, but I just updated through settings and it worked flawlessly
Click to expand...
Click to collapse
NP! Just glad you got your update.
I changed the steps so that the last step is simply updating via settings. If that doesn't work for people I will help them out in this thread with the more complicated coding way.
Cheers!

Couldn't step ten be used to revert to stock from an international sbf?
Sent from my MB860 using XDA App

Ok..quick question. You said not to install for those using any international version. I have run the Telstra sbf at one point..as well as had the Greyblur rom on. Before installing the Telstra I had made a backup using CWM, and a few days ago I had to revert to my old backup due to a rogue app. In my About phone, it tells me my System version is Blur_Vision.0.37.4MB860.BellMobility.en.CA with a Build number of OLYA_U4_0.37.4.
Would this be still safe for me to do seeing's how it seems i'm back to my "Bell sbf" or is there still going to be some Telstra files in there that could cause me some problems?

I made it through to the end of step 10 and the phone was looking good. Then when I shut off the phone and tried to go into Android Recovery, it keeps going to the triangle symbol and I have to reboot.
After a couple times of that I decided to check Android Recovery from inside the app list and it said I no longer have root access.
Any ideas what to do now??

Rickroller said:
Ok..quick question. You said not to install for those using any international version. I have run the Telstra sbf at one point..as well as had the Greyblur rom on. Before installing the Telstra I had made a backup using CWM, and a few days ago I had to revert to my old backup due to a rogue app. In my About phone, it tells me my System version is Blur_Vision.0.37.4MB860.BellMobility.en.CA with a Build number of OLYA_U4_0.37.4.
Would this be still safe for me to do seeing's how it seems i'm back to my "Bell sbf" or is there still going to be some Telstra files in there that could cause me some problems?
Click to expand...
Click to collapse
Depends on whether or not you're still on the telestra framework. If you're confident with your ability to recover from a potential brick via early usb enumeration id go for it.

bdking2 said:
I made it through to the end of step 10 and the phone was looking good. Then when I shut off the phone and tried to go into Android Recovery, it keeps going to the triangle symbol and I have to reboot.
After a couple times of that I decided to check Android Recovery from inside the app list and it said I no longer have root access.
Any ideas what to do now??
Click to expand...
Click to collapse
Edit: See my lower post first, then this one
Open up the menu in android recovery by tapping both the bottom left corner and bottom right corner of the screen at the same time.
It should show you an error if there was one.
Does the phone boot fine?
You should lose root access. When you flash the .bin it restores your bell to stock like you got it from the store. That allows you to update.
Most importantly open up the recovery menu when you see the triangle by tapping the bottom left and right corners simultaneously. Itll take a few tries.

IrshaadH said:
Couldn't step ten be used to revert to stock from an international sbf?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
No, since you are on an international framework it will probably brick your phone.
That .bin file contains the system partitions from the stock bell framework.
If you want to try go ahead but I think the odds are against you

bdking2 said:
I made it through to the end of step 10 and the phone was looking good. Then when I shut off the phone and tried to go into Android Recovery, it keeps going to the triangle symbol and I have to reboot.
After a couple times of that I decided to check Android Recovery from inside the app list and it said I no longer have root access.
Any ideas what to do now??
Click to expand...
Click to collapse
Bdking I have another idea. if you can boot up your phone, re-root it using any normal methods, then install CWM. Boot into CWM recovery mode and clear the cache from there. Then do step 11.
Chances are the update file is hanging out in your cache so when the android recovery sees that it immediately tries to install the messed up package.
Thats why you should clear cache on CWm because it wont try to install anything automatically from the cache. Then do step 11.
Hope it helps, Mag.

No my phone boots fine. And now I can get into android recovery to clear cache and have done so. But before I read your response I rooted my phone again.
Should I just restart everything?

bdking2 said:
No my phone boots fine. And now I can get into android recovery to clear cache and have done so. But before I read your response I rooted my phone again.
Should I just restart everything?
Click to expand...
Click to collapse
No you should be good to go try to update via settings.
You flashed the bin right?
If so you're good to go

I flashed the bin for sure. But wasn't sure about the process because I rooted again.

bdking2 said:
I flashed the bin for sure. But wasn't sure about the process because I rooted again.
Click to expand...
Click to collapse
Root shouldnt change anything only deodexing/webtop mod/ theming should mess it up.
If you flashed the bin go for it. Worst thing that can happen is that the update fails.
In that case, redo step 10, then do step 11.

Magnetox said:
No, since you are on an international framework it will probably brick your phone.
That .bin file contains the system partitions from the stock bell framework.
If you want to try go ahead but I think the odds are against you
Click to expand...
Click to collapse
So, there is absolutely NO WAY I can get back to the Bell framework from 2.1.1 without an actual Bell sbf?

IrshaadH said:
So, there is absolutely NO WAY I can get back to the Bell framework from 2.1.1 without an actual Bell sbf?
Click to expand...
Click to collapse
NFHimself knows a way.
But hes a master of code.
Pm him, he might be able to help you.
He was happy he got his bell 2.2.2 thoough. so im assuming it wasnt easy.

Root & Install CM7 on Mytouch 3G Slide 2.2.1

Rooting & Flashing To Stock 2.1
1. Download the files below
2. Copy "ESPRIMG.zip" to the root of your sd card on your phone
3. Extract "Super-Click 2.3.1" & "Mt3s Rooter" to their own folders on your computer
4. Navigate to settings on your phone. Select "Connect to Pc", choose "Charge Only"
5. Navigate to "Applications" then select "Devolpment" and make sure "USB Debugging" is on
6. Run the .exe files within each of the folders (Run .exe as Admin if your using Vista/Win7)
7. In SuperOneClick, select "Shell Root", wait for it to finish rooting
8. In the mt3gs rooter program, click on "Root Me"
You will need to turn on the phones WIFI within 30 seconds so be quick and then wait for it to restart.
9. Once your phone is rebooted it should be in BOOTLOADER Mode. Press volume down to select fastboot (If it doesnt show fastboot then select Bootloader and it will then show the menu with fastboot).
Once fastboot is highlighted, press the power button once.
It will check for ESPRIMG.zip and should show a progress bar in the top right.
After waiting a while it will ask you if you want to update, press volume up.
When it is finished it will ask to reboot, press volume up to do so. (If phone says on Mytouch circle for too long just take out the battery and restart)
If you want to put CM7 on your phone do instructions below.
Installing CM7 with Google Apps
1. Rename "update-cm-7.0.3-Slide-signed.zip" to "update.zip"
3. Copy "Update" & "gapps-gb-20110613-signed" to the root of your phone
4. Turn your phone off. Once off press and hold the volume down and power button at the same time.
5. It will look for the ESPRIMG again, after its done you will see the menu. Highlight "Recovery" and press the power button
6. A Red Triangle screen will show. Press volume up and power, then select "Wipe data/factory reset" then done do the same with "Wipe cache partition
7. After all that you will select "Apply sdcard:update.zip"
8. Select reboot system now
9. Once phone is restarted go into the app drawer and open ROM Manager.
10. Scroll down and select "Download Rom" then select install and then select the option it shows. It should say that Clockwork Mod installed.
11. Now select "Install Rom from SD Card" and select "gapps-gb-20110613-signed" and press OK twice.
It will reboot and show it installing.
Once done it will reboot again and your done. (Btw it will have you sign in and such)
DOWNLOAD THESE FILES:
SuperOneClick 2.3.1-
http://depositfiles.com/files/n0dcxce3t
Mt3s Rooter-
http://depositfiles.com/files/hn8tn6141
or
http://www.mediafire.com/?7yq3wo5yl3odz4k
HTC Espresso Stock Rom (ESPRIMG for 2.1 stock rom)-
http://www.4shared.com/file/OsmF_ZD7/ESPRIMG.html
CM7 Rom for Mytouch 3G Slide-
http://download.cyanogenmod.com/get/update-cm-7.0.3-Slide-signed.zip
Google Apps-
http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
----------------------------------------------------------------------------
MyTouch 3G Slide Drivers (These Might Help With Failed ADB Connectivity)
http://secure.htc.com/US/support/t-mobile-mytouch-3g-slide/downloads/
http://developer.android.com/sdk/win-usb.html
I pieced this together so I don't take full cred. I know this works because I did it to my phone as I typed it
If this works make sure to post it. Also remember to give thanks. This was not easy to figure out.

problem
what if it says cannot roll back bootloader while espring is updated it says bypassed

It bypasses normally

Why not use ClockWorkMod recovery as update.zip and use that to flash roms and things from there?

Just didn't wanna do it that way

thank you so much for posting this i have been trying to gain root ever since i got my phone which was last year thank you

I cant flash update.zip it keeps saying cant mount sd and when i reboot it says i dont have an sd card i need help im stuck with 2.1 and cant load a rom

not working
Didnt work for me.
superoneclick worked saying i had temporary adb root, then i would run mts rooter and it seems like that when the cmd prompt comes up that it doesnt work.
on the first part it said
"cd: can't cd to /sqlite_stmt_journals"
then after I turn wifi on and the cmd prompt goes again I get:
"./exploid not found" and " secretlol not found"
any help?

one small hiccup
Used these instructions to root a friend's phone last night. There was one deviation we had to deal with:
5. It will look for the ESPRIMG again, after its done you will see the menu. Highlight "Recovery" and press the power button
Click to expand...
Click to collapse
While we could see the menu the phone only gave us the choice to run update (YES) or reboot (NO). Recovery was inaccessible. We ran the update (with the bootloader bypassed) then when asked to reboot we chose (NO) and then could select RECOVERY and follow the steps above.
Yes, we did repeat the UPDATE.ZIP process but this time it did not skip Bootloader. Soon CM7 was up and running.
Hope this helps and thanks for the great instructions.

i need some help my says i dont have sd card when it boots up .Also it wont let me apply the update.zip .it says cant mount /dev/block/mmcblk0
cant find /sdcard/update.zip
Ive already reloaded ESPRIMG aboput 15 times im stuck with a useless phone please help
Also my pc wont recognize my phone so i cant use adb or anything

angelo420 said:
I cant flash update.zip it keeps saying cant mount sd and when i reboot it says i dont have an sd card i need help im stuck with 2.1 and cant load a rom
Click to expand...
Click to collapse
Some sd cards work better than others. Sandisk with a little 4 work great. Try to reformat it with a pc and I think it needs to be Fat32
jasonftfw said:
Didnt work for me.
superoneclick worked saying i had temporary adb root, then i would run mts rooter and it seems like that when the cmd prompt comes up that it doesnt work.
on the first part it said
"cd: can't cd to /sqlite_stmt_journals"
then after I turn wifi on and the cmd prompt goes again I get:
"./exploid not found" and " secretlol not found"
any help?
Click to expand...
Click to collapse
Your pc is not detecting your phone. Try installing HTC Sync from the Mytouch 3Gs support page. Also make sure to run it as an administrator while being logged in on a admin account

I actually rooted mine while placing the phone in SYNC Mode after removing the sync program and pressing back button on phone to have it stop looking for SYNC...Just remove SYNC program from the computer not the drivers for the phone to be recognized.

Your pc is not detecting your phone. Try installing HTC Sync from the Mytouch 3Gs support page. Also make sure to run it as an administrator while being logged in on a admin account
Click to expand...
Click to collapse
I downloaded the htc sync software from htc dot com /us/support/t-mobile-mytouch-3g-slide/downloads/ (xda's settings stop me from submitting a link as this is my first post), I then tried to rerun the SuperOneClick and it failed saying "ADB server is incorrect version" or something similar. I copied the ADB.exe from the HTC Sync app directory into the SuperOneClick, and wham bam it worked. Of course the MT3Rooter failed with the same error, so I repeated the copy and I had root.
Thanks for your help everyone, it is very appreciated by this sorta geek.
PS: As a software geek and a 42 year old jerk, it hurts my heart that XDA has to run such nasty anti-spam settings just to keep crap off this forum. Ends up penalizing the users with good intentions. I totally see why it has to be done, and I support the effort, just is sad that it has to be this way.

how do you achieve s-off though? does downgrading, also downgrade your bootloader?
the goldcard app is not working, the site is down to generate keys.

Insanityrains: I have two stupid questions. Is there something I'm missing here? You don't have consecutive numbers for your instructions. Should I follow them in the order you have posted or in the order of the numbers?
Dumb question 2: Where is the download link for the ESPRIMG.zip file?
Thanks for your instructions! I hope it works for me.
UPDATE
I followed the steps to the letter. It worked seamlessly. Thanks insanityrains for putting all this together and the developer who actually figured this out!! However, few things I had to learn by doing it over and over again:
The first part worked awesome! (i.e. rooting and installing 2.1). It will keep saying there were errors and stuff but keep doing what insanityrains says to do.
The second part (installing CM7 with google apps was the hurdle for me): Follow his numbering in post #1 (once again, I'm refering to the second part) to understand what I'm saying below.
Before you begin, you don't need the ESPRIMG file anymore once you have rooted and installed 2.1 (the first part). So delete that file from the root of your SD card. By doing this, you can skip the annoying wait as it tries to reinstall 2.1 on your phone. Now for the two mistakes I did.
1. The first step was a silly mistake, but very much possible for someone to commit. Just rename the file "update" and dont add ".zip" like I did. Everytime I try installing the ROM it kept saying "cannot locate update.zip". I was scratching my head for a few times before I realized the mistake
2. Step #5. It will search for the ESPRIMG file and it is not going to find that. Select "recovery" then
For noobs, dont freak out while doing it. It was scary for me to root the phone. But once I did it fine, it was fun!

so in order to install roms you have to rename them to update zips?

anybody even here anymore?
theres too many outdated rooting guides on here. i already know i cannot achieve s-off now that we accepted the OTA. i already tried to root and it went fine but the clockwork recovery will not work. also when i boot into the 2.1 rom that i downgraded to i see there is no superuser app but it appears i am rooted because most root apps work minus wireless tether. i just want root and to run a semi stock non cm7 type rooted rom. is this possible with s-on or not?
if so can someone point me in the right direction please?

Worked!!!
Thanks insanityrains. Followed the steps and it worked. I would echo comments re: Menu choice for "Recovery" (see updates with fezmonger and ganjagarn).
Again - thanks!

fixxxer2008 said:
anybody even here anymore?
theres too many outdated rooting guides on here. i already know i cannot achieve s-off now that we accepted the OTA. i already tried to root and it went fine but the clockwork recovery will not work. also when i boot into the 2.1 rom that i downgraded to i see there is no superuser app but it appears i am rooted because most root apps work minus wireless tether. i just want root and to run a semi stock non cm7 type rooted rom. is this possible with s-on or not?
if so can someone point me in the right direction please?
Click to expand...
Click to collapse
I thought someone on here said that you could use clockwork mod but you probably have to put it in, i can't help since I rooted my phone with the original method that was much easier.
Have you tried installing rom manager and letting it flash clockworkmod recovery?

jacewt said:
I thought someone on here said that you could use clockwork mod but you probably have to put it in, i can't help since I rooted my phone with the original method that was much easier.
Have you tried installing rom manager and letting it flash clockworkmod recovery?
Click to expand...
Click to collapse
i was working on it for a client, i gave up. thanks anyways.

Did you use a toolkit ?

So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app

yes
Sent from my Nexus 4 using xda app-developers app

Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688

Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4

g2uzer said:
Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
I used Mr Skip's and it worked really well, most important thing to get right is installing the drivers on your PC, I donated to him cause it has so many options and worked so well

Never have and never will. Once you learn fastboot it's too much fun playing in the command prompt lol.

spaceman860 said:
Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4
Click to expand...
Click to collapse
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475

g2uzer said:
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4

spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
i disagree with you..
instead of using "done", id use "profit" :silly:

spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app

soham_sss said:
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device

simms22 said:
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device
Click to expand...
Click to collapse
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app

g2uzer said:
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd like a video of this too.
Can you brick your phone while unlocking? Or just while flashing?

g2uzer said:
So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
use the nexus 4 toolkit by msskip..
its the best one so far and very easy to use...and dont worry abt bricking..
post if any issues,,.

No toolkit. It's important to know how to use fastboot.
Sent from my Nexus 4 using Tapatalk 4 Beta

Unlocking the bootloader and rooting for new users
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:

sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app

g2uzer said:
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah, like I said, the toolkit makes it a lot easier to flash a factory image and frankly, I think it's safer. Less room for mistakes. The less you toy around with flashing the bootloader and the radio, the better chance you have of not bricking your device. Fortunately, when your bootloader is unlocked, as long as you aren't doing anything crazy, you will have a hard time bricking your device. If you have any further questions while you're working on it shoot me a PM and I will try to help. Good Luck!

sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Superb, all this I know already as I did this with one v
But, I read in some tutorial that if you don't reboot to stock recovery and data reset your phone AFTER you've unlocked the boot loader, you will end up with a soft brick? Is it true?
Sent from my Nexus 4 using xda app-developers app

I've been playing g with androids for a long time and dozens of devices. Personally have never used a toolkit and its hard for me to recommend or knock them.
My view is a toolkit teaches you nothing
If a toolkit was made so was another method
Everyone will have an issue with something at some point, so the more you learn now the less freaking out latter
Learning to do thongs yourself will always be safer, I mean yes manually typing a dd command can be dangerous but if you know what you are doing you know when to be cautious, there will always be an example for either argument on this, but I truly can't see a reason to believe a tool kit is safer
But I'm a to each their own sorta guy, but also one who feels the need to learn as much as possible so will promote as much manually methods for anything in life and will do my best to stay away from auto-just-about-anything.... Just a my $.02
Sent from my Nexus 7 using xda premium

[Q] How do you brick your phone?

Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice

dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
Nexus devices are hard to brick. Just to be on the safe side, just follow the videos, follow instructions and you'll be fine.
"Riddle me this, Riddle me that."

It's importanto to be sure that alla drivers are working correctly and if you are able root manually from the command line ( it's easy ).I'm going to root too,and I'm trying to understand if my drivers are working but with no results

Federico_96 said:
It's importanto to be sure that alla drivers are working correctly and if you are able root manually from the command line ( it's easy ).I'm going to root too,and I'm trying to understand if my drivers are working but with no results
Click to expand...
Click to collapse
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"

I used wugfresh's toolkit for the n7 and the n4 with absolutely no trouble. Other than not letting the drivers install automatically drivers. Once I let them go on auto it worked like a charm windows xp.
Sent from my Nexus 4 using Tapatalk 4 Beta

Th3RiddL3r said:
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
Is there a way to check if adb has been installed correctly? I'm using wugfresh toolkit,i already made the drivers test and it went fine,but i don't know if adb has been included in this test too,and I noticed that even if the drivers test said that all is ok,in my device manager i still see a yellow exclamation mark near to the MTP device...another question,if i plug my device with usb debugging on, should i be able to transfer files in the memory? beacuse i can't see my device
With a command prompt i moved in the adb directory and typed adb devices,it said daemon not running,daemon started running successfully,and it showed a serial number and "offline", is this correct?

dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
download the 4.2.2 factory images and keep them handy for emergencies, setup and learn fastboot, and never flash anything for another device/not meant for the N4. if you do this, you will never brick it.

Federico_96 said:
Is there a way to check if adb has been installed correctly? I'm using wugfresh toolkit,i already made the drivers test and it went fine,but i don't know if adb has been included in this test too,and I noticed that even if the drivers test said that all is ok,in my device manager i still see a yellow exclamation mark near to the MTP device...another question,if i plug my device with usb debugging on, should i be able to transfer files in the memory? beacuse i can't see my device
With a command prompt i moved in the adb directory and typed adb devices,it said daemon not running,daemon started running successfully,and it showed a serial number and "offline", is this correct?
Click to expand...
Click to collapse
You need to update the adb driver if it's showing offline. Try searching the new updated adb driver in google. I think it's also here in the N4 forums, not quite sure where.
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"

Th3RiddL3r said:
You need to update the adb driver if it's showing offline. Try searching the new updated adb driver in google. I think it's also here in the N4 forums, not quite sure where.
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
OK so now typing adb devices i get a serial number and "device", i suppose that now adb is working,and now i installed mtp drivers using this guide

Th3RiddL3r said:
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
what's the difference between auto root and manual? which is better?

Questions: 1.Difference between manually rooting and auto-rooting
2. This thing say we can root without unlocking bootloader, is that really legit and if so will our stuff be wiped or no?
3.How to back up my phone? Which program to use?
4.Long does it take to root?

dreseansr said:
what's the difference between auto root and manual? which is better?
Click to expand...
Click to collapse
1) Download either Clockwordmod http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-mako.img or TWRP http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img recovery image and move the file to the folder that contains adb and fastboot.
2) Open a command prompt in the folder that contains adb and fastboot type fastboot oem unlock and install a custom recovery by typing fastboot flash recovery recovery-image-name.img.
3) Boot into recovery and install SuperSU.zip downloaded from http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip.
4) Reboot your phone, search the Play Store for BusyBox, and install BusyBox.
Now your Nexus 4 is fully rooted. If you intend to flash a custom ROM, superuser and busybox will be included in the ROM.

BobWalker said:
1) Download either Clockwordmod http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-mako.img or TWRP http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img recovery image and move the file to the folder that contains adb and fastboot.
2) Open a command prompt in the folder that contains adb and fastboot type fastboot oem unlock and install a custom recovery by typing fastboot flash recovery recovery-image-name.img.
3) Boot into recovery and install SuperSU.zip downloaded from http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip.
4) Reboot your phone, search the Play Store for BusyBox, and install BusyBox.
Now your Nexus 4 is fully rooted. If you intend to flash a custom ROM, superuser and busybox will be included in the ROM.
Click to expand...
Click to collapse
Wait I'm confused, Clockwordmod is to backup my stuff?

dreseansr said:
Wait I'm confused, Clockwordmod is to backup my stuff?
Click to expand...
Click to collapse
Clockworkmod and TWRP are recovery software. Either can be used to perform nandroid backups of all system files, applications and data, and boot image installed on the phone at the time of the backup. Recovery may also used to flash custom ROMs or kernels and to install some software directly from a zip file and to wipe cache, Dalvik cache, and system before flashing a new ROM.
At a minimum, you should perform a nandroid backup of your phone when you have it rooted and have all essential programs installed so you have an image of your phone in a working state as insurance in case you do something wrong and need to restore your phone to normal operation.

BobWalker said:
Clockworkmod and TWRP are recovery software. Either can be used to perform nandroid backups of all system files, applications and data, and boot image installed on the phone at the time of the backup. Recovery may also used to flash custom ROMs or kernels and to install some software directly from a zip file and to wipe cache, Dalvik cache, and system before flashing a new ROM.
At a minimum, you should perform a nandroid backup of your phone when you have it rooted and have all essential programs installed so you have an image of your phone in a working state as insurance in case you do something wrong and need to restore your phone to normal operation.
Click to expand...
Click to collapse
hm ok so is there any video showing the steps of how to back up my phone or using this programs?

You need to do more research on your own all this info u need is on this site and on YouTube please read for yourself
Sent from my Nexus 4 using Tapatalk 4 Beta

dreseansr said:
hm ok so is there any video showing the steps of how to back up my phone or using this programs?
Click to expand...
Click to collapse
You Tube videos for using TWRP to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=laBKgRCpMeI and at http://www.youtube.com/watch?v=bGgTkzLHzHo respectively.
You Tube videos for using Clockworkmod to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=36cihz4l-vk and at http://www.youtube.com/watch?v=Gvi0cbMz1V8 respectively.

dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
Well I think there is an forum rule that says we're not supposed to discuss about things such as how to brick your phone. And the most, if not all, of the bricks on the Nexus 4 are recoverable anyways.
That being said, before you flash anything, especially kernel or bootloader, be absolutely sure the file is made for your device
Sent from my Nexus 4 using xda app-developers app

nelsonator1982 said:
You need to do more research on your own all this info u need is on this site and on YouTube please read for yourself
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
If you have read the thread you will see that i've done that already but since he/she is informing me on a program that they used, i am simply asking for a video that showed them how to do it so i know everything is legit.

BobWalker said:
You Tube videos for using TWRP to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=laBKgRCpMeI and at http://www.youtube.com/watch?v=bGgTkzLHzHo respectively.
You Tube videos for using Clockworkmod to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=36cihz4l-vk and at http://www.youtube.com/watch?v=Gvi0cbMz1V8 respectively.
Click to expand...
Click to collapse
Thank you

Stuck in TWRP

Hello,
I try to experiment with my phone a lot. I think I overdone it today.
Had no GPS running CM10.2 and went back to stock rooted.
Had a message today there was an update (from Sprint). Installed.
The phone booted right to TWRP and keeps on booting there.
I tried to restore the CM10 back up with no luck, tried restoring stock back up with no luck.
Then I wiped everything clean. Still boots to TWRP.
I do have my backups on my PC.
I have no roms in the phone anymore so I cant flash anything.
Any suggestions?
Keep in mind I am fairly new to this. If I have to read up on something just point me to the right direction.
THANKS!
Dominik

This belongs in the Q&A section. Do you know how to use adb? Chances are that even sideloading a rom will not work. I had this issue not to long ago and I had to completely restore my device using lg flash tool. It just keeps rebooting into twrp? Try downloading a rom on your pc. Download the android sdk, navigate to platform-tools inside of the sdk folder, place the download rom inside this folder, hold down shift key and right click, select open command window here, open twrp on your phone and click advanced and hit adb sideload, type adb devices in the command window and it should list your device(you need your phones drivers first!), the type in cmd adb sideload (name of rom) without "()". it should push it to your phone.
If that method does not work you need to use the lg flash tool. download this to your pc: http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/Sprint+LS980/
look at the readme inside the folder and it will navigate you to the step by step instructions. Just make sure you use the Sprint files included in the link above and not the Verizon files. Steps are the same, files are not. It's very important.

dozol said:
Hello,
I try to experiment with my phone a lot. I think I overdone it today.
Had no GPS running CM10.2 and went back to stock rooted.
Had a message today there was an update (from Sprint). Installed.
The phone booted right to TWRP and keeps on booting there.
I tried to restore the CM10 back up with no luck, tried restoring stock back up with no luck.
Then I wiped everything clean. Still boots to TWRP.
I do have my backups on my PC.
I have no roms in the phone anymore so I cant flash anything.
Any suggestions?
Keep in mind I am fairly new to this. If I have to read up on something just point me to the right direction.
THANKS!
Dominik
Click to expand...
Click to collapse
1. Never flash an OTA on a phone that's been modified in any way.
2. Never post questions in development.
3. What typo said

phatmanxxl said:
1. Never flash an OTA on a phone that's been modified in any way.
2. Never post questions in development.
3. What typo said
Click to expand...
Click to collapse
Sorry, I will ask in the correct sub-forum.
Dominik

dozol said:
Sorry, I will ask in the correct sub-forum.
Dominik
Click to expand...
Click to collapse
its an easy fix. search the forums for a fix.