Database Info

Transformer going insane

So, Recently a family member of mine told me something was wrong with their transformer. I take a look at it and it's not turning on so i assume it's not charged. I plug in the charger and it does not boot up. The transformer only goes to the eeepad screen with the asus logo and shuts off again. Basically it's in a bootloop but problem is, the tf101 is not rooted or tampered with and on stock fw (Tf101 is a b90 model) Anything i can do to fix??? Couldn't have been any sort of virus either as this transformer was only used for video streaming/ listening to music...
http://www.youtube.com/watch?v=DgCRfgGpwBw&feature=youtu.be

It might need to be reflashed. You could try using the wheelie tool, but the internal storage will be wiped. Sounds like a softbrick.
Sent from my Transformer TF101 using xda premium

I had exactly the same problem this week . . . this solved it:
http://forum.xda-developers.com/showthread.php?t=1620758

Reflash with NvFlash. Best idea as of now

Hey there,
I have nearly the same problem but my transformer just gets the first screen and then it tries to reboot.
I tried to reflash it with EasyFlasher but it didnt work. Is there a chance that your way will work?

If you can get ADB peri Might work, but just manually do it with NvFlash.

thanks, i'll try that when I hit back home in three days...
It is possible to get it in APX mode, so just put it on and flash?
Do you know why such a big problem occurs? It was on stock firmware and rooted for the last 5 months...

I'm starting to think my issue is related to condensation.
I started leaving the transformer in my bedroom, since my wife gave her tablet to her mother and is now using my transformer to read.
I was happy on HC, stock, non-rooted. My tablet was working with no issues for 3 months, give or take.
But then I started having random reboots and boot loops. Tried almost all roms for the transformer, same issue. Worked fine on the day I installed, got me bootloops the next day.
Today I thought about condensation after getting another round of boot loops and noticing my tablet screen with a bit of humidity. The temperature difference from my bedroom with A/C to my living room with no A/C can get to 15 or 20 celsius.
So I got the bootloop again today and instead of nvflashing the hell out of it as I have been doing, I put it in APX mode (since I have no recovery ATM, so I couldn't power it off) and leave it resting for 3 hours in room temperature. After that I rebooted it and it is now stable again. I will try to confirm those suspicious, but right now it sounds a lot like it for me. It never slept in the bedroom during the 3 months I was in HC.

theares2014 said:
thanks, i'll try that when I hit back home in three days...
It is possible to get it in APX mode, so just put it on and flash?
Do you know why such a big problem occurs? It was on stock firmware and rooted for the last 5 months...
Click to expand...
Click to collapse
I'm really not sure, but yes just download a stock nvflashable fw (xdafileserver.nl has some good ones) and put in nvflash mode and run reflash_sbkv#.bat (be sure to import wheelie into the stock fw folder and overwrite)
--
Regarding condensation, that's odd, but mabye. ..

Thanks, i'll try this when I am at home.

It is in APX mode but the computer doesnt recognise it... it says unknown device...
What shall i do?

That means the drivers are wrong/bad. Did you install any? You need the Universal Naked Drivers. (Search the tf themes and apps forum)

I installed the Asus PC Suite which means that drivers are inclueded, but I am going to search here if you say they are here.
Anyways, I can not find them there...

No, asus drivers is not what you need, you want the universal naked drivers: http://forum.xda-developers.com/showthread.php?t=1514942&highlight=universal+naked

well, that sounds quite nooby but how to install this drivers... i see several different files but absolutley no exe...
it is so embarrassing...

pnputil -a android_apxdriver.inf (or whatever the inf is called)
then plug in the tf

I opened it but nothing changes... the transformer in apx mode is still an unknown device

Have you tried 'update driver' in device manager, then point to the folder with the apx driver?

sure...

same problem with rebooting
I have exactly same problem...! My TF101 is B70 model and NVFlash not work with this model and higher... How I can fix it? is Megatron 1.1.6 installed on tablet and I have rom on sdcard, but reinstall rom not helped me, also wipe + reinsatll...
any ideas?
---------- Post added at 11:53 PM ---------- Previous post was at 11:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=1688012
this is helped me...!!!

[Q] Reboot to recovery broke device?

Hey everyone. I got my SL101 in the mail today and went straight to work rooting it. I got root access, flashed a non-CWM recovery, but I tried using Rom Manager to reboot to recovery. After granting SU permissions it turned off and.... stayed off.
Now it will not power on no matter what button combination I try. I've had it charging for 6 hours with the wall adapter (which does work as I've tested it with my phone, and it was charging before this mishap).
Should I just keep charging it or did my little "Reboot to recovery" adventure break my tablet? =\
Any help is greatly appreciated and I'll provide info upon request.

CQd44 said:
Hey everyone. I got my SL101 in the mail today and went straight to work rooting it. I got root access, flashed a non-CWM recovery, but I tried using Rom Manager to reboot to recovery. After granting SU permissions it turned off and.... stayed off.
Now it will not power on no matter what button combination I try. I've had it charging for 6 hours with the wall adapter (which does work as I've tested it with my phone, and it was charging before this mishap).
Should I just keep charging it or did my little "Reboot to recovery" adventure break my tablet? =\
Any help is greatly appreciated and I'll provide info upon request.
Click to expand...
Click to collapse
ROM Manager.... shouldn't be used for the Slider or Transformer. Ever.
Take a look at http://forum.xda-developers.com/showthread.php?p=26522267

Solar.Plexus said:
ROM Manager.... shouldn't be used for the Slider or Transformer. Ever.
Take a look at http://forum.xda-developers.com/showthread.php?p=26522267
Click to expand...
Click to collapse
I didn't think a simple "reboot" command would totally render my device useless.
Would a "reboot recovery" in terminal emulator have done the same to my tablet?
EDIT: I appreciate the response, but now do you have any idea how to fix my tablet? =\ This is a real bummer. I knew not to install CWM through the app at least.

CQd44 said:
I didn't think a simple "reboot" command would totally render my device useless.
Would a "reboot recovery" in terminal emulator have done the same to my tablet?
EDIT: I appreciate the response, but now do you have any idea how to fix my tablet? =\ This is a real bummer. I knew not to install CWM through the app at least.
Click to expand...
Click to collapse
I'm not sure. Have you checked out the PERI tool? It might be of help here for your soft brick.

Solar.Plexus said:
I'm not sure. Have you checked out the PERI tool? It might be of help here for your soft brick.
Click to expand...
Click to collapse
PERI tool doesn't detect my tablet being plugged in. Neither does... anything, really. ADB doesn't detect a device at all.

CQd44 said:
PERI tool doesn't detect my tablet being plugged in. Neither does... anything, really. ADB doesn't detect a device at all.
Click to expand...
Click to collapse
Running out of options here... Darn. Only other thing I can think is plug it into your PC then try to manually power on the tablet to see if the PC will recognize anything being turned on.

Solar.Plexus said:
Running out of options here... Darn. Only other thing I can think is plug it into your PC then try to manually power on the tablet to see if the PC will recognize anything being turned on.
Click to expand...
Click to collapse
Nada. Zip.
Too bad too. I normally don't have any trouble with ASUS products =\

I can't believe it won't even power on. You could probably send it in for hardware failure if that's the case though...

Well, ASUS gave me an RMA number so I'm sending it off today. I appreciate your efforts though!

Mine is doing the same thing. I rma-d it when it stopped booting too. They said they had to reload the BIOS. I got it back....it. boots but. Still no USB..I just bought another USB cable.waiting to get it. If it don't work, i all ready have another rma number.. ill wait to send it until I have my nexus4 so I don't go crazy from another 10 days without my tab....

Ah, sorry to hear about this guys. Hopefully everything gets worked out. It still puzzles me that the tablet's hardware failed.

[Q] BSOD, But I get lights when I plug it in

