[Q] Trouble flashing Stock & Custom ROM's - Droid Ultra Q&A, Help & Troubleshooting

So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?

morr22066 said:
So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
Click to expand...
Click to collapse
I had tried everything I could think of and it appeared that there was a partition problem. The phone continued to shut down and would only stay on while connected to the PC. If it were a PC I would reformat and re-partition the drive but I did not want to risk a permanent brick by messing with it.
So, as a last ditch effort to try and get my phone functioning again I let it download and install system updates. The phone is now working again, it has not shut down at all and there have been no warning messages about cool down mode.
BUT, I am now on "4.4.4, SU-5-24, build 23.3.24 dated 10-27-14. Since my boot loader is unlocked I flashed TWRP but it would not not accept Super SU zip so I am no longer rooted.
I finished reading up on it in the forums and realize I am pretty much screwed as far as root goes. But at this point I don't even care anymore. I just need to get the phone functioning correctly.
*So, I am still having the problem with flashing stock and getting the "red" letter message after system image boots saying "sp space not enough". So long as it is hooked up to the computer it stays on and if it is downloading or installing an update it stays on and I never get a warning about cool down mode and it does not shut off, but once I disconnect from the computer it starts all over again. The phone boots up but at random intervals it still either gets a pop up message saying that it has gone into "cool down mode" or it shuts off. It is not doing it as often as before, but it is still doing it. Does anyone have any suggestions on whats causing it or how to fix it? It sounds like a software / firmware issue but I am not sure how to fix it.
*Update. The phone is still not functioning correctly. At times it will appear to work fine for hours with frequent to heavy use at times then suddenly it will start acting up, the phone will shut down randomly and when it reboots some of my settings have changed. The temperature is usually pretty low but once in a while after a shut down I will check the temp when I'm able to reboot it and it will be high. When it shuts down like that I usually have trouble getting it to boot up again unless I plug in the factory cable, either in the PC or just the wall charge then it seems to boot up fine and I can even reboot it but once it shuts itself down it doesn't want to start again unless I use the factory cable.
It really does sound like a software / firmware / partition problem but after multiple attempts to flash the firmware with RSD I continue to get the same error message at the end of the system flash and the phone continues to have problems. Does anyone have any suggestions?

Got me an xt1080 which I'm trying to restore to stock, and in both House of Motor and RSDlite 6.2.4 at some point during the system partition flash 'so space is not enough' as well. The phone is in perpetual bootloop, unless I use a 'Factory/power' cord and starting up in fastboot (eventually). Tried both 1FF and CFC fxz files, no luck.

Related

[Q] Phone stuck at AT&T logo

Last night I was using my phone and it rebooted randomly, and when it came back up it got stuck at the AT&T logo. I pulled the battery and restarted several times with no luck. Even left it out overnight and tried again.
I can get the phone into 3e recovery just fine. Will clearing the cache possibly help? What information is on the cache that will be cleared?
I don't have an original charger cable right now, so I can't try download mode. I'm trying to avoid using Odin again, because I would rather not lose the huge amount of new contacts and notes I have in my phone, it would be a major setback.
My phone has also had some issues with a device I/O error, and I haven't been able to back up my phone, so I'm not even sure if download mode would work for me.
Please help!
Edit: As I was about to write that I have had this problem before.... my phone was at the AT&T screen and it magically works again.
InfuseIssues said:
Last night I was using my phone and it rebooted randomly, and when it came back up it got stuck at the AT&T logo. I pulled the battery and restarted several times with no luck. Even left it out overnight and tried again.
I can get the phone into 3e recovery just fine. Will clearing the cache possibly help? What information is on the cache that will be cleared?
I don't have an original charger cable right now, so I can't try download mode. I'm trying to avoid using Odin again, because I would rather not lose the huge amount of new contacts and notes I have in my phone, it would be a major setback.
My phone has also had some issues with a device I/O error, and I haven't been able to back up my phone, so I'm not even sure if download mode would work for me.
Please help!
Edit: As I was about to write that I have had this problem before.... my phone was at the AT&T screen and it magically works again.
Click to expand...
Click to collapse
I'm sorry if your not able to save all your contacts but the only way to stop your phone from flashing samsung over and over again is to use odin. Or the case could be is that your power button is either stuck or messed up.

'Optimising App' Bootloop

Hiya,
Very frustrated noob here. I have an unrooted/locked-bootloader 2nd Gen Moto G and a few weeks ago I tried to turn it on after charging it overnight and after the usual loading screen it went straight to a message saying "Optimising App 1 of 152", and after going through all the 152 apps it just restarts immediately without reaching the normal PIN input screen, and starts the "Optimising" all over again and repeats this until it runs out of battery and dies. I have tried waiting for it to die, charging a little and then entering recovery mode, where I tried wiping the cache partition which made no difference. I don't mind about getting the phone up and running again as I'm getting a new one, but is there some way of getting my files off it? There are some music recordings I made that I stupidly didn't backup that I'd really really like back. For example, is it possible to reinstall the latest OTA from an SD card without losing all the data on the phone that might kick it out of whatever it's looping? Any help at all much appreciated, cheers
1. If you want to take backup of ur data then Flash TWRP Recovery And Reboot to recovery and then connect your phone to pc and tada ur done.
2. u can flash another Roms Which can solve ur booting problem too.

Galaxy S7 G930U Unlocked stuck in boot loop - already flashed successfully but no fix

I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
gabeblack said:
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
Click to expand...
Click to collapse
You need to clear the cache after flashing to get out of the boot loop.
Use the download key combo to restart. As soon as the screen goes black move to Volume up+home+power.
In the recovery menu choose clear/ Wipe cache, then choose reboot.
I apologize for not updating this thread before when it was still recent. The fact is that I didn't manage to fix my phone; clearing the cache after flashing did nothing to stop the loop.
I ended up taking the phone to the people who have fixed it in the past and after more than one month, they gave up. So I got my phone back and I want to try to give it another go before I just sell it for parts.
Unfortunately, my phone has come back even worse. Now it has no Recovery Menu to speak of, at least none that I can access; after a few seconds of the blue text on the top saying that it's entering recovery mode, it then proceeds to a blue screen saying: "Security Error: This phone has been flashed with unauthorized software and is locked.". I can still access Download Mode.
I have attempted flashing a few firmwares that I believe should have worked with my SM-G930U. Odin listed the attempts as "pass" and, after restarting and going back to the Download screen, it says the binary is Official. However, after trying to restart the phone normally, it starts displaying the blue screen again, and then, after going to Download mode, the binary is reverted to "Custom".
I believe right now the order of the day is to get the recovery menu to work again so I can do all the cache cleaning that seems to be required after flashing firmware. Any ideas at all on how I should proceed? Is there something specific I should download to fix the recovery menu?
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Drunkpilot said:
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Click to expand...
Click to collapse
Never rooted, was using the phone legit before it froze and entered boot loop. I flashed all 4 files, multiple times.
Someone tried fixing my phone a few days after I replied to this thread and some progress seems to have been made, but now the phone cannot get past a black screen with a "SBL Error! rdx_init!" in red text, and "upload mode" in yellow text. Still cannot access Recovery Mode, but Download Mode still works.
I did a little Googling on rdx_init errors and it seems I need a firmware dump from another G930U or something like that...any ideas on how I can proceed?
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
STA1NL3SS said:
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
Click to expand...
Click to collapse
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
gabeblack said:
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
Click to expand...
Click to collapse
I thought I had one in my phone, but I don't. If you look at the thread where you downloaded the Root_V12, you will see it. It's near the end of the thread somewhere.

Galaxy S7 got stuck before boot. Need I to wait for the battery to die?

