Related
I just updated my LTE to the official Bell Mobility ICS software, I rooted it and was in the process of deleting bloatware and i accidentally deleted SystemUI.apk. Thus leading to a crash and now my phone is stuck on the LG screen with security error underneath. Can someone please help me get my phone working again.
Thanks.
You're going to have to go through the unbricking guide since you definitely just bricked your phone.
You can try doing a factory reset if it lets you. Not sure if it lets you in that situation though.
When device is completely off, hold power button and volume down button for 5-10 seconds. Then press power button twice to confirm.
He deleted SystemUI.apk. Even if that didn't trigger LG's secure boot error, it would be in an endless bootloop that only *might* be recoverable if adb still managed to function and he had root permissions. His only option is to unbrick, which is fortuitous in a way because it will allow him to install a proper recovery that can prevent this from happening in the future.
I just did the same thing, only I deleted Google Play Books. Holy **** is this ROM ever loaded with useless crap.
Press Volume Up + insert USB cable to access download mode. You should be able to unbrick using this.
Instead of using titanium backup to uninstall the bloatware... you need to freeze it (requires titanium backup pro)
Malnilion said:
He deleted SystemUI.apk. Even if that didn't trigger LG's secure boot error, it would be in an endless bootloop that only *might* be recoverable if adb still managed to function and he had root permissions. His only option is to unbrick, which is fortuitous in a way because it will allow him to install a proper recovery that can prevent this from happening in the future.
Click to expand...
Click to collapse
Yeah I misread what he said. I thought he meant he only "disabled" it.
Warrimonk said:
I just did the same thing, only I deleted Google Play Books. Holy **** is this ROM ever loaded with useless crap.
Press Volume Up + insert USB cable to access download mode. You should be able to unbrick using this.
Instead of using titanium backup to uninstall the bloatware... you need to freeze it (requires titanium backup pro)
Click to expand...
Click to collapse
Can't you just disable all the bloatware applications using Google's built-in method? You don't even need root to do that. And it's safer than using apps like Titanium Backup which will actually modify the system partition.
This is assuming LG hasn't removed the ability to disable apps.
Then again, I'm not sure what Google's method does. I assume it doesn't modify the system partition directly but I am not sure.
drumist said:
Can't you just disable all the bloatware applications using Google's built-in method? You don't even need root to do that. And it's safer than using apps like Titanium Backup which will actually modify the system partition.
This is assuming LG hasn't removed the ability to disable apps.
Then again, I'm not sure what Google's method does. I assume it doesn't modify the system partition directly but I am not sure.
Click to expand...
Click to collapse
What method are you talking about? Hiding an app in the app tray? It does not exist in this version... and the built in lg "App manager" only lets you remove a single app... leaves a lot more junk untouched.
Warrimonk said:
What method are you talking about? Hiding an app in the app tray? It does not exist in this version... and the built in lg "App manager" only lets you remove a single app... leaves a lot more junk untouched.
Click to expand...
Click to collapse
I'm talking about going to System settings > Apps > Select a preloaded app > click Disable. If the app has been updated, you have to do "Uninstall updates" first for it to show up.
I don't know if LG has changed how this all works though.
I was worried i was going to have to do that. I have no idea what i am supposed to do. That whole process has me lost. Do you think it is possible to bring it in to a local repair shop and maybe they can do it? I just don't want to mess it up anymore then it is.
Ethanp said:
I was worried i was going to have to do that. I have no idea what i am supposed to do. That whole process has me lost. Do you think it is possible to bring it in to a local repair shop and maybe they can do it? I just don't want to mess it up anymore then it is.
Click to expand...
Click to collapse
I just unbricked it following this guide http://forum.xda-developers.com/showthread.php?t=1784709
Just follow the steps carefully.
Have you tried running the Bell ICS installer again while the phone is in download mode? (To get to download mode, turn phone completely off, then hold down volume up button while inserting the USB cable. Don't press power button; phone should turn itself on.)
I think that's all you need to do to get it back up and working.
drumist said:
Have you tried running the Bell ICS installer again while the phone is in download mode? (To get to download mode, turn phone completely off, then hold down volume up button while inserting the USB cable. Don't press power button; phone should turn itself on.)
I think that's all you need to do to get it back up and working.
Click to expand...
Click to collapse
Are you talking about installing the .kdz file through LG tools? I have downloaded the official Bell ICS release from HO!NO!'s thread but don't know how to install it. I try updating through LG tools but it says i am already up to date. Is there a way i can force an update?
Ethanp said:
Are you talking about installing the .kdz file through LG tools? I have downloaded the official Bell ICS release from HO!NO!'s thread but don't know how to install it. I try updating through LG tools but it says i am already up to date. Is there a way i can force an update?
Click to expand...
Click to collapse
Ah, I figured I was forgetting something. LG's tools are frustrating. I don't really see the point in preventing you from reflashing a ROM.
Yes, you can force it -- that's actually what the unbricking guide does, basically. So I guess you will have to follow the unbricking guide process, except use the Bell ICS KDZ file when doing it (and stop after you finish flashing the KDZ). The KDZ can be downloaded here: http://forum.xda-developers.com/showpost.php?p=30177420&postcount=1
drumist said:
Ah, I figured I was forgetting something. LG's tools are frustrating. I don't really see the point in preventing you from reflashing a ROM.
Yes, you can force it -- that's actually what the unbricking guide does, basically. So I guess you will have to follow the unbricking guide process, except use the Bell ICS KDZ file when doing it (and stop after you finish flashing the KDZ). The KDZ can be downloaded here: http://forum.xda-developers.com/showpost.php?p=30177420&postcount=1
Click to expand...
Click to collapse
Alright so i attempted the unbricking process, something strange happened. My phone left download mode the home back and menu buttons flashed my computer recognized it and then it shut off. Now it won't turn on or go into download mode or recognize I'm charging it. Noting just a black screen.
Ethanp said:
Alright so i attempted the unbricking process, something strange happened. My phone left download mode the home back and menu buttons flashed my computer recognized it and then it shut off. Now it won't turn on or go into download mode or recognize I'm charging it. Noting just a black screen.
Click to expand...
Click to collapse
Pull the battery out, plug it back in, and see if you can get to download mode again.
drumist said:
Pull the battery out, plug it back in, and see if you can get to download mode again.
Click to expand...
Click to collapse
Tried that and nothing happened. I'm just assuming that the battery is dead because normally (correct me if I'm wrong) when the three buttons flash it means your battery is dead. And I have been doing some research and it seems that the phone will not charge in download mode. So I have it plugged into the wall to see if it powers up (taking an awful long time though).
Warrimonk said:
I just did the same thing, only I deleted Google Play Books. Holy **** is this ROM ever loaded with useless crap.
Press Volume Up + insert USB cable to access download mode. You should be able to unbrick using this.
Instead of using titanium backup to uninstall the bloatware... you need to freeze it (requires titanium backup pro)
Click to expand...
Click to collapse
I agree the ROM is filled with tons of bloatware. What a frustrating process. Waited so long for the update and not even 24 hours with it and this happens lol.
Ethanp said:
Tried that and nothing happened. I'm just assuming that the battery is dead because normally (correct me if I'm wrong) when the three buttons flash it means your battery is dead. And I have been doing some research and it seems that the phone will not charge in download mode. So I have it plugged into the wall to see if it powers up (taking an awful long time though).
Click to expand...
Click to collapse
Yeah, I've never let my phone get that low, but supposedly it takes a while for it to get high enough to stop doing that. I'd let it charge for a few hours to make sure it's high enough to not die on you again.
I just upgraded to Bell ICS ,but when the upgrade finished, my phone displayed the LG logo (like it would when you turn on the phone) for an hour......
not sure what to do as i have left the phone for a long time and nothing has happened, any suggestions??
Thanks for all the solutions from everyone. After many hours i have successfully "unbricked" my Optimus. My phone would not charge for 3+ hours and eventually got completely stuck in download mode. But I ran windows enabler and small server and after 50 or so tries the kdz update tool finally took my phone and updated it to the point prior to bricking.
My capacitive keys don't work. I've rooted and unlocked, but they didn't work before either. Even the app I installed puts keys on the bottom of the screen, and they don't work. I have show touches enabled, and the cursor shows up above the keys.
Trying to press back or view log in TWRP doesn't work either. I tried searching but didn't find anything...
Help! The phone is Rev.D. I can't install a custom ROM either.
EDIT1 Also, Secure Boot shows enabled in Fastboot, bootloader is unlocked.
EDIT2 Could this be solved by updating to OTA 4.1?
If the capacitive keys didnt work before rooting and unlocking, I would have returned/ exchanged the device.
chevro1et said:
If the capacitive keys didnt work before rooting and unlocking, I would have returned/ exchanged the device.
Click to expand...
Click to collapse
Well the thing isn't even booting now. Might get an RMA after all.
It usually won't even turn on, but sometimes I can get an LG logo on the screen, but it quickly goes to black...
Aha! It booted (into fastboot at least)! Now I just have to find the util to flash it back to stock and I'll return it.
SECURE BOOT - enabled
LOCK STATE - unlocked
I'm guessing I have to re-lock the bootloader. Can I do that in TWRP?
EDIT:
Aaaarg! It will sometimes get to fastboot, but never into recovery or ROM. Looks like I have to take my chances just sending it back...
EDIT2:
Could the lack of booting be because I screwed up some process in the unlocking? I had used freegee and it unlocked just fine, but getting into TWRP was flaky. The last hack I tried to do was restore the locked bootloader, and after that it even booted once. But after that, black screen, I don't get a battery charging icon when I plug in USB...
It's getting sent back to Rogers now. Just got off the line with tech support. Here's hoping the next one is fully functional.
Re: [Q] Capacitive keys & on screen keys not working
sunami88 said:
Aha! It booted (into fastboot at least)! Now I just have to find the util to flash it back to stock and I'll return it.
SECURE BOOT - enabled
LOCK STATE - unlocked
I'm guessing I have to re-lock the bootloader. Can I do that in TWRP?
EDIT:
Aaaarg! It will sometimes get to fastboot, but never into recovery or ROM. Looks like I have to take my chances just sending it back...
EDIT2:
Could the lack of booting be because I screwed up some process in the unlocking? I had used freegee and it unlocked just fine, but getting into TWRP was flaky. The last hack I tried to do was restore the locked bootloader, and after that it even booted once. But after that, black screen, I don't get a battery charging icon when I plug in USB...
It's getting sent back to Rogers now. Just got off the line with tech support. Here's hoping the next one is fully functional.
Click to expand...
Click to collapse
Use CWM on the next one. TWRP is junk on this phone. But only because CWM is getting more attention at the moment.
LG Optimus G E971
Elisha said:
Use CWM on the next one. TWRP is junk on this phone. But only because CWM is getting more attention at the moment.
LG Optimus G E971
Click to expand...
Click to collapse
Will do, thanks. It's too bad, I like the way TWRP looks (on my old phone it's just as reliable as CWM).
I can't stand the wait! I get the phone and it's a lemon! Ah well, few more days and I'll have another one to break .
Re: [Q] Capacitive keys & on screen keys not working
sunami88 said:
Will do, thanks. It's too bad, I like the way TWRP looks (on my old phone it's just as reliable as CWM).
I can't stand the wait! I get the phone and it's a lemon! Ah well, few more days and I'll have another one to break .
Click to expand...
Click to collapse
Are they sending you a new online or refurbished?
LG Optimus G E971
Elisha said:
Are they sending you a new online or refurbished?
LG Optimus G E971
Click to expand...
Click to collapse
Not sure, not going to argue at this point (I think the bootloader is unlocked). Probably refurbished as I called in.
Thirds happened to me. Had it for 3 weeks, lower left part of screen started going goofy and then "back" arrow capacitive key stopped functioning. Had to get exchange.
Sent from my LG-E970 using xda app-developers app
So for what it's worth I got the phone back to a bootable state. Used KDZ, "adb shell wipe data", and now I think it's back to fully stock for return.
Also, Button Savior is amazing. Should have the new phone tomorrow!
Done everything right (rooting/ unlocking phone), i've gotten up to the point of 'unlocking' my phone. but i don't have the use of my volume key because they were accidently damaged in the attempt to fix my phone not bothered to go into it.... but yeah as i've said i don't have the use of my volume keys so when im prompted for the use of these keys to select yes or no for 'unlocking my phone' it already is highlighted on 'NO' so i have no choice but to select that thus unable to unlock my phone..... such as simple defect with a great cause for me to be unable to root my device
Now my question is...
is it possible for some other method instead of using my volume keys to select yes or no in the bootloader menu to unlock my phone?
(at the moment the only key that works is the sleep button on the phone)
My device: Samsung galaxy nexus
Root method: nexus root toolkit v1.6.3
No you can't
Sent from my Galaxy Nexus using Tapatalk 2
Can you drive without a gas pedal?
Sarcasm at its finest
Fred Flintstone could
Sent from my Galaxy Nexus using Tapatalk 2
yeah there are two ways
1 First turn off phone, take off back cover, take out battery, see all the little screws? unscrew them and take apart the phone until you reach the volume rockers, see whats wrong. most likely there in wrong shape (should go into it more, if water damage then skip this way)
Idoubt this will work but give it a shot
2 sell your phone buy a new one
Jack Jake said:
yeah there are two ways
1 First turn off phone, take off back cover, take out battery, see all the little screws? unscrew them and take apart the phone until you reach the volume rockers, see whats wrong. most likely there in wrong shape (should go into it more, if water damage then skip this way)
Idoubt this will work but give it a shot
2 sell your phone buy a new one
Click to expand...
Click to collapse
Ahaahhaah yeah was the reason i messed it up in the first place... idoono ill mess aorund with the volume keys again just never was bothered with puting them back in the right spotn because it ripped off and i had no clue where it went but yeah ill try fixing it again
lolpeople345 said:
Done everything right (rooting/ unlocking phone), i've gotten up to the point of 'unlocking' my phone. but i don't have the use of my volume key because they were accidently damaged in the attempt to fix my phone not bothered to go into it.... but yeah as i've said i don't have the use of my volume keys so when im prompted for the use of these keys to select yes or no for 'unlocking my phone' it already is highlighted on 'NO' so i have no choice but to select that thus unable to unlock my phone..... such as simple defect with a great cause for me to be unable to root my device
Now my question is...
is it possible for some other method instead of using my volume keys to select yes or no in the bootloader menu to unlock my phone?
(at the moment the only key that works is the sleep button on the phone)
My device: Samsung galaxy nexus
Root method: nexus root toolkit v1.6.3
Click to expand...
Click to collapse
Maybe I do not understand really well why you need volume keys for unlocking phone, but you can reboot to recovery via pc, or from Rom, as well as you can unroot phone by using wugs tool for example(no need for hw keys).
You can then try to use twrp recovery as there is no need for hw keys, because twrp fully uses touch screen.
Hope this could help you.
greetings from tapatalk
standa75 said:
Maybe I do not understand really well why you need volume keys for unlocking phone, but you can reboot to recovery via pc, or from Rom, as well as you can unroot phone by using wugs tool for example(no need for hw keys).
You can then try to use twrp recovery as there is no need for hw keys, because twrp fully uses touch screen.
Hope this could help you.
greetings from tapatalk
Click to expand...
Click to collapse
That solves precisely nothing. He needs volume keys to unlock the boot loader.
There seems to be two ways: One is if he's on earlier versions of 4.x.x, root via adb backup restore exploit.
The second is via dd.. BOTH REQUIRE ROOT FIRST. I'd follow the best advice which is to fix those volume buttons or get rid of the phone.
063_XOBX said:
That solves precisely nothing. He needs volume keys to unlock the boot loader.
Click to expand...
Click to collapse
Well, boot loader could be unlocked via PC by using wugs application...no need to even touch the phone.
standa75 said:
Well, boot loader could be unlocked via PC by using wugs application...no need to even touch the phone.
Click to expand...
Click to collapse
narh thats the application i used.... once you get up to unlocking the phone you have to use volume keys unless im missing something/// any way i pulled apart my phone and long story short ****ed my phone aahah... but bought a dirt cheap nexus of ebay with cracked screen so im going to use the old screen of my phone which was mint
lolpeople345 said:
narh thats the application i used.... once you get up to unlocking the phone you have to use volume keys unless im missing something/// any way i pulled apart my phone and long story short ****ed my phone aahah... but bought a dirt cheap nexus of ebay with cracked screen so im going to use the old screen of my phone which was mint
Click to expand...
Click to collapse
So you have it already solved Did you use latest wugs app(1.6.3)? I usually flash stock+unroot. Then flash custom recovery, i.e. TWRP and there is no need to use volume keys as far as i remember. Access to recovery could be then possible from wugs by reboot into recovery if needed.
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
As the title goes I'm wondering if there is a counter which is triggered when root and can not be reversed when unroot.
Its the only thing that stops me (and I suppose I'm not the only one) from rooting in order to debloat & freeze some stuff.
pagegr said:
As the title goes I'm wondering if there is a counter which is triggered when root and can not be reversed when unroot.
Its the only thing that stops me (and I suppose I'm not the only one) from rooting in order to debloat & freeze some stuff.
Click to expand...
Click to collapse
Can root and unroot without issue on this device, no counter that I am aware of. I have gone back to Stock a couple of times now.
Thank you for your answer.
The thing is that I worry for any future update (international D855 is my variant). What / if we realize then that actually there is a counter.
I know it sounds as metaphysics but its just pure ignorance on my behalf.
Go to dialer and digit 3845#*855#, tap to "LG RCT", tap "display Result...this is root counter.
pagegr said:
Thank you for your answer.
The thing is that I worry for any future update (international D855 is my variant). What / if we realize then that actually there is a counter.
I know it sounds as metaphysics but its just pure ignorance on my behalf.
Click to expand...
Click to collapse
There isn't a binary count like on Samsung phones ,at least I haven't seen one yet.
Sent from my LG-D850 using XDA Premium 4 mobile app
roma1927 said:
Go to dialer and digit 3845#*855#, tap to "LG RCT", tap "display Result...this is root counter.
Click to expand...
Click to collapse
If so, this counter goes back to default value when unroot or showing something that means the phone had been rooted?
pagegr said:
If so, this counter goes back to default value when unroot or showing something that means the phone had been rooted?
Click to expand...
Click to collapse
On the G2 was always, even after a hard reset or reflashing the firmware. I do not know the G3...i did not root.
Thanks for the code (it seems very helpful): my display result is "Not rooted".
Now that we have an anchor we need the same info from a G3 user who unroot or went back to stock...
Hey,
I entered the 845#*855# code and now im in the hidden menu but I'm stuck there?
The phone is very slow and doesn't respond to anything I do. I even unplugged the batteries for a few minutes but it always boots up in the AAT mini OS 3.1 hidden menu.
When I press Normal Boot (+power) or any other options nothing happend but only red crosshairs appear?
How can I reset my phone now???
I tapped the code but nothing like that happened. After I check for root I just went back & and back again on my dial.
Is your phone a 855 (as in the hidden menu) or a 400 variant?
Other than that I can't think of.
digit 855 for european model, 400 for the Corea
---------- Post added at 06:47 PM ---------- Previous post was at 06:35 PM ----------
pagegr said:
Thanks for the code (it seems very helpful): my display result is "Not rooted".
Now that we have an anchor we need the same info from a G3 user who unroot or went back to stock...
Click to expand...
Click to collapse
Probably if you run root with Geohot app the counter does not write rooted or reset after hard reset...i do not know...on the Galaxy S5 with Geohot app the Knox contour does not advance.
Thanks for the reply. It would be good to have an answer from an owner who rooted already - better still if returned to stock for some reason.
I'll wait for a while before I try it myself reading about the two alternatives for rooting I came across in this forum.
pagegr said:
Thanks for the reply. It would be good to have an answer from an owner who rooted already - better still if returned to stock for some reason.
I'll wait for a while before I try it myself reading about the two alternatives for rooting I came across in this forum.
Click to expand...
Click to collapse
It doesn't change it when you go back to stock. I had performed a factory reset and it still shows the time and date of my first root.
hdcp said:
It doesn't change it when you go back to stock. I had performed a factory reset and it still shows the time and date of my first root.
Click to expand...
Click to collapse
Did you unroot via su? You could try to reflash a factory image.
Sent from my LG-D850 using XDA Premium 4 mobile app
Anyone - who root (towelroot or IOroot) and for any reason unroot and/or restored back to stock?
hdcp said:
It doesn't change it when you go back to stock. I had performed a factory reset and it still shows the time and date of my first root.
Click to expand...
Click to collapse
Which method did you use to go back to stock?
Sorry for the intervention, may I ask if your question means that the method you proposed to unroot can change also the result in the hidden menu concerning root?
Still searching & reading...
Schumi2004 said:
Hey,
I entered the 845#*855# code and now im in the hidden menu but I'm stuck there?
The phone is very slow and doesn't respond to anything I do. I even unplugged the batteries for a few minutes but it always boots up in the AAT mini OS 3.1 hidden menu.
When I press Normal Boot (+power) or any other options nothing happend but only red crosshairs appear?
How can I reset my phone now???
Click to expand...
Click to collapse
Same problem here.. Any solution to boot the phone normally?
pagegr said:
Anyone - who root (towelroot or IOroot) and for any reason unroot and/or restored back to stock?
Click to expand...
Click to collapse
SeptimiuB said:
Same problem here.. Any solution to boot the phone normally?
Click to expand...
Click to collapse
only way around seams a complete restore try doing this
I don't have the links to the tread where I got these from but lets just hope I don't get banned.
1) go to download mode
2) install this and download the correct .kdz file for your phone
-Modelnumber is ...
-serial number is your imei number
- wait until the download is done
3) run the lgflashtool2014.exe from this zip
-Select type= cdma
-phone mode= Diag
-reset time=33000
-Should be like this when You run it
-select kdz file= is where you need to find the kdz file you just downloaded(step 1)
-then press cse flash
-in the now pop-up window select start
-select your language
-ignore error (cannot connect to lg server)
-check progress on phone up to 100% then boots in recovery installs and restarts
-wait untill it goes to the welcom screen then you can unplug
-now the most inportant step Like my post
to enter download mode do this:
--You must switch off the device to start the process.
--Then press and hold the “Volume Up” and connect the USB cable from phone to PC.
--Use the original USB cable. Because, other device’s cable may not be detected in the Computer. So, only we recommend it to use the original-- one that you got it when you bought the phone.
--Wait for the driver installation on PC.
--Then you will get the download mode screen in your phone.
--That’s it.
SeptimiuB said:
Same problem here.. Any solution to boot the phone normally?
Click to expand...
Click to collapse
I got stuck on the miniOS crap and figured it out. Just search for my posts and you'll stumble across the thread I made for it. Very easy and yeah hit thanks ?
Sent from my LG-D855 using XDA Free mobile app