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.
Related
I wanted to run a 4.4 KitKat GE rom on my HTC One, therefore I decided to unlock my bootloader, install twrp, and flash the rom. So far all i did was unlock my bootloader. Then I proceeded to flash twrp recovery via a command prompt? on my desktop. But I kept getting an error message. I attached a picture of the message I am receiving. I read on the twrp recovery teams site that I need to have S-off before flash TWRP soooo I thought this is what was causing the error. I proceeded to change my S-On to S-Off using rumrunner but then I got an error message there saying I need to be rooted. SOOOOOO now I'm at a standstill and I don't know how to get TWRP recovery onto my device. I'm new to this device and this whole unlocking/rooting thing...Please help!
{
"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"
}
BTW I have USB debugging on and the fast boot option under power settings checked off. I have tried clearing cache also via cmd prompt 'fastboot clear cache'
Sent from my HTC One using xda app-developers app
cloud628 said:
I wanted to run a 4.4 KitKat GE rom on my HTC One, therefore I decided to unlock my bootloader, install twrp, and flash the rom. So far all i did was unlock my bootloader. Then I proceeded to flash twrp recovery via a command prompt? on my desktop. But I kept getting an error message. I attached a picture of the message I am receiving. I read on the twrp recovery teams site that I need to have S-off before flash TWRP soooo I thought this is what was causing the error. I proceeded to change my S-On to S-Off using rumrunner but then I got an error message there saying I need to be rooted. SOOOOOO now I'm at a standstill and I don't know how to get TWRP recovery onto my device. I'm new to this device and this whole unlocking/rooting thing...Please help! View attachment 2429761
Click to expand...
Click to collapse
First to clarify things:
you don't need to be s-off to flash a custom recovery just need unlocked bootloader
you need a custom recovery to root
you need root to s-off
so you need a custom recovery first in order to achieve s-off
The picture you attached tells me fastboot isn't finding the file ''twrp,img'' from your command line ''fastboot flash recovery twrp.img
in most cases because:
your recovery.img file is not in the ''platform-tools'' folder that contain adb.exe and fastboot.exe
the file name of your recovery is not twrp.img
Code:
fastboot flash recovery ''name_of_your_recovery_file.img''
fastboot erase cache
fastboot reboot-bootloader
i'll just leave this here: "cannot load" means the filename is WRONG!!! that's all
cya
okay I'll will give it a go with the suggestions tonight and update this thread with my results
Sent from my HTC One using xda app-developers app
So did I set this up correctly now? And I just open the CMD prompt window up from inside this domain and type "fastboot flash recovery "paste file name here" ? View attachment 2431242
So I just tried again....same error
I downloaded the newest SDK batch files and attempted again. Now I get a different error message.
cloud628 said:
I downloaded the newest SDK batch files and attempted again. Now I get a different error message. View attachment 2431302
Click to expand...
Click to collapse
Please no more screenshot! Just copy/paste command prompt (only the text)
Anyway, u have a .img.img (double extension)
Again, cannot load means filename is wrong!
nkk71 said:
Please no more screenshot! Just copy/paste command prompt (only the text)
Anyway, u have a .img.img (double extension)
Again, cannot load means filename is wrong!
Click to expand...
Click to collapse
Sorry about the screenshots, But where is there a double .img.img extension.....I only have it there once. I literally downloaded the image file from team wins website, saved it into the same folder containing the adb and fastboot files. I didnt change anything in the file name. Then i proceeded to Enter into the CMD window "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7" and I also tried "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" Both do not work.
C:\Users\dshi----\Desktop\sdk\platform-tools>fastboot devices
FA-----10153 fastboot
C:\Users\dshi----\Desktop\sdk\platform-tools>fastboot flash recovery openrecover
y-twrp-2.6.3.3-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.3-m7.img'
C:\Users\dshi----\Desktop\sdk\platform-tools>fastboot flash recovery C:\Users\ds
hi----\Desktop\openrecovery-twrp-2.6.3.3-m7.img
error: cannot open 'C:\Users\dshi----\Desktop\openrecovery-twrp-2.6.3.3-m7.img'
C:\Users\dshin---\Desktop\sdk\platform-tools>fastboot flash recovery openrecover
y-twrp-2.6.3.3-m7
error: cannot open 'openrecovery-twrp-2.6.3.3-m7'
nkk71 said:
Please no more screenshot! Just copy/paste command prompt (only the text)
Anyway, u have a .img.img (double extension)
Again, cannot load means filename is wrong!
Click to expand...
Click to collapse
OHHHHH!!!! It worked!. Now I get it! Jeeeze that was absolutely frustrating but now I know. Thank You SOOOOO Much!
cloud628 said:
Sorry about the screenshots, But where is there a double .img.img extension.....I only have it there once. I literally downloaded the image file from team wins website, saved it into the same folder containing the adb and fastboot files. I didnt change anything in the file name. Then i proceeded to Enter into the CMD window "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7" and I also tried "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" Both do not work.
Click to expand...
Click to collapse
It's not about about the screenshots, just reading them on a phone, is not easy! Anyway:
1- have u placed the recovery.img I'm ur adb folder?
2- did u do a"dir" to see the full filenames?
Sent from my HTC One using Tapatalk
thanks a ton!
nkk71 said:
It's not about about the screenshots, just reading them on a phone, is not easy! Anyway:
1- have u placed the recovery.img I'm ur adb folder?
2- did u do a"dir" to see the full filenames?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
So it's December 2016 and I was running into a very similar error. Doing the dir command showed I had a double ".img" on my file as well. Fixed that, and I'm back in business. Thanks so much!
Hi Guys, just an FYI, i'm leaving here the link to download the current versions of TWRP IMG
SITE: https://twrp.me/
Regards!
asmallmammal said:
So it's December 2016 and I was running into a very similar error. Doing the dir command showed I had a double ".img" on my file as well. Fixed that, and I'm back in business. Thanks so much!
Click to expand...
Click to collapse
please tell how you fix that i have the same problem
Just rename the file without typing in ".img" at it should be ok.
So in explorer, rename the file simply "twrp" and hit enter. There will be a ".img" extension on the file, but you won't see it. To make sure it's been corrected, run the dir command and it should show "twrp.img" even though the file doesn't have the ".img" when you look at it in explorer.
Does that make sense?
How to show/hide file extension
For Windows Vista, Windows 7, and Windows Server 2008
Start Windows Explorer, you can do this by opening up any folder.
Click Organize.
Click Folder and search options.
Click the View tab.
Scroll down until you notice Hide extensions for known file types, un-check this line by clicking the check box.
Note To hide file name extensions, check this line.
Click OK
For Windows 2000, Windows XP, and Windows Server 2003
Start Windows Explorer, you can do this by opening up any folder.
Click Tools, and then click Folder Options.
Scroll down and then click Folder and search options.
Click the View tab.
Scroll down until you notice Hide extensions for known file types, un-check this line by clicking the check box.
https://support.microsoft.com/en-us/kb/865219
what is it for htc at play?
hey guys.
My M7 is stuck in the bootloop. I tried to install a new rom like 2 years ago and it didnt worked out, but i already had a new phone, so i didnt care too much. now id like to reactivate my old m7 but dont know how.
here is a link to a picture of my fastboot
imgur.com/tzQe7Xi
Im running Windows 10 on my computer
thanks in advance
zuppiger said:
hey guys.
My M7 is stuck in the bootloop. I tried to install a new rom like 2 years ago and it didnt worked out, but i already had a new phone, so i didnt care too much. now id like to reactivate my old m7 but dont know how.
here is a link to a picture of my fastboot
imgur.com/tzQe7Xi
Im running Windows 10 on my computer
thanks in advance
Click to expand...
Click to collapse
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Boot into recovery and connect your phone to the PC.
Download any ROM from the forum, transfer it to the phone and flash it. Don`t since we don`t know anything about your previous ROM wipe cache, dalvik, data and system before flashing your chosen ROM.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.
proone said:
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Boot into recovery and connect your phone to the PC.
Download any ROM from the forum, transfer it to the phone and flash it. Don`t since we don`t know anything about your previous ROM wipe cache, dalvik, data and system before flashing your chosen ROM.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.
Click to expand...
Click to collapse
No need to extract anything. S-on doesn't matter for kernel flashing on this phone. So, flash ROM.zip and enjoy
proone said:
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery-file-name.img
fastboot erase cache
fastboot reboot-bootloader
Always erase the cache and reboot the bootloader after flashing a recovery to avoid problems booting the recovery.
Download any ROM from the forum
Click to expand...
Click to collapse
"any ROM" from the forum won't work on his phone. For example, his actual firmware is way to old to run roms based on Sense + Lollipop. With this firmware version (2.24.401.8), he is limited to JellyBean or Kitkat Roms.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.
Click to expand...
Click to collapse
Won't hurt but not needed on the M7 (unlike some other HTC phones). The kernel partition isn't secured and is flashed with the rom from twrp.
@zuppiger
If you want the phone back to stock and be able to intall ota updates (or if you want to install a custom lollipop + sense rom), flash this rom using twrp recovery. Select "yes" for stock recovery and stock radio, select "no" to root. then reboot the phone to the OS, install all the ota updates (a lot) until your version is 7.19.401.30. Then you can use the phone like this or you'll be ready to flash a lollipop custom rom. Otherwise you can go like suggested above but with older (JB or KitKat) Sense rom or any CM/AOSP roms.
Thanks guys.
but i think i might need some more help.
i downloaded the sdk manager to install TWRP, but when i try to write "adb reboot bootloader" it says "is not recognized as an internal or external command, operable program or batch file" (not entirly sure if this is the correct translation, in german it says the command is either wrong or could not be found)
i think it could be because of some driver issues.
any advice??
zuppiger said:
Thanks guys.
but i think i might need some more help.
i downloaded the sdk manager to install TWRP, but when i try to write "adb reboot bootloader" it says "is not recognized as an internal or external command, operable program or batch file" (not entirly sure if this is the correct translation, in german it says the command is either wrong or could not be found)
i think it could be because of some driver issues.
any advice??
Click to expand...
Click to collapse
Download the android sdk tools:
https://developer.android.com/sdk/index.html#Other
Make sure you have the latest htc drivers installed:
http://www.mediafire.com/download/2lyl151pt5pah2v
Make sure you don't have HTC Sync installed on your computer, if yes, uninstall it since it will interfere with fastboot/adb commands
To use adb or fastboot commands, open a command window from the same folder where adb.exe and fastboot.exe are located on your computer (C::\Programs\Android SDK Tools\platform-tools). To start a command window from this folder, hold your left "shift" key and right click a blank space in that folder, then in the contextual menu, select "open a command window here".
Don't forget that adb commands can only works when the phone is booted in the OS with "USB debugging" turned on from the developer option menu or from a custom recovery. Fastboot commands only works from the bootloader (in the fastboot menu).
{
"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"
}
alray said:
Download the android sdk tools:
https://developer.android.com/sdk/index.html#Other
Make sure you have the latest htc drivers installed:
http://www.mediafire.com/download/2lyl151pt5pah2v
Make sure you don't have HTC Sync installed on your computer, if yes, uninstall it since it will interfere with fastboot/adb commands
To use adb or fastboot commands, open a command window from the same folder where adb.exe and fastboot.exe are located on your computer (C::\Programs\Android SDK Tools\platform-tools). To start a command window from this folder, hold your left "shift" key and right click a blank space in that folder, then in the contextual menu, select "open a command window here".
Don't forget that adb commands can only when the phone is booted in the OS with "USB debugging" turned on from the developer option menu or from a custom recovery. Fastboot commands only works from the bootloader (in the fastboot menu).
Click to expand...
Click to collapse
Thanks. I installed everything like explained.
It worked better this time, but now I get "waiting for device".
On the phone itself it says "FASTBOOT USB"
zuppiger said:
but now I get "waiting for device".
Click to expand...
Click to collapse
When using what command?
alray said:
When using what command?
Click to expand...
Click to collapse
"fastboot flash recovery c:\twrp.img"
zuppiger said:
"fastboot flash recovery c:\twrp.img"
Click to expand...
Click to collapse
what is the output of "fastboot devices" ?
alray said:
what is the output of "fastboot devices" ?
Click to expand...
Click to collapse
Nothing.
I made the command again in the platform-tools folder
Anyone some more help? :good:
zuppiger said:
Anyone some more help? :good:
Click to expand...
Click to collapse
Well without any connectivity to the phone there is nothing we can do unfortunately. Might worth to try on another computer. Otherwise if you are 100% sure that the problem isn't the usb cable, the drivers or the computer then the phone usb port might be broken. This can be replaced (probably the "easiest" part to replace on that phone), you'll need to open the cover and replace that small usb/front mic board.
But the fact that your phone says FASTBOOT USB when in bootloader makes me believe its more a driver/computer problem since it would only says FASTBOOT if there were no connection detected...
thanks a lot for your help. I don't think I will get it working again anytime soon.
But i will look for a way
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
{
"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"
}
System Image: https://drive.google.com/file/d/1cAcgP55upO6UuX-gecPIXA_xnO0IXvUO/view?usp=sharing
Flash System Image:
- Download the appropriate system image for the Razer Phone from here, then unzip it to a safe directory.
- Connect your Razer Phone to your computer over USB.
- Start the Phone in Download Mode with one of the following methods:
- Using the adb tool: With the Phone powered on, execute: adb reboot bootloader
- Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
- If necessary, unlock the Phone’s bootloader. See Unlocking the Bootloader and Unlocking the Bootloader Critical Partitions for instructions.
- Open a terminal on your computer and navigate to the unzipped system image directory.
- Execute the flash_all script. This script installs the necessary bootloader, baseband firmware(s), and operating system for your Razer Phone.
- Once the script finishes, your Phone will reboot.
- You should now lock the bootloader for security.
Is this the global version?
Also, is there a list regarding the detail of each img file, and that whether they're considered safe to be flashed/updated?
LSS4181 said:
Is this the global version?
Also, is there a list regarding the detail of each img file, and that whether they're considered safe to be flashed/updated?
Click to expand...
Click to collapse
Yes very much so global
#1 - I can't read his info screenshot :silly: & #2 it's the same build number
I haven't flashed it personally but I would go out on a limb and say it's safe to flash
JDBarlow said:
Yes very much so global
#1 - I can't read his info screenshot :silly: & #2 it's the same build number
I haven't flashed it personally but I would go out on a limb and say it's safe to flash
Click to expand...
Click to collapse
I mean the detail of each img file. Since I'm now on a GSI I've only flashed the updated vendor.img so far (in my case, from MR1 to MR2). I'm not sure about other non-system parts (something like bluetooth, dsp, which are probably firmware blobs), and whether these are safe to be flashed/updated (however, some of those blobs do have diffs in the OTA).
LSS4181 said:
I mean the detail of each img file. Since I'm now on a GSI I've only flashed the updated vendor.img so far (in my case, from MR1 to MR2). I'm not sure about other non-system parts (something like bluetooth, dsp, which are probably firmware blobs), and whether these are safe to be flashed/updated (however, some of those blobs do have diffs in the OTA).
Click to expand...
Click to collapse
I see what you're saying
SMS working fine on the GSI you're running? I believe I read somewhere that someone was able to get latest Havoc to work
JDBarlow said:
I see what you're saying
SMS working fine on the GSI you're running? I believe I read somewhere that someone was able to get latest Havoc to work
Click to expand...
Click to collapse
I'm on Havoc 3.2.
Actually it was thanks to Reznor7's advice (first install it as a normal app, then move the installed folder to system) that I was able to get most of the things working (SMS, VoLTE).
LSS4181 said:
I'm on Havoc 3.2.
Actually it was thanks to Reznor7's advice (first install it as a normal app, then move the installed folder to system) that I was able to get most of the things working (SMS, VoLTE).
Click to expand...
Click to collapse
Perfect.
I can confirm this image does work ?
Something odd happened after flashing Havoc 3.3 I pulled my SIM card and reinsert it in the phone and my SIM card stopped working. I had to replace it ?
JDBarlow said:
Perfect.
I can confirm this image does work ?
Something odd happened after flashing Havoc 3.3 I pulled my SIM card and reinsert it in the phone and my SIM card stopped working. I had to replace it ?
Click to expand...
Click to collapse
Where did you get Havoc 3.3? Even ExpressLuke hasn't any Havoc 3.3 GSI build for ARM64/AB from what I could see (the SourceForge page still lists the 3.2 one as the latest).
LSS4181 said:
Where did you get Havoc 3.3? Even ExpressLuke hasn't any Havoc 3.3 GSI build for ARM64/AB from what I could see (the SourceForge page still lists the 3.2 one as the latest).
Click to expand...
Click to collapse
/HavocOS/Ten/20200402-vanilla/Havoc-OS-v3.3-20200402-arm64-ab-vanilla-nosu.img.xz
If anyone can get havoc 3.3 to work on Verizon without the sim card issue please let me know. No gsi rom will work on Verizon. Its frustrating. Thanks.
Finally got the MR3 update extracted
I worked all night extracting/converting the stock img and got beat by minutes posting Lol... anyway I also have the stock ota for global variant of MR3 if anyone needs it. You can easily patch the boot img with magisk and fastboot flash boot_a with the patched boot img and you have root again on MR3 Update. Works flawless
i Take a copy Thank You
Flashed some stuffs from MR3: modem (both), bluetooth (both), dsp (both), vendor (both), boot (inactive B slot only), system (inactive B slot only). These seem to work.
However, when flashing system and vendor I saw it mentioned something about "invalid sparse file format at header magic", but the flashed stuffs (at least vendor) looks fine.
Also, not sure if it's because of my Linux distro's (Manjaro/Arch) fastboot version or some other reasons (the cables are fine), I could only properly issue a fastboot command right after the phone restarted to bootloader. After that, the commands would stuck at Sending. Ctrl-C won't work at this point. I could only get out by unplugging the cable, and after that the phone won't be detected until I restart the bootloader again (if I issue a fastboot command here, it'll show <waiting for device>, but when the phone restarted, the command would begin and succeed).
Havoc 3.3 GSI works fine here (the SELinux fix may still be needed for it to boot). However, for some reasons (either due to recent Magisk canary update, or something else), I lost access to VoLTE and that after updating to the new GSI version, all my app's permissions were lost and I need to reassign them (maybe it's time I back things up and start over again, as the permission reset issue can indeed happen when dirty-flashing newer GSI versions).
LSS4181 said:
Also, not sure if it's because of my Linux distro's (Manjaro/Arch) fastboot version or some other reasons (the cables are fine), I could only properly issue a fastboot command right after the phone restarted to bootloader. After that, the commands would stuck at Sending. Ctrl-C won't work at this point. I could only get out by unplugging the cable, and after that the phone won't be detected until I restart the bootloader again (if I issue a fastboot command here, it'll show <waiting for device>, but when the phone restarted, the command would begin and succeed).
Click to expand...
Click to collapse
Running Manjaro Linux here too and experience the same behaviour.
Peace.
Can you dirty flash the mentioned images? Don't really feel like reinstalling all my apps and data.
is there a new root method
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Cheers Mystix
MystixBlack said:
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Those usb drivers didn't work for me. What did work however was the samsung usb drivers so I downloaded them and installed, however that wasn't enough. While in fastboot mode under device manager, I can't recall how I installed it but I forced the driver either from android device in list or added new legacy hardware and installed samsung android adb interface. After that when I typed fastboot devices in console from tools folder it reported back for me. I hope this helps.
Click to expand...
Click to collapse
I have 2 questions.
1. Can you flash this on other builds?
2. can any one link to P-SMR3-RC002-CKH-200226.3132 Build
Very much appriciated :good:
MystixBlack said:
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Cheers Mystix
Click to expand...
Click to collapse
I u forgot something....
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Xinfuzemodz said:
I have 2 questions.
1. Can you flash this on other builds?
2. can any one link to P-SMR3-RC002-CKH-200226.3132 Build
Very much appriciated :good:
Click to expand...
Click to collapse
Are you serious? The link of the OP is the link to MR3. If you click the flash_all.bat file it will wipe your phone and you get a fresh copy of MR3 installed so yes it can be installed on other builds
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