I just tried installing the Energy Rom from forum.xda-developers.com/showthread.php?t=2010108 and after I installed the Energy_JB_4.2.1_Partitions.zip file and rebooted I received the asus logo screen and then my tablet just went off. I tried rebooting into TWRP to continue installing the rom and just got a black screen. THAT'S ALL I GET NOW IS BSOD. I've tried holding down the the volume+power, just power, sticking a pin in the reset hole. NOTHING!!! However my light by the power button still lights up orange or green when charging.
IS THERE ANYWAY I CAN GET OUT OF THIS MESS??? I don't care if I have to wipe everything from the tablet. Just as long as I can get this thing to boot again in anyway would make me happy! :crying:

I would ask NRG as he was the one who created this zip. He will know more about it and its bugs/issues. Post in the energy thread if you haven't already.
Sent from my Nexus 7 using xda app-developers app

Take the back off, take the heatsink/metal plate off the device (WARNING THIS WILL VOID YOUR WARRANTY!!!!) Find the black cable with a white connector, disconnect it and connect it again.

CorkedA said:
Take the back off, take the heatsink/metal plate off the device (WARNING THIS WILL VOID YOUR WARRANTY!!!!) Find the black cable with a white connector, disconnect it and connect it again.
Click to expand...
Click to collapse
NOTHING!!!

When you have installed Energy, have you used offical 4.2.1 JB from Asus?

Hazard17 said:
When you have installed Energy, have you used offical 4.2.1 JB from Asus?
Click to expand...
Click to collapse
The more I think about it.... I think no. I was on Energy 12/22 which was 4.1.1 and then started the install of files. I installed the first one which was a 14MB partition file, it rebooted, I got the logo and then it shut off. The light still comes on though when I plug in the charger and changes from orange to green. But if I hold the power, power+volume, reset hole or anything else... Nothing happens.

Your tablet is unrecoverable bricked! You make misteak, because you should first install offical Asus JB 4.2.1 OTA via Fastboot.

Gogeta5026 said:
The more I think about it.... I think no. I was on Energy 12/22 which was 4.1.1 and then started the install of files. I installed the first one which was a 14MB partition file, it rebooted, I got the logo and then it shut off. The light still comes on though when I plug in the charger and changes from orange to green. But if I hold the power, power+volume, reset hole or anything else... Nothing happens.
Click to expand...
Click to collapse
Look at my signature and go to the link for getting into the bootloader menu. Don't worry with apx, just the info for the bootloader.
Good Luck!

tobdaryl said:
Look at my signature and go to the link for getting into the bootloader menu. Don't worry with apx, just the info for the bootloader.
Good Luck!
Click to expand...
Click to collapse
Thank you. I'll try it when I get home tonight from work!!!

Gogeta5026 said:
Thank you. I'll try it when I get home tonight from work!!!
Click to expand...
Click to collapse
Good Luck!

tobdaryl said:
Good Luck!
Click to expand...
Click to collapse
NO LUCK!!!

Not sure if this will help
If when you flashed this zip, and the 4.2.1 bootloader did manage to take I would try this.
Connect your device to your pc with the usb cable and power on like you would when normally trying to boot into bootloader (vol- & power)
Even though the screen is black if the bootloader did take then fastboot will be automatically running here.
Open command prompt (run as admin) and cd to your android-sdk\platform-tools folder and try command
Code:
fastboot devices
and see if you get a response.
If you do get a list with your s/n, then I would give my how-to a go & see if that works.

I'll try that tonight or tomorrow. I was going to try to find an identical one today at Best Buy and then return the screwed up one a few days later. But if I can save my original I'll just keep it and not go through all the hassle.
Sent from my LG-P930 using xda premium

[Q] My Tab 7 Plus is possibly hard bricked after JB ROM flash

I flashed the JB ROM on my Tab 7 Plus. After the "succeess" of the flashing as said by Odin v1.85, I tried to turn on the device, but it didn't. I tried to access download mode or recovery mode but it didn't work either. I tried to hold the volume down button and connect the cable to the tablet. That opened the download mode but the screen was "flashing". The rate at which the screen "flashes" keeps increasing until it becomes very fast and the device turns off. I tried to flash a ROM, but Unfortunately it turns off fast that there will be no time for the flashing process to continue.
Any idea what should I do?

what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....

