Related
I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please
ImjuzCY said:
I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please
Click to expand...
Click to collapse
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358
jj14 said:
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358
Click to expand...
Click to collapse
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be
ImjuzCY said:
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be
Click to expand...
Click to collapse
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this
jj14 said:
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this
Click to expand...
Click to collapse
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now
I tried everything and still get wrong build fingerprint when trying to flash the 5.0
ImjuzCY said:
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now
Click to expand...
Click to collapse
Hello!
Really want to flash the OTA without a total wipe.
First flashed it from TWRP 2.8.1.0 and got the wrong build finger print says I have Flo:4.3/JSS15Q/779366 and it expects KTU84P/1227136
Then using WugFresh 1.9.4 flashed stock recovery so I could sideload then encountered the whole adb disappearing in recovery - eventually solved that and finally managed to adb sideload saw my screen saying it was installing the update using the stock recovery - YAY! It was short lived as the stock recovery screen told me the exact same thing that TWRP had told me.
I looked at my build.prop and it says my ro.build.fingerprint=google/razor/flo:4.4.4/KTU84P/1227136. user/release-keys
Can someone enlighten me? I've wasted so much time on this I would love some keen insight - PLEASE!!
Thanks for any and all help!
Edbogue
Google changed the way OTAs work in 5.0. You will usually not be able to flash a OTA if your OS is modified. Means no custom recovery or root. You will have to flash your tab back to stock kitkat.
Before it would patch individual file blocks, now it patches the whole system partition as a blob. Read more http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
Workaround that helped me upgrade
Following the steps below seems to have done the trick for me. My issue was that Android 5.0 updates the system partition all in one go now, rather than each file separately. Following those steps will unroot your device but will allow you to install the OTA updates.
So follow these steps to refresh your current Android version (e.g 4.4.4) then use OTA or adb sideload to update to, for example, 5.0.
This will not wipe user data or the cache.
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
I would post my source, but as I only just joined to say what helped me, I'm not allowed to post links I'll just say Google "flashing-a-stock-android-image-without-wiping-user-data" and (as of 19/11/2014) it's the top result.
Please continue here: http://forum.xda-developers.com/nexus-4/help/android-5-0-0-to-5-0-1-update-t2972371#post57515317
Finally finally!!! A fix!
Raingram said:
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
.
Click to expand...
Click to collapse
Thank you Raingram! This worked perfectly!
I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.
You did the unlock bootloader bit in settings?
ReneX10 said:
You did the unlock bootloader bit in settings?
Click to expand...
Click to collapse
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.
GigahurtzUK said:
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.
Click to expand...
Click to collapse
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment
ReneX10 said:
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment
Click to expand...
Click to collapse
No other devices to test with.
I will have to try linux then. I just need a usb to make a linux live usb
Cheers
GigahurtzUK said:
I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.
Click to expand...
Click to collapse
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.
Is this the norm when changing recovery.img?
M_Kay said:
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.
Click to expand...
Click to collapse
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?
noob2016 said:
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?
Click to expand...
Click to collapse
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.
Thanks for the fast reply and help
M_Kay said:
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.
Click to expand...
Click to collapse
1st thanks for fast reply and help
im not in bootloop, thank goodness!
I'm currently in TWRP, when the recovery was in CM the gapp-arm64-aroma-5.1 it installed flawlessly following the cm12.1 flash but after the update 13.0 the gapp can't be installed even reverting back to 12.1 and using the same files. I did wipe all prior to change of rom also match it (i.e. cm13.0 to gapp 6.0).
Maybe this will solve it. I will try to erase recovery and re-install TWRP
i will report back after. Thanks
Works
Thanks it worked on pico gapp but not in aroma
followed the erase command and install TWRP again.
Many thanks
TWRP not working in Aroma Gapp need fix
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
noob2016 said:
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
Click to expand...
Click to collapse
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP
Thanks
robin0800 said:
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP
Click to expand...
Click to collapse
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb
noob2016 said:
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb
Click to expand...
Click to collapse
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial
I will try
robin0800 said:
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial
Click to expand...
Click to collapse
Thanks for the reply and also on my other post.
Since this is for swift, i will try to install but sadly i have given it back already. It was just here for the upgrade and when i got the chance to get hold of it again i will definitely try and report back.
Many thanks.
Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks
msiviter said:
Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
robin0800 said:
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
I think it was a windows 10 problem, I gave it all another try this morning firstly using the WinDroid Universal Android Toolkit to Unlock Bootloader and flash TWRP . I then rebooted into recovery and hey presto TWRP. Flashing CM13 nightly and pico gapps was then childsplay.
Any ideas why google play didnt offer to auto restore all my apps? Thats a bit of a pain.
Otherwise very pleased, phone seems a bit more responsive using CM13 than CyanogenOS. I tried to format my SD to use as internal storage too but i couldnt see them separately afterwards to free up device storage so I reverted back.
Thanks for trying to help.
Yey!!!
robin0800 said:
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
Confirmed!!! It works... i used TWRP 3.0. Works on both aroma and pico. Thanks so much!!!!
Got stuck in a TWRP loop after installation. Regardless which reboot option I choose, always TWRP 3.0.0 comes up. No idea what I did wrong but for me it is of more interest how to get rid of it. Accessible external SD contains cm14-zip and also Stock 6.0.1. Installed CM14 multiple times, but has no impact on what comes up after selecting reboot/reboot recovery/reboot fastboot - it is always TWRP. Tried it also via adb sideload from within TWRP, no change of behaviour. Same when I tried to install stock rom.
Bootloader issue? How to get it back? I have 2 further Swifts available so I can dump several necessary partitions from them, but I need to know which tools are required, since I usually deal with MTK-based androids. Backup of userdata and sdcards is available, so if a reset to stock is necessary, this is not a problem from that point of view - if I only would have the info, how to get back a working bootloader.
Even though I love this recovery, it is obviously annoying ... Any help appreciated. Tnx in advance!
Edit: Fixed. I removed the battery for several hours and without battery with plugged in USB cable (not the WF one, I have tons of them lying arround here) I was able to reboot to normal fastboot. From then on it was strraightforward:
checked OEM lock status via fastboot command on PC
flashed newest TWRP
rebooted to TWRP
installed Stock ROM to get all partitions reinitialized correctly
rebooted to OS - YEAH, the swift lives again
Rebooted to recovery
Installed CM14 and OpenGApps Nano (ARM, not ARM64, since it produces an error)
Reboot to OS - YEAH, here we are.
ROM for Sony Smartwatch 3 [LCA43, Android 5.1.1]
ROM Features:
Stock LCA43 base
Disabled OTA updates
Custom Kernel tetra_2.x
TWRP recovery
Tweaks
Click to expand...
Click to collapse
Versions
v 2.0
Kernel tetra_2.27.1
Minor tweaks
v 1.0
Stock LCA43 base
Kernel tetra_2.22
Disabled Low Bit Ambient Mode (thanks to andrewia)
Minor tweaks
Click to expand...
Click to collapse
Installation:
Put ROM to your virtual SDCard
Boot into TWRP recovery
Select "Install", and choose ROM zip file
After installation completed- reboot watch
If necessary - make full wipe
Click to expand...
Click to collapse
Downloads
SW3_rom_v2
TWRP recovery
Click to expand...
Click to collapse
Big thanks to scrubber for his ROM backup!
Code:
[COLOR="Red"]DISCLAMER[/COLOR]
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or
you getting fired because the alarm app failed. Please do some research if you
have any concerns about features included in this ROM before flashing it!
YOU are choosing to make these modifications, and if you point the finger
at me for messing up your device, I will laugh at you.
If you like my work- Donate to me
Contributors:
alex6600
scrubber
Version Information
Status: Stable
Created 2016-04-27
Last Updated 2016-05-11
Reserved by OP
thanks alex6600.
can you upload original kernel to ?
edit : found on 4pda https://mega.nz/#!Rt8hBS5T!MHOufeqXYJqrcShyXG2_f3uLO7_ZlP_H6T0cVm0R4Hk
thanks again.
Thanks @alex6600!
Just factory reset, and downgraded from Marshmallow, to this ROM.
All is working well so far!
crunchybutternut said:
Thanks @alex6600!
Just factory reset, and downgraded from Marshmallow, to this ROM.
Click to expand...
Click to collapse
I honestly tried to use Marshmallow. Compiles kernels dozens of times. But no luck.
Reboots and lags does not suit me.
And decides to use 5.1.1, as more stable.
I'm all about this ROM as Marshmallow has just been one big rebooting mess!
However, during flashing everything went fine except the build.prop install...
Your line:
mount("ext4", "EMMC", "/dev/block/platform/sdhci.1/by-name/system", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");
Click to expand...
Click to collapse
Fails saying device is busy, or is not ready...???
Hobbzey said:
I'm all about this ROM as Marshmallow has just been one big rebooting mess!
However, during flashing everything went fine except the build.prop install...
Your line:
Fails saying device is busy, or is not ready...???
Click to expand...
Click to collapse
Did you mount system in twrp before install?
Sent from my HTC One_M8 using XDA-Developers mobile app
I got it sorted out actually, turns out it was because I was using the version of TWRP I got from here:
http://forum.xda-developers.com/sma...24h-twrp-root-busybox-kernel-adiutor-t3365990
I initially skipped installing the one you provided above because I already had that one installed, but switched to the one you provided and reflashed with no errors!
One last question, is it possible to turn off the rounded screen corners? Is that something that can be edited into the build.prop or is it in kernel?
Hobbzey said:
I got it sorted out actually, turns out it was because I was using the version of TWRP I got from here:
http://forum.xda-developers.com/sma...24h-twrp-root-busybox-kernel-adiutor-t3365990
I initially skipped installing the one you provided above because I already had that one installed, but switched to the one you provided and reflashed with no errors!
One last question, is it possible to turn off the rounded screen corners? Is that something that can be edited into the build.prop or is it in kernel?
Click to expand...
Click to collapse
Rounded screen corners is a kernel feature, not ROM.
And do you recommend your LCA43 kernel from here http://forum.xda-developers.com/sma...ment/kernel-sony-smartwatch-3-kernel-t3304102 or should we stick with the one already in the rom? Or are they one and the same?
Hobbzey said:
And do you recommend your LCA43 kernel from here http://forum.xda-developers.com/sma...ment/kernel-sony-smartwatch-3-kernel-t3304102 or should we stick with the one already in the rom? Or are they one and the same?
Click to expand...
Click to collapse
Rom include kernel v. 2.22.
Today I posted 2.23 in kernel thread.
Sent from my HTC One_M8 using XDA-Developers mobile app
Hi everyone, could someone please help me? I'm trying to downgrade my SW3 from MM to this rom, but I don't know how to do it. I've got installed windroid toolkit but it doesn't anything. I can't install twrp, unlock bootloader... nothing. I've got correctly installed ADB drivers, windroid recognises my watch, but this is everything I can do until here. I'm trying to do the downgrade because my battery flies twice per day, meanwhile in MM battery lasted up to 4 days... Has someone the same problem?
asecob said:
Hi everyone, could someone please help me? I'm trying to downgrade my SW3 from MM to this rom, but I don't know how to do it. I've got installed windroid toolkit but it doesn't anything. I can't install twrp, unlock bootloader... nothing. I've got correctly installed ADB drivers, windroid recognises my watch, but this is everything I can do until here. I'm trying to do the downgrade because my battery flies twice per day, meanwhile in MM battery lasted up to 4 days... Has someone the same problem?
Click to expand...
Click to collapse
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.
Do you plan feature 6.0.1 update? What are benefits over stock...?
crunchybutternut said:
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.
Click to expand...
Click to collapse
Thank you for your help, but unfortunately my watch didn't pass the white screen saying fastboot. PC was saying "waiting for device" for so much time. Am I doing something wrong?
crunchybutternut said:
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.
Click to expand...
Click to collapse
Hello and thanks for the command lines.
I want to try it because my battery drain is too high with MM and kernel 3.10.1 (but no reboots).
But .... How can I use the virtual SDCARD? How do I have to do to put the zip file in this SD? AFter, I think it will be ok....
Thanks.
It's OK actually, just after twrp flash, I have "VIRTUAL SDCARD" on my windows pc, I put the zip and I flashed it in recovery.
Thanks
mickael91210 said:
Hello and thanks for the command lines.
I want to try it because my battery drain is too high with MM and kernel 3.10.1 (but no reboots).
But .... How can I use the virtual SDCARD? How do I have to do to put the zip file in this SD? AFter, I think it will be ok....
Thanks.
Click to expand...
Click to collapse
When the watch is connected to computer, type:
adb push rom_file.zip /sdcard/Download/
This command will copy ROM to /sdcard/Download directory.
alex6600 said:
When the watch is connected to computer, type:
adb push rom_file.zip /sdcard/Download/
This command will copy ROM to /sdcard/Download directory.
Click to expand...
Click to collapse
Thanks.... I was editing my post in the same time....
Thank you
More excellent work! Will we be able to root this (i.e. flash supersu.zip in TWRP)? Also, I can't seem to access the files (ROM.zip, TWRP.img), is the site down?
KittenSauce said:
More excellent work! Will we be able to root this (i.e. flash supersu.zip in TWRP)? Also, I can't seem to access the files (ROM.zip, TWRP.img), is the site down?
Click to expand...
Click to collapse
Webserver was in the planned maintenance. Now everything is working as it should.
SuperSu work fine. You can download SuperSu_2.46 here
Hi all, so I have Verizon's Pixel XL. I have unlocked it successfully and had rooted. I asked on the forums about upgrading the OTA update and was told it was fine. After doing so, I noticed my SuperSU was gone (although I might have lost it earlier and not noticed). So after trying to get it back and keeping getting stuck, I bit the bullet and ADB sideloaded the factory image from google (NDE63X) and got it able to boot up. Yay.
So then I ran the 'adb reboot bootloader' command, then verified my device was connected with 'fastboot devices' and finally I ran 'fastboot boot boot-to-root.img'. And here I am, stuck on the splash screen again.
So I looked around and saw some mentions of people that had used older versions of Chainfire's SuperSU. I tried the newer one (2.78 SR3) and the same thing happened. I do see that there is a SR5, but I also see Chainfire's comment "Do not use the SuperSU ZIP on work-in-progress TWRP releases for Pixel, it will not work - use the model specific links above instead.
I can get it to run just fine without using chainfire's supersu...but then I don't have the supersu app or any real gains from having rooted.
So, I feel like I must be doing something wrong. Any suggestions?
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
cam30era said:
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
Click to expand...
Click to collapse
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
smokeydriver said:
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
Click to expand...
Click to collapse
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
cam30era said:
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
Click to expand...
Click to collapse
The OTA update I took only got me to a new version of 7.1, not 7.1.1 (from NDE63P to NDE63X). It still shows an available update to 7.1.1 which I have *not* done.
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Nitemare3219 said:
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Click to expand...
Click to collapse
I've tried, but keep getting an error 21 code that it can't install...I tried this with SR5 and SR2.
How I Rooted
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb boot.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
Ok, I must be doing something wrong on a very basic level. It gave me error 21 (signature verification error) when trying to use the unified android tookit to install 7.1. Anyways, I'll just move on and skip that step and see what happens.
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Dees_Troy said:
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Click to expand...
Click to collapse
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
I transferred those 2 files to my download folder on my phone, ran the twrp.img script, and then when I go in...the file names are not normal. Everything is random letters and numbers. Again, I feel like I'm making some stupid basic mistake that I don't understand (and I've rooted plenty of phones).
spotmark said:
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Click to expand...
Click to collapse
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
smokeydriver said:
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
Click to expand...
Click to collapse
You have TWRP RC1 installed?
spotmark said:
You have TWRP RC1 installed?
Click to expand...
Click to collapse
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Ah, I see. I misunderstood. I thought you were just under the impression that you couldn't flash SU with RC1. My apologies.
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
toknitup420 said:
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
Click to expand...
Click to collapse
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
smokeydriver said:
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
Click to expand...
Click to collapse
Never mind...it's my 4 digit password that's used when my finger unlock doesn't work. Ugh- I knew it was something simple and dumb I was doing!
smokeydriver said:
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
Click to expand...
Click to collapse
Can I ask you how you fixed this? I'm having the same issue and this post popped up on Google.
Sorry if this has been posted but is it possible to switch to a custom ROM when running Android 10 (v11.0.4.0)?
If you have adb installed on your pc you only need these 2 for twrp, there might be a newer versions but they work fine for me.
img: (to boot from adb)
https://drive.google.com/open?id=1AwtLrERrSEql-ihhiAWPUh6DoXSWhZb9
zip: (to flash in twrp)
https://drive.google.com/open?id=1whcfSqbcNjmqXdnysu25KVX9PyX4mb-P
andraslate said:
If you have adb installed on your pc you only need these 2 for twrp, there might be a newer versions but they work fine for me.
img: (to boot from adb)
https://drive.google.com/open?id=1AwtLrERrSEql-ihhiAWPUh6DoXSWhZb9
zip: (to flash in twrp)
https://drive.google.com/open?id=1whcfSqbcNjmqXdnysu25KVX9PyX4mb-P
Click to expand...
Click to collapse
So should I just use MiFlash to boot each image file individually? Then I assume once TWRP is in I can flash as usual?
RensoreK said:
So should I just use MiFlash to boot each image file individually? Then I assume once TWRP is in I can flash as usual?
Click to expand...
Click to collapse
Never used MIflash so I don't know how that works. I thought it's only to install stock rom, but I might be wrong. Use ADB to install custom ROMs
With the img file you can boot to twrp with ADB command. Then after installing a custom rom use the zip file to flash it .
I am unable to find any adaptable guide anywhere. Tried using XiaomiTools v2 and was unable to flash because my device (even though has a Mi account created) cannot be linked to my device, I have no where to link it on AndroidOne Global version on Android 10. No clue how you guys are doing this. I've flashed phones since Blackberry models here on XDA and this is the only device instructions are halfed.
RensoreK said:
I am unable to find any adaptable guide anywhere. Tried using XiaomiTools v2 and was unable to flash because my device (even though has a Mi account created) cannot be linked to my device, I have no where to link it on AndroidOne Global version on Android 10. No clue how you guys are doing this. I've flashed phones since Blackberry models here on XDA and this is the only device instructions are halfed.
Click to expand...
Click to collapse
find dee_stroy twrp img one. use adb (platfom-tool), then turn off your device and make it go to bootloader state (fastboot). on platform-tool open cmd. (just type on folder path cmd) then type fastboot boot (the name twrp).img and you are set to go. if you wanted to install twrp permanently, after u boot twrp via bootloader, copy the twrp zip to your device and install it. the procedure is all; the same for every rom tho. nothing has changed
Can anybody help me installing this?? .. I had twrp before I installed havoc is 3.6 (android 10) but i didnt install twrp now I can't install twrp please anybody help me
Autokiddo said:
Can anybody help me installing this?? .. I had twrp before I installed havoc is 3.6 (android 10) but i didnt install twrp now I can't install twrp please anybody help me
Click to expand...
Click to collapse
fastboot boot trwp.img
Use TWRP to install twrp.zip
If you were rooted...
fastboot boot patched.img
Use Magisk manager to install (direct)
install twrp
hi, could someone kindly give me a step by step guide to install the twrp recovery?
i have the build QKQ1.191002.002.V11.0.10.0QDLMIXM.
thank you.
InsectWarfare said:
hi, could someone kindly give me a step by step guide to install the twrp recovery?
i have the build QKQ1.191002.002.V11.0.10.0QDLMIXM.
thank you.
Click to expand...
Click to collapse
Nothing?
Inviato dal mio Mi A2 Lite utilizzando Tapatalk
InsectWarfare said:
hi, could someone kindly give me a step by step guide to install the twrp recovery?
i have the build QKQ1.191002.002.V11.0.10.0QDLMIXM.
thank you.
Click to expand...
Click to collapse
This has been documented elsewhere...
The short version is
1) fastboot boot twrp.img
2) adb push twrp-installer.zip /sdcard
3) use TWRP to install the zip
If you also want Magisk you have to install that again. Flash from TWRP or follow the usual process.