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.
Related
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.
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:
After attempting to upgrade my wife's Verizon Note 4 from 5.1.1 with root to 6.0.1 with root, it is now in a boot loop. I had done my exact phone earlier this month with no issues, so I was confident I could do hers. Now she's pissed because she has no phone and I'm in the dog house. Fortunately, I made a complete backup of her phone using TWRP before attempting this upgrade.
So, can I just restore her backup or are there other steps I need to perform before trying to revert it, since I did flash the N910VVRU2CQL1_PartialFirmware_DevEd.tar and the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar during the process, and also the JasmineROM_v7.0_N910VVRU2CPF3, though it was actually restored via TWRP.
The details are below if it helps determine what might have happened, but if I can just restore her backup, she'll be happy, which means I can finally get out of the dog house.
I tried upgrading my wife's phone since she has the same exact phone running 5.1.1 with root. Everything appeared to be going fine, but after performing the last step (flashing the N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z via Odin) and rebooting the phone, it now goes into a boot loop. It will load the Samsung logo for about 20-30 seconds, then reboot every time. I can still access TWRP from recovery and I have cleared Dalvik and Cache, but it still does the same thing. I also reflashed JasmineROM_v7.0_N910VVRU2CPF3, cleared Dalvik and Cache again, but still the same boot loop. It does still show the word Custom under the Samsung logo at boot, so I assume that is good news. Doesn't that mean the bootloader is still unlocked or something?
If it helps, the part of the process that had me concerned was after unlocking the bootloader. I powered off the phone, and then tried to load the recovery menu so I could factory reset the phone and clear the cache, but the recovery menu never appeared. It did show the Android fix-it guy for the recovery for about 10 seconds then a short progress bar under it for about 5 seconds, then it went straight to the Samsung logo. It never did give me the actual recovery menu, just the Android fix-it guy animation, which I thought was odd because I've always had the recovery menu pop up after that.
Any suggestions?
Mike
Modify_inc said:
After attempting to upgrade my wife's Verizon Note 4 from 5.1.1 with root to 6.0.1 with root, it is now in a boot loop. I had done my exact phone earlier this month with no issues, so I was confident I could do hers. Now she's pissed because she has no phone and I'm in the dog house. Fortunately, I made a complete backup of her phone using TWRP before attempting this upgrade.
So, can I just restore her backup or are there other steps I need to perform before trying to revert it, since I did flash the N910VVRU2CQL1_PartialFirmware_DevEd.tar and the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar during the process, and also the JasmineROM_v7.0_N910VVRU2CPF3, though it was actually restored via TWRP.
Click to expand...
Click to collapse
Not that I'm impatient, but I thought I had a backup phone I could put my sim card in until I resolve this issue. Only problem is I forgot it was an at&t phone. Duh!
From what I've read the Note 4 n910v is a robust and almost unbrickable phone. So I said what the heck, I'm going to restore my backup. I mean that is why before all instructions it is advised to make a full backup, so you can revert back, right!. I don't recall the instructions claiming there is a special process or order of steps to take before you can restore your backup.
So, I wiped everything and restored my full backup via twrp. Upon reboot, I finally had the "Kernel is not seandroid enforcing" and "Set Warranty Bit: Kernel" that I was accustomed to. I thought this must be a good sign, but then it went to a black screen, which I realized after about 20 mins, that it had powered itself off. So I tried it again and same thing, it doesn't reboot or even vibrate or flash the LED light. I can press the power button and it will come back on, so I know it turns itself off. So what would cause it to power off after displaying the first boot logo titled Samsung Galaxy Note 4 Custom w/ unlocked icon powered by Android?
The next thing I will try, unless hopefully someone advises me otherwise, is reflash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I assume that should be safe to do, and I'll just follow the directions for the "Easy Guide for How to Root Verizon Galaxy Note 4 (updated links and instructions)" though technically isn't the bootloader already unlocked since I have the red "Kernel is not seandroid enforcing" and the yellow, "Set Warranty Bit: Kernel" and the custom unlocked lock on my boot screen?
This is where I'm confused, I feel like this is not the issue, that it must be something else, but I'm at a lost.
Finally got my phone working! But no WiFi
I've finally got my phone working again! I just can't get the WiFi to work. I have tried three different modems but still the WiFi will not enable: N910VVRU2BPA1_Modem, N910VVRU2CPD1_Modem, and N910VVRU2CPF3_Modem. I even tried restoring the modem I had backed up, but still no go. I noticed that even when I restored my modem from backup, it still said my baseband was N910VVRU2CQL1, but when I flashed the other modems, they each updated the baseband correctly, displaying the correct baseband version, though still no WiFi.
Any suggestions?
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.
So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt