I have a Galaxy Note 3 and a Galaxy Note 4. I encrypted them and it seemed to go smoothly on both phones.
However after boot, the Note 4 started giving me headaches.
Turning it on I see the usual CyanogenMod's animation for a few seconds then it jumps and disappears. then I see a white box saying Android is finishing booting, and then I'm presented with a pattern screen different than the one I used to see. This one lets me change the amount of dots. It also lets me make emergency calls. So I slide my pattern, I see "Checking" then it's just the same initial CyanogenMod animation. For ever.
With the Note 3 I saw the exact same thing but the second animation lasted just a few seconds. Now it is working fine. The Note 3's storage had around 100MB in data. The Note 4 has several gigabytes of data in it. I presumed it was still doing some work, so I left it in the animation screen for a few hours. When I touched it was burning hot.
It won't enter Recovery Mode. I tried flashing recoveries with both Odin and Heimdall. With Odin it seems to work but it won't boot into Recovery Mode. Heimdall always gives me an error. I tried flashing cm-12.1-20160316-NIGHTLY-trltexx-recovery.img, twrp-2.8.7.0-trltexx.img and twrp-3.0.0-0-trltexx.img with Heimdall and twrp-2.8.7.0-treltexx.img.tar and twrp-3.0.0-0-treltexx-treltexx.img.tar with Odin.
Update: I've managed to install TWRP 3.0. The problem still persists though. TWRP doesn't ask for password or pattern, which doesn't allow me to do pretty much anything. The only MicroSD card I have is only 256MB - usable 240MB - latest CM 12.1 nightly is 255MB - so I can't even flash a new ROM! I'm surprised TWRP doesn't have a way to decrypt the storage. I very much hope I'm missing something.
Update 2: I've managed to flash a few different ROMs via ADB Sideload. I still can't get access to the data partition at all. I can't even format it! I'm getting quite desperate at this point.
Please, help!
I guess you could try a complete repartition using a pit file.
http://forum.xda-developers.com/showthread.php?t=3282641
I flashed a stock ROM. I genuinely thought it would completely erase the entire phone memory, but it didn't. as soon as it finished booting I saw the pattern decryption screen, but it just wouldn't accept my pattern.
I flashed another TWRP 3 again, went to that scary screen and wiped, and formatted, and erased, and did everything it allowed me to do, as I was sick and tired of that drama. flashed some CM to it and was done with it.
never trying to encrypt that thing again. Android's openness is too chaotic: too many OS variants, too many vendors, too many minor model variations, too many non-standard stuff going on. the result is it's unlikely someone else will have the exact same problem, with the same model, the same OS. I'm done.
Related
So I've been having this strange issue for a year now, where I want to upgrade my SM-T530 (Tab4 10.1 wifi) to the stock Lolipop (5.0.whatever) ROM in order to get the damn kernel updated so I can access all these wonderful custom ROMs (Stuck on CM 12 atm...).
But whenever I flash a stock ROM for my model, it seems to freeze the screen after the boatloader. As in, everything seems to be working, sound and touchscreen, it just doesn't update/refresh the screen. Basically, the same behaviour as described in this post.
So here's the steps I took, in the hope that anyone can point me in the right direction:
Boot tablet in recovery (TWRP 3.0.1, in this case) and wipe Dalvik, /data, /cache, /system, basically everything)
Reboot tablet into bootloader/download mode
Using Odin 3.11.1, flash T530XXU1BOL2_T530PHN1BOE1_HOME.tar.md5 (Found here, which should be the correct ROM for my model (Bought in the Netherlands, but I have no idea where you folks are pulling this T530XX stuff from, it's nowhere to be found on the back))
Reboot tablet
After the 4th step, the tablet will be unresponsive for ~10 minutes (I think it's doing the whole "upgrading apps" thing that follows a new installation). After that, when I hit a certain area of the screen, I can hear the regular Android touchresponse, raising the volume also give the normal beeps and pushing the power button plays the "turning off screen" sound, but the screen stays active, showing the Samsung Galaxy Tab4 boot logo.
Soooo... Anyone care to take a guess what I'm doing wrong?
Personally, I think it might have to do with flashing the incorrect stock ROM, but for the life of me, I can't find out which T530-code I have. I've been flashing different ROMs, but no luck so far...
As for troubleshooting I've already tried:
The above procedure, afterwards flashed TWRP via Odin and flashed a custom ROM via TWRP. Same effect.
Variations of the above procedure, where I keep wiping the tablet after each step
Different custom ROMs
Ugh, nevermind.
Turns out I have an UK tablet (BTU-T530XXU1BOG2). After flashing a dozen or so ROMs, this one did the trick.
Oh well, problem solved :good:
I restarted my S4 this evening and now it won't boot past the SAMSUNG logo. I have tried a variety of things to get it going but none have worked.
1) Soft boot
2) Pulled battery and let it sit awhile
3) Tried to boot into Safe Mode (stuck on the same spot with no indication of going into safe mode)
4) Wipe cache from CWM recovery mode
5) Reboot from CWM recovery mode
Everything is pretty well backed up but after looking at my sdcard it appears that my camera reverted to internal memory about a month ago so I am after any ideas to get those images.
My phone is rooted and running an old 4.2.2 stock Android OS with USB debugging enabled. I was wondering if by re-flashing the OS it might fix the boot issue and be able to recover the images. Or maybe even flash CM. Or maybe some other thing. I found something about adb but I don't want to do anything else yet until someone more savvy than me weighs in.
Unless it's a hardware issue, then flashing a ROM might work.
The other option is to try a reflow. Reflow means heating your phone up so that the solder becomes liquid and any cracks in the solder (which can cause a bad contact), or any piece that isn't seated right, will be remedied.
did u tried to flash stock firmware using odin?
Deleted
I got it going. I first spent a number of hours getting to know adb which was a dead end because I couldn't get it to see beyond the base directory. I then just flashed the stock rom and everything was there including things that shouldn't be like apps, contacts and texts. The phone is back exactly where it was before it boot locked without having to mess with a single thing. I am grateful but a bit confused.
Thanks in advance for any who can offer help, and I'm sorry if I missed something obvious.
I did a stupid thing and started playing with Odin, attempting to switch from Unlocked firmware on my 950U1 to T-Mobile firmware, in an effort to get RCS support. Before flashing I was running the latest available snapdragon pie beta.
At this point I have flashed all sorts of things in an attempt to restore my device, but I am fairly sure that I flashed a Factory Binary for my device that for some unknown reason would no properly boot and would then crash, rebooting into a kernel panic screen. I decided to abandon my project and flash back to stock and now my S8 will not completely boot. It will go through the Galaxy S8 splash screen, through the animated Samsung screen, then into a Starting Android screen were it will almost immediately freeze the animation and reboot.
I can't remember how exactly I got here but what I thought was that flashing stock firmware via odin succesfully should result in a complete restore. I have always chosen the CSC file as opposed to the HOME_CSC file in order to make sure that data is wiped. I have wiped the cache and data via recovery which resulted in no change.
Any thoughts on how to recover this device? I'm at wit's end with it after several hours of trying everything that google brings up so far as I can figure.
carterra3 said:
Thanks in advance for any who can offer help, and I'm sorry if I missed something obvious.
I did a stupid thing and started playing with Odin, attempting to switch from Unlocked firmware on my 950U1 to T-Mobile firmware, in an effort to get RCS support. Before flashing I was running the latest available snapdragon pie beta.
At this point I have flashed all sorts of things in an attempt to restore my device, but I am fairly sure that I flashed a Factory Binary for my device that for some unknown reason would no properly boot and would then crash, rebooting into a kernel panic screen. I decided to abandon my project and flash back to stock and now my S8 will not completely boot. It will go through the Galaxy S8 splash screen, through the animated Samsung screen, then into a Starting Android screen were it will almost immediately freeze the animation and reboot.
I can't remember how exactly I got here but what I thought was that flashing stock firmware via odin succesfully should result in a complete restore. I have always chosen the CSC file as opposed to the HOME_CSC file in order to make sure that data is wiped. I have wiped the cache and data via recovery which resulted in no change.
Any thoughts on how to recover this device? I'm at wit's end with it after several hours of trying everything that google brings up so far as I can figure.
Click to expand...
Click to collapse
Flash stock firmware with nand erase all
Tried flashing stock firmware with Nand Erase checked, no change.
I have a samsung s8 950f. I put havoc-3.9 on it and everything was great. But then I decided to encrypt the date section. I already carried out such an operation on another samsung (9505) and then everything ended in an hour quite well. Now, after the start of encryption, the screen turned off, the phone did not react in any way,despite the connected charging, the indicator did not light up, and so on. I waited like this for more than three hours and then decided to restart my phone. After rebooting, the phone demanded a pattern for decryption (what was needed), but then the interface constantly crashed (problems). It doesn't matter, I thought and did a full reset.After that, the phone refused to start at all, showing the inscription "custom binary blocked by oem lock". Google suggested that a complete flashing with the original firmware is needed. Since I'm using ubuntu, I flashed it using heimdall. Everything went well and I again saw the original samsung firmware. But I need havoc so I installed TWRP again. But now this recovery does not see the date section. I can install havoc, but it does not start because it requires formatting the date, it turns out a vicious circle. What should I do, I don't like the official samsung software.
The problem was solved this way: installing twrp, flashing havoc, installing recovery from samsung, clearing the date, and again installing twrp. After these manipulations, I got what it was before encryption.
I bought a used Samsung tab S2 with a working Lineage 17 already installed.
I tried to install stock ROM using ODIN.
The ODIN process seems to work fine; I get a "PASSED" in green in ODIN, but the tablet will not boot. Immediately after the "PASSED" in ODIN, the tablet displays "updating system", then "erasing" for about 20 seconds, tries to reboot, but hangs at "SAMSUNG" screen and will not boot.
I've tried several stock ROMs from from different sources.
I'm not sure about the Android terminology, but I think I can get into "boot" mode, but not "recovery" mode on the tablet.
I'm not familiar with a lot of the terms with tablets/phones, so learning by doing. However, I've successfully flashed many computers(Windows >Linux), Enigma 2 receivers, (much easier process), stick a USB stick in and go. I'm surprised the process of flashing a new ROM on Android devices is not more simplified, or less involved.
Thanks for any help.
I had this issue once, it was after I enabled 'Update Recovery' in Developer Options on LOS 17.1, it's "update the built in recovery with system updates" thinking it was a good idea but after it updated the first time it would boot-loop or hang, cant remember but it wouldn't get to the OS anymore so I had to re-flash it, but I was getting this problem. I remember it all being a mini nightmare at the time, I believe I had to find a PIT file to repartition it. I don't understand how it got so severely busted but I stayed right away from that option since then and the LOS 17.1 has been really great.
I had a similar type thing years back going from 1 type of OS to another, I didn't realise they used different file systems and I had similar issues when trying to fix my mess. Learning then about how different ROMs can depend on completely different file systems taught me that if things are really bad and you can't even flash a stock rom with Odin, then finding and flashing the PIT file is basically guaranteed to fix the issue. It's super rare that this type of thing happens though, so I tend to forget about crazy experiences like watching my new OS delete itself immediately after installing it, I forget about the techniques and tricks, I tend to swear and panic and chase my tail for a while before eventually working it out.