Database Info

[Q] Recovery mode not working

ISSUE
I can not get into recovery mode.
What is happening is a loop. I get booted into the fastboot mode and when i click on recovery, the screen goes black and then right back to fastboot mode.
I read all the related posts, and nothing helped. I downloaded Nexus Root Toolkit v1.6.2 and tried to use it as well but it didn't fix my issue. i took a screen shot of the message from NRT. When i get that message, the phone is just sitting at the fastboot menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also tried one click stock, same issue.
Nexus S
Att
Andriod 2.3.4
baseband version: I9020AUCKE1
KernalVersion: 2.6.35.7-ge382d80 [email protected] #1
build number: gtj61
I kind of think i may have done something when i was trying to unlock this phone a few months ago. Any help is much appreciated. I just want to reset my phone to factory settings.

zach18 said:
ISSUE
I can not get into recovery mode.
What is happening is a loop. I get booted into the fastboot mode and when i click on recovery, the screen goes black and then right back to fastboot mode.
I read all the related posts, and nothing helped. I downloaded Nexus Root Toolkit v1.6.2 and tried to use it as well but it didn't fix my issue. i took a screen shot of the message from NRT. When i get that message, the phone is just sitting at the fastboot menu.
View attachment 1637759
I also tried one click stock, same issue.
Nexus S
Att
Andriod 2.3.4
baseband version: I9020AUCKE1
KernalVersion: 2.6.35.7-ge382d80 [email protected] #1
build number: gtj61
I kind of think i may have done something when i was trying to unlock this phone a few months ago. Any help is much appreciated. I just want to reset my phone to factory settings.
Click to expand...
Click to collapse
First off, download the attached zip.Extract the zip to your desktop. Open up command prompt and navigate to the folder where you extracted the files. Now connect your phone to your computer and boot into fastboot. In command prompt, type in
fastboot devices
Click to expand...
Click to collapse
It should list your phone.
Then type in
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Now you can boot to recovery on your phone. Download a ROM you like and flash it from the recovery. Make sure to wipe data/cache before flashing the ROM though.
Lemme know if it works.

try another computer to install recovery back or just rom manager by wi-fi.

Talal916 said:
First off, download the attached zip.Extract the zip to your desktop. Open up command prompt and navigate to the folder where you extracted the files. Now connect your phone to your computer and boot into fastboot. In command prompt, type in
It should list your phone.
Then type in
Now you can boot to recovery on your phone. Download a ROM you like and flash it from the recovery. Make sure to wipe data/cache before flashing the ROM though.
Lemme know if it works.
Click to expand...
Click to collapse
Quick question, do i need to do anything special to get into fastboot? other than power button + volume up? The first line on the screen says FASTBOOT MODE. Nothing happens when i type in that command. it goes to the next line but nothing shows up.
any idea why my computer can't see the phone in that line? i probably missing a step.

zach18 said:
Quick question, do i need to do anything special to get into fastboot? other than power button + volume up? The first line on the screen says FASTBOOT MODE. Nothing happens when i type in that command. it goes to the next line but nothing shows up.
any idea why my computer can't see the phone in that line? i probably missing a step.
Click to expand...
Click to collapse
So being curious and trying to further troubleshoot, I followed this wiki to make sure everything was setup correctly.
Howto: Install the Android SDK (Google that, i can't post links yet)
When I typed
adb devices
Click to expand...
Click to collapse
and my device showed up.
But I am still not seeing it when I boot into FASTBOOT MODE, and type
fastboot devices
Click to expand...
Click to collapse

mypat said:
try another computer to install recovery back or just rom manager by wi-fi.
Click to expand...
Click to collapse
How do i install recovery back? where would i find that img?

zach18 said:
How do i install recovery back? where would i find that img?
Click to expand...
Click to collapse
Instal twrp.apk on your rooted phone. Connect to internet and twrp will download the IMG recovery for your phone. Reboot to boatloader and select recovery.
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk 2

Is your phone unlocked?

ej8989 said:
Is your phone unlocked?
Click to expand...
Click to collapse
So I finally figured it out. I do apologize for how vague and un informative the question was. It was a case of me needing to dig a little more.
Here is what i did.
I had installed a Rom Manager, CyonGenMod when i rooted the phone. They had a recovery img in the app which i used. I think googled around for cyogenmod 10 and ICS 4.0.4. Then i realized i had to find google apps, so i could add my contacts from gmail. Then it was just messing around with bootloader to get the right setup.
I do appreciate the help, y'all put me on the right path. Made me find answers to the right questions. Again I apologize for not doing more due diligence.
Thanks for the help

D2303 Bricked. Fastboot works, FlashTool doesn't

I have bricked M2 D2303. I don't know how it was bricked for the first time(it's not mine), but yesterday I temporarily resurected it by flashtool. It booted and worked few minutes on any system(i dont remember what it was) After trying to put customrecovery it started to bootloop.
Now Flashtool doesn't see this device anymore, but fastboot is stil alive. I flashed CM12.1 boot.img - it showed sony logo, android logo and then bootanimation(blue waves). After few more tries of flashing different images it doesn't start to boot, screen remains black. I searched for boot, system and userdata IMG packets, but I've found only this one: http://forum.xda-developers.com/xperia-m2/general/aosp-5-0-2-d2303-progress-t3073842
After flashing nothing happens. Fastboot still works, but flashtool doesn't.
I don't have any idea how to resurect it now...
I've never had any sony android device... My only ones were nexuses and Oneplus One.

