Started with device on July 5th security patch Android Oreo 8.1. 100% Verizon device. Got replacement phone in the mail. No SIM inside. Turned it on. Plugged it in to a computer. Skipped past everything on setup. Turned on Developer options. OEM Unlock was grayed out.
Turned off automatic system updates in dev options. Turned on USB Debugging. Keep screen awake while charging. Ran ADB "adb shell pm uninstall --user 0 com.android.phone". Turned on wifi and waited a couple minutes in the chrome browser. Returned to Developer options and OEM Unlock was no longer grayed out. Ticked it.
Kept phone running for a few minutes. Turned device off and booted to fastboot. Still locked. Returned to system from bootloader. OEM Unlock still blue. Let apps update and also logged into Google account. Noticed OEM Unlock was staying unlocked through a couple reboots.
Decided to upgrade to Pie. Did it OTA. OEM Unlock stuck through the update. Shut down phone from system. Once phone was off I held down power button and the volume down button to take me to Fastboot mode. Ran "fastboot flashing unlock". BOOM! Got the the screen to say yes or no to bootloader unlock.
Device was erased because I chose yes. OEM Unlock grayed out again but in unlocked position? Hmm...ok with me. The strangest thing happened when I checked my IMEI when I was done. I had checked before I started also and I could have sworn there was different information than what I ended up with at the last check. Im tired..maybe just trippin out. The OEM Unlock toggle is available to toggle again.
hallr88 said:
Started with device on July 5th security patch Android Oreo 8.1. 100% Verizon device. Got replacement phone in the mail. No SIM inside. Turned it on. Plugged it in to a computer. Skipped past everything on setup. Turned on Developer options. OEM Unlock was grayed out.
Turned off automatic system updates in dev options. Turned on USB Debugging. Keep screen awake while charging. Ran ADB "adb shell pm uninstall --user 0 com.android.phone". Turned on wifi and waited a couple minutes. Returned to Developer options and OEM Unlock was no longer grayed out. Ticked it.
Kept phone running for a few minutes. Turned device off and booted to fastboot. Still locked. Returned to system from bootloader. OEM Unlock still blue. Let apps update and also logged into Google account. Noticed OEM Unlock was staying unlocked through a couple reboots.
Decided to upgrade to Pie. Did it OTA. OEM Unlock stuck through the update. Shut down phone from system. Once phone was off I held down power button and the volume down button to take me to Fastboot mode. Ran "fastboot flashing unlock". BOOM! Got the the screen to say yes or no to bootloader unlock.
Device was erased because I chose yes. OEM Unlock grayed out again but in unlocked position? Hmm...ok with me. The strangest thing happened when I checked my IMEI when I was done. I had checked before I started also and I could have sworn there was different information than what I ended up with at the last check. Im tired..maybe just trippin out.
Click to expand...
Click to collapse
Go to this link http://www.imeipro.info/check_lg.html and plug in your IMEI number. What does it say under buyer code and buyer name? Don't stop with the unlock command, you need to also unlock_critical. This will also wipe your device again but it is needed to flash the bootloader and to be "fully" unlocked.
Same site wrong checker
v12xke said:
Go to this link http://www.imeipro.info/check_lg.html and plug in your IMEI number. What does it say under buyer code and buyer name? Don't stop with the unlock command, you need to also unlock_critical. This will also wipe your device again but it is needed to flash the bootloader and to be "fully" unlocked.
Click to expand...
Click to collapse
\
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://imgur.com/a/mEKLSbZ
I didnt have to do the unlock_critical. Just the regular one.
So is finally unlocked? Maybe we can try after a factory reset on Pie?
siggey said:
So is finally unlocked? Maybe we can try after a factory reset on Pie?
Click to expand...
Click to collapse
I've already done a few factory resets in Pie and its holding tough.
siggey said:
So is finally unlocked? Maybe we can try after a factory reset on Pie?
Click to expand...
Click to collapse
I tried many ways to get in with Pie. If you can do it. Props
hallr88 said:
I tried many ways to get in with Pie. If you can do it. Props
Click to expand...
Click to collapse
I really think it can be done ,9nce that toggle is cooperating ,there is like there's some other step to enforce that toggle,like doing an OEM_UNLOCK permission or state change in the bootloader.I ran fastboot getvar all when toggle was enabled,there is a OEM unlock id =yes, how to pull that id idk,but I think there's still a way.
Aslo I inserted the sim with the OEM toggle enabled,but my sim was never recgonized,I guess uninstalling the com.andriod.phone is the radio,or modem? I feel like I was as close as ever just missing something Stoopid.
djmouse said:
I really think it can be done ,9nce that toggle is cooperating ,there is like there's some other step to enforce that toggle,like doing an OEM_UNLOCK permission or state change in the bootloader.I ran fastboot getvar all when toggle was enabled,there is a OEM unlock id =yes, how to pull that id idk,but I think there's still a way.
Aslo I inserted the sim with the OEM toggle enabled,but my sim was never recgonized,I guess uninstalling the com.andriod.phone is the radio,or modem? I feel like I was as close as ever just missing something Stoopid.
Click to expand...
Click to collapse
I tried as many permissions that I could think of when I got to that point. When I uninstalled the system app I realized that I had to get it back eventually so I did a factory reset with the toggle on and it stuck through it. I was like omg. lol Keep at it!
I also had the SIM unrecognized when I uninstalled com.android.phone. Stopped the connection to Verizon servers I think. Spoof server? JK. There's gotta be some type of encryption in whatever it says to Verizon.
i will try this if it is indeed working.
hallr88 said:
I tried as many permissions that I could think of when I got to that point. When I uninstalled the system app I realized that I had to get it back eventually so I did a factory reset with the toggle on and it stuck through it. I was like omg. lol Keep at it!
I also had the SIM unrecognized when I uninstalled com.android.phone. Stopped the connection to Verizon servers I think. Spoof server? JK. There's gotta be some type of encryption in whatever it says to Verizon.
Click to expand...
Click to collapse
I never did a factory reset when the toggle was in the blue,I figured that would reinstall com.andriod.phone.a factory reset will make you have to.go back and enable Dev options ,and your saying OEM toggle was on? I'm not sure that even happens on a Google varient .
djmouse said:
I never did a factory reset when the toggle was in the blue,I figured that would reinstall com.andriod.phone.a factory reset will make you have to.go back and enable Dev options ,and your saying OEM toggle was on? I'm not sure that even happens on a Google varient .
Click to expand...
Click to collapse
I think I may have updated to Pie before I actually did the factory reset. I knew I should have recorded my screen. Ok, I remember. I did the update to see if it would give me back my phone use and it didn't. So I ended up saying just factory resetting in Pie and it stuck and gave me phone use.
Anyone else try this, it's been two days...
Sent from my Pixel 2 XL using Tapatalk
gcodori said:
Anyone else try this, it's been two days...
Click to expand...
Click to collapse
I'm going to try today
---------- Post added at 10:59 PM ---------- Previous post was at 10:59 PM ----------
I have a replacement waiting for me at home
so the device is on 8.0..tried the method and no go
shooterlgk said:
so the device is on 8.0..tried the method and no go
Click to expand...
Click to collapse
Dang. Shoulda Skyped r sumthin. Hate good thoughts that come a little too late.
hallr88 said:
Dang. Shoulda Skyped r sumthin. Hate good thoughts that come a little too late.
Click to expand...
Click to collapse
well i still have it without a sim..i havent quit yet
Hmu
Tried it on pie, no sim, but I was active before. Oem unlock became blue, I could toggle it... But upon going into fastboot, all I got was when doing "fastboot flashing unlock" or unlock_critical was "flashing not allowed
Update: left it charging all day, upon checking up again after hours, the toggle became grey again.
Update 2: Indeed, all i get is FAILED (remote: Flashing Unlock is not allowed) and upon reboot oem unlock becomes grey again
hork-bajir12 said:
Tried it on pie, no sim, but I was active before. Oem unlock became blue, I could toggle it... But upon going into fastboot, all I got was when doing "fastboot flashing unlock" or unlock_critical was "flashing not allowed
Update: left it charging all day, upon checking up again after hours, the toggle became grey again.
Update 2: Indeed, all i get is FAILED (remote: Flashing Unlock is not allowed) and upon reboot oem unlock becomes grey again
Click to expand...
Click to collapse
So u had service on ur phone already, and u tried his method and u got that far?
shooterlgk said:
So u had service on ur phone already, and u tried his method and u got that far?
Click to expand...
Click to collapse
Had but not for couple months.
Related
This an incredibly easy way to OEM unlock your G4.
**NOTE** This software feature might not be avaliable on the carrier based versions of the G4 like, Verizon, Sprint ect.
If you have a preview unit or carrier unlocked version of the G4 then this will be very simple.
1. Enable Developer Settings, going into the software version info in the settings and then clicking on the build number 5 times.
2. Go back to the settings and you'll find the developer settings tab at the bottom by about phone, if you setting menu is in list view.
3. Go into the developer settings and you'll see Enable OEM unlock right under Enable Bluetooth HCI snoop log near the top.
4. When you click on OEM unlock it will prompt you that device protection features will not work while this is enabled.
5. Click Yes and reboot the phone.
6. Now you can OEM Unlock your G4!
Cm9aphla said:
This an incredibly easy way to OEM unlock your G4.
**NOTE** This software feature might not be avaliable on the carrier based versions of the G4 like, Verizon, Sprint ect.
If you have a preview unit or carrier unlocked version of the G4 then this will be very simple.
1. Enable Developer Settings, going into the software version info in the settings and then clicking on the build number 5 times.
2. Go back to the settings and you'll find the developer settings tab at the bottom by about phone, if you setting menu is in list view.
3. Go into the developer settings and you'll see Enable OEM unlock right under Enable Bluetooth HCI snoop log near the top.
4. When you click on OEM unlock it will prompt you that device protection features will not work while this is enabled.
5. Click Yes and reboot the phone.
6. Now your OEM unlocked!
Click to expand...
Click to collapse
What will change after this?
danromania said:
What will change after this?
Click to expand...
Click to collapse
This will Unlock the Boot loader on the G4, which will make rooting very easy.
Cm9aphla said:
This will Unlock the Boot loader on the G4, which will make rooting very easy.
Click to expand...
Click to collapse
Hello
You've tried this ? It works ? What's your carrier phone ?
Cm9aphla said:
This will Unlock the Boot loader on the G4, which will make rooting very easy.
Click to expand...
Click to collapse
How to root ?!
scumpicule said:
Hello
You've tried this ? It works ? What's your carrier phone ?
Click to expand...
Click to collapse
I use AT&T but my model is a preview unit AKA the Korean Model.
hoangnova said:
How to root ?!
Click to expand...
Click to collapse
You probably still needs to wait for someone to write a custom recovery for the phone and use it to flash SuperSU. Shouldn't take very long though as long as the phone is unlocked.
That is very nice from LG side to easy unlock bootloader, it will really easy to mods, custom recoveries, roms etc
Looks cool times for G4 development theard
shouldn't it be possible to integrate supersu to the kernel? in ramdisk or wherever chainfire said it was going to be put in custom kernels
Cm9aphla said:
This an incredibly easy way to OEM unlock your G4.
**NOTE** This software feature might not be avaliable on the carrier based versions of the G4 like, Verizon, Sprint ect.
If you have a preview unit or carrier unlocked version of the G4 then this will be very simple.
1. Enable Developer Settings, going into the software version info in the settings and then clicking on the build number 5 times.
2. Go back to the settings and you'll find the developer settings tab at the bottom by about phone, if you setting menu is in list view.
3. Go into the developer settings and you'll see Enable OEM unlock right under Enable Bluetooth HCI snoop log near the top.
4. When you click on OEM unlock it will prompt you that device protection features will not work while this is enabled.
5. Click Yes and reboot the phone.
6. Now your OEM unlocked!
Click to expand...
Click to collapse
Ok, done!!! Now how to I enter fastboot mode?
Works on tmobile?
gsxcorey said:
Works on tmobile?
Click to expand...
Click to collapse
Yes. But now what can I do with this at this point?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MicroMod777 said:
Yes. But now what can I do with this at this point?
Click to expand...
Click to collapse
In fastboot you can push supersu. Then dowload twrp.img flash it. Then you got root with custom recovery. Boom, bam, bing.
dontbeweakvato said:
In fastboot you can push supersu. Then dowload twrp.img flash it. Then you got root with custom recovery. Boom, bam, bing.
Click to expand...
Click to collapse
Ok, how do I get to fastboot? adb reboot bootloader doesn't work, just reboots device.
From what I understand. And I may be wrong. This doesn't actually unlock the bootloader, it just allows it to be unlocked.
Until LG release the unlock.bin or someone finds a workaround it won't work.
There's also no TWRP for this device yet.
Coming from a Nexus 5 which was easy as pie it's taking me some getting my head around.
That said it's early days and in sure we'll get root soon enough.
MicroMod777 said:
Ok, how do I get to fastboot? adb reboot bootloader doesn't work, just reboots device.
Click to expand...
Click to collapse
With device off hold down power and vol down, then plug in usb cable while connect to adb terminal. But i wouldn't try this unless you know what your doing, or if your rich and have another device when you brick this one...... Its happened already.
MicroMod777 said:
Ok, how do I get to fastboot? adb reboot bootloader doesn't work, just reboots device.
Click to expand...
Click to collapse
for me on H815 this command really works rebooting on fastboot mode : adb reboot bootloader
sure,after checked OEM unlock bootloader option
H818P is working.
Cm9aphla said:
This an incredibly easy way to OEM unlock your G4.
**NOTE** This software feature might not be avaliable on the carrier based versions of the G4 like, Verizon, Sprint ect.
If you have a preview unit or carrier unlocked version of the G4 then this will be very simple.
1. Enable Developer Settings, going into the software version info in the settings and then clicking on the build number 5 times.
2. Go back to the settings and you'll find the developer settings tab at the bottom by about phone, if you setting menu is in list view.
3. Go into the developer settings and you'll see Enable OEM unlock right under Enable Bluetooth HCI snoop log near the top.
4. When you click on OEM unlock it will prompt you that device protection features will not work while this is enabled.
5. Click Yes and reboot the phone.
6. Now your OEM unlocked!
Click to expand...
Click to collapse
That just "allows" for oem unlock that doesn't mean it's actually unlocked. You have to do the same thing on nexus 6 before you run the unlock command line. To my knowledge though the g4 is the same. It's a lollipop feature that you have to check that before you unlock bootloader.
Isn't OEM unlock just so you can use another sim? I don't think that unlocks the bootloader?
Hey guys,
now... i'm pretty sure my Redmi 3S is a goner and im f***ed at this point. Please read carefully as i tried SO many different things now.
(Short Disclaimer! NO! My Device doesn't boot anymore. NO! I didn't enable Developer Options or USB debuging... YES! My Bootloader is locked.)
Short story beforehand:
I got my 3S from Ebay and was pretty satisfied with it. After about a Month i realised, i didn't get any updates (which i should've just by Securitypatch date and a few things.)
So i found out that i was on a ShopROM which don't get any updates at all. Then i googled and found different tutorials on how to flash a new ROM.
I followed them point by point... But it ALWAYS ended up with Errors. After every "mistake" i tried turning it on which worked... That was until something went really wrong.
Suddenly i got stuck in a Bootloop. Only the "Mi"-Logo was on the screen and that was all it did.
Sooooo... I found out i bricked it. OKAY! After several hours of searching i came up with SOOO many different tutorials on what i can do.
One of the more popular ones where:
"just flash another ROM."... Jeah, didn't work. I got so many different errors that i can't even name them all.
"Bootloader locked, enable USB-Debuging in Settings (which i cannot do)..."
NOW i recently found another tutorial that involved the official "Mi Unlock App". So i registered... Wrote them my Story and a few hours later i got a message saying "OKAY. We give you access to the tool and grant you permission so you can unlock your Phone." Sweet i thought... Now... Time to get this to work...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hell Yeah... I even tried FOUR different versions of the tool by now... The ones at v1x couldn't verify my device and got stuck at 50%. Both the v2x ones behave the same as shown in the picture.
Now i found tutorial that claimed to flash a "locked bootloader" phone. I had high hopes... Did everything as the tut said...
And i can't simpyl unlock it with "minimal adb and fastboot"
And trying to install TWRP also fails as expected:
So... as stated above...
Locked Bootloader, no developer options or usb-debuging, not allowed to flash because of critical state, mi unlock won't work...
Is there ANYTHING i can do now? I read about this "deep flash" method by i'm not that into these things and don't have the tools to do this...
The ONLY thing i can do now is WAIT. I read a lot that people have to wait for about a week or even two to use "Mi Unlock". Which doesn't make sense to me as they granted permission
and the error that comes up doesn't remedy itself by wating. At least that's my interpretation.
Thx for reading!
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
After that try Mi Flash again. And don't care about security patch date. Our device have old security patch from april 2017.
Dont wait for the unlock code becuase it wont help. Post getting the code, your mi ID needs to be binded with the phone before you attempt the unlock.
Try the EDL mode even if the bootloader is locked(you'll need a usb cable to make your own flashing cable that helps to get in edl mode on a locked bootloader).Lookout for the videos on youtube. If this also fails which i am pretty sure should get you going, the last resort would be test point method. Refer to the test point guide on the miui forum.
Sent from my ONEPLUS A5010 using Tapatalk
Hey Krauzaa,
thx for the suggestion... Now i'm not sure if i did this right... At first i did what the manual said and i think i got it into EDL mode.
For the lols i tried to unlock it without success obviously.
After trying to flash it now i got this error with every flashing tool i have on my pc:
(of course i extracted it before. It's not compressed)
I tried then to paste the file on different harddrives but getting the same result. After i watched another videotutorial i suddenly got this!
No error or anything at all... The problem, as you can see in the screen, the part "Nothing at all" continued. Even after nearly two hours (got downstairs and played Mario Odysee )
it didn't do anything.
NOW first i have a question:
By "rebooting in edl mode", my device restart itself and is stuck on the "Mi-Logo" screen... Only by holding Vol- i go to the fastboor menu. What is right?
I don't get it. On Every video i watched the screen clearly shows the fastboot logo.
BUT i tested it anyways with both states... And suddenly i only get the "Critical flashing not allowed" error again without changing the setup.
Strange.
gillboyzz
Actually i already got the whole unlock thing and permission.
With the "selfmade cable" thingy... I'll try to look it up but i'm really a n00b when it comes to things like this. Thx for the suggestion tough.
Schnaki89 said:
Hey Krauzaa,
thx for the suggestion... Now i'm not sure if i did this right... At first i did what the manual said and i think i got it into EDL mode.
For the lols i tried to unlock it without success obviously.
After trying to flash it now i got this error with every flashing tool i have on my pc:
(of course i extracted it before. It's not compressed)
I tried then to paste the file on different harddrives but getting the same result. After i watched another videotutorial i suddenly got this!
No error or anything at all... The problem, as you can see in the screen, the part "Nothing at all" continued. Even after nearly two hours (got downstairs and played Mario Odysee )
it didn't do anything.
NOW first i have a question:
By "rebooting in edl mode", my device restart itself and is stuck on the "Mi-Logo" screen... Only by holding Vol- i go to the fastboor menu. What is right?
I don't get it. On Every video i watched the screen clearly shows the fastboot logo.
BUT i tested it anyways with both states... And suddenly i only get the "Critical flashing not allowed" error again without changing the setup.
Strange.
gillboyzz
Actually i already got the whole unlock thing and permission.
With the "selfmade cable" thingy... I'll try to look it up but i'm really a n00b when it comes to things like this. Thx for the suggestion tough.
Click to expand...
Click to collapse
That method won't work for new devices... I.e. Xiaomi patched that way in new devices... Only old Redmi 3S devices can support it... (Very old ;_
Btw. You can go to edl with test-point-method... There you can flash with MiFlash without unlocked bootloader
To use MiFlash does it need unlocked bootloader? Didn't knewed that ! Damn !
metro20 said:
To use MiFlash does it need unlocked bootloader? Didn't knewed that ! Damn !
Click to expand...
Click to collapse
All tools that use fastboot to flash images would require an unlocked bootloader.
Sent from my ONEPLUS A5010 using Tapatalk
gillboyzz said:
All tools that use fastboot to flash images would require an unlocked bootloader.
Click to expand...
Click to collapse
I really didn't knewed that ! Damn ! I'm using land with unlocked bootloader and custom rom , but hell thanks for the advice ! The next Xiaomi i'de buy certainly will unlock bootloader first !
If u stuck at bootlogo and tried miflash u have to wait for some days after u got message of grant permission coz the server isn't updated once it updates in days after then try it will work ur bl will be unlocked once unlocked flash twrp via fastboot mode and from PC well will get enter button to go twrp and then u can flash rom same happend with me but I used twrp and fastboot it solved my problems again plzz wait for some days after granting permission message it would work 100% I got message and after 4days I was able to unlock and now m using atomic os
Bootdead, HardBricked Land
Same here or worse can't showing any sign , no boot no edl no led , no screen , only led flashing when charging and that too blinking
Yesterday I've flashed rom via fastboot , redmi3 and it worked like a charm
Hello everyone, I have bricked my OnePlus 6T...well, actually it wasn't me who is the reason this happened. :/ Open Beta 3 user.
On Thursday, I was using my phone like I normally would, I was sending a screenshot to a friend which I cut down, and after I cut the picture down, I was writing a text to support the picture, now here is what the big issue comes in. The phone was freezing - I was like, ''alright I am on a beta afterall'', and this wasn't the first time this freezing happened. Suddenly, the phone just shut itself down and went black. After a few seconds, it boot up, but while doing so, it went into Qualcomm Crash Dump Mode, which I knew I've seen before, but not on my ''old'' 5T, which had - and still has the Open beta installed on it, for well over a year now.
This was a first time thing, I have never seen this mode on my phone before and i was panicking a bit and immediately went up to my laptop. I googled a bit, and I saw that this issue isn't a first time issue, it happened before on the OnePlus 6's Open beta firmware. And I was somewhat relieved, since I thought I may be able to fix this easily without loosing any data. Wrong thought.
After this, I tried reflashing the OS in fastboot, i downloaded fastboot ROM's and tried flashing them - one after another, none of them worked.
Then I tried to ask some friends at the OnePlus forum, since some of them have more knowledge than me, a lot more actually. They tried giving me solutions without losing any data, no luck. Then I was like ''alright, I'm f**ked, I need to give up on my data''. And since all of this happened suddenly without me having a chance to predict, I had no chance to backup any important data. Then I tried the msmdownloadtool, which firstly was a mistake, as I (as stupid as I am) used the OnePlus 6 msmdownloadtool, then i realized that I was using the wrong tool, and I downloaded the OP6T msmdownloadtool, too. After the download finished, I ran the tool with my 6T plugged in, it went through in about 300 seconds and my 6T was not booting up. Sometimes, it came to the boot animation and just crashed while booting.
Friday came and I tried the same thing over and over, no luck. I was busy doing other things, so I had not much time doing this all day.
Saturday was in and I tried the same stuff, but this time, I downloaded the msmdownloadtool with OOS 9.0.5 instead of 9.0.11, which made a very good first impression, the phone was booting up! But - I couldn't do anything and it froze on me and crashed. It was booting up, but...the system was unusable, I could drag the statusbar down and tap onto the navbar, but thats all I could do before it froze.
After this, the phone rebooted and went into Qualcomm Crashdump Mode, again! But this time, there was the usual text you get while the phone is in this mode, which was NOT there before. ''Normally'', the phone went into that mode with only the Qualcomm Crash Dump Mode showing up.
I tried everything i could, but no luck. The bootloader is locked again, so I can't flash anything over fastboot, recovery has been changed with the 6/6T anyway, so no OS flashing possible with that either, I am clueless right now and i would like you guys to help me out before having to send the phone back.
And as I could no see a thread regarding this particular issue, I was sure I could open up a new one.
If there are any language mistakes or whatever, bear with me, English is not my primary language.
Oh, now I kind of forgot to edit this - My phone is back working again after RMA.
no no,it's cool,it's readable, English is fine.Msm tool should fix it..good thing is that its not hardbricked,it's still alive and sometimes booting.thats a good sign.in my opinion some partition is cousing problems and is probably corrupt.Try flashing latest MSM for 6T few times in a row,let it overwrigh,and while I bootloader try to unlock bootloader ,and then before you let phone boot,in bootloader fastboot boot TWRP img.if TWRP works,you can try flash something ,maybe OOS again and TWRP zip and try it boot.
shawek said:
no no,it's cool,it's readable, English is fine.Msm tool should fix it..good thing is that its not hardbricked,it's still alive and sometimes booting.thats a good sign.in my opinion some partition is cousing problems and is probably corrupt.Try flashing latest MSM for 6T few times in a row,let it overwrigh,and while I bootloader try to unlock bootloader ,and then before you let phone boot,in bootloader fastboot boot TWRP img.if TWRP works,you can try flash something ,maybe OOS again and TWRP zip and try it boot.
Click to expand...
Click to collapse
Hi! Thank you for your answer, but everything you mentioned, i have tried it already, every time I try to do a fastboot command, it'll not work, as Oem unlocking is disabled in the OS, and I'm not able to enable it, as mentioned, I'm not able to enter the OS.
xnutzii said:
Hi! Thank you for your answer, but everything you mentioned, i have tried it already, every time I try to do a fastboot command, it'll not work, as Oem unlocking is disabled in the OS, and I'm not able to enable it, as mentioned, I'm not able to enter the OS.
Click to expand...
Click to collapse
Can you sideload the OOS zip via stock recovery?
MarcoLK said:
Can you sideload the OOS zip via stock recovery?
Click to expand...
Click to collapse
Let me see, what's the cmd command for doing so?
xnutzii said:
Let me see, what's the cmd command for doing so?
Click to expand...
Click to collapse
Just type
Code:
adb sideload nameofthefile.zip
while you are in sideload mode of the recovery
MarcoLK said:
Just type
Code:
adb sideload nameofthefile.zip
Click to expand...
Click to collapse
Oh, alright, thanks. I'l try
xnutzii said:
Oh, alright, thanks. I'l try
Click to expand...
Click to collapse
Did not work. It says ''cannot read (name).zip''
MarcoLK said:
Just type
Code:
adb sideload nameofthefile.zip
while you are in sideload mode of the recovery
Click to expand...
Click to collapse
Also, there is no sideload on the 6T's stock recovery.
xnutzii said:
Did not work. It says ''cannot read (name).zip''
Click to expand...
Click to collapse
Even I have the same problem while sideloading zips.
I thought it was just my PC. And I never found any working solution for it.
Have you tried the HydrogenOS msmdownloadtool?
This is the chinese Version of OxygenOS (the system is in english I think)
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-hos-9-0-4-t3875673
Edit:
There should be an option.
It should look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MarcoLK said:
Even I have the same problem while sideloading zips.
I thought it was just my PC. And I never found any working solution for it.
Have you tried the HydrogenOS msmdownloadtool?
This is the chinese Version of OxygenOS (the system is in english I think)
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-hos-9-0-4-t3875673
Click to expand...
Click to collapse
Yes, I have tried it as well, I was hoping it'd do anything, but it didn't. The phone gets to the boot screen sometimes, but mostly it'll go to the Qualcomm Crashdump Mode again
xnutzii said:
Yes, I have tried it as well, I was hoping it'd do anything, but it didn't. The phone gets to the boot screen sometimes, but mostly it'll go to the Qualcomm Crashdump Mode again
Click to expand...
Click to collapse
I am sorry but I am out of ideas.
Maybe other people have other ideas.
But you can request a repair and ask if they can repair it and if it is free.
MarcoLK said:
I am sorry but I am out of ideas.
Maybe other people have other ideas.
But you can request a repair and ask if they can repair it and if it is free.
Click to expand...
Click to collapse
No problem, thanks for your support.
That was my last option, if nothing helped.
Also, I just saw your edit, there is no option like this, there are ''wipe data and cache'', '' Advanced'' ''Exit''
You said MSM tool 9.0.11 doesn't recognize your device.. did you try to press start on the tool anyway with your device plugged in via USB?
Most times it doesn't seem to recognise my phone either but then I press start and it takes some time before it start doing is thing..
Hey m8 use MSM tool took about 10 attempts plus for the files to start downloading not sure why? But that is your answer just stick with it
xnutzii said:
Hello everyone, I have bricked my OnePlus 6T...well, actually it wasn't me who is the reason this happened. :/ Open Beta 3 user.
On Thursday, I was using my phone like I normally would, I was sending a screenshot to a friend which I cut down, and after I cut the picture down, I was writing a text to support the picture, now here is what the big issue comes in. The phone was freezing - I was like, ''alright I am on a beta afterall'', and this wasn't the first time this freezing happened. Suddenly, the phone just shut itself down and went black. After a few seconds, it boot up, but while doing so, it went into Qualcomm Crash Dump Mode, which I knew I've seen before, but not on my ''old'' 5T, which had - and still has the Open beta installed on it, for well over a year now.
This was a first time thing, I have never seen this mode on my phone before and i was panicking a bit and immediately went up to my laptop. I googled a bit, and I saw that this issue isn't a first time issue, it happened before on the OnePlus 6's Open beta firmware. And I was somewhat relieved, since I thought I may be able to fix this easily without loosing any data. Wrong thought.
After this, I tried reflashing the OS in fastboot, i downloaded fastboot ROM's and tried flashing them - one after another, none of them worked.
Then I tried to ask some friends at the OnePlus forum, since some of them have more knowledge than me, a lot more actually. They tried giving me solutions without losing any data, no luck. Then I was like ''alright, I'm f**ked, I need to give up on my data''. And since all of this happened suddenly without me having a chance to predict, I had no chance to backup any important data. Then I tried the msmdownloadtool, which firstly was a mistake, as I (as stupid as I am) used the OnePlus 6 msmdownloadtool, then i realized that I was using the wrong tool, and I downloaded the OP6T msmdownloadtool, too. After the download finished, I ran the tool with my 6T plugged in, it went through in about 300 seconds and my 6T was not booting up. Sometimes, it came to the boot animation and just crashed while booting.
Friday came and I tried the same thing over and over, no luck. I was busy doing other things, so I had not much time doing this all day.
Saturday was in and I tried the same stuff, but this time, I downloaded the msmdownloadtool with OOS 9.0.5 instead of 9.0.11, which made a very good first impression, the phone was booting up! But - I couldn't do anything and it froze on me and crashed. It was booting up, but...the system was unusable, I could drag the statusbar down and tap onto the navbar, but thats all I could do before it froze.
After this, the phone rebooted and went into Qualcomm Crashdump Mode, again! But this time, there was the usual text you get while the phone is in this mode, which was NOT there before. ''Normally'', the phone went into that mode with only the Qualcomm Crash Dump Mode showing up.
I tried everything i could, but no luck. The bootloader is locked again, so I can't flash anything over fastboot, recovery has been changed with the 6/6T anyway, so no OS flashing possible with that either, I am clueless right now and i would like you guys to help me out before having to send the phone back.
And as I could no see a thread regarding this particular issue, I was sure I could open up a new one.
If there are any language mistakes or whatever, bear with me, English is not my primary language.
Click to expand...
Click to collapse
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
hagar006 said:
You said MSM tool 9.0.11 doesn't recognize your device.. did you try to press start on the tool anyway with your device plugged in via USB?
Most times it doesn't seem to recognise my phone either but then I press start and it takes some time before it start doing is thing..
Click to expand...
Click to collapse
I never said it doesn't recognize my phone though. I know how the phone gets recognized by msmdownloadtool, thanks for your input though.
MRobbo80 said:
Hey m8 use MSM tool took about 10 attempts plus for the files to start downloading not sure why? But that is your answer just stick with it
Click to expand...
Click to collapse
I have flashed the sh*t outta my phone already, it doesn't work out sadly enough. I have tried everything besides this ↓
twinnfamous said:
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
Click to expand...
Click to collapse
This seems very unlikely, but I thank you for your input, let's see if this actually works for me. Hope I get the timing right.
twinnfamous said:
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
Click to expand...
Click to collapse
Alright, I've tried this now and it still says "boot is not allowed in lock state" :/
xnutzii said:
Alright, I've tried this now and it still says "boot is not allowed in lock state" :/
Click to expand...
Click to collapse
Sorry about your luck. The only thing I can recommend is trying the patched msmtool that is for converting from T-Mobile to global.
I had problems getting it to connect but what I did was power off device and held volume up and volume down even after plugging it in and pushing start.
Then when I got the error it didn't connect I unplugged it and plugged it back in all while still holding volume up and volume down. It took a few tries but it will connect.
twinnfamous said:
Sorry about your luck. The only thing I can recommend is trying the patched msmtool that is for converting from T-Mobile to global.
I had problems getting it to connect but what I did was power off device and held volume up and volume down even after plugging it in and pushing start.
Then when I got the error it didn't connect I unplugged it and plugged it back in all while still holding volume up and volume down. It took a few tries but it will connect.
Click to expand...
Click to collapse
The problem is not that the phone doesn't connect, it connects right away without any issues with the volume buttons clicked together, the msmtool runs through too! But the phone does NOT boot up after all of this is finished. It goes straight to Qualcomm crashdump mode.
UPDATE: The issue was resolved and here is the [SOLUTION]first of all lets start with the problem, it doesn't matter if it's just hard reset loop or update loop problem, I actually did both, here's a thing this main issue comes with updates but somehow this time recovery mode was completely destroyed, so there is no escape you can only access fastboot which is a good thing in a way, follow the steps to unbrick your phone.
-if you can access recovery mode just download modified miflashpro and flash downloaded rom using it.
REQUIRMENTS: PC,USB CABLE,INTERNET CONNECTION.
SOLUTION:1. Install ADB on your PC with all the necessary drivers for your phone
2. Turn off your phone completely, press and hold volume down and power button together to go into fastboot mode
3. once you are in fastboot mode connect usb to phone and open cmd from adb directory and type in: fastboot devices (if device serial number is shown in fastboot mode everything is good so far... if not go to DEVICE MANAGER in your pc and check if driver is installed properly if anything ADB drivers and ANDROID USB drivers will come handy to install them manually)
4. now type in: fastboot continue
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. your device will boot into system if it fails try going into fastboot mode and going with fastboot continue command again try until it boot ups into safe mode
6. eventually it will boot into safe mode system without your files being touched because nor update nor hard reset was completed fully, phone will be in airplane mode.
7. DO NOT TURN ON WIFI OR MOBILE DATA it will crash your phone, if your phone storage is full remove some stuff plus the apps.
8. Turn on USB DEBUGGING,OEM UNLOCK MODE. open file transfers and download apk of MIUI updater from pc to your phone ( LATEST VERSION ) and install it.
9. now DEACTIVATE AIRPLANE MODE and turn on WIFI FROM SETTINGS
10. once you got internet connection wait a little bit for all of the notifications and stuff to pop up be careful, once it's all good go to settings about phone and system update and CHECK FOR UPDATES
11. let your phone download the update it should be around 1.7GB depends honestly let it decrypt and once you are ready click on INSTALL NOW.
12. it will take time to install and reboot will happen many time you might think that it gets stuck at 90.49% but let it finish be patient it happens it just needs time, once everything is done you are good to go
WELCOME TO MIUI 12
SIDE NOTE:
I - MAKE SURE YOUR PHONE IS CHARGED
II - I DID TRY EDL TEST POINTS BUT YOU DO NOT NEED TO OPEN UP YOUR PHONE NOR TO DO IT.
III - BE PATIENT
F
Unless you're willing to do a test point boot, take it to a Xiaomi service center, take a receipt with you or some proof of purchase.
You can try buying an EDL cable and testing your luck, I highly doubt tho since Xiaomi locks it's EDL mode.
got good news I managed to actually get in the system
using fastboot continue command it lags as hell but usb debugging is on
so from the looks of it recovery is gone
I am in phone adb devices are visible
anything that you might suggest ?
it took me three times to do this but it finally managed to do something
I think it's safe mode and this is why it's not crashing yet
XDHx86 said:
F
Unless you're willing to do a test point boot, take it to a Xiaomi service center, take a receipt with you or some proof of purchase.
You can try buying an EDL cable and testing your luck, I highly doubt tho since Xiaomi locks it's EDL mode.
Click to expand...
Click to collapse
anyways phone is on and going well charging but is in airplane mode trying to flash rom using miflash but not working... recovery is most likely gone... any ideas guys what to do?
Update:turning wifi makes it crash
UPDATE II: WHATEVER HAPPENS DO NOT TURN ON WIFI IT WILL CRASH AND KEEP ON CRASHING UNTIL YOU GET LUCKY AND TURN IT OFF YOURSELF
UPDATE THREE: I NEED A WAY TO FLASH RECOVERY WITHOUT FASTBOOT AND BOOTLOADER IS LOCKED
You said your device is locked? If it's unlocked try flashing TWRP, and flashing a different ROM so this doesn't happen again.
Careful of rollback index when trying to flash a MIUI ROM so it doesn't cause a hardbrick.
XDHx86 said:
You said your device is locked? If it's unlocked try flashing TWRP, and flashing a different ROM so this doesn't happen again.
Careful of rollback index when trying to flash a MIUI ROM so it doesn't cause a hardbrick.
Click to expand...
Click to collapse
I mean device is locked... there is no way to unlock it with that MI account BS
is there a way to flash twrp?
XDHx86 said:
You said your device is locked? If it's unlocked try flashing TWRP, and flashing a different ROM so this doesn't happen again.
Careful of rollback index when trying to flash a MIUI ROM so it doesn't cause a hardbrick.
Click to expand...
Click to collapse
If i somehow manage to get into recovery even if I will be able to install it I will flash rom and it's over
You can't force flash TWRP. You'll have to wait those days with MI Unlock, that's the only way.
There is this thread about an unofficial method of unlocking, I didn't bother looking tbh since I'm very sure you can't unlock it unofficially, but if you do find something then do it on your own risk.
good news managed to get wifi to work now trying to download update from the phone it's slowly going lets see if it installs safely this time boyz will update
gotta admit was a rough one
NikoWulf said:
good news managed to get wifi to work now trying to download update from the phone it's slowly going lets see if it installs safely this time boyz will update
Click to expand...
Click to collapse
NikoWulf said:
View attachment 5248941 gotta admit was a rough one
Click to expand...
Click to collapse
Well that's good, I've never heard a Xiaomi update bricking a phone except MI A3 recent Android 11 update. So most likely it will work fine. Make sure you have enough charge in the battery.
Gotta ask, how did you fix it? Did you do a test point?
well it's not over yet my dude,lets see how it's going to update this one hopefully everything will work fine
well I did had to use test points for nothing lmao, plus tweaking with right drivers from device manager and stuff...
well lets hope it works out... it was a nightmare bud
XDHx86 said:
Well that's good, I've never heard a Xiaomi update bricking a phone except MI A3 recent Android 11 update. So most likely it will work fine. Make sure you have enough charge in the battery.
Gotta ask, how did you fix it? Did you do a test point?
Click to expand...
Click to collapse
well I can't leave it like that until the update cause I can see it's buggy plus I removed SIM
so airplane mode was deactivated
activated Wifi it works pretty decent rn laggy a bit but at least I am able to download so lets see where will this update take me
been stuck here for a while now
BOYS phone turned on without a problem ladies and gentleman
PROBLEM IS SOLVED
NikoWulf said:
well I can't leave it like that until the update cause I can see it's buggy plus I removed SIM
so airplane mode was deactivated
activated Wifi it works pretty decent rn laggy a bit but at least I am able to download so lets see where will this update take me
Click to expand...
Click to collapse
Well I know I'd want a way out of this fast, so if you're still looking for a way to flash another ROM I think Hydra tool can unlock bootloader through EDL mode.
NikoWulf said:
BOYS phone turned on without a problem ladies and gentleman
PROBLEM IS SOLVED
Click to expand...
Click to collapse
Although if everything is working fine then I advice against it.
XDHx86 said:
Well I know I'd want a way out of this fast, so if you're still looking for a way to flash another ROM I think Hydra tool can unlock bootloader through EDL mode.
Although if everything is working fine then I advice against it.
Click to expand...
Click to collapse
Thanks might try it out if this one gets funky again but so far everything is going smooth
Hi, this is my first post.
My Device: Samsung Galaxy Note 4
Model Number: SM-N910F
Build: MMB29M.N910FXXS1DQFB
Version: N910FXXS1DQFB//N910fXXS1DQA3
Android Version: 6.0.1
Qualcomm Snapdragon 805 APQ8084
My first attempt flashing my note4 ended with a brick, now it works again, but i don't know what went wrong. I already activated developer options, but there is no "oem unlock". I read a lot on XDA Forum and it is emphasized that it is important to unlock OEM/bootloader in order to modify the device. I already know that some Note 4 devices have a locked bootloader and some don't, an i assume i haven't a locked bootloader on my device, but i'm not sure.
Can anyone confirm that my Note 4 has already an unlocked bootloader?
Older phones do not have OEM.
To verify if your bootloader is unlocked read these steps.
Open the Phone app or the Dialer.
Enter the code: *#*#7378423*#*#
This should automatically open a new window.
Tap the Service info.
Open Configuration.
You should see one of the two messages:
– Bootloader Unlocked Allowed – Yes
– Bootloader Unlocked – Yes
@Samarimama -thank you, but this doesn't work without sim-card i guess?
I'm sorry, but the code doesn't work with my sim card.
Ok, take off your SIM card and try it again.
I've tried with and without SIM card: "Invalid USSD-Code". Any other options?
Try with ADBCheck from Your PCTo check your bootloader status from your PC, you’ll need to use an ADB and fastboot tool. Until recently, you needed to download the full Software Development Kit (SDK) to get to ADB and fastboot. But now, you can get this lightweight tool separately.
Step 1: Setting Up the Command PromptWhen you install the tool, you should:
Locate the path to the ADB and fastboot folder.
Click on the Start Menu and type ‘cmd’ until the Command Prompt icon appears.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Type the path to the ADB and fastboot folder in your Command Prompt. For example:
C:UsersUsernameDownloadsADB and fastboot
Step 2: Turning on the Fastboot ModeOnce the Command Prompt is set, you should set your phone to fastboot mode. To do this:
Turn your Android phone off.
Hold the Volume Down and Power/Unlock buttons at the same time until the phone turns on again.
When it turns on, release the Power button, but hold the Volume Down key until you see the bootloader menu. It should display the little Android bot lying on its back on a dark background, with a text under it.
Connect the computer and your phone with a data cable.
Step 3: Checking the StatusNow that everything is set, you can use the Command Prompt to check the status of your bootloader. To do this, you should:
Enter the ‘./adb devices’ command into the Command Prompt to check if ADB can locate your device. This should list your phone.
Execute the ‘./adb bootloader’ command to boot into bootloader.
Once you are in the bootloader, type the ‘fastboot devices’ command in the Command Prompt and execute it. If it lists a code, that means that the system can detect your phone.
Enter the ‘fastboot oem device-info’ command and run it. It should list some device data, including the bootloader information.
Look for ‘Device Unlocked’ from the info.
If it says ‘true’ next to it, it means that your device is unlocked. If it says ‘false,’ it means that that it’s still locked.
Sometimes, you can see this information right away in the bootloader display of your Android phone.
I agree with @Samarimama . Bootloaders are usually not locked on older phones, and the option to unlock it can not be found in developer options. However, my understanding is that bootloaders could be locked on carrier tied phones, most often USA-based, but those versions are usually not F, but some other letters. Unsure about the version you have.
I do believe tho that you should try and first update the firmware on that phone, since that does not seem to be the latest version. N910FXXU12DRI2, is the latest one, i have worked with several CSC-versions of it, and have yet to encounter one with locked bootloader.
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".
It is why we need to unlock the bootloader to flash a ROM.
prkfsz said:
I agree with @Samarimama . Bootloaders are usually not locked on older phones, and the option to unlock it can not be found in developer options. However, my understanding is that bootloaders could be locked on carrier tied phones, most often USA-based, but those versions are usually not F, but some other letters. Unsure about the version you have.
I do believe tho that you should try and first update the firmware on that phone, since that does not seem to be the latest version. N910FXXU12DRI2, is the latest one, i have worked with several CSC-versions of it, and have yet to encounter one with locked bootloader.
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".
Click to expand...
Click to collapse
I got my Note 4 from a friend in Austria, but i live in Germany, so i made a reset and this is why i never knew there is a firmware update for my Note 4. I only use it in Germany, and after the reset i have N910FXXS1DQFB//N910fXXS1DQA3. Is it really neccessary to flash the newer austrian firmware? It's a bit confusing for me, excuse me for being so dumb.
Samarimama said:
Try with ADBCheck from Your PCTo check your bootloader status from your PC, you’ll need to use an ADB and fastboot tool. Until recently, you needed to download the full Software Development Kit (SDK) to get to ADB and fastboot. But now, you can get this lightweight tool separately.
Step 1: Setting Up the Command PromptWhen you install the tool, you should:
Locate the path to the ADB and fastboot folder.
Click on the Start Menu and type ‘cmd’ until the Command Prompt icon appears.
Type the path to the ADB and fastboot folder in your Command Prompt. For example:
C:UsersUsernameDownloadsADB and fastboot
Step 2: Turning on the Fastboot ModeOnce the Command Prompt is set, you should set your phone to fastboot mode. To do this:
Turn your Android phone off.
Hold the Volume Down and Power/Unlock buttons at the same time until the phone turns on again.
When it turns on, release the Power button, but hold the Volume Down key until you see the bootloader menu. It should display the little Android bot lying on its back on a dark background, with a text under it.
Connect the computer and your phone with a data cable.
Step 3: Checking the StatusNow that everything is set, you can use the Command Prompt to check the status of your bootloader. To do this, you should:
Enter the ‘./adb devices’ command into the Command Prompt to check if ADB can locate your device. This should list your phone.
Execute the ‘./adb bootloader’ command to boot into bootloader.
Once you are in the bootloader, type the ‘fastboot devices’ command in the Command Prompt and execute it. If it lists a code, that means that the system can detect your phone.
Enter the ‘fastboot oem device-info’ command and run it. It should list some device data, including the bootloader information.
Look for ‘Device Unlocked’ from the info.
If it says ‘true’ next to it, it means that your device is unlocked. If it says ‘false,’ it means that that it’s still locked.
Sometimes, you can see this information right away in the bootloader display of your Android phone.
Click to expand...
Click to collapse
ADB does not recognize my Note 4. Debugging mode is already acitivated.
Me too I have this problem with the same phone. My PCs do not recognize him
prkfsz said:
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".
Click to expand...
Click to collapse
I already had twrp on my phone and i simply panicked while flashing a rom. After that it had a permanent bootloop, after taking out batteries it was impossible to switch it on. It happened some years ago, i used recovery software, made a factory reset and it works. And I still want to install a system that is not as old as 2017. I have a lot of patience, and i will find a way - if the bootloader is unlocked. Therefore i try to figure out if Note 4 has a locked bootloader or not. You say, Note 4 is that old, it hasn't any, and because twrp was on the phone already, it is unlocked. Then it seems to be a waste of time to try to use ADB to be sure. Instead i could try to flash it right now and don't care about unlocking something that doesn't exist on Note 4.
If you can go to TWRP, install the ROM you want with your phone and flash it with Gapps.
Old Lady said:
I got my Note 4 from a friend in Austria, but i live in Germany, so i made a reset and this is why i never knew there is a firmware update for my Note 4. I only use it in Germany, and after the reset i have N910FXXS1DQFB//N910fXXS1DQA3. Is it really neccessary to flash the newer austrian firmware? It's a bit confusing for me, excuse me for being so dumb
Click to expand...
Click to collapse
You're not dumb for not knowing something.. ;-)
It's hard to say if updating is totally necessary but it's almost always recommended to update your phone to the latest firmware before flashing custom ROMs. And I would say, especially since the last made firmware seems to have been made more that a year after the firmware you actually have on your phone I would strongly recommend updating to the latest firmware. It's not difficult, you go to settings and find where you choose to update and let the phone find the latest update itself while being connected to internet.
After that, if you already have TWRP installed, which I understand you do, just try and flash the custom ROM you want. But please remember to before that back up everything you want to save from the phone. And also make a twrp backup of the phone so you can restore it if something goes wrong. And read the suggested flashing procedure several times before actually doing it so you are familiar with it. If something goes wrong go to twrp and restore it from there.
Old Lady said:
I already had twrp on my phone and i simply panicked while flashing a rom. After that it had a permanent bootloop, after taking out batteries it was impossible to switch it on. It happened some years ago, i used recovery software, made a factory reset and it works. And I still want to install a system that is not as old as 2017. I have a lot of patience, and i will find a way - if the bootloader is unlocked. Therefore i try to figure out if Note 4 has a locked bootloader or not. You say, Note 4 is that old, it hasn't any, and because twrp was on the phone already, it is unlocked. Then it seems to be a waste of time to try to use ADB to be sure. Instead i could try to flash it right now and don't care about unlocking something that doesn't exist on Note 4.
Click to expand...
Click to collapse
What do you mean "panicked while flashing a ROM"? What did you do while flashing?
It is not a serious problem.
prkfsz said:
What do you mean "panicked while flashing a ROM"? What did you do while flashing?
Click to expand...
Click to collapse
Phone showed a litte red android while flashing but nothing seemed to happen for a long time, so i disconnected phone and pc. After that my phone didn't work anymore, now everthing is fine and soon i will try it once more - without disconnecting.