Database Users

DREA100 and the infamous Triangle of death?

Ok.. So a friend of mine suddenly got a triangle with the exclamation mark picture on his phone. That's all it boots up to. So, he took it to T-mobile, they told him it's FUBAR, and sold him a new phone.
The fact that the thing boots to a recovery mode tells me that there's SOME way to un-FUBAR this phone. My friend is too technologically inadiquate to attempt to do any modifying, so I'm going to assume he was at whatever firmware level would hve been blasted out to T-mobile as of last Friday 01/15/2010.
If I boot the phone normally, it gives me the TriAngle. I pop open the keyboard and hit alt-L and the I get the Android System Recovery menu. at the bottom I get "E:CAn't open /cache/recovery/command"
I've spent all day bouncing around this forum, and many like it, downloaded all sorts of G1 fimwares trying to go back to RC29, RC28, 30, 33.. gah! The latest one I'm trying to update to is "signed-kila-ota-116143-prereq.TC4-RC19+RC28+RC29.zip" Which i rename to update.zip . I hit alt-L, select 'update from SD card' It goes through:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update package....
Installation aborted.
That's it... no more log than that.
I've done the Alt-W, and Alt-S.. wiped cache partition. I think playing around with the recent firmwares might be fun, but I'd like to get this bad boy reset back to factory defaults. I've read the forums here on how to do that.. but all of the procedures fail.
I can get Windows 7 to recognize the phone, but I cannot access the sd card while it is in the phone. I've been transfering data to it by taking the sdcard out, and putting it into a known good SD card reader. I've formatted the sdcard to FAT16, and FAT32 quick and not quick.
Seriously.. why is this so complicated? Now I need some serious digging assistance. Is there an interface that will allow me to directly talk to this phone via the USB cable? How can I force an firmware onto it? Clearly something is functional, or I would get no I/O. How can I get this silly thing back to where it was? I know this thread seems like a redundant one, but as far as I can tell, its not. The typical procedures posted here don't seem to work, but I'll be happy to run through any steps y'all suggest. I'll resign that it's been bricked if that's really whats happened.. but I'm not ready to throw this unit away yet.
Ask questions.. let me answer them. I know this team can get this phone working again.
Thanks y'all.
--Rob aka The Austin Slacker.

Have you tried the RC29 DREAIMG.nbh file?
http://forum.xda-developers.com/showpost.php?p=4593084&postcount=1

Roadmasta01 said:
Have you tried the RC29 DREAIMG.nbh file?
http://forum.xda-developers.com/showpost.php?p=4593084&postcount=1
Click to expand...
Click to collapse
bingo !
sounds like your friend tried to flash something he shouldn't have. or messed around with stuff he shouldn't.
as far as taking it to the store, and accepting their suggestion to "GIVE US YOUR MONEY!" that was a mistake.
the phone is likely fine, and maybe you'll buy it from him for cheap, then fix, resell/use.
good luck, should be easy.