Reply
chrisrotolo said:
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Click to expand...
Click to collapse
My Device is GT-P6200 and I got the GT-P6200 JB ROM for it.
______________
I left my device to charge all night. When I woke up I tried to see if the 'flashing' of the screen still occurs, but it didn't happen. I think I can flash a ROM now

I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?

yes, also a faulty or non-OEM cable would be the culprit.

SudoHalt said:
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
Click to expand...
Click to collapse
yess. flashing(blinking) screen is how download mode tells you that your battery is low. probably less than 10% since it even turned off by itself.

This Happend To me and I got it BACK
Hello... I totally understand your frustration... This exact same thing happened to me after my battery went dead just after I installed JB...
well here is the kick and it's kind of tricky...
If you want you can call me and I can tell you the instructions, it's complicated but if you follow the steps it will work...
I can also take the time to write it down, but i'm bad a typing.
let me know if you are interested...

Sorry for the late reply. It was fixed after less than a day from starting this thread.
Sent from my GT-I9001 using xda app-developers app

Constant rebooting

I have the cricket model. Sometime last night my phone started rebooting on every ROM and kernel. Nothing I do will get it to stop. It doesn't happen in TWRP and that's it. I thought maybe it was a battery issue as I haven't been able to fully charge it because of this issue but that's not helping either. I've been trying to use the upgrade tool but in this state the computer never even recognizes the phone and I can't even get that far, plus it reboots even when in download mode. I'm about to call cricket and see if they can just send me a new one since I've only had it a week but is there anything I can do? Does anyone have a boot IMG for complete stock 60450 ?!? EDIT: Got the tool to recognize phone and start process but what do ya know phone reboots even deep into download mode. It just always wants to restart to the system for some reason, except for when on twrp. UPDATE:EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.

it looks like motherboard is gone. I hope you can return it when you have custom rom installed.

DallasCZ said:
it looks like motherboard is gone. I hope you can return it when you have custom rom installed.
Click to expand...
Click to collapse
I've had the phone for one week lol. Motherboard is gone? Could something be messed up in build prop somewhere? I did try to use a DPI changer app on stock rom once or maybe xposed? I've done a lot of flashing since I got it trying to find the perfect setup. I just noticed that the USB cable it came with is crap so now that I'm using a different one I'm hoping that low discalobrated battery was the issue. Charging it up proper and gonna see what happens after. Also for some strange reason the Flyme OS ROM is the only one that doesent seem to want to restart as often. It still does but it lasts a lot longer before doing so , why idk lol.

turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk

DallasCZ said:
turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk
Click to expand...
Click to collapse
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.

carnivalrejectq said:
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.
Click to expand...
Click to collapse
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.

DallasCZ said:
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.
Click to expand...
Click to collapse
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.

carnivalrejectq said:
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.
Click to expand...
Click to collapse
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.

DallasCZ said:
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.
Click to expand...
Click to collapse
Well I first noticed my cable was funky when I loaded up Flyme it kept making an unplug sound and I thought it was just the ROM glitching out but I changed the cable and it stopped. About the tool......I have a Windows tablet that it's only USB connection is one of those mini USB to full adapters and it's a little loose. I have zero problems with it plugging my phone into it for file transfer or for adb, it's all fine there so idk why it would be causing an issue with the tool, last time I tried it k specifically made sure all connections were sturdy and didn't move the whole time and it still rebooted. I noticed somebody in one of the threads said his device did the same thing though and that's why he couldn't use the tool as well......nobody ever replied to him lol

Ahh I spoke to soon. Restored my stock, because that's what I prefer for even at OC it still doesent make the phone nearly as hot as CM ROMs and the restarts came right back even with a decent charged battery. I'm back on CM again though and its not happening. Doesent make much sense because before the restarts were happening across all ROMs. It can't be the kernel in my stock restore as I had used it a bunch of times before with no issues...... Though it is saved on my external SD..... But so is the cm build I'm using. Idk whats going on here. Just wanna return the phone to full stock and call it a day lol. Edit: spoke to soon again lol. There goes CM rebooting, although it took way longer than stock to do so.