[Q] Cannot make fastboot work - Transformer TF300T Q&A, Help & Troubleshooting

Hi all. I've run into a bit of a problem. I'll give you a bit of background first. My 300T is already unlocked. I had previously been running an early JB rom on ICS firmware. After some time away from my tab, I decided to get the JB firmware in place. I did and I'm currently on the stock rom. I went to get a custom recovery and then a rooted rom (KA01 most likely) back in place, and I'm realizing that no matter what I do, I cannot get fastboot to work. I've tried reinstalling drivers about 18 times and I've spent nearly 5 hours on the whole process. Nothing seems to work.I'm no stranger to this stuff, but I'm utterly stumped. ADB works fine, for what it's worth. I would greatly appreciate any help that the denizens of XDA can offer. What can I do?

Related

Well I did it. Phone is screwed. Sorry in advance. Can someone help?

I've searched the forums relentlessly with no luck. I rooted, installed some roms, tried to install Cyanogens latest rom, became stuck on the bootup screen for 30 minutes. Tried to wipe and reinstall and I get the same thing. Well now the boot screen comes up and the phone powers down automatically after about 5 seconds. I cant get to bootloader either. I'm worried it's really done now. Sorry in advance for being a dumb noob but if anyone could help i'd really appreciate it. Btw, I have a mytouch 3g.
Ok. I got to the bootloader and reinstalled the last working (hero) rom I had. It appears to be loading now. I still would like to change this rom as I really need bluetooth support but after that scare, I'm not sure what I did wrong. I was under the impression Cyanogen's ROMs were fairly simple to load. Sorry if this is not thread worthy but I've had this phone less than a week and if I brick it, my wife will kill me!

[Q] LG P500h with recovery issues...

Okay, so I read and read, searched and searched. So far I'm pretty stuck.
I did a ton of research before taking my LG P500h, and flashing the ROM because I wasn't a fan of the Froyo android setup. Did everything properly, ran an nandroid backup, everything that I was told to do.
Rooted using Gingerbreak APK, custom backup using Amon_RA custom recovery. All done using the latest USB drivers LG updated me with.
I am currently with Koodo Mobile here in Canada. Pretty much an offspring of Telus Mobile. Currently I am running Cyanogen Mod 7 the 6.5.7 beta build, and the phone is not bricked, or giving me any errors or hassle.
The problem is that I cannot use the 3G network or use the Koodo network. It only defaults to Telus towers. No android market showing up anywhere either. From what I've found on here, there doesn't seem to be a bugfix solution to this, and no settings I've been able to change on the phone has helped my situation. Maybe I missed something.
So, I decided to take it back to where I began, back to Froyo 2.2.1 . This is where it all went wrong. Tried going through the Nandroid backup and restoring that, I was given an " Error : run 'nandroid-mobile.sh restore' via adb! " . Okay, I'm not exactly a Java programmer so I'm a little intimidated. I do however have Android SDK going on my laptop.
Some more searching revealed the KDZ_FW_UPD.exe flashing method. I got the right KDZ file for my Koodo phone, V10V_00.kdz and began the process. Everything checks out, good to go, started update. Wait, phone not found? WTF! My laptop recognizes it, says my phone is connected and working. No problems here, just can't find it? UGH.
So, I need someone to either give me info on getting it to flash the kdz, or get Cyanogen Mod 7 working properly on my device.
Please help, I'll fully admit I'm a noob to this, and not an expert programmer either. But, I know computers and I fully understand what I have done so far to my phone. Just not enough to fix it.
Okay, I have gotten some things working on my phone. I think I am settling into Cyanogen Mod nicely. I missed the Google apps flash zip so I have my market and stuff. Its a shame the data does not work though. Oh well I will keep updating as it gets developed.
Sent from my LG-P500 using XDA App
GOT IT! finally...
Finally got my phone recovered to OEM specs. I had to restore my computer back to before I installed all my drivers and reinstalled all my USB drivers from there. Phone connected to USB properly, ran the KDZ updater, and it sucessfully installed the V10V kdz. All is well.
finally good luck.. enjoy androiding..
When you flashed the cyanogen mod rom what program did you use to flash the phone? And how did you make a rom backup? When you reflashed the stock rom did it still have all the original bloatware?
LG Optimus P500h TELUS became dead during Upgrading
Hi everybody!
I have LG Optimus P500h Telus. I purchased from Kijiji. I don't have any papers or documents for that so i cannot claim its warranty.
I was trying to upgrade its version during upgrading my device was stuck so I disconnected and plugged out its battery and inserted again. When i tried to turn it on. It never turned on again. It never ever appeared emergency mode again. I tried for several times by pushing home, power, and volume up and down buttons, and escape buttons. Now its just like dead. It never showed any sign of life. If anybody have any idea what happened with it and how I can recover or where I should take this one for repairs. I am in toronto, canada.
Your help and suggestions will be appreciated.
HELP!
http://forums.androidcentral.com/t-lg-phoenix-thrive/127858-jobans-kernel-2-08-overclock-cm7-2-3-7-etc-gyro-fixed-60.html
My problem starts from post #600
Please.

