Database Info

[Q] HELP CWM recovery problem, infuse wont boot

Hi, i just bought a samsung infuse and i was looking for an ICS rom and i found the cm9 unofficial http://forum.xda-developers.com/showthread.php?t=1601844 this one
and i flashed like the thread says and everything went good, ics started like a charm but then i turned off my phone to get into the recovery but i found out to be in a huge problem
My phone wont boot, it goes directly to the recovery (cwm 5.5.0.4) and it looks like a broken screen (sort of, rainbows) its usable but it wont boot, i even tried to reflash it
Would somebody help please?

riikiiee said:
Hi, i just bought a samsung infuse and i was looking for an ICS rom and i found the cm9 unofficial http://forum.xda-developers.com/showthread.php?t=1601844 this one and i flashed like the thread says and everything went good, ics started like a charm but then i turned off my phone to get into the recovery but i found out to be in a huge problem My phone wont boot, it goes directly to the recovery (cwm 5.5.0.4) and it looks like a broken screen (sort of, rainbows) its usable but it wont boot, i even tried to reflash it Would somebody help please?
Click to expand...
Click to collapse
Well I guess you didn't read all the way til post 3 of the thread where you pulled the CM9 unofficial ROM...BTW your probable gonna get flamed since you also didn't make a run thru the the Q&A...since this has been address, well I ran out of fingers and toes to count how many times...but
Go back the op [Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G... go down to post 3, and do a little reading, maybe you should of did some more homework before jumping in, but hey good on you for just jumping and not looking where you might land...
If you require more reading (i suggest) see my links below...ok,
Good luck

yes i know i will get flamed, and i did read the 3rd post about the bootloaders
but i just wanted to know if there is another way to do it, and since English is not my native language, i don't understand everything very well, but thanks

riikiiee said:
yes i know i will get flamed, and i did read the 3rd post about the bootloaders but i just wanted to know if there is another way to do it, and since English is not my native language, i don't understand everything very well, but thanks
Click to expand...
Click to collapse
Ok understood, just relax and re read it again, and go thru the Q and A seciton.
What part are you having trouble understanding...?
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
What I suggest is start over:
Use the one click back to stock and then use the one click to install CWM...which is what you need to get CM9 ics ok,
so first one click back using qkster method:
http://forum.xda-developers.com/showthread.php?t=1524081
1. Put your phone into Download Mode.
2. If you have not used Heimdall, you will need to set up the driver for device recognition.
3. Once your device is connected, the DEVICE STATUS should show: CONNECTED. The long FLASH bar will also turn on for flashing.
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
5. Once it has completed, your phone will reboot. You will hopefully see the ATT logo and reboot into STOCK UCLB3.
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked. This is more likely if you never had proper Gingerbread bootloaders on your phone, if you are coming from FROYO or if you never had Odin a Gingerbread leak to get your bootloaders.
Then use one click from same op, qkster method:
http://forum.xda-developers.com/showthread.php?t=1524081
post 2... After you have flashed the UCLB3, some of you may want to have Red ClockWorkMod (CWM) recovery to flash another ROM.
Put your phone back into DOWNLOAD mode after your phone has booted up.
Then reinstall the cm9 zip, once you reach this stage, you will have to flash it twice..ok this file...

Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.

timmetal6669 said:
Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.
Click to expand...
Click to collapse
Yes and No...
It is a step up for the infuse, well it will be...
The problem is people are not doing their homework, and have never flashed a ROM, much less know what the letter ICS or CM9 even are, and yes it has brought some challenges but for those of us that have installed and ran it on this phone and other phones, I don't mind assisting others, but they have to do the reading and homework for them self's...
Yes you have your opinion and I don't disagree or agree, but I do hope the ROM with be brought up fully functionally, and it will with the Developer we have working it and others who are "testing" it, the ones who are familiar with...

Alright thanks mate, right now im installing the driver for heimdall, I already read everything you said and the links you shared
Thanks again, you just saved another noob

When your up and running for good, let us know, and don't forget to thank the Dev that provided you with the tools you needed...not me...just pointed you there...

Yes I will

timmetal6669 said:
Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.
Click to expand...
Click to collapse
No one who actually FOLLOWED THE INSTRUCTIONS has had an issue.
I challenge you to find ONE person who has bricked an Infuse with CM9. The only time in the CM9 flashing process one might brick is when flashing the bootloaders to get rid of rainbows - and I have PLENTY of warning that flashing bootloaders is a dangerous and risky process.
Similarly, no one has bricked an I9100 flashing CM9 either, unless the recovery they were flashing away FROM was defective (such as the initial I777 UCLD3 recovery repacks) - but that same defective recovery caused hardbricks for people flashing even rooted stock with no CM9 involvement.
Task650 was right when he replied to you in the I777 thread - he contributed more to XDA when he took a dump this morning then when you spread your bull****.

Thank You "E"....well put...:thumbup: :thumbup:
I hate it when jokers like that guy pipes in, when trying to help others...the op admits to not to be good at his English...

hey, i downloaded everything that i needed
and even a little bit more
but i haven't been able to start OneClick
put my phone into download mode, install drivers for heimdall
I tried with heimdall frontend in the flash tab, just like the tutorial
add every partition, and then when i click Flash
this is what it says
"Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12"
any idea?

ok I am not trying to insult you just wanna ask a few question ok,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You sure your in Download mode...does it look like this your phone?
I go into download mode like this: I take out my battery, plug in the cable while holding both volume buttons i pop my battery in...bamm download mode...
you will see the pic above....
But once it does go into dl mode carefully place the phone down with still connected to the cable then...
if so then you click the one click to open it and you see the word "connects"..in green, click the button below it flash...
and then it should run thru you will see the blue line go across your phone will lots of remarks running thru on the screen in the one click window....ok

dont worry, but yes i know how to put it into download mode
but the thing is that i downloaded oneclick but i cant run it

riikiiee said:
dont worry, but yes i know how to put it into download mode but the thing is that i downloaded oneclick but i cant run it
Click to expand...
Click to collapse
1) ok, have you tried different usb port and or cable...
2)re-download the one click file again...here is a link
http://db.tt/Y2XEPwGv
3) And this the link to give you CWM, you run this after you have install above and you will have to put into download mode for this....and you will hear the lady voice talking that means it is installing cwm...ok but first do the above
http://db.tt/WEJyXywV

riikiiee.....status check my friend...

elostish venus.
Hey BigJoe
the problem was my computer, i used other one I have here, and now Im good and running GB I really appreciate your time and your help.
From now and on I will read everything I have to read
And thanks again mate, you really helped

riikiiee said:
Hey BigJoe
the problem was my computer, i used other one I have here, and now Im good and running GB I really appreciate your time and your help. From now and on I will read everything I have to read
And thanks again mate, you really helped
Click to expand...
Click to collapse
No problem....glad you found out what the real problem was...
Any time ...:thumbup:

goritat the
Yeah, now back to ICS again
the right way now

[Q] A question about my brick

I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.

jeremiah.wells said:
I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.
Click to expand...
Click to collapse
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.

MartyHulskemper said:
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.
Click to expand...
Click to collapse
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.

Can you get into recovery at all when you hold vol down and power? I had the same problem with my infinity when the .18 update came out, i had a freeze and a crash during normal use while the update was either downloading or changing something and when it restarted I couldnt do anything but go into APX. I never unlocked it (mainly because the asus tool wouldnt work) but I had to RMA to get it fixed. If you can at least get to the recovery menu you can try reinstalling the stock rom from an mSD. Otherwise you may have to do the same as me and RMA and hope that they dont tell you tough luck since its unlocked As far as I know the only way to recover the tablet when APX is your only option is with NVFlash, which I never installed because .30 was on my infinity when i bought it.

jeremiah.wells said:
I couldn't get either recovery to boot and so I attempted a data wipe
Click to expand...
Click to collapse
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).

_that said:
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).
Click to expand...
Click to collapse
Yes, with only APX available but no NvFlash backup, there's very little to no light at the end of the tunnel. I also wondered why the reports of RMA'd users mention a motherboard change, but I do remember something about unit-specific code being backed up with NvFlash. Although I'd think it strange, it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
@OP: with no fastboot available, you will not be able to follow either Scott's guide or reflash a recovery. I sincerely feel for you, especially since it was enthusiasm that got you into trouble. I know the resultant feeling, and I hate it, for it quells said enthusiasm in the future and make you overly cautious. I wish you a speedy and effective RMA!

jeremiah.wells said:
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.
Click to expand...
Click to collapse
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.

I feel for you too as this happened to me even without any type of modifications to my recovery or bootloader! As far as RMA and the motherboard change I am not sure whether they recovered my device without an actual change. When i got it back from RMA it was on the same firmware as before (not the most recent at the time) as well as retaining the same SN on my device. Since I got it back though I am unable to use the unlocker tool. I get that network error and a refusal from the asus unlock server that lots of people were having issues with a while back. I am in touch with Asus service now, but asus service is usually a long arduous process! I hope that they dont charge you for the replacement, but seeing as you unlocked its very possible if you have any sort of insurance from your credit card that may be a better route by trying to replace it as a lost or broken unit. My RMA was free (except shipping) but again, no unlock!
best of luck.

MartyHulskemper said:
it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
Click to expand...
Click to collapse
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.

_that said:
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.
Click to expand...
Click to collapse
In cases like this, I always hope you get a motivated technician that actually hunts down your serial from that database and helps you out. Guess I'm a bit naive in that regard.
Yeah, those 16 bytes keeping the door shut are a major bummer, as is the fact that NvFlash was not pre-installed anyway...

okantomi said:
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.
Click to expand...
Click to collapse
To answer your curiosity, NO... I did not install or use Rom Manager in any way to get to this state.

