yashsingh1/xdaforums huggingface dataset:
[Android General] pol098:
Stillworks July 2020

This worked in July 2020 to restore SMS messages (I didn't need contacts). I tried to restore selectively from a full OrangeFox (OF) NANDroid backup (a full restore didn't work, encryption/password issues) with Titanium Backup (TB), but this didn't work (maybe I simply didn't know what to restore?). I tried the old Nandroid Manager's facility to restore SMS from a NANDdroid backup, but it hung.

I then successfully extracted mmssms.db as described here and further extracted the xml file with the yaff extractor. TB's "Restore data from XML" hung, but SMS Backup & Restore worked fine.

Xiaomi Redmi Note 7 (lavender), all software current as of July 2020: xiaomi.eu 20-07-23 weekly ROM, TB 8.4.0.2, others downloaded today. A useful way to find the SMS file if it has a different name than mmssms.db: after extracting from the tar.gz, search the extracted files for a string that only appears in your SMS (I used "bekonscot").

Incidentally, a note on Titanium Backup, which can restore either from its own files or a NANDroid backup: the directory for the NANDroid file is hard-wired to the directories used by TWRP and CWM. I use the current OrangeFox instead of TWRP, and it uses a different directory. But the OF backup is compatible with TWRP; moving it to /storage/emulated/0/TWRP/BACKUPS/ works.

HTH
[Android General] LVArturs:
I used a Note 4 (Android 6) full nandroid to Note9 (Android 10). For contacts I just copied the .db to the new location (the directories where .db are located might not be the same) and rebooted - it worked (on rooted), but this will remove any contacts already made, replacing them with the backup.

SMS and Call logs were restored as described, but I used a newer version of the app (which combines both SMS and logs restoration), searched the backup archives with ZArchiver, and I ran the python2 version of the converter (https://github.com/abbot/android-restore-tools) on TermuxArch (meaning that, unlike the Windows version in the tutorial, this should work on any OS supporting python2, allowing me to do all steps on my phone).

Also, in the directories where. db files are located there are big .db-wal files, too, which might contain some data that aren't in the .db yet, so you might need to VACUUM with sqlite3 (https://stackoverflow.com/questions...f-sqlite-3-7-wal-file-into-main-database-file). I did it on TermuxArch as well, but the size of the db didn't change much, while the wal disappeared, so I don't know if that did anything.

P.S. Sqlite3 wouldn't open db at all just on Termux for some reason, opened on TermuxArch. Python2 also exists for Termux, didn't try but should work.
[Desire 820 Q&A, Help & Troubleshooting] melancholicx:
Hi All,

Long time reader, first time poster :)

Short story: I just need a straight link to a recovery.img file specific to my device which is a HTC Desire 820.

Long story:

- Upgraded my phone to Lollipop.

- Unlocked my HTC phone.

- Followed a guide on the net regarding flashing TWRP recovery image and rooting (did not realise I was unknowingly flashing a previous / incompatible version on my phone).

- Now stuck with a phone that can't boot to recovery or factory reset (because it then tries to boot to recovery when doing this).

- I can get into the boot loader screen and fastboot, but selecting HBOOT and then RECOVERY makes my phone vibrate a little and flashes a message, but then goes back to the boot loader screen.

- I tried to flash another recovery.img file, but this just made it so that the HTC logo is displayed and doesn't get passed that.

- Now I just want to flash the lollipop recovery.img so that I at least can root the phone and not necessarily install TWRP.

Any ideas?

Thank you in advance.
[Desire 820 Q&A, Help & Troubleshooting] melancholicx:
So... no ideas?

lol *bump*
[Desire 820 Q&A, Help & Troubleshooting] tomal:
Post your device model, i.e. 820n...820u...
[Desire 820 Q&A, Help & Troubleshooting] melancholicx:
Thanks for responding and providing guidance [MENTION=789040]tomal[/MENTION].

The model of my phone is: HTC DESIRE 820 Model Number: OPFJ50.

Thank you in advance.
[Desire 820 Q&A, Help & Troubleshooting] ksravan608@gmail.com:
Power of your device and connect the device to the charger when it is in power off after connected you quickly press vol up+power button or vol down+power button then you find a charging logo then release the buttons after tha the phone goes off automatically then you quickly press vol down button only it gets the bootloader then you flash the only lolliop stock official recovery.img because twrp of 64 bit having some bugs.but they fix it you wait for some time.
[Desire 820 Q&A, Help & Troubleshooting] Deleted member 7060308:
keep on pressing the power button for a minute and then restart into the os .

