Managed to mess up my phone (Alcatel OT Idol Mini, 6012x) with xposed modules, set it to restart and it's now stuck in a bootloop.
Wouldn't be so bad if I could get into recovery mode or anything, but nope - no combinations of accessing it work. Isn't recognised by my computer, can't force it to reboot in recovery, can't wipe it over usb in its current state.
I've tried ADB, fastboot, ODIN, and searched several guides/tutorials, all of which either require recovery/download mode or the phone to not be bricked.
I don't care about the data on it, it's just frustrating. Any help on how to wipe/fix this thing would be great.
I've come across a problem that's frustrating me to no end. I've been rooting phones for a few years now, usually older models. A friend asked me to root his newly aquired S6 (canadian model, eh), shouldn't be an isssue. I do the standard issue Enable Developer, wipe data/cache, install root and rom, and call it a day. I go to reboot it, and it's in a boot loop for the Samsung screen. I've had boot loops occur before, I'll take care of it.
I've been at this all day (10+ hours), and still don't have a way to escape this boot loop. Problem is that I didn't know about the Reactivation Lock that was still active when I attempted to root. Here' what I've attempted:
- Uninstall/Reinstall USB drivers several times and different versions. Phone will still not show up under ADB Devices and not detected by windows or toolkits (but will still register via Odin).
- Restore from backup: will only boot into stock recovery mode, no option for restore.
- Reinstall Firmware via USB OTG - "USB access is disabled"
- Install other roms, always fail or are denied access
- Update/Change kernel , see above
I could list on and on all the little tricks and toips i've tried from the internet, but what it essentially comes down to is I can't install anything onto the device due to the device not being recognized or being blocked by a permission, and yet I can't get into the actual Android OS to disable/Enable any permissions. Factory reset does not fix this loop, nor does clearing caches. I've tried sideloading, pushing, and various other means to get into Android, but nothing is working. Help?
I unlocked the bootloader and flashed TWRP just fine. I attempted to root, but everything was encrypted (I think), so I set a PIN and read that some people had to reboot several times before TWRP recognized and asked for the PIN. So I did that, and after the 4th or 5th time, it booted up to a blank screen only with the soft buttons. I tried erecovery, but it's the same. USB debugging was apparently turned off somewhere along the way, so I can't access ADB. Also, when I plug it into to my computer, a message pops up that says "the last USB device you connected to this computer malfunctioned, and Windows does not recognize it."
I'm at a complete loss as to what to do. I've searched and tried everything I've come across over the past two hours, but to no avail. I'm hopeful something's out there but I've missed it.
I can still access TWRP. I factory reset it a few times hoping that would work, but it didn't.
Any suggestions?
Hi all! I have been trying to fix this tablet for weeks. It's an SM-T580 Galaxy Tab A 10.1 tablet. It's actually my girlfriend's tablet and she tried to root it first and she royally screwed it up and I am having a lot of trouble cleaning it up.
So, when I got to it, she already had it stuck on the downloader mode and if you tried to boot it, it went to the blue screen that says "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software."
So here is everything I did as well as I can remember it:
1. Tried every version of smart switch and KIES software. It does not recognize it ever.
2. Tried to flash custom recovery, but FRP lock is still enabled. She must not have correctly changed the settings in the tablet before beginning the root.
3. Tried to flash stock firmware, but it says it needs to be repartitioned. I downloaded what I thought was the pit file, and repartitioned the chip, but it still won't successfully boot. I tried several different cables and ports.
4. Tried to flash probably 10 different firmwares to see if anything would stick. Used several different versions of Odin all the way from 1.3 up to 13.5. Nothing will successfully boot.
5. Found stock recovery (I believe) and got stock recovery on there but when i get to recovery it says it can't mount anything. It gets a huge list of errors like "can't mount E..." I am able to ADB sideload, but so far nothing I try to sideload works because it says it has the wrong footer and the wrong signature.
Am I boned? She left it plugged in for like a week at least, so my assumption is the emmc chip burned out. Any and all help massively appreciated!
hello, recently i bought myself a new op6, as it was good for modding and such. unlocked the bootloader, flashed twrp, and rooted it the day after, used it for a couple of days, before I installed elementalX. was happy with that for some days. then I decided I wanted to try out lineageOS, in order to de-google my self, in my quest for privacy.
TL;TR:
mtp is not working after flashing, neither is twrp, cant even access it through fastboot with booting the .img file.
does this have something to do with the a/b partition thing on these phones, perhaps?
I would guess that I flashed lineageOS the wrong way, and that is the issue, but since I cant access twrp, I cant restore and reflash the correct way.
more detailes below
--------------------------------------
backed up before installing elementalX, to have something to go back to, in case of failure
rebooted into twrp, and wiped everything, exept internal storage (i looked this up several places, prior to flashing, that this was the way to do it, so assumed this was the correct way)
flashed lineageOS 15.1
wiped dalvik and rebooted
took ages to boot, so figured id reboot again a couple of times, with no succsess
tried to boot to twrp, to restore back state prior to flashing, but ended up in lineageOS' own recovery.
tried to boot from fastboot, and reflash twrp
goes out of bootloader and screen turns black, led turns on, and nothing. tried waiting for a bit, but nothing seems to happen
have to manually turn of phone, and reboot. tried this several times, but same result.
after reboot i turned to the recovery to look after any solutions there, but nothing
started adb, just to check, and it says "device unauthorized"
sortof gave up, so figured I could atleast get going installing apks, but after downloading f-droid, I couldnt get it to install
found out this was some sort of permission issue, so had to move it to internal storage to get it to install
after installing some apks, I was going to transfer my contacts from my pc, but cant get mtp working..
if someone know a soulution to this, I would be really greatfull, as Im at a loss. cant seem to find anyone who has had a simillar issue..
You can always use EDL and MsmDownloadTool. Check that thread
thanks, will definetly check that out.
now it apears that I have another issue, the key for adb is no longer valid. i did get the prompt when I connected the usb, but that didnt appear to do anything. have tried to revoke it, reanable, reboot both phone and pc, also delete the keys on my pc. I have no root access anymore, so cant really enter the root on my phone, to pull out the keys there, neither can i push my own keys, as it seems atleast. I may be doing it wrong too, for all i know..
If you can enable debugging and see your phone with adb devices, you can adb push /sdcard/<romfile>.zip
I am able to enable debugging mode, yes. Will this enable me to push my own key, or any other existing key for that matter, to remove the unauthorized label?
Id also like to at that i done goofed when flashing lineageOS. Ive come to and understanding that I have to flash OOS 1.5.1 (i think that was it) on both slots, before then flashing the custom rom onto the device, and reflashing twrp after that. Which i did not do. I also were running pie at that time, so theres another mistake I made to begin with. Neither was I really aware of the concept of a/b partition system at hand..
Can i switch slots in fastboot, and then boot inton twrp, and reflash back to OOS 1.5.1, on both slots, and then reflash LOS 15.1? And ofcource reflash twrp and root afterwards, which totally slipped my mind..