Database Users

Firmware Upgrade Gone Wrong

Hey,
I tried to upgrade my xda's firmware earlier but something went badly wrong. It got stuck on the "Upgrading. This will take approximately 5 minutes" screen, on 0%. I tried doing the upgrade again, but now my computer can't establish a connection with the device, via USB I might add.
If I hold down the power button whilst I push the reset button, it takes me to the colourful, yet useless, "Wallaby Bootloader" screen.
Is it possible for me to recover my xda? If so how?
Any help would be much appreciated!
Thanks,
Andy.

^ Bump (original post was 4 years ago!).
I just found the xda in a drawer and decided to try and revive it. I plugged it in, ActiveSync tries to connect, the phone makes a chiming noise, but it can't actually establish a connection (since the firmware is toasted), therefore the Programme A ROM utility won't work.
Is there any way I can recover this device without needing a special serial cable? Would it be possible to boot from an SD card, even without a functioning firmware? Is there anything else I could try?

Quick update: I picked up an SD card this morning and booted from that, managed to reflash the ROM courtesy of the Rom Kitchen.
Only bad thing.. I snapped off the plastic cover from the SIM card slot, which unbeknown to me holds down a pin that controls the device's power - so I now need to tape it down.. honestly if it's not one thing it's another!

plaggypig: (if you ever read this) just wanted you to know I found the 4 year bump hilarious. I'm glad you salvaged your machine, sad about the cover with hidden switch! I always lusted after an xda but couldn't afford it back then. Am now the proud owner of a Topaz (TD2).

My odin issues finally solved!!!!!!

