Related
I was running the 8/3 update of Cyanogenmod 13 just fine on my L24. I downloaded the 8/13 nightly from the CM website and tried to flash it, but for some reason it returned error 7, which shouldn't happen because I already updated to EMUI4/MM firmware two weeks ago (as evidenced by me running the 8/3 version with no problems). However, when I then tried to boot back into system, the phone instead booted back into TWRP. Trying to boot into system in any way (from TWRP menu, through bootloader --> fastboot reboot, et cetera) just reboots the phone right into TWRP again. -_-
Now, I can access only TWRP and bootloader, but whenever I try to flash a .zip in TWRP it immediately reboots back into TWRP. I've tried reflashing TWRP (newest version and older versions), flashing the Cyanogenmod recovery for kiwi, factory resetting, and even reflashing the stock recovery and trying to return to stock EMUI. None of these have worked. (And yes, of course I've tried clearing cache/dalvik.)
At this point I'm just looking to actually boot into system...If anyone has any idea how I might be able to fix this, it would be great.
EDIT: to clarify, when I try to flash the ROM in TWRP, I get the following:
updating partition details
full selinux support is present
MTP enabled
and then an immediate reboot. This is very fast - I had to take a video of it and then freeze the frame to see what the message was.
Boot in fastboot and install your crap? Turn phone off connect to your PC hold Power and volume down until it boots.
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
radiobacter said:
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
clsA said:
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
Click to expand...
Click to collapse
Again, the issue is that I can't install any ROM through TWRP, because trying to instantly reboots the phone and brings me back into TWRP. I've tried reflashing TWRP, but it doesn't do anything.
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
radiobacter said:
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
Click to expand...
Click to collapse
The phone is known to be finicky about sd cards. Try formatting it with TWRP
Sent from my SM-N920T using Tapatalk
Hi,
there is something wrong with my Xperia Tablet Z. After upgrading from CyanogenMod 11 to CyanogenMod 12 a few Mouth ago the Custom Recovery i've installed before was replaced with CyanogenMod-Recovery. Because CM doesn't work very well i downgraded to Stock-ROM using Flashtool. Because i couldn't find a Way to root Firmware 4.2.x and higher i downgraded to 4.1.2 and rooted with towelroot. The Bootloader is unlocked (checked with *#*#7378423#*#*).
But when i try to install TWRP it failed. This is the error with Fastboot
Code:
fastboot flash recovery twrp.img
fastboot flash recovery twrp.img
sending 'recovery' (10688 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
All drivers are installed. I've tried this on Ubuntu 16.04 and Windows 7 with installed Flashtool and also with installed ADB Installer (https://forum.xda-developers.com/showthread.php?p=48915118#post48915118). I tried it with three usb cables and different usb ports.
It also doesn't work with TWRP Manager (https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=de) and the Official TWRP App (https://play.google.com/store/apps/details?id=me.twrp.twrpapp&hl=de). TWRP Manager show me this error
Code:
Flashing recovery was unsuccessful. Either you already have thos recovery installed or another error has occuured. Would you like to attempt to recovery now?
When i try to reboot the App freeze.
The Official TWRP App seems to install the recovery ("was successfully installed"), but i can't reboot into recovery with VOL+ (also tried VOL-). The Table starts normally.
Maybe there is something wrong with my Tablet now? Is there any other Way to flash a Recovery or to flash a Custom-Rom or a pre-rooted Stock-Rom? As i said before i can't root it with a Firmware higher 4.1.x. Update with the internal Update fuction also failed. So at the moment i can use [email protected] or a higher Version without root.
@PiereMallao
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Hi,
after some years with my pollux_windy left untouched, I decided I'd install my first custom ROM. But I'm having serious trouble to do so, and it seems unsolvable to me after hours of despair (I've been trying for almost 10 hours now).
I was on Lollipop (firmware .222), first unlocked my bootloader, then rooted my tablet (using kingroot). Then I tried to install twrp, and the only way I managed to do this was through this "TabZ-lockeddualrecovery2.8.26" thing. Only, I couldn't manage to flash anything, ended up bricking my tablet.
I then flashed a stock 5.0.2 ROM (.454), retried installing twrp via the same method, and although I manage to access twrp, I get the same error each time I want to flash a new ROM (tried CM/LineageOS 14.1 and ResurrectionRemix v5.7.0), which is : "E: error executing updater binary in zip [insert name of the .zip]".
If I hear Rootk1t correctly, I should flash a kernel with a built-in recovery first... But, doing some research, it looks like you need a working recovery in the first place to flash a custom kernel.
I'm completely lost in this... How can I get that damn recovery to work, and/or get a custom ROM ?
Edit : Alright, with a good 3 hours-long night and a lucky shot, I managed to install LineageOS ! I used twrp recovery (from the dualrecovery thingy-thing) to wipe clean the device, then tried to install the ROM. It gave me the same error message about updating binary. So I rebooted the device into fastboot (couldn't access the recovery anyway... not sure if it's normal), flashed the "boot.img" from the ROM using Flashtool, then rebooted again the device. On the bootlogo, I tried to enter recovery with Vol-, and it worked. i then flashed with ease the ROM. Maybe it will help somebody !
Hapaxx said:
If I hear Rootk1t correctly, I should flash a kernel with a built-in recovery first... But, doing some research, it looks like you need a working recovery in the first place to flash a custom kernel.
Click to expand...
Click to collapse
yep, one just need to
fastboot flash boot boot.img
Click to expand...
Click to collapse
enter recovery and flash firmware zip, gapps, etc from it.
Root works now, but i can't install TWRP 3.0.2.0 (but XZDualRecovery works).
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Click to expand...
Click to collapse
Hapaxx said:
So I rebooted the device into fastboot (...), flashed the "boot.img" from the ROM using Flashtool, then rebooted again the device.
Click to expand...
Click to collapse
If i understand correct Hapaxx flashed the boot.img form the LineageOS 14.1 Image? I don't want to install a Custom-ROM. crDroid is for Nexus. Where can i download a Kernel with build-in Recovery for tabz? or can i use the same crDroid also for tabz?
how can i flash the recovery to fota? can i do this with the same *.img or do i need an other image?
i just unlocked my bootloader and i dont know what else to do, i would like to install lineage 14.1 but i dont know what path to follow, i also hit the whole command not allowed thing, and what Hapaxx said, i'm unable to understand, could someone give a clear set of commands to follow? please? what to do in order so i dont brick my tablet.
Hi PiereMallao,
i have the same Odyssey behind me! Sony Xperia Tablet Z SGP321 LTE (16GB)
1. First check Bootloader unlocked with Flashtools 0.9.18.6. Check!
2. Install SGP321_10.1.1.A.1.307_Unbranded.ftf with Flashtools 0.9.18.6. Check!
3. Developertools on. USB-Debugging on. unknown sources on. Check!
4. Root with Doomlord_Rootkit_v18.rar. Check!
5. Check with App "Root-Checker" in Google PlayStore. Check!
6. And now I try to install TWRP for 3 days !
First try with TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip its ok, but i come only once after the installation in the recovery mode. Afterwards I have it with Vol+ or Vol- tried. It always starts the normal system.
7. With Fastboot -
Code:
fastboot flash recovery twrp.img
fastboot flash recovery twrp.img
target didn't report max-download-size
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
How can i check Bootloader unlock ? In Android Tablet Z i didnt have a keyboard to put in the hex-code *#*#7378423#*#* ?
In Flashtools i checked Bootloader unlock so i have no idea at this Point.
What can I do ?
sorry, i have so solution for this problem. i have given up. theonly way i know to ceck the bl is unlocked or not is flashtool.
I'm having issues with this as well. Trying to install LineageOS 14.1, I can initially get twrp onto the tablet, flash LineageOS 14.1.. boot into it, set up (it is recommended to reboot the tablet once before flashing gapps) ...however, rebooting wipes twrp out. I'm not used to this FOTA thing (first i've ever heard of it) so not sure how to get twrp to 'stick' and not get wiped out
I got it installed this weekend. First secret was fastboot TWRP to boot, not recovery:
Fastboot flash boot twrp-------.img
Make sure you have the right TWRP image.
Then boot into recovery and TWRP comes up.
Flash lineage and gapps.
See:
https://forum.xda-developers.com/xp...de-tutorial-sony-xperia-tablet-z-lte-t3392831
bowguy said:
I got it installed this weekend.
Click to expand...
Click to collapse
I'm a little confused about part 14.
Download app from Play Store : Recovery Manager for Xperia. (done)
Chose FOTAkernel -> Backup. (this makes the app unresponsive for me so i skipped it for now)
Then TWRP -> Download. (done)
then the rest of the steps are confusing. b/c following that guide twrp is already on there (flashed via fastboot), and so why am i replacing the fastboot flashed twrp with the twrp just downloaded in the above step?
and what does the fotakernel have to do with all this? am i suppose to replace the fotakernel with the twrp image downloaded above?
the steps in that guide need more detailed elaboration
x000x said:
I'm a little confused about part 14.
Download app from Play Store : Recovery Manager for Xperia. (done)
Chose FOTAkernel -> Backup. (this makes the app unresponsive for me so i skipped it for now)
Then TWRP -> Download. (done)
then the rest of the steps are confusing. b/c following that guide twrp is already on there (flashed via fastboot), and so why am i replacing the fastboot flashed twrp with the twrp just downloaded in the above step?
and what does the fotakernel have to do with all this? am i suppose to replace the fotakernel with the twrp image downloaded above?
the steps in that guide need more detailed elaboration
Click to expand...
Click to collapse
I never did step 14. Looks straight forward. You should ask this question on that thread
bowguy said:
I never did step 14. Looks straight forward. You should ask this question on that thread
Click to expand...
Click to collapse
Have you rebooted and tried to get back into twrp after you installed the rom? I did the first few steps of the guide a few days back, but every time after flashing the rom it would wipe twrp. I think the only way to get twrp to 'stick' permanently is to complete all the steps
x000x said:
Have you rebooted and tried to get back into twrp after you installed the rom? I did the first few steps of the guide a few days back, but every time after flashing the rom it would wipe twrp. I think the only way to get twrp to 'stick' permanently is to complete all the steps
Click to expand...
Click to collapse
After installing twrp via fastboot per the directions, then reboot into recovery I had few problems. The only issues I had are solved by installing the ROM first - not gapps. Boot and run setup. Then boot recovery and install gapps.
I never had issues with twrp after installing. Power off, power on and rock volume up/volume down until you are in recovery
bowguy said:
After installing twrp via fastboot per the directions, then reboot into recovery I had few problems. The only issues I had are solved by installing the ROM first - not gapps. Boot and run setup. Then boot recovery and install gapps.
I never had issues with twrp after installing. Power off, power on and rock volume up/volume down until you are in recovery
Click to expand...
Click to collapse
Are you using twrp-3.0.2-0-pollux_windy?
x000x said:
Are you using twrp-3.0.2-0-pollux_windy?
Click to expand...
Click to collapse
Yes.
I never bothered with step 14 in the guide. It works fine as is.
P.S.
As per my post on the guide referenced, I installed Rashr and flashed TWRP that way. Seemed to work perfectly. TWRP now shows 3.0.2 which is correct version. No change to system boot. Nice app
Rootk1t said:
@PiereMallao
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Click to expand...
Click to collapse
Bro please give me link to twrp latest for sgp321 m going to unlock bootloader using" flash tool" is it ok
Please tell me how to flash recovary too
Is it ok if i root my tab after unlocking bootloader using king root ajnd flash using flashify
Is ressuraction remex stableto use tell me bugs
?
i had equal problem
FAILED (remote: Command not allowed)
i also have the same problem with my huawei chc u23 gplay mini bricked no recovery please help
I re-unlocked my device a few days ago after a long time of using MIUI. Unfortunately, I am now facing a peculiar problem I had not faced the previous time I unlocked my device.
I cannot seem to replace MIUI stock recovery with official TWRP.
If I use fastboot flash recovery xxx.img, the terminal does confirm that the action was successful. Yet, when I reboot into recovery, I am greeted by Mi-Recovery 3.0 instead of TWRP.
My initial thought was that maybe there was some restriction in MIUI that prevented the stock recovery from being replaced, so I flashed RR 5.8.5-FINAL. I still cannot flash TWRP.
Some other info:
The MIUI build I was on: MIUI 9 7.9.21 Global Beta
My phone: RN3 SD 2GB/16GB variant, Fpc fingerprint sensor
The temporary workaround I used to flash RR was directly booting into TWRP using fastbooot boot xxx.img
NOTE: I did a standard wipe (factory reset, followed by wiping System, Data and Cache) when I flashed RR.
As you might imagine, using fastboot to boot into TWRP every time I want to flash something is quite tiring and so if anyone can help me to permanently flash TWRP, I'd be really grateful. Thanks in advance.
PS: If this question has already been answered, then please guide me to the relevant thread and I will take down this one.
This problem also happened to my friend's Redmi Note 3 MTK. I don't know if it's going to work on KENZO or not.
The solution is to flash the TWRP recovery image through fastboot ==> Turn off the device by holding down the power button (DISCONNECT PHONE FROM PC) ==> Boot the recovery using button combinations
This should let you boot into TWRP and stays permanent after the first session
Flashing Through Fastboot/EDL Mode
Flashing Twrp through Fastboot is the permanent way of flashing the recovery...The method is very simple and can be done even on locked bootloader but the thing in locked bootloader is that once you have flashed the TWRP the internal storage is inaccessible because the data is encrypted so you need to wipe->format data ...then press "yes" ..by typing yes the internal storage will be formatted completely so make sure you have a backup ...and do copy the ROM file in SD card for flashing ...after wiping process press install then select SD card and flash the ROM and gapps and enjoy the TWRP...
Refer this link for flashing process youtu.be/rCONN1_IPuU(please add https:// before the link)
Hope this solves your problem...
same problem !! did you find any solution !!!
Can anyone tell me how to flash custom recovery and root Redmi note 4 with MIUI 10. I tried a few but none of them worked for me. It never reboots to twrp recovery:crying:
aswindevsp said:
Can anyone tell me how to flash custom recovery and root Redmi note 4 with MIUI 10. I tried a few but none of them worked for me. It never reboots to twrp recovery:crying:
Click to expand...
Click to collapse
First you need to unlock your bootloader which almost take 3 to 4 days generally but in my case it take about 10 days to get permission from MI after which I am able to unlock my bootloader after that you have to download ADB and fastboot at your PC then you have to use it to change your stock recovery to custom recovery and once you successfully changed your stock recovery to custom recovery the only thing you need to do is to flash a magisk root file which would be in zip format through your custom recovery then after flashing the root file put your phone into recovery mode and then flash lazyflasher zip file as in my case I come to know that MI UI doesn't support custom recovery because of which you need to flash lazy flasher.
Note after flashing the custom recovery do not boot your phone into system mode rather than boot it to the recovery again or you can simply wipe Dalvik and cache and then flash the lazyflasher otherwise it will stuck while booting which happens in my case also I suggest you to wipe Dalvik and cache partitions after flashing any zip through your custom recovery
Note- I am not an expert this is what I had experienced while experimenting with my redmi Note 4 so don't blame me if anything goes wrong you can browse YouTube for many such tutorials. Hope it will help you
You must try few times. I tryied 3 times, success First and second time booting mi-recovery, not twrp so i tryied flash once again. Also miui 10.
Since you didnt provide much information. If you have unlocked Bootloader (ignore this)
If you have to unlock the Bootloader, check this topic:
https://forum.xda-developers.com/redmi-note-4/how-to/bootloader-unlock-variants-to-read-t3565459
It will take a maximum of 3 days if you read and do needful properly, in case it does not works, Redmi sends a message to wait for specific hours wait additional 1 hour in case required and try again.
After all Bootloader thing, follow this simple steps,
https://forum.xda-developers.com/showpost.php?p=78343517&postcount=240
Appreciate original author of topic @nik.desai07
my redmi note 4 mido is bricked and i don't know how, i left my phone for a month because i travelled away and when i came back the phone was stuck on mi logo i tried to fix it by this methods but nothing worked:
-i tried to flash stock firmware via mi flash tool and it failed so many times (i used an old version which stated that the installation succeed but the phone was still stuck in bootloop)
- i tried edl version and it didn't work
- i tried to install via adb and it didn't work also
- i tried to open recovery (volume + and power) it got me to twrp 3.2.3.0 but it's alway stuck on twrp logo and nothing happens
it only happened 2 times when twrp worked and asked me for decryption password, i wrote my phone pin but said wrong password (tried also password and default_password) then i bypassed the password section and got into twrp but i couldn't mount or format storage (it appears that internal storage and sd card is 0 gb) i tried to format it fails,
tried also to change storage to ext2 it got stuck and i couldn't open the twrp again.
any stock firmware flashed on my mido doesn't work and it still stuck on mi logo ( no android loading logo), and it still has twrp
(i tried to flash another twrp or orangefox it just doesn't flash even if it's successful flash on adb)
i tried also to boot the recovery image it also get stuck on the logo and doesn't open the recovery
please help me to know what the hell is wrong with this phone and how i can fix it
help pleassseeeeeeee
Install magisk if you are stuck in boot loop it fixes the problem otherwise download a recovery rom and change your twrp version to 3.1.0.0 because the decryption password in the new versions of twrp doesn't seem to work on rn4. Now wipe system,vendor,data. import recovery rom from your computer and install it. It will install the rom then flash Magisk otherwise your phone will be stuck in bootloop. Wait for a while and bam your system is back!
i can't install anything or even boot into twrp 3.1.0.0 even if i tried
Can you boot into fastboot atleast? If yes then type fastboot reboot recovery and as you said you have twrp installed then it surely means that your bootloader is unlocked. Do you know the name of your custom rom or are you using stock rom? If yes whichever rom you are using just download the recovery rom of that and extract the boot.img in your adb and fastboot folder and flash it via fastboot by typing fastboot flash boot boot.img . And also when booting in twrp which buttons are you using? This happened to me when I myself bricked my device. I thought I can't boot in twrp but the point was I was using volume up+ power but the actual key to boot to twrp is volume up+volume down+power key
You can flash your Xiaomi Redmi Note 4 [MIDO] using Mi Flash. I have an article that discusses how to flash Xiaomi Redmi Note 4 [MIDO / Snapdragon] that might help you: How to Flash Redmi Note 4 / 4x Snapdragon [Mido] with MiFlash
NOTE: Few problematic tool links in this article. Please search on Google | This website was translated using Google Translate [Indonesian -> English]
pandmc said:
You can flash your Xiaomi Redmi Note 4 [MIDO] using Mi Flash. I have an article that discusses how to flash Xiaomi Redmi Note 4 [MIDO / Snapdragon] that might help you: How to Flash Redmi Note 4 / 4x Snapdragon [Mido] with MiFlash
NOTE: Few problematic tool links in this article. Please search on Google | This website was translated using Google Translate [Indonesian -> English]
Click to expand...
Click to collapse
I think flashing the stock rom should be the last step before which everything possible should be tried
JustExperimentingRedmi said:
I think flashing the stock rom should be the last step before which everything possible should be tried
Click to expand...
Click to collapse
Yes, Flashing Stock ROM should be the last step before he tries to fix. But mostly if the smartphone is bootlooped or bricked there is no other step besides Erase All Data / Format Data or Flashing Stock ROM.
pandmc said:
Yes, Flashing Stock ROM should be the last step before he tries to fix. But mostly if the smartphone is bootlooped or bricked there is no other step besides Erase All Data / Format Data or Flashing Stock ROM.
Click to expand...
Click to collapse
You can flash orignal boot.img which most times fixes the problem and if it didnt work flash system.img it almost always works and the last option is flashing magisk. Then only i will recommend to flash stock rom.
JustExperimentingRedmi said:
Can you boot into fastboot atleast? If yes then type fastboot reboot recovery and as you said you have twrp installed then it surely means that your bootloader is unlocked. Do you know the name of your custom rom or are you using stock rom? If yes whichever rom you are using just download the recovery rom of that and extract the boot.img in your adb and fastboot folder and flash it via fastboot by typing fastboot flash boot boot.img . And also when booting in twrp which buttons are you using? This happened to me when I myself bricked my device. I thought I can't boot in twrp but the point was I was using volume up+ power but the actual key to boot to twrp is volume up+volume down+power key
Click to expand...
Click to collapse
the rom i was using before the phone got bricked is crdroid 10, i downloaded it again as you said and tried to flash boot img then i rebooted into recovery but i got stuck at twrp logo as usual and even if twrp worked it will as for a password i tried all pins i have used on my phone and tried default_password didn't work either, i can't even mount data or storage or anything and it shows everything with 0mb storage (external or internal storage).
i can't even format data to remove encryption it just freezes whenever i do that
pandmc said:
You can flash your Xiaomi Redmi Note 4 [MIDO] using Mi Flash. I have an article that discusses how to flash Xiaomi Redmi Note 4 [MIDO / Snapdragon] that might help you: How to Flash Redmi Note 4 / 4x Snapdragon [Mido] with MiFlash
NOTE: Few problematic tool links in this article. Please search on Google | This website was translated using Google Translate [Indonesian -> English]
Click to expand...
Click to collapse
i tried that before it's always shows me ( mi flash tool could not find a part of the path) error, there's a one time i tried an older version of mi flash tool and the flash succeeded but when phone rebooted it stayed at the bootloop
i checked the recovery and sadly it was still the same twrp recovery
i don't really know if my phone can be fixed or this an emmc problem
So it means you have your stock rom right? Extract boot.img and flash it with
fastboot flash boot boot.img
make sure to put it in adb folder
You can find boot.img in images folder
If it does not work get the system.img and flash it with
fastboot flash system system.img
i flash the whole stock rom via fastboot (adb) and it also didn't work.
sorry if this seems disappointing
Try orangefox recovery then, not sure why is this happening to you
If still not working type
fastboot oem edl
Then flash via mi flash it should work as far as I know. If not then go to mi service centre it's the last thing you can do