Develop Bugs

Cant Flash new ROMs anymore. Please help.

Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.

Copy the ROM to your device (some storage folder)
Boot directly to TWRP
Manually install the ROM and the appropriate GAPPS
(watch the script window and see what it says.. look for errors)
Clear caches and dalvik
reboot

LuckyColdJohnson said:
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Click to expand...
Click to collapse
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.

I think its my recovery Twrp. I changed something.
adam_wingert said:
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
Click to expand...
Click to collapse
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.

LuckyColdJohnson said:
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
Click to expand...
Click to collapse
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium

What have I done ?
Android The Greek said:
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day

LuckyColdJohnson said:
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
Click to expand...
Click to collapse
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website

I figured it out!!!!!!!
Doggydude said:
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
Click to expand...
Click to collapse
It was the settings in TWRP. One of the boxes was checked. Sim actions for theming. I unchecked that and was on my way. Rocking The Collective AoCP now !!!!! Yes.....Thanks to all of you for your input. I'm going back to each and will hit thanks right now! Thanks again XDA members.
Lucky

I'm glad things worked out... isn't it amazing how attached we get to our toys
Sent from my GT-N7105 using Tapatalk 2

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.

[Q] n7100 probam rom stuck at boot

I recently tried installing probam rom v4.4.9 from xda threads and followed all the instructions. everything worked fine up until the thread said to reboot the phone once more, anyway long story short i rebooted it and it was stuck at the galaxy note 2 logo (white letters black background) it was stuck like this for around 5-10mins at which point i pulled the battery and decided to go back to using rootbox rom.
Is their anyway i can install probam rom without this happening again?
I've also tried downloading and installing probam version 4.5.0 from their own website following the instructions given on xda, but once its booted from twrp it'll work until i have to reset, at which point i am back to square one, being stuck at the galaxy note 2 logo.
I have also tried installing pacman rom because i would like to use a 4.3 rom but the same thing happens, the rom will work fine until i have to reboot or it randomly reboots and gets stuck at the note 2 logo.
the only roms i am able to use without this happening are moon rom v10, rootbox rom and carbon rom, only thing is i would like to use different roms and check out their features, but i am somewhat limited to what i can use due to the above problem. Does anyone else have this issue? If so how did you get past it?

Haven't had the problem myself. Did you also format the system partition and not just wipe it? Wipe the data partition?
Perhaps you can try installing a stock firmware through Odin, reinstall your recovery. That might clean some thing up that keep you from booting in probam rom.
Sent from my GT-N7100 using xda app-developers app

Machiel187 said:
Haven't had the problem myself. Did you also format the system partition and not just wipe it? Wipe the data partition?
Perhaps you can try installing a stock firmware through Odin, reinstall your recovery. That might clean some thing up that keep you from booting in probam rom.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
through twrp i went to wipe, format data typed yes, after this i swiped to factory reset then advanced wiped clicking cache, dalvik cache and system, if i've done this wrong could you please tell me how to do it the right way as i'm not really sure how to, thanks in advance :highfive:
i did what you told me to and flashed a stock rom through odin, went through the whole rooting process and flashed probam 4.5.0 again and this time it worked!! But no signal at all

tired of this really need help

I can't take it ever since i updated my t210r to 4.4.2 problems galore. i flashed several roms still i get random reboots and app stopps. i wiped everything and flashed odin over and over and still i get random reboots and app stops its driving me crazy that update was the worst mistake i ever made surely there is someone out there experiencing the same thing or know of a way to fix

kgalv419 said:
I can't take it ever since i updated my t210r to 4.4.2 problems galore. i flashed several roms still i get random reboots and app stopps. i wiped everything and flashed odin over and over and still i get random reboots and app stops its driving me crazy that update was the worst mistake i ever made surely there is someone out there experiencing the same thing or know of a way to fix
Click to expand...
Click to collapse
Sounds like a dirty flash try another rom using transche myself which is fine.

i have tried that rom even nolekat and experience the exact same problems

