Background info: (My volume buttons broke while i repaired my phone screen after dropping my phone)So i tried flashing a new rom using twrp, but the install somehow botched (it would always go back into recovery). So i wiped everything, and tried flashing a different ROM, again, a botched install. I wiped system, and decided to flash the official version of twrp through fastboot (i had multirom version on), and then in my panic of bricking my phone, i forgot that i had no ROM installed and no way of getting into recovery. and put "fastboot reboot". (oh yea... i just noticed i flashed the oldest version of twrp.. not the newest... god... this is probably why my phone is hardbricked... :'( )So i was stuck with no way of getting into recovery to flash a ROM onto it. So i read online that if i plug in my device, eventually it would return into recovery. I plugged in my phone, and got a "Low battery" warning, but every now and thenit would go into recovery. I tried "adb push *RomFileName*.zip" and it would start working, but after a while, twrp would just disappear, and i would be shown the "low battery warning" Then i tried adb sideload while the phone was in twrp, and it completed, but when i clicked "reboot system" at the end, i was shown the "Low battery" and would return to twrp,, but now it would only show the "Teamwin" splash screen, and it would show a black screen after that, with the "Teamwin" screen flickering everynow and then.
Ps: "adb reboot recovery" and "adb reboot bootloader" both cause a "low battery warning", and then back into the flickering twrp splash screen.
Am i perma****ed?
Related
I rooted my MT4GS a few months ago but stuck with the stock ROM. I decided I wanted to try out the CyanogenMod 9.1 ICS ROM. I followed the following steps:
1) Installed ROM Manager.
2) ROM Manager indicated a newer version of ClockworkMod Recovery and I installed it (5.0.2.7).
3) Using ROM Manager, did a full backup of the current ROM. All went well.
4) Using ROM Manager, downloaded and installed CyanogenMod 9.1.0 stable-doubleshot. I specified to wipe the data and cache partitions. The installation seemed to go normally.
When the phone rebooted, it was stuck at the logo screen. Had to remove the battery to turn it off. Tried a couple times, still the same.
Since I had the backup, I decided I would use CWM to restore the old ROM.
When I boot into recovery mode, it shows CWM 5.0.2.7, but whatever option I try to choose from the recovery menu, The screen just goes blank with the CWM logo in the middle and nothing else happens. Hitting the power button returns me to the menu, but no option works, even power down or reboot. It just goes back to the CWM logo again and I have to remove the battery to shut it down.
So, I thought I would try using fastboot to flash the ROM again. When I boot the phone into the boot loader and select fastboot, then plug the phone in via USB, nothing happens. Windows does not see the phone and ADB or fastboot don't see it either. It's not a driver issue, as the computer is still setup from when the computer was rooted and I connect the phone all the time with no problems.
When the phone is off and plugged into USB or the charger, I still get the charging light, though it goes off after about 10 seconds, then comes back on and cycles like that.
Is there anything I can try at this point, or is my phone bricked? It seems like I followed all the steps correctly. Is there an update.zip I can put in the root folder and see if it picks it up?
Any help would be appreciated.
brucehvn said:
I rooted my MT4GS a few months ago but stuck with the stock ROM. I decided I wanted to try out the CyanogenMod 9.1 ICS ROM. I followed the following steps
...
Click to expand...
Click to collapse
Ok, after rebooting Windows, I was able to get the USB connection to the phone to work in fastboot. It seems I missed the step described in this thread:
http://forum.xda-developers.com/showthread.php?t=1508556
which states with S-ON you must flash the boot.img separately. I did that via fastboot and the phone boots into cyanogenmod now.
However, I still seem to have the issue with clockwordmod recovery. As long as I do the recovery functions from rom manager, everything is fine, but when I manually boot into the recovery menu, I get the same behavior of any choice from the menu just blanks the screen except for the CWM logo and nothing happens. I tried reflashing the recovery image using fastboot, but still no go.
brucehvn said:
However, I still seem to have the issue with clockwordmod recovery. As long as I do the recovery functions from rom manager, everything is fine, but when I manually boot into the recovery menu, I get the same behavior of any choice from the menu just blanks the screen except for the CWM logo and nothing happens. I tried reflashing the recovery image using fastboot, but still no go.
Click to expand...
Click to collapse
This is solved also. Seems on the MT4GS, the trackball is the selection button. The power button appears to only be a back button.
What a thread! Two nicely phrased problem definitions, two well explained solutions, and all from the same guy. Sorry we weren't able to help directly, but you obviously found the answers you needed elsewhere in the forum. And you updated the title as well to show it was solved. Thanks.
I've been following somboons' guide to root. The first time my phone went into TWRP, I tried to root, but it gave an error saying device not found so I reboot the device. I tried it again, but this time, it's stuck on that screen. I can't even turn off the phone. Any help?
You can't get into recovery right? And.. You have flashed recovery?
Actually, I can enter fastboot. When i try to get into recovery mode, I get into a screen that says "Huawei eRecovery". There's a button that says "Download latest version and recovery", should I do that?
EDIT: Rebooted the system from eRecovery, everything's OK somehow.
Ok, let me explain the situation, i'll try to cover up everything i've done, So, please read my whole post first.
The situation of the device is it able to go through bootloader and recovery, it load the animation and logo, but after it the screen is blank (i can see the "android is upgrading", strange it just only 2 apps then nothing)
no sign of life in the blank state, i've tried to press the power up quite times, no sound. Blank state = slightly bright black.
First, i tried to "factory" within the bootloader. it failed, result is blank screen.
Second, i tried the wipe data/factory reset in the recovery, it throws errors.
Third, i tried to flash TWRP. The procedure is finished successfully (complete), but when i tried to boot to the recovery it enter the stock recovery.
Fourth, i tried [5.0.2][Restore to Stock][XT1033] Asia Retail [Dual Sim][4.4.2/4.4.2][LockBootloader] method, i tried the manual one to make sure everything is done supposedly. The only thing that failed is when i tried the last step, mfastboot.exe oem lock. Still then I reboot the phone, blank screen.
Fifth, i tried [HOW TO] Unbrick Moto G 2013! [Falcon, Peregrine] [Lollipop guide], but i'm stuck at step 7 where my phone only detected as "Android Android USB Device"
Another info that might needed is my bootloader is unlocked.
i've also tried the latest KK rom and L rom, and tried flashing under win7 and win10. Both result in blank screen.
Any idea before i jump intio a dead emmc conclusion?
Not sure it'll help, but maybe try updating to the latest adb/fastboot. Mfastboot isn't really necessary anymore, latest fastboot should be ok for heavy loads
just boot into recovery using following cmd
fastboot boot (ur recovery name)
without brackets it will boot ur device in recovery then wipe and install the custom ROMs.
Hi, I have a Verizon variant of the OG Pixel, and decided to try to unlock the bootloader when I found this guide recently.
https://www.xda-developers.com/how-to-unlock-bootloader-verizon-google-pixel-xl-running-android-10/
So my phone was working properly before I did anything following this guide, it did not bootloop or had any problem whatsoever.
I'm not sure what version of the OS I had before I wipe/factory reset and sideload ota image, but when I did the first factory reset, it boot into the system and through all the setup process without any problem, so I decided to factory reset again through the settings menu.
This time I did not let it boot into system but going straight into recovery, factory reset through recovery, sideload OTA image, then factory reset again through recovery like the guide said, then reboot.
Now I got a constantly bootloop device. It stuck in Google logo for longer then I think it needs, then reboot; sometimes it get to the G logo but freezes then reboot; sometimes it couldn't finish the G logo animation and freezes there then reboot; sometimes it goes through Google logo, G logo animation, Android logo on the bottom, then freezes and reboot; the furthest it make so far was the progress bar animation under the G logo but freezes after all and reboot with no luck.
Since this is a locked devices, I could not:
-Wipe anything through fastboot
-Flash anything through fastboot
-Boot into a custom recovery image through fastboot
-Downgrade through adb sideload
-Push files through adb (I have no usable system or custom recovery, no listed adb devices in recovery, push command in adb sideload mode was not permitted.)
Things I've tried:
-Factory reset through recovery
-Sideload OTA image with different USB cables or computers (It only allows me to sideload the latest OTA image, no downgrade premitted, and the result was always success with status 0 without any error message using any combination.)
-Smashed the power button to make sure it is not the case that my power button was stucked
-Make sure it has enough power in the battery (Charge while powered off did shows the charging animation though.)
-Tap on the phone/massage the phone like some Youtube video siad
-Put it into a freezer like some article said
I think I've done anything I could. I thought it was software problem since I had a properly working device just not a long time ago, and have no problem booting into bootloader or recovery, had no error message when I sideload OTA image and factory reset, but now I begin thinking that this could be caused by faulty hardware maybe a non-wetting joint or something (similar symptom did happened on my Nexus 7 2013 which will not boot unless I apply some pressure on the back where motherboard underlies.) But before I did all these factory reset and OTA thing it has no problem at all, so I still not fully convinced that my beloved phone becomes a paperweight just because the hardware suddenly decides to loose a solder point or something.
Did this happened to you guys? Is there something I can do that I missed? Or any way I can get my phone back alive again?
So on my OnePlus Nord CE 2 Lite I was trying to root it. So I did everything extracted the boot image, patched it, flashed it and when my phone starts up it shows this boot animation and then it asks me for my pin. But when i try to input it the nothing happens the touch screen is not recognizing my touches. It can't be a hardware issue because I got the phone today and it worked like an hour ago before doing the rooting. When i boot into the pin screen and try to use adb to reboot it says: error: insufficient permissions for device. Then after a while the phone reboots so this is practically a boot loop. When i try booting up the phone it is really weird it starts the boot up process after a while and it shows the android and OnePlus booting screen then it has the red dot with the white dots going around it and then a black screen and then it either restarts again or it shows the pin screen.
I followed this guide: https://forum.xda-developers.com/t/rooting-oneplus-nord-2-ce-lite.4500297/
...download the correct firmware version for your device (EU / India), bring up fastboot, change slot, flash firmware and done ...the only thinkable reason is, you didn't wait until the phone downloaded the OTA update after unpacking it "one hour" before
I tried to wipe data but then I got stuck on a screen that requires a verification code that I obviously can't enter. And I can't reboot I have tried everything. When I hold the power button and nothing happens at all. I guess I have to wait for the battery to run out.
Okay, so now I got out of that using vol+ and power. But now I realized that the problem is that I had a different version of the boot image compared to other partitions. For example the boot image is like version 3.27 but everything else is version 2.85 (Those aren't actual versions just an example) But when I try to flash the system, vendor and product image it says: remote: '(system_a) No such partition'
or whatever image I'm trying to flash like product_a or vendor_a
Everything else works just those don't and the phone boots into recovery mode but I still can't use touch controls.
use "OppoRealme-OFP-Flash_1.0-x64_Windows" it will flash every thing.
//edit : one time it worked.
After i bricked in again. It's not working. Boot loops