I'm attempting to get my Memo Pad 8 fixed. I've got it into a bootloop by modifying build.prop and the only way to fix it is to change it back. I used a DPI changer app, and I felt that I was close to success yesterday, but may have been farther than I'd hoped. I went into recovery and when I used adb devices I got a set of numbers and then the word "sideload". A few commands worked. At the beginning, I attempted "adb pull /system/build.prop C:\Users\user\Desktop", replacing user with my computer name, and got "error: closed". Eventually, I did some things and then got that long list of suggested commands. I don't know what I'm doing wrong. My tablet is able to power on but I can't get into adb because I attempted at a factory reset before all of this. Can someone help me, is there anyway to change build.prop, or am I done for?
Any help?
@Klamman What recovery?
AJM-hackers said:
@Klammanmann What recovery?
Click to expand...
Click to collapse
I'm using the stock Memo Pad 8 recovery. I'm a newbie when it comes to these things. I'm using Android system recovery <3e>, recovery system version 4.2.31 apparently.
Klamman said:
I'm using the stock Memo Pad 8 recovery. I'm a newbie when it comes to these things. I'm using Android system recovery <3e>, recovery system version 4.2.31 apparently.
Click to expand...
Click to collapse
Maybe root is too much freedom for me to handle xD
(I am still in need of help )
Error: Closed
Nevermind... I'm still getting error: closed... please don't tell me that my situation is that hopeless... :'(
Klamman said:
Nevermind... I'm still getting error: closed... please don't tell me that my situation is that hopeless... :'(
Click to expand...
Click to collapse
Don't stress, it can be fixed! When booting hold the power button and Vol down key (it might be up I'm not sure). This will show you three icons (or maybe four). Go to the one saying factory reset/wipe data using volume down, and select it using vol. up. It''ll wipe everything and return everything to stock
AJM-hackers said:
Don't stress, it can be fixed! Your problem is that you need to install TWRP.
Click to expand...
Click to collapse
I'm asking some others for a copy of their build.prop (memo pad 8)
If I have this, would I need to use TWRP? I'd rather not change my recovery, as I've still got warranty for the place I got it from.
Okay, I've got the file.
Now, uhm, what do I do next?
Also, a factory reset is not deep enough, the system files have been edited, namely build.prop
Klamman said:
Also, a factory reset is not deep enough, the system files have been edited, namely build.prop
Click to expand...
Click to collapse
Did you at least attempt a full wipe/ factory reset? build.prop is in /system which it wipes. To use that file remove the .txt extension, go to recovery, mount system(which I'm pretty sure stock recovery can'' do) and adb push the new file.
AJM-hackers said:
Did you at least attempt a full wipe/ factory reset? build.prop is in /system which it wipes. To use that file remove the .txt extension, go to recovery, mount system(which I'm pretty sure stock recovery can'' do) and adb push the new file.
Click to expand...
Click to collapse
Yeah, I attempted multiple wipes which is why my usb debugging was disabled. I'm really new to adb, how do I mount /system? I've tried multiple commands, but most of them come up to error: closed.
Klamman said:
Yeah, I attempted multiple wipes which is why my usb debugging was disabled. I'm really new to adb, how do I mount /system? I've tried multiple commands, but most of them come up to error: closed.
Click to expand...
Click to collapse
I meant the factory reset option not wipe, as I said dig through recovery options I really don't think it'll be there though. BTW I think you should go to your respective forum on XDA I only have an ASUS TF700 and can't really help you unless you take pics of your bootloader options and recovery options and upload them here.
AJM-hackers said:
I meant the factory reset option not wipe, as I said dig through recovery options I really don't think it'll be there though. BTW I think you should go to your respective forum on XDA I only have an ASUS TF700 and can't really help you unless you take pics of your bootloader options and recovery options and upload them here.
Click to expand...
Click to collapse
http://www.smartmobilephonesolutions.com/content/stuck-android-system-recovery
If you go to that link, the first photo shows you what my recovery looks like.
Is there a specific forum for the Memo Pad 8?
AJM-hackers said:
I meant the factory reset option not wipe, as I said dig through recovery options I really don't think it'll be there though. BTW I think you should go to your respective forum on XDA I only have an ASUS TF700 and can't really help you unless you take pics of your bootloader options and recovery options and upload them here.
Click to expand...
Click to collapse
I'm not 100% sure what my bootloader is... is it the first thing that shows up when I hold down vol+ and power? When I do that, I get "No Command", then I have to do a series of taps (one quick power tap, then one quick power and vol+ tap) to get into the place where I can choose what to do.
Klamman said:
I'm not 100% sure what my bootloader is... is it the first thing that shows up when I hold down vol+ and power? When I do that, I get "No Command", then I have to do a series of taps (one quick power tap, then one quick power and vol+ tap) to get into the place where I can choose what to do.
Click to expand...
Click to collapse
Yes, when you first power on using vol+pwr that's it, can you take a pic of this "no command". Did you do data/factory reset in recovery? I'm you beg someone else for a rom.zip you can adb sideload it using the option that says install from adb
AJM-hackers said:
Yes, when you first power on using vol+pwr that's it, can you take a pic of this "no command". Did you do data/factory reset in recovery? I'm you beg someone else for a rom.zip you can adb sideload it using the option that says install from adb
Click to expand...
Click to collapse
Originally Posted by Klamman View Post
"But it seems that, due to the Memo Pad 8's limited recovery settings, a full ROM is required to unbrick my device.
If anyone can provide the full ROM for the stock Memo Pad 8, I'd be forever grateful, and I'm sure other people would be as well!
If you need instructions, I can provide them as well
Thank you so much in advance!"
I may be able to help. Am I just dd'ing partitions?
Is this was he has to do? It seems that my hopes of reviving my Memo Pad may come to reality!
Klamman said:
Originally Posted by Klamman View Post
"But it seems that, due to the Memo Pad 8's limited recovery settings, a full ROM is required to unbrick my device.
If anyone can provide the full ROM for the stock Memo Pad 8, I'd be forever grateful, and I'm sure other people would be as well!
If you need instructions, I can provide them as well
Thank you so much in advance!"
I may be able to help. Am I just dd'ing partitions?
Is this was he has to do? It seems that my hopes of reviving my Memo Pad may come to reality!
Click to expand...
Click to collapse
Do you still have the problem? If so tell whoever it is to make a system dump of the firware, it;s very straightforward, it's like the first result on Google. Cheers, you're almost there!
Klamman said:
Originally Posted by Klamman View Post
"But it seems that, due to the Memo Pad 8's limited recovery settings, a full ROM is required to unbrick my device.
If anyone can provide the full ROM for the stock Memo Pad 8, I'd be forever grateful, and I'm sure other people would be as well!
If you need instructions, I can provide them as well
Thank you so much in advance!"
I may be able to help. Am I just dd'ing partitions?
Is this was he has to do? It seems that my hopes of reviving my Memo Pad may come to reality!
Click to expand...
Click to collapse
As I've already written a how to in german,I think I could help you:
Obviously there is a stock rom indeed, but you have to modify it (dl link is saved as a txt file in the attachments, because i'm not allowed to post URLs
After you have downloaded it you open it with 7zip and navigate to X:\UL-K00L-WW-2.0.0.4-user.zip\META-INF\com\google\android\
and push the modified updater-script to there(it is attached as a .txt file but remove the extension, otherwise it won't work) .
i hope i could help you
AJM-hackers said:
Yes, when you first power on using vol+pwr that's it, can you take a pic of this "no command". Did you do data/factory reset in recovery? I'm you beg someone else for a rom.zip you can adb sideload it using the option that says install from adb
Click to expand...
Click to collapse
if there's a "no command" you're already in the recovery, just press power and vol+ and then it shows you the recovery.
I recommend installing cwm although, you're not able to update OTA anymore, but its way better than the stock recovery
Related
firsth of all hi to everyone, im new here , so be patient.
i was searching on the forum and try to solve my problem, but no succes.
all the methods ive tried are a no go
my problem here is that im already rooted (razorclaw tool), superuser installed aswell, so i dont know what else do i need to enter on the recovery mod (i know i have to press down power button and volume - , at the same time), no succes either, the TF just restar as always or the little android with an exclamation sign appears and i have to restart the TF again
my problem is that i cant install custom ROMS, because it always skip to home screen or to the android with the exclamation.
i cant see all those options that lot of people tallk(install from zip, backup current rom, install X rom)because i never get to that part....
so my problem again, how to install some tool that will allow me to enter in clockwork mode (??) ??, and enable those option at the intial boot (power button & vloume - at same time ) to be abble to access the install from zip, backup current rom, wipe data , etc etc
please if someone can help me with another step by step i will be really happy
I am having the same problem
Sent from my Transformer TF101 using xda premium
i think i have this problem since i got the " FIX the problem with DOWNGRADE from .21 to .19", something along those lines, with the method someone posted before (add both files to SD card but rename one of those and then apply update)
jesesystem said:
my problem here is that im already rooted (razorclaw tool), superuser installed aswell,
please if someone can help me with another step by step i will be really happy
Click to expand...
Click to collapse
but have you installed CWM recovery?
User RecoveryInstaller to install CWM.
http://forum.xda-developers.com/showthread.php?t=1346180
/agree with @baseballfanz
Check that you have CWM installed. Then you should hold volume down + power button till you see in the screen something like (push vol+ to enter recovery). It will appear on the top of the screen. You have to wait a little since it first appears the ASUS screen and if you stop pushing the buttons at that time, the TF starts normally. You have to hold them a little longer till the text appears in the screen.
AzureusPT said:
/agree with @baseballfanz
Then you should hold volume down + power button till you see in the screen something like (push vol+ to enter recovery). It will appear on the top of the screen. You have to wait a little since it first appears the ASUS screen and if you stop pushing the buttons at that time, the TF starts normally. You have to hold them a little longer till the text appears in the screen.
Click to expand...
Click to collapse
OR you can install 'transformer reboot to recovery' from market
Pepecillo said:
OR you can install 'transformer reboot to recovery' from market
Click to expand...
Click to collapse
If they don't have CWM installed, that will only reboot the TF, not get them to recovery.
AzureusPT said:
If they don't have CWM installed, that will only reboot the TF, not get them to recovery.
Click to expand...
Click to collapse
This is 100%. We've already told you this, in this thread This Thread.
You need to install a recovery image access recovery.
If you are this unsure of what you are doing i HIGHLY suggest stepping back and reading all about SU access and the rooting procedures again.
The "flash a new ROM to ________ device" steps are pretty much the same for every Android device w/o a locked bootloader.
Root
make sure SU access can be obtained
flash a custom recovery image
reboot into recovery
do a nandroid back up
wipe
flash
reboot
If you cannot get to where you want. You are doing something wrong. millions of people have followed these same step on millions of devices w/o any problems.
neidlinger said:
This is 100%. We've already told you this, in this thread This Thread.
You need to install a recovery image access recovery.
If you are this unsure of what you are doing i HIGHLY suggest stepping back and reading all about SU access and the rooting procedures again.
The "flash a new ROM to ________ device" steps are pretty much the same for every Android device w/o a locked bootloader.
Root
make sure SU access can be obtained
flash a custom recovery image
reboot into recovery
do a nandroid back up
wipe
flash
reboot
If you cannot get to where you want. You are doing something wrong. millions of people have followed these same step on millions of devices w/o any problems.
Click to expand...
Click to collapse
Thank you¡¡¡¡¡¡¡
Thats the step i was mising , all the instructions are for ppl that actually had cwm recovery, and i was taking advices from posts about installing custom roms and not the 1sth root
Its solved now ,thank you all for your help.
sorry, my bad for asking for help
Sent from my Transformer TF101 using xda premium
Bobsinclair25 said:
sorry, my bad for asking for help
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
In essence there is nothing wrong with asking for help. Heck even the smartest of android hackers started somewhere, asking questions the selves.
The problem lays in the fact that is is pretty common knowledge and a simple search would of gave you the answers you wanted.
Keep in mind nothing i say is meant to come across rude. Sharp maybe, rude? no. If you take what i say as rude. I'm sorry.
No problem. I have been trying very hard to learn on my own. The problem I had with this was trying to find information specific to the transformer. I have done quite a bit with my other android devices and the transformer is new to me and since I use it at work every day I am probably a bit more cautious about it. Thanks, I am working on it.
Sent from my Transformer TF101 using xda premium
I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.
xdatester11 said:
I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.
Click to expand...
Click to collapse
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Pretoriano80 said:
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
AFAIK the nvflash method doesn't work for TF700 and is possible that you really bricked your device... The only solutionn i can see is to flash a recovery in fastboot mod and flash the Asus stock from there,but if you can't even boot in fastboot then i don't see any other way to recover the device.
xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
attachment
NVFlash works with the TF700??? That's news to me!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
Sorry mate,but according to this --> http://androidroot.mobi/2012/07/15/nvflash-for-tegra3-transformer-prime/ <-- i don't think you will be able to use nvflash for recovery and it clearly states that you need to get fastboot working in order to use that method. (to get in fastboot mode press Volume down + Power and release the buttons when the message about having 5 second to press Volume Up shows...if this work you will get to a menu with the "USB icon" wich means boot in fastboot mode).
P.S : Can you tell us why you had to mess with nvflash?That is the most advanced way to recover/backup the Transformer 101/201 series and you have really high chances to brick your device for good.
EDIT: I don't think someone here will be able to make a backup for you with nvflash...it will only lead to more bricks.
EDIT 2: Can you please tell us the name of the app that bricked your device so we can avoid other people bricking their device?
The app was transformer reboot recovery I think.
I only used nvflash because it was the only option left as the tab wouldn't work with adb or fastboot.
I guess I'll keep it as a paper weight.
xdatester11 said:
The app was transformer reboot recovery I think.
Click to expand...
Click to collapse
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.
henbone11 said:
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.
Click to expand...
Click to collapse
Yes,i also used that app with no issue,but one of the developers behind TWRP advised to not use it at all,because if for some reason your recovery gets corrupted (that app send a custom command to boot into recovery) the device will boot loop trying to get in recovery and without nvflash we don't have many options to recover from that.
"
KEEP AWAY from that app for the moment,just stick with the old good " Volume Down + Power and then Volume UP " method to get into recovery.
Same issues here as well
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.
shasan2 said:
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.
Click to expand...
Click to collapse
1The first step is to get your recovery back and working...here's a how-to:
1) Download the recovery from here
2) Follow the instruction on how to flash the recovery in fastboot mode
If the flash went good and you can get in recovery mode follow this steps:
1)Download the 9.4.5.26 firmware from Asus site (the SKU for your region)
2)Extract the .zip file somewere on your desktop (the result will be another .zip file,use it for step 3)
3)Put the extracted zip to a MicroSD card
4)Insert the MicroSD card in your tablet and boot into recovery
5)Install the zip from recovery and restard when done
If all goes well your tablet will be again up and running
Ray of Teamwin
:good::good::good:Thanks a million, seeing the team win screen relieved me. The only problem is i cant boot into recovery (teamwin screen is visible)through the wipe data mode, wherein everything is wiped and it reboots automatically. I cant seem to force the table into recovery without this is there any fastboot command which i can use to force the tablet into recovery.
Need Stock Boot, Recovery, System img
Still no luck with the recovery mode. Every time i wipe the device it automatically reboots. I was wondering if i could get hold of stock recovery, boot and system .img files so that i can push them or flash them through fastboot.
i tried using the blob pack and unpack but i cant seem to get around the blob header thing.
Anyone to spare me stock .img files
End of Infinity
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available
shasan2 said:
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available
Click to expand...
Click to collapse
There's a thread (I can't find it again) that talks about this "Reboot into Recovery" app and how it might be bricking TF700T's. This guy wrote in, because he could not get to the recovery menu at all any more and could not do the "PWR+VOL-DOWN" combo. Nothing would happen. Maybe this was the thread, I don't know.
An XDA Mod in another thread said the app *might* be bricking them, but was waiting for confirmation before posting that it does.
I wish to confirm that IT DOES BRICK TF700T's! IT DOES!!!
And there is NOT A DAMN THING you can do! Your PC will not even recognize that the device is connected! You cannot get to the little icons to pick USB Mode, or whatever it's called.
This is the free app, not the other pay one in the Market. I don't know about that one, but this one is called, "Reboot into Recovery" and if you can somehow find that thread if I don't and just copy my post there, I would really appreciate it! I just want to warn people, ya know?
Also, using ANY of the "ROM Managers", whether it's CWM's, or GooMgr's, will take away all ability to get to a recovery menu at boot, at all! The device will still work and everything and boot to your Home Screen and everything. It won't be bricked like the app listed above does to it, but it will take away your recovery menu altogether and the PWR+VOLDOWN thing won't work any more either.
You can Unlock the TF700T, you can Root it. But you cannot use ANY ROM Mgr and you cannot use that Reboot into Recovery app.
But the app I listed above WILL BRICK YOUR DEVICE BEYOND ANY RECOVERY METHOD!
Please pass this on, I am confirming the experience. It doesn't matter if others say it worked for them. It is bricking them at random and even one of the guys who reviewed the app (diff guy than the one who posted here) said it bricked his. It is happening! It is not the user messing up! I did do it right!
Thanks!
I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No offense, but I think a huge problem in forums, is that people don't read carefully.
1) I think you are referring to the paid app. Read what I said about that.
2) You're saying what you're saying, in a thread started by a guy who had a running device and who didn't after using the app.
3) I said that it bricks them AT RANDOM.
4) Another problem with forums, is that whenever someone has a problem, A LOT of users want to post responses that ignore the users' experience and they want to act like the problem doesn't "really" exist. If multiple people are posting the same problem, then IT DOES EXIST. It just doesn't exist for YOU! But something working for you, does not mean it works for everybody and it does not mean there is a problem with their device, nor that they did something wrong.
5) And yet another problem with forums, is that when someone like me points things like this out, many users will respond by jumping on me, instead of those who try to make the guy feel like he's hallucinating and who, instead of trying to help him out, or just keep their mouths shut if they have nothing helpful to offer, think the right thing to do is to argue with the person having the problem.
These forums are for help and information. If someone has neither to offer the person, or at least warn others, then why are they responding at all? And why would anyone defend someone doing that?! It's ridiculous! But that's what typically happens, especially in XDA doe some reason (lots of snobs here, who like to prove they are, by doing as I just described).
The bottom line is, you do not run the app I talked about and even if you did, that does not take away from the experience that some have had and the best thing, is to avoid the app, because there's a risk involved and there is no recovery from it. I decided to warn people. You decided to tell us that we're hallucinating and that people should use the app. You did not carefully read what I wrote, or you would have checked the Market to see what the name of the app that does not have a pay version is. The one I am talking about does not.
I will tell you this. I am posting this from my laptop, because I had to return my Tablet and have a replacement shipped and now I have to spend a few days getting it all set up again the way I had it.
Avoid the ROM Mgr apps on the TF700T. And avoid the free app called "Reboot into Recovery". A user told me about it for my device, who had seen it used successfully. However, if you look at the reviews in the Market, you'll see that one of them says it bricked his *WORKING* *FINE* tablet and this thread right here has told you about two more. So just believe it and don't criticize, huh?
Okay Mods, feel free to jump on me again, just like last time.
I agree with many of your points, Zeuszoos, and thanks for pointing that out, but I believe there are many senior members at XDA willing to help if they have knowledge/abilities to do so, that's been my experience so far and hopefully it can be yours too. Of course, a little SEARCH won't hurt before posting one's problem, as you reasonably mentioned yourself
"reboot to recovery" has been in my apps STICKY thread in the sections "apps to avoid" (RED) for quite some time now after first reports of bricking users' devices started popping up and I believe it has helped some users who did a little reading before clicking...
My infinity. I was foolishly in a hurry to make sure I was going to be able to receive the JB update and downloaded the build.prop that was posted last week in the ota thread. I'm so retarded that I forgot that build.prop was for .26 and not 30. So I copied it into system/ and rebooted.
Now all it does is sit at the 1st asus screen and nothing else.
I'm rooted and not unlocked. Iv'e tried factory resetting, hard reset, and nothing works. So it looks like I got an expensive paper weight now.
Any recommendations? If so it would be really awesome.
e?
adb push the correct file? might have to root again first.
i know its tempting but wiping data when you can't boot is never a good idea.
I DID THE SAME THING!!! in fact I think he linked me to it :/ lol
any help PLEASE!!
lafester said:
adb push the correct file? might have to root again first.
i know its tempting but wiping data when you can't boot is never a good idea.
Click to expand...
Click to collapse
I'm in the process of downloading the .30 update from asus's website then i'm going to go from there.
darkreaper476 said:
I DID THE SAME THING!!! in fact I think he linked me to it :/ lol
any help PLEASE!!
Click to expand...
Click to collapse
Sucks don't it! I hope we can recover it.
Im new to the asus' is there any way we can adb into these things via stock recovery mode? any way to get that build.prob fixed? I can take it back but I DONT WANNA.. lol
and what would be the correct build.prop to use? I still have my modified one on the system renamed but.......
Ok, Iv'e tried the "adb devices" from the command prompt and i can't get get my computer to recognize the infinity. Iv'e downloaded android sdk and got it up and running but no dice. I don't know what else to do
If anybody has any advice or any suggestions that me and darkreaper476 can do, i will love you forever. :nohomo:
Nevermind...
I can get to where it says:
reboot system now
wipe data/factory reset
wipe cache partition
But i can't get my computer to recognize the tablet.
This might be a stupid question but I'll ask it anyway. Have you installed the proper drivers for ADB to recognize the TF700?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Biohazard0289 said:
This might be a stupid question but I'll ask it anyway. Have you installed the proper drivers for ADB to recognize the TF700?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
would ADB have recognized it recovery mode? Even it it does the ab doesnt give you enough time to work... 10 seconds before it attempts to reboot. what good is adb if the device isnt in an adb friendly mode? IDK... I'm sick of trying to fix these stupid little issues.. I just returned it, sure I lost some photos and files (I HATE INTERNAL STORAGE) but F it... That why I bought the warranty...
thanks anyway
Something similar to me happened when I was restoring what I thought was my original backup of the build.prop file. Now I get stuck on the Asus screen. Reseting cache, delvik, user data, etc doesn't help.
Does anyone have instructions on how to setup ADB, TF700 drivers, and how to take any firmware and flash it that method, in a simple set of instructions that doesn't require a nuclear physics degree?
I would rather not have to RMA this thing and wait a month or more to get a new one ...
1stx2 said:
I can get to where it says:
reboot system now
wipe data/factory reset
wipe cache partition
But i can't get my computer to recognize the tablet.
Click to expand...
Click to collapse
You don't need adb to recover your device, just follow my How-To guide from the General forum and you should be good but you need an external MicroSd card to do it.
Pretoriano80 said:
You don't need adb to recover your device, just follow my How-To guide from the General forum and you should be good but you need an external MicroSd card to do it.
Click to expand...
Click to collapse
This assumes that I'm able to get to the recovery. I was able to at one point, but now it won't. In other words, if I hold Pwr+VDown, wait till the text, and then release Pwr+Vdown, and then press VUp, it says booting recovery image, signature blah blah, shows an android guy with his chest open and a red exclamation mark. That screen shows for a few minutes, after which I get a reboot and its back to the Asus logo. Is recovery hosed now? If so, now what the hell do I do? Is it bricked for good?
spinaldex said:
This assumes that I'm able to get to the recovery. I was able to at one point, but now it won't. In other words, if I hold Pwr+VDown, wait till the text, and then release Pwr+Vdown, and then press VUp, it says booting recovery image, signature blah blah, shows an android guy with his chest open and a red exclamation mark. That screen shows for a few minutes, after which I get a reboot and its back to the Asus logo. Is recovery hosed now? If so, now what the hell do I do? Is it bricked for good?
Click to expand...
Click to collapse
That's the stock recovery, what happens if you press Power button once while you are at the "dead android" screen?
Edit: in your case Restore with Stock recovery should do the trick.
Hi all got my first brick , I use the TF300T and I need your help once., The problem with my tab is not coming when I turn into the asus fastboot screnn but will be forwarded directly to TWRP 2.5.0.0. And there is always some password is required although I have none. Thus, it is not possible to build me a link to the ADB pack I've downloaded, you have a tip for me? I can´t connect my pc with my tab
Can anyone help me here?
I do not go on.
kamil82 said:
Hi all got my first brick , I use the TF300T and I need your help once., The problem with my tab is not coming when I turn into the asus fastboot screnn but will be forwarded directly to TWRP 2.5.0.0. And there is always some password is required although I have none. Thus, it is not possible to build me a link to the ADB pack I've downloaded, you have a tip for me? I can´t connect my pc with my tab
Click to expand...
Click to collapse
I think its no password - pres next
I don't remember where I heave reader but you can tray Google with "twrp pass xda"
That's happen when you do factory reset from android.
You can tray reflash boot
ʞןɐʇɐdɐʇ on tf300t
I can´t to do that.
My problem is:
But I can't use fastboot...
Because I always enter TWRP and asks me for a password.
If I go abort it locks me all requests ,whem I do reboot..
so I can't flash nothing.
Do you have any idea?
I read there is a bug with twrp that shows the password lock screen. There isn't a password. You should be able to just press cancel and go into Twrp recovery. From there maybe try a nandroid restore. I've seen the password lock screen many times and simply "moving on" will allow you to use the recovery regularly.
Sent from my SGH-T989D using xda premium
Weaponx525 said:
I read there is a bug with twrp that shows the password lock screen. There isn't a password. You should be able to just press cancel and go into Twrp recovery. From there maybe try a nandroid restore. I've seen the password lock screen many times and simply "moving on" will allow you to use the recovery regularly.
Sent from my SGH-T989D using xda premium
Click to expand...
Click to collapse
The idea is not bad, but I can not work in TWRP he also gives me no access to my SD card otherwise I would have the floor it again.
Can I delete the main memory? He again offers the fastboot?
I'm slow wipe despair ... no no no cahe factory reset is possible.
HELLLPPPP I'm freaking out
if you want to get to bootloader type when you are in recovery
Code:
adb reboot bootloader
but if your device is bricked there is no solution to that yet...
kamil82 said:
The idea is not bad, but I can not work in TWRP he also gives me no access to my SD card otherwise I would have the floor it again.
Can I delete the main memory? He again offers the fastboot?
I'm slow wipe despair ... no no no cahe factory reset is possible.
HELLLPPPP I'm freaking out
Click to expand...
Click to collapse
If you com to TWRP in the advance menu look for adb update or so, then you can flash
I don't heave now with me main tf300 and I can't chaek where in the menu you can reflash blob with fastboot
ʞןɐʇɐdɐʇ on tf300t
I freaked out
Keshukas said:
If you com to TWRP in the advance menu look for adb update or so, then you can flash
I don't heave now with me main tf300 and I can't chaek where in the menu you can reflash blob with fastboot
ʞןɐʇɐdɐʇ on tf300t
Click to expand...
Click to collapse
you mean the adb sideload? i do not have any upgrade button in the advanced menu
anyway i am unable to do anything cause it always fails to mount partitions... then only thing that can work is the fastboot command but fastboot just freezes
matt95 said:
you mean the adb sideload? i do not have any upgrade button in the advanced menu
anyway i am unable to do anything cause it always fails to mount partitions... then only thing that can work is the fastboot command but fastboot just freezes
Click to expand...
Click to collapse
It is true I simply can not get access.
I think I must write to Asus times what a repair will cost
kamil82 said:
It is true I simply can not get access.
I think I must write to Asus times what a repair will cost
Click to expand...
Click to collapse
someone reported that a new Motherboard costs 196$ i won't repair it for that price...
EDIT: This is not working. Sorry.
all of them didn't work... idme not found....
Where can I order a Mainboards?
I'm from Germany and here I could not find any address.
I would rebuild it myself
I got the same problem, Exact same. I can push stuff to the internal storage but not flash cuz the mount problems.
kamil82 said:
Where can I order a Mainboards?
I'm from Germany and here I could not find any address.
I would rebuild it myself
Click to expand...
Click to collapse
ebay
Try this while in recovery: adb reboot bootloader.
however the idme method worked in fastbootmode, but nothing happened... just like before
Thank´s guy´s i searching a damaged tf300t on ebay.
I need only the mainboard
ok, I probably am not using the correct lingo but I know one of you guys can help me out. I think I'm hung up on the recovery screen?
Have an unlocked tf700t that HAD a JB recovery image on it. Wife wanted to sell it so she did a factory reset before consulting me.
Now the thing is stuck on the attached screen. Is that the recovery screen? The guts are spinning & the "running" bar below that scrolls as well.
I can shut it down & reboot it but can't get into CWM and can't find it with fastboot on my PC (don't think I can even put it in fastboot mode).
When booted up the "device is unlocked" text and the "ASUS" center screen shows briefly, then the android & his innards take the screen and remain. I've tried booting while holding volume up & volume down and I can't get the 3 icons or CWM to show up.
Have I got a brick on my hands?
Help?
Tf701 for sale how much?
Sent from my SCH-I535 using Tapatalk
psouth said:
ok, I probably am not using the correct lingo but I know one of you guys can help me out. I think I'm hung up on the recovery screen?
Have an unlocked tf700t that HAD a JB recovery image on it. Wife wanted to sell it so she did a factory reset before consulting me.
Now the thing is stuck on the attached screen. Is that the recovery screen? The guts are spinning & the "running" bar below that scrolls as well.
I can shut it down & reboot it but can't get into CWM and can't find it with fastboot on my PC (don't think I can even put it in fastboot mode).
When booted up the "device is unlocked" text and the "ASUS" center screen shows briefly, then the android & his innards take the screen and remain. I've tried booting while holding volume up & volume down and I can't get the 3 icons or CWM to show up.
Have I got a brick on my hands?
Help?
Click to expand...
Click to collapse
Yep - that's the stock recovery....
I've read about this... If you do a wipe from the bootloader (maybe the same for a factory reset from Settings) with a custom recovery installed, it can happen that the bootloader writes a command to the misc partition to boot straight into recovery and it gets stuck there.
Do you have ADB access when you are in recovery?
Try 'adb devices' and see if it gives you anything. _that developed a file to solve this particular situation, namely clearing the misc partition so that you can boot to the bootloader.
I think I have that file somewhere. Check if you ADB and I look for it.
The other option would be (if the stock recovery is working) to download the Asus firmware, unzip it once, rename the resulting zip to EP201_768_SDUPDATE.zip, copy it to the root of a microSD, insert it into the tablet and let it boot to recovery. It hopefully would recognize the firmware file and flash it.
You would loose all data though.
Thanks Bernd,
Going with the stock firmware is something I've been trying but not having any luck with. I've tried downloading
ASUS Transformer Pad TF700T Firmware: V10.4.4.20 Only for US SKU (Android 4.1.1)-2012.11.07 update
from
http://forum.xda-developers.com/showthread.php?t=1946456
several times but I have yet to get anything that I can unzip??
stuck into recovery
Hi same problem,
after factory reset inside lates cyanogenmod
stuck into stock recovery
cwm not usable
no adb device visible
won't boot from image taken from
WW_epad-user-10.4.4.20.zip
any other idea?
thanks
g.
psouth said:
Thanks Bernd,
Going with the stock firmware is something I've been trying but not having any luck with. I've tried downloading
ASUS Transformer Pad TF700T Firmware: V10.4.4.20 Only for US SKU (Android 4.1.1)-2012.11.07 update
from
http://forum.xda-developers.com/showthread.php?t=1946456
several times but I have yet to get anything that I can unzip??
Click to expand...
Click to collapse
golemlist said:
Hi same problem,
after factory reset inside lates cyanogenmod
stuck into stock recovery
cwm not usable
no adb device visible
won't boot from image taken from
WW_epad-user-10.4.4.20.zip
any other idea?
thanks
g.
Click to expand...
Click to collapse
Sorry - I do not understand what you are saying.
---------- Post added at 11:19 AM ---------- Previous post was at 11:13 AM ----------
psouth said:
Thanks Bernd,
Going with the stock firmware is something I've been trying but not having any luck with. I've tried downloading
ASUS Transformer Pad TF700T Firmware: V10.4.4.20 Only for US SKU (Android 4.1.1)-2012.11.07 update
from
http://forum.xda-developers.com/showthread.php?t=1946456
several times but I have yet to get anything that I can unzip??
Click to expand...
Click to collapse
That 10.4.xx is really old JB 4.1. The firmware you want to get a the source: Asus
Go here: http://support.asus.com/Download/Options.aspx?SLanguage=en&type=1
Enter "Transformer" in the search box
Choose your model
Select "Android" from the OS choice
....and you will be presented with a list of firmware file, freshest on top.
Scroll down a bit and you'll find the 10.6.1.14.8 firmware for US SKU. That firmware version is still rootable with Motochopper. The latest .10 firmware is not.
Merry Christmas everyone
Fantastic! Thanks Bernd.
DL'ing that file now.
Hope you and yours have a very Merry Christmas out on the west coast.
PS
berndblb said:
Yep - that's the stock recovery....
I've read about this... If you do a wipe from the bootloader (maybe the same for a factory reset from Settings) with a custom recovery installed, it can happen that the bootloader writes a command to the misc partition to boot straight into recovery and it gets stuck there.
Do you have ADB access when you are in recovery?
Try 'adb devices' and see if it gives you anything. _that developed a file to solve this particular situation, namely clearing the misc partition so that you can boot to the bootloader.
I think I have that file somewhere. Check if you ADB and I look for it.
The other option would be (if the stock recovery is working) to download the Asus firmware, unzip it once, rename the resulting zip to EP201_768_SDUPDATE.zip, copy it to the root of a microSD, insert it into the tablet and let it boot to recovery. It hopefully would recognize the firmware file and flash it.
You would loose all data though.
Click to expand...
Click to collapse
Bernd, tried the sd card with the firmware & no luck.
Checked adb and I do get
"015d2ea06d381211 recovery"
so I assume I have access that way. Did you have any luck finding the file you were talking about?
psouth said:
Bernd, tried the sd card with the firmware & no luck.
Checked adb and I do get
"015d2ea06d381211 recovery"
so I assume I have access that way. Did you have any luck finding the file you were talking about?
Click to expand...
Click to collapse
Dang! But at least you have adb....
I finally found the file and the corresponding thread:
http://forum.xda-developers.com/showthread.php?p=48773174
You can download bootit.ko from post 31.
That bloke's situation was somewhat different though and I don't know enough to tell you with confidence that this method would work for you.
The best would be if you could get @_that attention - he's the expert on this.
But read the thread - it should get you closer to a solution.
Good luck and report back please!
Well I'll be. Christmas just keeps on coming. I have a working tf700t this evening. I have no idea of what was taking so long or if it's just a Christmas miracle but I left my pad plugged up to the computer all day. Apparently it decided to get unstuck from the recovery screen all on it's own. Thing boots fine now, completed the reset and went through the initial setup with no problems. Wahoo!
Thanks for all the help Bernd.
psouth said:
Well I'll be. Christmas just keeps on coming. I have a working tf700t this evening. I have no idea of what was taking so long or if it's just a Christmas miracle but I left my pad plugged up to the computer all day. Apparently it decided to get unstuck from the recovery screen all on it's own. Thing boots fine now, completed the reset and went through the initial setup with no problems. Wahoo!
Thanks for all the help Bernd.
Click to expand...
Click to collapse
Santa did hear your pleading and the elves probably had some time to spare right after Christmas! Nice gift! :good: