Hi,
My phone suddenly locked up on me and stuck with following message:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 03:17:13)
eMMC Info: Size 32GB
Device is Locked, Status Code: 0
Battery OK
Connect USB
Data Cable
Load Kernel (boot) failed
Fastboot Reason: Boot Failure
I never rooted or flashed the phone or changed anything beyond stock version or OTA provided by Verizon. Tried the different options to reboot, or do factory reset, but keeps coming back to same screen. When trying Recovery option, I get the android picture with the triangle, but then pressing Volume Up and Down buttons at the same time does not do anything.
I am mainly interested in knowing if there is any way/hope to recover any of the pictures/videos that I have stored on the phone. As a secondary item, I am looking for any way to recover/restore the phone to operational condition. While searching for this online, I came across this forum. Any help you can provide is greatly appreciated!
Thanks!
Did you happen to set the storage location for your camera to "SD Card"?, because if you did, then just remove the SD Card and use a SD card reader to copy your pics to your PC.
As far as the phone goes, all I can suggest is to use RSDLite to flash the stock firmware while in AP Fastboot mode. Here is a link to RSDLite: http://rsdlite.com/rsd-lite-download/.
Here is a link to the XT926 (Droid RAZR HD) 183.46.15 firmware :http://www.mediafire.com/download/qwgk70yqf38ss86/VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml.zip. This will not wipe your phone, (At least it has not wiped my data as I have used it multiple times).
Before you use RSDLite, make sure you have all the drivers for your phone on your PC and while your phone is in AP Fastboot mode, plug it into your PC and let it load the driver. Let us know if you need any further help
Guapo613 said:
Did you happen to set the storage location for your camera to "SD Card"?, because if you did, then just remove the SD Card and use a SD card reader to copy your pics to your PC.
As far as the phone goes, all I can suggest is to use RSDLite to flash the stock firmware while in AP Fastboot mode. Here is a link to RSDLite:
Here is a link to the XT926 (Droid RAZR HD) 183.46.15 firmware :
This will not wipe your phone, (At least it has not wiped my data as I have used it multiple times).
Before you use RSDLite, make sure you have all the drivers for your phone on your PC and while your phone is in AP Fastboot mode, plug it into your PC and let it load the driver. Let us know if you need any further help
Click to expand...
Click to collapse
Guapo613,
Thank you very much for the quick reply. As far as memory card, unfortunately it was already full a long time ago, so practically all the pictures and videos I am talking about are on the internal storage of the phone (not the external card).
As far as restoring using RSDLite, are you indicating that this would maintain my data (pictures and videos) and only affect the boot partition? It seems all other methods I came across by searching were indicating that those methods would wipe out my data. It's great if this will help me restore the phone and not affect the data.
Note, the data on the phone is automatically encrypted, so hopefully this method will still maintain the information and allow me to use the same password for access afterwards?
As far as the firmware you pointed me to, is it the same for my phone? i.e., no difference between the Droid Razr HD and the Droid Razr Maxx HD?
Regarding your guidance to ensure all the drivers for my phone are on my PC, can you clarify how I can make sure of that? When I plug in my phone in the current state, it does not seems to be recognized by the PC and nothing is getting downloaded in the form of drivers.
Thanks!
NewVerizon said:
Guapo613,
Thank you very much for the quick reply. As far as memory card, unfortunately it was already full a long time ago, so practically all the pictures and videos I am talking about are on the internal storage of the phone (not the external card).
As far as restoring using RSDLite, are you indicating that this would maintain my data (pictures and videos) and only affect the boot partition? It seems all other methods I came across by searching were indicating that those methods would wipe out my data. It's great if this will help me restore the phone and not affect the data.
Note, the data on the phone is automatically encrypted, so hopefully this method will still maintain the information and allow me to use the same password for access afterwards?
As far as the firmware you pointed me to, is it the same for my phone? i.e., no difference between the Droid Razr HD and the Droid Razr Maxx HD?
Regarding your guidance to ensure all the drivers for my phone are on my PC, can you clarify how I can make sure of that? When I plug in my phone in the current state, it does not seems to be recognized by the PC and nothing is getting downloaded in the form of drivers.
Thanks!
Click to expand...
Click to collapse
rsd by default will wipe your data but for you that no longer matters because you said you factory reset and that erases data i recommend following this guide from @SamuriHL http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083
for your questions the razr maxx hd and razr hd are the same just different batterys and storage sizes
get Motorola drivers from here https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
The XML in the download I provided supposedly has been modified NOT to wipe data and in the times I have used it, it has not. I cant guarantee it will save your data but it has worked for me on both my RAZR HD and my RAZR HD MAXX.
billycar11 said:
rsd by default will wipe your data but for you that no longer matters because you said you factory reset and that erases data i recommend following this guide from @SamuriHL http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083
for your questions the razr maxx hd and razr hd are the same just different batterys and storage sizes
get Motorola drivers from here https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Click to expand...
Click to collapse
Sorry if I wasn't very clear enough on the factory reset. I mentioned that I tried that option after the Recovery option didn't work, and I know that would typically wipe off the data. However, when I chose it, it very quickly came back to the same boot fail screen, so I don't believe it actually did anything (including deleting any data). Given this information, and if assumption is that data was not wiped off and factory reset did not actually take place, is RSD still the best option, and will it still wipe off all my data? Is there any option I can try that may keep my data while just restoring the boot partition or clearing other areas such as cache (but not touching non-volatile data storage)?
Guapo613 said:
The XML in the download I provided supposedly has been modified NOT to wipe data and in the times I have used it, it has not. I cant guarantee it will save your data but it has worked for me on both my RAZR HD and my RAZR HD MAXX.
Click to expand...
Click to collapse
still does not matter anymore op says he factory reset phone already that wiped data he seems new so i linked to @SamuriHL 's guide so he knows how to do it he can still use your images if he wants
---------- Post added at 02:28 AM ---------- Previous post was at 02:24 AM ----------
NewVerizon said:
Sorry if I wasn't very clear enough on the factory reset. I mentioned that I tried that option after the Recovery option didn't work, and I know that would typically wipe off the data. However, when I chose it, it very quickly came back to the same boot fail screen, so I don't believe it actually did anything (including deleting any data). Given this information, and if assumption is that data was not wiped off and factory reset did not actually take place, is RSD still the best option, and will it still wipe off all my data? Is there any option I can try that may keep my data while just restoring the boot partition or clearing other areas such as cache (but not touching non-volatile data storage)?
Click to expand...
Click to collapse
so then yes try rsd with keeping data use whatever method of keeping data you wish use @SamuriHL method or the predone way from @Guapo613
billycar11 said:
still does not matter anymore op says he factory reset phone already that wiped data he seems new so i linked to @SamuriHL 's guide so he knows how to do it he can still use your images if he wants
---------- Post added at 02:28 AM ---------- Previous post was at 02:24 AM ----------
so then yes try rsd with keeping data use whatever method of keeping data you wish use @SamuriHL method or the predone way from @Guapo613
Click to expand...
Click to collapse
Great, thanks! You are right, I am new and not familiar with any of this so details are very helpful. I appreciate the help and patience that Guapo613 and you are providing. Hopefully I'll be able to get this restored, especially the data (mostly pictures/videos of first baby).
Verizon is your carrier?, did you use Verizon Cloud or Google Drive to back up your phone??, because if you did, then your pics are stored in either or both clouds.
Guapo613 said:
Verizon is your carrier?, did you use Verizon Cloud or Google Drive to back up your phone??, because if you did, then your pics are stored in either or both clouds.
Click to expand...
Click to collapse
Verizon is my carrier, but unfortunately I do not have most of the pictures/videos on Verizon Cloud or Google Drive. I copied a handful of them to Google Drive when I wanted to share them, but majority of them (95%) are unfortunately not backed up...
BTW, I have one more question. When I looked at the other link that was posted by SamuriHL, it had a warning "IF YOU HAVE NOT UNLOCKED, THIS BUILD WILL PERMANENTLY PREVENT YOU FROM DOING SO. STOP NOW and GO UNLOCK!". Does the same thing hold for the XML you suggested? Should I be doing something else to unlock first, or should I just proceed with rsdlite and your XML?
NewVerizon said:
Verizon is my carrier, but unfortunately I do not have most of the pictures/videos on Verizon Cloud or Google Drive. I copied a handful of them to Google Drive when I wanted to share them, but majority of them (95%) are unfortunately not backed up...
BTW, I have one more question. When I looked at the other link that was posted by SamuriHL, it had a warning "IF YOU HAVE NOT UNLOCKED, THIS BUILD WILL PERMANENTLY PREVENT YOU FROM DOING SO. STOP NOW and GO UNLOCK!". Does the same thing hold for the XML you suggested? Should I be doing something else to unlock first, or should I just proceed with rsdlite and your XML?
Click to expand...
Click to collapse
i believe you were already on the latest ota/update so you cant unlock that is only for custom roms and rooting and it seems like thats not something you want to do anyway,
just be sure to check the xml file and make sure "erase userdata" is gone from the xml that way you have the best chance of recovering your data
NewVerizon said:
Verizon is my carrier, but unfortunately I do not have most of the pictures/videos on Verizon Cloud or Google Drive. I copied a handful of them to Google Drive when I wanted to share them, but majority of them (95%) are unfortunately not backed up...
BTW, I have one more question. When I looked at the other link that was posted by SamuriHL, it had a warning "IF YOU HAVE NOT UNLOCKED, THIS BUILD WILL PERMANENTLY PREVENT YOU FROM DOING SO. STOP NOW and GO UNLOCK!". Does the same thing hold for the XML you suggested? Should I be doing something else to unlock first, or should I just proceed with rsdlite and your XML?
Click to expand...
Click to collapse
I'm going to assume that your XT926 was updated to the latest firmware available for your phone (183.46.15). If that was the case, then dont worry about un-locking the bootloader as this option is not currently supported by your updated phone.
Once you get this thing working again, you can root your phone, read this: http://forum.xda-developers.com/droid-razr-hd/general/root-droid-razr-hd-xt926-183-46-15-t3062040
billycar11 said:
i believe you were already on the latest ota/update so you cant unlock that is only for custom roms and rooting and it seems like thats not something you want to do anyway,
just be sure to check the xml file and make sure "erase userdata" is gone from the xml that way you have the best chance of recovering your data
Click to expand...
Click to collapse
Sounds good. I downloaded and unzipped the RSD Lite (from SamuriHL link, since the original link seems to fail to download 6.1.6 and only works for older versions such as 6.1.5). Currently, I am in the process of downloading the XML (1/3 done, it's pretty big at 753MB). When it's done, am I supposed to unzip it, and then look inside for the modification? How can I tell if "erase userdata" is gone from the xml? I assume RSD Lite is going to expect the XML as an input, or can it take the zip file?
BTW, when I plugged the phone to the data cable, it looks like the battery was run down. It took a little while, but then it came back up to the boot fail screen but indicates Battery Low. Do I need to charge the phone and wait till Battery OK before starting the process?
Guapo613 said:
I'm going to assume that your XT926 was updated to the latest firmware available for your phone (183.46.15). If that was the case, then dont worry about un-locking the bootloader as this option is not currently supported by your updated phone.
Once you get this thing working again, you can root your phone, read this: http://forum.xda-developers.com/droid-razr-hd/general/root-droid-razr-hd-xt926-183-46-15-t3062040
Click to expand...
Click to collapse
Sounds good, thanks for the additional clarifications!
NewVerizon said:
Sounds good. I downloaded and unzipped the RSD Lite (from SamuriHL link, since the original link seems to fail to download 6.1.6 and only works for older versions such as 6.1.5). Currently, I am in the process of downloading the XML (1/3 done, it's pretty big at 753MB). When it's done, am I supposed to unzip it, and then look inside for the modification? How can I tell if "erase userdata" is gone from the xml? I assume RSD Lite is going to expect the XML as an input, or can it take the zip file?
BTW, when I plugged the phone to the data cable, it looks like the battery was run down. It took a little while, but then it came back up to the boot fail screen but indicates Battery Low. Do I need to charge the phone and wait till Battery OK before starting the process?
Click to expand...
Click to collapse
yes you will unzip the file then find and open the xml file and delete the whole line that contains "erase userdata" also erase any lines that contain TZ and yes the xml is the input for rsd,
im not 100% sure if the battery will charge with no boot.img i don't think it will and in order to flash you need that low battery warning to be gone so check if it will charge and if not you will need to make or buy a Motorola factory cable.
NewVerizon said:
Sounds good. I downloaded and unzipped the RSD Lite (from SamuriHL link, since the original link seems to fail to download 6.1.6 and only works for older versions such as 6.1.5). Currently, I am in the process of downloading the XML (1/3 done, it's pretty big at 753MB). When it's done, am I supposed to unzip it, and then look inside for the modification? How can I tell if "erase userdata" is gone from the xml? I assume RSD Lite is going to expect the XML as an input, or can it take the zip file?
BTW, when I plugged the phone to the data cable, it looks like the battery was run down. It took a little while, but then it came back up to the boot fail screen but indicates Battery Low. Do I need to charge the phone and wait till Battery OK before starting the process?
Click to expand...
Click to collapse
Charge the battery to at least 70% before starting the process.
What I like to do is create a folder on your desktop and name it "RAZR HD" (or RAZR MAXX HD) and place the .zip file I provided in that folder, now just un-zip it inside that folder and when you open RSDLite, just navigate to the folder you created on your desktop and click on the XML document and click on "Start" and RSDlite will take care of the rest
Guapo613 said:
Charge the battery to at least 70% before starting the process.
What I like to do is create a folder on your desktop and name it "RAZR HD" (or RAZR MAXX HD) and place the .zip file I provided in that folder, now just un-zip it inside that folder and when you open RSDLite, just navigate to the folder you created on your desktop and click on the XML document and click on "Start" and RSDlite will take care of the rest
Click to expand...
Click to collapse
Hi Guapo613,
Sorry for the delayed response. I was away at a conference out of town, and just got back home where I have access to a Motorola charger. It is the travel one, so unclear if it is charging or not. The phone seems to be in a state in which it indicates Battery Low, and then after plugging back with power and back directly to the computer, it indicates Battery OK (switches back and forth during subsequent reconnect).
I got it to Battery OK indication, then extracted the files from the zip as you suggested and started RSDLite with the XML. However, it failed almost immediately. It shows the following output on the first two lines (all subsequent lines are blank other than Port No):
Model Port No. Port Type IMEI/ESN/MEID Status Result
1 USB The phone failed to switch to fastboot mode. FAIL
Fastboot VANQUISH S 2 USB N/A Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone returned FAIL. FAIL
Any ideas?
Thanks!
billycar11 said:
yes you will unzip the file then find and open the xml file and delete the whole line that contains "erase userdata" also erase any lines that contain TZ and yes the xml is the input for rsd,
im not 100% sure if the battery will charge with no boot.img i don't think it will and in order to flash you need that low battery warning to be gone so check if it will charge and if not you will need to make or buy a Motorola factory cable.
Click to expand...
Click to collapse
Hi billycar11,
As I mentioned in the post I just wrote to Guapo613, I tried using the xml he provided with RSDLite, but it did not work. Also, when looking at the XML, I did not see any line containing "erase userdata", so I guess that's a good thing (i.e. it was already done in that XML). I did not see any lines containing TZ, but I don't believe I saw any lines indicating that the XML is the input for rsd or where I would change anything to yes. My assumption was that the file is already good as-is since Guapo613 indicated he used it multple times before, so hopefully the changes you noted are not needed.
However, that process did not work, so I am not sure if it means the phone is in a worse state than thought, or maybe it has something to do with the battery and needing the stock (non-travel) charger. Maybe the phone will just not charge without boot.img, but as I noted in the other post, I did manage to get the Battery indication to OK rather than Low (regardless whether there is actually any charge in it or not).
One other note, before it allowed me to at least get to the menu in which I could navigate between options such as Recovery or Factory Reset (even though none of them actually accomplished anything), but now it seems even that is not possible (it doesn't get there when I press Volume Up, Down, and Power).
----> I take this last statement back. After disconnecting and then trying again, it looks like it is still possible to reach that first menu. However, end result is still the same, with Recovery no being able to get past the icon of Android on its back with triangle, and subsequent reboot (requiring down volume and power) getting back to the screen indicating boot fail.
Do you have any ideas on what I should try next?
Thanks!
Are you able to boot into AP Fastboot??
Guapo613 said:
Are you able to boot into AP Fastboot??
Click to expand...
Click to collapse
Can you clarify what you mean by this?
The screen I keep getting back to indicates at the top "AP Fastboot Flash Mode (S)".
Is there anything specific you would like me to try to get into AP Fastboot?
Related
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!
Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.
tobdaryl said:
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!
Click to expand...
Click to collapse
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
flumpster said:
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.
Click to expand...
Click to collapse
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD
Rojikku said:
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD
Click to expand...
Click to collapse
The twrp mentioned above can be found here.
tobdaryl said:
The twrp mentioned above can be found here.[/URL]
Click to expand...
Click to collapse
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.
Rojikku said:
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.
Click to expand...
Click to collapse
Wrong twrp! You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off stock 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Unless the rom you flash is also for 4.2 bootloader. Both are located at teamwin.
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock.
As far as flashing a new rom look at the op and determine if it is for the new stock 4.2 bootloader. If not do not flash over 4.2 but downgrade first. I have upgraded from 10.4.2.20 to stock 4.2 and downgraded from stock 4.2 to 10.4.2.20 several times without issue.
Stock 4.2 includes an assert to only allow upgrade from 10.4.2.20.
tobdaryl said:
Wrong twrp! [/URL]You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Both are located at teamwin.[/URL]
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock and hold a minute or you are going right back where you were or worse. You need slightly more info before going forward and I need to check my notes while you get the proper twrp flashed.
Click to expand...
Click to collapse
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.
Rojikku said:
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.
Click to expand...
Click to collapse
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.
tobdaryl said:
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.
Click to expand...
Click to collapse
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.
Rojikku said:
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.
Click to expand...
Click to collapse
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?
tobdaryl said:
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?
Click to expand...
Click to collapse
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?
I decided to take the risk and reboot it. Everything fine. I flashed the tool, ran the reboot command(Which actually didn't work... >>; But I rebooted it manually and it seems fine...)
On that note, is it actually possible to destroy a device beyond repair accidentally? And the TWRP tool said it flashed fine but I still have the old version. Odd....
I do have the image you said currently installed, I checked the version against my download.
Rojikku said:
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?
Click to expand...
Click to collapse
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.
tobdaryl said:
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.
Click to expand...
Click to collapse
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?
Rojikku said:
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?
Click to expand...
Click to collapse
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.
tobdaryl said:
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.
Click to expand...
Click to collapse
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.
Rojikku said:
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.
Click to expand...
Click to collapse
When it asks for the password hit cancel and just ignore the error.
tobdaryl said:
When it asks for the password hit cancel and just ignore the error.
Click to expand...
Click to collapse
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)
Rojikku said:
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)
Click to expand...
Click to collapse
Thanks for the link. I looked at the info provided for that rom. You don't want to flash that over an encrypted tablet which you now have. The only safe way I have found to go to or from stock 4.2 rom is with stock 10.4.2.20.
To do that you would flash 10.4.2.20 with twrp, boot into os, reboot back to the bootloader which will now be four icons, select usb, use fastboot to flash twrp again, and now flash your new rom.
This sounds long but removes encryption from your tablet and you should be able to flash the jb rom of choice that does not require stock 4.2 bootloader.
Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.
ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
You've got a few options...forgive me if you've tried any of these already...I'm just offering ideas for you to find one that works for you...
1) restore a nandroid backup if you have one
or
2) ADB sideload a zip for one of the roms in the development sections
or
3) ADB push then flash a zip from the development sections
or
4) Flash the factory images using fastboot
DaMonster said:
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
Click to expand...
Click to collapse
Download this ROM (Odex)
http://forum.xda-developers.com/showthread.php?t=2507861
Boot in TWRP, and either use adb sideload:
./adb sideload path_to_hammerhead_KRT16M_odex_signed.zip
or use adb push
./adb push path_to_hammerhead_KRT16M_odex_signed.zip /data/media/0
Then proceed with flashing it from recovery.
Yep, you have plenty of options so don't panic. Personally, I'd use this as an opportunity to teach yourself how to setup and use ADB and Fastboot commands to flash factory images. Once you teach yourself how to do this properly you will no longer get overly concerned when another situation like this inevitably occurs. This will be a learning experience that you will benefit from later on.
If you are on a Mac, follow THIS GUIDE to properly setup ADB/Fastboot for use. Then use THIS GUIDE to learn how to properly flash a factory image.
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
DaMonster said:
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
Click to expand...
Click to collapse
A few things:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
hotleadsingerguy said:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
Click to expand...
Click to collapse
Good point. I'll reflash to the openrecovery-twrp-xxx version shortly anyway, but the point is valid and I'll make sure to have an official image and regular NANDROID backups handy for future experiments
hotleadsingerguy said:
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
Click to expand...
Click to collapse
None taken. I'm not really young, just new to Android/ tinkering. In any case, blowing $400 on a device is still a big deal and I want to avoid that like a plague Alas, youth has no monopoly on stupid.
zerogun said:
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
Click to expand...
Click to collapse
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
DaMonster said:
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
Click to expand...
Click to collapse
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
J_Dutch said:
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
Click to expand...
Click to collapse
Use "adb push" to copy a zip from your PC to your phone.
The command would be like this:
adb push path/to/zip data/media/0
same issue
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
minerva330 said:
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
Click to expand...
Click to collapse
Just restore a nandroid in twrp
still a noob
jd1639 said:
Just restore a nandroid in twrp
Click to expand...
Click to collapse
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
minerva330 said:
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
Click to expand...
Click to collapse
I wouldn't worry about backing up at this point
still a noob
jd1639 said:
I wouldn't worry about backing up at this point
Click to expand...
Click to collapse
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
minerva330 said:
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
Click to expand...
Click to collapse
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
truly ashamed
jd1639 said:
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
Click to expand...
Click to collapse
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
minerva330 said:
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
Click to expand...
Click to collapse
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
jd1639 said:
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
Click to expand...
Click to collapse
How can I unzip a file from the factory image on my phone if it is on desktop? Am I missing something (thanks for tolerating this)?
At this point I could care less about loosing any apps, data, or pics,
I knew this day would come, I've traded PC trouble shooting for tablet troubleshooting. My son's tf300 gets to the screen where circles/dots go round and round and never gets any further. I am trying to learn everything I can and try everything I can before doing the wipe and starting over...as he has pictures and videos he'd like to save, and of course the all important saved game/app data...LOL. Anyway I'm new to tablets relatively speaking, but I've tried the volume down, and power button for doing a cold boot, same result. I've tried going to the recovery option just to see what that was about, and all I get is a flash of a screen saying something like updating android version or something like that and then the dead android with the usual red triangle and eventually the device will restart itself. I should that to him and told him he killed the android which gave me a puzzled look and then a smile...Anyway, you can't turn off the device nohow noway, except letting the battery drain completely.
I've been reading a little and learning about roots, backups, recoveries, etc... trying to come up with a plan of attack but feel like I'm spinning my wheels. Any advice here? and Can I access via PC to USB to device and just pull off his pics and videos to copy back over to the device after a wipe?
Problem started...I think when he ran the power dead completely and then had to restart...nor sure though... memories of a child are sketchy at best.
Feedback
chromegsx said:
I knew this day would come, I've traded PC trouble shooting for tablet troubleshooting. My son's tf300 gets to the screen where circles/dots go round and round and never gets any further. I am trying to learn everything I can and try everything I can before doing the wipe and starting over...as he has pictures and videos he'd like to save, and of course the all important saved game/app data...LOL. Anyway I'm new to tablets relatively speaking, but I've tried the volume down, and power button for doing a cold boot, same result. I've tried going to the recovery option just to see what that was about, and all I get is a flash of a screen saying something like updating android version or something like that and then the dead android with the usual red triangle and eventually the device will restart itself. I should that to him and told him he killed the android which gave me a puzzled look and then a smile...Anyway, you can't turn off the device nohow noway, except letting the battery drain completely.
I've been reading a little and learning about roots, backups, recoveries, etc... trying to come up with a plan of attack but feel like I'm spinning my wheels. Any advice here? and Can I access via PC to USB to device and just pull off his pics and videos to copy back over to the device after a wipe?
Problem started...I think when he ran the power dead completely and then had to restart...nor sure though... memories of a child are sketchy at best.
Click to expand...
Click to collapse
I have a solution, but your not going to like it, all data will be lost....:crying:
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700 and TF300: EP201_768_SDUPDATE.zip
B. For the TF101: E101_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Let me know if you need any help along the way.... Thx as always lj
lj50036 said:
I have a solution, but your not going to like it, all data will be lost....:crying:
...
Let me know if you need any help along the way.... Thx as always lj
Click to expand...
Click to collapse
So the RCK thing doesn't do anything unless you have SD card in to do something that's on the card?
And there's no way to access what's on the device without getting it booted all the way?
Sounds like your saving me and my son from updating from his original Android version after a wipe...Thanks
SKU
chromegsx said:
So the RCK thing doesn't do anything unless you have SD card in to do something that's on the card?
And there's no way to access what's on the device without getting it booted all the way?
Sounds like your saving me and my son from updating from his original Android version after a wipe...Thanks
Click to expand...
Click to collapse
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....
lj50036 said:
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....
Click to expand...
Click to collapse
Hey congrats on Recognized Contributor!
Happy
cmendonc2 said:
Hey congrats on Recognized Contributor!
Click to expand...
Click to collapse
I am happy about it.. Still so much to learn... Im not trying to let it go to my head...LOL:silly:
lj50036 said:
... NEVER select the WIPE DATA.. Bad things will happen...
Click to expand...
Click to collapse
As far as I know it's related only to custom recovery and if You have stock one it should work. Or I'm wrong?
Data Wipe
Graiden05 said:
As far as I know it's related only to custom recovery and if You have stock one it should work. Or I'm wrong?
Click to expand...
Click to collapse
Yes that is correct. I just like to move people away from even thinking its an option, as I have had people with stock everything and the Wipe Data
icon has even given them trouble, its just not worth touching....LOL...Thx as always lj
lj50036 said:
Yes that is correct. I just like to move people away from even thinking its an option, as I have had people with stock everything and the Wipe Data
icon has even given them trouble, its just not worth touching....LOL...Thx as always lj
Click to expand...
Click to collapse
Yep when I first got my tablet i was so scared about going into that menu because I learned that it was only 3-4 clicks away from a brick.
lj50036 said:
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....
Click to expand...
Click to collapse
Out of curiousity...Isn't doing these steps more or less just upgrading the firmware? Like getting an update from ASUS? If so, why will it lose all the data?
I haven't mustered up the courage yet to do this yet... actually it's more like getting the time to do it.
Feedback
chromegsx said:
Out of curiousity...Isn't doing these steps more or less just upgrading the firmware? Like getting an update from ASUS? If so, why will it lose all the data?
I haven't mustered up the courage yet to do this yet... actually it's more like getting the time to do it.
Click to expand...
Click to collapse
Yes, that is correct..but its not a ota.... So the process will wipe all data....Thx always lj
You could try using ADB to try and pull your files. I faced a similar problem and was able to pull some of my files:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
UndisputedGuy said:
You could try using ADB to try and pull your files. I faced a similar problem and was able to pull some of my files:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.
chromegsx said:
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.
Click to expand...
Click to collapse
Try installing the universal naked drivers.
cmendonc2 said:
Try installing the universal naked drivers.
Click to expand...
Click to collapse
Same result. Still nothing in Device manager.
chromegsx said:
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.
Click to expand...
Click to collapse
Apologies, I'm very rusty with this stuff now. If flashing a .blob file doesn't wipe data (I can't remember whether it does or not), perhaps you could try doing that if you're able to get into recovery?
Call me, Beep me, If you wanna reach me.
UndisputedGuy said:
Apologies, I'm very rusty with this stuff now. If flashing a .blob file doesn't wipe data (I can't remember whether it does or not), perhaps you could try doing that if you're able to get into recovery?
Call me, Beep me, If you wanna reach me.
Click to expand...
Click to collapse
I just gave in and did the flash procedure. Looked like it went well, now I'm watching the circles for round again for the last 10 minutes.
chromegsx said:
I just gave in and did the flash procedure. Looked like it went well, now I'm watching the circles for round again for the last 10 minutes.
Click to expand...
Click to collapse
Just wanted to follow up on this...lj50036 is top noctch helper here. going above and beyond does not even come close to explaining what he has tried to do for me. Ultimately it was after we hit a brick wall, that I suggested flashing back to an earlier version that finally worked. I'm not convinced flashing to the latest version (like I first tried) would not work, as I didn't personally create/rename the SD card to do the flash. but re-flashing the original firmware got the tablet to boot finally. Of course all was lost other than what had been automatically backed up via google servers. Pictures/videos back to exactly one year from when the pad stopped booting were recovered. Everything before a year was gone. No game data or installs were saved. I thought maybe it had to do with a space issue, but after re-installing every app my son had before and about 1GB worth of pics/videos restored, there is still 16GB left, I doubt game/user data would have consumed that much...so I still have no idea what might have cause the pad to stop booting. Other than it was trying to do something important when he ran the battery dead. So at this point I'm having my son clean out unwanted apps, and we are going to unlock and root after a proper backup is done. Thank you to all that have had input on my dilemma. I've learned a ton.
Hey all! My friend has an s3. He is in a different state so I can't experiment on it quite yet.
He has a lot of files he needs to recover from the internal storage. He already has the sd data.
The issue is that the phone will not fully boot. It gets a little past the verizon logo and crashes.
He has tried wiping cache, and booting without the sdcard in.
What can we do to get those files for him?
Verizon said they can't use their diag machine since the device needs to fully power on for them to service it in that fashion.
Is it possible to flash the stock system partition without overwriting data via Odin?
Bump
tr4nqui1i7y said:
Hey all! My friend has an s3. He is in a different state so I can't experiment on it quite yet.
He has a lot of files he needs to recover from the internal storage. He already has the sd data.
The issue is that the phone will not fully boot. It gets a little past the verizon logo and crashes.
He has tried wiping cache, and booting without the sdcard in.
What can we do to get those files for him?
Verizon said they can't use their diag machine since the device needs to fully power on for them to service it in that fashion.
Click to expand...
Click to collapse
tr4nqui1i7y said:
Is it possible to flash the stock system partition without overwriting data via Odin?
Click to expand...
Click to collapse
Really kind of a tough situation.
Can he get into recovery mode? If so maybe he can pull data from it that way. There's a few ways to do it. It's hard to tell unless I see what the phone does when it boots.
Sorry for the late reply, hardly ever check these forums anymore.
BadUsername said:
Really kind of a tough situation.
Can he get into recovery mode? If so maybe he can pull data from it that way. There's a few ways to do it. It's hard to tell unless I see what the phone does when it boots.
Sorry for the late reply, hardly ever check these forums anymore.
Click to expand...
Click to collapse
I know he can get to stock recovery, because he's wiped cache that way. I don't believe that he is rooted or anything. I won't know for sure until I'm in person. The issue is that he thinks Verizon wants him to send the phone to them. He used a free upgrade. They sent him the replacement phone with a return box, so he's still not sure at the moment. And I haven't used an upgrade in about 4 years so I don't remember ever having to give back a device.
tr4nqui1i7y said:
I know he can get to stock recovery, because he's wiped cache that way. I don't believe that he is rooted or anything. I won't know for sure until I'm in person. The issue is that he thinks Verizon wants him to send the phone to them. He used a free upgrade. They sent him the replacement phone with a return box, so he's still not sure at the moment. And I haven't used an upgrade in about 4 years so I don't remember ever having to give back a device.
Click to expand...
Click to collapse
If he has USB debugging enabled be can use ADB to pull the SD card folder onto his computer in recovery mode.
Otherwise can't do much with stock recovery, if he's rooted you may be able to load TWRP from download mode and boot immediately into recovery mode.
BadUsername said:
If he has USB debugging enabled be can use ADB to pull the SD card folder onto his computer in recovery mode.
Otherwise can't do much with stock recovery, if he's rooted you may be able to load TWRP from download mode and boot immediately into recovery mode.
Click to expand...
Click to collapse
He's got the SD data. We're working on the /data/ partition now. I think it's mainly notes and pics if I'm not mistaken. I'm really hoping that he's rooted and just forgot or something.
We can make it into odin mode.
You don't need root.
Sent from my Nexus 6 using XDA-Developers Legacy app
---------- Post added at 06:00 AM ---------- Previous post was at 05:59 AM ----------
I can probably help you out.
Sent from my Nexus 6 using XDA-Developers Legacy app
whodisname said:
You don't need root.
Sent from my Nexus 6 using XDA-Developers Legacy app
---------- Post added at 06:00 AM ---------- Previous post was at 05:59 AM ----------
I can probably help you out.
Click to expand...
Click to collapse
I'm thinking of trying to flash stock via Odin to see if that will make it boot. Otherwise, it may have to go jtag route.
I am going to attempt to ODIN on it. Unfortunately I don't know what version of android he was on.
Which ODIN files would you recommend? Preferably one that won't need me to wipe the data partition. Also, please provide links if possible. I have found some stuff on my own, but a lot of links are dead.
tr4nqui1i7y said:
I am going to attempt to ODIN on it. Unfortunately I don't know what version of android he was on.
Which ODIN files would you recommend? Preferably one that won't need me to wipe the data partition. Also, please provide links if possible. I have found some stuff on my own, but a lot of links are dead.
Click to expand...
Click to collapse
Odin will wipe everything. Every .tar file I've come across essentially just return the phone to a completely stock state.
Wish I had old stuff but I don't. What have you found?
BadUsername said:
Odin will wipe everything. Every .tar file I've come across essentially just return the phone to a completely stock state.
Wish I had old stuff but I don't. What have you found?
Click to expand...
Click to collapse
Ah, I had found one that said it wasn't going to wipe data. I'll try to find the link again today. They were saying it was like doing an ota update and it would leave data in place.
tr4nqui1i7y said:
Ah, I had found one that said it wasn't going to wipe data. I'll try to find the link again today. They were saying it was like doing an ota update and it would leave data in place.
Click to expand...
Click to collapse
O wait I think I vaguely remember, but that we when the bootloader was unlocked, like 5 years ago.
Make sure you post the for here and I can try to help you, but if it's an older version it won't. You need to make sure the Odin file is the same or newer than your current bootloader.
@BadUsername I found this, which has the crappiest hosting servers I have ever seen. You can only download one file a day, so I need to keep changing my IP if I need more than one file from it. here
This is the no-wipe file i was referring to. I am just not sure if it is an android version that his device will accept. I am not sure if Odin allows you to go forward and backward. Here
tr4nqui1i7y said:
@BadUsername I found this, which has the crappiest hosting servers I have ever seen. You can only download one file a day, so I need to keep changing my IP if I need more than one file from it. here
This is the no-wipe file i was referring to. I am just not sure if it is an android version that his device will accept. I am not sure if Odin allows you to go forward and backward. Here
Click to expand...
Click to collapse
Just open up download mode and post what it says in the top left corner.
Also that file you posted first is the newest one, assuming it's legit it would work. That would for sure wipe everything.
Bottom one is old, probably won't work. Odin should just fail and not let you flash it. If it did work, it would fail at the bootloader stage and brick your phone anyway.
BadUsername said:
O wait I think I vaguely remember, but that we when the bootloader was unlocked, like 5 years ago.
Make sure you post the for here and I can try to help you, but if it's an older version it won't. You need to make sure the Odin file is the same or newer than your current bootloader.
Click to expand...
Click to collapse
That's what I was afraid of. I have no idea how updated he kept the device. And since I can only get into stock recovery and download mode I can't learn much about the device. I wish I could just adb in and grab the data partition off of it. Verizon is hounding him to send the device back or they will charge him $500 or something absurd. Which seems extra crazy since he has had that device since it was released. I thought for sure he would own it by now. Verizon has never asked me for a device back.
Have you found any helpful odin stuff out?
BadUsername said:
Just open up download mode and post what it says in the top left corner.
Click to expand...
Click to collapse
I won't be able to see the device until tonight. I will try to see if he is around the device now so he can let me know. His house has terrible reception and no wifi so I am trying to gather everything before the next time I go there.
@BadUsername Do you know if there is a list of odin files anywhere? This sub seems so disorganized imo. I can't find a helpful sticky or anything.
tr4nqui1i7y said:
I won't be able to see the device until tonight. I will try to see if he is around the device now so he can let me know. His house has terrible reception and no wifi so I am trying to gather everything before the next time I go there.
Click to expand...
Click to collapse
You can still pull nearly everything off the phone with adb from download mode if USB debugging was enabled, you can literally pull every partition and extract what you need.
You can load a very old version of cwm recovery through Odin and flash aroma file manager if you are rooted, if you can get into recovery. Then you can move whatever you want to an external SD card.
Other than that you're likely stuck.