Related
I was trying to root my phone using unrevoked 3.32 and during the install it, it stop with a back up CID error missing or something like that. i checked to see in hboot if it was rooted with it showing s-off, and it was but recovery still showed the regular triangle red error. So i restarted normally and tried into install terminal emulator on the phone and thats when it first started vibrating 5 times, then go blank with a green led flash. the phone will boot normally usually be able to use it for a min or less then it will repeat with the blank screens. After checking back into hboot it now shows that its unrooted with s-on. Now i also have problems with the usb/sdcard.
Things i have done to get it back to normal:
- hard reset using clear storage.
-Checking in the SD storage menu i could see it wasn't reading the SDCard so i restarted it in bootload and thru fastboot typed: fastboot oem enableqxdm 0.
- flash through bootloader this file : 3.70.651.1_PC36IMG.zip
After flashing it still takes multiple battery resets to finally get it through the first start up menu and then to the regular home screen. Seems to read the SDcard fine but when connecting the usb from wall charger or PC it doesn't recongnize at all.
The phone is 4 days old and seems to be back to stock except it still vibrates and goes blank with green led flash and it wont recognize charging/pc connection. Will i have any problem if i just go back to sprint and say i want a new one its not working right?
Phone info:
Baseband: 2.15.00.11.19
kernel: 2.6.32.17-gee557fd
Software: 3.20.651.1
PRI: 1.90_003
PRL: 60676
Hardware: 0003
HBOOT-2.10.0001
strdrk1 said:
I was trying to root my phone using unrevoked 3.32 and during the install it, it stop with a back up CID error missing or something like that. i checked to see in hboot if it was rooted with it showing s-off, and it was but recovery still showed the regular triangle red error. So i restarted normally and tried into install terminal emulator on the phone and thats when it first started vibrating 5 times, then go blank with a green led flash. the phone will boot normally usually be able to use it for a min or less then it will repeat with the blank screens. After checking back into hboot it now shows that its unrooted with s-on. Now i also have problems with the usb/sdcard.
Things i have done to get it back to normal:
- hard reset using clear storage.
-Checking in the SD storage menu i could see it wasn't reading the SDCard so i restarted it in bootload and thru fastboot typed: fastboot oem enableqxdm 0.
- flash through bootloader this file : 3.70.651.1_PC36IMG.zip
After flashing it still takes multiple battery resets to finally get it through the first start up menu and then to the regular home screen. Seems to read the SDcard fine but when connecting the usb from wall charger or PC it doesn't recongnize at all.
The phone is 4 days old and seems to be back to stock except it still vibrates and goes blank with green led flash and it wont recognize charging/pc connection. Will i have any problem if i just go back to sprint and say i want a new one its not working right?
Phone info:
Baseband: 2.15.00.11.19
kernel: 2.6.32.17-gee557fd
Software: 3.20.651.1
PRI: 1.90_003
PRL: 60676
Hardware: 0003
HBOOT-2.10.0001
Click to expand...
Click to collapse
That's weird. I'm pretty sure the vibrate 5 times and green blinking led indicates that the phone is in diagnostic mode. I'm not sure how to remedy the situation, I would've suggested a PC36IMG back to stock, but you already tried that. I would try taking the battery out for an hour or more (i've read of people being stuck in diagnostic mode, and leaving the battery out for a good length of time fixed it, i think) then try booting up, and seeing if it works. If not, to answer your question, as long as the bootloader shows S-on, you will have no problems taking it back to Sprint. You need to make sure you have no 'evidence of rooting' on your sd card, just to make sure that the sprint tech doesn't see anything on there. Good luck.
I formatted the sdcard, but it seems to be creating these files QXDM_some numbers.dm is this normal or any indication of rooting the phone.
Sorry to be the bearer of bad news but I had the same issue and eventually gave up after 3 solid days of working on it. You name it, I tried it. Had to get it replaced.
Something about unrevoked and my old 002 phone didn't jive together and the root aborted at an unrecoverable stage. No sd card mount, no adb, not even able to connect via usb, so running an ruu or new pc3600img wasn't an option.
As for the 5 buzzes and shut down after a min or so... Your guess is as good as mine. You can put it in diagnistic mode with the arrow up/power button boot, but thats 3 buzzes not 5.
Wish I could offer some actual help :/ Let us know if you find a fix.
Oh, before I took it back in I did a hard reset so it would reboot before they could get past the setup menus and see the superuser permissions app. Not that they'd care, but just in case.
I have just returned my EVO to sprint for this same problem. He told me it was a common problem. I get my new on today. They could have cared less that it was rooted, he told me it did not matter.
derekstory said:
I have just returned my EVO to sprint for this same problem. He told me it was a common problem. I get my new on today. They could have cared less that it was rooted, he told me it did not matter.
Click to expand...
Click to collapse
I ended up exchanging mine also. The lady really could have cared less. i wish i would of known cause i spent some time trying to get it back to normal. My sister also ended up exchanging hers because she got the white one and wanted the black one instead.
thanks for any help and replies.
I too had the same problem. It all happened when I was trying to flash cyanogen 7 RC2, I wiped all data, and all seemed fine. I rebooted and it went right to the bootloader and I noticed I was S-ON. Tried to re-root, and run a RUU. I did actually get it to boot to sense, but it froze and then I got the buzzes, and the green lights. I went to sprint since I have insurance. They checked it out and then an hour later, they gave me another one.
My EVO is currently stuck in the same state. I have spent a huge amount of time working on it, and have some information. I'm just dumping as much as I can remember in to this post, so excuse the lack of organization.
Before I go any further - I have not been able to fix the issue!
My phone was about as stock as possible when I took it to the Sprint store. They ordered me a new one and gave the broken one back. I have taken a few more risks now that my new one is on the way.
The initial problem started after flashing MIUI recently. The phone booted normally, but I noticed that the SD card was inaccessible. I would bet that the phone was refusing to charge over USB at this point as well, as that issue goes hand-in-hand with the sdcard problem.
The sdcard and its contents were fine. I later made a backup of the card and lost nothing.
Symptoms, high level info:
Phone immediately vibrates 5 times and begins flashing a green indicator, screen black at power on
Under unknown circumstances, the phone will display the white EVO boot screen before exhibiting the above behavior
Cannot exit this mode unless phone is unplugged and battery is removed
Bootloader can be accessed by holding volume down and power when starting fresh
SD Card is accessible in bootloader - indicates the problem is not purely hardware related
Fastboot can be used to temporarily (1 boot) gain access to sd card
Phone can be flashed with official PC36IMG
Phone can be set into RUU mode and flashed with official RUU
Official update.zip can be flashed from stock recovery
Qualcomm diagnostic tools can be used
Phone will remain in the installed OS for a very short amount of time
Bootloader shows S-ON, 'fastboot oem boot' shows Super CID and CID=111111111 instead of SPCS_001
Because one of my initial ideas was to flash a stock PC36IMG from the bootloader, I lost access to a custom recovery very early in the process. Other users may have better luck if they do not immediately flash a stock recovery.
Flashing PC36IMG is accomplished as usual. Vol- + Power.
To temporarily enable the sd card, disable Qualcomm Download mode:
Boot into bootloader
Wait for it to scan the SD Card
Select Fastboot (Power to select)
Plug into computer
Open a command prompt and ensure you have the fastboot executable
Command: fastboot oem enableqxdm 0
Exit fastboot
Select Clear Storage and select No to reboot OR
Select Recovery
The phone will boot into the OS. Under unknown circumstances, the phone will reboot. The amount of time can vary quite a bit. Enabling Airplane mode does not help. Using diagnostic tools to put the phone in Offline mode does not help.
If you would like to use Qualcomm diagnostic tools, the phone will have to be in diagnostic mode, rather than Download mode. The above steps will get you most of the way there, with the added annoyance that the phone will not enter proper diagnostic mode if left plugged in the entire time.
To ensure diagnostic mode correctly enables (or rather, that download mode disables):
Perform the fastboot command to disable qxdm
Unplug the phone
Navigate back to the bootloader, select Clear Storage
Select No (Vol-) to reboot
The white EVO boot screen will display
The screen will go black before the Sprint/4G animation plays
Plug the phone as soon as the white screen disappears, before the Sprint/4G animation
The phone will display in QPST Configuration without saying *Download* everywhere. The phone number will be incorrect, but that value is actually stored as a Directory ID in the NAM. In other words, it's okay.
The QPST Service Programming tool looked like a good place to start. If you would like to look at the configuration options for the EVO, you can start an offline connection using the profile "FFA/SURF QSD8650 Rev 2.0".
Note that the phone will always reboot after writing any values to the phone. This means you will have to pull the battery, unplug it, boot into fastboot, disable qxdm, boot into the OS each time.
You will need your MSL code for many of these applications. You can get it by calling Sprint and asking. They will not provide the code through email.
I can confirm that at least some changes in the Service Programming app will stick. I changed the banner, under the Display tab, to "Brick" (from Sprint), and it showed up in the Notification dropdown.
The NV util can read the values from the phone correctly.
QXDM can issue command to the phone.
ADB will not work. This limits the ability of tools like unrEVOked to do whatever they do. Getting ADB to work could be useful. Note that I did re-enable Debugging in the Setting->Applications menu to no avail. I believe this is a general side effect of this problem and perhaps a key symptom.
The bottom line is that I have run out of ideas. I have not found a setting in any of the QPST or QXDM tools that indicate this mode can be turned off. I have a hard time believing that there is some permanent switch in the Qualcomm SOC that says "always boot into this mode forever", but who knows.
Any suggestions would be great.
To summarize, I have installed a stock PC36IMG, update.zip, RUU. I have access to almost any setting in the phone, but cannot write to NV because it's in the S-ON state, which limits certain fastboot wipe options and the ability to push new images to system partitions from fastboot. I can, in theory, use the QPST Download software to move images if I can find one that might work.
When is the last time you tried running a 3.70 PC36IMG RUU?
I ran the 3.70 RUU literally minutes ago.
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Apparently still not taking?
That's the thing - it *is* taking. Whatever is triggering this mode is not being reset by the RUU (or any other full clear/flash technique).
I have a dump of the NV memory, but I want to run through it with a hex editor to make sure it doesn't have anything that would identify my Sprint account or identity before posting it.
SLOSifl said:
That's the thing - it *is* taking. Whatever is triggering this mode is not being reset by the RUU (or any other full clear/flash technique).
I have a dump of the NV memory, but I want to run through it with a hex editor to make sure it doesn't have anything that would identify my Sprint account or identity before posting it.
Click to expand...
Click to collapse
Ah I see, and good precaution.
My ESN is in the qcn file, and I assume my MEID is as well. I will try to zero them out if I can find them all.
If my phone's ESN is 12345678, then it is in the qcn file as 78 56 34 12.
Does anyone else happen to have a known good QCN? Maybe I can compare them side by side to locate the differences. I suspect that there will be a lot of them, but I can eliminate most of them pretty easily.
While I work on the file (and debate whether or not it's safe to post), here is some information from the NV dump:
Code:
File Version: Major 2, Minor 0, Revision 0
File Summary:
Phone Model: 16 [FFA/SURF QSD8650 Rev 2.0], Configuration Name: default, Total NV Item Count: 1650
Phone Model 16 [FFA/SURF QSD8650 Rev 2.0] Configurations:
Configuration Name: default
Mobile Properties:
ESN: 0xMASKED
Phone Model: 16 [FFA/SURF QSD8650 Rev 2.0]
NV Major: 0
NV Minor: 0
SW Version: 8650B-SDCAPLYM-324026
Client Name: QPST Software Download 2.7.0.362
Code:
Feature Mask:
...Removed for brevity....
Total Set Bits: 108 of 432
Without bothering to specify all the set bits (although there are some interesting ones like "Bit 306: F_UI_GOOFY_MENU_BIT"), maybe someone can confirm that 108 or 432 is close to correct.
I loaded up a nv.img from a nandroid backup I took the day this problem happened (before flashing a ROM). I suspected that the nv.img and the qcn I just pulled should both represent the same general memory in the phone.
The image is...definitely an image. Exactly 640kb, tons of empty space and apparent padding. Much different in overall layout than the QCN, and no trace of my ESN. However, I was able to locate the GPS URLs in both files. While not even close to the same offset in the file, that small section of similarity indicates that the same memory was probably accessed.
Unfortunately I know of no way to push the nv.img to the phone in its current state. If I were able to get the nandroid backup's nv.img onto the phone I could at least eliminate the entire NV memory as a variable. If it fixes it, then awesome, and if it doesn't, then I can ignore the file entirely.
Here is the QCN file with my ESN removed. There may be other private information in the file, but at this point, Sprint is ordering me a new phone, and gave me this one back, so I don't know if they can really do anything about this.
http://rapidshare.com/files/455015717/public.qcn
My enthusiasm toward poking around this file is dropping off pretty quickly since I no longer believe this is where the problem lies.
I had the same thing happen to my EVO last week. Pretty much the exact same symptoms as you. I was able to get the RUU to run, and return my phone back to stock thinking this would fix the problem. I can boot into Sense, but the phone will shut off and do the 5 vibrate thing within a couple of minutes.
I took it into the Sprint store, and the rep told me there is nothing they would do and they would not replace my phone. He assumed it had been rooted (which it had, but I returned it 100% to stock before taking it in), but I have also read of this same thing happening on unrooted phones. I plan on calling Sprint and/or HTC directly to try and get the phone replaced.
From what I've read, it kind of sounds like this is a hardware failure. Possibly something in the internal memory or RAM. Of course, this is just mostly a guess I have. It seems this happens to unrooted phones, but is more common on rooted phones, possibly because of all the flashing we do.
Like I said, it's just a guess of mine, but it kind of makes sense. I wish I could be more help, and I'll definitely be following this thread because this seems to be a fairly common problem with EVOs and Incredibles that nobody has seemed to figure out yet.
hello,
the problem is heat.try to use your evo on the AC vent in your car with ac on you will not get reboot or eny shut down than try to use with out ac...
whenever internal temp goes more than 38C the evo goes off 5 vib. and flashig..
i spent long time testing this so i almost 100% sure that heat is the problem with my evo...
i dont know if there is a way to change the seting on shut down due to heat but it mey be...
adasio said:
hello,
the problem is heat.try to use your evo on the AC vent in your car with ac on you will not get reboot or eny shut down than try to use with out ac...
whenever internal temp goes more than 38C the evo goes off 5 vib. and flashig..
i spent long time testing this so i almost 100% sure that heat is the problem with my evo...
i dont know if there is a way to change the seting on shut down due to heat but it mey be...
Click to expand...
Click to collapse
I was never able to fix mine, but before getting it exchanged i let it sit all night with the battery out and would have the same results. So i know mine wasn't overheating.
strdrk1 said:
I was trying to root my phone using unrevoked 3.32 and during the install it, it stop with a back up CID error missing or something like that. i checked to see in hboot if it was rooted with it showing s-off, and it was but recovery still showed the regular triangle red error. So i restarted normally and tried into install terminal emulator on the phone and thats when it first started vibrating 5 times, then go blank with a green led flash. the phone will boot normally usually be able to use it for a min or less then it will repeat with the blank screens. After checking back into hboot it now shows that its unrooted with s-on. Now i also have problems with the usb/sdcard.
Things i have done to get it back to normal:
- hard reset using clear storage.
-Checking in the SD storage menu i could see it wasn't reading the SDCard so i restarted it in bootload and thru fastboot typed: fastboot oem enableqxdm 0.
- flash through bootloader this file : 3.70.651.1_PC36IMG.zip
After flashing it still takes multiple battery resets to finally get it through the first start up menu and then to the regular home screen. Seems to read the SDcard fine but when connecting the usb from wall charger or PC it doesn't recongnize at all.
The phone is 4 days old and seems to be back to stock except it still vibrates and goes blank with green led flash and it wont recognize charging/pc connection. Will i have any problem if i just go back to sprint and say i want a new one its not working right?
Phone info:
Baseband: 2.15.00.11.19
kernel: 2.6.32.17-gee557fd
Software: 3.20.651.1
PRI: 1.90_003
PRL: 60676
Hardware: 0003
HBOOT-2.10.0001
Click to expand...
Click to collapse
It's bricked. Happened to me when I tried to fix a problem with my phone not mounting the microSD card to any computer (got error message back on a Windows computer saying that the device wasn't recognized). You could probably try to flash the PC36IMG.zip file again from the bootloader, this time without all the addenda at the beginning (if you did that already, the nevermind).
My guess: pray that Sprint doesn't see any evidence of root. If you RUUed back already, they may not see it. You're probably in better position than I am, since the brick happened before I could RUU back with a PC36IMG file (and thus Sprint could see the root. At least Asurion doesn't seem to care about root, as long as I say nothing about it).
Hi all,
I've a samsung S4 mini (i9195) and I want to boot the device when it's plugged to charger
I tried many solution I've found like change the playlpm file but it simply does not work.
So I've decide to modify the kernel. Has someone change on the kernel to do this?
At this moment i'm trying to change the code in file /init/main.c but it does not work
Someone can help me?
Any solutions (I9295 and playlpm-script not working either)
Hi
I'm also looking solution for the same problem. I have Samsung Galaxy S4 active (international version I9295) and I have tried several different solutions to fix this. I have already tried following solutions:
- playlpm basic editing (as seen on many, many tutorials)
- playlpm including chmod changes and SU additions
- correct chmod and chown settings to playlpm
- 3rd party apps (which of most do the same as I have done by had)
When using shellscript above (playlpm), phone (when plugged into AC or USB when off), shows blank battery icon, shows it for 5-10 secs and then goes blank, and repeats whole sequence again and again.
What I what considered is that somehow reboot mode itself calls playlpm again, so it is stuck in low power mode bootloop, but this is just guessing game.
Anyone with helping solution? I really would like to get my S4 A to boot on charge.
On new Sansumg devices the file isn't playlpm. The new name is only lpm.
Try this and tell us if you have success.
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
Just wondering if some kind hacker would like to practice soldering and flashing on my Fire TV Stick. I was one of the folks who semi-bricked theirs with supersu me and Kingroot...
I have ADB but no root, boots to a black screen after animated rainbow logo. I can reboot to recovery, which seemingly does not make any changes to the device. Invoking a program like su or attempting a pm install freezes the adb shell. I haven't tried anything over USB yet. Invoking the settings menu, for instance, has no effect. I can get logs, ps, and navigate folders, but I don't think I'm going to be able to get it to a home screen.
But I wanted to put it out there - I'd throw some money your way for time, trouble, and shipping if you think you can re-flash it.
A dozen thanks in advance...
I have the same problem after I use supersu me with my box. stop at color amazon logo. Hope anybody can give me some idea to make it factory reset or pay for hardware write the emmc
I have 2 firestick 4ks.
Both identical in that they are rooted and debloated with (the same) various system apps frozen...
Both been running fine for a month or so...
Where I live I get frequent power cuts.
Yesterday after a power cut... one reboots correctly the other just goes to a black screen.
I connected it to my PC and ADB into it, I reenabled all apps via adb and rebooted, it just went to the same black screen.
So I booted to TWRP and reflashed RBoxes prerooted image, still nothing...
I then installed a stock image (Skel40's).... Still nothing.
Up to this point I had only been wiping Cache & Dalvik and dirty flashing.
I figured that there was a corrupted file that was affecting full boot, so I made the mistake of wiping data and installing stock again...
When I rebooted I had lost ADB!
I could still see the firestick in windows, however it just comes up as "Fire" in device manager with no ADB..
I grabbed an OTG cable and booted to TWRP and tried a few more times... each time gave exactly the same black screen (no orange amazon logo).
Finally I tried wiping system as well in case something was corrupted and reflashed stock.... Still nothing!
So I don't really know where to go from here... (I'm going to backup the other firestick and restore that over this one then reflash stock and see where that gets me...)
Does anyone have any ideas! I can get into TWRP, but I'm not sure it's wiping or flashing things correctly...
Any help greatly appreciated... Thx
Have you done any of the ideas listed in the other thread? Let me know if i can help #lockdown
Michajin said:
Have you done any of the ideas listed in the other thread? Let me know if i can help #lockdown
Click to expand...
Click to collapse
Hi Michajin...
Thanks for taking the time to help
I'll fill you in as to what I have and haven't tried...
I have wiped all standard partitions ( cache, dalvik, data, system) and reflashed both rooted and stock images *.*.6.8 and *.*.7.1
I think I may have wiped the Vendor partition, I'm not sure.
Under backup in TWRP I can see the Vendor partition, however under Wipe I see an extra 2 partitions (both) called storage and having not made a backup (I know!... )
I did'nt realise that the storage partition(s) may have been the Vendor partition.
After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal.
A couple of points that I can tell you...
I can boot to TWRP
I can reboot to hacked Bootloader
When I connect the firestick to my windows PC It's senses it straight away for a bout 10 seconds then drops it... It then senses it again and stays connected to my PC.
Windows recognizes it under portable devices as simply "fire" and an empty explorer window pops up, if I right click on the firestick in windows explorer (it shows as drive) I can pull a properties page which shows its serial number...!
On both my firesticks I have modified my build.prop for a faster boot which doesn't show the splash screen.
Both sticks were modified identically about a month ago and once setup had nothing added to them. They just get used for Kodi and catch-up TV apps.
I root them so as to boot directly into Kodi and freeze the bloat.
Both sticks have been rebooted multiple times.. This one failed after a powercut...
I been reading in the main rooting thread and have come across something about sticks not booting properly due to dm_verity failing and having to flash magisk before (or after... I'm not sure) the image flash.
I'm still reading through the thread so haven't tried anything yet... When i get head round what it is, I'll try.
The other 2 ideas I thought to try was to
1) flash an image directly from the bootloader (if possible.. I need to find more info on this) and
2) taking a backup of the working stick and trying that (It's in use a lot... due to #TotalLockdown! we're at 4 weeks with heavy police curfew! So I haven't had access to it)
If have any ideas or thoughts... I would be very grateful. Also I'm happy to try anything...
tinybilbo said:
Hi Michajin...
Thanks for taking the time to help
I'll fill you in as to what I have and haven't tried...
I have wiped all standard partitions ( cache, dalvik, data, system) and reflashed both rooted and stock images *.*.6.8 and *.*.7.1
I think I may have wiped the Vendor partition, I'm not sure.
Under backup in TWRP I can see the Vendor partition, however under Wipe I see an extra 2 partitions (both) called storage and having not made a backup (I know!... )
I did'nt realise that the storage partition(s) may have been the Vendor partition.
After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal.
A couple of points that I can tell you...
I can boot to TWRP
I can reboot to hacked Bootloader
When I connect the firestick to my windows PC It's senses it straight away for a bout 10 seconds then drops it... It then senses it again and stays connected to my PC.
Windows recognizes it under portable devices as simply "fire" and an empty explorer window pops up, if I right click on the firestick in windows explorer (it shows as drive) I can pull a properties page which shows its serial number...!
On both my firesticks I have modified my build.prop for a faster boot which doesn't show the splash screen.
Both sticks were modified identically about a month ago and once setup had nothing added to them. They just get used for Kodi and catch-up TV apps.
I root them so as to boot directly into Kodi and freeze the bloat.
Both sticks have been rebooted multiple times.. This one failed after a powercut...
I been reading in the main rooting thread and have come across something about sticks not booting properly due to dm_verity failing and having to flash magisk before (or after... I'm not sure) the image flash.
I'm still reading through the thread so haven't tried anything yet... When i get head round what it is, I'll try.
The other 2 ideas I thought to try was to
1) flash an image directly from the bootloader (if possible.. I need to find more info on this) and
2) taking a backup of the working stick and trying that (It's in use a lot... due to #TotalLockdown! we're at 4 weeks with heavy police curfew! So I haven't had access to it)
If have any ideas or thoughts... I would be very grateful. Also I'm happy to try anything...
Click to expand...
Click to collapse
It's really strange. Usually these steps should fix the issue :
1) Factory Reset from TWRP
2)Wipe System from TWRP
3) Flash full stock (non rooted) firmware
Of course, you could try flashing each image with hacked fastboot, or just boot, system and vendor with TWRP, which also have an option (install image) for that.
But you will have to convert system and vendor from sparse (.dat) to . img before being able to flash them.
Wiping these should have taken care of you issue.
"After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal."
What stock did you flash from where?
When you flash stock are there any errors?
You should be able to take a backup from you other one also for other one (if you are doing a full backup/restore, i would wipe data and cache after restore)
Thanks guys for the replies, I couldn't respond earlier due to an 8 hr powercut today!
Pretoriano80 said:
It's really strange. Usually these steps should fix the issue :
1) Factory Reset from TWRP
2)Wipe System from TWRP
3) Flash full stock (non rooted) firmware
Of course, you could try flashing each image with hacked fastboot, or just boot, system and vendor with TWRP, which also have an option (install image) for that.
But you will have to convert system and vendor from sparse (.dat) to . img before being able to flash them.
Click to expand...
Click to collapse
Hi Pretoriano80
Yeah... It's really weird... I'm starting to think that the stick is damaged in some way, although the fact I can get in both the hacked bootloader and TWRP confuses me!
I've even wiped each partition 3 or 4 times (and rebooted back into recovery to remount) before writing the new image just to make sure.!
I'm ready to try anything at this point, since the stick is a brick at this point.
I'm not really sure how or what to flash from the bootloader, I'll read up a bit before I try especially your tips about converting from sparse to .img.
(I may have some further questions for you, if that's alright )
I will try to restore a backup from another stick first (if I can get access to that stick for long enough...)
Michajin said:
Wiping these should have taken care of you issue.
"After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal."
What stock did you flash from where?
When you flash stock are there any errors?
You should be able to take a backup from you other one also for other one (if you are doing a full backup/restore, i would wipe data and cache after restore)
Click to expand...
Click to collapse
Hi Michajin
Thanks again for taking the time to reply... much appreciated...
I have tried this stock image update-kindle-mantis-NS6271_user_2493_0003590962564
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777
as well as a update-kindle-mantis-NS6268_user_2315_0003255372676 image (stock that I think i got from the main rooting thread)
I've also used Rboxes pre-rooted image mantis-6.2.6.8-rooted_r1
which was the image that worked fine on both boxes...
I'm happy to try any other image that you might have a link for.....
When I wipe the partitions there are no errors, except for when I wiped the storage partitions - they did throw up an error - although at this point I had already tried flashing new images at least a dozen times,
All the images flash without error as well!
I'm stumped... I've never had any android device brick before... (soft bricks many times! but never a hard brick), and it's weird since I have access to both the bootloader and TWRP.
Tomorrow I'll be able to get a restore image from the other stick, Then I'll try flashing from bootloader..
The only other thing i thought to try was to crack the case open and redo the the whole root procedure from scratch...
Sorry to double-post...
However I wanted to add this as a separate post rather than an edit.
After playing with my firestick for a few days, during which I tried a working backup and erasing from the bootloader and then restoring multiple images (stock and prerooted), as well running the exploit again.
I realised that the OS was loading (I regained ADB after the full restore) despite not giving an image over HDMI (just a black screen).
I was about to give up when I happened to be going through the options in ADBLink and I found the screenshot button.
I gave it a try and to my surprise it sent back an image of the stick with a working OS/screen.
I even manged to navigate through the settings and do a full reset from within FireOS by taking screengrabs.
After the reset it still gave a black screen, I re-enabled ADB from TWRP and was able to verify that it had reset correctly...
From ADB I ran a logcat...
I'm not really familiar with logcat but a couple of things seemed to jump out...
Code:
1) 596 617 I DisplayManagerService: Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 480, modeId 4, defaultModeId 1, supportedModes [{id=1, width=1920, height=1080, fps=60.000004}, {id=2, width=1920, height=1080, fps=59.94}, {id=3, width=720, height=576, fps=50.0}, {id=4, width=720, height=480, fps=60.000004}], colorMode 0, supportedColorModes [0], HdrCapabilities [email protected], density 320, 213.0 x 216.0 dpi, appVsyncOff 1000000, presDeadline 16666666, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
2) 1145 1145 I AmazonHdmiServiceManager: resolution applied and hdmi turned off
3) 596 2438 E AmazonHdmiService: Settings client binder died.
Seeing that there were some issues with the HDMI display (Display device change to built-In screen? and HDMI turned off?), I used the screengrab to navigate my way to display settings which wouldn't allow me to change resolution
So to sum it up...
Everything is loading and running correctly, however I can't get an image over HDMI only by getting screengrabs via ADBlink.
Maybe something on the chip (HDMI output) is damaged, I've had the stick for a while and it's had heavy usage, or something has stuck in a toggled state.
I don't know....
If anyone has any ideas how to test it I have full root access via TWRP and probably can get it over ADB, so any help or commands to try would greatly appreciated....
Thanks :good:
tinybilbo said:
Sorry to double-post...
However I wanted to add this as a separate post rather than an edit.
After playing with my firestick for a few days, during which I tried a working backup and erasing from the bootloader and then restoring multiple images (stock and prerooted), as well running the exploit again.
I realised that the OS was loading (I regained ADB after the full restore) despite not giving an image over HDMI (just a black screen).
I was about to give up when I happened to be going through the options in ADBLink and I found the screenshot button.
I gave it a try and to my surprise it sent back an image of the stick with a working OS/screen.
I even manged to navigate through the settings and do a full reset from within FireOS by taking screengrabs.
After the reset it still gave a black screen, I re-enabled ADB from TWRP and was able to verify that it had reset correctly...
From ADB I ran a logcat...
I'm not really familiar with logcat but a couple of things seemed to jump out...
Code:
1) 596 617 I DisplayManagerService: Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 480, modeId 4, defaultModeId 1, supportedModes [{id=1, width=1920, height=1080, fps=60.000004}, {id=2, width=1920, height=1080, fps=59.94}, {id=3, width=720, height=576, fps=50.0}, {id=4, width=720, height=480, fps=60.000004}], colorMode 0, supportedColorModes [0], HdrCapabilities [email protected], density 320, 213.0 x 216.0 dpi, appVsyncOff 1000000, presDeadline 16666666, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
2) 1145 1145 I AmazonHdmiServiceManager: resolution applied and hdmi turned off
3) 596 2438 E AmazonHdmiService: Settings client binder died.
Seeing that there were some issues with the HDMI display (Display device change to built-In screen? and HDMI turned off?), I used the screengrab to navigate my way to display settings which wouldn't allow me to change resolution
So to sum it up...
Everything is loading and running correctly, however I can't get an image over HDMI only by getting screengrabs via ADBlink.
Maybe something on the chip (HDMI output) is damaged, I've had the stick for a while and it's had heavy usage, or something has stuck in a toggled state.
I don't know....
If anyone has any ideas how to test it I have full root access via TWRP and probably can get it over ADB, so any help or commands to try would greatly appreciated....
Thanks :good:
Click to expand...
Click to collapse
Just checking, but have you tried another HDMI cable and different TV? Somehow it is not recognizing the format in the OS. TWRP uses a lower format i believe. I have had a power surge before damaging HDMI here, but I wouldn't get anything with it plugged in.
Michajin said:
Just checking, but have you tried another HDMI cable and different TV? Somehow it is not recognizing the format in the OS. TWRP uses a lower format i believe. I have had a power surge before damaging HDMI here, but I wouldn't get anything with it plugged in.
Click to expand...
Click to collapse
Hi Michajin,
Thanks for your reply...
Yes I have tried multiple TV's, Monitors , and cables... Including the TV that it had been running on for almost a year...
I get frequent powercuts where I live, and often power surges when the power comes back on...
I do use surge protectors, however they don't always work....
One time the electricity board double one of the phases to 440v and knocked out £5k worth of equipment!
So between that and the humidity I think there is some minor damage to the stick... shame because it's still running.
I'm going to see if I can get a logcat from TWRP and see what it says about the HDMI output, not that it'll help...
tinybilbo said:
Hi Michajin,
Thanks for your reply...
Yes I have tried multiple TV's, Monitors , and cables... Including the TV that it had been running on for almost a year...
I get frequent powercuts where I live, and often power surges when the power comes back on...
I do use surge protectors, however they don't always work....
One time the electricity board double one of the phases to 440v and knocked out £5k worth of equipment!
So between that and the humidity I think there is some minor damage to the stick... shame because it's still running.
I'm going to see if I can get a logcat from TWRP and see what it says about the HDMI output, not that it'll help...
Click to expand...
Click to collapse
So you get a display in TWRP, but go black after booting? I wonder if you can force whatever display mode and setting as used in TWRP as your display mode in FireOS. Had you tried another wall outlet (higher mA) ? A long shot at this point that you havent tried it....
Michajin said:
So you get a display in TWRP, but go black after booting? I wonder if you can force whatever display mode and setting as used in TWRP as your display mode in FireOS. Had you tried another wall outlet (higher mA) ? A long shot at this point that you havent tried it....
Click to expand...
Click to collapse
Correct, I can get a display with TWRP, but it goes black when it boots into FireOS (from which I can get screengrab via adblink of the stick displaying FireOS or whatever app is running).
Up until now (for almost a year) I've just used the power adapter that came with the stick, but it's a good idea to try something more powerful (I have a 2.4a one that I'll try a little later).
Another thing I'm going to try is "adb shell wm size ***x***" "adb shell wm density ***" command to change the resolution & pixel density (I think).
I hadn't thought about power being an issue up until you mentioned it (because so far it hasn't been), but maybe a component has (or is) failed (or failing) so it might need more power...
I can't try until a little later this evening, but at least I have something to try now cheers! I'll let you know how I get on....
tinybilbo said:
Correct, I can get a display with TWRP, but it goes black when it boots into FireOS (from which I can get screengrab via adblink of the stick displaying FireOS or whatever app is running).
Up until now (for almost a year) I've just used the power adapter that came with the stick, but it's a good idea to try something more powerful (I have a 2.4a one that I'll try a little later).
Another thing I'm going to try is "adb shell wm size ***x***" "adb shell wm density ***" command to change the resolution & pixel density (I think).
I hadn't thought about power being an issue up until you mentioned it (because so far it hasn't been), but maybe a component has (or is) failed (or failing) so it might need more power...
I can't try until a little later this evening, but at least I have something to try now cheers! I'll let you know how I get on....
Click to expand...
Click to collapse
Hey I have a debloated clean stable rom that will be available soon. You can try that and you need to be sure to have either a usb otg or a hub for transferring this backup which will be titled ftvs4kdebloatedv1.0. Paste this folder to TWRP/BACKUPS/YOUR SERIAL #/ftvs4kdebloatedv1.0.
Skel40 said:
Hey I have a debloated clean stable rom that will be available soon. You can try that and you need to be sure to have either a usb otg or a hub for transferring this backup which will be titled ftvs4kdebloatedv1.0. Paste this folder to TWRP/BACKUPS/YOUR SERIAL #/ftvs4kdebloatedv1.0.
Click to expand...
Click to collapse
Thanks Skel40
I'll definitely give the clean rom a go
I have an OTG & Hub and the serial number already
hi guys
i have a firestick 2th gen model ly78pr its brick stock on logo , the problem is usb debbug was off and i tried with the key board and otg cable pressing alt + printscreen + i and it does not work as , i tried different combination and nothing help , also i connected to the pc and it does not work with adb it doesnt reconize , if anyone can help to find any solution