Hello, I have moderate experience as an Android developer but I don't know much about custom ROMs.
Last weekend my cell phone died and for a temporary replacement I walked into an iffy local repair store and asked them for the cheapest Android phone they had. They gave me a preowned Z3352CA which I think is a "ZTE Blade A3 L". It is running Android 9 Build number Z3352CAV1.0.B03 ("Android Go"). It's pretty nice. However I have a sense buying a preowned Android is probably about as safe as sticking your hand in a garbage disposal. I did a factory reset first thing, but I would like to be reasonably certain the thing the factory reset installed was a legitimate ZTE OS with no extra presents from the previous owner like spyware*.
I asked a question in the ZTE Blade forum but got no responses, which is unsurprising for a question about a old and obscure budget phone. Trying again in here-- I understand people probably don't know about ZTE/ZTE Blade phones specifically, so I would like to ask some general questions about how to use fastboot or what you'd expect with a normal Android 9 ("go") device.
Specifically I found an iffy article describing bootloader unlock procedures, with this screenshot:
{
"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"
}
"Device tampered" caught my eye. Some discussions I see online about fastboot reference this "device tampered" flag. I am interested in this. If I had to guess, I'd guess this flag is supposed to go true if the device is unlocked and stay true even if the device is re-locked. To be clear, right now I *don't want* the bootloader unlocked. What I want is to be sure nobody before me has ever unlocked the bootloader.
When I saw this I attempted to put the phone into Fastboot Mode. I can't tell if this worked or not. I started up with the "volume up" and power buttons held, which dropped me into "Recovery Mode". It said "Android Recovery" at the top and offered a menu of options, one was "Reboot to Bootloader". I selected this and was sent to a black screen with "=> FASTBOOT mode..." in the bottom left corner in a terminal font. Nothing happens at this screen. The up and down volume buttons, and the power button, do nothing (I can boot the phone normally by holding the power button down 3 seconds). I can't tell if this is fastboot mode or not. If I run fastboot.exe devices on my Windows 10 machine, it is not able to see or connect to the phone in "=> FASTBOOT mode..." mode. (I have the normal Windows Android drivers installed for running adb but have not installed the ZTE specific drivers.)
I dropped the phone into Developer Mode and looked in Developer Options. I saw an "OEM unlocking" checkbox, which is unchecked. I thought: Maybe this will let me talk to fastboot. But if I tap it, it says:
Allow OEM unlocking?Warning: Device protection features will not work on this device while this setting is turned on.
I tapped "cancel" because at this point it occurred to me this switch, by itself, might qualify as "tampering".
(Other things I tried: I ran the app "SafetyNet Test" from Google Play and it said I passed. I enabled USB debugging and was able to connect to the device with adb. I tried "adb.exe reboot bootloader" but it just took me back to the "=> FASTBOOT mode..." screen. I looked on the Android Developer website for documentation of "fastboot oem device-info" but couldn't find anything.)
TLDR, what I am trying to figure out:
Is fastboot oem device-info documented anywhere? Is it an Android thing or a OEM specific thing? If its meaning is not fully standard, are there conventions?
What should I expect the "Device tampered" key in fastboot oem device-info to mean?
What effect should I expect the "Allow OEM unlocking" checkbox in Developer Options to have (either on fastboot, or on the "Device tampered" key?
Can either fastboot.exe or adb.exe tell me whether the device has ever been bootloader unlocked?
What will checking "Allow OEM unlocking" in Developer Options do? Will it allow me to talk to Fastboot? Will it result in the phone being flagged as "tampered'?
Generally is there anything I can do, with the tools available to me (ADB, and fastboot if I can make it work) to ensure a used phone has not had durable malware added and I am running a vendor-stock OS?
* I am also interested in any info as to the probability ZTE itself or the ZTE default ROM is spyware-ing me.
Related
Hi all,
This is my first post to XDA and before I go any further I must say that i'm quite the idiot when it comes to android terminology and general modification of android as a whole. So if i'm in the wrong place, sorry!
I've got myself a One SV on t-mobile and have had it approaching 2 years now. I came to this phone from my previous HTC Desire (wish i kept it).
Back when i got my desire and started looking into customisation, performance etc i learnt a little about rooting and the pro's and cons surrounding it. "How hard can it be" so I went ahead and somehow installed CM on my desire. All was well and I never ran into too many problems. Now I've tried to do the same with my one sv (after having poor battery life, lack of storage and just all round lack of options) and i'm a little stuck.
I've tried to follow this guide > http://forum.xda-developers.com/showthread.php?t=2113671 and various others. The wording, however and process just seems beyond me. I've managed previously to unlock the bootloader via HTC however that's where i'm stuck (the easy bit).
BASICALLY what i'm asking, is for some kind hearted, patient soul to walk me through this, in dummies terms.
I'm almost certain i've soft bricked the device (don't ask me how) as there's some major issue now surrounding the dialer, contacts and sync. I receive the message "'android.process.acore has stopped" repeatedly, rendering my phone useless at the moment. I'm at a loss now and i need some help! any advice would be greatly appreciated.
Luke.
Ok, your bootloader is unlocked.
Do you have a working fastboot command? And what version of One SV do you have (k2u, k2ul,...)
A working Fastboot command... you've stumped me already im afraid. As i said i really haven't got a clue... i don't want to mislead you. How could i find out which version of the device i have? i've taken a peek behind the battery and i can't see anything.
From what i've just read i'd presume it's the k2_ul due to me being in England. If you know otherwise though, i can check?
You had to flash the unlock token with fastboot, right?
If that worked, you should have a working fastboot.
To know your version, connect your phone to pc, boot into bootloader (look if there is fastboot usb written on the phone screen) and open your cmd window on pc in the same foldrr, where yourfastboot.exe is.
Type into cmd window:
fastboot getvar all
Put the output here, without your serial and imei.
When starting the phone in "hboot" i recieve the following
UNLOCKED
k2-UL PVT SHIP S-ON RL
HBOOT-2.21 0000
Including various bits of other info. Then going on to read;
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
SHOW BARCODE
If i connect the phone to my PC in hboot it won't detect or anything to be honest. Should i first connect the phone to the PC normally? as if to transfer files etc and then turn off the phone and boot in hboot? or am i doing something wrong.
Thanks for all the help by the way!
When trying to select FASTBOOT and then selecting BOOTLOADER from the following menu I receive a list of "no gift file" "no image" etc.
So from what you're saying, it's likely i haven't followed the flashing procedure correctly?
Bootloader has two modes: the one you have described "scanning for files" is the bootloader mode. The other is fastboot mode.
But i know enough.
With the command
fastboot devices
you can check if your device is recognised.
Try to check this:
connect your phone to pc, boot into bootloader/fastboot mode (look if there is fastboot usb written on the phone screen) and open your cmd window on pc in the same folder, where your fastboot.exe is and run the cmd above. Look, what output you get in cmd window.
Maybe you need to install htc sync on your pc to get the latest drivers.
Hi, first off sorry for the late reply. Work has been mega busy. Bad news is that this hasn't miraculously solved its self over night. i've had a brick for nearly a month now with no way to call my contacts etc.
When starting the phone in fast boot (vol down and power on) and connecting to the PC i have no option for "fastboot usb" as you've described. I've tried to update HTC Sync manager. I've also tried various USB ports on the PC (i've had the issue before, whereby some of the ports haven't got the required power) and it's still not available. Is there any easy method to solve this?
Fastboot USB is not an option to choose, its only written on the screen, that you can see you are connected.
Take a look at this picture:
{
"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"
}
Connect your phone to pc, go to the folder where your fastboot.exe is and open a cmd window there.
Type into that cmd:
fastboot devices
The output should be your serial number.
---------- Post added at 12:33 PM ---------- Previous post was at 12:29 PM ----------
As you are unlocked, you should be able to flash TWRP recovery (if your fastboot is working). From TWRP you can backup whats left and flash stock rom.
All under tbe aspect, the device is not screwed up.
As you can see, these are the only options i'm getting. The phone is plugged in via USB 2.0 and isnt being picked up by the PC at all. I've updated the HTC Sync Manager in hope of solving it that way but still no luck. Any other advice?
Is your phone booting and stable enought to get S-off (rumrunner.us would be your choice)?
Maybe try another pc or cable, you need either S-off or a working fastboot.
I can use the phone. The only real problem is inability to access contacts and the message " Unfortunately, the process android.process.acore has stopped." appears every 5 seconds or so.
Sometimes the message stops appearing and the phone works normally. This is what confuses me. Why is it only happening most of the time, not all of the time?
I dont really understand S-OFF either. I'm sorry i'm so useless with all of the terminology but i can't seem to manage without a very basic explanation of how to do these things. I'm totally to blame for this. I shouldn't have messed with the phone in the first place. Leaving it to the experts like yourself is best.
Have you tried a factory reset to solve this?
yes twice, im really out of options now so i may end up having to buy a new phone or take it to an expert
If your phone boots and it is fine sometimes, than you should be able to "rescue" it.
When the phone is in the state of the picture you have posted today, connected to pc with usb, then you need to hit the power button once to access fastboot USB.
Look at your picture: you are in Hboot mode, Fastboot is highlighted.
Hey, I've since managed to get the phone to this state with the USB plugged into my computer. Where am i going from here? It seems the cables i'd been using were faulty. Only one works!
Yeah, that is what we need!
Now you should try to do 2 things:
- try to backup your data with a app like Titanium Backup (if there is anything left, after your factory reset)
- Connect your phone to pc in this fastboot usb state, go (on your pc) to the folder where your fastboot.exe is and open a cmd window there.
Type into that cmd:
fastboot devices
The output should be your serial number.
yes! am i on the right track?
Yes, you are!
Remove the picture, it don't need to be public.
Download this recovery: http://d-h.st/m7F
Rename the file to recovery.img and copy it into the folder where your fastboot.exe is.
Then, in the cmd window type the command:
fastboot flash recovery recovery.img
You should see the progress on the phone screen in the corner of the upper right side.
I have read numerous threads on how to unlock the bootloader, however after the GTab2 7.0 p3100 is/was updated to JB 4.1.2 (VRBMI1), there is nothing i have found after a few days of looking and reading. Is this bootloader locked and no way to flash a custom ROM to it? Obviously, if this is a ridiculously dumb question, then I apologize in advance and the thread should be deleted. I just really would like to flash something really minimal to the 2 GTab2's that I have laying around to use them as home automation tablets in a couple of infrequently visited areas of my house. The stock ROM is really slow imho.
I do realize this is a very old tablet so it may be just too old to do anything with, regardless thanks very much for any help in this!
If you didn't buy it from a carrier and such, it's unlocked
Its from verizon and to the best of my knowledge, it is locked. Whats the best way to be certain of this?
To check if your bootloader is locked: install adb and fastboot to your computer as well as the proper drivers, boot your tab into download mode (power+volume down) and connect it to the computer with usb cable. Open a command prompt and type "fastboot devices" (without the quotes). If everything is right you will see your tab listed. Now for the check type "fastboot getvar unlocked" (again without the quotes). If the result is yes, your bootloader is unlocked.
Ok, so I already had adb/fastboot and odin 3 v 3.12 installed. Odin3 sees the device in both on and download states. adb doesnt see it at all in either mode. Windows 10 is my OS... Device manager see the tab unplug and plug in each time and I have used multiple USB ports as well. Any ideas? Chuck the tabs in the trash perhaps?
Trash is not a good idea It's probably a driver issue. Check that you have installed the adb/fastboot drivers, maybe there is an update to some driver you haven't done or seen yet. Also, try to install for your tab specifically the adb driver through the device manager (I don't know much about windows 10 so I can't tell you exactly how to do it, perhaps right-click on the tab or from some menu).
EDIT: Since odin works, try to install twrp with it. If it fails it's locked and you need fastboot to unlock it.
Thanks for the reply,
I have reinstalled the latest adb drivers in addition to getting the latest platform-tool download for adb and fastboot - the GTab2 shows up in the device manager when plugged in. When the Tab is on, I can see it (adb devices) return a device ID. When I put the GTab2 into download mode, it does not see the device (fastboot devices). I have read that fastboot may not always return a device ID so I tried to enter the command 'fastboot getvar unlocked' and it just hangs waiting for me to plug in a device. This happens for both of the GTab2 that I have. At least I am consistent in my failure. lol
One interesting thing is that when plugged into USB in the device manager the GTab2 shows up in 2 locations when turned on. Under Modems (SAMSUNG Mobile USB Modem #4 ) and under SAMSUNG Android Phone (SAMSUNG Android ADB interface). In download mode, the device shows up only as a modem? Odd.
On one device, I installed twrp as advised and when I try to boot into recovery it now states "System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help." ~meh
In download mode it now shows a custom binary download of 1 count lol - looks like I am really needing fastboot to work for me. Thanks for any help that can be provided.
zulutron said:
Thanks for the reply,
I have reinstalled the latest adb drivers in addition to getting the latest platform-tool download for adb and fastboot - the GTab2 shows up in the device manager when plugged in. When the Tab is on, I can see it (adb devices) return a device ID. When I put the GTab2 into download mode, it does not see the device (fastboot devices). I have read that fastboot may not always return a device ID so I tried to enter the command 'fastboot getvar unlocked' and it just hangs waiting for me to plug in a device. This happens for both of the GTab2 that I have. At least I am consistent in my failure. lol
One interesting thing is that when plugged into USB in the device manager the GTab2 shows up in 2 locations when turned on. Under Modems (SAMSUNG Mobile USB Modem #4 ) and under SAMSUNG Android Phone (SAMSUNG Android ADB interface). In download mode, the device shows up only as a modem? Odd.
On one device, I installed twrp as advised and when I try to boot into recovery it now states "System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help." ~meh
In download mode it now shows a custom binary download of 1 count lol - looks like I am really needing fastboot to work for me. Thanks for any help that can be provided.
Click to expand...
Click to collapse
"System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help."
are you really sure that you have a p3100?? it seems that you have a verizon varient of the tab 2. in this case dont flash p3100 stuff on your device. it will brick
Well, Its 3G capable and has wifi as well. I dont use it for 3G anymore though. That is P3100 afaik. Is there a more definitive way to know this?
zulutron said:
Well, Its 3G capable and has wifi as well. I dont use it for 3G anymore though. That is P3100 afaik. Is there a more definitive way to know this?
Click to expand...
Click to collapse
go to settings --- about the tablet. make a screenshot of this page and post it here.
Here it is. Thank for the help.
{
"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"
}
http://tinypic.com/r/2rzv3f8/9 <-- if the above doesnt work
zulutron said:
Its from verizon and to the best of my knowledge, it is locked. Whats the best way to be certain of this?
Click to expand...
Click to collapse
here you said that the tab is from verizon.
there is no rom available for your device.
i say it again
DONT FLASH P3100 STUFF ON THIS TAB !!
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
zulutron said:
Here it is. Thank for the help.
https://unsee.cc/tumezaso/ <-- if the above doesnt work
Click to expand...
Click to collapse
this is a sch-i705 and not a p3100. thats different devices
This thread calls them all SCH-i705
https://forum.xda-developers.com/showthread.php?t=1942674
zulutron said:
This thread calls them all SCH-i705
https://forum.xda-developers.com/showthread.php?t=1942674
Click to expand...
Click to collapse
look at the last 2 posts of the thread. all download links are dead since 1 year.
the best scenario for you. someone can help you out with the files. then you can install a damn old twrp recovery. with that you can backup your current system. nothing more.
there is no up to date twrp and no available rom for this device.
in this case unlocking the bootloader makes no sense, i think.
I appreciate the help for sure. I wont waste any more time on these tabs.
Hey, my friend has a Pixel 2 that seems to have gotten bricked today. His phone was working fine all day but when he tried to unlock it to check the time, it was suddenly in fastboot mode. He was running stock android, and has never flashed any custom ROM/software to it, nor unlocked it:
{
"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"
}
I can't open recovery mode or boot the OS from fastboot. The only option I can access is the "barcode" one. I've been trying to flash a factory image from google(as I've done several time for my Nexus 5 and Nexus 7 using the fastboot/ADB from CMD), but currently ADB won't recognize the device(probably because USB debugging and other developer settings are off/have never been accessed at all), and Fastboot recognizes the device but can't perform any flashing to it because it's locked. I also tried deuces script from a folder with all the factory .img files unzipped etc. I also updated the USB drivers in windows, but basically every step I can find here, on reddit or on stack overflow mention enabling USB-debugging and OEM unlock in the settings, which I can't access. Is there anything I can try or is it per definition bricked?
Marhan93 said:
Hey, my friend has a Pixel 2 that seems to have gotten bricked today. His phone was working fine all day but when he tried to unlock it to check the time, it was suddenly in fastboot mode. He was running stock android, and has never flashed any custom ROM/software to it, nor unlocked it:
I can't open recovery mode or boot the OS from fastboot. The only option I can access is the "barcode" one. I've been trying to flash a factory image from google(as I've done several time for my Nexus 5 and Nexus 7 using the fastboot/ADB from CMD), but currently ADB won't recognize the device(probably because USB debugging and other developer settings are off/have never been accessed at all), and Fastboot recognizes the device but can't perform any flashing to it because it's locked. I also tried deuces script from a folder with all the factory .img files unzipped etc. I also updated the USB drivers in windows, but basically every step I can find here, on reddit or on stack overflow mention enabling USB-debugging and OEM unlock in the settings, which I can't access. Is there anything I can try or is it per definition bricked?
Click to expand...
Click to collapse
Have you tried using the OTA instead of the factory image? That might give you a workaround to get it functioning again.
Sent from my Pixel 2 using Tapatalk
Have you tried changing your usb cable and the port its plugged into? Its stupidly simple, but has solved nuuuuuumerous problems I've had with manually flashing.
Other that that, I think you've covered a lot of bases. Are you sure you can't get into recovery mode tho? I was only able to get in by unplugging, full power off, then using power + vol dn for bootloader mode, then selecting recovery mode. You might be able to do some flashes from there.
Also, adb only works in the OS and maybe recovery mode. Fastboot only works in bootloader mode. I'm not exactly sure if fastboot needs to be authorized. Adb does though.
hi..pls help me
how to onlock oem a51 ??
Enable the Developer Options on your Samsung Galaxy A51 device.
Go to the phone Settings menu.
Scroll down to the bottom part and tap on About Phone → tap on Build Number 7 times continuously.
Now, Go back to the main Settings menu again and scroll down.
Tap on the Developer options → enable “OEM Unlock” option.
{
"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"
}
Reboot phone.
Unlock phone's bootloader via FASTBOOT commands
fastboot devices
fastboot oem unlock
fastboot reboot
Done.
h.azara said:
hi..pls help me
how to onlock oem a51 ??
Click to expand...
Click to collapse
How to Unlock Bootloader on Samsung Galaxy A51
In this tutorial, we will to show you the steps to unlock the Bootloader on Samsung Galaxy A51 via the New VaultKeeper Method.
www.droidwin.com
always make a nandroid backup before u go messing about the sys files
hope it helps,
regards,
ruky23 said:
How to Unlock Bootloader on Samsung Galaxy A51
In this tutorial, we will to show you the steps to unlock the Bootloader on Samsung Galaxy A51 via the New VaultKeeper Method.
www.droidwin.com
always make a nandroid backup before u go messing about the sys files
hope it helps,
regards,
Click to expand...
Click to collapse
I did all the steps, but in the download mode, the mode is locked
jwoegerbauer said:
Enable the Developer Options on your Samsung Galaxy A51 device.
Go to the phone Settings menu.
Scroll down to the bottom part and tap on About Phone → tap on Build Number 7 times continuously.
Now, Go back to the main Settings menu again and scroll down.
Tap on the Developer options → enable “OEM Unlock” option.
Reboot phone.
Unlock phone's bootloader via FASTBOOT commands
fastboot devices
fastboot oem unlock
fastboot reboot
Done.
Click to expand...
Click to collapse
All steps are done correctly, but the download mode is still locked
up........................................................
Has anyone been able to solve it?
up???
up//////////////////
enter download mode then long hold volume up button then he will ask you do you want to unlock bootloader now press volume up again
Unlock Bootloader Samsung Galaxy A51
How to Re-Lock Bootloader Samsung Galaxy Devices
I've got a Moto One 5G Ace that I picked up from eBay. It's an XT2113-2 according to the Recovery Mode 128/6. I guess the carrier was T-Mobile because the annoy screen always comes on when I boot. Fastboot lists it as
NK0T4M0308 fastboot
but when I try and write the recovery.img I get
fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) FAILED (Write to device failed (No such device))
When I try and use the Recovery and Smart Assistant(Windows) from Motorola
the IMEI doesn't match to the firmware
And it's stuck on Android 10, when I try and update from the phone it says it has the latest version of Android
When I try and run Rescue and Smart Assistant(RSA) and boot to the Recovery mode it soon drops and says it can't connect to the device
Mobile Assistant is installed by RSA but after RSA tries to detect the device in Recovery Mode but can't it can no longer detect the USB when it's attached. I need to reset the device so I can go through the entire process all over again.
Please help I don't know what's going on or how to fix it
{
"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"
}
You have an engineering phone. It cannot be updated via regular ways.
RETIEF said:
You have an engineering phone. It cannot be updated via regular ways.
Click to expand...
Click to collapse
So what irregular ways can I employ then?
Send it to someone who has the tools to flash it. I don't know anyone but perhaps someone on the Telegram channel does.
Just in case anyone else comes across this problem too. The internal hardware is not the same as the model would indicate with the model number it's entirely different. So in other words, it's an entirely different phone, it can't be flashed to anything. It's like comparing apples to oranges they are in no way the same.
In Developer options, does it say "Bootloader is already unlocked" under OEM unlocking?
Does it still fail to load recovery if you run "fastboot boot recovery.img" so it says "Waiting for device...", then plug the phone in while holding down the volume and the phone is shut down? Even retail kiev can be really finicky in fastboot mode.
Really cool find in any case.
fddm said:
In Developer options, does it say "Bootloader is already unlocked" under OEM unlocking?
Does it still fail to load recovery if you run "fastboot boot recovery.img" so it says "Waiting for device...", then plug the phone in while holding down the volume and the phone is shut down? Even retail kiev can be really finicky in fastboot mode.
Really cool find in any case.
Click to expand...
Click to collapse
it would be cool if I could image it, but the internals don't match to what it actually is
but yes it does say the bootloader is already unlocked