[Q] Would Samsung fix my bricked phone?

I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy
If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?
If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham
Yeah, you can still fix it. No need it to bring to samsung
Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!

[Q] Problems with ROM installation after 4.1.2 Newb help

Today, I checked for an OTA update in anticipation of the Premium Suite release with 4.2. Alas, Verizon was kind enough to give us a teaser. Frustrated, I took matters into my own hands and quickly rooted and unlocked my GS III with Odin carefully following the instructions and my device booted fine and all was well.
I explored my options of ROMs and chose Synergy as it had some very appealing options. I flashed it with CWM Touch recovery. It bootlooped, so I tried it again. It worked, but half of the features listed in the OP we're not on the phone. I had used the default installation of Synergy, so I went through it again doing a custom install. After a few tries it finally booted but still didn't have any advertised goodies. I played around with it anyway, and it was laggy and buggy, often rebooting.
After a few more variations of custom flashing the ROM, I resolved to restore my phone to a stable and working condition.
I expect that the issue is that I rooted and unlocked the 4.1.2, not from 4.1.1. But wouldn't that cause more serious issues? Or not work at all?
I haven't messed around with development since the Droid X and I wasn't an expert either. Any insight or direction would be awesome; I can still barely wait to get the multi-window feature!
Mark

[Q] need help please. can't grt phone to activare still

I got my one SV k2_cl from boost a little over a month ago and got the bootloader unlocked and rooted, working fine until one morning it wouldn'tmake calls or texts. I tried to factory reset and when I tried to boot got stuck at the HTC logo. Took me 2 weeks to get it to even flash a Rom on here that will somewhat work. I've got WiFi and partial 3g 4g connectivity but no voice at all. When I try to use the phones its activation tool-error, tried manually programming phone- nothing. I'm stumped. Can someone please help me out here. Don't want to have to buy another phone if I can help it. The only guess I've got at the moment is that if I could get a stock original rom to flash I'd be good to go probably and just hold out on doing anything else to it until after the kitkat ota is launched. The few stock roms I've tried either wouldn't download for some reason or just won't flash right. Thanks in advance for any help guys. I've always been more of a hardware geek more so than software but I can usually muddle through following guides of course.
I'm not much into boost, but did you try to flash the available RUU?
help...
As a matter of fact I have tried that and unfortunetly the installer locked up on a reboot of the phone because the phone wants to do the "Android is upgrading # of #" on every boot. That was why I was thinking since adb/fastboot and the HTC One Toolkit all sorta work that if I could get ahold of a working stock rom to flash on there and I have a stock CWM backup still on my laptop from when I first got the phone rooted and everything working. But of course thanks for the tip anyway. I wish that would work. It seems to be the easiest way to install back to stock.

Categories

Resources