Develop Bugs

Stuck at boot ani screen on all AOSP roms

I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.

I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta

jinxzn said:
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
Click to expand...
Click to collapse
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..

Zachinater said:
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did flashed SOAPKernel along with aosp roms.
wase4711 said:
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Click to expand...
Click to collapse
I flashed BeanStalk, SlimBean, CyanogenMod 10.1 official nightlies, FSC rom, and IllusionRom.
I have CWM Philz_Touch 5.07.1. Every time install a new rom, I wiped Caches + Data / Factory Reset 2x.
I flashed rom only, then flashed rom and GAPPS, those 2 didn't work, I even tried rom w/ SOAPKernel and still didn't work.

ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..

wase4711 said:
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
Click to expand...
Click to collapse
Switched to TWRP, and did all the wipes, install rom and GAAPS. Same thing.
Planning to flash stock rom, and redo all the root/recovery procedures all over again. Do you think I should do that?

it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...

wase4711 said:
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
Click to expand...
Click to collapse
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.

jinxzn said:
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
Click to expand...
Click to collapse
good luck, and post back if you get it working properly

flashed stock rom and rooted and installed boot recovery, after all that, it's still not let me install any AOSP roms. Really don't why I can only flash TW roms but not AOSP roms.

[Q] Rom Question

I'm having issues flashing multiple roms of the 4.x.x Roms. The only rom so far I have been able to install and actually run on my phone is TweakWiz V2. I have tried many other roms and they just stay in a boot loop screen. Examples are with the Avatar rom it just stays on the mask an keeps going and going. I have tried CyanogenMod/Cyan Kang an it just stays on the Circle with the bar going around on the inside.
I am running the TWRP Touch Recovery. I also have the latest Radio update and everything else is updated on my phone.
I also let the install itself run for 10+ minutes everytime. But all the roms I try they keep doing the exact same thing and staying in a boot loop.
Can anyone give me any tips or suggestions to maybe something I could do to use another rom or maybe even a suggestion to something I may have overlooked.. Any help is appreciated. Thank you.
An if you need me to give any other information let me know an I will provide.

1. what recovery version not just the name ?? 2.steps you are doing to flash 3. steps you are doing after you flash

krazierokz said:
1. what recovery version not just the name ?? 2.steps you are doing to flash 3. steps you are doing after you flash
Click to expand...
Click to collapse
1.Im using the latest TWRP.
2. Wiping System, Cache, Dvalik or whatever. I wipe everything in the usual instructions. And I make a backup of previous ROM. Flash the ROM then the G-Apps.
3. After I flash I let the ROM run its course an I wait from 15-45 mins for the ROM to load if it doesnt I switch back to TweakWiz or try another.
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app

try using this recovery since the recovery you are using is the latest one and technically for 4.3 ROMs, give this a shot http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.5.0.0-hercules.tar its the same recovery but lower . the steps you clarified seem very proper but your recovery may be at fault crossing fingers try flashing that recovery through odin or download the zip from the same website and report back after trying to flash again

Are you sure you are wiping DATA also?
You will need to do this, if you are flashing a 4.2 or 4.3 ROM, then you will also want to wipe the pre-load. Then flash the rom, and gapps.
Use the newest TWRP 2.6.1.0 to flash anything, don't need an older recovery to flash older ROM's.

idtheftvictim said:
Are you sure you are wiping DATA also?
You will need to do this, if you are flashing a 4.2 or 4.3 ROM, then you will also want to wipe the pre-load. Then flash the rom, and gapps.
Use the newest TWRP 2.6.1.0 to flash anything, don't need an older recovery to flash older ROM's.
Click to expand...
Click to collapse
Is there a option I'm not deleting ?
Because I've been flashing ROMS on different phones an I have never had any issues before. I was using ICS an GB etc before an just recently decided to upgrade an use the JB (I think that's the name.) on my phone.

[Q] Can't install new ROMs

So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.

You need to give more info on the error
Sent from my SGH-M919 using Tapatalk

serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.

Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app

spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.

Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?

Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.

Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.

Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?

So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.

Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.

To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.

Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.

Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3

I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?

Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something

Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement

GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)

My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.

You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.

Phone automatic restart error

