Edit: For the solution, go to post #7
Looking for help here. I have a butterfly X920d.
I received an update for 1.19.707.1 yesterday and I updated it. The problem is I have TWRP installed.
So now when the main update package (1.19.707.2) is downloaded and reboots to continue installation, it always reboots into TWRP instead of installing it.
I have tried to flash 1.12.707.1 RUU but it always end up in error 43 (FAILED (remote: 43 main version check fail), upon research tells me that it is incompatible with the 1.19.707.1 I have recently updated.
To perform the above action, I locked the bootloader, which introduce a new problem. When the 1.19.707.2 reboots to install, it is stuck at the HBoot/Fastboot screen. It remain there until I manually reboot it.
In a summary;
In 1.12.707.1, installed TWRP and rooted
Got an OTA update for 1.19.707.1, download and run it, while rooted
1.19.707.1 installed properly
Phone begins to download and install 1.19.707.2
Upon restart to complete, installation stuck in TWRP screen
Relocked phone and tries to flash 1.12.707.1 RUU to return to stock
Error 43 (FAILED (remote: 43 main version check fail) in fastboot RUU flash
Restarted process 4, but now instead of booting to TWRP, it is stuck in Fastboot
I'm thinking, as the update process does not support TWRP recovery, it is stuck in 1.19.707.1
As I have locked the bootloader, TWRP is unable to start. Would unlocking it again via unlock.bin softbrick my phone?
Is there any help or guide to help me get out of this spiral of misery?
Thank you in advance.
Edit: is there anyway to flash just the stock recovery to replace twrp instead of the whole RUU?
Stock ota update uses stock recovery twrp doesn't work try to pull from stock ruu.zip unzip and locate recovery.img and flash like you did twrp
Sent from my HTC Butterfly using xda app-developers app
Bassie39 said:
Stock ota update uses stock recovery twrp doesn't work try to pull from stock ruu.zip unzip and locate recovery.img and flash like you did twrp
Sent from my HTC Butterfly using xda app-developers app
Click to expand...
Click to collapse
@Bassie39, should I use recovery from 1.12 or 1.19?
Thanks
Depends on which version your are running now
Sent from my HTC Butterfly using xda app-developers app
It is strange that 1.19.707.1 did not overwrite my TWRP recovery during the initial upgrade.
It is strange but you can try to flash recovery yourself
Sent from my HTC Butterfly using xda app-developers app
Woah, took the dive, went in and emerged successfully.
Thanks to the advice from @Bassie39, I reflash my recovery from 1.19.707.1 (link) [Please read the instructions to get the correct files.]
I had to unlock my device before flashing the recovery due to relocking it earlier. Same old story, all of the data was wiped.
Summary of my steps.
Flash stock recovery.img, extracted from 1.19.707.1 RUU
Reboot phone
1.19.707.2 installed succesfully from OTA
2.33.707.3 updated as well upon reboot
Reflash TWRP 2.6
Root using busybox
SuperSU not working in 4.2.2 (probably leftovers from the previous root)
Downloaded SuperSU and flashed in recovery
Root and Titanium backup working finally
Those who are having the same issue, you need not relock your device. Just flash stock recovery, and the OTA is good to go.
After that, flash TWRP and root if you like.
Relock is indeed not necessarily only stock boot.img and recovery.img
Sent from my HTC Butterfly using xda app-developers app
Got the impression that lock was required for flashing stock recovery from other forums.
With my dlxu it works fine stock ota runs oke and bootloader still open
Sent from my HTC Butterfly using xda app-developers app
kemikelx said:
Woah, took the dive, went in and emerged successfully.
Thanks to the advice from @Bassie39, I reflash my recovery from 1.19.707.1 (link) [Please read the instructions to get the correct files.]
I had to unlock my device before flashing the recovery due to relocking it earlier. Same old story, all of the data was wiped.
Summary of my steps.
Flash stock recovery.img, extracted from 1.19.707.1 RUU
Reboot phone
1.19.707.2 installed succesfully from OTA
2.33.707.3 updated as well upon reboot
Reflash TWRP 2.6
Root using busybox
SuperSU not working in 4.2.2 (probably leftovers from the previous root)
Downloaded SuperSU and flashed in recovery
Root and Titanium backup working finally
Those who are having the same issue, you need not relock your device. Just flash stock recovery, and the OTA is good to go.
After that, flash TWRP and root if you like.
Click to expand...
Click to collapse
I have updated to 2.33.707.3 too. But I didn't save the Update file into my computer. I want to root my phone, so I need to flash TWRP first and then flash the root file, but after that I want to change my recovery to stock one. Do you have any backup of 2.33.707.3 stock recovery.img?
can you pls help me with the stock recovery.img of 2.33.707.3. i want to upgrade to 4.3 ota and it keeps rebooting to twrp recovery. looked all around but no solutions for 707 region. would be grateful for any help.
vsinha71 said:
can you pls help me with the stock recovery.img of 2.33.707.3. i want to upgrade to 4.3 ota and it keeps rebooting to twrp recovery. looked all around but no solutions for 707 region. would be grateful for any help.
Click to expand...
Click to collapse
I'm presently having issues to update to 3.15.707.4 as well. I'm trying recovery-1.12.707.1
Edit: Recovery failed.
Related
cwm with odin but if i go to recovery , it still go to stock revovery
i am using N8000XWALH1 after i get OTA update , it is normal , but i flash to stock recovery to get ota update ， and i flash cwm again ， its show success but i go to recovery it is still go to android system recovery （3e）
need help...
sorry for english
is android system recovery 3e 's plobrem?
Did you get OTA update?
I read that protects stock recovery in a new way.
Sent from my GT-N7000 using Tapatalk 2
lettucegoatee said:
Did you get OTA update?
I read that protects stock recovery in a new way.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
yes i ota update to N8000XWALH1
just i go to cwm but it will go to stock recovery
can somebody help me i need root
Did you read the instructions? In this case, when flashing CWM with Odin, do not set the "reboot" flag in Odin. Instead, after flasing, reboot manually and direct into recovery. Then flash SuperSU.
If manually rebooting immediately after flashing CWM brings you to stock recovery, the flash was not sucessful.
Update: This bootloader is older and is not the newest available one. If you want the 4.18 version one go to THIS post and flash it with fastboot.
Older bootloader version: Doesn't flash and take hold for everyone, flash at your own risk
Usefull for people that don't want to flash in fastboot. The official OTA for 4.2 flashes this bootloader through recovery in the exact same manner
Code:
md5sum: 7cb16bc418e15ee2c7c48b82ea923e23
Code:
sha1sum: 6151d4afd075d03cfdfa33d111a1a6bba25fcab8
Code:
sha256sum: 2b7efeade37c1ec00d03ba71a56d5b921e6c27d4393298020bcd1601ae079605
Code:
sha512sum: cd7444ec7073e553b7715e4ee30d69f64b06ab3846f1d0ff3d9129f652ab4e90c3400f139a0347f0b78a0719c86b6e2d7f41d36068f032472dbc90c3530cefcb
You need to be aware that on my Nexus7 the problem with Custom Recovery on the newest bootloader still exist.
Means you need to downgrade to 3.34 in order to flash CWM.
remmyhi said:
You need to be aware that on my Nexus7 the problem with Custom Recovery on the newest bootloader still exist.
Means you need to downgrade to 3.34 in order to flash CWM.
Click to expand...
Click to collapse
I need to be aware of problems that happens on your Nexus7? I don't have that issue I flashed TWRP Recovery just fine on this booloader...
No, I did not write to you personally. Glad it worked on your side.
Just the people to know.
That's really strange. I would try flashing the 4.1.2 factory images even though it might wipe everything including your sdcard.
Sent from my Nexus 7 using Tapatalk 2
Did that, thanks. Indeed wiped everything
Glad I had a backup
Hey guys,
So, I can flash this file from TWRP and it will upgrade my bootloader?
Thanks in advance!
you can, but make sure you check MD5, flashing a corrupt download can kill your device. OP, you should add a MD5 check in the zip if possible. but thanks for this none the less.
If you have a rom like cm10 installed or other rom that has buysbox in it, just type busybox md5sum /sdcard/bootloader-grouper-4.13.zip
Either in terminal emulator or adb shell.
If your on stock you'll probably want to check it with a program on your pc or install busybox from one of the playstore busybox apps. Of course you'll need to be rooted.
Sent from my Nexus 7 using Tapatalk 2
I went ahead and added sha1sum, sha256sum and sha512sum checks.
I have just flashed the file and thank you, I no longer have to keep my power button pressed for 20 seconds just to have my tablet go on
Thank you so much!!!
If anyone has any problems there is a link in my SIG to fix it or if you just need to revert back...
Just a FYI the older bootloaders are in the factory images! You can extract them out and flash the bootloader separately if you don't want to flash ALL the factory images. So far flashing this with twrp I have not had one single issue yet to speak of... Each bootloader is meant to run on specific platforms, recoveries, kernels ect. So on that note I still suggest if you want to revert your bootloader you revert completely with the factory images.
Sent from my Nexus 7 using Tapatalk 2
Hi,
thanks for that but when i falsh it in TWRP it's wipe all my data but i still have the 3.41 bootloader?
I'm not sure if i understood the thing to do with the md5sum?
f*** this bootloader i flash it yesteday.........
and my tablet stay on bootloader and i can't flash google image 4.1.1-4.1.2-4.2
why??
i can't downgrade bootloader too.........
CWM + CM10 stable
I just flashed this bootloader using CWM 6.0.1.0 and CM10 stable. I used Chrome to download it and the md5sum command in terminal emulator to check the md5 hash before hand. It flashed fine, I have the new version number, everything continues to work. Very easy.
farshad.shirzadii said:
f*** this bootloader i flash it yesteday.........
and my tablet stay on bootloader and i can't flash google image 4.1.1-4.1.2-4.2
why??
i can't downgrade bootloader too.........
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showpost.php?p=32735541&postcount=5039
Thanks, easy flash, works perfectly
Sent from my Nexus 7 using xda app-developers app
Wondering does the new boot loader support older custom ROMs and the nexus toolkit, will I need to re unlock bootloader after flashing it ?
Answered my own questions flashed with cwm still have root but don't know how to check if boot loader is locked or what version I have. Works fine with cm10.
Sent from my Nexus 7 using xda premium
blucmal said:
Wondering does the new boot loader support older custom ROMs and the nexus toolkit, will I need to re unlock bootloader after flashing it ?
Answered my own questions flashed with cwm still have root but don't know how to check if boot loader is locked or what version I have. Works fine with cm10.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
When you power your device on you hold the volume down button to get into bootloader. On the main screen it will say what version it is.
Sent from my Nexus 7 using Tapatalk 2
Hi everybody.
I had some custom roms installed but now I returned back to stock with the ruu.exe but I wanted to get root so I put twrp on my phone and flashed superuser but now there was an update for system optimizing but I cannot install it because it want to go into recovery but it open twrp because I don't have stock recovery so how will I get the stock recovery to my phone ?
Thanks in advence.
Sent from my HTC One S using xda app-developers app
Which one do you have?
The T-Mobile one is posted in a few places but not sure about others.
I have the EU one I have jelly bean since December.
Sent from my HTC One S using xda app-developers app
Simply download ville_recovery_signed.img from here and flash in fastboot mode
'fastboot flash recovery ville_recovery_signed.img'.
--- edit
little but important change...
rootrider said:
Simply download ville_recovery_signed.img from here and flash in fastboot mode
'fastboot flash boot ville_recovery_signed.img'.
Click to expand...
Click to collapse
Don't you mean
fastboot flash recovery ville_recovery_signed.img
Sent from my HTC One S using Tapatalk 2
Yep - absolutely!
Thanks a lot - was in a hurry!
Flash error...
I'm having the same problem. But when I flash the recovery (from link above) I get the error message
<remote: signature verify failed>
Is this the wrong recovery for my phone (4.1, C1, rooted, stock ROM)?
I also just realized, that I'm getting this error with ANY recovery (TWRP etc.) I'm trying to flash...
Please help! Thanks!
Schnorgl said:
I'm having the same problem. But when I flash the recovery (from link above) I get the error message
<remote: signature verify failed>
Is this the wrong recovery for my phone (4.1, C1, rooted, stock ROM)?
I also just realized, that I'm getting this error with ANY recovery (TWRP etc.) I'm trying to flash...
Please help! Thanks!
Click to expand...
Click to collapse
Are you using the all in one toolkit ?
sGollSv said:
Are you using the all in one toolkit ?
Click to expand...
Click to collapse
No, I'm not.
But I figured out what might have caused the problem: an outdated stock recovery file (they all have the same file name...
Installed RUU, TWRP and root and now everything works smoothly. What a hassle for such a minor update!
I recently rooted my one s succesfully. I go through twrp recovery and try to install a custom rom always unsuccessfully. I think the problem is that it cant extract files in my sdcard after mounting it and puting the rom zip manually by pc there, but i am not sure. It stucks in the HTC screen with no further progress. What can i do?
Seems like your phone is s-on. If that's the case you have to flash the boot.img file manually via fastboot.
Sent from my HTC One S using xda app-developers app
Mainly you can, better should do these two things:
1. Using TWRP version 2.3.3.0 for flashing as later versions exactly produce your kind of error
2. Flashing the kernel separately from your rom.zip file with 'fastboot flash boot kernel.img'
So Just received my 2.2 Update, and was going to install it when I remembered, "Wait! I am rooted!"
My question is can I update too 2.2 and not have anything "bad" happen.(Root Lost, System Boot Loop, etc)
I am running Stock Update 2.1 with Root.
EDIT: I have CWM set as my recovery.
Another user did it in general forum and it doesnt flash because of mismatch
Just like the last Lollipop update, if you're rooted, you'll need to return to stock.
Otherwise, wait until the full rom .zip is available and then download it and flash it in your custom recovery followed by re-flashing the latest SuperSU .zip.
Sent from my SHIELD Tablet using XDA Free mobile app
An Droid said:
Just like the last Lollipop update, if you're rooted, you'll need to return to stock.
Otherwise, wait until the full rom .zip is available and then download it and flash it in your custom recovery followed by re-flashing the latest SuperSU .zip.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Im on Philz
Can I flash recovery image via "fastboot flash recovery recovery.img", then reboot the tablet, install the OTA and then with Flashify flash Philz again?
EDIT: I just re-read what I posted. Can I use flashify to flash stock recovery, updating with OTA and then reflash Philz?
NaminatoR1254jaime.sier said:
Im on Philz
Can I flash recovery image via "fastboot flash recovery recovery.img", then reboot the tablet, install the OTA and then with Flashify flash Philz again?
EDIT: I just re-read what I posted. Can I use flashify to flash stock recovery, updating with OTA and then reflash Philz?
Click to expand...
Click to collapse
The "full" 2.2 OTAs are available everywhere on xda right now...Just flash the appropriate one, reflash recovery (if you have to) and then reflash supersu.
ailima said:
The "full" 2.2 OTAs are available everywhere on xda right now...Just flash the appropriate one, reflash recovery (if you have to) and then reflash supersu.
Click to expand...
Click to collapse
I already updated hahaha, I didnt remember this post. Thanks anyway!!