Related
I have searched the threads and have not been able to find a problem like mine
I modded my Gtablet with CyanogenMod 6.14b and have also installed the Gapps and all is working great!. But I wanted to do a image backup so I powered off and then using the Pwr VOL+ keys to try and enter recovery. I get the "android" text on the screen for about 15 seconds and then it just boots into cyanogen. I have done the following but to no avail
1) copy new clockworkMod Update.zip and recovery folder to root of MicoSD
no luck
2) same as above, but to mtn/emmc (What Cyanogen now calls Internal SDCARD)
3) Changed the value in command file from --update_package=SDCARD2:\update.zip
to
--update_package=SDCARD:\update.zip
I also noted that there are folders EMMC and SDCARD listed under "/" as well as under "/MNT" they appear to be the same. Is this normal???
No mater what I do, I cannot get into recovery Mode.
Any help will most likely get you into heaven
Success!!!! Was able to restore using the recovery.img in clockworkMod Many thanks to ngorgi and ReoBeet for the help.
Did you use the clockworkmod specifically for our device and the one I use, which is .08? It sounds likely, but I wanted to confirm that.
Assuming that you did and that recovery is borked, you won't be to fix it the normal way since there's no recovery to flash recovery (if that makes sense). You might have to try either flash_image which a few people have suggested might work, or nvflash. I personally have used the latter.
If you can get APX mode working and get bekit's nvflash setup working, you can just flash partition 9 with bekit's recovery.img and that might work. I have a post on nvflash here: http://forum.xda-developers.com/showthread.php?t=861950
i Used the .08 as your surmised, My question is how did the recovery get lost?
When the PWR + VOL+ get used to enter recovery, what file is executed?
It took me several days to configure my tablet, it would be a shame to lose all that work.
But If that is my only option, then NVFlashing I will go
Try to change the value in the command file to...
--update_package=EMMC:\update.zip
Might do it... you can't point it to SDCARD unless you place the update.zip on an inserted Micro SD Card.
- AdamZ
I'm not sure how your recovery is borked, but I'm assuming that it is. You can use nvflash to just flash recovery and nothing else - technically you shouldn't lose anything that way (but, backing up first is always a good idea).
Just Tried that (Good Idea), but no luck. I believe that the COMMAND file is only used when you execute the ZIP from recovery so It appears I am out of luck. The good news is that my Tablet is running great, just have no way to backup or restore an Image.
I may be suborn, but I believe there must be a way to get recovery working again. I do see that there is a recovery.img file on both my SDCARD and EMMS.
When I try and start recovery, I do get the Recovery Key Detected, just never goes into the recovery program.
This is an interesting problem ...
roebeet, Did not see your post until just now, I will reseach the NVFlash as I see there are a few threads on using it. I assume you can select what to flash.
Thank your
Tried the NVFLash and here is what I got
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvflas
loader.bin --download 9 recovery.img
Nvflash started
USB device not found
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvflas
loader.bin --download 9 recovery.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17141188448001d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x10800
sending file: bootloader.bin
| 933404/933404 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: recovery.img
- 589824/3463168 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>
Help!!!!
BUt it still boots fine
Now on trying recovery Mode it says Booting Recovery Image after recovery key detected (So a little progress is made)
I am wondering if I need to get the specific recovery image for the recovery partition. I was just using the one that came with NVFlash. I downloaded the NVFlash_Gtablet and there are 11 image files so I do not know what Image file is for the Recovery Partition.
Am i on the right track yet???
JUST fixed this problem for myself, I'm gonna post another thread with a how-to of how I fixed this.
brookfield said:
I am wondering if I need to get the specific recovery image for the recovery partition. I was just using the one that came with NVFlash. I downloaded the NVFlash_Gtablet and there are 11 image files so I do not know what Image file is for the Recovery Partition.
Am i on the right track yet???
Click to expand...
Click to collapse
Recovery is image 9. There is a recovery image floating around here that can be used in place of image 9 and it will put clockwork back.
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.
With the latest version of TWRP (2.8.5.0) I installed that zombi 5.02 rom a few days ago. It was running VERY slow, so I went back into TWRP a few hours ago and figured I would clean up the device and then re-install the rom.
So I used TWRP to wipe the device clean (I selected every partition to wipe, which I suspect is what the problem is). After doing this, I ran the install of the rom which seemed to run fine (although oddly, it seemed to install too fast, as opposed to when I installed it before).
Once I rebooted the device, I saw a quick message about a missing partition, and then it booted into TWRP recovery. but here is where the problem started. TWRP loads as far as you see the blue curtain background with test "teamwin" and then the screen clears for a sec, and then the blue curtain background appears again with the "teamwin" text.
This repeats forever. I can't get it to stop doing this.
I booted into fastboot, and via adb I re-installed the 2.8.5.0 twrp blob file. No errors during the install at all, however after rebooting the device, I am having the exact same issue.
I've tried re-installing twrp 3 times this way, but no matter what I do, I cannot get twrp to get out of this boot cycle.
It is odd that I can install twrp via adb over and over, yet it still has the same problem as before.
Even if i messed up by wiping every partition, why would the TWRP install succeeed, yet the program not run?
Anybody have an idea as to what I can do in order to get twrp back up and running? And if I do, is there something else I need to do to get all the partitions back up, or in theory will installing a rom re-create everything as needed?
Thanks for any help you guys can provide!
gbako said:
Once I rebooted the device, I saw a quick message about a missing partition, and then it booted into TWRP recovery. but here is where the problem started. TWRP loads as far as you see the blue curtain background with test "teamwin" and then the screen clears for a sec, and then the blue curtain background appears again with the "teamwin" text.
This repeats forever. I can't get it to stop doing this.
Click to expand...
Click to collapse
While TWRP is in the restart loop, you can try this on your connected PC:
Code:
adb pull /tmp/recovery.log
adb shell cat /proc/partitions > partitions.txt
The first gets TWRP's log file from which we should be able to see why it fails to start, the second gets a list of all partitions to see if mmcblk0p1 to ...p8 or ...p10 are there.
_that said:
While TWRP is in the restart loop, you can try this on your connected PC:
Code:
adb pull /tmp/recovery.log
adb shell cat /proc/partitions > partitions.txt
The first gets TWRP's log file from which we should be able to see why it fails to start, the second gets a list of all partitions to see if mmcblk0p1 to ...p8 or ...p10 are there.
Click to expand...
Click to collapse
--
I retrieved the logs as you suggested. I did this twice because after I retrieved the logs, I was looking at the partitions.log file and saw that only 3 partitions appeared. I know there should be more partitions (I don't know what they are called, but I know there should be more). So I was playing around with the fastboot.exe command, and I saw a command (fastboot -w). It said this command "erases userdata and cache". Well, it looked like something good to try, so I ran the command I've attached a file to this post called "fastboot.txt" that shows the output of this command.
Anyways, after doing this (thinking maybe this would do something), I went back into fastbook, and re-installed TWRP once again. Then I rebooted the tablet, and viola! It booted into twrp. Think I was so smart, I figured I would try to install my rom once again, so I started the installer of the rom, but at the very first screen of the installer where it shows device information, I saw what was obviously an issue. System size was showed as -1 MB, and Data Size was also shown as -1 MB. Not looking good, I exited the installer which puts me back into TWRP, and now I see a bunch of error messages about missing partitions.
On a hunch, I rebooted the tablet (back into reovery), and now I am back to the same thing, where TWRP will constantly load the blue curtain backgroud, show the word "teamwin" and then clear the screen, and repeat the process endlessly. So I now re-ran the two commands to retreive the partition info and the recovery log. The recovery log doesn't make much sense to me, but interestingly the partition log now shows a whole bunch more partitions. However, TWRP is once again back to it's boot loop.
So rather than re-trying my silly "fastbook -w" attempt, I will post this message, provide the request log info, and hope one of the experts here have a kind suggestion for me to try
Thanks guys for any help!
P.S. All the logs are in the ZIP file. I also attached a pic I took of the zombi rom installer, showing the partition size being -1 MB
The files "partitions1.txt" and "recovery1.log" are the files I retrieved from the tablet prior to using that "fastboot -w" command, the "partitions2.txt" and "recover2.log" are the files I retrrieved from the tablet after running that command, re-installing twrp and then having it go back into it's endless boot loop.
gbako said:
The files "partitions1.txt" and "recovery1.log" are the files I retrieved from the tablet prior to using that "fastboot -w" command, the "partitions2.txt" and "recover2.log" are the files I retrrieved from the tablet after running that command, re-installing twrp and then having it go back into it's endless boot loop.
Click to expand...
Click to collapse
Your logs indicate a problem with the "cache" partition. TWRP seems to crash after "Full SELinux support is present", and the next thing it does is trying to mount the cache partition. Your Fastboot log indicates a problem with cache too.
Try this:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
(make sure you get the "p2" right *before* you press Enter!)
If this doesn't help, I also need the kernel log - do this after the previous command failed or within the first 3 minutes of a fresh boot into TWRP:
Code:
adb shell dmesg > dmesg.txt
That worked! Tablet works once again!
_that said:
Your logs indicate a problem with the "cache" partition. TWRP seems to crash after "Full SELinux support is present", and the next thing it does is trying to mount the cache partition. Your Fastboot log indicates a problem with cache too.
Try this:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
(make sure you get the "p2" right *before* you press Enter!)
If this doesn't help, I also need the kernel log - do this after the previous command failed or within the first 3 minutes of a fresh boot into TWRP:
Code:
adb shell dmesg > dmesg.txt
Click to expand...
Click to collapse
---
That worked! Shortly after running that "adb shell make_ext4fs /dev/block/mmcblk0p2" command you had suggested, the tablet rebooted it self and the last ROM I had installed in it automatically booted up. It acted as though I had just installed it, so I went thru the standard setup (enter Google ID, etc...). The rom still runs pretty horribly (very slow and sluggish), but that's an issue with the rom hehe I am also able to boot back into TWRP without any problems. It seems that partition was the problem.
Thank you very much for your help; much appreciated!
I had the same problem with my TF700T with an endless loop in the TWRP start screen. I found an unkown device in my device manager called "TRANSFORMER" and i installed the Universal_Naked_Driver. Now i had access with ADB and i could clean the cache with the command here. Now my TF700T is back to life. Thanks a lot !
I seem to have a similar problem. The pad started having random reboots but it managed to fully boot. Since yesterday it is in the reboot loop. When trying to boot into twrp 2.8.7.4 it shows the teamwin screen for a short while and then reboots again.
I pulled the files requested above:
recovery.log
partitions.txt
dmesg.txt
I also tried:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
which shows:
Code:
C:\adb>adb shell make_ext4fs /dev/block/mmcblk0p2
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
However the recommended steps don't seem to help in my case.
I'll attach the log files. (If I can find the attachment icon that is)
Thanks for any help you guys can provide!
Rom and bootloader version please. To attach the logs use your browser to access XDA
Hi berndblb,
thanks for the quick reply.
Rom version is : KatKiss-6.0_TF700T_022.zip
Boot loader taken from the fastboot screen: Android cardhu-user bootloader <1.00e> released by "ww_epad-10.6.1.14.10-20130801" A03
As to attaching the files I think I'm blind as I'm not seeing the option to do so.
Looks like this is only an issue in this threat as I do have the icon in other posts.
Yeahh I think I got it.
After much trying various recommendations I did
fastboot erase misc
fastboot erase userdata
This allowed me finally to go into recovery without a reboot.
I could flash the new KatKiss-6.0_TF700T_024.zip and now the pad is on it's first startup. So far so good. Crossing fingers.
Is it possible that a recently installed app could cause such a problem?
Cathrin said:
Yeahh I think I got it.
After much trying various recommendations I did
fastboot erase misc
fastboot erase userdata
This allowed me finally to go into recovery without a reboot.
I could flash the new KatKiss-6.0_TF700T_024.zip and now the pad is on it's first startup. So far so good. Crossing fingers.
Is it possible that a recently installed app could cause such a problem?
Click to expand...
Click to collapse
Hard to say... Could be...
I am not very good at reading logs but the only problem I see in dmsg is a failure to set cpu frquency. Were you running Zombi-Pop? Looks as if you were running a _that kernel at least. Did you overclock?
berndblb said:
Hard to say... Could be...
I am not very good at reading logs but the only problem I see in dmsg is a failure to set cpu frquency. Were you running Zombi-Pop? Looks as if you were running a _that kernel at least. Did you overclock?
Click to expand...
Click to collapse
I think my very first upgade to 5.1.1. lolli pop has been a Zombi-Pop and a overclocking yes. But since then only the KatKiss versions.
At least everything works fine again now.
So thanks for the help.
Looks like I have this constantly boot to twrp issue. It doesn't stay into twrp long enough to do anything.
adb pull /tmp/recovery.log
Gives me error: Protocol fault (couldnt read status: no error
adb shell cat /proc/partitions > partitions.txt
Gives me the same error above.
adb shell make_ext4fs /dev/block/mmcblk0p2
Gives me filesystem with parameters----created filesystem with 11/27392 inodes and 3534/109568 blocks
fastboot erase misc
Gives me waiting for device
I was on Katkiss 22 before this happened.
Any help would be appreciated.
Hi Isham.padron,
yes that sounds familiar.
I could only get the logs with adb shell or put when I hit return at a very specific moment.
It did fetch the files only when the blue teamwin window has been shown.
Though my recovery.log always looked a bit too short as if the reboot was coming in the way.
for me in the end only fastboot erase userdata did the trick. Everything else failed.
fastboot erase userdata cause it to wait but then nothing happens. ADB seems to be more responsive. IDK, I loved my TF700 and Katkiss gave it new life.
If you get 'waiting for device' your pc does not recognize the tablet. You may have to install fastboot drivers. Check the entry in Device Manager. How does the tablet show up?
In device manager is shows up as ADB. That kind of explains it. I'm using a windows 10 pro machine and I installed ADB/Fast boot with this http://forum.xda-developers.com/showthread.php?t=2588979
Are there issues with Win 10? I dont know how to proceed.
When I do the vol up(left) and power combo and it boots into twrp and then reboots regardless. I don't have the option screen anymore
Did you disable driver verification in Windows before running the tool? Otherwise they probably did not install properly. Windows is a pain with drivers and Win 8 and 10 are very finicky with fastboot...
Although if you have the adb composite interface showing up that's kinda good news. Watch the tablet and Device Manager at the same time and try to get a feeling for when the adb connection is there. Try to hit enter on the already typed 'adb devices' command and see what you get.
This could be tricky and rake many tries but you want to try is to push a small file to the tablet (bootit. ko) and then ins is that file to kick the tablet back into the bootloader. Probably your only chance..
Read this: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Good luck!
I am able to do this.
adb push bootit.ko /
results are (27690 bytes in .023s)
When I run "adb shell insmod bootit.ko" I get Error : protocol fault (no status)
I see that on windows it starts installing MTP USB but then it fails when the reboot happens. Tablet continues to reboot.
Any ideas? I miss the TF700
This guide is to root the Australian Vodafone Huawei Y6 Elite (LYO-L02). This phone has recently become very popular in the land down under because there was several promotions happening that makes it a bargain. Being able to root it (and leading to potential custom ROM for it) makes it even better.
WARNING: The guide involves unlocking the device's bootloader. By doing so the phone will be factory formatted. Therefore, please backup your data before proceeding. Also, your warranty is now voided.
A short version of the guide for Android veterans are as followed:
1. Make sure adb and fastboot are available on your operating system
2. Download huawei-y6-elite-root-twrp.zip archive and extract it
3. Enable developer options and enable OEM unlock
4. Unlock bootloader from HUAWEI website: https://emui.huawei.com/en/plugin/unlock/index
5. Flash TWRP recovery for the device (huawei-y6-elite-twrp-3.0.2.img)
6. (Optional) Backup the stock firmware
7. Use TWRP to install SuperSU-v2.78.zip
More detailed instructions are as followed:
1. Make sure adb and fastboot are available on your operating system.
You can refer to the following article: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 .
To make sure you have adb and fastboot, open your operating system terminal (we will use this a lot in this guide) and type in
Code:
adb version
fastboot --version
And you should be greeted with (version numbers might be different)
Code:
$ > adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
$ > fastboot --version
fastboot version eac51f2bb6a8-android
2. Open device's Settings -> About Phone -> Tab on Build number several times until you are prompted with "You are now a developer".
Go back to Settings -> Developer options -> Toggle on:
- Developer options
- Enable OEM unlock
- USB debugging
3. Plug your device to your computer, in your terminal / command prompt, type in
Code:
adb devices
On the device, if asked, please trust the computer.
Doing adb devices again to confirm that your device is active and the computer has recognised it. You should see something like
Code:
List of devices attached
AKT012345678912 device
(If you see there are more than one devices attached, please unplug them and leave just the Huawei Y6 Elite plugged in. This can prevent accidentally triggering commands on other devices.)
4. Unlocking the bootloader
Go to: https://emui.huawei.com/en/plugin/unlock/index . Register an account if you haven't got one, then login, go to Downloads -> Unlock devices (this might take a while to load, or simply just use the URL again after logging in to go straight to the unlock page.
In the unlocking page, select:
- Before EMUI5.0
- Smartphone
- Product Model:
- Serial number: Get yours in Settings -> About phone -> Status -> Serial number
- Product IMEI: Open your dialer -> type in *#06#
- Product ID: Open your dialer -> type in *#*#1357946#*#*
Type in verification code and hit "Commit", the unlocking password will then be shown to you (mine looks like EF**************26)
5. Reboot into bootloader. There are two ways you can do this:
Either plug the device into the computer and type
Code:
adb reboot bootloader
Or power off the phone, hold volume down and power
If you successfully get to the bootloader, a small text at the bottom saying "=> FASTBOOT mode..." is shown to you.
6. Plug the device to your computer, type
Code:
fastboot devices
You should see
Code:
AKT012345678912 fastboot
7. (WARNING: Your device will be wiped, backup your data) Unlock bootloader by typing the following command (replace your password with the actual unlock password from step 4
Code:
fastboot oem unlock password
8. After unlocking, the device will reboot, and you will be greeted with the factory default settings.
Enable developer mode and OEM Unlock again (see step 2)
9. Reboot to bootloader (see step 5-6)
10. At this stage, you should see a red text saying "FRP Unlock" at the bottom
11. Flash the custom TWRP recovery by using
Code:
fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img
(point huawei-y6-elite-twrp-3.0.2.img to where you extract the img file)
12. After flashing the recovery, switch off the device (remove the battery), then boot to recovery using the Volume Up and Power button
13. You will be greeted with TWRP welcome. Do NOT select the Read-only option.
14. (Optional) It is recommended that you backup your stock firmware, so that you can restore back to stock later on if you need to. To do so, from TWRP click on "Backup", select "Boot", "Recovery", "System", "System Image" and "Data" then Swipe to Backup. If you don't have enough storage, you can change to backup the firmware to external SD Card by selecting "Select Storage".
15. Rooting: plug the device to your computer, then execute the following command:
Code:
adb push SuperSU-v2.78.zip /sdcard/
This will copy the SuperSU-v2.78.zip to your internal user storage. From TWRP, select "Install" -> navigate to /sdcard -> select the zip file, select "Reboot after installation is complete", Swipe to confirm Flash
16. After the zip file is installed, your device will be Rooted.
nkahoang said:
This guide is to root the Australian Vodafone Huawei Y6 Elite (LYO-L02). This phone has recently become very popular in the land down under because there was several promotions happening that makes it a bargain. Being able to root it (and leading to potential custom ROM for it) makes it even better.
WARNING: The guide involves unlocking the device's bootloader. By doing so the phone will be factory formatted. Therefore, please backup your data before proceeding. Also, your warranty is now voided.
A short version of the guide for Android veterans are as followed:
1. Make sure adb and fastboot are available on your operating system
2. Download huawei-y6-elite-root-twrp.zip archive and extract it
3. Enable developer options and enable OEM unlock
4. Unlock bootloader from HUAWEI website: https://emui.huawei.com/en/plugin/unlock/index
5. Flash TWRP recovery for the device (huawei-y6-elite-twrp-3.0.2.img)
6. (Optional) Backup the stock firmware
7. Use TWRP to install SuperSU-v2.78.zip
More detailed instructions are as followed:
1. Make sure adb and fastboot are available on your operating system.
You can refer to the following article: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 .
To make sure you have adb and fastboot, open your operating system terminal (we will use this a lot in this guide) and type in
Code:
adb version
fastboot --version
And you should be greeted with (version numbers might be different)
Code:
$ > adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
$ > fastboot --version
fastboot version eac51f2bb6a8-android
2. Open device's Settings -> About Phone -> Tab on Build number several times until you are prompted with "You are now a developer".
Go back to Settings -> Developer options -> Toggle on:
- Developer options
- Enable OEM unlock
- USB debugging
3. Plug your device to your computer, in your terminal / command prompt, type in
Code:
adb devices
On the device, if asked, please trust the computer.
Doing adb devices again to confirm that your device is active and the computer has recognised it. You should see something like
Code:
List of devices attached
AKT012345678912 device
(If you see there are more than one devices attached, please unplug them and leave just the Huawei Y6 Elite plugged in. This can prevent accidentally triggering commands on other devices.)
4. Unlocking the bootloader
Go to: https://emui.huawei.com/en/plugin/unlock/index . Register an account if you haven't got one, then login, go to Downloads -> Unlock devices (this might take a while to load, or simply just use the URL again after logging in to go straight to the unlock page.
In the unlocking page, select:
- Before EMUI5.0
- Smartphone
- Product Model:
- Serial number: Get yours in Settings -> About phone -> Status -> Serial number
- Product IMEI: Open your dialer -> type in *#06#
- Product ID: Open your dialer -> type in *#*#1357946#*#*
Type in verification code and hit "Commit", the unlocking password will then be shown to you (mine looks like EF**************26)
5. Reboot into bootloader. There are two ways you can do this:
Either plug the device into the computer and type
Code:
adb reboot bootloader
Or power off the phone, hold volume down and power
If you successfully get to the bootloader, a small text at the bottom saying "=> FASTBOOT mode..." is shown to you.
6. Plug the device to your computer, type
Code:
fastboot devices
You should see
Code:
AKT012345678912 fastboot
7. (WARNING: Your device will be wiped, backup your data) Unlock bootloader by typing the following command (replace your password with the actual unlock password from step 4
Code:
fastboot oem unlock password
8. After unlocking, the device will reboot, and you will be greeted with the factory default settings.
Enable developer mode and OEM Unlock again (see step 2)
9. Reboot to bootloader (see step 5-6)
10. At this stage, you should see a red text saying "FRP Unlock" at the bottom
11. Flash the custom TWRP recovery by using
Code:
fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img
(point huawei-y6-elite-twrp-3.0.2.img to where you extract the img file)
12. After flashing the recovery, switch off the device (remove the battery), then boot to recovery using the Volume Up and Power button
13. You will be greeted with TWRP welcome. Do NOT select the Read-only option.
14. (Optional) It is recommended that you backup your stock firmware, so that you can restore back to stock later on if you need to. To do so, from TWRP click on "Backup", select "Boot", "Recovery", "System", "System Image" and "Data" then Swipe to Backup. If you don't have enough storage, you can change to backup the firmware to external SD Card by selecting "Select Storage".
15. Rooting: plug the device to your computer, then execute the following command:
Code:
adb push SuperSU-v2.78.zip /sdcard/
This will copy the SuperSU-v2.78.zip to your internal user storage. From TWRP, select "Install" -> navigate to /sdcard -> select the zip file, select "Reboot after installation is complete", Swipe to confirm Flash
16. After the zip file is installed, your device will be Rooted.
Click to expand...
Click to collapse
Hi, can I please get the device tree you used to make this. Thanks!
Before flashing TWRP, can anyone share stock recovery for y6 elite (LYO-L02) please ? It is not available online.
Code:
[email protected]:/ # ls -al /dev/block/platform/mtk-msdc.0/by-name/
ROOTM -> /dev/block/mmcblk0p11
boot -> /dev/block/mmcblk0p7
cache -> /dev/block/mmcblk0p24
cust -> /dev/block/mmcblk0p23
expdb -> /dev/block/mmcblk0p10
flashinfo -> /dev/block/mmcblk0p26
frp -> /dev/block/mmcblk0p19
keystore -> /dev/block/mmcblk0p15
lk -> /dev/block/mmcblk0p5
logo -> /dev/block/mmcblk0p9
metadata -> /dev/block/mmcblk0p21
nvdata -> /dev/block/mmcblk0p20
nvram -> /dev/block/mmcblk0p2
oeminfo -> /dev/block/mmcblk0p18
oemkeystore -> /dev/block/mmcblk0p13
para -> /dev/block/mmcblk0p6
proinfo -> /dev/block/mmcblk0p1
protect1 -> /dev/block/mmcblk0p3
protect2 -> /dev/block/mmcblk0p4
recovery -> /dev/block/mmcblk0p8
seccfg -> /dev/block/mmcblk0p12
secro -> /dev/block/mmcblk0p14
system -> /dev/block/mmcblk0p22
tee1 -> /dev/block/mmcblk0p16
tee2 -> /dev/block/mmcblk0p17
userdata -> /dev/block/mmcblk0p25
To dump recovery, it should be as simple as,
Code:
dd if=/dev/block/mmcblk0p8 of=/sdcard/recovery.img
Additional partition info,
Code:
No. Start End Size F/S Name
1 524kB 3670kB 3146kB proinfo
2 3670kB 8913kB 5243kB nvram
3 8913kB 19.4MB 10.5MB ext4 protect1
4 19.4MB 29.9MB 10.5MB ext4 protect2
5 29.9MB 30.4MB 524kB lk
6 30.4MB 30.9MB 524kB para
7 30.9MB 47.7MB 16.8MB boot
8 47.7MB 64.5MB 16.8MB recovery
9 64.5MB 72.9MB 8389kB logo
10 72.9MB 83.4MB 10.5MB expdb
11 83.4MB 83.9MB 524kB ROOTM
12 83.9MB 84.4MB 524kB seccfg
13 84.4MB 86.5MB 2097kB oemkeystore
14 86.5MB 92.8MB 6291kB secro
15 92.8MB 101MB 8389kB keystore
16 101MB 106MB 5243kB tee1
17 106MB 112MB 5243kB tee2
18 112MB 179MB 67.1MB oeminfo
19 179MB 180MB 1049kB frp
20 180MB 213MB 33.6MB ext4 nvdata
21 213MB 252MB 38.3MB metadata
22 252MB 2721MB 2469MB ext4 system
23 2721MB 3146MB 425MB ext4 cust
24 3146MB 3305MB 159MB ext4 cache
25 3305MB 7801MB 4496MB ext4 userdata
26 7801MB 7818MB 16.8MB flashinfo
Digian said:
Before flashing TWRP, can anyone share stock recovery for y6 elite (LYO-L02) please ? It is not available online.
Click to expand...
Click to collapse
I have a Y6 elite that hasn't been updated yet. Care to walk me through the dumping procedure?
There is a catch to creating a backup of the stock recovery, you need to be root to read the raw recovery partition.
Once you have root, either enable developer mode in the android settings menu and connect via USB with the adb-tools and run the DD command above to create a backup copy. Or alternatively, use an app like Flashify to take a backup locally.
There's a few ways to get root without installing TWRP, you could try: KingRoot, FramaRoot, CFRoot, or Kingo Root. It may be trial and error to find which one works on this phone.
Before rooting, I suggest unlocking the bootloader using the guide above in case you run into any issues, obviously stop at Step #10 before installing TWRP if you want to take the stock recovery backup.
If anyone knows an alternate way to grab a backup of the stock recovery, or better ways to get root ... let us know.
Digian said:
There's a few ways to get root without installing TWRP, you could try: KingRoot, FramaRoot, CFRoot, or Kingo Root. It may be trial and error to find which one works on this phone.
Click to expand...
Click to collapse
Finally got around to playing with this. Unlocked the bootloader, tried a few of them but no success
Kingroot makes it to 66% and goes no further
framaroot says the device is not compatible with any exploits
Kingoroot makes it 90% and then comes back with there is a problem parsing the package
Kingoroot PC makes it to 31% then fails
CFroot, I don't know which link to use
Suggestions on where to go from here would be appreciated
outlander43 said:
Kingoroot makes it 90% and then comes back with there is a problem parsing the package
Suggestions on where to go from here would be appreciated
Click to expand...
Click to collapse
One idea was to try moving the KingoRoot .apk to a temp folder with full permissions, such as "/data/local/tmp" in case there is a conflict. Chmod 777.
Secondly, did you try these ? http://www.technicalnotes.org/fix-parse-error-in-android-there-is-a-problem-parsing-the-package/
Digian said:
One idea was to try moving the KingoRoot .apk to a temp folder with full permissions, such as "/data/local/tmp" in case there is a conflict. Chmod 777.
Secondly, did you try these ? http://www.technicalnotes.org/fix-parse-error-in-android-there-is-a-problem-parsing-the-package/
Click to expand...
Click to collapse
So .apk is the installation package. To be clear, it installed just fine. But running it, it only reaches 90% completion, then the screen changes and the parsing error comes up. Whatever the case, I copied the install .apk to local storage/android/data/tmp and installed it from there. Same result. I also tried the previous version 4.2.3 with no change in result.
Gave up trying the one click root apps, and installed TWRP. Very easy! One thing, if your having problems on step 3, disable and re-enable the usb debugging. Before I did that adb was showing UNAUTHORISED
plz help
when i do the command 'fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img ' it comes up with an error saying fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img erroe: cannot load 'huawei-y6-elite-twrp-3.0.2.img'
can some one please help me out
goodjonte said:
when i do the command 'fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img ' it comes up with an error saying fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img erroe: cannot load 'huawei-y6-elite-twrp-3.0.2.img'
can some one please help me out
Click to expand...
Click to collapse
so i mess ed around with it and what i did was i put in ' fastboot flash recovery ' and then draged the file in and then did it and now its working and ive rooted my device
Thanks
Phone sent for repair
Please Help
Whenever i try to flash the custom recovery a This happens in adb C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img
target reported max download size of 134217728 bytes
sending 'recovery' (11044 KB)...
OKAY [ 1.068s]
writing 'recovery'...
FAILED (remote: failed to get download permission because status is locked!)
finished. total time: 1.092s
not able to root huawei LYO-L02
HI everyone,
Ok im new to this so bare with me. Im trying to root my Huawei y6 Elite. I have followed the instructions(from in here) to the letter and everything went according to plan but when i go to check using root checker i get this error
Root access is not properly installed on this device
HUAWEI LYO-L02
Android version 5.1
Stage 1: Super user App : installed
Stage 2: Superuser Binary files Installed
Stage 3: Root User Account Error:
Error: stderr: null, stdout, null, exit_value: 1
So as you can see i really need some help; I hope there is someone out there that can help me it would be most appreciated
Moonlighter
I have this device an used this method at the start of the thread months ago when it was first posted an had no problems so the method works fine thanks.
You can alternatively root the phone with
Magisk - A Root & Universal Systemless Interface by topjohnwu.which I'm my opinion is the best root out there today for android 5 up so big thanks to him an his hard work.if you read the thread there it mentions it can be installed without custom recover like Twrp so this can be a way to get a stock recover image for the device as you now have root an still using stock recover.use flashfy to make a backup of stock image.go through the step at the start of thread on how to unlock the boot loader first.then try the way mentioned in the post
Which can be found at
https://www.google.co.nz/url?sa=t&s...DxAB&usg=AOvVaw0qTxicf0kOFDLDL-79NyS6&cf=1
This is the latest thread up at the moment.
But alternatively I just installed via Twrp as I found a stock recover for this device.note the latest version of magisk v15.3
Work fine but system less exposed module (sdk22)v.89 will cause boot loop.so in order to make it work use magisk v14.0zip at the bottom of the thread at the link above.An use system less exposed sdk22 v87.3 zip first as for some reason if you try install the latest version which is v89.1 it will cause boot loop also so flash sdk22 v87.3 which can be found here at https://www.google.co.nz/url?sa=t&s...FjAAegQIDxAB&usg=AOvVaw2A5-BuyM3GaodiV1QsBLb8
Now that you have both magisk an exposed (system less) working. open magisk manager now go to download an update to the latest exposed module an this will bring exposed up to v89.0 an not cause boot loop.note don't update magisk to latest version stay on magisk v14.0 but if you don't use exposed just install the latest version of magisk.
Here is a stock recover image for this device (Huawei y6 elite) that works an tested it originally comes from the Huawei A5/Y6ii hope this help you all out
Sorry I removed link as it was broken so I uploaded the file in next post
Thanks
Here is a stock recover image for this device (Huawei y6 elite) that works an tested it originally comes from the Huawei A5/Y6ii hope this help you all out
Flash via Twrp or flashfy
Good luck
goodjonte said:
when i do the command 'fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img ' it comes up with an error saying fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img erroe: cannot load 'huawei-y6-elite-twrp-3.0.2.img'
can some one please help me out
Click to expand...
Click to collapse
! Do the command so only type in'fastboot flash recover' then drop an drag the file Huawei-y6-elite-twrp-3.0.2.img in to the command.an you should be right.
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.