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?
Related
Ok, so I know this will eventually get buried in the forums but I thought I would attempt to give a little basic info here. Right now the QA section is flooded with people that have flashed and are now soft bricked (have problems but can recover) or hard bricked (have problems and cannot recover). I'm hoping that I can help some people prevent these issues to an extent.
Terminology, the differences in my opinion.
Soft brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your hardware buttons work or ADB works and you are able to boot into DOWNLOAD mode.
Hard brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your unlucky and hardware buttons do not allow access to DOWNLOAD mode or ADB is not downloading.
Also, after a new flash or flash to stock, it's a good idea to immediately enable USB debugging. Menu, Settings, Applications, Developement, check the box for USB debugging. It will make things easier later on.
1. First. BEFORE you flash, can you access download mode with your buttons??? Test it.
3 Methods.
Method 1: (ADB - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold Volume Up + Volume Down + Power
Method 3: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons (from i9000 just down, don't touch the power button)
Plug in the USB cable and continue holding both Volume buttons
If not, use designgears fix. http://forum.xda-developers.com/showthread.php?t=812434
2. Second. Download the SDK, drivers for your PC, and learn some basic ADB commands, ie, adb reboot download, adb reboot recovery, adb shell. Here's my quick guide. ADB can be used when the OS is running, when in recovery, and when stuck on ATT boot screen.
Here's what I do. After you download the sdk and unzip. There is a folder called tools. I copy that to c:
Then open a command prompt and type,
C:
CD tools
Then issue adb commands.
adb reboot, adb reboot download or whatever command you need.
Of course make sure your phone is connected via USB and debugging is enabled.
Here's another method for using adb.
1) start-> run-> sysdm.cpl
this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.
2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.
http://wtfokc.com/sef****/sysdm-1.gif
3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:
http://wtfokc.com/sef****/sysdm-2.gif
4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.
http://wtfokc.com/sef****/sysdm-3.gif
5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.
3. Third. Install Clockwork Recovery! Root your phone and download ROM Manager from market. Install Clockwork recovery from ROM Manager. BOOT into recovery to make sure it works. You will have to choose reinstall packages from stock recovery. What ROM Manager does, it put an update.zip on the root of your SDcard, then when you choose reinstall packages from stock recovery it install update.zip. I personally leave the update.zip file on my sdcard at all times, just in case.
Once you have clockwork installed, make a Nandroid backup of a good running rom. In case something happens, if you can boot into recovery, then you can possibly restore your nandroid to at least get you up and running quickly, and without the need of a pc.
NEW Info!!! You can recover from a hard brick, maybe. Here's how to create a USB Jig to reproduce the button download mode for you folks who don't have it.
http://forum.xda-developers.com/showthread.php?t=841512
Here's another thread about the USB Jig method.
http://forum.xda-developers.com/showthread.php?t=819551&highlight=USB+jig
If my captivate was one that had the missing button recovery/download out of the box, I would probably know how to make a USB jig or have one already before flashing. Even with the 3 button fixes that are out, it looks like some people are still bricking.
****Disclaimer****
This is just from personal exprience. I have flashed most roms available, and I have experienced every variation of soft brick mentioned above and have recovered.
I find that being able to get your phone into download mode and knowing how to use Odin will be your 2 biggest life savers after something bad happens.
This will not keep you from getting a bad flash or something else, but having this knowledge ahead of time may help you recover from issues more quickly and without asking a question on the forums that have been asked dozens of times.
Also, personally, if I cannot perform step 1, access download mode with buttons, I personally would be VERY cautious about flashing! ADB reboot download is nice, but if you are stuck at ATT logo or phone--!--PC mode then ADB doesn't work, YOU HAVE TO USE BUTTONS.
Just my 2 cents, take it or leave it.
Edit. Added some new info to post. Thanks for extra info guys. I'll mirror the links to the images later when not at work.
+sticky
excellent write up. a must-read for anyone even thinking about flashing
Original Post updated to add my information
bobbylx said:
ADB reboot download is nice, but if you are stuck at ATT logo
Click to expand...
Click to collapse
Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.
If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.
Steps
1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.
2: When the att screen comes on your pc should make a notification sound that the device is connected.
3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.
Mileage may vary but should work.
This has saved me a few times.
STICKY
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.
Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.
I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.
bulletproof1013 said:
STICKY
Click to expand...
Click to collapse
+1
This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.
Sent from my SAMSUNG-SGH-I897 using XDA App
This thing is getting buried in the BS posts....BACK TO THE TOP!
definitely sticky
Bump Bump Bump
Great Info
Updated original post with extra info.
Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.
Thanks, great info.
FWIW........
I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.
One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.
Thanks for the post, my vote for sticky as well.
+1 sticky
Sent from my SAMSUNG-SGH-I897 using XDA App
Moving this to the top. More questions in QA that can be helped by reading these tips first.
I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.
The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.
Test md5 checksums on the source and this file and make sure these match.
(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).
This will ensure your USB connection is stable enough for long, error free transfers to the phone.
Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.
Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.
Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply Thank you!
thanks for the reminder
there's so many steps to install a rom...
specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!
another good reason flashing stock with odin before flashing new rom
I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.
hi guys.. could you help me with my problem.!
I have an LG GT540 android 1.6 firmware version(stock)
So here are my problems:
1. I tried to upgrade it from 1.6 to 2.1 using this tutorial http://forum.xda-developers.com/show...27&postcount=3 thanks to lavero.burgos for posting it, I was successful at first part, but I cant follow the next because my device wont go to fast boot,, I tried putting it off, then camera+poweron but it doesnt do anything. It doesn't light, no lg logo appears, just nothing although the computer can read the drive when I connect it through usb. So I cannot flash it to 2.3,2.3 because it just wont go to fastboot.
2. When I turn it on normally, It takes long before it response like after 30sec to light, but just light, no lg logo appears although it wasnt bricked because I can use it normally after just waiting to on.(annoying)
3. Since I upgraded it to 2.1, I lost all 3rd party application and the internal apps were the only left, so I copied all my saved apps (.apk) to my sd card but the problem is there is no saved app on my phone to read and install those apps from my sd card.(irritating)
4. My device wont read my sim card, when I start it it says "sim card unprovisioned" so basically I cant connect to mobile networks here in the philippines(im using globe telecom). I feel that Im stucked in the middle of nowhere since I cannot contact and txt all my family and friends.
5. I cant connect to wifi,, when my device detects wi-fi, I try to connect to it but from the log it only try to connect but doesn't obtain the ip address. Even when the wi-fi signal is strong, it does the same thing.
So please help me guys,,I want to hear from my fellow xda-developers badly,,,
PS. also those who have problems with their LG GT540 pls feel free to post and share it with us here... thank you all guys in advance....
hi so let me get it right the phone is working (can turn on and use but cant call) yes? hmmmmm..... try this
MUST DOWNLOAD THIS DRIVERS!!!!
http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Step one!
1.turn off phone.
2.hold the POWER button till you feel the beep.
3.let go of the POWER button when you feel the beep and hold onto the CAMERA button only.
4.hopefully it turns on to a blackscreen and nothing else(fastboot)
5.unzip this CLICK ME!! to desktop and open the flash all no wipe file
or......
1.turn on your phone.
2.go to settings>applications>development>tick the usb debugging
3.connect phone to computer (make sure phone is on)
4.unzip this CLICK ME!! to desktop and open the flash all no wipe file
5. phone should boot into blackscreen like the one above......
Click to expand...
Click to collapse
Step 2!
both should flash a recovery image. Next
1.make sure the phone is off
2.press POWER button
3.when you feel the beep let go of POWER button and press the HOME button only.
4.phone should boot into recovery mode.
5.take out battery again
6. download a rom into the sdcard using computer
7.go to recovery again using the steps above (steps 1 to 4)
8.select wipe all data factory reset or something like that....
9.install zip from sdcard
10.select from sdcard
11.choose the file you downloaded
12.finish flash and reboot phone.
Click to expand...
Click to collapse
excellent guide! big thanx
bs828 said:
hi so let me get it right the phone is working (can turn on and use but cant call) yes? hmmmmm..... try this
MUST DOWNLOAD THIS DRIVERS!!!!
http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Click to expand...
Click to collapse
Thanks,, Ive tried the 2nd option on step one and i think my phone successfully got to fastboot(just clean blank screen) so the cmd automatically run and states
C:\Desktop\adb rebootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: protocol fault <no status>
C:\Desktop\fastboot flash recovery recovery.img
< waiting for device >
Did I miss something???
ok try again this time with the phone turned on. and then run the script and did you install the drivers?
bs828 said:
ok try again this time with the phone turned on. and then run the script and did you install the drivers?
Click to expand...
Click to collapse
yeah I installed the drivers...
hmmm maybe there are no fastboot drivers(main suspect....) there are a few ways to get it but for mine i just plug my phone in to my pc (windows 7 64bit) it just recognize it and tries to get the "google fastboot interface" drivers from windows update...
Try Volume Up+Search Key+Power to go into Fast boot Mode, There's different keys to activate Fastboot Mode (There is different versions of Fastboot)
Sent from my LG GT540 CM9 PreRC Polish Blood using xda premium
Your phone is/was bricked
Hey, I'm sorry to bing back such an old thread, but I just wanted to say this for posterity: your phone has/had a soft-brick. This means: you can't see Android nor LG boot logos, can't enter Recovery and (maybe) can't access Fastboot, but I'm not too sure on that last one. Besides that, the phone works "okay", but you should try to fix it.
Basically this soft-brick is almost always caught when upgrading from 1.6 to 2.1, so everyone should have it, including me. It took me a whole year to realize how to friggin' fix it lol, but here goes what I did:
Thanks for your help everyone, I came to a solution after a full year lol. Here's my enlightenment, from another Thread:
------------------------------------------------------------------------------------------
Just wanted to leave my 2 cents here, I've been trying to do my best since around august 2014, no success. 2 days ago I retried this, and I DID IT! I will tell everyone what I did very shortly:
My problem that I solved: I can boot, device works like a charm. But: no boot logos, no recovery.
My solution for TL;DR: UNINSTALL ALL DRIVERS FROM DEVICE MANAGER 1ST, then reinstall. After that, flash a fastboot ROM and use it to WIPE ALL THE DATA IN YOUR PHONE! THIS was what I needed and was never explained: you had to WIPE the old data in order to get the boot screens back.
IN THIS ORDER (THANK YOU to those people from previous replies, gathering all your info was of great value):
Uninstall all of your phone drivers from your PC!!! This is what made most of my headaches go away, just use Device Manager and uninstall anything from LGE. After that, plug in your device in your USB ports (always BACK ports, not front ports, important). It should detect all drivers and download them.
IF it fails (it generally does with LGE USB Modem), you can go to Device Manager > Unknown Device (the one that wasn't recognized) > Right Click and Update > Choose 2nd option, then choose "choose from a list of local controllers" (or whatever the button says). After that, scroll down to LG Electronics, Inc. and install what didn't install.
I also found these drivers, but I did not test them: http://www.mediafire.com/download/p693hcz6kkouh19/USB_Driver_LG_GT540.zip
Huzzah!
Now you're set to begin:
FIRST thing you wanna do is a factory reset, this is something I'd forgotten with time, don't make the same mistake as I did. You can do it by turning your phone on and pressing Volume +/- & Home & Quick Search buttons all together for 5 seconds (it works, be patient and wait for it, even if you open the camera or any other stuff).
Download this Google SDK Tools (unzip and put the folder in C:\ drive) and this Fastboot drivers for GT540 (unzip and put the files inside the folder in C:\android-sdk).
Skip this next line if you know your ROM has fastboot.
Now, if you don't have a ROM with fastboot, I recommend you use either European Open+Fastboot or V20C Orange France Fastboot ROM.
Click to expand...
Click to collapse
Since you have Fastboot enabled, now all you need to do is turn off your device (all this with its battery on it, no weird things) and hold the Camera button before turning it back on. This should take you either to a black screen, or simply to no display, like me. Either one will work anyways.
Now press the Windows key > Type cmd and open it with Right Click > Run as Administrator.
In it, type all this, command by command (you can paste by right clicking):
cd C:\android-sdk
fastboot -w
fastboot erase boot
fastboot erase system
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
And now it's go time! Do what everyone else says in here: Take out your phone's battery, SD and SIM cards, fire KDZ Updater up as Administrator (If your KDZ freezes, then it's either faulty or you did not install msxml, look for a good KDZ that comes with that file and delete your current one), choose CS_Emergency PhoneMode and:
1-Plug your phone while holding the volume DOWN button (don't worry! My phone didn't show "Download Mode" either, if you hear the Windows "Somethingpluggedin" Bump noise, it's ok).
2-Flash French V20A
3-Unplug your phone once KDZ says "==FINISHED==".
4-Plug it once again, holding the volume DOWN button.
5-Flash out.kdz (remember! it's CS_Emergency).
Click to expand...
Click to collapse
THANK YOU XDA!
--------------------------------------------------------------------------------------
Also, if you look in here you'll find how to flash an awesome ROM, Cyanogen Mod 10 (should say "Final Version#2).
I have spent Hours on this site looking for help with my phone...
I have down loaded app after app. reset factory setting. hard reset the phone. but the fact is my phone will not Root. I am with sask-tel. this all started with me wanting to unlock the phone.
What the phone will do:
down load apps
hook up to wifi
hard factory resets(up and down /power button)
usb debug
but thats it. if I try run a root program it does nothing. if I try to open the tech aids(down and power) nothing happens it says downloading for hours.
I have manually looked for the efs file and SU start commands are not reponding(jack's program for got the name).
Model number
GT-i9000m
firmware 2.3.3
baseband version I9000Ugkg3
kernel version
2.6.35.7-19000ugkg3
[email protected]#2
build number
gingerbread.gkg3
Mobile network type
Umts
yeah soo... please help sorry the post was so long I have no idea what I am doing...lol
Have you checked this thread??
http://forum.xda-developers.com/showthread.php?t=939752
Gti9
UMMM..
gcuchiha said:
Have you checked this thread??
http://forum.xda-developers.com/showthread.php?t=939752
Gti9
Click to expand...
Click to collapse
I did look at but it still does not help me as I am trying to refresh all the software in the phone because some one delete vital file Samung told me the carrier did it and they are the only ones who can fix it. I am really startiung to dislike Sasktel
but I really cant afford to by a new phone that 22 percent, or more, of my monthly income.
keepitsimpleplease said:
but the fact is my phone will not Root. I am with sask-tel. this all started with me wanting to unlock the phone.
Click to expand...
Click to collapse
Flash this rooting kernel using odin and install superuser and busybox from the market
keepitsimpleplease said:
if I try to open the tech aids(down and power) nothing happens it says downloading for hours.
Click to expand...
Click to collapse
If you are trying to get into recovery, it's volume up, power and the home button.
Volume down, power and the home button gives you download mode, so it's normal for it to say "downloading" for hours.
try the file xsenman posted. Put your phone in download mode, open Odin, choose the file under PDA, plug in your phone
(make sure you have the Samsung USB drivers installed) and that the ID:COM box is lit, then flash.
Once it is finished, download Busybox and Superuser from Google Play and you are rooted.
By the way, KG3 is a very difficult ROM to get a rooted kernel for.
Ian
I'll try that....
Thhank you very much... I do hope that it works. I am taking a couple days break from it all. spend 9 hrs yesterday trying to simply diagnose, and for some one whom knows nothing about system programs, or tech access points for the phone I think I have done well for a newbie.
So far all I have been able to do is fix every lag in the phone. lol. thank you for the File link and for the walk through
Quick questions
w98seeng said:
If you are trying to get into recovery, it's volume up, power and the home button.
Volume down, power and the home button gives you download mode, so it's normal for it to say "downloading" for hours.
try the file xsenman posted. Put your phone in download mode, open Odin, choose the file under PDA, plug in your phone
(make sure you have the Samsung USB drivers installed) and that the ID:COM box is lit, then flash.
Once it is finished, download Busybox and Superuser from Google Play and you are rooted.
By the way, KG3 is a very difficult ROM to get a rooted kernel for.
Ian
Click to expand...
Click to collapse
Ian,
How do I insure my "Samsung USB drivers" are installed?
Can you please further explain what you mean by "ID:com box is lit"
Thank you
Re
Samsung drivers are installed together with Samsung Kies. If you already have Kies installed on your computer and it connected successfully at least once before then you have the right drivers.
Now, when flashing anything onto your phone the Kies application must not be running. Make sure you stop it (e.g: by stopping any Kies service from Windows Services).
"ID:COM box is lit" means one of the upper boxes in Odin turns green.
The steps are:
1. Start Odin on your computer and select the PDA and CSC files (you should find more details about what files to flash in other posts)
2. Start your phone in Download mode : Vol. Down + Home + Power until you see Downloadin
3. Connect the USB cable to your phone.
If none of the boxes turn green in Odin you should try different USB ports on your computer. One of them will eventually work.
The point of this thread is to help people safely update their bootloader so that they may flash a touchwiz kitkat rom.
I have seen several threads where people are running into issues and even development threads get cluttered with questions. So I will give you the steps needed using my method.
Please note this is for windows 7. However it should work on other versions of windows too.
This method may wipe your internal storage completely so transfer anything you do not wish to lose to you pc.
This method will also trip yout knox counter which may void your warranty.
You also may not be able to downgrade to 4.3 so make sure this is what you want to do
I am not responsible for bricked devices. Proceed at own risk
You have been warned!!!
So what you need to do is download a few files.
I have created a zip file and uploaded it for easy access and simplicity reasons. If it becomes out dated I will update accordingly.
What is needed is your variants stock firmware. You need to get the one for your device off sammobile.com
On sammobile you must create an account in order to download (if you don't have an account already).
Once you are logged in click on the firmware tab. Then enter your device name.
Canadian variants enter: SM-N900W8
TMO variants enter: SM-N900T
You will then be able to pick the most recent firmware for your device and download it. So now that you have the correct firmware (please double check, and if unsure google it)!!!
So lets begin
You also need to download the zip file I have made and extract it. Inside it you will find the samsung drivers, 3 recovery options to pick from, the supersu.zip and also odin.zip. once you've extracted the file you've just downloaded you need to extract the odin.zip inside it as well.
So if you have not previously installed the samsung drivers you will need to do so. Simply run the samsung mobile driver.exe file and install it. Once successful in installing, reboot your pc.
when it boots up, connect yout device to you pc and transfer over the supersu.zip over to your phone. The root of your sd card is recommended for easy access.
Now what you need to do is ensure usb debugging is enabled. Do so by going to settings, general, developer options and ensure its checked. If you do not have developer options simply go to about phone, and tap om build number 7 times to enable developer options.
Once this is done you need to power off your device with it unplugged. Now we need to enter download mode. You can do this by holding the home button, volume down and pushing and hokding the power button. You will be presented with a warning screen. You push volume up to proceed or vokume down to cancel and restart device.
We want to push volume up. It will then show a big android saying warning do not turn off target.
Now connect your device to your pc and run odin as administrator.
In odin near the top left you shoukd see a box colored in saying:
Com and have a number. If you see this that means odin recognizes your device. If you do not that means eiter you dont have the drivers installed properly or perhaps you need to try a different usb port or cord.
You then will see a few check boxes checked off. Auto reboot and f.reset time. leave these checked only.
Theres an AP BUTTON. Click this button and then navigate to your stock firmware file you've downloaded and select it. It may take a few minutes to load it. Once it does load all you need to do is click the start button and let odin do the rest. Do not touch anything.
This will take a few minutes. You should see a green "pass" in the box at the top left. Your device will eventually reboot and you will now be stock, unrooted on the latest firmware.
*please note that if at this point your device hangs on the Samsung logo sayong "recovery booting" you need to pull the battery and reflash the firmware. This time also check the repartition box.
Now we need to root and flash a custom recovery.
Again you'll need to enable usb debugging on your phone so I recommend skipping the google setup stuff on your phone.
Once you have enabled it, power off your phone with it unplugged and again enter download mode the same way you did before.
Plug in your device and in odin press the reset button to clear the stock firmware file.
Now connect your device to your pc and again ensure that odin recognizes it.
Click the AP BUTTON again and this time navigate to the custom recovery of choice ( I reccomend twrp. I am also using the tmo version as I could not get the canadian version to boot)
Once selected again hit the start button. In a few seconds you should again receive a "PASS" message. That mrans you have successfully flashed a custom recovery.
Now power off your device and unplug it. Now we need to enter recovery.
Do so by pressing the home button, volume up, and push and hold the power button. Once you see recovery booting you can let go. You will also see in red font: recovery is not seandroid enforcing. That just means you have a custom recovery.
If your device hangs at this screen you will need to oower it off and try a different recovery.
Once in recovery I reccomend making a nandroid backup. (Optional)
Next we are going to root. All that you need to do is press install or install zip from sd card depending on which recovery you chose and navigate to the supersu.zip
Now install the zip by following the instructions of the recovery and then reboot.
Congratulations you are now rooted (you can confirm if you like by downloading the root checker app if you wish) and on the latest firmware and can flash custom 4.4.2 roms for your device. Please read and follow the directions of the op in the thread of the rom you wish to flash.
Download link: http://d-h.st/4xl
sent from my JEDI ELITE Note 3
for best xda results, click to enlarge ?
http://img268.imageshack.us/img268/9564/searchitnoob.gif
phone stuck on recoveryboot a
Theres an AP BUTTON. Click this button and then navigate to your stock firmware file you've downloaded and select it. It may take a few minutes to load it. Once it does load all you need to do is click the start button and let odin do the rest. Do not touch anything.
This will take a few minutes. You should see a green "pass" in the box at the top left. Your device will eventually reboot and you will now be stock, unrooted on the latest firmware.
= at this part of the instruction odin has said pass but my phone just has samsung logo and says on top recovery boot... and nothing else i dont know how to continue or move forward i hope someone can help me thank you and sorry for troubling you
nymomo789 said:
Theres an AP BUTTON. Click this button and then navigate to your stock firmware file you've downloaded and select it. It may take a few minutes to load it. Once it does load all you need to do is click the start button and let odin do the rest. Do not touch anything.
This will take a few minutes. You should see a green "pass" in the box at the top left. Your device will eventually reboot and you will now be stock, unrooted on the latest firmware.
= at this part of the instruction odin has said pass but my phone just has samsung logo and says on top recovery boot... and nothing else i dont know how to continue or move forward i hope someone can help me thank you and sorry for troubling you
Click to expand...
Click to collapse
I replied to your pm you sent me. Anyway just flash a different recovery if it's hanging after flashing recovery. If its hanging after flashing stock 4.4.2 firmware try it again by oulling battery and going back into dl lodem this time also check the repartition box
sent from my JEDI ELITE Note 3
for best xda results, click to enlarge ?
http://img268.imageshack.us/img268/9564/searchitnoob.gif
Where are the download links?
Arturofm2 said:
Where are the download links?
Click to expand...
Click to collapse
Well if you're having to ask this then that leads me to believe you did not read the op. I suggest you do so or you may have a bad experience. Once you read all of the op I will tell you where it is
Sent from my GT-I9205 using Tapatalk
markbencze said:
Well if you're having to ask this then that leads me to believe you did not read the op. I suggest you do so or you may have a bad experience. Once you read all of the op I will tell you where it is
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
Now I see the download link, but it wasn't there yet.
Thanks, by the way you said that it may be difficult to go back to a different version, does this include the backups too?
Arturofm2 said:
Now I see the download link, but it wasn't there yet.
Thanks, by the way you said that it may be difficult to go back to a different version, does this include the backups too?
Click to expand...
Click to collapse
Yes
Sent from my GT-I9205 using Tapatalk
My phone is not flashing
its working never mind lol. I just tried again and it worked
regarding the stuck on RECOVERY BOOTING, you have to reflash it, WITHOUT ticking the REPARTITION (as stated in the instructions. you just need to reflash again. and it should work the 2nd time around
Thanks very
How can i get it to work with mac
Sent from my SM-N900T using xda premium
westkhalifa13 said:
How can i get it to work with mac
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
No idea man. I don't have a mac. Google it man
running DECEPTICON rom (coming soon)
for best xda results, click to enlarge ?
http://img268.imageshack.us/img268/9564/searchitnoob.gif
I was trying to root my phone using the information/program on http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 . The program started to run and seemed to be working but it never finished or I was an idiot who didn't give it enough time. Either way, I now have a phone that I can only get to the bootloader screen but it isn't unlocked so I can't put a new ROM on it and the factory reset doesn't get me back in. Is there any way to unlock from here or do I need to seek out and download the stock Verizon ROM and install it again via the SD card?
mwolf00 said:
I was trying to root my phone using the information/program on http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 . The program started to run and seemed to be working but it never finished or I was an idiot who didn't give it enough time. Either way, I now have a phone that I can only get to the bootloader screen but it isn't unlocked so I can't put a new ROM on it and the factory reset doesn't get me back in. Is there any way to unlock from here or do I need to seek out and download the stock Verizon ROM and install it again via the SD card?
Click to expand...
Click to collapse
After you get your phone back to 5.0 stock, run the one click root again on win 10 using the stock cable if you have it, then install SuperSU. Go to thread Official bootloader unlock for Verizon note 3 by ryanbg. This will completely unlock bootloader and you can install TWRP. But read the warning thread about using the new version.
I'm new at this but it worked for me
Good luck, some of those threads have info on getting you back to normal
Thank you for your reply. Unfortunately, right now I'm not sure if I'll even be able to get back to 5.0. The original USB cable is a thought as I'm not able to get the PC to see the phone. My only access is SD card so far.
mwolf00 said:
Thank you for your reply. Unfortunately, right now I'm not sure if I'll even be able to get back to 5.0. The original USB cable is a thought as I'm not able to get the PC to see the phone. My only access is SD card so far.
Click to expand...
Click to collapse
If you:
- pull battery, wait 10 sec, insert battery. (USB *not* plugged in)
- startup w/ Vol-Down+Home+Power
- select "Cancel" when warning splash screen displays
what happens? Does it hang for a while before it goes back to the Odin Download screen?
I'm not aware of any method to install from the SD card.
(Maybe w/Mobile Odin but that doesn't apply here).
99% of the time if there is a connectivity issue between the phone & the PC, the issue is on the Windows side if things.
bftb0 said:
If you:
- pull battery, wait 10 sec, insert battery. (USB *not* plugged in)
- startup w/ Vol-Down+Home+Power
- select "Cancel" when warning splash screen displays
what happens? Does it hang for a while before it goes back to the Odin Download screen?
I'm not aware of any method to install from the SD card.
(Maybe w/Mobile Odin but that doesn't apply here).
99% of the time if there is a connectivity issue between the phone & the PC, the issue is on the Windows side if things.
Click to expand...
Click to collapse
When I go through the steps you suggest, after I select the cancel action, the phone restarts and enters the boot loader with very little delay. The whole process takes about 10 seconds.
I've downloaded the stock ROM. Is there a way to install it from SD card? Can I use Odin on it to create a file the phone can boot from? It seems there should be something I can do...
Also - As for the connectivity issue being on the windows side, before this whole process, I had no issues connecting to the phone from Windows so I do not believe it is on that side...
mwolf00 said:
When I go through the steps you suggest, after I select the cancel action, the phone restarts and enters the boot loader with very little delay. The whole process takes about 10 seconds.
I've downloaded the stock ROM. Is there a way to install it from SD card? Can I use Odin on it to create a file the phone can boot from? It seems there should be something I can do...
Also - As for the connectivity issue being on the windows side, before this whole process, I had no issues connecting to the phone from Windows so I do not believe it is on that side...
Click to expand...
Click to collapse
'
Whew - I was able to get the stock ROM back on the phone. There was a pending update on my PC which might or might not have been part of the issue. After the restart, I was able to us Odin to push it back on. Now to root the thing again...