Related
Since all over Internet it says that KDZ cannot be decrypted, how are made FASBOOT roms with KDZ extension?
And what is difference between stock and fastboot roms?
As I can see only thing is ability to flash recovery image, for making backup /restore of roms "on the fly"
there are ways to extract kdz files
read this thread
h*tp://android.modaco.com/content-page/320950/recovery-on-our-device/page/20/
the only difference is that you can use fastboot commands on your phone to flash new roms and recoveries, and lose your warrenty
But it looks like that when you first time flash with fastboot , you can only flash others roms with fastfoot. Normal KDZ wont work on phone, stucked after blue LG animation.
I`m having problems with booting into recovery on my OnePlus2.
This started after I did an update to OxygenOS 3.0 (beta) from my previously working TWRP.
OS itself is working, but I noticed that phone must be rerooted.. and here I found that Power + VolDown is not working anymore (phone is just stucked on 1+ logo).
OKay... I decided to reflash TWRP (who knows what may happened with it after update) but nothing helped. I tried different versions, even original OP2 recovery.. but result is always the same.
How I was trying to reflash:
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (31700 KB)...
OKAY [ 0.702s]
writing 'recovery'...
OKAY [ 0.248s]
finished. total time: 0.950s
but booting is always giving DTB error:
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.713s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.781s
I saw in other posts that dtb means broken image/etc, but I tried several and all were with the same result.
What else I can try? Please note that regular booting is working with no problems. The only problem I have is booting into recovery (with buttons and with fastboot).
Posted in wrong section. Should be in Q&A.
However to answer your question.
This has the same bootloader as H2OS Marshmallow. So, please TWRP users flash the way as mentioned below. Else you won't be able to boot into old twrp.
DOWNLOADS :-
recovery.img :- https://www.androidfilehost.com/?fid=24459283995297945
Step 1 :- Clean flash the ROM with new boootloader.
Step 2 :- From TWRP,go to Install Menu,click on Images button.
Step 3 :- Select the recovery.img you just downloaded.Select Recovery.Swipe to flash.
Step 4 :- From TWRP Home,reboot to recovery.
Step 5 :- Clean flash ROM with new bootloader again.
Step 6 :- Reboot into system !!!
Thanks and sorry for the wrong section.
Can you please give a bit more info on step 1 ? what rom to flash and how (current recovery is not working) ?
taha198 said:
Posted in wrong section. Should be in Q&A.
However to answer your question.
This has the same bootloader as H2OS Marshmallow. So, please TWRP users flash the way as mentioned below. Else you won't be able to boot into old twrp.
DOWNLOADS :-
recovery.img :- https://www.androidfilehost.com/?fid=24459283995297945
Step 1 :- Clean flash the ROM with new boootloader.
Step 2 :- From TWRP,go to Install Menu,click on Images button.
Step 3 :- Select the recovery.img you just downloaded.Select Recovery.Swipe to flash.
Step 4 :- From TWRP Home,reboot to recovery.
Step 5 :- Clean flash ROM with new bootloader again.
Step 6 :- Reboot into system !!!
Click to expand...
Click to collapse
Follow guide this guide
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Now it is clear. you gave me an instruction to what I should do to avoid the situation where I am now. but there is also another instruction how to fix my problem.
Thanks one again!
taha198 said:
Follow guide this guide
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
It seems you are flashing the wrong version of TWRP. The version you are flashing isn't going to work on OOS 3.0 Beta. You need specifically the H2-MM TWRP 3.0.0-1 version, which, like the previous posters listed can be downloaded here:
https://www.androidfilehost.com/?fid=24459283995297945
If you are flashing a version that you downloaded direct from TWRP's website, it won't work.
I tested different versions, including 3.0.x mentioned by you. all of them gave the same result.
Btw, the recovery tool in the link above already fixed my problem.
madferretx said:
It seems you are flashing the wrong version of TWRP. The version you are flashing isn't going to work on OOS 3.0 Beta. You need specifically the H2-MM TWRP 3.0.0-1 version, which, like the previous posters listed can be downloaded here:
https://www.androidfilehost.com/?fid=24459283995297945
If you are flashing a version that you downloaded direct from TWRP's website, it won't work.
Click to expand...
Click to collapse
Delphir said:
I tested different versions, including 3.0.x mentioned by you. all of them gave the same result.
Btw, the recovery tool in the link above already fixed my problem.
Click to expand...
Click to collapse
Could you describe exactly what did you do? At the link that you mention there is 3 methods and different recovery tools.
I followed "Method 1" from the link and then flashed TWRP recovery on top of it - this way it worked with no problems. Flashing TWRP (different versions) without this recovery tool was always unsuccessful.
Well, as long as you flash the chinese HydrogenOS version of TWRP you should get a bootable recover system.
Best regards
Peter
I recently rooted my OnePlus 2.
The bootloader is unlocked.
The twrp recovery was working fine till I flashed to oxygen os 2.0.0
Now the OnePlus2 is not booting into recovery.
There is a oxygen os update (3.5.8) available which shows in the system updates section in settings.
Can I update to this without the recovery??!
Will that help to go back to twrp recovery?!
Please help
Nandish C said:
I recently rooted my OnePlus 2.
The bootloader is unlocked.
The twrp recovery was working fine till I flashed to oxygen os 2.0.0
Now the OnePlus2 is not booting into recovery.
There is a oxygen os update (3.5.8) available which shows in the system updates section in settings.
Can I update to this without the recovery??!
Will that help to go back to twrp recovery?!
Please help
Click to expand...
Click to collapse
Flashing stock firmware will overwrite twrp, so always flash OOS and twrp after it in case you want to keep it, twrp can flash the twrp.img file, not only zips, I never used OOS2 but actually you should have stock recovery back by flashing OOS, it seems that something went wrong. Just flash twrp again, like the first time you did it, if you want to go back to stock including recovery flash OOS full zip again and reboot...
Only OOS will overwrite twrp, custom roms won't
Sent from my OnePlus 2 using XDA Labs
I have a doubt that,In some of the devices we can install twrp using adb commands without rooting our device. But in many new generation devices there are always posts or videos about, first rooting the devices and then installing twrp.
So, what are the reasons that we don't directly flash twrp on moto g5 using adb commands, and first we prefer getting device unlocked by getting unlock code.
And for my general doubt can anyone please explain me what does "unlocking a bootloader" means and what does "OEM" means. Also if i unlock OEM using developer options it doesn't show up in the bootloader menu.
I request to please explain elaborately as I am just new to all this.
To flash Twrp you need unlocked bootloader. Rooting has nothing to do with it, that is OS side. If bootloader is unlocked, you can fastboot flash Twrp. However, I suggest if you are unsure but want to have custom ROMs, you should use the tool that does it all for you.
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
This tool will get your unlock information which you must submit on the moto unlock site. They will send you email with your bootloader key. Once you unlock bootloader through the tool, you can also flash twrp through the tool. When you have flashed twrp, you must wipe data in twrp and flash SuperSU to get past the data encryption. There is plenty of info around here on these subjects, I would suggest to read very carefully all the guides before continuing.
Hi guys
I destroyed my leEco le pro 3 x722
After passing the custom rom
Now the device is locked on fastboot only
There is no system and no recovery
The problem I have now is the decryption. If the oem unlock is I can update it. Please help oem unlock
The device does not respond to commands
Everything is written
PS C: \ adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (39337 KB) ...
OKAY [0.895s]
writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.940s
How can oem unlock in another way ????
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
sk8223 said:
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
Click to expand...
Click to collapse
You installed Batyan's 20s developer ROM
In the past I opened the boot loader but when I tried Rum Miwi did not work
I wanted to go back to the official 26s Rom
Unfortunately everything has lost and the device is ruined
I did not see the warning of testing
How is the solution now
The official 26s ROM locks the bootloader down. If you try to flash anything through it, you'll end up with a bricked device. I'm sorry.
Did you say that you tried to install MIUI? I don't know what "Miwi" is. All I know is, that's something you shouldn't have done.
I'm not sure if you successfully flashed the official 26s ROM or not, and then tried to flash something else... that would cause a brick for sure, AFAIK.
Again, post to the thread about bricked phones that I linked. There are quite a few people with bricks here. Hopefully a solution will present itself soon. Until then, hold onto your phone and hope. :/
sk8223 said:
The official 26s ROM locks the bootloader down. If you try to flash anything through it, you'll end up with a bricked device. I'm sorry.
Did you say that you tried to install MIUI? I don't know what "Miwi" is. All I know is, that's something you shouldn't have done.
I'm not sure if you successfully flashed the official 26s ROM or not, and then tried to flash something else... that would cause a brick for sure, AFAIK.
Again, post to the thread about bricked phones that I linked. There are quite a few people with bricks here. Hopefully a solution will present itself soon. Until then, hold onto your phone and hope. :/
Click to expand...
Click to collapse
Yes, unfortunately, the device is locked
Updated 26s
The manufacturer must find us a solution
Thank you for the kind word
sk8223 said:
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
Click to expand...
Click to collapse
So your fastboot works just flash the boot loader .
Nice. I finally able to unlock and root. Although I just wished, the first page gets updated with the current method. I have to go through all the pages to fully understand what to do.
So basically a quick roundup:
go in fastboot
flash emmc_appsboot.mbn inside the zip.
reboot
it will ask for a password, just ignore it and reboot back to fastboot
unlock the bootloader
flash twrp
boot into twrp
format phone
then you're done!
Sent from my LEX727 using xda premium
mchlbenner said:
So your fastboot works just flash the boot loader .
Nice. I finally able to unlock and root. Although I just wished, the first page gets updated with the current method. I have to go through all the pages to fully understand what to do.
So basically a quick roundup:
go in fastboot
flash emmc_appsboot.mbn inside the zip.
reboot
it will ask for a password, just ignore it and reboot back to fastboot
unlock the bootloader
flash twrp
boot into twrp
format phone
then you're done!
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Unfortunately I do not know how to scroll
Our Lord is wrong
PS C:\adb> fastboot devices
7b61ab59 fastboot
PS C:\adb> fastboot flash emmc_appsboot.mbn
unknown partition 'emmc_appsboot.mbn'
error: cannot determine image filename for 'emmc_appsboot.mbn'
PS C:\adb> fastboot flash emmc_appsboot.zip
unknown partition 'emmc_appsboot.zip'
error: cannot determine image filename for 'emmc_appsboot.zip'
That file has to be in adb main file.
Sent from my LEX727 using xda premium
mchlbenner said:
That file has to be in adb main file.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
If you have a file please give me the link
Or where I find it
I think you talk about different terminals.
The X722 with 26S strock brick CAN NOT FLASH FOR FASTBOOT.
Greetings.
fastboot flash emmc_appsboot.mbn <- that command is not correct, that's why it errors saying partition not found. The partition to flash is missing, not sure what partition is supposed to be specified, but the command should look like this...... fastboot flash 'thecorrectpartition' emmc_appsboot.mbn
meangreenie said:
fastboot flash emmc_appsboot.mbn <- that command is not correct, that's why it errors saying partition not found. The partition to flash is missing, not sure what partition is supposed to be specified, but the command should look like this...... fastboot flash 'thecorrectpartition' emmc_appsboot.mbn
Click to expand...
Click to collapse
Explain more please
What should i do
Put the file in disk c
Show me this message
PS C:\adb> fastboot flash thecorrectpartition emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'thecorrectpartition' (791 KB)...
OKAY [ 0.034s]
writing 'thecorrectpartition'...
toufik_d said:
Explain more please
What should i do
Put the file in disk c
Show me this message
PS C:\adb> fastboot flash thecorrectpartition emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'thecorrectpartition' (791 KB)...
OKAY [ 0.034s]
writing 'thecorrectpartition'...
Click to expand...
Click to collapse
Your terminal is blocked. It does not have a solution.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
What they say is for x720 and x727 NOT FOR X722.
The command they say is:
fastboot flash aboot emmc_appsboot.mbn
but as I say, it's NOT GOING TO WORK.
Greetings.
how you wiped everything?
do you have recovery?
F.J.V said:
Your terminal is blocked. It does not have a solution.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
What they say is for x720 and x727 NOT FOR X722.
The command they say is:
fastboot flash aboot emmc_appsboot.mbn
but as I say, it's NOT GOING TO WORK.
Greetings.
Click to expand...
Click to collapse
That command work for me.
Lex 727 21s.
Sent from my LEX727 using xda premium
mchlbenner said:
That command work for me.
Lex 727 21s.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Of course.
That's what I say, for X720 and X727.
For X722 DOES NOT WORK
Greetings.
danielpinto8zz6 said:
how you wiped everything?
do you have recovery?
Click to expand...
Click to collapse
I wanted to restore the official order
The device is running on fastboot only
Hi there! I recently got my first android phone so wanted to install Lineage os 15.1 but messed it up right away as it's in now in boot loop! Here's what I did:
It was on Android 8.0 angler-opr5.170623.011-factory-0e60ceb6 but I unlocked its boot loader and installed custom recovery and I successfully flashed in the fastboot , vendor, radio and boot loader from Lineage OS 15.1 thread, now instead of following the rest of instructions, I madly decided to reboot the device using fastboot reboot and now I don't see anything except these colored circles which is what boot loop probably is! Please help me find a solution! Thank you!
edited: I have successfully entered into bootloader mode but don't know how to proceed!
I'd flash all the stock firmware in bootloader and start over. Grab the latest firmware package from Google's site, extract it, then run:
fastboot flash bootloader bootloader.img (name changes with version)
fastboot reboot-bootloader
fastboot flash radio radio.img (name changes with version)
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Reboot to system
You'll probably have to flash your custom recovery again in bootloader after the first boot. It usually reverts back to stock.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page1
Part 10 in the thread above^
I recommend you installing an easy official ROM.
With them all you need to do is a clean flash of the ROM
Since I'm still a noob so I need to muster up courage to proceed but I really appreciate your valuable input guys!! Cheers!! :good:
edited: I have successfully installed stock firmware! cheers!