Database Info

With JB installed: CWM Recovery causes a hang when I try to load into it.

Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Edit: Forgot to also ask, am I just an idiot?

badfontkeming said:
Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Click to expand...
Click to collapse
I have the same issue, no fix yet.

untermensch said:
I have the same issue, no fix yet.
Click to expand...
Click to collapse
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.

I have the exact same problem so I right there with ya
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.

badfontkeming said:
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.
Click to expand...
Click to collapse
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.

EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
I've noticed the same issue, it exists with the latest TWRP flashed via fastboot as well.
The problem with flashing via the terminal is that we don't have root yet, and need a recovery to get it. Looks like the only option is to wait for a fix.

EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
Yeah... the issue is, the reason I'm trying to flash CWM is so I can get root.

krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?

sparky28000 said:
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?
Click to expand...
Click to collapse
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265

krhainos said:
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265
Click to expand...
Click to collapse
Now there is atleast 3 people since I bricked mine also

krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
just curious how are you able to get in APX mode it seems I cant even do that

Drgravy said:
just curious how are you able to get in APX mode it seems I cant even do that
Click to expand...
Click to collapse
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.

krhainos said:
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.
Click to expand...
Click to collapse
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient

Drgravy said:
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient
Click to expand...
Click to collapse
I used the reset hole in place of the power button when fiddling with button combinations. Hold down VOL+, and poke the reset hole with a paperclip and that'll get you in APX mode -- not like it does any of us any good.

I thought I had bricked mine...
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim

I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.

jdeatsch said:
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim
Click to expand...
Click to collapse
Not working for me at all...

untermensch said:
I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.
Click to expand...
Click to collapse
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
---------- Post added at 10:46 PM ---------- Previous post was at 10:40 PM ----------
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse
Weird. When I try to edit this post, I only get 3/4 of the quote and none of my actual post to edit. Anyway...
Just wanted to clarify: not asking for directions. If the file is what I think it is, I know what I'm doing. I just want to know that the file is what I think it is.

It is the Jelly Bean recovery kernel and the ClockWorkMod ramdisk repacked with mkbootimg, then blobpack,
then I added the "-SIGNED-BY-SIGNBLOB-" header with a hex editor. it seems like ADB does not work but I
was able to root with an update.zip
I installed this with fastboot and erased and re-flashed 4 time's before posting to make sure
it would not cause instant brick.
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse

[Q] TF300T RCK issues after reflashing stock ROM

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.

[Q] Stuck in a bootloop, dev ed, root, OTA

I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!

carmike692000 said:
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
Click to expand...
Click to collapse
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra

Caseyk621 said:
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Click to expand...
Click to collapse
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?

carmike692000 said:
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
Click to expand...
Click to collapse
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra

Caseyk621 said:
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Click to expand...
Click to collapse
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
EDIT - I'm sure one problem with the computer not listing the phone as a device is it cannot find the device driver to install for it, and I've not been successful googling for it. So in the Windows Device Manager list, my XT1080 has a yellow exclamation mark by it. Also, just installed TiB and froze "Motorola OTA" since I had to wait five minutes to post this edit anyways.

carmike692000 said:
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
Click to expand...
Click to collapse
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra

Caseyk621 said:
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Click to expand...
Click to collapse
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.

carmike692000 said:
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
Click to expand...
Click to collapse
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra

Caseyk621 said:
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Click to expand...
Click to collapse
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!

carmike692000 said:
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
Click to expand...
Click to collapse
Glad I could help! Don't forget to make a backup in TWRP! You may find yourself wanting to go back to stock sooner than you think! I keep trying ROMs but always end up missing active notifications and touch less as well as some others!
Sent From Droid Ultra

I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance

nubia11 said:
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
Click to expand...
Click to collapse
Flash the stock recovery with fastboot. I forget if you need to also unroot or not. Also make sure you have any apps that were disabled or frozen enabled/defrosted

[Q] How to root this device without deleting any data?

Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.

yes, of course..
root doesn't delete any of your data

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.

timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?

pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon

The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!

But how is anything going to be written to the system partition if it is locked ?

timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?

pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?

bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?

pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help

bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?

pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?

Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!

I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!

zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.

Help recovering files from an s3

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.