[Q] Help please-stuck at Samsung Logo - Galaxy Note 10.1 Q&A, Help & Troubleshooting

Hi everyone,
I was using Omega Rom v2.1 without trouble, then I decided to try Humberos Rom. After flasing it using TWRP it got stuck at the Cyanogen logo for 35 minutes without booting.
Because it didn't work and I did a backup, I decided to restore it and not use Humberos Rom. i went back to TWRP and everything is empty, I can't see nothing, I can't restore it or boot it.
I decided to flash a stock Rom as my only option using Odin. I tried Stock pre-rooted EUALAH2 from Entropy512. Odin flashed it but I'm stuck at the Samsung logo, no boot at all.
I need help because I can't live without my note 10.1!!!!!
Please move this post as necessary because I'm not sure I posted it in the right place.
Regards,
RM

Fix that will wipe data
lxjangels said:
Hi everyone,
I was using Omega Rom v2.1 without trouble, then I decided to try Humberos Rom. After flasing it using TWRP it got stuck at the Cyanogen logo for 35 minutes without booting.
Because it didn't work and I did a backup, I decided to restore it and not use Humberos Rom. i went back to TWRP and everything is empty, I can't see nothing, I can't restore it or boot it.
I decided to flash a stock Rom as my only option using Odin. I tried Stock pre-rooted EUALAH2 from Entropy512. Odin flashed it but I'm stuck at the Samsung logo, no boot at all.
I need help because I can't live without my note 10.1!!!!!
Please move this post as necessary because I'm not sure I posted it in the right place.
Regards,
RM
Click to expand...
Click to collapse
WARNING: THIS METHOD WILL DELETE YOUR DATA:
First flash Darkman's unofficial ClockworkMod via Odin. (instructions here: http://forum.xda-developers.com/showthread.php?t=2102677) Next, boot into recovery with power and vol-up, and tap wipe data/factory reset. After that finishes, tap mounts and storage, and then format system. When that finishes, hold down power and vol-down until the custom OS/ download mode screen comes up. From here, you can reflash the stock ROM you had via Odin. Everything should work properly, but as I said, your data will be wiped.

budzylikessoup said:
WARNING: THIS METHOD WILL DELETE YOUR DATA:
First flash Darkman's unofficial ClockworkMod via Odin. (instructions here: http://forum.xda-developers.com/showthread.php?t=2102677) Next, boot into recovery with power and vol-up, and tap wipe data/factory reset. After that finishes, tap mounts and storage, and then format system. When that finishes, hold down power and vol-down until the custom OS/ download mode screen comes up. From here, you can reflash the stock ROM you had via Odin. Everything should work properly, but as I said, your data will be wiped.
Click to expand...
Click to collapse
budzylikessoup, a million thanks to you...my beloved note 10.1 is back from the death!

I accept donations
Sent from my GT-N8013 using Tapatalk HD

Related

Assistance! ROM and Recovery both won't boot!

