No Recovery file - Asus Transformer TF700

DisabledDroid said:
I have a unique problem, and I hope to some guidance on it.
I have a used TF700t I am trying to get unlocked. But it is not simple and will explain -
Bought the tablet used and expected it was in good shape by doing a full restore with a wipe of all data. The next task was getting it rooted and I was successful (after my upgrading apps and reading forum). I then tried to put TWRP on it and was going nuts.
It seems not to have a recovery on. Several tools pointed me in the right direction.
It has build jro03c.us_epd-10.4.4.20_20121026 running Android 4.1.1. Says is rooted but no permission to use the 2020 fix for the unlocking.
I understand there is a way to get and put a stock recovery on it......
From a Disabled NOOBie

Related

[Q] Noob questions re: Auto Update

Last night, I read the posts re: the auto-update and the potential havoc it can wreak on my phone. As a Noob (I did my first root, this weekend), I'm concerned and would appreciate any help understanding the jargon and my situation.
I just got a SCH-I535 and despite "having no business" rooting it, curiosity got the better of me and I followed eMpTy43's [GUIDE] For beginners - Root Verizon Samsung Galaxy S3 SCH-i535/d2vzw. Per those instructions, I rooted using "Root Debug FS", unlocked using "EZ-Unlock", I installed "ROM Manager" and flashed "Clockwork Mod Recovery". On that last step, I had some problems due to the formatting of my external SD card. I think I successfully created a Nandroid backup to both my internal SD and, finally, to my external SD. Subsequently, I purchased Titanium Backup Pro. I ran "Batch Backup/Restore All" to my external SD.
If I understand correctly, I now have a "rooted", "unlocked", "stock ROM" SCH-I535 with a "custom recovery". Is that right?
My device reads that it is running baseband version VRLG1 and kernel version 3.0.8. From reading the posts on the auto-update, it seems my phone should need to auto-update. Is that correct?
Late last night, if I understood correctly, it seemed community members suggested several possible steps:
Some people suggested that I could prevent the auto-update from running my using Titanium Backup to freeze SDM 1.0. Is that correct? After I return from work and get the kids to bed tonight, I intend to look up what SDM 1.0 does. But, if anyone wants to help here, it'd be appreciated.
Someone posted a suggestion to install Voodoo OTA Rootkeeper, which I did. Does that, in effect, do the same thing as freezing SDM 1.0? Is there a problem in doing both?
I also read that having a "custom recovery" makes the entire issue moot. If that's correct, why would that be?
If I dodged the bullet, it's my understanding that I should either (1) sit tight and wait for the community to develop guidance for n00bs or (2) re-lock and un-root the phone since I have no business doing this in the first place.
Am I understanding all this correctly? Am I missing anything? Any recommendations?
Thanks in advance for any help.
Yes you are correct you have a rooted, unlocked(bootloader), stock ROM, and a custom recovery. (clockwork mod recovery that you flashed through ROM Mamager)
Because you have the Clockwork recovery installed the update won't actually install. It may still download and annoy you though. The reason it won't install is because over the air updates(OTAs) rely on the stock Android recovery for installation. By flashing Clockwork recovery you have replaced the stock recovery and that causes the update installation to fail.
I don't know what SDM 1.0 is exactly. I do know that freezing it with Titanium Backup will stop the update from downloading and annoying you and doesn't seem to cause any other issues.
All in all with the custom recovery you will be safe from the OTA. However, I would freeze SDM 1.0 for good measure to stop your phone from trying to automatically download the update. (even though with custom recovery it will never install)
I highly suggest you go through and read read read all the sections in Verizon Galaxy S3 (especially stickies) and anytime you come across a term you don't understand Google it. Just keep reading and reading and Googling. That's the best way you can learn more about all this. Until you understand it all a bit better I wouldn't do more than what you already have. (i .e. Flashing ROMS and kernels etc...)
Thanks for the substantial reply. I'm resting a lot easier at work, now. It would have been a real pain to have a brick 2 days after my first root.
Sent from my SCH-I535 using xda premium

[Q] A700 rooting question

