Develop Bugs

Help my phone is messed

I have a d2can with a d2att recovery and im on Telus network.
So I flashed a ported ROM (MSG CHUBZ) from a sprint s3 which I think is T999 or something, and now everytime I format data and factory reset. my phone calls immediately hang up and texts fail..
Help..?

Adizzzle said:
I have a d2can with a d2att recovery and im on Telus network.
So I flashed a ported ROM (MSG CHUBZ) from a sprint s3 which I think is T999 or something, and now everytime I format data and factory reset. my phone calls immediately hang up and texts fail..
Help..?
Click to expand...
Click to collapse
I flashed that ROM last night also...
Had that problem last night after restoring my paranoid android backup.
I did a full wipe. Cache, dalvik, system, factory reset and than restored my backup and it went away.
Something in that flash stuck around after a wipe. I was really freaked out last night. I never flash tw ROMs and that made me want to never again...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Adizzzle said:
I have a d2can with a d2att recovery and im on Telus network.
So I flashed a ported ROM (MSG CHUBZ) from a sprint s3 which I think is T999 or something, and now everytime I format data and factory reset. my phone calls immediately hang up and texts fail..
Help..?
Click to expand...
Click to collapse
Just flash a d2can rom. Should fix your problem. Ports are not always reliable and it may not "like" your phones hardware.

aybarrap1 said:
Just flash a d2can rom. Should fix your problem. Ports are not always reliable and it may not "like" your phones hardware.
Click to expand...
Click to collapse
I have flashed a d2can and formatted and factory reset it as well.. any other suggestion please? Cache, dalvik, and fixed permissions too..

Adizzzle said:
I have flashed a d2can and formatted and factory reset it as well.. any other suggestion please? Cache, dalvik, and fixed permissions too..
Click to expand...
Click to collapse
You can always go the long way and it may help. Wipe everything from custom recovery (system, data, cache, dalvik, internal sd card) and then go into download mode and ODIN back to stock. Factory reset then proceed to rooting and installing as you wish.

stuck on galaxy S4 bootscreen

I cannot explain this.
Got my S4 early in May and the next day, received tge MDL ota update. Since then I have been trying to install custom ROMs for the S4 (tmobile). But everyone get stuck on the S4 bootlogo.
I'm using TWRP 2.5.0.1 and ALWAYS do a full wipe(Dalvic, cache, system & Data)
The only way I can get my S4 to work is to ODIN back to stock, TWRP and Root...no other rom works.
What am I doung wrong

bert269 said:
I cannot explain this.
Got my S4 early in May and the next day, received tge MDL ota update. Since then I have been trying to install custom ROMs for the S4 (tmobile). But everyone get stuck on the S4 bootlogo.
I'm using TWRP 2.5.0.1 and ALWAYS do a full wipe(Dalvic, cache, system & Data)
The only way I can get my S4 to work is to ODIN back to stock, TWRP and Root...no other rom works.
What am I doung wrong
Click to expand...
Click to collapse
Are you flashing a custom kernel, as well? Because you applied that MDL stock firmware update.. you locked your phone down at the kernel level with that update. You need to install a custom kernel that will allow you to use a custom ROM and attain full root.
Just my guess. Give it a try.
You may also want to try this after flashing the stock firmware with ODIN:
http://forum.xda-developers.com/showthread.php?t=2294005
Otherwise, here are some kernel options:
http://forum.xda-developers.com/showthread.php?t=2273440
http://forum.xda-developers.com/showthread.php?t=2274992
http://forum.xda-developers.com/showthread.php?t=2271976

bert269 said:
I cannot explain this.
Got my S4 early in May and the next day, received tge MDL ota update. Since then I have been trying to install custom ROMs for the S4 (tmobile). But everyone get stuck on the S4 bootlogo.
I'm using TWRP 2.5.0.1 and ALWAYS do a full wipe(Dalvic, cache, system & Data)
The only way I can get my S4 to work is to ODIN back to stock, TWRP and Root...no other rom works.
What am I doung wrong
Click to expand...
Click to collapse
Wipe data, both caches, then format the system and cache and try flashing again
Sent from my SGH-M919 using xda premium

