hiya guys! So I just recently unlocked my d6503's bootloader after years of running it on stock. I wanted to access fastboot features for this device. My goal at the moment is edit to add just one line in build.prop to enable Multi-window. Right now my phone is on stock stock MM 23.5.A.1.291. I already tried flashing TWRP successfully to check if I can really edit the build.prop via fastboot commands (newbie here ) which I did. Right now my dillema is that either it's flashing the custom recovery, an unlocked bootloader, or simply editing the build.prop trips SafetyNet.
I am failing miserably to temporarily boot TWRP via fastboot. It gives me this feedback:
downloading 'boot.img'... OKAY. booting... FAILED (remote: dtb not found).
I did use the latest version of TWRP and even went ahead and used 2 of the previous versions via fastboot to no avail.
Related
im trying to flash cwm custom recovery rom. fastboot flash recovery <downloaded img> yielded a bootloader variable not supported (error). mfastboot flash recovery <downloaded img> yielded sending 'recovery' <7892 kb>..., okay [0.610s], writing 'recovery'..., okay [1.614s], finished. total time: 2.224s. but when i reboot into recovery, i get the stock recovery.
ive searched around online. ive looked for the stock rom file with no success (using android commander) to rename it. i know it must be there, but this is my first time rooting, unlocking the bootloader, and flashing roms. heck i cant even see the cwm rom written.
being a noobie im probably just missing something very basic and could use some detailed instructions to get past this point (my technical vocabulary in this area is very limited). i'm trying to use manual tools, so id like to stick with learning the manual way please.
btw, when i'm in fastboot mode other than rebooting the phone via 3 finger salute is there a terminal command to get back to adb mode? after flashing, i wanted to go back to adb to issue a reboot command from there. i read my flash might be overwritten as i reboot my the stock rom.
thanks in advance for the help.
Tools being used:
adb
fastboot
Android Commander
The phone:
Motorola Droid Razr HD (CDMA) running 4.1.1 build 9.8.10_39
Rooted via Motochopper
Bootloader unlocked via Motopocalypse
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
Code:
fastboot flash recovery recovery.img
the following error came:
Code:
sending 'recovery' (10240 KB)...
OKAY [ 0.417s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.430s
I searched and I got to know that this may be because of bootloader lock.
So I tried the command
Code:
fastboot oem unlock
and
Code:
fastboot flashing unlock
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
sumit77seo said:
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
the following error came:
I searched and I got to know that this may be because of bootloader lock.
So I tried the command and
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
Click to expand...
Click to collapse
You can try putting the stock ROM zip file on the root of your sdcard (As in not located in any sub folders) and renaming the ROM file to update.zip then use the stock recovery to flash the ROM. Let me know if you still have questions!
hello folks,
I was on Android 7.0 on my Moto G 4.
I unlocked the bootloader, installed TWRP and flashed Android 7.1.2 and then 8.0 a week later.
Had backed up the stock Android 7.0 and the 7.1.2 also before i went to 8.0.
Today i restored the system back to the Stock version backup (7.0) and rebooted it.
Everything went fine. Then there was the notification of the Android security update. I proceeded with the install and it started rebooting.
In the reboot it stuck with the error message for bootlocker being unlocked and came back to TWRP. Even after going to reboot it only came back to TWRP. I then tried logged into the bootloader and tried to relock the bootloader using the commands (i was using mfastboot)
mfastboot oem lock
mfastboot flashing lock
mfastboot oem relock
it showed me an error for the 'relock' that it was an invalid command. Later i found that the unlock key also needs to be supplied (not sure). Then i tried the commands again after installing fastboot, and from the stock firmware folder.
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
it showed me an error on this l9ast command saying invalid boot mode.
Any advise on how to start the relock process cleanly? my worry is if the system is bricked !
I was missing the stock moto so i need to go back there, all the flashing didn't seem too worthwhile.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Solution is in mentions by echo92 in the post by tywinlannister7 below
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
anoopgkris said:
hello folks,
I was on Android 7.0 on my Moto G 4.
I unlocked the bootloader, installed TWRP and flashed Android 7.1.2 and then 8.0 a week later.
Had backed up the stock Android 7.0 and the 7.1.2 also before i went to 8.0.
Today i restored the system back to the Stock version backup (7.0) and rebooted it.
Everything went fine. Then there was the notification of the Android security update. I proceeded with the install and it started rebooting.
In the reboot it stuck with the error message for bootlocker being unlocked and came back to TWRP. Even after going to reboot it only came back to TWRP. I then tried logged into the bootloader and tried to relock the bootloader using the commands (i was using mfastboot)
mfastboot oem lock
mfastboot flashing lock
mfastboot oem relock
it showed me an error for the 'relock' that it was an invalid command. Later i found that the unlock key also needs to be supplied (not sure). Then i tried the commands again after installing fastboot, and from the stock firmware folder.
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
it showed me an error on this last command saying invalid boot mode.
Any advise on how to start the relock process cleanly? my worry is if the system is bricked !
I was missing the stock moto so i need to go back there, all the flashing didn't seem too worthwhile.
Click to expand...
Click to collapse
I'm not sure about this. As far as I know you can only relock the bootloader after a full (fastboot) wipe and install of the latest stockrom.
In the (far) past I managed to relock the bootloader of my Moto G 2014. Only after trial and error and only after a full flash. A week or so later I unlocked again....
I never relocked my Moto G4 Plus, nor my Moto G5 Plus. Simply because I don't see the need. The times that Motorola provides us with regular stock updates are, apparantly, over....
Thanks, Harro.
I thought that my TWRP would restore it back to stock. I read some half information about relocking and went ahead with the commands.
I also don't know if the USB debug settings are on.
It's shows a preflash verification error on the partition gpt.bin command. Think it's because maybe the stock version i downloaded is a downgrade. Can't find the exact stock for my LATAM dds_cust one. Another G4(Plus) version that was successful for others didn't work too.
Tried to skip and load boot partition but it said invalid boot state.
Need to keep trying different things. At least the bootloader and TWRP recovery are accessible for now.
Regards.
anoopgkris said:
Thanks, Harro.
I thought that my TWRP would restore it back to stock. I read some half information about relocking and went ahead with the commands.
I also don't know if the USB debug settings are on.
It's shows a preflash verification error on the partition gpt.bin command. Think it's because maybe the stock version i downloaded is a downgrade. Can't find the exact stock for my LATAM dds_cust one. Another G4(Plus) version that was successful for others didn't work too.
Tried to skip and load boot partition but it said invalid boot state.
Need to keep trying different things. At least the bootloader and TWRP recovery are accessible for now.
Regards.
Click to expand...
Click to collapse
Hi Anoop!
Yes, you'll have find the latest stockrom for your region. Also, a locked bootloader and TWRP is, in my humble opinion, a impossible combination. You'll have to fastboot install the whole rom, including (stock)recovery and the bootloader. And indeed: it's impossible to downgrade the bootloader: trying that will possibly result in a hardbrick...
Thank you, thank you for jumping in to always help.
Really sad that Moto also goes the way of not providing updates that too on a not so old phone. ROMs and the beautiful world of XDA is there, hopefully.
Hi,
So long story short, I tried to get good phone for someone for a good price, I ordered a Xiaomi Mi 10 from China - But it came with a bunch of Chinese bloatware so I wanted to flash the Global ROM and have Google on there
I added it to my Xiaomi account, unlocked the bootloader (waited 168 hours), then followed instructions from a youtube video (
)
It worked well - I used adb to flash TWRP, and was able to install the Global ROM from xiaomi.eu using TWRP (version 12-11) (filename: xiaomi.eu_multi_MI10_V12.2.9.0.RJBCNXM_v12-11)
This worked well and everything went smooth, and I thought I was done, then I wanted to remove the device from my Xiaomi account, so I did remove the device from my account via Mi Cloud, and then I went to factory reset the phone, and then it just keeps booting into Fastboot.
I tried to hold buttons to boot into TWRP (volume UP and Power) but just goes into Fastboot, I tried to flash TWRP again via adb using "fastboot flash recovery twrp.img" but am getting this error when I run "fastboot boot twrp.img" - FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
Please let me know if there is anything I can do - even to get back to the chinese stock ROM
Thanks in advance
Hi all - I solved the problem by using the Global Fastboot ROM and MiFlash tool - I got a CRC error "update sparse crc list failed" but followed some advice to edit the "Flash.all" script and remove the 2 lines that contain "CRC"
Then the Flash process worked and the phone did boot into Global ROM
The xiaomieu stable version has a problem with custom recovery, so you grabbed fastboot.
if you want to use recovery, you need to boot recovery via ADB with the command fastboot boot recovery ....
Do not use on a stable version of xiaomieu recovery via the restart button to recovery
Actually, one can boot to recovery via restart button, but only after flashing the twrp 3.4.0 little turtle.
However, this recovery isn't able to decrypt the partitions, and could be used for flashing ROMs only from OTG drive.
The one that does decrypt and could be used in "normal" way is twrp 3.4.2.1206, but this one can only be booted as you said with fastboot boot recovery.img
I have two N200.
I successfully rooted both of them. Some how the second phone got updated to android 12 and lost the root. Ever since this is a headache. Phone is already unlocked boot loader and shows "Device state - unlocked" in fastboot mode.
I wanted to try booting from the patched boot.img i had earlier (From version 11 i assume) just to see if it works but the command fails:
fastboot boot boot.img
Sending 'boot.img' (98304 KB)
Booting Failed (remote: 'unknown command')
fastboot: error: Command failed
Also maybe this is due to being on android 12? If so how can i downgrade? I downloaded the zip file from:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Thank you.
First, I don't think you can use your previous boot. Scanman has a thread on this forum with all pre-rooted boot files, you just need to match according to the FW you're on. Second, after A12 they don't allow fastboot boot anymore, the file has to be flashed instead with fastboot flash.
Again, make sure you use the correct boot otherwise it won't work and you may cause yourself a bigger headache.