Hi guys,
I've searched everywhere and can't get a definitive answer on this so here goes -
I'm a noob when it comes to Android, having recently defected from being an Apple Disciple (I got hacked off with iTunes and bored in general with the Daycare Centre which is iOS) and have recently acquired an Acer A700 tablet.
I have installed the JB update OTA and everything is working fine and am chomping at the bit to get it booted, but most of the posts I have read regarding unlocking the bootloader and rooting it relate to ICS.
My questions are -
Does the bootloader process apply regardless of Firmware? (Are there different versions for different Firmwares)
Can anyone point me in the direction of a decent tutorial on how to do this?
What happens regarding a future update? Do I have to revert back to stock and update from there or can i jump from one ROM to another? (I'm assuming that I can't use the OTA updates any more)
Sorry for the long OP and thanks in advance for your answers.
ianrobbie said:
Hi guys,
I've searched everywhere and can't get a definitive answer on this so here goes -
I'm a noob when it comes to Android, having recently defected from being an Apple Disciple (I got hacked off with iTunes and bored in general with the Daycare Centre which is iOS) and have recently acquired an Acer A700 tablet.
I have installed the JB update OTA and everything is working fine and am chomping at the bit to get it booted, but most of the posts I have read regarding unlocking the bootloader and rooting it relate to ICS.
My questions are -
Does the bootloader process apply regardless of Firmware? (Are there different versions for different Firmwares)
Can anyone point me in the direction of a decent tutorial on how to do this?
What happens regarding a future update? Do I have to revert back to stock and update from there or can i jump from one ROM to another? (I'm assuming that I can't use the OTA updates any more)
Sorry for the long OP and thanks in advance for your answers.
Click to expand...
Click to collapse
No problem. Seeing you are on JB, then you have a JB bootloader.
You need to go here http://forum.xda-developers.com/showthread.php?t=1953917
And download Vorbeths easyroot2.0. It's for the 700.
You have to unlock your bootloader first, which shouldn't be an issue for you. Easy instructions for that.
Then download his package to a folder on your PC. (not sure, but you may have to download each file individually) Open a command window (shift & right mouse click) and type in whatever his instructions say. Should be painless.
Make sure USB Debugging is turned on first in your tablet (Settings/Developer Options/USB Debugging), and make sure you have the Acer Drivers installed on your PC.
Then connect, wait 30 seconds, and run his batch file.
You should be ok.
MD
Oh yes, one more thing, once you unlock your bootloader, chances are you will not be able to get OTA. And the only way to re-lock the bootloader is to install a stock rom.
Thanks!
Thanks for the reply. I am now the owner of a fully rooted A700!
Had a few issues during unlocking the bootloader. That thing timeouts quick! Also, didn't realise you had to run the .bat file while the tablet was on the Bootloader USB protocol screen. I thought you had to wait until it booted fully into JB.
Anyway, took the plunge and thanks again for your help.
ianrobbie said:
Thanks for the reply. I am now the owner of a fully rooted A700!
Had a few issues during unlocking the bootloader. That thing timeouts quick! Also, didn't realise you had to run the .bat file while the tablet was on the Bootloader USB protocol screen. I thought you had to wait until it booted fully into JB.
Anyway, took the plunge and thanks again for your help.
Click to expand...
Click to collapse
No problem. I thought I mentioned it timed out in about 5 seconds These days I don't remember much
Yeah, I haven't looked at Vorbeth's script, so I don't know which screen he launches it from. With mine for the 701, you can be when the tab is running normal. No difference in the end result though
Happy Hunting!
MD
One last question - do I have to install Clockwork Recovery for re-flashing the stock images or is it just a case of renaming it update. zip and putting it on an SD Card? Any chance you can point me in the right direction of the most recent/stable build? Is it easy to install?
Thanks again.
Sent from my GT-I9305 using xda app-developers app
ianrobbie said:
One last question - do I have to install Clockwork Recovery for re-flashing the stock images or is it just a case of renaming it update. zip and putting it on an SD Card? Any chance you can point me in the right direction of the most recent/stable build? Is it easy to install?
Thanks again.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Well, this is a trouble spot.
If you wish to install a custom rom, then you will need to install CWM. The most recent version.
If you want to try your luck at installing a stock rom, my opinion, is to leave the stock recovery inplace. I haven't had luck in installing stock update.zips, as Acer has made them very specific. So I can't be much help to you in that.
However, you can always flash back to CWM or a stock JB recovery pretty easy. Personally, unless you plan on flashing a custom, I would just leave the stock recovery.
MD
Sometimes "leaked" update appear here in the forums. They are unofficial. And you never know if they improve things, or make things worse. So be careful.
Moscow Desire said:
Well, this is a trouble spot.
If you wish to install a custom rom, then you will need to install CWM. The most recent version.
If you want to try your luck at installing a stock rom, my opinion, is to leave the stock recovery inplace. I haven't had luck in installing stock update.zips, as Acer has made them very specific. So I can't be much help to you in that.
However, you can always flash back to CWM or a stock JB recovery pretty easy. Personally, unless you plan on flashing a custom, I would just leave the stock recovery.
MD
Sometimes "leaked" update appear here in the forums. They are unofficial. And you never know if they improve things, or make things worse. So be careful.
Click to expand...
Click to collapse
So, just for future reference, how would I go about re-flashing the stock image? I'm assuming it's saved on the tablet in a separate partition?
I've decided to stick with the stock rooted ROM but would like to know how to re-flash for when Key Lime Pie and future updates are released.
And, seeing as how you haven't steered me wrong so far, I though I'd pick your brains one last time.
Hope you don't mind!

