Related
I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
slide mon said:
I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
Click to expand...
Click to collapse
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
haxin said:
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
Click to expand...
Click to collapse
I was trying to downgrade the phone to ICS using the factory image from google. I picked the wrong image from the google site (picked soju, needed sojus) and flashed it using fastboot. As soon as I flashed the wrong bootloader the USB connection stopped working so I didn't flash the radio or os. I no longer can connect to the phone using fastboot or adb, usb debugging stopped working. The USB debugging option is set in developer options. So, trying to get the phone working now without USB. Hope that makes sense now. :good:
Hi,
I'm trying to take control of my galaxy s3 which has a broken screen. I saw a windows tool for it, but I need ADB enabled, which was not enabled on this one. So I'm trying to go in recovery mode and follow some instructions I've seen to enable adb. Sadly, it looks like my home button is also broken (I can't go in recovery mode, or the problem maybe that adb.exe does not list it at all). So few questions :
1) When a pure new stock galaxy s3, when the first screen appears after booting up, does the home button triggers some vibrations? (If no, I'll be sure it's broken)
2) Is there any way to directly flash my S3 with a custom firmware that have adb enabled by default in its properties, without going through recovery mode?
Thanks in advance!
noxew said:
Hi,
I'm trying to take control of my galaxy s3 which has a broken screen. I saw a windows tool for it, but I need ADB enabled, which was not enabled on this one. So I'm trying to go in recovery mode and follow some instructions I've seen to enable adb. Sadly, it looks like my home button is also broken (I can't go in recovery mode, or the problem maybe that adb.exe does not list it at all). So few questions :
1) When a pure new stock galaxy s3, when the first screen appears after booting up, does the home button triggers some vibrations? (If no, I'll be sure it's broken)
2) Is there any way to directly flash my S3 with a custom firmware that have adb enabled by default in its properties, without going through recovery mode?
Thanks in advance!
Click to expand...
Click to collapse
Yes. Theoretically You can flash a custom firmware with odin or heimdall in download mode. Make sure your new rom has enabled adb and debugging and then you can use "adb reboot recovery" and add or remove packages.
BUT, unless you can cook you own room with that enabled, i dont think you will find a room adb and debug enabled by default.
Alternative:
Flash the param zone. After it flashes it will boot into recovery mode. Or try flashing CSC file (just the cache is enough) which does the same.
Edit:
I assumed u know how to go into download (fastboot) mode even though u cant boot into recovery mode. For fastboot is easier, u can google for many tricks. From there u use odin to use Alternative above.
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Wow that can't be good. I'm new to the oneplus stuff, normally I would say boot into recovery and reflash to stock but since we do not have roms yet I have a feeling your going to have to take it back to tmobile or oneplus and exchange it.
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Restore with hard reset or Recovery mode OnePlus Nord N200 5GRestore with hard reset or Recovery mode your OnePlus Nord N200 5G can solve problems that have not been solved with a normal factory reset.
1- First turn off your OnePlus Nord N200 5G completely. If you can not unlock the screen, press and hold the power button for about 20 seconds and the phone will turn off.
2- Keep holding on volume down and power keys together for a few seconds in your OnePlus Nord N200 5G. In some devices according to the Android version the combination can be the power key and the volume key up.
3- When the OnePlus logo is displayed, release the buttons.
4- Move through the menu with the volume up and volume down keys until you reach the “Recovery Mode” option and press the power button to access.
If the device menu appears in Chinese characters, click here to see how to reset a mobile in Chinese
5- Use the volume up and volume down keys to select the “wipe cache partition” option and press the Power button to activate the option and clear the mobile cache.
6- After a few seconds you will return to the previous screen, with the volume buttons go to the option “wipe data / factory reset” and press the power button to enter. A screen with many NOes and a YES will appear, with the volume keys again go to the YES and press with the power key.
7- After finishing again with the volume keys, click on “reboot system now” and press the power key of your OnePlus Nord N200 5G, the device will reboot and take several minutes to start while restoring the device to its factory state and optimizing the applications pre-installed in the system Android 11, OxygenOS 11.
Click to expand...
Click to collapse
edale1 said:
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Click to expand...
Click to collapse
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
fogles2021 said:
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
Click to expand...
Click to collapse
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
edale1 said:
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
Click to expand...
Click to collapse
I can only boot into fastboot, recovery just boots back to "your device is corrupt'.
I can connect usb but i can't find drivers for the phone, its connect as QUSB.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
edale1 said:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
Click to expand...
Click to collapse
I've installed these and it still comes up as qusb bulk.
Yeah, selecting recovery from fastboot goes to corrupt message, too.
Just going to make a aservice request.
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
daboross said:
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
Click to expand...
Click to collapse
Can u give me a link to platform tools, also..my computer is detecting the phone as QUSB BULK:"
From one of my other threads:
------
USB DRIVERS
You may need to use the Google USB Driver from Android Studio to allow your PC to recognize your phone when it's in fastboot mode.
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Android Studio won't install the USB Drivers by default, you'll need to install them through the SDK Manager (Android Studio -> Projects -> More Actions -> SDK Manager -> SDK Tools -> Google USB Driver checkbox -> Apply)
You'll need to manually install the drivers through the device manager while the phone is in fastboot mode and connected to the PC (right-click -> Update Drivers -> Browse Computer -> Let Me Pick -> Have Disk).
The drivers should be located at:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
You'll want the 'Android Bootloader Interface' driver.
Click to expand...
Click to collapse
------
Basically, you need to manually update the drivers through device manager.
edale1 said:
From one of my other threads:
------
------
Basically, you need to manually update the drivers through device manager.
Click to expand...
Click to collapse
I can't get it to work...
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
From the first update drivers dialog (your phone should be in fastboot mode):
"browse my computer for drivers"
"let me pick from a list of available drivers on my computer"
"have disk"
And the drivers should be at
Code:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
Once you select the .inf, you'll want to select this from the resultant list:
"Android Bootloader Interface"
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
Your phone is in EDL mode, also known as hard brick. It seems like the phone thinks both of your system partitions are empty or corrupt, as well as the bootloader is perhaps corrupt, due to which it is now gone to EDL mode as a last resort.
Typically, the only way to come out of it is to flash in EDL mode using MSMDownload Tool. Unfortunately for you, I don't see that Oneplus has released the MSMDownload Tool for the N200.
There are 4 things you can do at this stage.
1. If the phone is in return period, get it exchanged for another one.
2. Assuming the phone is under warranty, get it repaired under warranty
3. Wait for Oneplus to release the MSMDownload Tool for the N200. From past experience, Oneplus has eventually released it for every one of their phones. Once it is released, it is literally a 5 minute fix to get your phone to factory refreshed stage.
4. As a long shot, we can try to see if the bootloader is not corrupt, and if that is working, try to check if either of the 2 system partition is still intact, as @edale1 is suggesting above. Try the following
a. Press Volume Down+Power when phone is power off stage, and see if you can get the phone in fastboot mode.
b. Go to the folder when you have downloaded the Android SDK Toolkit. Alternately, search for the folder containing "fastboot.exe" on your hard drive. Open a command prompt in that folder containing fastboot.exe.
c. Run "fastboot devices" in the command prompt.
d. If you get a response of "no devices", then that means either phone is not in fastboot mode ( Go to Step a and repeat a,b,c until it is in fastboot mode) or bootloader is corrupt (nothing can be done other than Steps 1, 2 or 3 I have outlined above)
e. If you get a response of "XYZ fastboot" where XYZ is a random string/number, then bootloader is not corrupt. Proceed to Step f.
f. Type "fastboot getvar all" in the command prompt.
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device, either 'a' or 'b'
g. Follow @edale1's instruction above to change active partition to the *opposite* of whatever currently active partition e.g. if it says 'a' as the active partition in Step f above, then type in "fastboot --set-active=b" in command prompt, and vice-versa i.e. if it says 'b' as the active partition in Step f above, then type in "fastboot --set-active=a" in command prompt
h. If you get success in Step g, type "fastboot reboot" in command prompt, and keep your fingers crossed that it boots up normally. If not, that means both system partitions are corrupt. Follow Steps 1, 2 or 3 above.
Good luck!
fogles2021 said:
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Click to expand...
Click to collapse
No stock rom on oneplus/tmobile website
Im having a device corrupt error and cannot access phone anymore. Im trying to find the stock rom to flash with MSM tool but cantyfind it anywhere. You'd think oneplus would have it up on their website already. Anyone?
forum.xda-developers.com
Had the same problem, had to do a warranty replacement
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Ethanvio said:
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Click to expand...
Click to collapse
If you didn't enable OEM unlocking in developer options before you bricked your phone, you can't unlock those fastboot commands.
my oneplus nord n10 5g is stucked on fastboot. to reinstall stock rom , i want to unlock bootloader , but my usb debudding and oem unlocking is off. how can i fix that ?
hfsva007 said:
my oneplus nord n10 5g is stucked on fastboot. to reinstall stock rom , i want to unlock bootloader , but my usb debudding and oem unlocking is off. how can i fix that ?
Click to expand...
Click to collapse
You don't need either adb debugging or OEM unlock ticked to reset it to stock.
Just go into edl mode on your phone and start the process.
ninjasinabag said:
You don't need either adb debugging or OEM unlock ticked to reset it to stock.
Just go into edl mode on your phone and start the process.
Click to expand...
Click to collapse
Thanks mahn thatks for the help. the first time im head about edl mode. download the edl mode firmware and flashed it. its worked......thank a lotb
hfsva007 said:
Thanks mahn thatks for the help. the first time im head about edl mode. download the edl mode firmware and flashed it. its worked......thank a lotb
Click to expand...
Click to collapse
Care to explain how to do it please?
I get into fastboot, but I cant get in to EDL mode in any way.
There are a few other posts in this forum on this subject. I almost want to ask mods for a sticky on it, as it seems to screw up a lot of people. The threads are all there, I won't repeat them here, but here's the stuff I didn't find obvious:
Make sure you have the right drivers installed. There is a SPECIAL set of Qualcomm drivers- different from the phone, and anything fastboot/ADB, needed to make Windows happy. Without this, you will get nowhere.
If Windows isn't your OS, and you are running an emulator (e.g. VirtualBox on Linux), make sure the USB ports are pass-through to the VM. This often requires permissions settings NOT DONE by the installer.
Likewise, make sure you pull your computer off the internet during this process or Windows may randomly reboot you to do system updates, with your phone half-flashed.
When you use the plug-in method for EDL, YOU ONLY GET IT FOR LIKE 3-5 SECONDS. You will not have a screen indication. You will not have vibration, or any other signal I know of beyond the USB device indication.
Quick process refresher: If memory serves (it has been a while) have the phone powered off, hold AND CONTINUE TO HOLD both volume buttons, and plug the phone in. *THEN* it should show up in Windows as a Qualcomm device. Let go of the buttons, take a deep breath, pat yourself on the back for having VM and drivers installed correctly. Get the phone powered off again however you can, then repeat the process again with the flash tool running, and it should give you a short window of "ready" or whatever for you to start the flash. Once you do that, and it goes into "beginning firehose" something or other, you can let go of the volume buttons. If you miss the window, repeat again until you hit it.
FWIW, it is pretty much impossible to brick a OnePlus without physical damage. The EDL mode is a separate methodology that allows a complete overwrite of everything that can be overwritten.
the idea is to simply deggogle my a10. i found a few videos on how to do it. however i took the liberty of making a note of the base build number and after searching the internet, i found a firmware farchive that contained several md5 files. i figured i may need this in case anything went wrong.
so i went into settings and developer mode, turned on unlocking oem and usb debugging and attempted to flash the phone by booting into rescue mode (power off phone then power on while holding the volume up button) then selecting boot into bootlader from the menu before using a toll called odin on my pc, which given the threads i've seen on here, most of you are aware odin. i tried to flash the tar file reccomended on the site. odin reported failure. so without rebooting i flashed the firmware that matched my phone my selcting the respective md5 files and telling odin to do it. it reported neither success nor failure but gave a message of something like cs select. i have no idea what that means. however on rebooting the phone it booted fine. no errors or anything, just a completely reset phone. I like to add that this is not may main phone as i am a newbie on this area and wouldn't be so reckless as to experiment on my main phone. hower there is an app on there now called lazade which i beleiv is a shopping app based in the asian continent which isn't where i'm from. i unlocked developer mode once again as it had reset and found that the unlock oem option is missing. is it becasuse of the firmware i burned on it and to i need to reburn another? or is ther another way to get it back?
the baseband version is a105gdxu8cvg2
android 11
one ui 3.1
Your post isn't very clear....have you been able to unlock your bootloader?
The OEM Unlock toggle often disappears if 1) the bootloader is already unlocked, or 2) the system has not yet verified whether OEM unlocking is allowed. This is most likely not a firmware issue.
V0latyle said:
Your post isn't very clear....have you been able to unlock your bootloader?
The OEM Unlock toggle often disappears if 1) the bootloader is already unlocked, or 2) the system has not yet verified whether OEM unlocking is allowed. This is most likely not a firmware issue.
Click to expand...
Click to collapse
it's an old phone. i've had it for a number of years, but i got a new phone recently so i took the oppounity to attempt to degoogle my old one. apparently there's more than one way to do this One is to replace android with other operating system. if youtube is to be beleived. i doubt the phone needs veryfying as it's an old phone although the firmware is fresh. perhaps it is unlocked. in tairness i don't know how to determine that.
fjb59 said:
it's an old phone. i've had it for a number of years, but i got a new phone recently so i took the oppounity to attempt to degoogle my old one. apparently there's more than one way to do this One is to replace android with other operating system. if youtube is to be beleived. i doubt the phone needs veryfying as it's an old phone although the firmware is fresh. perhaps it is unlocked. in tairness i don't know how to determine that.
Click to expand...
Click to collapse
The best I can suggest is to flash a LineageOS GSI without Gapps. There are other custom ROMs available that are sanitized of all Google services.
V0latyle said:
The best I can suggest is to flash a LineageOS GSI without Gapps. There are other custom ROMs available that are sanitized of all Google services.
Click to expand...
Click to collapse
are they available here?
fjb59 said:
are they available here?
Click to expand...
Click to collapse
Just Google LineageOS, they have a website. You should be able to flash a GSI image via TWRP.
V0latyle said:
Just Google LineageOS, they have a website. You should be able to flash a GSI image via TWRP.
Click to expand...
Click to collapse
that's my next goal. i haven't got twirp on there. none of the methods i saw on youtube worked.
fjb59 said:
that's my next goal. i haven't got twirp on there. none of the methods i saw on youtube worked.
Click to expand...
Click to collapse
i found the site for it but the a10 is not listed on thier choice of phones
Assuming your bootloader is already unlocked, here is the TWRP thread for your device., which you probably could have found by searching. Instructions for flashing are in that thread. And here is the LineageOS 19.x GSI thread.
If you haven't unlocked your bootloader yet, that's your first step. Some devices are not bootloader unlockable.
V0latyle said:
Assuming your bootloader is already unlocked, here is the TWRP thread for your device., which you probably could have found by searching. Instructions for flashing are in that thread. And here is the LineageOS 19.x GSI thread.
If you haven't unlocked your bootloader yet, that's your first step. Some devices are not bootloader unlockable.
Click to expand...
Click to collapse
i don't know if i have yet. i went though a process and now the oem unlocking option disappeared ffrom the developer menu. i can boot into the bootload from the rescue menu. I assume that's what you mean.
fjb59 said:
i don't know if i have yet. i went though a process and now the oem unlocking option disappeared ffrom the developer menu. i can boot into the bootload from the rescue menu. I assume that's what you mean.
Click to expand...
Click to collapse
When you're in download mode, you should see OEM LOCK among the text in the upper right of the screen. If this says ON, your bootloader is locked.
V0latyle said:
When you're in download mode, you should see OEM LOCK among the text in the upper right of the screen. If this says ON, your bootloader is locked.
Click to expand...
Click to collapse
oem lock onu1)
looks like it's on. how do i disable it for this phone?
Turn the phone completely off, and leave it off for a few minutes. Then, while holding both Volume buttons together, plug in the USB cable. The device should start in Download mode. Hold Volume + until the bootloader unlock screen appears, then follow the prompt to unlock your bootloader. This will wipe data.
V0latyle said:
Turn the phone completely off, and leave it off for a few minutes. Then, while holding both Volume buttons together, plug in the USB cable. The device should start in Download mode. Hold Volume + until the bootloader unlock screen appears, then follow the prompt to unlock your bootloader. This will wipe data.
Click to expand...
Click to collapse
never shows up. i get to the download screen but pressing the vol up keys doesn't do anything. not even adb can see the device. use debugging is turned on. and usb mode is set to file transfer mode. it weorked finde before i reflashed it. perhaps i need another version of the firmware
development, i noticed the wifi wasn't turned on. i turned it on the went into the development mode. unlock oem was there and ticked
so i did what you said again, this time the option for unlocking oem in download was present. i followed the instructions. it booted and came telling me the oem is unlocked and won't be able to verify the intergrty of the os. now it's doing a reset. i think we got here. what next? you you said twrp?
fjb59 said:
never shows up. i get to the download screen but pressing the vol up keys doesn't do anything. not even adb can see the device. use debugging is turned on. and usb mode is set to file transfer mode. it weorked finde before i reflashed it. perhaps i need another version of the firmware
Click to expand...
Click to collapse
ADB only works in Android or in recovery mode. Samsung devices don't have a fastboot mode.
fjb59 said:
development, i noticed the wifi wasn't turned on. i turned it on the went into the development mode. unlock oem was there and ticked
so i did what you said again, this time the option for unlocking oem in download was present. i followed the instructions. it booted and came telling me the oem is unlocked and won't be able to verify the intergrty of the os. now it's doing a reset. i think we got here. what next? you you said twrp?
Click to expand...
Click to collapse
Yep. Since you don't already have TWRP installed, follow "Method 2" in the thread I linked.
V0latyle said:
ADB only works in Android or in recovery mode. Samsung devices don't have a fastboot mode.
Yep. Since you don't already have TWRP installed, follow "Method 2" in the thread I linked.
Click to expand...
Click to collapse
yep it does. i had a little bit of trouble between installing the first and second file. it kept reporting a corrupt operating system but i noteiced it cycled a reboot wo i held hte power and volume up buttons together when it cycled. this allowed me into rescue mode. from there i was able to power down the phone so i could reboot it back into download mode then upload the rescue file contained in the zip file mentioned. after that it booted ok but keeps claiming that the operating system isn''t offician but then boots into android ok. i expect installing the disable_drm_very app wil fix that. then i can try installign a new os.
but that's for tomorrow
Jjflick said:
I noticed this thread and would like to keep looking
Click to expand...
Click to collapse
i hope it helps you. i've detailed the steps i took as best as i could.