Develop Bugs

EVO on life support

Dear XDA Community,
This post will be as detailed as possible for those who enjoy detail.
It’s about the problems my EVO has been experiencing over the past 3 months and, after trying to fix the problems though IRC it seems that the attention should be brought to the forums for a larger audience. It was 3 months ago when I flashed a rom ( cannot remember the rom ) and my EVO took a turn for the worst.
What Happened :
When the rom was flashed and booted for the first time everything seemed normal but, the rom started to freeze at random. At first I though it was a normal process due to new ROM’s installs but, it kept repeating it over and over until it went into a boot loop syndrome.
Prior to these problems I did my daily clean/wipe dalvik rituals for ROM consumptions.​
After 15 - 30 boot-loops my battery dies and the crusade begins.
I begin looking for another ROM to flash, to rid the sickness the previous ROM infected my EVO with. I installed my favorite (SalvageMod) and, the problems began to show. Salvage installed perfectly fine (as always) but, my phone started to lag, the speed was reduced to about 35 - 50%. It’s noticeable big time. The camera stopped working and everything seemed to be falling apart.
(RECENT)In panic I started looking for ways to RUU so I can avoid any other problems. This is when I noticed that usb was not accessible. I couldn’t mount my device; [CLICK HERE FOR VIDEO], so I used a SD card reader to RUU my phone and get it back to stock.
Phone is back on stock settings but, no root and, without usb support revolutionary.io is lightyears ahead of my time.


Problems :
Not mountable through usb cable [SD Card Reader option / Software Error]
System lag noticeable slower (BestBuy rep even confirmed its unresponsiveness)
Device will not charge when on [Either mount / Software Error],
Camera problems.
[Click Here For Second Video]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So can you guys help a member get his EVO back in business, my wallet would greatly appreciate it.
Thanks,
samthewildone
Aspiring Mathematician

​

Well, the easy way out is that now that you're back on stock and a rep has agreed the phone is not working properly and you have no USB, trade it in

I would right click on that device and uninstall the drivers. then hook the phone up to the PC and see if it automatically installs the correct drivers or find better drivers.
This may have been covered, and it looks like there's a lot more going on then just drive issues, but to get this phone into a state in which you can root it and wipe it again, you need to eliminate that variable.
Not saying that the USB drivers are even an issue, but its something worth exploring first and foremost.

Tried that, as in my thread. I uninstalled and reinstalled drivers and, it just keeps showing what that picture shows above. The phone isn't damaged but, the software is borked due to a bad bad kernel or ROM flash.

Not a solution to your problem, but if you are still s-off then you don't need Revolutionary. You can put a PC36IMG of a (reliable, ie Amon Ra) recovery on your SD card. From there you can wipe thoroughly and try flashing something else.
Unfortunately it seems like some sort of hardware failure, so the only fix could be getting a replacement.
Supersonic Evo 4G | MIUI | Tapatalk

Seems like you've gone through the same steps I would've gone through to fix it. Apart from the possible driver issue the phone should still charge when plugged into a wall charger. The fact that it doesn't, in tandem with the inability to access USB via computer, tells me that most likely you've got a hardware failure. Take it to Sprint and get a replacement. Problem solved.

GT-P5210 stuck on boot screen after trying to root