Hi, it is an older device so you might have experienced everything possible.. so,
After a long time of trying to fix that phones mind, I wiped everything avaible in TWRP
multiple times(got mad). Last thing was data.
That way I went from a bootloop to an active nothing.
Phone does not react to any command, it does not react to USB charging or on PC.
That's the case a few months back, the phone halfway in the trash and I bought
myself a iphone (hate it).
I put the Galaxy S7 on a charger today and it starts immediatly in to TWRP.
From there I tried to install a ROM that's left on the SD card, which forced
a restart into TWRP. Into download mode I managed to install the stock Oreo ROM via Odin.
It went through like a charme, all green. PASS!
The phones screen is black and does not react to any command, nothing.
I had "auto-reboot" activated.
The phone is active it's warm and I'm waiting for the battery to die again, to restart.
..meanwhile,
Can you give some advice please?
Why would the phone have struggle with the boot with stock rom installed.(which has worked before,no updates installed)
When should I install TWRP?
When do I install what kernel?
Last thing running was the LightROM with moro kernel with nothing tweaked.
Also. The issue why i deaded the phone was a camera/flash thing, where I could only take pictures with flash activated.
Front and back camera. On all camera apps, I couldnt scan my ID for banking due to that.
Also on different kernels and different ROMs including the Samsung stock.
Why would that be
Could not accept...
Jvers said:
Hi, it is an older device so you might have experienced everything possible.. so,
After a long time of trying to fix that phones mind, I wiped everything avaible in TWRP
multiple times(got mad). Last thing was data.
That way I went from a bootloop to an active nothing.
Phone does not react to any command, it does not react to USB charging or on PC.
That's the case a few months back, the phone halfway in the trash and I bought
myself a iphone (hate it).
I put the Galaxy S7 on a charger today and it starts immediatly in to TWRP.
From there I tried to install a ROM that's left on the SD card, which forced
a restart into TWRP. Into download mode I managed to install the stock Oreo ROM via Odin.
It went through like a charme, all green. PASS!
The phones screen is black and does not react to any command, nothing.
I had "auto-reboot" activated.
The phone is active it's warm and I'm waiting for the battery to die again, to restart.
..meanwhile,
Can you give some advice please?
Why would the phone have struggle with the boot with stock rom installed.(which has worked before,no updates installed)
When should I install TWRP?
When do I install what kernel?
Last thing running was the LightROM with moro kernel with nothing tweaked.
Also. The issue why i deaded the phone was a camera/flash thing, where I could only take pictures with flash activated.
Front and back camera. On all camera apps, I couldnt scan my ID for banking due to that.
Also on different kernels and different ROMs including the Samsung stock.
Why would that be
Could not accept...
Click to expand...
Click to collapse
OK so what you've done is correct flashing stock (which includes stock kernal). You have to make sure the stock ROM is correct for your device and region or it will not start.
It's not unusual to have to flash it twice with Odin.
Next up you don't need to wait for batt to die to restart. Press volume down+home+power and keep them pressed until phone restarts. Should now be in download mode, reflash correct ROM with Odin. TWRP is wiped off the phone when you flash a stock ROM.
If it doesn't go through the boot up/freezes/ does nothing etc. You need to "wipe cache" then reboot from the recovery menu.
Press and hold volume down+home+power. As soon as the screen goes black move your finger to volume up (it may take more than one attempt). Once your in recovery menu use volume up and down to move through options and power to execute. Wipe cache then reboot and allow the phone to go through all the reboot stuff. It can take a few minutes just leave it alone. It will also reboot a couple of times.
If it does nothing after 15 minutes then start again and repeat the process.
Thanks for reply.
The Phone was off for a day and after charging for 1h it still does not react to any command. Vol down + home + power does nothing. Same with vol up.
Is there a way to force a boot? Even if the PC does not recognize a device on usb?
I Tried the commands 30 secs each, plugged in and off. Also usb port is not broke since the phone is getting temperature after a while charging..

Question Bricked can't Seem to access anything

Hi everyone.
Last night my phone ran out of power and when I charged it back up it wouldn't boot at all, so this morning I decided to try and fix it but I think I have just screwed it up even more to the point that its completely bricked.
I could still access TWRP and tried to reinstall the firmware and flash TWRP through the checkbox execpt about 1 minute in the screen went off due to the time out, but the screen wouldn't come back on at all so I left it for an hour just in case if it was still running in the background, after this time I hard restarted the phone and entered TWRP again and but it didn't install the firmware properly and my computer wasn't reading the phone properly so as a test I tried to swap bootloader from A to B stupidly and now I can't seem to access anything, only thing I can do is the menu where it says start, power off, recovery mode and restart bootloader. Pressing any of these settings seems to just put me back in to this menu again.
When plugging in the phone in to the PC it make's no noise at all as well.
Have I completely hard bricked my phone? Or is there a way to fix it?
Thanks Ben
All fixed I flashed the RAW firmware

Categories

Resources