Well, I was using TWRP, everything was good until it started to fail to unmount the system and data partition, is there any fix for it? :crying:
unmount of /system failed; no such volume
script succeded: result was [0.200000]
Click to expand...
Click to collapse
unmount of /data failed; no such volume
script succeded: result was [0.200000]
Click to expand...
Click to collapse
Flash original firmware using fastboot..
rajit said:
Flash original firmware using fastboot..
Click to expand...
Click to collapse
It's still doing the same error :/
And the log? Whats the log when u entered fastboot flash ........ Command?
rajit said:
And the log? Whats the log when u entered fastboot flash ........ Command?
Click to expand...
Click to collapse
http : / / bit.ly / 1PnCdAx
put everything together
Hmm seems everything fine .only comtomize error.. Do one thing..
Flash all system.img......
Flash boot.img
Flash recovery.img
Thn
Fastboot erase userdata
Fastboot erase cache
Fastboot reboot
Dont flash ne thing else
rajit said:
Hmm seems everything fine .only comtomize error.. Do one thing..
Flash all system.img......
Flash boot.img
Flash recovery.img
Thn
Fastboot erase userdata
Fastboot erase cache
Fastboot reboot
Dont flash ne thing else
Click to expand...
Click to collapse
Thanks, I'll try now :good:
rajit said:
Hmm seems everything fine .only comtomize error.. Do one thing..
Flash all system.img......
Flash boot.img
Flash recovery.img
Thn
Fastboot erase userdata
Fastboot erase cache
Fastboot reboot
Dont flash ne thing else
Click to expand...
Click to collapse
Now it is stuck at the Android Moving Animation
Wait for a while it will boot.. First boot take 15min nearly.. Till then check have u flash right firmware ? Look this stuff ... And if this does not boot then again just fastbbot erase cache .. Thn reboot .. Hope it will work
rajit said:
Wait for a while it will boot.. First boot take 15min nearly.. Till then check have u flash right firmware ? Look this stuff ... And if this does not boot then again just fastbbot erase cache .. Thn reboot .. Hope it will work
Click to expand...
Click to collapse
So it's the same as custom roms?
Ok, The Bootanimation showed up
Booting and now it shows to me to choose the language, i will test the recovery now!
One last thing.. If this step not help u to boot thn just flash twrp
Thn fastboot erase system
Fastboot erase cache
Fastboot erase data
Then try to open twrp and flash custom rom . i think u know what is custom rom
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
Remeber dont flash whole file in fimware .its my opinion. Just flash boot system erase cache data thats all tc
rajit said:
One last thing.. If this step not help u to boot thn just flash twrp
Thn fastboot erase system
Fastboot erase cache
Fastboot erase data
Then try to open twrp and flash custom rom . i think u know what is custom rom
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
Remeber dont flash whole file in fimware .its my opinion. Just flash boot system erase cache data thats all tc
Click to expand...
Click to collapse
Yes, I know what Custom ROM is, My Cousin showed it to me (He had an Samsung S3 Neo)
Booting into RR 6.0.1 02/01/2016 build now, but the error still showed up when installing it
Weird, SlimGApps was installed normally
rajit said:
One last thing.. If this step not help u to boot thn just flash twrp
Thn fastboot erase system
Fastboot erase cache
Fastboot erase data
Then try to open twrp and flash custom rom . i think u know what is custom rom
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
Remeber dont flash whole file in fimware .its my opinion. Just flash boot system erase cache data thats all tc
Click to expand...
Click to collapse
I got this error :/
C : \Program Files (x86) \ Minimal ADB and Fastboot > fastboot erase data
erasing 'data'...
(bootloader) Invalid partition name data
FAILED (remote failure)
finished. total time: 0.007s
Tyrone936 said:
I got this error :/
C : \Program Files (x86) \ Minimal ADB and Fastboot > fastboot erase data
erasing 'data'...
(bootloader) Invalid partition name data
FAILED (remote failure)
finished. total time: 0.007s
Click to expand...
Click to collapse
Another error in recovery :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fastboot erase userdata
Fastboot erase cache
I dont why why u geeting this error.. Try other version of recovery.. Try some roaming
Wtf?
My phone is giving me the same thing. It's rooted unlocked and I tried to flash custom roms, but it gives me the same error. I tried to flash a boot image to get rid of the bootloader warning. It says it works it says can enjoy your boot image. But nothing happened. So far I have been unable to install anything new Please help me out. Thank you .
Thanks, but i switched from my surnia.
I had the same issue as the OP. Very annoying to have to flash back to stock. It makes me not want to reflash a custom firmware again for now.
I flashed to stock using RSD Lite. It's much easier to use and less chance of messing up your device.
http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
Maybe this is the same prob I ran into, unless I'm misunderstanding? This thread helped me out, the quote by Q9nap, "Use rm -rf instead of formatting". Just a simple change in the settings..
forum.xda-developers.com/moto-e-2015/development/recovery-moto-e-lte-twrp-2-8-6-0-rm-rf-t3135232
use the squid twrp (surnia) instead. the official one seems have a bug on unmounting system partition when flashing custom roms
Related
I hate to be a newbie but I really read through the entire troubleshooting guide and didn't really understand how to proceed.
I have a rooted Evo 4G LTE with latest stock ROM and TWRP recovery installed (2.5).
This morning my device was pissing me off so I thought it would be a good idea to flash it with CyanogenMod. I went into TWRP, wiped EVERYTHING. loaded the CYanogen Zip on the SD Card, and flashed. Device went right into soft brick.
Tried to flash a couple of other ROMS, also didn't work. in the mean time I discovered BeanStalk which I think is the ROM I want to use.
I have ADB / Fastboot / Latest drivers installed on my computer but when I try to do anything it acts like the device is not connected.
Any advice how to proceed?
From the troubleshooting guide I think my problem might be:
Missing ROM Due to a misunderstanding, you have already wiped all ROM data from phone (cache, dalvik, and system) and fastboot flashed the kernel. Now phone hangs on HTC boot screen and will not load Android. Only the kernel has been flashed, the screen hangs because there is no OS to load. Fear not, return to recovery and flash the ROM package that your boot.image originated from. Now select reboot to system and wait for your phone to restart. The kernel will boot, your OS will load, and all will be right with the world.
Click to expand...
Click to collapse
But I already tried to flash the rom package ( I think).
Help would be much appreciated! thank you!
yoerz said:
I hate to be a newbie but I really read through the entire troubleshooting guide and didn't really understand how to proceed.
I have a rooted Evo 4G LTE with latest stock ROM and TWRP recovery installed (2.5).
This morning my device was pissing me off so I thought it would be a good idea to flash it with CyanogenMod. I went into TWRP, wiped EVERYTHING. loaded the CYanogen Zip on the SD Card, and flashed. Device went right into soft brick.
Tried to flash a couple of other ROMS, also didn't work. in the mean time I discovered BeanStalk which I think is the ROM I want to use.
I have ADB / Fastboot / Latest drivers installed on my computer but when I try to do anything it acts like the device is not connected.
Any advice how to proceed?
From the troubleshooting guide I think my problem might be:
But I already tried to flash the rom package ( I think).
Help would be much appreciated! thank you!
Click to expand...
Click to collapse
If you are s-on you have to fastboot flash or use Flash Image GUI to flash the boot.img/kernel first then flash the rom from twrp
bigdaddy619 said:
If you are s-on you have to fastboot flash or use Flash Image GUI to flash the boot.img/kernel first then flash the rom from twrp
Click to expand...
Click to collapse
Thanks for the help man, I'm just not sure HOW to flash the boot.img/kernel first then flash the rom from twrp
1. Where do I get the Boot.img/kernel? is it just a file I download?
2. What's the command to flash it to the device?
THANK U
You can get a copy of Flash Image GUI here to flash the kernel or pull the boot.img from the rom zip and put it in the folder you have adb and fastboot in and fastboot flash from there.
Here is a guide you can look at to show you how to do the whole process
http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
bigdaddy619 said:
You can get a copy of Flash Image GUI here to flash the kernel or pull the boot.img from the rom zip and put it in the folder you have adb and fastboot in and fastboot flash from there.
Here is a guide you can look at to show you how to do the whole process
http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
Click to expand...
Click to collapse
Well, clearly "Flash Image GUI" isn't going to help me because as I stated before, my device is in boot loop.
I've placed boot.img in my C:\ROOT folder where I keep all my root related files (like ADB and FASTBOOT) but when I run the command:
fastboot flash boot.img
I get the error: unknown partition 'boot.img' error cannot determine image filename for boot.img
Should be
fastboot flash boot boot.img
at this point it just goes < WAITING FOR DEVICE >
I think this is part of the problem. Even though I installed the latest HTC Drivers it seems the computer isn't recognizing the device. When I'm in TWRP and I mount it - it DOES show up in My computer. But not when I'm at that first boot menu.
yoerz said:
at this point it just goes < WAITING FOR DEVICE >
I think this is part of the problem. Even though I installed the latest HTC Drivers it seems the computer isn't recognizing the device. When I'm in TWRP and I mount it - it DOES show up in My computer. But not when I'm at that first boot menu.
Click to expand...
Click to collapse
Try this
On your PC go to device manager and find your phone, right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Whats next
OK! turns out I just needed a restart. I ran the command:
C:\ROOT>fastboot flash boot boot.img
sending 'boot' (5770 KB)...
OKAY [ 0.899s]
writing 'boot'...
OKAY [ 1.461s]
finished. total time: 2.360s
Now what? what's the next command? do I flash the rom? the recovery?
yoerz said:
OK! turns out I just needed a restart. I ran the command:
C:\ROOT>fastboot flash boot boot.img
sending 'boot' (5770 KB)...
OKAY [ 0.899s]
writing 'boot'...
OKAY [ 1.461s]
finished. total time: 2.360s
Now what? what's the next command? do I flash the rom? the recovery?
Click to expand...
Click to collapse
Choose recovery from the bootloader then flash the rom like you normally would
ALL GOOD
NEVER MIND! That totally did it! Wonderful! Thank you so much for your help man!
I REALLY appreciate it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
I m not the onlu one getting this error while side loading lollipop
I have the same issue
I Give up, i'll wait for the final release... these tutorials don't even help...
Nilangan Ray said:
I m not the onlu one getting this error while side loading lollipop
Click to expand...
Click to collapse
i got this.... it is a download error...
if u r rooted:
http://forum.xda-developers.com/moto-e/general/root-flashable-lollipop-t3028596
use this
T3snake said:
i got this.... it is a download error...
if u r rooted:
http://forum.xda-developers.com/moto-e/general/root-flashable-lollipop-t3028596
use this
Click to expand...
Click to collapse
but we dont have rooted moto e, just stock
Dinepada said:
but we dont have rooted moto e, just stock
Click to expand...
Click to collapse
use general method
T3snake said:
use general method
Click to expand...
Click to collapse
doesn't work for us, mine version says 21.12.44 maybe is the reason the name of the zip is seen like older version
Yeah , exactly ! All the tutorials giving up their own version of procedure.
Sent from my XT1022 using XDA Free mobile app
kirtybs12 said:
Yeah , exactly ! All the tutorials giving up their own version of procedure.
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Dinepada said:
doesn't work for us, mine version says 21.12.44 maybe is the reason the name of the zip is seen like older version
Click to expand...
Click to collapse
All of them pretty much amount to the same thing......
If u are having some problems with the file name.... Just sideload it using adb(this only works with stock recovery)
If u have a custom recovery... Some1 has posted a twrp flashable zip which u can use...
These 2 options should cut it for any xt1022 model
Sent from my XT1022 using Tapatalk
can't update
M sure that u can't update even when get lollipop through over the air(ota)... Same thing happens to me .. Today I got lollipop update notification from motorola.. While installing it I got error at the middle..but I m using stock version
---------- Post added at 07:36 AM ---------- Previous post was at 07:32 AM ----------
T3snake said:
All of them pretty much amount to the same thing......
If u are having some problems with the file name.... Just sideload it using adb(this only works with stock recovery)
If u have a custom recovery... Some1 has posted a twrp flashable zip which u can use...
These 2 options should cut it for any xt1022 model
Sent from my XT1022 using Tapatalk
Click to expand...
Click to collapse
How can I get stock recovery again
salman.student said:
M sure that u can't update even when get lollipop through over the air(ota)... Same thing happens to me .. Today I got lollipop update notification from motorola.. While installing it I got error at the middle..but I m using stock version
---------- Post added at 07:36 AM ---------- Previous post was at 07:32 AM ----------
How can I get stock recovery again
Click to expand...
Click to collapse
if u have ever rooted.... ie if u have an unlocked bootloader and a custom recovery
since even sideloading doesnt work if the normal method isnt working
use this...
http://forum.xda-developers.com/moto-e/general/root-flashable-lollipop-t3028596
this works 100% i can confirm it
T3snake said:
All of them pretty much amount to the same thing......
If u are having some problems with the file name.... Just sideload it using adb(this only works with stock recovery)
If u have a custom recovery... Some1 has posted a twrp flashable zip which u can use...
These 2 options should cut it for any xt1022 model
Sent from my XT1022 using Tapatalk
Click to expand...
Click to collapse
but adb method says "installation aborted"
Steps followed by me to get lillipop working 100% in xt1021 with stock 4.4.4 brazillian.
Get the zip file in https://mega.co.nz/#!wVsQmajI!tmEkvt...jtAS2GwF5fncws, if you not from Brazil, get the stock 4.4.4 images files of your country and your phone model.
Extract the files
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
if you have bootloader unlocked: fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
if you have bootloader unlocked: fastboot.exe oem lock
fastboot reboot
You are in stock 4.4.4, apply your Google Account
Get the zip file in https://mega.co.nz/#!IJ9SVCaT!watj3-...GnKkg8od_kthLw (brazillian lollipop soak test, get it from your country, if not in Brazil)
Put this zip file in root internal memory
In Fone go to Settings, About Phone, System Updates
After detect and apply update your Moto E have Lollipop 5.0.2
if you have a bootloader unlocked warning in boot phone after update to lillipop
Get the zip file in https://mega.co.nz/#!MFVkCQ7J!W7SmL3...rWDXoHW5hz6l44
unzip the file
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
fastboot flash logo logo.bin
fastboot reboot
Enjoy.
Hit Thank's if you like help.
Hello, please help me to root Vernee M6. Thank you!
MoeKyawThu991 said:
Hello, please help me to root Vernee M6. Thank you!
Click to expand...
Click to collapse
Hello, I too want recovery and root for the Vernee M6
Orat60 said:
Hello, I too want recovery and root for the Vernee M6
Click to expand...
Click to collapse
I have M6 also. I would buy 1 for somebody who can create us a ASOP ROM with root and recovery!
Hi, developer here, just asked Vernee for kernel source code so i can start developing a custom recovery asap.
Regards.
josalaito said:
Hi, developer here, just asked Vernee for kernel source code so i can start developing a custom recovery asap.
Regards.
Click to expand...
Click to collapse
Awesome josalaito!
Root done! Writing and posting a tutorial ASAP!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 05:38 PM ---------- Previous post was at 05:23 PM ----------
Rooting Vernee M6:
First of all, unlock developer settings by going to Settings - Phone Status and pressing 10 times over Build Number.
Then, in developer settings, turn on OEM Unlocking flag and USB Debugging.
Download this pack.
Open a cmd terminal, drive to the unpacked folder and type the following commands: (IMPORTANT: THIS WILL ERASE ALL YOUR DATA, MAKE A BACKUP FIRST)
adb.exe reboot-bootloader
fastboot.exe oem unlock
After this, reboot and configure the phone, reenable USB Debugging, install Magisk Manager and again type the following commands:
adb.exe reboot-bootloader
fastboot.exe flash boot root_boot.img
Ur phone is now rooted.
josalaito said:
Root done! Writing and posting a tutorial ASAP!
---------- Post added at 05:38 PM ---------- Previous post was at 05:23 PM ----------
Rooting Vernee M6:
First of all, unlock developer settings by going to Settings - Phone Status and pressing 10 times over Build Number.
Then, in developer settings, turn on OEM Unlocking flag and USB Debugging.
Download this pack.
Open a cmd terminal, drive to the unpacked folder and type the following commands: (IMPORTANT: THIS WILL ERASE ALL YOUR DATA, MAKE A BACKUP FIRST)
adb.exe reboot-bootloader
fastboot.exe oem unlock
After this, reboot and configure the phone, reenable USB Debugging, install Magisk Manager and again type the following commands:
adb.exe reboot-bootloader
fastboot.exe flash boot root_boot.img
Ur phone is now rooted.
Click to expand...
Click to collapse
Rar file doesn't open
rodpgfx said:
Rar file doesn't open
Click to expand...
Click to collapse
Try this mate M6.zip
josalaito said:
Try this mate M6.zip
Click to expand...
Click to collapse
That one worked.
rodpgfx said:
That one worked.
Click to expand...
Click to collapse
Perfect, i hope i can bring TWRP asap, to AOSP rom i contacted Vernee to source code but still no answer
I tried every way to try to extract recovery from the firmware.....no way! Doesn't show recovery in partitions
Root
Crackloi said:
Root
Click to expand...
Click to collapse
The phone is already rooted. I wouldn't be able to see the system partition otherwise.....
Guys any luck getting any scatter files for this phone? I sent Vernee multiple messages and not one reply! I need the firmware for this phone so I can fix it. Stuck in bootloop now with not even option for recovery.....
I could work with this device this week and finally build a working TWRP device(Data partition decryption dont work, but i'm working on a kernel which dont encrypt data), you can backup system, boot and much more to a external sd card.
Get it from here: recovery.img
Reboot fastboot mode and perform the following commands:
Fastboot flash recovery recovery.img
Fastboot boot recovery.img
Once on recovery, keep the device blocked for a min or two, and then unlock it, allow system modifications, go to mount, mount system, then click on options, file explorer, go to system folder and delete the recovery-from-boot.p file.
I cannot get my phone to go to fastboot, recovery or anything else. Just keeps boot looping.....
rodpgfx said:
I cannot get my phone to go to fastboot, recovery or anything else. Just keeps boot looping.....
Click to expand...
Click to collapse
Didnt work fully turning it off(Power off + Vol -) and then boot into fastboot pressing Vol + and power off at the same time?
If u make it work i can send you a system backup so you can fix your phone
I done all that. I pressed Vol + and power until it was off then vol- and power, just start boot looping again. I fear the only thing that can save it now is a scatter file...... Even AliExpress didn't help me with warranty still left, and why I will not buy from them again.
rodpgfx said:
I done all that. I pressed Vol + and power until it was off then vol- and power, just start boot looping again. I fear the only thing that can save it now is a scatter file...... Even AliExpress didn't help me with warranty still left, and why I will not buy from them again.
Click to expand...
Click to collapse
I can scatter all my partitions and upload then to you, but got not a nice connection until monday.
That would be nice. Thanks!
Hi everyone
ive been using Berkeley for the past like 2 weeks, mainly testing random stuff, cuz its the first flagship phone from Honor, while using/testing i
frequently get stuck at TWRP splash screen, because crypto somehow get corrupted, which doesnt TWRP to decrypt you data, yet it doesnt boot
into TWRP, so i decided to look into decryption, you can follow those steps:
Needed Files:
Patched TWPP Here
Disable_DM-Verity_FEC
Latest Magisk Beta
HuRU Updater
update_all_hw & update_data_public, check here for more info's about update files
Backup your data, kernel, kernel ramdisk and vendor, cuz those will be edited, and copy backups to PC
Boot into fastboot, and Run
"fastboot -w", to wipe crypto
without rebooting flash included patched TWRP
Boot into TWRP, then Wipe internal storage, Wipe > Format Data then write "Yes"
Then flash Disable_DM-Verity_FEC & Latest Magisk Beta
Now you could continue to EMUI steps, or just flash AOSP/LOS ROMs
Now you have to flash update_all_hw.zip & update_data_public.zip with HuRU-Updater, to restore CUST data under /data to fix couple of EMUI features
And we're Done
Notes:
This method is risky, because your device could encrypt back when you bootloop or booting up to eRecovery
Restoring Encryption will also wipe your data
The Good thing about this is twrp wont stop again for you
Creadits:
@Pretoriano80 for TWRP
@vache for TWRP with edited mount points
How to restore encryption
Flash EnableEncryption-Berkeley to restore vendor edits
Restore your unpatched kernel/ramdisk
Format Data, and reboot to system
How to check your encryption:
Run "getprop ro.crypto.state" in terminal, or
"adb shell getprop ro.crypto.state" in adb
you should get back "unencrypted"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice?
The attached twrp didn't work for me but decrypted using official twrp worked fine for me..
mondalakash said:
The attached twrp didn't work for me but decrypted using official twrp worked fine for me..
Click to expand...
Click to collapse
included twrp tested on L04
AL_IRAQI said:
included twrp tested on L04
Click to expand...
Click to collapse
Ya that's why mine is l09...
fbe
mondalakash said:
Ya that's why mine is l09...
Click to expand...
Click to collapse
@mondalakash
how about a nandroid backup. did you try? please report back. this decryption method seems to be once again a proof only for bkl l04 devices.
kurvenmeister said:
@mondalakash
how about a nandroid backup. did you try? please report back. this decryption method seems to be once again a proof only for bkl l04 devices.
Click to expand...
Click to collapse
Just made an nandroid backup to flash los on bkl l09 but didnt restore it yet, if I face any issue I will let u guys know...the thing the internal storage doesn't get encrypted every time u flash a new ROM..[emoji3]
Sent from my Redmi Note 4 using Tapatalk
fbe, nandroid twrp
mondalakash said:
Just made an nandroid backup to flash los on bkl l09 but didnt restore it yet, if I face any issue I will let u guys know...the thing the internal storage doesn't get encrypted every time u flash a new ROM..[emoji3]
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
one of the most important things by flashing all this stuff is a fully working recovery. i am also keen on giving this a try.
kurvenmeister said:
one of the most important things by flashing all this stuff is a fully working recovery. i am also keen on giving this a try.
Click to expand...
Click to collapse
Just restored backup everything fine here no issues
@ all cool guys here. it worked. used the modified vache-twrp. performed many nandroids and restored them. perfectly. great guys here.
took the same tool to decrypt my oneplus 5t
AL_IRAQI said:
included twrp tested on L04
Click to expand...
Click to collapse
If I use fastboot format usedata and then flash recovery and format data from recovery and then flash the DM verity and magisk after that?
Will this work also?
P.S
Actually I tried fastboot -w and then boot to recovery it say could not found crypto footer and unable to create data/media
mondalakash said:
If I use fastboot format usedata and then flash recovery and format data from recovery and then flash the DM verity and magisk after that?
Will this work also?
P.S
Actually I tried fastboot -w and then boot to recovery it say could not found crypto footer and unable to create data/media
Click to expand...
Click to collapse
Yup, fastboot only wipes crypto for you, then you have to wipe manually from TWRP
AL_IRAQI said:
Yup, fastboot only wipes crypto for you, then you have to wipe manually from TWRP
Click to expand...
Click to collapse
So, fastboot format userdata equivalent to fastboot -w....is that what are u saying?
mondalakash said:
So, fastboot format userdata equivalent to fastboot -w....is that what are u saying?
Click to expand...
Click to collapse
Hmm, i think Huawei locked userdata formating from fastboot, cuz i tried more than one, and it wiped crypto
AL_IRAQI said:
Hmm, i think Huawei locked userdata formating from fastboot, cuz i tried more than one, and it wiped crypto
Click to expand...
Click to collapse
I tried fastboot format userdata and it said
Failed remote command not allowed
Sent from my Redmi Note 4 using Tapatalk
mondalakash said:
I tried fastboot format userdata and it said
Failed remote command not allowed
Click to expand...
Click to collapse
Yeah it wont let you wipe it
AL_IRAQI said:
Yeah it wont let you wipe it
Click to expand...
Click to collapse
fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.025s]
finished. total time: 0.026s
THIS IS WHAT HAPPENS WHEN I RUN FASTBOOT -W
This worked flawlessly for me. But now I don't have fingerprint options in settings>security & privacy. I'm on the latest AICP 13.1 build. I did not do the last EMUI steps (because I flashed AICP). Does anyone know what might have happened or how to fix it? I've tried everything I could find online (factory reset, clearing credentials, booting into safe mode, etc.). I'm at a loss!
Hi, so I successfully installed TWRP from here, everything went well until this point. I flashed a more stable EU rom and then tried to flash Magisk, but when I rebooted it just went to fastboot mode.
Now everytime I try to turn it off or go back into TWRP it just goes to fastboot mode.
I have tried to flash using MiFlash but I can't seem to get the right thing to flash apparently.
When trying to reinstall TWRP
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.498s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.503s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Zelyric said:
View attachment 5448807
Click to expand...
Click to collapse
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
akins0405 said:
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
Click to expand...
Click to collapse
Reading on that post I saw that there are issues with Ryzen powered computers, and I indeed have a Ryzen CPU. Really hopes this helps, thanks for showing me regardless - ill keep you updated!
@akins0405
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try flashing you stock boot img
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
Where do I find that?
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
You have it in fastboot stock rom
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
Try to transfer the rom to the system partition
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
adb doesn't show my device under adb devices but fastboot devices does show it..
MTP also is disabled
Zelyric said:
adb doesn't show my device under adb devices but fastboot devices does show it..
Click to expand...
Click to collapse
Flash in fastboot stock boot img, can you do it
akins0405 said:
Flash in fastboot stock boot img, can you do it
Click to expand...
Click to collapse
fastboot flash b boot.img
Sending 'b' (196608 KB) OKAY [ 4.817s]
Writing 'b' FAILED (remote: '(b_a) No such partition')
fastboot: error: Command failed
nevermind, i understood the partition wrong.
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.558s]
Writing 'boot_a' OKAY [ 0.707s]
Finished. Total time: 6.103s
what now?
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try firstly erasing your recovery partition with fastboot erase recovery
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Zelyric said:
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Click to expand...
Click to collapse
I'm glad you made it, hello