I was trying to install EagleBlood ROM to run Gingerbread on G2x, and followed all instuctions, installing ROM manager, using that to flash to their recovery, then deleting caches, then flashing the ROM. After a reboot, EagleBlood is stuck on a bootloop, displaying an image of and android surrounded by a sparkly blue circle. If I take out the battery and then try to boot into recovery, the recovery image is displayed for a while, but then resets and goes back to rebooting without opening recovery. I am very scared that I may have bricked my brand new phone and do not want to pay for a repair. Any help is very much appreciated.
XDvinSL said:
I was trying to install EagleBlood ROM to run Gingerbread on G2x, and followed all instuctions, installing ROM manager, using that to flash to their recovery, then deleting caches, then flashing the ROM. After a reboot, EagleBlood is stuck on a bootloop, displaying an image of and android surrounded by a sparkly blue circle. If I take out the battery and then try to boot into recovery, the recovery image is displayed for a while, but then resets and goes back to rebooting without opening recovery. I am very scared that I may have bricked my brand new phone and do not want to pay for a repair. Any help is very much appreciated.
Click to expand...
Click to collapse
I would suggest that you NVflash clockworkmod by reading the thread here. Once you do that, you can access your recovery via volume down and power. If you do not have CWM installed via NVflash, for now, you should be able to reset everything by pressing the volume down and power to restore your phone to a factory state.
Thank you very much for that tool! Booted up the recovery and am currently recovering from earlier today on the stock ROM. If this is my last post, it was a success!
XDvinSL said:
Thank you very much for that tool! Booted up the recovery and am currently recovering from earlier today on the stock ROM. If this is my last post, it was a success!
Click to expand...
Click to collapse
Now, when you install a rom through CWM, i would suggest wiping data (if you are switching between roms) and cache. This will prevent you from going into bootloops. I would also suggest after flashing a new rom, going into CWM > Advanced > Fix Permissions. You should now be golden.

[Q] Red Triangle, Dead Android

After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
ttakacs said:
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
Click to expand...
Click to collapse
When you flashed to stock you erased your recovery.. Reconnect to your computer and push a recovery onto your phone and you're good to go..
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
ttakacs said:
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
Click to expand...
Click to collapse
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Setting.Out said:
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Click to expand...
Click to collapse
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
ttakacs said:
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
Click to expand...
Click to collapse
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Setting.Out said:
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
ttakacs said:
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
Click to expand...
Click to collapse
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Setting.Out said:
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Click to expand...
Click to collapse
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
ttakacs said:
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
Click to expand...
Click to collapse
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Sent from my Nexus S using xda premium
Setting.Out said:
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Click to expand...
Click to collapse
I am too. Every method known to me (Odin, fastboot, adb) to flash a ROM, whether custom or stock, has failed to boot. Thanks for hanging with me on this; if you can think of solution I'll be glad to have it. Or if I solve it, I'll post here.

Need Help getting my phone working again!

Hi all,
I was running the new SaberMod Carbon ROM for a few days and decided I didn't like it so I tried to restore a nandroid back up of what I had been running before (rwilco's mostly stock). The phone wouldn't reboot after restoring the backup, it would start and then go right back to recovery. Then I tried just flashing the rwilco's mostly stock as new instead of from a back up, and that had the same results - said it was complete but when I selected reboot phone it just went back to recovery. So I decided to flash the stock tar in Odin, but that kept failing. Now I can't get into recovery, it says something about an update being interrupted. I can get into download mode, but the stock firmware keeps failing in Odin.
I am guessing here that my problem is that the SaberMod rom is based on 5.1.1 and the stock firmware for the G900P (as well as the other rom and backup I tried) are 5.0.0, and I remember hearing you can't go back to an older firmware version. Does this sound right? and if so how do I get my Galaxy working again?
TIA for all help and suggestions!
daniel3x said:
Flash the TWRP recovery in odin
After that enter in recovery mode and format system, data, cache, dalvik cache, sdcards.
Then put the phone into download mode, and flash with odin the last stock rom (OG1) but make sure you don't have selected the "reboot" option in odin
After you got your phone flashed, take the battery out put it again and enter in recovery mode, choose "wipe data/factory reset"
Then put your phone in download mode and flash again the stock rom (OG1) this time with the "reboot" option selected
After you flashed your phone the first boot takes some minutes (in the yellow screen), just be patient.
After this you should have your phone complety clean and your problem solved.
DOWNLOADS
Odin 3.10.7
Stock Rom OG1
TWRP 2.8.7.0
Click to expand...
Click to collapse
Try this
I have phillz recovery on it right now....can't get into the recovery though since it says a firmware update was interrupted. Would TWRP be better than phillz? and would flashing that get it past the firmware interrupted message?
I tried starting by flashing TWRP but that fails too....any other suggestions?
Can't flash anything in Odin, everything fails. Any other ideas before this thing goes for a swim in the sink?