[Q]

Hi everyone
First off I would like to thank everyone who contributes on this board, I have been lurking for quite awhile even though I dont have any android devices, the reading is very interesting.
I have just got my first android device today delivered from BH Photo (I am in Australia) and have charged and powered it up. I have been reading on the forums about rooting and then unlocking. The android version appears to be 4.0.3 (ICS).
My questions are these:
Should I root this device and unlock the bootloader with ICS, then install TWRP and make a backup of it. Once this is done then update to JB? The firmware of the tablet is (I think this is right) IM74K:US_epad_9.4.5.26-20120720 and the kernel is 2.6.39.4 [email protected] #1
or
Update the device to JB then root it, but Im a bit confused with the unlocking part here what program is used to unlock the bootloader? Is it the Asus one? Also with rooting programs which one is more commonly used for both ICS and JB? Can I apply a manual update of JB using the Ausrtalian version instead of the US one.
Sorry for all the noob questions. I have read the index and after reading it still had some questions.
Thank you for your time
deathwalker01 said:
Hi everyone
First off I would like to thank everyone who contributes on this board, I have been lurking for quite awhile even though I dont have any android devices, the reading is very interesting.
I have just got my first android device today delivered from BH Photo (I am in Australia) and have charged and powered it up. I have been reading on the forums about rooting and then unlocking. The android version appears to be 4.0.3 (ICS).
My questions are these:
Should I root this device and unlock the bootloader with ICS, then install TWRP and make a backup of it. Once this is done then update to JB? The firmware of the tablet is (I think this is right) IM74K:US_epad_9.4.5.26-20120720 and the kernel is 2.6.39.4 [email protected] #1
or
Update the device to JB then root it, but Im a bit confused with the unlocking part here what program is used to unlock the bootloader? Is it the Asus one? Also with rooting programs which one is more commonly used for both ICS and JB? Can I apply a manual update of JB using the Ausrtalian version instead of the US one.
Sorry for all the noob questions. I have read the index and after reading it still had some questions.
Thank you for your time
Click to expand...
Click to collapse
Welcome to the Community!
There are a few on-going threads regarding this same topic. You might want to read those and make sure you understand the lingo/jargon being used (like: fastboot, bootloader, Recovery, adb. etc) as well as what it's for before you start your hacking.
Some things to keep in mind
Currently to have Root access in JB, you need to get root in ICS then use OTA Keeper to maintain Root for JB update.
The Bootloader unlocker tool is from ASUS and needs to communicate with ASUS servers for it to unlock.
Unlocking the bootloader will void your warrenty. Make sure you have a good device before you do it.
You have a version of tablet (9.4.5.26) that is able to use NVFlash that can help recover your tablet during a soft brick.
You should use an update that is appropriate for your device. If it comes with US, stay with US. Installing an update for a different region might not cause problems but there is no guarantee. Best to avoid the possibility by staying with the region it comes with.
For some reading material, I think that my blog post might help give you some additional details. However, I highly suggest that it be used for research only until you are aware of exactly what you are trying to accomplish. Remember to ask questions if things are confusing or if you are wondering what needs to be done next. 'Tis better to ask and be delayed than to be over-eager and bricked.
Hope this helps you during your first steps of XDA Android hacking!
I just got my TF700 last week and I wanted cleanrom on it and this is the order of stuff I did:
1. Unlocked bootloader
2. Nvflash setup
3. Installed TWRP
4. Flashed official Asus update
5. I lost TWRP so I installed it again
6. Flashed cleanrom
Probably not the most efficient way, but it was easy to do and didn't take too long.
hong90 said:
I just got my TF700 last week and I wanted cleanrom on it and this is the order of stuff I did:
1. Unlocked bootloader
2. Nvflash setup
3. Installed TWRP
4. Flashed official Asus update
5. I lost TWRP so I installed it again
6. Flashed cleanrom
Probably not the most efficient way, but it was easy to do and didn't take too long.
Click to expand...
Click to collapse
It's the most efficient way.
I have nothing to add except for the remark that NvFlash is key -- GET IT WHILE YOU STILL CAN!
I'm not even kidding here. It gives you 100% flexibility in doing whatever you wish (up- as well as downgrading, even the bootloader!) and provides a key benefit in recovering your device when that whale-sized piece of excrement hits the large ventilator running at top speed.
Thanks to everyone that has replied to my post. I have successfully rooted the tablet and unlocked the bootloader. Before I do anything else Im going to run NVflash and back it up. I have a quick question though. I have download NVFlash to my computer and extracted it. Do I need to copy it across to the tablet and then enter fastboot? I havent got an extenal sd card will it save the images to the tablet's hard drive?
Cheers
Deathwalker
i followed this video:
https://www.youtube.com/watch?v=J3ypzUaKxvo&feature=youtube_gdata_player
i watched it before i actually did it once or twice to make sure i know what to do. you don't need an external sd card. following the fastboot steps will pull the files that you need onto the internal one in a folder
Last night I used NVFlash to make backup of the tablet. A big thank you to alienedd as I followed his blog and also the guide from androidmobi team and managed to get the img files done. Is there anyway to test bar for wiping the tablet?
Now all I have left to do is install OTA RootKeeper and TWRP, back up the existing tablet and then flash a custom ROM (Im thinking cleanrom)
You don't need OTA Rootkeeper anymore because you have unlocked you're bootloader. And custom roms like Cleanrom are already pre-rooted so after flashing the cleanrom you will have root anyway.

