Requirement :
Should haveWugfresh Nexus Root Toolkit installed on your computer [with all updates installed ( not necessary),Should wait for it to download necessary updates for your device ( If no net connection then also no prob just wait) ]
( To download nrt visit wugfresh site(can't post link soory) )
You should how to connect your device using nrt, else, follow these steps,
Navigate to about phone section, while you are in the About Phone section, click on the Build Number option seven times to enable Developer mode. Then,go back to settings menu scroll down to developer options, in the Developer mode options, enable USB debugging. A screen will pop up on your phone when the program attempts to make a connection. Make sure to allow it.
Installing drivers :If the program and computer aren't recognizing your device, you will have to install software drivers. In the Nexus Root Toolkit, click on the "Full Driver Installation Guide" button and follow steps one to four. This is the most difficult part of the process. Be sure to follow the steps exactly.
Should know how to boot into bootloader.( can't post a link on where to find out sorry)
How to find if your nexus is bricked:
You see a message "Boot failed...." on your device.
The device is not booting but is staying on boot animation screen for long time (>30 minnutes).
The device is bootlooping means the device is rebooting again and again upto boot animation.
And any other problem that might result in your device, not being able to boot.
What you should do:
Don't panic this error is 100% rectifiable.
if you happened to end up in "boot failed" message on your device after the computer you were using switched off halfway through the flashing process.Then you have to restart your computer and then boot your nexus into bootloader mode and connect it to your computer.
Open Nrt ( Nexus root toolkit)
You should select change in your model type and set "select the android build you are currently running to the version of android you were trying to flash if you were trying to flash some other ROM, then just leave this step.
Then select "soft-bricked or bootloop" or "device is on or normal" depending on your device's current state and press on "Flash stock + Unroot".
you will have to either download a factory image and browse to it when asked so by the software, or let the software download it for you.
( For obtaining factory image for your nexus and search for your device based on build number of your device... )
All the screen on your computer read and do as necessary (Most of the times it is "OK" button that you have to press)
The device should be back to normal after it reboots.
Else just let me know......!
This can be done without a toolkit, Flashing factory image with fastboot instead.
Toolkits cause many of the issues on here, learning to do it manually with fastboot can both avoid issues, and fix issues. And teach people valuable skills.... As adb/fastboot are essential tools, especially with a Nexus. ?
But thanks for the info. Contributions like this are always good. ?
Problems with "Boot Failed"
visnkmr said:
Requirement :
Should haveWugfresh Nexus Root Toolkit installed on your computer [with all updates installed ( not necessary),Should wait for it to download necessary updates for your device ( If no net connection then also no prob just wait) ]
( To download nrt visit wugfresh site(can't post link soory) )
You should how to connect your device using nrt, else, follow these steps,
Navigate to about phone section, while you are in the About Phone section, click on the Build Number option seven times to enable Developer mode. Then,go back to settings menu scroll down to developer options, in the Developer mode options, enable USB debugging. A screen will pop up on your phone when the program attempts to make a connection. Make sure to allow it.
Installing drivers :If the program and computer aren't recognizing your device, you will have to install software drivers. In the Nexus Root Toolkit, click on the "Full Driver Installation Guide" button and follow steps one to four. This is the most difficult part of the process. Be sure to follow the steps exactly.
Should know how to boot into bootloader.( can't post a link on where to find out sorry)
How to find if your nexus is bricked:
You see a message "Boot failed...." on your device.
The device is not booting but is staying on boot animation screen for long time (>30 minnutes).
The device is bootlooping means the device is rebooting again and again upto boot animation.
And any other problem that might result in your device, not being able to boot.
What you should do:
Don't panic this error is 100% rectifiable.
if you happened to end up in "boot failed" message on your device after the computer you were using switched off halfway through the flashing process.Then you have to restart your computer and then boot your nexus into bootloader mode and connect it to your computer.
Open Nrt ( Nexus root toolkit)
You should select change in your model type and set "select the android build you are currently running to the version of android you were trying to flash if you were trying to flash some other ROM, then just leave this step.
Then select "soft-bricked or bootloop" or "device is on or normal" depending on your device's current state and press on "Flash stock + Unroot".
you will have to either download a factory image and browse to it when asked so by the software, or let the software download it for you.
( For obtaining factory image for your nexus and search for your device based on build number of your device... )
All the screen on your computer read and do as necessary (Most of the times it is "OK" button that you have to press)
The device should be back to normal after it reboots.
Else just let me know......!
Click to expand...
Click to collapse
Well I had a different kind of problem.
My Nexus was running fine in 4.4.4 when I rooted it since it was out of warranty. It upgraded to Lollipop 5.0 without a problem and continued to function in rooted state.
It made several attempts at updating to 5.0.2 but always ended with "Failed" message. I figured unrooting the device might help with the OS upgrade. It did not and screwed up everything. I then Set it to Factory default and it went to wiped 5.0 state. Then disaster struck. I tried rooting it , unfortunately with older Chainfire which bricked the device and would not let me install 5.0. So I tried to force install 4.4.4 and then the device got bricked. I simply get the message "Boot Failed" I boot into fastboot mode and I get the basic display with green start in the upper right corner, large Android icon in the center of the screen and the standard fine text on the lower let side. Unfortunately Windows ( x64 - Ultimate) insists on recognising the device as "Unknown Device" and when I go into properties this is is what is states ...
"Windows has stopped this device because it has reported problems. (Code 43)"
Do you think I might have better luck if I tried this on a Win XP machine ? I have both, x86 and x64.
Now, can you please tell me how I can get around this problem ?
BTW I do remember olden days of Cassiopeia PDAs before the flash memory came on the stage. The original OS would be on a plugged in masked rom daughter board in the event of losing all battery power. You could always force it to load it and get to factory mode. I think it is high time Android device manufacturers reverted to this process. I believe it can live side by side with the current system at a very marginal higher cost but have a whole lot of satisfied and LOYAL customers. It would give the user ability to go to factory mode albeit without any OS updates/upgrades but a fully functional device.
Would very much appreciate your feedback.
Hello. I have a US Cellular Samsung Galaxy Note 3. A week ago, I agreed to a software update, but that update never finished. The phone boots, gets to a screen saying "Optimizing apps 'N' of 257", counts up to 12 or so, and then reboots and repeats the same process.
The phone is not rooted, and AFAIK, USB debugging is not enabled. I want to retrieve the data from the internal card, as there are 2 years of photos on it, and it was not backed up.
What I've tried:
A call to tech support informed me to perform a factory reset, which I declined, as I do not want to lose my data.
I took it to a Samsung kiosk, and the tech attempted to flash the update from his laptop. The newly-flashed update behaved the same as the OTA update.
I can connect to it successfully with Odin and Heimdall, but receive errors when I try to load a custom recovery image using either one (TWRP, as I couldn't find a USC-compatible version of ClockworkMod).
I tried ADB, but it only lists as a device if I select "Upgrade with ADB sideload" in the recovery console. Otherwise, it does not appear in ADB.
I'm currently downloading the previous firmware version from Sammobile, but I am concerned that installing this firmware will delete/format/overwrite/repartition/obliterate my photos within the data folder.
Any suggestions or help would be very welcome.
Update
Things are worse. After trying the Android Recovery tool from Androiddatarecovery.co, the phone is now nearly hardbricked. When the phone starts, it indicates that it is booting into the recovery menu, and "Set Warranty Bit: recovery", and then it immediate shuts off.
What actual Note 3 model is it ??
SM-N900R4
I have a Verizon Note 3 running Android 5.0, non-rooted (never had luck getting it rooted). As far as I know, the bootloader is locked. Here is all the information that I thought might be pertinent:
Model #: SM-N900V
Baseband version: N900VVRUEOF1
Android version: 5.0
Kernel version: 3.4.0
Build number: LRX21V.N900VVRUEOF1
Although I work in IT and am fairly comfortable with this sort of stuff, I have almost no experience when it comes to working with Android development / phones, etc.
The phone does not have a valid SIM card, nor do I have service for it. I use it just as a WiFi device and I don't care if it ever works for phone/SMS/MMS again. That being said, I would really like to be able to (a) root the phone and (b) load the Resurrection firmware that I've read about that would allow me to run Marshmallow.
Is there someone who is willing to take me "under their wing," so to speak, and take me through what I need to do, step by step, to make this happen. I've read several posts, but they all assume a prior level of knowledge that I just don't possess. I'm confident that I could do this if I have a clear list of instructions and and understanding of what steps I need to follow to do this. Thanks in advance to anyone who could give me a hand.
Same problem here. Would appreciate help
Alright,
*First thing you need to do is enable USB debugging:
How?
On your phone Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times. You'll get a short pop-up in the lower area of your display saying that you're now a developer. Then Go back (to the settings menu) and now access the Developer options menu, check ‘USB debugging’ and click OK on the prompt.
------------------------------------
(DONT plug your phone to your PC yet)
Download USB Drivers and Install.
------------------------------------
*2nd thing to do is Rooting your phone:
Download THIS tool on PC > Run. then plug your phone to PC > Choose Version OF1 > Click Read phone info (Your phone will ask if the program can access your phone press YES on your phone)> Root. wait until its done. now you are Rooted.
------------------------------------
Here is the fun part (Unlocking your bootloader) All through the phone no PC required for this.
You need to use an SDCard for this and
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD)) So backup your MicroSD or use another one.
* Install Busybox on your phone (you can get it from the Playstore)
* Download Samsung Unlocker N3
1. Install SamsungUnlockerN3.apk
2. Grant SU access
3. Click On Install SamBootloader Unlocker
4. Grant SU access
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD))
Thats all. your N3 is rooted and bootloader unlocked
Sczar said:
Alright,
*First thing you need to do is enable USB debugging:
How?
On your phone Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times. You'll get a short pop-up in the lower area of your display saying that you're now a developer. Then Go back (to the settings menu) and now access the Developer options menu, check ‘USB debugging’ and click OK on the prompt.
------------------------------------
(DONT plug your phone to your PC yet)
Download USB Drivers and Install.
------------------------------------
*2nd thing to do is Rooting your phone:
Download THIS tool on PC > Run. then plug your phone to PC > Choose Version OF1 > Click Read phone info (Your phone will ask if the program can access your phone press YES on your phone)> Root. wait until its done. now you are Rooted.
------------------------------------
Here is the fun part (Unlocking your bootloader) All through the phone no PC required for this.
You need to use an SDCard for this and
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD)) So backup your MicroSD or use another one.
* Install Busybox on your phone (you can get it from the Playstore)
* Download Samsung Unlocker N3
1. Install SamsungUnlockerN3.apk
2. Grant SU access
3. Click On Install SamBootloader Unlocker
4. Grant SU access
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD))
Thats all. your N3 is rooted and bootloader unlocked
Click to expand...
Click to collapse
I tried this root method and all it does is put me in a boot loop.Goes to somethingiin recovery and just stays there until I manually reboot phone then get boot loop.Tried both 1 click versions.
Sent from my LG-D851 using XDA-Developers Legacy app
AtrixHDMan said:
I tried this root method and all it does is put me in a boot loop.Goes to somethingiin recovery and just stays there until I manually reboot phone then get boot loop.Tried both 1 click versions.
Click to expand...
Click to collapse
Try to do a factory reset in recovery mode. It will wipe all your apps and data and restore it to factory settings. The instructions you got from @Sczar are very good , so try again step by step if factor reset doesn't work to get you out of the boot loop.
S2_brickmaker said:
Try to do a factory reset in recovery mode. It will wipe all your apps and data and restore it to factory settings. The instructions you got from @Sczar are very good , so try again step by step if factor reset doesn't work to get you out of the boot loop.
Click to expand...
Click to collapse
I got it figured out.Had to use a different twrp and flash Samsung lollipop 01.
Sent from my LG-D851 using XDA-Developers Legacy app
Very new to this. Have a technical background but confused on the above steps. Completed all listed Note3 connected,odin started on phone, then progress stopped at 28 sec. Waited over an hour then crossed fingers and unplugged phone removed battery and restarted. Luckily it came back up. Any ideas on went wrong with root process? Help!!
Thanks in advance.
Sczar said:
Alright,
*First thing you need to do is enable USB debugging:
How?
On your phone Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times. You'll get a short pop-up in the lower area of your display saying that you're now a developer. Then Go back (to the settings menu) and now access the Developer options menu, check ‘USB debugging’ and click OK on the prompt.
------------------------------------
(DONT plug your phone to your PC yet)
Download and Install.
------------------------------------
*2nd thing to do is Rooting your phone:
Download tool on PC > Run. then plug your phone to PC > Choose Version OF1 > Click Read phone info (Your phone will ask if the program can access your phone press YES on your phone)> Root. wait until its done. now you are Rooted.
------------------------------------
Here is the fun part (Unlocking your bootloader) All through the phone no PC required for this.
You need to use an SDCard for this and
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD)) So backup your MicroSD or use another one.
* Install Busybox on your phone (you can get it from the Playstore)
* Download
1. Install SamsungUnlockerN3.apk
2. Grant SU access
3. Click On Install SamBootloader Unlocker
4. Grant SU access
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD))
Thats all. your N3 is rooted and bootloader unlocked
Click to expand...
Click to collapse
OK, made it to rooted. It came back up the first time while connected to the computer. I shut down to swap sd cards to put in an older one that isnt used and when I start back up all I get is Process System isnt responding in a white box. If I do nothing, the white square asking to quit or wait will disappear, I get the top bar with 4G, bars, battery level, and time, but black screen. If I swipe the screen with my finger, the desktop (for lack of better word) flashes on, then goes all black. In about 3-5 minutes it will restart again. Before it restarts on its own, I can hold the power button and it will give me the power off, restart, etc menu and allow restart.
EDIT: Nevermind... If it warns Process System is not responding, wait for the notification bar to appear, use the power button to get the restart menu and choose restart. Then it starts normally and is Rooted! THANK YOU! I will work on the rest tomorrow!
Oldguy64 said:
Very new to this. Have a technical background but confused on the above steps. Completed all listed Note3 connected,odin started on phone, then progress stopped at 28 sec. Waited over an hour then crossed fingers and unplugged phone removed battery and restarted. Luckily it came back up. Any ideas on went wrong with root process? Help!!
Thanks in advance.
Click to expand...
Click to collapse
Why are you using Odin?
Sczar said:
Why are you using Odin?
Click to expand...
Click to collapse
It just started, I assume, as a result of running the root program. I downloaded program from the suggested link. I ran it which installed files on my pc and made a desktop shortcut. I double-clicked the shortcut, the program started, I connected the phone via usb, and selected the scan button in the program. It found the phone and I selected install root. I then had a progress bar start in the program and a window opened on the task showing odin 3.10. The phone indicated that odin had started and said it was downloading, however, progress stopped at 28 seconds. Did I do something wrong? I would really like to get this thing rooted so I have control over it.
Thanks immensely for your help.
Oldguy64 said:
It just started, I assume, as a result of running the root program. I downloaded program from the suggested link. I ran it which installed files on my pc and made a desktop shortcut. I double-clicked the shortcut, the program started, I connected the phone via usb, and selected the scan button in the program. It found the phone and I selected install root. I then had a progress bar start in the program and a window opened on the task showing odin 3.10. The phone indicated that odin had started and said it was downloading, however, progress stopped at 28 seconds. Did I do something wrong? I would really like to get this thing rooted so I have control over it.
Thanks immensely for your help.
Click to expand...
Click to collapse
Are you on OF1 baseband and Build?
Sczar said:
Are you on OF1 baseband and Build?
Click to expand...
Click to collapse
Yes on both accounts. Because I had no intent to flash a new ROM and only wanted to root I did not have an SD card in the phone. Could this be affecting the process?
Oldguy64 said:
Yes on both accounts. Because I had no intent to flash a new ROM and only wanted to root I did not have an SD card in the phone. Could this be affecting the process?
Click to expand...
Click to collapse
If you just want to root your phone you only need to run the root program on your pc. You DO NOT use odin. If I'm reading your post correctly you are saying the odin program is starting automatically? That should not happen. SD card should not matter if you just root.
Yes it is starting automatically. Any ideas why. Going to search registry on computer to see if it might be on there. Does Samsung Kies use Odin in any manner. I do have Kies on the computer. Grasping at straws I know. Thanks for the help you folks are great.
Oldguy64 said:
Yes it is starting automatically. Any ideas why. Going to search registry on computer to see if it might be on there. Does Samsung Kies use Odin in any manner. I do have Kies on the computer. Grasping at straws I know. Thanks for the help you folks are great.
Click to expand...
Click to collapse
I have no idea why odin would start on its own. If you would like to, uninstall Odin so you can root your phone without any interference from Odin. Samsung Kies DOES NOT use Odin. Samsung Kies is its own separate program from Odin.
If all you want to do is root the phone follow Sczar post and run the root program again it should only take about 1 minute tops to root phone.
Tried one more time. Stopped in exactly the same place as multiple times before. As far as Odin goes; after downloading the root file and running it, it extracted a number of files and created a directory in my program files directory on my pc. One of the files extracted was Odin.exe. Also the program does not automatically detect my phone or ask me to select OF1. I have to select a scan button and it then populates the fields showing the build. I select install root and all goes good,like I have mentioned until 26 or 27 seconds of progress has occurred the the program stops. My phone shows Odin has started and says it is downloading not to turn off, but nothing ever writes to the phone. I have to get into the task manager on the pc to stop the processes dealing with the root program as it becomes totally unresponsive. I have to kill adb also. I am totally baffled and about ready to give up. Wish I had stayed with Motorola at least that phone I was able to root. I have been holding off the new software update for days but may just let it fly unless someone has any other ideas about why this thing stops. Thanks to those who have tried so far.
Oldguy64 said:
Tried one more time. Stopped in exactly the same place as multiple times before. As far as Odin goes; after downloading the root file and running it, it extracted a number of files and created a directory in my program files directory on my pc. One of the files extracted was Odin.exe. Also the program does not automatically detect my phone or ask me to select OF1. I have to select a scan button and it then populates the fields showing the build. I select install root and all goes good,like I have mentioned until 26 or 27 seconds of progress has occurred the the program stops. My phone shows Odin has started and says it is downloading not to turn off, but nothing ever writes to the phone. I have to get into the task manager on the pc to stop the processes dealing with the root program as it becomes totally unresponsive. I have to kill adb also. I am totally baffled and about ready to give up. Wish I had stayed with Motorola at least that phone I was able to root. I have been holding off the new software update for days but may just let it fly unless someone has any other ideas about why this thing stops. Thanks to those who have tried so far.
Click to expand...
Click to collapse
I'm starting to figure out what you are saying is going on (I think).
1. Forget about Odin you do not use it, at all for root.
2. If I'm right your "phone" is going into DOWNLOAD MODE automatically that is what it should do.That is not Odin running. That's how your phone programs itself.
Quick checks
1.Make sure you have latest drivers from Samsung installed.
2. check USB debugging is on.
3. Install Arabic Tool For rooting on PC.
http://www.mediafire.com/?pvm1reerboz2c25
4. Open Arabic tool,
5. plug phone into PC make sure you connect as MTP not installer mode.
6. Click on Version, select OF1 (make sure your firmware is running on OF1)
7. Click Read Phone Info. (Your phone info should fill in the blanks)
8. HIT ROOT.
Your phone should go into "Download Mode" not Odin (a little green dude should be on the screen) automatically. Let the program do its thing. Then it will reboot your phone automatically, and if everything goes correctly it should say your rooted!.
9. It should take about 1 or 2 minutes to complete.
10. If it doesn't work try it again. It took me 2 tries for it to work right.
Everytime I've tried rooting my SM N900V with this Yemen tool I get hard bricked. To fix that issue I just put phone in odin mode and flash the OF1 firmware and everything is back to normal but still no root. Any suggestions?
mdj8606 said:
Everytime I've tried rooting my SM N900V with this Yemen tool I get hard bricked. To fix that issue I just put phone in odin mode and flash the OF1 firmware and everything is back to normal but still no root. Any suggestions?
Click to expand...
Click to collapse
Try the Arabic tool I posted above ^^^. I rooted my phone 3 times with no problems. I've not used the Yemen root method.
I made it to root, but the bootloader is not replacing so I am evidently missing an obvious step.
Samsung Note 3 SM-N900V 0F1 firmware
1. Install SamsungUnlockerN3.apk
2. Grant SU access (How do I do this? It is not asking anything)
3. Click On Install SamBootloader Unlocker
4. Grant SU access (Again, how do I do this? It is not asking anything)
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
It says it works, it shuts down and I remove the battery, and I reboot. However, as soon as I install TWRP and allow it to reboot I get the unauthorized software message from Verizon, use Kies to save, use Odin to reflash 0F1, root again, and now what? Why is the actual bootloader not being installed? How do I enable superuser?
I realize there are many other threads on this, bear with me please, I was not able to find a solution that works.
-display is broken, shows light but nothing else
-digitizer is 99%? broken, back and menu buttons work, there is some heptic feedback in upper part of the screen
-phone does not have a lock pattern or password, just swipe to unlock
-voice commands work
-phone was rooted a long time ago, I don't recall the mehod, I think the current OS is likely 4.4 but i'm not sure (is there a way to check)?
-I had a custom recovery on it which i think was CWM, again, not sure how to check this now
-I can install apps via web appstore
-At some point I installed a clockroot app (never worked) it's probably still on the phone
-I don't have OTG, ordered one
-I don't want to order a new digitizer
Here are somethings that kind of work and some that don't
-dr.fone shows a USB debug promt with instructions on how to accept the RSA key. I'm guessing USB debugging mode is on but it's not the same computer
-if I have the device in download mode, it is "sometimes" recognized by dr.fone, just says its in download mode and asks to reboot
-if I have the device in recovery mode (i think), it's not recognized at all, does not even show up in device manager
-when phone is just on, it's recognized by the computer, I can browse and backup files (i need to backup google auth app)
-with phone on, its recognized by windows and adb, adb says the device is not authorized.
-however adb does not recognize it if I boot into recovery
I think my best best to just to push the rsa key to the phone in recovery but I'm stuck because the phone is not recognized. I will try re-installing drivers next but I doubt this will help.
Lastly, I wasn't sure if I really do have CWM installed or its stock recovery. So I tried to flash CWM using Odin, with phone in download mode, recognized by Odin, the flash fails with an auth error, i'm reading that might mean the phone is not rooted which is 100% not the case here, maybe the rootclock app is doing something to it.
Any advice?
I'm starting to recall the rooting process a bit and I'm fairly sure I used safestrap method, as I was on 4.4.2-4 NJ something kitcat at the time. So I may not have CWM installed after all.
little bit of progress to report. I'm fairly certain i have safestrap recovery on this phone. So booting into recovery must have been bringing me to the safestrap screen that needs a screen tap to recovery or continue. If I hit power it reboots, if its only 2 options recovery or continue to normal boot, volume down move me to the other option, + power....now adb detects the phone! in sideload mode, lets see if I can do something with this, fingers crossed.
no luck, sideloading seems useless. How can i get myself into recovery!?
I think if I can push the adb rsa key I would be set to use one of the screen mirroring apps. How can I sideload it in?