Hi I was following the instructions here:
http://androidforums.com/wildfire-s...-how-root-wildfire-s-a510e-gsm-s-finally.html
I got to stage 4A when I have to fastboot the recovery. It seemed to work alright then when I tried to load into recovery it just went to black screen. So I did the alternative and tried to flash TWRP recovery but now it just restarts my phone when I select recovery in the Boot screen.
What shall I do?
I dunno if it is related but google play cannot connect. Everything else works ok.
Maybe if I put the original recovery back on it i can try to get clockwork or the other on there again? Is it because I have a more recent version of the hardware?
Related
What I was trying to do: I have a stock 4.4.2 AT&T GS3 that I wanted to root, and then install Cyanogen Mod.
What I did: I flashed Auto-Root with Odin 3.10, restarted and then flashed TWRP 2.8. I then booted to TWRP and attempted to wipe/format the phone but it showed some errors along the way, I think it was something having to do being unable to mount the SD card. I then rebooted into recovery and flashed CM12 and slim Google Apps zip. When it was flashing both I got a string of errors but it said it was successful.
Where I'm at now: When I try turning the phone on (without holding any buttons down) it attempts to boot straight to the TWRP but gets stuck at the blue TeamWin screen. I'm able to get to download mode by holding down the appropriate buttons. I'm wondering if there's anything I can flash from Odin to resolve this.
I also realized I have unbacked up photos on the device, I don't think the format was successful, is there any way to recover those?
Thanks
To recover the pictures, try re-installing TWRP, boot into TWRP, and mount the partitions. Connect the phone to your computer and copy your pictures.
TWRP
I have had this happen before. Try using Odin to flash an older version of TWRP, uncheck reboot after flash and then when it is done, do a battery pull. This has gotten me back into a working TWRP to restore my previous setup. Note: You made need to go back to 2.6. Once you have gotten back up and running flash to the current TWRP with the app.
my tmob s4 is stuck on boot screen i tried to update twrp from twrp manager and it said unsuccessful and ask to reboot into recovery i said yes and it rebooted and now when it goes to boot screen and says on top in little blue words botting recovery it just stays there what can i do?
i tried battery pull and Manually going into recovery nothing seems to work plz help.
UPDATE: odin latest firmware NK2 working great!
The lateat version of twrp is borked. Its what caused your problem.
Any previous version will work fine
So recently i flashed the new cyanogen 14.1 nightly rom but it said their was an update but after i installed it it tried to go into recovery and wouldnt start. I shut it down and it would only go into fastboot mode and show the boot image. after this i downloaded fastboot and adb files and a tool kit and it now boots into the actual rom but still not recovery. so how can i get the recovery to pop up? iv already tried to flash twrp again but it still didnt load. and i even flashed the stock recovery and still wouldnt boot up. if anyone knows a way i can fix my recovery it would help alot.
May want to check out http://forum.xda-developers.com/oneplus-3/help/boot-recovery-cm14-1-nightly-official-t3497425 thread.
thanks i will try this
i checked it out and will try it as soon as i can
Same question over and over again
Dude on same page you got answer just USE EYS
Hi,
I had TWRP .28 recovery installed but it was unable to decrypt data, so I decided to flash stock recovery back via fastboot. Now if I try to boot into recovery I get the 1+ logo and after that the phone gets stuck in black screen. I tried to flash it again and same issue.
How can I get the stock recovery working again?
Same here. I got a boot cycle after the update of 4.0.1 and thought, reverting to stock recovery is a good idea ... NOT.
The problem now is the the same as you described it: black screen after the 1+ Logo.
When selecting the boot options (unlocked OEM Warning) i can go to fastboot, but the device is not found => no sideloading
Any idea
derdakkar said:
Same here. I got a boot cycle after the update of 4.0.1 and thought, reverting to stock recovery is a good idea ... NOT.
The problem now is the the same as you described it: black screen after the 1+ Logo.
When selecting the boot options (unlocked OEM Warning) i can go to fastboot, but the device is not found => no sideloading
Any idea
Click to expand...
Click to collapse
I managed to fix mine. Apparently the old stock recovery doesn't work with Android N. I downloaded open beta 8 recovery and flashed it via fastboot.
I got the link here: https://forum.xda-developers.com/oneplus-3/help/ota-failed-boot-stock-recovery-t3533927/post70445320
Was trying to update the supersu binary by installing the updated zip in recovery. On reboot it was stuck in a boot loop. First off nothing else worked, then fastboot worked and then 10 mins later twrp recovery started working. I tried to restore a backed up image but still got boot loop. Then tried to flash a rom I had on sdcard - still boot loopy. Tried to go the miflash tool root but couldn't get it to find the phone despite it appearing in explorer. Copied stock miui zip onto sc card from pc and installed but still same problem. Standard dalvik/cache wipe before and after each install. Now I'm struggling to get recovery up.
Help - haven't managed to totally brick something despite many years of tinkering. :/
PS. I can still get fastboot up. Now when I try to get recovery up the screen goes black and I have to reboot.