Develop Bugs

[Q] re-odexed rom stuck at htc logo

i re-odexed a rom with the help of the tutorial. but when i flash that rom it gets stuck at the htc logo screen while booting. what should i do?

daninantro said:
i re-odexed a rom with the help of the tutorial. but when i flash that rom it gets stuck at the htc logo screen while booting. what should i do?
Click to expand...
Click to collapse
which rom did you flash. Did you do the wipes?
You can pull your battery and go on the bootloader then recovery and flash the rom again or a different rom.
Remember to thanks if it helped =D

i flashed eintrin.frat's thing rom! i flashed the rom 3 times.. it is still not going pass the boot screen

daninantro said:
i flashed eintrin.frat's thing rom! i flashed the rom 3 times.. it is still not going pass the boot screen
Click to expand...
Click to collapse
then try another rom and see if the same problem occurs like cm7 or another sense

you need wipe cache，wipe data，also if the rom is 2.37，you need use the recovery5.028

striker280 said:
then try another rom and see if the same problem occurs like cm7 or another sense
Click to expand...
Click to collapse
ok, i'll try with another sense rom

question about 5.0.2

Ok was using 5.0.2 alpha. but had cell call drops so moved back to 4.4.4 CM11 rom rebooted after flashing... and now phone doesn't wanna boot back on its just black screen. if anyone has anyinfo how to repair would be great

Did you wipe cache, data, and Dalvik after installing cm11?

Yup i did a fresh clean, wiped everything and then installed cm11 and did a cache/dalvik after install, then put gapps and did a cache/dalvik again and rebooted
once rebooted the phone never turned on again

You mean your phone doesn't turn on at all?

nope must of bricked ive flashed roms lots of times and never had issues

What exactly did you flash?
No lights when you plug the phone into a charger or computer?

I flashed CM11 with ShiftKernal. and gapps and no theres nothing i get a detection on windows but its a hard brick thing its weird how going from 5.0.2 back to 4.4.4 would do this

I wouldn't think flashing cm11, gapps, and a kernel would brick the phone.
Excuse my ignorance but the shift kernel is for cm11 on the i747? Did you do flash or touch the bootloader?

audit13 said:
I wouldn't think flashing cm11, gapps, and a kernel would brick the phone.
Excuse my ignorance but the shift kernel is for cm11 on the i747? Did you do flash or touch the bootloader?
Click to expand...
Click to collapse
Agree with @audit13 here...
Isn't the shift kernel for AOSP KK ROMS on i777/959G?
Which version of shift kernel did you flash? If you flashed Shift-D2-SE.zip that's for lollipop...
If you flash CM11 and Gapps without flashing shift kernel, does it boot?
I went from CM11 nightly to 5.0.2 then back to CM11 without any issues last week.

nope inless flashing lollipop alpha changed the bootloader some how then. and ya the shift kernel is for i747 too

Is the kernel designed for cm11? I see a shift kernel in for Cyanide 5.02 but not sure if it is for cm11: http://forum.xda-developers.com/galaxy-s3-att/development/rom-cyanide-l-v1-android-5-0-2-t2980174
I doubt the ROM would have altered the bootloader as doing so would or could cause all sorts of problems for the end user.
Which 5.0 ROM did you flash?

magedx9 said:
nope inless flashing lollipop alpha changed the bootloader some how then. and ya the shift kernel is for i747 too
Click to expand...
Click to collapse
Ahh.. didn't know they had one for i747.
Depends on the ROM but usually doesn't touch bootloader/baseband...
Can you get into download/recovery mode?

well my bad i flashed s2 shift kernel. and hard bricked my device

Maybe this de-brick thread will help: http://forum.xda-developers.com/showthread.php?t=2549068

magedx9 said:
well my bad i flashed s2 shift kernel. and hard bricked my device
Click to expand...
Click to collapse
Can you get into download or recovery mode?
Volume down + home + power or Volume up + home + power? (with the phone off)

Nope i tryed the debrick its not good for 4.4

You had the 4.4.2 bootloader on your phone?
From my understanding the phone boots from an sdcard so a 4.3 debrick image may work. I'm just guessing as I don't have an s3.

Stuck on Samsung Galaxy Tab Pro boot screen.

Last night I successfully rooted my Samsung tab pro 10.1, and this morning I used Flashify to attempt to install CWM custom recovery, it said everything worked but now it won't boot past the screen mentioned in the title, any suggestions are most welcome!

Can you still get in recovery mode? (Volume UP + Home button + Power button while device is off)

Miniricho said:
Last night I successfully rooted my Samsung tab pro 10.1, and this morning I used Flashify to attempt to install CWM custom recovery, it said everything worked but now it won't boot past the screen mentioned in the title, any suggestions are most welcome!
Click to expand...
Click to collapse
Are you still having problems? You might try going back to stock and try again. I personally use flashify and Twrp

Well I was able to get into download mode and flash a recovery that worked thank god. I do not like stock though, any roms to recommend? Tried GraveD's rom but it freezes on the Samsung boot screen I'm afraid.

Miniricho said:
Well I was able to get into download mode and flash a recovery that worked thank god. I do not like stock though, any roms to recommend? Tried GraveD's rom but it freezes on the Samsung boot screen I'm afraid.
Click to expand...
Click to collapse
I have not yet found a rom that I have stuck with. CM 12 has been my favorite so far.

bricked after ofe + root

I did the ofe update, then the v kernel root, then twisted rom and now the phone seems pretty bricked. It will take a flash of anything 5.1.1 (of7 stock, and twisted thru twrp) but both result in booting to a black screen with the blue led pulsing.
this doesn't seem good.
i have tried every combination of kernel's and recoveries and roms available here and they all do the same thing.
it was running great for a few days until a reboot happened and its been a no boot since then.

mozot said:
I did the ofe update, then the v kernel root, then twisted rom and now the phone seems pretty bricked. It will take a flash of anything 5.1.1 (of7 stock, and twisted thru twrp) but both result in booting to a black screen with the blue led pulsing.
this doesn't seem good.
i have tried every combination of kernel's and recoveries and roms available here and they all do the same thing.
it was running great for a few days until a reboot happened and its been a no boot since then.
Click to expand...
Click to collapse
Probably need to use Odin and re flash stock 5.1.1 rom
http://www.androidexpertclub.com/ho...-to-official-android-lollipop-5-1-1-firmware/

bigmikehd2 said:
Probably need to use Odin and re flash stock 5.1.1 rom
http://www.androidexpertclub.com/ho...-to-official-android-lollipop-5-1-1-firmware/
Click to expand...
Click to collapse
i have the stock 5.1.1 that is available and have tried that, i think that means there are deeper problems.

Oh, well it seemed to me from your post that you only tried flashing through recovery. If you can't flash a stock rom through odin and download mode, you are probably bricked...

mozot said:
I did the ofe update, then the v kernel root, then twisted rom and now the phone seems pretty bricked. It will take a flash of anything 5.1.1 (of7 stock, and twisted thru twrp) but both result in booting to a black screen with the blue led pulsing.
this doesn't seem good.
i have tried every combination of kernel's and recoveries and roms available here and they all do the same thing.
it was running great for a few days until a reboot happened and its been a no boot since then.
Click to expand...
Click to collapse
The good news is if you can still flash and get into download mode it is not a brick. I would odin the tar as suggested, it should boot once that is done.
Make sure you're giving it enough time on the first boot as well, it takes awhile to build the caches on the first boot.

Flashing ROMS causes "bootloop" ?

I've been away from Samsung phones for a bit over a year now, so I may have just forgotten something simple, but on my Note 2, I have TWRP on it and when I flash a ROM and gapps in TWRP, everything is fine, I reboot, and it's in a boot loop kinda? The whole phone doen't continuously boot and boot and boot, but the ROM never boots, the bootanimation is just there, going along, forever. I've tried Liquidsmooth 4.0 & 3.1.
Am I missing something? I'd like to NOT run stock/stock rooted, as I was using my Note 2 for Vainglory but now it lags too much on stock and I need to run a custom rom that's fast, great battery life, and minimalistic.

does it stuck at the samsung logo? if yes, try to boot into recovery and wipe data and cache.
i sometime had that happen, when i odin to stock.

cfli1688c1 said:
does it stuck at the samsung logo? if yes, try to boot into recovery and wipe data and cache.
i sometime had that happen, when i odin to stock.
Click to expand...
Click to collapse
No, it boots into the rom but all it does is boot forever, it plays the boot animation non stop and never fully enters the rom

xBr4v3x said:
No, it boots into the rom but all it does is boot forever, it plays the boot animation non stop and never fully enters the rom
Click to expand...
Click to collapse
Keep away from TWRP on the Note 2, it is known to cause such problems. I did my self the experience.
Instead, use Philz recovery who do his job perfectly with all roms i tried until now.

zlazaar said:
Keep away from TWRP on the Note 2, it is known to cause such problems. I did my self the experience.
Instead, use Philz recovery who do his job perfectly with all roms i tried until now.
Click to expand...
Click to collapse
Still getting the same problem.
I've tried twrp& philz. No success.
Trying to use LiquidSmooth, and all I get to is the bootanimation, an infinite loop of it.