Related
I have spent hours searching and reading, but I can't find an up-to-date answer.
I have a B70 TF101 that is at 8.6.5.21. I rooted using nachoroot. I want to put on cyanogenmod 9 RC. It does work using ROM Manager. Seems that in spite of telling it to install clockworkmod, it doesn't. I can't get it into APX mode. So I guess I'm ready to try to downgrade it to 8.6.5.19. I find loads of references and links to multiupload for that file, but it no longer is available.
How can I downgrade to 8.6.5.19? I just want to put on Cyanogenmod.
Please help.
Hi Thornthree,
try http://forum.xda-developers.com/showthread.php?p=25385687 step 3.
in this post you find places for the blob file and what to do (step 3)
I think you need the 8.6.6.19 (is for tf101/g, but also for the tf101
But is your TF now able to go into apx mode yes or no?
maybe start with this:
http://forum.xda-developers.com/showthread.php?t=1688012
goodluck......
There's not a need to downgrade.
You could also use PERI.
http://forum.xda-developers.com/showthread.php?p=26737790
Yep, several one-click rooting methods out for the latest versions.
My PERI tool as mentioned above is one of these, just plug-in, run and root.
I could never get into APX mode. I followed all of the instructions to get there that I could find but none of them worked. The power and up volume keys did nothing on my TF101. I finally got power and volume down to get me into clockworkmod, but then it couldn't find the zip file. When I finally got the zip file visible, then chose reboot system now, it just kept looping into clockworkmod. Somehow, in the end, after all kinds of crazy attempts of key combinations, it's somehow worked.
I had to end up going back to factory reset, then all kinds of acrobatics to place a zip file in the right place, then do another factory reset and wipe, which somehow ended up in my having cyanogenmod working. I don't know if I could reproduce the process. Also, it's very frustrating that none of the tutorials did anything to work on my tablet. I'm just thankful that it's where I want it right now. I don't know if I need to install OTA root keeper or not, and I don't know what I'll do if I ever need to upgrade to a different ROM or an updated cyanogenmod.
Thanks for all the replies. I'll keep them in mind for the future.
Sent from my DROID2 using xda app-developers app
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
Hi guys,
A while ago, I've rooted/unlocked my device in order to install Cyanogenmod, installed PhilZ bootloader. Been running through some versions, never happy with the result - slow response, games not running that well, etc. The last time, I got some new update (can't remember which one though ...) which was the worst nightmare. Without any app running, I thought I was on some Eboda tablet, the cheapest one. Last night I've tried to connect the tablet to my laptop, to put some ebooks on it, without success. Nothing I did convinced the 2 devices to see one another. So, I tried to go back to some previous ROM, boot the device in recovery mode and did a wipe. Forgot that at some point I erased all ROMs from it ... now, I still can't connect to it, so that I can copy some version of ROM, any version, although Windows shows it as installed and connected. Bottom line is that now I got no ROM on the tablet, not installed and also not one that I can install, only got the PhilZ bootloader. Is there any way to get my tablet back or is it bricked ?
You are confusing bootloader and recovery. But as long as you can get to the bootloader *or* to your recovery, it is possible to restore your tablet.
To talk to the bootloader, you need to use fastboot.
To talk to the recovery, you need to use adb.
For more details, read berndblb's comprehensive guide in the General section.
_that said:
You are confusing bootloader and recovery
Click to expand...
Click to collapse
You are right, I have to admit I have not been very thorough the first time I went about this
Thank you very much, I will track down this guide, perhaps I will be able to restore my tablet to some use ...
Hi all,
As it turns out, I had only to push one flashable image (used CM11) and was able to put the tablet back on it's feet. Many thanks to berndblb
Have fun!
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!
Hopefully it isn't but I have a bad feeling.
I haven't been here for a long time, life got in the way and I didn't have time to play around with things. A few years back, I rooted my TF101 and installed Cyanogenmod. It sat in a drawer for most of the last year.
A few days ago, I decided to try a different rom that sounded cool. Attempted to flash it but it didn't go right. Could only boot into recovery. So I tried to sideload TWRP via ADB. I followed some steps I found here, or somewhere else on the internet, not sure now, but it said to delete pretty much everything first. I deleted everything it said to, but I think that was a bad move.
I can now only boot to APX mode. I have tried using Easyflasher to "unbrick" it, but Nvfalsh just hangs. Same if I try to install a recovery with it.
So is it time to give it up and use it for a target the next time I do some target shooting?
EDIT: Sorry, I kept getting interrupted with work calls. When I said I could only boot to recovery after attempting to install the new rom, I meant fastboot. When I used volume up to select recovery, I got an unrecoverable bootloader message. It was at this point that I used fastboot to try to install TWRP. After doing that, it hangs on the ASUS splash screen and APX is all I have now.
Well I really screwed up! Like I said, it sat in a drawer for a year, and I don't know WHY I had it in my head that it was a 101. It's a TF701T. So attempting to flash a 101 rom has probably totally hosed it.
If anyone has any suggestions, that would be great. Otherwise, I have a new target this weekend!
Bluze said:
Well I really screwed up! Like I said, it sat in a drawer for a year, and I don't know WHY I had it in my head that it was a 101. It's a TF701T. So attempting to flash a 101 rom has probably totally hosed it.
If anyone has any suggestions, that would be great. Otherwise, I have a new target this weekend!
Click to expand...
Click to collapse
I know this is a few weeks old but in case you are tracking, how about heading over to the tf701t thread and see if you can find anything helpful. the 701t would be worth the hassle of trying to unbrick
Did you know the Virtual Machine? Any kind(Virtual Box, VMware, etc...). I think that you can use virtual machine to create a Windows XP. In the WinXP, driver verification problem did not like Win7, Win8.1, Win10, you can easily install APX Driver without any problems, and i guess you can run the "Easyflasher" correctly.
I had the same problem when i use the latest "Clock Work Mod" recovery for TF101, the recovery can't mount SD card, so if you can flash back to asus rom with Easyflasher, I suggest you flash the TWRP V2.8.1.1, the flash file can be found on XDA Forum, hope you can resolve your problem