Related
Hello, First time Poster here, please bare with me...
I really shouldn't of touched this.....
I have an Atrix w/ the newest updates to it, and attempted to unlock the phone. Using the guide from atrix4ghacks.com Everything started well, then it failed while writing to the device. Now, when I attempt to boot, I get the message
SVF:405;1:2
Failed to boot 0x1000
1- RSD
2-Fastboot
3-NVflash
4- BP HW Bypass RSD
5-BP HW Bypass QC DLOAD
6-BP HW Bypass & Boot AP
7-BP HW Bypass BP only
8- BP SW Bypass RSD
9- Andriod recovery
10- Boot Andriod (no BP)
11- Device UID
12- Console
13- Early USB
14- BP tools
I can get into fastboot, though I honestly am not sure what to do from there. I have the fastboot s/w downloaded, along with the gingerbread OS. When I tried to execute the command via Command prompt. I keep getting unknown command errors (yes, directories within the command are good).
Did I just kill my phone?
I have found a few posts here related to this, though I havent found what seems to be a solid answer to a "fix" for this. I would highly appreciate if someone could try to help me with this.
Sorry, I have broken a noob rule (was pretty late when I watched the video), I thank you all in advanced for any help
STOP!!! YOU HAVEN"T KILLED YOUR PHONE JUST YET!
BUT IF YOU SBF YOU WILL!!!
Go into fastboot and repeat all of the unlock commands, reboot and your phone should boot fine after that.
Ok, I will give that a shot!
Hopefully this will work. THANK YOU!
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Grumbles said:
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Click to expand...
Click to collapse
Ugh... from what I heard the battery won't charge while in fastboot mode. You need a standalone charger or a different battery.
So, it doesn't let you get into fastboot at all, huh?
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Grumbles said:
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Click to expand...
Click to collapse
The factory cable would allow you to use the phone without the battery, but it might take more money and time to make then you think.
From what I understand, RSD threw you an error when you were flashing bootloader unlock.
Anyway, you need to find a way to charge your battery and they do the fastboot unlock commands.
If that doesn't work you need to reflash the pudding SBF, (make sure you install the drivers Windows x64 version here prior to flashing and that your phone is recognized in RSDlited)
Get the correct pudding file from here: http://forum.xda-developers.com/showthread.php?t=1136261
Use instructions here (start at step 1) : http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Note that after pudding is flashed successfully and you do the unlock commands, you will get a failed to boot error (seems like what you have now). You need to redo the unlock commands in fastboot and it will fix the problem.
Good luck.!
Alright!
Got the cable completed and works!
So, battery situation is handled, now to follow your steps
THANK YOU! I will report back and let you know.
Ok,
Clearly I am doing something wrong here.....
I followed the instructions using the newest Pudding_preroot.sbf file, and the RSD software sees the device (as a SE flash not a NS if that matters) and will start the flashing process.
Everything works to plan until the phone does its reboot(99$ executed), gives the fail to boot message again. Then wants to start back up in RSD mode.... The RSD application on the otherhand, it seems like its trying to switch the phone to"BP passthrough mode" I do not see that exact option, and after it failed while rebooting to RSD. I tried to move it to fastboot, BP HW Bypass RSD, and finally BP SW bypass RSD... All with the same failure on the RSD screen:
"Failed Flashing Process. Phone (0000): Error switching to BP Pass through mode (0x70BE); phone connected"
I have a funny feeling that this part is obvious, for that I am sorry for my ignorance.
I am pretty sure this thing is toast...
After getting nowhere after step 12, and multiple attempts to install the pudding_preroot file. I did some searching around and found multiple atrix users that would get the same issues. From the flash showing up as SE rather than NE, to the constant failing during the flash via RSD lite, with the same failure errors.
I noticed a "NV flash" option, and found this link that could establish a recovery USB driver to the phone. Do you think this maybe my next best route?
http://forum.xda-developers.com/showthread.php?t=1123429
My factory cable is good, so that option IS open..... Though I am starting to think this is toast.
We cannot use NVFlash unless we get the SBK (signature file). Currently, we do not have it. Motorola does, so plead to them
OK, well now it decided to only mount itself as a unknown APX device... Not sure the whats or whys there. Nothing has changed since the last failures?
Hey man, I think RSD shows the flashing process as failed since it can't fully reboot the phone.
Go into fastboot mode and try doing the unlock commands. (try this twice if ita fails after the first time).
In the worst case scenario if unlocking fails no matter what, you can flash a complete 2.3.4 rom via SBF and that should get you back up and running.
Let us know how it goes.
Remember, if you can get into RSD or fastboot - the phone isn't bricked yet!
Alright so my issue is I flashed an ics rom on my evo LTE but accidentally with the wrong firmware. When the update was just about done, the screen went black. No charge light when plugged into a charger and the device will not power on, or do anything(tried button combinations). However when I plug it into my computer,device manager sees my phone as “My HTC”. So it seems to have a connection but it doesn’t do anything to the phone. Fix possibly?
Sorry for asking such a basic question guys. New to the forums but definitely not new to flashing roms. This problem just confuses me to death.
Can you supply as much info as possible.
QUOTE=bigdaddy619;45718286]Can you supply as much info as possible.[/QUOTE]
Yes I can my friend. Of course, I got S-OFF with moonshine. Never had a problem there. Rooted also with moonshine as well. Flashed a lot of different jelly bean roms (CM, Meanbean) to see which one best suited me. Well after awhile I decided to give one of the ics roms a shot but the firmware version on my evo was for jelly bean only, not ice cream sandwich. Just as the flash of the ics rom was about finished, the screen went black. (Battery was above 50%). I tried every button combination, but nothing worked. Tried connecting it to a charger and the orange charge light wouldn't even come on. I even left it on the charger overnight, but no dice. So the phone is totally unresponsive to everything. One thing I did notice however is that when I tried connecting the phone to the computer, my computer makes the connection noise when it finds a
Usb device. Checked my device manager on windows and my phone shows up as "My HTC". So it seems as my computer has some type of connection to the phone. With that being said, would there be some way to use some unbricking software or any other way to unbrick my phone? (From what I see, I think the bootloader may be corrupted)
Since you can hear USB connection, I wonder if running fastboot devices from CMD would yield any results. Though I suspect you'd probably have to be booted to fastboot USB to see.
Sent from my EVO using XDA Premium 4 mobile app
scottspa74 said:
Since you can hear USB connection, I wonder if running fastboot devices from CMD would yield any results. Though I suspect you'd probably have to be booted to fastboot USB to see.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Would you know of what commands may work for my device? Cmd is new to me, or well at least when it comes to sending commands to phones lol.
Click the link in my sig. There is a guide for setting up ADB as well as commands in it.
FinZ28 said:
Click the link in my sig. There is a guide for setting up ADB as well as commands in it.
Click to expand...
Click to collapse
Thank you much sir. Here's what I found out. When I type the command "adb devices", nothing shows up. When I type in "fastboot devices" here is what it says:C:\Users\lisa\Desktop>fastboot devices
C:\Users\lisa\Desktop>fastboot devices
t♥☻ fastboot
guessing that's not a serial number, as it should be, but it recognizes my device as a fastboot device. Is there any hope of fixing this paperweight?
ADB commands only work when the phone is booted to the ROM, whereas Fastboot commands only work in the bootloader when connected via Fastboot USB mode.
Can you get to the bootloader at all?
FinZ28 said:
ADB commands only work when the phone is booted to the ROM, whereas Fastboot commands only work in the bootloader when connected via Fastboot USB mode.
Can you get to the bootloader at all?
Click to expand...
Click to collapse
The only way I can get to the bootloader is by using the command prompt. Otherwise, my phone remains inoperable.
What happens when you select the recovery option in the bootloader?
Meaning that fastboot shows my device is connected but I cant access it on my phone.
rwhittaker13 said:
Meaning that fastboot shows my device is connected but I cant access it on my phone.
Click to expand...
Click to collapse
Ah.
HTC bricked
I have the same problem with my lte. I wanted to boot into recovery mode and that was the end of my phone. I can't turn it back on, but when i connect it to my computer it makes the connection sound and thats it, my phone is still dark.
stasikbest said:
I have the same problem with my lte. I wanted to boot into recovery mode and that was the end of my phone. I can't turn it back on, but when i connect it to my computer it makes the connection sound and thats it, my phone is still dark.
Click to expand...
Click to collapse
What did you do prior to booting into recovery? Also, when you plug your phone into your computer, what does your device show up as?
Sent from my HTC EVO 4G LTE
Bricked Phone Stuck in Fastboot
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
juanrocklin said:
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
Click to expand...
Click to collapse
Use Fastboot to fastboot flash a recovery to your phone
Sent from my SPH-L710 using Tapatalk 2
juanrocklin said:
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
Click to expand...
Click to collapse
That's not a brick. Do as instructed above and install TWRP via fastboot.
Sent from my HTC EVO 4G LTE
Thanks
FinZ28 said:
That's not a brick. Do as instructed above and install TWRP via fastboot.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Bammm! Worked like a charm. Back in business. Thanks much!
*im not developer, neither noob i just like to share what I know*
Maybe this is a noob guide, but i did my best to share something helpful
before you go deeper, be sure to check your phone able to get into fastboot mode. If you cant, use REAL unbrick method instead
If your phone soft or hard bricked, bootloop, stuck on logo etc you know you are f***ed unless you know what should to do.
Some time ago bootlooped my phone, but i cant go to recovery, cant ADB because I forgot to enable USB debugging, my computer wont recognize my phone poperly because my phone mad at me, and my phone flickering like hell *party hard*. Maybe this is a brick not bootloop but whatever
Good friend of mine tell me what should to do
What you need:
Working PC with minimal ADB and fastboot installed //see the thread here, your phone's USB and ADB driver installed //download here if you dont have it
Working USB DATA cable
Custom recovery everything will do, as long as its compatible with your current android version. Rename the img to recovery.img
ROM you prefer everything will do, as long as its compatible with your current android version. Move to your SD Card
The power of will
Step:
1. Make sure your phone is turned off
2. Boot into fastboot mode, you will see some chinese message
3. Plug your phone to to your PC
4. Check if your PC at least know that you are pluged in your phone (check via device manager by 'plug and un-plug' your phone and check for 'appear and disappear' device , mine listed as it is was a modem.)
5. Move the recovery.img inside minimal adb and recovery folder root usually under c:/programfiles directory
6. Run the minimal adb and fastboot, check your device by using /adb devices/ command without backslash
7. If your device is not listed, dont worry. We still able to use the fastboot
8. Boot your phone into recovery mode by using /fastboot boot recovery.img/ command without backslash
9. Wait for few secs, and your phone should touched down to recovery mode.
10. Do wipe (data, dalvik, cache, system, internal)
11. Flash your prefered ROM
12. ..........???
13. Profit
Troubleshooting:
If your PC unable to recognize your phone completely, try using another usb cable, usb ports, uninstall-reinstall, plug-unplug, and make sure your phone in fastboot mode before you plug your phone to the PC.
Feel free to critics, I hope this helped you :fingers-crossed:
Thank you for all who helped me making this post.
McBubu_1337 said:
*im not developer, neither noob i just like to share what I know*
Maybe this is a noob guide, but i did my best to share something helpful
before you go deeper, be sure to check your phone able to get into fastboot mode. If you cant, use REAL unbrick method instead
If your phone soft or hard bricked, bootloop, stuck on logo etc you know you are f***ed unless you know what should to do.
Some time ago bootlooped my phone, but i cant go to recovery, cant ADB because I forgot to enable USB debugging, my computer wont recognize my phone poperly because my phone mad at me, and my phone flickering like hell *party hard*. Maybe this is a brick not bootloop but whatever
Good friend of mine tell me what should to do
What you need:
Working PC with minimal ADB and fastboot installed //see the thread here, your phone's USB and ADB driver installed //download here if you dont have it
Working USB DATA cable
Custom recovery everything will do, as long as its compatible with your current android version. Rename the img to recovery.img
ROM you prefer everything will do, as long as its compatible with your current android version. Move to your SD Card
The power of will
Step:
1. Make sure your phone is turned off
2. Boot into fastboot mode, you will see some chinese message
3. Plug your phone to to your PC
4. Check if your PC at least know that you are pluged in your phone (check via device manager by 'plug and un-plug' your phone and check for 'appear and disappear' device , mine listed as it is was a modem.)
5. Move the recovery.img inside minimal adb and recovery folder root usually under c:/programfiles directory
6. Run the minimal adb and fastboot, check your device by using /adb devices/ command without backslash
7. If your device is not listed, dont worry. We still able to use the fastboot
8. Boot your phone into recovery mode by using /fastboot boot recovery.img/ command without backslash
9. Wait for few secs, and your phone should touched down to recovery mode.
10. Do wipe (data, dalvik, cache, system, internal)
11. Flash your prefered ROM
12. ..........???
13. Profit
Troubleshooting:
If your PC unable to recognize your phone completely[B/], try using another usb cable, usb ports, uninstall-reinstall, plug-unplug, and make sure your phone in fastboot mode before you plug your phone to the PC.
Feel free to critics, I hope this helped you :fingers-crossed:
Thank you for all who helped me making this post.
Click to expand...
Click to collapse
Good work bro
The Hard Gamer said:
Good work bro
Click to expand...
Click to collapse
Thanks, its noob post so i dont expect anything special
McBubu_1337 said:
Thanks, its noob post so i dont expect anything special
Click to expand...
Click to collapse
It is a good help to those who are new to getting bricked
It shows waiting for device
Tommen1998 said:
It shows waiting for device
Click to expand...
Click to collapse
You may need to check some things:
Your PC actually know that you have inserted your phone. It doesn't have to know it's a phone (so it can be detected as unknown device or something similar, mine is detected as a modem)
Your phone is indeed in fastboot mode, you can tell yours is in fastboot mode by a Chinese message at the bottom of the screen
Change your cable data, make sure it is a cable data, not a normal charging cable
let me know if you need some help
McBubu_1337 said:
You may need to check some things:
Your PC actually know that you have inserted your phone. It doesn't have to know it's a phone (so it can be detected as unknown device or something similar, mine is detected as a modem)
Your phone is indeed in fastboot mode, you can tell yours is in fastboot mode by a Chinese message at the bottom of the screen
Change your cable data, make sure it is a cable data, not a normal charging cable
let me know if you need some help
Click to expand...
Click to collapse
Hello. I Tried a lot, but my PC doesn't recognise my phone. The phone is in fastboot mode. I've tried by changing cables too
same issue
Tommen1998 said:
Hello. I Tried a lot, but my PC doesn't recognise my phone. The phone is in fastboot mode. I've tried by changing cables too
Click to expand...
Click to collapse
I am also getting the same issue tried different cables but not working. Anyone please help me
The same issue. I think it's about getting it recognized in Fastboot mode. It's recognized in Android but not in Fastboot. All new devices are installed including those you get in Diagnostic 9091 mode (Power+V+). What do I need for Fastboot mode?
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.