[Q] root Verizon Razr XT912 Version: 98.72.165.XT912.Verizon.en.US

I need some help, I have been trying to root my Verizon Razr XT912 running Device Software Version: 98.72.165.XT912.Verizon.en.US with the only tool I can find to use on DROID_RAZR_Utility_Jellybean_XT912_WinMacLin
Can anyone guide me in the right direction? thanks
Did you extract tool to desktop and then open it? It will give you all the instructions you need. Make sure you have USB debugging on too.
http://www.youtube.com/watch?v=XDV_72mPt4k
http://droidrazrroot.com/droid-razr-root/how-to-upgrade-to-and-root-jelly-bean-on-droid-razr/
There are two links that might be helpful to you. Hope it helps.
I lost root upon this last Verizon upgrade to 98.72.165. I think it was 98.72.16 before this weekend's update. I am going to try and go back to the original JB (98.72.16), enable root and hopefully find some type of rootkeeper utility that will stop this craziness. I can keep you posted if this works as I don't know what else to do. I use the Tasker application and most of my tasks are not functioning.
Everything worked well. I was able to reinstall the 98.72.16 image and then I applied root. So, I am back at the point before the upgrade of the software. I have root back and just completed a full titatium backup. Now, I need to figure out what others are using to keep root enabled so when a software update is applied I do not lose root. Anyone who can suggest what they use would be helpful.
To the first person who posted, I may be able to walk you through what I did and we can then learn what others are doing to keep root together.
98.72.165.en.US version
I am rooted. Haven't changed from the Moto/Verizon JellyBean update (4.1.2) but have deleted a lot of the programs I don't like or use. When I've tried to let the 98.72.165.en install it starts, then the Droid animation goes "belly up" with a "!"
I know others with root have installed it and I wouldn't mind having the update since I do travel within Canada about once a year. But, if I can't get it to install, then how do I tell the updated I don't want this? It's getting a bit tiresome to tell the installer "Not Now" every twelve hours.
Anybody have an answer?
fredlpage said:
I am rooted. Haven't changed from the Moto/Verizon JellyBean update (4.1.2) but have deleted a lot of the programs I don't like or use. When I've tried to let the 98.72.165.en install it starts, then the Droid animation goes "belly up" with a "!"
I know others with root have installed it and I wouldn't mind having the update since I do travel within Canada about once a year. But, if I can't get it to install, then how do I tell the updated I don't want this? It's getting a bit tiresome to tell the installer "Not Now" every twelve hours.
Click to expand...
Click to collapse
mwyarm said:
Everything worked well. I was able to reinstall the 98.72.16 image and then I applied root. So, I am back at the point before the upgrade of the software. I have root back and just completed a full titatium backup. Now, I need to figure out what others are using to keep root enabled so when a software update is applied I do not lose root. Anyone who can suggest what they use would be helpful.
To the first person who posted, I may be able to walk you through what I did and we can then learn what others are doing to keep root together.
Click to expand...
Click to collapse
How did you go back to 98.72.16?
Can you show me the steps please?
I was able to successfully root my phone after the update without a re-flashing or a wipe with Matt's Utility.
I followed the instruction in the link below. However, once I put the phone into BP Only mode, nothing happened. I let it sit there for about 5 minutes, then rebooted it normally and finished the exploit. It rooted the phone just fine.
http://mobility.forumsee.com/a/m/s/p12-9245-0620611--root-after-ota-165.html

