I can't get my droid ultra to be recognized other than offline and can't flash it back to try the root method it says i need the fastboot o bake driver .RSD lite doesn't recoginze it in fastboot can anyone suggest a fix i have installed moto device manager 5 times each differet downloads
If I boot it up in bp mode red lite see the phone until it reboots to fastboot the it says it didn't switch modes but it seems to
Sent from my XT1080 using XDA Premium 4 mobile app
Make sure USB debug is enabled. Make sure the phone is not on the lock screen while plugged in. Unplug and replug the device. Restart the adb service (adb kill-server, then adb start-server).
These are the easiest things to try that come to mind.
Debugging is on ,lockscreen is not on . unplugged my phone and killed and restarted the server and still showing offline. Just used the same computer to unlock a HTC droid incredible 2 today and restore a lg optimus elite from a bootloop cycle. So I am pretty sure its not a issue with the computer I am using ,but I guess its time to try another computer and see if it changes anything. Any ideas or help is much appreciated and thanks nimdae for the input
Sent from my XT1080 using XDA Premium 4 mobile app
Make sure you have updated adb to the latest
Sent from my XT1080 using XDA Free mobile app
akellar said:
Make sure you have updated adb to the latest
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Glad you mentioned that has been quite some time since I updated it. Will get it done when this lg p930 is finished and be back .with good news I hope
Sent from my XT1080 using XDA Premium 4 mobile app
Yes, if it reports offline, then you don't have ADB 1.0.31. Type "adb version" and make sure it's 1.0.31.
kcipopnevets said:
Yes, if it reports offline, then you don't have ADB 1.0.31. Type "adb version" and make sure it's 1.0.31.
Click to expand...
Click to collapse
OK your right . how do I get the new one download it from the android SDK website? Well that's what I'm going to do tonight thanks all for the great help
Sent from my XT1080 using XDA Premium 4 mobile app
dogie425 said:
OK your right . how do I get the new one download it from the android SDK website? Well that's what I'm going to do tonight thanks all for the great help
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You should be able to update the tools through the manager, though I've been having trouble using the latest manager myself (it doesn't load). Otherwise, you can go to dev.android.com and download the latest package which includes the tools.
Got the new version install . and I plan to flash back to 4.4 version 19.5.3 for my phone. RSD lite is still not detecting the phone when it switches to fastboot so that brought up the question in my mind do I need to update fastboot or was this done when I updated the adb and is there anything else I might be forgetting to do b4 I start this since I will be using the manual method to flash this in fastboot? Any and all feedback is greatly appreciated. This is my everyday driver and I'm still paying for it thru the edge plan.
Sent from my XT1080 using XDA Premium 4 mobile app
Have you tried putting your phone in fastboot mode then connecting it to pc
TRIED Flashing thru fast boot
so i got the nerve to try downgrading my ultra with fastboot since rsd won't detect my phone when it switches to fastboot using this tutorial http://forum.xda-developers.com/showthread.php?t=2580060 all went well except on the mfastboot command i got this responce
C:\ANDROID PWNAGE\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-x86_64-2
0140321\sdk\platform-tools>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (574208 KB)...
OKAY [ 36.243s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 59.547s
and it said on the screen mfastboot error invalid piv image size for system
now the phone won't boot just jumps right back to the bootloader screen
tried it 2 more times and still no joy same out come so what do i do now? download the file again and try once more . and do i need to repeat all the steps b4 this command or will just running this command alone be fine to fix me HELP pls
Lordomn said:
Have you tried putting your phone in fastboot mode then connecting it to pc
Click to expand...
Click to collapse
yes i tried that but found out my adb was an older version and need to be updated its seeing the phone fine now. just have to figure out my latest problem
GOOD NEWS i unzipped a second download i had in my downloads folder and used that system img file to try flashing and it when through. phone is rebooting now. time to clam down and try me some pie in a bit
(thanks jcase for the pie)
You need to update your adb and fastboot files if your devices is shown as offline...
joel_sinbad said:
You need to update your adb and fastboot files if your devices is shown as offline...
Click to expand...
Click to collapse
Pretty sure we established that roughly 3 weeks ago
Sent from my XT1080 using XDA Free mobile app
akellar said:
Pretty sure we established that roughly 3 weeks ago
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Lol
usb debugging is not necessary for fastboot commands, only ADB; however, it sounds to me like you do not have the proper drivers installed for the device if RSD is not detecting it. I would delete all Motorola drivers and Motorola Device manager, reboot computer with device unplugged, reinstall Device Manager, and then connect device. You can also download Minimal ADB and Fastboot (Google search) and it is a lot less hassle than trying to use the SDK.
You may also try using a different USB cable on a different USB port (not USB 3.0). Sometimes that causes problems.
In the end my problem was my SDK was not updated ,so the device was only seen as offline as for why rsd doesn't detect it in fastboot I do not know ,but I was able to manually flash it in the end. Now I'm loving w/p off and root with safe strap installed despite the locked bl
Sent from my XT1080 using XDA Premium 4 mobile app
Related
I missed out something i think.
I have my sdk, with those files.
I went to cmd and type the commant
bla bla bla
fastboot devices >>> no error, means connected
fastboot oem unlock
>>>> it is connected but why it still waiting for my device?
I added the path to the system too, but still cant get rid of
I search the net and I cant get the solution.
Any idea anyone?
What drivers did you install? And yes, I read the "fastboot devices"
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Phone has to be in bootloader mode?
Sent from my Nexus S using XDA App
yup.. it is in volume up + on mode.
If you plug your NS in and look in the Device Manager, do you see an unknown device with the question mark? If so, you should try to manually install the driver located in android-sdk-windows\extras\google\usb_driver
And when you issue the command
Code:
fastboot devices
It should display your NS device id, not just a blank line.
melvinchng said:
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Click to expand...
Click to collapse
"samsung" driver... no
you use the drivers obtained from the Android SDK or PDAnet
Pretty much what suksit said.
Try pdanet! Last place i go y find drivers
Sent from my Nexus S using XDA Premium App
I tried sdk driver, pdanet driver. I can't unknown driver, it is listed as android. Means my phone is found by computer
I have android 2. 3. 4. Does it effect?
Sent from my Nexus S using XDA Premium App
Just curious, did you enabled the option in Settings > Applications > Development > USB debugging?
In Device Manger it should say something like "Android Composite ADB Interface"
I enabled it too... maybe I will try to reinstall and root it via my XP in VM.
I rooted my wildfire with this pc last time, maybe the drive mixed up.
Sent from my Nexus S using XDA Premium App
Just noticed that your location is in Malaysia. Could it happen that you have the i9023 (SLCD) model? If that's the case then I think you should try this.
Ya, I bought slcd set.
I will try it tomorrow at night and report back to you guys.
--------------------------------
It is really strange. Tried everything and won't work.
Pdanet detected my device that it is connected to computer, but it just show wait for device.
----------------------------------------
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
melvinchng said:
Ya, I bought slcd set.
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yeah thats normal, Samsung did some weird battery calibration thing!
However people here have found to get 100% or close to it.
When charging just leave screen on for 1 hour and have tethered wifi On, so far im charging full up to 98%, just waiting to squeeze in the last 2%.....could take awhile.
and yeah the 95% charge is normal. heres a explanation in further detail
Your battery gauge is lying to you (and it's not such a bad thing)
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
j0l6 said:
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
Click to expand...
Click to collapse
i have these in tools. and still waiting for device.
anyone any idea?
I forgot to tell you guys that my windows is 64-bit
Sent from my Nexus S using XDA Premium App
Try this or this then (the latter is quite hard to read anyway, I think they messed up the code formatting)
Unlocked bootloader!
thanks!
Sent from my Nexus S using XDA Premium App
melvinchng said:
I haven't root yet.
After I root, my storage and Rom will be wipe? So I need to install new Rom?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Rooting will add su binary and Superuser app to your NS. But your data will be wiped (both on phone and SD card) when you unlock the bootloader -- it's the same as doing a factory reset. However, your system partition will not be affected so no need to install new ROM if you prefer using stock.
Okay, so this is a new one to me, I installed TWRP Recovery after formatting System, Boot, Recovery, and Modem. I successfully reinstalled everything using a combo of fastboot and TWRP, but now my device is acting, well, weird. My system loads, but only after I open the bootloader and choose the "Normal Startup" option. Everytime I power down, it shuts off and loads into fastboot. I then need to open the bootloader and choose the above stated option to load my OS. What the heck, all I want to do is be able to UPDATE so I can participate in the JB Soak Test...has anyone come across this issue? Need some Dev Love right about now, I'm relatively new to this.
Reflash stock FXZ.
mrvek said:
Reflash stock FXZ.
Click to expand...
Click to collapse
Can I do that from TWRP?
Sent from my XT897 using xda app-developers app
galacticservant said:
Can I do that from TWRP?
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
No. You need RSDLite. FXZ from Skrilax_CZ's thread here.
But I've seen in other threads you have issues with rsd. You should fix drivers issue first, ie. get your device recognized first. Remove all drivers, reinstall, use device manager to see if some drivers are missing... IIRC, windows needs to install different drivers for running system (mtp, mass storage mode...) and different for bootloader mode, it should notify you of the process happening.
mrvek said:
No. You need RSDLite. FXZ from Skrilax_CZ's thread here.
But I've seen in other threads you have issues with rsd. You should fix drivers issue first, ie. get your device recognized first. Remove all drivers, reinstall, use device manager to see if some drivers are missing... IIRC, windows needs to install different drivers for running system (mtp, mass storage mode...) and different for bootloader mode, it should notify you of the process happening.
Click to expand...
Click to collapse
Yeah, I just installed a driver cleaner. Then I disabled the auto driver updater that windows has. Next I'll reinstall Moto device Manager and RSD Lite. The one driver that does not install is the Moto Networking Interface, which I believe is the culprit here if I'm not mistaken.
Sent from my XT897 using xda app-developers app
mrvek said:
No. You need RSDLite. FXZ from Skrilax_CZ's thread here.
But I've seen in other threads you have issues with rsd. You should fix drivers issue first, ie. get your device recognized first. Remove all drivers, reinstall, use device manager to see if some drivers are missing... IIRC, windows needs to install different drivers for running system (mtp, mass storage mode...) and different for bootloader mode, it should notify you of the process happening.
Click to expand...
Click to collapse
Yes, went into My Computer right click Properties, then chose Environmental Variables, and entered a user variable to allow showing of unused and hidden device drivers. Cleared all the ones that were outdated or possible conflicts (usb and adb drivers from samsung, htc, etc.), then reinstalled RSD Lite 6.1.5 and Moto Device Manager. Booted into Android system, ADB loaded. USB Mass Storage loaded. Booted into AP fastboot, NOTHING. Booted into Tools and a bunch of drivers were not found. Strange, I thought Moto Device Manager would cover those, isn't that what it's for??? I somehow am not getting the needed drivers, probably the Motorola Networking Interface. Any ideas?
Sent from my XT897 using xda app-developers app
galacticservant said:
Yes, went into My Computer right click Properties, then chose Environmental Variables, and entered a user variable to allow showing of unused and hidden device drivers. Cleared all the ones that were outdated or possible conflicts (usb and adb drivers from samsung, htc, etc.), then reinstalled RSD Lite 6.1.5 and Moto Device Manager. Booted into Android system, ADB loaded. USB Mass Storage loaded. Booted into AP fastboot, NOTHING. Booted into Tools and a bunch of drivers were not found. Strange, I thought Moto Device Manager would cover those, isn't that what it's for??? I somehow am not getting the needed drivers, probably the Motorola Networking Interface. Any ideas? I even progressively went through and installed every version of RSD all the way back to version 5.7.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Sorry for the double post
Sent from my XT897 using xda app-developers app
I really do not know. I'd try to reinstall drivers while in bootloader. But seems like a long shot.
Why did you format system, boot, recovery, modem?
Is your system functional? Try to connect it as MTP instead of mass storage (if not already).
On my XP machine for the additional BP Tools devices, I had to use the pre-release v5.9.1 drivers (developer version, 32bit only) that have been posted here:
http://forum.xda-developers.com/showthread.php?t=1891582
kabaldan said:
On my XP machine for the additional BP Tools devices, I had to use the pre-release v5.9.1 drivers (developer version, 32bit only) that have been posted here:
http://forum.xda-developers.com/showthread.php?t=1891582
Click to expand...
Click to collapse
I will definitely try that...thanks
Sent from my XT897 using xda app-developers app
mrvek said:
I really do not know. I'd try to reinstall drivers while in bootloader. But seems like a long shot.
Why did you format system, boot, recovery, modem?
Is your system functional? Try to connect it as MTP instead of mass storage (if not already).
Click to expand...
Click to collapse
Well, I was being stupid. Trying to bring back to stock, didn't have RSD, and had 8 hours till Moto pushed JB to my phone. So, I formatted and wiped the whole thing, oops.
Sent from my XT897 using xda app-developers app
galacticservant said:
Well, I was being stupid. Trying to bring back to stock, didn't have RSD, and had 8 hours till Moto pushed JB to my phone. So, I formatted and wiped the whole thing, oops.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
I could easily be wrong but I doubt formatting recovery, modem, kernel and ramdisk (boot) is a wise thing to do if you're only trying to get clean stock. Simply re-flashing stock image should take care of everything.
mrvek said:
I could easily be wrong but I doubt formatting recovery, modem, kernel and ramdisk (boot) is a wise thing to do if you're only trying to get clean stock. Simply re-flashing stock image should take care of everything.
Click to expand...
Click to collapse
Hind sight.....
Sent from my XT897 using xda app-developers app
So it turns out that I didn't run the command "moto-fastboot oem fb_mode_clear" after manually reinstalling my OS through fastboot utility. My phone now boots up normal. Still no end in sight for getting RSD Lite to recognize my phone...
Sent from my XT897 using xda premium
galacticservant said:
So it turns out that I didn't run the command "moto-fastboot oem fb_mode_clear" after manually reinstalling my OS through fastboot utility. My phone now boots up normal. Still no end in sight for getting RSD Lite to recognize my phone...
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
(I followed the .xml script contained in the SBF and manually erased and flashed my entire system. Forgot the above referenced line though and my system was locked going to sticky-bit factory fastboot. There is a command line "moto-fastboot oem fb_mode_set" which I believe RSD uses to make the device reboot into fastboot after partitioning and such (.mbn?). Anyway, I'm still learning so cut me some slack. Everybody has to start somewhere, right?
Sent from my XT897 using xda premium
If you have help, thank you. If not, just move on. I'm asking for an answer, not a smart ass remark. And yes, I know I'm an asshole. :laugh:
Anyways...
My computer won't recognize my phone when it is in fastboot. I've looked at other threads saying that Windows 8.1 (my computers OS) will not work with ADB, but I no longer have that problem. Fastboot still doesn't work however. Any direct answers? Can you point me to a thread that will help?
Much appreciated.
Do you have the proper drivers? And are you using using the correct "fastboot devices" command?
Sent from my HTC One XL using XDA Premium 4 mobile app
pandasa123 said:
Do you have the proper drivers? And are you using using the correct "fastboot devices" command?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Proper drivers are installed. (99% sure about that) And I am using the right commands. Nothing comes up with "fastboot devices" and any other fastboot command just says "waiting for device"
Hmm...are you in fastboot usb or just bootloader only?
Sent from my HTC One XL using XDA Premium 4 mobile app
pandasa123 said:
Hmm...are you in fastboot usb or just bootloader only?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Fastboot USB
ConnorAAVance said:
I've looked at other threads saying that Windows 8.1 (my computers OS) will not work with ADB, but I no longer have that problem.
Click to expand...
Click to collapse
If still on Windows 8, my guess would be that is the culprit.
ConnorAAVance said:
And yes, I know I'm an asshole. :laugh:
Click to expand...
Click to collapse
Not really. fastboot and adb can be amazingly finicky, and I've had any number of the "usual" fixes not work for me. And your issue with adb working, and fastboot not is a little curious (the opposite or both not working seem to be the much more common cases).
But I can appreciate your . . . uh . . humbleness.
redpoint73 said:
If still on Windows 8, my guess would be that is the culprit.
Not really. fastboot and adb can be amazingly finicky, and I've had any number of the "usual" fixes not work for me. And your issue with adb working, and fastboot not is a little curious (the opposite or both not working seem to be the much more common cases).
But I can appreciate your . . . uh . . humbleness.
Click to expand...
Click to collapse
That's how it was for awhile. ADB and fastboot would not work, but i downloaded the current SDK and the update for HTC Sync and that fixed my ADB problem. The fastboot just didn't change. I've been wanting to go back to Windows 7 for quite some time now; I guess this problem is whats going to get me to do that.
I had a lot of trouble with my computer not recognizing my phone in fastboot also. I have a windows 7 laptop with windows 8 as a dual boot. When trying to s-off my phone, windows 7 wouldn't recognize my phone. I ended up doing the s-off process with windows 8 as everything worked fine there. I definately think the problem with yours is windows but not necessarily windows 8. What I would do if i was you is partition the hard drive, get a copy of windows 7 and install it to the new partition. A fresh copy of windows could make the difference. Either that or you could back up your hard drive and do a factory restore with windows 8. The dual boot is better because if you have problems, with one, you can boot up the other operating system and try again. Just a suggestion.
Or you could just download VirtualBox and install Ubuntu virtually, then download ADB and away you go. A lot easier than dual-booting two OS's that are essentially the same..
Okay so I did read up on another post about the same issue but it didn't really explain what fixed it. I only have a windows xp or vista or something computer. Its a 32 bit. I have installed and uninstalled drivers from SDK manager, manually installed Google drivers, universal drivers. All of it. I originally tried rooting using cf auto. Than tried to do it manually. That is when I realized it was a fastboot issue. I'm in fastboot mode during my attempts. Should it say fastboot USB when plugged in?
Sent from my Nexus 5 using xda app-developers app
whozilla said:
Okay so I did read up on another post about the same issue but it didn't really explain what fixed it. I only have a windows xp or vista or something computer. Its a 32 bit. I have installed and uninstalled drivers from SDK manager, manually installed Google drivers, universal drivers. All of it. I originally tried rooting using cf auto. Than trues to do it manually. That is when I realized it was a fastboot issue. I'm in fastboot mode during my attempts. Should it say fastboot USB when plugged in?
Click to expand...
Click to collapse
Have you endabled USB debugging under Developer options in your Settings?
Yep. More details
I have uninstalled and re installed all drivers from
lgs driver .exe
From the universal. Driver.
And google drivers
via sdk manager.exe.
I did that after i re set up android SDK in the c drive,s root. and ran the commands from directly in the platforms folder. Still my device is only seen under adb devices. Not fastboot devices. I just type in fastboot in the promt and it shows all the commands listed so I assume it has been set up.
Now it seems SDK manager won't open. A promt pops up and closes with no program open thereafter. I wanted to retry googles drivers because I uninstalled and re set up android SDK. I wanted to re download the packages and start fresh.
Sent from my Nexus 5 using xda app-developers app
whozilla said:
Yep. More details
I have uninstalled and re installed all drivers from
lgs driver .exe
From the universal. Driver.
And google drivers
via sdk manager.exe.
I did that after i re set up android SDK in the c drive,s root. and ran the commands from directly in the platforms folder. Still my device is only seen under adb devices. Not fastboot devices. I just type in fastboot in the promt and it shows all the commands listed so I assume it has been set up.
Now it seems SDK manager won't open. A promt pops up and closes with no program open thereafter. I wanted to retry googles drivers because I uninstalled and re set up android SDK. I wanted to re download the packages and start fresh.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Google tool adb fastboot drivers xda. That should get them working
Nice. gonna try as soon as I get home from work. I'll report back with result :thumbup:
Sent from my Nexus 5 using xda app-developers app
You're still thinking of HTC phones...
When in fastboot it will no change on the phone itself, you check by running 'fastboot devices' in the command prompt. If you see your serial number, it's fine. If you don't, go into Device Manager and manually update the driver
If you run 'adb devices' when connected in fastboot nothing will happen as adb is ONLY FOR WHEN ANDROID IS RUNNING (how many more times does this need to be said??).
whozilla said:
Nice. gonna try as soon as I get home from work. I'll report back with result :thumbup:
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I'm sorry eddy. It seems you misread my posts. Im not having an issue understanding the difference between adb and fastboot. Allow me to clarify. While phone is on. With USB debugging enabled. I type
adb devices
in the command prompt under platform tools.. My device shows up and I have authorized it
When my phone is in the bootloader in fastboot mode. I type
fastboot devices
Nothing. That is my issue. Feel free to scroll back up and read the details. Any help is good help :beer:
Sent from my Nexus 5 using xda app-developers app
EddyOS said:
You're still thinking of HTC phones...
When in fastboot it will no change on the phone itself, you check by running 'fastboot devices' in the command prompt. If you see your serial number, it's fine. If you don't, go into Device Manager and manually update the driver
If you run 'adb devices' when connected in fastboot nothing will happen as adb is ONLY FOR WHEN ANDROID IS RUNNING (how many more times does this need to be said??).
Click to expand...
Click to collapse
I quoted myself by mistake haha. PS
I have manually updated drivers. After uninstalling them to be clear. That's what I meant when I said I tried the universal drivers. For the record. All attempts I have made to get fastboot to recognize my device have been done using forums with detailed instructions.
Sent from my Nexus 5 using xda app-developers app
Sounds like Windows isn't wanting to use the driver. Manually update the driver and point it to the *.inf file in the SDK. It should then work fine
Solved. Such a small detail. Eddy you were right. Before I could see your post I realized. Vuala! I needed to update the drivers manually with the phone plugged in in fastboot mode!. That was my mistake. Cf root did the rest.
In device manager you will see a yellow triangle under other devices when the nexus is plugged in on fastboot mode. I installed drivers from the .exe found in this thread.tool adb fastboot drivers. I let the computer search on its own for updates. Done. Rooted
Sent from my Nexus 5 using xda app-developers app
jd1639 said:
Google tool adb fastboot drivers xda. That should get them working
Click to expand...
Click to collapse
Thank you sir. You lead me in the right path
Sent from my Nexus 5 using xda app-developers app
I am new and noob , i hope i am asking at the right place
So i have a galaxy note 4 verizon model , i am using a different carrier and the problem is that i cant add apn's because verizon is restricting that, i searched the web for a solution but only found solutions involving rooting which i will not risk at any cost
Until i found this post of someone explaining how to overcome this using a flashable mod and recovey mode ,
Is this possible without rooting for some claimed so ? I have uploaded his post can someone pleeeeease explain this for me and direct me to what to do
Sent from my SM-N910V using XDA Free mobile app
maqqam said:
I am new and noob , i hope i am asking at the right place
So i have a galaxy note 4 verizon model , i am using a different carrier and the problem is that i cant add apn's because verizon is restricting that, i searched the web for a solution but only found solutions involving rooting which i will not risk at any cost
Until i found this post of someone explaining how to overcome this using a flashable mod and recovey mode ,
Is this possible without rooting for some claimed so ? I have uploaded his post can someone pleeeeease explain this for me and direct me to what to do
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
The method 1 in the image says you to use a custom recovery. To use a custom recovery also your phone must be rooted and bootloader unlocked. So, you can't do this without rooting your phone.
Yeah, 4shreyas is right.
Sent from my SPH-L300 using XDA Free mobile app
maqqam said:
I am new and noob , i hope i am asking at the right place
So i have a galaxy note 4 verizon model , i am using a different carrier and the problem is that i cant add apn's because verizon is restricting that, i searched the web for a solution but only found solutions involving rooting which i will not risk at any cost
Until i found this post of someone explaining how to overcome this using a flashable mod and recovey mode ,
Is this possible without rooting for some claimed so ? I have uploaded his post can someone pleeeeease explain this for me and direct me to what to do
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Actually, your shud have asked it here: http://forum.xda-developers.com/note-4-verizon
Okay, install Minimal ADB and Fastboot in PC. (Google it)
Then install your phone drivers and ADB drivers (Google it).
Download this: http://www.techerrata.com/file/twrp2/trltevzw/openrecovery-twrp-2.8.5.0-trltevzw.img
Rename it to recovery.img and place in C:/ drive
Enable USB debugging in phone and connect to PC. (Google it)
Then open 'Minimal ADB and Fastboot' shortcut in Desktop as Admin and type the following:
Code:
adb reboot bootloader
fastboot boot recovery C:\recovery.img
Now install the mod zip file which you saw from there.
That's all. Your phone won't be rooted.
GokulNC said:
Actually, your shud have asked it here: http://forum.xda-developers.com/note-4-verizon
Okay,........
That's all. Your phone won't be rooted.
Click to expand...
Click to collapse
I think this method also changes the system status to modified which breaks the warranty. If it doesn't then this method can be used.
4shreyas said:
I think this method also changes the system status to modified which breaks the warranty. If it doesn't then this method can be used.
Click to expand...
Click to collapse
Booting doesn't break the warranty. I'm damn sure
GokulNC said:
Booting doesn't break the warranty. I'm damn sure
Click to expand...
Click to collapse
Thanks so much , i am on it
Sent from my SM-N910V using XDA Free mobile app
I think i got everything ready , before i proceed will this erase everything ?
Sent from my SM-N910V using XDA Free mobile app
GokulNC said:
Actually, your shud have asked it here: http://forum.xda-developers.com/note-4-verizon
Okay, install Minimal ADB and Fastboot in PC. (Google it)
Then install your phone drivers and ADB drivers (Google it).
Download this: http://www.techerrata.com/file/twrp2/trltevzw/openrecovery-twrp-2.8.5.0-trltevzw.img
Rename it to recovery.img and place in C:/ drive
Enable USB debugging in phone and connect to PC. (Google it)
Then open 'Minimal ADB and Fastboot' shortcut in Desktop as Admin and type the following:
Code:
adb reboot bootloader
fastboot boot recovery C:\recovery.img
Now install the mod zip file which you saw from there.
That's all. Your phone won't be rooted.
Click to expand...
Click to collapse
So i have done all these steps , after the first command the phone reboots and start with a green droid screen that shows *downloading dont turn off*
When i type the second command the adb command screen shows *waiting for phone * but nothing happens ??
Sent from my SM-N910V using XDA Free mobile app
maqqam said:
So i have done all these steps , after the first command the phone reboots and start with a green droid screen that shows *downloading dont turn off*
When i type the second command the adb command screen shows *waiting for phone * but nothing happens ??
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
After rebooting into bootloader, check if your phone is connected to fastboot mode properly by:
Code:
fastboot devices
If an unique device number is listed, then it means your phone is connected properly.
You can proceed.
You can also try manually going into fastboot by holding some button combination like power + volume up+ volume down while phone is switched off. (This is device specific, so better ask in your phone's forum if you can't figure out)
After going into fastboot mode, do the recovery booting as I gave command before