{
"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"
}
NOTE: You need to be bootloader unlocked in order to flash a factory image!
Download the Lollipop Factory Image from here
https://dl.google.com/dl/android/aosp/hammerhead-lrx21o-factory-01315e08.tgz
Save the factory image to your desktop (easiest to find).
Extract the file using WinRAR, 7zip, Winzip or whatever you prefer for extracting files.
Boot your N5 into the bootloader. (Power off then press and hold Volume Down and Power Button)
Connect your phone to your PC.
Inside the folder of the factory image, double click the "flash-all.bat" NOTE: THIS WILL WIPE DATA AND INTERNAL STORAGE!!!
Wait for the command prompt to prompt you to "click any key to exit." Meaning it's finished.
First boot may take up to 10 minutes.
Download Chainfire's AutoRoot from here:
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Extract zip to desktop
Ensure that you are in the bootloader and connect your phone to your PC.
Open the Auto Root folder and double click the "Root-Windows.bat" and let it run.
Phone will reboot with root, and will have SuperSU installed.
(For these steps, you must have Java installed)
Boot phone into the bootloader and connect phone to PC.
Download the adb files you need here:
http://dottech.org/downloads/adb_fastboot_and_other_tools.zip?68a68a
Extract the zip to your desktop
Download your recovery of choice. I suggest TWRP which can be found here:
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.1.0-hammerhead.img
Rename the recovery image to "recovery.img" and place it in the adb_fastboot_and_other_tools\adb_fastboot_and_other_tools\Android folder you just extracted.
Right click that folder and select "Open command prompt here"
In the command prompt, type the following
Code:
fastboot flash recovery recovery.img
Hit enter and let it flash recovery. You are now rooted and have TWRP installed, on Lollipop!
Note: This guide may seem a little lengthy and redundant but I posted it for a reason. This guide is broken down "barney style" for everyone out there that wants to know the EXACT steps to installing Lollipop, rerooting and reflashing recovery. This may not be the easiest or fastest method to do any of this, but it's the way I do it and it's pretty fast. If you have any questions, please post them below and I will do my best to answer them all in a timely manner. Thanks and enjoy Lollipop!!
If you do not have the Nexus 5 drivers installed, please follow the first 7 steps found here: http://www.technobuzz.net/install-nexus-5-driver-adb-fastboot-unlock-bootloader/
If I helped you out, please click the "Thanks" button to show your appreciation.
Another part of the reason for this guide is to get people more familiar with adb commands and doing things the "old school" way. Not that there is anything with toolkits and one click methods, I just don't prefer them.
How does this differ from the sticky threads that have been up since forever?
RoyJ said:
How does this differ from the sticky threads that have been up since forever?
Click to expand...
Click to collapse
Honestly I find most of the "sticky threads" here to be jumbled with information and may either be confusing or intimidating to newer users. This guide is broken down easier. As opposed to saying "download this zip to root." I tell them what to do with the zip as well. I clearly stated why I made a different thread at the end of this guide. I will also be a lot more active in my thread than most people are in their guides. The only way I will not respond to a question is if I physically cannot respond or I am in class.
thank you SO MUCH for this!
sookieball said:
thank you SO MUCH for this!
Click to expand...
Click to collapse
Very welcome!
I get this when running flash-all.bat
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1005154516 bytes
error: update package missing system.img
Press any key to exit...
After which I get the red triangle when attempting to boot to recovery, and and endless boot if I try to normal boot.
I've downloaded multiple times and multiple machines and nothing seems to work for me.
Good job and thanks for the very detailed explanations!
Pyronaught said:
I get this when running flash-all.bat
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1005154516 bytes
error: update package missing system.img
Press any key to exit...
After which I get the red triangle when attempting to boot to recovery, and and endless boot if I try to normal boot.
I've downloaded multiple times and multiple machines and nothing seems to work for me.
Click to expand...
Click to collapse
When you extract the factory image file, what all files show up in that folder?
mikka06 said:
Good job and thanks for the very detailed explanations!
Click to expand...
Click to collapse
You're very welcome!
Pyronaught said:
I get this when running flash-all.bat
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1005154516 bytes
error: update package missing system.img
Press any key to exit...
After which I get the red triangle when attempting to boot to recovery, and and endless boot if I try to normal boot.
I've downloaded multiple times and multiple machines and nothing seems to work for me.
Click to expand...
Click to collapse
You need to flash the files manually. Follow these steps:
Found these steps here: http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
Pyronaught said:
I get this when running flash-all.bat
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1005154516 bytes
error: update package missing system.img
Press any key to exit...
After which I get the red triangle when attempting to boot to recovery, and and endless boot if I try to normal boot.
I've downloaded multiple times and multiple machines and nothing seems to work for me.
Click to expand...
Click to collapse
I ran into the same problem. You'll need to extract the img files from the embedded update zip file and flash them separately. The instructions that I followed are in the following link:
http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
The bootloader and radio flashed fine before the error, so I followed the steps after that.
Well I'll be.
I actually followed these steps before, but it didn't change anything. So this time I decided to flash 4.4 cleanly back to it and try this process and it finally took.
Thanks for the help, and Android Police for having an article on this only a few hours after it was released.
So I got the "not enough memory" thing while updating to lollipop, but when I rebooted my phone, it seemed like lollipop installed just fine. Should I reflash the update?
punkmetalska said:
So I got the "not enough memory" thing while updating to lollipop, but when I rebooted my phone, it seemed like lollipop installed just fine. Should I reflash the update?
Click to expand...
Click to collapse
I would suggest the same thing and just flash all the images separate. Since your phone seems fine though, I would just leave it be. Did you check the baseband and everything to make sure all the images flashed right? Check your storage too if you have the 32gb version.
Sent from my Nexus 5 using Tapatalk
spc_hicks09 said:
I would suggest the same thing and just flash all the images separate. Since your phone seems fine though, I would just leave it be. Did you check the baseband and everything to make sure all the images flashed right? Check your storage too if you have the 32gb version.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have the 32gb version and mine ended up with only 12.55 gb. How can I fix this? Should I just reflash?
[EDIT] did a quick look around. Seems like doing a factory reset should make it ok. I'll report back after that's done
[EDIT again] factory reset worked!
spc_hicks09 said:
I would suggest the same thing and just flash all the images separate. Since your phone seems fine though, I would just leave it be. Did you check the baseband and everything to make sure all the images flashed right? Check your storage too if you have the 32gb version.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My baseband version is M8974A-2.0.50.2.21. Dunno if that's correct or not. My storage is fine, since I have the 16GB version, and I have 12.55GB available.
punkmetalska said:
My baseband version is M8974A-2.0.50.2.21. Dunno if that's correct or not. My storage is fine, since I have the 16GB version, and I have 12.55GB available.
Click to expand...
Click to collapse
Sounds like you're good then. I wouldn't worry about it unless you start having issues. Then I would just manually flash the files.
Sent from my Nexus 5 running stock Lollipop, using Tapatalk.
spc_hicks09 said:
Sounds like you're good then. I wouldn't worry about it unless you start having issues. Then I would just manually flash the files.
Sent from my Nexus 5 running stock Lollipop, using Tapatalk.
Click to expand...
Click to collapse
Awesome, I'm definitely relieved. Thanks so much!
I can't download cf-root file
Can anyone upload other host like mediafire?
Sent from NEXUS5
And if I don't want to wipe data?
What are the ramifications of editing the flash-all.bat (which I assume is like previous ones) and remove the "fastboot -w flash userdata userdata.img" or something similar. That's how I've always updated, I really don't want to blow away my whole phone just to upgrade the ROM. I either take that out of the .bat or just run the individual fastboot commands myself. I'd like to keep my things as they are. Would that be any different from wiping it and going back and restoring with TiBu? Seems like it would be quicker to dirty flash...but nobody is talking about it.
Related
[Resource/DevTools] TheCollectiveHelpPackageSCH-i800[everything you need & some]72813
{
"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"
}
TheCollective SCH-i800 Help package
http://wiki.cyanogenmod.org/w/P1c_Info
---------------------------------------------------------------------------------------------------------------------------------------------
TheCollective is Proud to present to you StockRooted-sch-i800 Verzion Galaxy Tab
For what ever reason we all need to get back to the default factory state.
soft brick
resale
loss of stablity
to name a few.
Here are the steps you will need to take.
First let's point out that this package contains EVERYTHING YOU NEED for this Except the windows PC to which it will be used on.
Before we begin Install Samsung usb device drivers located in the package.
**\tools-resources\drivers
Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
next is unpacking Hemdall 1.3.2 (The only one that worked for me on my SCH-i800)
**\tools-resources\Heimdall\
heimdall-suite-1.3.2-win32.zip
But here is a link to the developers page so you can download the original/newer if you want.
http://www.glassechidna.com.au/products/heimdall/
You will also need *Microsoft C++ 2012 32bit [if 2013 32/64bit has already been installed you will need to remove it first to install 2012]
This needs installed on your machine because it has .dll files Heimdall uses.
**\tools-resources\MicrosoftC++12\
vcredist_x86.exe
Now you will need to install the drivers this is also needed for Heimdall.
unzip heimdall and go into the drivers folder where you will see /zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device (or whatever it says, eg genirc serial device) (tho NOT massStorageDevice)
[good idea to remove any other usb devices as they can and sometimse do interfere with the packet data sending/receiving]
Click the button "replace driver" and let heimdall download/install the drivers. {libusb0 is the one that worked for me, but try another if it dont for you, there are three}
Run Heimdall-Frontend.exe as admin
Files provided To Flash Your Tab with
**\TheCollective-StockRooted-sch-i800.tar.gz >--TheStockRooted 2.3.5 that came on your tab.
**\tools-resources\HumberOS\heimdall-uses
boot.img >-- a CM10.1 kernel with TWRP for sch-i800
recovery.bin >-- CM10.1 twrp for sch-i800
if you need the pit file --> my-sch-i800.pit [extract it from the stock tar gz]
Ok, Let's get to flashing over the files and getting your tab back to normal.
1: Connect your tab to your PC
2: Launch your tab into download as it is already connected to your PC.*(Do this by holding the volume down and pushing the power button)
3: Go in to the folder "Heimdall" and start " heimdall-frontend.exe" as ADMIN
4: Set up the file you are about to LoadPackage tab. [It should look something like image.]
5: After you have the file in place click load, it will change tab to flash with files listed, simply click start to flash.
ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems.
Tab should boot. [if not factory data reset in recovery e3 and reboot]
Click to expand...
Click to collapse
After this is should be just like you took it out of the box, and already rooted.
Hope this helps!
---------------------------------------------------------------------------------------------------------------------------------------
If you wish to unroot I've included SuperOneClick shortfuse.
just hit unroot
If you wish to install CM or other AOSP rom here is some helpfull info.
Heimdall command line
Flash boot.img with heimdall command line like this:
Press Power + VolDown untill you get the Download screen or PC <–> Tab screen.
on PC open CMD prompt in the folder of Heimdall and place boot image in same folder
type this command string:
Code:
heimdall flash --kernel boot.img --recovery boot.img
Or just replace boot.img inside the ROM ZIP with your desired kernel.
*TIPS
In case you get any strange symptoms.
Flash full TheCollective-StockRooted-sch-i800.tar.gz (with repartition) via Heimdall.
Flash the Kernel included in the package using the heimdall command above.
Boot directly into CwM Recovery, holding Power + VolUp.
Flash CM10.1 ROM, if it reboots by itself repeat the step above.
If you want Google’s stuff, flash latest GApps for Android 4.2.2.
Only Reboot after everything.
Wrong MAC? Wrong IMEI? Try restoring files from /sdcard/backup/efs*/* to /efs/. If you don’t have a backup, then start over with FULL Restock, and next time save your backup/efs folders, which are created everytime you install CM10.1.
Market problems? Clear Google Services Framework data and reboot.
No touch? That means you got the wrong kernel installed. A couple of builds had problems identifying the exact model. Just flash your kernel through recovery or heimdall / odin.
No boot? Stuck at the SAMSUNG logo? Flash the correct kernel using Download Mode using heimdall!
Deep Sleep not kicking in? Try wiping cLock’s data or freezing / removing it (com.cyanogenmod.lockclock).
--------------------------------------Highlights of What you get inside---------------------------------------------------------------
**\TheCollective-StockRooted-sch-i800.tar.gz
The Heimdall package
**\tools-resources\drivers\Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Samsung Mobile Drivers for usb
**\tools-resources\Heimdall\heimdall-suite-1.3.2-win32.zip
Heimdall
**\tools-resources\HumberOS\heimdall-uses\boot.img
CM10.1 humberOS Kernel P1c
**\tools-resources\HumberOS\heimdall-uses\recovery.bin
TWRP Touch Recovery 2.5.0.0
**\tools-resources\HumberOS\CwM_CM10.1-humberos_kernel_p1c-20130715.zip
CM10.1 humberOS Kernel P1c
**\tools-resources\MicrosoftC++12\vcredist_x86.exe
Microsoft C++ redisturbutial
**\tools-resources\ODIN-1.7\
Odin3 v1.7.exe
If you need it for modems or kernels
**\tools-resources\PartitionTool4microSD\pwhe8.exe
if you get encryption failed, you might find this usefull to partition your external sdcard [deeper instruction online at rootzwiki]
**\tools-resources\SuperOneClick\SuperOneClickv2.3.3-ShortFuse.zip
unroot/root what ever just good to have hard to find
DOWNLOAD
MD5 Sum: F0F9C9FA54219EDFA50E85163D9A7C54
Excellent job of documentation! Thanks for all the hard work.
I come up with an MD5 of f0f9c9fa54219edfa50e85163d9a7c54 Anyone want to confirm?
robjective said:
Excellent job of documentation! Thanks for all the hard work.
I come up with an MD5 of f0f9c9fa54219edfa50e85163d9a7c54 Anyone want to confirm?
Click to expand...
Click to collapse
F0F9C9FA54219EDFA50E85163D9A7C54
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4 Beta
Appreciate the thread! Is it possible to get a mirror though? The current host keeps cutting me off whenever I try to download the file... Can't make it past 200MB no matter what I try; other files download fine.
Going through the whole process but "Heimdall.exe" stopped working EVERY time I press start. Any ideas?
Cellulah said:
Appreciate the thread! Is it possible to get a mirror though? The current host keeps cutting me off whenever I try to download the file... Can't make it past 200MB no matter what I try; other files download fine.
Click to expand...
Click to collapse
I had the some problem. Tried it at work with FF, Chrome, and Free Download Manager and all would fail at some point after about 2/3 done.
Came home and tried and got it first try.
tinpanalley said:
Going through the whole process but "Heimdall.exe" stopped working EVERY time I press start. Any ideas?
Click to expand...
Click to collapse
Perhaps bad DL.
Make sure you follow all instruction.
Don't skip any steps.
Don't forget to have the correct ms c++ redist istalled.
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
Perhaps bad DL.
Make sure you follow all instruction.
Don't skip any steps.
Don't forget to have the correct ms c++ redist istalled.
Sent from my GT-P5110 using Tapatalk 4
Click to expand...
Click to collapse
I'll try again. The download was fine but I suppose I could try again.
No use.. same error every time . Tried with each driver as well. All I get is this:
tinpanalley said:
No use.. same error every time . Tried with each driver as well. All I get is this:
Click to expand...
Click to collapse
Tell me more about your operating system that your using.
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
Tell me more about your operating system that your using.
Sent from my GT-P5110 using Tapatalk 4
Click to expand...
Click to collapse
Windows 7, 64-bit
Intel i5-2400 3.10 GHz
Just a question. Every time I boot to recovery <3e>, and try to wipe data, I get the following:
E:failed to mount /data (Invalid argument)
E:install_application_for_customer: Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions
Could this have anything to do with why I'm not able to get out of my bootloop?
tinpanalley said:
Just a question. Every time I boot to recovery <3e>, and try to wipe data, I get the following:
E:failed to mount /data (Invalid argument)
E:install_application_for_customer: Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions
Could this have anything to do with why I'm not able to get out of my bootloop?
Click to expand...
Click to collapse
Yes. I had same issue on my captivate trying to restore stock from a cm7
To fix I had to flash in the kernel and recovery from cm and in cwm under advance mounts format data. Back then on that device speedmod kernel allowed users to select format method (fat32/ext4/etc)
But also hemidall should format with the repartition. But that is assuming it can read and mount the partition.
You can use this package but instead of flashing the ROM package,
Load the pit and load only the kernel and recovery
Then boot into cwm and mount and format data (might as well while your at it mount and format system, and cache)
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
You can use this package but instead of flashing the ROM package,
Load the pit and load only the kernel and recovery
Then boot into cwm and mount and format data (might as well while your at it mount and format system, and cache)
Click to expand...
Click to collapse
I did try this but I still get the crash of heimdall.
Also what does "mount and format data" mean? I can format data, system and cache but I don't see "mount" at all.
The Collective DL Fails
So I am trying to download the package that is for this which would be most helpful for me as I'm trying to help out my pastors wife with her Galaxy Tab, I started the download and it got all the way up to 144MB and quit, and file won't work.
Is there somewhere else that you can put it so we can try downloading from there? Can I give you my dropbox and you can drop it in there?
Again just to say I don't have a problem with HEIMDALL I have a problem downloading your link for the files needed for the flash.
I would really like to try to get this working for her as I've been looking around for a solution for this thing for about 2wks already and its been blowing my mind.
So we need the DL fixed so we can download the Collective Package.
Thanks again for the help and great write-up.
Lem
:angel:
chi_tilt said:
So I am trying to download the package that is for this which would be most helpful for me as .......
So we need the DL fixed so we can download the Collective Package.
Thanks again for the help and great write-up.
Lem
:angel:
Click to expand...
Click to collapse
Try a direct download link
http://www.theandroidcollective.org/i800/public/TheCollective-HelperPackage_sch-i800.zip
Sometimes download errors like yours seem to happen when the user is behind a proxy.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
No 3G with alroger's latest kernel
I guess this is a pretty common issue for CDMA user's. alroger's download page says to copy the modem.bin to the /radio. I downloaded the original verizon modem binaries for my sch-i800 but I don't see a /radio folder. In the about tablet section, baseband is unknown. I just created a radio folder on the root of the tablet and renamed my download modem.bin and stuck it in there. I'm about to reflash the just the kernel but I'm pretty sure that's not how it works. So how do I get my radio/modem back and get 3g working with this kernel? cafe-ti.blog.br/1956~cm10-1-sgt7-p1000.html
arielja87 said:
I guess this is a pretty common issue for CDMA user's. alroger's download page says to copy the modem.bin to the /radio. I downloaded the original verizon modem binaries for my sch-i800 but I don't see a /radio folder. In the about tablet section, baseband is unknown. I just created a radio folder on the root of the tablet and renamed my download modem.bin and stuck it in there. I'm about to reflash the just the kernel but I'm pretty sure that's not how it works. So how do I get my radio/modem back and get 3g working with this kernel? cafe-ti.blog.br/1956~cm10-1-sgt7-p1000.html
Click to expand...
Click to collapse
Easiest way is to tar the modem.bin and Odin it into the device.
Load it into the phone slot
Sent from my GT-P5110 using Tapatalk 4
Help to download...
Hi... I have tried many times to download the package (TheCollective-RootedStock-Odin-sch-i800.tar.md5) but I can not , the download starts fine, but not complete!.
If you could upload to another server like 4shared, mediafire, dropbox... I would be very grateful..
Still not working as it should
So I have downloaded the package finally and I Have done all the steps according to your writeup. Still doesn't give me a fresh startup on the tablet, I still get many error popups and also all my apps are still there.
What could I be doing wrong? Could there be something wrong with the tablet?
Any help on this would be great, as I'm dumbfounded on this already.
Thank You
Lem
HARD BRICK NO MORE!!! Asus ZenPad S8.0 Fix
I made the sad retarded mistake in updating a manual zip file thru CMW... I know retarded... anyways this caused the tablet to Hard Brick bootloader only with very little options, you might even have your serial number showing up as all 1's.
Usually this isn't a big deal sadly this tablet gets little to no love on the internet it seems... This is a guide to help anyone un-brick their tablet
Step 1. First this is more of a windows 10 issue than anything but some driver installs thru the Asus Flash Tool might fail.. something to do about Driver Certificates, so you'll want to disable that on your Win 10.. here a tutorial link for more youtube link HERE
Step 2. Installing the proper Drivers if you haven't already, which will all be in this zip folder HERE
Make sure you installed the ADB-Setup | Intel Android Drv Setup | Asus Android USB Drivers | Asus Flash Tool Installer 1.14
Step 3. Next you'll want to download the .raw file for the ZenPad can be found HERE
Step 4. Open your Asus Flash Tool Installer, boot up your device in the boot mode. (Hold Down the Volume Up + Power ) till you see a little android man with a hardhat.
Step 5. Plug in your device and you should see your device show up as shown HERE, next you'll want to select the model in the model drop down.... Z580C or Z580CA.. then select file. Now if it only lets you select zip thats okay. On the open file dialog box you'll see you can type in the file, simply type in the file path of the .raw file. Once you have that check on Erase Content which will erase all your internal content, and hit flash... let it run until the blue light on the program is green and has flashed succefully.
{
"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"
}
Now you may still get on a bootloop when it restarts, if that happens simply again restart in boot loader screen and do a hard reset and you'll be good to go! Afterwards just throw that new Marshmallow update in the internal and restart .. and you'll device will ask if you want to update now u got your tablet back and Marshmallow!!! I hope this helps if you have any troubles with the links, images please feel free to let me know pm or reply to this post!!! Best of Luck!
.RAW File was provided by Portzebie! Thanks again bud!!
Thanks for this guide. You mentioned .img file, but the file has a .raw extension. Do I need to change the extension from .raw to .img ? Yor response will be highly appreciated. my device is Z580CA.
Thanks again.
tfq535 said:
Thanks for this guide. You mentioned .img file, but the file has a .raw extension. Do I need to change the extension from .raw to .img ? Yor response will be highly appreciated. my device is Z580CA.
Thanks again.
Click to expand...
Click to collapse
Just followed the guide and after a little tinkering was able to get it to work. You don't need to change the file extension.
A few additional notes:
-to install the asus android drivers (not sure if it's even necessary but), open the ASUS_Android_USB_Drivers folder, then the android folder, then right click android_winusb.inf and select install.
-in the asus flash tool, after you select model, the location of the raw file and wipe, make sure you click on the SN to select the device. I didn't do this the first few times and it didn't do anything.
portezbie said:
Just followed the guide and after a little tinkering was able to get it to work. You don't need to change the file extension.
A few additional notes:
-to install the asus android drivers (not sure if it's even necessar but), open the ASUS_Android_USB_Drivers folder, then the android folder, then right click android_winusb.inf and select install.
-in the asus flash tool, after you select model, the location of the raw file and wipe, make sure you click on the SN to select the device. I didn't do this the first few times and it didn't do anything.
Click to expand...
Click to collapse
Thanks again, it worked like a charm.
bert_747 said:
Step 5. Plug in your device and you should see your device show up as shown HERE, next you'll want to select the model in the model drop down.... Z580C or Z580CA.. then select file. Now if it only lets you select zip thats okay. On the open file dialog box you'll see you can type in the file, simply type in the file path of the .img file. Once you have that check on Erase Content which will erase all your internal content, and hit flash... let it run until the blue light on the program is green and has flashed succefully.
Click to expand...
Click to collapse
Thanks for the guide.
The link to your screenshot is missing.
PMikeP said:
Thanks for the guide.
The link to your screenshot is missing.
Click to expand...
Click to collapse
Sorry bout that, screen shots should be working.
a little question,
is it possible to get xfstk files to restore a corrupt bootloader?
thx,,,
ASUS Flashtool doesn't start flashing
Hi all, apprechiated all the posts above however, came across another issue when trying to downgrade from MM 6.0.1 to Lollipop
1. Hooked up my Z580CA tablet as described above.
2. ASUS flashtool recognized my device (right serial number and blue light on)
3. I was not able to put in the raw-file location, only (neither with backslash or without)
4. When pasting path and including backslash I was able to select the raw file (H:\EDV\Tablet\Android 5 LP\RAW\Z580C_all_WW_user_V4.6.1.raw was quoted in the file name window)
5. When I hit start, the flashtool ask for confirmation upon wiping data.
6. Nothing happens
Does anybody have a clue what went wrong
These instructions do not work for Ubuntu. I find it very hard to believe that there is only a Windows version of the flash tool available.
Does anyone know how to upgrade again to MM after flashing this rom?
EDIT: CAUTION People, there seems to be no way to upgrade back to MM after flashing this ROM.
Yes you can upgrade
Servaas said:
Does anyone know how to upgrade again to MM after flashing this rom?
EDIT: CAUTION People, there seems to be no way to upgrade back to MM after flashing this ROM.
Click to expand...
Click to collapse
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles
edu47 said:
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles
Click to expand...
Click to collapse
And you did this by downloading the .zip file from Asus Support? Then you placed it on the internal memory of the Zenpad? Unzipped or zipped?
EDIT: Until someone more senior comes to this thread and confirms that they have a. Used the provided .raw file, and b. updated afterwards with the precise steps i'm very much questioning this .raw file legitimately.
Servaas said:
And you did this by downloading the .zip file from Asus Support? Then you placed it on the internal memory of the Zenpad? Unzipped or zipped?
EDIT: Until someone more senior comes to this thread and confirms that they have a. Used the provided .raw file, and b. updated afterwards with the precise steps i'm very much questioning this .raw file legitimately.
Click to expand...
Click to collapse
download on asus homepage the file "UL-P01M-WW-5.4.3.0-user.zip", just copy it like it is on the root of your internal sdcard.
restart your zenpad and it will show you the message, upgrade available.
Edit:are you sure you on lollipop? If you are on Marshmallow ,the device wont recognize the systemupgrade.
if you re rooted it may also wont work
edu47 said:
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles
Click to expand...
Click to collapse
edu47 said:
download on asus homepage the file "UL-P01M-WW-5.4.3.0-user.zip", just copy it like it is on the root of your internal sdcard.
restart your zenpad and it will show you the message, upgrade available.
Edit:are you sure you on lollipop? If you are on Marshmallow ,the device wont recognize the systemupgrade.
if you re rooted it may also wont work
Click to expand...
Click to collapse
All of it does nothing for me. I'm stuck on 5.0. To people reading this use this .raw file at your own risk.
Servaas said:
All of it does nothing for me. I'm stuck on 5.0. To people reading this use this .raw file at your own risk.
Click to expand...
Click to collapse
Did you made an factory reset after installing lollipop on fastboot mode?
Switch your device off. Turn it on by pressing volume up and powerbottom at the same time.
When the little androidman appears you can stop pressing both bottoms.
Choose factory reset with volume bottom and confirm with power bottom.
edu47 said:
Did you made an factory reset after installing lollipop on fastboot mode?
Switch your device off. Turn it on by pressing volume up and powerbottom at the same time.
When the little androidman appears you can stop pressing both bottoms.
Choose factory reset with volume bottom and confirm with power bottom.
Click to expand...
Click to collapse
I just did this, this is my second tablet by the way, I returned the other one and this second one also does NOTHING when trying to update.
Its a shame really, its a great product but the lousy support on Asus side does little to inspire to again purchase from them. Honestly who rips out multiple user support on a tablet?
I'm all out of options to be honest, I have tried everything even variations on suggested sulotions but nothing works to make the update pop up.
This .raw file to me is broken when there is no way to update beyond that. But I need multi user support so I guess ill just stay on 5.0.
Servaas said:
I just did this, this is my second tablet by the way, I returned the other one and this second one also does NOTHING when trying to update.
Its a shame really, its a great product but the lousy support on Asus side does little to inspire to again purchase from them. Honestly who rips out multiple user support on a tablet?
I'm all out of options to be honest, I have tried everything even variations on suggested sulotions but nothing works to make the update pop up.
This .raw file to me is broken when there is no way to update beyond that. But I need multi user support so I guess ill just stay on 5.0.
Click to expand...
Click to collapse
Probably you still on lollipop by this version "Z580C_all_WW_user_V4.6.1.raw" from the tutorial . Get from asus usa website the "UL-P01M-WW-4.7.1.0-user.zip" and update to latest lollipop version . Then it might update again to mm.
Here the link
h ttp://www.asus.com/us/Tablets/ASUS_ZenPad_S_80_Z580CA/HelpDesk_Download/
edu47 said:
Probably you still on lollipop by this version "Z580C_all_WW_user_V4.6.1.raw" from the tutorial . Get from asus usa website the "UL-P01M-WW-4.7.1.0-user.zip" and update to latest lollipop version . Then it might update again to mm.
Here the link
h ttp://www.asus.com/us/Tablets/ASUS_ZenPad_S_80_Z580CA/HelpDesk_Download/
Click to expand...
Click to collapse
This zip file also doesnt register, nothing pops up and no, when pushing the update button it also does nothing.
It would seem that the OP provided a nice 5.0 raw file that renders your tablet un updateble.
I'll be returning this tablet and going for the only available option in the netherlands the samsung 8 incher.
Z580C tablet is bricked, it happened on update, I think battery was too low. Screen is black all the time, under windows device manager it connects as other devices, MOOREFIELD device with no drivers and I can hear from windows sounds that it reboots after some time. All post #1 drivers are installed.
Please help.
Thank you
magnus_bn said:
Hi all, apprechiated all the posts above however, came across another issue when trying to downgrade from MM 6.0.1 to Lollipop
1. Hooked up my Z580CA tablet as described above.
2. ASUS flashtool recognized my device (right serial number and blue light on)
3. I was not able to put in the raw-file location, only (neither with backslash or without)
4. When pasting path and including backslash I was able to select the raw file (H:\EDV\Tablet\Android 5 LP\RAW\Z580C_all_WW_user_V4.6.1.raw was quoted in the file name window)
5. When I hit start, the flashtool ask for confirmation upon wiping data.
6. Nothing happens
Does anybody have a clue what went wrong
Click to expand...
Click to collapse
Had the same problem and what I did to make it work was.
1. Lunch Asus Flash Tool
2. Connect device in download mode (volume up + power)
3. Wait for device to be visible in Asus Flash Tool ( Serial number + blue dot) - you may need to restart tablet using reboot droidboot
4. Select model number
5. Point to raw file and choose to erase data (accept the prompt )
6 Hit Start
What I also did prior to that was factory reset of tablet
hope that helps you
Trying to flash twrp recovery...getting error "target reported max download..."
I'm trying to install twrp recovery but getting the error message: Target reported max download size of 536870912 bytes; error: cannot load 'twrp.img': unknown error
The phone was previously unlocked and rooted on lollipop....had problems and restored...took OTA update to Marshmallow 6.0.1
Any ideas? Please and thanks!
DoritoKing said:
I'm trying to install twrp recovery but getting the error message: Target reported max download size of 536870912 bytes; error: cannot load 'twrp.img': unknown error
The phone was previously unlocked and rooted on lollipop....had problems and restored...took OTA update to Marshmallow 6.0.1
Any ideas? Please and thanks!
Click to expand...
Click to collapse
1) how are you trying to install TWRP?
2) You are using the most recent version from our official TWRP maintainer?
January 12, 2017
twrp-3.0.3-0-Mod_01-quark.img
https://www.androidfilehost.com/?fid=745425885120699982
3) And you are showing known file extensions in Windows? Do you know what that means?
{
"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"
}
If you have a jpg or pdf, and you see a file name -- do you also ALWAYS, ALWAYS see the extension like jpg or pdf? Default in Windows -- for idiotic reasons -- is to "hide known file extensions".
Make sure that box is UNchecked in your Windows settings. Because otherwise you are re-naming TWRP as TWRP.img(.img). You do NOT have to type the .img part, it's ALREADY an .img file.
That may or may not be your issue, but it messed up a lot of people in the past. ADB couldn't find TWRP.img because they had unknowingly called it TWRP.IMG.img -- because they couldn't see the file extension and thought they needed to add it to the file name.
1. I had the previous version 3.0.2-0...will try your link.
2. I unchecked the extension box...
will try again and let you know...thank you!
Just tried with the changes....still getting same error messages.
DoritoKing said:
1. I had the previous version 3.0.2-0...will try your link.
2. I unchecked the extension box...
will try again and let you know...thank you!
Click to expand...
Click to collapse
When you unchecked the extension box, what is now the visible name of your TWRP file? Does it say TWRP.img.img or just TWRP.img? Besides unchecking the extension box, you also need to make sure you are typing the actual name of the file. IF you had typed "TWRP.img"(.img) before, you now need to re-name it just "TWRP".img.
If you confirm that's not the issue, then we'll get @bhb27 involved over in the Quark TWRP thread.
I changed the filename to twrp and I'm using the command: fastboot flash recovery twrp.img and I've tried every other combination of twrp.img.img, twrp, etc just to make sure I wasn't missing something!
My goal is to be able to flash a new build.prop to allow for tethering...if there is a way to do that without installing twrp, that would be great
DoritoKing said:
I changed the filename to twrp and I'm using the command: fastboot flash recovery twrp.img and I've tried every other combination of twrp.img.img, twrp, etc just to make sure I wasn't missing something!
My goal is to be able to flash a new build.prop to allow for tethering...if there is a way to do that without installing twrp, that would be great
Click to expand...
Click to collapse
OK, just as a test, do this. Forget the name TWRP. That's just a convenience. Call it something else. Rename it box or chair. I'm not joking. Then, in your PC, what file name do you see? IF you renamed it "box", you should see box.img. You do NOT type .img. It's just the extension that should already be there!
then flash: fastboot flash recovery box.img
I'm suggesting this because somehow, somewhere it seems your file name is messed up?
Also you have done all this too? Permissions and stuff?
Enable USB debugging on your device:
Open Settings on your device.
Go to About phone and tap seven times on Build number, this will enable Developer options.
Now go back to Settings and you’ll see Developer options there, open it.
Tick the USB Debugging checkbox.
Connect your device to the PC. And type the following into the command window we opened to boot your device into bootloader/fastboot mode:
adb reboot bootloader
└ If you get a permission dialogue on your device to “Allow USB debugging”, tap OK.
Click to expand...
Click to collapse
Maybe revoke those permissions and re-enable them?
Renamed it "dummy"....the name I see on my file list is "dummy"......Still getting same error message. I tried recovery dummy.img and recovery dummy....still same error.
adb reboot bootloader works....cant flash the recovery image though. Do I need to do something else on the phone side prior to flashing the image? It has the android laying on its back with the "Start" option showing on top...
DoritoKing said:
Renamed it "dummy"....the name I see on my file list is "dummy"......Still getting same error message. I tried recovery dummy.img and recovery dummy....still same error.
adb reboot bootloader works....cant flash the recovery image though. Do I need to do something else on the phone side prior to flashing the image? It has the android laying on its back with the "Start" option showing on top...
Click to expand...
Click to collapse
I was just suggesting you revoke the USB permissions and re-enable them in Developer Settings, just to make sure. That's the only thing I'm aware of you need to do on the phone side... If anyone knows something different, feel free to correct me!
@bhb27 is our TWRP maintainer for our official TWRP. So, I'm mentioning him here so he'll see this issue. Maybe he'll have some ideas?
Also, you you can post this issue over in the Quark TWRP thread. You can put a link to this thread in your post, so people can see what all we've tried.
[RECOVERY][OFFICIAL TWRP 3.0.2-0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
https://forum.xda-developers.com/mo...recovery-twrp-2-8-7-0-touch-recovery-t3180308
I need print screen of what is going on in the terminal when the problem is manifested...
need a print screen of the folder were adb, fastboot and the recovery files are.
need a print screen of the content of properties of the twrp.img
bhb27 said:
I need print screen of what is going on in the terminal when the problem is manifested...
need a print screen of the folder were adb, fastboot and the recovery files are.
need a print screen of the content of properties of the twrp.img
Click to expand...
Click to collapse
Here are the screenshots...if this isn't what you were looking for, just let me know.
DoritoKing said:
Here are the screenshots...if this isn't what you were looking for, just let me know.
Click to expand...
Click to collapse
Yes it is.
can you try this fastboot?
https://www.androidfilehost.com/?fid=24052804347845784
add a m to fastboot command
Code:
mfastboot flash recovery twrp
if it fails give
Code:
mfastboot devices
and print the screen...
:good:
bhb27 said:
Yes it is.
can you try this fastboot?
https://www.androidfilehost.com/?fid=24052804347845784
add a m to fastboot command
Code:
mfastboot flash recovery twrp
if it fails give
Code:
mfastboot devices
and print the screen...
:good:
Click to expand...
Click to collapse
Didn't recognize that command...here is the screenshot
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
DoritoKing said:
Didn't recognize that command...here is the screenshot
Click to expand...
Click to collapse
did you download the file I share?
TheSt33v said:
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
Click to expand...
Click to collapse
I didn't know how to open my command prompt in a particular folder, but I figured that out now. I was able to try again and run the original fastboot and it worked! I've got TWRP on my phone!!
I've attached a screenshot. I was told that when I type the commands, to not include the .img for the TWRP file.....so I just typed fastboot flash recovery twrp and it worked.
Thank you everyone for all your help. I'm a newbie, so I appreciate everyone being patient when I don't know how to do certain things correctly.
TheSt33v said:
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
Click to expand...
Click to collapse
Right. His screenshot is showing other extensions, like .exe, .txt, .dll -- so his TWRP extension should be .img. It's missing.
What I cautioned him about was double naming the extension -- TWRP.img.img, which can accidentally be done if you have your Windows settings to hide known file extensions. Since his file extensions are no longer hidden, his TWRP file should say TWRP.img.
But naming it TWRP is just a convenience instead of using the regular file name like "twrp-3.0.3-0-Mod_01-quark.img". It's easier to type TWRP.img in the Windows command box than that long official file name. You could easily also re-name it "chair.img" or "box.img" as long as you were re-naming the correct file. I even suggested he do that because he seemed hung up over the TWRP name.
At this point, he probably needs to also re-download the TWRP file and re-name it. Now that he can see file extensions, it should automatically have the .img extension.
Me again...the guy who probably shouldn't be messing with his phone
I got TWRP installed. Tried flashing a zip for tethering...upon reboot it was getting stuck at bootloader warning screen. Eventually tried a wipe through TWRP (data, cache, and dalvik) and a factory reset through the phone menu, but still keeps getting stuck at bootloader. I can still get into TWRP, but not sure where to go from here
Do I need to do the wipe differently? Anyway to get past the bootloader screen?
DoritoKing said:
Me again...the guy who probably shouldn't be messing with his phone
I got TWRP installed. Tried flashing a zip for tethering...upon reboot it was getting stuck at bootloader warning screen. Eventually tried a wipe through TWRP (data, cache, and dalvik) and a factory reset through the phone menu, but still keeps getting stuck at bootloader. I can still get into TWRP, but not sure where to go from here
Do I need to do the wipe differently? Anyway to get past the bootloader screen?
Click to expand...
Click to collapse
I'm going to hazard a guess here that you also flashed SuperSu in TWRP and you are running the new Marshmallow update. (Yeah, confirmed, I just checked your first post. You took Marshmallow update.) In which case, it sounds like you flashed the wrong version of SuperSu. You have to flash an older version for initial root or your phone will stick at the bootloader warning screen. This has been discussed in all the Marshmallow threads.
What version SuperSu are you using? If on stock Marshmallow or stock-based Marshmallow ROM, the one required is BETA-SuperSU-v2.62-3-20151211162651). You can boot into TWRP, plug your phone into a PC and drag it over like a flash drive. It will show up in the root folder. Flash it, wipe all caches, reboot.
I've attached it to this post.
AFTER initial root, and after you successfully boot, then you can update to newest version of SuperSu. You just need it for initial root and to successfully boot the first time.
PREDICTION: Your next question will be how to get rid of the unlocked bootloader screen. Because you will see it every time you reboot your phone. When you do, here's your answer. But first, you need to flash the correct SuperSu to get past the bootloader screen.
DoritoKing said:
I didn't know how to open my command prompt in a particular folder, but I figured that out now. I was able to try again and run the original fastboot and it worked! I've got TWRP on my phone!!
I've attached a screenshot. I was told that when I type the commands, to not include the .img for the TWRP file.....so I just typed fastboot flash recovery twrp and it worked.
Thank you everyone for all your help. I'm a newbie, so I appreciate everyone being patient when I don't know how to do certain things correctly.
Click to expand...
Click to collapse
Congratulations on installing TWRP.
There seems to be a little confusion on how to do this and I've written down how to in many posts now so I figure I'd just write it down in a little guide.
What you need:
Firmware update.zip from http://pro-teammt.ru/firmware-database/
Windows only: Huawei Update Extractor
Linux/Mac(?)/(Windows too): splitupdate perl script (requires perl)
Direct link: https://mega.nz/#!4PBknJrK!iZQDI4ti6ERmQJC6afgUGTSvHHKcm9KFz9okmwwez3I
Source: https://github.com/marcominetti/split_updata.pl/tree/f5f415262be3487de28321b49dcb69d947897bf1
(Or my 'special' version https://mega.nz/#!NS4VnL7Q!5GMn-soCf_WMW6fZANd-TDzxjQkZW2LynEQtJ_TlUdU which extracts
to the same folder as 'splitupdate' instead of 'output/', and includes a mount script (Linux only, maybe Mac?) for extraction of files of the different images)
Archive extractor of your choice (7zip, winrar, winzip and so on.)
Firmware build
First you need to determine what your current firmware is, this can be done by going to 'Settings -> System -> About Phone' on your phone. Check 'Build Number'.
Mine says:
{
"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"
}
BLA-L29 8.0.0.132(C636) (Replace 8.0.0. with C636 and add a B infront of 132 )
This can be translated into BLA-L29C636B132.
Now we have our current firmware!
Info on Nougat -> Oreo
As of Oreo the partitions changed a little.
'Boot' partition was split into 'ramdisk' and 'kernel'.
'Recovery' partition was split into 'recovery_ramdisk', 'recovery_vendor' and 'recovery_vbmeta', and shares the 'kernel' partition with 'ramdisk'.
The one's you probably want to flash are 'ramdisk' and 'recovery_ramdisk'. (Ramdisk is where Magisk/SuperSU goes, recovery_ramdisk is where TWRP goes)
Firmware update.zip
In this example I will be using my firmware, BLA-L29C636B132.
First start by going to http://pro-teammt.ru/firmware-database/ and enter your full firmware in the 'Enter model', click on Find Model.
This is what it will look like after you have searched. Locate the row that says FullOTA-MF and click on the 'update' link in that row.
When it's downloaded, open update.zip in your choice of archive manager and extract UPDATE.app to your desktop or somewhere easy to find.
Huawei Update Extractor:
Download Huawei Update Extractor from the link above, it's attached to first post in that thread I linked to (v0.9.9.5).
Extract the zip to your desktop (Or Downloads folder).
Enter the newly created folder that should be named 'HuaweiUpdateExtractor_0.9.9.5', and run HuaweiUpdateExtractor.exe.
Start by going to the 'Settings' tab and uncheck 'Verify header checksum'.
(Something is wrong with the header of erecovery_ramdisk, also it's mispelled to erecovery_ramdis, or maybe character limit? The partition on phone is named correctly. This does not need to be unchecked on Nougat firmware)
Then go back to the 'Extract' tab and click on the button that says '...' and open your UPDATE.APP
Rightclick on the file you want to extract and click on 'Extract Selected', this will bring up a dialog where you choose where to extract to.
After this you can flash the file using fastboot. Take 'ramdisk' for example.
Make sure you have adb & fastboot installed (https://forum.xda-developers.com/showthread.php?t=2317790)
Open up a command prompt and connect phone, reboot to fastboot mode using: usb plugged in, power + vol down, release power when phone vibrates.
Or you can use the command 'adb reboot bootloader'.
Make sure phone is recognized in fastboot mode with the command: 'fastboot devices', it should show up as a fastboot device.
Next we can flash RAMDISK.img using: 'fastboot flash ramdisk RAMDISK.img'.
On Nougat you would extract 'BOOT' from UPDATE.APP and flash using:
'fastboot flash boot BOOT.img'
Linux/Mac(?)(and Windows with perl installed, I use Strawberry Perl)
First download the splitupdate zip from above.
Extract it and enter the extracted 'split' folder, open a terminal and:
'chmod +x splitupdate'
'chmod +x crc'
Now put your UPDATE.APP in the 'split' folder and open a terminal and use the following command:
'./splitupdate UPDATE.APP file_to_extract'. If you write 'file_to_extract' or anything that is or is not in the UPDATE.APP it will list all images in it.
Typing './splitupdate UPDATE.APP' will extract all files in UPDATE.APP
It will output files to the newly created 'output' folder. The filtering is not perfect. If you use './splitupdate UPDATE.APP RAMDISK', it will extract all images with RAMDISK in its name, so you will get RAMDISK.img and RECOVERY_RAMDISK.img. This is fine for me as the original script extracted everything, which takes long for the larger images.
And if you use the 'special' version:
'chmod +x simg2img'
'chmod +x mount.sh'
I edited the splitupdate script for the 'special' version just to make it easier for me as I like to check SYSTEM, VENDOR, PROCDUCT and those images for changes.
So it made it easier if it extracted directly to the root of 'split' folder instead of 'output', then I could run the mount.sh script directly.
To use mount.sh, first edit the script and replace YOUR_SUDO_PASSWORD_HERE with your password or remove 'echo YOUR_SUDO_PASSWORD_HERE | ' and input password manually when it asks.
Then simply extract SYSTEM.img (or Product, vendor, odm whichever you like) and './mount.sh SYSTEM' (yes, no extension).
This will convert SYSTEM.img to SYSTEM.raw and mount it to 'split_folder/SYSTEM/' as a loop device, it will also chmod 777 everything in SYSTEM/.
Linux ADB and Fastboot
Use google for this one. ADB usually works fine right away, Fastboot might get 'no permissions' and need to be run as sudo if it's missing udev permissions/entries.
You can make fastboot work without sudo but it's easier to google it as it might get lengthy and there are a lot of different distros of linux (I use Ubuntu)
Hi ante0, i have downloaded the bla a09 8.0.0.109 c567 which is the recent update for my US mate 10 pro version, i was using hisuite to update my phone which is failing but i was able to grab the update which it down loaded and it has the following files in it, bla-a09_hw_usa( which contains update_full_BLA-A09_hw_usa, public( which contains update_data_full_public), update.zip which contains update.app and other xml files, i have already bl unlocked and rooted with supersu but i wanted to install magisk and i installed twrp and tried sideloading magisk but it fails stating boot image already modified and advised flask stock boot, so which files do i need to flash and what are the fastboot commands to do so and i was also thinking about complete bl lock just to make it look like new phone and how do i do that, please direct me, thank you.
I think to update you'll need to:
A) Unroot your supersu.
B) Restore stock boot and restore your stock recovery with guide in OP and with the firmware files actually installed on your phone.
Then you could root oreo with magisk.
oslo83 said:
I think to update you'll need to:
A) Unroot your supersu.
B) Restore stock boot and restore your stock recovery with guide in OP and with the firmware files actually installed on your phone.
Then you could root oreo with magisk.
Click to expand...
Click to collapse
there lies my problem, i am trying to flash an updated stock firmware than the one that came with my phone, i have unrooted supersu and deleted supersu app and dont have root anymore confirmed by rootcheck apps, since my boot is already patched once magisk wont flash and advising me to flash stock boot image but i dont know which to flash as with oreo there seems to be different partitions and i dont know commands other than basic fastbbot commands to flash stuff.
ok so i was able to flash ramdisk, recovery and system and boot back to OS ( i have earlier erased system by mistake) and i have flashed system.img from updated firmware but version still shows old one, and i am trying to use funkyhuawei erecovery method to flash the updated firmware and when i boot to erecovery to update but the update button is missing and i just have rebbot, wipe date/fr and wipe cache, so what do i need to flash and commands for it in order to make erecovery work and i have update button enabled, thank you.
lingarajug said:
ok so i was able to flash ramdisk, recovery and system and boot back to OS ( i have earlier erased system by mistake) and i have flashed system.img from updated firmware but version still shows old one, and i am trying to use funkyhuawei erecovery method to flash the updated firmware and when i boot to erecovery to update but the update button is missing and i just have rebbot, wipe date/fr and wipe cache, so what do i need to flash and commands for it in order to make erecovery work and i have update button enabled, thank you.
Click to expand...
Click to collapse
If you can, use the HWOTA method instead. It's free and found: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
If you can't use HWOTA and have to use Funky:
You seem to be in normal Recovery. You should see a button that says 'Download latest firmware', the one you're describing is showing buttons that are in normal Recovery.
Are you booting using Usb plugged in + vol up + power?
For some reason my phone would only boot to revovery and not erecocery, anyway i used hisuite method and was able to flash new firmware. Thank you.
I've just unbricked my Mate 10 pro via this method. Thank you Sir.
Not sure if this is the right place but where can I find the original Huawei OS it was shipped with? I installed Lineage and want to go back to Factory.
I just want to .img file. I have only unlocked the bootloader not rooted the phone.
Lack of camera and other features means I need to get back.
Any ideas?
elviss0812345 said:
I've just unbricked my Mate 10 pro via this method. Thank you Sir.
Click to expand...
Click to collapse
You bricked your device because you don't know what you are doing,not because of this guide.Oh,and i thought KangRom was responsible for bricking you device....anyone else to blame ?
My phone was bricked because of Lineage OS, and i unbricked with this guide. Read my post first.
Pretoriano80 said:
You bricked your device because you don't know what you are doing,not because of this guide.Oh,and i thought KangRom was responsible for bricking you device....anyone else to blame ?
Click to expand...
Click to collapse
elviss0812345 said:
My phone was bricked because of Lineage OS, and i unbricked with this guide. Read my post first.
Click to expand...
Click to collapse
lol,i've read "bricked"... .I apologize for that!:good:
There is no way at least for the US version to find firmwares shipped with phone until now, i figured it out by connecting phone to hisuite on PC and it showed update available and i clicked update and waited until download part of update process completed and then i went to documents folder and hisuite and the app stores the download there and it will have 3 zip files, u can copy them to a different place because once the update completes those files are deleted. Might be the same for other models if supported by hisuite.
Here https://playstoreappinstall.com/play-store-for-huawei/ more info
@lingaraguj not already listed there :
http://pro-teammt.ru/firmware-database/?firmware_model=ALP
?
oslo83 said:
@lingaraguj not already listed there :
http://pro-teammt.ru/firmware-database/?firmware_model=ALP
?
Click to expand...
Click to collapse
US version firmware not listed, lots of international versions though.
can i flash everything in UPDATE.APP to go back to fully stock.
if i can what is the fastboot command for every one of them files like "fastboot flash ramdisk RAMDISK.img'?
ive mate 10 pro.
lex71 said:
Not sure if this is the right place but where can I find the original Huawei OS it was shipped with? I installed Lineage and want to go back to Factory.
I just want to .img file. I have only unlocked the bootloader not rooted the phone.
Lack of camera and other features means I need to get back.
Any ideas?
Click to expand...
Click to collapse
It should say your current firmware (besides Lineage) in Settings -> (System?) -> About.
dark3bod said:
can i flash everything in UPDATE.APP to go back to fully stock.
if i can what is the fastboot command for every one of them files like "fastboot flash ramdisk RAMDISK.img'?
ive mate 10 pro.
Click to expand...
Click to collapse
It's better to use:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I'm not sure if symlinks will be set up correctly if you flash images directly. And some partitions can't be flashed from fastboot (like the erecovery ones)
ante0 said:
It should say your current firmware (besides Lineage) in Settings -> (System?) -> About.
It's better to use:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I'm not sure if symlinks will be set up correctly if you flash images directly. And some partitions can't be flashed from fastboot (like the erecovery ones)
Click to expand...
Click to collapse
@ante0
This man is a legend.........
I would like to express my gratitude in you answering my pms and assisting to get the device up and running.
If ever am in Sweden:silly: ill definitely buy you beeeeeeeeeeeeeeeeeeeeeeers
Thanks for the patience and the help you bring to us noobs bricking these bloody Mate 9's
Im now on lineage os. I didnt flash twrp and magisk. Can i only flash stock system.img to get fully stock. Or i have to flash ramdisk and boot first before system.img
Hello,
So my phone was stuck in bootloop and thus, I created a backup in my SD card. The files are shown as 13 files of 2GB size each with an extension ".backup" Anyone has any idea on how to combine these files and access the data inside on PC. The data is very important. Thank you!
deadmanspeaks said:
Hello,
So my phone was stuck in bootloop and thus, I created a backup in my SD card. The files are shown as 13 files of 2GB size each with an extension ".backup" Anyone has any idea on how to combine these files and access the data inside on PC. The data is very important. Thank you!
Click to expand...
Click to collapse
Crosspost from https://forum.xda-developers.com/t/moto-e4-plus-restart-loop.4241427/
I've had numerous Moto devices and have never seen any backup options in stock recovery., so I haven't any idea what format these are using.
readback stock recovery from SP Flash Tool and flash TWRP. also readback metadata partition (crypto footer). do not unlock bootloader because encryption is bonded to bootloader state. if you are lucky TWRP will work on locked bootloader. TWRP will decrypt your data so you can backup everything
aIecxs said:
readback stock recovery from SP Flash Tool and flash TWRP. also readback metadata partition (crypto footer). do not unlock bootloader because encryption is bonded to bootloader state. if you are lucky TWRP will work on locked bootloader. TWRP will decrypt your data so you can backup everything
Click to expand...
Click to collapse
How to do this? USB debugging and OEM are not ON in my phone. I saw some tutorial on YouTube, but it requires USB debugging.
Can't I use those userdata_*****.backup files?
usb-debugging is another option to access your data (can be enabled in boot.img)
SP Flash Tool is for preloader mode, no usb-debugging required
https://android.stackexchange.com/q/203283
wait, you did factory reset already? in that case crypto footer is reset too. backup is encrypted and therefore useless unless crypto-footer is restored.
you said you restored backup, are you sure? does the phone boot into lock screen like before and is pattern still the same?
aIecxs said:
wait, you did factory reset already? in that case crypto footer is reset too. backup is encrypted and therefore useless unless crypto-footer is restored.
you said you restored backup, are you sure? does the phone boot into lock screen like before and is pattern still the same?
Click to expand...
Click to collapse
Yes, the password is still the same. It's like the phone is again in the same condition with the same issue of boot loop.
I saw some tutorial on SP flash tool and what I did was:
1. Downloaded the SP flash tool
2. Downloaded TWRP recovery specific to my phone
3. Opened flash tool, went to download, clicked on scatter loading, selected the file and then clicked on download and connected my switched off device to the PC via USB
But, nothing happened after that.
My phone started charging, but nothing else happened.
I thought drivers weren't installed, so I went Driver Autoinstaller folders (there were 2 of them) and clicked on Driver Install, but it showed me this
{
"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"
}
Then I clicked on finish and it showed this
When I went to the second folder, it showed me this
Is it because of this, that my device is not detected by this flash tool, and if yes, what can I do?
Yes it's driver issue. Disable driver signature enforcement and reboot. open device manager, connect phone and immediately select yellow triangle. install inf manually with let me pick option
you should not flash TWRP without a backup of stock recovery. Do a readback first. Also it is important the scatter file is matching your current partition layout. therefore you should analyze the result. if you are able to extract ramdisk with AIK then you have successfully dumped stock recovery (and can proceed with next step flashing twrp)
aIecxs said:
Yes it's driver issue. Disable driver signature enforcement and reboot. open device manager, connect phone and immediately select yellow triangle. install inf manually with let me pick option
you should not flash TWRP without a backup of stock recovery. Do a readback first. Also it is important the scatter file is matching your current partition layout. therefore you should analyze the result. if you are able to extract ramdisk with osm0sis' AIK then you have successfully dumped stock recovery (and can proceed with next step flashing twrp)
Click to expand...
Click to collapse
Understood before the readback thing. What is readback? I saw the tab in flash tools, but didn't get what it was? Can you please tell how to do that? (sorry for irritating, as I said I am a noob )
And how to analyse the result part? I didn't get the "extract ramdisk with osmosis AIK"
Is there any tutorial video that you know of, if yes, kindly send the link please coz I don't understand these terms.
And thanks a ton for this!!!
on readback tab delete all entries. add one entry for EMMC_USER. give meaningful file name recovery.img. enter length and start address in hex (refer to scatter file). start readback and connect phone.
Disable Antivirus program and download AIK. copy recovery.img into AIK directory and execute unpackimg.bat. enable Antivirus when done
aIecxs said:
on readback tab delete all entries. add one entry for EMMC_USER. give meaningful file name recovery.img. enter length and start address in hex (refer to scatter file). start readback and connect phone.
Disable Antivirus program and download AIK. copy recovery.img into AIK directory and execute unpackimg.bat. enable Antivirus when done
Click to expand...
Click to collapse
Okay, thank a ton!
I'll do all of this and get back to you.
aIecxs said:
on readback tab delete all entries. add one entry for EMMC_USER. give meaningful file name recovery.img. enter length and start address in hex (refer to scatter file). start readback and connect phone.
Disable Antivirus program and download AIK. copy recovery.img into AIK directory and execute unpackimg.bat. enable Antivirus when done
Click to expand...
Click to collapse
So, what length and start address am I supposed to enter in hex?
And you shared the link AIK, in that there are so many options, which one do I have to select?
What can I do now?
deadmanspeaks said:
So, what length and start address am I supposed to enter in hex?
Click to expand...
Click to collapse
refer to scatter file
check your model name owens (XT1774 XT1775 XT1776) or nicklaus (XT1771 XT1772 XT1773)
download scatter file matching to your device model
https://motostockrom.com/motorola-moto-e4-plus-xt1770
https://motostockrom.com/motorola-moto-e4-plus-xt1771-dual-sim
https://motostockrom.com/motorola-moto-e4-plus-xt1772
https://motostockrom.com/motorola-moto-e4-plus-xt1773
https://motostockrom.com/motorola-moto-e4-plus-xt1775
deadmanspeaks said:
And you shared the link AIK, in that there are so many options, which one do I have to select?
Click to expand...
Click to collapse
Android.Image.Kitchen.v3.7-Win32.zip
Code:
S_BROM_CMD_STARTCMD_FAIL (2005)
[BROM] can not pass bootrom start command! Possibly target power up too early.
deadmanspeaks said:
What can I do now?
Click to expand...
Click to collapse
pretty much self explaining.
why flash boot.img? are you sure that scatter matches your partition layout (you will erase wrong area if not)!?
aIecxs said:
refer to scatter file
View attachment 5281905
check your model name owens (XT1774 XT1775 XT1776) or nicklaus (XT1771 XT1772 XT1773)
download scatter file matching to your device model
https://motostockrom.com/motorola-moto-e4-plus-xt1770
https://motostockrom.com/motorola-moto-e4-plus-xt1771-dual-sim
https://motostockrom.com/motorola-moto-e4-plus-xt1772
https://motostockrom.com/motorola-moto-e4-plus-xt1773
https://motostockrom.com/motorola-moto-e4-plus-xt1775
Android.Image.Kitchen.v3.7-Win32.zip
Code:
S_BROM_CMD_STARTCMD_FAIL (2005)
[BROM] can not pass bootrom start command! Possibly target power up too early.
pretty much self explaining.
why flash boot.img? are you sure that scatter matches your partition layout (you will erase wrong area if not)!?
Click to expand...
Click to collapse
Thanks a lot here it is written nma26.42-169/300 and my phone is xt1770. The link you gave shows the file can't be downloaded, can you please give any other link. I googled the same, it gave me NMA26.42-169 INDIA something but those files are paid
drive.google.com links working fine to me
aIecxs said:
drive.google.com links working fine to me
Click to expand...
Click to collapse
tested all links. must be something about your country. you should get something like
Couldn't preview file. You may be offline or with limited connectivity.
click on -> Download
Google Drive can't scan this file for viruses
click on -> Download anyway
aIecxs said:
tested all links. must be something about your country. you should get something like
Couldn't preview file. You may be offline or with limited connectivity.
click on -> Download
Google Drive can't scan this file for viruses
click on -> Download anyway
Click to expand...
Click to collapse
Yes, I did that, after that only it shows this.
I am about to cry, it's been 14 months trying to get those files. Every time, I get too close and then bam! back to square one. Can't access those userdata***.backup files, can't access the phone, as soon as it starts, it gets stuck in a reboot loop, can't flash TWRP because not able to download the file. You have no idea how painful this is. Still thanks a lot, you helped me a lot, but I guess it's a lost cause now. Earlier lost the person, now lost the memories. Thanks anyways
deadmanspeaks said:
can't flash TWRP because not able to download the file.
Click to expand...
Click to collapse
https://twrp.me/motorola/motorolamotoe4plus.html