I seem to have soft-bricked my one-v and could really use some pointers.
The things I did to get the phone bricked:
- Unlock the bootloader
- Try to flash miui.
Since this attempt the phone only boots until the "quietly brilliant" screen appears (with a red "This build is for development purposes only..." warning, but I guess this just indicates the bootloader is unlocked right?)
Since then I have installed ClockWorkMod recovery image. This seems to work, I can get in recovery mode and do things like install specific zip files from sdcard.
Unfortunately whatever ROM I try to flash the result is the same: boot until the quietly brilliant screen and then nothing.
For instance, I tried to flash shpongle_primou_20130521.zip (the One-V is the GSM version) using the following steps:
- Download the above zip file
- Extract boot.img
- Copy the above zip file to sdcard using another phone (cannot boot with the one-v so I cannot use it to write to sdcard)
- Put the sdcard back into the One-V
- Start the phone in fastboot mode and connect to USB
- use fastboot to flash boot.img (flashboot flash boot boot.img)
- Switch to recovery mode
- Use ClockWorkMod to flash the zip file
- Reboot the phone
Result: hang in quietly brilliant screen. If I just let the phone alone it seems to reboot every 5 minutes or so.
I fear that I am doing something stupid due to a lack of understanding of some basic concept. Can you guys give me some pointers on how to proceed to unbrick the phone?
it seems u have not flashed the correct kernel for shpongle (the boot img inside zip doesnt work)
try this kernel (ONLY FOR SHPONGLE) http://www.mediafire.com/download/vj8vv8hjyhzg3xv/boot-HELLBOY-42-201305202359.img
Also do factory reset from recovery everytime u flash a rom( u can backup data via titanium backup)
Also, your command command should be fastboot flash boot boot.img.
Sent from my HTC One V using xda app-developers app
Awesome, I got SHPONGLE to work. Installing the correct boot.img and clearing all data did the trick.
Now I can try to install miui again but I have a stable situation (and backup ) to work with.
Thanks a lot!
I have the same issue with my HTC one V but it is the virgin mobile version ( I live in the east coast of U.S.A.)
Will I be able to use the same solution?
which is the right ROM and Kernel for me?
Related
Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)
oh and ....
ALSO I've googled the problem and tried all of the options I can find which could help - please don't just send me a link to a page because i can guarantee I've probably already tried the solution and failed. When I boot into recovery, I can't use adb push to send files to the phone because it says it's not connected even if i try the option for mount data, or mount storage - the only time windows seems to manage to aknowledge it's existence is on the fastboot screen -
lazclark said:
Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)
Click to expand...
Click to collapse
Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app
thanks!
wow that was a quick reply - yes I've flashed the cm boot img and erased the cache - which version of CWM is the latest? - When you say mounting as USB storage is fixed, do you mean that windows will be able to see the device and write files to it?
(I'm really sorry for asking these questions - the problem is that I know a BIT about how android works but not as much as I should do)
treebill said:
Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't
This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!
sorry hope i'm not wasting your time!
I ran the command as follows :-
fastboot flash boot boot_signed.img
(I got the img file from the ruu )
I'm not 100% sure if it worked, but at that stage I didn't see any errors
Michealtbh said:
Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't
Click to expand...
Click to collapse
CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache
thanks!
I'll give it a go - to be honest i don't insist on using cm10 at all - i just wanted to see what jellbean was like and it seemed like a reasonable way of achieving that.... i'd be quite happy with any decent rom if it can fix the lag problems i have and some of the other issues.....
great tutorial by the way! - once my phone has charged up again I'll try it
ORStoner said:
This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!
Click to expand...
Click to collapse
ahhhh!
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
BenPope said:
CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache
Click to expand...
Click to collapse
Thanks.
I use CM10 myself at the moment because of the aesthetics, but because of the amount of ram and battery it uses I wish I had stuck with ARHD.
Come October we should see Jellybean ARHD which will have great features like USB OTG without a powered hub.
lazclark said:
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
Click to expand...
Click to collapse
Mount as USB not working on that version, also charging not working either. It was not a great release in terms.of features, but it was updated quickly, that's quite an.old version now.
Do you know which tutorial you followed? It really needs updating, there are a lot of people on this old version struggling more than they need to.
Right, first you're going to flash a recovery which allows you to mount USB storage. Either cwm or TWRP, download the recovery.img and flash through fastboot using fastboot flash recovery rocoveryname.img.
Download a new rom and extract the boot.img from it. Flash that boot.img using the usual fastboot method.
Now boot into the new recovery, connect to your pc and mount USB storage from the option in recovery. Copy over the rom you downloaded. Unmount USB storage. Now do a full wipe through the menu in recovery - format /data, /system and /cache. Now flash the rom and reboot
hi
i already unlock the bootloader, install custom recovery TWRP, and done a backup
i also copy my backup to PC
now i'm confuse
- i need to root the phone or can i just flash the new room?
- if i need to root the phone i found an italian guide on 4.0 and attach file, can i use that? i have 4.1.1 on mine now
i'm not interested to have HTC stock with root but what i want is to install MIUI ROM
this is the only guide i found in english that explains how to install the rom
external link (i can't post it) miuiandroid.com/community/threads/installing-the-htc-one-x-required-s-on-steps.16592/
what i understand is:
- boot my device power + menu down, to see the FASTBOOT USB i have to select FASTBOOT
- flash the boot.img
- press the power button once (HBOOT i guess), click volume down, highlight recovery & press power
- Flash the downloaded ROM via recovery normally and it followup at this link
external link (i can't post it) miuiandroid.com/community/threads/how-to-update-upgrade-miui.15424/
i need to copy the img rom in SD ROOT before starting with all this process
- now i need to Wipe data/factory reset, Cache Wipe & Dalvik Cache Wipe in all tutorial i found this is done with clockworkmod
in TWRP under menu WIPE i guess are System, Cache, Dalvik buttons
after that i'm note sure if i need to flash italian language, if i don't need and i can just download it later i tihink is not a big deal
unless is all in chinese
is the metod correct?
do i have to copy ROM file in .zip format as i download?
here where i found ROM
from official site grey button miui.com/download-7.html
OR
from UK web site miuiandroid.com/community/threads/3-4-28.20232/
the boot.img is here
point 3 miuiandroid.com/community/threads/installing-the-htc-one-x-required-s-on-steps.16592/
i'm not sure if would be better to use clockworkmod, since most tutorials use that..
thanks
Doesn't matter which recovery you use. Yes just place the zip file on your sd card. Flash boot.img as you already said. Perform a full wipe and then flash the Rom zip. Reboot and its done.
The Roms are pre-rooted so you dont need to worry about that. Italian language should be included i guess.
Sent from my HTC One X using xda app-developers app
Heres what i do :
1) Put Rom.zip on SD card
2) Put boot.img in fastboot folder
3) fastboot erase cache
4) fastboot flash boot boot.img
5) fastboot erase cache
6) Reboot into recovery
7) Full wipe (except sd card)
8) Install rom
9) Enjoy new rom
Andy
i did my first mess but fortunally i could restore since i had copy the backup on my mac too
i don't know what went wrong but this is what happened:
- i did how was told before, but actually i download boot.img and rom from 2 different sites
- after reboot it didn't move from first screena waited for 15 minutes almost, so i did reboot in recovery tri to wipe but nothing happened
- so i decide to restore... but it did boot even if it was successful
- i thought that if i flashed the boot.img first time i may need to do it again, i found boot.emmc.win, rename it to boot.img, flash it and then i restored successfully
:victory:
now, to try a different rom i need to restore (maybe is safer)? can i copy the rom from recovery or fastboot?
what can it be wrong with my miui rom? could it be boot.img and rom file mismatch? can't find where to download both
al404 said:
i did my first mess but fortunally i could restore since i had copy the backup on my mac too
i don't know what went wrong but this is what happened:
- i did how was told before, but actually i download boot.img and rom from 2 different sites
- after reboot it didn't move from first screena waited for 15 minutes almost, so i did reboot in recovery tri to wipe but nothing happened
- so i decide to restore... but it did boot even if it was successful
- i thought that if i flashed the boot.img first time i may need to do it again, i found boot.emmc.win, rename it to boot.img, flash it and then i restored successfully
:victory:
now, to try a different rom i need to restore (maybe is safer)? can i copy the rom from recovery or fastboot?
what can it be wrong with my miui rom? could it be boot.img and rom file mismatch? can't find where to download both
Click to expand...
Click to collapse
extract the boot image from the rom you are going to use
ok, i tryed again but now it get stack on Mi black screen
i waited 8 minutes but nothing happens, i also tried to wipe cache and davik, nothing happens
at list i get to black Mi screen
do i need to delete the boot.img from ROM zip?
what could it be?
1st u didn't mention which phone u r using
2nd dn't get confuse while downloading rom n .img file
Type in google
(Ur phone model) android development xda
U'll find all the stuffs related to ur phone
So try this 1 n remember before updating or rooting or anythg related to ur which can mess ur phone or can brick ur phone
I suggest u read twice the thread n procedures n also check thrice the stuff which u gonna need to perform ur act.
Sent from my GT-N7100 using xda premium
al404 said:
ok, i tryed again but now it get stack on Mi black screen
i waited 8 minutes but nothing happens, i also tried to wipe cache and davik, nothing happens
at list i get to black Mi screen
do i need to delete the boot.img from ROM zip?
what could it be?
Click to expand...
Click to collapse
i would try a different rom for now, viperx perhaps. and the boot image is in the rom zip, extract the boot img from the rom and put it in your fastboot folder then copy the rom to your sdcard. once you have done that, fastboot erase cache, flash the boot image, fastboot erase cache again, then back into recovery, wipe cache and dalvik just to be sure then use recovery to flash the rom and hey presto. all of the above is assuming you have the one x international tegra 3
I have htc one x european terga 3, as far as I know mini is only for tegra 3
what you describe is exactly what I did:
- I leave the rom zip ad it is, I didn't remove boot.imf that I extract, correct?
- when I flash I hit hoot fastboot, connect USB and fastboot change in fastboot USB, to go back I select Hboot and and hit power, prom there recovery
- I did unlock bootloader but did not get rooted my phone, could it be that?
al404 said:
I have htc one x european terga 3, as far as I know mini is only for tegra 3
what you describe is exactly what I did:
- I leave the rom zip ad it is, I didn't remove boot.imf that I extract, correct?
- when I flash I hit hoot fastboot, connect USB and fastboot change in fastboot USB, to go back I select Hboot and and hit power, prom there recovery
- I did unlock bootloader but did not get rooted my phone, could it be that?
Click to expand...
Click to collapse
read this post. at least twice!! http://forum.xda-developers.com/showthread.php?t=2069904 do not do the "unlock bootloader" section as you already did that
@nogotaclue sorry i read so many, and some of them sayed that root was not necessary if you flash a new rom, other sayed it could still be necessary... now i rooted with the app and did a new backup that i'm coping on PC
reading further it says: to wipe, install rom, and flash boot.img after
"Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it."
al404 said:
@nogotaclue sorry i read so many, and some of them sayed that root was not necessary if you flash a new rom, other sayed it could still be necessary... now i rooted with the app and did a new backup that i'm coping on PC
reading further it says: to wipe, install rom, and flash boot.img after
"Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it."
Click to expand...
Click to collapse
yes you can do it that way, i usually flash first but sometimes it does not work, so just flash it last as it says in the tutorial
after root, with the same steps, the ROM starts... but
touch screen is not working :crying:
now i'm gonna look arond to see if i found some post about that
this (kernel patch) solved my last issue
http://miuiandroid.com/community/threads/hox-miui-v5-official-release.20215/page-2
al404 said:
this (kernel patch) solved my last issue
http://miuiandroid.com/community/threads/hox-miui-v5-official-release.20215/page-2
Click to expand...
Click to collapse
So everything working now ?
Sent from my underpants using Daz and Lenor summertime
YES :good: without that path touchscreen wasn't working :victory:
hope is not going to mess all up with first update
Hi Dudes and Dudettes.
PLease go easy on me - I am a noob.
Ive been handed a HTC ONE X (International version) that is stuck in aboot loop.
On power on, it simply goed to cyanogen load screen, and stays there forever (till the battery runs out or the phone is powered down)
I dont know what has been done to this phone, but I do know the following:
1. It seems to be rooted (Says UNLOCKED in Fastboot/bootloader screen)
2. Has CWM installed, can access it via Recovery.
3. Can not be restored via Backup/Recovery in CWM.
4. Does not have any roms on the device (tried zip file recovery - doesnt work)
5. Wiping of caches doesnt help.
6. Factory reset doesnt work either.
So I am thinking that I should prolly get a rom on the device and install it.
My question is HOW do I get a ROM on this phone if it is stuck in a loop?
Seem like windows picks it up (its visible in device manager) but doesnt show up as a drive in my computer.
Any help will be greatly appreciated.
Cheers!
heinrichvr said:
Hi Dudes and Dudettes.
PLease go easy on me - I am a noob.
Ive been handed a HTC ONE X (International version) that is stuck in aboot loop.
On power on, it simply goed to cyanogen load screen, and stays there forever (till the battery runs out or the phone is powered down)
I dont know what has been done to this phone, but I do know the following:
1. It seems to be rooted (Says UNLOCKED in Fastboot/bootloader screen)
2. Has CWM installed, can access it via Recovery.
3. Can not be restored via Backup/Recovery in CWM.
4. Does not have any roms on the device (tried zip file recovery - doesnt work)
5. Wiping of caches doesnt help.
6. Factory reset doesnt work either.
So I am thinking that I should prolly get a rom on the device and install it.
My question is HOW do I get a ROM on this phone if it is stuck in a loop?
Seem like windows picks it up (its visible in device manager) but doesnt show up as a drive in my computer.
Any help will be greatly appreciated.
Cheers!
Click to expand...
Click to collapse
flash this custom recovery link
then go into recovery
connect your phone to PC or laptop
select USB mass storage in recovery
copy rom file into sd card
and flash rom in recovery
extract boot.img from rom.zip file in pc or lappy
flash boot.img in fastboot mode
and good to go..!!:good:
Poojan Patel said:
flash this custom recovery link
then go into recovery
connect your phone to PC or laptop
select USB mass storage in recovery
copy rom file into sd card
and flash rom in recovery
extract boot.img from rom.zip file in pc or lappy
flash boot.img in fastboot mode
and good to go..!!:good:
Click to expand...
Click to collapse
Thanks, i am going to try that now.
Not sure how to flash the custom recovery, but sure ill figure it out.
Will let you know.
thanks!
Shot a lot mate!
Its working. Must have been the img file.
Thanks!!!
Hello..
I have a HTC One X that I have a problem with, it goes into bootlop all the time, as soon as I install a rom so begins the Android fuss and I get FC on the program all the time and then after a few minutes the phone turns off himself and restarts again and I can only see the HTC logo.
I have tried to Factory Reset and i didnt help..
My cid is: HTC__Y13
Adrianiii said:
Hello..
I have a HTC One X that I have a problem with, it goes into bootlop all the time, as soon as I install a rom so begins the Android fuss and I get FC on the program all the time and then after a few minutes the phone turns off himself and restarts again and I can only see the HTC logo.
I have tried to Factory Reset and i didnt help..
My cid is: HTC__Y13
Click to expand...
Click to collapse
Are you flash the boot.img from the ROM archive?
Thant said:
Are you flash the boot.img from the ROM archive?
Click to expand...
Click to collapse
Yes i always flash boot.img from fastboot before flashing roms.
Adrianiii said:
Yes i always flash boot.img from fastboot before flashing roms.
Click to expand...
Click to collapse
1.Make sure you are using the right kernel version for the Rom,and for your device (CM based kernels for CM based Rom's,and Sense for Sense,etc..)
2.Make sure you are flashing boot.img using the correct commands and a procedure
3.And make sure that recovery is compatible with the rom (example Viper rom and Phil'z advance recovery,etc..)
The right commands for flashing the kernel are
1.Go into fastboot mode on your phone
2.Connect the phone and PC
3.command is: fastboot flash boot.img (you can drag and drop your boot.img of choice right in the command window instead of typing the whole name of it)
4.after flashing it's done do the: fastboot erase cache without leaving the terminal
5.Now just unplug the phone from usb cable and reboot into recovery
6.Now find the zip of that kernel you've just flashed on your sd card (I assume you've placed it there) and install it by flashing that zip(that's where the modules are)
7.reboot and that should be it.
Fikus011 said:
1.Make sure you are using the right kernel version for the Rom,and for your device (CM based kernels for CM based Rom's,and Sense for Sense,etc..)
2.Make sure you are flashing boot.img using the correct commands and a procedure
3.And make sure that recovery is compatible with the rom (example Viper rom and Phil'z advance recovery,etc..)
The right commands for flashing the kernel are
1.Go into fastboot mode on your phone
2.Connect the phone and PC
3.command is: fastboot flash boot.img (you can drag and drop your boot.img of choice right in the command window instead of typing the whole name of it)
4.after flashing it's done do the: fastboot erase cache without leaving the terminal
5.Now just unplug the phone from usb cable and reboot into recovery
6.Now find the zip of that kernel you've just flashed on your sd card (I assume you've placed it there) and install it by flashing that zip(that's where the modules are)
7.reboot and that should be it.
Click to expand...
Click to collapse
I downloades this recovery: TWRP Recovery [2.7.1.0] [Unofficial] http://forum.xda-developers.com/showthread.php?t=2776581
I downloaded One_X_4.18.401.3_odexed stock rom from Mike.
Then i run the commands:
fastboot flash boot boot.img
fastboot erase cache
Then i unplug the phone and and reboot into recovery.
I do a factory reset and wipe data.
Then i choose to install the rom from sd card and the rom installs complete.
I start the phone then after a few minutes Google Play and Sense start to FC all the time and the phone restarts and hangs at the HTC logo and i cant do nothing anymore.
What im doing wrong, i have flashed roms several years and never had these difficulties.
Where can i find the kernels for stock roms?
Adrianiii said:
I downloades this recovery: TWRP Recovery [2.7.1.0] [Unofficial] http://forum.xda-developers.com/showthread.php?t=2776581
I downloaded One_X_4.18.401.3_odexed stock rom from Mike.
Then i run the commands:
fastboot flash boot boot.img
fastboot erase cache
Then i unplug the phone and and reboot into recovery.
I do a factory reset and wipe data.
Then i choose to install the rom from sd card and the rom installs complete.
I start the phone then after a few minutes Google Play and Sense start to FC all the time and the phone restarts and hangs at the HTC logo and i cant do nothing anymore.
What im doing wrong, i have flashed roms several years and never had these difficulties.
Where can i find the kernels for stock roms?
Click to expand...
Click to collapse
Here are some kernels
http://forum.xda-developers.com/showthread.php?t=2226360 (this one I've used on sense stock Rom,and it's a good one for battery life
http://forum.xda-developers.com/showthread.php?t=2588449 (here you have versions both for aosp and sense rom's,also great kernels from @audahadi )
And you can try some sense rom's other then mike's,cause as i understand his rom is something firmware dependent as well as cid,I'm not really sure cause I haven't used it or tried to flash it at all
Also think about trying regular cwm recovery or Philz,just try differnet stuff and I'm sure you'll figure it out.
Hello!
My Oppo Find 7 (international) seems to be bricked.
I'm on stock ROM COS 1.2.5 with stock recovery 1.0
After booting it stuck in the Setup-Wizzard with "settings has stopped"-Loop.
Unfortunately in stock-ROMs the USB-debugging is disabled, so i can't acces via adb fastboot to flash other recoverys.
And cause of the loop i can not enable USB-debugging...
The recovery (stock 1.0) let me only flash 1.2.5, no other ROMs work.
Things that work:
- entering fastboot (but no access via adb as i wrote)
- entering recovery and execute "zip from sd" (while sd means only internal sd here)
- normal boot to the f****** Setup-Assistant, enter PIN. At slect Language the "setting has stopped"-loop starts
- while the device is in loop, i can access the internal and external SD-card via PC, copy and delete files works
Please, has anybody an idea what to do ?
Thanks to all
Marco
Since you can get into fastboot, download a custom recovery, go to fastboot, type
fastboot flash recovery x
Replacing x with the full name and extension of the file, and install a ROM. Alternatively, if you want ColorOS, try downloading 1.2.4i, and installing it through the stock recovery. Then you can update from there
Hmmmm....
Positive! At this moment i learned that USB-debugging is needed for adb-access on a booted device, not for fastboot-access
Yes, i could flash TWRP via fastboot (puuhh, not bricked)
THANKS !!
Now i can mess around the "settings has closed"-Loop, wich is still in place.
(No wiping fixes the problem, even 1.2.1 nor 1.2.3 or whatever)
But i'm on the road again and can check out fixes.
Thanks again!!
That's weird. Did you ever install custom ROMs before having this issue?
Did you try formatting System in TWRP? But be careful, when you format System you have to install stock Color OS BEFORE rebooting your device. That means stay in TWRP after you format and install the ROM, then reboot.