Experiencing my first hard brick.. I should of stuck with stock but naturally wanted to flash a new rom, rooted n900a with safe strap running lollipop oc1. Been back and forth with safe strap, well wasn't paying enough attention on my last go around, instead of wipe, i formatted data , typed in yes, and phone just turns off and goes into a constant bootloop. I fire up odin, flash nl1 kernel and that gets me back into safe strap, but i am unable to mount data. Sooooooooo i go ahead and just format again, hoping this fixes the partitions.. it went smooth, i went to reboot, and reboot into recovery.. phone turns off and thats it.. nada.. zip.. no download mode, no recovery, no signs of any life whatsoever on the phone...
i guess my question now at this point is it totally gone? am i missing something to fix this?
http://forum.xda-developers.com/showthread.php?t=2476353
or is this my only possible solution?
Related
So I'm trying to get my VZN Galaxy Tab back on its feet. After trying to get Gingerbread in it so I can use Netflix - and failing - I'm going through a lot of motions.
Okay. First I rooted it with Super One Click. I should have been happy with that, but noooo. Then I tried flashing GB on it (I wish I can remember which ROM I started with...it's a mess. I think the pit file was gt-p1000_mr? Does that sound right?).
When that didn't work, I went to the much-cross-posted procedure for returning it to stock using Heimdall and SCH-i800_VZW_stock. Tried it five times. Each time, it booted into the Galaxy Tab/Samsung logos, then a fast glimpse of scrambled letters for a second followed by twinkly music, then black nothingness. It would then bootloop. I attempted to boot into recovery to wipe data/cache, but I couldn't get there. Vol-Up/Pwr just brought up the logo and scrambled video again.
Since I was still able to get into download mode, I tried flashing another ROM...this one the "P1000XXJQ1_P1000XXJQ1_P1000XXJPZ" method. With this, I was able to also flash CWM so I have SOME recovery mode. Sadly, booting brings up the GT/SAMSUNG logos and I get the spacey animation, but after that, again - blackness. This time, however, the Menu/Home/Back/Search buttons light up, so something's happening in there.
Also, booting into CWM, I cannot get my sdcard to be recognized. I tried different cards, so there's something goofy with the slot itself, I'm guessing.
So nothing is really working, but since I can get into CWM and also download modes, I'm holding out hope that this is not completely bricked.
I just need to find the right method of getting it back to a functioning tablet. If anyone has any suggestions, I'm all eyes. Thanks so much.
UPDATE: I tried reflashing stock using the tried and true method. But this time, I went in and flashed CWM replacing the stock recovery which never worked for me. I got the Galaxy Tab/Samsung logo, and at long last, the animated VZW logo. Then it would bootloop there. I booted into CWM recovery and wiped the data/system and the cache from the first page. It still booted and bootlooped the same. This time, I booted into recovery, went to the mounts and storage section and formatted the system, data and cache. Opening logo only. CWM again, and got a whole bunch of "cache missing" messages. But I think I'm getting closer. Back to work.
UPDATE II: So the farthest I can get is the animated VZW logo using the combo of the stock flash through Heimdall, then flashing CWM with Odin. Still no sdcard access. Anything I should try here? Thanks.
same question here
Did anyone figure out how to restore Verizon tab?
hi, yes i will admit i am still very new to the whole rooting/flashing/mods etc, but i f-ed up my captivate bad... first i should tell ya how i got to the point where i am now... (dont worry will be the abridged version):
-got phone, couldnt sideload apps
-rooted phone and enabled install of sideloaded apps
-tried to backup rom/phone with clockwork, learned that i had to flash modded kernal
-backed up and flashed new kernal (flashed clockwork recovery & backed up rom)
-learned about voodoo, so reflashed a voodoo kernal
-started to have issues with static, speaker volume, basically anyone who called me or i called couldnt hear me and was all static
-reflashed different kernal
-got ballsy, backed up rom again, and all user/system data, and attempted to flash custom rom (firefly3.0)
-flash failed... tried to reflash, failed again... error said parameters did not match
-tried restoring original backed up rom, failed again, and again...
-then, boom, phone boots up and am able to make calls and receive them, cant send text though..
-scoured the forums, and tried to fix phone/restore to stock.
-flashed odin, and then BRICKED!!!!
*NOW ALL PHONE DOES WHEN I TURN IT ON IS BOOT TO ATT SCREEN AND THEN OFF, THEN ATT SCREEN, THEN OFF.. TRIED BOOTING INTO RECOVERY, DOWNLOAD MODE AND STILL NOTHING WORKS...
wondering what happened, or what i did wrong, what i can do to fix my phone (if possible)????
any of u wicked smart devs care to help out a little 'ol noob?? please
obviously its not bricked!
i hate that misnomer. you are bootlooping....
you need a jig at this point if normal means of getting into download mode do not work
(power down phone, pull battery. put battery back in, and while holding vol up+down, plug into computer.) if that doesnt put you in download mode, you definitely need a jig.
once you get that jig, flash a custom cwm kernel, then try flashing a new rom. you dont need to boot into stock, which is what you are stuck on now.
BY DEFINITION: A BRICK IS SOMETHING THAT NO LONGER POWERS ON, AT ALL
Damn beaten to the punch.
Sent From My Captivating Shanna, yes I Named My Phone get over it.
hi all
i ahve not installed a custom rom on my note, but i have rooted it and installed abyss note kernal. everything has been working fine for months and months with this, all of a sudden last night i saw my phone was off, i went to switch it back on and the boot screen just keeps looping and i have no idea why.
I can get into recovery (it says odin mode) and the phone is connected to odin on my PC.
i obviously would like to get the phone working again some how, but if at all possible i would like to keep everything that was on there as i was using the phone as a usb drive to store my college work on and dont want to lose it.
any help would be appreciated
Are you able now to start your phone???and if not, can you enter in download mode(pressing vol down+home key+power key)
Sent from my GT-N7000 using xda app-developers app
ok i just flashed a stock gingerbread rom from odin. odin said pass (successful) but i am still having boot loop i thought flashing a stock would have sorted it.
i did the flashing by accessing download mode and connecting to odin on my pc
please help i just want a working phone
htchd2rules said:
ok i just flashed a stock gingerbread rom from odin. odin said pass (successful) but i am still having boot loop i thought flashing a stock would have sorted it.
i did the flashing by accessing download mode and connecting to odin on my pc
please help i just want a working phone
Click to expand...
Click to collapse
hmmm so what your trying to say is that just right after reflashing to stock GB your phone went into a bootloop after? You didn't have any chance still of restoring your backups did you? it just rebooted right after flashing back to GB?
i didnt flash any rom before, i was just on stock what came on the phone. the boot loop randomly happened last night. i have just now flashed a stock GB rom through download mode and odin.
the boot loop is still happening even after i just flashed a stock rom
did you restored your backups back on your phone? if you did.. try not to.. just observe it for now.. all stock.. no datas at all, turn off your phone(in airplane mode) and see if your still getting the bootloops.... if your still getting it then I'm doubting you may have a corrupted data partition inside your phone.
Mate, if you're on stock GB (NOT STOCK ICS!!!!), then you can safely go into Recovery Mode and full wipe:
- Hold Power + Volume Up + Home button alllll the way until a weird recovery, safe-mode like menu appears
- Navigate using the Volume Keys to "Wipe Data/Factory Reset"
- Use Home button as ok and do that
- Navigate to "Reboot System"
And you're done and safe, no worries
i didnt restore any backups as i didnt have any baackups. i cant access the phone at all it just boot loops only. i think it is a corrupted data partition as i have flashed a stock rom and it still boot loops. i dont know how it happened though as i didnt do anything i just pulled it out my pocket and it was turned off, i tried to turn it back on and thats when i got the boot loop
htchd2rules said:
i didnt restore any backups as i didnt have any baackups. i cant access the phone at all it just boot loops only. i think it is a corrupted data partition as i have flashed a stock rom and it still boot loops. i dont know how it happened though as i didnt do anything i just pulled it out my pocket and it was turned off, i tried to turn it back on and thats when i got the boot loop
Click to expand...
Click to collapse
Make sure you hold on to the buttons for long, 30 seconds to 1 minute.
in my recovery i dont have any options it just says odin mode
i went into the proper recovery and did a wipe data factory reset, it worked!!!!!! thankyou!!!!!
htchd2rules said:
i went into the proper recovery and did a wipe data factory reset, it worked!!!!!! thankyou!!!!!
Click to expand...
Click to collapse
Most Welcome!
Just remember to press thanks!
One more thing... Please make sure you know about recovery and/or download mode, about CWM, stock and custom ROMs + kernels before flashing
It will turn the experience of customizing your Note into something really pleasurable, not a teeth-chattering experience Believe me, I know.
You can check out the stickies in every thread + you can check out some articles either here on XDA or "Android A-Z" that talk about CWM (Clockwork-Mod Recovery), Rooting and that sort of thing.
Best of luck to you!
Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..
TabascoTX said:
Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..
Click to expand...
Click to collapse
I just jumped in and read your post. unfortunately, I had no chance to reply to you after I read the last line But it's nice to know my tools is helpful.
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
You didn't mention how you tried to install the stock ROM . Did you use Odin?
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Nabeel mhd said:
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
Click to expand...
Click to collapse
hi OP,
did you find any solution to your problem?
Hello all. I'm also pasting this in the T-mobile thread in case it can be of benefit to someone. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
chrismcnally123 said:
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Click to expand...
Click to collapse
Thanks sir! I have the same issue! it's working now after replace the battery