I found this idea when trying to install heimdall in ubuntu - where nothing worked there either. Someone had one of the usual issues (can't connect to the computer) but then he cleaned the connection! I personally was trying all day on 4 machines and trouble shooting in between before I found this. It just all clicked - like the fact that at the beginning I could see it on the computer, now it sometime recognized as a unknown item but not always etc.
So if you found this you've like found all the usual stuff already: install/reinstall kies or the drivers, try different USB ports etc.
Well add to the list: clean the usb port on the phone with alcohol and the cable and the computer too. I did that and bang, like 8 proper drivers installed!!! probable because I had installed and reinstalled so many many many times. this was literally days of my life and hours of my sleep (including now to share but XDA is worth it).
Now the fellow in question apparently would use it as a boombox in the bathroom while having a shower (not sure how that worked) but in my case it was only 3 months old and never really wet or abused. But it still worked awesome!!!!
I can't believe I can use Odin finally! Good thing too because I have an i9000m with the dreaded SD card of death (which just came back from its 1st repair - hence the need to root it which with 2.2 is much more painful than 2.1 was.
Please thank me if it helped!
Oh and one other note. It would not just see in when going straight from cleaning to download mode. I had to do it regularly with the power on first and then I pulled the battery and went into download mode.
ahhhh I can finally get some bleeding work done - except for looking at custom roms now....
Oh - and I guess I should have backed up the existing firmware but I'll try and get that from someone...

[BRICKED] I have two gt-i9000m's,only one bricked

I have two Galaxy S gt-i9000m both with Bell and I live in Newfoundland which is the 850mhz radio as well.
One phone became bricked few months ago when I started getting random reboots I changed rom, it converted fs from rfs to ext4 and recovery gave some screens to go through but at this time I was only new, I messed up and my internal sd started causing issues. It was when gingerbread first arrived
I used odin to flash a number of firmwares, but now I feel I was not doing odin correctly, regarding bootloader and partitioning, anyway what ended up making the actual "BRICK" was when I flashed a vibrant rom and rebooted, now its a perm black screen.
If I have a fully charged battery and leave in, it dies overnight, If i plug usb in, the motherboard heats up very noticably, but no sound, no connection through device manage, nothing at all, no matter what tricks or buttons I try.
So not I have another identical phone that works perfectly. I have been researching if there was a way using my good phone to flash a chip, or solder something together could I fix it but I could not find any relevant info.
So I am left with the jtag/riffbox.
Can someone do this service for me, I dont want to actually buy one just to use it once, or can someone help me fix my bricked galaxy s, I will pay you for info that helps as well as put videos up, etc.
Please I have been last 4 months trying when I have free time, someone that knows how to help me, please do!!!
Thanks,
Dave Husk
709.764.7890
**EDIT**
I would love to work with someone, I attached pictures of my phone's internal parts including chip shots, and i also took a picture of my sim card writer, which is a serial to usb device and I'm sure somehow I can solder together to make a device to help unbrick our SGS's, I am even willing to send free of charge to the next person in need, and pay for shipping to continue the good will as every bricked SGS owner deserves HELP!
**EDIT 2**
I also already have a Download mode jig, the 301k resistor here as well

Does the download jig do anything?
If not your into specialized territory with the jtag stuff. I would add to an existing thread on that and hope someone is still watching it.
G
There are jtag shops in TO that can do it (on xda somewhere) and you could likely ship it to them and get the service.

Totally Borked TF101

I think I have totally borked my ASUS TF101..
I get nothing on the screen and the only sign of life it shows is that it goes into APX mode..
I have tried to follow many different guides for recovery......
http://forum.xda-developers.com/showthread.php?t=1688012
..... but they all pretty much end with this:
http://sjfm.us/temp/tf101c.jpg
It just sits there like that. I left it for almost 10 hours... No change.
This is a really awesome tablet and I want to exhaust all possibilities before giving up..
Anyone have another procedure I can try???
Thanx
Michale

I'm assuming your unit is a b60 or greater since you're running wheelie? I'm bricked too but I have a b30 and Nvflash has always been confusing to me.

To be honest, I am not sure what TF101 I have.. I don't get ANYTHING on the display and the only sign of life is when I have it hooked to my PC via USB and can go into APX mode...
This is the label on my TF101:
http://sjfm.us/temp/tf101a.jpg
Here's a more detailed analysis of my issue..
http://www.transformerforums.com/forum/asus-transformer-help/25346-tf101-dead-doornail.html
Since the last post on that thread, I have tried the PERI package and the package here:
http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.24
It still freezes at 100% right after the bootloader load...
http://sjfm.us/temp/tf101e.jpg
I am pretty much at the point to where I either have a bad USB cable (waiting for a new one) or my TF101 is completely borked..

I have a friend here in Spain, in the same situation.
no way to restart pressing power button , the tablet seems to be always in apx.
I tried all possible methods, rootkit, easyflasher, reflash with wheelie.
and always the same result, stuck on the same spot as you.
I've run out of ideas already, and just hope that someone who has solved something like this , give us a hand.

partio said:
I have a friend here in Spain, in the same situation.
no way to restart pressing power button , the tablet seems to be always in apx.
I tried all possible methods, rootkit, easyflasher, reflash with wheelie.
and always the same result, stuck on the same spot as you.
I've run out of ideas already, and just hope that someone who has solved something like this , give us a hand.
Click to expand...
Click to collapse
That's interesting that you have the exact same problem.. Hopefully there is someone out there who also had, but fixed it. I PMed with a guy and he said to keep trying NVflash (wheelies) and see if it will "POP".. I did that for several hours with no luck..
I'll follow up on this when my new cable gets here. Frankly, I don't hold out much hope that it's going to fix things, but there is always that possibility.
If not, I'll just keep searching around for a TF101 that has a busted screen..

on the screen of my friend's tablet, when the process starts it appears:
Entering NvFlash recovery mode / Nv3p Server
Chip uid: 037c710942ffc217
check out : http://youtu.be/bwW0RiL35_o

partio said:
on the screen of my friend's tablet, when the process starts it appears:
Entering NvFlash recovery mode / Nv3p Server
Chip uid: 037c710942ffc217
check out : http://youtu.be/bwW0RiL35_o
Click to expand...
Click to collapse
Well, that's very interesting.. Mine did the same thing, except I didn't see any text on the TF101..
When I get home, I'll check it more closely..
Thanx

Well, apparently I have a bad LCD in addition to a borked unit.. I don't see ANY text on my screen, but the output from NVFlash is identical...
This just keeps getting better and better.. :crying:

I couldn't really find the serial number in your picture, IIRC it's just a sticker with a bunch of numbers and letters on it. Mine peeled off a while ago so I have nothing to compare it to :-/ It should start with a B
Sadly, the only way to make sure that the tablet is truly off is to rip the thing open and disconnect the battery (which is connected by an 8-pin connector). You need a T-5 torx screwdriver to take out the two screws around the charging port so you can pop the bezel off and a small Phillips screwdriver to remove the screws that hold down the screen/rear cover. I had to do this with mine because the only two things that I could get to were APX mode and the stock recovery, but my cable seemed to crap out the moment I needed it even though it had worked a few minutes earlier!

brando56894 said:
I couldn't really find the serial number in your picture, IIRC it's just a sticker with a bunch of numbers and letters on it. Mine peeled off a while ago so I have nothing to compare it to :-/ It should start with a B
Sadly, the only way to make sure that the tablet is truly off is to rip the thing open and disconnect the battery (which is connected by an 8-pin connector). You need a T-5 torx screwdriver to take out the two screws around the charging port so you can pop the bezel off and a small Phillips screwdriver to remove the screws that hold down the screen/rear cover. I had to do this with mine because the only two things that I could get to were APX mode and the stock recovery, but my cable seemed to crap out the moment I needed it even though it had worked a few minutes earlier!
Click to expand...
Click to collapse
Havn't tried it myself but there is this tool (http://forum.xda-developers.com/showthread.php?t=1290503) to check the SBK version

JoinTheRealms said:
Havn't tried it myself but there is this tool (http://forum.xda-developers.com/showthread.php?t=1290503) to check the SBK version
Click to expand...
Click to collapse
Thanx JTR.. I'll check that...
On another note, I got a new USB cable in. This one actually does worse than the first one. With the new USB cable, I can't even get the TF101 into APX mode..
Something else I noticed that may or may not be related...
When I have either cable plugged in, it seems to take over my USB ports. If I plug in a Thumb Drive while the TF101 cable is plugged in, the computer will not see the ThumbDrive..
Does that indicate that BOTH cables are bad???

Your TF may be done for :-/
Sent from my Transformer TF101 using Tapatalk 2

i am currently having the exact same issue as you do...can only go into apx mode and nothing ever shows up on the screen. Mine all started from trying to install an OTA firmware from asus...i feel like im about ready to give up

Same problem here.
In fact my tablet work very well but the display died. It works with an hdmi cable though.
In didn't try this but maybe it could fix some thing for you:
http://www.youtube.com/watch?v=yRLcxI2JddQ
I really am disgusted, my display dies two weeks after warranty without more obvious reasons than randomness.
If a lot of people have their display broken (and only the display, with hdmi working) I think we should think complaining to asus... It's not acceptable for this kind of devices.

have you tried flashing RougeXM recovery 1st? Then flash the asus recovery fw from easyflasher in apx mode.
Make sure its in /AsusUpdate dir. You won't see anything on the screen in apx.
I thought I killed mine but EF saved it. Was stuck hanging just like yours is doing so i reflashed & it worked.
Good luck,
Sent from my Transformer TF101 using xda app-developers app

N910F - strange issues with charging

Hello everybody,
- On monday i ran into a strange problem with my N910F. At first it was just not charging whatsoever.
- after the phone ran out of power, i attempted to charge it which gave me a brick with a black screen, vibrating short every two seconds
- Fine by me i thought, went and got a replacement battery (after checking simple stuff like the physical state of the battery (normal) and killing the batterystats (which i heard both yay and nay about so i decided to give it a try).
- Replacement battery charged overnight on the USB Port of my computer (2.0, for the completionists) went smooth (didn't turn it on, just had this bubble animation of charging).
- Turned it on this morning (booting apparently took 3% off my battery) and all well so far.
- finally in my chair at work i plugged it into my power cable (genuine Samsung FastCharging adapter that came with the phone itself) and nothing happened
- tried another adapter (some cheapo 1A adapter) which started charging around 10secs after connecting but decided to stop charging after a couple of minutes
- some shaking and gentle knocking brought back the charging symbol for some seconds, seemed like some loose contact or a broken cable so i felt fancy and plugged the very same cable (the one originally shipped with the phone) to my laptop. started charging instantly and no shaking or knocking stopped this (so no loose contact or broken cable at all)
This is the story until now, put together as complete and organized as possible. For now i'm stuck to charge my phone on the laptop or computer which seems to work. In this progress above i tested around 7 chargers, 3 laptops, 2 computers, 10 cables and 3 screens with both batteries, although the workaround i have now is only tested with the genuine cable as i was just done with testing for the night.
Now for my questions (apart from a touch with the magical fix-everything tool):
- What i see as possible causes based on my very shallow knowledge are either the microUSB port on the phone or the power distribution unit. Anyone has an idea what to check?
- As i have no idea how deep the OS goes, could it be a software issue by any chance?
Even though the device is only ~9 months old, I don't like the idea of going through Samsung for this one as i tripped KNOX already.
Hope there's still hope for me
Cheers,
Fachtal

sooooooo, does nobody have an idea lying around somewhere?

Fachtal said:
Hello everybody,
- On monday i ran into a strange problem with my N910F. At first it was just not charging whatsoever.
- after the phone ran out of power, i attempted to charge it which gave me a brick with a black screen, vibrating short every two seconds
- Fine by me i thought, went and got a replacement battery (after checking simple stuff like the physical state of the battery (normal) and killing the batterystats (which i heard both yay and nay about so i decided to give it a try).
- Replacement battery charged overnight on the USB Port of my computer (2.0, for the completionists) went smooth (didn't turn it on, just had this bubble animation of charging).
- Turned it on this morning (booting apparently took 3% off my battery) and all well so far.
- finally in my chair at work i plugged it into my power cable (genuine Samsung FastCharging adapter that came with the phone itself) and nothing happened
- tried another adapter (some cheapo 1A adapter) which started charging around 10secs after connecting but decided to stop charging after a couple of minutes
- some shaking and gentle knocking brought back the charging symbol for some seconds, seemed like some loose contact or a broken cable so i felt fancy and plugged the very same cable (the one originally shipped with the phone) to my laptop. started charging instantly and no shaking or knocking stopped this (so no loose contact or broken cable at all)
This is the story until now, put together as complete and organized as possible. For now i'm stuck to charge my phone on the laptop or computer which seems to work. In this progress above i tested around 7 chargers, 3 laptops, 2 computers, 10 cables and 3 screens with both batteries, although the workaround i have now is only tested with the genuine cable as i was just done with testing for the night.
Now for my questions (apart from a touch with the magical fix-everything tool):
- What i see as possible causes based on my very shallow knowledge are either the microUSB port on the phone or the power distribution unit. Anyone has an idea what to check?
- As i have no idea how deep the OS goes, could it be a software issue by any chance?
Even though the device is only ~9 months old, I don't like the idea of going through Samsung for this one as i tripped KNOX already.
Hope there's still hope for me
Cheers,
Fachtal
Click to expand...
Click to collapse
You seemed to have tried using the cheap charger which allowed you to charge after shaking it a bit, have you tried purchasing a new genuine charger?
Sent from my trltexx using XDA Premium 4 mobile app

Tripping Knox does not necessarily mean that you've lost warranty.

Battlehero said:
You seemed to have tried using the cheap charger which allowed you to charge after shaking it a bit, have you tried purchasing a new genuine charger?
Sent from my trltexx using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried around 7 adapters (from cheap ones to genuine galaxy S3, Note2, and Note4), around 10 different cables (again, from cheap ones to genuine samsung cables), 3 Laptops (again with all cables), 2 computers (all cables) abd one of those mobile charging battery things.
The only thing that works is either the genuine cable on my computer or the same cables on my screen at work.
@geevh that's news to me. As far as i heard is tripping know equal to losing warranty.

Fachtal said:
I tried around 7 adapters (from cheap ones to genuine galaxy S3, Note2, and Note4), around 10 different cables (again, from cheap ones to genuine samsung cables), 3 Laptops (again with all cables), 2 computers (all cables) abd one of those mobile charging battery things.
The only thing that works is either the genuine cable on my computer or the same cables on my screen at work.
@geevh that's news to me. As far as i heard is tripping know equal to losing warranty.
Click to expand...
Click to collapse
Have you tried to flash stock firmware, in case it's the kernel?
KNOX warranty shouldn't void your warrant in the EU as I have gotten two knox tripped devices repaired from Samsung before.
Sent from my SM-N910F using XDA Premium 4 mobile app

Battlehero said:
Have you tried to flash stock firmware, in case it's the kernel?
KNOX warranty shouldn't void your warrant in the EU as I have gotten two knox tripped devices repaired from Samsung before.
Sent from my SM-N910F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flashed the official ROM using Odin. Had some problems getting the phone connected while in DL mode (didn't work at all while in normal android mode).
This seemed to be a dirty flash (already was on stock Rom, just put CWM on, rooted the phone and replaced the kernel to have SELinux permissive for Viper4Droid) as it didn't go through the setup process and was like before.
Anyway, charging still doesn't work. Is there anything else I can test? I'm nearly at the point where I migrate back to my old SGS3 and have the N910F sent to the carrier (well, in the end it will go to Samsung) to get it fixed.
Thanks about the whole Knox false knowledge.
Cheers, Fachtal

Fachtal said:
I just flashed the official ROM using Odin. Had some problems getting the phone connected while in DL mode (didn't work at all while in normal android mode).
This seemed to be a dirty flash (already was on stock Rom, just put CWM on, rooted the phone and replaced the kernel to have SELinux permissive for Viper4Droid) as it didn't go through the setup process and was like before.
Anyway, charging still doesn't work. Is there anything else I can test? I'm nearly at the point where I migrate back to my old SGS3 and have the N910F sent to the carrier (well, in the end it will go to Samsung) to get it fixed.
Thanks about the whole Knox false knowledge.
Cheers, Fachtal
Click to expand...
Click to collapse
I would just give the device in for repairs but make sure to flash a full stock rom and factory reset before giving the phone, since you have already tried everything else.
Good luck

Battlehero said:
I would just give the device in for repairs but make sure to flash a full stock rom and factory reset before giving the phone, since you have already tried everything else.
Good luck
Click to expand...
Click to collapse
Well, flashing stock ROM seems to be slightly less relaxing than I thought. It feels like I have to connect the phone to the pc, put it on the table in a very specific position/way and then hope that it doesn't disconnect halfway through flashing...
This has become quite an adventure so far and I hope I'll get this done so i can get rid of this very expensive paperweight
Thanks for all the help so far, I guess I'll add the explanation from my carrier/Samsung as soon as I (hopefully) get my device back.
Fachtal

PMIC or Charging IC is probably broken on the mainboard, i hear more N4's have this problem.
Best is to send it for warranty or let the components be replaced by a "good" repair shop.
Most service centers don't check knox status so i would go for that, if all fails take it for repairs if the costs are not too high.

Hi guys, back for a rather unexpected "solution"
When i finally freed up some time to actually get to the carrier shop to get my phone fixed, I was in for a rather embarrasing experience.
The lady in the shop pulled a charging cable and an adapter out of a box, plugged my phone in and it suddenly charged as if nothing ever happened. Now, some time later, it still works perfectly fine, as if there never were problems...
I have absolutely no idea on what happened. Before going to the shop i obviously flashed the stock rom yet again (with the usual wipe user data/cache/dalvik procedure).
Now, on what i had when the problems started: stock BOC5 ROM, touch CWM, rooted and with a custom kernel for SEAndroid permissive (emotion something i believe the kernel was called). Now during my rather extensive troubleshooting I actually flashed the stock ROM at least once and the issue persisted, which is why i just stood there, staring on my charging phone, my jaw somewhere on its way to the ground, unable to form any proper words :silly:
So basically, does someone have a possible explanation to clear this up? If not, I'll consider this thread solved i guess^^
In the meantime, I downgraded to Stock 4.4.4 with CWM, root and xposed (which i really missed on Lolli) and I'd say I'm happy with this :victory:
Fachtal

Fachtal said:
Hi guys, back for a rather unexpected "solution"
When i finally freed up some time to actually get to the carrier shop to get my phone fixed, I was in for a rather embarrasing experience.
The lady in the shop pulled a charging cable and an adapter out of a box, plugged my phone in and it suddenly charged as if nothing ever happened. Now, some time later, it still works perfectly fine, as if there never were problems...
I have absolutely no idea on what happened. Before going to the shop i obviously flashed the stock rom yet again (with the usual wipe user data/cache/dalvik procedure).
Now, on what i had when the problems started: stock BOC5 ROM, touch CWM, rooted and with a custom kernel for SEAndroid permissive (emotion something i believe the kernel was called). Now during my rather extensive troubleshooting I actually flashed the stock ROM at least once and the issue persisted, which is why i just stood there, staring on my charging phone, my jaw somewhere on its way to the ground, unable to form any proper words :silly:
So basically, does someone have a possible explanation to clear this up? If not, I'll consider this thread solved i guess^^
In the meantime, I downgraded to Stock 4.4.4 with CWM, root and xposed (which i really missed on Lolli) and I'd say I'm happy with this :victory:
Fachtal
Click to expand...
Click to collapse
It's sound strange but a couple of years ago i read somewhere,forgotten where and about the specific device. The thing was that phone wasn't charging eather ,and now it comes.....the solution was turnig around the charger in te power socket.

ludoke said:
It's sound strange but a couple of years ago i read somewhere,forgotten where and about the specific device. The thing was that phone wasn't charging eather ,and now it comes.....the solution was turnig around the charger in te power socket.
Click to expand...
Click to collapse
this indeed sounds strange. And honestly, i didn't pay attention on the orientation of the power adapter (although my stock samsung one is always in the same orientation because the cable goes out on the side (which means it worked in the same direction as it didn't before).
The only even remotely considerable approach would be that the custom kernel along with this synapse app somehow screwed with the power intake and i forgot to wipe everything when i first flashed stock over it, meaning that synapse still had its fingers in the system screwing around with that.
But then again, as I seem to be the only one with this problem and this custom kernel had more than just a few users I don't think this is the way it went (I don't even use an unusual collection of root Apps which could cause some sort of malfunctioning combination of effects).
I had a few evenings just thinking about this and draw some simple mindmaps/schematics to make some sort of a sense...