I'm currently downgraded my phone back to Jellybean (98.30.1) because the Kitkat firmware was a huge battery hog. I then decided to flash TWRP 2.6.3.0. Everything goes well, and then I flashed the pacman msm8960jbbl rom. After that, the phone no longer goes beyond the splash screen. I can still go to recovery and ap fastboot but no matter how many times i wipe my phone, the results always stay the same. The rom worked the first time, but the next few flashes were a trainwreck. Any idea how to fix this problem?
Try returning to stock ROM with RSD lite after that repeat the process to install the custom ROM
Sent From My Razr M (Bliss Stalk ROM) xt907
Related
I have been running AOKP on my Fascinate for a while now, but something wierd is going on with the device. After about a week of running AOKP (I tried the Hacksung ICS builds as well), the Fascinate begins to bootloop, so I have to go through and ODIN (cannot wipe and reflash because it continues to bootloop after wipe and reflash) then flash AOKP again. The process repeats itself after roughly a week of use.
I went back and Odin'ed to 2.3.5, but ever since then, I have been unable to install a working recovery on my device. I can flash the recovery fine (Voodoo, and CWM fixed for CM7), but when it boots up, and I try to flash a file, the screen goes black for a minute, then goes back to the recovery menu, like it is rebooting recovery. I've tried Heimdall and Odin.
Anyone got any tips? Am I just forgetting something?
Sent from my SCH-I500 using Tapatalk 2
in odin did you use the atlas.pit repartition file when you flashed back to stock?
if not then try that. also, which CWM are you trying to flash?
I know my fassy had problems with certain versions, but a 2.5.x version always worked for me no matter what happened to my phone.
This guide always worked for me.... http://forum.xda-developers.com/showthread.php?t=1238070
Hi all,
its been days I am using CM10 and it started to be choppy and randomly "fast reboot"ing so I decided to go back to CM7.2. The moment I flashed CM7.2 zip via recovery my phone was stuck in bootloops.
So I decided to downgrade to froyo rom (which I have previously used to downgrade my phone as well, http://forum.xda-developers.com/showthread.php?t=1037076)
After successfull flashing through RSD lite my phone is stuck in the motorola bootscreen for ever (not the bootloader but the OS boot screen)
Kindly suggest me if I am doing something wrong here :/ I cant get it resolved anyhow.
Thank you
Resolved: I downloaded the 3.4.2 177-003 UK rom and flashed it, wiped afterwards and it booted.
I unlocked my bootloader awhile back when the exploit first came to light and have been enjoying it mostly problem free since.
I've been using CWM with CM10.1 for the most part but the issues I was having with CM were finally getting to me so I thought I'd just try a debloated stock ROM, and thought it was a good time to try out TWRP while I was clearing everything out.
So I loaded up Matt's tool and flashed the stock ROM back (because for some reason my computer doesn't like to recognize CM over USB), no problems there. At the suggestion of the tool I also flashed the stock recovery (since I intended to flash TWRP I figured it was a good idea). Here's where my problem lies now: The phone boots fine back into stock ROM and I can get back into fastboot no problem but if I try to get into recovery (after flashing stock, CM or TWRP) I only get the opened up Android with the red triangle/exclamation.
Is there some step I need to take that I'm not?
I boot into fastboot and flash recovery (stock). Boot normally wait a couple min (skip setting up accounts, etc) then flash the custom recovery but I seem to end up back at the broken android every time.
EDIT: I might just be an idiot. I completely forgot to root the stock ROM before trying to put the custom recovery back.
Broken android is stock recovery...
Sent from my XT907 using Tapatalk 4
i root my device, i unlock the bootloader, i flash the cwm but when i try to flash a rom sometimes the process starts, but when i reboot the device the rom is still the earlier...
now i flash OSE ROM 4.3.1, but wifi doesn't work, so i try to flash stock clean rom BareBone, but the device after the reboot stays in red motorola logo...
i try to flash philz cwm, but resultless...
Return to stock using Matt's utility and start over.
Sent from my Nexus 7
I just got a N7. It came with stock 4.4.2 but I unlocked and flashed a few 4.4 ROMs to try out (Liquid, CM, OMNI). Anyway, I figured I might want to try a 4.3 ROM so I flashed one. It didn't boot. Went back and installed the 4.4 ROM and all was good. I thought maybe I needed to flash a 4.3 factory image first, so I did. I fastbooted (verb) everything in the JWR66Y directory and OMG it booted. Great, time to flash a ROM, right? Nope. Flashed CWM touch 6.0.4.3 again and it booted using the stock ROM/kernel but after I flashed a custom ROM, it just sits at the boot screen. The obvious answer here would be to have patience and wait. I have waited for 35+ minutes at the bootanimation screen with no sign of booting. This is on any 4.3 ROM I try. However, it will boot right up if I flash the stock JWR66Y system and boot images. What do you think, kernel related or am I missing something more obvious?