The "press camera and power to get to bootloader" procedure. I've tried holding the Camera while pressing power over and over and all I get is the triangle. However if I press power and the "back" button (swooping arrow to the left), I'll get the bars screen, and a Gray screen telling me to press send to restore.... Which is all good, but there's no progress or any thing to indicate that i've done something by pressing the send button.(based on cell phone standards, I'm assuming "send" is the green "call" button.
Is this normal?
No yeah.. he gave me the G1.. its mine. I just need to fix the little bugger.. .. well.. then laugh at him

Ok.. one more day (well ok.. couple hours) of fiddling with this thing, and i'm begining to wonder if Microsoft was involved. I'm not able to get this poor G1 to do anything new. I tried using a different SD card, hoping perhaps the one I got with it was bad... no dice. camera + power doesn't do anything useful.
I can connect it to the PC.. but i can't see the data card that way. adb devices reads no output, so its not correctly attaching to the PC (tried Windows 7 32bit, and Windows XP 64bit).. There's gotta be a good way to force a known good image onto this silly thing.
Is it probable that the internal memory has gotten corrupt somehow? I know someone out there's got the golden suggestion, please do tell if you do. I'd really like to use this phone.
--Rob

If you can get into fast boot (the tri color screen) there are ways to flash it... try getting into your tri color, then plugging in the USB cable and see if it switches from Serial 0 to USB at the bottom, if so you are golden to flash using the fast boot method.
There are guides around on how exactly to do that, as well a couple places that you can download the official RUU that will do all the hard work for you!

gah.. nothing doing. I can hit Back and Home, and end up with the tri-color screen for about 1/5th of a second, then a gray screen saying:
This operation will delete all your personal data, and reset all settings to manufacturer default. Press Send to restore manufacturer default, or press other keys to cancel.
At this point, the unit is dead. I can remove the battery, and continue on my little quest.. but hitting *any* key at all (including the Send key) will not produce any sort of output. I've tried pressing Send one time, then setting the phone down for a full hour (watched a netflix show) nothing. I can't power it off either w/o removing the battery.
I would throw in the towel.. but from all the research i've been doing, it seems as if this one is behaving in a manner in which other forum users havne't posted. Maybe by continuing to try options and post results, a positive outcome will come out, and someone else who has a G1 behaving this way will have an easier time.
... or y'all can tell me that its toast and to bugger off.. ha ha.. either way.. I continue to google. If you can think of anything, please toss it out.
OH!.. tried an RUU.. found one called. RhodiumSPLRelocker Looks promising.. but can't see the device when attached to the PC... yeah.. guess the phone has to have a functioning OS before that will happen...

You would want a Dream RUU... I looked around a bit and couldn't find one. Maybe someone has a quick link?
Double check that your SD card is formatted FAT32 and see if you can get ADB to see it when on that greay screen.

I've formatted the SD card in FAT32 multiple times.. I even questioned if my Windows 7 32bit would do it, and formatted it on a laptop running XP 64bit. adb doesn't seem to see it ever.
I don't get why I can't get it into fast boot. I've been looking on ebay for dream G1s with broken screens.. heh.. I guess i'm preparing for the worst. really sad, becasue this G1 was actually pretty well taken care of. My friend didn't do anything he shouldn't. HE woke up one morning and it was like this. He lives out in the country.. so he gets pretty spotty signal. I'm wondering if T-Mobile didn't push out an update, and it got interrupted by signal loss.
By the by... I've been doing all this work w/o a SIM card. Does that matter?

austinslacker said:
(based on cell phone standards, I'm assuming "send" is the green "call" button.
Click to expand...
Click to collapse
its not the green send button -- its the red end button
see below extracted from http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
Load the DreaIMG.nbh File
1. Download the Original DreaIMG.nbh file:
http://www.megaupload.com/?d=XXSQ0T7W
2. If the file downloaded above downloads as a .Zip file, please unzip it first then put the DreamIMG.nbh file that is inside on the SD card, NOT in any folder. (If you did Section I the phone is off still, take out the memory card, put it in the MicroSD adapter and plug it into your computer to transfer the file over, since your G1 won’t turn on right now if you did Section I above. Otherwise if you did not need to do Section I above, then you can just put it on the SD card normally using the usb cable and the phone).
3. Turn the phone off if it is on.
4. Turn on the phone by holding the Camera button and the End key until the bootloader screen turns on.
5. Hit the End key to start the update. DO NOT INTERUPT THIS PROCESS.
6. Once it is done, hit the trackball to restart the phone. You now are on the stock firmware RC29

austinslacker said:
The "press camera and power to get to bootloader" procedure. I've tried holding the Camera while pressing power over and over and all I get is the triangle. However if I press power and the "back" button (swooping arrow to the left), I'll get the bars screen, and a Gray screen telling me to press send to restore.... Which is all good, but there's no progress or any thing to indicate that i've done something by pressing the send button.(based on cell phone standards, I'm assuming "send" is the green "call" button.
Is this normal?
No yeah.. he gave me the G1.. its mine. I just need to fix the little bugger.. .. well.. then laugh at him
Click to expand...
Click to collapse
You mention that you can access fastboot by pressing the back button while turning it on, isn't that how the hero gets into fastboot? maybe your friend tried flashing a rom that was meant for the hero. if you have access to fastboot you should be able to flash a new image from there, just place the image file in the root of your card and follow the fastboot instructions

Also if fastboot isn't doing it for you have you tried adb? if you don't know what that is look it up I've seen a couple guides on how to do it and they are really detailed.

Im having the same problem, Im stuck in the recover triangle of death. Ive done the alt+w and reboot, the RC29 DREAIMG.nbh , the update.zip, camera+power, I cant get the gray screen to pop. Nothing, its brickkkkeeeddddd, FUBAR. There has got to be someway I can reload this G1. I wasnt trying to root it or anything. I was bowling and then it triangled on me. Anyone have any ideas at all on how to fix it?

Triangle of Death
I'm from Brazil, I can't take it to t-mobile to fix...
when i tried to root my G1 did the downgrade perfectly, the screen was just as it was suposed to be.
But in the recovery mode boot, appeared this triangle with an exclamation...
what do i do now???? help plz!

deftoneage12 said:
Im having the same problem, Im stuck in the recover triangle of death. Ive done the alt+w and reboot, the RC29 DREAIMG.nbh , the update.zip, camera+power, I cant get the gray screen to pop. Nothing, its brickkkkeeeddddd, FUBAR. There has got to be someway I can reload this G1. I wasnt trying to root it or anything. I was bowling and then it triangled on me. Anyone have any ideas at all on how to fix it?
Click to expand...
Click to collapse
Any one have any ideas? hell ill pay someone to fix it for me

The only idea I have is make'ing an goldcard so your sure your phone accepts the update (dreaimg)... other than that...
Sent from my HTC Dream G1 using the XDA mobile application powered by Tapatalk

Any chance the home button is stuck? I'm not 100%, but I think if you were to hold home, camera and power, the recovery would come out on top.

Home button is not stuck, and cant seem to figure out the CID of my SD card since my phone is unaccessable.

People with hardware locked vibrants..

What can we do? I dont want to mess with anything again because i know if anything goes wrong i cant get in to download mode.. But i too want to flash the new roms and gps fixes. Is there anyway to make the hardware buttons unlocked?

Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.

You can root using clockworks and run some of the patch through clockworks too. Try not to use odin unless you really know what you're doing. A lot have odin hang on them. Other than that, you can flash rom using clockworks.
Sent from my SGH-T959 using XDA App

jonathan3579 said:
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
Click to expand...
Click to collapse
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*

TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.

glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
exactly my point. this is what happened to me. but think about this lets say i flash a rom right and you know how sometimes it hangs on the vibrant screen and just stays there. and in order to get it back i am going have to use odin. which i cant.......... so i think i wont mess with anything anymore. Rather just wait for official 2.2 ota update.

Chief Geek said:
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
Click to expand...
Click to collapse
Take it back and do a warranty exchange cause the buttons arent working correctly.

I've never tried it because I could never get Kies to connect to my phone, but isn't there a way to update firmware through Kies? I know the i9000 guys use Kies to upgrade, but I think that's only to get drivers and the updates though. I wish Samsung had a better interface than Odin to flash firmware. It's absolute garbage.

Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????

glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
This is how I got out of "phone to pc"
get into download mode (i went through it manually, as in plug in the phone, and pressing the volume buttons together at the same time)
Connected to ODIN, and by perfect accident, I clicked on "start" without placing ANY files in ANY spots.
This is what I thought "OMG $h!t" Well my phone was already bricked enough, so i just let it run its course through ODIN. My phone magically rebooted, and it booted into the ROM i had installed before I got the "phone to pc" problem.

Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA

demo23019 said:
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
Click to expand...
Click to collapse
The disadvantage is that it is harder (maybe impossible in some situations?) to get into the Download mode if something goes wrong during a ROM update. You can still load custom ROMS but if something goes wrong, you might not be able to get to Download mode to be able to fix it.
I had the phone ! PC screen on mine when I first tried to unsuccessfully flash Vibrant8. Luckily, my Vibrant doesn't seem to be hardware locked and I was able to get back into Download mode and re-flash it with Odin.

I'm able to access download mode with volume keys and i can access recovery mode so i guess im ok
also date on box is 8/27/10

How do you know whether you have a hardware locked Vibrant or not?

No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene

eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I trust what you're saying.. but is there any way to test that out without having an already bricked phone? I want to make sure I can recover my phone before flashing your Vibrant hybrid ROM. So after Step 6 do you get the download mode screen? Or does ODIN now show a COM port and it works, even without the little digger guy?

eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).

johnny12times said:
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
Click to expand...
Click to collapse
Download Mode is controlled by SBL, so if they truly changed anything that would be the cause.
I would think you could target redbend to update the SBL or even boot.bin bml /stl location.. I've not tried this, nor do I need too.. Just tossing options out there for people to try & don't mind risking a brick..
If you can get the SBL / Boot.bin for the Stock to flash via redbend, then this will solve the HW locks.. Now, Regarding my Phone, I can still get into Download Mode however, only by doing the USB trick &/or ADB reboot download.
I can not get into recovery unless I use clockwork Manager or ADB into
By the way, this is not a Hardware Lock issue as the thread states.. Not being able to get into download Mode like described, is a zImage issue & not the SBL / BOOT.bin
just as a FYI.
~Eugene

Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
Click to expand...
Click to collapse
Its happening because you ran a full titanium backup including system data. Yeah, dont do that. Reflash, then reinstall user apps with data, and pick and choose the system ones that are obvious (mms, bluetooth settings, wireless settings, etc.) Then reboot for changes to take effect. When in doubt, dont restore.
Good luck. Although you won't need it if you do what I just told you.
Sent from my SGH-T959 using Tapatalk

Just to share...
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I had the phone!computer bricked Vibrant, and just got my replacement from Asurion (in fact, of the phones in front of me are from Asurion since my original got stolen 2days after it came out ).
On phone1: The original TMO date is 8/12/2010, while the Asurion date is 8/19/2010. Also the ID is GJ/HLP. This one was HW Locked.
On phone2: The original TMO date is 9/2/2010, while the Asurion date is 9/10/2010. Also the ID is SM/HLP. This one doesn't seem to be HW Loocked, I can get into recovery easily, DL Mode ... not so much . Booting with vol+&- gets me into recovery, but booting with just vol- does nothing ...
Any thoughts?

it just froze up, I reset a couple times, then tried power+vol up then..

Not sure what the heck happened to my device. I was using it when it just froze up outta nowhere. I tried resetting it a couple times but it wouldnt get past the android screen. Hard Reset, nothing. So I tried going into APX mode, power+vol up(idk why) then, it wouldnt get past the 'Acer' screen after that. So I let it charge overnight now it doesn't show anything at all. The power button does light up, but thats it. what the heck just happened?
NOTE: I lent out my sdcard with the update.zip in it. would putting my sdcard back in fix the problem or is it bigger than that?
is this thread a possible solution to my problem? problems seem similiar
http://forum.xda-developers.com/showthread.php?t=1874345
can someone please help me find out what happened with this, I really dont wanna call Acer n send it in if I can fix the problem myself

500tab said:
Not sure what the heck happened to my device. I was using it when it just froze up outta nowhere. I tried resetting it a couple times but it wouldnt get past the android screen. Hard Reset, nothing. So I tried going into APX mode, power+vol up(idk why) then, it wouldnt get past the 'Acer' screen after that. So I let it charge overnight now it doesn't show anything at all. The power button does light up, but thats it. what the heck just happened?
NOTE: I lent out my sdcard with the update.zip in it. would putting my sdcard back in fix the problem or is it bigger than that?
is this thread a possible solution to my problem? problems seem similiar
http://forum.xda-developers.com/showthread.php?t=1874345
can someone please help me find out what happened with this, I really dont wanna call Acer n send it in if I can fix the problem myself
Click to expand...
Click to collapse
Eh, well, need to know the condition of the tab. Sounds like it is stuck in APX mode. (Black display, white PWR light). Is this the case?
Generally, you might be able to PWR down, by press and hold the pwr button for several seconds. Then try to boot it normally.
Oh, BTW, Pwr and Vol+ is not how to get it to APX. That usually gets the stock bootloader which really isn't much of anything unless you have an update.zip on your ext sd card.
Were you completely stock? (not rooted or custom rom)
MD

Yes that's the condition, black screen white pwr light. It is rooted, thats it. Running ICS 4.0. I wont be able to get my sd card until wednesday so if I need that update.zip file I'll have to wait a few more days. Its completely off right now, I tried powering on and off a few times and I got nothing just a blank screen. Im unsure, what to try next??

500tab said:
Yes that's the condition, black screen white pwr light. It is rooted, thats it. Running ICS 4.0. I wont be able to get my sd card until wednesday so if I need that update.zip file I'll have to wait a few more days. Its completely off right now, I tried powering on and off a few times and I got nothing just a blank screen. Im unsure, what to try next??
Click to expand...
Click to collapse
Yeah, you're going to need an SD card. And make sure the tab is charged.
In the meantime, you can try a couple things just to see it you can get a different response. However, understand this.
1. You can probably forget any personal data that's stored on it. Photos, downloads, music, etc. Just to prepare you.
2. You probably have a corrupted bootloader partition. How it happens, with a normally functioning tab, nobody really knows.
You can try doing a data wipe. Usually we would wait till you get an SD card, but I'm curious if you can get anything on the display. To do this, with the tablet off, Press and hold PWR, while at the same time, continiously cycle your rotation lock left and right, quickly until you see "erasing user data" or something similar on the display.
Another thing, manually put it into APX mode. This involves using a paper clip, and press and hold the "reset" button near the USB port, then press and hold PWR. Count to 4 and release PWR, and 1 second later release the paperclip. Then plug your tablet into the PC, and see if the PC loads the drivers for it. You should already have installed the Acer USB drivers. If not, get them from the Acer site.
Understand, your chances of getting it going again, are less than 50/50. But, we all will give it a shot.
MD

This is exactly the situation I'm in... Black screen, White power light...
I was in the middle of an app, when tablet rebooted, wouldn't boot back up..
I was able to get into CWM recovery... investigated, and found that /system wouldn't mount... So, I was prepared to re-flash, so I first went to do a nandroid backup of my data folder... I also had an old nandroid backup, so I decided to restore that... After I did that, I couldn't even get into recovery anymore...
I've tried setting my tablet into apx mode, and trying to flash, but they always seem to freeze at "uploading image" (both with afterota unbrick and blackthund3r's tool)
Now, blackthund3r's tool will actually get the acer logo to show up, with "Entering download mode...", so that leads me to think the tablet isn't completely shot? It just gets stuck during the upload image...
Tried the erasing data as suggested by MD, but no luck, just black screen...
What is the sdcard method that you are speaking of? Is there anything else I can try?
Thanks in advance
---------
Edit:
Tried placing update.zip on sdcard for flashing, tried turning on the tablet with volume down...No joy
Hopefully someone has some other ideas for me? Thanks again in advance.
---------
Edit 2:
After a day of searching, finally came across this post.
Fixed and saved my tablet... Whew!

[Q] Phone not booting correctly, installed a ROM incorrectly

Today I was finally able to get my phone rooted, install SafeStrap and get into TouchWiz. Thing is, I dislike TouchWiz so I downloaded CyanogenMod for note 3. I put the CyanogenMod zip in my downloads folder on my Note 3. I went into safestrap, clicked install, found the .zip and swiped to flash. After that finished I clicked reboot and I got black screened. I then took the battery out and then the **** hit the fan. I booted the device and the SafeStrap splash screen came up along with the stock bootloader android bot image and my screen was displaying all of these colors and tripping acid. I now have taken the battery out and am hoping I can save my device. For some information on the device, It's a Galaxy Note 3 on Verizon running 4.4.2 rooted. I cant even get into ODIN mode... I've been getting tons of views and no reply's so that's leading me to believe it's something major. If it is please don't be afraid to respond and if you need a clearer explanation please PM me so I can get this fixed. I need my phone for work and I picked a really bad time to start tinkering with my phone haha. Thank you so much for reading! :cyclops:

No sure but it sounds like you hard bricked your device ( no acces to download/odin mode or recovery).
"my screen was displaying all of these colors and tripping acid" sounds like a display error.
Put in the battery and keep trying to acces odin mode if the screen is working ( Hold power + home button + volume down) .

zat0x said:
No sure but it sounds like you hard bricked your device ( no acces to download/odin mode or recovery).
"my screen was displaying all of these colors and tripping acid" sounds like a display error.
Put in the battery and keep trying to acces odin mode if the screen is working ( Hold power + home button + volume down) .
Click to expand...
Click to collapse
What should I do if that doesn't work? I've tried a few times already but I'll keep going at it. The screen has now shifted from "Tripping acid" to a white fuzzyish screen that shows the SafeStrap splashscreen kind of outlined.

Have you tried to boot into recovery? That is assuming you have a backup saved.
Put battery in...hold down power, volume up and home key...when you see Samsung logo let go of the power key only...hopefully it might boot into recovery. Just one idea...

brojoe11 said:
Have you tried to boot into recovery? That is assuming you have a backup saved.
Put battery in...hold down power, volume up and home key...when you see Samsung logo let go of the power key only...hopefully it might boot into recovery. Just one idea...
Click to expand...
Click to collapse
OMG I GOT INTO RECOVERY!! I did make a back up but I did it in SafeStrap. It dropped me in the default BootLoader with a dead android with its chest opened up. Idk if this means something haha.

If it won't let you load the backup, you might could use kies software on a desktop or notebook to recover you device back to stock. Just another idea. Sometimes with enough persistence you can recover a semi bricked device. I sure hope you get it going. A messed up phone will make you pull your hair out....

brojoe11 said:
If it won't let you load the backup, you might could use kies software on a desktop or notebook to recover you device back to stock. Just another idea. Sometimes with enough persistence you can recover a semi bricked device. I sure hope you get it going. A messed up phone will make you pull your hair out....
Click to expand...
Click to collapse
Thank you so much! :fingers-crossed:

brojoe11 said:
If it won't let you load the backup, you might could use kies software on a desktop or notebook to recover you device back to stock. Just another idea. Sometimes with enough persistence you can recover a semi bricked device. I sure hope you get it going. A messed up phone will make you pull your hair out....
Click to expand...
Click to collapse
When I plug the phone in, Kies isn't recognizing it... Thoughts?

TheCottonKid said:
When I plug the phone in, Kies isn't recognizing it... Thoughts?
Click to expand...
Click to collapse
have you tried to boot in to bootloader? Take battery out and press Vol down + home button then power button. If you get in there you can use odin 99% to flash an other rom or stock firmware

TheCottonKid said:
Thank you so much! :fingers-crossed:
Click to expand...
Click to collapse
You are welcome. Hope you got it going. :highfive:

TheCottonKid said:
Today I was finally able to get my phone rooted, install SafeStrap and get into TouchWiz. Thing is, I dislike TouchWiz so I downloaded CyanogenMod for note 3. I put the CyanogenMod zip in my downloads folder on my Note 3. I went into safestrap, clicked install, found the .zip and swiped to flash. After that finished I clicked reboot and I got black screened. I then took the battery out and then the **** hit the fan. I booted the device and the SafeStrap splash screen came up along with the stock bootloader android bot image and my screen was displaying all of these colors and tripping acid. I now have taken the battery out and am hoping I can save my device. For some information on the device, It's a Galaxy Note 3 on Verizon running 4.4.2 rooted. I cant even get into ODIN mode... I've been getting tons of views and no reply's so that's leading me to believe it's something major. If it is please don't be afraid to respond and if you need a clearer explanation please PM me so I can get this fixed. I need my phone for work and I picked a really bad time to start tinkering with my phone haha. Thank you so much for reading! :cyclops:
Click to expand...
Click to collapse
You must clarify if you can get into download (Odin) mode:
- if you can not there is some major flash corruption going on, not much you can do
- if you can get into download mode you need to write your stock ROM.

S7 Edge "Bootloader Exception" bug

Hi all,
I've received my S7 Edge today(Exynos), yay.
All was working flawlessly until few moments ago, I was running 3Dmark, and before I even start to bench, while i was downloading the first scene The screen goes all black, then after 10 seconds, there's a message on top (in the same way a rooted phone would display "kernel is not seandroid enforced..."):
Bootloader Exception
[RST_START = 0x100000000 ]
[...]
Exception: do_handler_serror: SERROR(esr: 0xbf00000000)
[...]
I didn't install any rom, root or else, it's pure stock untouched. I tried to reboot phone using volume down+power, it reboots I think (screen goes all black) but quickly the same message appears...
I'm surely going to call phone operator to tell them that phone is KO, but if one of you guys has any idea that would avoid me to send back phone to warranty, it would be nice
Thanks !

@mods : Sorry for posting in wrong section

Try this...
https://www.youtube.com/watch?v=UV0Zp7F1LHs

I'd suggest a factory reset if the above fails.
Hold Power + Volume Up + Menu
Then use the volume keys to scroll to factory reset and select using menu or power buttons.

Hi guys,
Thanks very much for you answers,
Unfortunately any key combination is not working can't get into recovery nor download mode ...
I don't want to try Odin, scared about potential warranty issues ... but it kills me to have to send the phone back to sammy and wait ..

Mr_PoPoP said:
Hi guys,
Thanks very much for you answers,
Unfortunately any key combination is not working can't get into recovery nor download mode ...
I don't want to try Odin, scared about potential warranty issues ... but it kills me to have to send the phone back to sammy and wait ..
Click to expand...
Click to collapse
The phone must be off for the Volume Up + Power + Home button combination to work. Keep those pressed for like 10 seconds, even after the phone powers on. I just tried it on my S7 Edge (which drops every call) and could restore to factory settings (but didn't solve the issue).

Cst79 said:
The phone must be off for the Volume Up + Power + Home button combination to work. Keep those pressed for like 10 seconds, even after the phone powers on. I just tried it on my S7 Edge (which drops every call) and could restore to factory settings (but didn't solve the issue).
Click to expand...
Click to collapse
Thanks for your advices !
Unfortunately, even with this combination and a lot of patience I cannot manage to "bypass" this Bootloader error ...
I'm mad because it will take one month to get a new phone from my operator(just called them ...)
So maybe i'm going to try Odin ... but if I cannot put my phone into download mode, i'm f*ckued, right ?
Here's a photo of the error message :
https://drive.google.com/open?id=0B_3xOO1wyNGMVWl1RUFybTZoM3c

Mr_PoPoP said:
Thanks for your advices !
Unfortunately, even with this combination and a lot of patience I cannot manage to "bypass" this Bootloader error ...
I'm mad because it will take one month to get a new phone from my operator(just called them ...)
So maybe i'm going to try Odin ... but if I cannot put my phone into download mode, i'm f*ckued, right ?
Here's a photo of the error message :
https://drive.google.com/open?id=0B_3xOO1wyNGMVWl1RUFybTZoM3c
Click to expand...
Click to collapse
I'm stumped. I've never seen that before

From where did you order your phone?

thunderroid said:
From where did you order your phone?
Click to expand...
Click to collapse
A french mobile operator , Bouygues Telecom.

Can you do a factory reset from the Settings menu?

thunderroid said:
Can you do a factory reset from the Settings menu?
Click to expand...
Click to collapse
Nope, the phone doesn't boot anymore... it only displays the bootloader error message...
And no possibility to access reboot or recovery...
Maybe I can try to check with ADB, but my problem is that i would need to active USB debugging in settings ... but i can't do that

Return it. Nand flash died.
Sent from my iPad using Tapatalk

Yap, I think you have to return it.

hiepgia said:
Return it. Nand flash died.
Click to expand...
Click to collapse
Yep, I wanted to avoid it, but I don't see other reasonnable option. The phone didn't last more than 24h ... ok, it happens, I know ...
My previous (Still actual (sic)) Phone was a Note 3 and I installed so much roms, soft bricked the device so many times, but I could always restore it ... But not the S7 EDGE ... And I didn't spot any other user with same bootloader issue...
I've just sent back the phone for replacement, Thanks for all who replied to me in this thread
Oh and by the way : don't download 3DMark from play store , it will Hard brick your phone !!! (haha just kidding , i know it's not what caused my phone to die, I'm sure of it , however I won't try to install it anymore i think^^ )
Cheers XDA crew !!

Mine has done just the same. went to bed, woke up this morning and the same message as yourself.

Borgella said:
Mine has done just the same. went to bed, woke up this morning and the same message as yourself.
Click to expand...
Click to collapse
Sorry to hear that bro
Try things to troubleshoot if you wanna, but my advice : don't lose one day of trying to fix it, send it back directly to warranty...
I tried lot of things, key combination to reboot phone in recovery or download, I tried Kies, Odin, ADB....
I believe it's a real samsung bug that will happen to many people, So send it now before sammy is drowned under hard bricked S7 phones and start to have issues to provide replacement devices....

the S7 edge is getting a "urgent" update on approx 3mb..maybe this is a fix of some sort.

johanbiff said:
the S7 edge is getting a "urgent" update on approx 3mb..maybe this is a fix of some sort.
Click to expand...
Click to collapse
That is to correct the Screen Edge sensitivity

For anyone else who runs into this issue, I managed to fix my phone.
Holding the power and VOL down buttons for about 5-10 seconds will reboot the phone; if you hold home at the same time you can get into download mode (might take a couple tries).
From there, you can flash a new bootloader (BL option in odin) and then get back into recovery to do whatever you need to do.
Went from soft-brick to full restore in about ten minutes--not even a factory reset necessary.
Hope this helps!