Develop Bugs

[Q] Flashed Rom Hangs

So I flashed a new rom, did the usual, clear everything, reset/cache/dalvik and flashed the rom. However, when I rebooted the trinity logo/initial startup just stays on that screen forever. I tried reflashing from recovery and it still hangs forever on that screen. Do I have to go thru download mode/odin and get stock/root to be able to flash again or is there a quicker easier way?

Have you tried to restore a nand backup?

Try a factory reset after you flash the new rom.

Aerowinder said:
Try a factory reset after you flash the new rom.
Click to expand...
Click to collapse
I tried the reset after flash... and I never do NAND backups T_T. But I never do anything that could ruin it. I just thought there would be a quicker way instead of a compete reset to stock. But o wells, now I can set the flash counter back to 0 and not trip it anymore.

Stuck in bootloop

I had decided to upgrade my cm10 to the latest version so I went into twrp recovery backup it up wiped data, system, cache, dalvik cache, then I installed the rom and gapps and whiped cach and dalvik. Now im rebooting and im stuck in the first cm10 bootscreen with the samung galaxy s3 text an the cm10 alien dude. I tried restoring my twrp backup and it failed.
What do i do with formatting data? I tried installing older cm10 rom version I got on my phone and none worked and for some reason i cant see my sd card when i mount it through twrp
Help!

re: bootloop
genardas said:
I had decided to upgrade my cm10 to the latest version so I went into twrp recovery backup it up wiped data, system, cache, dalvik cache, then I installed the rom and gapps and whiped cach and dalvik. Now im rebooting and im stuck in the first cm10 bootscreen with the samung galaxy s3 text an the cm10 alien dude. I tried restoring my twrp backup and it failed.
What do i do with formatting data? I tried installing older cm10 rom version I got on my phone and none worked and for some reason i cant see my sd card when i mount it through twrp
Help!
Click to expand...
Click to collapse
Have you tried this? - It should work every time.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you have purchased it except with the benifit of being rooted.
Download the stock-rooted T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware (a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!

Sometimes it can take a while to get past that screen the first time you turn it on with a new ROM (like, 5+ minutes) - how long did you wait ?

Wow. What a crazy 24 hrs. My S3 kicked out a couple hiccups yesterday. Gave me a gapps error and then one other I don't remember. I decided to just reboot to restore everything. Phone would not boot past boot screen. Crazy. I could get into recovery. Tried to restore from backup. Nope. Stuck at boot screen. Odin back to stock w/root. Nope. Odin back to stock. Nope. Ended up Odin to stock. Boot into recovery. *Wipe data and factory reset 3 times*. It then completed a boot. FINALLY!!! OMG. Such a bizarre fluke. I am back on rooted Wicked 9.1 thanks to a backup. I searched various forums and threads on here. I tried the above procedure. (It was actually the first thing I did and what I used as a guide.) It wasn't until I did the Odin, boot into recovery and wipe data 3 times that my phone would completely boot up fully.

radar9 said:
Wow. What a crazy 24 hrs. My S3 kicked out a couple hiccups yesterday. Gave me a gapps error and then one other I don't remember. I decided to just reboot to restore everything. Phone would not boot past boot screen. Crazy. I could get into recovery. Tried to restore from backup. Nope. Stuck at boot screen. Odin back to stock w/root. Nope. Odin back to stock. Nope. Ended up Odin to stock. Boot into recovery. *Wipe data and factory reset 3 times*. It then completed a boot. FINALLY!!! OMG. Such a bizarre fluke. I am back on rooted Wicked 9.1 thanks to a backup. I searched various forums and threads on here. I tried the above procedure. (It was actually the first thing I did and what I used as a guide.) It wasn't until I did the Odin, boot into recovery and wipe data 3 times that my phone would completely boot up fully.
Click to expand...
Click to collapse
Could have saved yourself hours by doing a factory reset.

Yeah guys I restored it thorugh odin and then went into the stock recovery like an idiot and being used to the twrp recovery clicked wipe data/factory reset thinking it would reset the rom and I lost everything. Well really only lost music buts its k. Now im back on stock but I might have to root again DDD

genardas said:
Yeah guys I restored it thorugh odin and then went into the stock recovery like an idiot and being used to the twrp recovery clicked wipe data/factory reset thinking it would reset the rom and I lost everything. Well really only lost music buts its k. Now im back on stock but I might have to root again DDD
Click to expand...
Click to collapse
Next time you should keep stock rom and kernel on your sdcard so that if anything goes wrong you could flash that, usually it might fix the bootloop. When installing a JB rom, be sure that you have a kernel that is compatible with JB. If not, you could enter a bootloop. Also, BACKUP EFS.

In between 4.2.2 and 4.3 problem.

I was on 4.2.2 XenonHD with LeanKernel. I directly flashed Cataclysm ROM with cache, dalvik cache wipe and factory reset on GooManager. It booted flawlessly the first time. Then after completing the startup I rebooted. But then I became stuck on the google logo (surprise surprise...)
I don't get it. Why did it boot perfectly the first time but not after a reboot?
Anyway, I tried to restore my nandroid backup of the 4.2.2 XenonHD ROM. But then I got stuk at the google logo again. Why?
I haven't backed up my mediafiles (music, photo's etc) yet, in case a factory image installation is needed. I assumed I didn't need to backup those mediafiles, becuase I already have a nandroid backup, meaning I can always go back to the last ROM.
Does anybody have a solution for this? I don't care if I end up booting in 4.2.2 or 4.3, as long as I can preserve my media files.
Or do I have no other options than installing factory boot image of 4.3, meaning my files will be gone?
Thanks in advance.

