Related
I recently discovered this, and I thought it would be of some benefit to those who are wanting to unlock, modify partitions, etc without the need to flash derpunlock.sbf or modify your photon in any way. What you need to do this:
1) fastboot for Windows or Linux
2) unlocked RDL3 (ramloader) which I am providing
The process is very simple, reboot your Motorola Photon, and hold the volume down button and power button. You will see "fastboot" on the screen, now press volume up. Connect your phone to your computer, and issue the following command which I discovered:
[email protected]:~$ fastboot flash rdl.bin RDL3_unlocked.smg
sending 'rdl.bin' (3072 KB)...
OKAY [ 0.193s]
writing 'rdl.bin'...
OKAY [ 0.000s]
finished. total time: 0.193s
This will load the unlocked ramloader (unlocked will be displayed at the top even if your phone is locked) which is normally only loaded into ram when flashing an SBF! Amazing, I know. Now you can do all kinds of stuff and you've made no modifications, just issue a "fastboot reboot" and nothing has been modified. Now you are able to erase boot, recovery, oem unlock, etc. Here is an example after you have executed the above. This is just me restoring my default boot and recovery partitions which you can't do from your locked bootloader:
[email protected]:~$ fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.739s]
finished. total time: 0.739s
[email protected]:~/Desktop/SMG$ fastboot flash recovery CG58_0x00000120.smg sending 'recovery' (8192 KB)...
OKAY [ 8.760s]
writing 'recovery'...
OKAY [ 1.013s]
finished. total time: 9.773s
[email protected]:~/Desktop/SMG$ fastboot erase boot
erasing 'boot'...
OKAY [ 0.761s]
finished. total time: 0.761s
[email protected]:~/Desktop/SMG$ fastboot flash boot CG59_0x00000130.smg
sending 'boot' (8192 KB)...
OKAY [ 8.800s]
writing 'boot'...
OKAY [ 0.697s]
finished. total time: 9.497s
good progress on it
You can actually unlock the radio with the stock locked bootloader still in place (derpunlock.sbf flashing no longer needed):
[email protected]:~/Desktop/SMG_derpunlock$ fastboot flash rdl.bin RDL3_unlocked.smg
sending 'rdl.bin' (3072 KB)...
OKAY [ 0.193s]
writing 'rdl.bin'...
OKAY [ 0.000s]
finished. total time: 0.193s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock
...
(bootloader) Unlocking your device can permanently VOID your warranty.
(bootloader) This process cannot be reversed. If you wish to proceed,
(bootloader) reissue the unlock OEM command containing the unique ID
(bootloader) of your device: XXXXXXXXXXXXXXXX
OKAY [ 0.006s]
finished. total time: 0.006s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock XXXXXXXXXXXXXXXX
...
(bootloader) Device is already unlocked
OKAY [ 0.003s]
finished. total time: 0.003s
[email protected]:~/Desktop/SMG_derpunlock$
4G ?
Has anyone tried this method and retained 4G?
scottgl9 said:
You can actually unlock the radio with the stock locked bootloader still in place (derpunlock.sbf flashing no longer needed):
[email protected]:~/Desktop/SMG_derpunlock$ fastboot flash rdl.bin RDL3_unlocked.smg
sending 'rdl.bin' (3072 KB)...
OKAY [ 0.193s]
writing 'rdl.bin'...
OKAY [ 0.000s]
finished. total time: 0.193s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock
...
(bootloader) Unlocking your device can permanently VOID your warranty.
(bootloader) This process cannot be reversed. If you wish to proceed,
(bootloader) reissue the unlock OEM command containing the unique ID
(bootloader) of your device: XXXXXXXXXXXXXXXX
OKAY [ 0.006s]
finished. total time: 0.006s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock XXXXXXXXXXXXXXXX
...
(bootloader) Device is already unlocked
OKAY [ 0.003s]
finished. total time: 0.003s
[email protected]:~/Desktop/SMG_derpunlock$
Click to expand...
Click to collapse
what would be the process coming from locked stock _6, would i just flash clock work mod, flash rom.zip then OP's inputs?
bigslanki said:
what would be the process coming from locked stock _6, would i just flash clock work mod, flash rom.zip then OP's inputs?
Click to expand...
Click to collapse
The process of loading the unlocked ramloader is the same regardless of your firmware, even if the bootloader is 'locked'. The ramloader is just that, its written to ram, and so when the phone is reset the code is cleared out of memory. This means to unlock your radio, you don't have to flash anything to your ram, flashing rdl.bin basically just loads the ramloader to executable memory, then jumps to it. I'm still working on figuring out how to use this to chain load a custom recovery.
Love this! Keep up the good work!
So can I flash CWM after this kind of unlock the bootloader and then custom rom.
Sent from my SPH-D710 using XDA
Will this be useful for the ones that flash the electrify rom on the photon?
Sent from my MB855 using XDA
may you attach stock recovery here? thanks
rrusek said:
Has anyone tried this method and retained 4G?
Click to expand...
Click to collapse
+1
4G confirmed working or not?
I like what I m reading. Sounds like this would be the saving grace for those photon users stuck on an electrify rom (and yeah I m one of them!). Please let us know when you get to rewrite system with a custom rom with this method!
dito33 said:
So can I flash CWM after this kind of unlock the bootloader and then custom rom.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Not yet, you can flash it but it is not yet bootable since I haven't figured out yet how to jump to recovery from the ramloader (you'll probably get an error 2 if you flash CWM then boot to recovery). After you reset your phone, rdl.bin gets cleared out so the same protection mechanisms are still in the bootloader. It's something I'm working on.
firtermish said:
I like what I m reading. Sounds like this would be the saving grace for those photon users stuck on an electrify rom (and yeah I m one of them!). Please let us know when you get to rewrite system with a custom rom with this method!
Click to expand...
Click to collapse
I already can. just do the following:
fastboot flash rdl.bin RDL3_unlocked.smg
fastboot erase system
fastboot flash system your_system_file.smg
fastboot erase boot
fastboot flash boot your_boot.smg
fastboot reboot
EDIT: file extension doesn't really matter, can be smg or img
Theres also updating from fastboot using a zip file, I'm not 100% sure if this works the same as in recovery:
update <filename> reflash device from update.zip
jortiz12885 said:
Will this be useful for the ones that flash the electrify rom on the photon?
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Nope. I just tried and it doesn't work. I get error on phone like below.
1c10d60
SVF:106:1:2
sec_exception: b655, eddc, eb
Anyone knows what that is?
herach said:
Nope. I just tried and it doesn't work. I get error on phone like below.
1c10d60
SVF:106:1:2
sec_exception: b655, eddc, eb
Anyone knows what that is?
Click to expand...
Click to collapse
At what point did you receive the error?
scottgl9 said:
At what point did you receive the error?
Click to expand...
Click to collapse
After the Fastboot. It does Fastboot successfully but it gives the error on the phone screen.
herach said:
After the Fastboot. It does Fastboot successfully but it gives the error on the phone screen.
Click to expand...
Click to collapse
It looks like it is some sort of security error(possibly a failed sigcheck or something).
Lightsword1942 said:
It looks like it is some sort of security error(possibly a failed sigcheck or something).
Click to expand...
Click to collapse
I'm pretty sure the reason you're receiving this error is because this RDL is from derpunlock.sbf from photon_pudding.rar. I'll post the unlocked pudding electrify ramloader.
Attached is the unlocked pudding electrify ramloader, run:
fastboot flash rdl.bin RDL3_unlocked_electrify.smg
scottgl9 said:
I'm pretty sure the reason you're receiving this error is because this RDL is from derpunlock.sbf from photon_pudding.rar. I'll post the unlocked pudding electrify ramloader.
Attached is the unlocked pudding electrify ramloader, run:
fastboot flash rdl.bin RDL3_unlocked_electrify.smg
Click to expand...
Click to collapse
Tried that. It reboots the device and the device stays on Moto Logo Dual-core Screen with nothing written on it and nothing else works.
Hey everyone!!
My device is stuck at boot logo.
If i try to open the recovery it also stuck on teamwin logo.
My device is totally unusable now.
please help!!
Thanks in advance.
shubhm said:
Hey everyone!!
My device is stuck at boot logo.
If i try to open the recovery it also stuck on teamwin logo.
My device is totally unusable now.
please help!!
Thanks in advance.
Click to expand...
Click to collapse
Try reflashing the TWRP recovery using fastboot. You can find the steps here.
LijoDXL said:
Try reflashing the TWRP recovery using fastboot. You can find the steps here.
Click to expand...
Click to collapse
Gives Mismatched partition size(recovery) error.
shubhm said:
Gives Mismatched partition size(recovery) error.
Click to expand...
Click to collapse
Mismatched partition size(recovery) should not be a problem, it just saying that your recovery is smaller in size than the stock recovery. Did you got this problem after downgrading from lollipop? As a trial and error thing, try to flash stock recovery and see if it boots.
LijoDXL said:
Mismatched partition size(recovery) should not be a problem, it just saying that your recovery is smaller in size than the stock recovery. Did you got this problem after downgrading from lollipop? As a trial and error thing, try to flash stock recovery and see if it boots.
Click to expand...
Click to collapse
Flashed stock recovery.
got this error in cmd
C:\Users\MOHIT\Desktop\ooo\mfastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.341s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.929s
and on booting in recovery same teamwin logo appears.
Try this command mfastboot flash partition gpt.bin (you must have the stock firmware in the directory)
shubhm said:
Flashed stock recovery.
got this error in cmd
C:\Users\MOHIT\Desktop\ooo\mfastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.341s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.929s
and on booting in recovery same teamwin logo appears.
Click to expand...
Click to collapse
try flashing whole stock 4.4.4 rom. and you didn't mention what you did (upgraded to lollipop/downgraded/ flashed any specific rom) which led to this problem.
zeshan94 said:
try flashing whole stock 4.4.4 rom. and you didn't mention what you did (upgraded to lollipop/downgraded/ flashed any specific rom) which led to this problem.
Click to expand...
Click to collapse
i had put my phone on charging. Then it itself got off. On pressing power button it was stuck on bootlogo.
I did a reset to factory using twrp with lollipop and the phone is stuck at moto logo... help please
LijoDXL said:
Mismatched partition size(recovery) should not be a problem, it just saying that your recovery is smaller in size than the stock recovery. Did you got this problem after downgrading from lollipop? As a trial and error thing, try to flash stock recovery and see if it boots.
Click to expand...
Click to collapse
i got the problem while downgrading from lollipop ...i tried flashing cm12.1 from 4.4.4 stock....but now i am stuck with the boot logo...help please!
Long story short, I tried to flash new rom on my Mt2-L02 mate2 and failed and its bootlooping (at Huawei Ascend screen and keep rebooting) now. using the SDcard udload to load new rom don't work either. I cannot go into recovery, or boot into system.
My phone is bootloader unlocked, so I tried to flash (extract from a rom) boot.img, recovery.img and is ok but when flashing system.img, it stucked in writing 'system'... for long time.... so I tried fastboot erase system -w and get FAILED (remote: Command not allowed)... why is it so? my phone is already unlocked. I tried unlock again and flash the system.img, same problem.
So... I'm screwed?
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
kimtyson said:
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
Click to expand...
Click to collapse
Only have 1 pc, yes, I'm flashing MT2-L02 ROM, tried alot of version but discovered only these version rom (b408, b603, b606, b607) able to write the system.img, original out of box android version for my phone is 4.4.2. but still bootlooping after flashing boot.img, recovery.img and system.img. I think only custom recovery can save now, but there is none for this model... or maybe there is no hope for my phone? Maybe my phone got some system modified lock so that I'm not able to erase using flashboot?
C:\adb>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
C:\adb>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
If I'm able to erase those, I'm might solved the bootlooping problem..
Try using this thread as reference, http://forum.xda-developers.com/asc...to-fix-soft-bricked-phone-using-twrp-t2886630. It's for a different model so just use your stock ROM in place of the L03 ROM. I'm not sure how to help beyond that. There has to be a way to return to stock on the L02.
Maybe this message is late, pls try following
http://pan.baidu.com/s/1dDpc4eP
http://www.huaweirom.com/rom/mate2/2619.html
usb flash instructions:
http://www.huaweirom.com/guide/2621.html
You may need to use google translate since all the info is in Chinese
Basically they are saying you should use B117 if B4xx not working.
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
prasannazx said:
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
Click to expand...
Click to collapse
Use mega unbrick guide if you tried all other procedure.
I was caught up in the same situation. Follow the mega unbrick guide and your phone will be back to normal.
link to the mega unbrick please..
Asmmahin said:
link to the mega unbrick please..
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Is mega unbrick or hard unbrick is same ?
amgh said:
Is mega unbrick or hard unbrick is same ?
Click to expand...
Click to collapse
Both are same.some call it hard unbrick or some mega that's it.
1.) Make sure driver signature enforcement is disabled.
2) Download this :- http://www.mediafire.com/download/4aqwyi3g1d6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
4) press vol up button for 10s and plug it in pc keeping pressed
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
5) now flash it with msmtool u can downloa th 47mb one in comments
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6) the phone now should have the stock recovery
---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------
sabrinano24 said:
1.) Make sure driver signature enforcement is disabled.
2) Download this :- http://www.mediafire.com/download/4aqwyi3g1d6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
4) press vol up button for 10s and plug it in pc keeping pressed
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
5) now flash it with msmtool u can downloa th 47mb one in comments
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6) the phone now should have the stock recovery
Click to expand...
Click to collapse
ps= remove the space in the frist link
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
did you install a rom after the fix ?
After fix, it's the official ROM so déveloper > OEM and USB debuging
adb reboot bootloader
Adb oem unlock ans After the command i write
prasannazx said:
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
Click to expand...
Click to collapse
That is because the kernel and boot loader used for 14.1 is different you need to update the kernel.
Follow Mega unbrick guide carefully to unbrick the phone.
sabrinano24 said:
did you install a rom after the fix ?
Click to expand...
Click to collapse
After the fix, i've OOS, and that all.
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
I had same issue you need to flash different TWRP. If your on 2.X.X TWRP 3.0.2 . If you have updated to 3.X.X then 3.0.3. If you have issues with 3.0.3 you can try twrp 3.0.2-0 or bluesparks 3.0.2-1 V41.
just flash the arsenic-kernel everything will be fine.. https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
The problem is not the kernel but the bootloader so how to change/update recovery?
Bjr49000 said:
The problem is not the kernel but the bootloader so how to change/update recovery?
Click to expand...
Click to collapse
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
I used to have this problem. You need to flash the new bootloader, sometimes updates and whatnot doesn't flash it for you. If the zip doesn't work you can try finding the fastboot partition image and flashing to aboot (instead of fastboot flash recovery recovery.img when flashing a twrp build for example, it would be fastboot flash aboot emmc_appsboot.mbn). There was a post on the oneplus forums where the files could be found, just google dtb not found error.
I've bean trying to go to twrp and every time it only says
downloading 'boot.img'...
OKAY [ 1.523s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 3.874s
can anyone help and yes i did unlock the bootloader
Did you try
Bash:
fastboot boot twrp.img
i did
dizziboi said:
I've bean trying to go to twrp and every time it only says
downloading 'boot.img'...
OKAY [ 1.523s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 3.874s
can anyone help and yes i did unlock the bootloader
Click to expand...
Click to collapse
TWRP recovery is not boot.img, but is recovery.img
i fixed it
dizziboi said:
i fixed it
Click to expand...
Click to collapse
So how did you go about fixing it? Thanks for sharing your method!
i found a way to get back into recovery mode then i sideloaded the android 12 dev preview