Yes, it does in fact work.
Sorta.
Pre requisites: ROOT, File explorer of your choice that uses root and make sure in the settings to enable hidden folders.
You'll need to clear out substratum to make sure there isn't anything lingering and then select your overlay and build/enable them.
Once you do you'll need to open up your file explorer and go to
Data/media/0/.substratum
(If you don't see .substratum you didn't enable hidden folders)
You should have the overlay apks inside. Select all, copy and go to
System/app
And paste your apks inside of it then reboot.
Once your phone boots back up go into substratum and inside of the manager you should see your overlays. Select them and enable them! You may have to reboot for the overlays to properly work as usual
Aaaaaand Substratum already has a beta working! https://play.google.com/apps/testing/projekt.substratum/join
Happy modding!
So far themes that work:
Pi Dark: System, GPS, Settings, and System UI work flawlessly
Swift Dark/Black: All apps except for system/UI work
Sai's Oreo Theme: Android system (stock blue only) System UI and QS tiles only!! Anything else will cause your phone to bootloop. You'll need to boot into twrp, mount storage and go into your system/system/app folder and delete the APK's that caused it to loop
Gave it a shot... Long story short.... Bootloop..... Reflashed factory image.
My stupid fault. I followed directions from another source. May try again after the next update.
so i tried this yesterday and got into a bootloop. followed directions and all but now my phone doesnt connect to my laptop when i plug it in via usb. so now i'm not able to use fasboot to flash the imgs. im running out of ideas to try.
holla420 said:
so i tried this yesterday and got into a bootloop. followed directions and all but now my phone doesnt connect to my laptop when i plug it in via usb. so now i'm not able to use fasboot to flash the imgs. im running out of ideas to try.
Click to expand...
Click to collapse
You may have to use different cables or pc. I assume your SDK/platform-tools is up to date?
Badger50 said:
You may have to use different cables or pc. I assume your SDK/platform-tools is up to date?
Click to expand...
Click to collapse
yes my platform-tools is up to date. i tried another laptop and cables. still not seeing my phone. im getting a unknown usb device (Device descriptor request failed ). think my phone is done:crying:
holla420 said:
yes my platform-tools is up to date. i tried another laptop and cables. still not seeing my phone. im getting a unknown usb device (Device descriptor request failed ). think my phone is done:crying:
Click to expand...
Click to collapse
Can you boot into bootloader? Power + volume down?
azpatterson3 said:
Can you boot into bootloader? Power + volume down?
Click to expand...
Click to collapse
yes im able to boot into bootloader and twrp.
Don't think your phone is a goner but can't understand why it isn't being seen as a fastboot device while in bootloader mode.
azpatterson3 said:
Don't think your phone is a goner but can't understand why it isn't being seen as a fastboot device while in bootloader mode.
Click to expand...
Click to collapse
i didnt think so neither but nothing i tried working i also have a friend of mines hes a developer and even he dont understand why its not being recognized in adb/fastboot
holla420 said:
i didnt think so neither but nothing i tried working i also have a friend of mines hes a developer and even he dont understand why its not being recognized in adb/fastboot
Click to expand...
Click to collapse
If you can get into twrp mount your storage, go into system/system/app and you should see the theme apks inside of it. Delete them and reboot
azpatterson3 said:
Gave it a shot... Long story short.... Bootloop..... Reflashed factory image.
My stupid fault. I followed directions from another source. May try again after the next update.
Click to expand...
Click to collapse
Substratum is working now without needing to manually copy paste the files. I'd still do a titanium backup before messing with themes
Cosmo100292 said:
If you can get into twrp mount your storage, go into system/system/app and you should see the theme apks inside of it. Delete them and reboot
Click to expand...
Click to collapse
I did see the apks I removed 3 of them and rebooted. That didn't do nothing. Still boot looping and now it's just stuck at the TWRP bootup screen. And my laptop wasn't seeing my phone when plugged in. I tried numerous computers. I did a RMA yesterday. It was unlocked from VZW so I know the replacement will end my rooting and having fun with the phone.
Not sure what I'm doing wrong but I have the latest 997 version and I checked to make sure it was installing the apk's into the system folder. I'm using pi dark by the way
holla420 said:
I did see the apks I removed 3 of them and rebooted. That didn't do nothing. Still boot looping and now it's just stuck at the TWRP bootup screen. And my laptop wasn't seeing my phone when plugged in. I tried numerous computers. I did a RMA yesterday. It was unlocked from VZW so I know the replacement will end my rooting and having fun with the phone.
Click to expand...
Click to collapse
That's extremely odd
Cozzeck said:
Not sure what I'm doing wrong but I have the latest 997 version and I checked to make sure it was installing the apk's into the system folder. I'm using pi dark by the way
Click to expand...
Click to collapse
I would clear everything out, uninstall and reinstall substratum and try reapplying the overlay. Reboot, re apply the overlay and it should come up in the manager section in substratum
Cosmo100292 said:
If you can get into twrp mount your storage, go into system/system/app and you should see the theme apks inside of it. Delete them and reboot
Click to expand...
Click to collapse
Cosmo100292 said:
That's extremely odd
Click to expand...
Click to collapse
I can still boot into bootloader/fastboot mode to bad I can't get USB to read my phone
Can someone be kind enough to please help with the android p button drawables? The pill shaped button especially!
holla420 said:
I can still boot into bootloader/fastboot mode to bad I can't get USB to read my phone
Click to expand...
Click to collapse
Do you have your stock image on your phone? You could wipe it and flash the stock image through twrp
Cosmo100292 said:
If you can get into twrp mount your storage, go into system/system/app and you should see the theme apks inside of it. Delete them and reboot
Click to expand...
Click to collapse
Cosmo100292 said:
Do you have your stock image on your phone? You could wipe it and flash the stock image through twrp
Click to expand...
Click to collapse
Unfortunately it's bootlooping to TWRP and stuck on TWRP splash screen. I think she's done now. R.I.P. lol
Related
[Q]Sony BootLoop Solution??
Only post here is somebody get the solution of bootloop problem..
i think that the only think that we can do is wait for someone that posts an update.zip to be flashed via recovery, obviously for the different versione..mine is 16gb 3g (europe sgpt114it)...your is?
I understand that we're all happy we got root, but you gotta be careful running out and deleting/freezing everything without a proper way to restore!
Also, these question threads should all be moved to general.
sorry for posting here, but I can see many people facing this similar boot loop issue & other threads are getting flooded, that is why I posted here..
Lets try to find some way as of now to get rid of this frustrating boot loop !!!
EDIT:
Can anyone tell me, what exactly should be present inside those update.zip?
I am not able to unzip or see the content of signed-nbx03_001XXXXXXXXX.zip, giving some error !!!
it gives errors because the zip is encrypted
what if someone posts a full rom dump and i flash all the files manually via adb?
I tried with another zip and now in Recovery Mode , getting below error:
E:signature verification failed
Installation aborted.
xperiax10.awesome said:
I tried with another zip and now in Recovery Mode , getting below error:
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
on that boot loop - do you have access to adb? for a second or two?
br
condi
i had, now it just hangs on the sony logo on the boot..the only hope left is an original update.zip for my model...
condi said:
on that boot loop - do you have access to adb? for a second or two?
br
condi
Click to expand...
Click to collapse
No..
sent via awesome aRc (rooted 2.3.4)
sapphire88 said:
it gives errors because the zip is encrypted
what if someone posts a full rom dump and i flash all the files manually via adb?
Click to expand...
Click to collapse
Since some files are encrypted or contain personal keys, I would think that this would be not advisable. Especially if you have the 3G version (IMSI keys, eyc.)
However, if you can remember what was the last action you performed before the bootloop (for example, uninstalled a particular system app), I would be happy to find the .apk and/or relevant system folder for you so you can install it via ADB (I suppose this would be possible, provided you still have ADB access and root/su).
I was trying to change the fonts using FONT CHANGER, I have not deleted any of the default apps or anything.
Tablet S, 16GB WiFi version (SGPT111SG)
xperiax10.awesome said:
No..
sent via awesome aRc (rooted 2.3.4)
Click to expand...
Click to collapse
****.. thats not good.. you cant even reflash the same version of update..
you could wait for another update from sony, or wait for some hack of recovery, or hm... warranty?
are you able to get into recovery?
I am able to go into Recovery Mode, tried updating thru sdcard but I think we dont have the proper firmware to restore!!!
Its under warranty but donno wanna go there, it needs a solution coz I will again try to change fonts for sure
Did you try looking at condi's post? I am not quite sure what condi managed to achieve, but it sounds at least relevant.
Also, bear in mind I have posted a link to the contents of the (stock) font folder. If we knew exactly what changes are made by this application, it would be possible to revert them. If you can find out, I can find the stock files for you so you can manually reverse this issue.
EDIT: Do NOT try any of the above -- according to sapphire88. You've been warned!
tried both the way, by replacing the fonts with the original ones and by editing the build.prop...the results is that now i'm stucked at the sony logo (no more one time access to the home screen) ...contacted sony to ask them if i could have the original firmware in update.zip format...perhaps (i don't really think that they will give it to me)...
Well, this still makes no sense however. Can we approach the developer of Font Changer and ask the sort of changes the application is performing? I assume that it is not just replacing fonts, but also some system files that point to the fonts that are being used. If we could track all changes and reverse them, surely this would fix the issue.
What about condi's downgrade/upgrade option? (you said it did not work)
Also, do you still have access to ADB (perhaps in recovery)? If you do, then you can still essentially find ways to fix this issue. But for the time being let's black list Font Changer.
i haven't used an app to change the fonts, i've manually replace the three clock fonts (only those three files), and it ended in a bootloop, in recovery adb doesn't work and i can't no more access to the home screen to use adb..
anyone know about Safety Mode?? How to enter into safety mode.
Note: I am NOT talking about Recovery mode..
grcd said:
What about condi's downgrade/upgrade option? (you said it did not work)
Click to expand...
Click to collapse
I think that I found a way to downgrade. Will check it today evening, will post the results.
sapphire88 said:
i haven't used an app to change the fonts, i've manually replace the three clock fonts (only those three files), and it ended in a bootloop, in recovery adb doesn't work and i can't no more access to the home screen to use adb..
Click to expand...
Click to collapse
ADB is available in recovery - just wait a minute or two - it will become available. But its not fully working as in normal boot. Check it, you can 'adb push' some files, maybe you could turn your fonts to stock ones?
xperiax10.awesome said:
anyone know about Safety Mode?? How to enter into safety mode.
Note: I am NOT talking about Recovery mode..
Click to expand...
Click to collapse
Yes, I figured it out some time ago, press power + vol-down, and keep vol-down pressed until tab fully start system.
ohh, so safe mode of no use as we are stuck with boot loop !!!
Good evening Ladies & Gents.
Firstly can I say, this site has been my bible, and I am so very very grateful for all the work that everyone has put in to making this site what it is.
Now down to business.
I have an HOX+ and have been flashing for about a year now but still consider myself to be a complete nub! first with hox then i broke it and now hox+. Im in a bit of a predicament.
I flashed a version of aosp 4.4 onto the phone, installed from the zip file, cleared the cache, user data and dalvik.
rebooted, and got stuck in a boot loop.
So i went to my backup and restored from there...
boot loop again.
So i went back into bootloader, then fastboot, and reflashed the viper+ 2.0.1 that I had on before.
But when I got stuck on sending boot
Now im stuck in a boot loop, none of my backups will restore properly.
I fear I am hardbricked as I cant get anything to work...
Any help before I have to be back at work tomorrow would be very helpful! and even more appreciated!
Yours
A very frustrated and stressed British nub
Sorry, also, I have checked through xda and I cant seem to find anything that would explain why I am stuck!
flash the boot.img
from a welsh person who can't understand why people cannot flash rom's correctly
Fastboot
Lloir said:
flash the boot.img
from a welsh person who can't understand why people cannot flash rom's correctly
Click to expand...
Click to collapse
I used "fastboot flash boot boot.img" in my cmd, like i always have done, and this time it doesn't want to work...at all
ryutnm said:
I used "fastboot flash boot boot.img" in my cmd, like i always have done, and this time it doesn't want to work...at all
Click to expand...
Click to collapse
you tried fulling wiping? then just flashing the rom + bootimage after
thanks
Lloir said:
you tried fulling wiping? then just flashing the rom + bootimage after
Click to expand...
Click to collapse
No, does that require different fastboot commands?
i have cwm touch recovery installed. Would that make a difference?
Also, could I just say thank you in advance for your help sir!
ryutnm said:
No, does that require different fastboot commands?
i have cwm touch recovery installed. Would that make a difference?
Also, could I just say thank you in advance for your help sir!
Click to expand...
Click to collapse
Unless you mean the user data and cache wipe.
Then yeah i did that
ryutnm said:
Unless you mean the user data and cache wipe.
Then yeah i did that
Click to expand...
Click to collapse
Data/system/cache
Sent from my Nexus 5 using Tapatalk
ryutnm said:
Good evening Ladies & Gents.
Firstly can I say, this site has been my bible, and I am so very very grateful for all the work that everyone has put in to making this site what it is.
Now down to business.
I have an HOX+ and have been flashing for about a year now but still consider myself to be a complete nub! first with hox then i broke it and now hox+. Im in a bit of a predicament.
I flashed a version of aosp 4.4 onto the phone, installed from the zip file, cleared the cache, user data and dalvik.
rebooted, and got stuck in a boot loop.
So i went to my backup and restored from there...
boot loop again.
So i went back into bootloader, then fastboot, and reflashed the viper+ 2.0.1 that I had on before.
But when I got stuck on sending boot
Now im stuck in a boot loop, none of my backups will restore properly.
I fear I am hardbricked as I cant get anything to work...
Any help before I have to be back at work tomorrow would be very helpful! and even more appreciated!
Yours
A very frustrated and stressed British nub
Click to expand...
Click to collapse
Well the bootlooping has something to do with not flashing the boot.img stated by yourself and lloir. About that bug of "Sending boot.img", it happens to me but I fix it by running CMD as administrator , If that doesnt work, try using a different usb port. Preferably one directly to pc/laptop rather than using a hub. Try a 3.0usb port first, if that doesnt work then 2.0usb port.
P.S Without S-Off you can't become hardbricked. Till now I didn't see a single person who bricked their HOX+ unless he received an S-Off developer phone..
Lloir said:
Data/system/cache
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Im now only getting "waiting for device"
which I can only assume means my pc now doesnt even recognise the phone when its booted in bootloader/fastboot usb mode?
ryutnm said:
Im now only getting "waiting for device"
which I can only assume means my pc now doesnt even recognise the phone when its booted in bootloader/fastboot usb mode?
Click to expand...
Click to collapse
stop....Hammer time...
have you got a rom on the sdcard (in cwm) if yes
wipe data/system/cache
then
reboot into bootloader
fastboot flash boot boot.img
if not ----------
full wipe (as above)
adb sideload romname.zip
then reboot into bootloader as above
Lloir said:
stop....Hammer time...
have you got a rom on the sdcard (in cwm) if yes
wipe data/system/cache
then
reboot into bootloader
fastboot flash boot boot.img
if not ----------
full wipe (as above)
adb sideload romname.zip
then reboot into bootloader as above
Click to expand...
Click to collapse
I have the zip on the internal storage as i dont have "sd/ext" or what ever the extention is. When I bought the phone I never had the sd card. Never was able to save anything onto an sd card.
so should i try installing from the zip? even though the fastboot commands arent working?
or would a sideload skip the fastboot commands?
or am i just being completely retarded
Edt - just tried the sideload using the cmd, and i had error: device not found
so windows isnt recognising my phone...it was working this morning
ryutnm said:
I have the zip on the internal storage as i dont have "sd/ext" or what ever the extention is. When I bought the phone I never had the sd card. Never was able to save anything onto an sd card.
so should i try installing from the zip? even though the fastboot commands arent working?
or would a sideload skip the fastboot commands?
or am i just being completely retarded
Click to expand...
Click to collapse
Why am i being ignored you guys lol. Did you try my solution ?
Terribly Sorry
Ghand0ur said:
Why am i being ignored you guys lol. Did you try my solution ?
Click to expand...
Click to collapse
dude, im so sorry - i didnt even see the post!
i will try now!
sorry again
edt - still no joy as for some reason my phone is no longer being recognised by my pc =[
HTC sync uninstalled ?
you have killed adb (if on windows just kick open taskman and kill adb)
or in cmd\terminal adb kill-server
then do adb devices
reboot pc?
try a different usb cable (maybe the one from your charger if you are not using that one)
*edit the above is assuming you are in recovery
IF NOT in recovery, but fastboot_usb mode
then fastboot devices (but you cannot do jack apart from flash boot image)
IF in recovery, you got a few choices
wait 5-10minutes (don't ask, it's a common issue with the X+ and CWM\TWRP)
put the device in adb sideload for a minute or so (^ see above reason)
i have adb issues in CWM\TWRP myself, especially when i have no rom and so on, so i know your frustration, patience young padwan
looking good so far
Ghand0ur said:
Why am i being ignored you guys lol. Did you try my solution ?
Click to expand...
Click to collapse
Lloir said:
HTC sync uninstalled ?
you have killed adb (if on windows just kick open taskman and kill adb)
or in cmd\terminal adb kill-server
then do adb devices
reboot pc?
try a different usb cable (maybe the one from your charger if you are not using that one)
Click to expand...
Click to collapse
So I tried starting cmd in administrator mode [never had to before]
- Didnt work
- Plugged into a different usb slot as lloir suggested, didnt get the "windows does not recognise this device" this time
restarted cmd as admin like Ghandour suggested.
Just managed to install the viperx+ 2.0.1 rom and i am now setting it up!
THANK YOU SO FREAKING MUCH GUYS [and gals if either of you are female]!
do you know why I had to start using cmd as an administrator?
ryutnm said:
So I tried starting cmd in administrator mode [never had to before]
- Didnt work
- Plugged into a different usb slot as lloir suggested, didnt get the "windows does not recognise this device" this time
restarted cmd as admin like Ghandour suggested.
Just managed to install the viperx+ 2.0.1 rom and i am now setting it up!
THANK YOU SO FREAKING MUCH GUYS [and gals if either of you are female]!
do you know why I had to start using cmd as an administrator?
Click to expand...
Click to collapse
might be because of where you have the adb tools. and i'am 100% male
thanks
Lloir said:
might be because of where you have the adb tools. and i'am 100% male
Click to expand...
Click to collapse
well dude, thank you for your help!
I dont understand why though, ive been using this pc the whole time to flash recovery images and boot images and never had to use admin
Thank you
Also a thank you to Ghand0ur for your help as well!
So very much appreciated
ryutnm said:
Also a thank you to Ghand0ur for your help as well!
So very much appreciated
Click to expand...
Click to collapse
Glad you got it working. Just always try those common solutions:
-Restart PC
-Run as admin
-unplug replug
-reboot phone
-try different usb port
-try different usb cable.
So here it goes!
I have this phone, a Cherry Mobile Aeon [ full specs: please find on google. Can't post links yet, apparently. ], and rooted it. It rooted successfully the first time ( with usb debugging enabled and everything. ) and so, as idiotic as I am, I installed CF3D on a JB phone so it ended up bootlooping. And so I data/factory reset it by STOCK RECOVERY then I tried recovering it by ADB but then, everytime I type the su command, it always says UI CONNECT - TIMED OUT or something like that.
And so I've searched Google on why is that happening and found out that it prompts if the device is unrooted!
Now I can't root it back cause I don't have USB Debugging enabled. And I can't get it to the service center because they said that they don't have the software for this phone yet! WHICH IS VERY IDIOTIC!
Please halp.
LockeMishil said:
So here it goes!
I have this phone, a Cherry Mobile Aeon [ full specs: please find on google. Can't post links yet, apparently. ], and rooted it. It rooted successfully the first time ( with usb debugging enabled and everything. ) and so, as idiotic as I am, I installed CF3D on a JB phone so it ended up bootlooping. And so I data/factory reset it by STOCK RECOVERY then I tried recovering it by ADB but then, everytime I type the su command, it always says UI CONNECT - TIMED OUT or something like that.
And so I've searched Google on why is that happening and found out that it prompts if the device is unrooted!
Now I can't root it back cause I don't have USB Debugging enabled. And I can't get it to the service center because they said that they don't have the software for this phone yet! WHICH IS VERY IDIOTIC!
Please halp.
Click to expand...
Click to collapse
Your phone not booting after installing cf3d?
Hell_X said:
Your phone not booting after installing cf3d?
Click to expand...
Click to collapse
It's stuck on bootloop.
LockeMishil said:
It's stuck on bootloop.
Click to expand...
Click to collapse
dont worry
cf3d creates a backup zip which can be flashed if you get bootloop simply boot to cwm recovery and then flash the zip it will be on /sdcard/ something related to cf3d.zip
Hell_X said:
dont worry
cf3d creates a backup zip which can be flashed if you get bootloop simply boot to cwm recovery and then flash the zip it will be on /sdcard/ something related to cf3d.zip
Click to expand...
Click to collapse
That's my problem. Since my phone is kinda new on the market and a very remote brand for that matter, I haven't been able to find a CWM that would be compatible on my phone. Which sucks.
And also, I haven't seen that back-up you are saying. I think it is stored on the internal sdcard. :/ Which I cannot access, obvs.
LockeMishil said:
That's my problem. Since my phone is kinda new on the market and a very remote brand for that matter, I haven't been able to find a CWM that would be compatible on my phone. Which sucks.
And also, I haven't seen that back-up you are saying. I think it is stored on the internal sdcard. :/ Which I cannot access, obvs.
Click to expand...
Click to collapse
If you have your Rom Backup than flash that?
Hell_X said:
If you have your Rom Backup than flash that?
Click to expand...
Click to collapse
As I was saying, I am only rooted, no cwm, no way of flashing and since I am an idiot. I didn't have back up too. Can you suggest an easy way on porting CWMs though?
Yeah um I was changing some things in framework-res.apk and I forgot to change it back and now my phone just stays on the boot animation.
I have a rooted Sony Xperia m5 and I would like to know is there anyway that I can somehow access the phones folders while its in this state so I can rename it or just something to get it going again without losing all of my data because I have something kind of important on it. Any help is appreciated
If you have root then just use ADB to rename the file. There are plenty of tut on how to do this.
zelendel said:
If you have root then just use ADB to rename the file. There are plenty of tut on how to do this.
Click to expand...
Click to collapse
Do I need twrp or something because it keeps saying device offline
ih8redsn0w said:
Do I need twrp or something because it keeps saying device offline
Click to expand...
Click to collapse
That is just a driver issue. If it is installed them remove it and reinstall it.
zelendel said:
That is just a driver issue. If it is installed them remove it and reinstall it.
Click to expand...
Click to collapse
I've tried but still says offline
Am I supposed to to put it in some certain mode because I don't think it's working
ih8redsn0w said:
I've tried but still says offline
Am I supposed to to put it in some certain mode because I don't think it's working
Click to expand...
Click to collapse
Download mode is what you need to be in. Also helps alot if your in a Linux os
zelendel said:
Download mode is what you need to be in. Also helps alot if your in a Linux os
Click to expand...
Click to collapse
I put it into download mode and when I type adb devices it just stays blank but if I turn it on and it stays at the boot animation it comes up but says unauthorised and I'm on Windows 10
Would it help if I flashed twrp or no?
My brother decided to update the his phone from CM12 to CM13, however after the update started as soon as the screen flashes the picture of the android robot the screen simply turned itself off.
Then the screen turns on a for a second or so only to turn off after. This keeps repeating, sometimes it turns on with a black screen, other times with the android robot.
I waited a while to see if it could be something update related but it just kept going on like this for hours, so I took off the battery and plugged it on again, but whenever I try to access recovery it goes back to updating.
If it's worth noting, he was using an SD card as internal memory, his device storage was mostly full but he made some space for downloading the update image.
Is the phone bricked or is still possible to undo this and force updating with adb or something?
Thanks in advance.
Do you have a custom recovery on the phone?
Did you wipe data before updating?
Vagelis1608 said:
Do you have a custom recovery on the phone?
Did you wipe data before updating?
Click to expand...
Click to collapse
There is CM recovery on the phone, but no, data wasn't wiped. It was an update through the phone settings, not through recovery.
gemah said:
There is CM recovery on the phone, but no, data wasn't wiped. It was an update through the phone settings, not through recovery.
Click to expand...
Click to collapse
I am not familiar with CM's update process.
Try booting without the SD card plugged in. Recovery also.
Vagelis1608 said:
I am not familiar with CM's update process.
Try booting without the SD card plugged in. Recovery also.
Click to expand...
Click to collapse
I just checked wiki and other stuff. Updating from 12 to 13 shouldn't be an issue without wiping user data (as a matter of fact I did it with my Xperia SP/huashan and despite GApps crashing every second, everything else worked fine.
I tried without SD and SIM card, no difference.
And I actually managed to access recovery (it's slightly tricky), but it's stock. I'm pretty sure I've got CM recovery installed on this phone but now I'm even more puzzled about what the heck is going on.
No luck trying to access recovery with adb.
gemah said:
I just checked wiki and other stuff. Updating from 12 to 13 shouldn't be an issue without wiping user data (as a matter of fact I did it with my Xperia SP/huashan and despite GApps crashing every second, everything else m worked fine.
I tried without SD and SIM card, no difference.
And I actually managed to access recovery (it's slightly tricky), but it's stock. I'm pretty sure I've got CM recovery installed on this phone but now I'm even more puzzled about what the heck is going on.
No luck trying to access recovery with adb.
Click to expand...
Click to collapse
No wonder the update process is stuck.
The ROM sees the update files and boots into recovery to flash them and the recovery checks their signature, but since the files are not singed by LG, the check fails and reboots back into android.
The files are either in /cache or /data.
Try to wipe /cache. If you can't or if it doesn't work, wipe /data. (You can use the recovery)
I tried to wipe user data with stock recovery but it's no use. Unfortunately it's limited to that.
Is it not possible to force flashing of the cm image or stock firmware image somehow? I've tried to access download mode (for flashing other images when an update fails) but I can't either.
Oh, and Merry Christmas and Happy Holidays y'all!
gemah said:
I tried to wipe user data with stock recovery but it's no use. Unfortunately it's limited to that.
Is it not possible to force flashing of the cm image or stock firmware image somehow? I've tried to access download mode (for flashing other images when an update fails) but I can't either.
Oh, and Merry Christmas and Happy Holidays y'all!
Click to expand...
Click to collapse
I run out of ideas...
Are you sure the procedure you are following to access download mode is the right one?
Merry Christmas!
Vagelis1608 said:
I run out of ideas...
Are you sure the procedure you are following to access download mode is the right one?
Merry Christmas!
Click to expand...
Click to collapse
Yeah, I'm pretty sure. Plugging the USB has it locked on the charging screen, unable to turn on. Trying to remove and place back battery works while plugged, but the Volume Up + Power combination boots to Android, not to download mode, unfortunately.
gemah said:
Yeah, I'm pretty sure. Plugging the USB has it locked on the charging screen, unable to turn on. Trying to remove and place back battery works while plugged, but the Volume Up + Power combination boots to Android, not to download mode, unfortunately.
Click to expand...
Click to collapse
The other end of the USB cable is plugged in a PC with the proper drivers, right?
Vagelis1608 said:
The other end of the USB cable is plugged in a PC with the proper drivers, right?
Click to expand...
Click to collapse
Yes, everything, but the phone, right on my side.
gemah said:
Yes, everything, but the phone, right on my side.
Click to expand...
Click to collapse
You should figure out why download mode doesn't work.
Hard to say, though.
Vagelis1608 said:
You should figure out why download mode doesn't work.
Hard to say, though.
Click to expand...
Click to collapse
I'd be more confident about trying something, like flashing recovery again, if I could access the internal storage of the phone somehow directly or if adb worked fine with it, but without that there isn't much that can be done I guess.