Related
After several unsuccessful attempts to mount 3.1 on my Xoom, something seems to have caused the display to reverse. That is, the display is a mirror image of what it should be! This starts with the boot-up image of the Motorola Icon and carries all the way through till it's up. Several restarts have failed to resolve it, and it has me in a bit of a panic.
Have I just bricked my Xoom? Has this happened to others? Ideas? Suggestions? There's nothing on it that I have to save, so I could re-flash it, but I am not sure if/how to do this.
Many thanks in advance for any suggestions/fixes!
Phillip
Its not bricked if it boots...
That is strange though. May have to reflash stock images.
Try bringing everything back to stock?
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
Gr3yghost said:
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
Click to expand...
Click to collapse
No push the images using adb
I figured it could be done. Could you please point me to a thread explaining how to push images using adb?
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
That's great, thanks for the info. I'll have to do this later today when I am at a PC (now at a Mac).
Any ideas about why this would happen in the first place? I've looked through the forums but haven't seen any other threads about this issue. It may be fixable with a reflash, but it sure was 'easy' to 'break' today without even knowing why...:^(
djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
I have the 3G model. Looking at the instructions in that post, I have to admit I am not sure about a few (like most!) of the steps. It may become more apparent when I am doing it, but right now I am not clear as to where these steps take place.
[edit] Ok, I have just done some more reading and it appears I have quite a bit of work ahead of me, and that's just to get back to square one. Dang this was too easy to mess up!
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.
djsaad1 said:
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.
Click to expand...
Click to collapse
Sorry for the confusion, but I haven't been using adb. I was trying to install the update manually with a usb data stick and the microsd cord that came with my Xoom. That's how I got myself into this pickle...way too easy it was!
Sent it back
Thanks to all who helped here. I ended up taking it back to Verizon and asking for a replacement. This they did, and even shipped it overnight at no charge (though I had to ask them to do that--they were going to charge me). The fellow at the counter was as perplexed as me. Apparently this is not a common problem.
Hi y'all, i recently within the last month 2 months taken up a very unsual craving for delving deeper into my technology, with that being said. my tab 4 7.0 sm-t230 i Downloaded an app called "lucky patcher" was messing with it, been reading about deoxe(ing) my tablet,it gave me the option to do it for me (usually i enjoy the challange of using a emulated terminal and what not) but every file etc would take too long, and it worked, my daughter ot well over 150 million score on subway surfers etc. i notice my phone sluggish even bein over clocked, I/Os that i did myself, running max cpu and performance i could blabber forever since my 3 kids arnt interested in my newly found hobbie and my husbands a truck driver, i'm getting it out here (i'm sorry but i do need help) so anywyas i decided to kick her into recovery and begin to just manually delete all the dex copied files through TWRP went good till i wetn to reboot after staring at my screen for 3 hours and got threw up on twice from sick babies and i was boot looped. i decide to restore a previous freshly flashed rom/root backup. well they were deleted too. and all i could do was a master re format i think is what i read it was called, and excited to get back and re download everything i notice i now have no OS and no recoveries and TWRP fulll of emptiness. i can play through TWRP i've changed file permissions i've tried everything ive read and tried everything i learned and experianced to fix this issue, and yet stillno idea how to fix this issue..
Now the fun part is my set up. the only pc i have means and access too is my samsung Chromebook, and my tablet, that's it, no phone because my tablet handles everything my little heart can desire.
needless to say, i need some kinda recovery tool kit i can use via my chromebook, that'll allow me to use ADB for chrome (which another question i have is how do i enable my tablets USB debugging if i can't get into the phone?) so toolkit for chromebook for a ADB side load if possible. or some way to do it through my emulated terminal in TWRP,. my minds rushing, i'm confused and my over emotionally stressed female head is killing me without my tablet. (drive to any town where i could use anything but my chrome book. 3.5 hours.
sorry i pray this post doesnt get deleted. I need help because my tablet is my main source of income being in real estate when i'm back in town once a month. never made a page or a forum or anything like this usally google magic does it. but 3 days and countless mind numbing forums i've given in.. please help me! i'll donate pay something idc at this point. -a pissed off irish southen woman on the verge of pms and a meltdown thanks in advance i'll try to reply as fast as humanly possible, ill be up for awhile tonight going through more posts.
0well with a little more tinking around, i think i have found the issue as too why no matter what i do i'm unable to boot a rom/os. mt EXT3 wil not mount my system i'm clueless as to how to fix that at all threw TWRP, anyone have an idea of any kind please? i'm for anything, even if after more attempts and countless hours, i'll record me skipping it across my lake, and we'll all take guesses as too how many skips it'll do. hopefully my dog will fetch it if i throw at the wrong angle. (completely dumb jokes are the only thing keeping me from returning Sain.) we all cant be too serious. please very interested on how to fix this issue tho.
s,
you need to get a custom rom zip onto an sdcard, check development section.
in twrp, flash the rom,
if the rom still doesn't boot, then reboot to twrp again and use the format data option, then reflash rom and try again.
twrp terminal sucks, you can try flashing aromafm https://www.androidfilehost.com/?fid=95916177934547314
this is for the marvell variant, it may work for the msm/qcom variant.
stop using lucky patcher.
m
moonbutt74 said:
s,
you need to get a custom rom zip onto an sdcard, check development section.
in twrp, flash the rom,
if the rom still doesn't boot, then reboot to twrp again and use the format data option, then reflash rom and try again.
twrp terminal sucks, you can try flashing aromafm https://www.androidfilehost.com/?fid=95916177934547314
this is for the marvell variant, it may work for the msm/qcom variant.
stop using lucky patcher.
m
Click to expand...
Click to collapse
Hi, that's where another problem lies within, I have no way of communicating with the phone or being able to do much, considering the only pc/laptop i have access too is my chromebook, and this thing is a ssteaming pile of regurgitated dog bile. if theres one regret in life.. buying this thing.. even dual booted i still can't process the zips or compile them properly, maybe i need to find out how to build a zip file from scratch and comepile the corresponding stuff myself in small hopes it'll work on this chromebook
and yes, never again will I use that. it worked don't get me wrong. but then it decided to deodex my system to oblivion.
s,
hey that rhymed !
your alternative is to use a usb thumbdrive and an otg cable , else nada.
m
moonbutt74 said:
s,
hey that rhymed !
your alternative is to use a usb thumbdrive and an otg cable , else nada.
m
Click to expand...
Click to collapse
I'm gla you have a sense of humor, thank you hun. looks like i'm tabletless until i go back into town in two weeks ): i suppose till then i will tinker with it some more and unlock the universe, or find a way to convert zips that are made for windows or mac and be able to convert it to be able to be used and transfered unto the phone. Chromium os or chrome now has ADB for chrome as an extension but very iffy, has 3 options to screen record/screenshot and terminal. i was able to use vitural box for about 2 hours and force odin to pretend i was on a widnows enough to orignally root, then it crashed my chromebook. Maybe i've gotta achieve 88 mph first to get this thing to work? lol my chromebook "overclocked" 810 mghz.... maxx.... frequency says it can go to 2100... i think if i even try that i'd recreate the "hydrogen bomb"
Here is the current status. Unrooted N7 2012 Wifi that has seen daily use for around 4 years. Never unlocked, newest firmware. Started to act loopy, kid never told me until it completely stopped booting (of course). It boots to the Google screen, goes no further. I go into recovery and try to clear /cache, it will not complete.
Now there is 4 years of stuff on here, never backed up (again, of course) that I would like to get off it. That is all I care about. Spent about 5 hours reading everything to no avail, even got desperate enough the knock on the thing like I read a few people doing. So in short are there any hacks, any "full ota" for the 2012 model like the 2013 one, leaked diagnostic apps, anything? Hell I'm to the point of pulling out the soldering iron if it would help.
Just to stop the usual replies, no, I will not "oem unlock", the goal is to get the stuff off it, I will worry about fixing it after.
baconbacon said:
Here is the current status. Unrooted N7 2012 Wifi that has seen daily use for around 4 years. Never unlocked, newest firmware. Started to act loopy, kid never told me until it completely stopped booting (of course). It boots to the Google screen, goes no further. I go into recovery and try to clear /cache, it will not complete.
Now there is 4 years of stuff on here, never backed up (again, of course) that I would like to get off it. That is all I care about. Spent about 5 hours reading everything to no avail, even got desperate enough the knock on the thing like I read a few people doing. So in short are there any hacks, any "full ota" for the 2012 model like the 2013 one, leaked diagnostic apps, anything? Hell I'm to the point of pulling out the soldering iron if it would help.
Just to stop the usual replies, no, I will not "oem unlock", the goal is to get the stuff off it, I will worry about fixing it after.
Click to expand...
Click to collapse
Bootloader unlock will wipe data. Did you try to connect tablet to pc? If drivers are installed data in internal storage should be accessible. Another option is to look for adb minimal distribution and install it on PC in a single directory. Then if adb is working (adb devices return something) then copy data using adb pull / command.
Sent from my Nexus 6 using Tapatalk
No, ADB is not working.
Finally the damn thing threw me a bone. Every time I would press power+up it would have no log but this time was different. So I let it format cache for 12hrs+ and it did not finish or probably not even try.
Any tricks for this? Have no luck finding any.
baconbacon said:
Finally the damn thing threw me a bone. Every time I would press power+up it would have no log but this time was different. So I let it format cache for 12hrs+ and it did not finish or probably not even try.
Any tricks for this? Have no luck finding any.
Click to expand...
Click to collapse
Can try looking at this https://youtu.be/VJRKuQf0puE assuming that you can boot into TWRP
Sent from my Nexus 6 using Tapatalk
Hjicons said:
Can try looking at this https://youtu.be/VJRKuQf0puE assuming that you can boot into TWRP
Click to expand...
Click to collapse
Locked.
Edit: My phone is miraculously recovered, see last post for details. Big thanks to everyone throwing in suggestions! :highfive::good:
Edit 2: Here we go again... Had my phone set up for a day and after installing the "App Systemizer" Magisk module, the restart upon booting is back. Please help, is magisk causing this??
So, I'm reaching out because I'm now at a loss. I have no other ideas as to how I could fix my phone.
Background:
A few days ago, I was setting my alarm for work in the morning and I noticed the UI was extremely sluggish. I then locked my phone with the lock button and a notification saying "Powering down..." came up and proceeded to shut off. At this point, I knew I should re-flash my ROM/boot.img first. Didn't help, every boot up ended in the same "Powering down..." message and shutting down within 15 seconds of unlocking the device. At this point, I think to fully wipe and revert to stock. Now, I try to install the latest stock OOS via fastboot. Same result as before when I booted after the fastboot install. And this is where it ended... I tried to use the MSM tool and the device went BLACK with no response after that.
What I've tried:
- fastboot
-MSM Tool
- randomly pressing/holding all physical buttons in every order
- leaving the device plugged in to charge overnight
Conclusion:
Any suggestions other than what I've tried would greatly be appreciated. If, by some chance, my phone is truly bricked... would anyone know about whether T-Mobile would replace the device for me if I act clueless as to what happened to my device? lol, I'm on the Jump! plan, so this phone isn't even paid off yet.
Thanks!
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Car Transport in mumbai
Car Transport In Mumbai[/URL]
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Jager said:
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
Click to expand...
Click to collapse
MSM didn't even pick up my device... it said something along the lines of "No communication"
F5:ed said:
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
Click to expand...
Click to collapse
Thanks for the suggestion! Unfortunately, all steps were tried before seeing this post and didn't help.
i7vSa7vi7y said:
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is important... but did not help me... initially.
sanjeev7 said:
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Click to expand...
Click to collapse
Well boys, she's up and running again!
Here's what happened:
- I left my phone on the stock charger (wall-block and cord) to make sure the battery wasn't just dead. This resulted in nothing, still no response from the device.
- Early in the morning, while getting ready for work, I continued to press all physical buttons in any and every order as well as holding different combinations of the buttons. Nothing.
- Gave up, took it off the charger, and tossed the damned thing to the side. I took my iPhone X to work and hated every minute of it lmao.
- I then get off work and decide to mash the physical buttons in a half fit-of-rage and half last-ditch-effort.. and BOOM! The screen flashes with a screen saying the battery is dead in a few different languages.
(I never plugged a device in to charge so fast... lol)
At this point, I decided to fastboot the latest stock OOS (.13) to both A/B partitions and she's like brand new!!!! I spent the day rooting and reinstalling everything today and I'm honestly relieved. :victory: All of my data is lost... pics of my baby sister after just being born and of my fiance But order has been restored.
tl;dr - My phone is fixed, don't ever underestimate the power of button mashing! :good:
..Cory.. said:
MSM didn't even pick up my device... it said something along the lines of "No communication"
Click to expand...
Click to collapse
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
Well, like I said... I couldn't just change modes at will... I was legit stuck with the screen completely off and no response to any physical button being pressed. So as long as switching modes was impossible... so was the MSM tool. I read a F*CK-TON of threads before I posted this, I haven't seen anyone else post about being in my situation of not being able to boot into ANY kind of a mode... at all lol.
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
You'd probably be better off seeking support in the mod thread.
..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Cablespider said:
You'd probably be better off seeking support in the mod thread.
Click to expand...
Click to collapse
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
sanjeev7 said:
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
Click to expand...
Click to collapse
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
F5:ed said:
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
Click to expand...
Click to collapse
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
..Cory.. said:
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
Click to expand...
Click to collapse
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
That systemize tool is not very stable in my experience. There is two location's of system apps in my experience which is most always only about at least half correct a little less than half the time. Is that if you use something like MiXplorer and move the apk into either system apps or priv apps then reboot it is much easier to do than rely on scripts that may not be setup for the device you are using. It shouldn't take any longer than 25.89 seconds to manually move an app.
..Cory.. said:
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Click to expand...
Click to collapse
Download the magisk uninstaller zip , put it on your internal storage
So when magisk modules messing up with your boot
Go to twrp, flash the uninstaller zip , reboot to twrp, reflash magisk and then you're be able to boot again to your rom ..
F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
Sorry, I forgot ur the internet law enforcement. Yes, sir! Please dont shoot! :HandsUp: :ShakingInFear: :Terrified: :NotReally: :WatchOut_InternetBadAss:
Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
The MSM Tool does not fix everything. The 6T I have is brand new was working fine until I installed LOS on A & B and deleted the persist partition. I have flashed the original stock rom as well as 3 other OOS roms. MSM Tool completes the flash no problem with no errors, but on every rom it only makes it to the boot screen and hangs. If the MSM Tool is supposed to fix this, then why isn't it getting fixed? I don't know what else to try to fix? Usually it fixes most problems for me, but on this occasion it is not.
So I just picked up a clean used International 6T. Was going through the root and update (I did the Android 10 update through Oxygen Updater) process and all that, things were going great, then out of nowhere they weren't and I had a complete black screen. I've literally been up all night trying to fix this thing, then again out of nowhere it actually boots, and I was able to use the MSM tool to restore it to that earlier version, then proceeded to get back up and running again.
Thought, phew, dodged a bullet. Nope, after getting rooted and TWRP installed, transferring a bunch of files over from my old SD card and restoring apps through Titanium (again, everything was going great again), and yet now all of a sudden I'm back where it all started earlier, stuck at the 'The boot loader is unlocked and ....' boot screen, it just hangs there, I can reboot into recovery just fine, but no operating system.
I'm literally about to pull my freaking hair out and try and sell this thing if it's going to keep doing this, I've never had a phone act like this one has (prior phone was a Nokia 8, headache). I have friends/family who haven't heard from me in a couple days now because I'm out of a phone and I need to get this thing working stable.
Can anyone help or shed some light on why this has happened again? I didn't update to 10, left it on the last stable Pie (begrudgingly), didn't flash any custom rom or anything, it was restoring most of the titanium apps just fine (some just hang there, not sure what that's about) and now I can't reboot into the os. To say the least I'm beyond pissed and annoyed at how much time I've lost on this thing.
Please please please help if you can, I'm not a newb to rooting (already rooted this one twice) but I don't know what to do at this point.
Thank you in advance, let me know what/if any info is needed.
Edit: I think I know/understand partially that magisk is to blame for this and reinstalling it fixes it, though I just did that through TWRP and it's still stuck on the boot screen.
Edit: Yup, right back where I was, device now shows as HS-USB QDloader..... in device manager. What gives? I have to use the MSM tool again? Why? Why is this happening...I've never had this much trouble with a phone
Try a clean install. Don't root and don't restore the titanium apps. Install them fresh. If your problem persists then it may just be hardware. But something you are restoring may be causing the crash due to the way it is trying to restore the app data.
I had similar problems. For me it was my self-created magisk module that ran without problems under Android 9. As it seems, there are also problems with modules from the magisk repo.Could be the case with you.
Clean install of the apps, after doing another MSM restore? And trust me, I won't be installing ANY other magisk files other than just the magisk.
Is there any way to save all the work I just did though without having to start over again via MSM? I'm guessing not....sigh
Grrrr...ok before the MSM tool worked, the phone was just unresponsive. It's back at that stage where the MSM tool times out and doesn't do a darn thing to save the phone.
I swear this thing is all over the place, now I'm in the bootloader, yay. I guess I'll try a wipe in TWRP and start over.
One thing I forgot to ask, is magisk the ONLY option available for root?
The question would be, how did you root.
TWRP is not working when you don't follow the instructions which involves OldKeysFlasher.zip.
Otherwise you have to flash Magisk with a patched boot image, be sure uyou have one for OOS 10 Stable.
The correct comands are here: https://forum.xda-developers.com/showpost.php?p=80638253&postcount=2853
jgro1976 said:
(...)
I'm literally about to pull my freaking hair out and try and sell this thing if it's going to keep doing this, I've never had a phone act like this one has (prior phone was a Nokia 8, headache). I have friends/family who haven't heard from me in a couple days now because I'm out of a phone and I need to get this thing working stable. (...)
Click to expand...
Click to collapse
I hope that anger is directed towards yourself because you can't hold the device or its manufacturer responsible when you get into the flashing game.
If you had done some reading, you'd know that TWRP doesn't play well with Android 10 and upgrading from 9 takes a very specific procedure. There's a dedicated thread for it even. Happy searching. You may also want to take a peek at my posting history for some pointers.
One more thing, are you absolutely sure it's an international device and not a converted T-Mobile version? Because that can cause a major amount of troubles.
Wrapped with delicious Fajita [emoji896]
I'm well aware it's my own doing, part of the frustration is having too many sources of information all claiming they fix a 'thing'. There's the "fix it with fastboot" camp who doesn't like MSM, and there's the MSM camp that helped me the first time. Phone is currently dead/black screen, going to try MSM again, and will check out the info you provided.
And I'm sure, double sim tray, does not flash a pink tmobile screen and/or no branding of any kind on the phone related to tmobile.
jgro1976 said:
And I'm sure, double sim tray, does not flash a pink tmobile screen and/or no branding of any kind on the phone related to tmobile.
Click to expand...
Click to collapse
Just remember that dual SIM trays are easy to get and if it's been converted from TMO to international version there will be no indicators till n you try to flash A10. Best bet would be to treat it as a converted TMO, if it is the info in recovering and flashing a TMO device will work and if it's truly an international version it will work too. Best of both worlds.
I'm 99% certain, by the label on the box, etc. Regardless, I'm to the point now that I can't even get it to boot to TWRP after 'fastboot flash boot twrp.img', it just does nothing and when I try to boot to recovery it bounces right back to bootloader. I've been trying all afternoon to fix it with no luck.
Was android 8/oreo good on these phones? That was my sweet spot and I'm just gonna downgrade if possible, there's too many things I don't like about 9 and 10.