still searching for the recovery.img compatible with htc desire 820.

please if you get let me know at saiyedsaleemahmed@gmail.com .
[Desire 820 Q&A, Help & Troubleshooting] ksravan608@gmail.com:
Flash stock official recovery....it having no bugs while booting,restarting,formatting the phone. but it can't handle the ota updates. You have also wait for some more time they will updated best recovery or stock ruu or how to s off.
[Desire 820 Q&A, Help & Troubleshooting] kehfren:
Hi, I don’t know who or were to ask, my HTC Desire 820 was working fine, no problem at all. I got a voice chat and while listening there was a loud noise and the device shut off. After a few seconds it booted back up and didn’t load android, it was on a constant bootloop. I couldn’t turn it off or anything. After a while it shut itself down. Assuming the battery was low I connected it but to my surprise it wasn’t charging, the orange LED was blinking. I leave it plugged in for more than one hour but the situation continued, the phone was not powering on and the led was flashing. At that point what I did was to remove the back cover and reset the battery which make it begin to charge normal. After 30 min I tried turning it back on but the boot loop was still there. I could manage to enter fastboot and perform a factory reset. After it finished the device was booting back up and at a certain point the bootloop start over. The device was not rooted, bootloader locked, everything stock, since I didn’t want to mess with it because it is my only phone at this moment. I think on unlocking bootloader, and rooting to try install a custom rom or a backup save from someone. I have been able to unlock bootloader but TWRP doesn’t load, the device will not go into custom recovery and I have tried several versions. Now I don’t have the stock recovery anymore. I can go into bootloader, but nothing else.

I have to mention that now I have more than 24H dealing with this with no luck or signs of fixing my phone. Please, please any one that can help I will be very grateful.

My phone info is the following

HTC Desire 820 dual sim.

A51_DTUL PVT SHIP S-ON

HBOOT-3.19.0.0000

OS-2.10.709.2

SEP 25 2015
[Desire 820 Q&A, Help & Troubleshooting] ksravan608@gmail.com:
SO in this way you have to s off the htc desire 820 and flash the ruu means os zip file in bootloader or type the command fastboot rebootruu in fastboot mode then flash the ruu with fastboot files with the help of computer.
[Desire 820 Q&A, Help & Troubleshooting] kehfren:
But as far as I have read there is no way to S-OFF the Desire 820 so far. And I havent been able to find any RUU on the web
[Desire 820 Q&A, Help & Troubleshooting] ksravan608@gmail.com:
It is there to s off but you have to pay some money with the help of sunshine
[Desire 820 Q&A, Help & Troubleshooting] kehfren:
I have used it before with another device I had. and to be honest I will be glad to use it again. the big problem here is that the phone is not booting, so I cannot install sunshine to gain S-OFF.

If there is any other way to get it done or something to allow me boot to the OS it will be great
[Desire 820 Q&A, Help & Troubleshooting] ksravan608@gmail.com:
The only solution for this is wait for a few days.because the htc desire 820 is the first model to get android 64bit.so the developers are not able to develop thirdparty code for it.if the device is locked go to the service center and give the phone they are all having the more stock roms to flash it.
[Nexus 5X Q&A, Help & Troubleshooting] iamterence:
Is it just me and I happen to have a faulty camera, or does the camera still sorta suck?

I mean, don't get me wrong, the pictures are sharper than ever due to the bump in megapixels, but from my experience, I can't get too close to a subject, or else the camera just won't focus. I have to pull back slightly to get a good macro shot. Not only that, but usually when you're in a dark room with a single light source, you have to tap on the light in order for the exposure to adjust to the light so you can get a clear picture. With my phone, its actually the opposite. You have to tap on a dark spot in order for the exposure to adjust to the light source. If you tap on the light source, then the exposure gets blown WAYYYYY TF (the ****) out. It's... Actually kinda weird.

