Database Develop

[Q] Stuck after boot animation. No Recovery/Download

Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!

cumanzor said:
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
Click to expand...
Click to collapse
Did you ever get this problem fixed? The reason I ask is because I'm in this same situation.

We seem to be having the same problem also... Nothing has worked for me so far
http://forum.xda-developers.com/showthread.php?t=960419

Pull your battery, pull your sd card, hold the volume button and plug in the usb cord, this will get you into download
Sent from my GT-I9000 using XDA App

Keep hope alive glaze!
Sent using XDA App

Im going to get a jig hopefully all goes well.

[Debricking] Hang at samsung animated logo

Hi everyone, I spent all day trying figuring this out, even if probably the solution was really stupid, so I thought of doing a little post for future reference. If you have no time for my babbling, feel free to go to the short version (I wanted to put a link here, but I still have to learn how to do it and it's almost dinner-time...). If this post happens to be a duplicate feel free to remove it.
=== Whole story ===​A week ago I got a Galaxy SIII mini N (GT-I8190N) and just kept it that way because I didn't had a win pc to use Odin. Yesterday I finally came back to my parents, powered up the win machine and followed an awful lot of different guides to manage to install the Macław CM 10.1. So, for short: installed CWM touch trough Odin, installed the root zip trough CWM and finally installed CM 10.1 & Gapps trough CWM. Here I did my first mistake: the first thing I did after installing CM was formatting internal and external SDs. Where the Nandroid backups of the working Samsung firmware were.
After some experiments I decided to go back to Samsung stock (reason 1: no gtalk, only hangouts, reason 2: NFC support still in development, reason 3: trying to restore SMS from a SmsContactsBackup I (luckily) had I messed up the SMS DB so much the app couldn't start). NOTE: Macław's ROM is amazing, I'm surely going to try it again when NFC support comes up. Sadly, I am an idiot who thinks he knows better so I ignored all the warnings of doing a wipe of data/cache and restoring the Samsung original recovery. I just went to Kies for a "Firmware upgrade and initialization" instead.
The result was a disaster. The phone rebooted but hanged at the Samsung animated logo. After a lot of hanging I decided to redo a Kies firmware upgrade. Obviously I had no luck. So I switched to Odin, took the image Kies downloaded (since I didn't want to wait an hour and an half to the download from unofficial sites) and flashed. And flashed. And flashed. Always without success. After a little bit I decided to try changing Odin options (repartition, NAND erase etc). Still nothing. So I started trying all the guides out there (here?): repartitioned with a PIT file, reflashed a CWM, reflashed stock recovery, various combinations in different orders of all the "solutions" above... You guessed right: nothing worked.
Since I read somewhere that there are Galaxy have 25 partitions (what the ****???) and saw that Odin was flashing only 8 or so I decided that something some the other partitions was missing, so I switched to Heimdall. Since the Win version didn't want to start, I did a fresh Ubuntu 13.04 install (lucky for me I happened to have an empty HD waiting to be installed on the server that I could use for an afternoon ), installed Heimdall, started figuring out how it works, realized I needed a custom-made package (nowhere to be found, apparently), started looking into the partition scheme to understand where the problem could have been... Finally I realized my skills are a tiny little bit inadequate for that and found a reference somewhere to a "hard reset".
In all this it never occurred to me to try and enter Samsung recovery. The first thing I noticed was that it didn't start right away with VolUP + Home + Power, but I had to keep them pressed a lot longer than what it's needed to go in download mode. In practice the SIII mini logo went up two times before showing the android with the open belly. Then finally the recovery appeared, I navigated to wipe data and cache with the volume buttons, accepted with the power button and rebooted. Thus I finally had a Samsung animated logo that was followed shortly by an "installing applications" loading bar and the first start configuration tool.
So, what I learned today:
1) Samsung tools are not necessary evil
2) if you don't understand what you're doing and you're doing it anyway, be prepared to suffer
3) we probably need a unified guide/troubleshoot the whole community can edit (wiki-like). Threads are great, but it's really easy to miss the obvious (for the whole time I was sure it was a bootloader problem, never occurred to me that there could have been some data left... also because I did a NAND wipe through Odin and I thought that was supposed to wipe personal data...) and often propose a solution without explaining the rationale behind it. I'm sorry if there's something like that out there somewhere, I wasn't able to find it
Thanks to you that bore my babbling
And now it's time for:
=== The short version ===​
Problem: I messed up doing a Kies reset after installing a custom rom (CM10.1) without the dues precautions; the result was a phone caught in an endless loop at the Samsung logo. Installing firmware with Odin didn't solve a thing.
Solution: I booted in recovery (volume up + home + power) and wiped data and cache. After that I rebooted and waited a little bit, a progress bar appeared and everything was fine (well phone was at factory default but at least now it's working ).
I hope all of this could be useful to someone

Dumb, Dumber and me

N900A (AT&T so no custom recovery).
Rom de la Vega worked fine, got root. Loaded some apps, some needing root, some not. Didn't trigger the 0x1, it''s still 0x0.
Everything worked fine until ... well, I don't remember exactly what I did, but it wasn't anything close to "stupidest move ever made". Phone now boots to the Samsung logo with the circles orbiting each other, then goes to the AT&T symbol with a few (about 4) bars of music, and stops. No soft keys (they do flash on for about half a second) and the home key does nothing.
If I wait a few seconds, it reboots, back to the unlocked lock, the "Custom", the Samsung orbits, etc. I assume that's a boot loop.
ADB doesn't see a device. I can boot into recovery (standard AT&T thing), download or standard boot, but ADB doesn't see any device. (The computer is set up correctly - plug my wife's N900A into the same cable and Kies reads it immediately.)
I've tried N900AUCUBMI1_OneClickBin and it seems to run properly, running Odin 3.09 after about 5 minutes. Press Start and the files start downloading. (Port 22, but I''ve learned not to argue with Win7 serial port assignments.) It finishes with all files listed and a green "passed". The pnone boots into the little green guy, then into the boot loop. This is with the original 16GB microSD, a clean 2GB microSD or none at all. I've cleared cache/system or not - same results.
I can't finish the rest of the procedure, because I can't put anything into internal storage - because the computer doesn't see the phone.
I'm at the end of my knowledge. I don't know how things are laid out in Android, so I don't know what to flash or if there's anything I can flash to fix anything.,
Oh - nothing shows on the computer - no Phone and no Card. If USB debug got turned off, I don't know of any way to turn it on from outside. I can't run any Android apps, of course. It I have to, I can install Linux on a partition on this laptop, but is there something I can do to just get back a plain working (preferably rooted) Note 3?
If not, I'm going to have to go back to the big blue and yellow place and feign stupidity, and hope all the boot looping articles will convince them that this is just another one.

You didn't update to the latest MJ 5 firmware, did you? ,accidentally and then try the one click to mi 1?
Sent from my SAMSUNG-SM-N900A using Tapatalk

tdamocles said:
You didn't update to the latest MJ 5 firmware, did you? ,accidentally and then try the one click to mi 1?
Click to expand...
Click to collapse
That's possible. I''ve been looking for links to MI5 and MI9 but with all the deleted links, I haven't been able to find any. All I have is MI1 and the MI9 file with the .tar.md5 files, which I'm reluctant to use, in case I cause a hard brick.

[HELP] I changed some of my system files and i can't turn my phone on!

Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/goo...x-bypassing-pie-security-check-t2797731/page1

You are booting into recovery. I think when the android is laying down you hold power and press the volume up key. You will probably have to restore the backup of the file you changed (you did back it up right?).
If that doesn't work, you will most likely have to flash your system partition with the stock one and root again.

Red_81 said:
You are booting into recovery. I think when the android is laying down you hold power and press the volume up key. You will probably have to restore the backup of the file you changed (you did back it up right?).
If that doesn't work, you will most likely have to flash your system partition with the stock one and root again.
Click to expand...
Click to collapse
Ill try flashing the stock one, see if it works, thank you

Samsung Tab s2 stuck booting into TWRP

Ive been lurking on this forum for a while but ive finally hit a wall I cant find an answer to
I successfully rooted my tablet using magisk and TWRP about 4 months ago, everything was going great. about 2 months ago my tablet booted up into TWRP and would not get out, no matter what I tried. eventually I fixed it by wiping everything and reflashing stock ROM from ODIN and going through the root process again, not a big deal. cut to 2 days ago, my tablet restarts and boots into TWRP again and wont boot into system, basically seemed like the same as before, until I plugged it into my computer
For some reason, my tablet no longer connects to ODIN or my laptop at all. Ive used the same cable and different device and same usb port and it worked just fine, ODIN picked up the connection and everything. Ive updated and unistalled and reinstalled drivers for all the USB ports and I dont think that is the issue. I even deleted and reinstalled ODIN but still nothing.
I thought maybe there was some setting on the tablet that might be preventing a connection to ODIN, so I wiped the rooted ROM off the tablet (im new to this, dont know if this was a bad idea) and tried again but got nothing. now with a soft bricked tablet I got a micro SD card, put a TWRP flashable version of the ROM onto it and plugged that into the tablet and flashed this new ROM onto the tablet, and that worked from what I can tell (system folder went from like 8mb to 17000 or something) but I still cannot get the tablet to boot into system.
I can access download mode (there appears to be two versions, one where it just says downloading and another where a bunch of text appears on the top left, some of it mentioning ODIN) and all the functions of TWRP, but ODIN does not connect and I cant get it to boot into the system.
TWRP version 3.1.0.1_ashyx
link to the post where I got the stock lite version of the ROM currently flashed to my tablet:
https://forum.xda-developers.com/tab-s2/development/rom-nougat-stock-lite-v1-t3746583
any help would be greatly appreciated, sorry for the wall of text.

Wish I had something useful to add. I'm having the same issue. TWRP 3.4.0.0 and LineageOS. I've had this issue forever. I flash a clean ROM, it works for a week or two, then I come back to it and all I get is recovery.
I can access Odin however.
Usually it takes wiping and installing a ROM to get the device working again, in fact it issue takes several rounds of that. But of course, in all of that I've lost my setup and some files.
Is there an actual solution to this?

On my T810 I'm having TWRP 3.3.1-0 with this ROM https://forum.xda-developers.com/tab-s2/development/rom-aospextended-rom-v6-7-t3979381
plus Magisk and Pico Gapps.
Of course it's only Pie and not Q, but working well.
3.4.4-0 not tested yet.
Once had an issue with black screen, but at that time I was using case with a screen cover.
Since that I've switched to TPU case only covering the back.
No more issues after that, perhaps it was a problem with FlipFlap like on other devices.