Database Develop

New software update!!?!

My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?

Does it automatically do the update? was your Nook Color rooted?
foxfire235 said:
My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?
Click to expand...
Click to collapse

Yeah, does it do it automatically. I have my Nook Color at home connected to my Wi-Fi. Hopefully, it doesn't download just download it without me being there =T

foxfire235 said:
My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?
Click to expand...
Click to collapse
How did it screw it up? I haven't received an update, been tethering all day

What is your software version in settings after the update?

I was using a rooted nook. It bricked it, and I couldn't get past the B&N logo on boot. I just had to do a factory reset.

After the factory reset, I got a confirmation dialog that said - "your nook has been updated to software version 1.0.0" ??? that doesn't seem like an update. Although maybe that's the factory default?

foxfire235 said:
I was using a rooted nook. It bricked it, and I couldn't get past the B&N logo on boot. I just had to do a factory reset.
Click to expand...
Click to collapse
Not to be a pr*ck, but if you're still able to do a factory reset, that would mean it wasn't "bricked", or did I miss something there?
Did the unit want to auto-update again once you reset?
-CC

clockcycle said:
Not to be a pr*ck, but if you're still able to do a factory reset, that would mean it wasn't "bricked", or did I miss something there?
-CC
Click to expand...
Click to collapse
I guess we have different definitions of brick. What would you call a device that doesn't boot?

A
A device that doesn't boot is a soft-brick
a brick cannot be fixed through trivial methods.

foxfire235 said:
I guess we have different definitions of brick. What would you call a device that doesn't boot?
Click to expand...
Click to collapse
As I understood "brick" means it's totally useless, other than as a paper weight or a door stop, essentially just dead weight.
I think if your device doesn't boot, but you can still recover, would be exactly that. {my device didn't boot, I had to factory reset it}
-CC

I wonder if they have something in there to detect a change to the OS that forces it to re-download ?

clockcycle said:
As I understood "brick" means it's totally useless, other than as a paper weight or a door stop, essentially just dead weight.
I think if your device doesn't boot, but you can still recover, would be exactly that. {my device didn't boot, I had to factory reset it}
-CC
Click to expand...
Click to collapse
in the venacular, "brick" means that the device is dead and cannot be fixed without replacing hardware. If a 'simple' reset will restore the device to working order, it isn't bricked it is just in a bad state.
We try to avoid the term "brick" when describing anything else because we don't want to gve the impression that we might be saying "I just did what I read in your post on the forum and now my device is broken beyond repair".

I'm fairly certain (but not 100% positive) that FW version 1.0.0 is installed automatically when you are registering the NC for the first time (like when the OOB setup is first done). After my initial setup I checked the version and 1.0.0 was installed.
And I've also noticed that if you do a factory reset and re-initiate the device 1.0.0 is automatically installed.

I'd like to see some verification that there is new software out there than this one user's report. Confirmation?

PHiZ said:
I'd like to see some verification that there is new software out there than this one user's report. Confirmation?
Click to expand...
Click to collapse
I remember somewhere, that there was a way to trigger it, or something like that... but its not a new firmware but just a redownload of 1.0

I think this is a known issue for some users after they root. I've read it before on here somewhere and in IRC.
MBM or Pokey9000 can confirm but i'm pretty sure it's nothing to be concerned with. Just re-root and see if you have anymore issues.

Mine was updated to 1.0.0 as well but I was still able to root it and do Angry Birds though.

nk414 said:
Mine was updated to 1.0.0 as well but I was still able to root it and do Angry Birds though.
Click to expand...
Click to collapse
People need to clarify more what they are talking about here.
Did you have it rooted before it was "updated" ?

Apparently these devices were rooted. While I'm sure there's a small, very small minority of XDA-ers who don't mess with their devices, the rest of us do. From a statistical standpoint it would stand to reason that these NCs were rooted.

[Q] XperiaT boot failed; Titanium 'merge updates to rom'. Any ideas for recovery?

