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
Related
So I was interested in getting a root, did fastboot boot twrp.img, the version you get from shakala's megaupload page and tried to do a mtp mount to copy the supersu in. That didn't work because I'm on mac and I rebooted... surprise phone doesn't boot. It's just stuck on the 'asus, in search of incredible' screen that comes up 1 second after booting.
Tried to instead flash twrp to recovery, no dice, black screen. Tried flash stock recovery from the shakala's page, I get the droid belly up with an exclamation mark over the open belly...
Tried fastboot boot twrp.img and then sideload the actual OTA firmware, no dice. It won't even try to flash and just gives the 1001 error.
I have tried and unpacked 3 different stock images I've found
UL-ASUS_A001-WW-14.1010.1702.36-user.zip
UL-ASUS_A001-WW-14.1010.1703.42-user.zip
UL-ASUS_A001-WW-14.1010.1704.46-user.zip
and flash the sytem.new.dat to the system partition, no dice again. Phone just doesn't boot.
TL;DR
Something got wonky, phone doesn't boot
Recovery is broken, flashing stock recovery from shakala's page produces belly-up-android image
Without stock recovery, I can't sideload a full system update...
Halp? Ideas?
Got a little bit progress...
The TWRP black screen can be fixed by just turning off the display via the power button and then pressing it again, and you can see the twrp. Looks like even the normal one
Next hurdle was that /cache and /system couldn't be mounted for sideloading so in the end I had to go to the adb shell and format them manually. Then the wiping of system was possible and there were no more errors from TWRP.
So I went ahead and tried sideloading again, it put the image in nicely and everything looks good. Go to reboot screen and it say 'no OS installed'.
I guess those 1.7G images don't exactly have the full OS so a /system formatted Zenfone 3 Ultra can't be restored from those?
Alrighty, got stuff working. Sharing for people who might run into this later.
At this time, you need the stock recovery working to be able to `adb sideload` a full image. The TWRP goes to 50% and then actually doesn't unconditionally push the stock ROM into the partition. I saw the difference when using TWRP/Stock Recovery.
My biggest failure was not to recognize that the green android belly up with an exclamation mark on top of it actually meant that the stock recovery was working. You have to do a little bit more finger juggling to actually enter the recover commands section of the recovery. Mainly after the android appears, volume up+power for a few seconds, release volume up. Illustrated here:
https://www.asus.com/zentalk/in/thread-121896-1-1.html
From the stock recovery, you can then wipe caches and start adb sideload, and using your pc to sideload the image (or from sd card if you so wish).
blosphere said:
I guess those 1.7G images don't exactly have the full OS so a /system formatted Zenfone 3 Ultra can't be restored from those?
Click to expand...
Click to collapse
I can testify that the 1.7G image contains a full OS on /system.
If you read META-INF/com/google/android/updater-script inside the UL-ASUS_A001-WW-14.1010.1704.46-user.zip, you will see the official recovery do use system.transfer.list and system.new.dat in the zip to flash /dev/block/bootdevice/by-name/system.
Recovery is broken, flashing stock recovery from shakala's page produces belly-up-android image
Click to expand...
Click to collapse
When you see the belly-up-android image, press Power + Volume-Up. The stock recovery menu comes up. I was confused at the beginning, too.
From you id Tokyo, did you buy the phone in Japan? If so, it is a JP_Phone, and need some tweak to the initrd in boot.img to flash WW firmwares.
Oh, glad to see you've already solved it! You might want to mark the thread title as "[SOLVED]".
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.
Hello,
So I got myself in a funny situation. After i updated Magisk yesterday my phone wouldn't boot anymore, so i went into TWRP and did a factory reset.
However right now it won't boot anymore at all. Also TWRP is gone.
When i turn my phone on it can still enter bootmode. However my recovery mode is gone. Loading my phone normally just leaves a white LED and black screen.
When i try to install TWRP or any custom kernel i get the message that it is failed and that Recovery partition is not found.
Also loading into recovery just goes to white LED and black screen.
I tried installing the default Oneplus ROM, and it says:
writing 'recovery'...
FAILED <remote: Partition not found>
So now I get stuck because there is no recovery partition and everything i try throws back that my recovery partition isnt there.
Now i tried to install the OPX recovery image to restore it, but when it tries to write the recovery partition it gives the same error but with the name <recovery_a> No such partition.
What can i do to fix this?
EDIT:
Also booting from twrp boot.img will say OKAY.
It restarts the device but then again stays stuck un the black screen with white LED
OPX recovery image?? Never flash an image from another phone. Just reflash your phone with Qualcomm Download Tool and youre good to go
I have followed a guide.
Then i came into the next issue, i started my phone with the blackscreen and white LED, and the driver appeared and I installed it.
http: // prntscr.com /njf9ry
However the download tool doesn't find my device.
http :// prntscr.com /njfa1w
Cyxno said:
I have followed a guide.
Then i came into the next issue, i started my phone with the blackscreen and white LED, and the driver appeared and I installed it.
http: // prntscr.com /njf9ry
However the download tool doesn't find my device.
http :// prntscr.com /njfa1w
Click to expand...
Click to collapse
Try to boot your PC in testsigning Mode and then do It again
So, I just decided to try and Flash the old TF101 with Katkiss 6.0.1 and Gapps, but I always get stuck on the same problem.
My TF101 is running Android 4.0.3 ICS and USB Debugging is on
I downloaded TWRP app on the transformer, as well as the latest .blob flash file through the app.
Before this, I rooted the tablet using Kingroot.apk, which worked. When I went to flash the tablet with the recovery, the app noted "Recovery Partition not found".
I tried to boot into recovery mode on my own, (Pressing Pwr + Volume down , Then hitting Volume Up), The android screen popped, up and then flashed to a fallen android with a red triangle.... The screen stays on this for a minute and then boots into the normal system. I can't even boot into recovery through ADB, using the
Code:
adb reboot recovery
, The tablet will just reboot normally, not into recovery mode.
The Device does recognize through ADB....
Is my recovery partition just non existent? Even when I just let the system though without pressing volume up, it only gives me the option of (Android) or (Erase Data). when I click erase data, ill stay on the asus loading screen indefinitely and nothing will happen until i turn it off and on.
I just cant seem to boot into TWRP for some reason, and that means I just cant install the downloaded custom ROM.
How Can I fix this and boot into TWRP? I've tried for hours and have been hung up due to the same problem each time, even after rooting.
Did you already solve that problem? I also need a solution.Thanks
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?