Related
I got this phone from ebay, and it worked a few days before I flashed it so I know it's not hardware or a bad flash on their part because it was stock when I got it. Anyway, I flashed the generic fw through flashtool and it was working fine for awhile until one day it froze and nothing was responsive. The battery died, and I recharged it and threw it into flash mode to repair the firmware through SEUS, and it got it working for awhile until it happened again. So instead I went ahead and used flashtool to put AT&T's fw back on the phone. After I did that, the phone now only vibrates when I turn it on and then does nothing. If it does do something, it just continuously vibrates until I pull the battery. I tried using SEUS and Flashtool to flash another fw because I can get it to flash mode, but it says failed everytime no matter what firmware I use. And SEUS fails right up front when trying to repair. Any ideas?
Pull out the battery....plug the usb cable...run latest flash tool...click on flash button..when it is searching for the fone then put back the battery with pressing the return key.
Recheck the latest driver for 2.3.3
Did it work?
Dude are you aware of rooting procedures?
First you should flash the stock rom back in, then you flash some pre-rooted GB rom. Threads on X10 Android Development are full of options.
jeancca said:
Dude are you aware of rooting procedures?
First you should flash the stock rom back in, then you flash some pre-rooted GB rom. Threads on X10 Android Development are full of options.
Click to expand...
Click to collapse
Dude did you even read my post?
I've been a member here for 3 years and have been flashing Android to phones ever since then. I have looked at the troubleshoots but they were all giving a failed flash. Not to mention this has nothing to do with root or GB, I was talking stock firmware, this brick happened before SE pushed out the GB update.
To subhanker.ds, thank you for the input, I'll give it a shot.
EDIT: Just got the same error
Uploaded with ImageShack.us
As per your screen shot, debugging mode is of....but it is not possible to on now as ur phone is dead.
I think somehow jeancca is correct...use rooting process..(no need to flash any rom)..it will automatically turn on debugging mod & then you flash ur rom...
Hope ur prob will be solved dear...
I've tried several rooting methods that and they all state I should turn on Unknown Sources and Debugging. But I cannot do this, is there a way that will force it into usb debugging as you said?
Actually at the time of flashing debugging mode automatically turn on...
Anyway i'm not getting any clue...although you can try to flash only system.sin file.then see what will happen....best of luck...
I've tried everything I can think of and I still can't get it to work. A new symptom has came up though, when I try and connect it to my PC, it will go into flash mode but after awile the LED goes off but is still recognized by the PC as being in flash mode. Same goes for when I plug it into the charging cable.
Bump.
Sorry for doing it, but is there anyone out there that can help me?! I had to think I have a $200 paperweight.
Hi..... I mentioned this on another post but thought I might see if this might help you. Although I didn't mention the use of other Flashtools in the other thread, I did end up trying Flashtool 2.8.0 and 2.9.1 and the latest edition. In the end I ended up going with the 2.8.0 to start fresh and since that was the one that was used for An Android 2.1, I flashed back to 2.1. With a few instances like those you mention I tried this and worked out.
What I did was open my devices and printers (control panel) and noticed the SEMC USB or IDE blah blah......The device pops up when connecting my phone. I would flash my phone and the go to the "Turn on phone and check debug" and ..... Same as you green light (Flash) would go on and then nothing.
What I did was unplug my phone and Uninstall the device used (SEMC USB or IDE, it named itself differently on an occasion or two) and then started my Flashtool then tried again. Goto Flashtool and prepare your Flash and wait for it to load up (took some time once or twice but....) connect your phone and try again.
I have been messing around with a bunch of apps and FW's and ROMS and lately Unlocking the BootLoader.
Some you can just goto Task Manager and Stop the ADB.exe processes but this uninstall worked excellent for me when needed.
Hope this solves your issue. Good Luck. Oh you may not need the other Flashtools but I have them on file just in case because 2.9.1 gave me a problem before when doing something. You might be able to do with whatever Flashtool you are using but just thought I would share my experience.
I have the same problem . i I flashed it with X10i rom but work for while and after 1 or 2 hours hanged and when i remove the battery it's hang in sony ericsson .
After that I flashed it with SEUS and upgrade to official rom 2.3.3
and has the same problem .DO THINK IT IS A HARDWARE PROBLEM
Tingles said:
Hi..... I mentioned this on another post but thought I might see if this might help you. Although I didn't mention the use of other Flashtools in the other thread, I did end up trying Flashtool 2.8.0 and 2.9.1 and the latest edition. In the end I ended up going with the 2.8.0 to start fresh and since that was the one that was used for An Android 2.1, I flashed back to 2.1. With a few instances like those you mention I tried this and worked out.
What I did was open my devices and printers (control panel) and noticed the SEMC USB or IDE blah blah......The device pops up when connecting my phone. I would flash my phone and the go to the "Turn on phone and check debug" and ..... Same as you green light (Flash) would go on and then nothing.
What I did was unplug my phone and Uninstall the device used (SEMC USB or IDE, it named itself differently on an occasion or two) and then started my Flashtool then tried again. Goto Flashtool and prepare your Flash and wait for it to load up (took some time once or twice but....) connect your phone and try again.
I have been messing around with a bunch of apps and FW's and ROMS and lately Unlocking the BootLoader.
Some you can just goto Task Manager and Stop the ADB.exe processes but this uninstall worked excellent for me when needed.
Hope this solves your issue. Good Luck. Oh you may not need the other Flashtools but I have them on file just in case because 2.9.1 gave me a problem before when doing something. You might be able to do with whatever Flashtool you are using but just thought I would share my experience.
Click to expand...
Click to collapse
Thanks a lot, I will give this a shot as soon as I get home. I'll keep my fingers crossed that this may help me and the others having this sort of issue.
Mobark, I don't think it's a hardware issue. For awhile I was thinking it was a dead screen, but from the people I have heard that did indeed have dead screens, they have lines in the center of the screen while my screen just doesn't turn on.
Hi everyone i am having the same problem my phone only vibrates for sec and the green led just flash for sec than nothing but my phone goes into flash mode but the flash aborts i have also made a thread in which i fully listed my progess and software i used http://forum.xda-developers.com/showthread.php?t=1257581
Nope, didn't seem to work. I think my problem is the phone doesn't want to stay in Flash mode for some reason.
I fix this error, i download and flash this, next i updated in SEUS, my phone is Xperia Play
Sorry for my bad english.
Ok, so I upgraded to 3.0.0 and tried flashing the generic fw again to no avail. And as far as above, the firmware isn't for the x10, it's for the Play, Arc, and Neo.
This is what i did
Not sure if this will work for you but this is how I fixed my phone.
When I first changed the rom on my phone i was on baseband 435. I never changed the baseband with the custom rom install.
My friend factory erased the phone and then it would take 45 - 50 mins to finish booting (would turn on i would see se logo and 50 mins later I'd get to a stock "slide to unlock screen" upon doing so i would get a black bg with the custom batt meter and clock at the top. it also dected the sd wasnt plugged in.
While the phone was on, Sony Ericsson pc Companion would say please mount sd card, and that i couldnt do.
While trying to use flashtool 2.9.1 it would say please put the phone in debuggign mode.
At this point, your ss shows you making it further than i did. because mine wouldnt make it past the date/time (yours starts flashing an fails some way through).
I tried 4 roms and none of them worked.
Then i found http://www.multiupload.com/9H20YEXEHR and After updating to flash tool 3.0.0, and using the stock rom that i posted the link to, It worked. but i had to try a few times. At http://forum.xda-developers.com/showthread.php?t=920746 There are 3 different stock roms for x10a (I used the first one in the x10a list)
I used the one that matched my baseband. Try an match yours if you know it.
When i connected usb, the phone would not turn on. The phone would only turn on with batt in. So i connected usb, held back and put batt in.
Doing this worked, I held the back button until the flash completed.
Also as a note, I did not change the bootloader, that could be why it would boot after 50 mins or so.
I hope this helps.
-Mike
Hi guys, I've had a look around for this, but I can only find the solution for bootloaders that are unlocked. I suspect my Ray WASN'T unlocked. I accepted the OTA 2.3.4 update, thinking it would be fine. But the phone now shows the exclamation mark. I can get into both the recovery and fastboot modes (green/blue LED).
None of the recovery solutions are working for me. Is there a way for me to fix this, or will the phone have to go to a Sony Ericsson shop.
The official PC software from SE won't restore it either.
it is wise to go to sony shop , they will fix it
Not sure if this will solve your problem, but it solved mine:
The problem was with the bootloader. So I tried FlashTool_0.2.9.1_FOTAUnbrick which brings a small firmware information to reset the bootloader.
The problem I was having was to be able to correctly connect the phone to the flash tool. My phone's USB connection was constantly going up and down. So I decided to uninstall all the tools and drivers and install them from scratch.
In short, here's what I did.
Installed Update_Service_Setup-2.11.10.7.exe from sony ericcsson in order to get the USB drivers to work.
Followed the instructions of the Update_Service and flashed the latest update available for my phone (2.3.4). This didn't solve the startup problem, just installed the latest update.
I ran the Update_Service again and restarted the process has if I was going to flash again, but after the Update_Service detected the phone I canceled the installation. (I did this just to make sure the phone was connected in FlashBoot)
Then I installed FlashTool_0.2.9.1_FOTAUnbrick.exe, opened the folder of the application and ran X10FlashTool.exe
Hit Flash button and the program opens a Firmware Selection window with a preloaded firmware with two reseting contents (loader.sin, preset.ta). Hit OK button and waited until the program indicated the flash process was finished. The process of flashing takes a few minutes and we need to be patient. It might even seem like it's doing nothing but we just have to wait.
After finishing the flash process the program invited me to disconnect the phone and turn it on. I did so and the phone took probably a minute or so to startup. At first I thought it didn't solve the problem, because it was taking so long to start, but it did solve! So I waited patiently and the Sony Ericsson logo showed up giving me a new hope. After that I had to wait another 4 or 5 minutes for the phone to finish applying the new firmware mentioned in point 2. (There's no visual information of the conclusion process so you might wonder the phone might have hung.) Just waited and everything got back to normal with the benefits of the new firmware 2.3.4 (instead of the previous 2.3.3).
I hope it helps someone having the same issue.
xperia ray said:
it is wise to go to sony shop , they will fix it
Click to expand...
Click to collapse
Might not fall under warranty.
http://forum.xda-developers.com/showthread.php?t=1568792, check my tutorial, there is a guide to unbricking.
LG C800
Device will not enter fastboot.
Can't get into recovery mode.
Each time it boots it hard resets. There is an unofficial CWM Recovery Rom on this forum from chui101 which is for this exact phone, but I have as of yet not had any luck in getting the phone to take it.
So far i've tried Flash_image recovery.img (renamed chui's CWM recovery file to recovery.img)
Doesn't seem to matter what I do the phone starts(LG on screen), resets (the LG goes away for a sec then comes back), does a hard reset (a white box with an arrow pointing out of it an to a little android), again resets the phone one last time for a "normal" boot.
I've tried a few different things to try and flash anything overtop of the stock recovery but nothing works. It seems like very early in the bootstrap is a command to do a hard reset and anything that gets put in AFTER that command is ignored. (And the phone hard resets and anything else it was supposed to do is gone.)
Device is rooted with SuperSU.
Phone is fully functional except that it hard resets every boot, and if its plugged in when off it doesn't go to a charging screen, it starts the phone 100% up.
Adb devices CAN see the phone.
I CAN get into Download (sometimes called Emergency) mode.
"reboot recovery" doesn't do anything but reboot the phone as described above.
I can't afford a new phone guys, so I'm over a barrel at this point.
i'll pay whoever provides meaningful help in getting this thing fixed.
You should start fresh. So, flash the stock rom FTF of your phone, then the phone should boot up normally. Then you could either root it and install a CUSTOM recovery, or flash a pre-rooted custom kernel that already contains a recovery. From there, just flash the custom rom you want
Just press thanks if I helped, no need for money
stock rom FTF?
From the factory?
I'd love to do that. But am bewildered as to how when every guide I've found says use fastboot -- which doesn't work on my device. And every guide without fastboot thus far has not worked. I've been reading 10 hrs a day for the last 3 days looking for a solution to this.
If there was a way to completely wipe the entire phone and then install stock rom I'd be glad to do it.... I have found no such guide... only those to replace recovery. (not a 100% clearing as if it came right off the line with no software yet installed)
Additional information:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p-bak
Spits out a "No such file or directory" error
I don't know about you, but for Xperia Devices there is a PC software called Flashtool to flash stock roms and custom kernels and stuff from the PC. There should also be a software like that for your device. You just download the stock FTF for your phone (just type in google "download stock FTF for LG C800") and flash it in Flashmode that should be working
One more thing, this issue is not called bricked
press thanks if i helped
There is an LG tool but it says current software is up to date.
Other option is run recovery, which just reboots the phone as is.
No, this software I am talking about is not made by LG or Sony in my case. It should be a general tool for all LG devices. it should root, flash, install busybox, etc......
blakstar said:
No, this software I am talking about is not made by LG or Sony in my case. It should be a general tool for all LG devices. it should root, flash, install busybox, etc......
Click to expand...
Click to collapse
LG MOBILE SUPPORT TOOL ?
Thats the one that so far doesn't work.
the one named:
KDZ_FW_UPD_EN ?
He doesn't appear to support GSM phones. Plus I hit "Read info from phone" button... it gets almost everything -- correctly -- then crashes.
IT wants kdz files... looking for them now... chui has a dl link for the stock recovery but even though its a few mb it looks like only a zipped folder hierarchy with no files.
Slightly mis-read. still not finding any "generic" flashing software
trying octopus now....
crashed....
run as admin..... ah... you need their hardware which is hundreds of dollars...
Flash image gui, phone is not supported.
ok, a couple cyanogen dev's have both told me i'm screwed. Imma try for the rest of today and then just never turn it off again.
ok, paying lg to fix it... anybody guess what that will cost?
Try flashing CyanogenMod on your phone as no stock firmware is avaiable currently for your phone cyanogenmod shall fix the problem and you should boot normally (first flash CWM)
http://forum.xda-developers.com/showthread.php?t=1752704 - flashing cwm recovery (do it!)
Flashing cyanogenmod (requires usb debugging on)
First to put the cyanogenmod rom in the sdcard use adb push - http://forum.xda-developers.com/showthread.php?t=1667929
Page 1 (Pre Requisites - http://droidnoob.com/update-lg-c800-to-android-4-0-4-ics-via-cm9.html
Page 2(The actual flashing part :victory - http://droidnoob.com/update-lg-c800-to-android-4-0-4-ics-via-cm9.html/2
Probably will fix the problem....
hi techmasta,
I'd love to flash cyanogenmod, but the phone never enters fastboot to flash anything. The first link you posted says to use fastboot. I can't do that. The phone doesn't goto fastboot, it runs its recovery first.
EDIT: if there is a way to force it while the phone is in download mode that could probably work.
secondly, I've spend more than 40 hours on this issue, mostly reading forums but still a great deal on google.
I'm pretty unhappy with google as neither of those droidnoob forums ever come up. And believe me, there isn't much out there referring to the lg c800 so they should have!
As the topic reads, I've been trying most of the day to unlock the bootloader, I went through the process of obtaining my unlock code and my phone status when typing out a code suggested that it allows unlocking of the bootloader - I'm thinking okay cool, hopefully I'll have Cyanogenmod 12.1 on this thing in no time, right? WRONG! The device needs me to download and install fastboot drivers, which I thought should be an easy process but no matter what I do when I look at my phone through the device manager all I see is 'S1Boot Fastboot' - I even attempted using Flashtool (not Emma) and it too says install failed when trying to download the files needed. I just really need some help getting through this part of the problem, I've downloaded the SDK downloaded the USB drivers, updated them with the file from Sony but the end result remains the same. If it makes any difference (which I'm sure it will) I'm on Windows 10.
Thanks for any and all replies .. Edit // I forgot to mention the model is C833 and I recieved the latest OTA update from Sony for Lollipop 5.1.1
Installing the SDK is quite the overkill.
- Install ADB and Fastboot by downloading and running this tiny installer. It'll do the job for you.
- Install Flashtool and be sure that it recognizes your device. The device should be powered on when you open Flashtool the first time.
- Click the "BLU" button and copy/paste the unlock code you received from Sony.
You're done
Be sure to backup important stuff on your phone, in case something goes wrong. Move photos etc. to your SD card or something.
Klaos3000 said:
Installing the SDK is quite the overkill.
- Install ADB and Fastboot by downloading and running this tiny installer. It'll do the job for you.
- Install Flashtool and be sure that it recognizes your device. The device should be powered on when you open Flashtool the first time.
- Click the "BLU" button and copy/paste the unlock code you received from Sony.
You're done
Be sure to backup important stuff on your phone, in case something goes wrong. Move photos etc. to your SD card or something.
Click to expand...
Click to collapse
I appreciate the reply, and I managed to get the bootloader unlocked (I think) as both ADB and Fastboot are acknowledging my phone now. Problem I have now is while in Cyanogen Recovery, I hit the first option and may have soft bricked this phone - the cyanogen wiki stated I could make a backup by booting back into Android which is what I tried to do. I'm in the process now of repairing it with the PC companion hopefully and then I'll give it another go, this isn't my main phone though so basically I'm just tinkering/trying to learn the basics of installing custom ROMs. Thanks again for the reply, and if you have any other suggestions for me be sure to leave em here. BTW, I never installed the full Android Studio, just the zip file for the ADB and Fastboot files, I attempted that at first but found out you didn't really need em in the first place.
The CM Recovery is... pretty crappy, so don't use it if you don't have to. If you soft brick it (i.e end up in a bootloop or something), then just flash or hotboot a kernel with recovery, and you're good to go again, so you don't have to re-flash a ROM.
You can either use fastboot to flash a kernel (if you know how to use a terminal), or you can use Flashtool, QuickIMG etc, so:
Soft brick?
- Download a custom kernel with recovery. Doesn't matter which one if you're planning to flash a ROM straight away. You're planning to flash CM12.1, so you can use a random Ultra kernel like this one.
- Let's say we'll use Flashtool to flash it (since you already have it installed). Open it, hit the lightning bolt, click "fastboot", and then "kernel". Browse and choose the kernel you downloaded. Now disconnect from the computer and remember to press VOL up to enter recovery when it vibrates or the LED lights up.
- You're now in recovery again and you can go ahead and flash CM12.1. Remember to WIPE before or after you've flashed CM12.1. You'll end up with a bootloop if you don't do it. If you do, flash that kernel again and you're back on track.
Klaos3000 said:
The CM Recovery is... pretty crappy, so don't use it if you don't have to. If you soft brick it (i.e end up in a bootloop or something), then just flash or hotboot a kernel with recovery, and you're good to go again, so you don't have to re-flash a ROM.
You can either use fastboot to flash a kernel (if you know how to use a terminal), or you can use Flashtool, QuickIMG etc, so:
Soft brick?
- Download a custom kernel with recovery. Doesn't matter which one if you're planning to flash a ROM straight away. You're planning to flash CM12.1, so you can use a random Ultra kernel like this one.
- Let's say we'll use Flashtool to flash it (since you already have it installed). Open it, hit the lightning bolt, click "fastboot", and then "kernel". Browse and choose the kernel you downloaded. Now disconnect from the computer and remember to press VOL up to enter recovery when it vibrates or the LED lights up.
- You're now in recovery again and you can go ahead and flash CM12.1. Remember to WIPE before or after you've flashed CM12.1. You'll end up with a bootloop if you don't do it. If you do, flash that kernel again and you're back on track.
Click to expand...
Click to collapse
Gonna give all this a shot since the PC companion doesn't seem to be doing anything - I'll post my findings in a few if you're around. Thanks again man, I really appreciate your help.
Edit // Okay, nothing seems to be working now .. Flashtool says that my device has USB Debugging disabled, and whenever I power on the device you see the Sony logo, then a violet led and then the screen stays on and every once in a while it'll show a small battery indicator.
D2084 said:
Gonna give all this a shot since the PC companion doesn't seem to be doing anything - I'll post my findings in a few if you're around. Thanks again man, I really appreciate your help.
Edit // Okay, nothing seems to be working now .. Flashtool says that my device has USB Debugging disabled, and whenever I power on the device you see the Sony logo, then a violet led and then the screen stays on and every once in a while it'll show a small battery indicator.
Click to expand...
Click to collapse
Hmm, plug in the wall charger and charge it for a bit. I highly doubt that it's hardbricked since that's very very hard to achieve on a Sony device. Just kick it into fastboot by holding VOL UP while you plug it into your computer. The blue LED will light up. Then open Flashtool and flash the kernel, or download QuickIMG and flash the kernel (.img) with it. Be sure that it says "connected" before you do anything. Keep also in mind that you have to be in fastboot.
Klaos3000 said:
Hmm, plug in the wall charger and charge it for a bit. I highly doubt that it's hardbricked since that's very very hard to achieve on a Sony device. Just kick it into fastboot by holding VOL UP while you plug it into your computer. The blue LED will light up. Then open Flashtool and flash the kernel, or download QuickIMG and flash the kernel (.img) with it. Be sure that it says "connected" before you do anything. Keep also in mind that you have to be in fastboot.
Click to expand...
Click to collapse
I seem to have a brand new issue now, umm whenever I unplug the device and press VOL UP, I get this distorted screen. It's blue and has what looks to be white wording in the middle, I can't make it out though, this is after I put the kernel you recommended on my device. The kernel is the IMG file, correct?
Just thought I'd give you a bit of an update, I now have Cyanogenmod 12.1 on my Xperia Z Ultra - I flashed the custom recovery that came with the nightly I downloaded and then moved the actual zip to an SD card since like you said Cyanogen Recovery is a bit wonky (I tried sideloading to no avail). I have a couple question though, during the install process I noticed it said something about there 'no such volume' and I was sure I seen two failed prompts too but the ROM is on my phone? Should I look into that at all or is it fine? Most things seem to work .. camera, bluetooth, gonna have to throw my sim in there one of these days and test the cellular radios, but I just wanna say thanks again .. I learned a lot and managed to make something happen even if it's something small like installing a custom rom lol
D2084 said:
Just thought I'd give you a bit of an update, I now have Cyanogenmod 12.1 on my Xperia Z Ultra - I flashed the custom recovery that came with the nightly I downloaded and then moved the actual zip to an SD card since like you said Cyanogen Recovery is a bit wonky (I tried sideloading to no avail). I have a couple question though, during the install process I noticed it said something about there 'no such volume' and I was sure I seen two failed prompts too but the ROM is on my phone? Should I look into that at all or is it fine? Most things seem to work .. camera, bluetooth, gonna have to throw my sim in there one of these days and test the cellular radios, but I just wanna say thanks again .. I learned a lot and managed to make something happen even if it's something small like installing a custom rom lol
Click to expand...
Click to collapse
Just ignore that error. I've seen that myself a couple of times, and I don't know what it means, but it doesn't seem to affect anything.
There are a couple of things to keep in mind. CM12.1 has had some glitchy WiFi in the past, and I believe some people are still experiencing issues, so if you also experience some WiFi issues, it's a CM issue and not a hardware issue. Also, keep in mind that the Ultra GPe (Togari GPe) exists and is also supported by Cyanogen, so be sure to not flash the wrong version since the partitions are different between those two. I believe the recovery system will stop you from flashing it though.
Since Sony devices do not have a default recovery system, we have to bundle it with the kernel, so all custom ROMs around here, including CM, will have a recovery system added, but if you flash a ROM without a recovery system (like a stock ROM that you flash with Flashtool), you'll have to flash a kernel with a recovery yourself.
It's pretty easy to recover from issues and stuff on a Sony device once you know how things work. It's also a good idea to learn how to use flashboot through a terminal since that will potentially save you a lot of time down the road
Klaos3000 said:
Just ignore that error. I've seen that myself a couple of times, and I don't know what it means, but it doesn't seem to affect anything.
There are a couple of things to keep in mind. CM12.1 has had some glitchy WiFi in the past, and I believe some people are still experiencing issues, so if you also experience some WiFi issues, it's a CM issue and not a hardware issue. Also, keep in mind that the Ultra GPe (Togari GPe) exists and is also supported by Cyanogen, so be sure to not flash the wrong version since the partitions are different between those two. I believe the recovery system will stop you from flashing it though.
Since Sony devices do not have a default recovery system, we have to bundle it with the kernel, so all custom ROMs around here, including CM, will have a recovery system added, but if you flash a ROM without a recovery system (like a stock ROM that you flash with Flashtool), you'll have to flash a kernel with a recovery yourself.
It's pretty easy to recover from issues and stuff on a Sony device once you know how things work. It's also a good idea to learn how to use flashboot through a terminal since that will potentially save you a lot of time down the road
Click to expand...
Click to collapse
Everything seems to be working quite well so far, including the wifi but I'll keep what you said in mind. I used the same process to install GApps on it too so now I have the play store and google apps install as well. I have another question though, whenever I plug in a charger to charge the device .. I notice the screen never goes off but stays black and has nothing on display sorta like ambient display, would you know if that's a feature of Cyanogenmod or did I goof somewhere during the install? Thanks in advance for your reply.
D2084 said:
Everything seems to be working quite well so far, including the wifi but I'll keep what you said in mind. I used the same process to install GApps on it too so now I have the play store and google apps install as well. I have another question though, whenever I plug in a charger to charge the device .. I notice the screen never goes off but stays black and has nothing on display sorta like ambient display, would you know if that's a feature of Cyanogenmod or did I goof somewhere during the install? Thanks in advance for your reply.
Click to expand...
Click to collapse
Could it be Daydream? Go to Settings -> Display -> and disable Daydream. Now check again. If it's not Daydream causing it, then it might be a bug. Do a reboot in case it's a small glitch of some kind. If it's still on when charging, then I'm not sure what it could be (other than a bug, that is).
Sorry for the late reply, but I figured out the reboot issue .. I had to turn off the 'wake up' feature when you plug in your device. I have a whole new issue though, I'm not sure if it can be resolved though - I was on the phone with MetroPCS for about an hour trying to figure out why my phone wouldn't connect to their network. I know Cyanogenmod comes with APN's pre-installed but even after the representative tried helping me set up a new APN .. it was a no go, so I switched back to the current phone I'm using - Alcatel Idol 3 4.7 .. anyways, I'd like to hear your input on what the issue could be as I'd really like to go back to using this phone since the software aspect is far more flexible with a custom ROM like Cyanogenmod.
D2084 said:
Sorry for the late reply, but I figured out the reboot issue .. I had to turn off the 'wake up' feature when you plug in your device. I have a whole new issue though, I'm not sure if it can be resolved though - I was on the phone with MetroPCS for about an hour trying to figure out why my phone wouldn't connect to their network. I know Cyanogenmod comes with APN's pre-installed but even after the representative tried helping me set up a new APN .. it was a no go, so I switched back to the current phone I'm using - Alcatel Idol 3 4.7 .. anyways, I'd like to hear your input on what the issue could be as I'd really like to go back to using this phone since the software aspect is far more flexible with a custom ROM like Cyanogenmod.
Click to expand...
Click to collapse
Are you talking about connection to their network altogether, or just data? Do you have reception? Check that data is enabled in Settings -> Data usage.
I can guarantee that this is a software issue, BUT one last question. How old is your SIM card? There have been a few cases when people have been in the same situation as you, got a new SIM, and that fixed the issue. You could do that, or flash another ROM. CM12.1 is beta, so bugs have to be expected, and it's far from a solution if you plan to just flash something and use it for a longer period of time. If you want something very stable and stock, then highly recommend Scrubber's GPe 5.1 port, which is rock solid.
Well my sim card isn't too old, had it for about a year. Once she laced the sim card to the new phone I could make calls and texts but for some reason the Internet wasn't working - she had me go through all the steps to make sure things like data was enabled and airplane mode was off but it still resulted in not being able to establish a connection to the web. So I'm gonna try and flash the GPE rom you're talking about later on tonight once I get home from work and see what happens then - mind leaving me a link to the rom/recovery? Thanks in advance.
D2084 said:
Well my sim card isn't too old, had it for about a year. Once she laced the sim card to the new phone I could make calls and texts but for some reason the Internet wasn't working - she had me go through all the steps to make sure things like data was enabled and airplane mode was off but it still resulted in not being able to establish a connection to the web. So I'm gonna try and flash the GPE rom you're talking about later on tonight once I get home from work and see what happens then - mind leaving me a link to the rom/recovery? Thanks in advance.
Click to expand...
Click to collapse
Sure. Here it is. Remember to download 5.1, and not 5.0. Recovery is included in the ROM, so you don't have to flash anything else.
Quick update, I've flashed the ROM but so far it seems to be stuck in a bootloop, its been stuck on the swaying Google logo for about 10 minutes now. It might be because I sideloaded using a micro SD card because for some odd reason the 'flash the system' option on Flashboot wasn't working for me. So I turned the phone off and will give it another try tomorrow, if you have anymore tips for me I'll be glad to hear em.
D2084 said:
Quick update, I've flashed the ROM but so far it seems to be stuck in a bootloop, its been stuck on the swaying Google logo for about 10 minutes now. It might be because I sideloaded using a micro SD card because for some odd reason the 'flash the system' option on Flashboot wasn't working for me. So I turned the phone off and will give it another try tomorrow, if you have anymore tips for me I'll be glad to hear em.
Click to expand...
Click to collapse
How did you flash it? It must be flashed in recovery on the device and not using Flashtool. Flashtool is strictly for stock Sony ROMs or FTFs. Never use it for anything else besides flashing FTFs and kernels. So:
- Go into recovery
- Remember to wipe! If you don't, you'll get a bootloop
- Install from SD card
- It will probably throw an error at you, but don't touch anything. It's still flashing.
- Reboot
- Wait a couple of minutes.
Klaos3000 said:
How did you flash it? It must be flashed in recovery on the device and not using Flashtool. Flashtool is strictly for stock Sony ROMs or FTFs. Never use it for anything else besides flashing FTFs and kernels. So:
- Go into recovery
- Remember to wipe! If you don't, you'll get a bootloop
- Install from SD card
- It will probably throw an error at you, but don't touch anything. It's still flashing.
- Reboot
- Wait a couple of minutes.
Click to expand...
Click to collapse
Just did everything you just said, will update you tomorrow with results.
Well I did what you said and left the phone to charge overnight - it was in bootloop when I went to sleep and .. bootloop when I woke up (at least it's charged now lol) I'm gonna try again though. I see that CWM has a sideload option, so I'm gonna wipe everything and try to sideload it from the ADB through the command prompt and see what happens. Feel free to leave any other suggestions though.
Got a question though, when I sideload the zip file should I sideload everything within the zip file or just the system image file? Maybe I'm getting bootloop because I'm installing a kernel on top of another kernel?
D2084 said:
Well I did what you said and left the phone to charge overnight - it was in bootloop when I went to sleep and .. bootloop when I woke up (at least it's charged now lol) I'm gonna try again though. I see that CWM has a sideload option, so I'm gonna wipe everything and try to sideload it from the ADB through the command prompt and see what happens. Feel free to leave any other suggestions though.
Got a question though, when I sideload the zip file should I sideload everything within the zip file or just the system image file? Maybe I'm getting bootloop because I'm installing a kernel on top of another kernel?
Click to expand...
Click to collapse
Sideload/flash the .ZIP. Do not extract it. You should simply just boot into recovery, choose "ScrubberPortRom_GPE5.1_LMY47D.zip", flash and wait for a couple of minutes and then reboot. That's it. The first boot should take around 5 minutes.
- Remember to do a full wipe in recovery before you flash
- Flash ScrubberPortRom_GPE5.1_LMY47D.zip
- Reboot
And do share any error messages if you get any while flashing.
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Pyrolectic13 said:
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Click to expand...
Click to collapse
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
kilroystyx said:
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
Click to expand...
Click to collapse
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Pyrolectic13 said:
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Click to expand...
Click to collapse
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
kilroystyx said:
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
Click to expand...
Click to collapse
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
kilroystyx said:
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
Click to expand...
Click to collapse
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
kilroystyx said:
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
Click to expand...
Click to collapse
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Pyrolectic13 said:
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Click to expand...
Click to collapse
You can check the official documentation about that.
Please let us know how you solved this problem.
kumarsid7 said:
Please let us know how you solved this problem.
Click to expand...
Click to collapse
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
Sent from my iPhone using Tapatalk
in first picture youle see many circles golden 2 smallest is testpoint good luck
Pyrolectic13 said:
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
View attachment 4579956
View attachment 4579957
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
in first picture youle see many circles golden 2 smallest is testpoint good luck
well, try to restore your device using dload method. It needs you to copy the UPDATE.APP in dload folder of an external sd card(formated in NTFS format) and then just press both vol up+down along with power button for a few seconds. It will auto launch huawei e-recovery and will try to flash the UPDATE.APP you stored in ext sd card. This should definitely work.
Dload method doesn't need you to unlock your device or bootloader.
Maybe?
I know it’s a long shot but I still have this phone. If anyone maybe knows if there’s been a way to fix this as of yet please let me know. ?
Lol. Still got this damn thing. Been searching around and seen a few people reporting similar errors. Never find out if they ever solve it though.
So. Anyone maybe have any knowledge to share? Anything at all.
I don't know if you still have your device, but I had the exact same issue with a P10 (VTR-L09)
I was able to fix fastboot using https://github.com/mashed-potatoes/PotatoNV
That tool was designed to unlock the bootloader, but I noticed that It actually flashes a slightly modified version of fastboot.
PotatoNV can also unlock P20 lite bootloader, so you should give it a shot.
Good luck!
If it works, you should be able to flash stock recovery image and then restore the system using the dload folder.
you can Repair it with Software Testpoint and Full Bootloader Unlock ,and then flash a Board Software via Software Testpoint, that helps 100%!!!
use this Firmware Download ANE-LX1
use the Software with logins and you have all what you need.
you must start the Software Testpoint so!!
VIDEO : how to start Software Testpoint P20 Lite
than in Software Testpoint you flash the included Board Software with DC-Phoenix and after that use the included dload update via sdcard and eRecovery mode and your Phone is running!!!
I would unlock the bootloader via Software Testpoint with DC-Phoenix, then the FBLock is unlocked and you can flash as you wish!!!! And the great thing about it is that you don't need an UnlockKey either, you can then read this with HCU client software, the only thing that's stupid is that you need a time-based license for the two programs, which you have to buy.
HCU client download
https://hcu-client.com
DC Phoenix download
https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/155916-dc-phoenix
Since I accidentally bought a 3-day license twice and my P20 Lite is now completely rooted on Lineage 19.1, I can give away 2 access data, which are still valid for 2 days.
you can edit your smartphone with it.
username : bl26457
password : kKncnkMj
username : bl26390
password : JDAZqnkN
Then I wish you a lot of fun with it, hope it helps you if someone else is active in this thread.