Did any if you try installing OTA from TWRP?
I'm tempted to but seeing as it's installed block by block stuff could go wrong when you've modified /system, /vendor and/or /product...
ante0 said:
Did any if you try installing OTA from TWRP?
I'm tempted to but seeing as it's installed block by block stuff could go wrong when you've modified /system, /vendor and/or /product...
Click to expand...
Click to collapse
i have tried but can't get thru..keeps getting error.
Sent from my Mate 9 using XDA Labs
eddmecha said:
i have tried but can't get thru..keeps getting error.
Sent from my Mate 9 using XDA Labs
Click to expand...
Click to collapse
Did you try editing the updater-script?
I was trying to make a flashable zip, found this python script (sdat2img) but doesn't work with OTA :/
Well then, its probably using "huawei-only" commands.
ante0 said:
Did you try editing the updater-script?
I was trying to make a flashable zip, found this python script (sdat2img) but doesn't work with OTA :/
Well then, its probably using "huawei-only" commands.
Click to expand...
Click to collapse
hmm never tried edit the script.
Maybe someone have to try sideload like OnePlus.
Enable sideload in twrp and in adb type: adb sidload update.zip
And use latest Google adb not minimal adb https://developer.android.com/studio/releases/platform-tools.html
Tried, but no success.
Tried with fastboot - same result.
Must have kernel sources and build new TWRP.
Until then - patiently waiting
Related
So, I updated to 2.3.4 today, and after a rebbot into recovery, CWM was gone.
No problem, I tought, and used fastboot to flash it back.
fastboot went OK, but when I tried to use CWM from recovery, I got stucked at the "stock" recovery (android with a exclamation mark). Is anyone else facing this?
Click to expand...
Click to collapse
NVM this first part, solved that.
Also, I can´t get adb to work, tried pushing some files and got permission denied; abd remount gave me a "remount failed: Operation not permitted" error.
Yeah, having the same problem here. The 'remount failed..' error is because the update patched our boot.img and now they are no longer 'insecure.' I think I might fix it so we all can have root again. I've also had better luck when running a shell script and physically moving apps, etc to the places i want them...then have to chmod, etc...freaking sucks.
If you need any help with some workarounds shoot me a message..also have some personal scripts that get everything going
du5t3r said:
Yeah, having the same problem here. The 'remount failed..' error is because the update patched our boot.img and now they are no longer 'insecure.' I think I might fix it so we all can have root again. I've also had better luck when running a shell script and physically moving apps, etc to the places i want them...then have to chmod, etc...freaking sucks.
If you need any help with some workarounds shoot me a message..also have some personal scripts that get everything going
Click to expand...
Click to collapse
Thanks, I spent a long time yesterday trying to solve this.
Finally, I gave up and installed Root Explorer. Let me know if you have any progress with this.
Use RootExplorer after flash to rename the recovery.sh to recovery-no.sh its found in the ETC folder.
Try choosing erase recovery in the rom managers settings then flash.
kaizxclusive said:
Use RootExplorer after flash to rename the recovery.sh to recovery-no.sh its found in the ETC folder.
Try choosing erase recovery in the rom managers settings then flash.
Click to expand...
Click to collapse
Hmm, I found a install-recovery.sh, is that one?
I am not using rom manager...
gasparzim said:
Hmm, I found a install-recovery.sh, is that one?
I am not using rom manager...
Click to expand...
Click to collapse
yes, just rename it to something like install-recovery.sh.old
Bajo76 said:
yes, just rename it to something like install-recovery.sh.old
Click to expand...
Click to collapse
Thanks, looks like it´s working now.
For some reason I am not able to install any custom ROM's with TWRP 2.3.3 I transfer the files across to the root directory of my internal storage using ADB pusher but whenever I try and install a ROM I seem to get this error message
E:Mount: Unable to find partition for path '/[email protected]_Edition_V02.zip'
Error flashing zip '/[email protected]_Edition_V02.zip'
Updating partition details..
Click to expand...
Click to collapse
Does anyone have any idea as to why this is happening, and how I can get around it?
I currently dont have a ROM installed on my TF300 due to me being an idiot, but I can use ADB, TWRP and fastboot so I should be able to sort this out.
Nekrom4n said:
For some reason I am not able to install any custom ROM's with TWRP 2.3.3 I transfer the files across to the root directory of my internal storage using ADB pusher but whenever I try and install a ROM I seem to get this error message
Does anyone have any idea as to why this is happening, and how I can get around it?
I currently dont have a ROM installed on my TF300 due to me being an idiot, but I can use ADB, TWRP and fastboot so I should be able to sort this out.
Click to expand...
Click to collapse
I can not remember,
Is the update a complete rom ??
If not,then install OC V.3 instead..
Nekrom4n said:
For some reason I am not able to install any custom ROM's with TWRP 2.3.3 I transfer the files across to the root directory of my internal storage using ADB pusher but whenever I try and install a ROM I seem to get this error message
Does anyone have any idea as to why this is happening, and how I can get around it?
I currently dont have a ROM installed on my TF300 due to me being an idiot, but I can use ADB, TWRP and fastboot so I should be able to sort this out.
Click to expand...
Click to collapse
Try Clockwork, this 4.2 is weird. I can do a backup in TWRP, but it cannot find what I placed on the sd card, so I have to use Clockwork for some reason....
Managed to sort it. For some reason TWRP didn't like installing from root, and changed to a sub directory and it works fine now. Installed paranoid android in the end
Sent from my Transformer Pad TF300T using XDA Premium HD app
same issue
i have the same proble only im stalling from /mnt/sdcard not from root.
On htc one s3..........
have been withoutmy droid for weeks!
samo problem
I have the same issue but when i put the ROM in a folder it does not work.
I have a goophone i5 and i wiped my system have no OS on it only TWRP.
I need to install a new recovery can anyone help me i am a noob for this !
Thank you
What command are any of you using to push the file??
Thx Josh
problem
lj50036 said:
What command are any of you using to push the file??
Thx Josh
Click to expand...
Click to collapse
i am trying to install a rom from the TWRP recovery .
i uploaded the file on the external SD card .
Nekrom4n said:
Managed to sort it. For some reason TWRP didn't like installing from root, and changed to a sub directory and it works fine now. Installed paranoid android in the end
Sent from my Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! As soon as I put the zips (PA4.4 + gapps) into my sdcard folder my nexus 7 was able to install w/ out fail.
Nekrom4n said:
Managed to sort it. For some reason TWRP didn't like installing from root, and changed to a sub directory and it works fine now. Installed paranoid android in the end
Sent from my Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
How did you changed to your root directory to sub directory
Help i've accidentally deleted my backup OS on my nexus 5. i am using CWM. i was trying to put android L on my nexus 5 and it couldnt install. so i went back to the recovery mode in attempt to restore my device to the backup i made. i couldnt find the backup on my sd card...weird. so i am stuck. trying to find a way to get my device back.
AHMEDNATOR said:
Help i've accidentally deleted my backup OS on my nexus 5. i am using CWM. i was trying to put android L on my nexus 5 and it couldnt install. so i went back to the recovery mode in attempt to restore my device to the backup i made. i couldnt find the backup on my sd card...weird. so i am stuck. trying to find a way to get my device back.
Click to expand...
Click to collapse
If your backup got deleted then it is lost forever. Flash cwm again then flash the rom you used before L
You should keep a copy of the backup off your device. Maybe third time will be the charm.
http://forum.xda-developers.com/showthread.php?t=2750414
Wakamatsu said:
You should keep a copy of the backup off your device. Maybe third time will be the charm.
http://forum.xda-developers.com/showthread.php?t=2750414
Click to expand...
Click to collapse
i kept a copy of it but when i went back to try and restore with that copy. i didnt see it any more. the bad luck i get with android phones
bitdomo said:
If your backup got deleted then it is lost forever. Flash cwm again then flash the rom you used before L
Click to expand...
Click to collapse
how to flash it again if i have no way to get back in my device?
AHMEDNATOR said:
how to flash it again if i have no way to get back in my device?
Click to expand...
Click to collapse
What do you mean by "get back in my device"? You cant turn it on?
bitdomo said:
What do you mean by "get back in my device"? You cant turn it on?
Click to expand...
Click to collapse
scratch that. i can turn it off and back on. i tried adb sideload but i cant seem to be able to push a rom on the nexus.
AHMEDNATOR said:
scratch that. i can turn it off and back on. i tried adb sideload but i cant seem to be able to push a rom on the nexus.
Click to expand...
Click to collapse
Have you flashed cwm?
bitdomo said:
Have you flashed cwm?
Click to expand...
Click to collapse
yeah i have CWM installed
AHMEDNATOR said:
yeah i have CWM installed
Click to expand...
Click to collapse
What is the command you use to push the rom?
bitdomo said:
What is the command you use to push the rom?
Click to expand...
Click to collapse
the rom i downloaded is called something hammerhead. i renamed it to Rom.zip . when i am in my command prompt. i type "adb push Rom.zip" or when i do the sideload, i do "adb sideload Rom.zip"
AHMEDNATOR said:
the rom i downloaded is called something hammerhead. i renamed it to Rom.zip . when i am in my command prompt. i type "adb push Rom.zip" or when i do the sideload, i do "adb sideload Rom.zip"
Click to expand...
Click to collapse
There is the problem. You didnt tell where to push the zip.
Use this:
adb push rom.zip /data/media/0
after that you should see the rom.zip on the internal storage
bitdomo said:
There is the problem. You didnt tell where to push the zip.
Use this:
adb push rom.zip /data/media/0
after that you should see the rom.zip on the internal storage
Click to expand...
Click to collapse
alright, let me give it a try.
bitdomo said:
There is the problem. You didnt tell where to push the zip.
Use this:
adb push rom.zip /data/media/0
after that you should see the rom.zip on the internal storage
Click to expand...
Click to collapse
it says "error: cloased"
AHMEDNATOR said:
it says "error: cloased"
Click to expand...
Click to collapse
running
adb devices
command showes you any output?
bitdomo said:
running
adb devices
command showes you any output?
Click to expand...
Click to collapse
yeah, it shows some numbers and letters which i assume is my device and next to it, it says "sideload"
AHMEDNATOR said:
yeah, it shows some numbers and letters which i assume is my device and next to it, it says "sideload"
Click to expand...
Click to collapse
Then use
adb sideload rom.zip
command
bitdomo said:
Then use
adb sideload rom.zip
command
Click to expand...
Click to collapse
i get a bunch of stuff and commands come up in the command prompt. i ll try to take a picture for you
bitdomo said:
Then use
adb sideload rom.zip
command
Click to expand...
Click to collapse
there it is
If you don't have path variables set up make sure your rom.zip is in the platform-tools folder of the sdk.
NM. Looks like you do have path variables set up. That second longer error in you screen shot is because you put a space after rom. The first looks like it can't read it because your typing the name wrong. Remember it's case sensitive so Rom.zip and rom.zip are two different things.
I did a backup with the TRWP recovery but I can't find the directory "TWRP" in the sd card, neither in the explorer nor in the pc when connecting. However, the directory is there if I look from the recovery.
diegodm said:
I did a backup with the TRWP recovery but I can't find the directory "TWRP" in the sd card, neither in the explorer nor in the pc when connecting. However, the directory is there if I look from the recovery.
Click to expand...
Click to collapse
Do you see it in adb shell? Or did you try do adb pull it?
k-kuchen said:
Do you see it in adb shell? Or did you try do adb pull it?
Click to expand...
Click to collapse
I see it in the adb shell, but cannot access to it, "Permission denied". I can't adb pull it, it says that the remote object doesn't exist.
Are you doing that while in TWRP or in Android? Your problem might be related to SELinux contexts.
_that said:
Are you doing that while in TWRP or in Android? Your problem might be related to SELinux contexts.
Click to expand...
Click to collapse
I was doing it in Android, but now in TWRP i've been able to adb pull it.
Is there any reason I should be worried about that SELinux thing?
Are you using the latest version of TWRP from here: http://forum.xda-developers.com/showthread.php?p=57672469 ?
lost101 said:
Are you using the latest version of TWRP from here: http://forum.xda-developers.com/showthread.php?p=57672469 ?
Click to expand...
Click to collapse
No, I'm using the 2.8.6.0 downloaded from the TWRP site. Should I use the GPE version from your link? (I have GPE firmware flashed)
diegodm said:
No, I'm using the 2.8.6.0 downloaded from the TWRP site. Should I use the GPE version from your link? (I have GPE firmware flashed)
Click to expand...
Click to collapse
Yeah, try that.
lost101 said:
Yeah, try that.
Click to expand...
Click to collapse
Wow, I had no idea that a recovery could be so beautiful Well, now I've done a backup and I can see it perfectly in my PC. Thanks!
[Global] Mi A2 Lite V11.0.10.0.QDLMIXM rolling out!
Wow. That's gotta be some kind of record for Xiaomi
Mine is only 13M though. Must be a tiny update.
Wow! First time ever that this Android One device is actually up to date security wise.
Yes, from July update only 13MB.
Maybe it was there before, but after updating I noticed a native screen recorder icon.
Updated: It is not native. I have a screen recorder app installed.
Direct share not yet available.
penahj said:
Maybe it was there before, but after updating I notice a native screen recorder icon
Click to expand...
Click to collapse
strange i dont have this one and never had screen recording option
Antho02 said:
strange i dont have this one and never had screen recording option
Click to expand...
Click to collapse
You are right. It's not a native app. I have a screen recordering app installed. Sorry for the wrong news.
Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex
Alibabara said:
Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex
Click to expand...
Click to collapse
+1 I am also looking for this
Alibabara said:
Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex
Click to expand...
Click to collapse
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way
Antho02 said:
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way
Click to expand...
Click to collapse
So you Flash the whole Rom (~1.2gb) and not just the Update?
I would like to find a way to Flash just the Update since your method is taking too long for me...
Best regards
Alex
If you only have Magisk, the standard process should work for you.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
If it's not working and you have somehow modified some other partition, it will be written to the logcat.
adb logcat | grep update_engine
My Problem is, even with magisk 'uninstalled' the Update App from xiaomi still says 'Installation failed: Installation Problem'
That even happens with totally Stock rom, no root and no twrp.
I dont know why. But is there any other way to Update manually without flashing the whole Big Rom file? Just the Update file...
There must be a reason why there is an update file in zip Format which is 13mb Big.
Best regards
Alex
Alibabara said:
My Problem is, even with magisk 'uninstalled' the Update App from xiaomi still says 'Installation failed: Installation Problem'
That even happens with totally Stock rom, no root and no twrp.
I dont know why. But is there any other way to Update manually without flashing the whole Big Rom file? Just the Update file...
There must be a reason why there is an update file in zip Format which is 13mb Big.
Best regards
Alex
Click to expand...
Click to collapse
Alex, You don't have to flash the whole big rom file, but you do have to download it though. You can get it from here: https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
You then have to extract the files that you need with payload_dumper which you get from here:
https://androidfilehost.com/?fid=818070582850510260
NB that is the Windows 64bit version so make sure that is the OS your pc is using.
You then have to find which partition it is that is causing the problem for which you have to use a1291762's advice:
Code:
adb logcat | grep update_engine
and read very carefully through the results because the offending entry will be difficult to spot amongst the dozens of others.
You then flash the partition mentioned in the logcat. For example if 'system' is mentioned in the logcat as having an incorrect hash (that is always the reason for the failures) you would have to extract 'system.img' with payload_dumper and run
Code:
fastboot flash system system.img
Then try the update again. If it works you will also probably have to reinstall Magisk from scratch again as flashing system will probably remove it.
Yes it is complicated - far too complicated, but the simple measure you call for - just flash an update file - has, to the best of my knowledge never been possible, so there must be some reason why that is so, but I don't know what it is.
Incidentally, the reason I am able to respond to this question is that I had a torrid time yesterday trying to update my A2 lite on which I had not one, but 3 errors. aboot hash incorrect, system hash incorrect, and before any of that the normal Magisk uninstall told me it had no images to restore and so had to be uninstalled completely. It took me hours and it wasn't that much fun.
Alibabara said:
There must be a reason why there is an update file in zip Format which is 13mb Big.
Click to expand...
Click to collapse
The update is only 13M because it contains only changes. But for that to work, your partitions must be unmodified.
The larger update zip has complete partitions so it can work even if you have changes. You may be able to do the recovery update method with that file...
The even larger fastboot image has every partition.
thanks everyone for the help!
I did it as you said viking777 and it worked.
It's sad, that for an 13mb update this procedure is necessary, but thats how it is..
So thanks again everyone for the help
Antho02 said:
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way
Click to expand...
Click to collapse
Can I do this with out installing TWRP as I haven't installed it already.
Aadil Gillani said:
Can I do this with out installing TWRP as I haven't installed it already.
Click to expand...
Click to collapse
sure, even more quick if u dont need twrp
flash last rom with xiaomi flash (save user data selected)
then boot patched.img and install magisk, less than 10 mins and no need to worries about uninstall magisk or any mod before
Antho02 said:
sure, even more quick if u dont need twrp
flash last rom with xiaomi flash (save user data selected)
then boot patched.img and install magisk, less than 10 mins and no need to worries about uninstall magisk or any mod before
Click to expand...
Click to collapse
I have some questions it would be a be a pleasure if you could answer.
Q1 will the modules remain or not ?
Q2 how to make make patched boot img I mean should I make my self using Magisk Manager app
Q3 Also which TWRP do you use and if it has any problems
Q4 should I use zip file or tgz for mi flash