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
Related
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
DISCLAIMER: I'm completely new to Rooting devices.
My phone is an HTC One M9 running Marshmallow 6.0.1 on Telus.
I attempted to root my device recently to try and solve an unrelated issue that factory reset could not, which is no longer important.
I followed this guide and got all the way up to "Power off your device. Now, to boot into recovery mode.", which I can get into TWRP no problem. However, I cannot push "SuperSU" as it comes up as "device not found"(ADB drivers not installed? Though I got this far somehow). I thought this wasn't a big problem and I could install it later.
Now I'm stuck in infinite boot. The HTC logo shows up, and after a bit it changes and does the animation into the logo for the HTC One. Then it's stuck like this(bootloop?), the longest I've tried being 40 minutes. I can do a fake battery removal and then access the "download" bootloader, regular bootloader, and the recovery (TWRP) no problem still.
If I manage to get SuperSU installed will this solve my problem? Or are they separate issues? Can I flash another image to at least go back to "stock"?
I no longer have any idea what to do. Any and all help or suggestions are appreciated and I'll provide whatever information I can manage.
Further information: I have wiped the appropriate caches(dalvik included) as well as factory reset through TWRP in different instances. I've even downloaded the stock recovery image and wiped again. I simply fail to see what the issue is.
Edit: Managed to get SuperSU installed. I don't know what was different this time. Exactly how many times is it supposed to reboot on its own until it's done? Because it's been restarting for over 20 minutes now.
Greetings xda!
I came across the forum after searching the internet trying to fix my problem. I appreciate the advice in advance!
I have a Gigaset QV830 android tablet. I have had it about a year. or so A few days ago it started unexpectedly crashing/rebooting while browsing facebook and using firefox. It would start right back up until today when it finally got stuck rebooting at the Gigaset start screen. I let it sit for a few hours and nothing happened.
I was able to boot into Recovery mode, and I attempted to wipe the cache partition in hopes that I could reboot the tablet, save my data, and then hard reset. Unfortunately since I did this, I have been stuck in the android bot loading screen for hours now. Since I am a new user I can't post a link to the picture but it is the android bot with his front compartment open and a blue spherical structure spinning and a loading bar moving above it.
Now I cannot enter recovery mode to do a factory reset and my computer won't recognize my tablet. I am stuck and frustrated and am not sure what to do next. I plan on leaving my tablet plugged in over night with the hopes that the android bot loading screen will work itself out but I doubt that will happen.
I didn't do anything to modify my tablet in any way (all factory OS, just installed apps etc).
Any ideas on possible next steps? Disclaimer: I don't know much about android development but am open to learning/trying anything to fix this.
Thanks a lot for your help. :good:
I have tried a few things with no luck. Here is a bit of an update:
I installed Smart Phone Flash Tool, and the necessary drivers. I found two separate copies of my QV830 files to flash the system. I cannot flash my android with either of the system.img files. It gets stuck between 13-15% with the error message: ERROR: S_FT_DOWNLOAD_FAIL (0xFA8). Everything else will flash just fine with no errors (the boot file, logo, recovery etc).
I played around with a few other things. I found that if I tried to format or choose the firmware upgrade option, while they don't run successfully, they do seem to stop the android bot looping screen. After using these options, the tablet is unable to start whatsoever but after downloading the files to the tablet through the Smart Phone Flash Tool (again, all but system.img), I am able to start the tablet up and instead of getting stuck at the android bot screen, I get stuck at the Gigaset screen.
The good news is that I am able to enter system recovery now. The new problem is that when I try to wipe data/factory reset, the tablet gets stuck on the android bot screen and gets stuck saying --Wiping data..., Formatting /data... This once again when I reboot, gets me stuck at the android bot screen with the loading bar.
AHHH!! Ideas? Appreciate it!
EDIT: I also do have another, one of the Gigaset QV830 tablets that is working if that could be of any help to me.
Ok so I know its kind of late, and I'm new here, but I was having the same problem with the same tablet, and I wanted to know if I could follow the same steps that you did to revive your tablet. So could you please give me the QV830 file links so I could figure out how to use the flash tool to bring my tablet back to life? Thanks in advance.?
I did an oof!!!
I made an attempt to flash a ROM on my Quanta Gigaset QV830 tablet. It was the SDK and Fastboot ROM from Magisk Manager. That stupid decision may have soft-bricked my device, thus making it inoperable, yet repairable. I do not have a computer that will be of any help at the moment, as the only laptop I have is an Asus Chromebook C202SA under jurisdiction of a school district using Enterprise Origin, unless, of course, the repair simply involves downloading and unzipping a few files to an SD card.
My Quanta Gigaset QV830 tablet will not be read by a computer via USB, it will not boot into Recovery Mode, or Fastboot Mode, and it will not leave it's state of being in a constant bootloop. Please help me, as I have run out of ideas, and I cannot afford to get it fixed.:crying::crying::crying::crying::crying:
Hi all, attempted to root my phone today following this guide.
I got right up to step 9 but upon trying to reboot and launch from TWRP I began to have trouble. I've been able to access TWRP once, but after confirming install of SuperSU (step 11 here, my phone booted to the LG splash and I got the boot loop saying 'Your phone is unsecure, bootloader is unlocked' or words to that effect. Orange ! triangle.
I can launch to fastboot, or download mode. Turning on to a factory reset sends me back to a boot loop after confirming I would like to reset (leading me to believe I've not got a stock ROM in there at all).
Now when I try to flash any version of TWRP from command prompt in my ADB folder, I'm told my phone is corrupt and it won't allow me to flash.
Alternatively, trying to flash a stock ROM doesn't work either. LGUP does not recognise my model, it only shows COM Ports: [COM4, H85020s]. I've also tried using UPPERCUT but I get the following error: "Error reading from file: C:\Users\...\Roaming\Temp\F9FB5BD\TempFolder\UPPERCUT.exe. Verify the file exists and that you can access it." I've attempted running UPPERCUT from various locations, extracted.
I'm on Windows 10 and I've been trying desperately for the last 12 hours crawling through this site/ other articles for some kind of solution to give my phone SOME kind of functionality. Ultimate goal was LineageOS but now I'd be more than happy getting back to stock. I'd really appreciate any help, hope I've given enough information.
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.