• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Warning! Potential Soft Brick When Using UOT Themes

Curtis1973

Curtis1973

Android Expert
When you copy and paste the framework-res.apk over to system/framework you run the risk of the phone not rebooting but instead freezing where it should reboot. The only option youll have is to pull the battery. When you do youll be stuck in lg logo boot loop. ADB will not recognize the device to copy back the framework-res.apk either. I even tried using LGNPST to reflash my tot file but the device would only show as in standby mode. I used root explorer to copy the file over originally. It worked flawlessly and the freeze happened at random. So be careful and be aware that it can happen. There may be a method to get back into the phone. I did not try any of the boot loop methods I found but they may or may not work. I ended up getting a replacement.
 
Also for jcase and those who developed the root exploit,can we actually perform a factory reset? I did try that when I had the freeze up and it did nothing. Wasnt sure if it was due to copying the edited uot framework/systemui files or if the factory reset isnt available after rooting. Any info would be helpful on this so I dont try to use factory reset. Thanks.
 
I had no issues with factory reset after flashing rooted tot file. It wasn't until I had removed some bloat apps that a factory reset screwed up. I got stuck in a loop where eveytime I rebooted or turned on phone it would factory reset. I used the memory debug app of qpst to rest phone and it fixed loop

If you are straight rooted there should be no issue

If you have removed system apps you may wanna hold off on factory reset. I been meaning to ty and figure out if one paticular app is to blame or if it's an md5 or similar issue
 
makes sense. i hadnt thought that removing the system/bloat apps might effect the factory reset. so what ill do is just reflash my tot instead of using the factory reset in recovery mode. that way (i hope it can be done lol) i avoid ye olde BRICK!!! lol
 
Curtis1973 said:
makes sense. i hadnt thought that removing the system/bloat apps might effect the factory reset. so what ill do is just reflash my tot instead of using the factory reset in recovery mode. that way (i hope it can be done lol) i avoid ye olde BRICK!!! lol
Click to expand...

Well, I can't test this due to the fact that I dont have the phone anymore. BUT What about booting into recovery and flashing the tot from there? It was possible on some other thing that soft bricked the phone, maybe for this one too?

I still watch these forums lol
 
nah booting into recovery and flashing the tot from there doesnt work. atleast it doesnt after a failed copy to system of framework-res.apk where the phone freezes and doesnt complete the copy and overwrite. the phone shows but only as in stand by mode. now flashing the tot via recovery where you have the original or even modified framework-res might work. i think the issue i had was because the entire framework-res file was borked or not even in system/framework any more.
 
I have had an issue with uot spitting out crap files. Most on my themes are around 2.4mb and I've had is spit out ones that are less than 1mb. Wonder if you got a crap file?
 
that is possible. and I've noticed uot having varying file sizes even though nothing was changed enough to add up to or lessen file size by much.
 
So, just how would you go about reflashing the .tot then, if it is stuck on the LG splash logo and won't go from there, while still being able to boot into recovery and the download mode? I just had a framework-res issue and it soft-bricked, and I'm not sure how to undo the soft brick.
 
you might be able to enter recovery and NOT factory reset but try loading the lg flash tool to reflash the tot. i factory reset and then couldnt get the lg tool to recognize the device properly. it showed as in standby mode but no other functions would work,nor would adb. but adb SHOULD work to push a working framework-res to system/framework as long as you just enter recovery without doing anything else. or atleast my theory. i made the mistake of factory resetting in recover before i tried the lg tool or adb and then neither worked. i ended up getting a replacement. try both methods. but they may not wprk. also there is a bootloop fix method here on page 2 or 3. but im not sure itll work for a device with a borked framework-res. worth a try though.
 
LGNPST? I tried that, but not adb, before already factory resetting. My computer will recognize the OE when it's booted into recovery, but not in download, adn adb can't find it even when my computer does. LGNPST only gave me the option "Emergency", and any attempt to flash the ROM failed with a path error.

Just tried QPST memory debug for the boot loop fix, and no dice - computer can only see the phone in recovery, QPST needs it in download, but computer can't see the phone in download. I might have to get a replacement *sigh*

EDIT: If there were only a way to get the phone to read the paths and data from the ExSD, it wouldn't be an issue, as I've a .tot there.

EDIT: If nothing else, this is good data for the future!
 
You must log in or register to reply here.
Back
Top Bottom