No as long as you don't flash userdata.img nothing will be wiped (I think maybe to be sure you have to check twice). You can use adb pull to pull the mediafiles if you want.
Sent from my Galaxy Nexus using XDA Premium HD app

Try factory reset and then try to restore from the backup..

lastforone said:
Try factory reset and then try to restore from the backup..
Click to expand...
Click to collapse
It didn't work. I can still see my files and everything in TWRP recovery.

Rapydax said:
It didn't work. I can still see my files and everything in TWRP recovery.
Click to expand...
Click to collapse
I had Purity ROM with A.S.K.P kernel when 4.3 came out, i grabbed the zip from one of the topic in development and flashed it VIA CWMRecovery, was pretty smooth but i wanted all my setting which wasn't possible so i reverted back to Purity, this is how i did it.
Factory Reset.
Format /system
Flashed 4.3
--
Factory Reset.
Format /system, /cache, cleared Dalvik Cache as well
Flashed PurityRom 4.2
Flashed A.S.K.P Kernel
Flashed CrossBreeder Mod
Booted into OS successfully.
Restored My Apps
Click to expand...
Click to collapse
had no problem, well yeh first boot took its time to load but it did, i knew that A.S.K.P will take its time to boot for the first time so i let it be for like 4-8 mins.

Updating SGH-I747 from 4.1.1 to 4.3

I've looked around a bit and can't quite find someone that has had my specific situation.
I have a AT&T S3 SGH-I747 that is rooted running stock 4.1.1 with CWM 6.0.4.7. I have updated the modem and bootloader (Baseband - I747UCUEMJB and Build # JRO03L.I747UCDLK3).
I have tried to flash custom and stock ROMS with CWM but get stuck on the glowing Samsung logo. I have tried to follow the instructions listed here but I cannot flash the stock ROM with ODEN.
I am not sure as to what to attempt next. I first want to be able to update to 4.3/4.4.2 and then try custom builds.
I have all my apps and data backed up with MyBackup and a Nandroid backup as well.
Thank you.

Are you wiping the cache, davilk, and data before of after flashing the ROM?

I wipe/format before the flash. I factory reset, clear cache, clear davilk, format data, and format system then flash the ROM. I've tried several combinations of clearing/formatting. The flash always goes well and then I reboot. The boot goes and then just sits at the Samsung logo (It does make the AT&T sound during this time)

Hubbins said:
I wipe/format before the flash. I factory reset, clear cache, clear davilk, format data, and format system then flash the ROM. I've tried several combinations of clearing/formatting. The flash always goes well and then I reboot. The boot goes and then just sits at the Samsung logo (It does make the AT&T sound during this time)
Click to expand...
Click to collapse
Try to factory reset once the flash is done if it doesn't boot after 5-10min.

Thanks. I'll give it a shot and we'll see how it goes.

Unfortunately that tip did not appear to help. I still got stuck on the glowing Samsung logo.
I was final able to flash 4.3 using the method here using odin.

T999L - soft bricked

Ok I have T999L 16GB.
Phone working fine. Did hard reset because they hadn't been used in a while and wanted to start fresh.
After reboot, phone stuck in "T-Mobile 4G LTE" bootloop forever. Tried again, same thing.
Did Odin flash of latest ROM for that device (per what I could find?)
T999LUVUBOH1_T999LTMBBOH1_T999LUVUBOH1_HOME.tar
same thing, no result. Downloaded the PIT file for that phone, did another odin flash of the ROM above, but checked "re-partition" and pointed to the PIT file. Successful flashing, device rebooted. Same thing endless bootloop.
Not really sure what to do now, any ideas?
@DocHoliday77 possibly as one of the resident experts 'round these parts...

Immediately after flashing and before the first boot, get into recovery and perform a full wipe.

audit13 said:
Immediately after flashing and before the first boot, get into recovery and perform a full wipe.
Click to expand...
Click to collapse
worth a try, will report back.
edit: @audit13 - Worked like a boss, did the odin with repartition PIT file, but deselected auto-restart, went into recovery after flashed and wiped factory reset plus cache, rebooted, and BAM, got into the set up screen.
Thanks for your help.

Glad it worked for you. A factory wipe is sometimes required to make the data and cache partition available to the newly flashed rom. Even wiping via twrp or cwm may not be enough at times.

audit13 said:
Glad it worked for you. A factory wipe is sometimes required to make the data and cache partition available to the newly flashed rom. Even wiping via twrp or cwm may not be enough at times.
Click to expand...
Click to collapse
Yeah sure seems to be that way, glad that's all it was. I know the PIT mapping with the ROM must have helped too, but flashing in stock recovery after that cleared it up for writing to the new partitions like you said.
Coming from a Nexus 6 this was pretty annoying, I am used to using fastboot to do everything, I don't see a Samsung device in my future.

Same thing can happen with a nexus 4 and nexus 5 in that I still have to perform a full wipe in stock recovery if the phone was running a custom rom. Don't have a nexus 6 or 6p to play with
Samsung phones don't have a fastboot mode. The closest thing would be their download mode.