thank you.
I will try these kernels next time.
thanks[

is the order important?
nbeebe24 said:
Wipe data, both caches, then format the system and cache and try flashing again
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
Ok. I have wiped the data and both caches, BUT not system.
I installed the Darth v4 Rom, and it works. For the first time I managed to get a rom installed AND it boots correct when I restart the phone again, and again. Before I could not restart the phone and it would not go past the S4 logo.
.
I suspect it has something to do with the way that TWRP is wiping system - it is not correct.

re: stuck on boot screen
bert269 said:
Ok. I have wiped the data and both caches, BUT not system.
I installed the Darth v4 Rom, and it works. For the first time I managed to get a rom installed AND it boots correct when I restart the phone again, and again. Before I could not restart the phone and it would not go past the S4 logo.
.
I suspect it has something to do with the way that TWRP is wiping system - it is not correct.
Click to expand...
Click to collapse
If you would have done a "Factory Reset" along with the other wipes you have done before flashing
you would have not gotten stuck on the boot screen and the phone would have booted up normally.
Always include "Factory Reset" in your "Full Wipes" for best results.

Cannot boot S4 after custom ROM flashes

My T-Mobile Galaxy s4 M919 will not boot after any custom ROM flashes. I tried 4 different ROMs with success messages. As soon as I reboot my phone after the ROM flash, it's stuck at the Samsung Galaxy S4 logo and would not enter the "phone desktop". I can easily enter download mode and recovery mode without any issue.
Background: I rooted with Odin successfully. (Used both CWM and OUDHS with the same no-boot results after flashing any custom ROMs). I can restore back to stock and phone boot up fine but tried root again and then with custom ROM and it would not boot. Any help would appreciate it.

After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app

Android_Monsters said:
After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.

anothersaddream said:
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.
Click to expand...
Click to collapse
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?

I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.

Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?

I switched to PhilZ Touch Recovery a couple of weeks ago and have not had Any issues as I did before.
TWRP 2.5.0.2 was issue free for months, until I started flashing ROMs with Aroma.
Nothing but issues re Samsung splash screen freezes, different solutions working sometimes and sometimes not, having to ODIN back to stock on many occasions, having to wipe INTERNAL SD on many occasions, etc., etc.
PhilZ was the solution.
This is coming from a hard core TWRP guy......
Check the link in Red in my sig for PhilZ and other good stuff

dynospectrum said:
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?
Click to expand...
Click to collapse
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.

DKYang said:
Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?
Click to expand...
Click to collapse
I have not tried TWRP 2.5 recovery yet. I mostly use CWM. I have waited 20+ minutes after flashing a custom ROMs but to no success.
I have done the following ROMs:
Insanity v1
VirginROM

stevessvt said:
I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.
Click to expand...
Click to collapse
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.

anothersaddream said:
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.
Click to expand...
Click to collapse
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.

anothersaddream said:
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.
Click to expand...
Click to collapse
wipe = format
yes, format system in mounts/storage.

Skipjacks said:
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.
Click to expand...
Click to collapse
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung S4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.

anothersaddream said:
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung g4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.
Click to expand...
Click to collapse
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.

find stock kernel, flash the roms you want and flash the stock kernel after and see if you boot

Biker1 said:
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.
Click to expand...
Click to collapse
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?

anothersaddream said:
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?
Click to expand...
Click to collapse
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.

Biker1 said:
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.
Click to expand...
Click to collapse
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.

anothersaddream said:
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.
Click to expand...
Click to collapse
I have no idea why it ain't working for you.
On the plus side, I don't know everything
If you ODINd Stock.
ODINd Recovery.
Did a Md5 Checksum match between the ROM file and your Download.
Wiped Internal SD.
Flashed the ROM......
and you're still having issues.......
I'm at a loss....
Try again is my only suggestion, and insure the steps taken are correct, including ODINing the proper files for your device.
Check & Double check
Including making sure you have a good usb cable, which sometimes can work and sometimes not....

If you haven't, try flashing from internal sd card. Maybe remove th external sd card just in case.

[Solved] Bootloop after flashing any Touchwiz based rom

Hi,
For about a few days, I can't flash any touchwiz based rom, even the ones I could flash without any problem before. After I flash any touchwiz rom, my phone goes into a bootloop cycle. Though I can boot into recovery and download mode with key combinations. I don't know when this happened for the first time but as far as I can remember, it would be after I flashed some 4.4 AOSP rom (could be Omnirom, I'm not sure though)
What I did to recover from boot loop:
- Wipe cache, wipe dalvik cache and reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, wipe data/media, reboot, no joy.
- Pulled out the battery between these steps too.
At first, I thought something was wrong about the aroma installer itself because the phone was getting frozen during aroma installer setup screen, then I came up that it was caused due to my older CWM version, so I updated the recovery and it didn't freze again during installation.
And by the way, I've lost my efs partition during these processes, thankfully I've had a nandroid backup from a couple of months before.
Now I'm stuck with AOSP roms and the only way I can use a touchwiz rom is to flash the stock rom via odin. But I want to use the new leaked version based Note3 featured roms.
I've seen similar topics at S4 section but I couldn't be sure if I can do the exact steps for an N7100 international device.
I'm pretty familiar with linux system and I can use adb so I can provide any kind of information you need to diagnose this issue. Thanks in advance. Best regards.
HOW I SOLVED THIS PROBLEM
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.

Guys, I really need some help.. Any idea about what might the problem be?
Sent from my GT-N7100 using XDA Premium 4 mobile app

Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful:http://d-h.st/fWr

Full wipe cache and reset in recovery menu, clear everything, you should be up and running.

akp.ajinkya said:
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful..
Click to expand...
Click to collapse
Thanks for the reply. I flashed this superwipe script, then flashed DN3 rom but still I got stuck at Samsung Galaxy Note II screen boot loop. I really don't understand this. What am I missing? What would happen if I wipe the entire internal memory block, I mean the whole things, even the root partition too.. I'm thinking that maybe there's some file inside the root partition that prevents me to flash touchwiz roms or perhaps something wrong about touchwiz based roms' bootloaders.. I'm truely pissed..
(InsertNameHere) said:
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
Click to expand...
Click to collapse
Have you read my first message? I remember that I've mentioned I've done already what you ask me to do.. Believe me I wouldn't shoot a new thread if I could've solved my problem with such easy steps. I've already done so many wipes, including internal SD and whatsoever.. I'm really confused and NEED help. Thanks anyway..

I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.

Im having the same problem but after flashing kernels (e.i. saber & perseus).
Im currently running on Tigra rom. Is this a compatibility issue or im just missing something here too?
I came across flashing bootimg but this thread http://forum.xda-developers.com/showthread.php?t=1752270
is for One S, im not sure if will work on Note 2 & haven't tried it yet.
Any suggestions? help pls...

akp.ajinkya said:
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Click to expand...
Click to collapse
Well, the problem is gone.
What I did was the things you said.
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.

Happy to help you bro

[Q] Deleted System with TWRP

Hi Everyone !
Im having a problem with my sgh-i747 samsung galaxy s3 at&t version
I accidentally deleted data and system of the phone with twrp and now my phone wont continue to boot
It is being stocked on the Samsung Galaxy S3 Logo
Im using the rom on this thread http://forum.xda-developers.com/showthread.php?t=2789917
I tried flashing the same rom and the CM 11 rom but its no good
Im wondering what can i do yo fix this problem?
Any help of response will be greatly appreciated
Thanks

What stock ROM was on your phone before you formatted the system?
Since you still have TWRP, flash a custom ROM, boot to recovery, wipe cache, data, Dalvik, and reboot.