Maybe I'm not camering right or something. Or maybe this is something that can be fixed in a future update and/or a different camera app. I will admit though, however, that before I got my N5X, I was using my Galaxy S6 for about a week, so I might have been slightly spoiled by that, lol.
[Nexus 5X Q&A, Help & Troubleshooting] gtg465x:
Which camera app are you using? Exposure works as expected and not how you describe in Google Camera for me.
[Nexus 5X Q&A, Help & Troubleshooting] iamterence:
Using stock Google camera as well. I don't know. It's not really bad, just... Head-scratching lol
[G4 General] nipun1110:
Weird title, isn't it? Thing is I am a bricked device sufferer. And I couldn't repair it in my country cause it has motherboard problem. See I am seeing still some new users are getting motherboard problem out of nowhere. There has been an unofficial news that some devices manufactured before September 2015 are having motherboard problem. So only solution is replacing the motherboard. I didn't know this info before buying a new G4.

As a root enthusiast, I would definitely unlock my bootloader by now. But I cannot do that as it will void my warrenty if anything goes south again. U can already find many unlocked bootloader owners are having motherboard issue (even recognised developer S3V3N also), so obviously they cannot claim warrenty anymore. This is a painful feeling that when or whether my device will have motherboard problem again.

LG isn't saying anything officially why this problem is arising. There must be a specific motherboard batch that is having the bootloop issue and LG must know it. If LG were a good company who think about their consumers, not only profits, they would already publish a list of IMEI of those devices or at least give some ideas how to identify which devices may have the issue. Right now it's completely uncertain if my new device will ever get bootloop issue and if so, when???? I wish my phone would get into bootloop now since I am having locked bootloader, so that I could replace the motherboard and then use my phone free of tension the way I want.

I don't know if you guys understand my pain, but it's a matter of humanity. Not everyone is capable enough to buy a new phone twice or thrice a year, right?
[G4 General] mgolder:
If you haven't voided your warranty then send it back and get a replacement. If you have voided the warranty, then that is surely the risk you take when deciding to root etc?
[G4 General] lurker316:
I didn't root or do anything to my phones if I couldn't afford to buy a replacement right away. Perhaps you should also err on the side of caution.
[G4 General] nipun1110:
hey man, try to understand the point. breaking yr screen is one thing, getting yr phone soaked in water is one thing, but getting faulty motherland in a almost new device is totally unpredictable and uncool and should not be. a brand new device should not have such a major issue. but as it persists, being a leading OEM, LG should acknowledge it publicly or help people find out a solution. that's what I meant. suppose if I would know that my device has already a faulty motherboard inside which is prone to cause trouble, I could go now and ask for a replacement. That would be convenient, isn't it?
[G4 General] mgolder:
But the fact remains that if the phone is as it left the factory, and was bought brand new from a retailer, then you are entitled to a repair or exchange. So just do that.
[G4 General] ABotelho23:
See, LG has stated that they cannot maintain the full scope of the warranty. If the motherboard is shot, and it has nothing to do with what software you've installed, why would LG not honor the warranty?
[G4 General] KennyG123:
You are correct in some units being defective before the September builds. Sprint has listed a recall with their technicians and T-Mobile has been replacing bootlooping devices no questions asked. The way to determine the date of manufacture of your device is in the first 3 numbers of the serial number. The first number would be the year, so a 5 means 2015. The next 2 numbers are the month. So 09 would be September.
[G4 General] dvgb173:
Do units made after May 2015 show HW rev other than 1.0?

Doug B.
[G4 General] Darkmasterhk:
So an s/n starting with 509 would be safe than?^^
[G4 General] KennyG123:
That is what it sounds like as Sprint was told "before September"
[G4 General] nitrous²:
Does that only count for US devices or are devices globally affected? I have 507 on a H815-EUR in Germany.
[G4 General] chaki-:
Mine was bought in Germany and starts with identical serial number.

Already motherboard replaced....
[G4 General] nitrous²:
Yeah, but why has yours been replaced? Had it have the listed symptoms? Mine doesn't.
[G4 General] phsnake:
THX for this post - H815 EU (bought in Slovakia) already at seller and waiting how they will deal with that - Also similar problems appeared in Poland (developer S3V3N from here), another thread in troubleshooting section started by some Thailand and Israeli users.
[G4 General] chaki-:
Mine has started to restart itself outta nowhere. But before that i had installed the z cpu app and strangely it showed that the processor its clocked at 1.2 ghz...

After the bootloop started it couldn't been stopped till the battery died. It got crazy hot of course.

Tried to charge it. It did charge a bit then stopped charging either. And it was officially dead?.

Send it for repair.

After two weeks i got it back. On the repair report was stated that motherboard was unable to repair so they put new one. And a new usb port too.
[G4 General] KennyG123:
It is global and effects a small percentage of the ones made before September.
[G4 General] nexy33:
Samsung had similar probs 3 years ago with the s3 sudden death bug that was a faulty emmc controller chip literally thousands had their motherboards replaced, plug it in at night wake up dead phone mine worked fine for 11 months then just died
[G4 General] nipun1110:
Everyday new users are facing bootloop problem. All having serial no 505....... But most of the devices were made on that batch.. I am getting frustrated. Exactly feeling like the Thread Title. I wish I could go to LG & change my current device to a new one.....
[G4 General] superbonto:
this is just the piece of enlightenment we all need. many peeps in my region speculate if the bootloop are software related or heat related
[G4 General] dman1049:
Are there an Vs986 (Verizon) confirmed faulty motherboards?
[G4 General] novastar1:
How many of you on the board had/have this motherboard issue? Haven't seen much topics. I have a 506 .... No problems so far. Hopefully none in future

Does anyone know any specifics on the motherboard fault?

This reminds me of the faulty nand in the early batches of note 2/s3

Edit

Saw poll topic

This is ridiculous. Really no way to tell if your is ticking down to it's own failure

However pool doesn't say how many units are unaffected.... So incidence is hard to tell.... As most users happy with their units won't be looking for this topic at all
[G4 General] misteurz:
I'm afraid now. I was about to unlock my h815 bought very early. It's serial number begins with 500.

What to do... I do t know now

Envoyé de mon LG-H815 en utilisant Tapatalk
[G4 General] nipun1110:
exactly what I am feeling & what this thread is all about
[G4 General] nipun1110:
there are already guys who have repaired their devices and u can find that from the comments of some users... and there are many people who are not in XDA. plus if u look through Sprint's own forum (not in xda), u will b shocked seeing how many incidences there are.... doesn't matter how many, what I say LG should free check all the devices with s/n 500-505.
[G4 General] misteurz:
hey, i don't want to become paranoid.

could you mention a few threads in which people have this problem?

tx
[G4 General] phsnake:
misteurz: here are threads I found on xda. As I know, there is something on androidnow.pl (polish), 4pda.ru (ruusian)... I'm one of those "lucky" people affected :( & waiting for seller decision about repair - if they wont fix it I'm ready to bring it to court

Sprint

Verizon

Thailand, Israel, EU

H815 - INT/EU

T-Mo USA

AT&T
[G4 General] xdaboobs:
What's up guys

I just bought one here in the UK (GBR) with s/n 507. How worried should I be?

Interestingly - the box has an IMEI sticker stuck over the top of a pre-existing IMEI sticker, and the seal sticker is stuck over also a pre-exiting seal that looks to have been broken. Which is kinda weird isn't it?

I purchased the phone as a new item from ebuyer.com
[G4 General] awes0me1:
Mine is 502 so Im not gonna unlock BL just incase...still under warranty
[G4 General] spartan268:
This is great. I'm really hoping for some kind of statement from LG. Probably won't be much of a statement more likely a "oh too bad so sad. Defects happen" it will def leave a bad taste in everyones mouth
[G4 General] nipun1110:
LG finally has addressed the issue publicly and promised for repair. See in androidauthority forum.
[G4 General] xdaboobs:
Brilliant! :D do you have a link please?

vvv Thanks awesome news!
[G4 General] nipun1110:
Sure. Wait.
[G4 General] nipun1110:
http://www.androidauthority.com/lg-admits-g4-bootloop-problem-hardware-fault-669603/
[G4 General] spartan268:
Well for the most part. It is not like they were refusing to repair any phones. Everyone is still under warranty. At this point they just acknowledge it but aren't really going to do anything for the consumer beyond what they're already doing.
[G4 General] phsnake:
i hadnt any prob,i ended with bootloop, brought it to seller,and only one prb was 3weeks that i was forced to use some old spare nokia.it happened even before lg admited the fault with early released devices(sn:505) i gor brand new g4 in foil...

