I was installing my invisibleSHIELD last night with my phone turned off, and apparently managed to do something while trying to fiddle it on as the screen turned on with some small amount of data, and it was colored like some color test screen, red blue green and white horizontal areas(or something like that).
So what did I manage to do? Was it dangerous in anyway for the phone? Probably not, but I'd like to know how I did it and what's its purpose =)
This is called the bootloader screen (popularly known as the Tri-colour screen), you got to this screen by starting up the phone with the Volume Down button held.
Not dangerous at all, unless you had a RAPHIMG.nbh file on the root directory of your fat32 formatted storage card
[along with a wrapper] (Having that file in the root and starting up to the bootloader would allow one to initiated a flash)
This mode is used to flash a new rom, radio or spl to the device, either run to it automatically by a Wrapper from your computer or forced by the user. From this screen one can even flash any of those items from a storage card instead of from the computer. (I do this from time to time when I dont have access to a computer with active sync and wish to flash a rom.
Of course, one needs hard spl to flash anything custom.
Related
I've got a rooted (Super SU, but the original root manager was Superuser) LG C800 that I was having problems with. To be specific, I installed some apps on to the system. Some of these apps would be Titanium Backup for root, Avast Mobile Security, ROM Tool Box Lite, Super SU, and a quite a few others. From day one they seem to be kicked right back to my S.D. card, but not all at the same time, and some would stay on the system. I read where I should move the apps back to my S.D. card and try to re-install them on the system minus the data. When I did, the phone went nuts. Now it stays in a restart mode but never fully boots up. Can I salvage it, and if so, please tell me how?! I have tried the hard reset/recovery boot where you hold down the power button, volume, and a few other keys, but it did not work. I'm a broke college student and can't really afford to buy a new phone. I used this one for everything including tethering it to get my assignments done at home and turned in on time. Please help! I'm open to suggestions....... My phone will be completely off. When I plug it into my computer, via U.S.B., it automatically turns it on whether I want it to be on or not. Then it starts off in "reboot recovery" mode, will boot all the way to the point to where the home screen would normally turn on, but then it starts in that "boot loop" all over again but never fully boots up before going back to the beginning of that "boot loop" yet again. I can't even get it to register on my laptop as being plugged in. The reason I took the apps I placed on the system off was because sometimes when I'd re-boot the system the apps would be on the system and sometimes back on my S.D. card without my involvement of any kind other than rebooting my phone. Is completing a Nandroid recovery or re-installation of my ROM even possible with my computer no longer recognizing it as even being plugged in? From what I can tell it won't be. Am I fighting a lost cause or is it salvageable?
Rooted myTouch Q 4G, a.k.a. LG C800
I believe it has a 2.3.4 GRJ22-perf, and then something like 2.6.35.7? I can't remember off the top of my head, and I can't pull it up on my phone anymore or else I'd double check.
Have you tried booting into recovery?
(More about my phone from the original post) Honestly.........I'm not what you may consider technologically inclined. I have however done about as much research online concerning this matter as any one person can do. I've looked it up on all major sites, and many smaller ones too, that post remedies for phone, or "human" if you'd rather, malfunctions. They all talk about still being able to reach a home screen or doing the whole holding the power and volume decrease buttons until I "reboot recovery" screen appears (if that's what you're referring to as doing a recovery reboot as). Don't forget the one where you hold hold the power and volume decrease buttons along with the "A" and "F" keys as well. I even tried one from here where you're supposed to push the genius button after the Android figure leaves the screen. My phone won't allow me to do either. Basically if it's online, I myself, or this girl that's been staying with me, have tried it without any results. On the initial boot the Android figure and the box with the arrow coming out of it show up and it boots until just about the point that it use to switch over to the home screen and it will start the whole "boot loop" over again. The thing is though that the Android figure and box aren't there any other time after the first boot, and with every boot loop it makes after that, the time is reduced from the beginning of the loop to the end when it starts all over again. The phone won't shut off unless I remove the battery and even though my laptop no longer recognizes the device, when I plug my phone into it or another power source and it's off, it automatically turns itself on and begins that boot loop all over again. there is one thing I have yet to try. I read on one site where I could download a custom ROM on my S.D. and then try reboot it, but it never makes it to the point in which the files on my S.D. card are ran, much less scanned. I am still 100% open to any and all suggestions in the diagnosis of this issue. I may record and place a video on one of the more popular "tube" sites to better show or further explain what's happening and then come back on here to post the link?! Feel free to reply back if it's possible you can help before I'm able to complete that later this evening. And thanks for any and all help in advance to everyone.
Hi All,
Saw a few posts with similar things such as random reboots and bootloader issues, however my issue seems a little different. I already know the first few things I'm going to try but would just like a little bit of input.
The tf700 isn't my first transformer tablet, I had a prime back during release and replaced it with the 700 after my friend broke the screen. I have plenty of experience with flashing the devices and putting on custom roms etc. My infinity has been on JB since the OTA update came (infinity is 100% stock). I use the device every day extensively and it is in the keyboard dock about 99% of the time.
Today while checking my email the device randomly froze, went to a black screen, and then started up at the first asus logo (has happened before so I was not that surprised). After getting to the second splash screen with the silver asus logo I let it sit for about 15 minutes where I continued to get the loading animation. I decided to restart and go into the bootloader menu and thats where I noticed some issues.
Once in the bootloader it seems that Volume UP (to change between RCK, Data wipe etc..) is always recognized as Volume DOWN, meaning I cannot switch between any of the bootloader tasksJust realized they changed the input even though the bootloader text still has ICS commands listed. That leaves me the option of waiting 10 seconds for a cold-boot or starting the RCK. Unfortunately either task I decide to do freezes the screen on the bootloader. I know that the device is responding at first because of the highlight over RCK fading in and out, and then it freezes. Prior to the freeze the prompt always reads Signature Match when trying to cold-boot or start the RCK. Restarting the device again leaves me stuck on the first splash screen, and never progressing after that. I am somewhat concerned about possible corruption from this.
Currently I am letting the power drain all the way down while in the dock and will try charging it to see if that brings it out of this brickish state. In addition I also have a micro-sd in the device, as well as an SD card in the dock.
Other than power draining I would really appreciate some advice, because of freezing in the bootloader I am unsure whether I would be able to perform any sort of modification to overwrite whatever has been corrupted.
Thanks in advance,
Jon
jallweiss said:
Hi All,
Saw a few posts with similar things such as random reboots and bootloader issues, however my issue seems a little different. I already know the first few things I'm going to try but would just like a little bit of input.
The tf700 isn't my first transformer tablet, I had a prime back during release and replaced it with the 700 after my friend broke the screen. I have plenty of experience with flashing the devices and putting on custom roms etc. My infinity has been on JB since the OTA update came (infinity is 100% stock). I use the device every day extensively and it is in the keyboard dock about 99% of the time.
Today while checking my email the device randomly froze, went to a black screen, and then started up at the first asus logo (has happened before so I was not that surprised). After getting to the second splash screen with the silver asus logo I let it sit for about 15 minutes where I continued to get the loading animation. I decided to restart and go into the bootloader menu and thats where I noticed some issues.
Once in the bootloader it seems that Volume UP (to change between RCK, Data wipe etc..) is always recognized as Volume DOWN, meaning I cannot switch between any of the bootloader tasksJust realized they changed the input even though the bootloader text still has ICS commands listed. That leaves me the option of waiting 10 seconds for a cold-boot or starting the RCK. Unfortunately either task I decide to do freezes the screen on the bootloader. I know that the device is responding at first because of the highlight over RCK fading in and out, and then it freezes. Prior to the freeze the prompt always reads Signature Match when trying to cold-boot or start the RCK. Restarting the device again leaves me stuck on the first splash screen, and never progressing after that. I am somewhat concerned about possible corruption from this.
Currently I am letting the power drain all the way down while in the dock and will try charging it to see if that brings it out of this brickish state. In addition I also have a micro-sd in the device, as well as an SD card in the dock.
Other than power draining I would really appreciate some advice, because of freezing in the bootloader I am unsure whether I would be able to perform any sort of modification to overwrite whatever has been corrupted.
Thanks in advance,
Jon
Click to expand...
Click to collapse
Seems like you only have RCK option on your device. I would download the full JB .16 version from the Asus site, unzip it and rename the new unzip file to EP201_768_SDUPDATE.zip on your PC, plug in your micro SD card (make sure no other zip file(s) on the root of your micro SDcard), then copy this file to the root of your micro SD card, remove the micro sDcard and plug it back to your tf700, Hold down volume down and power button and let it boot to the RCK (by default) see if the device perform the update.
buhohitr said:
Seems like you only have RCK option on your device. I would download the full JB .16 version from the Asus site, unzip it and rename the new unzip file to EP201_768_SDUPDATE.zip on your PC, plug in your micro SD card (make sure no other zip file(s) on the root of your micro SDcard), then copy this file to the root of your micro SD card, remove the micro sDcard and plug it back to your tf700, Hold down volume down and power button and let it boot to the RCK (by default) see if the device perform the update.
Click to expand...
Click to collapse
Thanks buho,
Full power drain and repower didnt seem to fix it.
I gave it a shot with the update and I still got the message saying that the signature matched and then freezing at the bootloader trying to use the update. As I edited in my post I found that the bootloader commands had been swapped, so I can get to the other options to work. However all of them freeze the bootloader, I cant get any kind of USB recognition at all.
Unfortunately things may have gotten even worse...
I figured since I just need the device to work I would do a full wipe, I started the data wipe, got the freeze after a bit of text. I left the device for about 20 minutes hoping it would go through with the wipe. It was still frozen on the bootloader so I reset the device again... After resetting I cant even get into the bootloader anymore, power button + volume down does nothing.
So currently Im stuck on the first splash screen, unable to access the bootloader. I would appreciate any help at all.
Just to update, I can get APX mode to function right now, but I am not really sure where I can go from there...
This Desire S is almost dead, and the screen is permanently black - it cannot even boot to the HTC screen.
I can only find 4 visible states for the device: (1) off (only after battery removed and replaced); (2) when power button pressed from state (1) LED off, vibrator immediately buzzes 7 times at about 0.5 sec intervals, then nothing else, cannot switch off; (3) when plugged into USB or mains charger from state (1) LED on, otherwise identical to state (2) and LED remains on after unplugged; (4) after states (2) or (3) screen remains blank, nothing happens, cannot be turned off (LED either permanently on or permanently off).
History: the phone is visually in excellent condition, but the previous owner wanted to install ICS. To this end he downloaded and tried to install RUU:
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed.exe
and in the middle it froze. After 30 minutes he pulled out the battery, giving rise to the state it is in now. (I naively imagined I could easily re-flash it, until I read about the eMMC hardware problems of the Desire S after pulling out the battery).
It seems almost totally dead, but the only cause for doubt is that it has the three different states above after turning on - obviously stuck in a loop, presumably the early stages of the bootloader. However it is not recognised by adb or fastboot through USB, nor by the RUU installer, nor by the Unrevoked installer. I also tried copying hboot.img (0.98.0000) or PG88IMG.zip (Eng Hboot for AlphaRevX) to the root of an SD card, and that had no discernible result.
Once turned on, up-vol + down-vol + power has no effect at any time. There is no difference visible between turning on from state (1) with power alone or with vol-down + power. The battery is 3.77 volts, and does not charge when plugged in for a few hours (reduced from 3.83 volts earlier).
Can a zapped eMMC have this effect, or would it then reach the HTC screen?
Sounds pretty hopeless, doesn't it? Is there any stone I have left unturned?
I think that with fried emmc phone should stay on white htc screen, your problem looks like corrupted bootloader and this can be fixed AFAIK only by JTAG
441Excelsior said:
I think that with fried emmc phone should stay on white htc screen, your problem looks like corrupted bootloader and this can be fixed AFAIK only by JTAG
Click to expand...
Click to collapse
Is the bootloader also stored in the eMMC chip or in another chip? From the available description the upgrade is supposed to have frozen in the middle, so I'd have thought the bootloader should already have been written by that time. I agree with you that the symptoms look like a corrupted bootloader, but if the corrupted bootloader was caused by pulling the battery then it seems to me the hardware the bootloader is on (whether eMMC or another chip) must come into question.
There is more than one bootloader in the system. The simplest system includes 2 of those - primary (PBL) and secondary (SBL).
HBOOT is secondary bootloader and resides on eMMC.
Jack_R1 said:
There is more than one bootloader in the system. The simplest system includes 2 of those - primary (PBL) and secondary (SBL).
HBOOT is secondary bootloader and resides on eMMC.
Click to expand...
Click to collapse
Aha!! And is it possible to reprogram the primary bootloader to load an hboot from SD card? Is the secondary bootloader required for reprogramming the primary bootloader? What about the programming from the root of the SD card (PG88IMG.zip etc) - is that initiated from hboot or from the primary boot loader? (I'm afraid I already suspect the answer to that one, as the PBL will be as short and sweet as possible - that's why we don't hear much about the PBL!)
Same problem
You have the same problem as I do, but i did not do anything to it, I just woke up and my phone was dead. (Heart attack :silly The only sign of life what I see is if I plug-in the cable AC or PC and after that I plug-in the battery, the orange led show up for about 5 seconds, thats it.
I found a flasher you could use, they say that this program works even if your phone is dead over usb, but only if you are S-Off, you should try it. http://forum.xda-developers.com/showthread.php?t=794638
olysmen said:
I found a flasher you could use, they say that this program works even if your phone is dead over usb, but only if you are S-Off, you should try it. http://forum.xda-developers.com/showthread.php?t=794638
Click to expand...
Click to collapse
I downloaded it and tried to run it. On my main computer (XP) it would not run, because it required DotNet 4 (which I cannot install on this machine). I tried running it on a Windows 7 machine, and it said: "AndroidFlasher does not work any longer. A problem has stopped the proper running of this program." I tried switching off firewall, but that had no effect.
Hello everyone!
Yesterday I powered off my Moto G3 and plugged it in to charge. After a few minutes I heard a short vibration, which normally means that the phone powered on by itself and is booting. I then checked the screen; I had to put in the PIN for my SIM card, but afterwards there was no pattern I had to draw in order to unlock the phone (I had one set up before!). After unlocking the screen I can see a blue screen with "Welcome" at the top, a choice of language and a yellow arrow ("next") button in the middle and "Emergency" call button at the bottom. And in the top right hand corner are the usual signal strength and battery icons.
When I press the yellow button, I'm asked to connect to a Wi-Fi network. I haven't proceeded beyond that point, as I don't want to mess up my phone even further. Basically it looks like my Moto G3 returned to factory settings and wants me to set it up for first use.
I then tried to reboot the phone a few times. I always get the standard Motorola "stitching" animation and get booted into the described screen. I also went into recovery mode, but almost every single option booted me into the blue screen and one time I got the "No command" screen. But maybe I did something wrong; I'm certainly no expert when it comes to using the bootloader.
Having described all of that, my questions are: is it possible for the phone to have reverted itself to factory settings? If yes - why and how? I have an SD card with a lot of photos, documents and application data that is very important to me. Is it still possible to retrieve the data that was saved on the device?
I would very much appreciate any help with this problem!
Thank you,
Meletel
You can copy the contents of the SDCARD while in TWRP.
1. Put MicroSD card and copy the contents of Internal Storage to microsd though TWRP File manager
2. Connect your phone to your computer by USB Cable while in TWRP and you can access your phone through MTP
Heu guys,
So I received a P30 as a gift yesterday, it said it had an update so it downloaded. Then it said it needed to be at 20% to install the update so I just left it until later when I could get to a charger. The thing is, I also didn't have a sim card in it.
I pulled the sim slot with the phone turned on (install pending) , and as soon as I did that I got a new black screen of death, nothing like in any of the videos online.
This one allows me to interact with the screen, however the entire screen stays black except for about 50% of the top (like I can see 50% of the battery icon) notification area. The tiny section of the screen that turns on also looks sorta wonky, like screens often do when they get water damage.
I've been able to turn it off, by guessing where the power buttons were. I *think* I even got it to the hard reset menu, but not being able to see, I can't type on the screen. It does react to the soft reset (power + volume down) but when it turns back on, it won't even show the logos on boot, everything still stays black minus a section of the notification bar.
Is there a way to do a hard reset without being able to interact with the screen at all? Can I do it using my computer somehow?
I know the screen is not broken because I can interact with it. Also on 1 of the 30 soft resets I did, the screen flickered some sort of error message for a quarter of a second, so fast all I could do was see it was text.
I'd just return the phone but it was a friend's old work phone and there is no way to get a replacement.
I recommend you to use Hisuite on a computer, try to connect the phone (I said try because you must select the type of connection on the phone). If the phone connects to Hisuite, use the recovery option to reinstall the default firmware. Good luck!
marselcj said:
I recommend you to use Hisuite on a computer, try to connect the phone (I said try because you must select the type of connection on the phone). If the phone connects to Hisuite, use the recovery option to reinstall the default firmware. Good luck!
Click to expand...
Click to collapse
this might be my only option. I was trying to find something just like that. Couldn't figure out if there was a software for it or not. Thanks will try when I get back to a computer tomorrow!