Need help getting back to stock from weird FW - Fire HD 8 and HD 10 Android Development

Hello,
I bought a Fire HD 8 (2018) from ebay, but it gives me some headaches. There is almost nothing on it, no playstore (neither amazon nor google), no browser, only six basic apps like a calculator. And there is something called WebView Browser Tester. When I enter Recovery and do a factory reset it reverts to this exact stage. I was able to use adb to install VLC Player but it acts a little strange. But when I install Google Playstore (+ Framework, Account Manager, Services) it will crash. Rebooting after that will end in a bootloop, that can only be broken by several attempts trying to get into recovery and do a reset.
So, I think this device once belonged to a developer. It also identifies itself as "kayak" in recovery menu. So I assumed it was unlocked at some point. But when I try to use fastboot to flash it, it states "locked hw". ADB sideload is not available.
I don't know what to do right now. I spend last night doing research without much success. Pretty much all Unlock-Tutorials assume that you are on stock firmware, and the ones for getting back to stock assume you have twrp installed which is also not the case here.
Hope somebody can help me getting this thing working again.
Thanks in advance,
Scoop

Can you unlock the BL

Well, I'm not quite sure how to do that. I only started to dive into the topic by yesterday. Do I have to setup a linux system to do that or is there another way?

Bro…. What are you trying to do if you did not unlock the BootLoader. Just follow a normal guide. Google.

Google brought me here ^^ I wanted to aks if there is en easier way to unlock it then opening it up and setting up a linux boot drive, given that the device has clearly been tinkered with before. I thought, it might be a "known" custom rom that has been to it flashed before. Just trying not to brick it...
But thanks for your answer.

I meant using fast boot….

Now you got me confused. I'm really sorry, but could you be a bit more specific? When I try to use the unlock command I'm always getting the error "the command you input is restricted on locked hw".

scoop111 said:
Now you got me confused. I'm really sorry, but could you be a bit more specific? When I try to use the unlock command I'm always getting the error "the command you input is restricted on locked hw".
Click to expand...
Click to collapse
do these (not at the same time, wait to boot into bootloader then do second and third cmd)
Code:
adb reboot bootloader
fastboot flashing unlock
fastboot reboot

That's exactly what I did. I also tried fastboot oem unlock instead of fast flashing unlock. But I'm always getting the same error "command restricted on locked hw".
I read on some site that "OEM unlock" must be enabled in developer options to have this working, but there is no such option.

ohhhhhh. Then your device is not unlockable.

I managed to unlock it via the hardware mod, but I'm stuck after that. It won't boot into recovery. Is there a way to flash the firmware just with fastboot access?

scoop111 said:
I managed to unlock it via the hardware mod, but I'm stuck after that. It won't boot into recovery. Is there a way to flash the firmware just with fastboot access?
Click to expand...
Click to collapse
If you did the hardware unlock all the way through, you should have TWRP recovery. From that you can flash anything.

scoop111 said:
I managed to unlock it via the hardware mod, but I'm stuck after that. It won't boot into recovery. Is there a way to flash the firmware just with fastboot access?
Click to expand...
Click to collapse
Can you message me in Telegram?

Have you had any success?
I have the exact same issue, and this is pretty much the only topic that shows up when searching "Kayak".
Fire Toolbox v30.3 doesn't like it either
'Codename "kayak" isn't supported/recognized by the Toolbox. Please plug in a supported Fire tablet and try again.'

What model is on the back there are hardware revisions of the 8 2018 L5S83A: Normal OG revision K29A5E: Pre production model for patching CLK Exploit

Related

Latest update MHC19J how to flash twrp

So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
What are you talking about? Before unlocking have you checked OEM unlocking from Developer tools? After this you need to flash Twrp, boot into it directly from bootloader and flash SUPERSU. That should be the minimal steps in order to keep the custom recovery in place.
HaiKaiDo said:
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
Click to expand...
Click to collapse
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
You do need some knowledge so take a look at the howto conversation http://forum.xda-developers.com/showthread.php?t=3206930
, this is my go to tool since my Nexus 4 http://forum.xda-developers.com/showthread.php?t=3258492
Darke5tShad0w said:
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
Click to expand...
Click to collapse
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
HaiKaiDo said:
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
Click to expand...
Click to collapse
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
wtoj34 said:
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
HaiKaiDo said:
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
Click to expand...
Click to collapse
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
wtoj34 said:
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
Click to expand...
Click to collapse
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Well i went and redid everything the same way I did the first time and it worked! I must done something stupid the first time. Guess this thread was for nothing! xD Thanks for clarifying some things for me though guys.
HaiKaiDo said:
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Click to expand...
Click to collapse
Disabling encryption does give you a speed increase. It may or may not be noticeable for your use but the majority can see the difference.
So you have to decide between security and a snappier phone.
Just remember to back all your data up as this requires wiping your data and possibly a clean flash and either switching from the stock rom to another rom(Most have the forced encryption disabled) or when on stock rom either flash another kernel or flash supersu in systemless mode.
Hotspot need it Help! Nexus 5x
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Varsismaname said:
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Click to expand...
Click to collapse
You need to go and start your own thread in the q&a section, its not polite to high jack someone else's.

I broke it

Update: The guys at Razer are just about as clueless as a retail phone carrier. They told me to do the exact same thing, the factory reset and all that, but they don't know what they're doing.
So FYI: IF YOU'RE BOOTLOADER IS LOCKED AND YOUR OS WON'T START, YOU'RE SCREWED.
Okay so I rooted the phone on Oreo, the second to last update, and tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again.
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it.
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader.
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------
Dashaquavius said:
Okay so I rooted the phone on Oreo, the second to last update, sand tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again..
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it..
Click to expand...
Click to collapse
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Roxas598 said:
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader
Click to expand...
Click to collapse
iliais347 said:
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
Click to expand...
Click to collapse
waiflih said:
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Click to expand...
Click to collapse
1. I didn't flash TWRP with the bootloader in the locked state, it was while it was unlocked.
2. Out of desperation, after flashing the stock images multiple times (while it says errors and maximum download reached and stuff) I re-locked the bootloader with the command thinking it would finally at least boot into the OS, to no avail.
3. Factory images didn't flash without some kind of error.
4. I'm unable to run any kind of commands, it says it's not allowed.
5. I've flashed multiple times, flashed the previous updates and the latest updates, and there's always some kind of error or it's not allowed.
I'm just gonna contact Razer. Apparently, I can't flash anything if the bootloader is locked? And the phone won't even boot into the OS to let me tick the option? I think I'm screwed.
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
waiflih said:
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
Click to expand...
Click to collapse
It says flashing is not allowed for everything.
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
waiflih said:
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
Click to expand...
Click to collapse
I just got off with Razer support, they're just gonna send me a new one.
And apparently, absolutely NO OTG support!
Let this thread serve as a warning..
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
parky169 said:
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
Click to expand...
Click to collapse
Interesting. I sent 2 phones with speaker issues and they offered a replacement for both and gave me shipping labela.

Can’t get out of bootloader

Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
I forgot to mention that when I try to use the and side load it says something about the e drive, like if there es no drive on my phone
rectangularspace said:
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
Click to expand...
Click to collapse
Do you know and understand how you use fastboot or the Deuces script to flash factory images to return you to stock OS?
Well not really. But I follow many instrucciones from differents post and nothing
rectangularspace said:
Well not really. But I follow many instrucciones from differents post and nothing
Click to expand...
Click to collapse
Read over this thread. Then let us know if you need help. https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Also, if you have twrp installed, you can flash the OTA zip that corresponds to your current OS version :good:
I do have twrp installed the problem is that I don’t have the zip on the phone to install the ota file.
Try with deceus Script (Just search for it) and select repair bootloop. It will download the factory Image and flash it on a and b partition then your phone will boot again. But your data will be lost :/
Ok., I will let you guys know thank you
Also, I forgot to mention that it looks like that I don’t have a OS installed ( twrp is telling me that every time i try to get out to the get out of the twrp menu. At this point i haven’t don’t anything mention in this post because I’m resetting my computer nd I’m installing right now the android sdk software.
You don't have to install the full Android SDK software for the job you're trying to do. You can download the latest Fastboot commands and ADB through Google, or even XDA(somewhere).
I've installed adb to my Windows commands, so once in recovery, when I need a file, I just "adb push file.zip /sdcard/".
No worries though. You'll be back up and running. ?
Edit: Also, if you still have data on your phone, you can check using the file explorer on TWRP. If you do, you can adb pull anything you want to keep.
@rectangularspace Link to the standalone platform tools HERE. This is all you need.
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Yes, but going down from 9 to 8 will cause/require a data wipe.
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Why did you decide to install Oreo?? There will be no further security or functionality updates for 8.1. The next monthly update to Pie should be the first Monday of next month (October 1st) if you don't get a OTA nag before then.
I have the update available to install on my settings. But what I'm looking for is to start over on rooting my pixel 2 xl. But after last experience I'm a little conservative when it comes to mess with the phone. I'm reading right now the post where it says to do the critical unlock for the phone but I don't know witch bootloader version I have. Can you guys help me out
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
rectangularspace said:
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
Click to expand...
Click to collapse
You only need to do the unlock process one time, BUT there are two separate unlock commands which include unlock_critical. If in doubt you can use fastboot device-info or getvar to check the current status. Make sure you are using the latest version of the platform tools I linked to above. One word of caution... don't EVER re-lock your bootloader or you WILL run into problems. Even if you are returning the phone to Google for RMA you do not need to re-lock it.
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
rectangularspace said:
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
Click to expand...
Click to collapse
I meant the only way to lock the bootloader will be thru a fastboot command.
rectangularspace said:
I meant the only way to lock the bootloader will be thru a fastboot command.
Click to expand...
Click to collapse
Yes, once you have successfully unlocked the phone in fastboot using the two separate commands, you will never have to do it again, AND flashing anything will not re-lock the bootloader. Please read over Nathan's GUIDE HERE to confirm you have done this correctly (and completely). Once this is done you can flash OTA's , full Google images, custom roms, etc. Lastly, if you are properly unlocked you cannot brick your phone. No matter how bad it gets, you will always have a path to restore the phone to it's original state. Don't hesitate to take the OTA being offered on your phone. It will take you to 9.0 without losing data or locking anything. :good:

Question Re-lock Bootloader? Help needed, thx!

One question, I don't usually open a new thread for something like this. I've already searched here and Google Search anyway.
Has anyone found out how to re-lock the bootloader? "Fastboot flashing lock" or "fastboot oem lock" ends in a softbrick.
For info, rooting and safety net did not work for me. Don't know if it helps to lock the bootloader again and start over.
Grateful for any help!
How it sounds like you have tried rooting your phone but failed?
Maybe you could explain your current phone situation in more detail.
It looks like you have the "patched" boot .img on your phone.
Flying Fox said:
One question, I don't usually open a new thread for something like this. I've already searched here and Google Search anyway.
Has anyone found out how to re-lock the bootloader? "Fastboot flashing lock" or "fastboot oem lock" ends in a softbrick.
For info, rooting and safety net did not work for me. Don't know if it helps to lock the bootloader again and start over.
Grateful for any help!
Click to expand...
Click to collapse
If you're rooted then you need to un-root. Just install the default rom over itself. (If you have the default boot.img you can use fastboot to flash it)
Then reboot into Fastboot and run "fastboot oem lock", you should then get a prompt, it WILL wipe the device.
noname122414 said:
How it sounds like you have tried rooting your phone but failed?
Maybe you could explain your current phone situation in more detail.
It looks like you have the "patched" boot .img on your phone.
Click to expand...
Click to collapse
Don´t think so, but maybe I took the wrong one. But some other users talk about the same issue. I´ll try to find the right one. Maybe somebody has a link.
My situation: I have the EU-model. Rooted two phones using exactly the same steps. One time it worked, the other time not. One the second one, I get no safety net. Also, netflix, for instance, is not working. Tried already every stuff I could find here... thx for your answer.
djsubterrain said:
If you're rooted then you need to un-root. Just install the default rom over itself. (If you have the default boot.img you can use fastboot to flash it)
Then reboot into Fastboot and run "fastboot oem lock", you should then get a prompt, it WILL wipe the device.
Click to expand...
Click to collapse
That all I did.. maybe I got the wrong boot.img. Searching for a link. Thx anyway and nice WE!
Just double check your version's and flash them. You can also try to wipe your device before you lock it again, sometime that helps
Ok, haven´t found any solution. Took the right boot.img. Whenever I want to lock the bootloader, it shows me "device is corrupt" or something like that.
Problem is that after root I cannot pass safety net. Also apps like Netflix don´t work.
The app "Safety Net Checker" tells me to lock the bootloader and to do a factory reset...
Any solution somewhere? Thx
It's probably stupid, but have you tried to lock bootloader in Developer options? (I'm newb)
Edit: don't
Can you unlock and boot into the OS? If so, take the OTA local upgrade to the same version OS version you are currently running. Do this twice (so both slots gets written) then try oem lock.
drozd128 said:
It's probably stupid, but have you tried to lock bootloader in Developer options? (I'm newb)
Click to expand...
Click to collapse
Don't do this. You shouldn't even be able to do this, but if you somehow do it, your only way out will be MSM
Your only problem seems to be safety net pass, which can be solved. There are tons of guides for the OnePlus 8 which work for your phone too.
craznazn said:
Can you unlock and boot into the OS? If so, take the OTA local upgrade to the same version OS version you are currently running. Do this twice (so both slots gets written) then try oem lock.
Don't do this. You shouldn't even be able to do this, but if you somehow do it, your only way out will be MSM
Click to expand...
Click to collapse
Thanks. That was the trick, I did it twice and I was able to re-lock now.
After unlocking a further time and trying to root, I again was not able to pass safety net. Strange, have two devices here. One did it without any problem, the othder not.
Did the same procedere again, re-locked the bootloader. Now the button for oem-unlock in the developer settings is greyed out. So no possibility to unlock again..
Is there another trick or work around?
Anyway, thanks for all advices and help here!!
Edit: Sorry, tired after 25hrs working... Wifi / data connection was off. Now next try...

