[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 !!!
Related
Hi, sorry if posting in wrong section
Im currently stuck in bootloop after modifying framework-res.apk.
Phone is of course rooted, used root explorer to paste the framework-res.apk, renamed the original one.
I have googled around a bit, and im pretty confused
Any ideas how to make it boot?
Thanks!!
As it is stuck in a bootloop , all u can do is flash a stock Rom again, I find this is the only solution or may be u can push stock framework if available using adb!!
Sent from my SK17i using XDA Premium App
Wenever modifying framework u shud always consider backing up your Rom!!
Sent from my SK17i using XDA Premium App
First, thanks for the replies !!!
I messed around with fastboot a little yesterday, and i have a little problem installing it. I finally figured out how to install the drivers, but I cant get adb open, it just closes after clicking on it
How can I get this work?
First of all you should have set right permissions for the file before restart
ADB starting only from command line, and if you use Vista or Seven just right click on the folder where ADB is situated and type "ADB"
use SEUS ... it's the easy way ...
um isnt that for older SE phones? Or maybe im wrong
I couldnt find anything about it..
Ok I finally got ADB working, however it cant find my phone :/
I connected it via fastboot (?), like holding down vol-up and plug in USB, phone gets a blue notification light up left.
Is this the right mode? Drivers should be working just fine according to device manager..
Thx
rubikum said:
Ok I finally got ADB working, however it cant find my phone :/
I connected it via fastboot (?), like holding down vol-up and plug in USB, phone gets a blue notification light up left.
Is this the right mode? Drivers should be working just fine according to device manager..
Thx
Click to expand...
Click to collapse
I think so
jaxzkeren said:
use SEUS ... it's the easy way ...
Click to expand...
Click to collapse
SEUS knows if you tried to modify your phone. It won't help.
SUES is like Big Brother, it's watching you... :creep:
rubikum said:
um isnt that for older SE phones? Or maybe im wrong
I couldnt find anything about it..
Click to expand...
Click to collapse
SEUS? or sony ericsson update service still work with android devices, in fact for me works better than PC companion....
Phantoome said:
SEUS knows if you tried to modify your phone. It won't help.
SUES is like Big Brother, it's watching you... :creep:
Click to expand...
Click to collapse
I have rooted, and modified the system with uto kitchen, and other mods here in the forum and still dont have any problem if I try to flash it with SEUS
Change the permission of the file which you have copied.
Don't worry it will work fine.
---------- Post added at 08:21 AM ---------- Previous post was at 07:49 AM ----------
Root Explorer Can do the trick.
hello.. im also stuck in boot loops.. so how can i fix this using adb tools ??? plsss help :\
reflash using wotanserver
may be you wrong to set permissions
sir please please please help me i have micromax A110 i have same problem but i have backup my data and it is in internal sd card i have backup data through clockword recovery but no luck it is just boot lopping please someone help
Lol this happends never, because i know how to modify framework-res.apk properly (lol), i build a flashable zip on my phone always to make sure it copied, and have a flashable zip with framework-res.
Well, the easiest solution is to reflash the ROM/framework-res.
Jader13254 is right, you should always have a rescue strategy before messing around with something like framework-res.apk. It sounds like you don't have cwm recovery installed, which sounds particularly crazy. The bootlooping is going to make it difficult to use adb or android commander or anything similar with out recovery. If you have cwm you have some options to push the working framework onto the phone, but with out cwm, I think you can only use SUS/SEUS/PCC or flashtool to repair your phone. Just check for any of the guides for rooting, unbricking, updating ,etc your device.
PSM is now out and works on our devices all you need to do is install the Certificate by XxXPachaXxX
Download http://xxxpachaxxx.kleinrealms.com/?p=246
Download http://www.playstation.com/psm/store/en.html
Flash the Sony Package in TWRP or CWM, Only Install the Playstation Certificates
Reboot
Install APK
Login/Create Username
Rejoice!
If you go to arcade there is currently one FREE game
Note: As i said only install the playstation certificate, anymore can result in a bootloop or no boot
msfguard said:
Note: As i said only install the playstation certificate, anymore can result in a bootloop or no boot
Click to expand...
Click to collapse
Hello mate and thanks for posting the info.
When you say 'only install the playstation certificate', are you saying there's an option to pick what to install after you select the downloaded ZIP in TWRP / CW?
I really want to try this but I fear bricking my device if there's some other manual step required, such as modifying the ZIP prior to flashing from recovery.
Any additional information from you, or anyone who has applied this, would be greatly appreciated!
mroshaw said:
Hello mate and thanks for posting the info.
When you say 'only install the playstation certificate', are you saying there's an option to pick what to install after you select the downloaded ZIP in TWRP / CW?
I really want to try this but I fear bricking my device if there's some other manual step required, such as modifying the ZIP prior to flashing from recovery.
Any additional information from you, or anyone who has applied this, would be greatly appreciated!
Click to expand...
Click to collapse
Yes, The first screen ask you if you would like to install Bravia, Say No,Second is for playstation say yes!, third is xloud say no, then say stay in recovery dont let it reboot for u, reboot it after it closes aroma
Ill try to find time today to pull that certificate out, but its the only VERSION of the certificate ive gotten to actually work without constant forcecloses
Is it working on jb?
envoyé de puis mon Nexus s, aiiiiight ! (Michel rules the world)
ptr347 said:
Is it working on jb?
envoyé de puis mon Nexus s, aiiiiight ! (Michel rules the world)
Click to expand...
Click to collapse
Have only tried it on JB
Confirming it works !
THANKS !
Does it just work with root?
daxter19 said:
Does it just work with root?
Click to expand...
Click to collapse
i would assume so being that you must FLASH the permision thing
UltimateEnd said:
i would assume so being that you must FLASH the permision thing
Click to expand...
Click to collapse
I tried copying the two files from the zip to system/etc/permissions and system/frsmework and setting permissions on both to rwrr and i get the error code when starting the app. I'm not unlocked just rooted. I read on the other post about this that is all that needed to happen but no luck. It's there a way to tell from the zip what else i may need to do? I'm on JB as well.
Thanks
Brandon
bmathis said:
I tried copying the two files from the zip to system/etc/permissions and system/frsmework and setting permissions on both to rwrr and i get the error code when starting the app. I'm not unlocked just rooted. I read on the other post about this that is all that needed to happen but no luck. It's there a way to tell from the zip what else i may need to do? I'm on JB as well.
Thanks
Brandon
Click to expand...
Click to collapse
sorry i did not mean permission , (CERTIFICATE)
first download the the first file- , you should be able to download it straight from your phone, you said you are rooted ? make sure you have access to RECOVERY MODE - after your download, go in there, find the CERTIFICATE and FLASH IT . . . follow the steps given on here.
i did it twice to make sure it wasnt luck , and it worked great.
UltimateEnd said:
sorry i did not mean permission , (CERTIFICATE)
first download the the first file- , you should be able to download it straight from your phone, you said you are rooted ? make sure you have access to RECOVERY MODE - after your download, go in there, find the CERTIFICATE and FLASH IT . . . follow the steps given on here.
i did it twice to make sure it wasnt luck , and it worked great.
Click to expand...
Click to collapse
I tried one more time instead of flashing but doing it manually and the key was to completely power off instead of just rebooting. I don't know why but after that the PSM app quit erroring and works now. So it is possible to do it manually without flashing.
Side note, I tried to get into recovery and it gave me a dead android icon. I started with Power + Vol Down, chose the RCK icon and then it died. So I don't know what is up there. First time I had ever tried to get into recovery mode.
Thanks,
Brandon
Installation works as described!
But when I try to log in with my PSN credentials, I get a 'Deze service is niet beschikbaar in uw land/regio'. (This service is unavailable)
I live in Belgium. Will this be available in the future?
Or what can I do about this?
Thanks in advance.
Sent from my Transformer Prime TF201 using xda premium
Eskern said:
Installation works as described!
But when I try to log in with my PSN credentials, I get a 'Deze service is niet beschikbaar in uw land/regio'. (This service is unavailable)
I live in Belgium. Will this be available in the future?
Or what can I do about this?
Thanks in advance.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
could be restriction on country atm
bmathis said:
I tried one more time instead of flashing but doing it manually and the key was to completely power off instead of just rebooting. I don't know why but after that the PSM app quit erroring and works now. So it is possible to do it manually without flashing.
Side note, I tried to get into recovery and it gave me a dead android icon. I started with Power + Vol Down, chose the RCK icon and then it died. So I don't know what is up there. First time I had ever tried to get into recovery mode.
Thanks,
Brandon
Click to expand...
Click to collapse
that means you probably just updated to JB, you need to flash a recovery
No luck for me.
Running JB rooted only, NOT unlocked.
Installed apk.
Copied .jar file and .xml to correct directories and changed permissions on the .jar to 644.
Shutdown and restart.
Error 8008103E when trying to open.
Any ideas where I went wrong?
Never mind, you have to change permissions on the .xml file to 644 also. The AndroidPolice instructions leave that part out.
Q&A for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
hhzznn said:
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
Click to expand...
Click to collapse
Hello there,
If not using the "adbsetup" drivers or the ones off the ASUS website (sorry, couldn't find the ASUS drivers when I looked ), use one of the above. If using one and still not connecting, try the other option.
Also, check your USB ports to make sure you are not connecting via a USB 3.x standard. Android (or at least some Android devices) don't like those.
If all else fails, you may need a Linux build
Hope this provides a head start.
Sent from my LG-D520 using XDA Free mobile app
help me please
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
hhzznn said:
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
Click to expand...
Click to collapse
Looks you got a little further... :good:
From what I remember when I followed the guide, there was no feedback (nothing on the screen, and tablet remains black) on when you issue the unlock commands - which by the way, are:
Code:
fastboot oem unlock61646
fastboot oem unlockD696E
Then, reboot the bootloader and install CWM (first line may be substituted with rebooting into fastboot by hand):
Code:
fastboot reboot-bootloader
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
You shouldn't get a write-protect error this time around. Hope this helps.
By the way, your SKU is WW version, right? If not, my ROM may not help you (without going the long way around of instead of flashing the ROM, copying the odex files back into /system/app using CWM's ADB push command). Just a warning. If you are not WW, and insist on flashing anyway, I would highly recommend a nandroid backup (and probably copied) to MicroSD to protect your original (broken) ROM.
help me
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
hhzznn said:
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
Click to expand...
Click to collapse
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
the code:fastboot unlock oem61646 worked but fastboot oemD696E not working
in stock recovery i cant install rom.zip
and in fastboot when install recovery cwm answer bootloader lock
any offer for me?
---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------
**you may need a Linux build **
i have a linux base ,, may you help me??
hhzznn said:
**you may need a Linux build **
i have a linux base ,, may you help me??
Click to expand...
Click to collapse
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
i have ubuntu....what should i do?
hhzznn said:
i have ubuntu....what should i do?
Click to expand...
Click to collapse
In a terminal...
apt-get install android-tools-fastboot
...would be a good start. You may need to register the device vendor in your configuration, which I can research later if...
fastboot devices
...lists nothing. Hope this helps.
Sent from my LG-D520 using XDA Free mobile app
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Syncline said:
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Click to expand...
Click to collapse
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
joel.maxuel said:
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
Click to expand...
Click to collapse
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Syncline said:
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Click to expand...
Click to collapse
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
joel.maxuel said:
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
Click to expand...
Click to collapse
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Syncline said:
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Click to expand...
Click to collapse
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
joel.maxuel said:
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
No I wasn't encrypted before but from what I read it seems to involve a failure to mount the DATA partition correctly, and the Android OS erroneously assumes it's encrypted. I'm not overly concerned about setting up apps by hand, I do have a titanium backup of my apps and data. As I'm still at work, I can't do too much playing around on my tablet. I don't have access to my personal computer that has all my tools like adb, fastboot, etc. until the work day is done. I've said it a couple of times, but I truly appreciate the assistance that you've provided.
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Syncline said:
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Click to expand...
Click to collapse
That's an interesting side effect...never had that happen before.
You can try it, and let me know. Hopefully your CWM is still kicking around, or else you will have to reinstall via fastboot. Or alternatively, just re-root normally (like with Kingo).
By the way, before you do that, does /system/xbin/su exist? Or what you could answer, is you could download Voodoo OTA RootKeeper and report back which values are not checked off. I think SuperSU update.zip places the su binary, nothing else. But we shall see.
Sorry Joel, I didn't see your reply before I flashed the SuperSU zip but it did work, my tablet is rooted again.
Hi guys!
I have made a serious mistake, and I feel so stupid! I was wondering if any you awesome people at XDA would be able to save me.
I have an LG G2 vs980 Lollipop 5.0.2
So, all I wanted to do was change my startup screen to get rid of that boring LG logo and replace it with something neater. I went over to Google and found a guide on how to do this, and followed the steps 1 by 1. Everything actually worked out perfectly, but it wasn't until after I was locked out of my phone that I realized that I had used a startup image that was not compatible with my LG G2! (Total face palm!). Now, whenever I power my phone, it flashes that "neat" image that I replaced the stock one with - before the screen goes completely blank. Not good at all.
So my question is this - Is there a way I can acess my system folder without having access to my phone? I know EXACTLY what file I need to remove/edit to solve this problem! In fact, that is what is frusturating me the most. It's not some random error message out of the blue that I know nothing about. I know exactly what the problem is, I just don't know if I have access to the solution. I just really hope I don't have to wipe everything back to stock all because of a lousy startup image.
If anybody can help me access my system folder so I can switch out the bad file for the default one, and get access to my phone again - I would be so forever grateful! Thank you in advance to anybody that can save me!
Much appreciative,
Terri (Psyintz)
PsyintZ said:
Hi guys!
I have made a serious mistake, and I feel so stupid! I was wondering if any you awesome people at XDA would be able to save me.
I have an LG G2 vs980 Lollipop 5.0.2
So, all I wanted to do was change my startup screen to get rid of that boring LG logo and replace it with something neater. I went over to Google and found a guide on how to do this, and followed the steps 1 by 1. Everything actually worked out perfectly, but it wasn't until after I was locked out of my phone that I realized that I had used a startup image that was not compatible with my LG G2! (Total face palm!). Now, whenever I power my phone, it flashes that "neat" image that I replaced the stock one with - before the screen goes completely blank. Not good at all.
So my question is this - Is there a way I can acess my system folder without having access to my phone? I know EXACTLY what file I need to remove/edit to solve this problem! In fact, that is what is frusturating me the most. It's not some random error message out of the blue that I know nothing about. I know exactly what the problem is, I just don't know if I have access to the solution. I just really hope I don't have to wipe everything back to stock all because of a lousy startup image.
If anybody can help me access my system folder so I can switch out the bad file for the default one, and get access to my phone again - I would be so forever grateful! Thank you in advance to anybody that can save me!
Much appreciative,
Terri (Psyintz)
Click to expand...
Click to collapse
You can flash TWRP 3.x.x using adb and access system from there, as it has a built-in file manager in it.
MigoMujahid said:
You can flash TWRP 3.x.x using adb and access system from there, as it has a built-in file manager in it.
Click to expand...
Click to collapse
Really?? That would be great! However, I am unable how to go about doing this. All of the guides I can find require access to my phone in order to do this. I tried using this guide (https://www.xda-developers.com/how-to-install-twrp/) and when I try to run the "adb reboot bootloader" command, it says "error: device (null) not found." I am starting to get worried that there is nothing I can do. Does anybody know how I would go about installing TWRP? Or am I out out of luck? Thanks again in advance!
Sincerely,
Terri
PsyintZ said:
Really?? That would be great! However, I am unable how to go about doing this. All of the guides I can find require access to my phone in order to do this. I tried using this guide (https://www.xda-developers.com/how-to-install-twrp/) and when I try to run the "adb reboot bootloader" command, it says "error: device (null) not found." I am starting to get worried that there is nothing I can do. Does anybody know how I would go about installing TWRP? Or am I out out of luck? Thanks again in advance!
Sincerely,
Terri
Click to expand...
Click to collapse
In order to use adb you must have USB debugging enabled, had you have it enabled?
If not you can use lg flash tool 2014 to flash stock rom, there is a way to flash it with out wiping, by using normal mode.
Follow this guide:
https://forum.xda-developers.com/showthread.php?t=2432476
As mentioned in the guide about Normal mode:
Normal Flash: Flash ROM without losing any data. Only use this when you need to fix system error. Beware of boot loop when flashing ROM that differ from current ROM on your phone or MOD ROM.
Click to expand...
Click to collapse
Which looks like your case.
Use the firmware from this link, it's lollipop:
https://www.androidfilehost.com/?fid=95916177934539835
MigoMujahid said:
In order to use adb you must have USB debugging enabled, had you have it enabled?
If not you can use lg flash tool 2014 to flash stock rom, there is a way to flash it with out wiping, by using normal mode.
Follow this guide:
https://forum.xda-developers.com/showthread.php?t=2432476
As mentioned in the guide about Normal mode:
Which looks like your case.
Use the firmware from this link, it's lollipop:
https://www.androidfilehost.com/?fid=95916177934539835
Click to expand...
Click to collapse
Yes. I had to enable USB Debugging during the process of swapping out my bootanimation files. However, I am still recieving that "error: device (null) not found." message.
PsyintZ said:
Yes. I had to enable USB Debugging during the process of swapping out my bootanimation files. However, I am still recieving that "error: device (null) not found." message.
Click to expand...
Click to collapse
Read my full post again, there is an alternative method
However, try downloading PDANet and try connecting again.
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