I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.
still no results
To no avail I have tried everything! I have seen some changes but nothing that tells me that its fixed! I have tried qpst, but either I don't know how to run it or it wont connect properly, as a matter of fact I dont think it connects properly to any of the programs I run on it. It doesn't help that the only way the computer recognizes it is when it is on demigod mode.has anyone out there in android land had some experience or any idea of how to format the internal sd and start over from scratch?
shiftykidd said:
I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.
Click to expand...
Click to collapse
You managed to fix it?
am facing the same issue.
Not yet i am thinking about just sending it back to lg. It's mixed up partitions, due to power surge from unauthorized power cords.
Do you have your phone rooted and with a custom recovery?
If yes,
Give this a try:
1.Enter recovery
2.Wipe data
3.Wipe cache
4.Wipe dalvic cache
5.Reboot
I've had the same problem with an LG L9 ii and this one fixed it.
So i really hope this will help. Inform me after doing this.
Greetings.
About five months ago I was able to access recovery but nothing was functional, now I cant even turn it on, if you left it on a different charger, kernal crash handler popped up half the time. Before it quit turning on the lg boot logo started going fuzzy, logic leads me to believe its a messed up Q C mother and the partitions are scrambled due to me using a non-oem charging cord and block, I also suspect the power button mounted to the back, on top of mother might have caused some hw problems. But those are just theories, it could simply be a bad battery!
Related
HI,
I used to be more active in this forum, but honestly nowadays I can't found any reason to since everything has been smooth sailing for me without any problems—until this day, at least. Somehow I got my internal sdcard busted, it was pretty spontaneous, all I can recall is suddenly the system starts to reboot itself. Nothing much, I thought to myself, problem is the system keeps rebooting, it doesn't even last a minute. Naturally when faced with this problem one would do the usual procedure, namely completely format the thing to stock the rule out any possibility on the user side of things, but then this is the part when it starts to get interesting...
The thing refused to be formatted, seriously, it baffles me at first but it does
Things I've tried:
Fastboot, it hangs at writing system, whether I was doing it line per line manually or via the flash_all.sh script, I haven't tried the toolkit but I think it's safe to assume that It'll do the same thing. Even if it does go on (which it did, once) it doesn't do any sort of changes whatsoever to the system.
ADB, nope, not this one either. And since the system reboots faster before I can do anything worthwhile it's pretty much out of the question.
Recovery, multiple times I've tried nuking everything via CWM, nada. I've tried TWRP too, I have to boot it from fastboot since it apparently doesn't allow me to flash a new recovery either, it reverts back to CWM every time. Also tried to flash a different ROM (CM), that didn't work, it spits out an error message regarding some failure in changing metadata, thought it was a corrupted file or something, so I re-downloaded it, that doesn't work. Still convinced that it's corrupted I tried 4 different version of it without any luck. Even the one I had successfully flashed before. Interestingly enough, flashing the exact same ROM I'm currently using (ShinyROM) works, not that it seems to do anything.
Built-in data format from settings, now this doesn't work because I assume that it needs the stock recovery to work, which I couldn't flash because it wouldn't let me—in a sense that it flashes just fine on the command line—fastboot doesn't show up any error or anything—but it defaults back to CWM as soon as I reboot it.
Manually via terminal emulator/file manager, still nothing, curiously enough, Terminal Emulator indicates that the whole system is read-only (I tried making a file with it, it shows that exact message).
Grit my teeth, clench my fist and screams out every curse word that I know of, this somewhat reduced my stress levels, but ultimately yields nothing.
Which led to be believe that either my phone was either a) Haunted or b) Has a serious hardware problem, I'm leaning on the latter. A few quick lookup with my limited amount of Google-fu and I've found several threads that described the exact same issue:
http://forums.androidcentral.com/go...-factory-settings-no-matter-method-i-try.html
http://forums.androidcentral.com/go...eset-nexus-7-2102-using-multiple-methods.html
Both of which hints at it being a hardware problem. Which was my biggest fear since I can't really revert the phone back to stock now can I? Locking the bootloader doesn't seem to work either (the 'fastboot oem lock' command works just fine but just like every single thing I've tried, reverts back to my previous setup as soon as I did a reboot), plus this means I have to send it back with my private data still on it, and I can't say I trust Samsung, Google (or anyone really) with my private data. Not to mention some of the stories I've heard/read about Samsung and their policy regarding rooted devices (much less ones with an unlocked bootloader).
In case it helps, here's a few more details:
What state the device is currently in:
It boots up just fine, but nor for long, apps starts to hang and ends up with a cold reboot (sorry if it's not the right jargon, but it starts right from the Google screen).
Everything that doesn't require you to access the filesystem works fine.
Apps doesn't seem to be able to write anything to the filesystem, I tried backing it up with Titanium Backup, much to my surprise the backup files weren't made (although TiBu seems to indicate that they were).
What the device is running:
Variant: Maguro 16GB
ROM: ShinyROM 4.4.2
Kernel: franco.Kernel r395
Baseband: XXLJ1
Bootloader: PRIMED04
Also I don't know if this will affect things but for the record I'm running the latest Ubuntu and Debian.
So this post is pretty much a shot in the dark, since I think I know what I'm dealing with already; if anyone had this problem before in the past, or has it now and somehow managed to fixed it, please do tell. Or if anyone has any experiences RMA-ing your device with a condition like this I'd love to know.
Yep your EMMC is fried. Sorry man.. But you can go to warranty. They *should* accept it since it is a developers phone but they could make a lot of hassle about it being rooted..
Sent from my Galaxy Nexus using XDA Premium HD app
Hey XDA,
So I need your help with something. This morning I woke up to my LG G3 D855 v10i stuck in a bootloop, for no apparent reason. I'd set an alarm to go off, and it did but only for a second and not the full 10 seconds it should have, and then it shutdown and went into a boot loop with the LG Boot Animation and the notification light was flashing yellow. I pulled the battery out, put it back in, and then restarted it. I got the same boot-loop except the notification light was alternating between blue and green as it should have been, but it was still stuck. So I pulled it out, tried again twice more, until the phone finally decided to boot. Then the phone boots, and I see my customized lockscreen with my lockscreen image and lock code, and then it goes to the screen to setup the phone completely again; Like it's a brand new phone with nothing on it, except that some of my apps were opening/running and I could see them doing things while on the setup screen. At this point I knew something was up, and I suspect a corrupted file or something on the phone, and then I started getting a whole bunch of errors on the phone itself, such as "Gmail has stopped working", "com.google.gapps has stopped working" "YouTube has stopped working" and basically all the Google apps had stopped working, but mine were still running fine.
So, after a whole day of trying to flash a new KDZ in Normal Flash mode to the phone using the LG Flash Tool 2014 here on the forums, and failing over and over (Yes, the phone was in download mode, COM port on the PC was set to 40 and I tried port 41 as well, I even put the .kdz file itself in the LG Flash Tool 2014 folder as it says to do, but nothing worked and I kept getting all this http://gyazo.com/158044ffe14287157a4388a2a42680c0 ) So I just decided to do a hard factory reset on the phone itself. I've now updated it and everything's fine, it's just a vanilla LG G3 with none of my apps on it.
Now I'm onto my current predicament. I've installed LG PC Suite when I first got the phone and since then I've done 2 full backups of the phone using it, as seen here ( http://gyazo.com/cebada2d6b06cd116afce22d8caad8bc ) but LG PC Suite recognizes NONE of them as seen here ( http://gyazo.com/3359f520739ab229334d9fa9d4e1edd2 ). In the area down the bottom where it should list the backups I've done, it doesn't list anything, even though the backups are in the correct folders themselves. Since factory resetting the phone wiped the internal memory, I lost all 32GB of my Apps, Photo's, Videos, and all my App Data. I NEED a way to get LG PC Suite or something else (Even ADB?) to push the backup/backup files to the phone and restore it. As you can see here, when LG PC Suite backs up the phone, it creates all of this data ( http://gyazo.com/a62ad1efa0e127c1b5830562965ed50a ) but in LG PC Suite's Backup/Restore device area when my device is plugged in, it shows no backups. I've even tried changing the directory the backups are in, re-installing PC Suite, everything.
I just really need a way for the PC, ADB or LG PC Suite to push all the files onto the phone and restore them, copying the files to the phone and using the G3's built-in restore app doesn't work either; All backups done by the phone were on the internal storage which was wiped with the factory reset
If someone could come up with a solution to this, I would be eternally grateful; You would save me an immense amount of time having to re-download my 32GB on my internet (Which is slow here in AUS) and I'd be eternally grateful. I'm not sure if it's the LG Software just being crap like their Android App Code, or if it's just an error or if the backups need to be in a specific place, I'm not sure. I just need a way to push them onto my phone and restore it. Thank you SO much to anyone that comes up with ideas or a solution!
TL;DR: I need a way to get LG PC Suite to recognize my backups I've done so I can push them to the phone.
iDefalt said:
the op
Click to expand...
Click to collapse
try This, I am sorry to say but you will have to redownload the 1gb file if this doesn't work esspecially since imei is motherboard depended'(imei error that you get) I guess you have a faulty motherboard you will have to bring your phone in for repairs
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse
nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).
Hi all!
Some days ago I urooted my TV android tv box with superSU and then I restarted it. From that moment when I plug the device it only reach the T9 logo (not the android one) and don't go further.
I've tried different ways to try to unstuck it, but nothing has worked.
I tried:
- enter recovery boot by holding the button in the av hole -> nothing happens
- install new firmware with adb sideload with both ubuntu and windows 10 -> always get errors (often error: closed, sometime other errors that at the moment don't remember)
- install new firmware with sd card using SDCard Installer -> the device doesn't boot when the sd is inserted
Moreover, with adb in ubuntu sometimes it recognises the device and I can enter the adb shell (but obtain errors when try any tipe of command), and sometimes don't (after adb devices I see list of attached devices: ??????????????? offline)
Now I'm thinking to try to install an ubuntu like on an usb pendrive...
I will be very grateful of any help/suggestion to how to revive my device :fingers-crossed:
Thank you!!!
Does this happen to be a pendoo model? I have a pendoo x10 MAX and i actually simply just installed supersu while it was rooted. Since then, I haven't gotten this thing to boot. Just stays on the boot screen the entire way. I wiped in recovery, knew that'd do nothing. I just wanted a root MANAGER. I tried Magisk, my favorite.. no go.. so then I went a bit old school.. so I tried ChainFire's SuperSU.. and THAT updated the SU binary! It said it succeeded.. it asked to do recovery install or normal install.. on phones, I've always done normal.. so I chose normal. Plus.. this thing has no custom recovery. I found it on Amazon. Overpriced, but great with the controller it had. It looks like I'll need a replacement and maybe a request to ask this guy if he could possibly NOT use something like KingRoot/KingoRoot/AmaraRoot or ANY One click root tool.. they just cause more bloatware, inciting boot issues and problems within the Android box itself. These One Click Root tools are out of control. It's to the point where I need to find a way in to adb and find the firmware for the latest version of this thing... X10Max from Pendoo.. I have not found a thing anywhere regarding firmware, and their website is ****. NOTHING *anywhere* on these things.. hell I'm about to return it as I bought it for $72. I have another one, same model.. wondering if the root method was different. About to boot that up and find out. I'll even swap the board. At this point.. he rooted it.. the WRONG way.. you can MOUNT THE /SYSTEM PARTITION IN RECOVERY. THIS IS ANDROID 9 we're talking about--the recovery supported by API v3.
This can and should have a TWRP custom recovery. If none exists, don't bother. As long as you can mount /system then you have a chance, at least, to root the damn thing.. which is why I'm still messing with it. I have another two weeks to return it. I'll give it another couple of days before I call it off and just switch out the good board for the bad one, return it, then return the other one and just use it until I find a way to use a custom recovery on this thing. There has to be.. unless there is no firmware available in sight (for an RK3318 or 3328, can't tell.. recovery mode says 3328, model name says RK3318. I see no difference at the moment aside from processor naming at this point--maybe speed?)
I'm still a nub with Android TV boxes so don't hold it against me for updating the damn root binary. If I could find a way to just reinstall the entire firmware and delete all previous stuff, I would. It would be worth it to learn. I would then mount /system in recovery and soldier on.
One little issue with this thing.. there's only one USB port that actually works. Same applies for the same exact product, a replication of the same thing.. was a "replacement" that still have/has the same qualities.
I've ranted enough. I vote more research into RK33xx processors and possible custom recoveries. I'm about to look for it based on only the device itself.
Note: Been stuck at boot screen ever since the binary was updated. I felt it was necessary to have a boot manager. I don't know where to even find the firmware. Can.. anyone point me in any direction? Something that MIGHT work on this thing? Android 6 or 7 would even suffice, return or no return, as "stuck on boot screen" will be my complaint. That's.. the actual complaint. I can't just *flash it* like the old days.. and maybe the original Android 9.0 firmware would suffice.. I don't know, but Pendoo.. wouldn't that be preferred?
You will need an SDcard to recover this box. I think the T9 32GB 4GB rom will do the job since its a cut down version.
Make a update SDcard and pop it in and power on the box. It will start the recovery on its own.
hello, sorry for my English I live in France I would have a question about the box: TV T9 RK3318, 4gb / 64gb. the problem is that the time is desynchronized on restart and creates problems to connect to applications when the time is out of order, I tried everything changed the time zone to deactivate and entered the time Manual it goes out of order all the time . is there a custom version or a version 10?
Very cook did I checked this out awhile back alot of good information that's for your contribution
So I bought a new phone since my old Onyx (One+ X) died (cracked screen and charging port is getting iffy). And finally I decided on this one, a cheap Chinese docomo branded one off Ebay.
I was so exited when it arrived, the UPS truck was at my gate when I got home that day, ready to leave, but the driver was nice enough to wait and give me my package then and there. Pheew.
Well, now to my, bootloader unlocking, recovery flashing, after market os installation and rooting story...
Bootloader:
The phone was supposed to be unlocked, and I guess that only meant SIM unlocked, because the service menu read "Bootloader unlock allowed: no". Damn.
A few Duckduckgo searches later, turned up I needed the "S!Unlock tool" which I found a copy off online, but username/password fields needed to be filled in, and I think I found a pirated s/n which didn't seem to work, (might have if I had tried harder).
But since it was just over £22 at https://networkunlocking.com/ I thought I could spare that on the off chance it worked. I was very surprised when it finally did, truth, I needed a few tries. And it actually did turn that service menu's pesky "no" to a thumbs-up "yes". Yay!
So now, pulling the cable, holding "volume up" and inserting cable for that blue light goodness, and running the "flashtool.exe -i 0x???? oem unlock bootloader 0x????????????" comand.
Not so fast, that doesnät work with newer flashtool versions...
Finding the old one from my Xperia Arc days and runnning it again, Yay!
(Wish I had read ahead and done that temporary root trick to rip my DRM codes off my phone first. But I don't plan to revert to stock, and I gather (might be wrong) that the DRM is only needed for stock roms, and not Lineage OS and such.)
Recovery (TWRP):
Now the problems start for real, getting into recovery was a **** and a half. Most guides for the phone says to push "volume up" multiple times during the boot-process. This turns out to be plain wrong. The actual button combo is holding "volume down" and "power" button together atleast until the screen goes blank after the unlocked bootloader warning.
Now, I wanted 17.1 on the phone and the recommended TWRp is 3.1.1 or something, and this works to install lineage fine, but don't forget to erase /data partition as I did. Stupid mistake that made wifi fail miserably, and probably a lot of other stuff, that I never tried before noticing my mistake.
However trying to get my own set of ringtones on the phone turned out to be another issue, going back into recovery when I noticed my ringtone.zip had failed. Obviously the media folder had moved since los 15.1,so no wonder right? Turns out it wasn't the only problem. TWRP 3.1.1 (or something) failed to unencrypt the root partition, so changing anything via recovery was a lie. fortunately the latest recovery, 3.5.2_9 did. So after installing that everything was rosy peaches.
Rooting:
SuperSU? forget it.
Magisk? yeah, but how? No really good step by step guide out there, except download from the github page, but what version?
A little trial and error, tried with the arm64 version and it turned out to be the right one. (Sometimes you just get it right on the first try...)
Renamed the apk to .zip put it on the phones memory, entered recovery and installed the zip, et voi effing la, Magisk root installed.
Root checker verifies root status, TitaniumBackup and RootExplorer works. Yes, my phone is playing ball.
Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone. 4 hours or so wasted trying different versions rebooting and flashing. Getting back my Viber messages turned out to be a problem to, TitaniumBackup got the messages back, but the db had references to my old images on my old phone, and probable pointed at the wrong directory so trying to send images either from gallery or take new photos crashed the app. Solution, backup the messages to my google account, uninstall and reinstall viber and restore from that backup. TitaniumBAckup is good but no magic bullet, it's a ***** that we have to rely on Google for backups though, I am allergic to the cloud, something about it makes my skin crawl.
Otherwise I like the phone, it says docomo on the back, something I can live with. The Chinese vendor even supplied one glass screen protector for the phone and a clear soft plastic case, in case I wanted some extra protection. I only wish there was a screen protector that had the same surface as the one that was on the phone in the box, that slightly opaque cloudy feel was so nice on my finger.
Can I recommend this phone? Nah, if noone writes a step by step guide that will cut down the time I spent on making this phone palpatable, I can't. But if you, like me, don't mind to tinker and don't want a phablet or spend way too much for the privilege to get a screen size you don't want, then sure. But why do we have to get them from China?
My trusty xz1 compact is slowly dieing on me and i am looking for a replacement how much did you pay for yours and is a really new or just refurbished ?
"Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone"
This Phone is in the mobile Sphere already ancient. Don't expect to get any help here or newer hot to guides.
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
muhschaf said:
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
Click to expand...
Click to collapse
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
4qx said:
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
Click to expand...
Click to collapse
Handy cannot boot now anyway so i would probably not able to recover anyway.
muhschaf said:
cannot boot now anyway so i would probably not able to recover anyway.
Click to expand...
Click to collapse
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
4qx said:
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
Click to expand...
Click to collapse
okay i will explain.
i had this common issue with this running out of internal space (13GB pictures i could not find, only 300MB left) and after looking into it i figured, that, due to my constant app installing and deinstalling, i had literrally thousends of little images (thumbnails, icons, you name it) that got not deintalled for whatever reason and clogged up my internal memory. So i made a Backup and decided to completly wipe and flash the newest lilac from Modpunk (18.1) and did a big Mistake here. i go into recovery and wiped EVERYTHING...without checking that recovery is untouched. then during the same session i installed the ROM and rebooted...so far all nice and dandy. Setting up the Phone, then get the newsest Gapps and then try to reboot into recovery to install them...well did i mentioned that i had wiped EVERYTHING? Well, there was no recovery anymore. Not my first rodeo i headbutt myself into the desk and spun up ADB/fastboot...only to run into the same problem i run everytime due to improper intalled driver i forgot already about. Longs story short: after some time handy refused to boot also into system.
Phone is now unbootable into any state, but Black screen fastboot over hardware buttons...
i COULD still try to make a blind fastboot flash after following the driver install instruction from above, but consider my lucky or clumsyness i will **** this up too and only waste time. and due to my current covid recovery i have not the energy nor the patient to diddle around with this sorry excuse of an absolute restrictive Phone and rather get me a S5 mini or something else that has no bootlock whatsoever and let you flash it from the very start.
i am plain running out of patient with sonys harassment.
/€: Also the constant "cannot get root" on a rooted phone is plain BS³. having permanent trouble to install adaway or use my sdcard proper is so friggin annoying that i now will search for a android version that got rid of this bull**** and will buy any phone that is suported by that ROM.
It is MY phone, and not Goolge nor the the phone company will dictade what i can or cannot install on it. i decide and i carry the risk, period. and the biggest security reason holds the phone anyway.
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
4qx said:
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
Click to expand...
Click to collapse
i known, the question is more "i really want that?" like i said i struggle with this phone ever since. and i realized yesterday the problem is not the phone itself, it's the bull**** of androids security architecture. Google seems to be very prone to make sure that they can shove any amount of advertisements down your throat. Given that they earn their money with ad network it doesn't surprise me.
i came to the conclusion that in reality i want to have a reliable way to install ad away on any given phone i own. i archive similar things on my desktop with Firefox and umatrix and ublock. And what can is say: Having Advertisment fee Internet is a bliss and i not care a bit about "but the free stuff" and i incrisingly fury about my inability to archive similar things on my phone i rely quite a bit.
@muhschaf I get it but you know what they say: good things require effort. But I find that once I set my Android up, I'm happy to have done it.
In regards to ads, you can actually install uBO on Android Firefox now, and many other addons also.
So i gave it a try again and the result was that it detects now a "?" under fastboot but ADB can't see anything failing sucsequently to flash recovery. i am also seemingly unable to get even into hardware fastboot anymore. But could be quite possible that the battery is already drained again. so i recharge it the night.
4qx: i was going away from uBO several years ago. Wonder that he has survived the drain after his "whitelist" decision, but it seems like.
Adaway block advertisement in apps and this is mainly the feature i wanted, see advertisment have gotten out of the browser itself into the Base/apps systems (Android, Windows) and therefore the Adblocker have to go with it. under windows i can control the System itself pretty easy and throughoutly with Powershell and package debloating scripts or regedit. under Android i haven't this option and have to rely on app like adaway. This shortcoming is pretty frustraing for an "Open Source" OS
After nearly a Year i stumble upon something windows related and now i have finally my xz1c back:
Windows USB Hubs of ANY kind (Monitor USB Hubs, Powers external USB Hubs, hell sometimes even the PCH, that is technical also a USB Hub), can and sometime WILL prevent proper lowlevel access to devices like...USB Headsets (Logitech Pro X) and Mobile Phones in fastboot mode (xz1c).
To circumvent this you have to connect the phone to a USB Port on the Back of your PC Motherboard DIRECTLY. every other Port can have an USB Hub in between that alters your write or readout and therefore failed the flashing.