I've been running venom viperx roms for some months. Today I wanted to upgrade from a 3.3 version to 3.4 but to my dismay I found that my recovery no longer worked. If I select the recovery option from the bootloader, I get sent to a black screen where ADB works but nothing I do seems to impact what is seen on the screen. I tried some things like fastboot clear cache, reflashed CWM, tried TWRP but no dice. Then I relocked, reverted back to stock using a RUU, unlocked again and flash CWM again.. Only to still be greeted by nothing but a black screen when entering recovery. I'm not sure what to try next, but what I do know is that I currently seem stuck at a stock ROM and this will not stand
Any advice?
I didn't think it'd be related, but once I started to search for "black recovery after screen replacement" I found a this thread with a link to this recovery which got me back on track.
Related
Can someone help, i just used odin to flash the rooted g1 image. Now i am stuck at the "samsung" screen. I just came from other custom roms such as cyanogenmod, aokp, and other touchwiz roms. I am assuming i have a diffrent kernal or diffrent bootloader and thats why I am stuck? How can i fix this?
My process:
I went from cyanogenmod to a touchwiz rom. Decided to go back to stock. Flash using TWRP Bootloader and kernal from the first post (http://forum.xda-developers.com/showthread.php?p=31802808). Then used odin to flash root injected g1 image. Now it hangs at the samsung logo, i cant get into recovery (pretty sure i flash over that), but i can get into download mode.
hunter99507 said:
Can someone help, i just used odin to flash the rooted g1 image. Now i am stuck at the "samsung" screen. I just came from other custom roms such as cyanogenmod, aokp, and other touchwiz roms. I am assuming i have a diffrent kernal or diffrent bootloader and thats why I am stuck? How can i fix this?
My process:
I went from cyanogenmod to a touchwiz rom. Decided to go back to stock. Flash using TWRP Bootloader and kernal from the first post (http://forum.xda-developers.com/showthread.php?p=31802808). Then used odin to flash root injected g1 image. Now it hangs at the samsung logo, i cant get into recovery (pretty sure i flash over that), but i can get into download mode.
Click to expand...
Click to collapse
You might want to try flashing the "UCALH9 Kernel, Modem and TWRP Recovery Tar" from here with Odin. Make sure the "Auto Reboot" switch is not checked in Odin. When the flash is done, disconnect from the computer, pull the battery, then boot into recovery by holding Home and Vol Up and then pressing Power. Hold Home and Vol Up until you see the Samsung logo and some little blue text, then release. If you can get there, do a factory reset, then you should be able to flash the rooted LG1 image with Odin. Or, you can flash LH9 from the same thread or from here by flashing the Bootloader, ROM and Kernel files from the PIECES section (in that order) before rebooting.
Wipe cache and devlik and it will fix your issue. I had the same problem before.
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
chemisch said:
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
Click to expand...
Click to collapse
I had the same issue a few days ago and ultimately fixed it by doing factory reset, wipe cache, dalvik, etc.. I had forgotten to do it after flashing back to stock. You were probably smarter than me and did those things BUT if you didn't it's usually something simple like I did to fix the problem.
\Hey hunter you prolly figured it out already but I was in the same situation today going from AOKP to stock rooted.. what fixed it for me was after flashing, booting into the stock recovery (HOME + VOL UP + POWER) and doing a wipe data and wipe cache. Then going back to download mode and reflashing the stock rooted tar. not sure if reflashing was necessary but it worked like a charm after that.
well as i wasnt in clockwork i was pushing a stock rom through odin i don't beleive i iclearly the cache that could of helped but nonetheless im stuck and i can't get into cwm or regular recovery etc
chemisch said:
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
Click to expand...
Click to collapse
My suggestions including flashing a bunch of stuff. Which one caused the error? The flash of the modem/kernel/recovery tar file in Odin or the subsequent flashing of the zips in recovery? What was the exact error you received?
It's pretty hard to help you if you don't provide all the details.
I flashed a custom six months ago and all was good until I tried to flash the new version of the rom.
When I go into recovery I get a black screen with the backlight on.
When I press the capacitive buttons I feel the phone vibrate I then connect it to my pc and can send commands to the like reboot phone, reboot bootloader etc.
I have tried flashing the latest versions of 2 custom recoverys, tried clearing the cache using fboot, tried flashing the rom through goomanager and it gets suck at recovery and nothing is working.
When I flash the recovery image is says image flashed successfully.
I have downloaded the ruu for the phone so might have to flash the ruu as it should not need to use the recovery.
Please help I need to flash a custom rom or go back to stock.
I have a real frustrating problem with my Canadian Rogers Note 3. I'm rooted and running CM11, but I was looking for a ROM that might be more stable than the nightly builds. I wanted to try a TW-based ROM so I downloaded BobCat, JediElite, and FireNote ROMs.
I copied the ROMs to the SD card, booted into CWM Recovery and tried flashing one of them (don't remember which). The installation seemed to go fine, no error messages or warnings. But when I finished and rebooted the phone just stopped at the Note 3 boot screen. No boot animation, no loading, nothing.
I went back to CWM Recovery, tried the other two ROMs, and got the exact same results. Then I tried flashing the stock Rogers Note 3 ROM. CWM refused to flash it and spat out some garbage about a corrupt zip file (re-downloaded it with the same results). I eventually gave up and restored the CM11 image I'd backed up.
At this point I began to reason maybe CWM wasn't suited to installing TW ROMs, so I decided I needed TWRP instead. Goog.Im and TWRP manager both refused to install TWRP however. So I dropped the TWRP Recovery zip on my SD card and tried flashing it using CWM.
Here’s where it gets really freaky. When my phone rebooted I got a "recovery booting" message, but the recovery never loaded. The screen just froze at the Note 3 logo. If I pulled the battery the phone would again display "recovery booting" and sit there endlessly. The only way I could break the cycle was booting to Download Mode, then exiting so it enters a normal ROM boot.
I let the phone boot up fully and then opened ROM Manager. It showed TWO recoveries installed, one CWM and one TWRP, apparently side by side. Is this even possible???
So anyway, I went back to playing around between ROM Manger, Goo.Im, and TWRP Manger, trying to re-flash it to either CWM or TWRP, but not both. Nothing worked; every time I tried booting to recovery the system would hang at the “recovery booting” message.
I eventually tired of this and decided to get out Odin. I flashed TWRP Recovery successfully (according to Odin), but it still won’t launch. I then tried flashing CWM Recovery with the same results.
So completely out of options, I tried flashing the stock Samsung Recovery. It boots just fine. So I try again flashing the custom recoveries, but they still refuse to launch. Each time I have to reinstall Samsung Recovery.
And that’s where I am currently: I have a (badly) working CM11 nightly ROM on my phone. I have the stock Samsung Recovery installed. I’m afraid to try flashing any zips using Samsung Recovery because my backup image was created using CWM, and if I can’t get CWM recovery to work I won’t be able to restore the backup.
Have I broken some law of the universe by trying to go from CWM to TWRP? Would TWRP work better with TouchWiz ROMs? And can I even install TouchWiz ROMs after hacking my phone to CM11 nightlies? Lastly, how can I get this $#@& Samsung Recovery off my beautiful phone and install a working custom recovery?
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?
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
The_mamba said:
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
Click to expand...
Click to collapse
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Stevica Smederevac said:
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Click to expand...
Click to collapse
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
The_mamba said:
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
Click to expand...
Click to collapse
No need, newest will work with MM