Hi all,
I have asked this on the miui forums but no one was unable to assist,
I was updating my phone to the MIUI version that contained the new Android OS, and my stupid cat pulled the cable, causing the phone to unplug during flashing procedure, big no no
Firstly the phone would would just flash red which I believe was EDL mode, so I was able to after several goes reflash the chinese variant of MIUI rom onto the phone.
it would then be stuck on the MI screen, so I reflashed again and it started to proceed with the initial setup
However every couple of seconds the phone would crash, restart, get a bit further, crash and repeat till it finished the initial setup, this is where the device is today
I managed to flash twrp to see if there was anything I could do, I noticed it was complaining that /persist was missing/unable to process, I tried to reflash /persist using the online guides available but all of them ended up as the same result of "could not be flashed to device"
My bootloader is unlocked as confirmed by offical Xiaomi unlocker tool,
so I am stuck with a phone that bootloops and has no /persist, is there any hope for this device?
I am located in Australia so sending it to a service centre will not be an easy process if I can even get the seller to do so (dx.com)
Thanks for reading
Cexitime said:
so I am stuck with a phone that bootloops and has no /persist, is there any hope for this device?
I am located in Australia so sending it to a service centre will not be an easy process if I can even get the seller to do so (dx.com)
Thanks for reading
Click to expand...
Click to collapse
Hey there, Have you tried this method:
https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Hoping that it may help you.
Cexitime said:
Hi all,
I have asked this on the miui forums but no one was unable to assist,
I was updating my phone to the MIUI version that contained the new Android OS, and my stupid cat pulled the cable, causing the phone to unplug during flashing procedure, big no no
Firstly the phone would would just flash red which I believe was EDL mode, so I was able to after several goes reflash the chinese variant of MIUI rom onto the phone.
it would then be stuck on the MI screen, so I reflashed again and it started to proceed with the initial setup
However every couple of seconds the phone would crash, restart, get a bit further, crash and repeat till it finished the initial setup, this is where the device is today
I managed to flash twrp to see if there was anything I could do, I noticed it was complaining that /persist was missing/unable to process, I tried to reflash /persist using the online guides available but all of them ended up as the same result of "could not be flashed to device"
My bootloader is unlocked as confirmed by offical Xiaomi unlocker tool,
so I am stuck with a phone that bootloops and has no /persist, is there any hope for this device?
I am located in Australia so sending it to a service centre will not be an easy process if I can even get the seller to do so (dx.com)
Thanks for reading
Click to expand...
Click to collapse
Try to flash some custom rom through custom recovery and see if it works. I think your device isnt bricked because I've done the same when I realised that clean all and lock was ticked so I just unplug the cable in the middle of the flash process and flash the ROM again. Go to recovery and wipe all Dalvik, system and cache and then flash custom ROM and gapps. After that go and flash official rom through mi flash tool from fastboot.
GabrielScott said:
Hey there, Have you tried this method:
https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Hoping that it may help you.
Click to expand...
Click to collapse
Hi, I tried the link and got the following;
C:\adb>adb shell
~ # [6nmake_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
open: No such file or directory
~ # [6ne2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck 1.42.9 (28-Dec-2013)
e2fsck: No such file or directory while trying to open /dev/block/platform/msm_sdcc.1/by-name/persist
Possibly non-existent device?
~ # [6n
bpodnar said:
Try to flash some custom rom through custom recovery and see if it works. I think your device isnt bricked because I've done the same when I realised that clean all and lock was ticked so I just unplug the cable in the middle of the flash process and flash the ROM again. Go to recovery and wipe all Dalvik, system and cache and then flash custom ROM and gapps. After that go and flash official rom through mi flash tool from fastboot.
Click to expand...
Click to collapse
I tried to install lineage OS according to their instructions and got this error during installation
{
"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"
}
Cexitime said:
I tried to install lineage OS according to their instructions and got this error during installation
Click to expand...
Click to collapse
Error 7 issue is probably due to corrupted zip.
Redownload the ROM again.
This time, format data or wipe everything then flash.
GabrielScott said:
Error 7 issue is probably due to corrupted zip.
Redownload the ROM again.
This time, format data or wipe everything then flash.
Click to expand...
Click to collapse
I downloaded the rom again and this time it flashed, however the phone just got stuck in a boot loop till it went flat, still have the /persist error in twrp that I cannot fix utilizing the above commands,
I think shes dead jim
Cexitime said:
I downloaded the rom again and this time it flashed, however the phone just got stuck in a boot loop till it went flat, still have the /persist error in twrp that I cannot fix utilizing the above commands,
I think shes dead jim
Click to expand...
Click to collapse
Last Try , did u already tried flashing persist img from official fastboot ROM?
@_ sorry, out of ideas
So you just had corrupted persist partition, and cant mount persist partition right?
Have you tried flash persist.img from fastboot?
fastboot erase persist
fastboot flash persist persist.img
Sent from my Redmi Note 4 using Tapatalk
Someone please share persist.img file, the one present in fastboot file is low in size, & after flashing that file it keeps on rebooting.
I had to flash sensorfix file that comes with coloros to restore it to normal, & again this creates a new problem "this device associated with another mi account".
Hii tired to do that in twrp as well, however when selecting the persist.img the /persist isn't a selectable option in twrp
arshy said:
So you just had corrupted persist partition, and cant mount persist partition right?
Have you tried flash persist.img from fastboot?
fastboot erase persist
fastboot flash persist persist.img
Click to expand...
Click to collapse
Hi,
Tried that as well, it comes up with the error in one of my replies
Try this way:
first go here and download "Redmi Note 4X ( (3GB+32GB) Latest China Developer Version Fastboot File Download";
then follow this guide but only the PART II (the guide is for locked bootloader, but it doesn't matter on our case, because on mido you must have an unlocked bootloader to enter EDL).
The guide will modify some text file to flash only the persist.img, but if need you can flash all the firmware's files (but remember to insert the "persist.img" in the bat file, because it's not present by default). You will got a Chinese language phone (I don't know if English is present) but you can test if everything works and then re-flash a Global ROM or a custom ROM.
The summary of the procedure is flashing the China Developer ROM (including the persist.img) with MiFlash when the phone is in EDL mode (RN4 can be put in EDL mode with this tool but only if bootloader is unlocked).
Let us know if this works for you.
I can help may be.... Read my post .... We can reflash stock ROM with all partitions and stuff(I know how to edl RN4) I believe it will work for sure..
i have tried all the methods both locked as well as unlocked bootloader methods but for me none works. i have no persist file and it wont get flashed with miflash.
Cexitime said:
Hi all,
I have asked this on the miui forums but no one was unable to assist,
I was updating my phone to the MIUI version that contained the new Android OS, and my stupid cat pulled the cable, causing the phone to unplug during flashing procedure, big no no
Firstly the phone would would just flash red which I believe was EDL mode, so I was able to after several goes reflash the chinese variant of MIUI rom onto the phone.
it would then be stuck on the MI screen, so I reflashed again and it started to proceed with the initial setup
However every couple of seconds the phone would crash, restart, get a bit further, crash and repeat till it finished the initial setup, this is where the device is today
I managed to flash twrp to see if there was anything I could do, I noticed it was complaining that /persist was missing/unable to process, I tried to reflash /persist using the online guides available but all of them ended up as the same result of "could not be flashed to device"
My bootloader is unlocked as confirmed by offical Xiaomi unlocker tool,
so I am stuck with a phone that bootloops and has no /persist, is there any hope for this device?
I am located in Australia so sending it to a service centre will not be an easy process if I can even get the seller to do so (dx.com)
Thanks for reading
Click to expand...
Click to collapse
http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Flash this file via fastboot, if you are getting reboots.
arshy said:
So you just had corrupted persist partition, and cant mount persist partition right?
Have you tried flash persist.img from fastboot?
fastboot erase persist
fastboot flash persist persist.img
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
t only says C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase persist
erasing 'persist'...
FAILED (remote: Error: This image isn't allow download
)
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash persist persist.i
mg
target reported max download size of 536870912 bytes
sending 'persist' (4716 KB)...
OKAY [ 0.162s]
writing 'persist'...
FAILED (remote: Error: This image isn't allow download
)
finished. total time: 0.194s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I think that means this isn't working.
BubuXP said:
Try this way:
first go here and download "Redmi Note 4X ( (3GB+32GB) Latest China Developer Version Fastboot File Download";
then follow this guide but only the PART II (the guide is for locked bootloader, but it doesn't matter on our case, because on mido you must have an unlocked bootloader to enter EDL).
The guide will modify some text file to flash only the persist.img, but if need you can flash all the firmware's files (but remember to insert the "persist.img" in the bat file, because it's not present by default). You will got a Chinese language phone (I don't know if English is present) but you can test if everything works and then re-flash a Global ROM or a custom ROM.
The summary of the procedure is flashing the China Developer ROM (including the persist.img) with MiFlash when the phone is in EDL mode (RN4 can be put in EDL mode with this tool but only if bootloader is unlocked).
Let us know if this works for you.
Click to expand...
Click to collapse
Hello. I have a Redmi Note 4 Snapdragon with the Bootloader unlocked because I bought it used and I have an account lock that prevent me to use it (it is like a bricked phone because the vendor doesn't know about the MI account and xiaomi cannot unbind the device from the MI account because I have not the registration email neither invoce of purchase).
Searching a way to avoid the lock of the MI account I am trying to flash persist.img because I read that the data of this account is saved in this partition.
- I downloaded the mido_global_images_8.12.20_20181220.0000.00_7.0_global_3947ba5143.tgz
- I modified the flash_factory.bat in order to add the line 28:
Code:
fastboot %* flash persist %~dp0images\persist.img || @echo "Flash persist error" && exit /B 1
- I modified rawprogram0.xml in order to add the "persist.img" in line
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="persist.img" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
- I entered in EDL using the test points, flashed with MiFlash20191206 and it says "flashSuccess" (attached is the log of the MIFlash)
But when the new ROM starts and connects to the internet, the MI account lock appears again. Then I have a device that cannot be used when connects to internet.
I have read in some threads that persist partition cannot be flashed in EDL mode with the unlocked Bootloader but it seems that I can do it (not in FastBooot that says explicitly that this partition cannot be flashed).
I have flashed the persist image that comes with the original ROM but I haven't tried with the ones that users upload in order to avoid another conflict of MI Accounts.
I have another Redmi Note 4 working with the unlocked BL, TWRP and LineageOS 16. I tried to make a backup of persist from TWRP in order to flash it in the locked device but it says that the partition uses 0 MB and the persist.ext4.win file has 473 KB that makes me think I am not doing it right.
Please, let me know what you think. Am I in the right way?
Thanks
Related
Dell has updated their open source site with the developer files for the Lollipop update for the Venue 8 7840:
http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
This includes the kernel source, a guide Doc, and a "blankphone" image which will re-partition the device and leave it in the fastboot interface OS and wait for a system image to be flashed. It does not erase or provision a system image or boot image. The documentation mentions a separate "fastboot" image paired with the "blankphone" image, and traditionally (based on files posted by other OEMs) the "fastboot" zip is what contains the OS images. So hopefully (maybe?) they will be posting that at some point. We should be able to get images pulled off working devices for people to flash.
This "blankphone" zip should function as an "unbrick" and put a mis-flashed device back into a functioning (flashable) state, but you may end up without an OS. (This is why I called it "partial" unbrick, because you won't have a brick but you won't necessarily have a booting-to-Android device either.)
ALSO A WARNING: This should be all fine and good but proceed with caution.
I have flashed the IFWI-only.xml and successfully booted back to Android.
The zip file can be flashed with Phone Flash Tool Lite, available here from Intel for Windows and Linux.
There is a "Flash file" selector in Phone Flash Tool.
To unbrick and format, use the file: flash-DDO_BB.xml
{
"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"
}
To just flash the unlocked bootloader firmware, use the file: flash-IFWI-only.xml
DO NOT use the EraseFactory xml; I'm not certain but I think there are DRM keys in the /factory partition, and you could permanently break things like Netflix if you erase it.
Since mine is currently useless, I may as well try this. Will the image you uploaded here work?
Don't have access to the tablet at the moment but I'll try when I get in (couple of hours).
I know @wirebook tried on the older bootloader and failed but not harm in trying with this new stuff I suppose...
That system.img doesn't flash I think... Though it sounds like it's just an issue of repacking it somehow.
This is great news!
If bootloader can be unlocked, does it mean someday (if best) it is possible to install windows os on this little pad?
wonglynn2004 said:
This is great news!
If bootloader can be unlocked, does it mean someday (if best) it is possible to install windows os on this little pad?
Click to expand...
Click to collapse
Windows is unlikely, as it would require additional drivers and a custom bootloader OS to be created, among other issues. Linux may be possible though.
I've managed to unbrick my device, but I'm honestly not sure how.
So using the intel flash tool, I used the option flash-DDO_BB.xml, understanding that it would wipe the device (erase system, repartion, etc). I then had access to fastboot. From fastboot I attempted to flash the system.img @xBIGREDDx uploaded, obviously that failed with the sparse image header issue.
Next I converted the system.dat.new in the OTA to a system.img, attempted to flash that from fastboot, no go.
I decided it might be a good idea to flash the boot.img from the OTA, so I did that. Ended up on the original Dell/Intel boot animation (progress?). This seemed to infinitely bootloop (however maybe I was just impatient?).
I then booted CWM using the temp. recovery method (T4), wasn't able to do much at all, most directories were empty and nothing was mountable. Rebooted the tablet once more, went to get a drink and it's booted into Lollipop!?
I'm both confused and pleased... Can anyone shed any light?
anggusss said:
I'm both confused and pleased... Can anyone shed any light?
Click to expand...
Click to collapse
Hahaha not sure, maybe the reboot caused it to process the update again? The OTA may have been in the cache still.
Update: I have looked at the xml files and it turns out they are not erasing the boot or system partitions after all. That has been the standard procedure in the past so I didn't think to check. They are, however, wiping the data partition, and they wipe the cache twice. Maybe they've been reading XDA too much?
Ah I see. So if my system was never wiped, I assume flashing the new boot.img from fastboot is what kicked it into life.
I probably should have posted somewhere that I wrote a second query to Dell and heard back from someone in Legal six days ago stating that they were going to go bug the team and get the images posted online. They promised to follow up- never did- but looks like the rest of you were a lot more diligent in checking out the open source repository.
Anyway, the tablet I was working on belonged to a family member now living in a different city. Seems like we've figured out more or less how to unbrick this thing, so that's fantastic! I'm a bit confused as to which guide / instructions I should be passing along to convert the "it's-okay-it-makes-a-pretty-doorstop" back to working condition? Much appreciated!
For now, I wanna ask how to unroot the device with 5.0.2 if an OTA out there that I'm gonna update but don't wanna brick my device?
wonglynn2004 said:
For now, I wanna ask how to unroot the device with 5.0.2 if an OTA out there that I'm gonna update but don't wanna brick my device?
Click to expand...
Click to collapse
Wait for someone else to confirm, but I don't think it was the rooting that caused the OTA to fail, it was the developer unlock. I imagine you're safe to OTA with root applied although someone correct me if I'm wrong.
anggusss said:
Wait for someone else to confirm, but I don't think it was the rooting that caused the OTA to fail, it was the developer unlock. I imagine you're safe to OTA with root applied although someone correct me if I'm wrong.
Click to expand...
Click to collapse
Yes, it was the developer unlock firmware that broke the OTA, not rooting. With the new Lollipop boot firmware, I think even if it's the unlocked firmware we should be good moving forward.
If you still want to unroot, there should be a menu option in SuperSU, it's like "cleanup" or something.
wirebook said:
I'm a bit confused as to which guide / instructions I should be passing along to convert the "it's-okay-it-makes-a-pretty-doorstop" back to working condition? Much appreciated!
Click to expand...
Click to collapse
1) Install Phone Flash Tool Lite from Intel.
2) Download the blankphone zip from Dell's open source site.
3) Load the zip file with Phone Flash Tool and select "Flash file: flash-DDO_BB.xml"
4) Boot the tablet with the Volume Up button held for about 10 seconds. You won't see anything on the display.
5) Connect USB to the computer. Phone Flash Tool should recognize the device and list the "Status:" as "FW_DNX" mode. If not, try powering off the tablet by holding the power button for ~12 seconds, and then try booting again with the Volume Up key held. Eventually you'll get the right mode.
6) Click "Start to flash" and wait.
7) Even after it hits 100% in the Flash Tool, maybe wait another 5 minutes or so, just in case.
If all goes well you'll end up in the fastboot OS. If all goes really well, you'll end up with a functioning Android device.
xBIGREDDx said:
1) Install Phone Flash Tool Lite from Intel.
2) Download the blankphone zip from Dell's open source site.
3) Load the zip file with Phone Flash Tool and select "Flash file: flash-DDO_BB.xml"
4) Boot the tablet with the Volume Up button held for about 10 seconds. You won't see anything on the display.
5) Connect USB to the computer. Phone Flash Tool should recognize the device and list the "Status:" as "FW_DNX" mode. If not, try powering off the tablet by holding the power button for ~12 seconds, and then try booting again with the Volume Up key held. Eventually you'll get the right mode.
6) Click "Start to flash" and wait.
7) Even after it hits 100% in the Flash Tool, maybe wait another 5 minutes or so, just in case.
If all goes well you'll end up in the fastboot OS. If all goes really well, you'll end up with a functioning Android device.
Click to expand...
Click to collapse
Thank you so much for posting that! I'll attempt to walk my father through the process this weekend.
Stuff wasn't quite working right for me, the screen was turning on randomly, reboots took a ridiculously long time, and a few other things. Decided that it may be better to start with a fresh system partition.
Tried converting both the system.img from @xBIGREDDx and the one from the lollipop OTA to sparse imgs and flashing, however I'm getting
FAILED (remote: flash_cmds error!
When I try to flash system, during the write stage. I'd like to think they're correct sparse images since fastboot reads and sends them to the device.
If I look at the tablet screen during the flash, it complains of an "Unknown chunk type" before failing.
I can get to the default recovery and fastboot, I just don't seem to be able to flash something to my now empty system partition from fastboot...
EDIT: Managed to flash system through the tethered recovery, but I'm still met with a black screen on regular boot.
EDIT2: Fixed, had to push xBIGREDDx's system.img to the device over adb and then dd it to the system partition. The advantage of using that is that it's pre-rooted! I guess we just can't flash system through fastboot.
Another note, I wasn't able to ever get the tablet booting straight into fastboot mode using power/volume buttons. I had to keep sticking it into DnX mode and then using a cut-down xml config along with the flash tool lite to get it to fastboot.
anggusss said:
EDIT2: Fixed, had to push xBIGREDDx's system.img to the device over adb and then dd it to the system partition. The advantage of using that is that it's pre-rooted! I guess we just can't flash system through fastboot.
Click to expand...
Click to collapse
Can you explain how you did this? Through the tethered recovery or through fastboot or....? Trying to walk someone through this via Skype turns out to be a lot harder than I expected...
wirebook said:
Can you explain how you did this? Through the tethered recovery or through fastboot or....? Trying to walk someone through this via Skype turns out to be a lot harder than I expected...
Click to expand...
Click to collapse
Sorry, I could have been clearer.
The steps I performed:
First, booted to fastboot
Trigger the tethered recovery (T4)
Once in the recovery, I then formatted /system using the graphical menu. (Probably not necessary since we're DDing the img directly?)
I had a microsd card in the device which was EXT4 formatted, so I pushed the system.img to that after mounting it by hand.
Code:
mount -t ext4 /external_sd /dev/block/mmcblk1p1
Then from the PC side
Code:
adb push system /external_sd/system.img
You could probably push to the data partition if you can get it mounted in the event you don't have a microsd.
Once you have the system.img on the device, you can dd it onto the system partition
Make sure /system is unmounted
Code:
umount /system
dd if=/external_sd/system.img of=/dev/block/by-name/system
NOTE: /dev/block/by-name/system may be wrong, I'm going from memory. I'll correct it when I get in from work.
After flashing system, reboot to fastboot again
Code:
adb reboot fastboot
And finally flash the boot.img from the OTA zip I uploaded
Code:
fastboot flash boot boot.img
Perform a normal boot, and it should be working. First boot takes a while, 3-4 minutes.
anggusss said:
Another note, I wasn't able to ever get the tablet booting straight into fastboot mode using power/volume buttons. I had to keep sticking it into DnX mode and then using a cut-down xml config along with the flash tool lite to get it to fastboot.
Click to expand...
Click to collapse
It's possible your fastboot partition is broken. After using the Flash Tool to get into fastboot, you could try:
fastboot flash fastboot droidboot.img
There is a droidboot.img in the update.zip from the OTA.
xBIGREDDx said:
It's possible your fastboot partition is broken. After using the Flash Tool to get into fastboot, you could try:
fastboot flash fastboot droidboot.img
There is a droidboot.img in the update.zip from the OTA.
Click to expand...
Click to collapse
I did try that quite a few times but no luck. I just seem completely unable to boot straight into fastboot. I either have to reboot to it using ADB or use the flashtool. Not necessarily a problem, just an inconvenience.
Hello, the question is very simple: does anyone who has installed the rom 26S in x722 have been able to then unlock the bootloader or install another rom?
We know that in the rom 20S with the one that comes from the factory you can unlock the bootloader and install twrp, we know you can upgrade to the 26S, we know that there are people who have upgraded to 26S, but no one who has upgraded to 26S has Commented that it was able to install another rom then, only comment that the bootloader is blocked with the 26S.
All those who have updated to 26S you have to stay with her because you can not change?
Well if someone has succeeded, it would be nice to say how he did it.
Greetings.
*** TODAY, THE ONLY WAY TO LEAVE OFFICIAL 26S IS TO INSTALL THE ROM 01D, THAT UNLOCK THE BOOTLOADER AND ALLOWS US TO INSTALL ANY OTHER ROM. ***
My phone came with 20s shoprom and the bootloader is unlocked. I checked. So I will wait for a twrp before I update to 26s. Is the x720 twrp compatible with our phone to flash?
I have not tried it, but according to the comments of this and other forums, with the 20S factory version it is easy to unlock by ADB, and it allows you to install twrp from x720 which by comment works fine.
The problem is that if you upgrade to version 26S, the bootloader can no longer be unlocked and as the recovery is changed to the stock, you can not reinstall Twrp or any other ROM (I suppose you can install another official ROM, but The only one that exists is the 26S, there is not even the 20S with which it comes from the factory)
In short, if you upgrade to version 26S, the bootloader is blocked, and you can not reinstall twrp or anything that is not official, and for the moment there is nothing more.
Greetings.
It's not like there are so many ROMs
The bootloader changes in 26s and it makes device bootloader locked.
I would suggest to stay on 20s until a workaround is available for unlocking bootloader also on 26s.
I guess anyone who already has the 26S version will have to wait. But for the one who has a hard-brick with the blocked bootloader should try to get a copy of bootloader of 20S and with some flash tool try to change it.
Also it could be that with a flash tool install the rom 26S and before restarting change the bootloader by the 20S version. In some terminals, this has worked.
Greetings.
I have a nandroid copy of 20S Shop ROM boot. I made nandroid copies of all major partitions (the same ones that have stock ROM) before installing 26S Stock. I used the TWRP of the X722 version to install the ROM. Everything worked. Then I installed the GApps and gave it some error and rebooted. Now I have the bootloader locked, it does not go into recovery mode and it does not start the system. Totally brick.
And the worst: QFIL does not work here. I have tested on different versions, different computers, different drivers and nothing. He always gives this error:
Code:
15:47:28: ERROR: function: rx_data:247 Error occurred while reading from COM port
15:47:28: ERROR: function: sahara_main:924 Sahara protocol error
15:47:28: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
And Windows emits the disconnected device sound.
Here is a detailed log using the command to send the FireHose through the CMD:
Log.txt
Does anyone have any idea what this error is? And how to solve it?
Hello DK Boneco, I can not tell you how to solve it, but I can give you an idea.
The fault is because the bootloader is locked.
Look for another tool that does not use qfil and that allows you to flash with locked bootloader. Surely there must be some.
And by the way, if you have a copy of the complete 20S version, I would try to flash this one.
Greetings.
DK Boneco said:
I used the TWRP of the X722 version to install the ROM.
Click to expand...
Click to collapse
Can you please post a link
ziaba said:
Can you please post a link
Click to expand...
Click to collapse
Hi, this thread talks about "unlock bootloader with rom 26S" not from twrp.
Anyway there is no twrp for x722 but it works for x720.
Query in twrp threads or create one in section x722 for more information.
Greetings.
F.J.V said:
The fault is because the bootloader is locked.
Click to expand...
Click to collapse
A friend who has the same smartphone with unlocked bootloader did the same process and the exact same error happened.
F.J.V said:
Look for another tool that does not use qfil and that allows you to flash with locked bootloader.
Click to expand...
Click to collapse
Do you know another method? All that I looked for, ending up using the background QFIL to get the job done.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
ziaba said:
Can you please post a link
Click to expand...
Click to collapse
Here's the link: https://twrp.me/devices/leecolepro3.html
DK Boneco said:
A friend who has the same smartphone with unlocked bootloader did the same process and the exact same error happened.
Click to expand...
Click to collapse
The hard brick came from gapps on top of 26s. Never flash Gapps on top of stock ROMs. Never.
The 26s firmware locked bootloader blocking the CRITICAL partition, so you must unlock it first, then unlock the bootloader.
Try this sequence, in fastboot mode:
fastboot devices
fastboot device info
- when in fastboot device info, check CRITICAL partition unlock status. if FALSE, then try
fastboot flashing unlock_critical
fastboot device info
- now CRITICAL partition unlock status should be TRUE, try unlocking
fastboot oem unlock-go
- if you succeded unlocking, check status with
fastboot device info
fastboot reboot or fastboot flash recovery twrp.img
- if you still cannot unlock, you could try flashing a different emmc_appsboot.mbn file. You can extract emmc_appsboot.mbn from x722 20s firmware or from x720 firmware.
In fastboot mode
fastboot flash aboot emmc_appsboot.mbn
- if flashing is successful
fastboot reboot
adb devices
adb reboot bootloader
fastboot oem unlock-go
- if unlock is succesful
fastboot device info
fastboot reboot or fastboot flash recovery twrp.img
Flounderist said:
The hard brick came from gapps on top of 26s. Never flash Gapps on top of stock ROMs. Never.
The 26s firmware locked bootloader blocking the CRITICAL partition, so you must unlock it first, then unlock the bootloader.
Click to expand...
Click to collapse
I tried this and several other ways to try to unlock the bootloader. I could not find a way. It does not allow flash any partition.
{
"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"
}
DK Boneco said:
I tried this and several other ways to try to unlock the bootloader. I could not find a way. It does not allow flash any partition.
Click to expand...
Click to collapse
Would you try
fastboot format userdata
fastboot format data
fastboot reboot bootloader
fastboot device info
Check if (bootloader) is_allow_unlock: changed from 0 to 1. If it is still on 0 try
fastboot erase userdata
fastboot erase data
fastboot reboot bootloader
fastboot device info
If still on 0....try also formatting or erasing cache.
It seems that kernel does not allow any tampering attempt if value is =0, hence critical partitions are locked.
Hello DK Boneco, the error is reading the COM port.
Is the phone charged?
It appears that the phone is disconnected or exits EDL mode.
It may be a driver problem, or some phones exit EDL mode within a few seconds if the flash has not started.
Try not to take more than 4 or 5 seconds from the time the phone enters EDL until the flash starts.
You can also try the flash with MiFlash Xiaomi, say that can flash any modern phone and is quite effective, look for a manual and test.
Greetings.
DK Boneco said:
And Windows emits the disconnected device sound.
Click to expand...
Click to collapse
You may need to install drivers to your pc to recognize your, thats why it emits the disconnected device sound.
Hello DK Boneco, try these steps:
1. Method published with flashone2.0 and zip qfil.
2. When the fault appears, disconnect the USB phone.
3. Reconnect the phone in EDL mode (vol + and vol- and connect to USB)
4. Without losing time, in flashone2.0 press the "Refresh" button, select the COM port, press the "Flash" button and then "NO" (do not unzip it again).
From connecting the phone to USB until you press the "NO" button as fast as possible, without wasting time.
I hope it serves as something, what I see is that the phone goes out of EDL mode and that's why it fails.
Greetings.
To be sure to stay in EDL mode, you can type
fastboot reboot edl or fastboot reboot-edl
Be sure to install Qualcomm driver properly on PC.
Anyway it seems that QFIL is missing for X722 device. I assume that this device lacked a lot of development due to company failure, or it was developed exclusively for CN market (no google play support and locked bootloader from kernel to avoid any hacking activity).
Qfil is a Qualcomm tool for any Qualcomm smartphone, no matter brand or development.
Qfil should work for any phone with chip qualcomm, another thing is that the phone requires some specific configuration, or that the zip that is intended to flash is not correct.
Greetings.
Hi all,
For those who don't know, I'm known for rooting HMD Nokia Android Phones.
{
"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"
}
So after few hours testing, I finally found out how to root it.
Note, I've only dumped stock ROM from Verizon Wireless Variant as it's the only variant I've obtained so far. For non-operator variant and AT&T variant, I need your help for firmware dumping in case you want to restore your phone back to factory original state or OTA update if possible.
Known working build: H1A1000.010ho.01.01.01r.109
Procedure is pretty regular.
Step 1: Unlock the bootloader
Unlike HMD Nokia Android Phones, bootloader unlock is straight forward.
Just enable OEM unlocking in developer options, reboot your phone to Fastboot mode and unlock the bootloader with following command:
Code:
fastboot flashing unlock
Then confirm unlock on the phone.
As I've always recommended for HMD Nokia Phones, you should do critical unlock as well:
Code:
fastboot flashing unlock_critical
Then confirm unlock on the phone.
Strange enough, this phone doesn't have unlock warning after unlocked. Not sure about open market release or AT&T Variant.
Step 2: Install Magisk Manager and allow storage permission
You can download it from Magisk release topic or https://github.com/topjohnwu/magisk/releases
Step 3: Reboot to fastboot mode and flash patched boot image
You can download required patched boot image and representative stock boot image from here: https://www.androidfilehost.com/?w=files&flid=297410
For Verizon Variant that available with build "H1A1000.010ho.01.01.01r.109" so far, download "H1A1000.010ho.01.01.01r.109-boot_magisk_patched_193.img". You can check software version yourself if correct.
The command is straight forward too:
Code:
fastboot flash boot /path/to/H1A1000.010ho.01.01.01r.109-boot_magisk_patched_193.img
If you use Platform tools from Google officially, you needn't to care about your current slot actually.
Now reboot your phone:
Code:
fastboot reboot
Step 4: Restore stock boot image and reinstall Magisk (For OTA update ability although no update for months)
After your phone booted, enable USB debugging and copy the file "H1A1000.010ho.01.01.01r.109-boot.img" you downloaded along with patched boot image. I would assume you copied it to root directory of internal storage.
So execute following ADB commands:
Code:
$ su
(Confirm Root permission on the phone)
# getprop ro.boot.slot_suffix
If it returns a, you'll need to execute this command:
Code:
# dd if=/storage/emulated/0/H1A1000.010ho.01.01.01r.109-boot.img of=/dev/block/bootdevice/by-name/boot_a
If it returns b, you'll need to execute this command:
Code:
# dd if=/storage/emulated/0/H1A1000.010ho.01.01.01r.109-boot.img of=/dev/block/bootdevice/by-name/boot_b
Then open Magisk Manager on your phone, tap no thanks if it asks for extra modules, then tap "Install" at the right of Magisk version, choose "Direct Install", and wait for the procedure complete.
If installed successfully, you can reboot your phone on Magisk Manager now.
That's it!
At least this phone will work with Treble GSI build, so you should have idea about how could I dump the phone.
For Treble GSI report, read this: https://github.com/phhusson/treble_experimentations/wiki/Red-Hydrogen-One
For those who want to know how I dumped the phone:
Well, I found the phone could support Treble GSI and received update before.
So if your current slot is B, you definitely want to give it a try.
1. Unlock the bootloader
2. Download AOSP 8.1 Treble GSI from @phhusson 's repo:
https://github.com/phhusson/treble_experimentations/releases
In my case I chose system-arm64-ab-gapps-su.img.xz one
3. Enter fastboot mode and flash the image
Please check current slot as well
Code:
fastboot getvar current-slot
I would assume your current slot is B in this case.
Code:
fastboot flash system /path/to/system-arm64-ab-gapps-su.img
fastboot erase frp
4. Use volume key to choose "Reboot to recovery" then press power key to confirm
Press power key and volume up key to get the menu if "No command" appears, then choose "Wipe data/factory reset" to erase userdata storage.
Then reboot the phone.
5. After the phone booted, finish Setup Wizard.
6. Dump the boot image
Code:
adb shell
$ su
(Confirm root permission on the phone)
# dd if=/dev/block/bootdevice/by-name/boot_b of=/storage/emulated/0/stock_boot.img
# exit
$ exit
adb pull /storage/emulated/0/stock_boot.img
adb reboot bootloader
7. Switch to previous version, do factory reset
Code:
fastboot --set-active=a
Reboot to recovery and perform factory reset.
8. Reboot to normal OS and accept OTA update.
9. Use Magisk to patch the boot image you dumped, then root it with your patched boot image, or you can upload it if possible.
10. You can dump other partitions as well if you want.
Reserved 2
How to unlock the titanium alloy version?
great man! but H1T1000 ?How to unlock the titanium alloy version? Which one does boot. img use?
mavitz said:
great man! but H1T1000 ?How to unlock the titanium alloy version? Which one does boot. img use?
Click to expand...
Click to collapse
For Titanium variant H1T1000, I don't have the phone right away.
If you can assist me, I'd like to help you for H1T1000 firmware dumping and rooting.
你好,你也是中国人呀?能加一下QQ吗?我的QQ361212944 ,我进开发者里面OEM锁打勾了,然后进fastboot模式,输入那两个命令,都提示出错。希望你能帮帮忙。谢谢。
Well Sir
Just performed this procedure on my VZW black aluminum model and yup got ROOT! Everything works and is stable so far. 4view is working, camera is shooting 3D just fine. Not a single error, stopped app, like I said everything is chugging along. So sweet! Thanks man. I almost tried this exact procedure on my own but discussions in the h4vuser.net forums swayed me away. Just happy to have root access on my H1!
the H1 open market needs unlock code
Hey guys I ****ed up pretty big. Red wants me to send in my phone to get reimaged.
Can someone please dump their system.img for me.
https://www.addictivetips.com/mobil...es-boot-recovery-and-system-partition-images/
SynxSynx said:
Hey guys I ****ed up pretty big. Red wants me to send in my phone to get reimaged.
Can someone please dump their system.img for me.
https://www.addictivetips.com/mobil...es-boot-recovery-and-system-partition-images/
Click to expand...
Click to collapse
dump is here
https://github.com/AndroidDumps/red_hydrogenone_dump
joeyw007 said:
dump is here
https://github.com/AndroidDumps/red_hydrogenone_dump
Click to expand...
Click to collapse
Thank you so so much dude.
SynxSynx said:
Thank you so so much dude.
Click to expand...
Click to collapse
your welcome, hope it helps.
joeyw007 said:
your welcome, hope it helps.
Click to expand...
Click to collapse
I"m a little bit dense when it comes to this. I'm assuming this is the full oTA image that was captured somehow. Do I just repackage the whole thing into a zip, drop it on an SD card and then update through recovery mode? My flashing experience is kind of limited to just nexus devices which are notoriously easy.
SynxSynx said:
I"m a little bit dense when it comes to this. I'm assuming this is the full oTA image that was captured somehow. Do I just repackage the whole thing into a zip, drop it on an SD card and then update through recovery mode? My flashing experience is kind of limited to just nexus devices which are notoriously easy.
Click to expand...
Click to collapse
An official rom does not exist for this phone. at least not one we can access. That's why it's SUPER IMPORTANT not to make any booboos with rooting this phone. This is just a dump from a bone stock phone. I'm not sure, you're going to have to do some homework to see if it's even possible. I would think flashing the boot.img to the current boot slot Magisk patched should fix the issue depending on what caused it. Maybe someone else could chime in with a little more expertise on the matter. Never used a phone dump to create *.img file to flash via fastboot, if it's even possible. If you get it working and try to re root stop after step three do not perform the tasks in step four and turn off automatic system updates in dev options.
joeyw007 said:
An official rom does not exist for this phone. at least not one we can access. That's why it's SUPER IMPORTANT not to make any booboos with rooting this phone. This is just a dump from a bone stock phone. I'm not sure, you're going to have to do some homework to see if it's even possible. I would think flashing the boot.img to the current boot slot Magisk patched should fix the issue depending on what caused it. Maybe someone else could chime in with a little more expertise on the matter. Never used a phone dump to create *.img file to flash via fastboot, if it's even possible. If you get it working and try to re root stop after step three do not perform the tasks in step four and turn off automatic system updates in dev options.
Click to expand...
Click to collapse
Right for sure, but the thing is I think I messed up at the point where I ended up not being able to get it to boot after removing the stock facebook apps (Lord knows why) but I did get t successfully rooted. Once it hit that point I kind of panicked and ended up
c:\adb>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system_b'...
OKAY [ 0.354s]
finished. total time: 0.356s
That was my dun goofed point.
At this point it's now flashing to a boot_a slot where it used to be flashing to boot_b slot. I am able to get it to start loading the OS but I'm not sure why it's not actually booting. It makes it to the Verizon boot screen, but then just hangs there.
My request from you earlier to see if you could dump your system.img (Which should still be bone stock and doesn't contain user data) was to see if I flashed the system from fastboot it would work.
I think bootloader wise it's totally fine, it's just I can't get the system to boot.
So I'm not really looking for a rom-per-se I just want to see if I can get the system.img from someones (now rooted) device to see if loading it through fastboot will make it so I don't have to send it in and wait for 5 days to get my phone back
Yeah it's completely hosed. If anyone who's rooted can do the following steps for me, I would really appreciate it because I have no phone at the moment.
adb shell
su
ls -al /dev/block/platform/*/by-name
read the Partition Management Table and find something that looks like
system ---> /dev/block/mmcblk07
dd if=/dev/block/mmcblk07 of=/sdcard/system.img
then upload the ~3gb file
It's basically the only thing that will save me right now.
So I did some digging as I had no choice. I basically found that the hydrogen one doesn't use mmcblk's so I was giving bad info.
I worked with a friend who helped compile TWRP for the H1A1000 which can be found here https://androidfiles.host/2RE~i?cb1f802841522869ba768a30999b613a
You can use this by going into fastboot and doing fastboot flash boot twrp-3.3.1-0-HydrogenONE.img
If someone P L E A S E can load twrp
go into advanced>terminal
ls /dev/block/by-name
find their system_a and system_b mountpoints (Mine were sda6 and sda8 respectively) and then do
dd if=/dev/block/sda6 of=/sdcard/system_a.img
dd if=/dev/block/sda8 of=/sdcard/system_b.img
then upload those files to a mega
I would really really really like 100% totally appreciate it. Like I'll throw you 20$ at this point just for the trouble.
SynxSynx said:
So I did some digging as I had no choice. I basically found that the hydrogen one doesn't use mmcblk's so I was giving bad info.
I worked with a friend who helped compile TWRP for the H1A1000 which can be found here https://androidfiles.host/2RE~i?cb1f802841522869ba768a30999b613a
You can use this by going into fastboot and doing fastboot flash boot twrp-3.3.1-0-HydrogenONE.img
If someone P L E A S E can load twrp
go into advanced>terminal
ls /dev/block/by-name
find their system_a and system_b mountpoints (Mine were sda6 and sda8 respectively) and then do
dd if=/dev/block/sda6 of=/sdcard/system_a.img
dd if=/dev/block/sda8 of=/sdcard/system_b.img
then upload those files to a mega
I would really really really like 100% totally appreciate it. Like I'll throw you 20$ at this point just for the trouble.
Click to expand...
Click to collapse
Like FIH made HMD Nokia phones, I've created fastboot image for H1A1000 (Verizon only).
I will upload that to AFH soon.
hikari_calyx said:
Like FIH made HMD Nokia phones, I've created fastboot image for H1A1000 (Verizon only).
I will upload that to AFH soon.
Click to expand...
Click to collapse
Dude thank you so much.
edit, read your profile, donation link secured
To subscribers of this topic:
raw dump of H1A1000 for Verizon uploaded. Note, system and vendor images are raw ext4 images, use img2simg to process them if you want to use fastboot to flash it.
https://www.androidfilehost.com/?fid=1899786940962611843
Obs: these were the steps that i did to get it, try it by your own risk
----------------------update------------------------
Some people are saying that can't get the 11.1.021 via ota from zui10, but I got the information that this version of qfil 11.1.021 is getting ota to the 11.5, so you should try it just changing the files in the tutorial of step 1 and if don't get the ota, jump to the step 3
-------------------------------------------------------
I did the first part with my bootloader locked, and just got it working this way. I tried to qfil directly the 11.1.021 or use the version updated with the bootloader unlocked but i got error 7 later.
To start, you will need adb and fastboot, and you can get them from here
1- Qfil the zui 10 version from this tutorial
2- Set up a pin (it will be important) and update the zui to version 11.1.021 (right after you install the zui 10 it will pop the update, if not you can use the zui update app)
3- Now that you have 11.1.021 from ota you have to go to fastboot mode (adb reboot bootloader) and unlock your bootloader, if you do this on zui 10 or zui 11.5 you will got on bootloop and have to start all again (tutorial <- you can use this to lock your bootloader for start the proccess too)
4- Go again to bootloader and use fastboot flash recovery twrp.img (download twrp)
5- From fastboot mode, press volume down repeatly until you see "Recovery mode" then press power button, the phone will reboot twice and enter in twrp, you will need to put the pin set on step 2
6- Pass this update zip to your phone from the PC then select it on "install" section and swipe to flash (this was the step where i got error 7 with qfil version of 11.1.021, if you got this, the only solution i know is start all over again owith qfil zui 10)
7- After flash is done, go back to the home page of twrp, select "wipe" and mark "dalvik", "cache" and "data" then reboot system
Your phone will be on bootloop and this is the part that i discover after 2 days trying
8- Turn off your phone and turn it back pressing the power button and the volume down to enter in fastboot mode, you will see on last line that your bootloader will be locked again, and this is the cause of bootloop
9- Use the commands to unlock bootloader again (fastboot flash unlock your_unlock_img.img and fastboot oem unlock-go)
Your phone will boot and reboot in twrp that will do an automatic process, than will reboot again in ZUI 11.5.141 (may take some minutes)
Obs²: After this proccess, if you want to use TWRP to install a rom or something, you will need to flash it again
when I try to install just I got error 7 for everstep :S how can I solve it ?
brujaboy said:
when I try to install just I got error 7 for everstep :S how can I solve it ?
Click to expand...
Click to collapse
Did you try it from qfil the zui 10 with the locked bootloader?
Because i got this error when i ota updated from 10 to 11.1.021 with the bootloader unlocked
Astronomico said:
Did you try it from qfil the zui 10 with the locked bootloader?
Because i got this error when i ota updated from 10 to 11.1.021 with the bootloader unlocked
Click to expand...
Click to collapse
yes I did my friend I installed zui10 with QFIL after that I ınstalled 11.0.21 with twrp and when I try to install 11.5 I got error 7, I did edit with notepad++ but still have this problem
brujaboy said:
yes I did my friend I installed zui10 with QFIL after that I ınstalled 11.0.21 with twrp and when I try to install 11.5 I got error 7, I did edit with notepad++ but still have this problem
Click to expand...
Click to collapse
I think the problem is with the version you're installing in TWRP , after qfil zui10, wait for the OTA for 11.1.021 of the app zui update, it seems to exist some versions of 11.1.021 and the TWRP version is not the same of the OTA
The version of 11.1.021 that i've got by OTA with my bootloader already unlocked on zui10 got error 7 too, just the version i've got with the bootloader locked worked
Astronomico said:
I think the problem is with the version you're installing in TWRP , after qfil zui10, wait for the OTA for 11.1.021 of the app zui update, it seems to exist some versions of 11.1.021 and the TWRP version is not the same of the OTA
The version of 11.1.021 that i've got by OTA with my bootloader already unlocked on zui10 got error 7 too, just the version i've got with the bootloader locked worked
Click to expand...
Click to collapse
we need wait thank u bro
Microsoft Windows [Version 10.0.18362.657]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot> adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Fixed
this is whilest in fastboot.. ^^
{
"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"
}
View attachment 4951729
it pushes a command when phone was on but when in fastboot / bootloader nothing ? any ideas?
Fixed
every time i push recovery img twrp via ADB it gets bootloader loop
leerh said:
every time i push recovery img twrp via ADB it gets bootloader loop
Click to expand...
Click to collapse
That's weird, i've uploaded the same img i used on mine smartphone, it reboot twice, but starts after in my case, i just got bootloop after unlock the bootloader, but never after flash the twrp...
Try to turn your phone on holding the vol down button to enter in fastboot and check if it's really unlocked, since you flashed the twrp, you will need it
Btw, try to use the files of this tutorial
Astronomico said:
That's weird, i've uploaded the same img i used on mine smartphone, it reboot twice, but starts after in my case, i just got bootloop after unlock the bootloader, but never after flash the twrp...
Try to turn your phone on holding the vol down button to enter in fastboot and check if it's really unlocked, since you flashed the twrp, you will need it
Btw, try to use the files of this tutorial
Click to expand...
Click to collapse
yhyh it says device is unlocked ive used unlock image from lenovo site to unlock it.
im currently on 11.1.021 st cant install twrp affter installing keeps booting to bootloader (unlocked) from here i will need to use qfill to get stock firmware 10.5.304 cn version stock recovery still works
ive also tried on ZUI_10.5.304 same thing
qill emergency flash dose not lock bootloader for me? well i cant twrps anymore makes me feel its step away from total brick
do i need to lock it then qfill then 11.1.021st via OTA then unlock it
I've Just googled It and i found that flash magisk could repair the twrp bootloop, because magisk changes the boot.img that is the cause of the problem
You can download It on magiskmanager site, put it on your phone, than use twrp install session to flash it
And Qfil doesn't Lock your bootloader
Astronomico said:
I've Just googled It and i found that flash magisk could repair the twrp bootloop, because magisk changes the boot.img that is the cause of the problem
You can download It on magiskmanager site, put it on your phone, than use twrp install session to flash it
And Qfil doesn't Lock your bootloader
Click to expand...
Click to collapse
thanks for looking into it for me and i will try this out now and let you know the results done.
this a fresh from factory flash so there is no magisk modules. can you post the links to the information you found.. i cant flash any files affter installing twrps which is successful the via ADB but affter the reboot or trying twrps or access phone or recovery will bootloop my phone to go into fast boot every single time...
can i install twrps on 10.304 and 11.021 both are offical cn roms? device has to be unlocked right which it is? is there any place i can get stock recovry image?
i wanna try= fastboot flash boot_a stockboot.img=fastboot flash boot_b stockboot.img
but i dont think i should as qfil provides stock factory flash? means its fully fresh?
leerh said:
thanks for looking into it for me and i will try this out now and let you know the results done.
this a fresh from factory flash so there is no magisk modules. can you post the links to the information you found.. i cant flash any files affter installing twrps which is successful the via ADB but affter the reboot or trying twrps or access phone or recovery will bootloop my phone to go into fast boot every single time...
can i install twrps on 10.304 and 11.021 both are offical cn roms? device has to be unlocked right which it is? is there any place i can get stock recovry image?
i wanna try= fastboot flash boot_a stockboot.img=fastboot flash boot_b stockboot.img
but i dont think i should as qfil provides stock factory flash? means its fully fresh?
Click to expand...
Click to collapse
Oh, i thought you could access the twrp after install it, sorry
The tutorial on step 1 provides the official cn rom zui10, if you use it, your phone will probably boot normally.
I think you should lock your bootloader and use the official, you will have the updates via OTA, since you can't use TWRP, I think it will be the best for you, I don't know how help you more :/
I have a request anyone can share with my twrp back up clear update without data like zip file because I have problem with my QFIL and when I try to install zui 10.5 give me sahara error and I thought about this option
brujaboy said:
I have a request anyone can share with my twrp back up clear update without data like zip file because I have problem with my QFIL and when I try to install zui 10.5 give me sahara error and I thought about this option
Click to expand...
Click to collapse
Sorry, i didn't see it, but saraha error is probably caused because wrong version of USB drivers in your PC, or you're being too slow to press "download content" on qfil after plug the phone (I don't know exactly why, but you have to click it fairly fast)
Astronomico said:
Sorry, i didn't see it, but saraha error is probably caused because wrong version of USB drivers in your PC, or you're being too slow to press "download content" on qfil after plug the phone (I don't know exactly why, but you have to click it fairly fast)
Click to expand...
Click to collapse
doesn't matter, thank u so much for replying yesterday I installed all of driver versions but I saw still again and I find another method like pushing very fast download click button and I did successfully 11.1.021 thank u so much again for supporting
Astronomico said:
Obs: these were the steps that i did to get it, try it by your own risk
I did the first part with my bootloader locked, and just got it working this way. I tried to qfil directly the 11.1.021 or use the version updated with the bootloader unlocked but i got error 7 later.
To start, you will need adb and fastboot, and you can get them from here
1- Qfil the zui 10 version from this tutorial
2- Set up a pin (it will be important) and update the zui to version 11.1.021 (right after you install the zui 10 it will pop the update, if not you can use the zui update app)
3- Now that you have 11.1.021 from ota you have to go to fastboot mode (adb reboot bootloader) and unlock your bootloader, if you do this on zui 10 or zui 11.5 you will got on bootloop and have to start all again (tutorial <- you can use this to lock your bootloader for start the proccess too)
4- Go again to bootloader and use fastboot flash recovery twrp.img (download twrp)
5- From fastboot mode, press volume down repeatly until you see "Recovery mode" then press power button, the phone will reboot twice and enter in twrp, you will need to put the pin set on step 2
6- Pass this update zip to your phone from the PC then select it on "install" section and swipe to flash (this was the step where i got error 7 with qfil version of 11.1.021, if you got this, the only solution i know is start all over again owith qfil zui 10)
7- After flash is done, go back to the home page of twrp, select "wipe" and mark "dalvik", "cache" and "data" then reboot system
Your phone will be on bootloop and this is the part that i discover after 2 days trying
8- Turn off your phone and turn it back pressing the power button and the volume down to enter in fastboot mode, you will see on last line that your bootloader will be locked again, and this is the cause of bootloop
9- Use the commands to unlock bootloader again (fastboot flash unlock your_unlock_img.img and fastboot oem-unlock go)
Your phone will boot and reboot in twrp that will do an automatic process, than will reboot again in ZUI 11.5.141 (may take some minutes)
Obs²: After this proccess, if you want to use TWRP to install a rom or something, you will need to flash it again
Click to expand...
Click to collapse
Hi bro. I see a little error in your command: The second command in the 9th step is wrong, the correct command is: "fastboot oem unlock-go".
Greetings.
leerh said:
yhyh it says device is unlocked ive used unlock image from lenovo site to unlock it.
im currently on 11.1.021 st cant install twrp affter installing keeps booting to bootloader (unlocked) from here i will need to use qfill to get stock firmware 10.5.304 cn version stock recovery still works
ive also tried on ZUI_10.5.304 same thing
qill emergency flash dose not lock bootloader for me? well i cant twrps anymore makes me feel its step away from total brick
do i need to lock it then qfill then 11.1.021st via OTA then unlock it
Click to expand...
Click to collapse
i got step 1,2,3,4,5 and 6, got an error #7.
so i used the tutorial to flash the device in step 1
it was unable to update cuz bootloader was unlock
i locked bootloader and update to 11.1.021
so afther that, i unlocked again to install twrp.
intalled twrp and transfer file to phone
booted twrp and installed the zip, got the error 7 again.
lipeneiva said:
i got step 1,2,3,4,5 and 6, got an error #7.
so i used the tutorial to flash the device in step 1
it was unable to update cuz bootloader was unlock
i locked bootloader and update to 11.1.021
so afther that, i unlocked again to install twrp.
intalled twrp and transfer file to phone
booted twrp and installed the zip, got the error 7 again.
Click to expand...
Click to collapse
best thing is to try again an follow every letter and step this only way to install 11.5 (beta) did u set a pin it is needed ive not seen another guide to install android 10
Lombachita said:
Hi bro. I see a little error in your command: The second command in the 9th step is wrong, the correct command is: "fastboot oem unlock-go".
Greetings.
Click to expand...
Click to collapse
Ops, fixed
Hello. I've tried many different ways to install the customs ROMs on here for Moto G8 Power (XT2041-3) but nothing has worked. When I try to flash using fastbootd every ROM except the Lineage one fails at the stage where I try to load the system.img. Even when I think I've correctly installed Lineage that way, when I go to reboot my phone it won't boot properly. I keep getting the screen alternating between the Motorola icon and the unlocked bootloader warning screen. It does that repeatedly for a while and then eventually boots as if I am powering on my phone for the first time out of the box after buying it.
So I've also tried TWRP. Again, I can seemingly install some of the flashable zips (Lineage and Omnirom), but when I reboot the same thing happens. Motorola screen, unlocked bootloader warning screen, etc, repeately for a couple of minutes, and then it boots to the Android system that came with the phone. As if there's been a total factory reset and I am turning on the phone for the first time. ADB sideload doesn't work either because even though it can detect ADB devices at first, as soon as I go to sideload on TWRP and then try "adb sideload .....zip" on the terminal of my computer (Linux) it doesn't seem to recognise any ADB devices any more.
I know it says to reboot to recovery after installing a custom ROM, but the same thing happens if I try that. Some sort of bootloop I think, and then basically a factory reset start.
TWRP doesn't seem to permanently install on my phone. If I try going into bootloader and then recovery after I have just used TWRP then all I get is the 'No Command' screen. Could this be part of the reason? I recently found out about DM-Verity. Could something on my phone be preventing changes to the system? It's really frustrating. Previously when I've installed custom ROMs on other Motorola phones I haven't had any problems. Any suggestions would be much appreciated. Thanks
Check out my post here.
Thanks tinbilly but I'm still unsure what to do. I hadn't tried CrDroid before so before anything I tried flashing those image files via fastbootd. Same problem - it failed at system.img. Which leaves me unable to boot into custom ROM or stock ROM. Before when that has happened I have always been able to just reflash stock using the commands on the XML file. Now even the first command fails (fastboot getvar max-sparse-size) so I don't seem to be able to get back to stock at the moment. I'll keep trying.
I didn't know how you flashed stock ROM to partition b. The only way I can think to change to partition b is to go into fastbootd and use the "fastboot set_active b" command. Or to flash TWRP (which doesn't work at the moment) and change slots that way. I think changing it on fastbootd might have messed me up a bit because it just went into a bootloop when I tried to do anything after that. For some reason I seem to be back in partition a now though (I typed "fastboot getvar all" while I was in fastbootd and it came back showing slot a).
Here is my suggestions:
1. Hard reset your device following this or this. They are basically the same instruction. Hopefully this will get your phone back to the stock rom. If not, then just try step 2 below.
2. Install the xt2041-3 stock rom on your device by following the instructions in the download link. Or you could try this method.
3. Once you are back to stock rom, you can install any custom rom via fastboot mode.
Hope that will help.
Thanks for that. I'm going to work on it over the weekend and see how I get on. I feel like I've spent too many valuable hours of my life trying to figure this out. If only this custom ROM thing could just be straightforward for everyone all the time.
tinbilly said:
Here is my suggestions:
1. Hard reset your device following this or this. They are basically the same instruction. Hopefully this will get your phone back to the stock rom. If not, then just try step 2 below.
2. Install the xt2041-3 stock rom on your device by following the instructions in the download link. Or you could try this method.
3. Once you are back to stock rom, you can install any custom rom via fastboot mode.
Hope that will help.
Click to expand...
Click to collapse
Cheers for your suggestions but nothing has worked. The phone wasn't taking any commands to reinstall stock ROM so I went to fastbootd (via recovery - no command - hold power button and up) and did a factory reset from there. Then I was able to flash the commands on the stock ROM xml file via the bootloader. So I got back to stock fine. But after trying to flash Lineage OS it seems to have worked fine but when I go to reboot I keep booting to bootloader. I tried fastboot oem fb_mode_clear but that didn't change anything. I'll keep trying different things and let people know if I find a solution.
lazzr said:
Cheers for your suggestions but nothing has worked. The phone wasn't taking any commands to reinstall stock ROM so I went to fastbootd (via recovery - no command - hold power button and up) and did a factory reset from there. Then I was able to flash the commands on the stock ROM xml file via the bootloader. So I got back to stock fine. But after trying to flash Lineage OS it seems to have worked fine but when I go to reboot I keep booting to bootloader. I tried fastboot oem fb_mode_clear but that didn't change anything. I'll keep trying different things and let people know if I find a solution.
Click to expand...
Click to collapse
Did you format data before or after installing lineage os? As in, where you have to type yes, not just wiping data.
Beetle84 said:
Did you format data before or after installing lineage os? As in, where you have to type yes, not just wiping data.
Click to expand...
Click to collapse
Hi Beetle. I always swipe to the right to wipe the cache etc. And after flashing I swipe to wipe the dalvik. But I'm never given the option to type yes. I'm not sure what you mean.
I've spent a lot of time wondering why TWRP never reboots when I try to reboot into recovery after flashing a zip. I just realised (after reading the instructions for flashing ArrowOS on this forum) that I can flash TWRP to partition b as well by using the commands:
fastboot flash recovery twrp.img
fastboot flash recovery_b twrp.img
By doing that I was able to (or so I thought) install the zip to the inactive slot b, and then reboot to recovery using TWRP, and it comes back as having the active slot b. I got excited but when I went to reboot system the same thing happened. Just some sort of bootloop thing. Nothing seems to work. I've tried OmniROM and Stag zips as well.
lazzr said:
Hi Beetle. I always swipe to the right to wipe the cache etc. And after flashing I swipe to wipe the dalvik. But I'm never given the option to type yes. I'm not sure what you mean.
I've spent a lot of time wondering why TWRP never reboots when I try to reboot into recovery after flashing a zip. I just realised (after reading the instructions for flashing ArrowOS on this forum) that I can flash TWRP to partition b as well by using the commands:
fastboot flash recovery twrp.img
fastboot flash recovery_b twrp.img
By doing that I was able to (or so I thought) install the zip to the inactive slot b, and then reboot to recovery using TWRP, and it comes back as having the active slot b. I got excited but when I went to reboot system the same thing happened. Just some sort of bootloop thing. Nothing seems to work. I've tried OmniROM and Stag zips as well.
Click to expand...
Click to collapse
When you press wipe in twrp, down the bottom is a button 'format data', tap that, type yes and enter.
Then reboot.
Beetle84 said:
When you press wipe in twrp, down the bottom is a button 'format data', tap that, type yes and enter.
Then reboot.
Click to expand...
Click to collapse
Thanks. I tried it but then I end up with no zip file in my internal storage so have nothing for twrp to install. I tried copying and pasting the file from my PC to my Android folder but it was going to take about a week to copy over. I also can't use ADB sideload for some reason. I get this:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
and
E:Unable to get child ID
on my phone when I cancel the sideload. I can't figure it out at all.
I also just tried flashing my stock recovery to replace twrp. After I had already used twrp to format everything. Then went to fastbootd and tried flashing the image files. They looked like they had installed but now when I reboot it automatically takes me to bootloader instead of into system.
In twrp, there's no option to wipe system. So in my case, I replaced twrp with stock recovery, then did a Factory Reset [Advanced > Reset options > Erase all data (factory reset)].
Before "tried flashing the image files" in fastbootd, did you "fastboot set_active a"?
tinbilly said:
In twrp, there's no option to wipe system. So in my case, I replaced twrp with stock recovery, then did a Factory Reset [Advanced > Reset options > Erase all data (factory reset)].
Before "tried flashing the image files" in fastbootd, did you "fastboot set_active a"?
Click to expand...
Click to collapse
I've tried the "fastboot set_active a" but it still doesn't work. I've factory reset through stock recovery too, and seem to have tried everything I can think of. I miss my old original Moto G which was easy to install on. I've been trying for weeks and keep running into the same issues. I'll keep trying over the next few days and report back if I solve it in case anyone else has the same problem.
Mine is a XT2041-1. What I did:
1. flashed back to stock ROM 10_QPE30.69-16
2. rebooted the phone, then set it up (I did not upgrade to Android 11 as notified by the system)
3. wiped the phone using System > Advanced > Reset (just to be safe)
4. flashed to crDroid 7.4 (Android11-based)
You said you failed to load the custom ROM's system.img. What is the exact error message? Please attach some screenshots as well.
tinbilly said:
Mine is a XT2041-1. What I did:
1. flashed back to stock ROM 10_QPE30.69-16
2. rebooted the phone, then set it up (I did not upgrade to Android 11 as notified by the system)
3. wiped the phone using System > Advanced > Reset (just to be safe)
4. flashed to crDroid 7.4 (Android11-based)
You said you failed to load the custom ROM's system.img. What is the exact error message? Please attach some screenshots as well.
Click to expand...
Click to collapse
I thought I'd try some more possible ways to fix it before replying but I've just wasted another few hours to no avail. I have the flashable zips for OmniROM 11 and Lineage, but I can't even get TWRP to ask for a password anymore so all my files show up as gobbledegook. Not that I think they would work either because they haven't so far.
The one that I thought had been successful was installing Lineage images using fastbootd, but whenever I go to reboot I end up in bootloader. The bootloader log says "Reboot mode set to fastboot". I have no idea how to get out of that. Fastboot fb_mode_clear doesn't work.
I thought I would try to root the phone (I know people say you don't need to do that first but I'm sure in the past I have done) but I can't get Magisk to install.
I installed Lineage images again, and then after it rebooted into bootloader I installed TWRP and tried entering the dd commands on this page in the terminal (I didn't know how to do the backup in section 2 of the instructions):
Troubleshooting: TWRP Boot Loop after OTA update in MOTO G4 (XT1621 Athene)
Hi. This is my first post in this forum. I had this problem, the phone always started in TWRP Mode after updating by OTA update, I should NOT have updated it this way, but I have done it still. :cyclops: XD To fix it, try this: TWRP Method: 1-...
forum.xda-developers.com
All I got back was "no such file or directory".
The error message from installing images (the one below was CrDroid 7.4 but it happens with most of them) seems to be quite common from what I can tell from reading other people's posts. I have also I tried "sudo" before flashing the system image because I've seen that recommended, but it didn't work either:
writing 'system_a' 5/6 (usually 3/3 on other ROMs)...
FAILED (remote: Operation not permitted)
{
"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"
}
Wiping my data and formatting has caused me some issues too. I've done that many different things that I can't remember what exactly, but I do know that when I tried to install ZIP files using TWRP the Failed to mount '/system_root' error message came up a few times.
I've attached an images below to give an example of the types of other red screen messages I've had:
Forgive the long message. If any of this gives you any ideas or you've seen it before then please let me know. To be honest I just want a phone without all the google stuff on it and the amount of time I've spent on this I'm feeling like I should just get myself a different phone it would be easier to install on.
By the way, the image at the bottom there was the error message I got while trying to wipe in TWRP
A final attempt for now. I factory reset through fastbootd. Then "installed" Lineage image files. Rebooted and ended up in bootloader. Flashed TWRP, which this time could recognise my folders. ADB pushed Omnirom zip to my data folder. Tried a wipe, got lots of error messages, then tried installing the zip, and got the below:
This whole experience has been brutal.
From my experience with TWRP on my XT2041-1, I won't go with TWRP to flash a custom ROM. So just forget TWRP for now.
One important question, I think: Can you flash and boot your device to stock Android 10? [Note: I find this is a reliable method to go back to stock ROM. Just make sure you get the correct one matching your device.]
If yes, let take it as a starting point. From there, I suggest you wipe the phone using System > Advanced > Reset then flash to a Custom ROM using fastbootd. Btw, which custom ROM you prefer and intend to flash on your phone?
lazzr said:
A final attempt for now. I factory reset through fastbootd. Then "installed" Lineage image files. Rebooted and ended up in bootloader. Flashed TWRP, which this time could recognise my folders. ADB pushed Omnirom zip to my data folder. Tried a wipe, got lots of error messages, then tried installing the zip, and got the below:View attachment 5309925
This whole experience has been brutal.
Click to expand...
Click to collapse
What did you do after factory reset? How did you install Lineage image files? Please briefly describe what you did step-by-step. Just briefly.
tinbilly said:
From my experience with TWRP on my XT2041-1, I won't go with TWRP to flash a custom ROM. So just forget TWRP for now.
One important question, I think: Can you flash and boot your device to stock Android 10? [Note: I find this is a reliable method to go back to stock ROM. Just make sure you get the correct one matching your device.]
If yes, let take it as a starting point. From there, I suggest you wipe the phone using System > Advanced > Reset then flash to a Custom ROM using fastbootd. Btw, which custom ROM you prefer and intend to flash on your phone?
Click to expand...
Click to collapse
I can boot to stock using the same list of commands in that link. Starting with fastboot getvar max-sparse-size. Then I set up my phone to enable USB debugging and "file transfer" under default USB configuration. Then "ADB reboot bootloader", and click to enter recovery. I get the "No command" screen so I hold the power button and press up. Then "enter fastboot" to enter fastbootd. I've followed the next few instructions exactly as everyone says. Set active a, flash boot then system etc, then erase userdata.
This time I enabled "PTP" instead of "File Transfer" under default USB configuration to see if it made any difference. It still won't load system and I get this message:
sending sparse 'system_a' 1/2 (720896 KB)...
OKAY [ 20.736s]
writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
I don't understand how it helps to install stock ROM and then wipe the phone using System > Advanced > Reset. That just puts me back to the same place as after I installed stock and I have to go in Developer Options etc again.
I'll try any ROM. I'm trying CrDroid now but it doesn't work. Lineage is the only one that seems to install system but I can't reboot to system.