Alright, I've tried a lot of things. I'm using Pie firmware, .10 to be specific, flashed through EDL, used parted to resize my partitions.
Problem is, it starts booting. Then, nothing. It's like a complete pause to the bootanimation.
I removed the bootanimation that comes with it, so that I'd see that gradient "android" text bootanimation, which doesn't seem to freeze, but it doesn't solve my problem either.
Any ideas?
-I even gone as far as to give my system_a, which ZenUI is currently residing on about 6 gigs of space, just to make sure it's not freezing because of running out of space, since it only had about 400 MBs left beforehand.
-I'll try flashing last Oreo firmware, repartition, then ZenUI again, but that's my best bet.
-I did use permissiver, don't know if that was a mistake or not though.
-I also tried installing magisk, to see if it's a boot problem.
-Lastly, I tried removing the bootanimation.zip from /system/media.
Bump, since not a single person out of the 3-away-from 110 people said a single word of advice, through a matter lasting more than 10 days.
I'm either alone with this problem, or people who knew about the issue missed this, or just nobody took the effort to explain. I'd rather take the second option.
I´m not sure exactly, I tried in other devices and most of them booted up after to target on the exact files combination required.
Just some things to consider and that they could help:
- Be sure that the image is for A/B partitioned devices.
- Check through fastboot the active slot and/or where the image was installed and see on wich slot device is trying to boot.
- Permissiver v4 looks like the last solution zip to be flashed.
- Try with other vendor, for this you have to first erase the actual by fastboot erase vendor and then flash other using command along fastboot.
- The same thing as last with boot image, you can try with other boot image from different roms.
- Flash Disable Force Encryption variants.
- In any try you have to return to the original state before to add an action, it means that if a combination files didn´t work probably you have to start again from the scratch by wiping, formatting, installing, etc.
I tried with and without permissiver, I resized partitions myself, so I naturally checked where it installed, it was always A
Either way, I resized everything so that both slots were 3.5GBs, just to make sure that 200MBs of free space wasn't enough.
Since I was resizing, I always went back to clean slate through EDL, even as far as to try using Oreo firmware instead of Pie, to see if that boots. No difference.
Only thing from what you said I haven't tried is using a different vendor image, always used provided from our firmwares.
Related
Hi,
I made some mistake when trying to get the Oreo soak to flash. I flashed back the stock boot.img (since the backup made by Magisk caused some error) and WiFi wasn't working. It showed to be disabled woke searching for WiFi without possibility to turn it on, so I tried to reflash the latest official ROM.
RSD lite can't find my device and all the manual methods either and in since error or include bootloader locking or going back from a custom ROM (and most likely wiping /data for compatibility). I found one that separated out a few files that could wile internal storage but it would be stuck on that back/white Motorola logo (the one you get unlocking bootloader and hiding the warning). A different one wanted to flash that gpt file but that gave me an error in terminal.
I was able to get everything running by restoring boot image and something else from TWRP, the only thing remaining is that when I bootup/reboot my phone it automatically boots into fastboot so I have to hit the power button on,"start", which is a bit annoying.
But also for the future: is there any simple way to flash from the .xml.zip files like with Googles image files or Samsung's .tar.md5 through ODIN or something like that? Or at least a working manual method not including bootloader lock or loosing any data?
It seems like I've found a working manual myself that includes creating a bat file and explains what you have to do to either keep or whipe data. Don't know what it's doing that much different, I just know that it doesn't give me any (real) errors.
So after an upgrade attempt to Resurrection Rom, which worked, except for a failure of the System restore/backup tool upon setup...so I decided to once again Deuce back to stock.
Now, ever since that, I run the normal process, reboot after Deuce to do a stock setup, it keeps defaulting back to Slot B apparently.
So, I have to keep fastboot --set-active=_a then restart, and it boots and works normally.
No idea how/why it keeps going back to B slot after Deuce, which sets it in the script to Slot A...when this happens, it gives the Device is Corrupted message. So I force it to slot A, boots normal.
Anybody seen this? Any Rom I flash now, or any flash back to Stock using something like Deuce, keeps reverting the default Slot to B?
Edit: Also, can someone post their getvar all through fastboot and post it...obviously clear out your IMEI/phone info...but want to see the default settings for the slots etc.
Thanks
I would suggest flashing the stock ROM images per Google's instructions here. That's how I went from Android 8.1 to the Android P Dev Preview. I don't know what Deuce is or does, but I would try Google's method to see what happens. Attached the output of the command on my device (Pixel 2 XL, 128 GB, Android P Dev Preview, Bootloader locked, not rooted).
RMarkwald said:
I would suggest flashing the stock ROM images per Google's instructions here. That's how I went from Android 8.1 to the Android P Dev Preview. I don't know what Deuce is or does, but I would try Google's method to see what happens. Attached the output of the command on my device (Pixel 2 XL, 128 GB, Android P Dev Preview).
Click to expand...
Click to collapse
Deuce you take the OTA/Google official, extract the zip to the folder Deuce is in...it will basically run all the commands to do what the Flash_all does. Many people, like me, if I run the standard Google Flash all, get an error about not enough space to flash the files. Deuce solves this for many.
I can flash it and go back to stock, it is just when I then try to flash a custom Rom, it goes all crazy and then back to Slot B...no idea. Otherwise, get corrupt system message, have to change the slot to Active A...and it boots from there.
Thanks for the getvar. Everything is identical except my bootloader is: version-bootloader:TMZ12bb
techlogik said:
Deuce you take the OTA/Google official, extract the zip to the folder Deuce is in...it will basically run all the commands to do what the Flash_all does. Many people, like me, if I run the standard Google Flash all, get an error about not enough space to flash the files. Deuce solves this for many.
I can flash it and go back to stock, it is just when I then try to flash a custom Rom, it goes all crazy and then back to Slot B...no idea. Otherwise, get corrupt system message, have to change the slot to Active A...and it boots from there.
Thanks for the getvar
Click to expand...
Click to collapse
Yeah, I recall the flash-all file being an issue in the past. I thought I'd run into that when going through their instructions on flashing their Android P Dev Preview, to my surprise, it worked without error/issue. Don't know if this was fixed by them along the way or if I just happened to get lucky.
I have it back on the stock Dom after Deuce and restored. But anytime now I try to install a custom Tom, slot B ends up active after the normal install routine. Weird. Stock no problems.
Thanks think the phone is jacked somewhat now.
I have it back on the stock Dom after Deuce and restored. But anytime now I try to install a custom Tom, slot B ends up active after the normal install routine. Weird. Stock no problems.
Thanks think the phone is jacked somewhat now.
I have the exact same issue, using Pixel 2 XL 64gb. I've tried everything and slot a is not working.
Did you find a fix?
I actually get this error now:
C:\Data_Files\1>fastboot flash boot --slot all radio-taimen-g8998-00202-1802061358.img
Sending 'boot_a' (60412 KB) OKAY [ 1.300s]
Writing 'boot_a' FAILED (remote: Error flashing partition.)
Click to expand...
Click to collapse
At first I tried to update my existing TWRP (3.2.1-0) to the 3.2.1-2 variant. It flashed ok, but then the phone would only boot to TWRP (reason for upgrade is that 3.2.1-0 would hang). I was attempting initially to put myself on the path to a "custom rom". When this failed, I manually flashed the latest google firmware from their page and it still will not do anything other than fastboot mode. No recovery, no firmware load. When I try to do the flash-all.bat method now, all I get after it loads the archive contents is "error: Cannot generate image for userdata. Guess I got a $1000 brick at this point?? Image from the PC screen included.
See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698
I am going to have to find another way to look at that thread. My ipad is getting directed to some HTC desire article about and orange and black theme.
I have tried so far very unsuccessfully to wipe everything by booting to twrp via fastboot method. Then I used the dueces script to reflash everything completely (both partitions). No matter whether I flash complete stock or flash magisk and verizon radio files, it just hangs on the white google screen now and that is as far as I have gotten. Left it at home in this mode hoping it will clear.
JoeNeckbone said:
See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698
Click to expand...
Click to collapse
That link is bad. Three devices are going to an htc desire theming page.
remove the -w from the update line in flash-all.
I have got the same problem since yesterday and search for a solution.
ctradio said:
That link is bad. Three devices are going to an htc desire theming page.
Click to expand...
Click to collapse
Not sure what happened with link, https://forum.xda-developers.com/pi...ry-image-flashing-fails-t3715350/post74751631
new adb dont help for me. I cannot flash slot a and change to b and got the error message that no slot is supported.
Still need help? Have you tried Skipsoft? Sure its not been updated but it might beable to help ..
Where fastboot flashing failed for me one time it got me out of a hole....
Otherwise i can try and remote and help... BTW its not finding the userdata file in the fastboot side... Something isnt right hence why it cant create the userdata file...
I try to boot with skipsoft to temp twrp but stuck on boot.img loading. the flashed twrp stuck on twrp logo and before I have changed from slot b to a inside twrp i can boot. now I cannot flash inside fast boot or delete anything.
Have you guys tried Deuces Bootloop Recovery & Flashing Script? I'd imagine you'd run into the same issues as the script runs a lot of the same fastboot commands...but it has worked wonders for many other users so......
I also might try re-downloading the factory image and comparing the Checksums to make sure you have a whole exact download just in case that's getting in the way of properly generating the userdata image. I'd also suggest making sure you have more than 4GB of space on your C drive; I was getting similar messages about not finding or not generating system images because they couldn't be fully extracted (temporarily) because I didn't have sufficient temp space on my C drive.
But I had encountered this issue before. It was either userdata or system_other partition. I did attempt to fastboot erase and fastboot format those partitions and other tweaks; even messed with changing the size of the partition (you might have better luck). What I seemed to conclude is that I was flashing the wrong month's Full Factory image; i.e. I was manually flashing system_other image from February when the whole phone was still on January. But I believe what I ended up doing was flashing a Full Factory image with the "-w" intact; therefore, if you still have access, you should copybackcup (via TWRP or adb pull) your internal storage (/sdcard and-or /data/media) and simply flash a Full Factory image with wipe option enabled...
Just some thoughts and suggestions...hope this helps...
I figured it out finally. Even though my ADB/Fastboot tools were a later creation date than the ones posted online, the ones online worked great. Even used the dueces script to ensure the junk is gone. Thanks all! Hate pesky gotchas like that!!
Hi,
This is less of a question and more of an experience. That being said, if anyone has any suggestions, I still do not have a correctly mounted /system partition (I think).
Background:
I am new to the world of custom ROM's and the community with which it resides. I did dabble in it a few years back with the original casio commando, but that was before I ever touched a linux machine or read a line of code. I decided to mess with my new Moto e4 (XT1768), mostly to remove bloatware and maybe flash a custom ROM, though I did like the factory.
Procedure:
I unlocked the bootloader and flashed a custom recovery (TWRP) through fast boot. Flashed Magisk and got superuser permissions. Everything seemed to go fine. I didn't notice it at first, so I'm not exactly sure which step caused it, but every time I would reboot the phone, it would boot to recovery.
I was able to boot into fastboot from TWRP. From there I could start the OS. So i ignored it. But upon trying to run system updates they would fail.
Problem:
NOW I decided this minor glitch was the result of a larger issue. Turns out, somewhere between flashing TWRP recovery and flashing Magisk, I inadvertently removed/corrupted my /system partition. I get a error on reboots "unable to mount partition." When I tried to flash a custom rom RR, it would raise errors about /system not existing. In the TWRP "mount" menu, "system is unchecked, even when I check it and reboot. When I reboot the bootloader from TWRP I would get a msg NO OS Installed. This last one is contradictory because I can still access the OS, could make calls, etc.
Troubleshooting:
I tried remounting the /system partion, though I don't think I did it correctly. I couldn't find much about fixing partitions, and do not feel like breaking my phone, since it still works. Unfortunately I did not take a backup of the factory installation (won't do that again). The only backup I had was after the bootloader was unlocked and Magisk was installed. Rolling it back to this image, I am able to flash RR custom rom and it works fine, though the original issue still exists. I tried a few attempts to remove Magisk from the backup image, but results in a boot loop when booting to the OS. When it went well, I was able to boot straight to the OS, without it automatically booting to recovery, but the boot loop prevented any advancement.
I so far have not seen this particular issue happen to anyone else. If you have any suggestions, or advice on where to find a compatible factory ROM for the Moto e4 (XT1768), send them over. I've tried to flash a factory ROM that was close to my model, but no luck. If anyone has run into this probem, let me know so I don't think I'm the only one out here.
Nich
I know of one instance which can cause rebooting to result in recovery mode and system mount issues, as well as a solution to resolve it. When installing firmware via fastboot, or any other files via fastboot (even unlocking the bootloader with fastboot), it is extremely important that your first command is this:
fastboot oem fb_mode_set
And your last command this:
fastboot oem fb_mode_clear
Sometimes, a failure to initiate and close fastboot with the above command lines will result in exactly what you are describing. Of course, to fix the issue, you will need to flash a compatible stock firmware package with the opening and closing lines I've listed. I will check my sources and try to find a package for your model.
Update: I have found a factory firmware package for the xt1768, which I am downloading now. I'll get you a link as soon as I get it downloaded, then uploaded to my cloud host.
Amazon xt1768 Moto E4 stock firmware package -- Build No. NPQS26.69-64-8
https://drive.google.com/file/d/12hABSzvUpSZOYEUdX5ssCXYZmjA-Z10n/view?usp=drivesdk
nich42 said:
I so far have not seen this particular issue happen to anyone else. If you have any suggestions, or advice on where to find a compatible factory ROM for the Moto e4 (XT1768), send them over. I've tried to flash a factory ROM that was close to my model, but no luck. If anyone has run into this probem, let me know so I don't think I'm the only one out here.
Click to expand...
Click to collapse
If you have a retail (aka open market) XT1768 - you can get firmware from here. The one at the bottom dated September 18th is the most recent.
The Amazon one posted by MotoJunkie01 may have differences from the this one (i.e. Amazon apps/branding).
hitokage004 said:
If you have a retail (aka open market) XT1768 - you can get firmware from here. The one at the bottom dated September 18th is the most recent.
The Amazon one posted by MotoJunkie01 may have differences from the this one (i.e. Amazon apps/branding).
Click to expand...
Click to collapse
Thanks everyone. Yeah I have the open market version. I'll give these a look.
MotoJunkie01, I have not seen these commands before, which would probably explain why I broke it. Thanks I'll try and implement them.
fastboot oem fb_mode_set
And your last command this:
fastboot oem fb_mode_clear
nich42 said:
Thanks everyone. Yeah I have the open market version. I'll give these a look.
MotoJunkie01, I have not seen these commands before, which would probably explain why I broke it. Thanks I'll try and implement them.
fastboot oem fb_mode_set
And your last command this:
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
This is probably a dumb question. How do I flash it with fastboot? I've only installed a ROM from TWRP, so not sure how to run it from fast boot. do I need to install each partition separately or is there a flash-all file. I notice the flashfile file has a lot of command like arguments in it. Can I use that?
Thanks,
nich42 said:
This is probably a dumb question. How do I flash it with fastboot? I've only installed a ROM from TWRP, so not sure how to run it from fast boot. do I need to install each partition separately or is there a flash-all file. I notice the flashfile file has a lot of command like arguments in it. Can I use that?
Thanks,
Click to expand...
Click to collapse
Yes if you flash it with fastboot you do it one image at a time. You can also install RSD Lite on a Windows computer and it will do it all for you by selecting either the flashfile.xml or the service file. XML.
UPDATE:
Thanks for the assistance. I know it's been a while, but I've been busy the past few months.
I found a guide that had all the pieces I was looking for. As far as I can tell it went well, though it doesn't seem to be completely back to normal. I was able to unmount the recovery partition, but it was not re-mounted/installed.
I plan to unlock and install TWRP as the recovery. I may also try and root the phone, but keep the factory OS. But we'll see...
I'm about 4 hours of reading in on this matter, and I still don't have a proper answer. I've run through countless threads with similar titles, and found some helpful tidbits, but nothing the resolves or fully explains what is going on here.
I just made the jump from Android 9.0.0 (latest) rooted to Android 10.0.0 (latest.) Here were my steps:
Download the latest Platform Tools & unzip
Download the latest Android 10.0.0 Factory image for Pixel 2 XL & unzip into the platform tools folder
Download the latest USB drivers & install
Hook up my phone to the computer (Windows 10) and verify that ADB & Fastboot are working properly via command prompt
Execute the flash-all.bat (left the -w flag in so that it wiped my data) -- it appeared to be only flashing the one slot except for a couple mentions of the other slot's system towards the end of the commands
The phone booted just fine and I went through and installed TWRP and Magisk 23 and so on
Here's where I encountered the error:
As I was rebooting out of TWRP, I realized I'd never used the "Slot A" or "Slot B" buttons, so I picked one, and it started rebooting the phone. The normal screen with the yellow text about phone being unlocked came up, then switched to the white background with the 'G' as expected. The expected next step would've been the 'G' spinning into a circle for a second, and then going to the homescreen, but instead what happened was the screen went black, and then a screen that said "Your device is corrupt. It can't be trusted and may not work properly." showed. It looked similar to the one when the phone first boots with the yellow text about the bootloader, but this text was red. I attempted to use the power button to bypass it, and when I did, it switched the the normal yellow-text-about-bootloader screen, and then switched to the 'G' with the white background again, but there it stayed, just frozen.
I was still able to boot to bootloader by using the power + down button, and could then boot to the stock recovery, but that was it. After a bit of reading, I discovered the following command:
fastboot set_active a
or
fastboot set_active b
and also fastboot getvar all
The set_active command chooses which Slot is being used, and the getvar command shows all the fastboot variables, one of which shows the "current_slot." Once I set the other Slot to be the active one and rebooted, the phone booted normally. Buuut, now I'm concerned that someone is screwed up with my phone, and it's going to fail at some point when I don't have my computer handy, so I went back to work trying to resolve the error when I booted out of the one slot.
Here's what I've tried:
Run the flash-all.bat file in one slot, let the phone reboot, boot to bootloader, switch slots, reboot to bootloader, flash-all.bat in the other slot.
Same as above, but without the -w flag.
Manually flash the bootloader, radio and image zip on both slots
Install the TWRP while booted into the adb-loaded TWRP img (this seems to write to both slots based on the output)
Install and uninstall Magisk both via recovery and via the patched stock boot image.
After every single attempt, the one slot would work just fine, and the other slot would exhibit the behavior I mentioned. Depending on which Slot is flashed first, the Slot that fails to boot properly does change (ie. it's not always Slot A or Slot B that fails.)
Untested methods:
Screwing with dm-verity -- I saw one thread that gave a few fastboot commands to disable dm-verity, and a couple people reporting success with it. After searching around and doing a bit of reading on dm-verity, I still don't understand what it does, whether disabling it would have any negative repercussions, and whether disabling it would fix the issue legitimately, or just kinda mute it.
Using Deuce's bootloop recovery tool -- again, I don't really know what that thing is running, it hasn't been maintained in quite some time as far as I can tell, and there are several threads indicating that it runs a bunch of haphazard stuff that could cause more problems. Some reports indicated it worked for them, but I'm concerned about what else it might be doing that may negatively affect things down the road.
Re-locking the bootloader -- I saw this one mentioned several times, but I also saw several people warning that you could brick your phone if you do it wrong. I also saw one or two folks who seemed like they couldn't get back to being unlocked after re-locking. I don't want to screw with this option given those risks.
Can anyone give me any more tips on how to resolve this? I'm pretty sure that the Pixels are supposed to run equally well from both slots, so I'd really like to get the matter resolved so I don't have to worry about what would happen if my phone moved me over to the other Slot for some reason. Any insight and explanations are appreciated!
People say that you cannot install both TWRP and magisk (I haven't tried it myself). So start again with a flash-all, and then, instead of installing TWRP, run it using fastboot boot whenever you need it.
The OP needs to flash a factory image first or the corruption message will never disappear. While he's at it he should make the jump to Android 11...latest radios and all that. If he doesn't want to lose data he can edit flash-all.bat in the factory image and remove the -w flag in that batch file.
From there he can flash anything he wants. If he plans on rooting however he cannot install TWRP, only boot it using ADB. The combination of Magisk and TWRP causes a bootloop.
runekock said:
People say that you cannot install both TWRP and magisk (I haven't tried it myself). So start again with a flash-all, and then, instead of installing TWRP, run it using fastboot boot whenever you need it.
Click to expand...
Click to collapse
The problem presents with even the stock boot image though.
Strephon Alkhalikoi said:
The OP needs to flash a factory image first or the corruption message will never disappear. While he's at it he should make the jump to Android 11...latest radios and all that. If he doesn't want to lose data he can edit flash-all.bat in the factory image and remove the -w flag in that batch file.
From there he can flash anything he wants. If he plans on rooting however he cannot install TWRP, only boot it using ADB. The combination of Magisk and TWRP causes a bootloop.
Click to expand...
Click to collapse
Understood on the magisk / twrp thing, but regarding the factory image, that is exactly what I was going. The problem presents even after doing that. That's why it's so puzzling.
Edit: it's admittedly a very long post, but if you look at the section that's numbered, you'll see I'm grabbing the latest factory image for Android 10 and flashing it. Then in the section labeled "Here's What I've Tried" (aka my attempts to troubleshoot) the very first thing I did was flash the factory image (including the wipe) to both Slots and then trying to boot from one slot and then from the other.
Grab an Android 11 package and don't remove the -w flag when installing. The corruption may be persisting because user storage isn't being wiped.
The factory image - NOT OTA - is the only way to fix this short of sending the device to Google for service.
Strephon Alkhalikoi said:
Grab an Android 11 package and don't remove the -w flag when installing. The corruption may be persisting because user storage isn't being wiped.
The factory image - NOT OTA - is the only way to fix this short of sending the device to Google for service.
Click to expand...
Click to collapse
Why would it be any different when I wipe with Android 10 or Android 11? I flashed the latest Android 10 factory image to the phone *with* the -w flag as mentioned in my "here's what I tried" section. I even went so far as to force the phone to Slot A with the "set_active" command, and then set_active Slot B and flashed the factory image (not the OTA) again. After doing that, the one slot will boot just fine while the other gives the error. If I change it up and flash Slot B first and then Slot A the same thing occurs, just in reverse (the slot that booted before throws the error while the slot that threw the error before now boots.)
My initial post explains why I recommended an Android 11 ROM (updated radio). Any of them will of course work, but that's beside the point. Try using ADB to format the partitions and see if that resolves the issue. Otherwise contact Google, as I can't think of anything else that would be blocking you.
I had this same issue and Flashing Android 11 on both partitions (without removing the -w command) resolved it.
I first booted into Recovery Menu and wiped both slots. Then downloaded the factory image (not ota) and flashed each slot separately wiping the device after each flash in recovery menu. it's the only way to fix this just like user @Strephon Alkhalikoi
If that doesn't resolve it then you have an issue that's more serious and will require a repair of some sort (not necessarily hardware).