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.
Related
***********Don't follow this method**************
THIS is what you want to do. This thread is an older method.
Do this at your own risk!!!....I'm by no means an expert on this. In fact it's the first time I have done this. There are probably tons of guide to doing this on the T-Mobile version but I made this to help people with the Canadian Rogers G1. So it only applies to that specific phone. This is also expecting you be using Windows (I use XP but Vista will work but I don't know where the command prompt is found....google it if it isn't in the usual spot). Also the commands would be the same using a Mac but yet again I don't know what or where the equivalent of windows command prompt would be found on a Mac.
First off you need the Android SDK which you can get from here (http://developer.android.com/sdk/1.5_r2/index.html).
Unzip the folder inside the .zip file to C:\Android so the final resulting file structure will look like C:\Android\android-sdk-windows-1.5_r2\
Now do the steps 2 and 3 found here http://developer.android.com/guide/developing/device.html
I have cut and pasted these steps here but if you are using a mac you may need to refer to the link. Actually refer to it anyways in case I missed something.
**************** Steps 2 and 3 *********************
Turn on "USB Debugging" on your device.
On the device, go to the home screen, press MENU, select Applications > Development, then enable USB debugging.
Setup your system to detect your device.
If you're developing on 32-bit Windows, you need to install the 32-bit USB driver for adb. The USB driver is included in the SDK package. To install it, follow these steps:
1.Connect your Android device via USB. When the Found New Hardware Wizard appears, you'll be asked if you'd like Windows Update to search for software. Select No, not this time and click Next.
2.Select Install from a list or specified location and click Next.
3.Select Search for the best driver in these locations. Browse to the usb_driver/x86 in the SDK package (<sdk>\usb_driver\x86).
4.Click Finish. The system should install the driver files as necessary. Your machine may require a reboot.
********************************************
Plug your USB cord into your phone and plug the USB cord into your computer.
Open a command prompt in windows by going to Start/Run and then type cmd. You should a dos like window open up. Now navigate to the directory C:\Android\android-sdk-windows-1.5_r2\tools
Type “adb devices” to confirm USB Debugging is turned on
Keep the command prompt open for later use
Get fastboot from here (http://www.htc.com/www/support/android/adp.html) and put it in the tools section of the SDK
Get these files http://drop.io/ii4t2ax and put them in the tools section of the SDK. Mount your sd card so you can copy update.zip to the root of your sd card.
Turn off your phone and then press the camera button and the power on button so it loads up to fastboot mode (or whatever it is called..lol). Once it gets to the screen with 3 androids on skateboards on the bottom you should press the “call” button to the farthest left. It should go to another screen that says “FASTBOOT USB”. If it only says “FASTBOOT” then you gotta plug in the USB cable which you should have left plugged in if ya followed the steps properly .
Now in the command prompt you need to type “fastboot boot recovery.img” don't touch your phone tile it gets to a new choice of menus in recovery mode. Once it gets there you should make a nandroid backup. I really urge you to make the backup. Make sure there is space left on your SD card.
So follow the menus and press the button combination to make the back up and once that is done press the other button combination to apply the update.zip file....Do not touch your phone at all....I'll cut and paste what Haykuro's directions were on this part to emphasize the importance of not touching anything....
(LET IT FINISH, DO NOT TOUCH ANYTHING UNTIL YOUR PHONE IS COMPLETELY IDLE. DO NOT TOUCH AFTER FIRST REBOOT (WHEN CHIP APPEARS) UNLESS YOU LIKE A BRICK. )
Mine didn't take very long but if it does still do not touch anything. Please....just don't!
Once it is done press HOME+BACK to reboot the phone out of recovery mode.
Power off your phone and then press the camera button while pressing the power on button to go back to the fastboot menu. Press the “call” button (to the farthest left remember!) so you see it say “FASTBOOT USB”. Once again...If it only says “FASTBOOT” then you gotta plug in the USB cable which you should have left plugged in if ya followed the steps properly .
In the command prompt which you should have left open for convenience you have to type “fastboot flash boot boot.img”
Then type “fastboot flash recovery recovery.img”
Then type “fastboot reboot”
At this point you basically have root but you need to change permissions on a file that need to be on the phone so everything works as your would expect with root
Turn the phone on to be on the operating system.
Type “adb root” in the command prompt to confirm you have root access
Download this file http://www.magicandroidapps.com/su.zip
Unzip the file to the tools folder of the SDK
In the command prompt type “adb remount”
Then type “adb push su /system/bin/su”
Then type “adb shell” and you should get prompted with a # symbol
Type “chown root.shell /system/bin/su” right after the # symbol
Then type “chmod 6755 /system/bin/su”
That should be it...try running the market enabler or SetCPU which you can get here http://forum.xda-developers.com/showthread.php?t=505419
If they work then you have root....currently you CANNOT use any of the custom roms because they were made for T-Mobile versions of the G1. I'm waiting for conversions of these roms myself so have fun waiting just like me. This is the first time I have ever hacked/rooted any phone so be sure to research stuff yourself...I might have things wrong. Who knows....it's all a risk just like I took when I decided to try it without having a step by step guide to read from.
Remember guys...I JUST wrote this so be sure to read it the whole way through before jumping into things. Post problems you run into here so I can fine tune it.
so you managed to root the rogers G1?? great job!! did you figure this out yourself???
no...Haykuro did this. I just took all the available information and put it in order to help others do it. It was all in this thread here http://forum.xda-developers.com/showthread.php?t=522127
Can we get a tutorial of how to flash a new rom now I really want to try out the new hero rom.
there are currently no compatible roms. Cyanogen would like to port his ROMto the rogers version but he doesn't have a rogers phone to test with. Hopefully we would not need to buy him a whole phone just to port his ROM....if he employed a bunch of testers to help him he might be able to do it. I really don't know what he requires to do this though. I'm sure we will get some compatible roms soon. Maybe some of the roms do work....pretty early in the game to know what works and what doesn't. I've personally been having a great time ever since I bought this phone just reading about it, watching things happen and tinkering with things. I can just imagine how Haykuro feels being the one to make this happen. I need a compatible ROM to go further though.
XwXDv8XwX said:
there are currently no compatible roms. Cyanogen would like to port his ROMto the rogers version but he doesn't have a rogers phone to test with. Hopefully we would not need to buy him a whole phone just to port his ROM....if he employed a bunch of testers to help him he might be able to do it. I really don't know what he requires to do this though. I'm sure we will get some compatible roms soon. Maybe some of the roms do work....pretty early in the game to know what works and what doesn't. I've personally been having a great time ever since I bought this phone just reading about it, watching things happen and tinkering with things. I can just imagine how Haykuro feels being the one to make this happen. I need a compatible ROM to go further though.
Click to expand...
Click to collapse
Is Haykuro working with Cyanogen? Man I just want to play with the Rogers Rom. Oh well I guess I'll settle for getting rid of the Rogers crap and being able to buy stuff on the Market finally.
Yep, I made a 3.6 for the Rogers Dream. I haven't actually tested it because I don't have one, but I used Haykuro's tools to build the boot image. Let me know if it works for you guys!
Holy...where is that at? lol
My wife has gotta get her ass home with my phone damnit! lol
http://forum.xda-developers.com/showthread.php?t=518851
lol, I just finished restoring my phone too. Oh well I am downloading your files now cyanogen, here's to hoping I don't brick my phone on my first flash attempt.
Can someone point me to a guide to flash this rom to my phone?
XwXDv8XwX said:
Can someone point me to a guide to flash this rom to my phone?
Click to expand...
Click to collapse
After you have rooted, copy the file to your sdcard as "update.zip", boot into the new recovery mode, wipe your data if you are coming from the stock build, then flash the update! The first boot will take a bit longer than usual. Check my thread for a FAQ.
Just wanted to say "Thank You" I have been following the threads in the background for the better part of a week, and was hesitant to give it a shot as I am not too sharp on dealing with dos boxes. However followed it along and everything went off perfect, grabbed set CPU and installed it and works. So I guess I have root. Not really sure what I can do with root, but will look forward to browsing around and seeing what is cool.
The big thing is I want to be able to flash new roms. So I guess this is the first step in doing that. (already actively flash PPC roms on the Hermes)
Again thanks for everyones work on this.
well here it goes....it'll be the first time I ever flashed a new rom to my phone...at least I know some other people have tested this version of cyan's rom so I feel pretty safe doing this. I would just send it back and pretend I don't know what's wrong with my phone if I did brick it but things seem to be going pretty smooth so far.
I wonder if Cyanogen meant to wipe date first or after I applied the update.zip.....I figure he meant to wipe after I apply the update since the update was on the sdcard so I would not be able to apply an update I wiped off the sdcard. It's taking longer to boot up like he said so hopefully that's a good sign. I did just remember there were a few pics I would have prefered to save...lol....oh well.
XwXDv8XwX said:
I wonder if Cyanogen meant to wipe date first or after I applied the update.zip.....I figure he meant to wipe after I apply the update since the update was on the sdcard so I would not be able to apply an update I wiped off the sdcard. It's taking longer to boot up like he said so hopefully that's a good sign. I did just remember there were a few pics I would have prefered to save...lol....oh well.
Click to expand...
Click to collapse
No, you wipe before the update. Wiping doesn't erase your SD card, only the internal data partition.
Also, my ROM is a "Google" based ROM. You'll have to sacrifice the spiffy HTC dialer and Exchange support, but I include all the other HTC apps.
How's your flash going XwXDv8XwX? I tried, but was stuck on the Rogers screen for more than 10 minutes. I rebooted the phone and tried again using the "adb logcat" command to try and see what my phone is doing but as soon as it restarted I stopped getting stats. Is this like a 20-30 minute setup process perhaps?
This is taking ALOT longer than usual. It's staying at the rogers logo right now....how bad is this?
I bought my Samsung Nexus S from a Koodo booth here in Canada two days ago and have been enjoying it quite a lot since. I've also been reading up on the wealth of information pertaining to rooting it and trying to sort out so many different factors. I notice I'll have to use the search feature to find one little triviality that comes along and the fix it.
Then I decided to just make my own thread where I'll post every step of the ways I find and how I figure out how to solve my issues involved with rooting my phone.
To start, I found out you can create a backup with NANdroid.
I couldn't find any information on where to download this elusive "NANdroid" and then heard from This thread that all I have to do is
kenvan19 said:
Now lets get started. First, how does one install mods on Android? Lets do a NANDroid backup to begin:
1) Turn your phone off.
2) While holding the Volume Up button press the power button until the screen turns on and you will see a black screen with an Android on it and a lot of numbers and words that will mean nothing to you. This is called the Bootloader. In both the bootloader and the recovery mod you will use the volume buttons to navigate between options and the power button to select one.
3) Navigate down to Recovery option and select it.
4) Navigate down to backup and restore
5) Navigate down to backup and select it and let it run.
Click to expand...
Click to collapse
This didn't seem to be the case when I followed these steps; coming first to the predicted screen,
(containing this information)
Code:
FASTBOOT MODE
HW VERSION - REV 16
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020UCKB2
CARRIER INFO - ATT (but im with Koodo?)
SERIAL NUMBER - Lots of digits.
LOCK STATE - LOCKED
Also giving me the option to select between
Reboot Bootloader
Reboot
Recovery
Power Off
When going into recovery mode I'm greeted with an animation of a box with an arrow coming out of it. This turns into a triangle with a exclamation in the middle of it.
From here I press power and volume up to come to a menu that is supposed to have a NANdroid option I've been told.
Instead; I get the options:
Reboot system now
Apply update from /sdcard
wipe data/factory reset
wipe cache partition
At this point I'm currently stumped, though I'll continue searching as I'd rather not be stuck without a backup before starting the rooting process.
UPDATE: Even though I'm weary of proceeding without backing up, I'm sure I'll be able to restore my phone back to factory somehow.
I spent the night downloading and installing the Android SDK, then started configuring my device for use on windows 7.
Currently I'm in the bootloader interface after installing my phone's device drivers while being in fastboot mode.
The drivers take a couple of minutes, but they install successfully!
On I go, I'll just point DOS to the directory I want it to. Now I'll run the program through dos. What's this?! AND ERROR!?
Psht, I WOULD be missing the "AdbWinApi.dll" Not a hard thing to fix. I'll just google for the file!
Oh! I don't even have to download the file, the directory has just changed!
That was an easy problem to solve with many solutions provided!
Time to try again!
Sweet, it works. WHOA! TEXT ON MY ANDROID WHAT ARE YOU DOING!
And I select Yes to come to a nice screen that says my phone is now unlocked!
Now I need to download an image file? Okay. I can do this.
Okay, flash recovery the flashboot. Looks like the image has updated since the thread's instructions. Hopefully it's still compatible.
Now I just need to root. Just need to install a nice zip file.
AAAND, I can't seem to push it onto my phone for some reason. Time to search.
Oh, I can just copy and paste this file by enabling USB storage and dragging it over.
I'll just follow the rest of the steps, to no errors! Whoo! I'm free to install any ROM I want!
You'll need a custom recovery for nandroid, but first you will need to root. There's guides in the nexus s general section on doing that.
I kind of like this post.
Sent from my Nexus S using XDA Premium App
apreichner said:
You'll need a custom recovery for nandroid, but first you will need to root. There's guides in the nexus s general section on doing that.
I kind of like this post.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I just read through Kursk's guide for rooting the i9020a and i9023 and noticed I have no ability to backup my android in the case something goes wrong.
Am I missing something, or do I have to root before having the privilege of backing up my phone's current ROM.
edit: Got sidetracked by a thread in the Chef's forum and learned that Java is the language for App development for Androids. Been reading about the Android OS and how it works for the past couple of hours. Brains bursting. xd
http://forum.xda-developers.com/showthread.php?t=895545
^ Has pretty much all you need to know for installing a custom recovery and rooting your phone.
It's only once you've installed ClockWorkRecovery Mod that you'll be able to easily make backups.
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.
I'm NOT responsible if you bork your tablet because you can't follow simple instructions!
I've just made a simple batch file with adb, and the recovery file all in one zip for y'all.
Make sure you've unlocked your bootloader by following instructions HERE
1) Download Chainfires latest root and copy to Your Internal SD card on your tablet
2) Download and install DRIVERS
3) Download and extract nexus7_2013_recovery_A+.zip to a folder on your PC.
4) Open folder where you extranted nexus7_2013_recovery.zip
5) Make sure your tablet is powered on, and connected to the PC, then click on "Nexus7.bat" and follow instructions. (If your PC is installing drivers once it boots into fastboot, WAIT until the drivers are installed before clicking next!)
6) Be ready and hold volume up as the tablet will restart automatically, keep holding volume up until you reach the TWRP screen
7) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
8) when you reboot Superuser will be updated automatically by the Play Store
Enjoy!
BIG thanks to Chainfire for his root, and team win recovery project for their fast work on the recovery!
07/30/13 Updated SuperSu link to latest revision (ver 1.51).
07/29/13 Updated SuperSu link to latest revision (ver 1.50).
For those that couldn't find their azzes if a target was painted on it, here's a link to the video.
http://www.youtube.com/watch?feature=player_embedded&v=UpcTMTu-5Qc
I'm NOT responsible if you bork your tablet because you can't follow simple instructions!
I got through the first 5 steps. However the tablet rebooted to the OS. At step 6 how do you reboot into recovery?
Ravynmagi said:
I got through the first 5 steps. However the tablet rebooted to the OS. At step 6 how do you reboot into recovery?
Click to expand...
Click to collapse
ADB reboot recovery
Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Edit - Didn't see you had a video. It didn't boot me into fastboot. I'm sure I did something wrong. Thanks again!!!
evodon84 said:
Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Make sure you've unlocked your bootloader by following instructions HERE
1) Download Chainfires latest root and copy to SD card
2) Download and install DRIVERS
3) Download and extract nexus7_2013_recovery_A+.zip to a folder on your PC.
4) Open folder where you extranted nexus7_2013_recovery.zip
5) Power off your device.
6) Once powered down, hold Volume Down and Power. (this will boot you into fasboot)
7) Make sure your tablet is connected to the PC, then click on "Nexus7.bat" and follow instructions. (If your PC is installing drivers once it boots into fastboot, WAIT until the drivers are installed before clicking next!)
8) Be ready and hold volume up as the tablet will restart automatically, keep holding volume up until you reach the TWRP screen
9) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
10) when you reboot Superuser will be updated automatically by the Play Store
Click to expand...
Click to collapse
Umm thanks, but the bat file boots you into fastboot...watch the video
When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.
greenmky said:
When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.
Click to expand...
Click to collapse
Yes, you may want to create a folder in there for organizing all your flashable zips
greenmky said:
When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.
Click to expand...
Click to collapse
Yes, your INTERNAL SD CARD
Thanks guys, I haven't done much rooting / flashing with devices without SD cards before. I used the Nexus 7 toolkit to root the old Nexus 7. Everything I rooted before that had a real SD card to dump zips on - wanted to make sure where TWRP could access.
Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.
evodon84 said:
Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Edit - Didn't see you had a video. It didn't boot me into fastboot. I'm sure I did something wrong. Thanks again!!!
Click to expand...
Click to collapse
I'm ammending the video now to reflect your suggestion about booting right into recovery afterwards...thank you
Ravynmagi said:
Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.
Click to expand...
Click to collapse
What error message are you getting at the end of the flash, or does it say success...watch the screen as it's flashing.
I just ammended the video, follow along
Ravynmagi said:
Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.
Click to expand...
Click to collapse
Try going directly into recovery right after the batch file finished and restarts your device. I had the same problem if I let my device boot and then reboot into recovery.
ATGAdmin said:
I'm ammending the video now to reflect your suggestion about booting right into recovery afterwards...thank you
Click to expand...
Click to collapse
Cool, glad I could be of some small assistance.
Rooted just fine, thanks! Saved me typing some adb commands and such.
evodon84 said:
Try going directly into recovery right after the batch file finished and restarts your device. I had the same problem if I let my device boot and then reboot into recovery.
Click to expand...
Click to collapse
Yes, that was the problem. I started doing the steps manually and instead of letting it reboot after flashing the recovery.img, I went straight to Recovery from Fastboot and it worked fine. Thanks.
Ravynmagi said:
Yes, that was the problem. I started doing the steps manually and instead of letting it reboot after flashing the recovery.img, I went straight to Recovery from Fastboot and it worked fine. Thanks.
Click to expand...
Click to collapse
I dont know what happened but this did not work, I can still boot my device, but now I have no recovery installed. If I attempt to boot into recovery, i get the red triangle underneath it says *No command* I have tried to research the problem here but no luck in getting TWRP to flash.
Just curious why was this moved out of development? I'm glad I caught it yesterday before it was moved. All the past android devices I've owned have had their root instructions under a development forum here on XDA. I would have assumed since this device was so new the root instructions where not available yet. I admit it would have been my fault for not searching but as I said the precedence has been search the development forum for root guide. Just a thought, I know you moderators are obviously forum gurus..but I think a good portion of the community is used to finding them their. Even the OP thought it was the proper location.
samg77 said:
Just curious why was this moved out of development? I'm glad I caught it yesterday before it was moved. All the past android devices I've owned have had their root instructions under a development forum here on XDA. I would have assumed since this device was so new the root instructions where not available yet. I admit it would have been my fault for not searching but as I said the precedence has been search the development forum for root guide. Just a thought, I know you moderators are obviously forum gurus..but I think a good portion of the community is used to finding them their. Even the OP thought it was the proper location.
Click to expand...
Click to collapse
There's no telling why they do what they do. I don't question it anymore lol
Sent using XDA premium on my Nexus 7 (2) tablet.
ATGAdmin said:
There's no telling why they do what they do. I don't question it anymore lol
Sent using XDA premium on my Nexus 7 (2) tablet.
Click to expand...
Click to collapse
Well honestly I posted the question mainly to have an intellectual conversion regarding allowing this to be in development until a alternate root method is posted.I mean I am not an android developer but I am a systems engineer for twenty years (by this I'm just simply pointing out I am of above average technical skill) and simply because I've always my root method for the past ...I'd estimate about a dozen android models I've rooted found root under development. So some others might miss it too
samg77 said:
Well honestly I posted the question mainly to have an intellectual conversion regarding allowing this to be in development until a alternate root method is posted.I mean I am not an android developer but I am a systems engineer for twenty years (by this I'm just simply pointing out I am of above average technical skill) and simply because I've always my root method for the past ...I'd estimate about a dozen android models I've rooted found root under development. So some others might miss it too
Click to expand...
Click to collapse
You're preaching to the choir bro, I'm with ya.
Sent using XDA premium on my Nexus 7 (2) tablet.
Retail Verizon Note 4 N910VVRU2BPA1 going to the Developer Mode, Relax and take your time, You're in no hurry. I reduced the number of steps to gain permanent root and unlock the bootloader.
Files and HYPERLINKS you may need:
View attachment SAMSUNG_USB_Driver_for_Mobile_Phones.zip
View attachment minimal_adb_fastboot_v1.3.1_setup.zip
View attachment samsung_unlock_n4-fix.zip
View attachment NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.zip
View attachment 3779589
View attachment Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
View attachment BETA-SuperSU-v2.71-20160331103524.zip
View attachment Odin3_v3.10.7.zip
View attachment twrp-3.0.2-0-trltevzw.tar.zip
View attachment Debloater-setup-v3.90.zip
( Re-partition sd card ) ( PaulPizz ROM-5.1.1 is under Past Builds )
Here we go....In Windows, Copy samsung_unlock_n4-fix to the "Minimal ADB and Fastboot" install folder location.
On Phone, after doing a Factory Reset and without a sim card, Skip all initial phone setup except wifi.
Rejected all popup offers and tick don’t remind me.
Connect phone to usb as a Media Device then Copy these files to the phones internal storage.
(1)NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
(2)Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
(3)BETA-SuperSU-v2.71-20160331103524.zip
Disconnect usb cable and enable USB debugging, allow Unknown sources installations, also change Display timeout to 10 min. and format your sd card. Close all recent apps. Reconnect usb cable ( When prompted click Always allow usb debugging on this computer)
Install and open Kingroot ( decline Google offers...) and go to the point "Root access is unavailable" DO NOT start root yet, WAIT until the last second so the phone will remain stable. Copy the name "samsung_unlock_n4-fix" from the actual file so it will be on your clipboard and you can right click it into the adb commands.
Start the program "Minimal ADB and Fastboot" and use the commands
(1) adb devices
(2) adb push samsung_unlock_n4-fix /data/local/tmp/
(3) adb shell
{[ HERE NOW Start Rooting with Kingroot. Once phone is rooted continue with the adb commands }]
(4) su ( You have to grant root permission on the phone and continue)
(5) cd /data/local/tmp/
(6) chmod 777 samsung_unlock_n4-fix
(7) chown root.root samsung_unlock_n4-fix
(8) ./samsung_unlock_n4-fix
When prompted type in yes and Wait... Wait for the phone to go into a boot-loop then disconnect the usb cable, pull the battery and SD card.
Check in Download, you should now have MODE: Developer. The boot-loader is unlocked.
On computer close “Minimal ADB and Fastboot” and open Odin untick auto reboot. Connect usb cable then flash twrp-3.0.2-0-trltevzw.tar.md5. Wait a minute... untill Odin finishes then pull the battery.
Next to last thing, reinstall battery and manually boot into recovery. You now have a unlocked bootloader with TeamWin Recovery. STOP FIRST thing, use it to make a complete backup { Now at this point you could restore a TWRP backup or -HYPERLINK-install a custom ROM. OR To remain stock with root continue.......}
Install Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip and BETA-SuperSU-v2.71-20160331103524.zip with TWRP from internal storage. Then do a Factory Reset with TWRP or from within the phones setting and it will be good to go. -HYPERLINK-To reuse the SD card re-format / re-partition it with your computer.
I have also been able to used Odin to flashed the SM-N910V Developer Edition up to date with the retail BPA1 file found on Sammobile then used the direction above to convert it back to Developer Mode. Have Fun and less get busy before Verizon closes the window.
I recommend using Gatesjunior's Debloater program to block SDM.apk before reconnecting wifi or someday you could get a over the air updated that could lock it back up.
Some people are having problems with Kingroot because they are starting off with a corrupted phone.
To clear up corruption, junk files or whatever from your phone Odin Stock 5.1.1, and do a Factory Reset twice in a row. Restore from within Recovery and from within the Phone Setting. Skip all the initial phone setup just do the clean up twice. After that you could still have some corruption but, That should clean it up.
doctor-cool said:
Retail Note 4 going to the Developer Mode, using the same files found HERE http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883. Relax and take your time, Your in no hurry. I stabilized the process and reduced the number of steps to gain permanent root and unlock the bootloader.
Here it is....In Windows, Copy samsung_unlock_n4-fix & BETA-SuperSU-v2.71-20160331103524.zip to the Minimal ADB and Fastboot install folder location.
On Phone, after doing a factory reset in recovery and without a sim card, I skipped all the initial phone setup except for putting in my wifi password.
I rejected all popup offers and clicked don’t remind me later. I deleted the time widget to make room for shortcuts so I could work on the home screen.
Connect phone to usb as a Media Device then Copy these files to the phones internal storage.
1. Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
2. NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
3. BETA-SuperSU-v2.71-20160331103524.zip
Disconnect usb cable and enable USB debugging, allow Unknown sources installations also I would change Display timeout to 10 min. and format your sd card. Close all resent apps. Reconnect usb cable (if and when prompted click Always allow usb debugging on the computer)
Install and open Kingroot on the phone go to the point that says "Root access is unavailable" DO NOT START ROOT yet WAIT!!! Close all resent apps and ok the popup about recent apps.
Pull the battery and if you haven’t already done it, install a formatted sd card. Power up the phone and connect usb cable.
{[Be ready to grant permission when asked by phone.}] Close all resent apps again. Open Kingroot and go to the point "Root access is unavailable" DO NOT start root yet, wait until the last second so the phone will remain stable. I would copy the name "samsung_unlock_n4-fix" from the actual file so it will be on your clipboard and you can right click it into the adb commands.
Start the program "Minimal ADB and Fastboot" and type the commands
(1) adb devices (if and when prompted click Always allow usb debugging on the phone)
(2) adb push samsung_unlock_n4-fix /data/local/tmp/
(3) adb shell
{[ HERE NOW Start Rooting with Kingroot once phone is rooted continues with adb commands }]
(4) su ( you have to grant permission on the phone and continue)
(5) cd /data/local/tmp/
(6) chmod 777 samsung_unlock_n4-fix
(7) chown root.root samsung_unlock_n4-fix
(8) ./samsung_unlock_n4-fix
Wait... Wait for the phone to go into a boot-loop then disconnect usb cable pull the battery and SD card.
Check in Download, you should now have MODE: Developer. The boot-loader is unlocked.
On computer close “Minimal ADB and Fastboot” and start Odin. Connect usb cable to flash twrp-3.0.2-0-trltevzw.tar.md5.
Here is a tricky part. As soon as Odin finishes and you can feel the phone vibrate off quickly pull the battery or it will reload stock recovery.
Next to last thing, reinstall battery and manually boot into recovery. Now you have a unlocked bootloader with permanent Kingroot root.
Now install Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip then BETA-SuperSU-v2.71-20160331103524.zip with TWRP from internal storage do a Factory Reset with TWRP and it’s good to go.
I also used Odin to flashed the SM-N910V Developer Edition up to date with the retail BPA1 file found on Sammobile then used the direction above to convert it back to Developer Mode. Have Fun and less get busy before Verizon closes the window.
I think we should use Gatesjunior's Debloater program to block SDM.apk or we could get a over the air updated that could lock it back up.
Click to expand...
Click to collapse
Follow all steps and work like a charm thanks :good::good::good::good::good::good:
if we untick auto reboot we can access twrp after manual reboot without any problem
vvverma said:
Follow all steps and work like a charm thanks :good::good::good::good::good::good:
if we untick auto reboot we can access twrp after manual reboot without any problem
Click to expand...
Click to collapse
I have not tried the untick auto reboot. In should work in this case but be careful making changes to Odin.:fingers-crossed:
doctor-cool said:
I have not tried the untick auto reboot. In should work in this case but be careful making changes to Odin.:fingers-crossed:
Click to expand...
Click to collapse
That is a step mentioned in some of the other guides. It would make the experience a little less harrowing as during the last step people could simply power the phone back up in recovery themselves instead of having to try to pull the battery just after they feel the phone vibrate.
Point taken people can choose for themselves
MissionImprobable said:
That is a step mentioned in some of the other guides. It would make the experience a little less harrowing as during the last step people could simply power the phone back up in recovery themselves instead of having to try to pull the battery just after they feel the phone vibrate.
Click to expand...
Click to collapse
Thanks for the information. [/B]
Tested and EDITED untick auto reboot and other improvments. Works Great[/COLOR]
So glad there's another thread for this. Maybe my mailbox will stop blowing up.
It worked perfectly!! Thank you so much!
I was a little skeptical about that 910P kernel image, but no problems so far, and the SuperSU bootloop didn't occur this time.
I didn't even have to do a factory reset and it worked.
EDIT:
May have spoken too soon. I inserted my SD card and the screen went blank and the phone buzzed once, almost as if it had restarted. I held down the PWR and two VOL buttons to force restart it and I may be stuck at the Verizon logo screen. It hasn't rebooted, but it's not doing anything.
EDIT AGAIN:
I force-rebooted again on the Verizon screen and it booted up. No problems after formatting the SD card with a computer.
Zacharee1 said:
It worked perfectly!! Thank you so much!
I was a little skeptical about that 910P kernel image, but no problems so far, and the SuperSU bootloop didn't occur this time.
I didn't even have to do a factory reset and it worked.
EDIT:
May have spoken too soon. I inserted my SD card and the screen went blank and the phone buzzed once, almost as if it had restarted. I held down the PWR and two VOL buttons to force restart it and I may be stuck at the Verizon logo screen. It hasn't rebooted, but it's not doing anything.
EDIT AGAIN:
I force-rebooted again on the Verizon screen and it booted up. No problems after formatting the SD card with a computer.
Click to expand...
Click to collapse
Some people are having problems because they have already corrupted their phone rooting while it was unstable. They need to Factory Restore. Not only is Samsung and Verizon working to block root but so is Google. The SD Card need to be formatted with a PC.
doctor-cool said:
Some people are having problems because they have already corrupted their phone rooting while it was unstable. They need to Factory Restore. Not only is Samsung and Verizon working to block root but so is Google. The SD Card need to be formatted with a PC.
Click to expand...
Click to collapse
So the factory reset is a safety step?
For Security and to avoid corruption problems.
Zacharee1 said:
So the factory reset is a safety step?
Click to expand...
Click to collapse
At some time we all have given Google permission to gather information. For that reason and because Kingroot is connected to a Chinese Server. I would prefer not having my information on the phone when rooting with Kingroot.
I would call Kingrooting with your personal accounts on the phone HOT ROOTING. If I were going to HOT ROOT I would remove all my personal accounts from the phone. I have done it and it will work but I prefer to do a factory restore.
doctor-cool said:
At some time we all have given Google permission to gather information. For that reason and because Kingroot is connected to a Chinese Server. I would prefer not having my information on the phone when rooting with Kingroot.
I would call Kingrooting with your personal accounts on the phone HOT ROOTING. If I were going to HOT ROOT I would remove all my personal accounts from the phone. I have done it and it will work but I prefer to do a factory restore.
Click to expand...
Click to collapse
Oh, so privacy. Well I have nothing very important on this phone, so that's fine for me. If I do this on someone else's phone though, I'll definitely remember that.
I am an idiot that is stoned and had no issues following these directions thanks! Stupid question.. the stuff it copied to my sdcard during rooting.. do i need to keep that for anything? or is it basically used as swap space?
Icetech3 said:
I am an idiot that is stoned and had no issues following these directions thanks! Stupid question.. the stuff it copied to my sdcard during rooting.. do i need to keep that for anything? or is it basically used as swap space?
Click to expand...
Click to collapse
I read somewhere you should keep it because someday we might be able to make a backup out of it. I deleted mine. I am able to use Odin to restore the original N910VVRU2BPA1 any time I want it.
Need help please noon
So I followed all the steps and achieved permanent root and Developer Edition everything worked great I went back into the T wrp recovery 2 wipe my cash and ended up wiping everything including operating system so someone told me to just install a custom rom I install custom ROM two different ones actually the new cm marshmallow and another one both of them do not recognize my SIM card I am using a Straight Talk SIM inside of a Verizon Note 4 I don't know what to do at this point can someone please help me thank you for the great unlock directions extremely user-friendly much appreciated.
Was curious... i cannot get TWRP to see my external SD.. anyone else have this issue? not a major thing just annoying...
And to the guy above.. i put on the CM13 rom and using a ting sim it works fine.. so not sure.. sorry.
doctor-cool said:
At some time we all have given Google permission to gather information. For that reason and because Kingroot is connected to a Chinese Server. I would prefer not having my information on the phone when rooting with Kingroot.
I would call Kingrooting with your personal accounts on the phone HOT ROOTING. If I were going to HOT ROOT I would remove all my personal accounts from the phone. I have done it and it will work but I prefer to do a factory restore.
Click to expand...
Click to collapse
I would also format, not just wipe your data partition when you flash your first ROM as well.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Icetech3 said:
Was curious... i cannot get TWRP to see my external SD.. anyone else have this issue? not a major thing just annoying...
And to the guy above.. i put on the CM13 rom and using a ting sim it works fine.. so not sure.. sorry.
Click to expand...
Click to collapse
You're not the first here to have problems with sd cards in TWRP. There are several threads here on how to fix that.
douger1957 said:
I would also format, not just wipe your data partition when you flash your first ROM as well.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
You're not the first here to have problems with sd cards in TWRP. There are several threads here on how to fix that.
Click to expand...
Click to collapse
Ah thanks.. will do a search
Am considering trying this, my thanks to doctor-cool for providing the instructions. I had kinda given up on being able to root my Note 4, and am attempting to get up-to-date with what's going on at this point.
Out of interest, are there any methods for doing this on a Verizon Note 4 that can be accomplished without the use of KingRoot or is that a must have? I'd really like to finally get this done, but have to admit to some reluctance over the unknowns that have been discussed on XDA when it comes to KingRoot. Honestly, I'm not even fully convinced that wiping your phone in advance of using KR will definitely resolve all potential problems that may exist. Would like to find a solution that just bypasses it altogether.
mray99 said:
Am considering trying this, my thanks to doctor-cool for providing the instructions. I had kinda given up on being able to root my Note 4, and am attempting to get up-to-date with what's going on at this point.
Out of interest, are there any methods for doing this on a Verizon Note 4 that can be accomplished without the use of KingRoot or is that a must have? I'd really like to finally get this done, but have to admit to some reluctance over the unknowns that have been discussed on XDA when it comes to KingRoot. Honestly, I'm not even fully convinced that wiping your phone in advance of using KR will definitely resolve all potential problems that may exist. Would like to find a solution that just bypasses it altogether.
Click to expand...
Click to collapse
Unfortunately, no.
My suggestion would be to disable wi-fi and remove your sim card until you can format your data partition.
douger1957 said:
Unfortunately, no.
My suggestion would be to disable wi-fi and remove your sim card until you can format your data partition.
Click to expand...
Click to collapse
Thanks for your response. I'd thought about that or similar solutions. The problem is there's so many question marks around KingRoot -- I figure if you're thinking it out, one of those questions has to be, what if anything does it leave on your phone even after you've finished the sort of process described here and removed KR? I'd feel so much more comfortable were it a solution that comes from one of the guys that have been around here for a long while. It seems the Note 4 agita never fully ends.