Anyway to fix that or am I boned?
What did you do before this? Is this after the official AT&T OTA?
Edit: What he said^^^^^
Sent from my MB860 using XDA Premium App
infinite01 said:
Anyway to fix that or am I boned?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ya I read some articles that flashing it after the gingerbread update does that... after I did it. But ya I got it after trying to flash back to the 1.2.6 update, just got unlucky I guess. I plan on going to AT&T store today and telling them it was the gingerbread update.
infinite01 said:
Anyway to fix that or am I boned?
Click to expand...
Click to collapse
What did you do?
Which version were you on, and which version were you flashing to?
What mods had you done to your phone?
0x1000 is what people get with hard brick:
http://forum.xda-developers.com/showthread.php?t=1165154
Like I said above, basically I had just got the Gingerbread update, but my fingerprint scanner hadn't been working, figured a flash might fix that but I knew the new update was coming out so I thought, if i'm lucky that will fix it, it didn't so I flashed it to 1.2.6, (and it was the same SBF I've used a few times before so i don't think it was that) and it said the flash failed and i got that wonderful hard brick screen.
infinite01 said:
Like I said above, basically I had just got the Gingerbread update, but my fingerprint scanner hadn't been working, figured a flash might fix that but I knew the new update was coming out so I thought, if i'm lucky that will fix it, it didn't so I flashed it to 1.2.6, (and it was the same SBF I've used a few times before so i don't think it was that) and it said the flash failed and i got that wonderful hard brick screen.
Click to expand...
Click to collapse
Yup, that sounds like what bricks everyone else. Never flash backwards after the OTA.
Well I've done it before a few times and there was never a problem, I've looked online and it appears this is specifically a bug with there Gingerbread update. I'm wondering what there policy on this is, I mean if i don't tell them about the flashing, just there update bricked it. I've had a phone go bad before and they sent me a replacement.
infinite01 said:
Like I said above, basically I had just got the Gingerbread update, but my fingerprint scanner hadn't been working, figured a flash might fix that but I knew the new update was coming out so I thought, if i'm lucky that will fix it, it didn't so I flashed it to 1.2.6, (and it was the same SBF I've used a few times before so i don't think it was that) and it said the flash failed and i got that wonderful hard brick screen.
Click to expand...
Click to collapse
Hard brick. You cannot flash back after doing the OTA 4.5.91 upgrade.
You could while on Froyo (2.2.*), but those were updates (4.1.26, 4.1.57, 4.1.83) and not upgrades, which the flash to GB is. AT&T made it so you cannot flash back to an earlier Android version with this upgrade.
See my link in post #6.
infinite01 said:
Well I've done it before a few times and there was never a problem, I've looked online and it appears this is specifically a bug with there Gingerbread update. I'm wondering what there policy on this is, I mean if i don't tell them about the flashing, just there update bricked it. I've had a phone go bad before and they sent me a replacement.
Click to expand...
Click to collapse
You had done it before while on Froyo. That's why you had no problems. I have not flashed the OTA, but I imagine/assume (I know, never assume) that there was probably a warning before installation telling you you could not flash back. If there was not, you could argue they never told you that you could not flash back after upgrading.
Well thanks for the knowledge i'm going to go to the store now I'll keep ya'll up to date for future reference
Also see here ----> http://forum.xda-developers.com/showthread.php?t=1160408
CaelanT said:
Also see here ----> http://forum.xda-developers.com/showthread.php?t=1160408
Click to expand...
Click to collapse
Wow.......I almost feel bad for Motorola that many of these bricks aren't their fault and is a prime example of why they didn't want to unlock the bootloader for us and for why RSD was never meant for us. Would be nice if people would do a little more research before just jumping in with both feet. They were nice and gave us the means to unlock, the least we could do is to take responsibility for if we screw up our phones.
I spend hours on this tread to avoid bricks at all costs.
Honestly i could careless for the unlocked bootloader, didn't even want root except for 3rd party app support, and either way I would have went to get a new phone bricked or not, the fingerprint scanner was defective, but as of now the phone was under warranty so either of the issues would have warranted me a new or refurbished phone, which I now have after about an hour of waiting. I've never flashed my phone unless the problem that i was trying to fix would otherwise have me seek a phone replacement anyways, so i wouldn't feel bad for Motorola when I'm getting a replacement for faulty software/hardware.
infinite01 said:
Honestly i could careless for the unlocked bootloader, didn't even want root except for 3rd party app support, and either way I would have went to get a new phone bricked or not, the fingerprint scanner was defective, but as of now the phone was under warranty so either of the issues would have warranted me a new or refurbished phone, which I now have after about an hour of waiting. I've never flashed my phone unless the problem that i was trying to fix would otherwise have me seek a phone replacement anyways, so i wouldn't feel bad for Motorola when I'm getting a replacement for faulty software/hardware.
Click to expand...
Click to collapse
In your case, that is probably true. Reading through the treads lately, my comment was more towards all of the people that didn't take the time to read before they start flashing. Many of the bricks aren't necessarily due to Motorola update, but that people are trying to flash back after.
Gr8Danes said:
In your case, that is probably true. Reading through the treads lately, my comment was more towards all of the people that didn't take the time to read before they start flashing. Many of the bricks aren't necessarily due to Motorola update, but that people are trying to flash back after.
Click to expand...
Click to collapse
i also dont understand why people keep flashing back to froyo after flashing GB. the build is very stable and doesnt have any serious issues.
neotekz said:
i also dont understand why people keep flashing back to froyo after flashing GB. the build is very stable and doesnt have any serious issues.
Click to expand...
Click to collapse
I 2nd that thought.
Like I said I did it to see if I can't get the scanner to work again, but after using it a little I'm finding it a lot slower than froyo
Related
I hoping that someone may be able to help me with this… I recently rooted my note via instructions here and installed CWM and TiBu. So far so good!
I began freezing some of the bloat and then found this post to see what else I could freeze. This is were things went wrong… I guess that I may have frozen something that I shouldn’t have because my home button stopped responding and then the back button took me to a black screen.
At this point I thought that my phone was nearly bricked, so I downloaded the firmware from SamMobile and flashed it. Still have a black screen, but I received a text and pop-up through chomp which let me know that my phone was still alive! I installed Go Launcher and can now can use my phone as 'normal'. However, I no longer have root according to TiBu, CWM and the like. I can still boot into download and recovery modes.
I found this thread, but it didn’t do much for me.
How’s that for an introductory post?!!
:cheers:
CivilE
CivilE said:
I hoping that someone may be able to help me with this… I recently rooted my note via instructions here and installed CWM and TiBu. So far so good!
I began freezing some of the bloat and then found this post to see what else I could freeze. This is were things went wrong… I guess that I may have frozen something that I shouldn’t have because my home button stopped responding and then the back button took me to a black screen.
At this point I thought that my phone was nearly bricked, so I downloaded the firmware from SamMobile and flashed it. Still have a black screen, but I received a text and pop-up through chomp which let me know that my phone was still alive! I installed Go Launcher and can now can use my phone as 'normal'. However, I no longer have root according to TiBu, CWM and the like. I can still boot into download and recovery modes.
I found this thread, but it didn’t do much for me.
How’s that for an introductory post?!!
:cheers:
CivilE
Click to expand...
Click to collapse
Did you have ICS or GB ? BTW all the tools you needed are right here in XDA GNote threads.
http://forum.xda-developers.com/showthread.php?t=1740367
bigjoe2675 said:
Did you have ICS or GB ? BTW all the tools you needed are right here in XDA GNote threads.
http://forum.xda-developers.com/showthread.php?t=1740367
Click to expand...
Click to collapse
ICS. I've seen all of the tools in that thread, but not sure if I need the screwdriver or the hammer to 'get my root back' in this situation. Ultimately I'd like to be able to do it without having to do a full wipe/recovery.
Freezing an app will not brick your phone...
and in this case....you did not need to flash a new firmware. you could have simply pulled the battery, then put it in and booted to recovery to restore a backup.
but of course, the new firmware did break root....
bigjoe is right on the links info. it has all you need to start again.....and I "would" re-root using the odin CWM flash method......
In the general section, under the "galaxy note everything" thread.
All you need is there....g
CivilE said:
ICS. I've seen all of the tools in that thread, but not sure if I need the screwdriver or the hammer to 'get my root back' in this situation. Ultimately I'd like to be able to do it without having to do a full wipe/recovery.
Click to expand...
Click to collapse
Follow the big green arrow for ics rooting (btw if you miss it, do not root)....can i get a Hoot for the Root!
Hammer> CWM install via odin...no wiping
Nail> super user flash with no wiping for Root
Good to go...
gregsarg said:
Freezing an app will not brick your phone...
and in this case....you did not need to flash a new firmware. you could have simply pulled the battery, then put it in and booted to recovery to restore a backup.
but of course, the new firmware did break root....
bigjoe is right on the links info. it has all you need to start again.....and I "would" re-root using the odin CWM flash method......
In the general section, under the "galaxy note everything" thread.
All you need is there....g
Click to expand...
Click to collapse
+100
H--o--o--t !!!!
Bigjoe for moderator !!!
Good to go!! Apparently twlauncher was inadvertently frozen which explains the black screen. Had I realized what the problem was, yes a simple recover from backup might have fixed it.
So tell me this, as I am still learning here... What is the difference in the method in bigjoe's thread vs trying to re-root my phone by the method I used previously? Whenever I tried to install SU after the original method I used, I would get a failed signature error. No problems with using bigjoe's recommendations.
:cheers:
CivilE
bigjoe2675 said:
Follow the big green arrow for ics rooting (btw if you miss it, do not root)....can i get a Hoot for the Root!
Hammer> CWM install via odin...no wiping
Nail> super user flash with no wiping for Root
Good to go...
Click to expand...
Click to collapse
I see what you did there
CivilE said:
Good to go!! Apparently twlauncher was inadvertently frozen which explains the black screen. Had I realized what the problem was, yes a simple recover from backup might have fixed it.
So tell me this, as I am still learning here... What is the difference in the method in bigjoe's thread vs trying to re-root my phone by the method I used previously? Whenever I tried to install SU after the original method I used, I would get a failed signature error. No problems with using bigjoe's recommendations.
:cheers:
CivilE
I see what you did there
Click to expand...
Click to collapse
The difference is ....bigjoe is a god among men, and probably led the Crusades in a previous life.
I'm quite certain he drank beer with Khan and Hun. Now ignore those historical timelines because bigjoe was there ...period !!
Those things, combined with the fact that he invented the first telephone, make him knowledgeable in all things android and beyond ....so take his word for it ...
And ..after every post ..please use the phrase ....." BIGJOE FOR MODERATOR"....
While it isn't the Crusades over again, he certainly deserves to be one.
After all ...he did invent the telephone for cryin out loud .....LOL
Bigjoe for moderator !!!!!.......H...O....O...T !!!
gregsarg said:
The difference is ....bigjoe is a god among men, and probably led the Crusades in a previous life.
I'm quite certain he drank beer with Khan and Hun. Now ignore those historical timelines because bigjoe was there ...period !!
Those things, combined with the fact that he invented the first telephone, make him knowledgeable in all things android and beyond ....so take his word for it ...
And ..after every post ..please use the phrase ....." BIGJOE FOR MODERATOR"....
While it isn't the Crusades over again, he certainly deserves to be one.
After all ...he did invent the telephone for cryin out loud .....LOL
Bigjoe for moderator !!!!!.......H...O....O...T !!!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hi
i was tryingto back to stock with odin file I777UCKH7 OCD With Root
i get FAIL! on odin.
now the phone shows GT-I9100 and doesnt boot
i used
I777UCKH7-CL503881-No-BL
and
I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar
PLEASE HELP!!
More information is needed before we can suggest anything that would help. Start by telling us everything about your phone, what it was running, why you were going back to stock, etc.
creepyncrawly said:
More information is needed before we can suggest anything that would help. Start by telling us everything about your phone, what it was running, why you were going back to stock, etc.
Click to expand...
Click to collapse
i was trying to root my phone the superuser apk was installed but dont work. so i decided to back to stock to sell the phone later. now the phone has a yellow triangle and doesnt work.
killar777 said:
hi
i was tryingto back to stock with odin file I777UCKH7 OCD With Root
i get FAIL! on odin. now the phone shows GT-I9100 and doesnt boot
i used I777UCKH7-CL503881-No-BL and I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar
Click to expand...
Click to collapse
killar777 said:
i was trying to root my phone the superuser apk was installed but dont work. so i decided to back to stock to sell the phone later. now the phone has a yellow triangle and doesnt work.
Click to expand...
Click to collapse
Maybe you think we can just look into a crystal ball and divine what is wrong with your phone and how to fix it? No, we need more information. So, since you can't think what information to provide, I'll ask specific questions. You will need to answer these questions completely and thoroughly. (I hope you will, as you did not answer very much of the questions I posed in my last response.)
So lets start with those:
1. Tell us everything about your phone. How long have you had it? Did you buy it new or are you the second owner? What operating system was it running before you started the process that caused your question? I assume this means what operating system was on the phone when you tried to root? One would assume that since it wasn't rooted, it had been stock? Was it working normally before you tried to root?
2. What exactly did you use to try to root the phone? What method did you use, or specifically what did you flash to achieve root? You didn't get the yellow warning triangle from flashing stock, so it must have occurred when you tried to root.
Let's start with that. If I need more after you answer these, I'll ask.
creepyncrawly said:
Maybe you think we can just look into a crystal ball and divine what is wrong with your phone and how to fix it? No, we need more information. So, since you can't think what information to provide, I'll ask specific questions. You will need to answer these questions completely and thoroughly. (I hope you will, as you did not answer very much of the questions I posed in my last response.)
So lets start with those:
1. Tell us everything about your phone. How long have you had it? Did you buy it new or are you the second owner? What operating system was it running before you started the process that caused your question? I assume this means what operating system was on the phone when you tried to root? One would assume that since it wasn't rooted, it had been stock? Was it working normally before you tried to root?
2. What exactly did you use to try to root the phone? What method did you use, or specifically what did you flash to achieve root? You didn't get the yellow warning triangle from flashing stock, so it must have occurred when you tried to root.
Let's start with that. If I need more after you answer these, I'll ask.
Click to expand...
Click to collapse
omg im sorry..
1- i bougt this phone new. have 4 months. it was on android 4.0.2. i try to root the phone use SuperOneClick. and yes the phone was on a stock rom. was working normally.
2- i used SuperOneClick root. doesnt work so i downloaded I777UCKH7 Return/Unbrick to Stock (or Root) Odin3 One-Click Downloaders.
now no matter what rom i download, odin allways says FAIL!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Am I correct in assuming that after you first tried SuperOneClick, the phone was able to boot normally? I am guessing you were able to boot the phone or you wouldn't know that superuser.apk was installed.
And how did you know that the root didn't work?
I'm not sure exactly what SuperOneClick does, but I don't think it will work with stock 4.0.2.
By the way, since the S4 was released, a lot of people have left the I777 forums so I don't know if you'll find anyone else to help besides myself. I'll try to check on this thread as often as I can, but you may have to wait hours between messages.
Edit: Oh and have you tried to boot into recovery. If not, try it now. Hold down vol- vol+ and pwr continuously for at least two initial boot screens. And if you by some chance can enter recovery, I'll need to know that information.
Alright listen, you're gonna be fine.
You really dodged a bullet as your phone is SOFT BRICKED.
This is easily fixed, the phone I'm typing this with had the same issue.
First, get into download mode and make sure your battery is out, this is often looked over. As long as your battery is out before odining you're fine.
Now using ODIN I'd flash an official ROM from the Samsung site. Get that tar/md5 file and hook it up to PDA. Start the flash.
If it fails flashing try it AGAIN.
If it fails IMMEDIATELY then try a different ROM.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
ok guys thank you very much for your time and your patience.
i try to flash the stock rom on another computer and.... BOOM!! the phone is working again. :laugh: :victory:
thank you!
Hello All,
Looks like I got myself into a pickle with my DNA......
Right now the only two things I can access on the phone are the bootloader and CWM.
How I got here:
I went into CWM recovery and deleted/formatted everything (absolutely everything that could be deleted and/or formatted), thinking I could flash a radio/firmware upgrade, then the LiquidSmooth rom from adb/fastboot. Been a long time since I've worked with this phone and now all I got is the bootloader and CWM. Thought I could use adb to push the rom zip to the device, then go into recovery and flash it the right way, but when I go to fastboot on the device and use the push command in adb it tells me "error device not found".
Gonna stop right there and seek some advice. What's the best way to correct this mess?
Thanks ahead of time!
PS: Working with a DNA with an unlocked bootloader (S-ON), and it was running the stock rom before the first OTA update. I did make a backup file and save it to my PC before I did anything. But, now adb is suddenly not recognizing that the device is connected so I can't push any files to it.
http://forum.xda-developers.com/showthread.php?t=2632351
HTC DNA
LG Optimus G
d08speed3 said:
http://forum.xda-developers.com/showthread.php?t=2632351
HTC DNA
LG Optimus G
Click to expand...
Click to collapse
Not real sure how this will help me.
I cannot boot into Android, and at this point whenever I try to push files to the device via adb it gives me an error and says device not found.
Tried to sideload in recovery?
RLGL said:
Tried to sideload in recovery?
Click to expand...
Click to collapse
Hmmm, I have not. Wasn't familiar with the term until now.
Actually just tried it and thought I was out of the woods. LiquidSmooth started to install, then failed/aborted. Here is a screen shot if someone can tell me what they can make of it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hackenstein said:
Hmmm, I have not. Wasn't familiar with the term until now.
Actually just tried it and thought I was out of the woods. LiquidSmooth started to install, then failed/aborted. Here is a screen shot if someone can tell me what they can make of it:
Click to expand...
Click to collapse
The problem with that turned out to be an outdated version of CWM. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade I also needed a driver upgrade which I took care of (after I had installed TWRP to test as well, just stuck with TWRP). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When I'm done there, should I run firewater to achieve S-OFF so I can update the radio as well, or is there a better way?
No os installed!!! Need help asap!!!!please
I hope im posting in the correct forum (forgive me if im not i mean no disrespect) im new to this rooting thing and made a choice the other day to root my htc dna thats currently on kit kat 4.4.2. I started out with clockworkmod and didnt like that so i then flashed twrp. The reason i didnt want to continue with clockworkmod is because i notice that there was some storage issues going on, i went to my settings and located my storage and saw that the other field was reading that over 13gb was being used up. I couldnt find out what the 13gb was so i started researching and found out that clockworkmod might have been having some issues with duplicating the os therefore taking up too much space. So what i did was try to flash the twrp thinking that would work and the storage was still being taken, so i started researching again and found out that i would need to do a factory reset and start all over....well when i did some how i erased the os as well now im stuck on the htc screen or i have the option of booting up into twrp but thats it.... I downloaded what i thought was the right ruu but thats not working i keep getting error 158....please somebody help me!!!!!!
CHRIST STARZ said:
I hope im posting in the correct forum (forgive me if im not i mean no disrespect) im new to this rooting thing and made a choice the other day to root my htc dna thats currently on kit kat 4.4.2. I started out with clockworkmod and didnt like that so i then flashed twrp. The reason i didnt want to continue with clockworkmod is because i notice that there was some storage issues going on, i went to my settings and located my storage and saw that the other field was reading that over 13gb was being used up. I couldnt find out what the 13gb was so i started researching and found out that clockworkmod might have been having some issues with duplicating the os therefore taking up too much space. So what i did was try to flash the twrp thinking that would work and the storage was still being taken, so i started researching again and found out that i would need to do a factory reset and start all over....well when i did some how i erased the os as well now im stuck on the htc screen or i have the option of booting up into twrp but thats it.... I downloaded what i thought was the right ruu but thats not working i keep getting error 158....please somebody help me!!!!!!
Click to expand...
Click to collapse
There is a search feature to use for finding out how to recover from your mistakes.
Try searching for error 158.
Hackenstein said:
The problem with that turned out to be an outdated version of CWM. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade I also needed a driver upgrade which I took care of (after I had installed TWRP to test as well, just stuck with TWRP). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When I'm done there, should I run firewater to achieve S-OFF so I can update the radio as well, or is there a better way?
Click to expand...
Click to collapse
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
santod040 said:
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
Click to expand...
Click to collapse
Well Said, and on that note, DEVS - I do appreciate all info that I receive here, whether it's from searching/reading or when a question gets answered. Thanks for all you do!!!
tat
santod040 said:
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
Click to expand...
Click to collapse
I really love the fact that so many came in to actually ANSWER my question(s) and give relevant info on the issues I was experiencing (heavy sarcasm obviously). Ironic that only when I took a jab at someone's work (out of frustration) that the thread became active with people only sounding off on that issue, still ignoring the original problems I brought to the table. Top notch support!!!!!!
With that out of the way, to santod040; please accept my apology. I said that out of complete frustration and it was totally unecessary. Contrary to the negative vibes that comment conveyed, I DO appreciate all the devs hard work and allow me to publicly thank you for that. It was bad night of troubleshooting for me as I've been out of the loop for quite sometime and was rusty in several areas. Adding to that was the complete lack of helpful info I was finding not only on this site but several others. Kept going in circles and getting no where.
It is extremely important I point out that out of five different ROM's I tried to install via sideload, your's is the ONLY one that actually worked and in the end, I went back to it as it allowed me to finally boot into Android and enable USB debugging and help get the S-OFF process started via Firewater. Conclusively, I was finally able to get the baseband upgraded and get the phone fully up to date. So, thank you, wholeheartedly, and I apologize again for letting my stress get the better of me that night. LiquidSmooth saved my ass.
Cheers, my friend, and thanks again.
I can help if your s-off
hackenstein said:
the problem with that turned out to be an outdated version of cwm. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade i also needed a driver upgrade which i took care of (after i had installed twrp to test as well, just stuck with twrp). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When i'm done there, should i run firewater to achieve s-off so i can update the radio as well, or is there a better way?
Click to expand...
Click to collapse
if your s-off i have a method that will help you .....have you switched to s-off?
I just received the prompt to do a System Update, see the image below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone have any idea what it is? Lollipop??
If anyone has installed it, does it break root?
I installed it and now I'm stuck in recovery (TWRP). Can't figure out how to boot back into system no matter what I do. Any suggestions would be appreciated.
Interested in knowing if this breaks root as well. Til then, no install for me.
No idea. Got the update notification just now but since I'm rooted and on a custom ROM, I don't think I should flash it.
If you're rooted, and unlocked, I would avoid this update like the plague. Give the devs time to look at it.
Just got the same message. It looks forced, you cant get rid of the message without adding a time to postpone until. I did 10am tomorrow, hoping it wont auto-update at that time and will bring the prompt back so i can postpone again. If anyone knows what apps to disable so that this cant happen that info would be great right now
ryman222 said:
I installed it and now I'm stuck in recovery (TWRP). Can't figure out how to boot back into system no matter what I do. Any suggestions would be appreciated.
Click to expand...
Click to collapse
I suggest never taking an OTA update if you aren't 100% stock.. and def never do one if on TWRP.
Fix being stuck in twrp - http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
General info on taking OTA - http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
I'd assume this new OTA update today will block ioroot and stump from working. Whether a previously rooted phone will retain root through the OTA is a gamble.. may or may not work. Some have reported already that root has stuck thru the OTA. So might luck out with this one. For those who are not rooted and take the OTA update.. gaining root again may not be so easy (without downgrading).
Without seeing the bootloader.. can't say if Bump is blocked. Most likely not yet though.
Dobrah said:
Just got the same message. It looks forced, you cant get rid of the message without adding a time to postpone until. I did 10am tomorrow, hoping it wont auto-update at that time and will bring the prompt back so i can postpone again. If anyone knows what apps to disable so that this cant happen that info would be great right now
Click to expand...
Click to collapse
Yeahh if we could get that, that'd be great. I don't wanna have to deal with breaking root/unlocked bootloader.
What I did when it asked for a time to update was just press the home button. Then it went into a notification saying an update is available. I think that'll keep it at bay.
Dobrah said:
Just got the same message. It looks forced, you cant get rid of the message without adding a time to postpone until. I did 10am tomorrow, hoping it wont auto-update at that time and will bring the prompt back so i can postpone again. If anyone knows what apps to disable so that this cant happen that info would be great right now
Click to expand...
Click to collapse
If you just press the back button itll stay in your notifications, but it wont force you to do anything. Notice the blue checkmark.
Guys come on updates should never be taken period rooted. Sooo wait few days until there is time to examen and provide the community with info
dabug123 said:
Guys come on updates should never be taken period rooted. Sooo wait few days until there is time to examen and provide the community with info
Click to expand...
Click to collapse
+1 lol...
Guys just freeze system update with titanium backup...
Lollipop? On Verizon? Hilarious.
I took the update. I'm not an expert but it looks like it's just an update from software version B to C. It puts a camera shortcut on the lock screen, which isn't really necessary given the back button shortcut. Still missing the rom I had on my Galaxy Nexus, which was more current than this. Love my phone, hate having outdated Android.
Root does not appear to be affected. I am not a dev, just a rooted phone owner so take that for what it's worth.
To Block OTA's visit this thread:
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-disable-ota-downloads-verizon-t2914735
I caught wind of this on reddit before the update showed up and had a feeling my IORoot/Bump unlock setup wouldn't agree with this OTA. I used TiBu to freeze "System updates 1_13_10_0" and made a nandroid backup just in case. All good so far. Several redditors with custom recovery softbricked when they tried to install it, so this seems like the way to go for now.
ryman222 said:
I installed it and now I'm stuck in recovery (TWRP). Can't figure out how to boot back into system no matter what I do. Any suggestions would be appreciated.
Click to expand...
Click to collapse
I just accidentally installed it and the same thing happened to me. This got me out of it:
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
I noticed this sitting there today and was wondering about it before i proceeded. I never use WiFi so it won't download so for now I am safe.
I just don't get it..Blow away!
Anyone know where the update is stored once downloaded? I'm assuming it's somewhere in the system folder, but not sure where to look.
Is this at all possible? When attempting to downgrade with LGUP, it interrupts the flashing process (usually) around 9% with this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there a way to force-flash it regardless of this error? Or am I stuck without root forever?
Any answers are greatly appreciated.
At this moment in time the answer is NO. This is why you want to not do an upgrade until root is confirmed for the newer OS. Once recovery is available maybe you might be able to get root back.
I should correct myself you can't use the kdz files and go back to lolipop
details here :
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I was thinking about the TWRP method before, my bad.
LBJM said:
I should correct myself you can't use the kdz files and go back to lolipop
details here :
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I was thinking about the TWRP method before, my bad.
Click to expand...
Click to collapse
Thank you for the snappy reply! I have been very closely watching these forums on updates to either downgrade to lollipop, or root marshmallow. I sure hope we can get this resolved for people who's phone came with marshmallow
jingTongy said:
Thank you for the snappy reply! I have been very closely watching these forums on updates to either downgrade to lollipop, or root marshmallow. I sure hope we can get this resolved for people who's phone came with marshmallow
Click to expand...
Click to collapse
I had to downgrade using that same software when I purchased my Lg G3 and that alone sold me on the V10. With Samsung phones you are stuck if you have a newer OS.
The main reason you cannot downgrade is that the software won't flash an old version (as it checks your version stub), at all, on Verizon.
mcbeat257 said:
The main reason you cannot downgrade is that the software won't flash an old version (as it checks your version stub), at all, on Verizon.
Click to expand...
Click to collapse
So, with the way you termed it, it sounds like it's a software problem with LGUP?? If so, do you think it can be patched to ignore the version?
jingTongy said:
So, with the way you termed it, it sounds like it's a software problem with LGUP?? If so, do you think it can be patched to ignore the version?
Click to expand...
Click to collapse
The software itself makes it do this, and it is irrevocable and not able to do so in the builds, it reminds me of when I had my galaxy s4 and this happened as well.
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
mikekoz said:
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
Click to expand...
Click to collapse
Could you quote the part on that post where it talks about downgrading the firmware? As far as I can tell from the link you provided, that post only talks about returning the phone back to stock. And just to be clear, once you install the OTA update to the MM build, your stock is now the MM firmware. Please correct me if I am wrong.
zatanas33 said:
Could you quote the part on that post where it talks about downgrading the firmware? As far as I can tell from the link you provided, that post only talks about returning the phone back to stock. And just to be clear, once you install the OTA update to the MM build, your stock is now the MM firmware. Please correct me if I am wrong.
Click to expand...
Click to collapse
You may be correct, and hopefully somebody more knowledgeable than myself will chime in, but this text is part of the instructions from that thread:
TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a FULL wipe, tick BIN file. Press Start. Make cup of tea and be patient
This does not work on the Verizon variant
Sent from my VS990 using XDA-Developers mobile app
mikekoz said:
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
Click to expand...
Click to collapse
I was having the same battery drain problem after the Marshmallow update on my V10. I let it go for a couple days to see if things would improve. Unfortunately, things weren't getting any better. While I've rooted a lot of Android phones in the past, I didn't really want to void the warranty on this phone yet.
I went ahead and did a factory reset and the battery is working better than ever. I usually use Titanium Root to backup, but had to rely on LG Backup this time. It worked well enough even though it took a long time to copy everything to the SD Card (about 3 hours for 4 GB). Only things that didn't come through after restoring were my home screen settings and the history for one game. No big deal, about an hour to get everything configured back to original (grab screenshots of your homescreen first).
Pretty thrilled to see the battery performing better than ever. Just got 16 hours out of it yesterday and had 35% left on somewhat light use.
burnsky05 said:
This does not work on the Verizon variant
Sent from my VS990 using XDA-Developers mobile app
Click to expand...
Click to collapse
The instructions say otherwise. There is even links to Verizon drivers. Where do you see that this method does not work for Verizon V10's?
http://forum.xda-developers.com/showthread.php?t=3344828
Sent from my VS990 using XDA-Developers mobile app
The thread also states its for certain models of LG V10 but the LGUP has a anti rollback built into it that will not allow you to go from marshmallow to lollipop on certain models...
burnsky05 said:
http://forum.xda-developers.com/showthread.php?t=3344828
Sent from my VS990 using XDA-Developers mobile app
The thread also states its for certain models of LG V10 but the LGUP has a anti rollback built into it that will not allow you to go from marshmallow to lollipop on certain models...
Click to expand...
Click to collapse
Thanks. :good:
So, maybe someone could come up with a anti rollback work around? Hopefully, or some other alternative.
hann1balk1ng said:
So, maybe someone could come up with a anti rollback work around? Hopefully, or some other alternative.
Click to expand...
Click to collapse
Possible if someone could reverse-engineer LGUP to allow downgrading. I have the lollipop KDZ file, now all I need is a way to flash it to my vs990.
In an attempt to downgrade an error was not seen in LGUP. As far as anyone could tell the phone and LGUP were in sync up until 85% or so and the reboot was initiated. The phone never came back on. LGUP made it to 100% but the phone stayed black. Maybe not,enough time was allowed to pass but the battery was then removed. The phone became a brick and wouldnt start in any mode. When plugged into a computer the computer sees something tries to install a driver then fails. Do not try and downgrade from Marshmallow with LGUP. It will not work.
AMCJUNGLE said:
In an attempt to downgrade an error was not seen in LGUP. As far as anyone could tell the phone and LGUP were in sync up until 85% or so and the reboot was initiated. The phone never came back on. LGUP made it to 100% but the phone stayed black. Maybe not,enough time was allowed to pass but the battery was then removed. The phone became a brick and wouldnt start in any mode. When plugged into a computer the computer sees something tries to install a driver then fails. Do not try and downgrade from Marshmallow with LGUP. It will not work.
Click to expand...
Click to collapse
Oh man that sucks.
Sent from my Nexus 7 using XDA-Developers mobile app