Sent from company iPhone thru Tapatalk - only because of company sec rulez [emoji24]
[G4 General] martin9400:
So, people with unlocked bootloaders are pretty much f*cked. I got this problem a week ago, serial number starts with 505, H815 bought in Norway
[G4 General] toybxb:
Not really, i know people that add bootloader unlock / root and sent to LG and they solved the problem, it´s a hardware problem (motherboard), not a software.
[G4 General] martin9400:
Yeah, I know, but right now I'm discussing with LG Norway that because of law, similar law to the us in regards to modifications that the producer, LG, need to prove that me unlocking bootloader and installing root is the sole cause of the bootloop, but all of the technicians in Norway goes straight at the fact that it's rooted and won't fix anything.

So I guess wish me luck in this heated discussion that I'm having with LG.
[G4 General] ObiDanKenobi:
One idea on another thread was to put 24V on the battery pins of the phone and the motherboard will fry so they cannot check if the bootloader was or not unlocked
[G4 General] martin9400:
Hahah, nice, but by law I'm going to win this one, just have to know my rights and all of that bs.
[G4 General] Loulou-13:
For this damned bootloop hillness ,now i'm really convinced that ALL G4 are affected ! no special series...

we have seen an impressive spate of feedbacks (tsunami ! ) of all android comunauties about 5xx series ....and now with the 6xx series (released later on factory ) have the first cases ( more and more) : it's logic......

and after the second wave of people who already have had this problem ,with theirs seconds phones as a replacement (again ! )

i think that this summer and autumn , a too big % of all G4 models manufactured will be affected on the bad story of this lg phone (more and mire bad reputation ,and with LG).... and this winter too many people here will have changed their phone and have others ones with others manufacturers...

In France ,more and more shops no longer offer G4 and mobil phone operators don't like at all to purpuse this phone (they prefer much more all IPhone ,samsung....)

Goodbye LG !
[Sable] paolitox:
I have made my worst error in my life i think... i was trying to update my rom.... but not really knowing what i was doing.. so.. unfortunately made the error...

now i have my ipaq HW6945 with a great hp logo wich says "hp invent, vG.39" and in the top something that says "serial" or "usb" when i plug it up.

After reading all the things you talked and having no idea of what to do... i asked someones help..

Do i have something to do ??? Has my ipaq chances ?... i was reading and looking for HW6945 ROM to flash my ipaq... but i had no good response...

Did anyone dump a rom of this ??? does anyone has a 6945 rom in your hard disk ?? or know where to find one ??...

PLEASE HELP ME !!!!

And forgive my english.. is not my first language...

im asking some help, because where i live, nobody knows about the solution if it has..
[Sable] nicromant:
hello

try to find HP Original ROM

i mean go to HP Website and download any ROM Update

or search on ther ftp servers

Regards
[Sable] paolitox:
thank you for your help..

but there is no IPAQ Original rom, to download... and it became really hard to find on internet..

thats why i posted here !!

thanks
[Sable] papizdono:
ho to HP and download the FW Update for the 6945... just use the german, or whatever rom is best for you, but there is no english rom... at least you will have a working phone for start.

where r u from anyway ?
[Sable] paolitox:
Hi..

first of all... i appreciate your consern, but i looked for it.. having no luck... so anyway... it doesn't matter if it is in english, german, italian... but i coulden't find it... i talked to hp consumers department, and they told me that there is no rom avaible for my hp model.... thats why i wrote here-- trying to find an aswer.

my hp is blocked... with the hp logo and the version of the rom or something like that....... and i dont' want to give up... thinking there is no solution...

thank you papizdono..... and im from uruguay.. a little country in south-america..
[Sable] nicromant:
Genial Otro amigo latino mas

puedes intentar Dumpear la ROM que es algo asi como copiarla del aparato de algun amigo tuyo y flashearla en tu 6945 hay un par de trucos para cargar roms de 69XX en tu ipaq no importa cual sea brincando la validacion del modelo, esto es un poco dificil mas no imposible se puede hacer desde las 63XX y las 65XX yo te recomendaria echar un ojo por...mobilitytoday, davesipaq o similares... espero captes el tip

Saludos!! :)