Related
Fluxion reset & recovery tool
Hi everyone,
I have created a reset tool which allow to bring the Oneplus Two back to stock
At the moment it is only available for Linux, but if think that i will add the tool
for windows shortly too.
Warning
You do this on your one risk. I’m not responsible for any damage. I’m also not responsible:
If your alarm clock is not working and you gets fired.
If you phone will get overheat
If the phone don’t turn on.
Features
1) Erase everything
2) Back to stock
3) [Auto] custom Recovery
4) Auto root
Fluxion erase:
Cache
Userdata & Userdata_64
System
Modem
Modemst1
Modemst2
Instructions:
1) Download and install fastboot
2) Download the ZIP file
3) Extract the ZIP file
$ sudo unzip restore.zip
4) Move in the folder
$ cd restore
5) Type:
sudo chmod +x restore.sh
sudo ./restore
[now a menu should pop up]
Select Erase
Select back to stock
Select custom recovery (please select costum recovery if something goes wrong you have access to your phone & and file storage )
Download the newest oxygen version
Reboot into recovery [Press volume button down and power button at the same time]
Connect your phone with PC
Drag and Drop the oxygen version on your phone
Go to flash
Select oxygen version and click on flash
Click on change recovery
Reboot
Done!
Solves:
Fingerprint BUG ( 50 % changes )
Fix IMEU BUG
Wifi and simcard and bluetooth should now work
Fix crashes after flashing a android 6 ROM
TOOL: http://www.mediafire.com/download/1jf67jsvlm1thr5/restore.zip
Man this is a great tool. I only use linux aka ubuntu and couldnever find a tool to return to stock. after a few fails I finally got my device back to stock. thanks again. if you even need help or wanna work on a project together on future oneplus devices let me know.
HELP BAT
the_rooter said:
Man this is a great tool. I only use linux aka ubuntu and couldnever find a tool to return to stock. after a few fails I finally got my device back to stock. thanks again. if you even need help or wanna work on a project together on future oneplus devices let me know.
Click to expand...
Click to collapse
Do you now how write functions in batch, because I plan to create a BAT file so windows users can use it too. I though that the partitions are still to bugy because /devinfo would not longer work, I hope you / I can fix it soon hopefully...
And what does mean after few fails? Crashed the program or get you a error
I've used fastboot zip to roll back to stock with everything, even got OTA after it. It has a command bundled, just run it once and you're done.
Got it 2nd post from the link below:
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
i managed to edit the linux command to windows cmd
will try to erase all and flash the stock function now
UPDATED to include instructions for flashing other ROMS
I've successfully unlocked, flashed TWRP, rooted, and flashed Lineage on both an XT1602 and an XT1607. I'd done this before on other devices, but had forgotten just how it all came together, so when I was done I went back and made this step-by-step guide. It's a bit shorthand.
Many thanks to squid2 for his TWRP port, to the folks who make superuser, to parrotgeek1 for superSUFixer.zip, and to spiked_mistborn for reminding me about it. And, of course, huge thanks to squid2 and Alberto97 for the killer Lineage ROM. It is far better than stock or the last Nougat CM. If I forgot anyone, or made any mistakes here, somebody please point them out. Have fun!
1. Preparation (if the links don't work, search on xdaDevelopers or with Google)
a. Backup entire phone to the extent you are able, either with a dedicated tool and/or to Google via the Android backup feature
b. Download and install Motorola Device Manager on your computer from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 so as to make sure you have the proper drivers
c. Download adb and fastboot tools onto your computer from
http://forum.xda-developers.com/showthread.php?t=2588979 or
http://forum.xda-developers.com/showthread.php?t=2317790d. Download TWRP for Moto G4 Play to same folder as adb and fastboot tools from http://forum.xda-developers.com/devdb/project/?id=16870#downloads
e. Depending upon whether you want to flash Lineage or stay with the stock ROM, download to the same directory on your computer either:
i. Lineage and the Lineage SU addon (if you want root) from https://forum.xda-developers.com/g4-play/development/rom-lineageos-14-1-moto-g4-play-t3544646 and Google apps (arm 7.1 micro) from http://opengapps.org/; or,
ii. superSUFixer.zip from http://forum.xda-developers.com/g4-play/development/automatic-flashable-zip-fix-supersu-t3464396 and superusersu.zip from http://www.supersu.com/download
Note: I did not find superSUFixer.zip necessary when I intially rooted, but after later installing squid's kernel it was indispensable to reinstallation of superusersu.zip.g. Attach phone to computer with USB cable, enable file transfer on phone and either copy the Lineage zip and Lineage SU addon zip and gapps.zip to your phone, OR copy superSUFixer.zip and superusersu.zip to the phone (you don't need to copy twrp)
2. Unlock bootloader
a. Enable developer options (Settings/About Phone/tap Build Number 7x)
b. Enable USB debugging on phone (Settings/Developer Options)
c. Enable OEM unlock on phone (same)
d. Open command window and change to the directory where you put adb, fastboot, and twrp
e. > adb devices (to check that you are connected - you should get a response with a device id)
f. > adb reboot bootloader
g. >fastboot oem get_unlock_data
h. On computer, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a (you need to proceed through the login and to the second page)
i. Copy data returned by phone in the command window (make sure you copy all of it!)
ii. Paste that data into the Data Scrub Tool on the web page
iii. Copy scrubbed data, paste it into the box on the web page at step 6, and click the button; if it says you can't unlock your device, either you didn't copy and paste all the data, or your phone can't be unlocked and you're done; otherwise,i. Copy unlock key from email
j. > fastboot oem unlock <unique unlock key>
3. Flash TWRP
a. > fastboot flash recovery twrp.img
b. > fastboot reboot recovery
4. Flash Lineage and root, or just root -- when the phone has rebooted into recovery (you'll be in TWRP now)
a. follow prompts to make TWRP permanent or not
b. DO A FULL BACKUP OF EVERYTHING with TWRP
c. make sure you performed step b (or you may wish you had later, if something goes wrong!)
d. To flash another ROM, in TWRP
i. Wipe Data, Cache, and Dalvik. (Yes, you have to do this.)
ii. For Lineage - Install the Lineage zip file, the Lineage SU addon zip file, and the gapps zip file, one after the other, in that order, WITHOUT REBOOTING in between. TWRP will let you add all three to its queue to flash in order;
iii. For other ROMs - see instructions for those ROMs, but in general, install the ROM zip file, and then the gapps zip file, one after the other without rebooting in between. For root access, depending on the ROM, you may need superSUFixer, supersu.zip, or both; again, see the instructions for the ROM you are flashing.OR
e. To stick with the stock ROM but get root access, DO NOT WIPE, just flash superSUFixer and then supersu.zip
5. If TWRP does not automatically reboot your phone (if you unchecked the "reboot when done" box), then reboot to the System; if you left the box checked, then your device will reboot by itself once the zip files have been flashed.
6. Follow the prompts to set up your new ROM or stock Android.
7. Reboot into recovery (TWRP) and make another backup!
8. Want to get rid of the "Unlocked Bootloader!" warning screen? Flashing this file from TWRP worked for me (all the others I tried did not work):
https://forum.xda-developers.com/attachment.php?attachmentid=4065906&d=1488923356
For me, and it seems like I'm not the only person facing this issue either, I cannot unlock my boot loader on their website as it says it's not eligible. I do have the unlocked XT1607, bought it at Walmart for $150. I contacted their customer support and they said it can be unlocked and that they'd forward the boot loader string to the dev team and then follow up and email the unlock code, yet it's been almost 24hrs and no response which is saddening.
-Edit-
I did some research quickly, and it does fully quality according to their forums, as my CID value is 0x0032 and they state that devices with that CID are eligible for being unlocked. So they must be updating things in the background in their system
fireball0093 said:
For me, and it seems like I'm not the only person facing this issue either, I cannot unlock my boot loader on their website as it says it's not eligible. I do have the unlocked XT1607, bought it at Walmart for $150. I contacted their customer support and they said it can be unlocked and that they'd forward the boot loader string to the dev team and then follow up and email the unlock code, yet it's been almost 24hrs and no response which is saddening.
-Edit-
I did some research quickly, and it does fully quality according to their forums, as my CID value is 0x0032 and they state that devices with that CID are eligible for being unlocked. So they must be updating things in the background in their system
Click to expand...
Click to collapse
Any word yet on that unlock code?
loociddreemr said:
Any word yet on that unlock code?
Click to expand...
Click to collapse
After talking to their customer support, I never got an email. The next day however I decided to go online to their boot loader page and put my code in, then it worked! The data scrub tool or whatever it may be called that they have I recommend using it too.
where the twrp backups are stored? how do I transfer them to pc? (coz phone's capacity is not enough).
Thanks a ton for the guide
haher2 said:
where the twrp backups are stored? how do I transfer them to pc? (coz phone's capacity is not enough).
Click to expand...
Click to collapse
They are in a subdirectory of the TWRP directory. With the proper drivers installed on your PC you can transfer them via File Explorer. Or, 20 pounds/euros/dollars will get you a 64gb SD card.
3. Flash twrp
a. > fastboot flash recovery twrp.img
b. > fastboot reboot recovery
Click to expand...
Click to collapse
I tried to fastboot boot recovery from the bootoader but it didn't work. I rebooted the phone first and did it with: "adb reboot recovery" in windows.
Overall nice guide, works like a charm, i also flashed the unlocked bootloader warning with a custom logo.bin, no issues here and works like a charm (I flashed it with the stock logo you see when you first bought the phone with a locked bootloader)
Thank you!
Yah fastboot reboot recovery doesn't work. But very nice guide.
While in the main bootloader menu, the Power & Vol+/- buttons are active and you can go straight to recovery (and other modes) using the toggles. Perhaps this should be mentioned in the OP.
It should also be noted that after flashing recovery, one needs to go to recovery straight before rebooting to normal (system) for the TWRP/Custom Recovery to stick.
Also worth noting, Power + Volume Down will boot to bootloader/fastboot and then hardware buttons to navigate to all other modes as needed.
.
loonix said:
Yah fastboot reboot recovery doesn't work. But very nice guide.
While in the main bootloader menu, the Power & Vol+/- buttons are active and you can go straight to recovery (and other modes) using the toggles. Perhaps this should be mentioned in the OP.
It should also be noted that after flashing recovery, one needs to go to recovery straight before rebooting to normal (system) for the TWRP/Custom Recovery to stick.
Also worth noting, Power + Volume Down will boot to bootloader/fastboot and then hardware buttons to navigate to all other modes as needed.
.
Click to expand...
Click to collapse
Yes and, adding to what you said, you need to re-enable the "Allow bootloader unlocking" and "USB Debugging" in Developer Settings if you failed to flash your recovery as the device expects to be flashed. Else, you'll get a "unable to load kernel" error in the bootloader log and being rebooted again to the bootloader menu.
Great tutorial indeed, thanks a lot. Nandroid backup doesn't worked for me but i'm going on.
Edit - worked after disable sd as internal memory
I found the stock firmware for my phone here :
https://mirrors.lolinet.com/firmware/moto/harpia/official/
Is it possible to relock and revert the phone to stock after flashing twrp/Lineage/Root ?
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-relock-bootloader-t3410399
does it work with g4 play ?
I want to throw something out there, because it happened to me. In newer builds of Windows 10, you are no longer able to open a command window in a folder (the only available option is Powershell). I even tried that Path thing some Android tutorials talked about, and it failed. When I went to flash TWRP, I had to put twrp.img in my User folder directly (I only figured this out because when I did t-tab it fetched the .thumbnails folder). Make sure you know what CMD is referencing BEFORE you start the process, because doing so will save you a lot of headache down the road.
hamelg said:
I found the stock firmware for my phone here :
https://mirrors.lolinet.com/firmware/moto/harpia/official/
Is it possible to relock and revert the phone to stock after flashing twrp/Lineage/Root ?
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-relock-bootloader-t3410399
does it work with g4 play ?
Click to expand...
Click to collapse
In concept, I don't see any reason why you couldn't use TWRP to flash the stock ROM and then fastboot to flash the stock recovery ... or fastboot to flash both (be easier and quicker). The Moto website may have instructions for re-locking.
mkollersms said:
I want to throw something out there, because it happened to me. In newer builds of Windows 10, you are no longer able to open a command window in a folder (the only available option is Powershell). I even tried that Path thing some Android tutorials talked about, and it failed. When I went to flash TWRP, I had to put twrp.img in my User folder directly (I only figured this out because when I did t-tab it fetched the .thumbnails folder). Make sure you know what CMD is referencing BEFORE you start the process, because doing so will save you a lot of headache down the road.
Click to expand...
Click to collapse
In a command window use the cd command to change directories. For example:
C:> CD \mytopdirectory\mysubdirectory
Another link to consider about OTA update if you stick with the stock ROM :
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-sucsessfull-ota-update-rooting-t3472658
Thanks again.
If your phone is from Verizon Prepaid, Moto will say the device is not eligible to be unlocked. Knowing Verizon, it's not likely to be unlocked later along down the line either. Hopefully someone comes up with a good way to bypass this restriction and install some ROMs.
Does this method work on the Verizon prepaid model, or does it have to be from moto/amazon?
Moto g play twrp IMG file not IMG it's **** IMG file please develop it
Does this works with LATAM version? XT1601?
Thanks :good:
Hey everyone, I've been lurking around this forum for years. Thought it might be the right time to contribute now... (wanted to post in Venue Android Development, but my low post count prevented me from doing so. Maybe a mod could move the thread to the correct location...)
Please be gentle…
I managed to root the Dell Venue 7040 on Android 5.1 (EPP101A173600DEL)
Disclaimer
Fist the mandatory disclaimer: I cannot be held responsible for any harm done to your device or anything else. Not guarantee, warranty void etc., etc.... DO THIS AT YOUR OWN RISK!!!
Basic idea
Using a legacy 5.0.1 fastboot kernel from the Dell Venue 7840 will allow to launch tethered temporary custom recovery session by social-design-concepts
The old bootloader will be flashed to the recovery partition (this will cause you to lose the stock recovery! You can however always use the temporary recovery session). The old fastboot bootloader can then be launched as recovery and perform the rooting process)
Perquisites:
1) Intel Android drivers
Description: Drivers needed for ADB and Fastboot interaction.
Download: https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
2) Intel Fastboot Tethered Temporary Recovery Session
Description: Utility to launch a temporary custom recovery session
Download: IntelAndroid-FBRL-07-24-2015.7z (https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096)
3) Bootloader “droidboot.img” from the archive “Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397.zip”
Description: Outdated bootloader of the Venue 7840 (Android 5.0.1). This file is needed in order to fire up the temporary recovery session (see [file 2])
And yes, I am well aware that I posted the files for the 7840 (NOT 7040 !!!). We will get the file working anyways.
a) Download: http://opensource.dell.com/releases...s_rd_opensource-blankphone-userdebug-1397.zip
b) Extract droidboot.img (NOT droidboot_dnx.img) from archive.
4.) Fastboot (facultative)
Description: Tool to establish a communication between the PC and the tablet’s bootloader
Download: https://forum.xda-developers.com/showthread.php?p=42407269#post42407269)
Note: If you intend only to root you may use the fastboot.exe that comes with the temporary recovery session [file 2]
5.) Chainfire’s SuperSU
Description: Actual super user file – the file you want to install to obtain root access.
a) Download: https://download.chainfire.eu/696/supersu/
b) Copy this file onto an external SD card and put the card inside the tablet.
Rooting:
1. Become a developer by tapping five times on the build # in the android settings (on the tablet).
2. Fire up the developer’s options in settings.
3. Enable OEM unlocking.
4. Connect your tablet with your PC (USB cable required).
5. Reboot to bootloader.
6. Open a terminal on the Windows PC (cmd.exe) and use fastboot.
WARNING: THIS WILL ERASE ALL USER DATA ON THE TABLET (so make sure you have got a backup)
fastboot oem unlock
7. Now it’s time to say good bye to your stock recovery and flash the new one [file 3]
You cannot recovery the recovery (no pun intended ) Actually now you can, see step 13
WARNING: DO NOT FLASH AS BOOT OR FASTBOOT IMAGE. OTHERWISE THE SYSTEM WILL NOT BE ABLE TO BOOT.
fastboot flash recovery droidboot.img
8. Boot recovery kernel (this will instead bring up the 5.0.1 bootloader which will enable us to launch FBRL in the next step).
Use the volume rockers to select "RECOVERY MODE", then press the power button.
The old bootloader will launch (you will see a blue line of text indicating you successfully launched the 5.0.1 bootloader)
9. Launch launcher.bat from [file 12] on your Windows PC
launch.bat
10. A turquoise menu shows up. Choose “ACCEPT”; 5 (CWM); T4 (not T1, T2 or T3, but T4)
The bootloader will receive the necessary files and launch CWM after a while (may take two minutes).
11. Choose
a) install zip
b) choose zip from external sd card
c) choose the SuperSu file you copied to the sd card.
d) Confirm you want to install.
This may take a moment. Reboot without fixing any root (as suggested by CWM).
12. Your Dell Venue 10 7040 is now rooted.
13. You may now restore the stock recovery. Download the stock recovery (attached). Unzip the file. Then:
fastboot flash recovery 7040_510_stock_recovery.img
14. In case you want to relock the bootloader (this will prevent the annoying message when booting)
fastboot oem lock
(This will again wipe all your personal data from the device)
Note: If you relock the bootloader you will not be able to boot into recovery!
15. Finished.
Hope you enjoy!
Credits and Thanks to social-design-concepts and johnsag49 and of course Chainfire and many others.
thanks fcipaq
but my 7040 is lost
microbai said:
thanks fcipaq
but my 7040 is lost
Click to expand...
Click to collapse
Sorry to hear that. Do you mean lost like lost or bricked?
Ok so long story short, my Venue 10 7040 thinks it's a Venue 8 7840, because I had to restore the entire OS including all the partitions, and of course there are only stock images for the 7840 online, and literally nothing for the 7040. So now my 7040 is running again, but because it thinks it's a 7840, there's a lot of weirdness, most significantly, the touchscreen doesn't work... at all. And, rotating the device to landscape or portrait rotates the screen in the opposite direction.
So, the ONLY stock image of anything 7040 related I could find is this stock recovery image posted here, but is there ANYONE out there that owns a Venue 7040 and is reading this??? If so, could you back up all of your 7040's partitions and upload them somewhere? I'm so desperate here, and because Dell completely abandoned these tablets, there's not a single stock image of anything anywhere, besides the open source thing, which I've spent the last 10 hours attempting to flash in various configurations. Please, anyone, could you back up your partitions (system, factory, boot, fastboot, and DNX and IFWI if possible), and upload them somewhere???
Well... I do have a TWRP backup of the system partition. However it is a quite huge amount of data (2 GB). I'll try to upload soon. Recovery and droidboot a virtually the same as 7840. So is the kernel (boot.img)...
Best reagrds
fcipaq said:
Well... I do have a TWRP backup of the system partition. However it is a quite huge amount of data (2 GB). I'll try to upload soon. Recovery and droidboot a virtually the same as 7840. So is the kernel (boot.img)...
Best reagrds
Click to expand...
Click to collapse
Awesome, thank you! Idk how it's messed up so horribly, in terms of the touchscreen not working, it must be because of the different screen sizes between the two devices...
Also, do you think you could upload the default.prop file, and the files inside of the /config folder? There's one specific file in there that sets the panel width and height in millimeters.
Hey, here is what you could do:
1. Get the device in a clean stat
a) Download intel paltform tool
b) Download eaglespeak_qs_opensource_blankphone-userdebug-503034.zip and flash factory erase using platform tool. This way you will get a clean lollipop partition table.
WARNING: Backup your FACTORY partition first (e.g. using tehtered TWRP)
2. Get into tethered recovery
Hint: Getting into TWRP is a little tricky as the starter is buggy. Try more than once.
3. Flash the backup file (PM). You still need to replace the XXXXXXX directory name with you serial # (it is displayed on the bootloader screen).
Chances are good you damaged/deleted your FACTORY partition. In that case your camera calibration data was destroyed. That means you can no longer take "Depth shots" as this requires a proper calibration. Taking "normal" picutres however works fine...
fcipaq said:
Hey, here is what you could do:
1. Get the device in a clean stat
a) Download intel paltform tool
b) Download eaglespeak_qs_opensource_blankphone-userdebug-503034.zip and flash factory erase using platform tool. This way you will get a clean lollipop partition table.
WARNING: Backup your FACTORY partition first (e.g. using tehtered TWRP)
2. Get into tethered recovery
Hint: Getting into TWRP is a little tricky as the starter is buggy. Try more than once.
3. Flash the backup file (PM). You still need to replace the XXXXXXX directory name with you serial # (it is displayed on the bootloader screen).
Chances are good you damaged/deleted your FACTORY partition. In that case your camera calibration data was destroyed. That means you can no longer take "Depth shots" as this requires a proper calibration. Taking "normal" picutres however works fine...
Click to expand...
Click to collapse
I'll try this right now, thanks for the info. I'd still really love to have that TWRP backup though, if you don't mind uploading it somewhere!
PS: Build properties are contained in flash-EraseFactory.xml... No need to set the resolution anywhere as the driver will detect it.
I PMed the link
nil
Were you able to unbrick your tablet?
fcipaq said:
I PMed the link
Click to expand...
Click to collapse
can you PM me too？ thanks
I can do that. Do you only need the system partition?
fcipaq said:
Hey, here is what you could do:
1. Get the device in a clean stat
a) Download intel paltform tool
b) Download eaglespeak_qs_opensource_blankphone-userdebug-503034.zip and flash factory erase using platform tool. This way you will get a clean lollipop partition table.
WARNING: Backup your FACTORY partition first (e.g. using tehtered TWRP)
2. Get into tethered recovery
Hint: Getting into TWRP is a little tricky as the starter is buggy. Try more than once.
3. Flash the backup file (PM). You still need to replace the XXXXXXX directory name with you serial # (it is displayed on the bootloader screen).
Chances are good you damaged/deleted your FACTORY partition. In that case your camera calibration data was destroyed. That means you can no longer take "Depth shots" as this requires a proper calibration. Taking "normal" picutres however works fine...
Click to expand...
Click to collapse
Im having the same issue that ShotSkydiver did. I followed these instructions but im stuck at flashing factory reset I get this error from the platform tool:
"08/10/17 12:08:48.734 ERROR : [Port 1/2] Command `"C:\Program Files (x86)\Intel\Platform Flash Tool Lite\xfstkFlashTool.exe" "-1" "C:\Users\user\Downloads\eaglespeak_qs_opensource_blankphone-userdebug-503034\dnx_fwr_eaglespeak_qs.bin" "C:\Users\user\Downloads\eaglespeak_qs_opensource_blankphone-userdebug-503034\ifwi_eaglespeak_qs.bin" "" "C:\Users\user\Downloads\eaglespeak_qs_opensource_blankphone-userdebug-503034\droidboot_dnx.img" "0x80000c27" "none" "none" "0"` failed
08/10/17 12:08:48.734 ERROR : [Port 1/2] Flash failed (Command type: Ifwi)"
Any idea what the problem is?
---------- Post added at 05:32 PM ---------- Previous post was at 05:16 PM ----------
arabham said:
Im having the same issue that ShotSkydiver did. I followed these instructions but im stuck at flashing factory reset I get this error from the platform tool:
"08/10/17 12:08:48.734 ERROR : [Port 1/2] Command `"C:\Program Files (x86)\Intel\Platform Flash Tool Lite\xfstkFlashTool.exe" "-1" "C:\Users\user\Downloads\eaglespeak_qs_opensource_blankphone-userdebug-503034\dnx_fwr_eaglespeak_qs.bin" "C:\Users\user\Downloads\eaglespeak_qs_opensource_blankphone-userdebug-503034\ifwi_eaglespeak_qs.bin" "" "C:\Users\user\Downloads\eaglespeak_qs_opensource_blankphone-userdebug-503034\droidboot_dnx.img" "0x80000c27" "none" "none" "0"` failed
08/10/17 12:08:48.734 ERROR : [Port 1/2] Flash failed (Command type: Ifwi)"
Any idea what the problem is?
Click to expand...
Click to collapse
Figured it out. It turned out there was a driver signature issue. I just disabled the driver signature checking in windows to fix it.
---------- Post added at 06:11 PM ---------- Previous post was at 05:32 PM ----------
Can I get the backup file?
Sorry for bumping up this thread. My Dell 7040's running 5.0.2 rooted. How can I go back to clean state and update to 5.1? (then I'll root 5.1 to avoid annoying messages). Thanks!
thanks!
Do you have the rom of venue 10 7040?
please send me your device's backup.
fcipaq said:
I PMed the link
Click to expand...
Click to collapse
can you PM me too？ thanks
I am very sorry that I cannot provide the files you are looking for. I no longer do not possess these files in a clean state so that they would be useful for you. I am sorry! (Have been tinkering too much myself)
It is really a pity the files cannot be downloaded from Dell. I have been looking all over the internet myself to find a set of files providing the ability to return the device into a clean state.
This guide is outdated now. Please refer to the thread OPs of the respective projects.
Hi all, I am starting this thread with the very reason to educate and help newbies as well serve as a resource guide that could be used by all. I will try my best to update this thread often. You can ask any question regarding Moto Z2 Play aka albus here. Our XDA Community will try to help you. Make sure you always read before posting the same queries. If you're stuck in a problem, make sure you provide us with as much as information of what you were exactly doing and what happened along with your device details ofcourse.
Also remember that unlocking the bootloader will void your warranty. Relocking it won't give you back your warranty. If you are visiting a service center for repairs of any kind, they will come to know that you have unlocked your bootloader (you put a code on their site lol). But yea you can try your luck by visiting them after you lock your bootloader using the fastboot firmware.
No one, but you are responsible for whatever you do to your device. If something happens due to your ignorance or lack of backups or knowledge, only you are responsible, not the developer, not the XDA Community. Just read the respective posts, search (at XDA and at Google) before posting and you might probably find answers. Cheers.
Setting up adb/fastboot on your system:
These drivers are quite essential for every android user.
How to use?
Windows:
Minimal Fastboot/ADB: https://www.androidfilehost.com/?fid=745425885120698566
Just install the setup. Reboot your phone in bootloader mode (Power off and then press and hold power + vol down simultaneously) and connect via USB cable. On your computer, navigate to the directory where you installed them. Press shift+right click and choose Open Command Window / Powershell here. Type:
Code:
fastboot devices
If you get a serial number, fastboot is working.
For adb to work enable Developer Options and turn on USB Debugging on your device. Open Settings app on your device and go to About Phone section. Next, tap 7 times on Build Number and get the Developer Options enabled.
Now authorize USB Debugging by allowing it (Choose something like Always trust)
Type this on your command window / powershell window:
Code:
adb devices
Again it should return a serial number.
If both these fail, you might consider rebooting your computer or even installing (MDM) motorola device manager. Make sure you don't have any crappy or outdated drivers. (Always keep your system upto date ) Anything else, you'll have to google up things.
Motorola Device Manager:
For more info regarding adb/fastboot open this: https://developer.android.com/studio/command-line/adb.html
Linux users might need to install it from their respective package manager repos, Ubuntu for example:
Code:
sudo apt install android-tools-adb && sudo apt install android-tools-fastboot
Arch Linux on the other hand:
Code:
yaourt -S android-tools --noconfirm
Similarly for the other distros.
Commands are the same. fastboot needs to be used with sudo.
Unlocking the bootloader:
Unlocking Bootloader
>>> Unlocking Bootloader will overwrite any data stored on your device, backup your files before proceeding <<<
Unlocking Bootloader:
1- Register
Head to Motorola website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b and register your E-Mail ID.
Open Settings app on your device and go to About Phone section. Next, tap 7 times on Build Number and get the Developer Options enabled.
Head back to Main Settings Menu and go to Developer Options and switch the 'Allow OEM Unlock' option.
2- Getting Unique ID for each device
Reboot to Bootloader/fastboot mode (power off the device, then press the power and volume down buttons simultaneously).
On your computer, go to the directory where you installed the adb/fastboot drivers (or make sure this folder is in your $PATH to acess fastboot and adb system wide).
Open CMD/Powershell/bash in here. (Windows users might need to Shift+Right Click and choose "Open Command/Powershell Window here" , Linux users can open terminal as per their respective distro. Now , type
Code:
Code:
fastboot oem get_unlock_data
You will get something like this:
On a Windows Desktop, the returned string format would be:
Code:
(bootloader) 0240540162024205#4C4D3556313230
(bootloader) 30373as313630330df332323239#BD00
(bootloader) 8A672BA4746C2CE0a328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
On a Mac OS Desktop, the returned string format would be
Code:
Code:
INFO0A40040192024205#4C4D3556313230
INFO30373731363031303332323239#BD00
INFO8A672BA4746C2CE02328A2AC0C39F95
INFO1A3E5#1F53280002000000000000000
INFO0000000
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this:
Code:
0240540162024205#4C4D355631323030373as313630330df332323239#BD008A672BA4746C2CE0a328A2AC0C39F951A3E5#1F532800020000000000000000000000
3- Unlocking the device:
Check if your device can be unlocked by pasting this string in the specific field on the Motorola website, and clicking “Can my device be unlocked?”
NOTE: If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of that page. Click on it and wait for the unique code to be sent to your mail.
After you got the code type the following :
Code:
fastboot oem unlock your_code
and wait your device to reboot !
Flashing TWRP Recovery:
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda.
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to format data once via twrp wipe options and reboot back to twrp for functioning of /data
Downloads : http://www.androiddevs.net/downloads/
Keep the twrp recovery file (.img extension) in the adb/fastboot folder
Reboot to bootloader, open cmd/bash and type:
Code:
fastboot flash recovery filename.img
(if you want permanent flash) or
Code:
fastboot boot filename.img
(if you want temporary
boot)
Now you must flash the verity disabler zip.
HIGHLY RECOMMENDED:
After the twrp is done and you have successfully rebooted to system, it is a good time to reboot to TWRP again and backup your phone. (System and Boot most necessary)
Flashing Stock ROM:
Will be updated as soon as the fastboot version of the stock ROM is available.
Unbricking your hard bricked/dead device:
Connect your device via the usb cable, extract this zip file to the adb/fastboot folder and then run:
blankflash.bat file if on windows; the .sh file if on linux.
Once this is completed, you must flash the full stock firmware via fastboot. This is MANDATORY.
Blankflash zip: http://cloud.vache-android.com/Moto/albus/blankflash/blankflash.zip
Reserved
please forgive the ignorance, but is this device fully unlockable in the same fashion that Nexus devices are, similar method if i'm reading this correctly? Im very used to unlockable bootloaders on VZW
OneArm said:
please forgive the ignorance, but is this device fully unlockable in the same fashion that Nexus devices are, similar method if i'm reading this correctly? Im very used to unlockable bootloaders on VZW
Click to expand...
Click to collapse
Yeah, I am not sure what is going on this time around with the VZW variant. Since the Droid Z was bootloader locked and the unlocked Z wasn't (but not VZW compatible) I am almost expecting the same here, but I keep being told that the unlocked version of the Z2 will work on Verizon so maybe they just don't care anymore. I mean, the unlocked Nexus 6 and VZW Nexus 6 were pretty much the same phone too, and both were bootloader unlockable.
The only thing that gives me pause from going out now and getting the VZW version vs the unlocked model (whenever its slated to come out) is that Motorola's Bootloader Unlock page doesn't have it listed (yet). Either it can be and they are behind on updating the list, or it can't... at which point the unlocked one will be listed with a (Except VZW Model) like the other phones have. But... if either version works on VZW... what's the point of making one unlockable and the other not? Seems like a waste of time.... of course VZW's past decisions on phones don't make sense in some aspects.
All I know is... I want one of these if they are unlocked. Once the keyboard mod is released I will be back to the nerdy bliss that is a sliding keyboard and making this phone the spiritual successor to the Droid 4.
After flash twrp when rebooting the mobile system, stopped in screen of bootloader unlocked .... how to proceed help me: /
---------- Post added at 06:05 PM ---------- Previous post was at 05:46 PM ----------
After installing TWRP it asked for the encryption password so I put it and it opened normal I went to restart> system, then appeared option to install the application twrp, I slipped it to be installed, then went on reboot> system and stopped on the screen Of bootloader unlocked .. help me: |
m.lucas said:
After flash twrp when rebooting the mobile system, stopped in screen of bootloader unlocked .... how to proceed help me: /
Click to expand...
Click to collapse
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
yunzo said:
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
Click to expand...
Click to collapse
how should I proceed? My device has no ROM only TWRP installed. :s
m.lucas said:
how should I proceed? My device has no ROM only TWRP installed. :s
Click to expand...
Click to collapse
Start TWRP, and you can transfer zip file from PC by using "adb push"
"adb sideload" may work too.
yunzo said:
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
Click to expand...
Click to collapse
Don't use SuperSU.
Use Magisk-v13.0(54e6a79)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Junior Passos said:
Don't use SuperSU.
Use Magisk-v13.0(54e6a79)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Click to expand...
Click to collapse
Thank you for information.
I have just tried Magisk, but failed with error message as below.
Code:
mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v13.0(54e6a79).zip'
It is same for latest version (c4377ed).
yunzo said:
Thank you for information.
I have just tried Magisk, but failed with error message as below.
Code:
mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v13.0(54e6a79).zip'
It is same for latest version (c4377ed).
Click to expand...
Click to collapse
Latest version don't work.
I use Magisk-v13.0(54e6a79) on my Moto Z2 Play.
Z2 Play stock ROM needed.
Anyone help to search complete stock Noughat Rom, for the Z2 Play (Indian retail unit model no XT 1710-10), I did not find yet. Please help will be highly appreciated.
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
tywinlannister7 said:
Reserved
Click to expand...
Click to collapse
Z2 Play stock ROM needed.
Anyone help to search complete stock Noughat Rom, for the Z2 Play (Indian retail unit model no XT 1710-10), I did not find yet. Please help will be highly appreciated.
@niteshpant kindly edit your post and remove the reserved post from the quote.
Moreover, the links will be added here as soon as the firmware is available.
Junior Passos said:
Latest version don't work.
I use Magisk-v13.0(54e6a79) on my Moto Z2 Play.
Click to expand...
Click to collapse
As I wrote before, I have failed both of 54e6a79 and latest.
Error message on TWRP is same.
Have you met this message but rooted successfully after boot?
Today I tried system-mode SuperSU, and met boot failure which continues to show Motorola/lenovo logo.
It is different from dm-Verity failure (which shows unlock warning).
Stuck in TWRP, Help
I have successfully flashed the TWRP but now it is looping at TWRP and when try to do factory reset, in just seconds it is boot again and shows TWRP main screen again, moreover storage shows about 50000 mb in internal memory, secondly my memory card is not accessible, selection is not working only shows internal memory. As I think at this stage my bootloader(stock) is fine, original stock recovery is replaced by the TWRP 3110 . My factory Android rom is still there in my phone because twrp inernal memory option shows about 50000 mb space captured in internal storage. I have clear delvik and cache but all fails, how I can get the OS by the TWRP. I assume if my old OS has been erased then twrp should have give the "no OS install" massage but this is not happening in my case. Any help...... I am not doing something more due to complete device failure in this stage mainthing is this no factory rom image is available yet, very annoying issue.... regards
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
nea102 said:
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
Click to expand...
Click to collapse
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
I had used that guide, was following that when I was getting the out of space errors.
However, I got it all sorted in the end - I just downloaded a different (older) version of the firmware and that worked.
Help for you
samlis said:
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
Click to expand...
Click to collapse
Hi good day.
I have been following your work from another page, and now in XDA.
I had not read your message, and, I changed the recovery for the stock, and, I was an idiot to close the bootloader.
What happened? Brick simple on my cell phone, did not come out (because I fixed it) of the image of erecovery (EMUI) without tabs or options, a rather rare image.
How do I solve it:
1. I did not enter fastboot, I did not correctly enter the stock recovery (I had deleted the twrp), I had closed the bootloader (my stupidity)
2. Be patient and wait for the battery to run out (wait a day for it).
3. Open cmd and place the command to open the bootloader (fastboot oem unlock) and execute.
4. Put the device in fastboot mode when connecting to the laptop (I did not work several times, the fastboot came out with error FUNC No 10 and NO 2), after numerous attempts and not to let it charge the battery too much (because it was restarted and towards brick in the EMUI logo), correctly enter the fastboot and unlock, when you enter step 3 automatically, it will be executed. I had an advance in removing the cell phone from the brick.
5. It reboots and wonderfully happened to the Rom (that had previously installed), that is to say, the erase was not executed when the bootloader had previously closed.
6. As I had little energy, it was turned off, but I connected it and entered charging mode without restarting (before I did it).
7. Wait for a load of at least 5%, and install the Catuva21 TWRP from the tutorial.
8. I put it by command to restart in fastboot, but I generate error (Error Func No 10 and No 2).
9. I turn off the cell phone and with volume up and power key
10. Enter the TWRP correctly, verify that it is installed.
11. Restart system and log in to the system. I had not deleted anything, but to avoid problems, I hope to load 55% and execute the steps to install the rom.
12. Enjoy and dry spilled tears.
Experience lived and I hope you do not do something that developers do not advise.
Grcias and happy day.
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
heindrix said:
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
Click to expand...
Click to collapse
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
yoni sofer said:
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
Click to expand...
Click to collapse
take a look here, mate.
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904