kgalv419 said:
i have tried that rom even nolekat and experience the exact same problems[/
I would suggest disabling the tablet of the apps you are not using and install greenify which will hibernate the apps until you are using them.
Click to expand...
Click to collapse

kgalv419 said:
I can't take it ever since i updated my t210r to 4.4.2 problems galore. i flashed several roms still i get random reboots and app stopps. i wiped everything and flashed odin over and over and still i get random reboots and app stops its driving me crazy that update was the worst mistake i ever made surely there is someone out there experiencing the same thing or know of a way to fix
Click to expand...
Click to collapse
Try flashing the full stock firmware from sammobile; then boot into the stock recovery and do a full factory reset. If that doesn't work, then you may want to install a custom recovery and re-format (not wipe, but actually format) the data partition.

Ok will try that. After wiping the data partition what should i do?

kgalv419 said:
Ok will try that. After wiping the data partition what should i do?
Click to expand...
Click to collapse
I would boot into the complete stock system and see if you have any problems. If everything works fine when completely stock, then you can install a custom recovery and try some other roms.

Ok cool i really hope this works bud because I've tried everything even used twerp recovery to advance format system, data, cache and internal storage

gr8nole said:
I would boot into the complete stock system and see if you have any problems. If everything works fine when completely stock, then you can install a custom recovery and try some other roms.
Click to expand...
Click to collapse
still no luck gr8 i tried booting into stock still i get random app stops, like "unfortunately playstore has stopped"., "unfortunately systemui has stopped", "unfortunately touchwizhome has stopped", and all other apps depending on which one i'm using. they still come on back but its really annoying also i get random reboots. i feel like i have tried everything.

Did you ever get this fixed?
Did you ever figure out a fix? I'm having the exact same problem.
gr8nole said:
Try flashing the full stock firmware from sammobile; then boot into the stock recovery and do a full factory reset. If that doesn't work, then you may want to install a custom recovery and re-format (not wipe, but actually format) the data partition.
Click to expand...
Click to collapse
I've flashed back to the stock fimware from sammobile and I still have errors and random rebooting. So I rooted with CWM ad did a full factory reset, still the same problems. I've re-formatted the data and the data/media (/sdcard) partition,still the same problem.
gr8nole said:
I would boot into the complete stock system and see if you have any problems. If everything works fine when completely stock, then you can install a custom recovery and try some other roms.
Click to expand...
Click to collapse
Even a completely stock system, I'm having problems. I've tried wiping everything (cache, dalvik ,data/factory reset ) then flashing back to the stock firmware using Odin3 v3.09, and I'm still getting errors and random rebooting.
Has my t210 bit the dust?

Seems like a lot of people are having trouble with the new updates. I would try to find an older version of the stock rom and load it thru Odin 3.7 and see if you still have the same problems.

Same thing I'm thinking but I still have hope

Did any of you all clear your cache and dalvik-cache as part of the flashing process?
The 4.4 ROM is an update to the stock 4.2. If you use a custom ROM, you will probably need to reflash stock 4.2 in order to flash 4.4.

But this tab never had 4.2 only 4.1 and I did a complete wipe before flashing anything

kgalv419 said:
But this tab never had 4.2 only 4.1 and I did a complete wipe before flashing anything
Click to expand...
Click to collapse
Here's what I would do then:
Reflash 4.1, then try 4.4. If that doesn't work, flash all three consecutively. Gotta test around to find out what works.

Greaper88 said:
Here's what I would do then:
Reflash 4.1, then try 4.4. If that doesn't work, flash all three consecutively. Gotta test around to find out what works.
Click to expand...
Click to collapse
We have got a V4.2.2 Version, but this was ported from the Tab 3 sm-t110 lite.

Format and wipe all folders using none stock recovery like CWM this will empty all junk left behind

Should I erase all this everything I've included in the screenshot?

andynroid said:
Format and wipe all folders using none stock recovery like CWM this will empty all junk left behind
Click to expand...
Click to collapse
U there bro?

...What recovery you r using ? Cause the wipe n format is under in recovery mode (not stock recovery)
Yes everything must be deleted

Help. Bricked(?) t999l

Hi,
I don't know what happened because I didn't do anything out of ordinary, but my S3 (TMO LTE) seems bricked. It was unlocked, rooted, and was running pacman lollipop ROM. The recovery was TWRP (the latest). I was going to sell this phone, so I turned off, removed sim card and microsd card. Powered it on. Everything was working. Then, I went to setting and hit factory reset from there. The phone restarted, but got stuck on the blue teamwin screen (the one that gets displayed before TWRP loads). The phone can't get past it. Not sure what caused it because it was a simple factory reset from the OS itself. Any help would be appreciated.
Thank you,

Just flash stock rom from sammobile.com using Odin. After flashing, boot to recovery and perform a full wipe.

audit13 said:
Just flash stock rom from sammobile.com using Odin. After flashing, boot to recovery and perform a full wipe.
Click to expand...
Click to collapse
If I flash the firmware from there, I'm going to lose root, right?

The phone will go back to completely stock, no root.

audit13 said:
The phone will go back to completely stock, no root.
Click to expand...
Click to collapse
Is there an alternative fix that will maintain the root TWRP? I know I can just root it again, but if possible I'd rather not go through all that because I am relocating in 3 days.

Do you want to sell the phone with a custom ROM? If you do, you could download and flash another custom ROM after re-installing TWRP.

audit13 said:
Do you want to sell the phone with a custom ROM? If you do, you could download and flash another custom ROM after re-installing TWRP.
Click to expand...
Click to collapse
Yes. I'm trying to make it more appealing with Lollipop on it lol So, just to double check, I should just install TWRP using Odin then install custom ROM, correct? By the way, do you have any idea what why my S3 got bricked? Did I do something wrong???

Sometimes, things just happen. Could be a several factors, one of which is the fact that cm12.1 may not have reached a stable state on the device. Also, the latest bootloader for the T999L is 4.3 while KK is the latest for T999v. Maybe the KK bootloader makes the phone more stable? I really don't know.
Yes, just flash TWRP, boot to recovery, do a full wipe of the system, cache, dalvik, data, flash ROM, flash Gapps, flash supersu if the ROM is not pre-rooted, and re-boot.

audit13 said:
Sometimes, things just happen. Could be a several factors, one of which is the fact that cm12.1 may not have reached a stable state on the device. Also, the latest bootloader for the T999L is 4.3 while KK is the latest for T999v. Maybe the KK bootloader makes the phone more stable? I really don't know.
Yes, just flash TWRP, boot to recovery, do a full wipe of the system, cache, dalvik, data, flash ROM, flash Gapps, flash supersu if the ROM is not pre-rooted, and re-boot.
Click to expand...
Click to collapse
Thank you for all your help. You are awesome!

You're very welcome. We're all here to help each other out!