My daughter locked herself out of a nokia mediatek helio p22 by pin lock. During my relentless searching I came across an article showing how to use fastboot cmd commands to get the userdata pin password encryption and how to decipher it by taking out certain things. To be able to enter into the phone. I CAN'T FIND THE ARTICLE NOW!! . The phone itself will not hard reset by hardware keys. Will not enter into recovery mode only fastboot works. I've tried using many screen unlocking software but they all say device not supported o need usb debugging which I can't enable. Fastboot erase userdata ver throws up errors. Does anyone know the fastbood I'm looking for. I've tried all other possibilities that I can find. Any and all help would be greatly appreciated.
Fastboot operates on device's bootloader, not on Android OS. The FRP code is stored within Android file system what can only get accessed by ADB.
jwoegerbauer said:
Fastboot operates on device's bootloader, not on Android OS. The FRP code is stored within Android file system what can only get accessed by ADB.
Click to expand...
Click to collapse
Correct I know. But the device isn't recognized with adb only fastboot recognizes it. I've tried erasing the device with all fastboot commands and everything results in error. When I try to fastboot recovery it has the no command andriod guy and if I press any hardware buttons it reboot back to lock screen. Do u have any ideas on a work around. Or how to access the userdata using cmd promt?
Try to connect phone in USB-MTP mode via a USB-C cable - requires phone supports USB-C.
@Tlink00
Plug up to your PC and do:
sudo fastboot -w (push enter)
That will format data and erase everything on the device, pictures and all. If you are trying to get in your phone I've been able to delete lockscreen.db and a few other directories using TWRP file manager in the past on OnePlus 6t and also on a few Motorola phone's I've owned. But I believe you have to have encryption disabled to go that route. Best to just wipe it with fastboot -w. Just be sure you know your password to your Google account because if your phones signed in and has a Google account on it the password will be required to use the device again.
Tlink00 said:
My daughter locked herself out of a nokia mediatek helio p22 by pin lock. During my relentless searching I came across an article showing how to use fastboot cmd commands to get the userdata pin password encryption and how to decipher it by taking out certain things. To be able to enter into the phone. I CAN'T FIND THE ARTICLE NOW!! . The phone itself will not hard reset by hardware keys. Will not enter into recovery mode only fastboot works. I've tried using many screen unlocking software but they all say device not supported o need usb debugging which I can't enable. Fastboot erase userdata ver throws up errors. Does anyone know the fastbood I'm looking for. I've tried all other possibilities that I can find. Any and all help would be greatly appreciated.
Click to expand...
Click to collapse
I can send you tools that support the Nokia 2.2/2.3 (I'm assuming from chipset) that can erase user data and frp
areallydumbperson said:
I can send you tools that support the Nokia 2.2/2.3 (I'm assuming from chipset) that can erase user data and frp
Click to expand...
Click to collapse
Yeah...that be great! I'm willing to try anything. But the usb debugging isn't enabled.
flash713 said:
@Tlink00
Plug up to your PC and do:
sudo fastboot -w (push enter)
That will format data and erase everything on the device, pictures and all. If you are trying to get in your phone I've been able to delete lockscreen.db and a few other directories using TWRP file manager in the past on OnePlus 6t and also on a few Motorola phone's I've owned. But I believe you have to have encryption disabled to go that route. Best to just wipe it with fastboot -w. Just be sure you know your password to your Google account because if your phones signed in and has a Google account on it the password will be required to use the device again.
Click to expand...
Click to collapse
I've tried the fastboot -w but it comes up with an error about not having permission. Idk about the encryption being disabled or not. And I haven't been successful with TWRP even coming up. Maybe I'm missing something
jwoegerbauer said:
Try to connect phone in USB-MTP mode via a USB-C cable - requires phone supports USB-C.
Click to expand...
Click to collapse
Are you taking about changing it in the PC device manager properties? Bc I don't have access to change it on the device itself. I will try it though. I'll let u know what happens. Thanks for the idea!
Have found it that your Nokia 2.2 supports OTG.
Tlink00 said:
Yeah...that be great! I'm willing to try anything. But the usb debugging isn't enabled.
Click to expand...
Click to collapse
Doesn't matter because it uses fastboot and the way the tool works bypasses permission errors
areallydumbperson said:
Doesn't matter because it uses fastboot and the way the tool works bypasses permission errors
Click to expand...
Click to collapse
Ok thanks! I'll let u know if it works!
Tlink00 said:
Ok thanks! I'll let u know if it works!
Click to expand...
Click to collapse
did it work?
areallydumbperson said:
did it work?
Click to expand...
Click to collapse
I haven't had a chance to try it, yet. But I will really soon. I'm very eager to use it.
areallydumbperson said:
did it work?
Click to expand...
Click to collapse
It says request permission fail. I have phone in fastboot mode
Nvm I GOT IT!!! OMG u are a life savor. Thank you, thank you,thank you!!! I've been working on this for 2 months now. Thank u so much!!
Tlink00 said:
Nvm I GOT IT!!! OMG u are a life savor. Thank you, thank you,thank you!!! I've been working on this for 2 months now. Thank u so much!!
Click to expand...
Click to collapse
Haha np
Having the same issue here, my son locked his nokia with a passcode he can't remember. Unable to get it into recovery mode, stuck on "no command"
djekl said:
Having the same issue here, my son locked his nokia with a passcode he can't remember. Unable to get it into recovery mode, stuck on "no command"
Click to expand...
Click to collapse
should be able to get in by pressing power + volume up or power + volume down at that no command screen
Tried that, just got back from the local phone repair shop, and they were unable to factory reset it also, and get past the no command screen.
Related
Hello,
So I'm trying to unlock and root my tf700t now that my warranty is expired and hope for an ASUS update is diminishing. I downloaded the unlock app from the website and went through the procedure. It took a few weeks and several emails with ASUS support but I think it is unlocked. The reason I say I think its unlocked is whenever I reboot the device, I don't get the message that says its unlocked. The unlock app however says the device is unlocked. So is my device unlocked?
I operated under the assumption that it was and tried to install the twrp recovery using the minimal adb and fastboot exe file. My tablet is recognized by my PC and I put the tablet in fastboot. The error I get when I do that is a writing error. It says writing recovery.... FAILED <remote: <INVALID STATE>>. Does this mean that I am not unlocked or did I do something incorrectly? Any help would be appreciated. I've been working on this for a few weeks and really want to get it moving.
Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.
berndblb said:
Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.
Click to expand...
Click to collapse
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.
Jkeeper18 said:
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.
Click to expand...
Click to collapse
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.
sbdags said:
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.
Click to expand...
Click to collapse
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.
Jkeeper18 said:
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.
Click to expand...
Click to collapse
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.
berndblb said:
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.
Click to expand...
Click to collapse
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.
I am in the same boat - they think it is unlocked but it is not
The Asus v7 and v8 bootloaders both say "device is unlocked" but the fastbook info shows that it is not. I do not see any unlock inormation after the boot process starts. Also , the unlocker did not automatically restart my tablet. It also asked for my google credentials the first 5 times until the unlock said it worked. Now it does not ask that, it just says that it is unlocked. When I try to fastboot install the TWRP rom, it fails.
(remote - invalid state)
I called Asus and they have my tabler listed as unlocked. They are opening a case so that I can prove that it is unlocked.Then hopfully if they reset that setting, I can re-unlock it...
I was following this thread:
http://forum.xda-developers.com/showthread.php?t=2571542
Is there any work around? Please help!
I want TWRP and CM 10.2 on this slow TF700T tablet.
Thanks!
Jkeeper18 said:
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.
Click to expand...
Click to collapse
Well you typed fastboot device not fastboot devices.
Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk
berndblb said:
Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
No, I did not have two-step verification. I hope Asus creates a case and actually looks into it and resets my device's status in their system. It sounds like that is my only option -- a very lengthy and painful one.
I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
Well you typed fastboot device not fastboot devices.
Click to expand...
Click to collapse
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?
Jkeeper18 said:
I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?
Click to expand...
Click to collapse
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.
berndblb said:
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.
Click to expand...
Click to collapse
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.
Jkeeper18 said:
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.
Click to expand...
Click to collapse
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384
sbdags said:
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384
Click to expand...
Click to collapse
Sorry Im still new at this. Where is the fastboot folder?
Jkeeper18 said:
Sorry Im still new at this. Where is the fastboot folder?
Click to expand...
Click to collapse
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.
sbdags said:
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.
Click to expand...
Click to collapse
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.
Jkeeper18 said:
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.
Click to expand...
Click to collapse
I have followed the TF700 forums for the last year pretty extensively and until about 2 weeks ago never read about anyone having this problem: Asus database having you unlocked, but it actually isn't. Since then I think I've read about 4 cases.
My best guess: It's a problem with the v8 Unlock app or the way their servers store/process the information they get from the Unlock Tool.
That you got to a support person willing to contact Taiwan is a big plus already. Other users just ran into a wall of: We do not support unlocking this device.
So stick with the person you contacted already. Take pictures of your boot process (to document that it does NOT say: This device is unlocked) and they always seem to ask for a screen shot of your About Tablet page with your SN number and MAC address.
Persistence seems to be the key. And luck to get someone at Asus willing to help....
There is no other way to unlock the bootloader. So you would be limited to rooting the tablet which would give you more freedom to tweak it and uninstall bloatware, but you still would have to deal with the slow stock rom.... :fingerscrossed:
Hi
My phone is international NXT-L29
I was on Ephemeral B180 rom but i decided to upgrade it to get emui 4.1
I flashed back stock b180 rom, and after I flashed stock b321 rom
ROM works great but i would like to get root and twrp back again, but everytime I try to go through fastboot i get this screen on picture.
I logged into my dc unlocker again and followed the procedures (manufacture mode, unlocking,...) and dc unloccker tool informs that the phone was unlocked...but no, when I do adb reboot bootloader i still get the same message on the picture.
I saw other suggestions here on XDA, i confirm oem unlock is activated on developer options...i made factory reset and then "vol+- power" (with or without phone connected to PC) but i dont't get any option to unlock bootloader. I always arrive to a menu saying that the phone is looking for upgrade and tries until 5% is reached... (if I keep waiting it does not fisplat error message, only waits and waits and after a while it reboots normally (i don't have any dload folder either on phone or sd card)
Any suggestion to solve this is highly appreciated
many thanks
Try to get ur unlock code from huawei website maybe this can help.
Did you run the bootloader unlock command with your unlock code again?
Ephemera said:
Did you run the bootloader unlock command with your unlock code again?
Click to expand...
Click to collapse
the only command my phone accept is adb reboot bootloader
Then i get the screen of picture that I posted, which says that it is a cold reboot (?)
Whem I reach this point it doens not respond to anything else taht I type on Command line (I type fastboot oem unlock (and the code) but on pc screen i read 'ewaiting device' and nothing happens on phone
gm007 said:
Try to get ur unlock code from huawei website maybe this can help.
Click to expand...
Click to collapse
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Can I replace the stock boot.img that comes inside the UPDATE.APP file byone decrypted boot image of same rom?
If that would be possible then flashing this "modified" UPDATE.APP would solve the problem?
Many Thanks
pasil.pt said:
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Click to expand...
Click to collapse
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
grofock said:
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
Click to expand...
Click to collapse
I don't see any kedacom usb device folder...
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Ephemera said:
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Click to expand...
Click to collapse
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
pasil.pt said:
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
Click to expand...
Click to collapse
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
grofock said:
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
Click to expand...
Click to collapse
YES!!!!!!
many thanks to you. grofock, and to ephemera, and XDA
At last i got it done. (Huawei are so tricky compared to samsung...but at least they do not explode
gm007 said:
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
Click to expand...
Click to collapse
You were probably right because i recently changed PC and aeverytime w10 upgrades I pray...
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
timasan said:
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
Click to expand...
Click to collapse
try grofock's hints about control panel and Device manager on windows....
pasil.pt said:
try grofock's hints about control panel and Device manager on windows....
Click to expand...
Click to collapse
I try it on four different PCs and still error 43 "wrong descriptor".
timasan said:
I try it on four different PCs and still error 43 "wrong descriptor".
Click to expand...
Click to collapse
Maybe explain more what you did,what are you trying to do and which tools you used.
gm007 said:
Maybe explain more what you did,what are you trying to do and which tools you used.
Click to expand...
Click to collapse
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
timasan said:
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
Click to expand...
Click to collapse
Did you install hisuite it has all the drivers and make sure to enable allow hisuite to use hdb in phone settings under security.
So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus
mark_at said:
So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus
Click to expand...
Click to collapse
Did you already try ro flash ramdisk and system sith stock images via fastboot?
alohahe3000 said:
Did you already try ro flash ramdisk and system sith stock images via fastboot?
Click to expand...
Click to collapse
I would flash anything ... if I could! That is my problem at the moment and I can not solve it.
When I start phone I get into Huawei eRecovery after two tries to boot > does not help!
When I connect to PC > phone gets not detected! (during boot try it gets connected shortly ... but then gets disconnected after some seconds, in between I can not get into phone via PC)
So when I would want to use fastboot .... not possible because of that issue. I tried to connect in fastboot mode ... but no difference. Actually I do not understand why I can not connect to PC anymore!
The only way I can imagine now is flash or update something via SD card. I tried with asian update.zip, but it will only go to 5% .... and then ends.
But to be honest ... I am not very optimistic about finding any solution. I think only some very smart pro from this site might have an idea. But not sure if these guys read questions about bootloops.
mark_at said:
Next try was to force the phone to update with SD card.
Click to expand...
Click to collapse
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
here the link to the stock ROM:
https://mega.nz/#!W9hjiTgZ!_ZGq7V83bkWPF_Ue7_c41wVXNrQ_YjnsQUxRS0_MevU
Taobaibai said:
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
Click to expand...
Click to collapse
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!
mark_at said:
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!
Click to expand...
Click to collapse
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image. Stock system.img download link can be found in AOSP thread, second post.
alohahe3000 said:
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image.
Click to expand...
Click to collapse
Exactly
alohahe3000 said:
Stock system.img download link can be found in AOSP thread, second post.
Click to expand...
Click to collapse
Or just use my link. I copied it from the AOSP Thread
I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.
mark_at said:
I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.
Click to expand...
Click to collapse
It wasn't so difficult.
Viel Spaß mit dem Smartphone!!!
one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.
mark_at said:
one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.
Click to expand...
Click to collapse
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!
mark_at said:
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!
Click to expand...
Click to collapse
Never ever relock bootloader untill you have a backup plan. We have dload method till emui 7 buut not sure on EMUI 8 so can't suggest you anything at the moment. Someone played with EMUI 8 can guide you through it.
I understand that I was not allowed to relock bootloader! I feel awful and stupid about it ... believe me!
I was able to erase FRP with HCU client from DC Phoenix.
After that I was in phone again
And afterwards I could open the bootloader again.
Halleluja!!
Thanks for everyone's help here ...
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
Yes,there are several unbrick tools on the forum i used this one and it worked for me!
I am not able to share links so im posting a few screew shots but if you google oneplus 7 pro unbrick you ahould find this thread easy
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
I replied to you from the xda labs app and i couldnt attach a link but it works from the browser so i apologise for my first reply hope this one is more helpfull
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3934659/amp/
Hello.
Forgot PIN on my Galaxy S22 Ultra, and tried to remote unlock it using samsung find my mobile, but it says that I didn't enable remote unlock in settings. Any idea how to enable it through adb, if yes, please walk me through how to do it.
? Adb should be locked if your phone is locked, but this is not a problem.
1. Boot into fastboot mode.
2. Run this command on your PC:
fastboot -w
It will reset your phone without pin code.
If you has forgotten sim card code, so can you take it out.
Now go to settings, enable developer mode and OEM unlocking.
ekhaydarov said:
Hello.
Forgot PIN on my Galaxy S22 Ultra, and tried to remote unlock it using samsung find my mobile, but it says that I didn't enable remote unlock in settings. Any idea how to enable it through adb, if yes, please walk me through how to do it.
Click to expand...
Click to collapse
Reboot to recovery and select factory reset (all your data will be erased)
After this when device boot, it will start setup wizard and you will have option to unlock with your Google account that must be same as currently logged in Google Ac
To reboot to recovery : Connect device to PC
Reboot device - keep holding vol up +power
JonasHS said:
? Adb should be locked if your phone is locked, but this is not a problem.
1. Boot into fastboot mode.
2. Run this command on your PC:
fastboot -w
It will reset your phone without pin code.
If you has forgotten sim card code, so can you take it out.
Click to expand...
Click to collapse
The thing is I can't lose my data. is there any workarounds?
even if I reset it, what is the probability of recovering all data ?
Thank you!
I think your phone is Qualcomm, use Edl mode to backup your partitions with qfil tool
JonasHS said:
I think your phone is Qualcomm, use Edl mode to backup your partitions with qfil tool
Click to expand...
Click to collapse
can you walk me through it ? I really don't have any idea about qfil and edl
and I dont really know if my USB debugging is on or off
It would be super helpful
ekhaydarov said:
can you walk me through it ? I really don't have any idea about qfil and edl
and I dont really know if my USB debugging is on or off
Click to expand...
Click to collapse
It does not matter whether USB debugging enabled or not , if your phone is locked adb will not work
Any other ways to restore data ?