Gear Live 5.1.1 OTA Url - Samsung Gear Live

Grabbed this from a logcat of my freshly reset watch
https://android.googleapis.com/pack...1f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf
.zip

elitistphoenix said:
Grabbed this from a logcat of my freshly reset watch
https://android.googleapis.com/pack...1f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf
.zip
Click to expand...
Click to collapse
Thanks. Installing it right now. Do you by any chance have a backup of recovery partition? The one that is newer than or KNX01Q
Wohoo they included wifi support in this(unlike some other android wear watches that were promised wifi, but didn't get one with update).
{
"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"
}

Sorry not at the moment

how do you install it?
EDIT:
I figured it out:
1. reboot into boot menu(samsung logo + diagonal swipe)
2. select recovey
3. use adb to update
4. adb sideload file.zip

https://android.googleapis.com/pack....signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip

any other option other than sideload? I'm having hard time with TWRP and win drivers for sideload use

What about power saving for wifi? In advanced setting is set to 120 minutes, but I don't know what does this mean: disconnects from wifi after 120 minutes?

And I don't have my charge cradle at the office.
Guess I will do this tonight!

insaned said:
any other option other than sideload? I'm having hard time with TWRP and win drivers for sideload use
Click to expand...
Click to collapse
Yea, sideload on TWRP doesn't work for me too. What I did was I modified updater-script in ota zip, pushed zip file using adb into watch storage and just installed it as update.
1. Follow this video https://www.youtube.com/watch?v=WSi0yuRkfPk
2. In TWRP click on install
3. Go into /sdcard/ folder in the TWRP filemanager
4. click on 1e8de7cfe6d5fece253b47a727bb7f1580f31f21...
5. swipe and install

aligatro2010 said:
Yea, sideload on TWRP doesn't work for me too. What I did was I modified updater-script in ota zip, pushed zip file using adb into watch storage and just installed it as update.
1. Download https://dl.dropboxusercontent.com/u/36544414/updater-script
2. Open your 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip using winrar
3. Place file from 1 into \META-INF\com\google\android
4. load into TWRP and on pc do adb push 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip /sdcard/
5. In TWRP click on install
6. Go into /sdcard/ folder in the TWRP filemanager
7. click on 1e8de7cfe6d5fece253b47a727bb7f1580f31f21...
8. swipe and install
Click to expand...
Click to collapse
Thanks for the detailed steps.
However I still get a error flashing the zip..
"Error executing updater binary in zip..."

insaned said:
Thanks for the detailed steps.
However I still get a error flashing the zip..
"Error executing updater binary in zip..."
Click to expand...
Click to collapse
Hmm I should probably zip that updater-script as the windows might be screwing up the endlines when you save it. What is the full error?
https://dl.dropboxusercontent.com/u/36544414/updater-script.zip Here you go.

aligatro2010 said:
Hmm I should probably zip that updater-script as the windows might be screwing up the endlines when you save it. What is the full error?
https://dl.dropboxusercontent.com/u/36544414/updater-script.zip Here you go.
Click to expand...
Click to collapse
Thanks.
I even deleted the file in the 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip and inserted your file there.
Still the same error.
will you mind upload the full zip you used and share it? Thanks for all the trouble.. I guess my watch is fighting back this update by all means!!
E:Error executing updater binary in 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip "
Error flashing zip '/sdcard/1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip'
Click to expand...
Click to collapse

insaned said:
Thanks.
I even deleted the file in the 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip and inserted your file there.
Still the same error.
will you mind upload the full zip you used and share it? Thanks for all the trouble.. I guess my watch is fighting back this update by all means!!
Click to expand...
Click to collapse
Try this one.
https://dl.dropboxusercontent.com/u/36544414/updater-script 2.zip I've redone it from scratch. And tested it flashing.
If that doesn't work, just follow this short video I made. Note that I am using notepad++
https://www.youtube.com/watch?v=WSi0yuRkfPk

aligatro2010 said:
Try this one.
https://dl.dropboxusercontent.com/u/36544414/updater-script 2.zip I've redone it from scratch. And tested it flashing.
If that doesn't work, just follow this short video I made. Note that I am using notepad++
https://www.youtube.com/watch?v=WSi0yuRkfPk
Click to expand...
Click to collapse
Tried both methods but something still returning this error.... it is like if I was trying to inject in in other watch

insaned said:
Tried both methods but something still returning this error.... it is like if I was trying to inject in in other watch
Click to expand...
Click to collapse
What happens if you try to flash the unmodified firmware file. Does it still return the exact same error or is it complaining about wrong fingerprint?
I am gonna upload my modified zip. its gonna take some time. my upload speed sucks.
Looking at your pictures, it seems that the file app_process2, on your watch, has a different checksum than what is supposed to be. So, either your have older firmware than LWX49K(5.0.2) or that file became corrupted or something else happened to it.

aligatro2010 said:
What happens if you try to flash the unmodified firmware file. Does it still return the exact same error or is it complaining about wrong fingerprint?
I am gonna upload my modified zip. its gonna take some time. my upload speed sucks.
Looking at your pictures, it seems that the file app_process2, on your watch, has a different checksum than what is supposed to be. So, either your have older firmware than LWX49K(5.0.2) or that file became corrupted or something else happened to it.
Click to expand...
Click to collapse
I have LWX49K (5.0.2) so I really dunno what might happened.. or it was doing root or I don't understand..!

insaned said:
I have LWX49K (5.0.2) so I really dunno what might happened.. or it was doing root or I don't understand..!
Click to expand...
Click to collapse
Well if thats the only file corrupted, I can give you a backup of mine.
Hmm now that I think about it, I can't because I already upgraded, but I can give you the one from newer firmware and remove check for that one file in the updater-script.
Ok so find this line in your updater-script and just remove it
apply_patch_check("/system/bin/app_process32", "a92a761aef714b5e97bc2f27991d6c6d3432e0eb", "ee28188953742e905c1b20a5349a2184581e2972") || abort(""/system/bin/app_process32" has unexpected contents.");
in TWRP fist go into "mount" and make sure that "system" has checkmark in front of it.
Then get a backup of your file by adb pull /system/bin/app_process32 . Save it to a safe place
Download https://dl.dropboxusercontent.com/u/36544414/modified OTA 81/app_process32
And do adb push app_process32 /system/bin/

aligatro2010 said:
Well if thats the only file corrupted, I can give you a backup of mine.
Hmm now that I think about it, I can't because I already upgraded, but I can give you the one from newer firmware and remove check for that one file in the updater-script.
Click to expand...
Click to collapse
If reseting device would fiznthe file I can do it straight, but I'm not sure of that!
Sent from my SM-G920F using Tapatalk

insaned said:
If reseting device would fiznthe file I can do it straight, but I'm not sure of that!
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I don't think it will since its located in the system partition. When you do reset it formats userdata partition.

aligatro2010 said:
Well if thats the only file corrupted, I can give you a backup of mine.
Hmm now that I think about it, I can't because I already upgraded, but I can give you the one from newer firmware and remove check for that one file in the updater-script.
Ok so find this line in your updater-script and just remove it
apply_patch_check("/system/bin/app_process32", "a92a761aef714b5e97bc2f27991d6c6d3432e0eb", "ee28188953742e905c1b20a5349a2184581e2972") || abort(""/system/bin/app_process32" has unexpected contents.");
in TWRP fist go into "mount" and make sure that "system" has checkmark in front of it.
Then get a backup of your file by adb pull /system/bin/app_process32 . Save it to a safe place
Download https://dl.dropboxusercontent.com/u/36544414/modified OTA 81/app_process32
And do adb push app_process32 /system/bin/
Click to expand...
Click to collapse
Thanks , I will trybit noe as soon as I arrive home sinxe I came to e work
Sent from my SM-G920F using Tapatalk

Related

[Resource/DevTools] TheCollectiveHelpPackageSCH-i800[everything you need & some]72813

[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

Asus ZenFone Live - Install Fail

Hello,
I Would install Magisk in my Asus ZenFone Live ZB501KL (bootloader unlock), I have an error in the verification of the archive ...
Can You help me ^^'
Thank's
(Sorry for my bad english i'm french ...)
Install/recovery log are useful additions to a query about installation errors. Please provide.
Didgeridoohan said:
Install/recovery log are useful additions to a query about installation errors. Please provide.
Click to expand...
Click to collapse
Where i can find this ?
voxan24 said:
Where i can find this ?
Click to expand...
Click to collapse
Click the link...
Didgeridoohan said:
Click the link...
Click to expand...
Click to collapse
Sorry my Phone dosnt would open thé link ? i senden it
voxan24 said:
Sorry my Phone dosnt would open thé link i senden it
Click to expand...
Click to collapse
I'm not sure what you mean, but I'm talking about the link in my first reply to you:
https://www.didgeridoohan.com/magisk/MagiskHelp
Didgeridoohan said:
I'm not sure what you mean, but I'm talking about the link in my first reply to you:
https://www.didgeridoohan.com/magisk/MagiskHelp
Click to expand...
Click to collapse
Despite the site I still can not register the log: /
voxan24 said:
Despite the site I still can not register the log: /
Click to expand...
Click to collapse
Unfortunately, that means it'll be really hard to help, since we have no way of knowing what's actually going on.
Didgeridoohan said:
Unfortunately, that means it'll be really hard to help, since we have no way of knowing what's actually going on.
Click to expand...
Click to collapse
If I can read this:
Supported API: 3
Battery remains 97 percent
--Install /sdcard/Magisk-v16.0.zip ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
voxan24 said:
If I can read this:
Supported API: 3
Battery remains 97 percent
--Install /sdcard/Magisk-v16.0.zip ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
Are you trying to install Magisk through the stock recovery? If so, that won't work... You need to use a custom recovery (like TWRP), or failing that you can let the Magisk Manager patch a copy of your device's boot image. Then you can manually flash the patched boot image with fastboot.
Code:
fastboot flash boot patched_boot.img
There are further instructions in the release thread.
Didgeridoohan said:
Unfortunately, that means it'll be really hard to help, since we have no way of knowing what's actually going on.
Click to expand...
Click to collapse
Didgeridoohan said:
Are you trying to install Magisk through the stock recovery? If so, that won't work... You need to use a custom recovery (like TWRP), or failing that you can let the Magisk Manager patch a copy of your device's boot image. Then you can manually flash the patched boot image with fastboot.
Code:
fastboot flash boot patched_boot.img
There are further instructions in the release thread.
Click to expand...
Click to collapse
TWRP is not avaible for my device and i dosn't have the original boot.img ... Asus dosn't give this :/
I Download the last Update package, we never know
{
"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"
}
voxan24 said:
TWRP is not avaible for my device and i dosn't have the original boot.img ... Asus dosn't give this :/
I Download the last Update package, we never know
Click to expand...
Click to collapse
Inside the firmware zip (you can also find them all here: https://www.asus.com/Phone/ZenFone-Live-ZB501KL/HelpDesk_BIOS/) you'll find the boot.img file. That's the file you need to place on your internal storage and then patch it with the Manager. Then copy it to your computer and flash it manually.
Didgeridoohan said:
Inside the firmware zip (you can also find them all here: https://www.asus.com/Phone/ZenFone-Live-ZB501KL/HelpDesk_BIOS/) you'll find the boot.img file. That's the file you need to place on your internal storage and then patch it with the Manager. Then copy it to your computer and flash it manually.
Click to expand...
Click to collapse
Thx it's work, but i dosn't can update my phone now
voxan24 said:
Thx it's work, but i dosn't can update my phone now
Click to expand...
Click to collapse
You'll probably have to restore the stock boot image before updating. Then, when you're all updated, you patch the new boot image (from the new firmware zip) and flash it to your device.
If you would the patched boot image (Rom V.WW-13.1407.1801.57) : [URL="h...[/URL] Link Dead
voxan24 said:
If you would the patched boot image (Rom V.WW-13.1407.1801.57) : http://voxan24.be/dok/Öffentliches/patched_boot.img
Click to expand...
Click to collapse
I'm sorry, I don't understand what you want me to do with that... And really, there's nothing I can do with it.
Edit: Ah... You're providing the image for other Zenfone Live users, aren't you?
Didgeridoohan said:
I'm sorry, I don't understand what you want me to do with that... And really, there's nothing I can do with it.
Edit: Ah... You're providing the image for other Zenfone Live users, aren't you?
Click to expand...
Click to collapse
Absolutely
Update: For WW-13.1407.1804.64 Version : patched_boot.img

Tutorial How to root ZTE z835 (Maven 3) with Magisk.

DISCLAIMER: I AM NOT RESPONSIBLE FOR WHAT MAY HAPPEN TO YOUR DEVICE, DO THIS AT YOUR OWN RISK.
Before I start: everything I'm going to post here, I learned from this thread: https://forum.xda-developers.com/maven-3/help/zte-maven-3-z835-root-t3705687/page9
VERSION OF MAGISK FLASHEAD v17.1 (Unfortunately no one has flashed version v18.1)
What we need (they will be in the links at the end):
-ZPST for AT&T (with this program we are going to flash the modified boot.img)
-Drivers: QDLoader, ZTE AndroidUSB and ZTE_V889F (in case the previous Zte driver does not work).
-Modified boot.img that are already flashed with Magisk, only the following versions are available:
-Z835V2.0.0B10
-Z835V2.0.0B12
-Z835V1.0.0B13
-Magisk Manager version compatible with v17.1
EVERYTHING YOU NEED IS IN A LINK AT THE END OF THE POST.
Let's get started.
I recommend to do a hard reset before starting, however, in one of my devices I did it having data and applications installed, if you have used kingroot or any other software in your phone, erase all trace of it so you do not have problems.
We download all the contents of the folder, install all drivers included, and the ZPST for AT&T.
Starting to flash:
WE NEED AT LEAST 50-60% of Battery
Turn off the phone and turn on pressing Vol Down + Power Button, the phone will start in FTM mode.
Open ZPST for AT&T and select version Z835
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING, remove the usim and sd card
Once inside the software we proceed to connect the cell phone.
1. You will see if the phone was recognized by the com port.
2. Download, this is where we will enter to download the firmware
3. You will see your information imei and so on.
This is how it will look once connected (Let's go to the download tab)
1. Let's select the firmware (it has to be the same as the cell phone otherwise it can corrupt the imei)
2. We chose where to keep a small log to check if everything went well.
3. HIT THE DOWNLOAD BUTTON!!!!!
WARNING: wait for the device to restart at least 2 or 3 times, one of them will be in FTM mode again, so do not panic, it will take a while in 3% or 5%.
When the phone starts normally, if you did a hard reset configure everything again, otherwise, we will proceed to install the magisk.
DO NOT INSERT THE SD CARD YET!
Magisk asks if I want to update to the latest version, press NO THANKS.
Proceed to uninstall
Now let's install the version of magisk manager we downloaded (com.topjohnwu.magisk_6.1.0-165_minAPI21(nodpi)_apkmirror.com.apk)
When the installation is finished we enter Magisk and this will ask us if we want to upgrade to the latest version, PRESS NO!
Now we will see that magisk is installed correctly.
We see that we can use all its functions.
We will proceed to verify if we have root access.
Download root checker
And Voila!
MEGA link: https://mega.nz/#F!ud8VwKRJ!-cJr7EJyhb1PkziNx5KvLQ
with this can you uninstall original system's apps such as device help, google apps? install recovery and titanium backup? I need to remove a lot of bloatware/default apps that is taking memory from the device
nvizync said:
Root
Click to expand...
Click to collapse
Nice work! This confirms that the bootloader is unlocked, which means we can then use just the firehose to flash these files. I will work on writing something up for that.
deadman96385 said:
Nice work! This confirms that the bootloader is unlocked, which means we can then use just the firehose to flash these files. I will work on writing something up for that.
Click to expand...
Click to collapse
Would love to see that, thanks for the reply! :good:
rickastillo said:
with this can you uninstall original system's apps such as device help, google apps? install recovery and titanium backup? I need to remove a lot of bloatware/default apps that is taking memory from the device
Click to expand...
Click to collapse
You can install titanium backup, twrp is not possible at this point, no one has done it yet, you can delete system apps through adb, using
Code:
adb shell pm uninstall -k --user 0 packagename
But i haven't figured out yet how to get rw permission on system/apps so i can delete system apk's.
@nvizync You should thank me for my boot.img mod of -Z835V2.0.0B10 (Magisk 17.1)
my boot.img mod of:
-Z835V1.0.0B13 (Magisk 18.1) Link: https://mega.nz/#F!88IiFapI!6Peah7woOOaIhusfYCAEcw
-Z835V2.0.0B10 (Magisk 18.1) link: https://mega.nz/#F!V4pAVIYQ!19tWE7_xk_aQtyiu050Y7A
-Z835V2.0.0B12 (Magisk 18.1) Link: https://mega.nz/#F!9lBVkQAZ!WqnRvYa4qcw5MgRxhp1hcA
Thanks for your detailed flash root tutorial
Alijosekt said:
@nvizync You should thank me for my boot.img mod of -Z835V2.0.0B10 (Magisk 17.1)
my boot.img mod of:
-Z835V2.0.0B10 (Magisk 18.1) link: https://mega.nz/#F!V4pAVIYQ!19tWE7_xk_aQtyiu050Y7A
-Z835V2.0.0B12 (Magisk 18.1) Link: https://mega.nz/#F!9lBVkQAZ!WqnRvYa4qcw5MgRxhp1hcA
Thanks for your detailed flash root guide
Click to expand...
Click to collapse
I totally forgot it, yeah, you deserve most of the credit, I linked the original thread, but I'm planning including all the credits.
@nvizync Look what I got! https://github.com/TwrpBuilderTests/android_device_zte_z835/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Alijosekt said:
@nvizync Look what I got! https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Click to expand...
Click to collapse
Ok my way
nvizync said:
Ok my way
Click to expand...
Click to collapse
not boot twrp
Alijosekt said:
not boot twrp
Click to expand...
Click to collapse
Did you tried it
Alijosekt said:
@nvizync Look what I got! https://github.com/TwrpBuilderTests/android_device_zte_z835/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Click to expand...
Click to collapse
I tried to flash it, but instead, I just got a bootloop, and I can't access the recovery mode anymore, I should flash the original recovery and see if it works.
nvizync said:
I tried to flash it, but instead, I just got a bootloop, and I can't access the recovery mode anymore, I should flash the original recovery and see if it works.
Click to expand...
Click to collapse
Done, i managed to enter in normal mode and use flashify to flash stock recovery.img.
Hi, I'm stuck at the first step. The ZPST download fails with the message that it can't find the file: sbl1.mbn Any thoughts?
penn462 said:
Hi, I'm stuck at the first step. The ZPST download fails with the message that it can't find the file: sbl1.mbn Any thoughts?
Click to expand...
Click to collapse
Are you using the custom boot.img listed in mega's folder?
nvizync said:
Are you using the custom boot.img listed in mega's folder?
Click to expand...
Click to collapse
Yes. I'm using the folder "Boot Mod Z835V1.0.0B13"
penn462 said:
Yes. I'm using the folder "Boot Mod Z835V1.0.0B13"
Click to expand...
Click to collapse
Thats odd, try this: download another folder B12 or B10, and just paste the B13 boot.img, maybe that could work, one of the devices i rooted was B13.
Well, I tried what you suggested, and now I get "download failed" and "failed to change mode before downloading firmware" It seems to be stuck in FTM. I guess it's bricked?
---------- Post added at 06:52 PM ---------- Previous post was at 06:48 PM ----------
Update: not bricked. Gonna try again.
penn462 said:
Well, I tried what you suggested, and now I get "download failed" and "failed to change mode before downloading firmware" It seems to be stuck in FTM. I guess it's bricked?
Click to expand...
Click to collapse
Fear not, that happened to me also, just keep in ftm and make a stock boot.img flash, provided in the mega folder. Paste the boot stock image inside the b13 folder
Placed stock boot.img into B13 folder in place of custom boot.img. The process failure point is now back to the missing sbl1.mbn problem. I can get the phone to start, however, so it's not bricked. Whew!

[MAGISK][Android 10]Patched Boot Image For OnePlus 7 Pro

Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk.
Recommended to patch your own image read this
Grab the latest Platform Tools HERE
Code:
1. Download a stock Oxygen OS ROM Zip from [URL="https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156267635"]Here[/URL] Or the general section of XDA many users post links to the latest builds.
2. Download [URL="https://androidfilehost.com/?fid=818070582850510260"]payload_dumper-win64.zip[/URL] And extract/copy it to Desktop.
3. Extract your payload.bin from the stock rom zip and copy it into the payload_input folder.
4. Run the payload_dumper exe.
5. When it's finished open the payload_output folder and copy the boot.img to Desktop keep it there as a backup.
6. Copy the same boot.img to your internal storage on your phone.
7. Install the magisk manager APK from here: [URL="https://github.com/topjohnwu/Magisk"]Magisk Manager[/URL]
8. Open Magisk Manager choose install and select "Select and Patch a file" Or if you wish to use beta release go to settings > Update Channel and switch to beta and then back to Install "Select And Patch A File"
9. Navigate to where you copied your boot.img on the phone.
10. Once it's patched you'll have an magisk_patched.img on your phone in the the Downloads folder.
11. Copy that image to your fastboot folder on your PC and flash it with fastboot flash boot magisk_patched.img
Done!
As always I'm not responsible for any issues your device might have or if your cat sets on fire.
Credits:
topjohnwu for Magisk/Manger
geminids14 for payload_dumper-win64
Nice, that is what we need .. Thanks Liam
How can i load twrp? Fastboot boot command, didnt work
DevrimSeven60 said:
How can i load twrp? Fastboot boot command, didnt work
Click to expand...
Click to collapse
Ask in the TWRP thread
Not working for me get a error file is to large to download when try to flash
dajumper said:
Not working for me get a error file is to large to download when try to flash
Click to expand...
Click to collapse
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
liam_davenport said:
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Still the same
Im already rooted with bootimg having lat pie release. Is it possible to flash Android Q on top of last pie release and be rooted? Again I am rooted with magisk, not having twrp.
To update I always flash full updat from local, not reboot, install magisk to other slot and I was ready to go.
Will this work with Q update?
Not working for me. Both sims dissapear and phone keeps FC.
pister said:
Not working for me. Both sims dissapear and phone keeps FC.
Click to expand...
Click to collapse
Issue is on your end, I've flashed this multiple times no issue.
Working perfectly here I've clean flashed and redownloaded from the link and flashed. I've noticed sometime magisk causes sims to not show on boot before reboot the device and they should show again.
{
"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"
}
I see that when I root, both IMEIs disappears. Very strange
Sent from my [device_name] using XDA-Developers Legacy app
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
pister said:
I see that when I root, both IMEIs disappears. Very strange
Click to expand...
Click to collapse
Mine both show. Not sure why yours have disappeared
liam_davenport said:
Mine both show. Not sure why yours have disappeared
Click to expand...
Click to collapse
Don't know. Tried to root by myself and the same happened
Sent from my [device_name] using XDA-Developers Legacy app
NateDev said:
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
Click to expand...
Click to collapse
If you have twrp already you don't need this I posted this for people that want root without using twrp, Just flash magisk 19.4 in twrp
There is a few guides in this forum section with all info you need on how to flash etc
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
mgear356 said:
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
Click to expand...
Click to collapse
You flashed it on Open beta 1?
liam_davenport said:
You flashed it on Open beta 1?
Click to expand...
Click to collapse
Yup open beta 1
Great thanks!
But can we update OTA to B2 with this?
@liam_davenport I'm sorry for the noob question, I just got my OP 7 Pro and never used one before, also, I've been away from everything root related for a long time.
Do I need to unlock the bootloader first in order to do this?

.backup file

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

Categories

Resources