My phone battery went off I plugged the charger and it boots me to twrp even though I didn't wish to open it when I press to boot me to system I still end up in twrp window... I also get this noffication
{
"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"
}
Au123456 said:
My phone battery went off I plugged the charger and it boots me to twrp even though I didn't wish to open it when I press to boot me to system I still end up in twrp window... I also get this noffication View attachment 5479285
Click to expand...
Click to collapse
Do you want to be able to modify your system partition(including rooting the device) at some point in the future? If so, check the box beside the "never show this screen during boot again" then just swipe the slider at the bottom to allow modifications in the future.
Or
If you do not plan to modify your system partition in any kind of way, tap the "keep read only" button.
This happened to me multiple times, for me it was an error with flashing Treble GSI from google, tho i fixed it by going in fastboot mode/bootloader and on my PC to flash boot, lk, lk2, recovery (official one) and then reboot my phone, but you will delete the TWRP Recovery just so you know.
_________________________________________________________________________________________________________________________
NOTE: I don't know if this will work for you and might brick your device if you don't use correct ROM files...
_________________________________________________________________________________________________________________________
Also if it then boots into Fastboot mode than you can try flashing all files (It will factory reset your phone)
You have to install adb and fastboot on your PC
Commands:
cd *the path to adb and fastboot*
fastboot devices
fastboot flash *what you wanna flash* *filename of the file that you wanna flash*
For Example if you wanna flash boot it will be like ( fastboot flash boot boot.img ) if the filename is with .bin wich most new devices use it will be fastboot flash boot boot.bin
Hope that this helps
Related
About the phone:
1. I dont know the exact phone model, but it is Cloudfone Ice plus. There is a phone called Cloudefone Ice (Huwawei u8500) but i dont know if mine has another name.
2. It looks like this,
h++p://cdn2.sulitstatic.com/images/2012/0926/222830332_22162996997ba02ceb979675b8093b33516b3b725d6504ce0.jpg
3. Adroid version 2.2.1
4. Detected as "Globe Phone" in Google Play Market. *Globe is a carrier in our country.
The Problem:
When I turn it on, the android logo appears, and stays like that forever.
Cause:
After I tried to install a custom ROM using update.zip in recovery mode, the process got aborted in the last part of the installation.
5. I'm not sure if it's fully rooted, I have superuser but when I tried Root Checker before, it's not.
Other info,
I already tried to boot in recovery mode(it's the only mode that I get into now), I wiped data and cache/factory reset.(still stuck on boot screen)
I tried to install other Roms(update.zip), but all gets aborted in the beginning
I tried to download an update.app file in a dload folder in the root of sd card(firmware for huwawei)- I can't go to update firmware.I can only go to recovery mode.
I tried adb, I can use adb devices, it shows MT(serial number)
adb shell shows adb shell exec '/system/bin/sh' failed: no such file or directory exists
superboot cant detect the device.
I boot the device using power button+volume up,
when I use power+volume down, android logo appears and "Factory Mode" in the lower left (then It stays there forever, whatever button i press)
These are the infos that I can give, please help, I'm looking for fixes since yesterday from google and forums but no luck, nothing works so I decided to post my own.
image
{
"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"
}
Click to expand...
Click to collapse
no spaces in link
{
"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"
}
Hello fellow BLACK owners, I know that HIVE has not got an update for a long time and is full of bugs but today I present you guys TWRP 3.0.2-2 for XOLO BLACK
CHANGELOG
Code:
TWRP 3.0.2-2:
Changed mount points.
TWRP 3.0.2-1:
Fixed a mount issue.
----
What works?
Everything, as far as I've tested it, everything works fine
----
Any bugs?
I haven't found any! If you do, please report.
----
How to flash?
Make sure you have unlocked your bootloader, guide can be found here.
Download, install and open Minimal ADB and Fastboot.
Execute adb reboot bootloader and your device will reboot into fastboot mode with the XOLO logo showing up. To ensure that your device is connected execute fastboot devices command and your device should be listed.
Download TWRP 3.0.2-2 for BLACK and then place it inside the Minimal ADB and Fastboot folder which could be found at C:\Program Files (x86)\Minimal ADB and Fastboot
Now execute fastboot boot twrp-3.0.2-2-black.img (If you don't want to flash the recovery and want to test it out before you do) and the device will temporarily boot into recovery mode.
If you want the recovery image to be flashed to your device then execute fastboot flash recovery twrp-3.0.2-2-black.img
Now, to reboot normally, execute fastboot reboot
How to reboot into TWRP recovery?
When your device is booted up normally, you can go to recovery mode via adb reboot recovery command or using third party apps which offer reboot options.
When your device is powered off, you can reboot to recovery by pressing both volume keys at the same time + power key.
----
CONTRIBUTORS
Me
lj50036 (Huge contribution, thank you!)
----
SOURCE
https://github.com/lj50036/android_device_xolo_black
----
NOTE: The tutorial part was a bit copied from here, sorry, I'm a bit lazy hehehe.
MINE!!!
lj50036 said:
MINE!!!
Click to expand...
Click to collapse
{
"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"
}
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Notice1:
U Pro has A/B partitions. to prevent issues its good to flash it in both slot, because i/we can not know on which partition you are
Notice 2:
This version only working on Eragon roms
Maybe soon I'll manage it to work on stock rom
Notice 3: Sdcard now working
DOWNLOAD
TWRP for 20180227 Base via Qfil Flashtools:
Go here : https://drive.google.com/file/d/1650peMjuk_WTFkxlufL84aJ6cMG5-g3q/view?usp=drivesdk
TWRP for 20180423 Base and newer:
Go here: https://drive.google.com/file/d/1vzDDVRl8vKMGzybVm_FYvufHlmOygOud/view?usp=drivesdk
INSTALLATION
if you use the old 20180227 Base you have to use Qfil Flashtools , because fastboot commands dont work in that Build.
we have a good guide of how to use FLashtools already
look here: https://forum.xda-developers.com/android/development/guide-elephone-pro-user-manual-t3775895
if you are on 20180423 Base and newer you can use fastboot commands
required : ADB and fastboot
enable usb debugging in developer settings.
do this:
Code:
adb shell
Code:
reboot bootloader
now we flash it in slot a
Code:
fastboot flash boot_a twrp.img
after that we flash it also in slot b
Code:
fastboot falsh boot_b twrp.img
Special thanks to
teamwin for this awesome custom recovery
@travis82 for his advices
And @skeleton1911 for his help
smartphone does not leave twrp
Thank you in advanced if you can help me.
Has given an error on startup and I can not restart system, restarting twrp
Givanildo01 said:
Thank you in advanced if you can help me.
Has given an error on startup and I can not restart system, restarting twrp
Click to expand...
Click to collapse
Join us on Telegram group
https://t.me/joinchat/GxIBOhKXi5I6bsNWOm6LFg
And for your problem it's because you are coming from stock rom and that's for the meantime not working because of data encrypted
my zenfone 4 problem:
it is charging but i am stuck at asus logo with rotating circle and whenever i am trying to get into droid boot it is showing an android with yellow helmet
{
"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"
}
As long as a phone powers on it's NOT hardbricked, but softbricked if Android doesn't get properly started.
even if it is soft bricked i am not able to get into recovery mode this was showing:
Re-flash phone's STOCK ROM.
damn, i am not able to get into fastboot dude that's what it is all about if i would be able to get into fastboot i would have flashed my phone long time ago.when i ty to get into fastboot android sign with yellow helmet appears.
My zenfone 4 problems:
access to droidboot or recovery (stuck at android icon with a yellow helmet), so i cant flash a rom or firmware.
Tried different combo keys, but always stuck with that android icon.
You typically re-flash a STOCK ROM by means of ADB Sideload method.
ook so for using adb sideload method u need to get into droid boot what i am saying it i am not able to get into droid boot mode and everytime i try an android sign with yellow helmet appears.
You are absolutely WRONG.
What you have to do is running ADB commands as follow
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ZIP_FILE_ON_PC_HERE>
i am noob please can u tell me the steps elaborately OKAY,
NOW I HAVE GOT IT BUT IS NOT SOWING ANY DEVIICES I HAVE CONNECTED MY MOBILE SEE:
Then you obviously never have enabled USB Debugging on phone what is prerequisite to run ADB commands.
jwoegerbauer said:
Then you obviously never have enabled USB Debugging on phone what is prerequisite to run ADB comso
Click to expand...
Click to collapse
so,now what should i do?
Was trying to flash my CN ROM to the WW ROM.
Forgot to turn on USB Debugging in Developer Tools.
Couldn't get it work using HunterTik's guide.
Ran flashall_ATF from windows explorer.
Command prompt flashed on screen then vanished.
Tried running flashall_ATF in an elevated command prompt.
It failed but has apparently wiped the ROM. Device is now stuck in boot loop to fastboot.
Whatever option I choose reboots the device back to fastboot.
Windows can see the device but adb devices returns List of Devices Attached is blank.
How do I recover the phone from here?
Found this thread Rog phone 5 stucked on fastboot
Ran this command: fastboot -v flash all WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
Received these lines of text & now device boots to splash screen, gets stuck there, reboots a few times then sends me back to fastboot.
Still can't access recovery mode
{
"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"
}
Device is now back in a fastboot loop with no access to any options but power off & restart.
Your phone is broken
Buy a new phone and don't try to mess with it next time
Flash back to CN and try again.
or, get a dump of the official firmware, then sent boot / recovery / super over fastboot manually.
[Windows] Asus OTA payload auto extractor
Since nobody is doing it, I thought I'd package it and just put it here to help people This is a packaged version of Vm03's payload dumper make to work with windows without installing python and other stuff I also included a single line script...
forum.xda-developers.com
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
yurishouse said:
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
Click to expand...
Click to collapse
9008 rescue is the direction I was headed & you're right. Although, on reflection, the partitions were already deleted prior to running the 'fastboot -v flash all xx.raw' command. Not sure how, since that command was the only thing I did which resulted in something happening.