Related
Hi, I apologize up front for the long winded post, but I want to relay as much info as possible in the hope that someone can point out my mistake(s).
This is the 2nd android phone I have managed to brick in the past couple years.. The first was an old dream and I flashed the wrong update file for a different phone by accident, but at least I knew what I did wrong that time.
Fast forward to yesterday. I picked up a brand new LG Optimus 2X (LG-P999 = G2X) From Wind Mobile in Canada running android 2.2.2. I bring it home and load up super one click and it tells me I am rooted, great! After that I loosely followed these instructions: hxxp://wiki.cyanogenmod.com/wiki/LG_Optimus_2X:_Full_Update_Guide to get ClockworkMod Recovery installed via the market (free version).
First little hiccup was that when I opened the mod manager and tried to click on 'Flash ClockworkMod Recover' it gave me an error saying, "Error while downloading from Server. Please make sure that you have a stable internet connection, and that your SD card is inserted and has free space!". That's weird.. I have a brand new 2gb sd card and my 3g connection is working great.. I was able to sort that out by connecting to my home wifi connection and then this message disappeared. When flashing clockwork it asks for my model of phone and I choose the LG G2X from the list. Success! Although when I try to click on the option to boot into recovery -- nothing happens. Since I don't want to power off my phone, I download "Quick Boot" by Sirius Applications Ltd. and try to click the reboot option, but again, nothing happens. The recovery option also does nothing, whats going on here? I finally decide to power down my phone the "normal" way from the home screen.
I boot back up normally and realize that I didn't download cyanogenmod yet, so I go do that. I download update-cm-7.1.0.1-G2x-signed.zip for the T-Mobile G2x, even though mine is not T-Mobile, I read on the internet that I definitely have a G2x even though it is marketed as an LG Optimus 2X. I also download the Google apps gapps-gb-20110828-signed.zip.
Once the files are downloaded, I attempt to copy them up to the memory card, but windows explorer (Im using Windows XP) seems to lock up for a bit and I get a weird error: Cannot copy gapps-gb-20110828-signed.zip: The path is too deep. I have never seen this copy error before. I look it up on google and don't get much help, although it tells me what I already assume, that this error appears when your filename + path combo is too long. But its not too long! gapps-gb-20110828-signed.zip is on my desktop, and I'm copying to the root of F:\ !! The other weird thing is that this gapps-gb-20110828-signed.zip is only 6MB large. I have no problem copying the update-cm-7.1.0.1-G2x-signed.zip which is 93MB! I can copy any other file I throw at it.. BUT I CANT COPY THE GAPPS FILE !? I tried so many things at this point. I renamed gapps-gb-20110828-signed.zip to gapps.zip. I redownloaded it from the mirror. I tried copying it from the root of C:\ and another drive. I tried unzipping it and rezipping it. I always got the same error.
Finally I decided to copy the gapps file to the internal memory, and it copied without a problem. I wasn't sure if I could access that drive from recovery, but I decided to try it, even without gapps since I wasn't having much luck getting it onto the card. In hindsight, I should have maybe tried copying it to another sd card and also tried copying to the same sd card plugged into my computer via sd reader to see if the same problems existed. Even rebooting the phone and my computer would have been some good troubleshooting, but I wasn't aware of what would happen next.
I booted to recovery at this point (I can't remember if I booted via the rom manager link or if I rebooted and held the power and volume down button) and it came up as expected. I first made a backup of the existing system even though I didn't think I really needed it. Then I did the Wipe data/factory reset and Wipe cache partition. Finally, I loaded the cyanogenmod update and was surprised at how it loaded in mere seconds-- my old dream always took at least 1 or 2 minutes even for a smaller file. I then noticed an option to load a zip file from my the other storage (I can't remember the exact name of the option - but it was the place where the gapps file was). I loaded gapps without error and rebooted the phone.
It is at this point that I never booted back into anything again. If I remember correctly, it loaded the first LG symbol as usual, and then I saw another 'fancier' LG logo come up, with no animation or progress bar. I waited on this screen for more than 10 minutes, expecting that it would finally change to cyanogenmod, but nothing ever happened. No problem I thought, I can just boot back into recovery and try again without the gapps perhaps. No dice. I removed and replaced the battery, and then booted up with the power and volume down arrow held. I saw a LG symbol with progress bar, I saw a android character coming out of a box with a progress bar. I let go of the buttons. The phone rebooted. I tried again and again. Nothing.
At this time I was getting quite worried, but I had my phone plugged into the computer still and I noticed that everytime I got to the 'fancier' LG logo screen, the computer would recognize the phone via usb. I decided to see what the internet offered for solutions and I read lots and lots of info.
Everything boiled down to pulling out the battery, holding the volume up and down buttons and then plugging the usb to the computer. I installed all the necessary drivers and ran nvflash in an attempt to either install CWM or even the stock recovery. Getting the computer to recognize the phone properly was a chore in itself. Often it would come up saying 'Unrecognized usb device' or it would simply show up in the device manager with an "!". Sometimes when it showed up with the "!" I would right-click and uninstall it, then unplug and replug and install the driver again and that would work for a time or two.
The problem was that when I ran any commands I found for nvflash, it seemed to take forever to do anything. I mean I would be waiting, and waiting, and waiting, and all the command prompt would say is:
"Nvflash started"
One post I read somewhere said to just try a harmless command of "nvflash --sync" to see if the proper output appeared. I tried it a few times, but all I got was the same "Nvflash started", but then one time I noticed after a while it came up with a new line after that of "rcm version 0X20001". I tried nvflash at least 1000 times, no joke. I wasn't about to let this brand new phone beat me without a fight.
On one occassion I tried using the "One Click Recovery Flasher" that I found, and I attempted to load the stock recovery. The response from nvflash seemed to flow a little quicker this time and I got further in the process then ever before. Since it was now 4am I decided to let it do its thing and I would wake up and check it in the morning. I woke up at 10am and it was exactly where I left it. After 6 hours, I would have expected it to do SOMETHING! Here is what it said:
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x037c704243a08357
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
It apparently was unable to send the fastboot file for some reason. I could try 1000 more times but I am defeated at this point. I am planning to return the phone today and see what they say. If by chance I return it successfully, and I get the same model of phone, I will be super wary of trying to root it again. But I also don't want a phone that I can't "have fun with". Any comments or suggestions are most welcome. I would like to know what I did wrong so that I can learn for "next time". Other than the weird sd card error, I really think I did everything correct. At this point I am thinking there was either something wrong with the sd card or even with the phone itself. Regardless, I thank you for reading my story and I look forward to any helpful responses.
Cheers!
I'm also on wind. The first thing I did was use nvflash to get a recovery. Never never use ROM manager to flash recovery on the g2x. It's a fake flash. Also, try running a vm or dual boot to use Linux. Nvflash worked fine on Linux didn't try on windows. no drivers needed. It recognizes it without doing anything special.
Sdcard problem is because the 2GB card is under /emmc or /sdcard/_Externalsd our something on stock.
tahahawa said:
I'm also on wind. The first thing I did was use nvflash to get a recovery. Never never use ROM manager to flash recovery on the g2x. It's a fake flash.
Click to expand...
Click to collapse
Did the same thing. I am on Linux too, and everything was extremely simple.
BTW, I think Wind's LG doesn't have screen bleeding or rebooting issues. I've never had them.
It sounds like you didn't install the drivers for the APX mode. When you get the explanation mark you need to right click and say update driver, then says I will find myself and browse to the apx directory where you extracted the One Click program for NVFlash. Then when it says the driver is unsigned click yes to continue. Once the apx driver is properly loaded you can flash CWM and reflash any rom you want. Don't worry your phone is not bricked. It is almost impossible to truly brick a G2X.
Did you resolve this issue. I just encountered it myself. Are you in Toronto by any chance. [sigh]. This sucks. I hope you can help shed some light.
Did you see my advice above? Try that. Also try re downloading everything, including all nvflash files.
Sent from my LG-P999 using XDA App
Awesome. Nvflash unbricked the SOB. I used the youtube video (lookup this one: "How To Install CyanogenMod 7 Nightly on T-Mobile G2x after Nandroid Backup") and the G2x P999 ROM from cyanogen, and got my phone back. The video worked perfectly for me and I would recommend it (but of course don't blame me if anything goes wrong... why should I be different? . The T-mobile stuff bugs me though. I wonder why the cyanogen mod has their branding in it. Ah well.
Now that my phone works again, I can figure out how to get those annoying lines to stop moving all over the frickin' place. Then back up this ROM so I have something to recover to. And maybe try the cynaogen Optimus 2x ROM; although it does say in the file name that it is 990 and not 999. And maybe give the fine xda ROM a go (since I found the answer here).
Thanks to Wind Mobile for messing around with the names and making it confusing. The Optimus 2x by Wind is a P999 and the same as what T-Mobile has, and an Optimus 2x looks to be a 990 everywhere else in the world. I guess Wind never intended to make it easy to upgrade these phones from the start (and aren't offering an official Gingerbread, never mind Ice Cream Sandwich upgrade). Now it looks like they won't even be selling them any more. I guess they would cut into the profit of the new more expensive Galaxy when it comes out.
I know I won't use that ROM manager again. At least not for this phone. Wow!
Thanks again for the quick reply and sticking my nose back into the answer.
Regards,
BillR
tahahawa said:
Never never use ROM manager to flash recovery on the g2x. It's a fake flash.
Click to expand...
Click to collapse
Is this true of ROM Manager in general, or is this something particular to the G2x?
dmj2012 said:
Is this true of ROM Manager in general, or is this something particular to the G2x?
Click to expand...
Click to collapse
Just the g2x/optimus 2x.
theshowmecanuck said:
Awesome. Nvflash unbricked the SOB. I used the youtube video (lookup this one: "How To Install CyanogenMod 7 Nightly on T-Mobile G2x after Nandroid Backup") and the G2x P999 ROM from cyanogen, and got my phone back. The video worked perfectly for me and I would recommend it (but of course don't blame me if anything goes wrong... why should I be different? . The T-mobile stuff bugs me though. I wonder why the cyanogen mod has their branding in it. Ah well.
Now that my phone works again, I can figure out how to get those annoying lines to stop moving all over the frickin' place. Then back up this ROM so I have something to recover to. And maybe try the cynaogen Optimus 2x ROM; although it does say in the file name that it is 990 and not 999. And maybe give the fine xda ROM a go (since I found the answer here).
Thanks to Wind Mobile for messing around with the names and making it confusing. The Optimus 2x by Wind is a P999 and the same as what T-Mobile has, and an Optimus 2x looks to be a 990 everywhere else in the world. I guess Wind never intended to make it easy to upgrade these phones from the start (and aren't offering an official Gingerbread, never mind Ice Cream Sandwich upgrade). Now it looks like they won't even be selling them any more. I guess they would cut into the profit of the new more expensive Galaxy when it comes out.
I know I won't use that ROM manager again. At least not for this phone. Wow!
Thanks again for the quick reply and sticking my nose back into the answer.
Regards,
BillR
Click to expand...
Click to collapse
Never flash anything meant for p990. Period. Unless it states it is for both. cyanogenmod had no Tmobile stuff except wifi calling.
Sent from my LG-P999 using XDA App
tahahawa said:
cyanogenmod had no Tmobile stuff except wifi calling.
Click to expand...
Click to collapse
When I first started the phone a message came up asking me if I wanted to run something, and that I could go to the T-Mobile site later if I didn't want to. Now I have been playing with it for the last hour and haven't seen any other TM related stuff, so maybe it was just that one.
The very first time it runs you get that message from the wifi calling app. You should never see it again unless you do a factory reset.
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.
First off, my tablet isn't bricked. I can boot it up fine. But when I try to install the factory downloaded software it just hangs on boot indefinitely. Similar things happens if I try to enter recovery. It goes fine until I have to press Volume ^, then it just freezes and I have to hold down the power key for 10 seconds. I've searched around and all I can find is threads from people stuck in a boot loop. Any help appreciated
A little more information. This tablet has been sitting for a while because it was such a disappointment. Before I decided I was fed up with it, it looks like I unlocked and rooted it. Iooks like I may have also tried to install Clockwork Mod on it. Trying to fix it has reminded me of why I stopped using it in favor of my nexus 7. The UI feels like it was designed specifically to make people not want to use tablets.
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
berndblb said:
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
Click to expand...
Click to collapse
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
RussTdesign said:
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
Click to expand...
Click to collapse
The first thing you should have done is upgrade your bootloader to the latest version. I would not actually use TWRP 3.0 for anything at this point if I were you. I have no idea if TWRP 3.0 works with that ancient JB 4.1 BL you got there, but I would not chance it. As a matter of fact, since you have to flash either stock rom or just the bootloader (and for both you use your recovery) I would highly recommend you flash an older TWRP version that is compatible with your BL. That combo - BL and recovery - is nothing you want to screw around with. You should go back to TWRP 2.4.1 or so.
TWRP Manager forced the latest TWRP version (developed for MM roms) on you and that's why I hate these apps! They do not check for compatibility at all....The proper way to flash a recovery is in fastboot and in fastboot only.
so I am going to give you a bunch of links and a general plan of attack, but you will have to do a fair share of reading.
First things is: Get fastboot working on your PC!!!!!! The first part of this guide I wrote way back tells you how: http://forum.xda-developers.com/showthread.php?t=2688891
Once you got that working flash TWRP 2.4.1 - instructions on how to are in the same thread. Reboot the tablet, then boot into TWRP.
Now flash the latest bootloader (Packaged with a slightly younger TWRP version from here: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
Reboot the tablet, then boot back into TWRP.
Now you again need to update your recovery to a version you can use with a current rom. I'd recommend this baby and it comes in a zip you can flash in your current recovery: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Flash the Kang recovery, then reboot and boot back into TWRP.
Format your data partition in TWRP. It takes an hour or so but it does a great job of leaving you with a clean slate for the new rom and is required before you flash a major change (which you are doing in any case).
Now you are ready to flash a rom.
I am going to recommend a really old one and a really new one. There are plenty of others to choose from in the Development section, but none of them is still under active development.
CROMi-X Resurrected. Based on Asus stock anno JB 4.2.1 but modded and fine tuned to the gills. LMK still puts out an update now and then, but those are more fine tunings of the fine tuning. Very slight changes - nothing major is going to happen here anymore. But it's a very stable and well working rom for those that actually like the Asus interface. http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
KatshMallow by Timudru. Yeah, Android MarshMallow for the TF700. Most Android users are still dreaming about MM and you can rock it on this ancient machine. And it's a beauty, just absolutely unbelievable what Tim has cooked up for this hardware. Trust me! Fantastic rom! http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
For both of them you should convert your data partition to f2fs which you can do in recovery. Instructions are here: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Actually, for CROMI-X Resurrected you don't have to do this - it's build into the rom installer.
You could try to short cut all this and just flash a new bootloader/recovery combo in your current TWRP 3.0. Maybe it works. Maybe it hardbricks your tablet. Nothing worse than trying to do something substantial (like flashing a bootloader) in an incompatible recovery....
Ok, now I shut up and let you read.
Have fun!
@berndblb thank you so much. I really appreciate you taking the time to help me out with this. This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions. I will get back later and let you know how it goes.
RussTdesign said:
@berndblb This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions..
Click to expand...
Click to collapse
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
berndblb said:
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
Click to expand...
Click to collapse
I have fast boot running and back-checked it via the fastboot devices. I downloaded twrp-2.4.1.0-tf700t.blob. the tried to load it. I keep getting a FAILED( command write failed (Invalid Argument)). Any thoughts
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Got fastboot running properly on my work computer with windows 7. I've gotten everything installed up to formatting the data partition. Doing that now. Super stressful & hard not to mess with it while it makes its way through a hour long process.
What did the trick to get fastboot working?
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Looks like I got it sorted. Decided on going with the KatKiss rom. And the performance is night and day. Thanks so much for all your help. Next time I will probably do more reading before I try anything more... But then again I tell myself I will read the instructions before I start assembling ikea furniture & never do. So only time will tell. Anyway. Thanks again.
berndblb said:
What did the trick to get fastboot working?
Click to expand...
Click to collapse
Installing it on a different computer. This one runs windows 7. My laptop runs windows 8.1, could be as simple as that. But who knows.
I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:
monogwai said:
I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:
Click to expand...
Click to collapse
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....
berndblb said:
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....
Click to expand...
Click to collapse
I figured that would probably be the case. Now, it's been several years since I've used Linux (Ubuntu Feisty Fawn was the last time I used Linux, and that was just to hack a first gen Xbox), but i'm a command-line based OS guy from the days of old, so I oughta be okay. I'm sure one of the various and sundry tutorials here on xda will help should I get stuck.
So, that being said, I guess I just need to install a distro and grab some adb/fastboot drivers for Linux? Or is that all built in? Is the command line interface sufficient, or will I need some GUI like xwindows (sorry if my info is horribly dated, lol.)
I'd probably better do some reading.
Nobody has any more expertise to proffer?
monogwai said:
Nobody has any more expertise to proffer?
Click to expand...
Click to collapse
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary
berndblb said:
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary
Click to expand...
Click to collapse
This is just the tip I needed. Big thanks!
Well, i assembled the troops- universal naked driver and minimal adb/fastboot on a fresh win 8.1 install. Bootit.ko file in my adb folder. Opened adb, plugged in tablet. Twrp starts. Hear the USB plug in noise, so adb is ready. Adb devices command, shows up recovery like it should. I then run a batch command to automate:
adb push bootit.ko /sdcard/
adb shell insmod /sdcard/bootit.ko
... as per the directions. I get this in response:
adb: error: connect failed: protocol fault <couldn't read status>: no error
on the first command, and 'no device found' on the second.
Now what?
Edit: nevermind. Added 'adb devices' to the batch file and it did it fast as anything. Lol.
New kink: adb command succeeded and i got fastboot access. Formatted 'misc' partition and rebooted-- still with the bootloop. I can still access fastboot, but that's it. Twrp always restarts. So, did SWIM bork the recovery partition too? Wondering if I should try re-flashing twrp, or downloading the original ASUS blob file and restarting from square one?
Edit:
Got impatient, started trying things. Links found thru the forums pointing to original ASUS rom blob are all broken, so i settled for starting with twrp. Downloaded freshest version from twrp.me compatible with the device and flashed it-- same result upon attempting to open twrp.
Took a break. Thought about it, and decided to fastboot erase recovery, and try flashing twrp again. Probably not a great idea... Now I get
Sending 'staging' <7210 kb>...
FAILED <data transfer failure (unknown error)>
So I guess there's a step after erasing to re-init the partition or something?
Just a note to anyone lurking - don't do stuff if you're only half-informed. You can be stupid and impatient like me and have broken stuff.
Impatience is a very bad advisor...
As long as you have fastboot you should be ok. Asus seems to have messed with their website again or they finally took the support pages down permanently.
I have a copy on my server and can upload it tonight.
Patience my friend, patience
berndblb said:
Impatience is a very bad advisor...
I have a copy on my server and can upload it tonight.
Patience my friend, patience
Click to expand...
Click to collapse
This is too true. That's why I threw in that little blurb. :good:
I'll await your link with bated breath.
Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again
berndblb said:
Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again
Click to expand...
Click to collapse
Debate my breath? Well, my breath reeks of Marijuana... I think it's a liberal.
Lol
Just a question: since I'll be repopulating all the partitions with the stock blob, does that affect my unlocked bootloader, or is it gonna be straight up manufacturer reset? I'm sure that's covered in the threads that address the 'buster99' process, but I need to go locate the thread. I didn't fully digest the thread as i'd yet to find the blob I could d/l, until you hooked it up. ?
No, you cannot relocate the bootloader. Flash away
berndblb said:
No, you cannot relocate the bootloader. Flash away
Click to expand...
Click to collapse
Ugh, corrupt archive. ? trying to download from a different server this time.
Edit: same results w/new download. Repairing the archive didn't help either.
Asus, ya'll are killing me! Every link on the interweb linking to a TF700 firmware is broken, and all that can be found are for the 700kl.
Final update:
Found a valid download link for 10.6.1.14.8. Had some difficulties with it (revived the post on the buster99 process) -- followed as written, and had a fail on the last process <invalid state>. Being super impatient (mentioned *that* before, lol), I decided to try and reestablish twrp, as that was the original issue. That took! Flashed 3.0.0-1 (iirc), was able to open twrp, but couldn't mount system or anything. So I formatted the crap out of all partitions, converted /data to f2fs, and was able to successfully flash katkiss nougatella. Wiped the caches, rebooted, and I'm golden! 3 months later, and it finally works.
Moral of the story: don't sell rooted devices to ppl who don't understand what that entails. You can tell a person till ur blue in the face, NO FACTORY WIPE VIA ANDROID -- Odds are, they'll forget. Worked out for me in the long run (took back the 700 and gave a 201 as replacement), but i was never sure I'd come out clean on the other end.
I have similar problem, i can't even go to bootloader.
Just keep bootlooping. Is there any chance of reviving my tf700t?
If yes please advice me step by step process to do that.
Thanks
Not enough information. What can you get to?
What's your ROM, bootloader, recovery?
berndblb said:
Not enough information. What can you get to?
What's your ROM, bootloader, recovery?
Click to expand...
Click to collapse
Thanks you already help on other thread.
It's a long story how this happened.
By the way I was running nougtell version don't remember as it happened in January.
I wanted to transfer some video files on my usb 2tb hard drive, so I did usb otg connection to my tab, i did this thing before and I use es file explorer to do the transfer, few occasions es file hang or whole tablet hang so I have to restart. But in January when this thing happened it just went into bootlooping i can go to fastboot but not recovery or android.
Then I search on many thread i couldn't find any working solution.
My cable was not detecting tab so I couldn't able to push recovery., But the same cable was ok for charging.
Then I bought new cable from eBay it took around a month to arrive.
But in mean time being impatient i tried data wipe from bootloader.
Then even i couldn't able to bootloader after that.
I know being impatient with doing something like this is not good you have to suffer.
Bootloader was latest version .14 at the end and recovery was 3.0.1
Using nogtella rom
Thanks
Hi all, a few months ago i had a perfectly running rooted TF101 with stock asus firmware. It has CWM recovery v6.0.1.3 and i had the CWM app installed.
somewhere along the timeline i decided it was a good idea to backup the whole thing using the CWM app just in case anything funny happens. Now don't ask me how or why it went the way it did, but the CWM app seemingly performed its backup, there was a disclaimer warning somewhere about possibly losing root access, to which i think i said "yes", the device rebooted and my entire image was gone - only left with CWM recovery mode.
I have been trying to reflash it with stock recovery image, but the SD card won't mount. I am also unsure whether i still have root access or not.
in terms of connectivity, all i was able to get back was ADB access, which i was able to search xda and find threads such as these to try and fake an sdcard then reflash
https://forum.xda-developers.com/showthread.php?t=911228
I've tried katkiss image and stock image but everytime i get a status 7 error or an error 21
https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
https://www.**********.com/fix-status-7-error-while-installing-ota-update-or-roms/
I'm not exactly an ADB crackhead and I'm not able to get past it so i've searched some more and found on xda again threads on using EasyFlasher, I've followed the instructions but can't get the APX drivers installed on windows 10.
https://forum.xda-developers.com/showthread.php?t=1688012
basically, at this stage i've read many articles, many posts, none have worked because links are outdated or instructions are outdated and mostly i'd rather stop trying all i am finding without really understanding before i brick this device for good out of ignorance.
sure it's old but it was functioning properly and was being used actively by my kids. if i can get it back to life, that'd be nice.
has someone experienced (and fixed) something similar or feel can contribute to unbricking my device?
Thanks guys.
I'm a noob myself, but I managed to get the APX driver installed on Win 10 (just now) by following the directions at how to geek dot com. I used "Option two: Use an Advanced Boot Option."
Good luck!