This isn't a double post; other resolved posts are too specific.
I have an IdeaUSA CT702, commonly referred to as an A777. It's rooted and I think the bootloader is unlocked (can't tell because one of my last posts wasn't answered: Fastboot Devices = ?).
The problem:
I recently modified my build.prop and replaced it with some corrupted one that I found online to allow for more compatibility (ie. Gameloft Apps). After restarting my tablet, the splash showed, finished loading, but didn't continue on to show the "android" boot logo. I then restarts after some point in time. The black screen that it stops on is fastboot mode (my fastboot is just a black screen for some reason. It always was. What should I flash? My original build.prop is attached in a zip file.
I also ripped my boot.img and recovery.img (I don't have CWM rocovery, there is no compatible one) earlier just for no reason. I don't have a nandroid backup, and I didn't rip the system.img. I can boot into recovery and fastboot, just not normal boot, so perhaps we could flash an update.zip? I also tried using UniFlash 1.2 and the build.prop editor but for some reason it always reverts back to the corrupted version when I restart the program. Why is this?
Hi,
I have compiled a kernel for my Samsung GT-S5690M from the samsung opensource website. I used the toolchain which was named in the Makefile. After I compiled the Kernel I booted into windows and put the kernel into a .tar and flashed it using ODIN and the flash went well.
My issue is that my phone boot loops on the initial splash screen. I can still get into download mode and flash the stock zImage and put everything back to normal. I am looking for a way to determine what is causing this. I really do not know where to look as adb is not an option because my phone does not get to the second splash screen. I enabled the debugging_config option in the config file but nothing came out after I compiled the kernel.
How do I determine what is wrong with my Kernel? is there a way to troubleshoot this?
Thanks in advance
:highfive:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?
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]".
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