I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
retfeg said:
I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
Click to expand...
Click to collapse
same problem here! brand new phone, 4.4.2 o2 UK.
the mismatched partition size error is not important i know that.
have tried Philz (got it to work once, but after rebooting, had gone again. ever after letting it fix the rom rewrite on exit!). also tried stock CWM 6046 and 6047.
have tried entering recover immediately after flashing.
have tried flashing multiple times.
have tried different usb ports.
ideas please?
i've never had this much trouble with any phone (have experience over 3 years with Blade, G300, Xperia range etc.)
edit: tried using fastboot -S 0 parameter also, seems to make no difference. phone won't boot into recovery. this is slightly different to the problem i had with old phone, that one would boot Philz but not boot any ROMs. this one is booting stock ROM. if i can get Philz to "take" again i could try flashing CM, but i wanted to stay on stock, and just root it..
edit2: just started working! bizarre.. hope this doesn't jinx it. i wrote two recovery images with -S 0 and it works, not sure if because of that or something else. btw Philz won't backup the stock rom, odd - it just errors out, CWM standard works though.
hurrah! i rebooted normally, went back to fastboot and recovery still there. this is with recovery-clockwork-6.0.4.7-falcon.img
now i can hopefully root it..
wonder if my 3rd moto g will get any easier! this is a huge PITA of random non-workiness so far.
Hi, I came here because I've tried to fix my phone but no hope. My situation si that I'm on a Loop in the booting process where the phone starts the booting process but crashes maybe on the bootloader. My system can see the Port COM 4 and I tried the Mobile upgrade program but after it detects the phone and I click "Update" button the phone goes into the loop maybe trying to get into Fastboot. Lastly, the download fails.
I have never hacked or made any modifications on an Android phone before so I'm a complete noob to this ADB tools and don't have a clue on how to use any tool to recover this phone.
I'm able to boot into "Download mode" and nothing else, maybe there's a combination for getting into the bootloader but I don't see anything about that in the many searches.
Any help is much appreciated.
you device is bricked and you try root install a custom rom or a bad upgrade
ravendepth said:
Hi, I came here because I've tried to fix my phone but no hope. My situation si that I'm on a Loop in the booting process where the phone starts the booting process but crashes maybe on the bootloader. My system can see the Port COM 4 and I tried the Mobile upgrade program but after it detects the phone and I click "Update" button the phone goes into the loop maybe trying to get into Fastboot. Lastly, the download fails.
I have never hacked or made any modifications on an Android phone before so I'm a complete noob to this ADB tools and don't have a clue on how to use any tool to recover this phone.
I'm able to boot into "Download mode" and nothing else, maybe there's a combination for getting into the bootloader but I don't see anything about that in the many searches.
Any help is much appreciated.
Click to expand...
Click to collapse
First boot into recovery and wipe cache and data.
If that fails try again. It fails again use the below method to restore your phone.
Go into download mode and using the ABD install your stock rom., Meaning your phones original version.
Your phones not bricked.
Stuck at Bootscreen (BootLoop)
Custo481 said:
First boot into recovery and wipe cache and data.
If that fails try again. It fails again use the below method to restore your phone.
Go into download mode and using the ABD install your stock rom., Meaning your phones original version.
Your phones not bricked.
Click to expand...
Click to collapse
Hi,
I tried to install RR on my Alcatel Idol 3 4.7 with using Shara & Firehorse according to this thread https://forum.xda-developers.com/idol-3/general/guide-unlock-flash-root-updated-alcatel-t3751845
everything went accordingly but TWRP never installed. I to boot into recovery and it booted android recovery instead of TWRP. So i tried again using Firehorse but my phone did not boot to download mode, so i cleared cache using the Android system recovery but then i received an error can't mount cache/recovery , so i tried to reset to factory data and received yet again other errors. Force-Restarting my phone ended up in a bootloop that i am not sure how to remove. Please help
Model: Alcatel One Touch Idol 3 6039 K
its-ian said:
Hi,
I tried to install RR on my Alcatel Idol 3 4.7 with using Shara & Firehorse according to this thread https://forum.xda-developers.com/idol-3/general/guide-unlock-flash-root-updated-alcatel-t3751845
everything went accordingly but TWRP never installed. I to boot into recovery and it booted android recovery instead of TWRP. So i tried again using Firehorse but my phone did not boot to download mode, so i cleared cache using the Android system recovery but then i received an error can't mount cache/recovery , so i tried to reset to factory data and received yet again other errors. Force-Restarting my phone ended up in a bootloop that i am not sure how to remove. Please help
Model: Alcatel One Touch Idol 3 6039 K
Click to expand...
Click to collapse
Hi, you may want to try a different TWRP recovery. Had the same problem. solved with TWRP 3.0.0 f2fs from Decker's MM TWRP backup. TWRP 3.1 also works with Sahara&Firehose.
Hope this helps.
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.
I was trying to get lineageos on my s6 edge+ but it is stuck in a samsung logo loop after being unable to flash the rom and now it won't go back into TWRP either.
Initially I flashed the official TWRP for the zenlte which worked fine, it just did not want to install the rom due to apparently not having any device data. (Rom is for zenlte, this device is . (or something along those lines))
after a few attempts and doing a quick wipe I flashed an unofficial twrp and thats when it started looping without being able to get back into recovery mode.
Download mode does still work after a power off but flashing the official twrp again makes no difference.
This is a little beyond me and I'm not entirely sure what is going on.
The last phone I installed a custom rom on was an s4 so I'm a bit out of the loop with this new security stuff. I would have expected to at least be able to boot back into twrp.
Ok some progress:
Recovery mode worked again after leaving phone off (but still attached to computer) for a while. (I had given up but decided to try again after a few hours)
Partitions were missing / corrupted. Did a full format.
Installing rom still gave the 'device type is .' message.
Edited the rom zip to allow "" and " " ( in META-INF\com\google\android\updater-script )
Flashed rom + gapps + magisk in 1 go.
This ended up in LineageOS trying to start but rebooting into recovery after about 5 minutes.
Re-instralled just the rom, this gave a few errors about Magisk missing, re-installed Magisk as well before wiping cache and rebooting.
Now it came up with the welcome screen rather quickly.
Weird, but problem solved any ways.
Thanks! That was also my problem.
How can in get out of this boot loop, any advice, answers, help appreciated?
As background my Lenovo Tab 4 10 plus (stock 7.1 rom) had a failed SD card so I replaced the card and factory reset and thought I would try TWRP, Linageos 17.1 with magisk and relevent gapps - this all worked fine other than a Skype issue. I then found an 18.1 rom and tried that and this is where it seems to have gone wrong I set it up in the same ways as the 17.1 rom but with Andriod 11 gapps to suit, did a factory reset and 30 seocnds in I got the boot loop.
To fix it I tried going back to the 17.1 rom set-up that had worked but this then boot looped even with a full recovery reset. I have gone back to the stock rom backup in TWRP again with a recovery reset same boot loop. I have even used the Lenovo recovery tool to EDL mode flash a newly downloaded stock rom and it's still boot looping. I can only think that the 18.1 andriod 11 rom changed something fundimental but I can't find what?
Further I have another problem, the EDL flash worked but it locked the bootloader, however as I can't get in to Andriod with the boot loops, I can't switch ADB mode on so I can't unlock the bootloader to get TWRP up again.
So is there a way to start ADB without access to develeoper settings maybe through fastboot or recovery which I can get in to? Unlock the bootloader without ADB? Does anyone know why after the 18.1 Andriod 11 based rom, I have this continous boot loop?
I have a tb-x704f wich was totally caught in a boot loop, but I manisched to get back to working stock.
I was running firmware s000056 when I flashed twrp without backing up anything. I thought I never would have to go back to nougat, but standby time on lineage os was just not good for me, as I only use my tablet maybe half an hour a day, and I had to charge several times a week nevertheless.
So I tried to get back to stock and awesome standby time.
It was not easy bootloop after bootloop.
Tried Lenovo rescue and smart assistant multiple times, factory reset before and after flash, without SD card inserted etc, but bootloop.
Tried flashing the rom downloaded from the rescue tool with qfil but same result.
I then tried flashing the files with miflash 2016.08.30.0 still the same rom as I thought it had to be s000056. Miflash stopped halfway with some kind of error.
I then downloaded a stock rom from lenovo-forums.ru http://lenovo-forums.ru/topic/24135-lenovo-tab4-a10-plus-proshivka-tb-x704f_s000037_170703_row_qfil/
from the link in the discussion in the bottom of the site.
I had twrp still so from there I got into terminal and wrote "reboot edl" to get into emergency download mode and then flashed away. I presume that I could just as well had gotten in to edl mode by pressing vol+ and vol- simultaneously and then connected to PC holding those to buttons pressed. When the tablet was finished it was off, so I started going to recovery and wipeed cache and did a factory reset. Then booted and instead of bootloop it showed the Lenovo screen with a progress bar underneath. I successfully booted and took a update and then i am back to stock s000056.
The rom I got from lenovo-forums.ru stated it was only for EU and wi-fi model only. I am in Denmark and my tablet is WiFi only.
I think chances for success is greater using miflash than other tools when recovering from bootloop, but then again I don't know. Maybe I could just have flashed the s000037 rom with qfil or maybe I was just lucky, who knows.
But this what worked for me.
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
pallep said:
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
Click to expand...
Click to collapse
Thanks kind man You helped finish my struggle!
The only thing I want to add is that the ROM from the original link is no longer available, so I found the correct ROM using Google from the original filename here https://firmware247.com/lenovo-tab4-a10-plus-tb-x704f-firmware/