Related
this is the short story:
my device is unlocked rooted and encrypted.
By mistake I performed format system instead of wipe data in recovery.
Now I can access fast boot and recovery but the device wont go beyond the first screen with the white asus logo and nvidia in the down corner.
Please help me.
I tried to flash the blob file from the latest version but It fails:
Failed to process command flash:system error(0x170003)
I tried to push the .29 update file thru ADB with CWM and ran it but it says: device is not found
I also tried to copy the rom file in to external micro sd card but the recovery does not see the card.
Please Please help!!!
Didnt you do a cwm backup before you did all that?
yes, but I cant restore it. I get the massage e:cant mount /sdcard
Hi,
I guess, you can't flash this way, if your dev is encrypted.
anywere I found a howto how to format the encrypted partition.
I look for it, if I found some time.
Midyr
please help me soon. i tried everything. dont know what to do next
Search for "Android_Revolution_HD_Super_Wipe_Full_EeePad.zip"
I dont't now, if it really works, because before I found this, I have bricked my dev with flashing a 201er image.
But I get no error after use the wipe.zip.
good luck!
Midyr
now when I try to push the rom zip with adb it says protocol error
Hey man Im sorry I cant help more. I bricked my first TF300 so I know what it feels like. Dont give up, someone can probably get you going again.
Check this topic. TS bricked his encrypted tablet and got it working again.
http://forum.xda-developers.com/showthread.php?t=1679274&highlight=encrypted
Hope it helps....
did not help
Not sure about the encryption stuff, but I recently went through the same thing.
I would try to use adb to push a custom rom (i've been having issues flashing stock rom for some reason)
I would also try to do a factory reset <--- this got my working.
I did a full wife (system format)+factory reset. I think that I have a shell.
Is there a way I can copy the rom to external sd card and somehow install from there?
I cant see the external sd card in recovery.
I tried every way to push the rom file -also a custom rom to the tablet-no success.
it gives me a protocol error or read only error. I cant mount the internal sd card.
I also tried to flash the blob of the rom with fastboot- it gives me a flash error.
can someone guide me step by step what to do?
I dont think that the tablet has a hard brick because I can enter recovery and fastboot. also I can flash boot.blob from cm9, I dont know how to flash the whole rom.
Please advice what to do next.
I'm willing to donate money the to person who knows how to save my device
If you could somehow push this to your device, you might be able to copy the stock zip onto your internal storage.
Yes you need to install the ADB drivers so you can push/fast boot on there
http://forum.xda-developers.com/showthread.php?t=1680570
Can we get my thread stuck?
TXKSSnapper said:
If you could somehow push this to your device, you might be able to copy the stock zip onto your internal storage.
Click to expand...
Click to collapse
will it fit for tf300? or brick it?
Northern-Loop said:
Yes you need to install the ADB drivers so you can push/fast boot on there
http://forum.xda-developers.com/showthread.php?t=1680570
Can we get my thread stuck?
Click to expand...
Click to collapse
i did all this steps. cant push the rom file to the sd card. I think that I need to re-partition the tablet somehow.
Try using "fastboot -i 0x0B05 -w," then try pushing the ROM to your sdcard.
tainka said:
i did all this steps. cant push the rom file to the sd card. I think that I need to re-partition the tablet somehow.
Click to expand...
Click to collapse
That's last steps!
When the device is in recovery and connected to the PC what devices are shown in Windows Device Manager?
prototype7 said:
Try using "fastboot -i 0x0B05 -w," then try pushing the ROM to your sdcard.
Click to expand...
Click to collapse
did it. wont pust protocol error on read only error
I have a question regarding recovery flashing because I am unable to flash any updated recoveries at all. I currently use TWRP and have been using Flashify for quite some to update anything.
However, whenever I go to update TWRP by hitting the "download TWRP" option, I always get the error that I am unable to write to the SD card, even after a number of reboots. I'm not really sure about how to fix this because I previously was able to flash recoveries to my device flawlessly, without issues. I have attached a screenshot for reference. Any help with this would be greatly appreciated!
I am also using DigitalHive's Lollipop ROM as well.
Thank you in advance!
I would just download the file to your computer and flash it in fastboot.
Hi,
It has been a while since ive dealt with custom roms and im wondering if im forgetting something, what im experiencing is that no matter which linageOS rom i install i get stuck for hours on end on the linageOS booting screen. Ive been wondering if theres something like a verbose boot that could show me what is happening when booting. What ive been doing is Install the rom (wipve dev/cache) then install gapps (nano or full) then wipe dev/cahce and still getting the same result every single time.
Now i dont know how to proceed from here, my conclusion is either im doing something completely wrong or this device is not compatible with the 8013 roms however it says 801X all the files say 8013 after youve downloaded them. If another brain could shed some light on this that would be greatly appreciated
Greetings,
Jules
Firgured out my issue it was due to having TWRP 2.8 instead of 3.0, somehow TWRP cant flash it properly on version 3.
I'm havng the same problem, or was. For me too it has been awhile! I was able to boot finally by following these steps:
1. advanced wipe, everything but my ext sd card
2. install os rom zip
3. install gapps zip
4. reboot by selecting do NOT install supersu root or whatever it offered
Now though I'm in and can't download chrome though the play store so I'm about to reflash the stock rom gapps rather than the pico gapps.
just saw your reply - strange as i'm using 2.8 and can't figure out how to update my twrp as fastboot totally freezes
TWRP see twrp thread in development .
or twrp.me
Updates via zip or tar file .
Fastboot on Note 10 ??
JJEgan said:
TWRP see twrp thread in development .
or twrp.me
Updates via zip or tar file .
Fastboot on Note 10 ??
Click to expand...
Click to collapse
@JJEgan when you say twrp updates via zip or tar, is this an automatic update? i also cannot seem to get past the lineage boot screen so not sure how to update it unless i can just drop it on the sd card.
No you update the file via Odin or TWRP .
twrp.me
JJEgan said:
No you update the file via Odin or TWRP .
twrp.me
Click to expand...
Click to collapse
Thanks. @JJEgan I was hoping you might be able to advise on my issue?
I have twrp 2.8 installed from when Blisspop was installed in 2015. It allowed me to wipe and proceed.
Using twrp i then installed Lineage lineage-14.1-20181103-TESTING-n8013, addonsu-14.1-arm-signed and open_gapps-arm-7.1-stock-20190403. These are the things I was able to make a guess that I needed based on reading here.
Problem: stuck at Lineage's logo boot screen
Mistakes I think I made from further reading:
- twrp 3.0 should be used to install ROM
- smaller gapps suite (nano) should be used
Obstacles:
- I can boot the 8013 to Odin Screen. I have Odin running on Windows 10. I have the driver for the 8013 installed in Windows that allowed me to drop the Rom and stuff onto the SD card. However, when I boot into Odin, nothing happens in Odin in Windows.
- Not sure what version of TWRP is really apporpriate
And overall, I'm just guessing about all of this. I understand "the answers are here" but there are millions of answers and I'm having problems deciphering which ones are correct.
Thank you so much. I would be most appreciative if you could point me to the correct twrp for the GT-N8013 and a guide to how to install it via Odin when TWRP is already present and if my other research is correct.
Either update through TWRP as twrp image or via Odin as TAR file .
<However, when I boot into Odin, nothing happens in Odin in Windows. >
You open Odin on windows put tar file in correct slot .
Boot to Download mode on tablet then connect usb cable
Odin press start.
https://forum.xda-developers.com/showthread.php?t=2080366
JJEgan said:
Either update through TWRP as twrp image or via Odin as TAR file .
<However, when I boot into Odin, nothing happens in Odin in Windows. >
You open Odin on windows put tar file in correct slot .
Boot to Download mode on tablet then connect usb cable
Odin press start.
https://forum.xda-developers.com/showthread.php?t=2080366
Click to expand...
Click to collapse
Thank you angel aka @JJEgan! I will try this when I get home from work.
Hi folks. As the title suggest I'm having problems installing TWRP recovery on teclast M89 tablet. I've tried a few different tutorials with no success. When I do it with fastboot it says that its installed, after that when I try to reboot the device, I'm stuck in bootloop. I've tried to do it a few times and its always the same problem. Does anyone have a solution? Thanks.
Hello, the same for me with my M89, I'm going crazy.... Help us please!!!! Thanks!!!
Teclast M89 TWRP 3.3.1
Teclast M89 TWRP 3.3.1
TWRP 3.3.1 for Teclast M89
The archive includes:
ZIP file for flashing via stock recovery
IMG file for flashing via fastboot
TWRP source code
Teclast M89 uses well-known firmware signature Android keys (test keys), that's why you can flash TWRP without unlocking the bootloader and erasing user data.
Installation instruction is inside the archive.
https://www.androidfilehost.com/?fid=6006931924117883832
My small Teclast M89 website: https://teclast-m89.neocities.org/
M89 TWRP Worked!
ValdikSS said:
Teclast M89 TWRP 3.3.1
TWRP 3.3.1 for Teclast M89
The archive includes:
ZIP file for flashing via stock recovery
IMG file for flashing via fastboot
TWRP source code
Teclast M89 uses well-known firmware signature Android keys (test keys), that's why you can flash TWRP without unlocking the bootloader and erasing user data.
Installation instruction is inside the archive.
https://www.androidfilehost.com/?fid=6006931924117883832
Click to expand...
Click to collapse
This TWRP worked like a charm for me. I had already rooted via Magisk- but was really looking for a working TWRP for backing up before I really went crazy with mods.
Thanks so much!!
Jmlanner said:
This TWRP worked like a charm for me. I had already rooted via Magisk- but was really looking for a working TWRP for backing up before I really went crazy with mods.
Thanks so much!!
Click to expand...
Click to collapse
Make sure to backup nvram, nvdata, private partitions.
ValdikSS said:
Make sure to backup nvram, nvdata, private partitions.
Click to expand...
Click to collapse
Will do. I did bkk nvdata, will double check if I bkk privdata. again TK!
stuck
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
voland34 said:
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
Click to expand...
Click to collapse
Hi
I think you are going to have to reflash the original Rom using SPFlahtool. Then you must install Magisk Manage on tabletr. Copy the boot image from the ROM files to Your phone. Then use Magisk Manager to Patch the copied boot image. Transfer modified boot image to PC. Use fastboot to flash modified boot image back onto the tablet. The long and the short of it is - you need to find a way to patch the boot image with Magisk before any TWRP will work.
Right. The problem was accesing the tablet enough time as it stayed connected and recognized by pc only 3-5 secs, and then permanent unresponsive through buttons, but i used then sp flash to just flash boot, then preloader, then recovery from stock at every reboot. From there i could turn it off, It got out of the loop, and accesible to reflash whole stock rom. In the end i only flashed magisk through fastboot, as twrp is not so useful to me as no custom rom, so better no risks.
Thanks for your reply though
voland34 said:
Right. The problem was accesing the tablet enough time as it stayed connected and recognized by pc only 3-5 secs, and then permanent unresponsive through buttons, but i used then sp flash to just flash boot, then preloader, then recovery from stock at every reboot. From there i could turn it off, It got out of the loop, and accesible to reflash whole stock rom. In the end i only flashed magisk through fastboot, as twrp is not so useful to me as no custom rom, so better no risks.
Thanks for your reply though
Click to expand...
Click to collapse
I am glad you got your tablet running again. I had originally started out with just Magisk as root also. I do like to have a working TWRP for backing up though. You should be able now to flash the above mentioned TWRP now via SpFlashtool or fastboot.
voland34 said:
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
Click to expand...
Click to collapse
It seems OEM unlock fills "para" partition with some data which forces it to boot into recovery. Stock recovery reads this data and perform data partition wipe or something similar, but TWRP does not handle this data and you get a boot loop. You can fix that by cleaning "para" partition. Execute the following command while booted into TWRP, either from TWRP terminal itself or from adb shell:
Code:
dd if=/dev/zero of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/para
ValdikSS said:
It seems OEM unlock fills "para" partition with some data which forces it to boot into recovery. Stock recovery reads this data and perform data partition wipe or something similar, but TWRP does not handle this data and you get a boot loop. You can fix that by cleaning "para" partition. Execute the following command while booted into TWRP, either from TWRP terminal itself or from adb shell:
Code:
dd if=/dev/zero of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/para
Click to expand...
Click to collapse
Ok, i'll try. Thanks!
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
gizmo862 said:
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
Click to expand...
Click to collapse
No, most probably it won't. PRO model has different SoC/CPU.
gizmo862 said:
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
Click to expand...
Click to collapse
No. It won't. I bricked my ****ing tablet. It refuses to reboot once it's unlocked because (as the screen say) it is now untrusted. There is no way to relock the bootloader again and the the tablet is stuck in a bootloop.
Teclast is ****.
Hello i'm new in XDA, i have this tablet althougth i can't conect the hdmi port to the tv, the screen keep in black, i think it's because of the display format (4:3) can the root solve this problem?
Thank You!!
w1nst0n sm1th said:
No. It won't. I bricked my ****ing tablet. It refuses to reboot once it's unlocked because (as the screen say) it is now untrusted. There is no way to relock the bootloader again and the the tablet is stuck in a bootloop.
Teclast is ****.
Click to expand...
Click to collapse
The bootloop is not because you've unlocked the bootloader, but most probably because the firmware is designed to perform userdata partition setup in the recovery upon first boot, and you don't have stock recovery, that's why it can't finish formatting procedure.
This could be fixed by flashing stock recovery and booting once.
You can ask for a firmware from Teclast (I used to ask them on vkontakte because they didn't respond my mails), they will provide it.
OR you can write zeros to "para" partition using fastboot, it should do the trick too.
---------- Post added at 16:58 ---------- Previous post was at 16:56 ----------
Edgaralanmx said:
Hello i'm new in XDA, i have this tablet althougth i can't conect the hdmi port to the tv, the screen keep in black, i think it's because of the display format (4:3) can the root solve this problem?
Thank You!!
Click to expand...
Click to collapse
Try to unplug/plug again HDMI cable several times. It seems that the HDMI controller or drivers are buggy.
To change the resolution I use "SecondScreen" software (requires root).
Hi guys,
I´m looking for a working rooting method for my Teclast M89 Pro model ??
Any idea ?? What about the "One Click Root" Program ???
Thank´s a lot
The device was trying to root.
I get the following information when restarting:
orange state
the device has been unlocked and can't be trusted
your device will boot in 5 seconds
Click to expand...
Click to collapse
When I try TWRP via sideload or recovery menu I get the following:
Supported API:3
-- Install /sdcard/teclast_m89_twrp_311.zip ...
Finding update packacke ...
Opening update package ...
Verifying update package ...
Update package verification took 0.5 s (result 0).
Installing update ...
E:Failed to find META-INF/com/android/metadata in update package.
Installing Teclast M89 TWRP Recovery
script succeeded: result was [1.000000]
Install from SD Card complete.
Click to expand...
Click to collapse
But TWRP is not installed.
Where is the problem?
kumpi said:
But TWRP is not installed.
Where is the problem?
Click to expand...
Click to collapse
Are you trying to enter recovery right after flashing it, without booting the OS first? I think you need do enter TWRP right after flashing it.
Hey,
following happend: I dirty flashed LOS 17.1 february update over december version following the instructions ivan gave. After flashing gapps and magisk I flashed the newest TWRP image.
Everything went well (at least it seamt so) I booted to LOS and set up new fingerprints (had to deleate them before flashing), started first app (spotify) and screen went black and phone restarted. Than I got the the FRP Lock message and wasn't able to boot agian neither to LOS nor to TWRP.
Everything followed is here. Tldr: I wasn't able to reflash Stock Rom with Odin no matter what I tried and got lost bettween download mode and nothing.
However I somehow got Android Recovery working!! This is what I can and cannot do:
chrisrevoltes said:
Now I'm able to boot to download mode and original recovery but not to system.
This is what Recovery shows:
View attachment 5218201
I can wipe data and cache partition, but not system partition.
I can view the logs, but I'm not sure what they are telling me....
I can view my external SD card, but trying to install ether TWRP, LOS or the stock image aborted with an error Update from external storage is disabled following a reboot to recovery. Any idea how to enable that?
ADB seams to be working. It can find the phone, although there is an message Stopping adbd... on the phone.
View attachment 5218209
adb devices -l shows:
XXXXXXXcf0cd263704 sideload product:heroltexx model:SM_G930F device:herolte transport_id:8
Sideloading the stock image or TWRP results in: Total xfer: 0.00x in console and adb status 1 on phonescreen with phone reboot to recovery.
Any other adb command (except those three getter) has ether no effect or results in an error.
Any further attempt to flash again with Odin results in the same errors like described in my last post.
Any ideas? ADB or external storage seams like a good way. But system partition worries me.
Click to expand...
Click to collapse
Can anyone help me?
Some time ago I had a Samsung S6 Edge G925I with which I had the same problems and errors as you. After an intense week flashing systems and without getting it to work, I took it to a colleague who has box and other tools to unbrick, unfortunately he discovered that the problem was hardware, more specifically emmc memory problem, I had to resort to changing the plate and problem solved. I would advise you to try all the firmwares that you can from your binary and with old versions of Odin, without opening as administrator, I hope you are lucky; I'll keep thinking if I can think of another solution, regards.
Thanks! I have finally made it. It took my the third day (thanks to covid home office) but I'm now up again with new LOS (but old TWRP).
For the record: My last try was using an older and modified version of Odin (3.13 here) and flashing the newest stock image with extracted PIT file. After 3 minutest it finally booted.
Im not sure if it was the older Odin version (some recommending using v3.14 for devices newer 2018) or the modified Odin version.