Hi community.
(I've searched without success!)
I've 'broken' my Xperia T. It was rooted and I used Titanium BackUp to 'merge updates to ROM'. Unfortunately the phoned locked up mid process and upon rebooting my phone is failing to boot. I *think its on Android 4.2.. I'd guess I've corrupted the ROM..
I'm afraid I'm unsure if my bootloader is unlocked or not, i rooted over a year ago and cannot remember what i did.
Upon boot I see the 'sony' name for a couple of seconds, it loops doing this and then sometimes I see the symbol that is its 'fix boot thing' that tries to fix the problem. But it never does. So it is stuck in a constant loop, never getting past the earliest part of the boot sequence.
I can't get into Recovery Mode.
What method can anyone suggest I try to recover this? To me as a noob there seem to be numerous recovery methods none of which i understand at this point. What I'd really love to hear is a suggested recovery method and then i can read up and try. As i stand I'm all a bit daunted of where to start.
Thanks for any help on a suggested recovery method. If my phone is beyond repair, that is fine.

It seems your kernel is broken.
It doesn't exist android 4.2 for our device... so, what is your version? 4.1.2? 4.3? And which is your actual firmware?
This is important because if you flash the proper kernel, you can access to your system again.
If you have no idea, then flash a new clean stock firmware.
Take a look here: http://forum.xda-developers.com/showthread.php?t=2648320
For rooting and recovery, it will depend on which android version you choose.
For last android version 4.3, here is a quick tutorial: http://forum.xda-developers.com/showthread.php?t=2798411

istux said:
It seems your kernel is broken.
It doesn't exist android 4.2 for our device... so, what is your version? 4.1.2? 4.3? And which is your actual firmware?
This is important because if you flash the proper kernel, you can access to your system again.
If you have no idea, then flash a new clean stock firmware.
Take a look here: http://forum.xda-developers.com/showthread.php?t=2648320
For rooting and recovery, it will depend on which android version you choose.
For last android version 4.3, here is a quick tutorial: http://forum.xda-developers.com/showthread.php?t=2798411
Click to expand...
Click to collapse
Thanks mate that is very helpful.
I'm afraid i really don't know my firmware, build number or anything. All i know is is was an older version of Android 4.xxx If i had to guess i'd say 4.1.2.
If i can flash it to a stock firmware that is great! I'll run through this process see if i can get the 'flashtool' to communicate to my device.
:good:

Watoh said:
Thanks mate that is very helpful.
I'm afraid i really don't know my firmware, build number or anything. All i know is is was an older version of Android 4.xxx If i had to guess i'd say 4.1.2.
If i can flash it to a stock firmware that is great! I'll run through this process see if i can get the 'flashtool' to communicate to my device.
:good:
Click to expand...
Click to collapse
You're welcome... and don't mess again with Titanium backup and tools like that... instead, once you've rooted, learn to use backup/restore of recovery... it's way better

I actually doubt its kernel related. More likely is a certain important system app has been wrongly replaced and is causing the problem.
As far as I know, Titanium Backup doesnt do anything to the kernel.

WhiteNeo said:
I actually doubt its kernel related. More likely is a certain important system app has been wrongly replaced and is causing the problem.
As far as I know, Titanium Backup doesnt do anything to the kernel.
Click to expand...
Click to collapse
Yes, maybe you're right...
but the behaviour he reports about powering on and loops, is usually related to something wrong with the kernel.
In addition to this, he can't access to recovery anymore... and recovery is loaded before system. Why?
Or he means "recovery mode" as a lighter system mode (like windows for PC)... yes maybe he means this one... and not a recovery like CMW, etc...
He talks about "merging updates to ROM"... I actually don't know what he means exactly, I don't know how that titanium backup feature works, but if you update system files without updating the kernel, sometimes you can get bootloops because they don't match anymore.
At this point it's better he flash kernel+system together, that's why I suggested Flashtool ...and wiping all data too, is even better

istux once again thank you so much. It worked... on about the 30th time!
I would never have persevered without being given direct advice that this should fix my issue, so i'm very thankful.
I did have several issues getting it to work. For some unknown reason my Win 8.1 desktop refused to install the drivers required. It took me several attempts to realise the drivers were needed. I then switched to my Win 7 laptop and the drivers installed without issue.
But the main issue i was having was the power loop, I couldn't effectively switch off the phone. I had to let it the battery die entirely and then try, after about 20 attempts over 12 hours and several battery drains it suddenly sprang into life and started flashing. Its now as a factory reset.

Watoh said:
But the main issue i was having was the power loop, I couldn't effectively switch off the phone. I had to let it the battery die entirely and then try, after about 20 attempts over 12 hours and several battery drains it suddenly sprang into life and started flashing. Its now as a factory reset.
Click to expand...
Click to collapse
Why didn't you tell you weren't able to power off before?
If you get infinite bootloops, you have to push power+vol.up until it turns off.
You don't need to discharge the battery completely, because if kernel is actually corrupted you couldn't be able to recharge the phone anymore, because recharging process is managed by the kernel.
The risk to turn a bad situation into a nightmare is very high in these cases!! Be careful next time!!

istux said:
Why didn't you tell you weren't able to power off before?
If you get infinite bootloops, you have to push power+vol.up until it turns off.
You don't need to discharge the battery completely, because if kernel is actually corrupted you couldn't be able to recharge the phone anymore, because recharging process is managed by the kernel.
The risk to turn a bad situation into a nightmare is very high in these cases!! Be careful next time!!
Click to expand...
Click to collapse
To be honest I didn't actually know i was unable to power off until the instructions told me I had to and i tried without success!

I have just ruined Android on my Xperia E1 and need help to get it running again

Hello!
I was deleting some system apps I thought I did not need, but now the device does not boot properly.
It tries to boot but before the boot-process normally would end it reboots and that repeats forever.
I know it is my fault and all but please help me, I do not want to be without my phone too long, lets say I would like to have a running android system on my device before the end of this week.
Stock Android would be okay with me, but a nice custom rom would be very nice.
I know there are guides out there for anything I will need, but my question is, what will I have to do? Flash it?
It would be best if there was a method to do the process on linux (cause I do not have Windows or MacOSX) but if necessary I could acces a Windows PC.
Regards, germanman2

germanman2 said:
Hello!
I was deleting some system apps I thought I did not need, but now the device does not boot properly.
It tries to boot but before the boot-process normally would end it reboots and that repeats forever.
I know it is my fault and all but please help me, I do not want to be without my phone too long, lets say I would like to have a running android system on my device before the end of this week.
Stock Android would be okay with me, but a nice custom rom would be very nice.
I know there are guides out there for anything I will need, but my question is, what will I have to do? Flash it?
It would be best if there was a method to do the process on linux (cause I do not have Windows or MacOSX) but if necessary I could acces a Windows PC.
Regards, germanman2
Click to expand...
Click to collapse
Hi, I know little about this, but have researched a bit about debloating and custom roms... however, you can see a couple of good links in my thread here : http://forum.xda-developers.com/xperia-e1/help/basic-questions-rooting-debloating-t3238730 and the first response mentions XperiFirm which I gather should be sufficient to get back to a working device.
Hope this helps!

Thanks for the answer, found a rom for me

germanman2 said:
Thanks for the answer, found a rom for me
Click to expand...
Click to collapse
Hi germanman2, yes I saw on your other thread there were 3 roms mentioned. Out of interest which did you choose, have you already installed it?

H811 unbrick help

Hi everyone,
Please forgive any n00b questions.
I got started with rooting / custom ROMs on a Nexus 4, and I didn't realize at the time that this made things really easy and I didn't need to learn very much about how everything worked. Fast forward to last week -- I decided, at long last, that I was tired of using stock MM on my T-Mo G4 / H811. How hard could it be? Probably not much different from playing on my old Nexus 4 right? Lol, maybe not.
So now 72 hours later, my phone is hard bricked and will not enter download mode. and I need some assistance, if anyone would be so kind.
I will try to recount what I did:
To start with, I was using a Mac, so I used Homebrew to install Android platform tools / ADB.
I decided I wanted to try out LineageOS so I went ahead and followed their very clear steps (on LOS wiki) to unlock the bootloader install TWRP. However, TWRP doesn't seem to have an official build for the G4(!) so I had to look up and use one of the betas from this post. Is this where I went off the rails already? [Of course, very stupidly I also failed to make a complete backup of anything before going on ahead. Rookie mistake.]
After unlocking bootloader and flashing my TWRP beta, I was able to boot into TWRP just fine. I followed the normal prescribed steps of doing a Wipe (normal TWRP defaults -- system, cache, etc.?) before flashing the latest LOS nightly (14.1-something) and also the nano-x64 variety of gapps. I rebooted and got stuck with the LOS boot animation. I let this go for 55 minutes, so I am pretty sure it was an actual bootloop, not just the 1st-time-startup and optimization going on.
I rebooted into TWRP and decided to try a different ROM to see if that was the issue. So I wiped again, flashed another ROM (I believe it was a flavor of AOKP 14.1.x), flashed gapps again, and gave it another try. Again got stuck with an endless bootloop (45 minutes).
Since this is my daily driver, I decided to go back to stock. Found this thread, downloaded the MM-debloated zip, pushed to phone, and again Wiped + Flashed. This time, when I hit reboot, my phone was immediately hard-bricked. No startup screen, no nothing. That was quite unexpected. Also, the first time I had ever HARD bricked a device that I was playing with. Yikes!
Since then, I got a hold of a PC, and have been trying to revive the device by flashing an image to the microSD and booting into Download mode, in the form of this thread or this one.
I did get this to work briefly yesterday, or at least I got to Download Mode / Firmware Update screen, and then attempted to run LGUP with the KDZ file. However I ran into an error at about 9%, and couldn't continue -- and then I had to give back my loaner PC for the day. I also noticed that the LG Mobile Support tool was recognizing my phone NOT as an H811 but as something like HX230 or ... whatever it was, it was definitely wrong. Which is worrisome.
Today I'm giving it another try but my phone will not enter Download Mode at all, nor respond in any other way. I'm curious if this is a battery issue? So I am simply charging it for the time being. I also re-formatted the microSD and re-flashed the single .img just to be safe, but still can't get a response out of the phone. On my PC's device manager it is showing up as the common Qualcomm 9008 that a lot of people seem to have seen. No recognition from LG Mobile Support tool, nor from LGUP.
So ... what now?
It's possible that once my battery gets some charge again, maybe I'll be able to enter DL mode. Let's hope so.
However, I am also totally in the dark about which software version I should be using. 20i? 20p? I have no idea what these refer to, and I did not make any prior notes to capture the state that my phone was in before this all began. So IF I get to DL mode I will definitely need further instruction on the CORRECT KDZ FILE to be flashing. Else I will just compound my problems.
ANY tips or suggestions will be appreciated! Thanks so much.

Should have verified being on 20o firmware
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?

freeradical426 said:
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
Click to expand...
Click to collapse
try search for a fix if not may be @steadfasterX knows how to help you.

Re: searching for unbrick solutions
raptorddd said:
try search for a fix if not may be @steadfasterX knows how to help you.
Click to expand...
Click to collapse
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.

freeradical426 said:
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
Click to expand...
Click to collapse
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Click to expand...
Click to collapse
Thanks very much for the guidance! The post that you linked to REALLY helps. Until now I really was not sure what 10n, 20i, 20o, etc. referred to, aside from just various software versions. Having a definition for anti-rollback and further links to explain, really helps! This gives me more information and I might be able to self-resolve from here. I will give it a shot.
As for your question ... unfortunately there was NO instance where I flashed a working KDZ file, and I didn't know (due to my past experience with my Nexus) that I needed to check the STOCK software version of my phone before beginning to play with ROMs. In other words, I have no idea if I was on 20i, 20o, 20p, etc. From what I understand, this makes things a lot more difficult
Having looked at the linked thread just a little bit, it appears that using a 20o KDZ is the best bet -- because I bricked my device using a 20i ROM so I expect it was due to violating the anti-rollback restriction.
I will look into it more closely and come back if I hit another brick wall. Thanks so much!

If anyone cares, here are the ending results of all this ...
#1 Be wary of anti-rollback restrictions before you flash anything to your G4. You WILL brick your phone!
I tried multiple rounds and multiple variations of all the MicroSD card methods that I could find. I could NOT succeed in unbricking my phone.
#2 Luckily ... I was able to convince LG that I was still technically under warranty!
Because I had the stock bootloop issue in May 2017, LG did an in-warranty repair for me, and replaced the motherboard. So last week, I simply told them "my phone is AGAIN unable to charge and will not power on, just like in May". Since it had only been 5-6 months since the first issue, they agreed to replace the motherboard again.
Moral of the story: you can definitely unbrick your phone by having LG replace the mobo XD XD
From here, I think I will just totally avoid doing any rooting or custom ROMs on my totally-stock G4 coming today in the mail. I will cross my fingers and hope we get OEM Nougat in the USA sometime in the next couple of months.
Thanks again for the help everyone!

Question Device asking for password after restart.

So all of a sudden the s21 is asking for password after restart. I use the same password or 4 variations of it for these accounts. However I cannot login. I can goto web or new device and log in to my Google and Samsung accounts. But the device does t want to allow this.
I’ve seen options to flash firmware back one, I’ve done this in past. And can walk through most options. I tried ADB. But it is not enabled. And that’s become a major issue. If I could do any kind of backup, retrieval of the photos and contacts. That’s all I care about. The rest is not a big deal.
Anyone have any kind of insight? Direction? Thoughts? I can see the device in find my, but there aren’t any options to unlock. Just send message and erase.
I am willing to try almost anything, and if there’s a paid service I will try that. I’ve never seen this screen before, and have never had this issue. It does not make sense.
I purchased a new device and setup with passwords no problem. But there isn’t a backup on Google of the phone there. I tried wiping tge cache and that didn’t help either. I attached a photo of what the screen looks like.
Fwiw. I have photos of wedding and brother that just passed. i don’t want to lose those. I am desperate for any answer. Someone with tech support said I could send device to LV and they can do it. Takes two weeks and phone might not be useable afterwards.

Have you tried using Odin to flash the latest firmware?
What exactly does the password screen look like?

Electronic Punk said:
Have you tried using Odin to flash the latest firmware?
What exactly does the password screen look like?
Click to expand...
Click to collapse
I have not tried flashing anything yet. I was afraid of messing things up. But I’m familiar with the process and am willing to try

Stop stealing phones

Back up your files and do a factory reset

0rigin said:
Stop stealing phones
Click to expand...
Click to collapse
What the hell are you talking about?
Samarimama said:
Back up your files and do a factory reset
Click to expand...
Click to collapse
How would I back it up if I can’t log in?
Electronic Punk said:
Have you tried using Odin to flash the latest firmware?
What exactly does the password screen look like?
Click to expand...
Click to collapse
I do have a question about Odin, I downloaded from XDA. But it says to delete Google account before flashing or it will have problems. Wouldn’t that cause me to lose data?

No, if you back up with smart switch
Or you can bypass

0rigin said:
Stop stealing phones
Click to expand...
Click to collapse
Heffro said:
What the hell are you talking about?
Click to expand...
Click to collapse
Fellas, let's try to keep it civil. If you don't have anything of substance to contribute, it really doesn't need to be posted in this thread.

Bill720 said:
Fellas, let's try to keep it civil. If you don't have anything of substance to contribute, it really doesn't need to be posted in this thread.
Click to expand...
Click to collapse
It is 0rigins that make it first
And we didn't solved this problem

This happened to a friend of mine and i was able to "solved" it because he had a custom recovery TWRP.
I copied his files to a PC, while the phone was in recovery mode, then do a factory reset.
Later i found out that was an easier way to unlock the phone:
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
But all this requires a TWRP recovery. If you don´t have that, i guess that the password you need is the one that you have set on the device, while configuring fingerprints.
If you have "find my phone" enable, you should be able to reset that password using a browser on a PC...
Have you found out any other solution?