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.
Related
First off, I don't know if this is the perfect place for this thread so I apologize in advance.
I have a HTC Evo 4G LTE and I accidentally wiped everything with TWRP. It can boot to the bootloader/fastboot menus and TWRP no problem, but I can't install anything. Maybe i'm just doing everything in the wrong order. Both the SD card and the Internal SD cards have been formatted to what they're supposed to be (caused me a bit of trouble at first). My phone is set to S-On, which is a pain in the ass, because from what I understand I can't turn it off to flash a new ROM without an OS, which I don't have. Every time I attempt to install the stock ROM for my device the phone restarts when attempting to install the kernel, included in the ROM. I borrowed my friend's identical phone, rooted it and installed TWRP, created a backup, moved the backup to my phone's ext SD card and attempted to recover off of that but my TWRP can't find any of the files, but they show up just fine with the file explorer.
I've properly srewed myself. Any advice?
windowpuncher said:
First off, I don't know if this is the perfect place for this thread so I apologize in advance.
I have a HTC Evo 4G LTE and I accidentally wiped everything with TWRP. It can boot to the bootloader/fastboot menus and TWRP no problem, but I can't install anything. Maybe i'm just doing everything in the wrong order. Both the SD card and the Internal SD cards have been formatted to what they're supposed to be (caused me a bit of trouble at first). My phone is set to S-On, which is a pain in the ass, because from what I understand I can't turn it off to flash a new ROM without an OS, which I don't have. Every time I attempt to install the stock ROM for my device the phone restarts when attempting to install the kernel, included in the ROM. I borrowed my friend's identical phone, rooted it and installed TWRP, created a backup, moved the backup to my phone's ext SD card and attempted to recover off of that but my TWRP can't find any of the files, but they show up just fine with the file explorer.
I've properly srewed myself. Any advice?
Click to expand...
Click to collapse
Since you are s-on you need to flash the rom twice.
BD619 said:
Since you are s-on you need to flash the rom twice.
Click to expand...
Click to collapse
I am new to ROM flashing, I just kind of got thrown into it, lol. Please elaborate? I'm assuming flashing is installing the rom with TWRP. I flash the rom, wipe cache/dalvik, then flash again? I'll try it then post results in a minute.
Result: Doesn't work, when it says "installing Kernel, please wait...", it stays on that message for a minute or so then the phone attempts to reboot into a nonexistant OS, effectively stopping itself so I have to restart into TWRP again with no progress made.
I think you want to let it reboot in between the two flashes. I have no idea why it makes a difference, but it does.
Sent from my EVO LTE using XDA Premium 4 mobile app
Read this:
http://forum.xda-developers.com/showthread.php?t=2443108
Some Sense ROM's include a kernel installer to help facilitate flashing while S-on. You'll need to check the ROM OP and see. Otherwise the kernel can be flashed via fastboot. For more info hit the top link in my sig.
Sent from my HTC device
fizbanrapper said:
I think you want to let it reboot in between the two flashes. I have no idea why it makes a difference, but it does.
Sent from my EVO LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It can't. It reboots while attempting to install the kernel then freezes because there's no OS to boot to.
Try flashing the kernel first. Extract the boot.img file from the ROM zip archive using your computer. Then, with the phone connected to the PC via USB, boot into the bootloader and go to fastboot. It should change to "fastboot USB". Then use the fastboot tool from a command prompt to verify connectivity and flash the kernel.
To verify connectivity, type fastboot devices. You should see your device's serial number of its connected properly.
To flash the kernel, type fastboot flash boot boot.img. If the boot.img file and fastboot executable are in different directories, you'll need to include the path to the file. Or just put them in the same directory.
Once you've flashed the kernel, try flashing the ROM through recovery again.
Sent from my EVO using Tapatalk
CornDogg said:
Try flashing the kernel first. Extract the boot.img file from the ROM zip archive using your computer. Then, with the phone connected to the PC via USB, boot into the bootloader and go to fastboot. It should change to "fastboot USB". Then use the fastboot tool from a command prompt to verify connectivity and flash the kernel.
To verify connectivity, type fastboot devices. You should see your device's serial number of its connected properly.
To flash the kernel, type fastboot flash boot boot.img. If the boot.img file and fastboot executable are in different directories, you'll need to include the path to the file. Or just put them in the same directory.
Once you've flashed the kernel, try flashing the ROM through recovery again.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Doesn't work. I can plug my phone in all I want but it will never change to fastboot usb. It stays in fastboot just fine and I can still boot TWRP, but there's no fastboot usb. I've reinstalled drivers and tried 32 bit LiveCD ubuntu. I may need to install firmware on this stupid phone.
From the main bootloader screen, you're pressing the power button on fastboot to go into fastboot, right? And from there you can never get it to go to fastboot USB?
Sent from my EVO using Tapatalk
If you're on the old partition layout have you followed my guide that I posted previously and tried to install MeanBean ROM?
Sent from my HTC device
CornDogg said:
From the main bootloader screen, you're pressing the power button on fastboot to go into fastboot, right? And from there you can never get it to go to fastboot USB?
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Yes, that was the case.
HOWEVER, I screwed up again. I reinstalled Ubunto on my laptop and now fastboot usb works just fine.
Sometimes it hurts to live. Now I just need to find out how to flash with fastboot on ubuntu.
windowpuncher said:
Yes, that was the case.
HOWEVER, I screwed up again. I reinstalled Ubunto on my laptop and now fastboot usb works just fine.
Sometimes it hurts to live. Now I just need to find out how to flash with fastboot on ubuntu.
Click to expand...
Click to collapse
Progress.
To get the fastboot binaries on Ubuntu, you can either download and install the Android SDK and install the platform tools or go download DirtyRacun from unlimited.io. The binaries are included in the .tar archive. You may need to use the chmod command on the fastboot and adb binaries to add permissions to execute the binaries.
Once you have the binaries executable, the commands are the same, except you'll have to elevate with sudo. So, assuming you're working in the directory where you have the fastboot executable and the boot.img file, the commands would be:
sudo ./fastboot devices
sudo ./fastboot flash boot boot.img
CornDogg said:
Progress.
To get the fastboot binaries on Ubuntu, you can either download and install the Android SDK and install the platform tools or go download DirtyRacun from unlimited.io. The binaries are included in the .tar archive. You may need to use the chmod command on the fastboot and adb binaries to add permissions to execute the binaries.
Once you have the binaries executable, the commands are the same, except you'll have to elevate with sudo. So, assuming you're working in the directory where you have the fastboot executable and the boot.img file, the commands would be:
sudo ./fastboot devices
sudo ./fastboot flash boot boot.img
Click to expand...
Click to collapse
fter I
{
"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"
}
This is what happens. My phone just sits there, the screen doesn't change, but it does say Fastboot USB. I restarted my phone but it got stuck at the dev boot screen with legal warnings in red text.
Addition: Booted to recovery to flash the ROM zip, not just the boot image, still restarts when attempting to install the Kernel.
The screen on your phone won't change when flashing the kernel with fastboot. After flashing it, press the power button on Fastboot to go back to the main bootloader screen and go to recovery to get into TWRP. From there, flash the .zip of the ROM that you pulled boot.img from like you normally would from TWRP (Install, select .zip, wipe cache/data, etc).
CornDogg said:
The screen on your phone won't change when flashing the kernel with fastboot. After flashing it, press the power button on Fastboot to go back to the main bootloader screen and go to recovery to get into TWRP. From there, flash the .zip of the ROM that you pulled boot.img from like you normally would from TWRP (Install, select .zip, wipe cache/data, etc).
Click to expand...
Click to collapse
I just did this, and the phone gets stuck at the dev boot screen that says HTC with the red legal text.
Have you tried a different ROM? Maybe try CM or Viper 4G. If you go the Viper 4G route, try this one: http://forum.xda-developers.com/showthread.php?t=2124391
I think the newest Viper 4G changes the partition layout or something, so I think that would just further complicate things at the moment.
CornDogg said:
Have you tried a different ROM? Maybe try CM or Viper 4G. If you go the Viper 4G route, try this one: http://forum.xda-developers.com/showthread.php?t=2124391
I think the newest Viper 4G changes the partition layout or something, so I think that would just further complicate things at the moment.
Click to expand...
Click to collapse
Yeah, I think I'll try cyanogenmod or stock android. Thank you for the suggestion, now i'll go see if it works.
No problem. If you decide to go the CM route, deck's CM11 is pretty great.
http://forum.xda-developers.com/showthread.php?t=2518211
Good luck!
CornDogg said:
No problem. If you decide to go the CM route, deck's CM11 is pretty great.
http://forum.xda-developers.com/showthread.php?t=2518211
Good luck!
Click to expand...
Click to collapse
I went on with installing DirtyRacun (http://unlimited.io/jewel.htm) and made it to step 12. As my phone ws rebooting it once again got stuck at that HTC red text dev warning screen. So now i'm stuck again.
windowpuncher said:
I went on with installing DirtyRacun (http://unlimited.io/jewel.htm) and made it to step 12. As my phone ws rebooting it once again got stuck at that HTC red text dev warning screen. So now i'm stuck again.
Click to expand...
Click to collapse
I didn't use DirtyRacun to S-OFF (I used RumRunner), so I can't speak on this with much authority. Just to confirm I understand correctly, though, you flashed the RUU (step 9), rebooted into the bootloader (step 10), and re-did the HTC Dev Unlock (step 11). Then, as it's booting up into the ROM installed via the RUU, it gets stuck?
Were you able to get anywhere with flashing Cyanogenmod? Or did you just decide to go through the S-OFF process instead?
How to flash a factory image | Return to stock | Unroot your Nexus 6P
Hello Nexus 6P Users!
This tutorial will show you how to reset/unroot/save your Nexus 6P by flashing the Google Factory Images.
{
"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"
}
WARNING!!!
This process will wipe your phone completely. Backup your storage before you continue.
I am also not responsible if anything goes wrong.
FOLLOW EVERY SINGLE STEP
or you will end up in a bootloop, or with a bricked phone, and we don't want that
Let's get started!!
Setting up
For this process, you will need to:
★Install adb and fastboot drivers. To do this, use this simple program:
http://forum.xda-developers.com/showthread.php?t=2588979
For MAC and Linux users: simply follow these instructions:
http://forum.xda-developers.com/showthread.php?t=2638673
Off-topic: installing ADB and Fastboot so easily, what a time to be alive!
★Download the latest factory images from here:
https://developers.google.com/android/nexus/images#angler
★Extract the archive you downloaded (Use WinRAR). It should look like this:
★Unlock your bootloader (In case you haven't already). Only follow step 1 from this thread:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Flashing the factory images
There is more than one way to flash these images. Each give the same results, but the first is for lazy (or smart) users
Method 1. Easy method.
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Execute the flash-all.bat script (for Windows) or flash-all.sh(for MAC and LINUX) in the folder where you extracted the factory images.
**!!** For MAC: You'll have to edit the flash-all.sh, and add "./" before every fastboot command.
★Wait for everything to flash.
★After everything finished, select "Recovery" using the volume buttons.
★When a small dead Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
Method 2. Long method (Same thing actually, but I'll mention it, just in case first one does not work)
★Extract the image-angler-xxxxxx.zip from the previously extracted folder somewhere easy to access (On C:\images for example. Make it easy to type). You will have the following files:
★In the new folder, from the original archive/folder, extract "bootloader-angler-angler-XX.XX.img" (rename it to bootloader.img) and "radio-angler-angler-XX.XX" (rename it to radio.img)
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Open a CMD window.
★Type the following commands, in this order (If you have a different folder, change the path)
Code:
fastboot flash bootloader C:/images/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/images/radio.img
fastboot reboot-bootloader
fastboot flash system C:/images/system.img
fastboot flash vendor C:/images/vendor.img
fastboot flash userdata C:/images/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/images/boot.img
fastboot flash recovery C:/images/recovery.img
fastboot erase cache
fastboot flash cache C:/images/cache.img
★After everything finished, select "Recovery" using the volume buttons.
★When a small Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
And now you have a brand new Nexus 6P (software wise, at least). Congratulations!
Credits and Thanks:
@Mr hOaX
Got some fastboot command "updates" from you
@Heisenberg
Really cool root tutorial
err.... Heisenberg's already have a tutorial on how to return to stock... not sure why we need a duplicate posting..
#9 How To Flash The Factory Images (And Return To Stock)
abaaaabbbb63 said:
Credits and Thanks:
Mr hOaX
Got some fastboot command "updates" from you
Heisenberg
Really cool root tutorial
Click to expand...
Click to collapse
Nice to see you here bro
Good job
This guy's tutorial will really save your nexus for sure
gd6noob said:
err.... Heisenberg's already have a tutorial on how to return to stock... not sure why we need a duplicate posting..
#9 How To Flash The Factory Images (And Return To Stock)
Click to expand...
Click to collapse
I thought that a separate thread would raise its visibility and would be easier to spot for users that do not know their way around XDA that well.
abaaaabbbb63 said:
I thought that a separate thread would raise its visibility and would be easier to spot for users that do not know their way around XDA that well.
Click to expand...
Click to collapse
Followed the instructions and im getting an error cant find the files
joeyac02 said:
Followed the instructions and im getting an error cant find the files
Click to expand...
Click to collapse
Can you describe what exactly did you do?
At which point did you encounter the error?
When I download the images it doesn't contains Angler-bootloader and Radio.img. It only contains one file with the boot.img, etc... I tried downloading all the 6.0.0 link and it's all the same . I don't understand.
Thank you for the post. Hope I don't need to use it tho. :good:
I cannot make phone calls through the phone app?
I followed directions step by step but every time I get to the dead android guy and hold vol up + pow. I do not get the "stock" recovery where I could choose to data/factory reset, I just get the little dead android guy again.
Any help?
Nice guide
Sent from my Nexus 6P using Tapatalk
From Heisenberg post says that
Note: You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have.
Click to expand...
Click to collapse
And I have 64gb of storage. should I wipe or flash?
cediedc said:
From Heisenberg post says that
And I have 64gb of storage. should I wipe or flash?
Click to expand...
Click to collapse
You can do both. Just in case, your storage spaces shows reductions after flashing (Like my 64GB variant shows 32 GB), you can fix it by wiping data from stock recovery.
If you're not willing to remove the data on your internal storage, you can skip flashing userdata.img.
tried to go back to stock but stuck on google logo..what to do?
jordy787 said:
tried to go back to stock but stuck on google logo..what to do?
Click to expand...
Click to collapse
Did you flash the the correct vendor.img, corresponding to your factory image?
DJBhardwaj said:
Did you flash the the correct vendor.img, corresponding to your factory image?
Click to expand...
Click to collapse
nope just the factory image from google..can you send me the link to the vendor img for latest stock build? and do i fastboot flash it? thanks
jordy787 said:
nope just the factory image from google..can you send me the link to the vendor img for latest stock build? and do i fastboot flash it? thanks
Click to expand...
Click to collapse
Vendor.img is already included in the factory image. If you used flash-all.bat script, it must have been flashed. What commands did you precisely use to flash the factory image?
cediedc said:
From Heisenberg post says that
And I have 64gb of storage. should I wipe or flash?
Click to expand...
Click to collapse
Don't ever flash it. It has no benefit and only causes problems. If you need to wipe your storage use this command:
Code:
fastboot format userdata
jordy787 said:
tried to go back to stock but stuck on google logo..what to do?
Click to expand...
Click to collapse
Did you wipe data with TWRP first? That's probably what's causing your problems. Vendor most likely has nothing to do with it.
Heisenberg said:
Did you wipe data with TWRP first? That's probably what's causing your problems. Vendor most likely has nothing to do with it.
Click to expand...
Click to collapse
I used the wug tool kit and it worked
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
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.
Will there be a TWRP version compatible with oxygen os V14 currently running on European Nord 2?
I tried previous TWRP guides for the Nord 2 but it didn't work.
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Zombnombs said:
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Click to expand...
Click to collapse
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Copaxy97 said:
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Click to expand...
Click to collapse
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Zombnombs said:
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Click to expand...
Click to collapse
Thanks for your help. I will try that again later.
What i can say i 100% opened the command prompt in the correct folder and the flash always said succesful.
I also thought about the command promt folder error before but it is correct. At least somehting got wiped (my recovery) but i simply cannot access it.
I will try again later and go over each step step by step and share ym results here. I hope i did a mistake because otherwise i don't know how to locate the problem.
Okey i did it again like the tutorial and also a second time like you said but it sadly didn't work.
{
"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"
}
This is my output from the command line. i use minimal ADB and fasstboot. But normal powershell by shift right click gives me the same output.
But when i try to reboot and boot into the recovery it just jumps to fastboot mode. So the stock recovery got flashed or removed then. But why i cannot boot into twrp?
Bootloader unlocked and based on the messages in the cmd everything fine.
Any ideas?
***Edit***
It worked now. If you ask me why, i don't know.
I did exactly the same in minimal adb and fastboot tools and on powershell. Both didn't work.
I did it in total 5 times and the last one in powershell randomly was succesful lol.
weird...
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Zombnombs said:
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Click to expand...
Click to collapse
Yeah might be true. I don't know.