I'm having an issue. Since I've updated to Kitkat and wicked kk, my phone randomly reboots.
I've tried factory reset, clear cache, clear dalvik.
I've even odin the stock rom and started over.
I've formatted the internal and sdcard, and changed sims.
I've also tried changing the Kernel
Someone in another thread stated it may be a bad download, so I downloaded again, which also didn't work.
I'm out of ideas, but it's still happening. Any idea how to fix?
I'm on Wicked rom

re: external sdcard
link1227 said:
I'm having an issue. Since I've updated to Kitkat and wicked kk, my phone randomly reboots.
I've tried factory reset, clear cache, clear dalvik.
I've even odin the stock rom and started over.
I've formatted the internal and sdcard, and changed sims.
I've also tried changing the Kernel
Someone in another thread stated it may be a bad download, so I downloaded again, which also didn't work.
I'm out of ideas, but it's still happening. Any idea how to fix?
I'm on Wicked rom
Click to expand...
Click to collapse
Have you tried to remove the external sdcard from the phone before
odin flashing the stock Samsung N900T 4.4.2 kitkat firmware/rom and
before rooting the phone and or flashing custom recovery?
(only flash the stock firmware for this test and nothing else.)
If you have not tried that, give it a try and remember to leave the
external sdcard out of the phone for a few hours after oding flashing
the stock rom to see if it still has the rebooting issue.
If your phone no longer reboots itself after trying this it means you
have either a defective external sdcard or you need to format the
sdcard using fat32 format.
Good luck!

Misterjunky said:
Have you tried to remove the external sdcard from the phone before
odin flashing the stock Samsung N900T 4.4.2 kitkat firmware/rom and
before rooting the phone and or flashing custom recovery?
(only flash the stock firmware for this test and nothing else.)
If you have not tried that, give it a try and remember to leave the
external sdcard out of the phone for a few hours after oding flashing
the stock rom to see if it still has the rebooting issue.
If your phone no longer reboots itself after trying this it means you
have either a defective external sdcard or you need to format the
sdcard using fat32 format.
Good luck!
Click to expand...
Click to collapse
thank you.
I've actually tried that too, but still get the error. I never had this problem on the last rom version (4.3)
I don't know. It's a weird error

Anymore ideas?
Using tapatalk.... can't rep/thank

What kernel and governor are you using?, intellidemand in previous builds was known to cause random reboots. Flash a newer kernel, I recommend leankernel 2.5.1

icenight89 said:
What kernel and governor are you using?, intellidemand in previous builds was known to cause random reboots. Flash a newer kernel, I recommend leankernel 2.5.1
Click to expand...
Click to collapse
I'm using the standard default kk kernel
What's governor?
Using tapatalk.... can't rep/thank

Flash a custom recovery and flash the efs-bootloop fix thats available in another thread, it basically wipes your efs.
If that doesn't resolve your issue, you may have to warranty the phone...

link1227 said:
I've even odin the stock rom and started over.
Click to expand...
Click to collapse
If you leave everything stock does it still randomly reboot?
Frank

icenight89 said:
Flash a custom recovery and flash the efs-bootloop fix thats available in another thread, it basically wipes your efs.
If that doesn't resolve your issue, you may have to warranty the phone...
Click to expand...
Click to collapse
Ok will try. Thanks
Frank Westlake said:
If you leave everything stock does it still randomly reboot?
Frank
Click to expand...
Click to collapse
I'm not sure

Frank Westlake said:
If you leave everything stock does it still randomly reboot?
Frank
Click to expand...
Click to collapse
Ok, I odined a stock rom, and it is still doing it.
I'm pretty sure it's something related to the system partition. Right before it reboots, every system app freezes. I can't use the phone app, settings, wifi stops working, etc.
Oddly though, when I flashed the odin rom, none of the system settings changed. It still has my system the way it was. I tried the format partition in recovery, and that didn't work either. Is there any way to format the /system? as I think that may be the issue.

Best way to currently install marshmallow after failed attempts

Hi, after trying to use philz recovery to flash a ROM on to my device I got what I think was called a soft brick where I had to download and flash the stock ROM.
My device (GT-N7100) is now not rooted again and back to square one. Any problems I come across occur from using old tutorials with dead links so if someone could recommend a tutorial to install a custom rom like 5.1 I would be very grateful. Thanks
EDIT. I found this guide on youtube http://mytechtube.in/samsung-galaxy-note2-rooting.html + http://mytechtube.in/samsung-galaxy-note2-6-0-1.html . Does it look like it will work?

Flash twrp using Odin, then flash a custom rom via twrp.