How to dump/backup my own stock firmware without root (nandroid like?)

Hi Team,
Prior any play with my new G930FD I want to fully backup all firmware elements like radio, EFS, etc. to bring it back to state as it is now.
Once this is done I can play with adding root, etc.
Thought process was that it should be possible with ODIN, but I can't find a guide treating this subject.
In the past I've used to use Philz Touch on S4 LTE and all worked fine besides I've had troubles to restore NAND backups. Needed to move back from LineageOS to older CyanogenMOD (due to some issues) only to find out that old backup was not working anymore. I've tested backup earlier but it was years ago and didn't re-test procedure anymore.
Since don't want to run into any similar situation that can't revert to state as I'm in now, thought will asks you experts here.
In the past I'd think about process of booting recovery from computer via fastboot, performing required backup to SD card and them doing whatever I'd need to do.
Checking all guides (and believe me I've spent plenty of time trying to find it) all I was finding was that it required root to perform dump, i.e. using su with dd.
I've no issue to type in terminal as used to patch kernel back in times of kernel v2.4.
I just want to make sure that throughout the process of getting root, I'll have always a roll-back procedure and don't want to trip Knox and other flags, whilst if possible keeping OTA access (based on guides here, this should be possible).
Please advise on steps I should take to backup all current data with any tool or point me to place I've missed as I'm sure someone has described it already and I'm just being blind.
Thanks in advance!
dkadds2 said:
Hi Team,
Prior any play with my new G930FD I want to fully backup all firmware elements like radio, EFS, etc. to bring it back to state as it is now.
Once this is done I can play with adding root, etc.
Thought process was that it should be possible with ODIN, but I can't find a guide treating this subject.
In the past I've used to use Philz Touch on S4 LTE and all worked fine besides I've had troubles to restore NAND backups. Needed to move back from LineageOS to older CyanogenMOD (due to some issues) only to find out that old backup was not working anymore. I've tested backup earlier but it was years ago and didn't re-test procedure anymore.
Since don't want to run into any similar situation that can't revert to state as I'm in now, thought will asks you experts here.
In the past I'd think about process of booting recovery from computer via fastboot, performing required backup to SD card and them doing whatever I'd need to do.
Checking all guides (and believe me I've spent plenty of time trying to find it) all I was finding was that it required root to perform dump, i.e. using su with dd.
I've no issue to type in terminal as used to patch kernel back in times of kernel v2.4.
I just want to make sure that throughout the process of getting root, I'll have always a roll-back procedure and don't want to trip Knox and other flags, whilst if possible keeping OTA access (based on guides here, this should be possible).
Please advise on steps I should take to backup all current data with any tool or point me to place I've missed as I'm sure someone has described it already and I'm just being blind.
Thanks in advance!
Click to expand...
Click to collapse
There's a method to do that but I'm afraid it's not for our phone, because you see for the devices that can install twrp with fastboot command you can make a command that only boots twrp "fastboot boot recovery" or something like that, I don't remember clearly,instead of "fastboot flash xxxx" but we can't flash twrp with fastboot so that's impossible for us I think, I strongly advise you not to try these methods because you might end up bricking your device, if you are afraid you might mess up your phone stay away from the root and flashing, AFAIK there's no other method than the one with Odin and formatting data.
Thanks for answer, hoped I was just missing something.
Might be interesting for some people, and in fact for myself too.
I've found out that baseband version I've is not listed at Sammobile:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930FD/
It is:
G930FXXU1DQEJ
Not sure how to proceed should I run into issues?
I do also consider downgrading back to Marshmallow to take advantage of Xposed.
btw. it was all so easy, nice and sweet back in times of my S4 LTE play and now it is all so complicated, that even encryption with root seems to be so, so dangerous. :-S
dkadds2 said:
Hi Team,
Thanks in advance!
Click to expand...
Click to collapse
Maybe this one https://forum.xda-developers.com/android/software-hacking/tool-twrp-backup-restore-tool-pc-t3572241 or https://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Long time ago... though forgot to make sure I say thank you! I've had laptop OS level issues and missed to say that. Sorry.

Categories

Resources