I have already attempted to flash the complete file and see if that worked to update, but I was stuck in a boot loop. I tried flashing the modem, boot and bootloader that also did not work. Do I have to go back to stock then flash the complete file and go back to the fluence patch?
Sent from my LG-H830 using Tapatalk
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.
So I'm not sure what went wrong or where but with in the last couple of days, I rebooted my phone and in loaded into odin with "could not boot normally." I could get passed this is using odin to flash some rooted images but no matter what I try, I can not get the bootloader unlocked. I can get root, recovery, and custom roms. However, every method I have tried won't unlock the bootloader and every reboot after a flash other than a stock rooted image will reboot into odin with the "could not boot normaly."
All help is appreciated.
Trybal said:
So I'm not sure what went wrong or where but with in the last couple of days, I rebooted my phone and in loaded into odin with "could not boot normally." I could get passed this is using odin to flash some rooted images but no matter what I try, I can not get the bootloader unlocked. I can get root, recovery, and custom roms. However, every method I have tried won't unlock the bootloader and every reboot after a flash other than a stock rooted image will reboot into odin with the "could not boot normaly."
All help is appreciated.
Click to expand...
Click to collapse
try this:
http://forum.xda-developers.com/showthread.php?t=1840030
Try the second post, sounds exactly like your problem.
Sent from my SCH-I535 using Tapatalk 2
You have to an unlocked bootloader to get recovery installed. So if you can reboot into a custom recovery then you have an unlocked bootloader
Sent from my SCH-I535 using Tapatalk 4
Sandman-007 said:
You have to an unlocked bootloader to get recovery installed. So if you can reboot into a custom recovery then you have an unlocked bootloader
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
True, but my Qualcomm Secureboot is always Enabled. And when I flash a rom and reboot during the rom, it goes to Odin saying could not boot normally.
I did try Hero's softbrick method and I got the same results. It's like the unsecured aboot doesn't stick. Do I need a to facepalm myself somewhere? I'm seriously lost.
Trybal said:
True, but my Qualcomm Secureboot is always Enabled. And when I flash a rom and reboot during the rom, it goes to Odin saying could not boot normally.
I did try Hero's softbrick method and I got the same results. It's like the unsecured aboot doesn't stick. Do I need a to facepalm myself somewhere? I'm seriously lost.
Click to expand...
Click to collapse
Ignore that Secureboot enabled message. It will always say that no matter what. It's been discussed that its a bug. Hang on and I'll link u to method of unlocking and rooting works no matter what. Doesn't rely on unsecure aboot images either
This works everytime. I recommend flashing the stock Image AND STOCK BOOTCHAIN or recovery won't install. Those are listed at the bottom of the tutorial. If you are on stock just install the stock bootchain
http://rootzwiki.com/index.php?/topic/29256-[TUTORIAL]-[ROOT/RECOVERY/BOOTLOADER-UNLOCK][ICS/JB]-Verizon-Galaxy-S-III
Sent from my SCH-I535 using Tapatalk 4
Alright, thank you. Hopefully this hold because getting stuck in odin is beginning to get annoying as well as being on a stock rom the last few days.
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.
My One has been acting up lately. It started out that I couldn't turn off WiFi. I would turn it off but it would turn itself back on shortly thereafter. It has nothing to do with WiFi optimization or anything like that...I've fiddled with all those settings. Anyway, I updated to 38R thinking it might fix things, but no such luck. So I fire up titanium backup in preparation for a full wipe and find out that my device is no longer rooted. On top of that, TWRP is gone as well. No big deal, reflash TWRP and re-root. Nope. ADB says that TWRP flashes successfully, but when I boot into recovery I get the standard Cyanogen recovery instead of TWRP. Any thoughts?
Have you tried flashing stock and starting from scratch?
Did you remember to uncheck the option for updating fastboot with system update as well?
Sent from my Nexus 7 using XDA Premium HD app
Admeisterz said:
Have you tried flashing stock and starting from scratch?
Did you remember to uncheck the option for updating fastboot with system update as well?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Unfortunately I missed the fastboot update bit. Did I **** myself with that?
If you could access CWM do a factory reset, and hopefully that clears up your problems, if not go back to stock via: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
the only reason why i could think that it'd say flashing is successful is it's flashing to the wrong partition (which doesn't make any sense), or the bootloaders locked, which it isn't since from your post it says you had TWRP installed, but try going back to stock fully via fastboot, then installing twrp and such.
I was just wondering because every time I flash a kernel I go through the process of flashing the stock kernel/boot image and every time I do that the stock recovery pops up again. Is it because the stock recovery is on the stock boot image? After flashing it I need to go through the process of flashing TWRP and the TWRP installer to get it back.
Sent from my ONEPLUS A6003 using Tapatalk
tdamocles said:
I was just wondering because every time I flash a kernel I go through the process of flashing the stock kernel/boot image and every time I do that the stock recovery pops up again. Is it because the stock recovery is on the stock boot image? After flashing it I need to go through the process of flashing TWRP and the TWRP installer to get it back.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Yes!