Hi. Yesterday i had a problem installing a recovery from Cyanogenmod rom and i got the message of fast booting. I found a tutorial saying how to repair it and i followed it without any problem.
But now, when i boot the phone, y reach the "Android" bootanimation and it stays like that forever. What can be happening now? I had Cyanogen from Mik and flashed a stock froyo (now trying a stock gb, maybe that´s the problem)
Can i save the phone?
Greetings.
After flashing the stock GB, the phone remains the same, staying in the Android bootlogo for ever
Any idea?
You have to wipe data.
Via normal Android recovery? Because when i access to it it shutdowns :S
Yes, but after factory reset, phone should reboot.. For you it only shuts down?
Let´s see, i followed the tutorial and flashed a stock gingerbread (before a stock froyo).
Then, when i access the recovery , a little image with a box, a droid and a bar appears, but then it only reboots. There, when Android bootanimation shows, the phone stays like that for ever and i need to quit the battery.
Edit: I accesed the recovery, but i can´t push any option, only go up and down.
strange.. the bar need to load till end and then the phone reboots.
maybe you have to wait for longer at bootanimation? because the first boot takes longer.
if not, try to flash ROM again, with kdz.
Edit: the menu button doesn't work?
I flashed like 3 different roms and waited in one of them 7 hours to boot. When it access the recovery it appears a warning button and this:
Finding update package
Opening Update Package
Veryfing update package
E: Failed to read footer from /cache/ (is a directory)
E:signature verification failed
Installation Aborted
Click to expand...
Click to collapse
No, in that recovery i can only go up and down, any other button works. If i push home, the recovery dissapear, but then if i push it again it appears again. That menu offers the option to wipe data but i can´t do it.
Are you able to wipe everything?
data, cache, dalvik cache and battery stats.
No, that menu doesn´t work. I only can wipe cache and factory reset.
It appears the rom is well-flashed, but when it reaches the android logo it goes in a loop.
then wipe data and cache.
It resurrected! :O
I flashed a stock Movistar rom from America and it booted normally! Thank god
But i don´t understand why booted now and not later. Also, i couldn´t do anything it the recovery. Anyway, i can root it again because it´s a froyo.
Thank you.
Greetings!
yeah, it's strange that it didn't boot earlier with other ROMs.
anyway, congratz
GL
Yeah, it´s weird. I´m returning it back to Cyanogenmod 7+francokernel like it was before the brick. I know what made it: install ClockWorkMod Recovery, so i´ll stay with the old recovery i had.
Greetings!
AgumonDX said:
I flashed like 3 different roms and waited in one of them 7 hours to boot. When it access the recovery it appears a warning button and this:
Finding update package
Opening Update Package
Veryfing update package
E: Failed to read footer from /cache/ (is a directory)
E:signature verification failed
Installation Aborted
No, in that recovery i can only go up and down, any other button works. If i push home, the recovery dissapear, but then if i push it again it appears again. That menu offers the option to wipe data but i can´t do it.
Click to expand...
Click to collapse
well dude
if you would have just toggled the signature verification off
you would have no problem installing the ROM
viv_jen said:
well dude
if you would have just toggled the signature verification off
you would have no problem installing the ROM
Click to expand...
Click to collapse
Well I dont know how we turn off signature verification. I faced an idential issue using v10E firmware from this link. KDZ update was not able to find the phone in emergency mode. Second time I tried, it did flash the f/w fine.
I got the triangle with an exclamation mark and a droid below. Recovery menu (pressing HOME button) was useless as I could not select any option with any of the hard keys.
This is how I solved it - rebooted once to recovery mode(volumen DOWN + Home), and face a progress bar for a few seconds - rebooted automatically to the LG sign. This time phone booted fine!
Related
Ok, So I've recently updated to stock gingerbread 2.3.3 with baseband .35. I rooted my phone with the SuperOneClick method. Root was successful (Finally).
I then wanted to install a custom ROM, so I installed ClockworkMod's ROM manager, flashed the clockwork recovery image and everything. I decided to make a backup image in case I didn't like the new ROM. I then selected the "Backup Current ROM" option, and left my phone to it's own devices. When I got back about 5 minutes later, I find that I have a hard reset on my hands :| To add to that, I don't even have a backup image!
I tried doing that a couple times more, once, I even held the POWER+VOL.DOWN+HOME combo and all. The same thing happened each time. The recovery backdrop and a sliding progress appeared, after about 4 seconds, the progress bar stopped moving, it shifted back to the LG boot logo. If I kept the combo pressed, it would go on and on for about 5 times, if I released it, it would just continue on to the boot and I would get another hard reset every time. I tried "Reboot into Recovery". Same thing. Once, I selected "Install ROM from SD card", with the backup option selected. Somehow or the other, due to the combo or something, I came to a screen that had four options.
1) Reboot
2) Install from SD card:update.zip
3) Wipe data
4) Wipe dalvik cache and cache
I was able to scroll up and down with the volume rocker, but the only other button that worked was the Home button, which toggled between the screen I mentioned above and a screen where all of the text was removed and there was just the recovery background. I finally popped out the battery and booted, and got yet ANOTHER hard reset.
HELP!
It seems Clockworkmod recovery was not flashed correctly. What you see is the stock android recovery. The recovery key mapping is:
volume rocker-up/down
menu (left most button)- select current option
back - go back
the behaviour you see when pressing the home button is normal.
After using Rom manager to install CWM recovery, it is not recommended to do further operations through rom manager, best uninstall it. Instead, boot into recovery using the three button combo and do operations from there.
I would suggest try again to re-flash CWM recovery.
mihir287 said:
After using Rom manager to install CWM recovery, it is not recommended to do further operations through rom manager, best uninstall it. Instead, boot into recovery using the three button combo and do operations from there.
I would suggest try again to re-flash CWM recovery.
Click to expand...
Click to collapse
Thanks, but do you have any idea WHY using ROM manager is a bad idea? Just curious.
snitch_95 said:
Thanks, but do you have any idea WHY using ROM manager is a bad idea? Just curious.
Click to expand...
Click to collapse
Well, one reason I've encountered is that while flashing cwm recovery, if the download fails for some reason, Rom mananger has flashed the incorrectly downloaded file without verification resulting in a fastboot semi-brick for many users.
Another reason is related to the way it operates the recovery. I'm not very sure about this point, but I've seen many people having problems with backups and flashing.
Thanks, you were brilliant. I flashed another recovery from ClockworkMod, this time with a WiFi connection, and everything worked great.
I was updating firmware of my LGP500 optimus one using kdz updater for 2.2 to 2.3.3...
battery level might be 40 to 50%.....
at the end i got an error and phone turn off.. now i tried to start it again but its not turning on....
any key combination is not working.. like home+down vol+ power_button or..
return+ up_vol+power_button,,,, what to do to get my phone turn on ??
even when i plugged in it to charger or USB cable .. it shows nothing on screen...
hardik.gcet said:
I was updating firmware of my LGP500 optimus one using kdz updater for 2.2 to 2.3.3...
battery level might be 40 to 50%.....
at the end i got an error and phone turn off.. now i tried to start it again but its not turning on....
any key combination is not working.. like home+down vol+ power_button or..
return+ up_vol+power_button,,,, what to do to get my phone turn on ??
even when i plugged in it to charger or USB cable .. it shows nothing on screen...
Click to expand...
Click to collapse
after the kdz method i think that u can do nothing, if u r under warranty then give your phone back and just say after trying to update through original lg software ur phone would not start at all. or try reading and asking in this thread
I am on 2.2.1 and I installed CWM recovery via ROM manager through wifi. Everything is perfect but whenever I go into recovery it just boots and resets my phone. Its my friends phone and I need help. I have tried other recoveries too but it is the same problem. Please help.
djdhruv said:
I am on 2.2.1 and I installed CWM recovery via ROM manager through wifi. Everything is perfect but whenever I go into recovery it just boots and resets my phone. Its my friends phone and I need help. I have tried other recoveries too but it is the same problem. Please help.
Click to expand...
Click to collapse
try to reflash recovery again and select reboot recovery from rom manager itself after flashing recovery
if still it doesnt work then flash recovery by below method
http://forum.xda-developers.com/showthread.php?t=1318750&highlight=recovery+through+lgdmp
Hi, I need some help with my smartphone. This was my first try to change a ROM, I did a lot of things... What I remember is that I downloaded the ROM and I tried to install it with the Stock Recovery (I did the "Wipe data/factory reset" and "Wipe cache" then the "Install update from zip")...I did'nt have the phone unlocked at first... Now the phone doesn't go further than the motorola logo. I've tried a lot of fixes and I can't get it done, I got the bootloader unlocked after, and after that I could install a nice recovery (It was really hard) I really don't know where it got bricked. I've downloaded some sbf files but none of them worked and some "automated fixes" but still did'nt work.
AT&T version
Was running on GingerBread 2.3.6
Thanks in advance
do you get the white text "unlocked" at the top left of the screen while you turn on the phone?
If you have a custom recovery you can flash any rom you download from the dev section.
jorno88 said:
do you get the white text "unlocked" at the top left of the screen while you turn on the phone?
If you have a custom recovery you can flash any rom you download from the dev section.
Click to expand...
Click to collapse
Yes, and i've tried as you say to install a ROM but it fails. I tried to install CM7 (The last version, a nightly) and Atrix-MROM... Oh and is there a difference in flashing and installing a ROM?
No flashing is installing a rom, can you elaborate more on the error you get (if you get one)?
what recovery are you using (twrp, cwm, ...)
jorno88 said:
No flashing is installing a rom, can you elaborate more on the error you get (if you get one)?
what recovery are you using (twrp, cwm, ...)
Click to expand...
Click to collapse
When I turn on my phone I don't get any error it just stucks on the logo screen, sometimes when I try to install a ROM I get that the file doesn't work or something like that but right now I tried again to install Atrix MROM and according to the recovery it installed succesfully, but when I reboot the cellphone to see if it works I get the same thing it won't pass the logo screen. The recovery that I use is one that has some chinese green words and it say "goapk.com" it also says on the top "Atrix 4G Recovery v4.0.0.2 GOAPK.COM" (It's not the stock recovery) and the options are in blue... I tried to instal CWM but I couldn't, I never saw it, it never worked, so I got that one from an automatic script. I'm sorry if didn't helped enough, just ask me anything that you want to know. I apologize for any typo I'm from Dominican Republic english is not my native language. Ohhh And the last time I tried to install a sbf with RSD Lite (It had like 500 mb) and after all the process fiinished It said "Fail. The pone did not re-enumerated..."
Thanks for replying
ok let's try to install cwm. I hope you have the fastbootdrivers installed
copy moto-fastboot.exe to download folder
then download this file.
then open up a cmd window (type it in start menu and open)
Code:
cd %userprofile%/Downloads/
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-clockwork-touch-5.8.1.8-olympus.img
moto-fastboot reboot
hold down the volume button while it is rebooting
then select recovery by pressing the volume down button untill it is shown on your screen en select it by pressing the volume up button
let's first see if this works
Now I can't flash it... -_- I get the error "The phone is to low to flash" and I can't get it charged, I'm seeing if I can charge it.
JCNouel said:
Now I can't flash it... -_- I get the error "The phone is to low to flash" and I can't get it charged, I'm seeing if I can charge it.
Click to expand...
Click to collapse
try turning the phone off, pull the battery out.
Then connect the charger to your phone (use a wallsocket, not usb from pc) and after a few seconds insert the battery, let it charge for a couple of hours
If that doesn't work i think you need to use someone else's battery or charge yours with another atrix.
It Worked!
jorno88 said:
try turning the phone off, pull the battery out.
Then connect the charger to your phone (use a wallsocket, not usb from pc) and after a few seconds insert the battery, let it charge for a couple of hours
If that doesn't work i think you need to use someone else's battery or charge yours with another atrix.
Click to expand...
Click to collapse
Hi, sorry for the time, I got it charged and I did as you said, now I have the CWM Recovery v5.8.1.8
What should I do now?
Thanks a lot!
JCNouel said:
Hi, sorry for the time, I got it charged and I did as you said, now I have the CWM Recovery v5.8.1.8
What should I do now?
Click to expand...
Click to collapse
Hey i got it... I installed the Rom successfully, thanks a lot I really appreciate it!
glad to be of help
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 (starting BL unlocked w most recent Sony stock .291 firmware) rooted and flashed with TWRP and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using rocker00's guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) and Gapps (A-GAPPS+6.0.1_14.05.2016_v5.2.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen (cm-12.1-20161016-NIGHTLY-sirius.zip). Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I rooted fine (same SuperSU as before) and started installing apps via Google restore. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP using the tool from rocker00's post with the phone in fastboot mode. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect, although I would get the android robot with the blue progress once before it reboot into the bootloop.
2) With the phone in flashmode I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect (i think the phone needs to be booted for this tool to work).
3) I've tried all the relevant commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
epeace said:
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 rooted and flashed with TWRP (twrp-3.0.2-0-sirius.img) and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using this guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen. Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I started installing apps, rooted fine. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect.
2) I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect.
3) I've tried all the commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
Click to expand...
Click to collapse
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
iXaidyiu said:
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
Click to expand...
Click to collapse
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
epeace said:
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
Click to expand...
Click to collapse
Well if so, let's just start from scratch, because you seems to have screwed quite badly and complicated.
Firstly, flash .291 firmware with the three boxes under "Wipes:" ALL CHECKED, check also "AUTO_BOOT" on the right column. These steps will return your device into factory state.
After the flashing process has finished, if your device turned on automatically, turn it off, then unplug the device and replug it when pressing vol+ key, this will enter fastboot mode, you can have two ways to follow now:
(1) Select "Flash", "Fastboot Mode", "Select kernel to flash", navigate to the directory that contain the kernel downloaded (I personally recommand Elite Kernel and extracted), then flash the .IMG file;
(2) Open a cmd using shift+R mouse on the blank space in the directory that stores your twrp.IMG (you can download it here), and type in:
Code:
fastboot flash recovery <filename>.img
and press Enter.
In both method, after you have pressed Enter and see there are two "Okay" printed in the CLI, unplug your device and boot it.
During boot, you will see yellow or green LED light blinked, press vol+ button once and hurray, you will be booted into TWRP recovery!
Now you can load your zip onto your SD card and start flashing! Happy flashing!
P's1 When you tried to boot up your device with the vol- button pressed together, you will be booted into SAFE_MODE, in this mode all 3rd party applications will be disabled.
P's2 I personally DO NOT recommend you to flash zip or erase anything using fastboot commands, use TWRP instead
Thank you iXaidyiu. Option 1, although it fails to boot normally, was successful in getting me back into recovery! Now that I'm in recovery, I first tried to restore my back up. But this failed with errors:
Code:
Failed to mount '/system' (Invalid Argument)
Failed to mount '/data' (Invalid Argument)
Failed to mount '/cache' (Invalid Argument)
So then I tried to flash PA again (since that was the only rom I had on my sd card right now) which also failed with the same errors plus new ones:
Code:
Failed to mount '/data' (Invalid Argument)
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Download/pa_sirius-6.0.3-20160809-signed.zip'
It also said that "This package is for "sirius" devices; this is a "".". Apparently my Z2 is no longer identifying as 'sirius'. I checked the file system, and I can see that the /data, /cache, and /system folders are physically there. Why are they not mounting? Permissions? :s What to do from here?
UPDATE: This "Failed to mount /data error" seemed to be the root of all the problems till now. Others on the net with this error also see boot hanging at the mfr logo. However, I was able to solve it by formatting /data. I still couldn't flash PA due to the 'This package is for "sirius" devices' error, but I was able to restore my TWRP backup, which then solved the "sirius" ID issue, after which I could flash PA just fine! Thanks iXaidyiu for your help in getting me back into recovery! That was clutch to me finding the solution!
@epeace
If you ever face the device id issue again, unzip the ROM, navigate down /META-INF/com/Google/Android/updater-script and delete the following line:
Code:
getprop("ro.product.device") == "sirius" ||
abort("E3004: This package is for \"sirius\" devices; this is a \"" +
getprop("ro.product.device") + "\".");
(probably the first of the code till a semi-colon)
This disable the Device ID check when you flash the ROM.
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Ok great tip, I'll make that edit for next time. Re: the charging, I think it's charging, but it's definitely charging very slow. But a number of things could be contributing to that, I'm constantly on it right now (setting it up), i'm charging off of my computer (usually slow to begin with), and this phone is a few years old so the battery is not what it used to be. I'll keep an eye on it the next days, and report back here and let you know what I've observed. Thanks again for your help!
iXaidyiu said:
@epeace
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Click to expand...
Click to collapse
Hey @iXaidyiu,
I no longer have PA installed, but in the couple days with it I didn't notice any difference in battery performance compared to other ROMs. I think that shouldn't be a deterrent. At the moment I'm trying out GarvityBox on rcstar6696's vanilla MM/Nougat. So far it feels right, although rooting was a little tricky for some reason. We'll see how that goes!
Hi guys, I really need your help.
I'm new at this rooting stuffs and I tried to root my Oppo Neo 5.
I tried so many softwares like OneClickRoot, FramaRoot, and Kingroot but none seemed to work.
So I resorted to an app called oppo tools
It worked at first but I got really annoyed when my status bar suddenly colored to red when my phone discharges to 15% so I unrooted my phone and rooted back again. I really thought that was going to fix my problem but that's where the bootloop issue started.
I tried to flash some custom recovery zip but it failed since I only have a stock recovery.
But the thing is, I found a guide that says to rename the clockworkrecovery img to PG86IMG.zip.
So I did tried that and as soon as I flashed the zip from my stock recovery, my phone hanged.
I long-pressed the power button to restart and boot into recovery mode but nothing seems to happen.
I'll try to explain a bit more on how it looks when I boot my device.
When it boots normally (I mean not pressing the volume to enter recovery mode) it will only show the logo but when I try to go into recovery mode it will show the logo with a little text on the lower left portion "Recovery Mode"
Before I flashed the PG86IMG.zip, recovery mode was still working and the charging screen when off is working too.
but after I flashed the zip, every time I try to recovery mode the logo shows up with the little text but RECOVERY MODE isn't working. When I charge my phone it automatically boots up and shows the logo and text like it's trying to go recovery mode (I'm just trying to charge? It's going to recovery mode)
I tried using "adb devices" on cmd but it's not detecting any devices.
I'm really out of ideas guys, I know not all people use this model but what would be your suggestion?
A suggestion on how to fix this would really be appreciated :good:
I'm sorry I'm really new at this, please correct me if I did something wrong starting this thread. :angel:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Salman Al-Badgail said:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Click to expand...
Click to collapse
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
DeepBricked said:
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
Click to expand...
Click to collapse
You made a soft brick, not to worry flash it with correct stock firmware, if the phone is in warranty than ask them to do flash, this will take approx 10-30min. If it isn't in warranty than you should try it own or else pay some amount and the rest they will do.
Salman.
how about bootloop, cant enter recovery, reboot continiously when turn on even going to recovery, only fastboot isnt rebooting automaticaly but pc days drivers not succesfuly installed, and when off it qont detect by pc because of rebooting auto,
where can i find a rom for my oppo neo 5
pls help me pls
Many of us are on custom OS and want to return back to stock Indian OS which was not possible till now. Below posted is a tried and tested method by me as well as my friend @ankan1993.
I assume you are unlocked BL and your device is atleast not bricked.
Please follow this guide step by step to get a stock working device. This is for Honor V10 Indian Version C675 and I'm not responsible for your loss if you make this worst by trying this on other variants/models or if you choose not to follow this guide properly.
I assume you are on Berkley TWRP with the latest version, unmodified one.
Downloads : (Keep both in your fastboot folder in PC)
Stock Recovery : https://drive.google.com/file/d/1WEUHRrba1dV3109e7h7b3Hp_aJhy0vM8/view?usp=sharing (stockrec.img)
Stock System Image : https://drive.google.com/file/d/1IABtk7HJ9ml6kOpytYHrnT6z3C1_9IfW/view
1. Enter TWRP and go to wipe -> Advanced -> Select system and data, and wipe them.
2. In TWRP, go back and Click Reboot button on main screen and reboot to Bootloader.
3. Connect you device and open cmd_here (open as administrator) from fastboot folder. ( I assume fastboot is installed and working in your system. You can check by the command "fastboot devices" . Device should show there. )
4. Type "fastboot flash recovery_ramdisk stockrec.img" (It should complete without error)
5. Once completes, Type "fastboot flash system system.img" (This may show error like "Invalid sparse file format". Ignore that and keep waiting for 10-12 minutes until the system gets flashed completely.)
6. Once it gets completed, disconnect your device and then press Vol up + power, until it screen shows stock recovery.
7. In stock recovery, use factory reset and cache wipe option one by one and then reboot.
Hit thanks if you think it helped :fingers-crossed:
Finally, after days, after being tormented by the bugs of custom Roms we have something to cheer about. Kudos Oreopie! Cheers to the long hours.
Kudo's bro.. appreciate your efforts :good:
Will this method also lock the Bootloader to stock?
vardaraju said:
Will this method also lock the Bootloader to stock?
Click to expand...
Click to collapse
No, It won't.
Im unable to access bootloader/recovery mode after unlocking bootloader with volume down+power button, used twrp option to reboot to bootloader, but now i flashed stock recovery and this system image, device bootlooped and im unable to access bootloader, i hold the keys but instantly that warning screen comes up, please help..started using android since 2010 with HTC desire HD and never in my life i stepped in service center because those devices were brick proof, looks like honor made me step into service center
didnt work for me, followed exact steps as mentioned above but stock recovery keeps giving error while factory resetting the device, device ends up in bootloop,, this device is crazy, i need to connect my device to pc and then press voldown+ power to access bootloader else it just jumps to warning screen
aditya desai said:
didnt work for me, followed exact steps as mentioned above but stock recovery keeps giving error while factory resetting the device, device ends up in bootloop,, this device is crazy, i need to connect my device to pc and then press voldown+ power to access bootloader else it just jumps to warning screen
Click to expand...
Click to collapse
Obviously warning screen will come up, but at the same moment you have to just leave power button and keep on pressing vol down button, until you get into bootloader mode. It takes time bro and let me tell you one thing, no matter which mode you boot, no matter what ROM it is, once the bootloader is unlocked it implies that the unlocked warning screen will show and then it will be allowed to get into whatever mode you wish.
Try it as I told, be patient and follow the same guide exactly if you do not wish to visit service centre. There is nothing wrong happening with you other than an improper method being followed in haste
aditya desai said:
Im unable to access bootloader/recovery mode after unlocking bootloader with volume down+power button, used twrp option to reboot to bootloader, but now i flashed stock recovery and this system image, device bootlooped and im unable to access bootloader, i hold the keys but instantly that warning screen comes up, please help..started using android since 2010 with HTC desire HD and never in my life i stepped in service center because those devices were brick proof, looks like honor made me step into service center
Click to expand...
Click to collapse
In cases of a bootloop, follow this- https://forum.xda-developers.com/ho...ustom-rom-to-stock-rom-honor-view-10-t3802872
will the system image work on honor 7x??
Can you share the screenshot of the about phone screen please
Anyone got it working? the stock recovery keeps showing error when factory resetting the device, error shows some where at 12%, it just shows exclamation mark, ROM doesn't boots up
Not working!
Rj_Param said:
Not working!
Click to expand...
Click to collapse
What is the issue and what you want to do.
shashank1320 said:
What is the issue and what you want to do.
Click to expand...
Click to collapse
I am on lineage and want to go back to the stock ROM. I also have backup of my system but i have tried many times after flashing the system image it is going in boot loop so i have followed all methods and it's not working..
Every time i have tried after flashing system whenever i go to recover to do factory reset it failed. Even i tried to lock the bootloader but nothing seems to be working.
Rj_Param said:
I am on lineage and want to go back to the stock ROM. I also have backup of my system but i have tried many times after flashing the system image it is going in boot loop so i have followed all methods and it's not working..
Every time i have tried after flashing system whenever i go to recover to do factory reset it failed. Even i tried to lock the bootloader but nothing seems to be working.
Click to expand...
Click to collapse
Because on custom you are on 8.1 and twrp doesn't support yet.
May be you can try dload the b161 version which is out on firmware finder now.
shashank1320 said:
Because on custom you are on 8.1 and twrp doesn't support yet.
May be you can try dload the b161 version which is out on firmware finder now.
Click to expand...
Click to collapse
I'll give it a try today...thanks
Invalid
as you mentioned, i m getting this error "invalid sprase file format". I waited more than 30 mins, still i couldn't see any message like compeleted or success. Still showing only that error "invalid spase file format". Help me with this.
Tamilarasan_Indian said:
as you mentioned, i m getting this error "invalid sprase file format". I waited more than 30 mins, still i couldn't see any message like compeleted or success. Still showing only that error "invalid spase file format". Help me with this.
Click to expand...
Click to collapse
Invalid sparse error happens when trying to flash .IMG files in Windows system.
It can be easily solved by using Linux system.
thanks for the reply
miststudent2011 said:
Invalid sparse error happens when trying to flash .IMG files in Windows system.
It can be easily solved by using Linux system.
Click to expand...
Click to collapse
I dont have Linux , and tried to flash other SYSTEM.img file for honor v10 from other threads. It completed flashing but still am not able to login into phone successfully. Still stuck at bootloop. Help me