Related
Hello
My device is running on Marshmellow [arm64-v8a] with locked bootloader [i cant able to unlock due to getting unknown command error]
so today i found that OTA which can able to upgrade my marshmellow to android N
so i think if i somehow inject superuser apk in OTA/system/priv-app and then i update my phone using that modified OTA, will it work to gain full root access?
or should i something try another method to inject super user in ota.zip?
so how to do?
Thank you
tcpcd said:
Hello
My device is running on Marshmellow [arm64-v8a] with locked bootloader [i cant able to unlock due to getting unknown command error]
so today i found that OTA which can able to upgrade my marshmellow to android N
so i think if i somehow inject superuser apk in OTA/system/priv-app and then i update my phone using that modified OTA, will it work to gain full root access?
or should i something try another method to inject super user in ota.zip?
so how to do?
Thank you
Click to expand...
Click to collapse
Mostly likely not, bootloader is locked meaning you can only run verified images.
Let's see why you can't unlock the bootloader instead.
What steps have you done, etc.
Matt07211 said:
Mostly likely not, bootloader is locked meaning you can only run verified images.
Let's see why you can't unlock the bootloader instead.
What steps have you done, etc.
Click to expand...
Click to collapse
FIrst i enable usb debugging and oem unlocker in developer setting
then i enter 'adb reboot bootloader' to boot into bootloader
after i entered 'fastboot oem unlock' so i got an error that 'unknown command'
so i guess my device manufacture somehow changed unlocking code.
after googling i found that oem unlock code saved in aboot.img file [https://www.reddit.com/r/Android/comments/54wz8j/how_to_discover_hidden_fastboot_commands/]
therefore i try to grab aboot from /dev/block using dirtycow, but BIG FAILURE
so i thought maybe in OTA Chinese company always hide their backdoor. so what if i inject superuser in my OTA.zip.
EDIT:
File content in OTA.zip
Code:
+media
+app
+etc
+fake-libs
+fake-libs64
+fonts
+framework
+lib
+lib64
+bin
+nv
+presetapp
+priv-app
+tts
+usr
+vendor
+xbin
Description about my OTA [1.7gb]
- It can upgrade Marshmellow to Android N, by open recovery mode and choose OTA.zip file from mmc.
- It contain lots of system apk and device mfg apk.
tcpcd said:
FIrst i enable usb debugging and oem unlocker in developer setting
then i enter 'adb reboot bootloader' to boot into bootloader
after i entered 'fastboot oem unlock' so i got an error that 'unknown command'
so i guess my device manufacture somehow changed unlocking code.
after googling i found that oem unlock code saved in aboot.img file [https://www.reddit.com/r/Android/comments/54wz8j/how_to_discover_hidden_fastboot_commands/]
therefore i try to grab aboot from /dev/block using dirtycow, but BIG FAILURE
so i thought maybe in OTA Chinese company always hide their backdoor. so what if i inject superuser in my OTA.zip.
EDIT:
File content in OTA.zip
Description about my OTA [1.7gb]
- It can upgrade Marshmellow to Android N, by open recovery mode and choose OTA.zip file from mmc.
- It contain lots of system apk and device mfg apk.
Click to expand...
Click to collapse
What's your device model?
Have you tried searching for <device model> root?
No copy of aboot.img or bootloader etc name I'm a full firmware image?
Is your device the kinda of device where you need to request a unlock code from manufacturers website (I think it's Sony who does that, not sure who else).
Can you give me any more info to work with?
Matt07211 said:
What's your device model?
Have you tried searching for <device model> root?
No copy of aboot.img or bootloader etc name I'm a full firmware image?
Is your device the kinda of device where you need to request a unlock code from manufacturers website (I think it's Sony who does that, not sure who else).
Can you give me any more info to work with?
Click to expand...
Click to collapse
Model is Coolpad Note5
yes i searched everywhere to find root solution, even in official forum, but no success.
no my device dont need unlock code.
im sending you OTA.zip extracted link so you can see whats inside.
tcpcd said:
Model is Coolpad Note5
yes i searched everywhere to find root solution, even in official forum, but no success.
no my device dont need unlock code.
im sending you OTA.zip extracted link so you can see whats inside.
Click to expand...
Click to collapse
I'm wondering, is your device MediaTek based?
Matt07211 said:
I'm wondering, is your device MediaTek based?
Click to expand...
Click to collapse
no its qualcomm/snapdragon based
tcpcd said:
no its qualcomm/snapdragon based
Click to expand...
Click to collapse
Can you be specific?
What fastboot commands work and don't?
Matt07211 said:
Can you be specific?
What fastboot commands work and don't?
Click to expand...
Click to collapse
Code:
fastboot getvar all
^^work only this one
Code:
fastboot reboot
^^this is not woking even. just got output "reboot..." but fone actually not rebooting.
i tried fastboot oem unlock,unlock-go,flashing unlock << all Failed
tcpcd said:
^^work only this one
^^this is not woking even. just got output "reboot..." but fone actually not rebooting.
i tried fastboot oem unlock,unlock-go,flashing unlock << all Failed
Click to expand...
Click to collapse
Not even
Code:
fastboot boot boot.img
?
I've sadly never had a device with fastboot, so it ain't my area of expertise
Matt07211 said:
Not even
Code:
fastboot boot boot.img
?
I've sadly never had a device with fastboot, so it ain't my area of expertise
Click to expand...
Click to collapse
i think that command is working, but i didnt checked
i only checked oem commands with fastboot
tcpcd said:
Not even
i think that command is working, but i didnt checked
i only checked oem commands with fastboot
Click to expand...
Click to collapse
If you can boot custom boot.img then you can root it.
I personally rooted the xCover3 by modifying the boot.img
Matt07211 said:
If you can boot custom boot.img then you can root it.
I personally rooted the xCover3 by modifying the boot.img
Click to expand...
Click to collapse
no i cant boot custom images
tcpcd said:
no i cant boot custom images
Click to expand...
Click to collapse
Okay. Can you detail, EVERY method you've tried (any apps, fastboot commands Cave's (E.g. Dirty Cow) etc.) So we can get a clear overview and saves us both time as we are not going over the same stuff
Matt07211 said:
Okay. Can you detail, EVERY method you've tried (any apps, fastboot commands Cave's (E.g. Dirty Cow) etc.) So we can get a clear overview and saves us both time as we are not going over the same stuff
Click to expand...
Click to collapse
OKay
I tried Kingroot, kingoroot << Failed
Using dirtycow << Got success :cyclops: for temp root
Used farm-root to pull boot.img << termination after long wait
VIKIROOT << Working but not spawn shell
I only check fastboot oem commands but << failure
Code:
fastbooot oem unlock
fastbooot oem unlock-go
fastbooot oem unlock_go
fastbooot oem flashing unlock
fastbooot flashing unlock
fastbooot oemunlock
Output: FAILED (remote: unknown command)
Big 0
But one command work:
Code:
[stark]:~|$ fastboot getvar all
(bootloader) yl_udiskname:userdata
(bootloader) version:REFRESH_emmccid_new
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4199000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5a7bfbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x140000000
(bootloader) serialno:366da886
(bootloader) kernel:lk
(bootloader) product:MSM8952
all:
finished. total time: 0.022s
So I believe using dirtycow will probably be your chance at getting root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
Unless you figure out the correct fastboot commands
Matt07211 said:
So I believe using dirtycow will probably be your chance at getting root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
Unless you figure out the correct fastboot commands
Click to expand...
Click to collapse
Well dirtycow is only option for temp root
would this work on specific firmware, for example a combination firmware (factory binary on samsung) then install a custom recovery from there...?
tcpcd said:
Well dirtycow is only option for temp root
Click to expand...
Click to collapse
Well it's better then nothing, you can work Frkm there if roots such a bug deal for you
I think DC Unlocker Tool Maybe Work.
Hello,
at first - I would like to apologize to moderators, if this topic is out of category, I tried to find some troubleshooting category but didnt. So please if Im blind, move it. At second, sorry for my english, Im not native speaker.
Model XT1635-02 Reteu dual sim 32GB
Trouble description:
I unlock bootloader, flash twrp and tested some custom rom. After that, I want to go back to stock rom. I flashed the stock rom, but forget to do NOT ota update. Ok - brick the phone. After few hours of searching, I relive a phone with right flashblank and had an access to bootloader again. But tried to flash a stock rom again, and that was a main fail again. So - I have a stock rom in phone, but doesnt work. And (from my point of view) I have a nonworking stock rom with locked USB debuging mode, I cannot unlock it, becasuse it doesnt work and I cannot flash twrp, because USB debug is locked. If I try to boot recovery twrp, phone restart but no twrp popup. vol up + pwr do nothing. So Im catch in some crappy circle at this moment. I tried fastboot erase system, but result is:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.006s
Click to expand...
Click to collapse
So question is: Is there some command in fastboot for deleting everything? Or other way how to delete a rom from fastboot? (idea is delete rom to skip locked USB debug)
Other thing to do, to test? Some tips, helps?
Thank you so much everyone who spend a time try to help me...
You can install twrp again? If you can, just do a advanced wipe. Because MZP Bootloader doens't allow to delete any part of system.
Hi,
Got a XA2 here which is bricked. The owner tried to install LineageOS they unlocked bootloader without root and tried to install TWRP.
Now the device is bricked. Tried recovering through Flash Tool, Sony Emma and Sony Companion.
But seem to keep getting USB Malfunctioned.
When I try get into bootloader it says the following..
Your device software can't be checked for corruption.
Please Lock the bootloader.
I've literally tried everything. Tried every driver I could find to try and fix the USB malfunctioned issue.
Anyone else experience this issue?
Regards
Kev
That's not an error. Its normal if you have unlxoekd the bootloader.
wigankev said:
Hi,
Got a XA2 here which is bricked. The owner tried to install LineageOS they unlocked bootloader without root and tried to install TWRP.
Now the device is bricked. Tried recovering through Flash Tool, Sony Emma and Sony Companion.
But seem to keep getting USB Malfunctioned.
When I try get into bootloader it says the following..
Your device software can't be checked for corruption.
Please Lock the bootloader.
I've literally tried everything. Tried every driver I could find to try and fix the USB malfunctioned issue.
Anyone else experience this issue?
Regards
Kev
Click to expand...
Click to collapse
Flash stock firmwre using newflasher
davidhozic said:
Flash stock firmwre using newflasher
Click to expand...
Click to collapse
How when I keep getting USB malfunctioned? Even with brand new cable.
wigankev said:
How when I keep getting USB malfunctioned? Even with brand new cable.
Click to expand...
Click to collapse
I've tried every driver I could find. But no success.
Phone goes back to owner tomorrow. Would have liked to have fixed it. But can't get it to go into flashmode due to USB not recognised error.
I also had this problem before.
Holding Power UP while plugging it into the USB brought me back to Fastboot.
Power DOWN and plugging it to USB brings it into flashmode for restoring the stock ROM.
Pretty hard to brick this thing with these options
Universal ADB drivers work with the XA2 btw:
https://adb.clockworkmod.com/
Same boot loop here. What shall I do?
Hello,
I am (was) in trouble: I have the same boot loop after I unlocked the bootloader and wanted to boot into TWRP with fastboot boot twrp-3.2.3-2-pioneer.img
I have no backup because I wanted to use TWRP to make a backup.
I followed the guide on wiki.lineageos.org devices pioneer install
but I did not perform step 7 "re-enable USB debugging to continue".
Volume UP and Power stops the boot loop, black screen, blue LED, and I can issue "fastboot" commands from Ubuntu.
Where did the twrp-3.2.3-2-pioneer.img go?
Is there still the Sony Recovery in place?
Can I use "fastboot reboot recovery"?
After shutting down the phone and re-starting after 1 hour, the phone presented the XPERIA logo for 2 minutes, and seems to be completely reset.
So I think I am lucky.
Now the question is, why did fastboot boot twrp-3.2.3-2-pioneer.img let to the boot loop?
Similar issue, but no solution yet
Hi!
I have a quite similar issue after booting TWRP although I do not have any controllability via the phone's screen (please find the whole story posted here https://forum.xda-developers.com/showpost.php?p=79335842&postcount=185).
Until today I was not as lucky as Markus and I cannot agree with Schmatzler saying "it's hard to brick" while both options (fastboot mode and flashmode) are still available with my XA2 but could not bring it back to life.
Now I read about "erasing or wiping" the partition and make a new clean install - but actually I don't really know how to proceed
I tried out "fastboot erase a(b)" but did not work ('unknown command'). Before I also tried to boot from slot a and b via "fastboot set_active a(b)" which worked, but both end up in bootloops (different reactions on screen, vibration, sound). Now I plotted data via "fastboot getvar all":
Code:
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4308
(bootloader) version-baseband:1311-2845_50.1.A.13.123
(bootloader) version-bootloader:1310-0301_X_Boot_SDM630_LA1.0_O_123
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x500000000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xB5000000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:no
(bootloader) product:H3113
(bootloader) serialno:
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
From that I think "version baseband" is saying I have stock 50.1.A.13.123 installed although I flashed stock 50.2.A.0.352 with flashtool yesterday ("successfully")...
Maybe someone could explain the other entries?
Maybe someone could explain how to wipe the slots and make a clean install?
Or maybe someone has another idea how to proceed?
Hi Klaus and others, I have the same problem (fastboot=bluelight and flash=greenlight works), but the screen just flickers and I have no idea how to proceed from here.
One thing I can think of is that my firmware is of H3113 1312-1890 which is not in the XperiFirm firmware list. I have been trying 1312-3773 for both 50.1.A.13.123 and 50.2.A.0.379 but to no avail
terranstyler said:
Hi Klaus and others, I have the same problem (fastboot=bluelight and flash=greenlight works), but the screen just flickers and I have no idea how to proceed from here.
One thing I can think of is that my firmware is of H3113 1312-1890 which is not in the XperiFirm firmware list. I have been trying 1312-3773 for both 50.1.A.13.123 and 50.2.A.0.379 but to no avail
Click to expand...
Click to collapse
Did you try this https://forum.xda-developers.com/xp...ageos-16-0-t3836151/post79651818#post79651818
markusXA2 said:
Where did the twrp-3.2.3-2-pioneer.img go?
Click to expand...
Click to collapse
We cannot install/flash twrp permanently. We can only boot into it through
fastboot boot twrp-........img.
When finished backing up/flashing rom etc whilst in twrp.... when rebooting into system we must press 'do not install' button when it is asking to install twrp.
This will remove the boot loop.
Although I just realised pioneer does have a twrp zip file and and can be flashed permanently it seems.
inestion said:
Did you try this https://forum.xda-developers.com/xp...ageos-16-0-t3836151/post79651818#post79651818
Click to expand...
Click to collapse
Not yet but I will (my USB cable got lost somewhere), thanks for the link.
inestion said:
Did you try this https://forum.xda-developers.com/xp...ageos-16-0-t3836151/post79651818#post79651818
Click to expand...
Click to collapse
OK, I found the cable and I am trying right now but after installing Emma on Win7 I have to find the Xperia XA2 drivers here https://developer.sony.com/develop/drivers/ but they're not there.
So I followed some other advice where they said I could use Xperia XZ2 drivers (the driver is "Sony sa0118 ADB Interface driver") but Windows still gives me Code 10 (This device cannot start).
There are some other shady driver sites out there but I don't know which one to trust here.
Any advice is appreciated.
inestion said:
Did you try this https://forum.xda-developers.com/xp...ageos-16-0-t3836151/post79651818#post79651818
Click to expand...
Click to collapse
OK, I managed to try on a Win10 computer and it worked NOT with the twrp 3.3.1-1 image but IT DID WORK with the one from https://forum.xda-developers.com/showpost.php?p=79624498&postcount=798
I have an odd problem that I never experienced before, maybe some have? Using Linux (Arch with android-tools installed), I'm trying to unlock my XZ2C like I have done lots of time with "sudo fastboot oem unlock 0x". But, this time it just wont run. The cursor jumps about 30 characters (spaces I guess) and just sits there, nothing else happens. Have to pull the cable to the phone to "abort" fastboot. It looks like this (the FAILED part is what I get after I pull the cable);
Code:
*#*sudo fastboot oem unlock 0x9366CB600ED6A33C
[sudo] lösenord för zynex:
< waiting for any device >
FAILED (Status read failed (No such device))
fastboot: error: Command failed
I have tried change the cable, but still the same. Any ideas?? I read in the twrp thread about a bootloader bug, not sure if that have something to do with it. I'm on latest fw (52.0.A.10.6).
PS, yes I have OEM unlock checked, ADB debug etc etc...
-- Mike
zynexx said:
I have an odd problem that I never experienced before, maybe some have? Using Linux (Arch with android-tools installed), I'm trying to unlock my XZ2C like I have done lots of time with "sudo fastboot oem unlock 0x". But, this time it just wont run. The cursor jumps about 30 characters (spaces I guess) and just sits there, nothing else happens. Have to pull the cable to the phone to "abort" fastboot. It looks like this (the FAILED part is when what I get after I pull the cable);
Code:
*#*sudo fastboot oem unlock 0x9366CB600ED6A33C
[sudo] lösenord för zynex:
< waiting for any device >
FAILED (Status read failed (No such device))
fastboot: error: Command failed
I have tried change the cable, but still the same. Any ideas?? I read in the twrp thread about a bootloader bug, not sure if that have something to do with it. I'm on latest fw (52.0.A.10.6).
PS, yes I have OEM unlock checked, ADB debug etc etc...
-- Mike
Click to expand...
Click to collapse
Latest is 11.3
I would update first
Do you use at least platform tools v29.0.4?
Is the phone in the blue led fastboot mode?
MartinX3 said:
Latest is 11.3
I would update first
Do you use at least platform tools v29.0.4?
Is the phone in the blue led fastboot mode?
Click to expand...
Click to collapse
Ah, seems that 11.3 hasn't been released here yet then, still says I'm up to date. Not sure if that's the issue here thou?
Yep, use android-tools v29.0.4-2, that's the latest release on Arch Linux.
Yes, it's blue. It finds the device when running fastboot devices, and continues after the "waiting for any device" part, but get stuck after that. Never had this issue before, so I'm not sure where to start. Maybe an issue with the bootloader itself?
zynexx said:
Ah, seems that 11.3 hasn't been released here yet then, still says I'm up to date. Not sure if that's the issue here thou?
Yep, use android-tools v29.0.4-2, that's the latest release on Arch Linux.
Yes, it's blue. It finds the device when running fastboot devices, and continues after the "waiting for any device" part, but get stuck after that. Never had this issue before, so I'm not sure where to start. Maybe an issue with the bootloader itself?
Click to expand...
Click to collapse
The bootloader didn't change since months
Do you use the correct code or only "0x"?
And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)
Can't install TWRP on XZ2C
Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out
MartinX3 said:
The bootloader didn't change since months
Do you use the correct code or only "0x"?
And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)
Click to expand...
Click to collapse
I used the code I got from Sony. Maybe should check so I entered the correct IMEI?
Yep, did get a bunch of stuff from it. Can post it if it would help?
m4ikl1983 said:
Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out
Click to expand...
Click to collapse
Bit of topic here, but check so you have read permission for the file (if using Linux). Not sure what you mean by ADB directory, but I guess you mean the directory you have the binary in? You will need to provide the full path to the image file (if you are not in the same directory), fx ~/Download/yourimage.img.
MartinX3 said:
The bootloader didn't change since months
Do you use the correct code or only "0x"?
And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)
Click to expand...
Click to collapse
Not sure why, but I think I entered the wrong IMEI last time. Although, I get the same problem. Running the command, the cursor just jumps like 30-35 characters to the right and stays there, not additional text. Have to pull the cable to abort the command.
This is some of the output from getvar (omitted the partition part);
(bootloader) hw-revision:20001
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4015
(bootloader) version-baseband:1311-5320_52.0.A.10.6
(bootloader) version-bootloader:1310-7079_X_Boot_SDM845_LA2.0_P_118
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:SDM UFS
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:BH901602BZ
(bootloader) serial:28b51f27
(bootloader) product:H8324
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
Click to expand...
Click to collapse
Ok, this was pretty odd. While typing the last comment here, I had run the unlock command and it was just sitting there in the backgrund for a couple of minutes, nothing happened. Pulled the cable, and then the bootloader was magically unlocked anyway. So problem fixed. Not sure why I didn't get any output from the command though
One question though, when rebooting I get a lock pad icon and the text "You device software can't be checked for corruption. Please lock your bootloader". Never seen that on a Sony device before. Is his a new thing?
m4ikl1983 said:
Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out
Click to expand...
Click to collapse
Please follow the TWRP instructions in the TWRP thread.
Your command is wrong.
---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------
zynexx said:
Ok, this was pretty odd. While typing the last comment here, I had run the unlock command and it was just sitting there in the backgrund for a couple of minutes, nothing happened. Pulled the cable, and then the bootloader was magically unlocked anyway. So problem fixed. Not sure why I didn't get any output from the command though
One question though, when rebooting I get a lock pad icon and the text "You device software can't be checked for corruption. Please lock your bootloader". Never seen that on a Sony device before. Is his a new thing?
Click to expand...
Click to collapse
Nice to hear that it works now.
I never saw a android device which doesn't mention on boot that it got unlocked.
So it isn't new for me.
Ahh btw
Since you unlocked on 9.0 your camera will still work in stock.
(In custom rom anyway but there the camera is under construction and get its next update this or next month, but only on android 10.0 with 4.14 kernel).
MartinX3 said:
Please follow the TWRP instructions in the TWRP thread.
Your command is wrong.
---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------
Nice to hear that it works now.
I never saw a android device which doesn't mention on boot that it got unlocked.
So it isn't new for me.
Ahh btw
Since you unlocked on 9.0 your camera will still work in stock.
(In custom rom anyway but there the camera is under construction and get its next update this or next month, but only on android 10.0 with 4.14 kernel).
Click to expand...
Click to collapse
Tried the camera, and it works like a charm
Oh, I never saw anything like it on my other Xperias, just the normal Sony logo The only device I seen it on is Samsungs.
Althougt, I still having problem now that I'm about to flash TWRP. Get the same problem as before, just
hangs there without anything happens.
Code:
Sending 'boot.img' (30904 KB) #FAILED (remote: 'unknown command')
fastboot: error: Command failed
The # is where the cursor is, and when i pull the cable I get FAILED. This is pretty odd.
zynexx said:
Tried the camera, and it works like a charm
Oh, I never saw anything like it on my other Xperias, just the normal Sony logo The only device I seen it on is Samsungs.
Althougt, I still having problem now that I'm about to flash TWRP. Get the same problem as before, just
hangs there without anything happens.
Code:
Sending 'boot.img' (30904 KB) #FAILED (remote: 'unknown command')
fastboot: error: Command failed
The # is where the cursor is, and when i pull the cable I get FAILED. This is pretty odd.
Click to expand...
Click to collapse
Did you follow the twrp instructions carefully including the correct booting into the fastboot mode?
MartinX3 said:
Did you follow the twrp instructions carefully including the correct booting into the fastboot mode?
Click to expand...
Click to collapse
Yep, I read about the bug and booted into fastboot with adb. But still hangs the same way when I tried unlocking the bootloader itself. Also downloaded the platform tools from Google and tried the fastboot from there, but still same outcome.
Is there another way to flash TWRP, think I seen a app of some kind long ago. But I guess I need to have it rooted before I can use it. Think I have a moment 22 situation here :/
zynexx said:
Yep, I read about the bug and booted into fastboot with adb. But still hangs the same way when I tried unlocking the bootloader itself. Also downloaded the platform tools from Google and tried the fastboot from there, but still same outcome.
Is there another way to flash TWRP, think I seen a app of some kind long ago. But I guess I need to have it rooted before I can use it. Think I have a moment 22 situation here :/
Click to expand...
Click to collapse
That's a very weird situation
Did you try it with another computer?
Or with linux instead of windows?
Or switched the slot to slot A with "fastboot --set-active=a" ?
That also requires to flash the newest 11.3 stock firmware again.
(With xperifirm and newflasher from XDA since OTA won't work any longer.)
MartinX3 said:
That's a very weird situation
Did you try it with another computer?
Or with linux instead of windows?
Or switched the slot to slot A with "fastboot --set-active=a" ?
That also requires to flash the newest 11.3 stock firmware again.
(With xperifirm and newflasher from XDA since OTA won't work any longer.)
Click to expand...
Click to collapse
Just tried with another one, running KDE Neon. Same problem. Always using Linux, don't even own a Windows system
Tried fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, but that one got stuck to. Nothing happens. I will try flash 11.3 and see is that might solve the issue I have.
zynexx said:
Just tried with another one, running KDE Neon. Same problem. Always using Linux, don't even own a Windows system
Tried fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, but that one got stuck to. Nothing happens. I will try flash 11.3 and see is that might solve the issue I have.
Click to expand...
Click to collapse
So weird.
You use google plattform tools v29.x and I assume a up to date linux distribution? (I tested it with at least kernel 4.15, running 5.0 now).
Since we both use the same bootloader, it must be something in your hardware or usb cable which disturbs the communication.
MartinX3 said:
So weird.
You use google plattform tools v29.x and I assume a up to date linux distribution? (I tested it with at least kernel 4.15, running 5.0 now).
Since we both use the same bootloader, it must be something in your hardware or usb cable which disturbs the communication.
Click to expand...
Click to collapse
Yep, downloaded the latest one from Google to but got the same error. Using Arch, so it's very up to date Using kernel 5.3.7-arch1-2-ARCH. Have tried another USB cable to, I will see if I can dig out a third one and try.
Btw, seems that NCB firmware are still at 10.6, that' why I haven't gotten any update yet.
zynexx said:
Yep, downloaded the latest one from Google to but got the same error. Using Arch, so it's very up to date Using kernel 5.3.7-arch1-2-ARCH. Have tried another USB cable to, I will see if I can dig out a third one and try.
Btw, seems that NCB firmware are still at 10.6, that' why I haven't gotten any update yet.
Click to expand...
Click to collapse
No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.
Maaaaybe the kernel is too new and contains a driver bug?
MartinX3 said:
No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.
Maaaaybe the kernel is too new and contains a driver bug?
Click to expand...
Click to collapse
I downloaded Customized DE 11.3 and flashed it, but still have problem trying fastboot boot twrp.img.
This is very odd indeed. Don't think it's the kernel, the other computer has kernel 4.4.
Starting to think there's an problem with the phone itself, whatever that could be!?
MartinX3 said:
No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.
Maaaaybe the kernel is too new and contains a driver bug?
Click to expand...
Click to collapse
It seems that I can't do anything regarding fastboot, except rebooting it. Nothing else work, tried fastboot --set-active=a, but nothing happens at all. Tried fastboot flash boot twrp.img, same thing. Fastboot executes, but then nothing. Have to pull the cable to abort the program.
Have never in all the years I played with Android phones run into this stuff. Fastboot has always worked.
Code:
*# sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.051s
*# sudo fastboot --set-active=a
<no output after this>
Basically I tried to install TWRP from https://forum.xda-developers.com/razer-phone/how-to/razer-phone-android-9-0-pie-cheryl-p-t3974325
Long story short (I can give details if it helps). I got into fastboot and tried to switch slots and reboot recovery. Instead it rebooted and the message that my bootloader is unlocked is gone, just bootlooping on the android logo. I can get to fast boot and it shows I'm not on either slot:
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4077
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:1
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:181801V00403118
(bootloader) product:cheryl
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) version:0.0
all:
Finished. Total time: 0.060s
I have no idea how to even just load TWRP and reflash the stock boot.img. (I'd like to preserve my phone data)
Any help would be greatly appreciated. Thank you very much.
If you can get into fastboot try to flask stock factory images and start over.
guillermohs9 said:
If you can get into fastboot try to flask stock factory images and start over.
Click to expand...
Click to collapse
I tried this:
fastboot flash boot twrp-3.2.2-0-cheryl.img && fastboot reboot
fastboot: error: Failed to identify current slot
Leprechaun7 said:
I tried this:
fastboot flash boot twrp-3.2.2-0-cheryl.img && fastboot reboot
fastboot: error: Failed to identify current slot
Click to expand...
Click to collapse
Download the stock image over at razer website. Unzipped the firmware and flash it using platform tool.
sinkoo1979 said:
Download the stock image over at razer website. Unzipped the firmware and flash it using platform tool.
Click to expand...
Click to collapse
Thanks for the help!! I ran flash_all.bat, some files wrote, some failed writes (I can post a long log, if that helps). I'm at least out of my latest dug hole, I can get to the bootloader screen. I'm still stuck at selecting a slot to do anything, still no slot selected. I guess that's the next step for me. I can't find anything about a phone with no slot selected. Any help from anyone would be appreciated.
Leprechaun7 said:
Thanks for the help!! I ran flash_all.bat, some files wrote, some failed writes (I can post a long log, if that helps). I'm at least out of my latest dug hole, I can get to the bootloader screen. I'm still stuck at selecting a slot to do anything, still no slot selected. I guess that's the next step for me. I can't find anything about a phone with no slot selected. Any help from anyone would be appreciated.
Click to expand...
Click to collapse
You should definitely post the log. I suppose you can attach it rather than flood the thread.
guillermohs9 said:
You should definitely post the log. I suppose you can attach it rather than flood the thread.
Click to expand...
Click to collapse
Here is the log (attached). Thanks!
Leprechaun7 said:
Here is the log (attached). Thanks!
Click to expand...
Click to collapse
Those are a lot of FAILED commands. I'm surprised it booted at all.
Did you issue the command
Code:
fastboot flashing unlock_critical
after
Code:
fastboot flashing unlock
?
guillermohs9 said:
Those are a lot of FAILED commands. I'm surprised it booted at all.
Did you issue the command
Code:
fastboot flashing unlock_critical
after
Code:
fastboot flashing unlock
?
Click to expand...
Click to collapse
No, I just ran flash_all.bat. I assume I should run those commands first then flash_all.bat?
My bootloader is already unlocked. Thanks for helping.
Leprechaun7 said:
Those are a lot of FAILED commands. I'm surprised it booted at all.
Did you issue the command after
No, I just ran flash_all.bat. I assume I should run those commands first then flash_all.bat?
My bootloader is already unlocked. Thanks for helping.
Click to expand...
Click to collapse
From the logs I'd say it's not fully unlocked. The 2 commands I quoted are necessary for that.
guillermohs9 said:
From the logs I'd say it's not fully unlocked. The 2 commands I quoted are necessary for that.
Click to expand...
Click to collapse
Good news: Thanks so much!, reunlocking the bootloader and then running flash_all.bat (2x, the first time didn't work right for some reason). It's back up and booting.
Bad news: I'm stuck at a "to start android enter your password" screen. I assume it's the pin to unlock the phone when you reboot. It doesn't seem to work. It might be a problem with the OS (https://www.reddit.com/r/razerphone/comments/bf7qes/restarted_phone_and_get_wrong_pin_when_prompted/)
I've tried all possible passwords I would have used, no luck. Now I've got limited attempts before the device wipes. Of course I think everything is wiped since I re-unlocked the bootloader and flash_all.bat
Leprechaun7 said:
Good news: Thanks so much!, reunlocking the bootloader and then running flash_all.bat (2x, the first time didn't work right for some reason). It's back up and booting.
Bad news: I'm stuck at a "to start android enter your password" screen. I assume it's the pin to unlock the phone when you reboot. It doesn't seem to work. It might be a problem with the OS (https://www.reddit.com/r/razerphone...arted_phone_and_get_wrong_pin_when_prompted/)
I've tried all possible passwords I would have used, no luck. Now I've got limited attempts before the device wipes. Of course I think everything is wiped since I re-unlocked the bootloader and flash_all.bat
Click to expand...
Click to collapse
Mm that doesn't sound right. The data partition should be formatted. There is a fastboot command to format user data. I don't know it by heart but it's on this forum.
guillermohs9 said:
Mm that doesn't sound right. The data partition should be formatted. There is a fastboot command to format user data. I don't know it by heart but it's on this forum.
Click to expand...
Click to collapse
um...cough..cough... I may have deleted the "%fastboot_cmd% erase userdata" command in a feeble attempt to save my data...
I'm guessing I should just pull the trigger on deleting my user data.
Leprechaun7 said:
um...cough..cough... I may have deleted the "%fastboot_cmd% erase userdata" command in a feeble attempt to save my data...
I'm guessing I should just pull the trigger on deleting my user data.
Click to expand...
Click to collapse
That may be it. Always back up first. Anyway, it may be worth the shot to try enter a PIN. Did you use a pattern or pin? You can translate a pattern to a PIN, it worked for me on recoveries on other devices...
When it asks for decryption by PIN and you've been using a pattern, I was able to "translate" pattern to pin using the following matrix:
1 2 3
4 5 6
7 8 9
So a diagonal line from bottom left to top right would translate to a pin "753" unless 5 is already used by another line in which case you'd go directly from 7 to 3.
guillermohs9 said:
That may be it. Always back up first. Anyway, it may be worth the shot to try enter a PIN. Did you use a pattern or pin? You can translate a pattern to a PIN, it worked for me on recoveries on other devices...
When it asks for decryption by PIN and you've been using a pattern, I was able to "translate" pattern to pin using the following matrix:
1 2 3
4 5 6
7 8 9
So a diagonal line from bottom left to top right would translate to a pin "753" unless 5 is already used by another line in which case you'd go directly from 7 to 3.
Click to expand...
Click to collapse
Thanks so much. I have a pin and have tried it many times, no luck. I actually bricked my phone in the first place trying to get TWRP and root (for Titanium Backup). I'm backup crazy. I might try to get TWRP working again and backup before I mess with the password anymore.
Leprechaun7 said:
Thanks so much. I have a pin and have tried it many times, no luck. I actually bricked my phone in the first place trying to get TWRP and root (for Titanium Backup). I'm backup crazy. I might try to get TWRP working again and backup before I mess with the password anymore.
Click to expand...
Click to collapse
Well, good luck. Last resort, flash_all without modifications and start from there.