EDIT March 11, 2016: Finally found a solution and no data was lost!
See post #5.
(is there no way to indicate on the thread that this is solved? I don't know exactly how it works on this forum...)
---------------------------------------------------------------
Hi!
So I've posted my problem on another forum but didn't get any reply, and I just realized I might have more chances to get faster replies on here.
Well, to make it short, I've tried to root my mothers' Galaxy Tab 3 (GT P5210), and as I've already rooted several devices (including another Galaxy Tab) without any problem, I didn't bother saving all the data on it... I'm afraid this was a big error.
I decided to root because it was getting stuck sometimes because of too many things running at a time in the background, and it made the tablet unusable until I reboot it. I wanted to install Greenify and make it work alone so my mother doesn't have anything to worry about but play without the tablet getting stuck. But I needed to root to use Greenify at its best...
As I've rooted several phones before, I know rooting doesn't wipe any data, unlike flashing seems to do. So I wasn't afraid of doing it.
I've followed this tutorial after installing the drivers.
Everything seemed to work correctly, Odin did what it had to do and it succeeded.
Though, now I can't turn on the tablet anymore: if it's turned on and that I press and hold the Power button, the "Samsung Galaxy Tab 3" screen shows up. But it doesn't move, it just stays here and does nothing.
I can turn it off, and try again, but the result is the same.
On the Internet I've read that charging it to 100% could solve the problem, but it doesn't seem to do anything as it was plugged all night and it's the same.
Now I've tried all combinations of buttons, because it was said that a second solution was to wipe the cache partition. But the only combination that works is Volume Down + Power, which brings the Download mode I had to get through in order to run Odin.
I've found this tutorial on here, but I don't even know if the correct word for my situation is "brick". And like many things I've found on the net, the tutorials for unlocking the tablet are for the tablets that have been flashed. But this is not what I wanted to do and I hope this is not what I did. And it doesn't inform if I'll lose data or not... which I'm afraid of.
I made the error of not making any backup before starting the process... I seriously hope nothing is lost.
Is there a way I can restart the tablet correctly again, even if I have to unroot, without losing anything?
Thanks by advance!

(sorry for the double-post)
No one?
Please, at least give me a clue on what I should do, or if there's hope to get back the data from it.

Joey79100 said:
(sorry for the double-post)
No one?
Please, at least give me a clue on what I should do, or if there's hope to get back the data from it.
Click to expand...
Click to collapse
I don't know if you've lost data or if this method will wipe data, but it's what I used to root stock kitkat
Method
Also - I seem to remember that you should uncheck auto reboot, and after flashing is finished power off and back on
Good luck

Thank you for your answer.
The thing is that I've already gone through some steps of the tutorial I linked in the OP (until step 10 / step 11), and when the tablet was meant to reboot, it got stuck on the "Samsung Galaxy Tab 3" screen. I can turn it off and on, but it won't go further than this screen.
I can still bring up the Download Mode (by pressing Volume Down + Power), but there's no way to bring up anything else. Even the debug menu with Volume Up + Power (though I don't know if it was even available this way before trying to root). It will just load the boot screen and nothing more.
I'd try something with the Download Mode only if I can be sure that no data will be lost. If it may erase data, I prefer not doing it and to find a way to get it back before anything else.
Do you know if there's some way to access the memory?

