Hi!
I have an absolute stock Samsung S9+ and I don't have a lot of knowledge of all this, but since this morning my S9+ maybe became an expensive paperweight.
Woke up, official Samsung update avalable and I press update. This usually takes a while and I go on with my day not paying attention. Quite a while later I notice that the phone is stuck at the Samsung screen and the LED is slowly pulsing blue.
Forced restart and again stuck at the Samsung screen.
A little bit of google and I get into this weird terminal start thingy (Power, Bixby, Volume Up).
Code:
Android Recovery
samsung/star2qltecs/star2qltecs
10/QP1A.190711.020/G965WVLS9FTL1
user/release/keys
Android Recovery
samsung/star2qltecs/star2qltecs
10/QP1A.190711.020/G965WVLS9FTL1
user/release/keys
Use Volume up/down and power.
!! CAUTION !!
Not enough storage resource.
Perform "lacking storage booting"
--------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SDCard
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
Repair apps
I tried Wipe cache partition - nothing.
Is there any way to bring it back to life without loosing all the data???
Samsung S9+
Canada/Rogers
Latest update.
That's all I know.
Any help is much appreciated!
This may not be much help.. But since it was a official update, that caused this issue.. I would get a hold of Samsung themselves.. Or go to the nearest store of your carrier and see what they can do.. I installed mine today, and not having any issues. Sorry to hear you are having this issue.
Related
Hi,
I tried to root my phone and install jelly bean 4.1.1 rom but f*cked up.
I used the wrong rom (for Verizon S3) and soft bricked my phone.
Worked 3 hours to get it back to a functional state.
However, since this happened the following problems occur:
Overal performance is a lot less smooth, I installed a stock ROM + CWR.
When booting, it often has problems at the "Samsung" logo, laggs etc...
Worst: It takes about 2 seconds for the lock screen to pop up EVERY time I turn the screen on.
I made a video to clarify what I mean: (can't link because new on forum, search on youtube for "Slow unlock screen Samsung Galaxy S3"
This makes the phone pretty useless imo since it drives me crazy to wait this long for just the screen to pop up.
Any help would be appreciated.
What would be the best course of action?
Install a -as close to stock as possible- ROM and start over again?
Or can I just wipe whatever's on there and flash/install a new ROM?
Thanks in advance, I'm freaking out because I'm afraid I just threw away 500€
Few steps to possible recovery as I have faced the same problem before....
1. download any rom like OMEGA V19 put it in root of the external sd card.
2. boot in CWM
- factory reset
- wipe cache partition
- go to advance
- wipe dalvik cache
- wipe battery status
3. install the omega rom.
4. remove the battery
5. press VOL UP + home button + power key to enter CWM
- repeat step no. 2
6. reboot.
It should solve the problem buddy... and bring your phone to a normal state...
Find the official firmware for your region..from here
Unpack the zip and use the md5.tar file..
Boot your phone in Download mode..vol down+power+menu
Open Odin and select the tar file as PDA
Start..
If you are stuck at the boot screen..hold vol up+menu+power to go to stock recovery..wipe data factory reset from there then reboot..
Your phone will be as good as new..
I have got a Samsung Galaxy Note GT N7000. My friend has actually made an update (claims to), and now my phone won't boot! I get the first Screen as
"Samsung Galaxy Note GT N7000" after which the Samsung logo splash should follow, but simply doesn't. All I get is a black screen. With the Volume Down + Power + home I get the "Downloading Do Not Turn Target off" and it just stays that way, I don't really think it is actually downloading anything. With Volume Up + Power + Home I get "Manual Mode" of some recovery mode. Wherein I have
Reboot
Update from External SD
Update from Cache
Wipe External SD
Wipe Cache
Reboot just simply does the same, I get a black screen after Samsung Galaxy screen. What could be wrong with my phone? I have no idea, help please.
Edit:
I have Odin downloaded, and in the Download Mode, I get that COM:ID port added, but I have no clue where to proceed from there on.
Imman07 said:
I have got a Samsung Galaxy Note GT N7000. My friend has actually made an update (claims to), and now my phone won't boot! I get the first Screen as
"Samsung Galaxy Note GT N7000" after which the Samsung logo splash should follow, but simply doesn't. All I get is a black screen. With the Volume Down + Power + home I get the "Downloading Do Not Turn Target off" and it just stays that way, I don't really think it is actually downloading anything. With Volume Up + Power + Home I get "Manual Mode" of some recovery mode. Wherein I have
Reboot
Update from External SD
Update from Cache
Wipe External SD
Wipe Cache
Reboot just simply does the same, I get a black screen after Samsung Galaxy screen. What could be wrong with my phone? I have no idea, help please.
Edit:
I have Odin downloaded, and in the Download Mode, I get that COM:ID port added, but I have no clue where to proceed from there on.
Click to expand...
Click to collapse
hey man, i fall into this problem and can't solve it . please if you or anyone can help me because i can't solve it and tried everything. help me if you can!
Your phone's soft bricked. Signup and download N7000 stock ROM (your region) from Sammobile.. Reflash stock ROM using Odin.
fall into same problem
i have fall into the same problem can u help me because it does not boot into custom recover
hermitabby said:
i have fall into the same problem and when i use Odin mode to install custom ROM it does not start, but it show betry charging then try to boot and flash black screen and back to charging mode if you plug the phone to PC or charge it does the same
Click to expand...
Click to collapse
Odin to flash a custom ROM? Well, that's new. Since when they stopped using custom recovery?
i will be much appreciate if you give me good way to fix my device because now it does not even start in custom recover
Wipe data [factory reset]
Imman07 said:
I have got a Samsung Galaxy Note GT N7000. My friend has actually made an update (claims to), and now my phone won't boot! I get the first Screen as
"Samsung Galaxy Note GT N7000" after which the Samsung logo splash should follow, but simply doesn't. All I get is a black screen. With the Volume Down + Power + home I get the "Downloading Do Not Turn Target off" and it just stays that way, I don't really think it is actually downloading anything. With Volume Up + Power + Home I get "Manual Mode" of some recovery mode. Wherein I have
Reboot
Update from External SD
Update from Cache
Wipe External SD
Wipe Cache
Reboot just simply does the same, I get a black screen after Samsung Galaxy screen. What could be wrong with my phone? I have no idea, help please.
Edit:
I have Odin downloaded, and in the Download Mode, I get that COM:ID port added, but I have no clue where to proceed from there on.
Click to expand...
Click to collapse
Even i faced the same issue on factory firmware. And was able to get my phone started after wiping the cache and data in recovery mode.
i have the same issue with you. It's solved by flash new rom.
pratik069 said:
Even i faced the same issue on factory firmware. And was able to get my phone started after wiping the cache and data in recovery mode.
Click to expand...
Click to collapse
Thnks. Getting a little bit nervious (ive been having a little too much fun putting different roms...and $%$#% was ment to happen...). So that did the trick.
ODIN <--- Stock Firmware <--- Stuck on Logo <-- Recovery <--- Factory Reset and Cache...
Presto...working again!
Thnk you
Hey guys,
I just upgraded to Revolution HD 32.0 (coming from 31.0).
Here's what i did.
Boot into recovery.
Clear cache+dalvic-cache.
Install zip from sd-card (select revolution hd 32.0)
Started Aroma installer, left everything pretty much default, just removed some of the samsung junk.
After the install was finished i cleared the cache again and rebooted the device.
It started with the start up logo and after a minute or so "Android upgrading..." with the applications counting.
After that it shows "Finishing boot"
Then nothing, it stays at that for like 5 minutes, then reboots and stays stuck at the samsung logo.
So i decided to boot into recovery, whipe caches and fix permissions and reboot again.
Same thing happened as before.
So i wanted to do a full clean install of the rom, wiping all userdata.
Surprise! Can't get into recovery or download mode anymore.
Took out battery for a few minutes and put it back in.
Still can't access download mode or recovery with vol+menu+pwr...
Does anyone know what's going on, or better, how i can possibly fix this?
I have no idea how to access my device now to make changes...
Thanks a lot!
If you can't get into bootloader with vol down, home and power button then you have a brick, service centre repair required.
Worth trying a USB repair jig to get download before paying for a repair .
jje
My device details: SGS3 T999, rooted, running Jellybean 4.3 on a liquid smooth ROM. Its a year old and has been a solid performer up until now.
My device is stuck in a cycle where it gives a quick vibrate, then SGS3 splash screen with white letters, then black screen, then tiny blue "Recovery booting..." words in upper left of screen, then black screen with couple vibrations, and around and around it goes in the same repeating cycle.
Just before it started I had taken the following actions: Dumped the following 2 files onto my EXTSD card (cm-11-20131217-NIGHTLY-d2tmo.zip, gapps-kk-20131119.zip) from my PC, booted phone into recovery mode using TWRP, did a factory reset wipe (success), cache wipe (success), dalvik cache wipe (success), flashed the NIGHTLY file (failed), flashed the gapps file (failed). At this point I should have sought some support. Fool! I next did a reboot step still in recovery mode. Without the reboot happening a message came up stating Superuser permission had been broken (the best I can remember) and the option to have TWRP repair the permission. I opted "yes" to repair. Then the loop started that I can't escape.
I have pulled the battery multiple times, tried a regular boot up, tried a recovery boot up (up volume+power+home) dropping the home button after a few seconds. Nothing is working. Prior to the above steps I backed up everything on the device. So I have backups to use if it can be done. My best guess is that I failed to update my CyanogenMod or TWRP to the very latest versions and it caused this hang up. Otherwise, I don't know what to do and need any help I can get.
Has anyone had this issue or heard of anyone who has and have any helpful suggestions, tips, ideas, etc..?
Thank you in advance. This is my first XDA post. Please forgive and offer tips if this thread needs any scrubbing.
I've had a few similar events for a few different reasons.
I would suggest booting into recovery but it seems you have tried that already.
If the device is plugged into a wall or pc, unplugg it, that has seemed to cause and fix boot issues for me before.
Other than that, I dunno, if you can't get to recovery or fastboot, I dunno...
I have an unlocked (but not rooted) ATT S4 active that I have been using on Cricket.
It now refuses to boot; just displays the ATT globe.
I can hold vol-down, power, and home and boot into a screen the warns me of the danger of booting a custom OS.
I can also hold vol-up, power, and home and, after a blue “recovery booting” appears, boot into a screen which at the top says
Android system recovery
LRX22C.I537UCUC0C7
And then the selection menu:
reboot system now
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery logs
Enable cp logging
Disable cp logging
I have tried wiping both the cache and the data (factory reset) to no avail.
Although it could be a hardware issue, I suspect it had to do with an app that started loading from a repo other than Google. I stopped it but it started generating errors; when I tried to reboot, it wouldn’t.
Since it is practically bricked, I see little downside to loading a later ROM, even with no ability to backup what was there. I have installed Android development and ADB on my Linux box but don’t see how to proceed. All of the help postings I see assumes that I can root the machine after the machine boots; I never get that far.
I have looked for help but haven’t seen anything. (I’ve tried to RTFM!) Can anyone point me in the right direction?
Thanks.
-Jack