Stuck on Boot loop 6.0 - X Style (Pure) Q&A, Help & Troubleshooting

Im on the latest Februarys version. Bootloader is unlocked. Flashed twrp-3.0.2-0-clark then this Is where I think I muffed up. installed SU 2.76. Then read somewhere to reflash 2.62. Right now im stuck on the blue M with circles. I need some help. I don't know where or what to do next. Ive read as much as I can but to no avail. If some one can help me I would appreciate and input.

StankFiss said:
Im on the latest Februarys version. Bootloader is unlocked. Flashed twrp-3.0.2-0-clark then this Is where I think I muffed up. installed SU 2.76. Then read somewhere to reflash 2.62. Right now im stuck on the blue M with circles. I need some help. I don't know where or what to do next. Ive read as much as I can but to no avail. If some one can help me I would appreciate and input.
Click to expand...
Click to collapse
Did you try wiping cahe and dalvik cache by rebooting into TWRP?
Do you have nandroid backup of your original ROM? if you have the backup then restore it.
Always make nandroid backup using TWRP before flashing anything like SUperSU / Viperfor andoird or any other custom kernel.
Thanks

Unfortunately I don't have a backup. in my excitement I proceeded. I did wipe dalvik cache. There has to be way out of this. But my knowledge is limited with android.. Im use to the old days of using RSD Lite to install image again. Is there a way to that:?

Well I done it now. It says no OS. When it boots it stuck on bootloader has been unlocked screen. Someone please help me. To restore to stock. Thanks in advance.

Nevermind figured it out myself. Any1 new to this and did what I did. go here http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833

Related

Need Help with looping device....

