Related
Like an idiot, I selected Re-Partition in Odin3 while trying to revert back to the stock firmware and after odin attempted to reboot my phone it's stone dead. The phone is completely unresponsive to anything, it won't turn on nor will it show the charging screen when it's plugged in. The only thing I can get the phone to do is to display what seems to be a useless status screen by holding down the power and volume up buttons which displays the following in orange text:
RST_STAT = 0x1
PMIC_IRQ1 = 0x0
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x0
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0x80
PMIC_STATUS2 = 0x0
I have noticed that the values are different when the phone is plugged in and they are:
RST_STAT = 0x1
PMIC_IRQ1 = 0x3c
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x0
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0xc0
PMIC_STATUS2 = 0x2c
thanks.
Why did you try to flash stock kernel thru Odin? Could of just done it from Clockwork Recovery.
Are you able to get into download mode? http://forum.xda-developers.com/showthread.php?t=741027&highlight=unbrick
Can't get into download mode, can't get into recovery mode, can't even reach the vibrant screen.
Then it's probably bricked, only way to unbrick is to get into Download mode or even recovery (if you have a previous backup)
Are you sure that you're pressing the right buttons to get into download mode?
Yeah I had to get into download mode to use odin in the first place.
I had exactly the same thing going on with mine. Odd status screen with red text is all I could get. This worked for me to get back to download mode:
1. Removed SD and SIM card
2. Removed battery
3. plugged the phone into USB (connected to PC)
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
Note that I didn't use the power button at all. Try it both ways, though.
Dex thank you so much, I followed your steps exactly and it worked instantly.
solarpanel said:
Dex thank you so much, I followed your steps exactly and it worked instantly.
Click to expand...
Click to collapse
Glad to help. I was sweating bullets when I was where you are until I figured that out. Thought I was bricked for sure!
It seems it is very difficult to brick this phone :-D. Thanks again.
solarpanel said:
It seems it is very difficult to brick this phone :-D. Thanks again.
Click to expand...
Click to collapse
I actually got mine to the point where it wouldn't even respond to the charger after removing and reinstalling the battery (or anything else), and still managed to get it operational.
mindaika said:
I actually got mine to the point where it wouldn't even respond to the charger after removing and reinstalling the battery (or anything else), and still managed to get it operational.
Click to expand...
Click to collapse
Me too.
i dont have oden but i do have adb. i can get to my recovery screen but its not the clockwork recovery screen that i want so i can restore my nandroid. any ideas?
mindaika said:
I actually got mine to the point where it wouldn't even respond to the charger after removing and reinstalling the battery (or anything else), and still managed to get it operational.
Click to expand...
Click to collapse
Care to let us know how?
b1u3m3th said:
Care to let us know how?
Click to expand...
Click to collapse
For me all it took was for Odin to hang during a flash. Couldn't get the phone to do anything after that...no download mode...no charging icon when plugged in...nothing.
Im having issuses where it will only boot to the Vibrant screen and just hang there, if i boot it with the usb cable in it will just go strait to the battery screen and kinda just hang there too.....any ideas? ive tried all your steps and none have worked, is it possible it wont boot into recovery if the battery is too low?
Thanks to everyone I got off the brick I was on like the guy in the thread. Now that I'm in the downloading screen should I run Odin again, it's kinda the reason why my phone bricked in the first place
I actually can't run Odin. My drivers have issues of not being read by my windows 7 or my virtually PC on mac book pro running VM ware via XP
Dead (Bricked) Vibrant
I have done everything, Recovery, download mode, flashed roms, etc. Now i am at the point where the phone wont turn on, it wont charge, it wont even give me this.
RST_STAT = 0x1
PMIC_IRQ1 = 0x0
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x0
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0x80
PMIC_STATUS2 = 0x0
I had to use adb to force update.zip to the root of the internal sd card. Once that was complete it started flashing then turned off and will not come back on. Guys as sad as it sound I think I'm the first to fully BRICK a Vibrant. PLEASE HELP
Am I the first to fully kill the phone? lol
Download mode and orange status screen are all I can get to, and Odin fails... =/
dex1701 said:
I had exactly the same thing going on with mine. Odd status screen with red text is all I could get. This worked for me to get back to download mode:
1. Removed SD and SIM card
2. Removed battery
3. plugged the phone into USB (connected to PC)
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
Note that I didn't use the power button at all. Try it both ways, though.
Click to expand...
Click to collapse
OMG, thanks so much I thought I bricked my phone.
Mage42384 said:
Am I the first to fully kill the phone? lol
Download mode and orange status screen are all I can get to, and Odin fails... =/
Click to expand...
Click to collapse
no you havent, if you can get into download mode then your golden. I have bricked my phone though
So, this is interesting. Got an a1 off of craigslist, started playing with it. Su wasn't there, so i thought nothing of it, but I tried to boot into recovery to wipe the thing.
And....aparently the previous owner tried to install CWM and borked it big time. it's v4.0.0.2, showing up landscape, but the button mapping is odd.
power: hides/unhides options
vol up: null
pol down: null
soft1(menu): hides/unhides options
soft2(home/companion cube button): null
soft3(back): null
This is lovely. any help?
Edit: well, just had to hold the power off. But, just in case, anyone know how to either fix CWM or get the stock recovery on there?
SGP 5.0 wifi, running Chip 1.5 GB ROM, but behavior described below also appears on stock ROM and ICS rom.
I'm not sure exactly what's going on with my player. I noticed this morning when I attempted to turn it on, instead of showing the samsung splash logo, (followed by the animation) it showed the loading/waiting circle then the battery charging screen for a second, then rebooting.
I fooled around with various settings, with no results. I flashed a backup nandroid, with the same behavior. I flashed an ics rom, same behavior. I'm back to my normal ROM right now. But the only way I can use my device (at all) is to do the following.
1. Boot into download mode. (power, voldown)
2. Flash a kernel (heimdall flash --kernel zImage)
3. It boots
Then everything works, until I power off the device. Then I have to flash the kernel again to get the device to boot. Reboots, Rebooting into recovery, etc work. But powering the device down completely requires a flashed kernel to get running again.
Any ideas on what's going on? I'm totally stuck. Thanks.
xterminus said:
SGP 5.0 wifi, running Chip 1.5 GB ROM, but behavior described below also appears on stock ROM and ICS rom.
I'm not sure exactly what's going on with my player. I noticed this morning when I attempted to turn it on, instead of showing the samsung splash logo, (followed by the animation) it showed the loading/waiting circle then the battery charging screen for a second, then rebooting.
I fooled around with various settings, with no results. I flashed a backup nandroid, with the same behavior. I flashed an ics rom, same behavior. I'm back to my normal ROM right now. But the only way I can use my device (at all) is to do the following.
1. Boot into download mode. (power, voldown)
2. Flash a kernel (heimdall flash --kernel zImage)
3. It boots
Then everything works, until I power off the device. Then I have to flash the kernel again to get the device to boot. Reboots, Rebooting into recovery, etc work. But powering the device down completely requires a flashed kernel to get running again.
Any ideas on what's going on? I'm totally stuck. Thanks.
Click to expand...
Click to collapse
That is a known bug that happens when plugged into a PC, but it's happening for you all the time?
Sent from my Galaxy Nexus
Mevordel said:
That is a known bug that happens when plugged into a PC, but it's happening for you all the time?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yeah, The bootloop is exactly what used to happen when I attempted to charge on the laptop's usb port. Now it does it regardless of power source, or even if there is no power source at all. In addition, I can't boot up the device at all without going into download mode and flashing a new kernel. Annoying.
xterminus said:
Yeah, The bootloop is exactly what used to happen when I attempted to charge on the laptop's usb port. Now it does it regardless of power source, or even if there is no power source at all. In addition, I can't boot up the device at all without going into download mode and flashing a new kernel. Annoying.
Click to expand...
Click to collapse
I'm kinda stumped here... So strange. No hardware mods? And of course no USB port short because it still works. Obviously, the boot loader or kernel is getting confused and always putting it in low power mode. Try running as root
Code:
echo 1 > /proc/param/debug
to reset the boot loader settings and see if that fixes it.
Also, what kernel are you running?
Sent from my Galaxy Nexus
Mevordel said:
I'm kinda stumped here... So strange. No hardware mods? And of course no USB port short because it still works. Obviously, the boot loader or kernel is getting confused and always putting it in low power mode. Try running as root
Code:
echo 1 > /proc/param/debug
to reset the boot loader settings and see if that fixes it.
Also, what kernel are you running?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
No Hardware mods. The above code resulted in the following in my dmesg
Code:
<6>[ 1207.038888] Parameters have been set as DEFAULT values...
<6>[ 1207.046140] -----------------------------------------------------
<6>[ 1207.050839] Information of Parameters
<6>[ 1207.054614] -----------------------------------------------------
<6>[ 1207.062599] - param_magic : 0x72726624
<6>[ 1207.065725] - param_version : 0x13
<6>[ 1207.069769] - 0. SERIAL_SPEED : 7
<6>[ 1207.073483] - 1. LOAD_RAMDISK : 0
<6>[ 1207.077908] - 2. BOOT_DELAY : 0
<6>[ 1207.081888] - 3. LCD_LEVEL : 97
<6>[ 1207.084413] - 4. SWITCH_SEL : 1
<6>[ 1207.087973] - 5. PHONE_DEBUG_ON : 0
<6>[ 1207.091895] - 6. LCD_DIM_LEVEL : 17
<6>[ 1207.096636] - 7. LCD_DIM_TIME : 0
<6>[ 1207.099345] - 8. MELODY_LEVEL : 0
<6>[ 1207.103233] - 9. REBOOT_MODE : 0
<6>[ 1207.106878] - 10. NATION_SEL : 0
<6>[ 1207.111616] - 11. LANGUAGE_SEL : 0
<6>[ 1207.114203] - 12. SET_DEFAULT_PARAM : 0
<6>[ 1207.118078] - 15. VERSION(STR) : I8315XXIE00
<6>[ 1207.122962] - 16. CMDLINE(STR) : console=ttySAC2,115200
<6>[ 1207.129529] -----------------------------------------------------
I figured it could be the usb port, so I cleaned it. It helped a bit, in that usb insertion/unplug events are detected all the time again, but didn't help with my problem.
I've used two kernel's at this point. 2012.03.05 Entropy and the kernel that came with PA 2.57 (which is 2.6.35.7). I've also tried a complete nandroid recovery I made from a "stockish" system back in April 2012. Didn't change behavior of device. I've also tried an nandroid I made of an ICS ROM I fooled with before Christmas. No dice either.
I'm currently back and running Paranoid Android 2.57, which I'm very pleased with overall.
Just to clarify, and because I've been fooling with this problem for a few days now, this is what's happening:
When Nothing is connected (No USB or AC)
* Short Power button depression does not start device
* Holding power button down for 5+ seconds the screen flickers on, and the "pre battery loading" animation shows for a second. Very rarely does the battery actually show. Before the actually battery graphic is actually shown, the device reboots and loops. As nothing is plugged in, I don't see why this sequence should even be loading. It *should* show the samsung logo, but it does not for some reason.
* Holding power down + vol up results in same behavior as above.
* Holding power down + vol down results in download mode.
When Plugged into USB.
* Bootloop, which is normal behavior I guess with custom kernels. I can still get into download mode.
When Plugged into AC
* Under normal circumstances I'd see the pre-battery loading animation then the battery status. Then holding down the power button would start things up. In my case, nothing happens at all. It just sits there, no startup animation or other activity unless I actually depress (and hold) the power button which results in a single loop as describe above. I can get into download mode though.
Behavior I've noticed which is otherwise odd:
* It (used to) behave flakey on detecting usb insertion. Sometimes it wouldn't detect the device, with even adb failing to detect it. Now it seems to work with cleaning up the usb connections. No other changes in behavior through.
* Powering down the device completely results in all the odd behavior described above. Restarting from a running android system works fine. Restarting into recovery works fine too, so the problem is in the cold-boot process.
* The ONLY way I get the device to boot up after powering down is to go into download mode. When I flash a kernel, which resets the device (warm boot?) As soon as it resets, I can hold down the power and vol-up to get into cwm recovery. If I let it continue I get a normal boot.
The only thing I can think of at this point is that possibly a (boot?) partition which normally isn't touched by flashing roms or an nandroid backup was messed up. I'm pretty good with android overall, but I don't know the internals like a developer would. Is this a possibility? Thanks for the advice so far.
when this happened to me I cleaned the USB port with a tooth pic and a little rubbing alcohol
Sent from my YP-G70 using xda app-developers app
xterminus said:
No Hardware mods. The above code resulted in the following in my dmesg
Code:
<6>[ 1207.038888] Parameters have been set as DEFAULT values...
<6>[ 1207.046140] -----------------------------------------------------
<6>[ 1207.050839] Information of Parameters
<6>[ 1207.054614] -----------------------------------------------------
<6>[ 1207.062599] - param_magic : 0x72726624
<6>[ 1207.065725] - param_version : 0x13
<6>[ 1207.069769] - 0. SERIAL_SPEED : 7
<6>[ 1207.073483] - 1. LOAD_RAMDISK : 0
<6>[ 1207.077908] - 2. BOOT_DELAY : 0
<6>[ 1207.081888] - 3. LCD_LEVEL : 97
<6>[ 1207.084413] - 4. SWITCH_SEL : 1
<6>[ 1207.087973] - 5. PHONE_DEBUG_ON : 0
<6>[ 1207.091895] - 6. LCD_DIM_LEVEL : 17
<6>[ 1207.096636] - 7. LCD_DIM_TIME : 0
<6>[ 1207.099345] - 8. MELODY_LEVEL : 0
<6>[ 1207.103233] - 9. REBOOT_MODE : 0
<6>[ 1207.106878] - 10. NATION_SEL : 0
<6>[ 1207.111616] - 11. LANGUAGE_SEL : 0
<6>[ 1207.114203] - 12. SET_DEFAULT_PARAM : 0
<6>[ 1207.118078] - 15. VERSION(STR) : I8315XXIE00
<6>[ 1207.122962] - 16. CMDLINE(STR) : console=ttySAC2,115200
<6>[ 1207.129529] -----------------------------------------------------
I figured it could be the usb port, so I cleaned it. It helped a bit, in that usb insertion/unplug events are detected all the time again, but didn't help with my problem.
I've used two kernel's at this point. 2012.03.05 Entropy and the kernel that came with PA 2.57 (which is 2.6.35.7). I've also tried a complete nandroid recovery I made from a "stockish" system back in April 2012. Didn't change behavior of device. I've also tried an nandroid I made of an ICS ROM I fooled with before Christmas. No dice either.
I'm currently back and running Paranoid Android 2.57, which I'm very pleased with overall.
Just to clarify, and because I've been fooling with this problem for a few days now, this is what's happening:
When Nothing is connected (No USB or AC)
* Short Power button depression does not start device
* Holding power button down for 5+ seconds the screen flickers on, and the "pre battery loading" animation shows for a second. Very rarely does the battery actually show. Before the actually battery graphic is actually shown, the device reboots and loops. As nothing is plugged in, I don't see why this sequence should even be loading. It *should* show the samsung logo, but it does not for some reason.
* Holding power down + vol up results in same behavior as above.
* Holding power down + vol down results in download mode.
When Plugged into USB.
* Bootloop, which is normal behavior I guess with custom kernels. I can still get into download mode.
When Plugged into AC
* Under normal circumstances I'd see the pre-battery loading animation then the battery status. Then holding down the power button would start things up. In my case, nothing happens at all. It just sits there, no startup animation or other activity unless I actually depress (and hold) the power button which results in a single loop as describe above. I can get into download mode though.
Behavior I've noticed which is otherwise odd:
* It (used to) behave flakey on detecting usb insertion. Sometimes it wouldn't detect the device, with even adb failing to detect it. Now it seems to work with cleaning up the usb connections. No other changes in behavior through.
* Powering down the device completely results in all the odd behavior described above. Restarting from a running android system works fine. Restarting into recovery works fine too, so the problem is in the cold-boot process.
* The ONLY way I get the device to boot up after powering down is to go into download mode. When I flash a kernel, which resets the device (warm boot?) As soon as it resets, I can hold down the power and vol-up to get into cwm recovery. If I let it continue I get a normal boot.
The only thing I can think of at this point is that possibly a (boot?) partition which normally isn't touched by flashing roms or an nandroid backup was messed up. I'm pretty good with android overall, but I don't know the internals like a developer would. Is this a possibility? Thanks for the advice so far.
Click to expand...
Click to collapse
Very intriguing. That is what I thought too, but there are only 3 boot partitions that I know of. If either of the first two (PBL and SBL) are corrupted, you're bricked. The third is boot loader config, which you just reset.
What happens when you are plugged into USB and you run adb reboot? You still loop, right? And you say you can reboot fine into recovery. Is that also true on Gingerbread? I know that on JB, low power mode is disabled when booting into recovery.
Now I'm beginning to think it may be a battery/charging circuit issue. After all, it is getting stuck in "low power mode". Does your battery still charge normally? Try draining your battery completely. Use it all the way normally; then reboot into recovery and wait until it shuts off. (Note that wiping battery stats is completely unrelated.) Hopefully that will de-confuse your device.
Sent from my Galaxy Nexus
Mevordel said:
Very intriguing. That is what I thought too, but there are only 3 boot partitions that I know of. If either of the first two (PBL and SBL) are corrupted, you're bricked. The third is boot loader config, which you just reset.
What happens when you are plugged into USB and you run adb reboot? You still loop, right? And you say you can reboot fine into recovery. Is that also true on Gingerbread? I know that on JB, low power mode is disabled when booting into recovery.
Now I'm beginning to think it may be a battery/charging circuit issue. After all, it is getting stuck in "low power mode". Does your battery still charge normally? Try draining your battery completely. Use it all the way normally; then reboot into recovery and wait until it shuts off. (Note that wiping battery stats is completely unrelated.) Hopefully that will de-confuse your device.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
adb reboot works fine. I have problems on a cold-boot or startup from scratch. I've been getting into cwm by flashing the kernel and immediately pressing power/volup. (Or going into recovery via adb or the power-off menu). From a cold-boot, cwm is just as inacessible as the normal android boot without a kernel flash.
Charging seems to work fine while the device is up and running. Charging while powered off doesn't seem to do anything but loop (even from ac power).
I'll run down the power like you suggested. Hopefully that'll clear things up.
follow up
Discharging the battery to 5%, then booting into cwm and letting the battery discharge to completely seemed to do the trick. As soon as I plugged it into the AC, the proper battery charging icon popped up, and it seems to start up now without issues.
Thanks Mevordel for your help.
Hi guys,
My step daughters tablet, the 7" Dual Core 4GB Trio Stealth G2 Hype, has frozen at the "Trio Stealth G2" logo boot screen. It won't go any further. I've tried every combination of key presses (pwr & vol+, pwr & vol-, pwr & vol-,vol+) to get it into recovery mode OR to hard reset it and nothing is working. I've tried hooking it up to my windows 7 computer, it shows up as M3-CHIP (only after I press pwr & vol-). I downloaded the android adt bundle like someone else suggested and then adding the hardware id of the device to the file called android_winusb.inf BUT that file doesn't exist anywhere within the adt bundle. I even just tried creating the file and adding the hardware id to the file I copied from another thread and when I click update driver and choose where that file is that I created it won't take, it says windows couldn't find a driver for this device.
Here's the file I created
Code:
;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 08/11/2009,2.0.0010.00002
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg
[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1
[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64
[Google.NTx86]
;Orange San Francisco
%SingleAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_02
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;TrioStealthG2Mine
%SingleAdbInterface% = USB_Install, USB\VID_1B8E&PID_C003&REV_0007
%CompositeAdbInterface% = USB_Install, USB\VID_1B8E&PID_C003&REV_0007
;TrioStealthG2
%SingleAdbInterface% = USB_Install, USB\VID_16D5&PID_8005&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_16D5&PID_8005&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
[Google.NTamd64]
;Orange San Francisco
%SingleAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_02
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall
[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys
[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install
[WinUSB_Install]
KmdfLibraryVersion = 1.7
[USB_Install.HW]
AddReg = Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"
[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller0100 7.dll,WdfCoInstaller","WinUSBCoInstaller.dll"
[CoInstallers_CopyFiles]
WinUSBCoInstaller.dll
WdfCoInstaller01007.dll
[DestinationDirs]
CoInstallers_CopyFiles=11
[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64
[SourceDisksFiles.x86]
WinUSBCoInstaller.dll = 1
WdfCoInstaller01007.dll = 1
[SourceDisksFiles.amd64]
WinUSBCoInstaller.dll = 2
WdfCoInstaller01007.dll = 2
[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"
I also don't believe I had enabled the usb debugging before it froze in this state so am I screwed or what?
It happened even to me.... something happened in your system folder.... to make your device work again you must do a restore ( in recovery mode) of a backup that you have made before this accident happened if you did not do a backup of your device you must do it from another device
Sent from my GT-S5310 using XDA Premium 4 mobile app
---------- Post added at 09:30 AM ---------- Previous post was at 09:26 AM ----------
Of the same type otherwise your device will never work again amd you'll have to buy a new one
Sent from my GT-S5310 using XDA Premium 4 mobile app
leodani said:
It happened even to me.... something happened in your system folder.... to make your device work again you must do a restore ( in recovery mode) of a backup that you have made before this accident happened if you did not do a backup of your device you must do it from another device
Sent from my GT-S5310 using XDA Premium 4 mobile app
---------- Post added at 09:30 AM ---------- Previous post was at 09:26 AM ----------
Of the same type otherwise your device will never work again amd you'll have to buy a new one
Sent from my GT-S5310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how would i do a restore of a backup if i can't get it connected to the computer? I suppose I could buy another one, make a backup of it and then return it to officemax BUT can you link me to how I would create the backup and then how I would restore please?
You could install a custom recovery (like Clockwork Mod) and do it from there but if you do a backup of your brikcked device... when you do the restore it will stay bricked so you have 2 options:
1) make a backup from the same device of a person you know.... there is one big problem of this... you'll get the same IMEI number as the other phone
2) buy a new one
Sent from my GT-S5310 using XDA Premium 4 mobile app
Hard Reset G2 – In the case of password lockouts or freezing, doing a hard reset on your android device could help you get back to the factory defaults. First you need to make sure your tablet is powered off. Hold down on the Volume + button and hold down the Power button at the same time. As soon as the tablet's screen turns on let go of the Power button but keep the Volume + button held down until you see a large Android in the center of the screen. At this point you will see a screen with boot options. Use the Volume – button to go down to Wipe Data Factory Reset and tap the Power button to select this option. On the next screen use the Volume – button again to go down to Yes and use the Power button to select. At this point it will be going through the wiping and resetting process. When it's done you will see the first screen you came to when you first started the setup. Just tap the Power button to select Reboot System Now.
Make sure tablet is powered off.
Hold down Volume + button and Power button at same time.
When screen comes on let go of Power button.
When the large Android shows on screen let go of Volume + button.
Use Volume – button to scroll to Wipe Data/ Factory Reset
Tap Power button to select.
Use Volume – button to scroll to Yes.
Tap Power button to select.
Tap Power button to select Reboot System Now.
Think im screwed
Ok so I have a tri stealth g2 which was froze at boot logo, I was able to use aml flash tool and erased nand, unfortunatley the rom I installed was Novo7 which said it installed successsfully but I tried to power on my trio and nothing came on at all; however when I plug it in to my pc it comes up as a novo7 portable media player device and lets me access the internal storage. The problem is how can I flash from the internal storage, is there a program that will allow me to erase all data? The internal storage reports 5.47 gb and 5.37 gb free. Once again nothing comes on the screen so trying to gain access to any recovery not possible. I was hoping I could change the driver for the device back to the world cup driver for aml but it refuses to do it saying the driver isnt compatible grrrr. If anyone can help be appreciated.
Ok so I used adt bundle and got the device to change to Android ADB Interface tried livesuit, didnt work anyone have any suggestions?
leodani said:
It happened even to me.... something happened in your system folder.... to make your device work again you must do a restore ( in recovery mode) of a backup that you have made before this accident happened if you did not do a backup of your device you must do it from another device
Sent from my GT-S5310 using XDA Premium 4 mobile app
---------- Post added at 09:30 AM ---------- Previous post was at 09:26 AM ----------
Of the same type otherwise your device will never work again amd you'll have to buy a new one
Sent from my GT-S5310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so how do I back up for another device?
leodani said:
You could install a custom recovery (like Clockwork Mod) and do it from there but if you do a backup of your brikcked device... when you do the restore it will stay bricked so you have 2 options:
1) make a backup from the same device of a person you know.... there is one big problem of this... you'll get the same IMEI number as the other phone
2) buy a new one
Sent from my GT-S5310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That can't possibly be true, I've never seen an Android device that had the built in factory reset functionality removed...
fail
I tried tried th Power button/ volume - button and it worked, but no it doesnt. it just stays on the boot screen
Need some help with Stealth G2 10.1
Hey can anyone tell me if its fixable, i got a Trio Stealth - 10 MST 10-21. I have been searching everywhere on how to fix my problem.
So the tablet freezes on the boot screen i tried all the buttons to get to recovery mode, but i don't think it is working because once i get the correct buttons to recovery the screen turns black and nothing else happens i hold the +volume button & power button and i only get a glimmer of black i hold it for minutes at a time to see if anything happens and nothing. My questions are am i using the correct button configuration to go in to recovery? and is this fixable?
Tablet not rooted stock firmware
Thanks in advance for your help.
Same problem
I have the same Tablet and same problem. This is what I do. Leave it unplugged and on to drain the battery. After it has totally drained, recharge it then turn it on. If still won't turn on try the reset button. I use a needle to reset the tiny hole. If that won't work, hold the volume + and power buttons and hold until it turns on. This takes awhile to get it on. Then let go of the power button. If that doesn't work, I just try all the buttons and keep pushing them all and have got it to turn on. What causes mine to go black is if I hold the power button on too long. Just press it until you see Trio and let go immediately. It sucks. The tablet is actually great but that and really poor sound is its drawback.
rodlopez619 said:
Hey can anyone tell me if its fixable, i got a Trio Stealth - 10 MST 10-21. I have been searching everywhere on how to fix my problem.
So the tablet freezes on the boot screen i tried all the buttons to get to recovery mode, but i don't think it is working because once i get the correct buttons to recovery the screen turns black and nothing else happens i hold the +volume button & power button and i only get a glimmer of black i hold it for minutes at a time to see if anything happens and nothing. My questions are am i using the correct button configuration to go in to recovery? and is this fixable?
Tablet not rooted stock firmware
Thanks in advance for your help.
Click to expand...
Click to collapse
Boot Logo
Same problem, stuck at boot trying to fix for a friend but it's looking doubtful now.
And it's missing the vol and power key so i have to use things to poke at them.
Things I've noticed though.
red charging LED turns green after hitting the small reset button.
If I keep holding down the vol+ after powering up it will stay green as soon as I let it go..
it turns red.
If I use vol+ with power and do not reset it then it will stay red.
same problem here
Trio Stealth G4 7 frozen at boot logo
Hi guys...
I made a mistake..
I download "Cydia Impactor" for rooting mi device and by mistake I clicked in the menu "device/Bootloader" option (I do not what is that option for) and now my tablet is frozen at boot logo when it restart.
I saw that my computer recognize de tablet like "USB Developer" when I connect it to the USB port but in the explorer I can not see any device letter assigned to the tablet (E:, F: G: etc.).
What can I do????
Also y tried to restart pressing (Volumen down and Power on together) for factoring reset but nothing happen.
Somebody can help me??? thanks.
Found it!!!
[email protected] said:
Hi guys...
I made a mistake..
I download "Cydia Impactor" for rooting mi device and by mistake I clicked in the menu "device/Bootloader" option (I do not what is that option for) and now my tablet is frozen at boot logo when it restart.
I saw that my computer recognize de tablet like "USB Developer" when I connect it to the USB port but in the explorer I can not see any device letter assigned to the tablet (E:, F: G: etc.).
What can I do????
Also y tried to restart pressing (Volumen down and Power on together) for factoring reset but nothing happen.
Somebody can help me??? thanks.
Click to expand...
Click to collapse
After a day or two of searching I have finally found the stock firmware for the trio stealth g2 hype. Downloaded it from baidu and flashed with out an issue.
The file can be had at this link; for those who don't know how to download from baidu I will am uploading it to 4shared now.
Edit: link to the file on 4shared.
To install just extract the files unto a sdcard and power on the tablet while pressing volume down.
Have a trio g2 with same problem. Sticking at the A9 screen. I got to the recovery screen and reformatted, wiped cache and wiped media. One right after the other. Done a restart from the recovery screen and behold.....It went to the setup screen like when it was new. Hope it works for others. I tried all of the above mentioned, except for the flashing.
irapeace said:
Have a trio g2 with same problem. Sticking at the A9 screen. I got to the recovery screen and reformatted, wiped cache and wiped media. One right after the other. Done a restart from the recovery screen and behold.....It went to the setup screen like when it was new. Hope it works for others. I tried all of the above mentioned, except for the flashing.
Click to expand...
Click to collapse
I just did the same thing, and it worked for me too!
To enter the recovery screen, you press the volume down button and the power button . . . not the volume up button like others have stated. Once in recovery, I wiped cache and did a factory reset, then rebooted the device. It went to the setup screen! And it only took me 5 minutes!
Berthfield said:
After a day or two of searching I have finally found the stock firmware for the trio stealth g2 hype. Downloaded it from baidu and flashed with out an issue.
The file can be had at this link; for those who don't know how to download from baidu I will am uploading it to 4shared now.
Edit: link to the file on 4shared.
To install just extract the files unto a sdcard and power on the tablet while pressing volume down.
Click to expand...
Click to collapse
I've mirrored the download to a less garbage file host. 4shared forces you to create an account to download at 25KB/s. Totally BS.
https://mega.nz/#!RNBmjBrI!hSmMhkf8acjjEzSBuBSsKWRcEgulSYGEbEmuxSaZLP8
I realize this is an older , (to say the least) post. But could someone please tell me do I need to format the Micro SD, to make it bootable, or can I simply unzip it onto the SD and start up the tablet using the ways described in the posts on this tread? It almost seems too easy, but any help...any at all, even the littlest, tiniest ity-bity bit would be so , so, so very greatly appreciated. Thanks for your time this evening.
I want to be able to have the Slate 21 tablet boot up automatically (if it's shut off) when power is plugged in.
i have tried to use the command that works on Nexus7, but no success:
reboot bootloader
fastboot oem-off-mode charge 0
Any idea what to do?
Thanks,