Root your phone first. Flash recovery like twrp and install custom rom like Resurrection remix the ROM is stable most of the things works and good as daily driver.
Sent from my GT-N7100 using Tapatalk

Root is not required to flash TWRP. TWRP can be flashed directly to the phone using Odin.

1life2love4 said:
Root your phone first. Flash recovery like twrp and install custom rom like Resurrection remix the ROM is stable most of the things works and good as daily driver.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
audit13 said:
Flash twrp using Odin, then flash a custom rom via twrp.
Click to expand...
Click to collapse
Should I just use the latest version of TWRP direct from their website https://twrp.me/devices/samsunggalaxynote2n7100.html ?
I think my phone code name is t03g how can i confirm?
Thanks
EDIT. Just installed TWRP :good: now on to picking a good ROM. will have a look at the ressurection one too.
To install apps that require root should O root it now or do some ROMS root it for me?
Sorry for the amount of questions

The easiest way to install twrp would be to flash the tar version using Odin.

audit13 said:
The easiest way to install twrp would be to flash the tar version using Odin.
Click to expand...
Click to collapse
Just did as you suggested thanks. To install apps that require root should I root it now or do some ROMS root it for me?

Most custom Roms come prerooted. If the rom is not rooted, you can flash supersu.zip from recovery.
Root can be enabled on cm13 under developer options in settings.

audit13 said:
Most custom Roms come prerooted. If the rom is not rooted, you can flash supersu.zip from recovery.
Root can be enabled on cm13 under developer options in settings.
Click to expand...
Click to collapse
Thanks for the info. I've watched some videos of cm13 and I so far thats what im going with. Will look for a youtube video to help with installing it.

To install, download cm13 to an sad card, wipe cache, wipe system, wipe data, install cm13 zip from ad card, reboot.
Cm13 does not come with Google apps (gapps) so you'll have to decide which version you want.

audit13 said:
To install, download cm13 to an sad card, wipe cache, wipe system, wipe data, install cm13 zip from ad card, reboot.
Cm13 does not come with Google apps (gapps) so you'll have to decide which version you want.
Click to expand...
Click to collapse
I didnt realise that before. Could I for example install any of the GAPPS from this link https://devs-lab.com/android-gapps-download.html " full google apps" or pico google apps ?
From whatI gather GAPPS are installed straight after rom install before root though is this the same in cm13?

Flash CM13, flash Gapps, reboot.
I like open gapps frome here: http://opengapps.org/

audit13 said:
Flash CM13, flash Gapps, reboot.
I like open gapps frome here: http://opengapps.org/
Click to expand...
Click to collapse
Perfect Im going to try that in the next hour. I like the look of aroma. For platform would I select ARM and android 6.0?
EDIT. Found the answer it was ARM.

Arm as I believe your phone has a Qualcomm processor.

audit13 said:
Arm as I believe your phone has a Qualcomm processor.
Click to expand...
Click to collapse
Yeah was ARM as I just installed CM13. Thank you seriously headig your way.

Hopefully, everything works.
Now that you have twrp on your phone, you can use it to create a backup of everything in your phone, including time efs folder. Save the efs folder in a safe place in case you need to restore it to the phone at a later date.
After making a backup, you can flash other Roms and you can return to cm13 by restoring your backup.

Just getting familiar with it. Thanks for the help.
Do you know if there's settings to turn screen on during during calls because it works with the front sensor and that sensor is broke on my phone?
Sent from my GT-N7100 using Tapatalk

You could try disabling the proximity sensor in the phone so the phone screen doesn't blank out during a call.

Got it sorted using an app from the play store.
Sent from my GT-N7100 using Tapatalk

audit13 said:
You could try disabling the proximity sensor in the phone so the phone screen doesn't blank out during a call.
Click to expand...
Click to collapse
Hi, phones been running great until yesterday when it started telling me the disk space was nearly full(via es filee xplorer). It then turned off a few times and i turned it on again. The phone would shut off if I tried to do anything like launch the camera app. It now bootloops when i try to turn it on.
I have tried wiping dalvic cache, factory reset, recover from a recovery point i made when i installed the rom and reinstalling the custom rom like I did the first time.
The phone did once go into a boot animation of the old boot screen(02 animation), another time it started the miui boot logo but went back to the normal samsung galaxy note 2 boot loop.
Any suggestions on how i could get it running again? Thanks!