Well I did what the developers specifically warned against. I wanted to try a few ROMS and then decide on one to settle with but obviously nothing is ever that simple. I can't remember which version of which software I installed, but after installing and reinstalling a mix of ROMS and TWRP versions I made a mistake somewhere and suddenly I got TWRP asking for a password. I panicked at first but when I clicked 'cancel' and went to the usual TWRP page, I thought all is normal again and continued to attempt installing a new ROM beginning with formatting all the data off the tablet! Lo and behold, after formating I learn that TWRP wont allow me to install any new ROMs (why does it allow me to format but not install?)! So now I'm stuck with a tablet that has no OS and boots straight to TWRP's password page.
How bad is my situation? Is the tablet redeemable?
For what it's worth I tried setting up the ADB thing as per the tutorial but whenever I type in "adb shell" I get something to the effect of "adb is not a recognizable command". I don't know if that even matters but it seems to be mentioned alot whenever a bricked Prime is brought up. :\
Thank you
Hi
I am really hoping someone can help me. I have been trying for weeks now to fix my phone: Samsung Galaxy S2 GT-i9100G. In July I stupidly updated from Gingerbread, which was working perfectly, to 4.1.2. Now my phone is practically useless. It switches itself off all the time, unless I just use it as a clock. Essentially I can only use it when it is plugged in. So I decided to try rooting it to do a battery calibration. With my mac I used heimdall to flash a rooted kernel and didn't get the full messages I expected: the final line about reattaching drivers was missing. Then when I used a terminal simulator or superuser on the phone I got an error: no su binary installed etc. So I decided to try using my linux machine last night. This time I got the full feed in terminal, so it looked like the installation was successful, but the same thing: the phone was not actually rooted.
I had also tried unsuccessfully to go back to gingerbread using the mac, no luck. Last night I was so frustrated that I decided to try installing cyanogenmod. At this point I have very little to lose: the alternative is to pay to unlock my old nokia and use that as an actual phone. I tried using the cyanogenmod wiki instructions (which I am not allowed to link to) but pushing to the sdcard didn't work. I got some error: is a directory. Note that when doing the factory reset through CWM recovery it said there was an error formatting the sdcard (something like android_secure. I should have written all of this down). Then I tried sideloading but I just got stuck on the sideload screen on the phone and had to restart the phone. I also found a guide about rooting through CWM recovery but it involves the same push method which just doesn't work. I guess that the problem is the sdcard formatting (note that after last night's factory reset I still have photos on my phone which shouldn't have survived) but I don't know what to do about it. I did try "format sdcard" from recovery mode but that failed.
I am comfortable with command line stuff but will need step by step instructions. I am not an expert at all, have just been reading a lot over the last few weeks trying to fix this. My flash counter now shows 14 or something (some resulted in soft bricking). I don';t know what I am doing wrong. Please help!
Try to flash it with Odin.
spider1029 said:
Try to flash it with Odin.
Click to expand...
Click to collapse
I'd have to get hold of a windows machine (none at home or work). Why do you think that would work better?
I have had the worst luck updating my Nexus 9 to Marshmallow (6.0). I’m pretty certain I “soft bricked” it. It’s stuck in a perpetual booting loop and everything I’ve tried so far doesn’t work.
Here’s what happened:
- I tried flashing 6.0 on a 5.0.1 build. That was the wrong move. I was supposed to update to 5.1 first, before flashing to 6.0. But I have a bad habit of not reading the instructions all the way through, so that happened.
- Somewhere in the process of flashing that, things got corrupt. The Nexus 9 booted up and asked me for my encryption password. But after I typed it in, it said that my data was corrupt. It then erased everything and rebooted.
- That’s when the perpetual reboot loop started.
I’m pretty sure there’s *no* version of Android installed. I tried side loading 5.1 through the ./adb sideload command after the Recovery menu, but no dice. I tried the OTA update from LRX22c to LRX22l, and though that installation was successful (apparently), it’s still stuck in a perpetual reboot.
Any idea of what I can do? My Mac won’t recognize the device unless I’m in the ./adb sideload option, so fast booting/flashing a ROM hasn’t been successful. (I get two error messages when I've tried.)
Is there something I can do, or do I need to send this back to the factory? I’d rather try to figure this out, since it’s clearly my user error that messed things up
FWIW, I have complete access to the bootloader. It's just getting an OS back onto the Nexus 9 that seems to be the problem. I'm left with limited abilities, though, since my Mac only recognizes the device when its in sideloading mode.
Download and install Wugs Nexus Root Toolkit, use the softbrick option first, or you can have it flash Android
https://www.google.com/search?q=usi...ndroid-google&sourceid=chrome-mobile&ie=UTF-8
And then:
https://developers.google.com/android/nexus/images?hl=en
Hi, ever since I began the install process for the Pixel Experience ROM for I9100 my S2 is in a continuous bootloop. I started from a LineageOS that was at least 6 months old because I kept the phone turned off without the battery in it for that period because I don't use, I have another phone that I use as a daily. My problem is that no matter what ROM I install it keeps bootlooping. I think I did some steps wrong at the first install of the Pixel Experience ROM but I tried like 6 or 7 times after that and I'm pretty sure I got the steps right. I even tried installing other roms with / without emulated storage with no success. As of now I have the bone stock firmware with the stock pit file and it still does not boot. It goes past the screen that says the "Samsung Galaxy SII I9100" in a screen that has a animation with the samsung logo and that is where it ends. I've tried numerous clean installs, cache wipes and all this stuff. I think good to mention is that sometimes the stock recovery says it can't mount data and efs folder and sometimes the TWRP can't mount data. I fixed all these, except the efs file thing but it does not always come up. The only thing I have't tried with success and I don't know if it works in my state is ADB but when I tried "adb shell" it came up as an error even though the phone was recognised by "adb devices" command. I even tried as a last resort the "Nand wipe" in Odin but it *fortunately I think* didn't work (literally nothing happening). I don't know what this might mean, NAND corruption maybe?! I've been messing with this for 5 days already in all my free time and I've got nowhere. If you have any ideea, no matter how crazy, I can try it and tell you how that worked out.
I got it to connect to ADB properly but I still don't know what to do. Any sugestions?
Sent from my SM-G965F using XDA Labs
I managed to fix this problem by following THIS tutorial step by step.
Hello, I am new here and I made a huge mistake!
I purchased Samsung Galaxy Tab S6 Lite (LTE) literarally 1-2 days ago and I wanted to root it, I had my smart phone rooted which did not have Knox protections, it was as straight forward as flashing TWRP and use Magisk via instructions I followed.
I make use of "Root" privileges a lot when using my device, I find it very important to my daily life so I decided to risk rooting it, after doing so my tablet was showing 2 errors, that its not using official samsung software and that the boot loader is unlocked, when I unlocked the boot loader using OEM Unlock everything went fine, the option was greyed out and checked afterwards.
During the boot process, it reboots 2 times and it shows a integrity error, integrity and some very long number, I am assuming its a integrity check? I have the exact matching firmware, so I flashed back the stock firmware and... the "not using official samsung software" warning disappeared, it boots me into recovery mode, I choose "reboot" and the device goes to boot looping with the same error.
I was following this tutorial: https://forum.xda-developers.com/galaxy-tab-s6-lite/how-to/howto-unlock-root-galaxy-tab-s6-lite-t4132289
But there are some things I skipped, here the exact steps I took:
Unlocking Boot Loader:
Followed all the steps from 1 to 4 but I skipped the 5th step entirely, the step where it asks you to mess with firmware date and twrp, I did none of that, I will mention that when I was looking for stock firmware to download before doing anything, I was not able to understand the CSC so I didn't know which firmware to exactly use until a software update came up which told me the exact firmware, I accepted the update and download that stock firmware, because my firmware was updated I didn't think that following the few steps of the step 5 would've done everything as I was already off the path.
I didn't do the 6th step as I just checked of the OEM Unlock is greyed out and still checked in the "developer options" section, I assumed that it was a success, not to mention the boot loader unlocked warning that was showing up and yes, all the data was erased and was forced to go through the setup process again as expected.
Root the tablet:
1. I have downloaded the firmware as it says not just for the purpose of rooting, the firmware that the software update told me about, this is the firmware I downloaded, the firmware is a exact match, everything is matching: https://samfrew.com/download/Galaxy__Tab__S6__Lite__-LTE-__/xs5l/SEB/P615XXU3BTI3/P615OXM3BTI3/
2. I follow all the steps from 2 to 11 from here.
3. When I reached step 12, I went to download mode and I look for any messages regarding it only allowing for official samsung images, but I saw no such message, didn't really pay attention to anything else, I just glossed over things, considering there was no such message I assumed that KG/RMM state was good, don't know what it was but it might not have been "prenormal" because there was no message regarding official samsung images, from here I falshed the boot.tar file like in the instructions, that lead me to my current problem I mentioned at the very start of this post.
4. There was no step 13 as I can't boot into android due to "integrity" error I have, right now I have my tablet turned off (thank god I can do that) via the recovery that shows up after flashing stock firmware.
Addition Info:
1. I don't have any data to lose, if I need to do a factory reset or something of that sort, I have no problems doing that.
2. As I mentioned at top, I do have a stock firmware downloaded from this link here: https://samfrew.com/download/Galaxy__Tab__S6__Lite__-LTE-__/xs5l/SEB/P615XXU3BTI3/P615OXM3BTI3/
3. The tablet is: SM-P615 (Samsung Galaxy Tab S6 Lite (LTE), I bought the LTE so I could use it as my phone)
4. At the download mode, the OEM (Boot Loader) state is set to NO and the FFS (I don't remember if its FFS exactly at the moment, something FF I believe, I don't want to turn on my tablet at the moment) was set to NO.
5. The KG (No RMM mention that I could see anywhere) state is showing up as "Checking..."
What do I need to do to fix my tablet? do I need to wait for 7 days? if so how do I do so, like does leaving my tablet off count or not?
PS: I am a self-thought experienced low-level windows programmer, I've been doing programming for over 10 years now, never have worked with Android development but I can attempt to build something from source if necesarry, I know very little about Linux OS as I purely work with Windows and use Windows for everything including servers.
I have done some research regarding that "integrity" error and I can't find any screenshot in google images that matches how it looks on my screen, but there are a lot of them quite similar to it, which basically says "verification failed, factory data reset your phone", in my case I don't have that message, it just says "integrity", but when the boot looping stops and shows that failure I do have 3 options, "try again" and "Factory data reset" and the 3th one I don't remember, I am suspecting that this could be my problem! I believe the samsung just changed the way that particular message is shown (visual change), so I just need a factory data reset and it will work, most likely with the rooted boot.img file! I will attempt this after a few hours of this reply, I may have panicked too early.
The issue has been fixed
Well this is surprising, I was about to do the factory reset but before doing so I decided to flash the same magisk patched boot.img file, when I flashed I saw seeing those 2 warning messages as expected, I was expecting for it to fail after 2 boot loops so I can do the factory reset as intended but on the 3th boot loop the tablet booted up! I was brought at the android setup screen, once I was done with that I checked the OEM Unlock, it was still checked and greyed out, downloaded Magisk Manager and to my surprised it worked! Magisk Root latest version is installed and working, it asked me to allow magisk do some "additional setup", the tablet booted up perfectly fine after that "additional setup", I check root privileges using "Root Checker" and it worked, I have root privileges! I most likely have panicked too soon, sorry for wasting your time! Hopefully this post will be useful to someone in the future looking to root their tablet.
My assumption of what happened: When I flashed the stock firmware AP a second time so I can turn off my tablet, it most likely did a factory reset without me knowing, so when I flashed magisk again before letting it try boot up again, the tablet booted perfectly fine because factory reset has already occured, which brought me to the android setup screen.