Develop Bugs

[Q] messed flashcreen no bootescreen when flashing any rom

whenever i flash any custom rom whether the rom version is android 4.2/4.1.2/4.1.1 , my phone has no bootscreen and a messed up flashscreen when it sais (samsung galaxy note 2 GT-N7100) but then after waiting the appropriate time, the rom works fine but same problem when rebooting... i attached the flashcreen and how it looks like, i have no idea why this happens.i just press the lockscreen after rebooting and waiting and the rom works normally. i rooted using the Galaxy Note II Toolkit v3.0.0 GSM. i first experienced this right after flashing and entering recovery(cmw) but twrp worked fine then, now any rom i flash i experience this,
Is anyone faceing a similar problem or can help in anyway ?
I am using Samsung Galaxy note II GT-N7100

possible hardware issue.. have you tried reflashing the original firmware?

yes it works fine
agent_so said:
possible hardware issue.. have you tried reflashing the original firmware?
Click to expand...
Click to collapse
yes both screens work fine on stock rom after restoring ...so i dont think its an hardware issue

[Q] Broke my modem

So I made the ultimate noob mistake of not making sure the ROM I flashed was made specifically for my model of Note, which is i317. I downloaded and flashed the International models version. Once I got into the phone, I noticed I no longer had cellular connectivity. When I tried to go into the network settings, it tells me there is no SIM card detected.
I restored from my backup, but the issue persists. I am currently downloading and preparing to flash the correct version in hopes that it will fix this issue.
Has anyone else had to deal with this issue? Did flashing the correct rom fix it? Is my only option to go back to stock, or will that even work?
Any help is greatly appreciated. Thanks.

Fixed
Fixed with the modem recovery rom found here.
http://forum.xda-developers.com/showthread.php?t=2484338
Still haven't gotten the proper DN3 v5 ROM to work. Gets stuck at the SAMSUNG boot logo.

scmc said:
Fixed with the modem recovery rom found here.
http://forum.xda-developers.com/showthread.php?t=2484338
Still haven't gotten the proper DN3 v5 ROM to work. Gets stuck at the SAMSUNG boot logo.
Click to expand...
Click to collapse
Same here on DN3 v5. I'd like to give it a try, but I get stuck at the SAMSUNG logo too. I have tried SlimKat and I like it alot... If you learn the trick to DN3, please let me know! Thank you and good luck!

Cannot downgrade to 4.2.2 (gt p5210), what should I do?

Hi,
After upgrading OTA to kitkat (australia version) one of my favourite apps stopped working and caused constant reboots to my tab3.
I tried to downgrade with odin to the stock 4.2.2 (auatralia, from sammobile) but I could not. After flshing, the "samsung galaxy tab 3" logo appeared but the tab never turned on, it kept rebooting and rebooting from ours. I tried the same with other 4.2.2 roms with the same results. However I was able to flash any 4.4.2 rom from sammobile.
After that I tried to flash some 4.2.2 roms using twrp and bindroid, I had the same rebooting problems. However, with twrp I can flash 4.4.2 based roms as pimpdroid.
So, I do not why, apparently my tab only accepts 4.4.2 roms... Any suggestions about what should I do to go back to 4.2.2?
Thanks for your time,
A.

Bootloop in P5210
Hi I'm trying to get back to 4.4.2 to 4.2.2 works because although there are excellent applications like Facebook that are causing me problems. But in trying to make the retoroceso as I usually do with ODIN stock form and I was left in a permanent reboot and does not pass the SAMSUNG logo .... solution? Thank you!:crying:

@planinsky, Have you tried a firmware for another region in the world? I live in the United States but have found firmware for the United Kingdom or Canada works best when I flash. There should not be any difference in the firmwares except for regionalization, but it seems some work and some don't work for me. Regional settings can always be tweaked in the Settings panel after install. Do you have a nandroid backup made in TWRP? Those usually always recover a device. I too had a problem having anything flash when I first started making my rom. 3 weeks I had a device that would not boot. So it is recoverable. Odin will save your device.
@planinsky and @MDCB try to download this firmware from Sammobile. This is for the UK 4.2.2 version. http://www.sammobile.com/firmwares/download/28243/P5210XXUANB4_P5210BTUANB1_BTU.zip/
I usually use ODIN 3.07. I assume you know the following but just in case. Remember to flash it in the PDA slot. Only have "Auto reboot" and "F. Reset time" checked.
Using Odin will reset anything the 4.4.2 builds have done to the partitions. If it doesn't work, I can only suggest to try again. When it comes to flashing, sometimes the TWRP builds for our device can be a little goofy in writing. I have not investigated completely. In the 4.2.2 roms I have flashed pimpdroid and cagrom, they seem to flash good with Moonbutt77's philz recovery with very little problems. I however cannot get 4.4 roms to flash in philz but only in TWRP. So sometimes the recovery itself seems to have a problem with the android version, or so it seems.
The above is only written from my experience on this device and cannot predict every situation.
Good luck.

Hi! Thanks for the tips.
Ufortunately, I have already tried 4.2.2 ROMS from different countries (from Sammobile): Australia (the original country of my Tab), UK, New Zealand, Belgium and US. None of them worked. I'm still downloading other ROMS but I'm startin to lose the faith... The custom ROMS I have tried, neither work and get into the bootloop.
The backup I have from TWRP is from a 4.4.2 so it's not a solution.
On the other hand, I can flash almost any 4.4.2 ROM with odin and/or TWRP. So I'm afraid I'll soon give up and I will accept that my Tab will not longer run the app I loved (Movistar TV)... Hopefully with the arrival of lollypop the developers will update the app and the bug which causes the crash will disappear.

[Q] Note 2 shows t0ltetmo instead of t03g when flashing

So i tried flashing the pa_n7100-4.6-BETA4-20141009 rom as well as cm-11-20141008-SNAPSHOT-M11-n7100 onto what i'm sure is my note 2 n7100. While installing, at the start, the recovery says the rom is meant for a t03g while mine's a t0ltetmo. There is no way in hell my phone's a t-mobile : firstly , i live in india, a country free from the tyranny of t-mobile, and secondly, it says gt-n7100 on bootup from stock rom. I tried removing the version checking part in the rom, hoping to force install it anyway, but it just popped up 'error'. Then i tried flashing one of the few roms available for the t0ltetmo, the Slim-t0ltetmo-4.4.4.build.8.0-OFFICIAL-6945 rom. After a successful installation, it was just stuck on the boot screen. I'm not saying i dont like the shiny slimkat logo twirling around, but i would eventually like to use my phone too. I'm now back to my stock rom after flashing my friend's n7100 recovery image, and then factory resetting, because cwm 'lost' my backup file. Anyway, i'd love to have the new 5.0 cm12 alpha, but i'm apprehensive now. Help me? :crying:

[Q]

Hello XDA. Currently I own a Samsung Galaxy S3 SGH T999 from T-Mobile. As soon as I got it I had my cousin root it for me. For a while I had no issues flashing ROMS. The ROM I am using is AVATAR 4.2.2. I am noticing now that when I go to flash a new ROM it stays in the boot logo screen. It does that with just about every ROM I try to flash. I went back to my cousin and he updated TWRP for me. To this day I am still having the same problem. I am not sure what is going on please help me.

ghostgaming said:
Hello XDA. Currently I own a Samsung Galaxy S3 SGH T999 from T-Mobile. As soon as I got it I had my cousin root it for me. For a while I had no issues flashing ROMS. The ROM I am using is AVATAR 4.2.2. I am noticing now that when I go to flash a new ROM it stays in the boot logo screen. It does that with just about every ROM I try to flash. I went back to my cousin and he updated TWRP for me. To this day I am still having the same problem. I am not sure what is going on please help me.
Click to expand...
Click to collapse
Be aware that you need to completely wipe your phone when switching between ROMs (does not apply if you are upgrading to a newer version of the same ROM). Flashing over can cause issues like yours.