Database Users

Can't get into recovery mode after changing bootloader

I got an Acer A501 tablet and installed lightspeed 4.8. Everything was working fine but for some reason I decided to update the bootloader to Skrillax_CZ's unlocked bootloader which was recommended. Since updateing the bootloader the tablet randomly reboots itself and shut down. I also can no longer get into recovery mode. I tried using Clockwork mod and also with the volume+- buttons manually but all that happens is it hangs at "booting recovery kernel". Does anyone know how to change the bootloader without entering recovery mode?

guitarguy6 said:
I got an Acer A501 tablet and installed lightspeed 4.8. Everything was working fine but for some reason I decided to update the bootloader to Skrillax_CZ's unlocked bootloader which was recommended. Since updateing the bootloader the tablet randomly reboots itself and shut down. I also can no longer get into recovery mode. I tried using Clockwork mod and also with the volume+- buttons manually but all that happens is it hangs at "booting recovery kernel". Does anyone know how to change the bootloader without entering recovery mode?
Click to expand...
Click to collapse
1. Make sure you have the Android SDK installed to your PC.
2. Boot the tab to fastboot using PWR and Vol+
you should get a menu
Select Fastboot Mode. Should say it at the top center when in fastboot
3. Download your CWM image file and copy it to your C:\Program Files\Android\Android-sdk\platform-tools folder. (might be in Program Files (x86).
in that folder you will see a file called "fastboot.exe"
Wait, plug your tab in.
4. Open a command window in that folder (shift + right mouse click)
in the window, type fastboot flash recovery nameofyourrecover.img (where nameofyourrecovery is what the recovery image file is named.
5. Hit Enter
Should flash your CWM recovery image back. I advise you use the latest CWM recovery. 1.7.2 or 1.7.3 you can get at tegraowners site
MD

If I don't have a recovery image am I SOL? Can I download one from somewhere?

guitarguy6 said:
If I don't have a recovery image am I SOL? Can I download one from somewhere?
Click to expand...
Click to collapse
tegraowners.com is one place.
The other recovery, is PublicRecovery which you can find in the Dev Forum.
Both are good recoveries. Albeit the CWM one is notorious for not revealing source code on his kernels. Non-GPL, which is why he is not allowed to post his kernels or roms at XDA. Might be sending your usernames and login's for all anyone knows,
The CWM "is" GPL compliant. So no needs to worry.
The "search" button, is such an easy thing to use.
MD

Thank you for the help. I found an app in the play store called "Acer Recovery" and used it to flash clockwork recovery. I was able to get into recovery mode after that and install the Tegra Owners ICS rom I wanted to try. I won't forget to do a nandroid backup ever again lol.

guitarguy6 said:
Thank you for the help. I found an app in the play store called "Acer Recovery" and used it to flash clockwork recovery. I was able to get into recovery mode after that and install the Tegra Owners ICS rom I wanted to try. I won't forget to do a nandroid backup ever again lol.
Click to expand...
Click to collapse
Yeah, keep forgetting about that one. But, just make sure the Recovery you installed is a recent one. Not sure how often that app gets updated.
Some of the older versions have issues with ICS sometimes, especially TWRP. So check versions.
MD

Request: Rehost of official ZTE Open C Flashing tool: Android version

Hi all,
I've been tracking this thing down all day to absolutely no avail. The main reason I'm after it is I've heard it changes the partition layout to enable a larger /data partition (Essentially turns the phone into a KIS 3).
The download links Comebuy are all completely down it seems, I've even tried using Wayback Machine but that's not coming up with much good either.
Does ANYONE have these tools - as I said, the one for flashing Android to the phone?
Thanks a lot everyone!

Hi.
I have the Open C upgrade tool zip. Is that what you need?

I've uploaded all Open C / Kis 3 Windows flash tool firmwares here. https://drive.google.com/folderview?id=0B9Xj0WNW4yX4b2tOXzFjN1RDRmc&usp=sharing#list
Also see Stock ROMs thread over at MoDaCo for regular firmware updates. http://www.modaco.com/forums/topic/373101-zte-kis-3-zte-open-c-stock-roms/

KonstaT said:
I've uploaded all Open C / Kis 3 Windows flash tool firmwares here. https://drive.google.com/folderview?id=0B9Xj0WNW4yX4b2tOXzFjN1RDRmc&usp=sharing#list
Also see Stock ROMs thread over at MoDaCo for regular firmware updates. http://www.modaco.com/forums/topic/373101-zte-kis-3-zte-open-c-stock-roms/
Click to expand...
Click to collapse
Will these work even if the device won't boot? I can't enable debug mode if I can't get past boot screen.

johnnynmonic said:
Will these work even if the device won't boot? I can't enable debug mode if I can't get past boot screen.
Click to expand...
Click to collapse
Why doesn't the device boot? What happened?
If you can boot to recovery (volume up + power) you can flash a firmware package. If you have Firefox OS bootloader you can boot directly to bootloader with volume down + power key combination and use fastboot to flash/boot recovery image first. I doubt Windows flasher will recognize your device.

KonstaT said:
Why doesn't the device boot? What happened?
If you can boot to recovery (volume up + power) you can flash a firmware package. If you have Firefox OS bootloader you can boot directly to bootloader with volume down + power key combination and use fastboot to flash/boot recovery image first. I doubt Windows flasher will recognize your device.
Click to expand...
Click to collapse
I don't know what happened, it belongs to my friend's daughter. She said she ran it down to 0% battery, then it never would boot up again. It SOMETIMES will boot as far as a welcome screen to set up language, but then says settings failed to start, exchange failed to start. I can't seem to get it into fastboot, but I can get it into recovery. Have tried flashing from sd, and via adb. Any image always fails. Have tried to load stock .zip images and even twmp and cwm, everything fails with either improper signature or footer. So not the end of the world, it's not even my phone, but I'm a chronic fiddler/tinkerer, and the fact that I can't make it work is maddening . Thanks for any tips.

johnnynmonic said:
I don't know what happened, it belongs to my friend's daughter. She said she ran it down to 0% battery, then it never would boot up again. It SOMETIMES will boot as far as a welcome screen to set up language, but then says settings failed to start, exchange failed to start. I can't seem to get it into fastboot, but I can get it into recovery. Have tried flashing from sd, and via adb. Any image always fails. Have tried to load stock .zip images and even twmp and cwm, everything fails with either improper signature or footer. So not the end of the world, it's not even my phone, but I'm a chronic fiddler/tinkerer, and the fact that I can't make it work is maddening . Thanks for any tips.
Click to expand...
Click to collapse
I assume it was running Firefox OS? On Firefox OS bootloader it just hangs on Firefox splash screen when you've booted to bootlader. Do you have proper fastboot drivers installed? ZTE uses generic Google mode for fastboot (18d1:d00d - e.g. USB driver from Android SDK works I've been told).
Stock recovery only allows you to flash matching stock firmware (and packages that are signed with ZTE's private keys). If you can get to bootloader you can flash/boot any recovery (stock or custom) and use it to flash firmware.

KonstaT said:
I assume it was running Firefox OS? On Firefox OS bootloader it just hangs on Firefox splash screen when you've booted to bootlader. Do you have proper fastboot drivers installed? ZTE uses generic Google mode for fastboot (18d1:d00d - e.g. USB driver from Android SDK works I've been told).
Stock recovery only allows you to flash matching stock firmware (and packages that are signed with ZTE's private keys). If you can get to bootloader you can flash/boot any recovery (stock or custom) and use it to flash firmware.
Click to expand...
Click to collapse
Thank you for taking the time to reply. I got it to get to the language selection (where it hangs if I can get it to boot that far). I plug it into the USB, and on the phone select connect to pc via software - then adb was able to detect it as a device. From there did: adb reboot bootloader, and once there was able to use fastboot to install cwm. From CWM was able to flash the EU_FFOS-Android kitkat rom. Works fine now. I see you've spent actually quite a bit of time making different roms and tutorials for theses ZTE phone in various forums. Thanks for sharing your knowledge with the community.
edit: I don't think it had FFOS. vol down+power never seemed to do anything (just perpetual bootsplash). Recovery failed to flash even stock roms (I'm in Thailand, downloaded the stock rom you linked to in another forum, also the stock UK rom. Always returned an error about the footer).

Flashed the wrong recovery

I followed this guide to root my Nexus 10, did the oem unlock, downloaded the linked version of TWRP and flashed it via fastboot, now it won't boot and I can't get into recovery mode, because the version of TWRP was apparently meant for the Nexus 7 aka Flo.
It starts booting normally, but the boot animation just seems to go on forever, I waited around 30 minutes for it to finish but it didn't.
I can get into fastboot mode, but can't change the boot option and I haven't been able to flash anything (doesn't show up with fastboot devices), Windows recognizes the device as "Gadget Serial".
Is there anything I can do?

codfreak said:
I followed this guide to root my Nexus 10, did the oem unlock, downloaded the linked version of TWRP and flashed it via fastboot, now it won't boot and I can't get into recovery mode, because the version of TWRP was apparently meant for the Nexus 7 aka Flo.
It starts booting normally, but the boot animation just seems to go on forever, I waited around 30 minutes for it to finish but it didn't.
I can get into fastboot mode, but can't change the boot option and I haven't been able to flash anything (doesn't show up with fastboot devices), Windows recognizes the device as "Gadget Serial".
Is there anything I can do?
Click to expand...
Click to collapse
Install the ADB drivers on your PC, and then use the command prompt to boot into recovery : adb reboot recovery
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225

What? I can't boot into recovery mode because I flashed a recovery for the Nexus 7. And I can't use ADB because I can't boot into Android either.

Use WugFresh Nexus Root Toolkit. It's worked for me on tablets that could not get past the bootloader on their own.
http://www.wugfresh.com/nrt/

1) Press power + volup + voldown and enter bootloader
2) Flash recovery with command:
fastboot flash recovery recovery.img
done

SM-G903F won't reboot into bootloader

Hi,
I'm on a Galaxy S5 neo (SM-G903F) running stock ROM 6.0.1. I'm using Windows 10 and both ADB and Google drivers are properly installed (the device is recognised both by adb devices and by ODIN when in download mode). OEM unlock is activated in the developer options.
I can adb reboot recovery flawlessly, but when selecting reboot to bootloader from the stock recovery, the phone just reboots to Android. Same applies when trying to abd reboot bootloader or adb reboot fastboot.
Am I missing something? Is there no bootloader unlock needed for flashing custom recoveries or ROMs for this device?

blablubb1234 said:
Hi,
I'm on a Galaxy S5 neo (SM-G903F) running stock ROM 6.0.1. I'm using Windows 10 and both ADB and Google drivers are properly installed (the device is recognised both by adb devices and by ODIN when in download mode). OEM unlock is activated in the developer options.
I can adb reboot recovery flawlessly, but when selecting reboot to bootloader from the stock recovery, the phone just reboots to Android. Same applies when trying to abd reboot bootloader or adb reboot fastboot.
Am I missing something? Is there no bootloader unlock needed for flashing custom recoveries or ROMs for this device?
Click to expand...
Click to collapse
I've working hard this week to completely reflash and root my S5 Neo on Android 7.1. If you want a clean reinstallation use this way.. or if you are already on 7.1 use only the CF_Auto_Root method.
this method work if your OEM is locked or not.
You need to download lastest firmware for your model (if found it on galaxyfirmware.com)
and For Odin, search the web for the modified version "Odin PrinceComsy"
You need the .PIT file for your phone model (ex: mine is S5NEOLTE_CAN_OPEN.pit for Canadian).
Extract firmware (AP_ BL_ CP_ CSC_files)
Launch Odin PrinceCmsy.exe (with phone disconected)
load each file BL to BL AP to AP etc...
Tick Repartition and Nand Erase under Options.
Load .PIT File (and return to the Log page)
Put your phone in download mode (vol down, home + power) click vol up to continue
Connect phone USB to Windows PC (wait loaded..)
Click START
optional, after first boot, close phone and do exactly the same thing but use the odin version coming with the CF-Auto-Root-s5neolte-s5neoltexx-smg903f. load the CF-Auto-Root-s5neolte-s5neoltexx-smg903f.tar.md5 in the AP section and click start (use default settings. no need to touch options and Pit page)
And if you want My package with all my files are using for my Canadian Galaxy S5 Neo

Problems installing a custom ROM on Grand Prime Duos (SM-G530H)

I have a Grand Prime Duos (SM-G530H), currently running an Android version 4.4.4 and I wanted to install a custom ROM to have a higher version of Android. (Tried installing LineageOS 17.1 from itexpert.120, but any custom ROM with a higher version of Android would do)
Problem 1: No custom recovery seems to work.
I installed the TWRP app and tried to flash 4 different versions of their recovery images (from twrp-3.7.0_9-0-fortuna3g.img to twrp-3.4.0-0-fortuna3g.img) and all of them resulted in a unless glitched gray recovery screen.
I also tried the CWM app but it fails to download a recovery image for the device, tried looking online for a image file but didn't find one either.
In the end I reverted the recovery to the default one that I had backed up.
Problem 2: ADB works but fastboot doesn't.
I downloaded the ADB tools to try and flash the ROM from my computer instead. The ADB commands work, but when the device enters recovery mode the fastboot commands don't work. ("fastboot devices" doesn't even list the device)
Went to check the drivers. Most tutorials say to open the device manager and look for the phone device with an exclamation mark and update the driver with ones downloaded from the official site. To my surprise the device doesn't show up at all in the device manager (not even with an exclamation mark). Trying to install the drivers anyway says it's already installed.
The Odin software showed the same problems, detects the device when it's on, but doesn't detect it when in recovery mode.
Problem 3: Error when installing directly through the recovery mode options.
This probably wouldn't work for technical reason I'm not aware of, but I went and tried anyway. On the default recovery mode there are 2 options, apply update from ADB and apply update from external storage. Tried both, the first using the command "adb sideload <lineage rom file>" and the second using the ROM file in a SD card. Both begin to unpack and install the file but after a while throw an error "E: failed to verify whole-file signature", then the device boots to the usual OS.
So, is there anything else I can try? any other recovery images or hacks that won't give me the glitched recovery that TWRP had? Or another method to install a ROM without fastboot? Maybe using another file format in problem 3?
OBS: the device is rooted and has no "OEM unlock" options in its settings

delete the samsung usb drivers and install an older version. only way you can flash custom recovery is with odin. only way to flash custom rom is with custom recovery. fastboot and sideload wont work, this isnt a nexus

You think the reason why the custom recovery was glitched is because it was flashed through the TWRP app and not Odin? Seems unlikely. Is there any non-TWRP recovery image for my model you can point me to?