Okay okay... I've struggled a long time with this problem, brought the tabled to a local repair shop but didn't find anything that couldn't risk any data loss... And finally I've found something, so I'll post my solution in case other people have the same problem.
Remember, I could only boot the tablet in Download mode. Every other button combination led me to the boot screen.
The problem was indeed the cache, that I needed to wipe, but without being able to access the Recovery mode there was no way to do it.
-------------------------------------
Solution:
First, I downloaded Odin 3.07 from somewhere else than from the link given in the tutorial (quick search on Google), because I had to untick Auto-reboot. Actually I'm not sure this is needed, but it worked for me with it unticked (while the version of Odin given in the tutorial doesn't let you untick it).
Then, download TWRP for P5210 (a quick search through Google led me to this ). Take out the .tar file from the .zip, but DON'T try to extract anything from the .tar file.
(basically, we'll "install" it onto the tablet using the same method as described in the tutorial)
Boot the tablet in Download Mode (Volume- and Power), choose Continue (Volume+ IF I remember correctly, but it's written anyway), then plug the tablet to your computer.
Run Odin, untick Auto-Reboot (as said before, not sure it's needed, but oh well, it worked...). Then click PDA, select the file you've downloaded (for me it was twrp-2.8.6.0-p5210.tar).
Then press Start, and wait (I waited approx. 2 minutes) until Odin displays "PASS!".
Now unplug the tablet, and turn it off.
Turn it on with Volume+ and Power, this time it will bring you to the TWRP menu (it asks to stay in Read-Only mode or not... choose no). Go to Wipe > Advanced Wipe, and tick Cache ONLY. "Swipe" to start the operation, wait, wait... then, once it's completed, press back until you go back to the main menu, press Reboot > System (then Swipe).
Now the tablet will boot normally. It won't be rooted, but at least it will work again, and fortunately, without any data loss.

You couldn't flash super user from TWRP?

I have the same issue, my Tab 3 is stuck on the Samsung logo.
And the Odin is stuck on the file mentioned above.
Can someone please help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Update annoyance

Would someone be so kind and help me to stop this annoyance. I have a Gen 1 AFTV box. Fire OS 5.2.6.2 (587700720). Twrp version 3.0.0.7
The whole problem is always finding the AFTV on the Twrp menu screen after returning to it after some time.
When I reboot and see the boot menu, the boot menu always has "boot normally" highlighted and a normal boot process happens. It appears to me there is a download in the system which gets scheduled for install and on boot the system gets put into recovery mode and the update doesn't go into effect.
So here is my question. How can I make this update go through? I have done all the network command statements into my router. I have ran commands through ADB. I can delete the download but it just keeps coming back.
How can I install the update through TWRP. I don't care if I lose the unlock bootloader and all that. This issue is no big deal for me but my wife . . . Oh gawd. Please help. Happy wife, happy life. She can't use the box if it is on the recovery menu.
Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-P905V using Tapatalk

Gonkulor said:
Would someone be so kind and help me to stop this annoyance. I have a Gen 1 AFTV box. Fire OS 5.2.6.2 (587700720). Twrp version 3.0.0.7
The whole problem is always finding the AFTV on the Twrp menu screen after returning to it after some time.
When I reboot and see the boot menu, the boot menu always has "boot normally" highlighted and a normal boot process happens. It appears to me there is a download in the system which gets scheduled for install and on boot the system gets put into recovery mode and the update doesn't go into effect.
So here is my question. How can I make this update go through? I have done all the network command statements into my router. I have ran commands through ADB. I can delete the download but it just keeps coming back.
How can I install the update through TWRP. I don't care if I lose the unlock bootloader and all that. This issue is no big deal for me but my wife . . . Oh gawd. Please help. Happy wife, happy life. She can't use the box if it is on the recovery menu.
Please help.View attachment 4524977View attachment 4524978
Sent from my SM-P905V using Tapatalk
Click to expand...
Click to collapse
This is a safety process with TWRP if i understand correctly, it wont let the system update and wipe your root/TWRP out.
Why would you want to lose Root/TWRP ? these Amazon Fire devices are no longer rootable with current firmware.
To have one is getting more rare everyday.
I seen a Gen2 box for sale for £180 UK on ebay a few days ago.
You would be much better off keeping root/TWRP but disabling updates, using this guide:
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Basically doing the following:
Your Fire TV must be rooted. Otherwise, use one of the other methods to block software updates.
Connect to your Fire TV via ADB
Run the command: adb shell
Run the command: su
(Be sure to select “Grant” if your Fire TV prompts you for superuser access.)
For Fire OS 5 (version 5.0.0 and up), run the command:
pm disable com.amazon.device.software.ota
This should sort out the issue of the FireTV idling then deciding to try and update, bringing you to the TWRP screen.

Thank you sconnyuk. I thought this would be the recommended action. *SIGH. LOL
I swear I have done this multiple times but it is easy and needs done before moving forward, and maybe I'm not as smart as I think I am and this will be the fix.
Also, being I had considered this box dead (past posts) and moved on by buying new. It is nice having old school V.1 [emoji3] v
Thanks for responding and popping me into gear. I'll know soon enough if it works.
Best regards
Sent from my SM-P905V using Tapatalk

Yeah, that was the fix. I had done this in the past but apparently not recently enough.
Moral to this: sometimes you just have to bite the bullet and admit you didn't follow all how-to's from the beginning.
Consider this matter closed. Thanks

i had my firetv 2 box doing this exact same thing around the time of the 5.2.6.3 OTA they were sending out, it had a message and countdown timer (60 seconds) that would pop up often and if not interacted with it would attempt to upgrade. of course i didnt initially notice the message due to it stalling via TWRP.
in device settings it did pass a version check that i had disabled, something re-enabled it. i disabled it again and it has remained disabled since. just goes to show amazon can control things via their unknown services...
enforcing firmware flashing is never a good idea, who is at fault if the owner removes power from the firetv but hadnt seen its message?

What's the Expected Level of Support from Google Support?

TL;DR: Really three questions
What kind of effort can/should we expect from Google Support?
Is there an escalation support path for real troubleshooting?
What's the best course of action to attempt to determine root cause?
The Setup
While driving to work this morning my stock Pixel 2 XL (locked, not rooted etc.) entered a boot loop then settled on this error (image):
Code:
Android Recovery
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device
I couldn't do much since I was driving but I selected 'Try again' a number of times when traffic stopped before giving up.
When I arrived at work I continued fiddling with it for a few hours, select 'Try again', power off, power on, fastboot etc.
Although debugging was enabled prior, could only see a device in fastboot or when in adb sideload mode.
When I attempted to go into recovery mode it would just take me back to the same screen.
I just assumed I'd have to wipe and start over
About 2 hours ago I was getting ready to factory reset/wipe the phone but thought I'd try fidgeting once more like I had been doing all day.
I don't know what I did but it booted to a screen displaying this error:
Code:
No valid operating system could be found.
The device will not boot.
Visit this link on another device
g.co/ABH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then the phone turned off.
I turned it back on, and I don't think I did anything differently, and suddenly it booted normally.
The only unusual thing I saw was a notification stating that Android was finishing up system updates - or something to that effect.
With the phone up, I backed up what little data had not yet been backed up, booted into safe mode then booted back into normal mode.
So far so good...?
My Complaint
I contacted Google support earlier in the day and the experience was just sad.
The person said that I would need to factory reset my phone.
But then quickly said that before doing so I would need to backup my data.
So I asked "How?" and they said "plug it into your machine and you can see it on your computer"
I went along with their script, specifically asking for detailed step by step instructions on what to do, how to do it and what to look for.
When I said it didn't work they said I would have to take it to a repair center first to get it repaired then once fixed I could back it up then perform the factory reset.
*smh*
Later, about 2.5 hours ago now, once the phone came back up, I backed up what little data needed backing up and contacted support a second time.
This time, the person said: "Now, if we need to restart the phone and check if the boot looping is triggered or not. If it does, then we need to do some troubleshooting steps here."
So I naturally asked "What are the troubleshooting steps if it enters into that state again?" but they couldn't provide any.
I just want to know root cause. Since this was an OS boot problem, surely there's a log somewhere that might reveal what happened or at the very least provide a clue. Right?

Question Missing second sim ( K50G / F4 GT )

I am very sorry to hijack a different device's forum, but XDA mods have neglected the F4 GT and we don't have a device forum of our own.
Hopefully the devices are similar enough (that being a modern Qualcomm SoC and running A12 based MIUI13) that you guys can help me solve my issue.
What happened is that I've been trying to enable voWiFi and make it stick while on airplane mode (WiFi re-enabled of course).
After a lot of back and forth with my carrier they did a kind of hard reset on my phone line. I didn't get 4/5G service for a long while, even after restarting multiple times, so I went to the test mode tool (dialing *#*#4636#*#*, which I've done several times before) and tried changing the preferred network type.
Out of desperation, after I nearly selected every other option, I selected TDSCDMA only, which is the only thing I've done differently compared to other times, and I got 4G and 5G working right after my phone did some funky radio reset (maybe a warning sign), but still no voWiFi. Decided to restart and that's when I lost the second sim slot, along with the voWiFi toggle, though it seems to connect just fine now.
Setting the preferred network type to anything else didn't solve the issue, even after several restarts the second SIM is still nowhere to be found.
After that happened the CIT menu shows both IMEI numbers as the same. (Had to censor it, but they are indeed the same).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've read that a factory reset might solve this, but I'd prefer another solution in the meantime. I will factory reset when an AOSP based ROM is released but I don't really want to go through the huge trouble of setting up my device again if I can avoid it.
All other suggestions involve messing with some partitions on TWRP, and while I'm unlocked, rooted and have TWRP installed I don't see why I should go that route when I was using built in tools of Android/MIUI. I'm not entirely aware to the ways that test tool works, but I can't see any where it corrupted anything besides a configuration file somewhere, certainly not messing with any other partitions' files.
I've also read that some AT commands might fix this without messing with anything, but I can't wrap my head around what I have to do (I do know where I can issue those commands, just not the commands themselves and what each does). The page I read mentions it's a temporary fix and it doesn't persist after a factory wipe, but that's kind of what I need right now.
While I don't currently own 2 sims, I was going to get one soon, and if this is a deeper issue, I'd like to know ASAP so that I can restore my phone as it came from Xiaomi and send it to warranty.
And yes, I tried inserting my current SIM in the second slot and it's not detected at all.
Is there some config file I can delete/modify that will solve this? I've already re-flashed my current ROM (as it was also suggested somewhere) and nothing happened. I haven't tried flashing through fastboot, but I don't think it's going to be different, right? Is there something related to this that fastboot would flash that a recovery zip wouldn't? Also, not going to have access to a PC where I could do this for a while (I have a Ryzen PC and it doesn't play well with my phone/fastboot).
Hope you guys can help me.

Oh, no one? Maybe I should post this again on a more general sub-forum.
Or would it be better if it was moved by a moderator?

If you don't want to factory reset everything, why not flash system partition then only and keep app data?

dagoban said:
If you don't want to factory reset everything, why not flash system partition then only and keep app data?
Click to expand...
Click to collapse
Well I tried that and the problem persists; that's one of the many reasons I suspect it has something to do with some config file on the data partition.
I'm thinking on doing the factory reset anyway and try a GSI ROM through DSU, MIUI really gets to my nerves, though I'm still a bit on the fence

Reflash the modem files, that should fix it. If you make changes with QPST it also changes the modem partitions.

Can a moderator move this to the freshly created ingres device forum please?