EDIT: Solution was to sit with OP5 technician which flashed my ROM to Oxygen 4.5.1. After this didn't do it, I RMA-ed it and got a new OP5.
EDIT: TL;DR: After updating OP5 to 4.5.5, It doesn't recognizes sim nor wifi, and can't rollback to 4.5.3 that did and stuck on phone setup (needs wifi). ADB devices is empty, I have Google USB Driver from SDK, Windows 10
Hello,
I just got a new OP5 today.
Opened it in the store, came with Oxygen 4.5.3 outta the box.
I putted the sim in, and I connected to the store's wifi, all was good and even had a phone call to my mother to check if the mic and speaker are working well.
Then when I got home, I upgraded the OS to 4.5.5 through the settings, where Android suggested. I'm new to OP and android (moved from iphone 5) and so if there is a right way to do it, and that's not it, I wouldn't have known.
Then, OP5 didn't recognize the sim anymore and couldn't start the wifi (switching it on wouldn't work, it would do nothing), so I tried Factory reset. Unfortunately it didn't reset the OS as well and now I'm stuck outside can't use my sim card or connect to my home wifi to setup the device.
Tried installing OP5 usb drivers (show when connecting the OP5 to PC) and press the power button and lower speaker volume together, then flush the 4.5.3 OS through USB, but it doesn't recognize ZIP folder and when I tried to unzip and send boot image (cmd->"adb sideload boot.img) it started and then failed at 0%.
Please help, the phone right now is unusable.
Tried the Factory reset through settings, but it took so long I thought it was stuck, so I did it through recovery screen.
Sounds like you got a lemon... I'd take it back and see if they'll swap it for another. Less than a week should be replaced immediatelly, at least that's been my experience here in Oz...
ultramag69 said:
Sounds like you got a lemon... I'd take it back and see if they'll swap it for another. Less than a week should be replaced immediatelly, at least that's been my experience here in Oz...
Click to expand...
Click to collapse
Why should it be replaced in less than a week? Also, isn't there a fix for adb problem so I could flash 4.3.5? Maybe a remote takeover?
Mine had 4.5.3 on it when I got it, updated to 4.5.4 then manually downloaded full rom, placed on internal memory and flashed 4.5.5 through the settings.
Had zero problems with WIFI before, during and after the update. No problems since.
Generally updating to a higher firmware version won't allow you to regress back to the lower, not sure with Oneplus as this is my first.
I'd also, if you can boot into Android go to settings nd check my IMEI numbers to see if they have been wiped (this can cause the sim to not be recognised) . If you have no IMEI then that is a BIG problem which will require an RMA unless you had backed up your efs files which from your description I doubt..
If the IMEI is OK I would download the full firmware version from here - https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190 - then using PC put the FULL ROM onto the internal memory then go to recovery and flash.
I'd also then unlock my bootloader(Just remember though that the phone will wipe all data after unlocking bootloader) and install TWRP - don't forget to 1st enable developer mode in settings and then allow usb debugging and OEM unlock - make a backup of the working stock rom and put it somewhere safe - home PC, in case this happens again. Best idea is to use the all-in-one tool, here - https://forum.xda-developers.com/on...l-skipsoft-android-toolkit-oneplus-5-t3625419 thankyou MSkip.
ultramag69 said:
Mine had 4.5.3 on it when I got it, updated to 4.5.4 then manually downloaded full rom, placed on internal memory and flashed 4.5.5 through the settings.
Had zero problems with WIFI before, during and after the update. No problems since.
Generally updating to a higher firmware version won't allow you to regress back to the lower, not sure with Oneplus as this is my first.
I'd also, if you can boot into Android go to settings nd check my IMEI numbers to see if they have been wiped (this can cause the sim to not be recognised) . If you have no IMEI then that is a BIG problem which will require an RMA unless you had backed up your efs files which from your description I doubt..
If the IMEI is OK I would download the full firmware version from here - https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190 - then using PC put the FULL ROM onto the internal memory then go to recovery and flash.
I'd also then unlock my bootloader(Just remember though that the phone will wipe all data after unlocking bootloader) and install TWRP - don't forget to 1st enable developer mode in settings and then allow usb debugging and OEM unlock - make a backup of the working stock rom and put it somewhere safe - home PC, in case this happens again. Best idea is to use the all-in-one tool, here - https://forum.xda-developers.com/on...l-skipsoft-android-toolkit-oneplus-5-t3625419 thankyou MSkip.
Click to expand...
Click to collapse
I can't pass the "Connect to Wifi" in the initial setup of the android, as it finds no wifi networks (but of course there are, when I use the sim in my iphone it works properly and there are wifi networks). So I don't know how can I get the IMEI number.
Right now my PC recognizes the OP5 connected via USB, but "adb devices" bring back empty list.
I think that once I get that working, I could unlock the bootloader. But I can't seem to be able to enable dev mode in settings - I can't get there.
I can only get to the recovery screen beyond the initial steps of setting up android.
Right now there is no important data on the phone and I have my laptop which is virgin to ADBs and Drivers (didn't use it to try to resolve it).
What driver and where do I get the right ADB so I could load 4.5.3 from usb to the phone?
When you upgraded, did you wipe cache and dalvik?
Binary Assault said:
When you upgraded, did you wipe cache and dalvik?
Click to expand...
Click to collapse
Wiped after the upgrade whem problems started
Might be wrong but I thought you could skip the wifi select screen on the setup wizard.
If you can get to Android you need to go to settings, scroll down to about phone and tap around 8 times on build number to enable developer settings.
You might be able to, might, pull down the settings menu in the wizard and bypass the wizard.
ultramag69 said:
Might be wrong but I thought you could skip the wifi select screen on the setup wizard.
If you can get to Android you need to go to settings, scroll down to about phone and tap around 8 times on build number to enable developer settings.
You might be able to, might, pull down the settings menu in the wizard and bypass the wizard.
Click to expand...
Click to collapse
It doesn't seem like I can skip it. Can't pull down a menu or anything
I guess only Oneplus can help me now?
Do you have any suggestion on fixing adb so it would recognize the OP5?
No, you need to enable debugging in developer settings for ADB to recognise.
Time to RMA...
ultramag69 said:
No, you need to enable debugging in developer settings for ADB to recognise.
Time to RMA...
Click to expand...
Click to collapse
Welp it is a pickle.
Going to go live chat with OP "level 2" representative.
See if they wipe the phone out and restore an older ROM.
If that't not going to work, RMA it is :/
Shame. A new phone. Took only one picture with my dad when we opened it back at the store. nothing else.
Unfortunately bad things can happen... You just got to be the one who got the dud this time round.....
Here's hoping it's the last time....
you can force update to a fresh installation of 4.5.5 by putting the 4.5.5 full zip into your phone in a folder called "update". Reboot to recovery im assuming you have stock recovery and follow the steps until you find the option that says something along the lines of "Update manually". It will detect if you have an update folder stored on your phone and it will begin reinstalling OOS 4.5.5. It sounds like a software problem but could be a hardware problem. Rule out the first option before RMA the latter.
OcazPrime said:
you can force update to a fresh installation of 4.5.5 by putting the 4.5.5 full zip into your phone in a folder called "update". Reboot to recovery im assuming you have stock recovery and follow the steps until you find the option that says something along the lines of "Update manually". It will detect if you have an update folder stored on your phone and it will begin reinstalling OOS 4.5.5. It sounds like a software problem but could be a hardware problem. Rule out the first option before RMA the latter.
Click to expand...
Click to collapse
When I connect the OP5 to the PC there are no folders under it (Computer -> OP A500 -> no folders), but I'll try and give it a shot. see what happens. Will update this reply.
Update:
After Oneplus flashed Oxygen 4.5.1 on the phone and some other magic I was able to skip wifi step on setup, yet still when I try to activate it it won't budge. the slider won't move and it looks as the page is being refreshed. Also, when I try to get into sim section in settings it would just freeze and alert the program stopped and suggest to close or wait.
Oneplus says it is hardware issue, and the fact it happened when I upgraded to 4.5.5 from settings menus is coincidence. They say I need RMA it.
If anyone knows how to fix it then I'm more than welcome to hear it.
EDIT: it also won't shut off unless I long press the power button.
Related
I've been searching for the last 6-7 hours straight for an exact answer. I have read http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 a few times. I've Googled. I've YouTubed. Facebooked. All that.
I bought a refurbished AT&T Galaxy Note 4 (SM-N910A) from eBay that was unlocked so I could use Straight Talk service. I believe it is using 4.4 KitKat but I could be completely wrong. I've had the phone for a year now. I never had to use the lock screen before until today. Reason is is because last time I didn't and I left it around co-workers, I ended up with a few unsightly photos from my 400lbs manager. Hahah. So today, I decided to use the pattern lock and put it on charge as I was outside for about an hour. I came in, was able to take the pattern off. But noticed my swipe option had been greyed. So I put the pin on (using only four numbers). For some reason, I thought it would enable the swipe option. I was obviously wrong. So I went to change it from the pin to the pattern and my pin became unrecognized/incorrect. Thought it was only because of the option settings. So I locked my screen. Obviously an extremely bad idea.
I now cannot get past my screen lock. I have tried getting into it with my computer through USB, it won't connect. Not even trying a Mini SD mounted (won't read on my computer). I have tried ADM, but apparently it has been **** for the "Lock" option for over a year now. I didn't register the phone with Samsung so "FindMyMobile" isn't working. The option to enter my Google account info doesn't show up; even after 35 attempts. No idea how to use ADB. Have read that Windows OS is pretty much impossible to use debugging. Especially with Win10. I have nothing backed up as I never expected/thought this would/could happen.
Of course, like nearly every other person, I just want to save the thousands of photos I have accumulated over the year of having my phone. At least before I have to do a factory reset.
I am a hardcore n00b at going so in depth with phones. So Layman's terms would be extremely appreciated. Or direct links would be great as well.
I believe I have covered as much information as I can think of. If any more info is needed to help figure out this issue, please ask. And thank you to all in advance!
itsjoshwho said:
I've been searching for the last 6-7 hours straight for an exact answer. I have read http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 a few times. I've Googled. I've YouTubed. Facebooked. All that.
...
Click to expand...
Click to collapse
I am no expert in this matter, but I believe factory reset is one option but you will loose all your data.
(non-root method- safest)
1. Power off
2..Keep holding the power button +volume up+home button together to go into recovery
3. Use volume keys to navigate and select factory reset
4. reboot and you are done
Second option is to root your phone. This will trip knox and your warranty will be void if you still have it
(Root Method)
The method I use to root is :
1. Download TWRP recovery for your mobile(search for your device) from https://twrp.me/devices/samsunggalaxynote4qualcomm.html site and keep it ready on your system
2. dowload super su 2.71 beta and put that into your external sd card using card reader.
3 Put your phone on download mode(power off and restart by holding power button + vol down + home)
4. Open latest version of Odin and connect phone to system via usb cable. Now "COM" in odin should turn blue
5. select tar file in AP section. Make sure repartition and reboot is unchecked just before flashing
6. click start
7.It will run for a few min and say pass when complete.
8.now remove your battery and insert after a few seconds. reboot into recovery by using step 2 in non-root method and you should login to twrp recovery
9.click install button and select super user zip u placed in sd card. flash it (u may have to uncheck signature verification). Now you are rooted!
10. wipe cash and reboot again into recovery
11. download the zip from :http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 (Developed by Dr. Ketan)
12. Install this zip as you installed Super SU and you should be good to go.
There are so many links and step by step guides on how to root your device. You can choose your favorite. This is what I can think of and please don't hold me responsible if you damage or brick your device. Good luck!
Note : It would be better to keep super su and the zip from Dr. Ketan downloaded and moved to external SD card before you flash the recovery
itsjoshwho said:
I've been searching for the last 6-7 hours straight for an exact answer. I have read http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 a few times. I've Googled. I've YouTubed. Facebooked. All that.
I bought a refurbished AT&T Galaxy Note 4 (SM-N910A) from eBay that was unlocked so I could use Straight Talk service. I believe it is using 4.4 KitKat but I could be completely wrong. I've had the phone for a year now. I never had to use the lock screen before until today. Reason is is because last time I didn't and I left it around co-workers, I ended up with a few unsightly photos from my 400lbs manager. Hahah. So today, I decided to use the pattern lock and put it on charge as I was outside for about an hour. I came in, was able to take the pattern off. But noticed my swipe option had been greyed. So I put the pin on (using only four numbers). For some reason, I thought it would enable the swipe option. I was obviously wrong. So I went to change it from the pin to the pattern and my pin became unrecognized/incorrect. Thought it was only because of the option settings. So I locked my screen. Obviously an extremely bad idea.
I now cannot get past my screen lock. I have tried getting into it with my computer through USB, it won't connect. Not even trying a Mini SD mounted (won't read on my computer). I have tried ADM, but apparently it has been **** for the "Lock" option for over a year now. I didn't register the phone with Samsung so "FindMyMobile" isn't working. The option to enter my Google account info doesn't show up; even after 35 attempts. No idea how to use ADB. Have read that Windows OS is pretty much impossible to use debugging. Especially with Win10. I have nothing backed up as I never expected/thought this would/could happen.
Of course, like nearly every other person, I just want to save the thousands of photos I have accumulated over the year of having my phone. At least before I have to do a factory reset.
I am a hardcore n00b at going so in depth with phones. So Layman's terms would be extremely appreciated. Or direct links would be great as well.
I believe I have covered as much information as I can think of. If any more info is needed to help figure out this issue, please ask. And thank you to all in advance!
Click to expand...
Click to collapse
If it's the reactivation lock then Factory reset will NOT help, it will just make you lose the data and still keeps you locked out.
Only "fix" i know for this is through a service center.
You could try to use ADB to pull the data so you won't lose anything, but i'm not sure if that would work (maybe through the recovery)
Good luck though :good:
Tuesday
306sh activated with MVNO, SA300 firmware, rooted, with TWRP recovery,
working fine for past 2 months.
For unknown reasons, it decided last friday (at home, none to low signal) to do a system update
(from SA300 to S7232). Phone - on the desk- just "dinged" and msg came up "updating
system software". I attempted to cancel, but it didn't respond. Less than a minute later, "Update Successful" msg. Didn't reboot, anything, settings showed S7232 firmware. (SA300 before,
i had done my weekly backup earlier that morning).
Since then, phone constantly reboots at the "Aquos" screen; after an average 8 hours of rebooting, it will boot to setup, the talking setup screen. Works perfect for about an hour then rebooting starts again. Let battery die last nite, tried again this am - same thing rebooting.
TWRP backups don't fix problem- weekly backup, i have 6 i've tried, factory reset doesn't fix, if i try to Software Update, it checks, tells me, "up to date".
I turn on wi-fi to use the phone from home, , guessing it did a ? hit & miss ? ota update since the
wi-fi was off when it attempted the update. Home is a very minimal signal area.
Any way to force it to take the S7232 update again?
(I could update over wi-fi if i had wanted, only i didn't want the update anyhow).
thanks, rik
I can give you a link for a backup with latest firmware, you will have to wipe data tho
https://mega.nz/#!fkommKgJ!fkiaT_p8ZFOBzyJpUdNAqOZlTWpt-5hNuQ-2vvA5tSQ
This is a full backup from newest firmware but you need to wipe data before boot
sent from rooted 306sh
Stick firmware updates are not compatible with custom recoveries
sent from rooted 306sh
Just home, thanks
Hi,
Thanks for the help, just home from work (rough), so i will plug the
Aquos in tonite and hopefully be able to try the file tomorrow,
(that 8 hour boot thing), just downloaded your file, i'm ready.
This is my take-to-work personal phone, sprint zone, and i missed it today.
Your help is really appreciated.
rik
Final note
thought i'd just post to let you know the phone obviously had big problems
-- it failed to start today -- just buzz on buzz off -- even after 4 hours charging,
all i could get was the battery dead screen, wouldn't come on at all.
Guess the real problem was with hardware, i laid it away in the junk phone box
in the attic, end of Aquos Crystal.
rik
I downloaded this backup and yesterday to restore the firmware, works great, huge thank you , you saved me. :хорошо:
can you help me?
badbadri said:
I downloaded this backup and yesterday to restore the firmware, works great, huge thank you , you saved me. :хорошо:
Click to expand...
Click to collapse
can you help me dude? :crying:
im already download this firmware and confuse how to restore it
im looking for how to root my phone but always confuse
and finally i installed supersu on playstore and reboot
im waiting for 5 minutes and not booting, and im plug my phone to pc and the computer request for formating all my storage
and my phone can enter the recovery mode and i go to wipe data & factory reset, and still not work
can you send to my email?
my email is [email protected]
thx ..
Question: My 306SH would not update (still at S8216). Could use your back up to update my firmaware?
After 306SH ph was acting weird, did a hard reset & saw system Software updtd to S7232, & unk file in Misc (.eCtcQjbu1dgnvtFnvnr6yepTp1M=) I then installed Malwarebytes & scan detects this S7232 software update as malicious malware Android/PUP.RiskyTool.Agent.ay (dm.redbend) "/system/priv-app/fotaClient.apk". When going to System to do an manual update, Malwarebytes popups w/same msg every scan "Software App", even aft reboot 2days ago 7/12/2017. And phone wont let me create new google acct. An error that "google account mgr not working" popup & I see that same unk file reappears. Ph not rooted -XDA says "there's no root for 306SH that works">see XDA blog 'Root for Aquos Crystal 306SH ONLY'.
Go to the Sharp USA website for the 306SH firmware, and see what firmware you are on.
Download the firmware from the versions higher than yours, and if there is a repeat, notably "kernel.img", download the most latest version of it.
Then, plug your device into your computer, make sure you have the proper drivers installed for the Sharp Aquos Crystal installed on your computer. Boot your device into bootloader. Go to a terminal, cd to the directory where you downloaded your .img's from the website, and do
fastboot flash kernel kernel.img
Ex.
fastboot flash foo foo.img
And you can flash all the latest updates. When done, exit the terminal, make sure the device is unmounted, unplug from computer, and reboot your Crystal.
Hooray, it should be updated!
turkbot said:
I can give you a link for a backup with latest firmware, you will have to wipe data tho
(Mega-nz link expired)
This is a full backup from newest firmware but you need to wipe data before boot
sent from rooted 306sh
Click to expand...
Click to collapse
Turkbot, I hate to beg on my first XDA post, but is there any chance that you still have that ROM and is there any chhance that it's not TextNow loaded? I've got TWRP, Busybox, SuperSU, Xposed, and I've tried every which way to edit the prop, tweak it with modules, unlock etc (it even works with my Sprint MSL, but crashes when I try to manually set my MDN and MSID) It just says no SIM/no service and refused to give me any signal except for GPS and WIFI without one. Countless 'techs' over the phone and 3 different Sprint repair stores claim they don't have the stock firmware and Sharp actually claims that the reason they can't help me with the firmware is their contract with Sprint forbids it.. If you still have the file or a TWRP / Titanium etc backup you would be my savior.
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.
I have a Galaxy Note 4 SM-N910V that I successfully rooted a couple of years ago. I played it safe and installed the stock ROM per the instructions, N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I also have TWRP installed. The issue I'm having now is I'm working in a building that I get no service whatsoever, except at the front door. It's terrible, but someone told me I should use WiFi calling, since we have WiFi throughout the building. He had me all pumped up until I realized I didn't have the option for WiFi calling on my Note 4. After researching it, I believe you must have at least Android 6.0.1 (Marshmallow).
Can someone confirm this or tell me what I need to do so I can enable this wonderful feature called WiFi calling on my phone? This would be a godsend for me. I've been told that since I have TWRP installed I can pretty much install and test any roms, but I've been afraid to because I figured there has to be more to it than that.
Thank you!
Modify_inc said:
I have a Galaxy Note 4 SM-N910V that I successfully rooted a couple of years ago. I played it safe and installed the stock ROM per the instructions, N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I also have TWRP installed. The issue I'm having now is I'm working in a building that I get no service whatsoever, except at the front door. It's terrible, but someone told me I should use WiFi calling, since we have WiFi throughout the building. He had me all pumped up until I realized I didn't have the option for WiFi calling on my Note 4. After researching it, I believe you must have at least Android 6.0.1 (Marshmallow).
Can someone confirm this or tell me what I need to do so I can enable this wonderful feature called WiFi calling on my phone? This would be a godsend for me. I've been told that since I have TWRP installed I can pretty much install and test any roms, but I've been afraid to because I figured there has to be more to it than that.
Thank you!
Click to expand...
Click to collapse
I'm almost certain that is a marshmallow feature. If you can see the option but it's grayed out and you can't turn it on then there's a fix for that. Otherwise you would need to upgrade to 6.0.1 and you'll have to go through the bootloader unlock method with a 6.0.1 bootloader is the only obstacle. If you don't update the bootloader your wifi won't work with the 6.0.1 roms.
Use this link for a guide to unlock your bootloader.
If you see the option but it's grayed out then follow this guide.
kevintm78 said:
I'm almost certain that is a marshmallow feature. If you can see the option but it's grayed out and you can't turn it on then there's a fix for that. Otherwise you would need to upgrade to 6.0.1 and you'll have to go through the bootloader unlock method with a 6.0.1 bootloader is the only obstacle. If you don't update the bootloader your wifi won't work with the 6.0.1 roms.
Use this link for a guide to unlock your bootloader.
If you see the option but it's grayed out then follow this guide.
Click to expand...
Click to collapse
Thank you for the reply and the link! I wish it were only greyed, but no, I do not have the option at all.
Regarding the bootloader, the link you provided shows in the title that it is for N910VVRU2CQI2, but I have N910VVRU2BPA1. I did originally have N910VVRU2CQI2, but to root my phone, I was told to flash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW] ROM to my phone.
Will I need to revert back to N910VVRU2CQI2 or can I still follow the instructions to unlock the bootloader with my current N910VVRU2BPA1 baseband version?
Thank you, again!
Modify_inc said:
Thank you for the reply and the link! I wish it were only greyed, but no, I do not have the option at all.
Regarding the bootloader, the link you provided shows in the title that it is for N910VVRU2CQI2, but I have N910VVRU2BPA1. I did originally have N910VVRU2CQI2, but to root my phone, I was told to flash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW] ROM to my phone.
Will I need to revert back to N910VVRU2CQI2 or can I still follow the instructions to unlock the bootloader with my current N910VVRU2BPA1 baseband version?
Thank you, again!
Click to expand...
Click to collapse
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
If you want, these are the steps I did:
1. Power down, pull the battery for 3 seconds, then boot into Download Mode
2. Using Odin, flash the BPA1\CPD1 hybrid firmware
3. Once that's done flashing reboot to recovery and factory reset. Then reboot and let that firmware install
4. Once you've gotten past all the setup part you'll want to power off again and boot to download mode again
5. Using Odin, flash the CQI2 aboot and then reboot. From this point on the process is the same as before.
6. Enable developer options, turn on USB debugging and turn on "allow unknown sources" in the security settings.
7. At this point, you'll want to have your spare SD card in and go ahead and open a command window from the same location that you have the samsung_unlock_n4-fix file in. In my case it was in my download folder and the easiest way to do that is to open that window, hold down the shift button, then right click. You should see an option that says "open command window here" then click that to open.
8. Once you open the terminal enter this command: adb devices
9. Then this command: adb push samsung_unlock_n4-fix /data/local/tmp/
10. Then install kingroot and let it start rooting. Be sure to keep the terminal open and your phone connected.
11. Once kingroot starts the rooting process do not let the phone go to sleep. Just keep a finger on the screen.
12. When kingroot gets past 50 -60 percent, enter this command in the terminal: adb shell
13. If you enter adb shell and it gives an error or says your offline, just unplug the Usb from your phone and plug it right back in. Then enter the adb shell command
14. As soon as kingroot says you're rooted, enter this command in the terminal: su (You have to grant root permission on the phone and continue)
15. Then this command: cd /data/local/tmp/
16. Then this command: chmod 777 samsung_unlock_n4-fix
17. Then this command: ./samsung_unlock_n4-fix
18. Once the scripts starts it will ask you if you want to continue, just type out: yes
Then it will do it's thing, back up your bootloader, and then power your phone down when it's done.
19. Once powered down, PULL OUT YOUR SD CARD, and boot back into Download Mode
20. Using Odin, flash Twrp and immediately boot into recovery when Odin reboots your phone.
kevintm78 said:
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
If you want, these are the steps I did:
Click to expand...
Click to collapse
Thanks for all your help, I finally got around to upgrading it. Everything went smooth and I am finally running MM 6.0.1 but unfortunately, I still can't find the feature for Wi-Fi Calling. I do now have a Advanced Calling option under Settings, which I believe you must have to use WiFi Calling, but I can't find the WiFi Calling anywhere to enable it. I must say, I'm really disappointed, yet still proud of myself that I didn't brick my phone in the upgrade process.
So, any suggestions as to why I can't find WiFi Calling on MM 6.0.1?
So no one has any ideas why I would still not have the wifi calling after installing the 6.0.1 MM? Is there a security or other update that I now need to install to get this feature? I installed the Jasmine v6 rom, if that makes any difference. Is there a way I can install 7.0 Nougat on this device, and would it likely provide the wifi calling feature or likely be a waste of time and effort?
I'm using Safelink with my Verizon phone, but they are no help, though they do say they support wifi calling as long as I can enable it on the phone. Is it possible Verizon could tell me what I need even though I don't have service with them but do use their towers?
Sorry for so many questions, I just really need wifi calling and can't understand why I don't have the option for it using 6.0.1.
I found an app named WiFi Calling while browsing through my phone directory. It looks like a system file, so shouldn't that mean the phone should have it? Is my Jasmine ROM keeping it from working or is it likely something else?
I'm now using Jasmine v7, if that makes any difference.
Help! Now my wife has no phone
kevintm78 said:
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
Click to expand...
Click to collapse
I tried to do the same for my wife since she has the same exact phone running 5.1.1 with root. Everything appeared to be going fine, but after performing the last step (flashing the N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z via Odin) and rebooting the phone, it now goes into a boot loop. It will load the Samsung logo for about 20-30 seconds, then reboot every time. I can still access TWRP from recovery and I have cleared Dalvik and Cache, but it still does the same thing. I also reflashed JasmineROM_v7.0_N910VVRU2CPF3, cleared Dalvik and Cache again, but still the same boot loop. It does still show the word Custom under the Samsung logo at boot, so I assume that is good news. Doesn't that mean the bootloader is still unlocked or something?
If it helps, the part of the process that had me concerned was after unlocking the bootloader. I powered off the phone, and then tried to load the recovery menu so I could factory reset the phone and clear the cache, but the recovery menu never appeared. It did show the Android fix-it guy for the recovery for about 10 seconds then a short progress bar under it for about 5 seconds, then it went straight to the Samsung logo. It never did give me the actual recovery menu, just the Android fix-it guy animation, which I thought was odd because I've always had the recovery menu pop up after that.
I made a complete backup using TWRP before attempting this upgrade. So, can I just restore it or are there other steps I need to perform before I attempt to revert back?
Did you ever get this resolved? I have been having an issue since mid-July where my phone does not send or receive texts or calls within half a mile radius of my office but otherwise works great everywhere else. I don't have to be in the building...I can be standing in the parking lot, parked at a nearby building/area, or driving down the street in vicinity of the area and nothing. When I try to send a text, I get a message stating there's no service. When I try to call, the phone goes from 4G with four bars to 4G with zero bars and is stuck on "dialing". When I end the call, it goes back up to four bars.
I have tried contacting Verizon many times and they tell me I need to enable WiFi calling but I don't have the Advanced Calling option in my settings. I am also running 5.1.1 on a rooted SM-N910V. Today when I spoke to them, they told me that even though my phone shows 4G, I really only had 1G service. I find this explanation ridiculous because if this was the case, I would have problems in other areas too and not just in the middle of the 8th largest urbanized area in Louisiana (while elsewhere in the same urbanized area, the phone works great). They told me I needed to do a system update which will cause me to lose root.
Hey! This is my first time here, sorry if I'm doing smth wrong, I just really need help. My fossil gen 6 is kinda useless at this point after updating to Wear OS 3 and I would like to flash it back to Wear OS 2, since I don't get any notifications & I can't even sync my notes at this point without connecting to wifi (not even through mobile data, which is pretty annoying -> my phone & watch doesn't connect to each other through bluetooth)
thanks, for any guides in advance!
night
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
edwin270 said:
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
Click to expand...
Click to collapse
Did that 3 times already, nothing changed. Thanks for your answer though!
Did you get anywhere with this? I also want to go back to wear os 2. I hate the fossil app
I'd like to know too. I just came back to Android with the S23 Ultra and wanted to pair my Razer x Fossil watch to it. But I decided to update since I was doing a factory reset/disconnect anyways. Big big BIG mistake.
There has to be a way to flash wear OS 2.3 back to the watch and re partition it as stock. I'm able to see my watch as a USB perhp on my machine without BT or wifi connection.
Anyone have the old firmware for these watches? Short of buying another Razer watch for $600
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
MiamKebab said:
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
Click to expand...
Click to collapse
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Or would you be able to provide some guidance on how to proceed?
Arkbird1000 said:
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Click to expand...
Click to collapse
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
MiamKebab said:
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
Click to expand...
Click to collapse
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
You guys seems way ahead on me in the downgrade process...
I made Wear OS 3 update but the Fossil app used to pair the watch won't work with Oneplus 8 Pro (Android 13), gotta go back but i have no idea how...
Yet i flashed a lot of custom roms and stuff in the past, but now.. kinda lost
Im looking forward to see news here
Good luck guys, i'll keep updated if i somehow manage to flash the OTA posted ahead
Edit : well i was on Apkmirror to try an older apk of the app, and found out their app targets android 12 but not android 13..........
Arkbird1000 said:
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
Click to expand...
Click to collapse
I do have the TWRP but need to find it, took some tweaks from Ticwatch 3 pro. I didnt pushed it on the repo tho. I didnt what made me do it, but I wiped my system partitions and had to rebuilt from the OTA only. But after getting the watch working again, I had few functionalities broke, including the OTA updates. If you can social enginner your way thru fossil to get files such as stock rom and other files for qualcomm software like rawprogrammer and firehose files it can be great help.