Hey, so i got an Alcatel one touch idol x+ and i had android version 4.2.2 jelly bean, so i tried to update the system to kitkat 4.4 (with the official update) and it was going well (it used to fail immediatly after i tried to update) so it was almost finished when it gave me an error.So i restarted the phone and it redirected me to the system recovery screen and i tried everything, every option, tried to wipe everything, factory reset, and i can't put it to work again, i need some help :/
Notes:
The battery is built in
I don't have sd card since it only has internal memory
It sends me everytime to system recovery or it just says the name of the phone and gets stuck there
Related
Hi,
So I had my ROM rooted, and I was messing around with the Xposed settings. I flipped a switch, the phone rebooted and it wouldn't boot anymore...
So I decided to go ahead and just flash a new ROM (ARHD 10.2). To my surprise, when I try to touch the sdcard partition or the data partition, the phone automatically reboots. I wiped everything (except sdcard and data, because I can't touch them).
I tried to sideload the ROM with no luck.
My phone is a VODAP304, HTC One 32 Gb. I can use fastboot USB and the recovery (latest clockworkmod touch). However, like I said, I'm unable to flash a ROM because I can't do that from the sdcard, and if I try to sideload it, when installing, it instantly reboots.
What can I do? Am I bricked? I'm really worried as I need this phone in a week or so because I'm going to be away from home for a few days
Hi all,
Last night, i rooted by N7000 through PhilZ-cwm6-DDLSC-ODD-5.08.5-signed and was successful in doing that.
Later i wanted to update my device to 4.2.2. So i downloaded cm-10.1-20130727-NIGHTLY-n7000.zip file and kept in my external SD card.
Then in recovery mode,i wipe the factory data. There was option wipe data or wipe to install new ROM. I selected the latter one. Wipe for installing new om was successful. Then i went to update zip.file option. But since the file was in external sd card, it was not detected and i was not able to select the file. Then i rebooted the phone but only 'Samsung galaxy N7000' screen was coming and nothing was happening.
I rebooted my phone many times but same screen was coming. Then in morning i went in advance options. I selected Recovery Bootloader. Downloading screen was coming and nothing was happening. Then i switched my off and trying to start in recovery mode but its not starting.
I thin i have no checked USB debugging.
Kindly help soon as i am helpless without phone. Your early response will be highly appreciated.
With the option "install new Rom" you removed your old Rom from your device. So it is only logical that your device won't boot into it.
Next time follow the installation instructions given in the CM-thread exactly.
And of course you can choose a zip from external sd card in CWM. So take a look again.
Best thing to do for you: boot into download mode, install a stock Rom with PC Odin and use it without changing things.
Hey Thanks for the help. But now i am facing new problem.
I flashed my phone using odin with stock rom.
Later i rooted with PhilZ-cwm6-DDLSC-ODD-5.08.5-signed and then updated it with cm-10.1-20130727-NIGHTLY-n7000.
This time i was successful. My phone was updated to 4.2.2.
Then i used it for some time and switched it off for removing the external SD card. After that i tried to switch on my phone, its not working.
Nothing is appearing on screen. I charged it and then tried to switch it on but nothing is coming on screen.
When i try to switch on my phone in Recovery mode or in download mode a thin line on the screen appears and then disappears and then nothing comes on screen.
Help please. Last suggestion worked.Kindly advise
My moto g xt1063 keeps rebooting but I can't figure out why. Sometimes it goes to the home screen and works fine for a few minutes before rebooting again, most of the times it gets stuck on the bootloader warning screen and reboots. I can access recovery though.
I had planned to install cyanogenmod on it a couple of months ago but I got stuck on an "Error updater binary in zip" so I just gave up. The device is running Official Rom provided by Telcel (México) and has SuperUser on it too, I had a notification about the binary but updating didn't fixed the problem.
I have a backup on my computer (mac) but since I can't get the phone to sync by usb I was wondering how to copy it via recovery (clockworckmod v6.0.4.7) or if it's best to buy a micro sd and try to install from there.
Any help would be greatly appreciated.
First try a factory reset.
Use an sdcard yo retore backup
If fail return to stock rom
If you have a recovery installed try to make a backup from there and save it in some place like a sd card.
After that I suggest you install CM 12.1 21/05/2015 and look how it works.
Or if you prefer then reinstall the stock rom.
Hi guys.
I have a moto X 1058 which I bought to someone about 3 months ago, it's an used phone so I can't rely on warranty.
I received the phone with Android 5.0, no root, bootloader locked, perfect conditions.
I installed Android 5.1 through an OTA update. Soon after the update, the phone began to boot suddenly every now and then with no apparent reason. Because of this I decided to downgrade to Kitkat 4.4.4 (The rom I downloaded is called: RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF) (I am from Colombia and the firmware of the phone is from Brazil). I used RSD lite, unlocked the bootloader, USB debug, etc. However the installing took way too long so I booted the phone while it was still installing (If i didn't do this, the installing would have probably taken 8 hours or so, because the system.img file was too big to download to the phone which is why i guess it took RSD so long). Anyways, I don't know why this happened, I just decided to boot it and see what happened. It went in a boot loop. I no longer have access to the bootloader screen. After two boots I can press POWER+VOLUME UP to get access to the screen "Android system recovery". Where the only options are:
reboot system now (takes me to the boot loop again)
apply update from sdcard (does nothing really)
aply update from ADB (My pc won't recognize my device anymore, RSD litle doesn't recognize my device either, I tried with mfastboot manually but it says "waiting for device" and does nothing)
wipe data/factory reset (tried this option as well, but nothing)
wipe cache partition (nope).
What can I do? I think this means my phone is soft bricked. How can I fix this? How can I get the bootloader screen back? I can't even turn off my phone, it's stuck in this bootloop. The only thing i can do is to stay in the system recovery screen, but i don't know what to do next. I don't handle Android systems at all, everything I did was based on youtube tutorials, so I'm a little slow to understand the basic concepts. Can someone explain me?
Thank you very much.
You don't downgrade Motorola phones!
Sent from my iPad using Tapatalk
Is your device fixed now?
mlspot said:
Hi guys.
I have a moto X 1058 which I bought to someone about 3 months ago, it's an used phone so I can't rely on warranty.
I received the phone with Android 5.0, no root, bootloader locked, perfect conditions.
I installed Android 5.1 through an OTA update. Soon after the update, the phone began to boot suddenly every now and then with no apparent reason. Because of this I decided to downgrade to Kitkat 4.4.4 (The rom I downloaded is called: RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF) (I am from Colombia and the firmware of the phone is from Brazil). I used RSD lite, unlocked the bootloader, USB debug, etc. However the installing took way too long so I booted the phone while it was still installing (If i didn't do this, the installing would have probably taken 8 hours or so, because the system.img file was too big to download to the phone which is why i guess it took RSD so long). Anyways, I don't know why this happened, I just decided to boot it and see what happened. It went in a boot loop. I no longer have access to the bootloader screen. After two boots I can press POWER+VOLUME UP to get access to the screen "Android system recovery". Where the only options are:
reboot system now (takes me to the boot loop again)
apply update from sdcard (does nothing really)
aply update from ADB (My pc won't recognize my device anymore, RSD litle doesn't recognize my device either, I tried with mfastboot manually but it says "waiting for device" and does nothing)
wipe data/factory reset (tried this option as well, but nothing)
wipe cache partition (nope).
What can I do? I think this means my phone is soft bricked. How can I fix this? How can I get the bootloader screen back? I can't even turn off my phone, it's stuck in this bootloop. The only thing i can do is to stay in the system recovery screen, but i don't know what to do next. I don't handle Android systems at all, everything I did was based on youtube tutorials, so I'm a little slow to understand the basic concepts. Can someone explain me?
Thank you very much.
Click to expand...
Click to collapse
i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.
also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying: