Hello everybody driving nuts with a solution for this:
Phone AGM X1 Chip MTK
Phone is root with Magisk.
Android. 6.1
It happens after flashing some magisk modules, never pass on the loading logo of Linage anymore. The Usb isnt activate.
And I don´t have TWRP installed (bc the phone never let me do it) I did flash in the past with fastboot and TWRP but never installed by default in the phone, always keep only the android recovery.
So I can only have access to Android recovery and bootloader, not to anything else, the screen is not broken, if I get the access to activate Usb debuggin somehow I could restore my phone .
Any clues, tips?.
Related
I tried flashing CWM recovery onto my AT&T Galaxy S4 and because my phone does not connect to my computer via USB for some reason (the phone charges and my computer recognizes that there's a device in, but I cannot actually do anything with it) I flashed it with Flashify. I rebooted into recovery mode, and I got slapped with the "Unauthorized software has been detected on your phone!" message. So I tried rebooting, and I got stuck in a recovery mode bootloop with the same message. Eventually, I realized if I just go into download mode and reboot by pressing the volume down key, it doesn't try to go into recovery mode. I have already endlessly researched my USB problem, and yes, I DO have USB debugging on. ODIN recognizes that I have an external device in as well, but I haven't tried flashing anything onto my phone with it because I don't want to brick my phone because the connection to my PC is faulty. I'm using the charger that came with the device as my USB drive, so that's not faulty either. I know rooting my phone did this, and I'm pretty sure it's because I missed a step. I used this tutorial to root my phone:
[droid views dot com] /root-att-galaxy-s4-sgh-i337-android-4-4-4-kitkat-firmware-i337ucufnj4/ (I'm not allowed to post links yet, so fix the URL if you're gonna have a look)
When I flashed the I337_NC1_Stock_Kernel, my phone refused to go into download mode and I couldn't flash the I337_NJ4_Stock_Kernel as a result. I'm pretty sure that's what caused it, but I have no idea how to fix it. I'm not an expert with my phone and, despite almost soft-bricking my phone via a corrupt CWM .zip, I'm not a newbie at this either. If I could figure out how to fix this problem, I wouldn't have to worry about throwing myself into a bootloop because I can just use ODIN. I was a sitting duck before download mode rescued me, so I'd like some help as to how I can accomplish this. Any and all help is appreciated. I am 100% certain my device is the right version for that tutorial, I wouldn't try to root my phone without checking all of the simple things first.
So i want to flash the recovery image for my nvidia shield tablet, becaouse it isnt booting at all (and no, nvidia didnt killed it, i bricked it :crying: :crying: ) So i got the drivers for adb, but since i cant boot/start the device i cant use adb at all, because it isnt showing any conected devices. I cant access recovery mode either. idk why, but i didnt turn on the usb debuging, so can i do smth to fix this? I would be thankful to anyone who helps me!
Hi,
I've got a Nubia N1 Lite (NX597J) to mess around with, and wanted to try modifying the ROM. I can enter developer mode and allow bootloader unlocking, adb also works. What I can't do is use USB while booting, or in the recovery menu. No fastboot or sending ROM images via adb to the recovery software. The phone doesn't connect to the computer at all (I'm using Linux, it should at least show up in dmesg). Recovery log says
Code:
musb_pullup 2498: no USB cable, don't need to turn on USB
A couple times, even though the cable is connected and works in Android proper. I've tried USB2 and 3 ports, on a hub and directly on the motherboard. It shows up as 0e8d:2000 MediaTek preloader when turned off and, very briefly, as 0e8d:2008 when booting into recovery.
Am I missing something, or is the recovery image just broken on this phone? I've tried both the EU and US firmware, which is a bit more recent.
Do I need some tool that interacts with the preloader, maybe? I have found this guy who's been messing with a phone that has the same SoC.
Have you managed to get it into recovery mode? I just get a dead android picture :/
I've accidentally broken it by flashing the US ROM but my phone is the EU version. Boots up okay but has lost the IMEI and once the screen turns off won't turn on again - unless I reboot it.
Have so far failed to re-flash with the correct EU ROM - it just fails half-way through.
No, and I'm in the same situation with the firmware.
Hi. im having an issue on fixing a locked out Vivo V5 Lite (y66) from a friend. As we all know about Vivo's securedness, we can't just wipe data without the password. and since the password (PIN) was forgotten (even the recovery questions are also forgetten too), its just useless. So I tried flashing it with a STOCK ROM. well at first I had a hard time with sp flash tool until I know how to flash procedurely… but it wont boot normally. it only reboots into system repair mode when attempting to normally turn it on. Recovery mode is accessible and also fastboot mode. wont detect any nearby wifi networks on my house even though is on, so I tried reflashing it... and...
present... vivo v5 lite seems to be stuck on booting into native recovery mode (all black) and wont boot into any modes anymore. pc detects it (on device manager, while turning it on) as "MediaTek USB Device (COM7)", "MediaTek Android USB (COM10)", and "MediaTek Android Device(?) (COM6)".
Any possible solutions? (theories and/or possible solutions)
P.S.: Tried flashing with stock rom versions 2.4.0 and 2.4.2.
Hello, guys.
Recently, I've tried to root a Cubot Power 4G following a guide I found online. I probably should have been more catious about it, cause now the phone is stuck on a bootloop. I tried to install a custom recovery to try and fix this, but as there was no official twrp for Cubot, I once again downloaded something that was probably shady. Thus, now the phone is stuck on bootloop, won't access recovery mode, is now turned off because battery gave out, but if I try to connect it to the pc, it will start to bootloop again. I cannot access adb, or at the least I don't know a way to, since it keeps bootlooping and I have no way to access a recovery mode(since there's no one, or at the least, if there is, it's faulty). What can I do here?
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
jwoegerbauer said:
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
Click to expand...
Click to collapse
I did! Or so I think... The moment I connect it to the pc, it starts bootlooping and so the pc cannot actually connect there
Bootloop is a situation where you cannot get into the "normal" Android system. Take note that as soon Android logo is shown on phone's display Android kernel got successfully initialized, ADB & Fastboot are ready.