I feel really sorry that I have to part with this device when I've only owned it for a couple of days. But I have to do it!
OK, I'll get straight to it:
1. I was on ICS 4.0.4 Stock,un-rooted and boot loader remained locked.
2. Then I decided to Unlock the Bootloader and flash the Twrp recovery and then I flashed the EOS Jelly Bean stable for MZ604 WiFi UK version.
3. I need to get it back to stock. As in, stock ICS, un-rooted and bootloader relocked (If that's possible).
4. Now I'm not that kind of guy that will ask a question before doing loads of research on a thing. So this is what I found out but just need some confirmation from some experienced Xoom users who have done this procedure before. First of all I've read through this Official Xoom website: http://developer.motorola.com/products/software/ And then I figured that I have to download this version:
Build H.6.2-24 for Retail Europe
MD5 Sum: cae470d91a6f6e1473f981bc06f452fd
Spain, Italy, Austria, Switzerland, UK, Sweden, Norway, Denmark, Netherlands 118 MB Jun. 2, 2011 MZ604 Product Specs Download
Since I do live in the UK. And then after that I would have to follow these instructions given by Motorola themselves:
INSTRUCTIONS TO FLASH & RE-LOCK YOUR MOTOROLA XOOM:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
And by this I'm guessing they mean, first download the Zip and then extract all of the files to the place where the file ADB and Fastboot reside. And then put your motorola xoom in fastboot mode by connecting it to the computer via the motorola usb cable that was provided in the box. And have usb debugging enabled. Then open command prompt and type in adb reboot bootloader. Which would then reboot to fastboot mode and then you'd have to type in these commands.
Also would I have to type these commands seperately right?
So first: Typing in command prompt: fastboot flash boot boot.img
Then after that has finished I do the next and the next and the next until it comes down to the "fastboot oem lock" which I guess should be the relocking part and the other parts were flashing the stock img and removing the recovery in order to put everything back the way it was before.
So now after following all those instructions, I'm guessing that everything should be back as it was before. As in, I could easily go and hand this in the store that I bought it from and they wouldn't notice a single thing. Right? And of course the tablet would be running stock ICS 4.0.4, unrooted and bootloader locked, right?
I would really appreciate anyone reading through these instructions and maybe confirming if they are right or if they are wrong, could you please show me the right way?
Thank you very much
With regards,
Beston94
This is all you should do,.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache..
an unlock bootloader still update..i never lock back mine..
tumpy said:
This is all you should do,.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache..
an unlock bootloader still update..i never lock back mine..
Click to expand...
Click to collapse
Perhaps you misunderstood me because I don't need to update but I need to return it as it was.
Hello! I've tried to root my phone (Moto G XT1541 Europe 1GB) but failed. I got an error when trying to flash the custom recovery. Unfortunately, it has overwritten the stock recovery and it didn't install. So, now I have a phone without recovery and I can't do a factory reset because of that (I think).
So, this is my question: how can I re install the default Android 6.0 recovery mode for my phone?
Also, my phone boots automatically on bootloader mode and I can't re-lock the bootloader because I can't flash anymore either; I got an error because the pre flash validation failed when trying to flash with adb fastboot, but this is minimal issues that doesn't really bother me, but they could be helpful and if someone knows how to get rid of them, I want to know!
I hope someone will help me!
Azyreal said:
Hello! I've tried to root my phone (Moto G XT1541 Europe 1GB) but failed. I got an error when trying to flash the custom recovery. Unfortunately, it has overwritten the stock recovery and it didn't install. So, now I have a phone without recovery and I can't do a factory reset because of that (I think).
So, this is my question: how can I re install the default Android 6.0 recovery mode for my phone?
Also, my phone boots automatically on bootloader mode and I can't re-lock the bootloader because I can't flash anymore either; I got an error because the pre flash validation failed when trying to flash with adb fastboot, but this is minimal issues that doesn't really bother me, but they could be helpful and if someone knows how to get rid of them, I want to know!
I hope someone will help me!
Click to expand...
Click to collapse
The bootloader cannot be relocked in the Moto G 2015, the best you can do is hide the warning screen. Find the stock image and fastboot flash the recovery from there, or better yet, flash the entire image so you are in a known working state
If you are in Pre-Flash validation, you do not have the correct image for your device... I suggest you post in the "How to flash factory images" thread about returning to stock, if it is possible. You MUST factory default before flashing factory images, if you can't, try 'fastboot erase userdata' and try again.
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system,
reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Rename twrp recovery as only twrp in fastboot folder in your pc , not as twrp.img,
But cmd as fastboot flash recovery twrp.img , then no errors ( are you unlocked bootloader ?)
acejavelin said:
The bootloader cannot be relocked in the Moto G 2015, the best you can do is hide the warning screen. Find the stock image and fastboot flash the recovery from there, or better yet, flash the entire image so you are in a known working state
If you are in Pre-Flash validation, you do not have the correct image for your device... I suggest you post in the "How to flash factory images" thread about returning to stock, if it is possible. You MUST factory default before flashing factory images, if you can't, try 'fastboot erase userdata' and try again.
Click to expand...
Click to collapse
drmuruga said:
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system,
reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Rename twrp recovery as only twrp in fastboot folder in your pc , not as twrp.img,
But cmd as fastboot flash recovery twrp.img , then no errors ( are you unlocked bootloader ?)
Click to expand...
Click to collapse
Hey! Thank you! I've been able to flash the TWRP recovery and now I can do a factory reset (and also send sms, which I couldn't do anymore for some reason).
I still have the issue where the bootloader screen appears everytime I turn my phone on, and I still can't re lock my device because I can't flash anything either. I've recovered all of my data, so I think I'm going to stick with that for a moment but maybe I'll try what you said some day.
Again, really thank you for helping me!
drmuruga said:
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system, reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Click to expand...
Click to collapse
Now I understand why my flashing TWRP did not take. I simply rebooted to system and still have stock recovery installed. I was successful booting twrp via fastboot and successfully flashed supersu 2.62.3. Is this step in listed in any faq? I must have missed it.
So after flashing TWRP, do you then power down device prior to manually booting to recovery?
MrTooPhone said:
Now I understand why my flashing TWRP did not take. I simply rebooted to system and still have stock recovery installed. I was successful booting twrp via fastboot and successfully flashed supersu 2.62.3. Is this step in listed in any faq? I must have missed it.
So after flashing TWRP, do you then power down device prior to manually booting to recovery?
Click to expand...
Click to collapse
Don't power down, already you are in fastboot mode, you can just enter recovery from that. I forget the reference, but i will search and post.
---------- Post added at 04:41 PM ---------- Previous post was at 04:18 PM ----------
I get this from twrp official page
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
In our phone press simultaneously volume down + power button to enter recovery.
hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?
well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this
ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing
If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.
I've got a BIG problem with my new Pixel 5. I've successfully rooted it and had it operating for a day.
I then decided to boot into recovery mode just to see what the new stock recovery looks like (I used to use TWRP.).
BIG MISTAKE!
All I got was the error icon that I've seen in the past meaning that no recovery image is available. OK, so I try to just try to do a simple reboot. I'm taken back to the same place.
Now I try to reload Android. No luck! I'm stuck on:
"Device product is 'unknown'"
Update requires 'bramble'.
HELP!!!!
In the file android-info.txt, what would happen if I patched the line
require board=bramble
to
require board=unknown
Did you figure this out? I'm facing the same issue with my Pixel 5.
Edit: I figured it out. If you are having an issue with the 'flash-all.bat' command like we were, you just need to manually push the individual files and it should boot you back up into stock.
Run these commands:
1. fastboot flash bootloader <bootloader image file>
2. fastboot reboot-bootloader
3. fastboot flash radio <radio image file>.img
4. fastboot reboot-bootloader
5. fastboot update <image zip file>.zip
6. fastboot reboot
All of the reboot-bootloader commands may be redundant but it worked for me. It booted me into stock, verified I was unrooted with Root Checker, then proceeded to reboot back into the bootloader and 'fastboot flashing lock' to re-lock my bootloader and wipe the device.
So i goofed up and wiped everything under advanced when I was switching Roms. I was able to get the original recovery image installed (nv-recovery-st-wx-na-wf-5.2.0.zip) but if i reinstall TWRP and attempt to install any rom, the device name is still "" instead of "ShieldTablet". Is there anyway to restore the device name? I have been digging around on the forums (Including other device forums) but installing recovery is all I have been able to find. (Note: There was some guides advising removal of the device name check from the script within the image file, then re-zipping it. But this seems to always fail with a bad image error.)
Recovery was installed manually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Recovery image pulled from https://developer.nvidia.com/shield-open-source
More info to issue.
Boot into bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Boot into OS. (everything works.)
EnableUSB debug
adb shell settings get global device_name (Gives back "SHIELD Tablet")
Reboot into bootloader
fastboot flash recovery twrp-3.5.1_9-0-shieldtablet.img
Reboot into twrp
Copy on Rom and attempt to install.
Error text:
E3004: This package is for device: shieldtablet; this device is .
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Lineage-14.1-20210312-unofficial-shieldtablet.zip'
Note: above error text occurs when trying to install any ROM.
I am trying to figure out where "E3004: This package is for device: shieldtablet; this device is ." is pulling the device name. That is the part that I need to fix somehow.
Hi did you try to use a older version of twrp ? I also had my issues with the 9.5.1 version as it doesnt recognize my sdcard so i reflashed the version 9.5.0
You beautiful person! Downgrading from twrp-3.5.1_9-0-shieldtablet.img to twrp-3.5.0_9-0-shieldtablet.img allowed the img to install!
Checking in with the same problem. Thank you for the solution listed of downgrading to 3.5.0_9-0.
Currently flashing!