Try repairing using Sony PC Companion...This may solve your problem

Than you. I tried to follow this instruction: http://talk.sonymobile.com/t5/Xperi...uctions-using-Pc-Companion-Win-or/td-p/249946
But in my version of app isn't any "repair phone/tablet" button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Download the TWRP recovery and OmniROM or any other flashable ROM.
Flash the recovery through fastboot.
Reboot into the recovery, allow /system modification and install the ROM; reboot to system.
Then re-flash stock if needed.

Maybe stupid question. I've already tried to unbrick via recovery yesterday, but I can't boot it. I flashed TWRP by "fastboot flash recovery twrp.img" but i wasn't able to boot. ADB works only on android and there is no fastboot command to boot recovery. I tried some hotkeys like volume up/down, both, but they do nothing.
fastboot boot twrp.img also returns an error.

wefhy said:
Maybe stupid question. I've already tried to unbrick via recovery yesterday, but I can't boot it. I flashed TWRP by "fastboot flash recovery twrp.img" but i wasn't able to boot. ADB works only on android and there is no fastboot command to boot recovery. I tried some hotkeys like volume up/down, both, but they do nothing.
fastboot boot twrp.img also returns an error.
Click to expand...
Click to collapse
If the bootloader is locked you shouldn't be able to flash any .img file. It it isn't unlocked in order to flash a recovery the phone must have a kernel (Sony made them for KK) that supports the recovery in a separate partition. Stock Xperia phones don't. Flashing any random .img file I won't be surprise if the phone gets bricked, it isn't like in many other phones.
Anyway, to fix it you must be able to flash via flash mode. Flashtool when connecting a phone reports in the log which mode is enabled (if the phone gets recognized at all). So you can use it to see if anything is alive. If the flash mode is dead for any reason but fastboot still works you must a kernel for Xperia M2 flashable via fastboot, if any is available. That may reopen the flash mode and from there do a phone repair from PC Companion.
Oh, and as usual if you are in Windows be sure all USB drivers are correctly installed..

