Develop Bugs

problems flashing roms, big problems.

I don't know what caused it... but no matter what rom I flash it seems that it always gets through the bootup screens and then gets stuck on the samsung screen, and won't load into a custom rom. It seems like something happened to my system and I have tried everything and nothing it working. I can only run with the stock rom it came with and thats it.
I have no clue whats going on. When I flash from ROM to ROM I take these steps.
1- put rom on SD card
2- nandroid
3- factory wipe from recovery
4- wipe cache
5- wipe dalvik
6- flash rom
7- flash gapps (if on AOSP based)
8- reboot.
I have went back to stock via odin, then reflashed via odin, repushed the recovery, basically started from scratch and nothing is letting me install a new rom. Wasn't really having any problems until today... any ideas? :crying::crying::crying::crying::crying:
edit- I was thinking, I did ALOT of debloating at the beginning using the aroma debloater, and did some minor debloating myself.. I wouldn't think this would have anything to do with a new rom because when I wipe everything it does a fresh install of everything... So I am stuck.

3.5- mounts and storage > format system
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

theROMinator said:
3.5- mounts and storage > format system
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
should this be done everytime?

Optimizer said:
should this be done everytime?
Click to expand...
Click to collapse
Yes. Although if you're updating a rom i.e. cm or aokp a cache/dalvik cache wipe will do (unless stated otherwise).
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

theROMinator said:
Yes. Although if you're updating a rom i.e. cm or aokp a cache/dalvik cache wipe will do (unless stated otherwise).
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
see my main thing was everyone was talking about how if I was going from a modded stock rom to a modded stock rom there would not need anything except cache wipes... and i still get hung..:/

I recommended backing up all of your data, do a factory reset, then go back to stock with an Odin package from development. From there you can root or whatever you please.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Rooting the right way?

The problem: I rooted with the SuperSU and so on, but when opening, it said to install BusyBox. I did that, and now upon rebooting, Wifi hangs on turning on. Am I supposed to skip the whole ' Busybox installation '?
* When wiping for a new rom, only wipe Cache, Dalvik, and Data, Correct? Not System?
* When flashing a rooted rom, I don't have root. Shoud I flash the SuperSU zip after flashing the rom?

Curiousn00b said:
The problem: I rooted with the SuperSU and so on, but when opening, it said to install BusyBox. I did that, and now upon rebooting, Wifi hangs on turning on. Am I supposed to skip the whole ' Busybox installation '?
* When wiping for a new rom, only wipe Cache, Dalvik, and Data, Correct? Not System?
* When flashing a rooted rom, I don't have root. Shoud I flash the SuperSU zip after flashing the rom?
Click to expand...
Click to collapse
Tell me what rom u use? Stock? System=rom so , wipe it off if and flash another u have problems
Sent from my One V using xda app-developers app

I didn't wipe System because all of the instructions to the roms, never really seen it, but brick warning said not to. Thanks. I'll wipe, it'll help clear things up
Sent from my HTC One V using Tapatalk 2

Curiousn00b said:
I didn't wipe System because all of the instructions to the roms, never really seen it, but brick warning said not to. Thanks. I'll wipe, it'll help clear things up
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
System is ur rom ...so if u have problems wipe and flash a new one
Sent from my One V using xda app-developers app

Yes. I know all partitions.
Just didn't know if it was safe due to that brick warning. Seems safe enough, everything is smoother now. No random crashes(not fc). Thanks
Sent from my HTC One V using Tapatalk 2

Curiousn00b said:
Yes. I know all partitions.
Just didn't know if it was safe due to that brick warning. Seems safe enough, everything is smoother now. No random crashes(not fc). Thanks
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
my pleasure!

X crashes all processes upon startup

Hi Xda,
I was working on putting a custom ROM on my one x as a result of it being slow.
everything started out fine, bootloader was unlocked fairly easy, gaining perm root as well.
however after a couple of tries I haven't been able to get a custom rom working properly. it will start up the system, passed the startup, then as soon as the first start screen opens up, every possible process starts crashing. (the only really visible crash is com.android.phone, however as soon as I click "ok" it will pop-up again within a second)
I've done the following:
Remove lock,
gain root access,
install CWM
downloaded ROM and Gapps (put it on the SD card)
performed a full wipe (Dalvik Cache, factory Reset)
install ROM and Gapps.
after this the problems started occurring.
a few solutions i tried:
1. I've retried the above process and included the boot.img loading using fastboot, then clearing the cache again.
2. I've wiped all possible data using the "superwipescript"
3. tried a different ROM which gave me the exact same errors.
atm i'm getting desperate because I've run out of options.
Is there a workaround for this problem?
Thanks in Advance!

Have you flashed boot.img via fastboot?
Sent from my GT-N8000 using Tapatalk HD

this might be a silly question, but it's not an AT&T one x? there have been a few of those here who shouldn't be here.
if it isn't...then check your HBOOT version

csec said:
Have you flashed boot.img via fastboot?
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
yeah i've flashed the boot.img and then cleared the cache!

jeroen2303 said:
yeah i've flashed the boot.img and then cleared the cache!
Click to expand...
Click to collapse
Does your hboot meet the required version for the ROM You flashed ?
Sent from my GT-N8000 using Tapatalk HD

csec said:
Have you flashed boot.img via fastboot?
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
ace9988 said:
this might be a silly question, but it's not an AT&T one x? there have been a few of those here who shouldn't be here.
if it isn't...then check your HBOOT version
Click to expand...
Click to collapse
No i'm on the international one x (Dutch, T-Mobile)
my HBOOT Version is 1.39.0000
I've tried installing Paranoid Android 3.10 and 3.15 and ICJ422
Is that the correct version?

jeroen2303 said:
No i'm on the international one x (Dutch, T-Mobile)
my HBOOT Version is 1.39.0000
Is that the correct version?
Click to expand...
Click to collapse
Yes. You have the latest hboot.
You may wait for more expert replies.
Sent from my GT-N8000 using Tapatalk HD

csec said:
Yes. You have the latest hboot.
You may wait for more expert replies.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
I've tried waiting with installing the Gapps till after the first boot but the same problem keeps occurring.
any other advice?

jeroen2303 said:
I've tried waiting with installing the Gapps till after the first boot but the same problem keeps occurring.
any other advice?
Click to expand...
Click to collapse
Reboot into recovery and under advanced, select fix permissions.
Sent from my GT-N8000 using Tapatalk HD

csec said:
Reboot into recovery and under advanced, select fix permissions.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
tried but won't work!

Make a clean wipe manually twice
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the rom

Mr Hofs said:
Make a clean wipe manually twice
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the rom
Click to expand...
Click to collapse
I've tried the above but it gives the same exact error. as soon as the systems has started up it gives: "Unfortunately, the process com.android.phone has stopped" when i press ok there is a second error about messages but i'm not able to read this since the first message will pop up again.
should I start to get worried by now?

jeroen2303 said:
I've tried the above but it gives the same exact error. as soon as the systems has started up it gives: "Unfortunately, the process com.android.phone has stopped" when i press ok there is a second error about messages but i'm not able to read this since the first message will pop up again.
should I start to get worried by now?
Click to expand...
Click to collapse
Do you get this on all ROMs??
Try using a Sense ROM....
Sent from my HTC One X using xda app-developers app

Boot the phone without the simcard....

athulele said:
Do you get this on all ROMs??
Try using a Sense ROM....
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I've tried using a Sense ROM without success. I Can't seem to get passed the HTC ONE logo.
as for the simcard, i've tried booting inserted and left out but none of the two work..

jeroen2303 said:
I've tried using a Sense ROM without success. I Can't seem to get passed the HTC ONE logo.
as for the simcard, i've tried booting inserted and left out but none of the two work..
Click to expand...
Click to collapse
Flash the boot.img from the sense ROM.zip.. and then fastboot erase cache...then it won't be stuck at HTC logo...
Which roms did your try??? :S
I was having the same problem on Paranoid Android... not all the time like you but 4-5 times a day... Changed to ICJ and everything is stable now! Also make sure you have flashed the proper gapps...

jeroen2303 said:
I've tried using a Sense ROM without success. I Can't seem to get passed the HTC ONE logo.
as for the simcard, i've tried booting inserted and left out but none of the two work..
Click to expand...
Click to collapse
I gave the phone a good hour and my phone seems to be working for now!
Thanks for all the help,
This is on a sense ROM!

Hmmm! Good to hear that m8!

vin4yak said:
Hmmm! Good to hear that m8!
Click to expand...
Click to collapse
felt only happy for a while, but back to problems now.
the ROM takes an hour to boot on average and won´t let me make any calls. besides the settings menu will crash as soon as I try to open anything.
I´m going to try another Sense based ROM now and will see what happens next!