Question Fastbook flashing unlock not recognized?

Hi guys, I'm stucked at this weird problem, basically when I type that command, fastboot reply with the list of options, like the command itself doesn't exist. Funny things is, to confirm it should work, I've tried to launch it with the device connected but not in fastboot, and it says "waiting for device" so the command actual exists.
I've tried so far: dl the last adb sdb from the official page
put the phone through fastboot using adb fastboot devices (it works)
launch the command: nothing works
This is hmm my 4th? Oneplus, so isn't like I'm new to unlock bootloaders but now I'm stucked, any ideas?
Of course OEM debug is on and also OEM unlock
ps.: I've also tried the old command but no resuts
here is the proper fastboot stuff you need. https://www.mediafire.com/file/xy5ifa0k1bz7tn4/fastboot.7z/file
with this one, fastboot flashing unlock
MrSteelX said:
here is the proper fastboot stuff you need. https://www.mediafire.com/file/xy5ifa0k1bz7tn4/fastboot.7z/file
with this one, fastboot flashing unlock
Click to expand...
Click to collapse
Ty, I've done it properly but sadly, I'm in the loop now, because following the guide to unlock:
because of the mismatch of the step 3 (which stated correctly I guess, "init_boot", and the pic, I've wrote boot instead of init_boot and flashed the patched magisk file to the boot.
Do you know/have where find the correct boot file to patch it back? My model is the CPH2449 A09 BA (europe) for what I remember...
Or, what guide can I follow withouth worst the situation... For now, I can still enter in the fastboot mode
If you flash init_boot to boot, it will hard brick your device. If you can't access fastboot now, then only way to recover is using MSM tool.
surajpai524 said:
If you flash init_boot to boot, it will hard brick your device. If you can't access fastboot now, then only way to recover is using MSM tool.
Click to expand...
Click to collapse
Yes I've noticed...someone helped me for 20 bucks from telegram so now its working...btw my mistake is due to the guide in the first post, as the pic there SHOWS to flash it to BOOT instead of INIT, please fix the guide and check it 200x times before post it wtf...
takui said:
Yes I've noticed...someone helped me for 20 bucks from telegram so now its working...btw my mistake is due to the guide in the first post, as the pic there SHOWS to flash it to BOOT instead of INIT, please fix the guide and check it 200x times before post it wtf...
Click to expand...
Click to collapse
I know.. That's why I used the other method to root. KernelSU method.
PROPER CPH2451 Root and Update instructions
This is for the CPH2451 Rom, but should also work for other roms. I have returned my device so I will not be updating this with future updates. I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or...
forum.xda-developers.com
surajpai524 said:
I know.. That's why I used the other method to root. KernelSU method.
PROPER CPH2451 Root and Update instructions
This is for the CPH2451 Rom, but should also work for other roms. I have returned my device so I will not be updating this with future updates. I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or...
forum.xda-developers.com
Click to expand...
Click to collapse
oh thanks for the link, ill check it after it finish to copy data from old one...this time it needs 1 hr (before 5 mins...lucky, without reason)... it worked for u then? Ok!
takui said:
oh thanks for the link, ill check it after it finish to copy data from old one...this time it needs 1 hr (before 5 mins...lucky, without reason)... it worked for u then? Ok!
Click to expand...
Click to collapse
Yes.. this method just needs booting and no hard flash. Also unlock bootloader and try setting passcode or patern before you copy data. If you can't set pattern, then relock and unlock bootloader till possible.
surajpai524 said:
Yes.. this method just needs booting and no hard flash. Also unlock bootloader and try setting passcode or patern before you copy data. If you can't set pattern, then relock and unlock bootloader till possible.
Click to expand...
Click to collapse
hey, did you perhaps found a way to fix fingerprint/passwords not working too? I guess that it is broken because I had one before unlocking it...so maybe locking it back, removing old one (if works) and unocking again, could work but...I'm still trying to figure out how to lock it back...maybe with enhanced tools... any ideas? Maybe I'm overthinking?
takui said:
hey, did you perhaps found a way to fix fingerprint/passwords not working too? I guess that it is broken because I had one before unlocking it...so maybe locking it back, removing old one (if works) and unocking again, could work but...I'm still trying to figure out how to lock it back...maybe with enhanced tools... any ideas? Maybe I'm overthinking?
Click to expand...
Click to collapse
Only is to fix phone lock issue is by relocking bootloader and unlocking it till it works. This must be done only if not rooted. No other method was found till now.
I've tried at least 5+ times, nothing. I've read first we need to flash stock then lock again, but idk how to flash stock frankly....now desperately I'm flashing it through enhanced fastboot tool, even if a guide said to avoid cuz some op10R got bricked... let's see....

Categories

Resources