Related
Tools
1. Flash Tools for HTC Magic (inculed USB driver, Fastboot.exe, nandroid img) HTC_G2_TOOL.rar http://www.hiapk.com/bbs/download.p...e825b983cad5661d08bef017c59522a12d38ed3f63b09
2. SDK Tools AdbWin.zip (adb for Windows)
3. SPL HBOOT Rom http://forum.xda-developers.com/showthread.php?t=529019
4. USB Cable
How to check your SPL Version
1. Power off your phone
2. Push “Back” + “Power” about 5s (**After that you should see three androids on skateboards)
3. Check your version and go here (http://forum.xda-developers.com/showthread.php?t=529019) download a downgrade version. (In my case, I will download Modded HBOOT-1.33.2004)
My HTC Magic SPL info:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
May 8 2009,21:02:32
How to go Recovery model:
1. Put the files Adb and AdbWinApi.dll from AdWin.zip into C:\WINDOWS\System32 folder on your PC. Substitute the correct drive letter if windows is not installed on you C: drive
2. Put the Windows Fastboot.exe into the C:\WINDOWS\System32 folder on your PC
3. Create a folder on the C: drive of your PC called android. The path should be C:\Android and unzip HTC_G2_TOOL.zip into C:\Android.
4. Unplug the USB cord and power off your phone
5. Power up your phone by holding “Black” + “Power” , you should see three androids on skateboards.
6. Plug the USB cord back into your phone. The screen on your phone should say fastboot.
7. Make sure your pc is using the correct driver. Open the device manager on your pc. It is helpfull to have all other USB storage devices besides your phone unplugged for this part. Look for a USB Mass Storage device in the list of the USB devices. Right click on it and update the driver. Pick the option to browse for a driver on your pc. The driver is located in HTC_G2_TOOL.rar.
8. Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
9. Type cd C:\android
10. then enter the following command C:\android > fastboot boot recovery.img
11. Your phone should now be reboot and booting in Recovery model
How to Backup your Rom:
1. After booting into recovery model
2. select [Alt+B] – Nandroid Backup 2.1
3. After few minutes all backup file will save in your SD card
How to restore from your backup file
1. Download one of the above signed SPL updates and rename it to update.zip
2. Copy update.zip to the root of your SD-card
3. Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder C:\Android.
4. booting your Magic into recovery model
5. select [Alt + S] – Apply sdcard:update.zip
6. select [Home + Back] – reboot system now
7. After reboot it will update upgrade/downgrade your SPL version, then power off your Magic again
8. Push “Back” + “Power” to HBOOT model
9. double check your SPL version is upgrate/downgrate
10. Plug the USB cord back into your phone. The screen on your phone should say fastboot.
12. Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
13. Type cd C:\android
11. then enter the following commands C:\android >
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
12. After reboot your Magic, it need about 2-5 min to restore
13. then a band new original Android 1.5 is restored
Remark:
**Please make sure your battery got enough power (Suggestion: more than 50%)
where is the restore img?
You can backup from your Phone~~
Hi there toneytse!
I have the exact same SPL/Hardware. The guide is extremely useful therefore, as it eliminated any doubt I had about the procedure, so thank you for that. I need a small clarification, though, if you care to oblige.
In order for the warranty to be valid no "tampering" must be evident, so if at some point I need to return the device for repair I will need to be able to replace the SPL (as well as the Nandroid backup) to the original ones.
How can I be sure that the provided signed SPLs are exactly-bit wise identical to the original one? Is there a way to back my own SPL (in case it is slightly different) instead of using one the signed provided ones? Or shouldn't I worry since all the SPLs with identical specs are actually identical?
Cheers
rayg256 said:
Hi there toneytse!
I have the exact same SPL/Hardware. The guide is extremely useful therefore, as it eliminated any doubt I had about the procedure, so thank you for that. I need a small clarification, though, if you care to oblige.
In order for the warranty to be valid no "tampering" must be evident, so if at some point I need to return the device for repair I will need to be able to replace the SPL (as well as the Nandroid backup) to the original ones.
How can I be sure that the provided signed SPLs are exactly-bit wise identical to the original one? Is there a way to back my own SPL (in case it is slightly different) instead of using one the signed provided ones? Or shouldn't I worry since all the SPLs with identical specs are actually identical?
Cheers
Click to expand...
Click to collapse
I suggest you find the same version SPL in here(http://forum.xda-developers.com/showthread.php?t=529019)
In my case, i can use SHIPMENT SPL HBOOT-1.33.0009H Signed update.zip to upgrade back to same SPL version, but i am not sure repair center will check it or not. So take your risk when you hacking in other Rom.
Hi Toneytse, i'm a little bit confused by the following description from you:
3. Check your version and go here (http://forum.xda-developers.com/showthread.php?t=529019) download a downgrade version. (In my case, I will download Modded HBOOT-1.33.2004)
I have exactly the same version of SPL with you, and i found our version is listed there http://forum.xda-developers.com/showthread.php?t=529019 which is HBOOT-1.33.0009 (SAPP10000), why you use HBOOT-1.33.2004 instead of HBOOT-1.33.0009 is it a must to use that version? i thought all the SPLs listed there are all MODIFIED?
Thanks. I am thinking of going back to my original ROM...
after i selected [Alt+B] to backup, got the following errors:
can't mount /dev/block/mmcblk0....
can't mount sdcard
update:
after got these errors listed above, i selected [Alt+B] again, it works!
thanks you ar.... i can backup and restore my rom....
one more think want to know, how can i root my magic(HK)???
cheers mate, brill!
when i type the command - fastboot erase system -w, i get waiting for device. whats wrong?
question. must i change my spl no matter what to be able to use nandroid backups?
jfive74 said:
when i type the command - fastboot erase system -w, i get waiting for device. whats wrong?
Click to expand...
Click to collapse
double check your USB cable and driver is installed, then check your Phone is ready on Recovery model
toneytse said:
double check your USB cable and driver is installed, then check your Phone is ready on Recovery model
Click to expand...
Click to collapse
got it to work. was the spl and i wasn't in fastboot usb mode(w/white screen) but in recovery mode. But thank you.
do you think its possible to swap the nandroid backup data.img from daldroids rom that i have with the nandroid backup data.img from rogers rom and then flash to device? just because i find the daldroid rom not really customised for rogers 7.2mbps data connection. i could be wrong. Please advise. Thanks.
I'm getting an errorm while trying to restore. any ideas? see below.
D:\android\tools>fastboot flash system system.img
sending 'system' (73515 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
D:\android\tools>fastboot erase system -w
erasing 'system'... OKAY
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
D:\android\tools>fastboot erase boot
erasing 'boot'... OKAY
D:\android\tools>fastboot flash system system.img
sending 'system' (73515 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
D:\android\tools>
aussiebuddha said:
I'm getting an errorm while trying to restore. any ideas? see below.
D:\android\tools>fastboot flash system system.img
sending 'system' (73515 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
D:\android\tools>fastboot erase system -w
erasing 'system'... OKAY
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
D:\android\tools>fastboot erase boot
erasing 'boot'... OKAY
D:\android\tools>fastboot flash system system.img
sending 'system' (73515 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
D:\android\tools>
Click to expand...
Click to collapse
You need to upgrade your SPL first~~
download here http://forum.xda-developers.com/showthread.php?t=529019
toneytse said:
You need to upgrade your SPL first~~
download here http://forum.xda-developers.com/showthread.php?t=529019
Click to expand...
Click to collapse
thanks mate that did it for me.
However, now I have a different SPL than what the phone came with.
How do I restore the original SPL?
thanks.
Thanks toneytse,
Thanks for the detail instruction, I have successfully backup my ROM. I have one question about the SPL. The shipment one 1.33.0009 while the modded one is 1.33.2004/2005. Does it mean 1.33.2004 is newer, or it is just the same thing just that it is modded to make flashing possible?
Hello! If i backup my rom , will it included the software which downloaded from market?
thanks
I had the can't mount sdcard issue on my tablet
I read somewhere that you can - erase the command system -. and so on. The boot-related files would be preserved
Unfortunately I have now only the acer logo and the boot loader on the screen.
When I press power and volume, nothing happens. Is there any possibility to rescue the Tablet?
I can just connecting and sending commands via usb and aio toolbox.
Please help me, my records from the study are in this tablet.
OK, lets summerize:
Tablet Acer 510
something happen - what does you've done?
I can just connecting and sending commands via usb and aio toolbox.
Click to expand...
Click to collapse
What is the AIO Toolbox? I didn't know....
If you've connect the Tablet on the PC, could the PC know the Tablet? Does you've access to the Tablett via adb ? Does the Tablett stopped at this point or it is in a reboot loop?
If you've an access via adb, you have the possibility
a) safe you work on PC
b) restore the 3 *.img on your tablett
If you need the 3 img files, I can give you a link of my 3 files (after root and NO-AD installation)
I tried this
Yes i can connect to pc by manipulating the lock screen button while starting with volume and power button.
Then i can send commands like this "fastboot oem unlock" or this "fastboot flash recovery recovery_nothrills.img"
I tried to send the nothrills image again, and it accepts the image and says image receyved but doesn't help.
Please can you mention what i have to do now.
Did you get my private message
Isn't it possible to mount the sdcard in ADB, and then pull the files you need?
In that way you have your records back and you can flash stuff without the fear of losing your files.
farris said:
Isn't it possible to mount the sdcard in ADB, and then pull the files you need?
In that way you have your records back and you can flash stuff without the fear of losing your files.
Click to expand...
Click to collapse
I can connecting via acer fastboot interface
Please can you tell me how is the command to connect sdcard in adb mode and where cani get the files and where have i need to drop it
Sorry, iam a very beginner
Can i push files in acer fastboot interface mode
I think i'd erased the bootfiles for the bootloader of nothrills boot image
i can just connect in fastboot interface mode and can sending commands
From what I have gathered on your thread on the other board you have erased your /sdcard partition
I believe CWM needs /sdcard (If I remember right, it says something to this effect when booting to CWM)
1) Try to flash the stock recovery from NoThrill's thread http://forum.xda-developers.com/showthread.php?t=1866378
2) put a stock ROM on an external SD card (rename to update.zip) http://forum.xda-developers.com/showthread.php?t=1897791
3) boot into recovery
4) keep your fingers crossed that it will install
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot flash recovery boot.img
sending 'recovery' (3970 KB)... OKAY [ 1.275s]
writing 'recovery'... OKAY [ 1.410s]
finished. total time: 2.686s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot reboot
rebooting...
finished. total time: 0.427s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
i tried what you mentioned, unfortunately no success.
ercuem said:
Can i push files in acer fastboot interface mode
I think i'd erased the bootfiles for the bootloader of nothrills boot image
i can just connect in fastboot interface mode and can sending commands
Click to expand...
Click to collapse
Should be:
fastboot flash boot [file]
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
ercuem said:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot flash recovery boot.img
sending 'recovery' (3970 KB)... OKAY [ 1.275s]
writing 'recovery'... OKAY [ 1.410s]
finished. total time: 2.686s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot reboot
rebooting...
finished. total time: 0.427s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
i tried what you mentioned, unfortunately no success.
Click to expand...
Click to collapse
Where did it go wrong?
Did you boot to recovery? (Vol- + power)
YEAH
a little success
I put updare.zip on external sd
Used this command "fastboot flash boot boot.img "This is the stock kernel of nothrill"
And now i got:
erasing cache before sd update...
sd update command: recovery
update package=sdcard: update.zip
Booting recovery kernel image
Now it stays on this state until 7 minutes an nothing happens
What boot.img did you flash?
Randomwalker said:
What boot.img did you flash?
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/showpost.php?p=31137321&postcount=1
Are you having issues with the ThrillsKernel (freezes, reboots, etc.)? Download the Acer kernel below:
Acer original kernel (mirror) (mirror)
(MD5 for the .ZIP file: b6e4f3fed3c96468ee25a0c3a8925433)
Flash this from the Recovery and wipe dalvik-cache. Note: This Acer kernel will only work with the ROM in this thread, do not attempt to use it on other ROMs!
In this zip is a boot.img and a directory called Meta.inf
OK, so that would be a stock kernel.
Can you try to flash the whole ROM via fastboot?
- copy the update.zip to your fastboot directory
- fastboot update update.zip
Randomwalker said:
OK, so that would be a stock kernel.
Can you try to flash the whole ROM via fastboot?
- copy the update.zip to your fastboot directory
- fastboot update update.zip
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
I USED THIS STOCK ROM
OS_Acer_RV28.RC04.EMEA.DE_A40I_A.zip
But you did unzip it first, right? Not just renamed the download to update.zip?
Randomwalker said:
But you did unzip it first, right? Not just renamed the download to update.zip?
Click to expand...
Click to collapse
Yes unfortunately i'm getting the mentioned message.
Thank you for helping me
Yes unfortunately i'm getting the mentioned message.
Thank you for helping me
shall i try "fastboot boot recovery_nothrill.img?"
No worries, maybe someone more knowledgeable will come around . Unfortunately I no longer have an A510.
So, you currently are on stock recovery and it hangs after: "Booting recovery kernel image", right?
Maybe we really need to reconstruct /sdcard... but I have no idea how.
EDIT:
shall i try "fastboot boot recovery_nothrill.img"
Click to expand...
Click to collapse
Definitely, give it a go! I thought you already tried that.
Randomwalker said:
No worries, maybe someone more knowledgeable will come around . Unfortunately I no longer have an A510.
So, you currently are on stock recovery and it hangs after: "Booting recovery kernel image", right?
Maybe we really need to reconstruct /sdcard... but I have no idea how.
EDIT:
Definitely, give it a go! I thought you already tried that.
Click to expand...
Click to collapse
unfortunately no success, i got the same message:
erasing cache before sd update...
sd update command: recovery
update package=sdcard: update.zip
Booting recovery kernel image
Where can i get an update zip, which it will accept for update?
I got the exactly the same message as attached as jpg and pdf.
I cannot flash to 8.1.0 through factory image, what I get through ./flash-all.sh is:
extracting vendor.img (346 MB) to disk... took 2.107s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
/usr/local/bin/mke2fs: illegal option -- b
Error: Unknown option ?
Usage: mkfs.f2fs [options] device [sectors]
What should I do?? I am using brew for fastboot, should I use something else?
I don't know what brew is but you probably need to update your fastboot. With this phone you should get your perform tools directly from Google just about every time there's a new image since the a/b partitions requires new commands and other more recent Android updates required newer fastboot still.
https://www.androidpolice.com/2017/...ble-without-full-sdk-android-studio-download/
has links to the direct downloads.
cntryby429 said:
I don't know what brew is but you probably need to update your fastboot. With this phone you should get your perform tools directly from Google just about every time there's a new image since the a/b partitions requires new commands and other more recent Android updates required newer fastboot still.
https://www.androidpolice.com/2017/...ble-without-full-sdk-android-studio-download/
has links to the direct downloads.
Click to expand...
Click to collapse
It was a stupid setup on my part. I had the latest version but my PATH was not set correctly. Double-checked and everything's alright now. Thanks!
Is often the easiest thing. The other day fastboot refused to recognize my phone. I was going crazy until I realized that the cable plugged into my laptop was not the same one plugged into my phone. Felt like a putz.
I was trying to flash stock rom in my Pixel 2 which had the march update and I am getting the error
ERROR: LoadImageAndAuth Failed: Load Error
Click to expand...
Click to collapse
Here's what happened:
I unpacked my phone, updated it to the latest OTA version available (the March version) using the OS update function. Then I followed a tutorial in YouTube to root the phone using Magisk (https://www.youtube.com/watch?v=M-0NIUUvYI4). It worked well, I had root access and I could boot into the phone as normal. All this was done using the latest platform tools, image and usb drivers
I then decided to recheck for updates. A new update appeared, the one from April. I tried to install it and I couldn't. I figured out it was because of the root. I tried to uninstall Magisk using the restore stock image (or similar, can't remember the name of the option) but said "Stock backup does not exist" So I decided to flash the factory image of this April update (I verified it was the correct one for my device. Maybe it could have been the March update, but it has been a wild ride and I can't think clearly anymore) and after that my phone won't boot back up, it is stuck in the bootloader. Sometimes if I use the flash-all of the factory image or modify the script to change the order of the flashing of images I can get to the screen with the Google words in a white background and an open padlock, but that's it. The bootloader is still unlocked
How could I troubleshoot if it is a hardware issue? How could it had damaged itself so quickly, literally I used it only for 30 min before attempting the root process. Sometimes I also do get ERROR: Slot Unbootable, but if I reflash with the script I usually end with the above error
I tried following the instruction to run the deuce script modifying the script such that:
Commented out the unlock_critical as
Code:
::fastboot flashing unlock_critical
the boot slots are as follows: https://pastebin.com/NTapvzXV
I ran getvar all if it is useful: https://pastebin.com/bKA20Jvy
But I am still getting the same error. I am desperate to fix since I haven't even used the phone at all and it is completely new.
Please, I need your help urgently
Here is the output from the flashing process: https://pastebin.com/AwiAyrWh
I think the problem seems that I am unable to mount the vendor partition:
When I try sending the command manually I get this:
Code:
fastboot flash vendor_a vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.130s]
sending 'vendor_a' (354100 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 8.012s
When I try wiping or something along those lines with TWRP it says
Failed to mount '/vendor' (Invalid argument)
Click to expand...
Click to collapse
Thank you
Be sure you have the very latest platform tools for your OS and try again. https://developer.android.com/studio/releases/platform-tools.html
westhaking said:
Be sure you have the very latest platform tools for your OS and try again. https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Unfortunately when I started all this process that was the first I did, download everything anew from the official sites.
Download the April factory image and try again. I had this same issue due to not using the most up to date platform tools and not placing the unzipped contents of the april update in the platform tools folder.
smokie75 said:
Download the April factory image and try again. I had this same issue due to not using the most up to date platform tools and not placing the unzipped contents of the april update in the platform tools folder.
Click to expand...
Click to collapse
That's exactly what I did unfortunately. The thing is I am unable to flash the vendor image.
Try a different USB port on your computer, preferably a USB 2 port instead of a USB 3 port.
Telperion said:
Try a different USB port on your computer, preferably a USB 2 port instead of a USB 3 port.
Click to expand...
Click to collapse
Would that help with problem of being unable to mount the vendor partition? I tried but the same problem persists
damnrecoverymode said:
Would that help with problem of being unable to mount the vendor partition? I tried but the same problem persists
Click to expand...
Click to collapse
Potentially, there are reports of sporadic issues with USB ports and USB cables around the forums.
Flashback the March firmware. Its gives you error because your not using the right firmware that was installed in your pixel.
Sent from my [device_name] using XDA-Developers Legacy app
Mangtas_666 said:
Flashback the March firmware. Its gives you error because your not using the right firmware that was installed in your pixel.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
By firmware do you mean the factory image? If so already tried to do that with Deuces script, that is: Download latest platforms tools and the correct factory image, then extract the first .zip and try the flash-all.bat, then when that doesn't work unzip the internal zip and try the script but to no avail. In both cases, as I said, I am unable to mount the vendor partition.
But if by firmware you mean something different, could you please point me in the right direction to download and install it?
I have seen this (https://developers.google.com/android/drivers#walleye), what is that vendor image in there?
Thank you for your help
I didn't use the deuces tool i just copy the necessary files direct to the platform tools folder then edit flashall.bat delete the -w if you dont want to wipe your device. Grab the march firmware at google site then unzip it copy all at the platform tools folder go to fastboot then click flashall.bat
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 06:18 PM ---------- Previous post was at 05:56 PM ----------
Grab it here...https://developers.google.com/android/images
Sent from my [device_name] using XDA-Developers Legacy app
Mangtas_666 said:
I didn't use the deuces tool i just copy the necessary files direct to the platform tools folder then edit flashall.bat delete the -w if you dont want to wipe your device. Grab the march firmware at google site then unzip it copy all at the platform tools folder go to fastboot then click flashall.bat
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 06:18 PM ---------- Previous post was at 05:56 PM ----------
Grab it here...https://developers.google.com/android/images
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes that's what I've been doing to no avail :crying:
damnrecoverymode said:
Yes that's what I've been doing to no avail :crying:
Click to expand...
Click to collapse
Can you go to fastboot? What does it say when you try to flash back to stock?
Sent from my [device_name] using XDA-Developers Legacy app
Mangtas_666 said:
Can you go to fastboot? What does it say when you try to flash back to stock?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
What it says is what is in the first post. You can check all the information I've been able to recompile. But I think the key problem is here:
fastboot flash vendor_a vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.130s]
sending 'vendor_a' (354100 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 8.012s
Click to expand...
Click to collapse
damnrecoverymode said:
What it says is what is in the first post. You can check all the information I've been able to recompile. But I think the key problem is here:
Click to expand...
Click to collapse
Try different pc and cable
Sent from my [device_name] using XDA-Developers Legacy app
Try switching to system B? Could also try uninstalling your usb driver and rebooting, then reinstalling it. Also if youre using something like LibUsb, that can mess with adb sometimes.
Do not use toolkits or whatnot. Download everything yourself, from official google links.
Platform tools: https://developer.android.com/studio/releases/platform-tools.html
Firmware: https://dl.google.com/dl/android/aosp/walleye-opm2.171019.029-factory-41296266.zip
I, personally would NOT try flashing an older firmware as these phones have rollback protection. The newest firmware should work, I just used it to return to stock to get the newest security updates.
I'm 99% sure this is a port / cable / driver issue, try all of this on a different computer with USB 2 ports and a fresh driver setup.
Telperion said:
I'm 99% sure this is a port / cable / driver issue, try all of this on a different computer with USB 2 ports and a fresh driver setup.
Click to expand...
Click to collapse
Sure it was. Had to ask to a neighbor his computer and cable to test and it really worked! Thank you for your help mate!
Telperion said:
I'm 99% sure this is a port / cable / driver issue, try all of this on a different computer with USB 2 ports and a fresh driver setup.
Click to expand...
Click to collapse
I've also experienced fastboot issues with the Pixel 2.
After a few successful flashes using my laptop, I started to hit errors when flashing the system partition.
I now check for fastboot broken-ness by repeatedly running "fastboot getvar all" (say, 10 times).
If "getvar" fails, then it is time to try flashing using another machine.
Possible solution
Has the OP ever found a solution to his problems? I stumbled upon this thread with similar issues, by searching for "FAILED (Write to device failed (Unknown error))". My problem looks like this:
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 12.198s]
Writing sparse 'system_a' 1/5 OKAY [ 0.000s]
Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 14.210s]
Writing sparse 'system_a' 2/5 OKAY [ 0.000s]
Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 14.160s]
Writing sparse 'system_a' 3/5 OKAY [ 0.000s]
Sending sparse 'system_a' 4/5 (521176 KB) FAILED (Write to device failed (Unknown error))
Click to expand...
Click to collapse
After a few shots in the dark, I managed to resolve the issue by reducing the sparse file size, specifically this fastboot option:
-S SIZE[K|M|G] Break into sparse files no larger than SIZE.
Click to expand...
Click to collapse
Using -S 256M did it for me (the default was just short of 512MB). So the last line in my flash-all.sh looked like this in the end:
fastboot -S 256M update image-walleye-pq2a.190205.002.zip
Click to expand...
Click to collapse
Well I bought this Calypso U318AA from a friend for cheap. It was his sons he got new phone. I bought it to root it. I was just going to do the magical root.. I've rooted several other phones in past. The world wide web has very little info well, no info on this thing. It's a Android 10. I'm not sure of even the best way to unlock the bootloader. I know it doesn't have nothing in developers options. On recovery reboot you can do a recovery boot and a fastboot as well as normal boot. Can't find anything but factory at&t stuff. So any info would be great. Thank you
dorkxperience said:
Well I bought this Calypso U318AA from a friend for cheap. It was his sons he got new phone. I bought it to root it. I was just going to do the magical root.. I've rooted several other phones in past. The world wide web has very little info well, no info on this thing. It's a Android 10. I'm not sure of even the best way to unlock the bootloader. I know it doesn't have nothing in developers options. On recovery reboot you can do a recovery boot and a fastboot as well as normal boot. Can't find anything but factory at&t stuff. So any info would be great. Thank you
Click to expand...
Click to collapse
I just received this phone from at&t. Found out mtk_client will unlock bootloader. so magisk root "should be" available after this unlock. I have not tried yet , i only unlocked bootloader earlier today. will keep looking for anyone else trying this and update as i find any info.
Twrp is working (mostly) for TINNO U318AA. (ATT&T Calypso)
still need to work out data decryption, and FatsbootD mode.
Device Tree: https://github.com/mrmazakblu/twrp-device-att_u318aa/tree/twrp-11
Device Dump: https://github.com/mrmazakblu/att_u318aa_dump
mrmazak said:
Twrp is working (mostly) for TINNO U318AA. (ATT&T Calypso)
still need to work out data decryption, and FatsbootD mode.
Device Tree: https://github.com/mrmazakblu/twrp-device-att_u318aa/tree/twrp-11
Device Dump: https://github.com/mrmazakblu/att_u318aa_dump
Click to expand...
Click to collapse
Phh aoap gsi a11 installs and runs good
mrmazak said:
Phh aoap gsi a11 installs and runs good
Click to expand...
Click to collapse
To clarify, let me tel you all which build version i have installed and outline the steps to get it loaded.
THIS IS NOT INTENDED TO BE STEP BY STEP GUIDE ONLY AN OVERVIEW
WHATEVER YOU DO ON YOUR DEVICE IS AT YOUR OWN RISK
system-squeak-arm32_binder64-ab-vndklite-vanilla
downloaded from :
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
!. Bootloader must be unlocked.
AT&T removed the enable OEM unlock from developer menu, but there is an excellent work around 'tool' to get around this.
MTK CLIENT will allow you to read (pull) stock firmware off from phone, much like spflash tool does, except with this phone and many other newer phones the manufacture has enabled security and authorization files to block sp flash tool , SOOOO, tools like mtk client try to stay a step ahead.
I only used the GUI options with the client, it was very user friendly , the tool has way more options than i needed to mess with.
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
2. Before flashing gsi, make sure you have pulled firmware from phone, so you have stock super.img. If you don't you will not be able to restore device when / if you mess up the vendor partition.
3. I disabled vbmeta verification .
will need stock vbmeta from pulled firmware.
boot into bootloader, (adb reboot bootloader , or reboot while holding the volume up button. You should get a boot menu)
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(the last part need to point to you file location where ever it is)
4. Now we need to move from bootloader to fastboot. fastboot reboot command didn't work for me so needed to boot recovery first, then fastboot.
Code:
fastboot reboot
hold volume up button to get boot menu, select recovery
from recovery select reboot fastboot
in the fastbootd connection you will be able to flash gsi
the system area is not large enough to fit gsi , so you will need to remove the /product partition.
Code:
fastboot delete-logical-partition product
fastboot flash system system-squeak-arm32_binder64-ab-vndklite-vanilla.img
once completed use the screen menu to reboot back to recovery and perform factory reset.
With the exception of needing to use mtk client, the rest of these steps are standard android process. documented in many locations. I go to the android source first for information. \
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Thanks a lot mrmazak, I'm working on a step by step guide for newbies like me to expand on your steps to unblock and reflash the phone.
I was able to use MRK Client, unlock bootloader and put the phone in fastboot.
The problem I have is to find the right MediaTek driver for the device USB\VID_0E8D&PID_201C
Where did you find them? I tried Google USB driver from ADP but they use different Device ID and all MediaTek driver with same VendorID 08ED have old ProductID instead of 201C.
Any help on MediaTek driver so I can finish the guide and post the link here?
Specifically, I was able to connect via ADB but Fastboot requires a different driver which I'm not able to find
Thanks a lot for your help!
mrmazak said:
I just received this phone from at&t. Found out mtk_client will unlock bootloader. so magisk root "should be" available after this unlock. I have not tried yet , i only unlocked bootloader earlier today. will keep looking for anyone else trying this and update as i find any info.
Click to expand...
Click to collapse
Thats awesome thanks
inglele said:
Thanks a lot mrmazak, I'm working on a step by step guide for newbies like me to expand on your steps to unblock and reflash the phone.
I was able to use MRK Client, unlock bootloader and put the phone in fastboot.
The problem I have is to find the right MediaTek driver for the device USB\VID_0E8D&PID_201C
Where did you find them? I tried Google USB driver from ADP but they use different Device ID and all MediaTek driver with same VendorID 08ED have old ProductID instead of 201C.
Any help on MediaTek driver so I can finish the guide and post the link here?
Specifically, I was able to connect via ADB but Fastboot requires a different driver which I'm not able to find
Thanks a lot for your help!
Click to expand...
Click to collapse
Did not have to install any drivers special.
mrmazak said:
Did not have to install any drivers special.
Click to expand...
Click to collapse
Yes, I had Other \ Android device listed in Device Manager, so I tried disable signed driver and force install of these drivers: https://forum.xda-developers.com/t/...32-64-bit-driver-install-tutorial-m2.3267033/
Now, I have it visible as MediaTek PreLoader USB VCOM Port but if I type "fastboot devices" is not listed.
ADB is able to see it correctly:
adb devices
List of devices attached
AYMB5PKZCUEUUOSC device
When I restart in fastboot with "adb reboot bootloader" the phone restart correctly in fastboot.
I'm not able to unblock the connection between fastboot tool and phone in fastboot mode, I suspect due to missing / wrong driver.
If you have any idea, it would be great!
Found the correct driver. I needed to force Google ADB Driver -> "Android Bootloader Interface" and it works!
They are available here: https://developer.android.com/studio/run/win-usb
Thanks for the help and sorry for confusion, newbie questions
Mod Edit: Quote removed since post deleted.
I received 'not enough space" error when flashed gsi, this is why i delete product partition.
I recall there are fastboot commands to list super.img size, but not sure for super sub-partiton size. there are tools to extract the sub-partitons and it will show individual size.
there must be commands for it in fastboot i think, But i do not know them.\
They deleted the previous post, so I'm copy paste the steps from the blog post.
Pre-requirements
Tested on Windows 11, it should work on any previous Windows versions
Install MTK Client to unlock bootloader: Inofficial MTK reverse engineering and flash tool – which requires Python 3.9 and Git – Downloading Package (git-scm.com) and UsbDk
Download phone image system-squeak-arm32_binder64-ab-vndklite-vanilla.img.gz from Release AOSP 12.1 v410 · phhusson/treble_experimentations
Download Android DevelopersSDK Platform Tools | Android Developers
Download Google USB Driver | Android Developers
Unlock phone bootloaderBootloader must be unlocked to install the new firmware.
MTK CLIENT will allow you to read stock firmware off from phone, except with this phone the manufacture has enabled security and authorization files to block sp flash tool.
Install Python 3.9 from Microsoft Store and Git – Downloading Package and daynix/UsbDk · GitHub, then open a CMD:
mkdir C:\test
cd C:\test
git clone https://github.com/bkerler/mtkclient
cd mtkclient
pip3 install -r requirements.txt
Once installation in complete, start MTK Client with
c:\Test\mtkclient
python mtk_gui
To activate BRUM mode for the phone and connect it to MKT Client
Turn off the phone if it’s on.
Press Volume UP + Volume DOWN and plug the USB cable.
Do not press power button and MKT Client will detect it.
Backup:
In the Read partition tab,
Select all of them and Save to C:\Test\Firmware\Original
It will take about 40min to complete all the operation
Unlock Bootloader
In Flash Tools tab,
Click on Unlock bootloader button
Debug log will show Bootloader: unlock and python windows list
sej - HACC init
sej - HACC run
sej - HACC terminate
sej - HACC init
sej - HACC run
sej - HACC terminate
Progress: |██████████████████████████████████████████████████| 100.0% Write (Sector 0x1 of 0x1, ) 0.03 MB/s
If you restart the phone, you will see a warning that bootloader is unlocked and it will ask you to factory reset the phone.
Install the new firmwareYou need to have Android DevelopersSDK Platform Tools | Android Developers installed to be able to flash the new firmware.
Enable USB Debugging in the phone and connect ADB
Start the phone
Perform a Factory Reset
Restart the phone and complete the initial wizard
Open Settings -> “About Phone” -> Tap the “Build Number” item seven times.
You should get a message saying you are now a developer.
Settings -> “System” -> “Advanced” -> “Developer Options.”
Open the menu and enable “USB Debugging.”
To verify that ADB in installed correctly and is able to connect to the device:
CD C:\Test\Tools
adb version
Android Debug Bridge version 1.0.41
Version 33.0.1-8253317
Installed as C:\Test\Tools\adb.exe
adb devices
List of devices attached
AYMB5PKZCUEUUOSC device
Boot into fastboot with the following command adb reboot bootloader
or reboot while holding the volume up button and select fastboot.
Install Google ADB FastBoot driver in Windows 11Download Google USB Driver | Android Developers as they will be needed to connect the device via fastboot. To install the driver, we need to force the installation in Device Manager with these steps:
Open Device Manager
Right click on Other Devices \ Android device
Select “Update Driver” -> “Browse my computer for drivers” -> “Let me pick from the list of available driver“
Select “Show All Devices” -> “Have Disk“
Navigate to “C:\Test\Tools\usb_driver_r13-windows” and let Windows load the drivers
Select “Android Bootloader Interface” as driver name
Test that Fastboot tool is able to interact with the phone
CD C:\Test\Tools
fastboot devices
AYMB5PKZCUEUUOSC fastboot
Next step is to disable vbmeta verification with the following steps:
Firmware update via Fastboot
While the phone is in the FastBoot mode, type the following:
CD C:\Test\Tools
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta "C:\Test\Firmware\Original\vbmeta.bin"
target reported max download size of 134217728 bytes
sending 'vbmeta' (8192 KB)... OKAY [ 0.204s]
writing 'vbmeta'... OKAY [ 0.189s]
finished. total time: 0.393s
After vbmeta image is flashed, perform:
fastboot reboot fastboot to restart the phone and enter fastbootd
Check the phone is connecting correctly with fastboot devices
and force the installation of Android Bootloader Interface in Device Manager if needed.
The following step delete product partition so system partition has enough space:
fastboot delete-logical-partition product
Deleting 'product' OKAY [ 0.016s]
Finished. Total time: 0.016s
This command flash the custom rom on system partition:
fastboot flash system "C:\Test\Firmware\system-squeak-arm32_binder64-ab-vndklite-vanilla.img"
Invalid sparse file format at header magic
Resizing 'system' OKAY [ 0.016s]
Sending sparse 'system' 1/5 (255489 KB) OKAY [ 14.939s]
Writing 'system' OKAY [ 7.651s]
Sending sparse 'system' 2/5 (262100 KB) OKAY [ 15.141s]
Writing 'system' OKAY [ 7.705s]
Sending sparse 'system' 3/5 (262104 KB) OKAY [ 15.001s]
Writing 'system' OKAY [ 7.595s]
Sending sparse 'system' 4/5 (261825 KB) OKAY [ 14.752s]
Writing 'system' OKAY [ 7.711s]
Sending sparse 'system' 5/5 (183741 KB) OKAY [ 10.421s]
Writing 'system' OKAY [ 5.832s]
Finished. Total time: 107.885s
Once flash of new rom is completed, you can restart the phone and it will boot using the new rom.
Original post suggested to perform a factory reset.
WARNING: In my case, a factory reset caused a reboot loop and was not able to
If you want to proceed, in the menu on the screen:
Select “Enter recovery” and
Select “Wipe data/factory reset“
Screen on the phone will show
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /metadata...
Data wipe completed.
If you missed the previous screen, or clicked the wrong button/option:
restart the phone holding Volume UP,
Select fastboot on the phone
Type fastboot reboot fastboot to reenter fastbootd screen
And repeat the factory reset
Restart the phone and you are up and running.
Restore original firmwareIf you need to restore original rom, use MKT Client tool to write:
vbmeta.bin
super.bin
then close the tool and restart the phone. It will be like new
hi! hope i can get some help. this is my first time using mtkclient but i can't seem to get it to detect the phone. i'm making sure to follow the steps listed of having the phone off first, then press both volume buttons and plug in the usb. on the phone it eventually pulls up a "select boot mode" where i can use the volume buttons to select recovery mode fastboot mode or normal mode boot. i've tried recovery and fast boot modes as well as just leaving it on that select screen but nothing is detected in mtkclient
thanks!
New to the world of droid but am familiar with modding stuff so I'm a semi-noob I suppose. Found myself getting one of these things from the local dollar general and followed this guide to get rid of all the google crap and hopefully speed it up a bit. Bootloader is unlocked, .img posted above is flashed, and it boots up and seemingly works. Can't figure out how to sideload apps nor can I find any type of write up explaining what to do with the tree and dump file posted above. Any help and/or clarification, greatly appreciated. MTKClient, ADB, and Fastboot are all installed and functional. Using Linux Manjaro.
--chuckles b
ltk6260 said:
hi! hope i can get some help. this is my first time using mtkclient but i can't seem to get it to detect the phone. i'm making sure to follow the steps listed of having the phone off first, then press both volume buttons and plug in the usb. on the phone it eventually pulls up a "select boot mode" where i can use the volume buttons to select recovery mode fastboot mode or normal mode boot. i've tried recovery and fast boot modes as well as just leaving it on that select screen but nothing is detected in mtkclient
thanks!
Click to expand...
Click to collapse
Run mtkclient. With the phone already off, hold down both volume buttons and connect the phone to your computer. You should hear the "usb connected" notification sound on your computer and mtkclient will pick up it. As soon as you hear that chime, release the buttons, set the phone down, and don't touch it. The screen shouldn't come on during this step.
Make sure you're ONLY holding down the volume buttons and plugging it in. Don't touch the power button.
If you're still having issues with it not picking up your phone, go through the standard troubleshooting steps: Recheck you followed every step, restart your computer, try other USB ports, try other cables.
*********
FYI this isn't applicable to this process, but should be noted: This phone has a weird way to get into the recovery menu. You have to hold Vol+ and Power, then select Recovery from the menu, THEN immediately press and hold the Vol+ (or Vol- I don't recall at the moment) and Power buttons again until the recovery menu comes up
veryspecialagent said:
Run mtkclient. With the phone already off, hold down both volume buttons and connect the phone to your computer. You should hear the "usb connected" notification sound on your computer and mtkclient will pick up it. As soon as you hear that chime, release the buttons, set the phone down, and don't touch it. The screen shouldn't come on during this step.
Make sure you're ONLY holding down the volume buttons and plugging it in. Don't touch the power button.
If you're still having issues with it not picking up your phone, go through the standard troubleshooting steps: Recheck you followed every step, restart your computer, try other USB ports, try other cables.
*********
FYI this isn't applicable to this process, but should be noted: This phone has a weird way to get into the recovery menu. You have to hold Vol+ and Power, then select Recovery from the menu, THEN immediately press and hold the Vol+ (or Vol- I don't recall at the moment) and Power buttons again until the recovery menu comes up
Click to expand...
Click to collapse
Thanks! that did help.
i was able to get all the way through up to flashing the new rom. I'm getting this error:
fastboot flash system system-squeak-arm32_binder64-ab-vndklite-vanilla.img
Invalid sparse file format at header magic
Resizing 'system' OKAY [ 0.013s]
error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096
Sending sparse 'system' 1/2 (262140 KB) error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096
OKAY [ 12.568s]
Writing 'system' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
still can't get past this error. i've confirmed my filename, file extensions, and file location. even checked file permissions. the img file is in the same folder as the fastboot command itself.
i also tried the command using the full c:\ path to the img file but it fails the same.
i then restored the phone to the original super.bin and the phone worked like normal. so i went all the way back through the steps starting from the top but failed at the same final step flashing the system.
ltk6260 said:
still can't get past this error. i've confirmed my filename, file extensions, and file location. even checked file permissions. the img file is in the same folder as the fastboot command itself.
i also tried the command using the full c:\ path to the img file but it fails the same.
i then restored the phone to the original super.bin and the phone worked like normal. so i went all the way back through the steps starting from the top but failed at the same final step flashing the system.
Click to expand...
Click to collapse
What are you trying to do? What is the purpose or end result you're hoping to achieve?
I ask because this thread is a bit convoluted and "noobs" looking to just root and tinker might come in thinking they have to do all the steps in this thread to get there.
Like someone wanting an oil change overhearing two mechanics rebuilding a transmission, taking notes, especially where they mentioned "oil," then walking away thinking that's what they need to do.
The tools linked above are great. The mtk one, once I was able to get it running, was how I got past the FRP. For anyone wondering, there's an FRP partition that you can just delete with the tool.
If you're just wanting root, see above for unlocking the bootloader, then stop. I'm 90% certain I achieved root by just following the process outlined the official Magisk page on GitHub.
Can I get some OP/MOD thoughts on breaking this thread up into specific guides with the purpose clearly written in the title?
veryspecialagent said:
What are you trying to do? What is the purpose or end result you're hoping to achieve?
I ask because this thread is a bit convoluted and "noobs" looking to just root and tinker might come in thinking they have to do all the steps in this thread to get there.
Like someone wanting an oil change overhearing two mechanics rebuilding a transmission, taking notes, especially where they mentioned "oil," then walking away thinking that's what they need to do.
The tools linked above are great. The mtk one, once I was able to get it running, was how I got past the FRP. For anyone wondering, there's an FRP partition that you can just delete with the tool.
If you're just wanting root, see above for unlocking the bootloader, then stop. I'm 90% certain I achieved root by just following the process outlined the official Magisk page on GitHub.
Can I get some OP/MOD thoughts on breaking this thread up into specific guides with the purpose clearly written in the title?
Click to expand...
Click to collapse
I understand your questioning. I'm trying to unlock and load aosp firmware, or frankly, anything other than what this device is loaded with since it's horribly bloated, slow and periodically unstable. this is a play phone, i have two of these phones actually.
ltk6260 said:
I understand your questioning. I'm trying to unlock and load aosp firmware, or frankly, anything other than what this device is loaded with since it's horribly bloated, slow and periodically unstable. this is a play phone, i have two of these phones actually.
Click to expand...
Click to collapse
So is mine. I agree with the bloat, which I thought was weird considering the Android 10 version it comes with (Go) is supposed to be a more streamlined version for lower end phones that lack the processing power.
I tend to not do new ROMs unless it's something with a track record and support like Lineage, but after playing around with it and testing some of the functions with things like WIGL, Termux, LSposed, etc, I'm thinking it might be a good Nethunter phone.
After some extensive Googling, and since I doubt this falls under the "you're flashing the wrong build/version" because there's only one variant of this phone, I'd say it might be possible you're not running the right SDK platform package.
Start Android Studio, go to Settings > Appearance & Behavior > System Settings > Android SDK and make sure you have the right platform packages installed (i.e. Android 10, API 29) and updated.