jeroen2303 said:
felt only happy for a while, but back to problems now.
the ROM takes an hour to boot on average and won´t let me make any calls. besides the settings menu will crash as soon as I try to open anything.
I´m going to try another Sense based ROM now and will see what happens next!
Click to expand...
Click to collapse
Maybe this could help you: http://forum.xda-developers.com/showpost.php?p=40817031&postcount=42

Problem with twrp, Lots of fail to flash

Lately I'm getting a lot of fail to flash in tarp recovery, the latest one for flo.
I have nothing spécial on it , only plain stock rooted.
Sometimes when i want to try another ROM or whatever that needs to be flashed in recovery I get a fail to flash.
I don't know why, any advice?
Sent from my Nexus 7 using xda app-developers app

What is the specific error you encounter?

Wipe cache, dalvic, data, and system. Then back out to main menu. Go to reboot, recovery. When it prompts you to root, click not now. When it re boots into recovery, flash away.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Micronads said:
Wipe cache, dalvic, data, and system. Then back out to main menu. Go to reboot, recovery. When it prompts you to root, click not now. When it re boots into recovery, flash away.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I too find that when I try to flash update from 4.3 to 4.4.2 using twrp, it fails.
Is there no way to do it without wiping my data? That would be a pain!
I'm on rooted stock rom.

Anderson2 said:
I too find that when I try to flash update from 4.3 to 4.4.2 using twrp, it fails.
Is there no way to do it without wiping my data? That would be a pain!
I'm on rooted stock rom.
Click to expand...
Click to collapse
Make sure you are using the lateste TWRP, earlier ones tend to fail, try Philz recovery works great

Thanks for replying. I'm using twrp 2.6.3.0. Still failing to flash.

Anderson2 said:
Thanks for replying. I'm using twrp 2.6.3.0. Still failing to flash.
Click to expand...
Click to collapse
Yup thats why look for 2.6.3.1 or try Philz

I'm not sure how to update twrp. Will open its recovery screen and see if it has an update option.
What is Philz? I searched for it and found coffee shops.

Anderson2 said:
I'm not sure how to update twrp. Will open its recovery screen and see if it has an update option.
What is Philz? I searched for it and found coffee shops.
Click to expand...
Click to collapse
It is custom recovery ,check it http://forum.xda-developers.com/showthread.php?t=2485264
there are many tutorials how to update /change cwm .

Boot loop Sprint Note 4

Well guys I had no experience in rooting but i thought it was going to be a straight forward task and went ahead and tried anyways. I have the Galaxy Note 4 it was on 5.1.1 lolipop and i attempted to use Cf-Auto-Root Just plugged the phone in and flashed it with Odin nothing else no other steps. Now I am stuck at an infinite boot loop and I do not know what to do. Please help anyone.

This should get you back on track. Just don't use CFAutoRoot but kernel with root exploit and SuperSU zip.
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Since you looped it, try a cache and dalvik wipe and reboot recovery also before you flash those and boot.
Sent from my SM-N910P using Tapatalk

samep said:
This could get you back on track. Just don't use CFAutoRoot but kernel with root exploit and SuperSU zip.
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Since you looped it, try a cache and dalvik wipe and reboot recovery also before you flash those and boot.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I attempted the wipe but it did nothing

imNoland said:
I attempted the wipe but it did nothing
Click to expand...
Click to collapse
You need Beastmode kernel and SuperSU zip from that post. Wipe cache and dalvik, reboot recovery and do it again plus flash those two zips and reboot.
If stl not working, format data and do the steps again.
Sent from my SM-N910P using Tapatalk

samep said:
You need Beastmode kernel and SuperSU zip from that post. Wipe cache and dalvik, reboot recovery and do it again plus flash those two zips and reboot.
If stl not working, format data and do the steps again.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Do I need an external sd to do this or am i able to use the system storage.

imNoland said:
Do I need an external sd to do this or am i able to use the system storage.
Click to expand...
Click to collapse
Hopefully you got it but the cache and dalvik-cache wipe wouldn't wipe internal storage.
Sent from my SM-N910P using Tapatalk

samep said:
Hopefully you got it but the cache and dalvik-cache wipe wouldn't wipe internal storage.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Samep I love you... Thanks for the help I got it working, I feel like a dip but thanks I really appreciate it.

You're welcome. Glad you got it back quickly.
Sent from my SM-N910P using Tapatalk