Related
Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer, as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
Click to expand...
Click to collapse
cheers
-Buster
Buster99 said:
Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
cheers
-Buster
Click to expand...
Click to collapse
At this part:
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
Click to expand...
Click to collapse
you put the instructions fo the TF300t, but you said this method also worked for the Acer a700. I know to change the code after -i to 0x0502, for the a700 device ID, but I'm not sure what to use for the system. I've been unable to find a system.img that works, as well. What should I do after erasing the partitions?
Also, usually when I try to flash anything, when fastboot begins the write process (or just before,) the tablet screen starts to slowly jitter (the Acer logo and Bootloader text in the top-left go down about 10 pixels for about a half-second then go back to their original positions.) I've tried multiple guides (can't fastboot boot recovery.img, Magic Value Mismatch error,) and I can't get into adb. Any ideas? It looks like your fix might work somehow.
OMIGHTY1 said:
At this part:
you put the instructions fo the TF300t, but you said this method also worked for the Acer a700. I know to change the code after -i to 0x0502, for the a700 device ID, but I'm not sure what to use for the system. I've been unable to find a system.img that works, as well. What should I do after erasing the partitions?
Also, usually when I try to flash anything, when fastboot begins the write process (or just before,) the tablet screen starts to slowly jitter (the Acer logo and Bootloader text in the top-left go down about 10 pixels for about a half-second then go back to their original positions.) I've tried multiple guides (can't fastboot boot recovery.img, Magic Value Mismatch error,) and I can't get into adb. Any ideas? It looks like your fix might work somehow.
Click to expand...
Click to collapse
When in doubt, disconeect all android devices and issue the command without the ID (usually fastboot/adb use the default id when only 1 device is connected.
"fastboot flash system c:\blob"
The erase worked on my TF300t/A700/Galaxy Nexus.
If you are having flashing probs make shure to switch cable and usb ports &/or try a linux to test.
gl
-Buster
Here's the input and output from that:
C:\android>fastboot flash system c:\blob
error: cannot load 'c:\blob': No error
Click to expand...
Click to collapse
Would I need the stock image in the blob folder, or should it be empty? Should I create it at all?
The screen problem is identical to the problem in this post:
http://forum.xda-developers.com/showthread.php?t=1976209
OMG - Thought My Prime was Dead In The Water...Thanks Buster!
Buster99 said:
Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
cheers
-Buster
Click to expand...
Click to collapse
Was getting the dreaded Option 2 - Unrecoverable Bootloader Error that was supposed to be the ultimate death sign. As a last resort, I tried the steps Buster provided and my Prime is up and running again!
When i turn on tablet, goes straight to recovery, even after have tried rebooting into system, i followed the button combinations to boot into RCK. The version installed of CWM was based in Recovery v6.0.2.3 occurs that after opening CWM immediately below error messages are displayed.
E:Can’t mount /cache/recovery/command
E:Can’t mount /cache/recovery/log
E:Can’t open /cache/recovery/log
E:Can’t mount /cache/recovery/last_log
E:Can’t open /cache/recovery/last_log
And now can’t grab any rom in SD card when I’m forced into recovery. I tried with two kind of SD, 1Gb Sandisk, 4Gb Kingston HC-(4). when I try to mount any partition like /data and /sdcard from “mounts and storage” obtain:
Error mounting /sdcard!, Error mounting /sdcard!, Error mounting /emmc!
Also i download android tools and installed adb universal drivers, from recovery mode, If I type "adb devices" shows a proper reorganization.
List of device attached
0123456789ABCDEF recovery
So every time when start up, even without hitting vol+power key, it goes into the recovery mode.when i type "adb reboot-bootloader",it goes power off.Nothing happen.Please help me.
So, I unlocked bootloader, flashed cwm, now I cant copy ROM to the phone, problem is phone DOES connect, the drive shows up, I can open it to see the existing folders inside. But I cant copy/delete anything to it. Its like its on read only permission.
On windows 8.1 I cant find any option in the properties to change permission.
Same with windows 7, no option to change the permissions.
On linux mint there is the option to change permissions, but sadly they wont change.
I have tried connecting both via the ROM itself and the cwm > mounts and storage > mount usb storage. Same result either way.
I have also tried pushing files via ADB, the process never completes.
Well, if it were usb issue, it wont even let me see the current files inside, so i am at a loss now. Thats all I could think of. Tried it on 2 laptops and one pc already.
Any suggestions?
Right now transfering ROM via bluetooth. But its taking mighty long (obviously).
EDIT: Nopes, cant do anything. It wont flash any other recovery now, in fastboot after the 'fastboot flash recovery........" it says "out of memory" if not that, it just hangs and does nothing.
Via terminal emulator it does not recognize flash_image
and cant flash rom unless i update the recovery.
So right now the priority is to update recovery, anybody know of any other terminal emulator command? ROM manager is not recognizing the current cwm recovery. and there was RASHR says done, but when i reboot its still the same old recovery.
Edit:
So I found this:
Theonew said:
Do:
Code:
fastboot erase recovery
Then reflash recovery.
Click to expand...
Click to collapse
Any ideas? Will this help with the out of memory issue?
I erased the recovery now I am getting this...
C:\Users\fasih\Desktop\asdsadasdsa\NexusS_files\NSFiles>fastboot flash recovery
ttw.img
< waiting for device >
sending 'recovery' (5572 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 0.251s
First of all thanks to the 68 viewers of this thread I managed to solve it, after 2 lappy's and 1 pc and 3 cables I found that the cables were all faulty, just got a new one and it solved the problem. Thanks for bearing with me guys.
As the title says, I (without thinking) did a factory reset from within the settings menu while using a custom rom. My tablet boots and sits on the attached screen. I cannot access fastboot but while on the screen I have ADB access and can send commands. Also, none of the Volume&Power Buttons combinations will work. Please advise..
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
berndblb said:
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggested thread, unfortunately after the "adb shell insmod /bootit.ko" command my tablet simply powers off and does not reboot. I read through the thread and saw that someone else experienced the same but there doesn't seem to be a resolution.
berndblb said:
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Will this work if I accidentally did wipe davlink in TWRP after I flashed a rom? I can get into TWRP but cant reflash rom and am in boot loop when I try to flash it says MD5 not found
JGuinan007 said:
Will this work if I accidentally did wipe davlink in TWRP after I flashed a rom? I can get into TWRP but cant reflash rom and am in boot loop when I try to flash it says MD5 not found
Click to expand...
Click to collapse
Is that a serious question???
I used red size 6 type in that post to make clear what that trick is NOTfor.....
You must have done a little more than "accidentally wipe Dalvik" my friend. Dalvik would just get rebuild on the next boot if you wiped it.
The message that no MD5 is found is pretty normal if no MD5 is present, but it would not prevent you from flashing the rom.
My wild guess is that you somehow corrupted /data and it won't mount, but I don't really know because your post lacks anything that might be helpful.
Like specific information.
Try again.
Harder.
berndblb said:
Is that a serious question???
I used red size 6 type in that post to make clear what that trick is NOTfor.....
You must have done a little more than "accidentally wipe Dalvik" my friend. Dalvik would just get rebuild on the next boot if you wiped it.
The message that no MD5 is found is pretty normal if no MD5 is present, but it would not prevent you from flashing the rom.
My wild guess is that you somehow corrupted /data and it won't mount, but I don't really know because your post lacks anything that might be helpful.
Like specific information.
Try again.
Harder.
Click to expand...
Click to collapse
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
JGuinan007 said:
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
Click to expand...
Click to collapse
jmms1124.
Here is the instructions that I followed that restored my TF700T:
Download and install ADB, Fastboot and the required drivers - Download and run this cool little tool which has it all packed into one: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
NOTE: at the moment Fastboot seems to have issues with Windows 8
This awesome tool installs the ADB and Fastboot.exe to a folder on your C:\ drive (look for a file titled “adb”) as well as the corresponding drivers. This takes about 15 seconds to install following the prompts.
I installed the device drivers - if you have already tried to connect the tablet to your PC and it's recognised as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it.
Download the latest firmware from Asus (Always make sure that you download the correct SKU version -WW, US etc.) and extract the zip twice so you access the blob file (a blob is a collection of binary data stored as a single entity) – copy and paste this blob file into the previously mentioned “adb” folder on your C:\ drive.
Reset the device with a paperclip/needle (about 2 cm down of the SDcard slot)
Power down the tablet and disconnect it from the keyboard dock.
Connect it to your computer via the original USB cable.
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in Fastboot mode and you will see three or 4 icons (depending on the bootloader version). Select the USB icon to get into the Fastboot mode.
Your PC should acknowledge that a USB device has been connected (an audible indication) Don’t panic if the device does not appear under “My Computer” (as mine did not either – Fastboot will still communicate with it), you can go into Control Panel/Hardware and Sound/ Device Manager and you may see “Fastboot” icon, expand this and the device will be represented again by the “Fastboot” icon. Right click, select “Properties”, Driver tab and then select “Update Driver” and allow it to search automatically and update from the internet. This should then update and change to Asus icons. You now can be certain that you have the current device drivers.
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7 press Shift + right click and select "Open command window here".
In the resulting command prompt screen type the following codes (those in bold):
C:\adb\ (or whatever the path to your fastboot folder is..)
fastboot devices (If that command returns a string of numbers and letters, you are good as gold. If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot)
Followed by each in turn of the below, selecting Yes as required and allowing each to complete the process:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
The resulting screen should look something like this below – NOTE, I did make a couple of typos while I was attempting this which returned some multiple choice garble if this happens recheck you input instructions:
E:\asus>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.979s]
finished. total time: 1.980s
E:\asus>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.023s]
finished. total time: 1.025s
E:\asus>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 39.623s]
finished. total time: 39.624s
E:\asus>fastboot erase boot
erasing 'boot'...
OKAY [ 0.303s]
finished. total time: 0.304s
E:\asus>fastboot erase misc
erasing 'misc'...
OKAY [ 0.602s]
finished. total time: 0.603s
E:\asus>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.459s]
finished. total time: 1.460s
fastboot -i 0x0B05 flash system c:\adb\TF700T\blob - depending where you stored your blob, also this was the first time that I saw the loading bar appear on my tablet.
It will now go through the process of reinstalling your Android stock ROM and you should see the something similar to the following:
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.731s]
sending 'system' (800935 KB)...
OKAY [134.276s]
writing 'system'...
OKAY [131.640s]
finished. total time: 267.649s
fastboot -i 0x0B05 reboot
E:\asus>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
E:\asus>
I disconnected and rebooted My Asus TF700T and I now have a fully functioning Tablet with a stock ROM.
It has been reported that after completing this you may have some issues getting back get into recovery, hitting RCK and getting the dreaded dead Android (with a red triangle with an exclamation point in the middle). I have not attempted this but have been led to believe that flashing TWRP 2.7.0.1 via Fastboot works.
All acknowledgement and appreciation for this method should go to Buster99, a Senior Member of XDA Developers
http://forum.xda-developers.com/show...2179759&page=2
And to Snoop05, also a Senior Member of XDA Developers for the awesome ADB/Fastboot/Driver tool.
http://forum.xda- developers.com/showthread.php?t=2588979
To whom I am most grateful for the return of my tablet to a working state, I hope this works for you. Good Luck.
Thanks to Browndog181 for this great instruction he made.
Good luck to bring back live to your tablet.:
Scenic-3.
JGuinan007 said:
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
Click to expand...
Click to collapse
So you got a little software engineer in the house, eh? :cyclops:
For these little rascals you need Apple devices: Safely locked down so the average user cannot do much damage :laugh:
You can do the buster99 described in the post above, but I would leave that as a last resort.
Sounds to me as if your son formatted something and since nothing exciting happened after typing "yes", he tried pushing some other buttons, interrupting the format and corrupting the partition.
I assume you can still boot into recovery and use it and fastboot is also accessible to you. Correct me if wrong.
Use TWRP's build in file manager to check if you can see the contents of your sdcard. If you can, it was not /data he formatted, but /cache or Dalvik. If so, just format cache, wipe Dalvik and reflash the rom
If /data is not accessible you'll have to format it from the Wipe > Advanced menu. That process takes 1 hour+, so send your son out of the house on a play date or some such....
That you see "md5 not found" probably means the box for "Verify MD5" (or "Check MD5" or something similar, can't remember what the official TWRP had there) is checked on the Install page just before you flash. TWRP will abort the installation if it does not find a MD5 for the zip you are trying to flash if you told it to look for one...
Make sure that is unchecked, then flash the rom.
If none of this works, take screenshots or write down the error messages you get and post them.
Here are pictures of what happens when I try to reflash
View attachment 4004171
View attachment 4004172
View attachment 4004173
View attachment 4004174
View attachment 4004180
Yes, /data and /cache cannot be mounted. Did you format them in TWRP?
Your version of TWRP is pretty outdated. You should update it to 2.8+ at the least, the last version is 3.0.2.
Did 2.7 even support f2fs? Can't remember....
Remember that if you format data you end up with ext4 file system and have to convert to f2fs again.
Sent from my TF700T using Tapatalk
I think i'm sending my son to boarding school. I'm not sure if he formatted them he has no idea what he did I know I can only use external sd to try to flash should I get TWRP 3.0.2 to my extenal sd and flash that or will that not work since it may have to be reformated? and how do I go about that?
JGuinan007 said:
I think i'm sending my son to boarding school. I'm not sure if he formatted them he has no idea what he did I know I can only use external sd to try to flash should I get TWRP 3.0.2 to my extenal sd and flash that or will that not work since it may have to be reformated? and how do I go about that?
Click to expand...
Click to collapse
No man, you have a working recovery now. Fix your problems first, then update the recovery.
BTW, I don't even know if you can properly flash Nougatella with TWRP 2.7. Maybe it's YOU who should be sent to boarding school... :angel:
Ok, so go to Wipe > Format Data, type yes and place the tablet on a high shelf. Leave it alone for an hour plus, this takes a while (and make sure it has enough juice)
Then go to Wipe > Advanced > check Cache and swipe the button. This will take a minute or two
Now go back to the home page, go to Mount and see if it lets you mount data, cache and microSD (check mark next to it). If it does not, reboot into recovery, go to Mount and see if they are mounted now. You are probably ok at this point. If you can mount the partitions you can flash a rom, but I think you should update TWRP first.
I don't believe anyone has made a recovery flashable package for 3.0.2 so flash it in fastboot. If you are not sure how, go to the General section and check out my Beginners Guide - it's all in there.
Once that is done, when you reboot (fastboot reboot), be ready to grab the tablet. Let it buzz once, then push and hold the Volume Down button to get into fastboot again and enter recovery through the RCK icon.
You should now have TWRP 3.0.2 on there.
Now convert data to f2fs (there's another guide in General for that), then flash the rom, gapps and SuperSU.
Enjoy
This is a guide to upgrade Nextbook Ares 8, disable encryption, and flash permanent TWRP recovery to device.
Walmart is selling the Nextbook Ares 8 for $62.52
This rom works great, and sound is now back to normal, on other roms sound worked but was very low.
https://www.walmart.com/ip/Nextbook-Ares-8-Tablet-16GB-Quad-Core/43267399
To use, download ares8_5.0_upgrade_5.1.zip, extract and run either Linux script or Windows batch file.
Bootloader must be unlocked
fastboot/adb must be installed system wide and working.
make sure scripts are set to executable
connect tablet to pc, leave connected until tablet reboots and is ready to set up
open terminal in folder where you extracted ares8_5.0_upgrade_5.1.zip
open cmd window where you extracted ares8_5.0_upgrade_5.1.zip
Linux
Code:
adb reboot bootloader
./fastboot.sh
Windows
Code:
adb reboot bootloader
fastboot_cmd.bat
That's it, takes a few minutes to install, leave connected to pc, when completed tablet will reboot to setup screen, setup and enjoy.
Download
https://www.androidfilehost.com/?fid=745425885120720323
Credits
@N810E
@zefie
@vampirefo
vampirefo said:
This is a guide to upgrade Nextbook Ares 8, disable encryption, and flash permanent TWRP recovery to device.
Walmart is selling the Nextbook Ares 8 for $62.52
This rom works great, and sound is now back to normal, on other roms sound worked but was very low.
https://www.walmart.com/ip/Nextbook-Ares-8-Tablet-16GB-Quad-Core/43267399
To use, download ares8_5.0_upgrade_5.1.zip, extract and run either Linux script or Windows batch file.
Bootloader must be unlocked
fastboot/adb must be installed system wide and working.
make sure scripts are set to executable
connect tablet to pc, leave connected until tablet reboots and is ready to set up
open terminal in folder where you extracted ares8_5.0_upgrade_5.1.zip
open cmd window where you extracted ares8_5.0_upgrade_5.1.zip
Linux
Code:
adb reboot bootloader
./fastboot.sh
Windows
Code:
adb reboot bootloader
fastboot_cmd.bat
That's it, takes a few minutes to install, leave connected to pc, when completed tablet will reboot to setup screen, setup and enjoy.
Download
https://www.androidfilehost.com/?fid=745425885120720323
Credits
@N810E
@zefie
@vampirefo
Click to expand...
Click to collapse
@vampirefo and others who contributed, this is the best rom for this 5.0 device yet. At 8 hrs. unplugged, in deep sleep, I had 98% battery left. The interactive governor deep sleep offline bug is gone. The power disconnecting, reconnecting on charge is gone also. The only issue I have noticed, so far, is that the wifi connection logo at the top is not always showing as full or 100%. That is despite being inches from my router. Furthermore, when I use mixplorer, totalcommander or quickpic to access my photos in onedrive, sometimes it is very slow, or fails to connect. When it does connect, the thumbnails are very slow to load. In the older roms this didn't happen. For me this is a minor issue, because I have other means to access onedrive from my computer. So overall this is a great improvement over the older rom. Thanks to all for your hard work and dedication to improve this device!
I am currently running @greatbal rom on my 5.0 it's equal to this rom, I have to remove supersu manually, I hate when a rom includes root, other than that @greatbal rom runs well on my 5.0.
By the way, did you use windows or linux to install the rom?
vampirefo said:
I am currently running @greatbal rom on my 5.0 it's equal to this rom, I have to remove supersu manually, I hate when a rom includes root. other than that @greatbal rom runs well on my 5.0.
By the way, did you use windows or linux to install the rom?
Click to expand...
Click to collapse
I used windows 7. my only experience with linux, besides Android is through bootable usb drives and cds. I have tried Ubuntu this way. The other bootable drives were mostly window repair, backup, and repartitioning disks.
One note to windows users, there are MANY, UAC promts to to approve the running of the fastboot.exe. So you have to stay with the install to approve each of the many prompts. one workaround would be to go into windows settings and temporarily disable UAC. Then, of course, re-enable it later, after the install finishes. There may be a better way to do this though. Under my fastboot.exe properties, on the compatibility tab, I had it set to always run as an administrator. Maybe that is what caused the constant prompts, not sure. And since I have the device re-partitioned and the rom installed, I don't want to go back and test that theory, since I have installed and updated many apps. It was very nice that you had the re-partitioning built into the script for the install. Just as you stated earlier, be patient, the routine takes some time, the device has not locked up.
I probably wouldn't have bought the Ares 8A, if I had had this rom for my old device. It is too late to return the 8A, now. I haven't figured out how to root the new device, without potentially messing it up.
@vampirefo I hate to ask what is probably a stupid-ass question, but I'm still running Batville. Do I need to re-partition before installing this ROM? If so, it has been a long time since I partioned it for Batville so I'm not sure what the original setup was--can you help? Thanks for continuing to work on the device--we all appreciate it.
zerozed99 said:
@vampirefo I hate to ask what is probably a stupid-ass question, but I'm still running Batville. Do I need to re-partition before installing this ROM? If so, it has been a long time since I partioned it for Batville so I'm not sure what the original setup was--can you help? Thanks for continuing to work on the device--we all appreciate it.
Click to expand...
Click to collapse
@vampirefo included a new partition table with the files. In addition, he put the re-partitioning in the fastboot_cmd.bat, so it is automatic.
martyfender said:
@vampirefo included a new partition table with the files. In addition, he put the re-partitioning in the fastboot_cmd.bat, so it is automatic.
Click to expand...
Click to collapse
Is there any benefit (e.g. speed or battery life) with this rom over batville? I'm assuming that the new one is larger.
zerozed99 said:
Is there any benefit (e.g. speed or battery life) with this rom over batville? I'm assuming that the new one is larger.
Click to expand...
Click to collapse
See my info a few posts above. The issue I am having is with wifi, which I never had in any of the other roms.
I tested with a wifi testing app, and the link speed is good, however, the latency is fluctuating from the norm of 2 ms., all the way up to above 1000 ms. I'm not sure what would cause that, as my tablet is within inches of my wireless router. If anybody has any ideas, please let me know. Web browsing seems ok with Firefox and Chrome, but in apps where I access my photos stored on OneDrive, I have problems. I haven't tried any other internet apps to see if there are any issues. I can access videos with vlc, through my LAN, to my desktop computer with no problems.
zerozed99 said:
Is there any benefit (e.g. speed or battery life) with this rom over batville? I'm assuming that the new one is larger.
Click to expand...
Click to collapse
From my personal experience, the biggest benefit is sound, I can listen to music on tablet without Bluetooth or headset.
The sound through the speaker is loud enough to enjoy.
As time permits, I plan on pulling the sound off of this and if possible apply it to my other roms, that lack good sound through speaker.
If all goes well, just applying sound patch to batville will be all that's needed for batville user's to get same sound quality, without the need to switch to this rom.
Batville is a great rom, just lacks good sound quality through speaker, I hope in time to be able to fix that, with a patch.
Sent from my Life_Max using Tapatalk
@vampirefo, This rom has been the best yet for my 5.0 Ares 8. The only problem I have had is with wifi connectivity. So I decided to start over. I re-ran the fastboot_cmd.bat again to reflash the rom. During the install phase it failed and bricked my device, my first. What did I do wrong to cause this?
I can boot into dnx mode and type fastboot devices, and it lists my Baytrail device. Fastboot flash commands fail with errors. adb commands don't work in this mode.
If I type: fastboot boot boot.img, it boots to uefi / bios access menu. I suspect I need a hub, a usb otg adapter, a keyboard and mouse to get the buttons to respond, though. Are there settings in this bio menu which will help me? Is there any way to recover from this that you know of?
In addition I can boot to an efi shell by holding down the home button and the power button. Unfortunately, your info on the wifi came after I did this blunder. I have a twrp backup, I can't get into it to reload the backup.
Any help recovering from this disaster will be greatly appreciated.
Thanks
Edit: I found this post:
https://forum.xda-developers.com/member.php?u=4821597
Not sure where to get this file: efilinux.efi. Is it the one in your esp folder or the one in the esp.zip?
Thanks
I solved this my self by following @social-design-concepts directions, then running the fastboot_cmd.bat to re-flash the system. Anybody have any ideas what may have caused this data corruption in the first place?
You want me to guess what you did wrong? No ideal, seeing it worked the first time and third time for you, and everytime for me, I would guess user error.
Sent from my Life Max using Tapatalk
vampirefo said:
You want me to guess what you did wrong? No ideal, seeing it worked the first time and third time for you, and everytime for me, I would guess user error.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
No, sorry, this is all I did:
I rebooted to bootloader. Then I ran your fastboot_cmd.bat. It never had errors in the command window until it was running the flash commands. Then it rebooted to the dnx window. So it didn't appear to be a user error. I am using minimal adb and fastboot. I have all of the files in that folder. I shift, right click, then choose open a command prompt here.
Instead of typing the command in windows, I dragged and dropped it in the command prompt window. I guess it will be a mystery. However, I did do a TWRP backup this time, even before flashing SuperSu and busybox.
I did use your fix for the captive portal and my internet seems to have improved, So thanks again.
Just curious, what is the: -S 200M, in the flashing system command?
martyfender said:
No, sorry, this is all I did:
I rebooted to bootloader. Then I ran your fastboot_cmd.bat. It never had errors in the command window until it was running the flash commands. Then it rebooted to the dnx window. So it didn't appear to be a user error. I am using minimal adb and fastboot. I have all of the files in that folder. I shift, right click, then choose open a command prompt here.
Instead of typing the command in windows, I dragged and dropped it in the command prompt window. I guess it will be a mystery. However, I did do a TWRP backup this time, even before flashing SuperSu and busybox. I did use your fix for the captive portal and my internet seems to have improved, So thanks again.
Click to expand...
Click to collapse
I don't use minimal adb, that is a problem, you need to be system-wide.
Use system-wide method, it's a better way to use adb and fastboot. The script was designed to be ran based on system-wide access.
https://forum.xda-developers.com/showthread.php?p=48915118
-S 200M is sparse, the 200M is the size or chunk I tell it to split, this can be raised or lowered depending on speed of computer, I am using a Windows tablet to run the windows batch file.
My Linux could push it much faster, 500 or more, but 200 is safe, slow, and steady.
Sent from my NXA8QC116 using Tapatalk
vampirefo said:
I don't use minimal adb, that is a problem, you need to be system-wide.
Use system-wide method, it's a better way to use adb and fastboot. The script was designed to be ran based on system-wide access.
https://forum.xda-developers.com/showthread.php?p=48915118
-S 200M is sparse, the 200M is the size or chunk I tell it to split, this can be raised or lowered depending on speed of computer, I am using a Windows tablet to run the windows batch file.
My Linux could push it much faster, 500 or more, but 200 is safe, slow, and steady.
Sent from my NXA8QC116 using Tapatalk
Click to expand...
Click to collapse
I had it set at one time in the system environmental variables, but when I redid my system I forgot to re-add it. Thanks for the link. I had seen that in the past, but it had older versions of adb and fastboot. I see now that it has been updated, so thank again.
Edit: I checked and apparently I did have Minimal ADB and Fastboot entered in the system environmental variables, which would make it system wide. I downloaded and installed your recommendation. it added an additional variable after: C:\adb.
Here may be the issue: I updated Minimal ADB and Fastboot with an installer and it appears it added an additional entry for it. I notice to that windows live has two entries also:
C:\Program Files\Mozilla Firefox;C:\Windows\System32;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Minimal ADB and Fastboot;C:\Program Files (x86)\Windows Live\Shared; C:\Program Files (x86)\Minimal ADB and Fastboot;C:\adb.
I think I should remove the double entries?
Here is a link for a microsoft script the remove duplicate path variables:
https://gallery.technet.microsoft.com/scriptcenter/How-to-check-for-duplicate-5d9dd711
I ran that script, but my entries remain the same. i'm not sure why.
I guess the simplest solution is to remove Minimal ADB and Fastboot, its variables and keep the other ADB.
This Ares 8 which originally came with 5.0 is running great since I redid it and applied your wifi fixes to it.
I find myself using it most of the time, over the new Ares 8A, because I have root on it and don't possess enough knowledge to feel safe in trying to root the Ares 8A, or building a working TWRP for it.
By the way, I had 98% battery left after leaving it overnight. That is a far cry from what I had with the 701Q and Batville roms. That is great.
With Batville I could never get contacts to work, despite trying playstore and other fixes. In addition, the sound is good with this new rom.
I don't do much gaming anymore, but i do have GT Racing 2 installed on the External microSD card, Using @vickybonick Apps2SD, and this graphic intensive game runs very well on it.
Thanks again for your great work.
By the way, in the past with the original 5.0 rom, I tried using three different SanDisk high speed UHS-1, Class 10 cards with Apps2SD, and all of them had good write speeds, but poor read speeds. I finally returned those cards and went with the Samsung EVO series. The read and write speeds are great on this card. I used several test apps, both on Windows and Android, to test them. Has anybody else had similar experiences with different brands of high speed cards?
If you have more than one adb install listed in the environmental variables, the first listed takes precedence in system wide access. I tested this by changing the order with Rapid Environment Editor. I viewed which one was running in Process Explorer.
Rapid Environment Editor will also show any invalid paths. This is of academic interest, as the simplest solution, is of course, to only have one adb installed system wide. If you run a command prompt from the folder where each adb is installed, that one will run, instead of the one installed system wide, unless you are already in the folder where the system wide is installed. (shift right click, choose open command prompt here).
That is what I did and should have worked fine, it always has before. So I am "beating a dead horse to death", in the pursuit of knowledge. i hope this helps someone else as well, that is learning, like me. By the way, is this considered OT?
I hate to be a thorn in your side, but:
Apparently I spoke too soon about the wifi connection working better. And please keep in mind I am comparing it to what I had on all three previous roms: the original 5.0, i708q and the Batville roms, and my newer Ares 8A. Also please keep in mind that the device is less than 2ft. from my wireless router in my tests.Using WiFi Network Analyzer, I see a continual fluctuation in the dBm signal strength, all the way from the normal -34, all the way up to the -70 to -92 range. In addition, the latency goes from normal 3-4 ms., all the way into the hundreds and even thousands ms. The older roms did not do this in the analyzer. My new Ares 8A remains in the -32-42 dBm signal strenth, and the latency stays in the 3-4ms range.
I seem to have improved things slightly by changing the following things in my router:
Allow n devices only
bandwidth set from auto 40mhz/20mhz, to 20mhz only
protected mode (not to be confused with WPS):
rotected Mode
NOTE: In most situations, best performance (throughput) is achieved with Protected Mode OFF. If you are operating in an environment with HEAVY 802.11b traffic or interference, best performance may be achieved with Protected Mode ON.
(I'm not certain if protected mode helped, or not.)
Is there anything I can do on the tablet to improve this or troublshoot it?
Furthermore are the system wifi files in the newer rom different to what was in the working i708q and Batville roms? Sometimes, turning off wifi and turning it back on helps for a while. Also I forgot to point out that the fan shaped wifi connection symbol fluctuates from full to partial, also. All other devices I have turned on to test, show no problems, that I can tell.
I haven't ruled out interference as I live in an apartment complex where I can see several neighbors on all non-overlapping channels 1, 6 and 11. However the older roms, the new 8A and other tested devices have no detectable problems with my wireless router. Does anybody have any suggestions?
Like I've said in the past this is a great rom for this device, if I can get this problem resolved.
Thanks
For my wireless configuation and router, I was able to improve my speed and connection by reading linux documentation on the hostapd.
I edited the hostapd.conf located in system/etc/wifi, changing the following entries:
preamble=0
dissoc_low_ack=0
I'm not sure, but maybe my wireless router doesn't handle the default settings as well?
If that was the case, though, why did the same defaults work well with the previous roms?
preamble=0 "Set optional use of short preamble."
0 sets a long preamble instead of a short one
dissoc_low=0 "Disassociate stations based on excessive transmission failures or other indications of connection loss. This depends on the driver capabilities and may not be available with all drivers."
0 turns this off.
My congested wireless environment may be partially to blame for this. there are at least 4 clients on each of the three non-overlapping channels of 1,6 and 11, respectively.
If anybody has any additional thoughts on this, let us all know.
Thanks
UPDATE: apparently, the above changes didn't help. In the terminal when I type: busybox ifconfig, I see dropped packets under p2p and wlan0 for rx, but not for tx. This has happened on other wireless networks as well. Maybe not as bad though. I'm not 100% sure though as I haven't run ifconfig on those other networks.
I am considering ordering an ASUS 3-In-1 Wireless Router (RT-N12), or an Asus RT-N12 D1 Wireless Router - IEEE 802.11n RT-N12/D1, to see if this improves things. I have no AC devices, so an AC router seems like a pricey overkill for me. However an AC might be more future proof. I don't have a new flat screen tv to stream to. I have an old Sony 36" CRT, which I haven't turned on for over a year, as I watch streamed TV shows on the internet, from my computer. So finally, the bandwidth that AC affords, doesn't seem necessary.
Well, I managed to (sort of) kill my Ares 8. I already had 5.1 installed and working an thought, "I'll run this and start fresh." Everything looked like it went normally but when the tablet rebooted, I have:
Entering DnX mode.
Waiting for fastboot command...
Tethered recovery gets this:
***********************************************************************
FASTBOOT TETHERED RECOVERY LAUNCHER 07-24-2015
***********************************************************************
=======================================================================
DEVICE STATUS: FASTBOOT-ONLINE
DEVICE INFORMATION: BaytrailBA302518 fastboot
=======================================================================
copy needed files to our device
sending '/tmp/recovery.zip' (7151 KB)...
OKAY [ 0.285s]
writing '/tmp/recovery.zip'...
FAILED (remote: unknown command)
finished. total time: 0.294s
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.036s]
writing '/tmp/recovery.launcher'...
FAILED (remote: unknown command)
finished. total time: 0.049s
we need to stop logcat before replacing it
...
FAILED (remote: unknown command)
finished. total time: 0.005s
sending '/system/bin/logcat' (349 KB)...
OKAY [ 0.021s]
writing '/system/bin/logcat'...
FAILED (remote: unknown command)
finished. total time: 0.026s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
FAILED (remote: unknown command)
finished. total time: 0.005s
Everything tethered or not comes up (remote: unknown command)
martyfender what exactly did you do to get tethered recovery to work?
N810E said:
Well, I managed to (sort of) kill my Ares 8. I already had 5.1 installed and working an thought, "I'll run this and start fresh." Everything looked like it went normally but when the tablet rebooted, I have:
Entering DnX mode.
Waiting for fastboot command...
Tethered recovery gets this:
***********************************************************************
FASTBOOT TETHERED RECOVERY LAUNCHER 07-24-2015
***********************************************************************
=======================================================================
DEVICE STATUS: FASTBOOT-ONLINE
DEVICE INFORMATION: BaytrailBA302518 fastboot
=======================================================================
copy needed files to our device
sending '/tmp/recovery.zip' (7151 KB)...
OKAY [ 0.285s]
writing '/tmp/recovery.zip'...
FAILED (remote: unknown command)
finished. total time: 0.294s
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.036s]
writing '/tmp/recovery.launcher'...
FAILED (remote: unknown command)
finished. total time: 0.049s
we need to stop logcat before replacing it
...
FAILED (remote: unknown command)
finished. total time: 0.005s
sending '/system/bin/logcat' (349 KB)...
OKAY [ 0.021s]
writing '/system/bin/logcat'...
FAILED (remote: unknown command)
finished. total time: 0.026s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
FAILED (remote: unknown command)
finished. total time: 0.005s
Everything tethered or not comes up (remote: unknown command)
martyfender what exactly did you do to get tethered recovery to work?
Click to expand...
Click to collapse
I didn't use a tethered recovery, I used the twrp recovery posted at the start of this thread. It is in the ares8_5.0_upgrade_5.1.zip.
When I had similar problems, I found a post by [MENTION=5368024 [user=4821597]@social-design-concepts[/user] https://forum.xda-developers.com/showpost.php?p=65435780&postcount=409 in the original ares 8 thread to fix the problem:
"
Member
94 posts
Thanks: 30
Quote:
Originally Posted by social-design-concepts
"thats the uefi / bios access menu you'll need an usb otg adapter and most devices ( not all ) require use of a powered usb hub ( which i personally recommend regardless as devices that use more power can short out the port ) and keyboard and mouse to navigate it. but it looks as if you esp is corrupt if you have the efiloader and droidboot.img you can try.
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
this should get you back into droidboot / fastboot where you can then partition your device and reflash the esp and the reset of android.
@social-design-concepts, thanks for this post. When I tried to reinstall vampirefo's latest 5.1.1 rom, ported to work on the 5.0 device, it failed and Could only get into dnx mode. I used your instruction to fix the ESP partition, then reinstalled the rom, with no problems. It is running great now.
Thanks, again."
I used the above commands and files within the rom posted above, so I didn't even need a usb otg adapter to do it. I believe I used the droidboot.img and efilinux.efi. The efilinux.efi is in the esp.zip. unzip to the root of your folder where you have adb and fastboot installed. The rom files must also be unzipped to that location.
The above commands are run through an adb and fastboot command prompt, from your computer. Those are the windows commands. they would be slightly different if you are on linux. Then I rebooted the tablet back into fastboot mode: fastboot reboot bootloader, which worked again, ran the fastboot_cmd.bat to reflash the rom again. This was all done from the computer with an adb and command prompt, using fastboot commands, of course. Type fastboot devices, to make sure your device is showing up, before proceeding
I never figured out the cause of the problem when I reflashed this rom the second time, but I suspect I should have done a factory reset before doing it. It was flashing the above files that gave me the ability to get into fastboot bootloader again, then I reflashed the whole rom the third time and it worked as it did the first time I did it.
Currently I am using the newer, twrp 3.1 recovery he posted in the ares 8 5.1 problems thread.
UPDATE: if you don't have a permanent recovery installed, this may or may not work in the tethered, temp, twrp recovery. I don't know as I have never used the tethered, temp, recovery.
Actually, I think I used the fastboot commands in dnx mode to flash the droidboot.img and efilinux.efi, rebooted into the bootloader: fastboot reboot bootloader and then ran the fastboot_cmd.bat to reflash the rom.
And of course, you have to make sure adb and fastboot drivers are setup correctly and recognizing your device, for all of the above to work. I tried to retrace my steps. I hope I didn't forget any of them!
Good Luck!
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.