Hello!
I was on the HKTW build as of yesterday. I have Tenfar's recovery and CWM installed too.
I attempted to install Kennith Penn's Alien Rom V2 and it seems like its flashing no problem... However, I get stuck in a boot loop.
I tried restoring to a previous back up , and that loops now too
So, I attempted to flash 2.3.4 Fruit cakes ( http://www.multiupload.com/U1EOJVAKPO ) and it seems that it is flashing it properly, because I got back my stock "AT&T" boot logo (from the factory) but, that goes into a boot loop too...
Can anyone please help point me in the correct direction of getting my device to boot the rom/ image properly? Is there a setting I need to ensure is checked on CWM (like mounts or something?) ... at this point, I cant even boot into Tenfars recovery... just CWM...
This sucks!
Thanks in advance for any help!!!
ssmr2t said:
Hello!
I was on the HKTW build as of yesterday. I have Tenfar's recovery and CWM installed too.
I attempted to install Kennith Penn's Alien Rom V2 and it seems like its flashing no problem... However, I get stuck in a boot loop.
I tried restoring to a previous back up , and that loops now too
So, I attempted to flash 2.3.4 Fruit cakes ( http://www.multiupload.com/U1EOJVAKPO ) and it seems that it is flashing it properly, because I got back my stock "AT&T" boot logo (from the factory) but, that goes into a boot loop too...
Can anyone please help point me in the correct direction of getting my device to boot the rom/ image properly? Is there a setting I need to ensure is checked on CWM (like mounts or something?) ... at this point, I cant even boot into Tenfars recovery... just CWM...
This sucks!
Thanks in advance for any help!!!
Click to expand...
Click to collapse
Bootloops in 99.9% cases means that you need to wipe.
1. Go back into CWM, wipe data / factory reset, wipe cache, go to advanced and wipe dalvik cache.
2. Flash the desired rom.
3. Go into CWM again and do all the wipes again.
And you should boot no probs.
p.s. these 3 steps should your blue print to installing any rom btw. even you want to backup apps - use TB.
thank you for your help....ive actually dome all of that and still no go
ssmr2t said:
thank you for your help....ive actually dome all of that and still no go
Click to expand...
Click to collapse
Have you tried wiping via fastboot?
moto-fastboot -w
p.s. do you have the latest CWM recovery? there can be problems if you arent using the latest one.
xploited said:
Have you tried wiping via fastboot?
moto-fastboot -w
p.s. do you have the latest CWM recovery? there can be problems if you arent using the latest one.
Click to expand...
Click to collapse
+1. i was having the same problem not too long ago and that fixed my problem.

SOLVED: Bricked D2 & can't boot into CWM - Using a Mac.

Ok, here's the deal. Loaded Liberty v3 on my D2 and it booted just fine. However, after installing an update, I was stuck in loop mode. Booted into CWM and installed a new ROM called Steel after wiping my cache and my data. Now, I'm stuck at the Moto Logo splash screen. CWM no longer loads and the only thing I can access is the Android system recovery.
That said, I have ADB installed on my Mac. Wanted to flash another ROM so I've fired ADB up but it can't connect to my phone in the recovery system.
Really need some help here... this is my only phone as I don't have a land line any longer. Keep in mind, I'm not a noob but I'm not a programmer either. Thank you, in advance, for any help you can give!
Did you wipe cache or wipe data from stock recovery?
Don't you need to be in bootloader for ADB?
HI there... I'd already done all that. However, I was still stuck. That said, I DID find a fix... and it's good for Winblows, Mac and Linux computers. http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html It was simple and worked flawlessly!

My backups are not working....

Ok so first off I was successful in rooting the phone, installing twrp rec., flashing loki files, and then flashing wicked rom with ktweaker tw kernel. I made a backup of the stock rooted rom before wicked was flashed. Then my troubles started when I wanted to go back to my stock backup. The rom booted but has serious issues like black screen with only status bar working and then eventually freezing. I also made a backup of a working wicked and tried restoring that but then I just get stuck in boot loop. Any help would be greatly appreciated.
what twrp version
did you wipe all before restoring
you could try to install Phils cwm recovery, folks say it works great and will restore twrp backups also
thesystem90 said:
Ok so first off I was successful in rooting the phone, installing twrp rec., flashing loki files, and then flashing wicked rom with ktweaker tw kernel. I made a backup of the stock rooted rom before wicked was flashed. Then my troubles started when I wanted to go back to my stock backup. The rom booted but has serious issues like black screen with only status bar working and then eventually freezing. I also made a backup of a working wicked and tried restoring that but then I just get stuck in boot loop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Follow full wipe procedures, have the same recovery you made the backup with, and try again.
rugmankc said:
what twrp version
did you wipe all before restoring
you could try to install Phils cwm recovery, folks say it works great and will restore twrp backups also
Click to expand...
Click to collapse
I flashed the stock firm. Soft brick averted. Did the same goo manager recovery method, but now i'm thinking of flashing that cwm as ppl have reported the same nandroid backup issues with twrp. My version is 2.5.0.2. I will keep trying to get twrp for a while with others users till i get sick of it (semi twrp fan). Any further advice would be cool. Oh and I did a factory twrp wipe the first time this problem occurred.
I wipe data caches and system before flashing. No more advice. Had newest TWRP hang on Team Win screen. Several manual reboots into recovery till it worked. Maybe I better do restore to see if it works.
Sent From My 32gb Samsung Galaxy S4 Running Tapatalk 4 Beta

"Camera Failed" After Restoring in TWRP

I restored a backup from a few weeks ago after trying out a marshmallow based ROM (I was on lollipop prior) and after the restore process, my old phone interface came up and it was as if I never flashed the newer rom at all as expected, however, now my camera does not work at all and I could use a hand figuring out how to resolve this issue.
Things I've tried:
- Rebooting (obviously)
- Clearing cache/dalvik from recovery
- Clearing the camera app's data and cache
When I restored my backup, I chose not to restore 'boot' and 'recovery' because while I was on the marshmallow rom, I unlocked my phone's bootloader and installed TWRP (as opposed to using SafeStrap) and I didn't want to lose it.
Samsung Galaxy S5 GM-900V
Android 5.0
Baseband: G900VVRU2BOG5
Build: OptimalRom 15-5
Marshmallow rom I referenced: Norma_Note5Port_V3.4_VZW
Any advice?
So I've formatted dalvik/cache/data/internal storage and installed the older rom (OptimalRom 15-2 ) again. Did the initial setup and the camera still didn't work. I tried reflashing a known-good kernel that's compatible with this rom and that didn't seem to help.
Can anyone point me in the right direction on how to resolve this? Something must have been flashed when I installed the Note 5 rom that wasn't when I went back to OptimalRom. I just don't know what. I'll keep searching and experimenting. Thankfully I have a real recovery menu now so softbricking isn't as big of a deal.
GoTeamScotch said:
So I've formatted dalvik/cache/data/internal storage and installed the older rom (OptimalRom 15-2 ) again. Did the initial setup and the camera still didn't work. I tried reflashing a known-good kernel that's compatible with this rom and that didn't seem to help.
Can anyone point me in the right direction on how to resolve this? Something must have been flashed when I installed the Note 5 rom that wasn't when I went back to OptimalRom. I just don't know what. I'll keep searching and experimenting. Thankfully I have a real recovery menu now so softbricking isn't as big of a deal.
Click to expand...
Click to collapse
Since you have TWRP now, try doing a complete and clean wipe. Go into recovery, Wipe, Advance Wipe and select Cache, Dalvik cache, Data and Internal and swipe. Then back out to Wipe and swipe twice on the slider and install the OptimalRom of choice. then install the PB1 firmware NO Bootloader. If you still have an issue then try with the ROM kernal and flash it which I think it'sthe OG5 Kernal No Bootloader. The reason for doing this particular wipe is to get anything that may be left over from a previous ROM. This is my preference and habit from when I started running ROM's on my S3. Beanstown103 and others had recommended doing this in TWRP and haven't had any issues or problems by doing this since. Hope this may help
Thanks al50. I will give that a shot. Sorry but I'm not familiar with "PB1 firmware". what are you referencing there?
GoTeamScotch said:
Thanks al50. I will give that a shot. Sorry but I'm not familiar with "PB1 firmware". what are you referencing there?
Click to expand...
Click to collapse
It's the version that your phone is on. Look in About Phone in settings. Anyways, that’s the Zip file you install after you install the ROM. But if you're already on PB1 then you don't have to worry about that. If you have issues with the camera then try flashing the No bootloader kernal that was made for that ROM, which I believe it was OG5 but check the OP to be for sure

Phone won't boot after flashing the SuperSU - SOLVED

Hi!
EDIT: Never mind, problem solved. Sorry.
I have finally decided to root my G900F (6.0.1). I flashed TWRP through Odin without problems, booted to TWRP to make it permanent, booted normally to check that all is well. After that I made a full backup in TWRP and flashed the BETA-SuperSU-v2.49.zip. After that, my phone no longer boots (hangs on the Galaxy S5 screen with a blue indicator LED).
I can still boot to TWRP.
How can I fix my phone? Please help. What did I do wrong?
I did try wiping the cache partition but nothing else.
Hopefully the solution does not require a full wipe.
EDIT: I see what I did wrong. I have accidentally flashed an old SuperSU.
Can I use a backup I made with a TWRP?
EDIT2: Luckily the restore did work! Will try to flash a more recent SuperSU.
flash it again but with latest version of supersu. It will work
Spawnknight said:
flash it again but with latest version of supersu. It will work
Click to expand...
Click to collapse
Yup, it did work beautifully. Lucky for me that I remembered to make a backup before rooting.

Categories

Resources