Boot loop s7 G930F after twrp installation

Hi guys, not sure if I'm in the right thread (please move me if not admins)
I was running superman on my s7, I decided to clean out my phone by flashing stock firmware and then reflash a custom rom.
The stock flash went well as expected, checked oem unlock and USB debugging then I flashed twrp 3.1.1
My phone was then stuck on the 3 logo (I flashed h3g csc while stock flashing) for 15 minutes
So out of lack of patience, I rebooted my phone, now it's stuck on a boot loop splashing the Samsung boot image then resetting with a vibrate and this is constant.
I managed to open twrp on the phone and thought a wipe might be in order, did that and FAILED, without me rebooting it rebooted itself.
Then I tried to reflash stock firmware in Odin, again that failed.
Still stuck in a boot loop.
I know I've screwed up but any advice would be grand.
Thanks guys :good:
right, fixed the issue.
went into twrp, wiped the system by typing 'yes'
wipe dalvik, data and system.
rebooted into download via twrp and flashed stock rom again
works fine
all because i didn't uncheck auto reboot in odin when flashing twrp..... D'oh! :silly:
i iz idiot
stewie2806 said:
right, fixed the issue.
went into twrp, wiped the system by typing 'yes'
wipe dalvik, data and system.
rebooted into download via twrp and flashed stock rom again
works fine
all because i didn't uncheck auto reboot in odin when flashing twrp..... D'oh! :silly:
i iz idiot
Click to expand...
Click to collapse
I am somewhat confused with your writing, or you write the wrong information.
1. Wiped system in twrp as long as I know do not need to write "yes".
2. Twrp is not download mode, it is recovery mode
#Btw, this should not be in this section
Best regards,
Quick one for you, if you ever can't get to twrp after bootlooping. Press and hold power+home+vol up. Let phone reboot but keep holding buttons till it reboots a second time and then you will get download mode.
tHIS IS RIGHT SECTION FOR QUESTIONS AND DIALOGUES ABOUT s7, so proceed pls.

recovery broken after format system and reboot - how to unbrick?

It's an old device. I got it for free since it was just laying around in friend's home. Worked OK after factory reset with stock ROM. Wanted to upgrade Android.
Previously successfully flashed TWRP from andi34.github.io/recoveries_tab2.html for Samsung Galaxy Tab 2 GT-P3100 using heimdall on Linux. Could start the TWRP recovery. Then I followed FAQ andi34.github.io/faq.html
backup all important files (e.g. contacts) and store them on your MicroSD-Card or on your PC/Laptop
copy the rom and gapps you like to install to your MicroSD-Card (make sure Gapps match the Android version of the Rom!)
boot into your custom recovery
make a backup of your current running rom and store it on your MicroSD-Card or on your PC/Laptop (some of the following are named slight different depending on the recovery you use)
wipe cache
wipe dalvic cache
wipe/format system
wipe/format data
reboot your recovery once!
Click to expand...
Click to collapse
After reboot, I could no longer start recovery.
Perhaps I should not have formatted system?
Perhaps I should not have rebooted before flashing the ROM zip?
I can still enter download (ODIN) mode. Re-flashed the TWRP recovery. Rebooted. Still cannot enter TWRP. But can still enter download mode.
What do you recommend now?
Can I flash LinageOS ROM zip from andi34.github.io/roms_tab2_lineage.html using heimdall? But heimdall does not really support zip files? It's harder than that? Any guide for that?
Or do I have to re-flash the stock ROM? Can I flash the stock ROM using heimdall?
Get the stock rom for the device then use ODIN to flash the stock rom back, the stock rom should fix it as it also flashes the stock recovery back.
Did you reboot System instead of Recovery? What TWRP version was this? I also thought of scenarios like this.
Can you still boot to recovery (twrp)

Categories

Resources