Got a question. Mine is rooted but locked, i attempted to install TWRP before unlocking. I can still boot it up but i cant get into recovery. Can i unlock it without a working recovery and just reinstall TWRP? what are my options? Any help would be great.
edit: nevermind, i think i found the answer...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

[Q] Stuck @ Boot Screen

Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!

xxboarderxx said:
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
Click to expand...
Click to collapse
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.

OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.

I think you could mean a kind of recovery loop: There is a file called "command" on the cache partition which causes the recovery image to boot. But if the recovery is broken then it will not empty cache. The recovery will boot but does not update screen (showing just boot splash). On the next time it will boot again ...
Please be just carefully: "wipe data" in the fastboot menu will create the "command" file.

ScottBroker said:
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
Click to expand...
Click to collapse
Sorry...if I could have made this attempt last week, I may have been able to help you then. :sly:
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

opethfan89 said:
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
Click to expand...
Click to collapse
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

xxboarderxx said:
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.

I was smiling as I read the first post, but this is going to come in real handy if I nuke my bootloader. Thanks. I wish I had gotten to this first, heh, I could have told you don't flash a Jellybean ROM over an ICS bootloader, it won't boot.
Good information to have though. Thank you!

opethfan89 said:
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
Click to expand...
Click to collapse
:good:

Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that

elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
You can do it if you have a custom recovery already flashed like TWRP or CWM. But I agree with you - after you start having a basic understanding of Android customization, there's no reason why you would want to use 'wipe data' from the volume down+power.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?

opethfan89 said:
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
Click to expand...
Click to collapse
Automatically gets flashed when you flash stock.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

If you are in recovery loop you cannot go into the fastboot menu. The only way to get the stock recovery back is to use nvflash.

Need some quick help

So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?

Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium

Any ideas?
Sent from my LG-LS970 using xda premium

Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.

No one can help?
Sent from my LG-LS970 using xda premium

Well that sucks...
Sent from my LG-LS970 using xda premium

Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.

I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.

[Q] TWRP v2.3.3 - No OS

So I decided to attempted to root and install a custom rom on my tablet today, watched a few videos, read a few threads on here. All in all a tad confusing with all the crazy fonts and such. I decided to follow [youtube[.]com/watch?v=iank8iYulzo] this video, got up to TWRP and installed the CleanROM. When it went to boot, however, it decided to not load (taking over 30 minutes), and I attempted a fresh flash (because I'm retarded). I then went to wipe the ROM, but somehow I wiped the entire OS.
Now I've realised that I had an old version of TWRP and that I had a newer rom version, somehow they were not compatible and I have accidentally royally screwed my machine.
If anyone would be kind enough to help me fix my tablet, and direct me to a nice place where I can follow instructions to install something nice like cyanogenmod.
If anyone helps, thanks in advance.

Pyroaves said:
So I decided to attempted to root and install a custom rom on my tablet today, watched a few videos, read a few threads on here. All in all a tad confusing with all the crazy fonts and such. I decided to follow [youtube[.]com/watch?v=iank8iYulzo] this video, got up to TWRP and installed the CleanROM. When it went to boot, however, it decided to not load (taking over 30 minutes), and I attempted a fresh flash (because I'm retarded). I then went to wipe the ROM, but somehow I wiped the entire OS.
Now I've realised that I had an old version of TWRP and that I had a newer rom version, somehow they were not compatible and I have accidentally royally screwed my machine.
If anyone would be kind enough to help me fix my tablet, and direct me to a nice place where I can follow instructions to install something nice like cyanogenmod.
If anyone helps, thanks in advance.
Click to expand...
Click to collapse
If you want go for CM roms I can't help you much - I'm a hopeless CROMI-X fanboy, but it sounds as if you followed some really outdated threads or instructions.
Do you still have access to your recovery?
If yes, go here, http://forum.xda-developers.com/showthread.php?t=2425383
download and flash the bootloader/TWRP package from the OP,
BOOT BACK INTO SYSTEM,
and you are in good shape to flash either CROMi-X or CM based roms.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

berndblb said:
Do you still have access to your recovery?
Click to expand...
Click to collapse
When you say recovery, do you mean main screen of the TWRP? Install, Backup, Restore, Wipe etc? If so, then yes I do.

Also, I don't have access to my internal storage. I'm not too sure how to open the .blob or any of the files in the META-INF. I'm so terrible at this ****.

too bad mate
yeah gday mate, tristan here.
i here your in a bit of strife about your tablet being a $700 brick, that bloody sucks mate.
i reckon what you should do is just do a backflip. always fixes me bricks.
---------- Post added at 11:27 AM ---------- Previous post was at 11:22 AM ----------
Dear joshua marks of bilgola,
sucked in to your brick. lol :victory::victory::victory::victory::victory::laugh::laugh::laugh::laugh::laugh::silly::silly::silly::silly::silly::highfive::highfive::highfive::highfive:

He is not bricked
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4