wefhy said:
Than you. I tried to follow this instruction: http://talk.sonymobile.com/t5/Xperi...uctions-using-Pc-Companion-Win-or/td-p/249946
But in my version of app isn't any "repair phone/tablet" button
Click to expand...
Click to collapse
To repair your phone by using PC Companion you have to go to Support Zone: 1
Then follow the steps (sorry for the language i can't change it) : 2
3
I hope it will help you

Hope your Xperia will fixed bro,
Keep your spirit

@Miche1asso
Fastboot mode works, I'm able to flash any boot image.
Windows drivers are installed correctly because flashtool repaired this phone few days ago.
Wchich kernel to flash? Recovey-friendly one? It's for 4.4.4, but last installed system was lollipop. I am able to flash system via recovery on bricked sony device? On my Oneplus One it's impossible.
Or rather any original kernel to revive flashtool?
Unfortunately most of download links are dead :/
@tromine It would be better if my PC companion worked the same... Support zone shows nothing.
Edit: I flashed this kernel: http://www.android.gs/install-cwm-recovery-on-sony-xperia-m2-lte/ It's a progress - its shows sony logo again I tried few times to boot into recovery bu every time it stucked on sony logo. I pressed power off button (next to sim/sd) and left it for few minutes on c harger and... It booted into recovery (without any volume hotkey)
It looks like stock recovery on my oneplus or zenfone:
I am able to flash system using it? Only stock one or any?
O rather i should flash any other recovery?
Push zip file via ADB or any other way to tho this?
Or one question for everything: What's the fastest way to flash CM12.1 from there?
Edit: Nearer than farther Now I have CWM v6 on it But it still can't flash any system image
It says installation aborted; error in storage(...).zip; can't partition non mmbcblk device: /devices/msm_sdcc.2/mmc_host

Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.

wefhy said:
Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.
Click to expand...
Click to collapse
Wich flashtool do you use?

wefhy said:
Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.
Click to expand...
Click to collapse
A couple of things: Did you update PC Companion to the last release? It must have the option to repair the phone somewhere. I can't help much on that because I use the OS X version, but the option is there on one of the top menu.
Anyway, since you managed to flash a working kernel (with CWM) the phone isn't bricked. From there (the CWM) I would flash a full custom ROM which includes a kernel with CWM, obviously wiping everything (cache and data). The kernel must belong to the ROM to avoid further troubles. At that point hopefully the flash mode is restored. But even if it isn't from there with the last PC Companion repair the phone.
PS: I realize I messed up a bit writing in English in my previous post. But it seems you've got what I meant anyway.

I use the newest flashtool and PC companion downloaded from sony page. I updated them.
I searched few times, but my pc companioj just hadn't got repair option.
CWM wasn't able to flash anything(alwatys the same error)
Anyway... I installed flashtool on Linux Mint. It detected device immediately. As linux version is hardly outdated, it couldn't flash anything on this device(device list stopped on Xperia T/S - no M/M2) but somehow it unlocked my xperia.
When I next time tried to use flashtool on windows it just detected it and flashed stock.
Now I'm on 5.1.1 and everything works fine Thanks!

TWRP for Razer Phone

https://dl.twrp.me/cheryl
Razer Phone Install Instructions
Read these instructions and follow them carefully. Failure to do so may result in not being able to update the device in the future and there are no factory images available.
The Razer Phone uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. Unlike the Pixel devices, Razer has disabled fastboot boot so there is no way to temporarily boot TWRP to perform an installation.
Getting into fastboot mode or recovery on the Razer Phone requires plugging the device into a USB cable. I would recommend against flashing or performing recovery-related actions unless you have access to a USB cable and port so that you can get back into recovery should something go wrong. Power off the device. Hold volume up to get into recovery or volume down to get into fastboot mode. Plug the device in while holding the appropriate button and the device should boot to the mode you selected. If it boots up to the charging screen, try a different USB cable or port. Make sure you are able to boot the device to fastboot via USB cable before flashing anything.
We are going to use the other boot slot to flash the initial copy of TWRP and boot TWRP. To do this you will need to turn on developer options and enable USB debugging. You will also need to enable OEM unlocking and unlock the bootloader. I am not going to discuss how to get the proper drivers installed or assist you with doing these basic steps. There's tons of guides elsewhere for these items if you need it. I will say that unlocking the bootloader requires using fastboot flashing unlock instead of fastboot oem unlock. Once you have adb working, run this command:
adb shell getprop ro.boot.slot_suffix
It should say:
[ro.boot.slot_suffix]: [_a]
Or:
[ro.boot.slot_suffix]: [_b]
Make note of whether you are currently using slot A or B. Next power off the device and boot to the bootloader using your USB cable and volume down. You want to switch to the other boot slot. If you are currently on slot A, type this:
fastboot --set-active=_b
Or on slot B type this:
fastboot --set-active=_a
You should see something like this:
Setting current slot to 'a'...
OKAY [ 0.042s]
finished. total time: 0.042s
I found the bootloader on the Razer Phone to be extremely finicky and I had to run the command multiple times until I got it to run successfully. You may have to hold the power button for 15 seconds to force power off the device and then re-enter fastboot mode. Keep trying until it works. Once it's on the right boot slot, type this:
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
Your device should now boot into TWRP. From here, decrypt your device if needed at the password prompt. DO NOT swipe to allow modifications until after you make your initial backup; instead tap on the read-only button. Go to the reboot page and tap on the button at the bottom to switch back to the slot you were originally using. Go to the backup page in TWRP and back up Boot and System Image. It is HIGHLY recommended that you save this backup in a safe spot on your computer because you may need to restore it to take official OTA updates from Razer. Once you have finished making your backup, run this command:
adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard
In TWRP, tap on Install and browse to the zip and install it. TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal, though with TWRP installed, you won't be able to take OTA updates without restoring the stock boot image.
MTP is disabled because it causes a kernel panic sometimes with the stock kernel. ADB also does not work with the stock kernel which makes transferring files between your PC and the device when using the stock kernel a bit of a challenge. The TWRP bootable image does have working ADB though and you can copy files to a SD card or USB stick if needed.

Reserved!

Thanks you so much @Dees_Troy

Let development begin
Awesome work! :highfive:

Awesome! Now we just need to let the dev fun begin! BTW You Rox!
Edit: Im trying to do a full backup of the current state of my phone. went into TWRP and selected every partition and hit backup. Was flying along till it got to Data and it just stopped. No movement @ 40% for about 5 minutes so far Is it working for anyone else? does it just take insanely long with no percentage increase, or am I just being paranoid cause its my new phone lol
Edit 2: I just cancelled it and backed up everything but Data and it went fine, I'm now attempting to backup JUST Data.. Ill have to restore 2 backups seperately, but it appears to be working
Final Edit: All good.. not sure what happened the first backup but doing them seperately worked. Rooted with Magisk 15.1 and running beautifully! Gonna try out some root stuff like Xposed.. Thanks for all your hard work devs & testers!

@Dees_Troy Thanks for your work. Broken link https://github.com/TeamWin/android_device_razer_cheryl
Please update when you have time
Another thing in your instruction consider that on european razer phone the right command is this (I've found problem only for slot b in slot a work without -i 0x1532)
ffastboot -i 0x1532 flashing unlock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

i get the no devices/ emulators found
EDIT: I didn't realize you had to do that part with the phone on. so when I boot in to bootloader i have slot b and type the command to switch to a. all I see is waiting for devices. thats when I redo it until it writes correct?

RicardoSal24 said:
i get the no devices/ emulators found
EDIT: I didn't realize you had to do that part with the phone on. so when I boot in to bootloader i have slot b and type the command to switch to a. all I see is waiting for devices. thats when I redo it until it writes correct?
Click to expand...
Click to collapse
I've Uses this command to open bootloader?
fastboot -i 0x1532 flashing unlock
If yes command for your device work add -i 0x1532

raimondomartire said:
I've Uses this command to open bootloader?
fastboot -i 0x1532 flashing unlock
If yes command for your device word add -i 0x1532
Click to expand...
Click to collapse
I would still get the message saying <waiting for any device>

RicardoSal24 said:
I would still get the message saying <waiting for any device>
Click to expand...
Click to collapse
Verify your driver in setting. You must add google driver

raimondomartire said:
Verify your driver in setting. You must add google driver
Click to expand...
Click to collapse
link please

RicardoSal24 said:
link please
Click to expand...
Click to collapse
https://developer.android.com/studio/run/win-usb.html

not able to update the driver manually
---------- Post added at 12:49 PM ---------- Previous post was at 12:20 PM ----------
apparently there's no "compatible" driver software for a x64 bit system

RicardoSal24 said:
not able to update the driver manually
---------- Post added at 12:49 PM ---------- Previous post was at 12:20 PM ----------
apparently there's no "compatible" driver software for a x64 bit system
Click to expand...
Click to collapse
Use this
http://www14.zippyshare.com/v/ufYG71o0/file.html

I remember seeing something about no Wi-Fi in the other thread from the chat about source code. Is that still an issue? I ask because I completed this and have no Wi-Fi. Just double checking I didn't miss something

raimondomartire said:
Use this
http://www14.zippyshare.com/v/ufYG71o0/file.html
Click to expand...
Click to collapse
My problem is getting the drivers to work. I've tried Robin. That succeeded. But updating drivers in Device Manager doesn't work. It says there are no compatible drivers for the phone. And if I can't update drivers I can't get the phone to be recognized in Device Manager so adb can work

edit

DarkestSpawn said:
I remember seeing something about no Wi-Fi in the other thread from the chat about source code. Is that still an issue? I ask because I completed this and have no Wi-Fi. Just double checking I didn't miss something
Click to expand...
Click to collapse
Try switching slots in Twrp then restart.

I have a bit of an issue. TWRP has been flashed to both A and B because it didn't reboot to TWRP the first time so i did it again and now i can't boot into system. Stupid mistake i know but what can i do about it?

Xshooter726 said:
Try switching slots in Twrp then restart.
Click to expand...
Click to collapse
No problem also for me. I can share my slot b image
---------- Post added at 02:59 PM ---------- Previous post was at 02:44 PM ----------
Firebuster said:
I have a bit of an issue. TWRP has been flashed to both A and B because it didn't reboot to TWRP the first time so i did it again and now i can't boot into system. Stupid mistake i know but what can i do about it?
Click to expand...
Click to collapse
Try to boot in bootloader mode from twrp and after write fastboot reboot

Installing TWRP makes me crazy

Hello !
Just acquired an HTC U12+ in replacement for my brave Oneplus One, that i kept updated to Android Pie. Compare to my old One, HTC didn't make it easy to make mod...
As I hate all these stupid UI, i want AOSP without the google app as much as i can, so i wanted to try the Android Pie GSI "FLOSS", hoping it works great.
Anyway since yesterday i spend a lot of time trying to install TWRP on my U12, and fastboot and adb make me crazy. First i unlock the bootloader with the describe procedure, it works fine, i use fastboot from offical repo of ubuntu 18.10. I red all the thread and understand that i must boot first twrp and then flash it with the installer. The problem is fastboot and adb are not working after unlocking the bootloader. I am using the USB type C to type A cable from HTC.
My phone was with firmware 1.25 with june patch when i bought it. So i download the right version of TWRP. Fastboot is not working anymore and i get an error of "protocol". Then i see in the FAQ that you need to use the last version from google. This fastboot didn't worked much more, "too many links" error or similar. I tried different usb port of my pc, it seems the usb 3.0 and 3.1 do this, with usb 2.0 error is different, it said "downloading boot.img" and nothing happens. Then i tried to update to 1.30, but fastboot is not working more. I tried in windows, i install the htc driver and use the latest fastboot, same errors. Also tried another pc running ubuntu 18.04 without success.
Right now "fastboot devices" find the U12 properly but all command show error, and "adb devices" shows nothing in download mode.
I guess the problem come from the usb cable ? I live in a small town in the middle of nowhere and have no type c cable, so i ordered two new cable among other accessories, i hope they works but i won't have them before two week probably more (revolution in coming in France ).
But what i don't understand, if it's a problem with the cable, why fastboot was working when i do the "fastboot flash unlocktoken Unlock_code.bin" to unlock the bootloader, and then it refuse to work ?
Regards !

When you do fastboot devices and U12 shows up then you should be alright.
To boot TWRP you must be in boot loader, NOT download mode.
fastboot boot twp.img
It has worked for me just fine on windows, macOS, and Ubuntu
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Use
fastboot --version
To see what fastboot version you have. Latest should be 28.0.1

Hello,
Thank you for your answer. I know the difference between the fastboot and download mode, i try everything but the problem is always the same. My fastboot is the latest from the xda topic :
./fastboot --version
fastboot version 28.0.1-4986621
For example i just try again, it's connected to the usb 2.0 port of my pc, i'm in fastboot (recovery) and not download mode :
./fastboot devices
FA8731F01429 fastboot
./fastboot boot twrp-3.2.3-2-ime.img
Downloading 'boot.img' ... and nothing happens
If it's connected to usb 3.0 or 3.1, get the "too many links" error.
Edit : another exemple, if i use the fastboot from kubuntu 18.10 repo :
[email protected]:~$ fastboot devices
FA8731F01429 fastboot
[email protected]:~$ fastboot boot twrp-3.2.3-2-ime.img
< waiting for any device >

@ghstmm
I've read your posts and I can't stop feeling that there's something off, obviously. Don't be mad at me cuz I'm not an expert, but you might be in the wrong mode. You should be in "Bootloader" mode which is different than "Recovery" mode.

That is a strange issue.
Several users on the Pixel 2 forum had the same issue and a different cable worked. I don't know how a cable only works with certain commands.
Looks like you're doing it right however. Unfortunately it might simply be a cable.
Maybe try flashing a boot.img that already has twrp in it so you can just use the bootloader recovery option?
---------- Post added at 08:35 AM ---------- Previous post was at 08:27 AM ----------
k_l_o said:
@ghstmm
I've read your posts and I can't stop feeling that there's something off, obviously. Don't be mad at me cuz I'm not an expert, but you might be in the wrong mode. You should be in "Bootloader" mode which is different than "Recovery" mode.
Click to expand...
Click to collapse
You should be on this screen.
BOOTLOADER
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yes i am to this screen when i use fastboot. Not have the same info in the screen though. I cannot make a photo now so i will just write what i see :
press volume key etc...
Fastboot Mode (in red)
PRODUCT_NAME - HTC_Phone
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - FA8731F01429
SECURE BOOT - PRODUCTION
SECURE STATE - S-ON
DEVICE STATE - UNLOCKED (U) (in red)
KEY STATE - NONE
*** Software status: Modified *** (in red)
Guess i will try again when i'll get the other cable, but it's very strange indeed.

@ghstmm
Have you installed the latest HTC drivers?
Edit:
Forgot to mention I had the "too mank link" error because my HTC Drivers were out of date when I replaced my HTC 10 with the HTC U12+

k_l_o said:
@ghstmm
Have you installed the latest HTC drivers?
Edit:
Forgot to mention I had the "too mank link" error because my HTC Drivers were out of date when I replaced my HTC 10 with the HTC U12+
Click to expand...
Click to collapse
I mostly use linux so their is no driver, but in windows i install the HTC SYNC MANAGER. It finds the phone when firmware was in 1.25, but after update to 1.30 i got a message saying this software is deprecated and the manager didn't find the phone. What driver should i use ?
Regards

ghstmm said:
I mostly use linux so their is no driver, but in windows i install the HTC SYNC MANAGER. It finds the phone when firmware was in 1.25, but after update to 1.30 i got a message saying this software is deprecated and the manager didn't find the phone. What driver should i use ?
Regards
Click to expand...
Click to collapse
I brought up the HTC Sync Manager only for the purpose of installing the drivers. I uninstall the Sync Manager portion of the package afterwards. Anyway, try this link for the latest HTC Driver:
http://www.mediafire.com/file/g4r62oz2v9b1x0q/HTC-Mobile-Driver-v4.17.0.001.zip

I was already in v4.17.0.001. Guess i have to wait now for the new cable, hope it solve the problem...

Hello,
Normally no problem with the cable provided in the box of HTC! It is true that the U12 is pretty capricious! sometimes it takes several times with ADB!
It is not a problem of ADB version even the version 'htc_fastboot' of 2016 works at home!
PS: The most painful is the touch button to go into bootload Pffffffffff

Alan-B said:
Hello,
Normally no problem with the cable provided in the box of HTC! It is true that the U12 is pretty capricious! sometimes it takes several times with ADB!
It is not a problem of ADB version even the version 'htc_fastboot' of 2016 works at home!
PS: The most painful is the touch button to go into bootload Pffffffffff
Click to expand...
Click to collapse
I don't have any problem with adb, it works always without issues. Yeah sometimes it's difficult to boot into bootloader, but I use adb for that also
Sent from my HTC U12+ using XDA Labs

Just to know, when you run fastboot boot image are in you in the correct directory where the image file is?

master66 said:
Just to know, when you run fastboot boot image are in you in the correct directory where the image file is?
Click to expand...
Click to collapse
I try pretty much everything, inside or outside the platform-tools directory, also renamed twrp several time but no success.
Good news, i make it works I receive the cables todays, and even if the fastboot boot twrp.img still didn't work for any reason, adb works with the two cable i ordered. So i root the phone and use magisk to install twrp.
Strange thing, adb didn't work in download mode, only in android.

ghstmm said:
I try pretty much everything, inside or outside the platform-tools directory, also renamed twrp several time but no success.
Good news, i make it works I receive the cables todays, and even if the fastboot boot twrp.img still didn't work for any reason, adb works with the two cable i ordered. So i root the phone and use magisk to install twrp.
Strange thing, adb didn't work in download mode, only in android.
Click to expand...
Click to collapse
If fastboot wasn't working, then it's a driver issue. If you're in bootloader/download, you have to install them completely new again. Also TWRP has to be booted from bootloader, not download....
Sent from my HTC U12+ using XDA Labs

DeeZZ_NuuZZ said:
If fastboot wasn't working, then it's a driver issue. If you're in bootloader/download, you have to install them completely new again. Also TWRP has to be booted from bootloader, not download....
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Hello,
Again i was using the fastboot to fastboot, and download to adb
However i get a more serious problem. Now that twrp is working i tried to flash the gsi img. It works but when i start android ask me a password, so i look for the problem and it seems i just didn't wip data. I go back to twrp and perform data and wipe again, i wanted to flash again the gsi image. Problem is their wasn't anything in the sdcard directory (i didn't wip internal storage, so why ?). I try to adb to push to send again the gsi img, but when i go to twrp and go to the adb option, i get "adb devices sideload" and every command :
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb push /home/satan/system-arm64-ab-floss-su.img /sdcard
adb: error: connect failed: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb usb
error: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb devices
List of devices attached
FA8731F01429 sideload
I guess i got a very bad idea to reboot my phone as their was no os. So now the phone is rebooting constently. How i can i go again to twrp ?
Edit : i didn't understand everything from this A/B partition system... i guess my phone is brick now ?

ghstmm said:
Hello,
Again i was using the fastboot to fastboot, and download to adb
However i get a more serious problem. Now that twrp is working i tried to flash the gsi img. It works but when i start android ask me a password, so i look for the problem and it seems i just didn't wip data. I go back to twrp and perform data and wipe again, i wanted to flash again the gsi image. Problem is their wasn't anything in the sdcard directory (i didn't wip internal storage, so why ?). I try to adb to push to send again the gsi img, but when i go to twrp and go to the adb option, i get "adb devices sideload" and every command :
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb push /home/satan/system-arm64-ab-floss-su.img /sdcard
adb: error: connect failed: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb usb
error: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb devices
List of devices attached
FA8731F01429 sideload
I guess i got a very bad idea to reboot my phone as their was no os. So now the phone is rebooting constently. How i can i go again to twrp ?
Edit : i didn't understand everything from this A/B partition system... i guess my phone is brick now ?
Click to expand...
Click to collapse
No not bricked, but you can't sideload an img. Just get it back to sdcard and flash it from there, also for GSI it is better to wipe from stock recovery
Sent from my HTC U12+ using XDA Labs

Ok but how do i go back to the recovery ? The phone is just constently rebooting. From now to go to recovery i waited to be in android, press power button and down right after black screen, now i can't do that.

ghstmm said:
Ok but how do i go back to the recovery ? The phone is just constently rebooting. From now to go to recovery i waited to be in android, press power button and down right after black screen, now i can't do that.
Click to expand...
Click to collapse
This is a quote from the root thread:
"Long press (sometimes really long!) the Power button until you feel the vibration motor (not the feedback) kick in. When it kicks in let go of power button quickly and push volume down to boot into bootloader."
If I remember correctly this is how I was able to get my phone into bootloader when my phone was also in a boot loop. The timing must be precise or you will not get it into bootloader mode. Good luck.
Sent from my HTC U12+ using Tapatalk

mauiblue said:
This is a quote from the root thread:
"Long press (sometimes really long!) the Power button until you feel the vibration motor (not the feedback) kick in. When it kicks in let go of power button quickly and push volume down to boot into bootloader."
If I remember correctly this is how I was able to get my phone into bootloader when my phone was also in a boot loop. The timing must be precise or you will not get it into bootloader mode. Good luck.
Sent from my HTC U12+ using Tapatalk
Click to expand...
Click to collapse
Ok i get it Short timing indeed.
Edit : I finally install the latest android 9 pie gsi. It's working great and i love the floss version, but their is a few bugs : no brightness adjustment, localisation not working and few screen bugs (icon mostly).
Anyway thanks you all for your help

How to boot into recovery of start 101 tablet?

Hi, i have a start 101 tablet with a Cortex-A9 cpu, a WM8850 chipset and a Mali-400 GPU and i do have root, it has android 4.0.3, im not very good in these things but i wanted to install google apps on this tablet, i already found a site that gives some links to some zip files for every android version, but i don't know how to install them. The site that gave those zip said that you need to boot into the recovery of the device and press install from zip, but the problem is that my recovery doesn't have any menu on it.
So 2 days ago i tried finding a way to boot into the recovery, holding the power button and volume up do not take me to the recovery, they take me to a screen which says "do you want to do system recovery? press power button before 10 seconds to confirm" and if i press the power button the tablet factory resets, if i wait 10 seconds the tablet shuts down, i also tried holding the power and volume down buttons but they just took me to normal android.
Now yesterday i found a way to boot into the recovery by using an adb command or by using an app called "Reboot manager ROOT", but the problem is that when i use abd or this app and reboot to the recovery, an android robot with a red triangle appears without any menu on it, and searching this on the internet i was told to basically press power and volume up / down untill a menu appears but i can't get this menu to show up, and since there is no menu if i hold the power button to reboot im stuck into this boot to recovery loop unless i factory reset which works and takes me back to normal android, so then i was thinking that maybe the recovery in this tablet does not exist but is that possible? im not very experienced with this but i also found out about custom recovery yesterday, so after like 5 hours on the internet i found a cwm recovery for my chipset and i saw a video on youtube that said that if you had a twrp/cwm recovery for the same chipset of your android device you can make a custom recovery for your device, the video i followed is this:
so i made this custom recovery img file now but how can i flash it? or can i just use the recovery that is already into my tablet to install the google apps?
because i searched the internet a bit and it seems that for flashing a recovery you need to go to the bootloader but i can't access this thing for some reason, power + volume down takes me to normal android so then i tried adb reboot bootloader but it also takes me to normal android, then i also tried the same app i used to reboot into recovery (reboot manager root) but pressing the reboot to bootloader buttons also does not work (it asks for root permission, i press allow and then it reboots to normal android) same with the reboot to download mode button, then as a last attemp i downloaded an app called "flashify" which basically allows to flash recovery, zip and etc, so i first tried to flash the recovery but pressing the button choose file made the app freeze, so then i tried the flash zip option to maybe flash google apps without recovey, but after choosing the zip it gets stuck at downloading 92% and the app freezes and it doesn't seem to have installed the google apps, do you know if there is any way to boot into this bootloader to flash this cwm recovery or maybe any way i can get the normal recovery to work?
i also have the tablet model url, here it is: http://www.start-tablet.it/tablet_start10_it.php
you can also get the english page version here: http://www.start-tablet.it/tablet_start10_en.php
also sorry for my bad english and bad explanation,
thanks for the help!
I also found a picture of what the normal recovery shows me, i will attach the jpg.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Update: i went to a local store and he said that the tablet doesn't have the bootloader so rip i guess

Every Android device has a bootloader, unless it gets removed by user: without a bootloader Android OS couldn't get started.

jwoegerbauer said:
Every Android device has a bootloader, unless it gets removed by user: without a bootloader Android OS couldn't get started.
Click to expand...
Click to collapse
hi and thanks for the reply, well then do you know any way i can access it? because the guy at the shop said that my tablet was too old that it didn't have one, i tried going into the bootloader with adb using the computer and also using an app on the tablet itself, both of those method don't work and they just boot normal android.

ADB deals with Android OS, whereas FastBoot deals with device's bootloader: totally different softwares.
To operate on its bootloader, device's bootloader must get made accessible, known as get unlocked: this gets enabled within Android -> Settings -> Developer options.
FYI: As with Android, recovery refers to the dedicated, bootable partition that has the recovery console installed from which you can perform specific tasks.

jwoegerbauer said:
ADB deals with Android OS, whereas FastBoot deals with device's bootloader: totally different softwares.
To operate on its bootloader, device's bootloader must get made accessible, known as get unlocked: this gets enabled within Android -> Settings -> Developer options.
FYI: As with Android, recovery refers to the dedicated, bootable partition that has the recovery console installed from which you can perform specific tasks.
Click to expand...
Click to collapse
hi, what i meant is i tried to type adb reboot bootloader into the cmd and it booted to normal android, now im going to turn on the tablet and go into the developer option to check if there is a bootloader thing to enable, so how do i unlock it? i go to the developer option and then what do i need to press?

jwoegerbauer said:
Click to expand...
Click to collapse
hi, unfortunately i didn't find any option that was talking about the OEM or the bootloader in the developer settings, i could try to attach the screenshots of all the developer settings i have, but i was also thinking that maybe the root is causing issues?

If I were you I would completely reset the tablet
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>

jwoegerbauer said:
If I were you I would completely reset the tablet
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
Click to expand...
Click to collapse
ok the stockrom is on the site only problem is that well it's 404 not found, but i will try archive.org, also should i unroot first?

jwoegerbauer said:
If I were you I would completely reset the tablet
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
Click to expand...
Click to collapse
hi, uhm the stock firmware isn't archived on wayback machine
http://www.start-tablet.it/ftp/START-LOGO_V1.5.1_20130107.zip
also i never changed the rom, i just rooted the device a long time ago so maybe the un-root will fix stuff? if not how can i find the stock firmware?

Hi, it's me again, i know this is kinda old but since i have the same problem i will say it here, basically i gave up on this device in june of last year but now i want to try again, im still having the same issue (in recovery i see no menu, i only see the android logo with a red triangle, and yes i tried power button + volume down or up and even both, but none of this key combination made the menu show up) so im stuck and i don't know what to do, i unrooted the device to see if maybe it could affect anything but it didn't so i rooted again with kingroot.
I also have the cwm recovery made for this tablet but i can't flash it because i can't access the bootloader, i tried to boot with volume down, adb reboot bootloader, and even one app on android that reboots to bootloader if you have root (which i have), from what i found on the internet my bootloader should be unlocked because i was able to root, i also tried apps like flashify and rashr to flash the cwm recovery but they don't work, after i give them root access i tried to flash with Flashify and when i press the button to select the zip file it just hangs the application,
with Rashr it gives "Failed Execute".

+bump

jonnyprogamer said:
Hi, it's me again, i know this is kinda old but since i have the same problem i will say it here, basically i gave up on this device in june of last year but now i want to try again, im still having the same issue (in recovery i see no menu, i only see the android logo with a red triangle, and yes i tried power button + volume down or up and even both, but none of this key combination made the menu show up) so im stuck and i don't know what to do, i unrooted the device to see if maybe it could affect anything but it didn't so i rooted again with kingroot.
I also have the cwm recovery made for this tablet but i can't flash it because i can't access the bootloader, i tried to boot with volume down, adb reboot bootloader, and even one app on android that reboots to bootloader if you have root (which i have), from what i found on the internet my bootloader should be unlocked because i was able to root, i also tried apps like flashify and rashr to flash the cwm recovery but they don't work, after i give them root access i tried to flash with Flashify and when i press the button to select the zip file it just hangs the application,
with Rashr it gives "Failed Execute".
Click to expand...
Click to collapse
Hello did you try a temp recovery?

notnoelchannel said:
Hello did you try a temp recovery?
Click to expand...
Click to collapse
Hi, thank you very much for replying, no and i don't exactly know what that means, can you explain it to me? Thanks.

I just want to flash the CWM recovery because i want to sideload the Google Apps, but since i can't find a way to go into the bootloader im trying to do it from adb shell, i also tried "flash_image recovery /path/to/recovery/" but it doesn't find the flash image command.

jonnyprogamer said:
Hi, thank you very much for replying, no and i don't exactly know what that means, can you explain it to me? Thanks.
Click to expand...
Click to collapse
Hello, temp recovery is flashable anytime FROM stock recovery but will not keep as your permanent recovery.Do you want a link for it?

jonnyprogamer said:
I just want to flash the CWM recovery because i want to sideload the Google Apps, but since i can't find a way to go into the bootloader im trying to do it from adb shell, i also tried "flash_image recovery /path/to/recovery/" but it doesn't find the flash image command.
Click to expand...
Click to collapse
adb push "/path/recovery.img" "/dev/recoverymount"
can you try it on ur pc? Replace recoverymount with your recoverys partition

notnoelchannel said:
adb push "/path/recovery.img" "/dev/recoverymount"
can you try it on ur pc? Replace recoverymount with your recoverys partition
Click to expand...
Click to collapse
Thanks, how can i find my recovery partitions?

jonnyprogamer said:
Thanks, how can i find my recovery partitions?
Click to expand...
Click to collapse
Can you send me your recovery.img? I'll send your recovery mountpoints and i can port a recovery for you