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] Deleted my OS!!!!!!

So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.

gmermel said:
So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.
Click to expand...
Click to collapse
You should be alright... Can you try this for me? Holding the power button and volume down at the same time.. You should see your bootloader menu whih has 3 icons... Please let me know if you can get there..:fingers-crossed:

gmermel said:
So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.
Click to expand...
Click to collapse
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post

berndblb said:
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post
Click to expand...
Click to collapse
Wow. 2 minutes and I'm getting help already.
I'm in TWRP. Where do I get the stock rom? I presume I'll download it my computer, but how do I tell the tablet to load it from there?

berndblb said:
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post
Click to expand...
Click to collapse
It is not a problem... I think that my device is running the ET so it is a little faster...:silly: Just kidding...
It would be better that you can help him/her.. I am a little busy testing new stuffs.. Thanks for the helps and talk more with you later...

LetMeKnow said:
It is not a problem... I think that my device is running the ET so it is a little faster...:silly: Just kidding...
It would be better that you can help him/her.. I am a little busy testing new stuffs.. Thanks for the helps and talk more with you later...
Click to expand...
Click to collapse
A LITTLE busy testing new stuff??? Haha! Are you doing anything but...?
---------- Post added at 10:48 PM ---------- Previous post was at 10:38 PM ----------
gmermel said:
Wow. 2 minutes and I'm getting help already.
I'm in TWRP. Where do I get the stock rom? I presume I'll download it my computer, but how do I tell the tablet to load it from there?
Click to expand...
Click to collapse
You don't. You have to copy the rom or firmware to your microSD.
Insert the card, boot into TWRP as described earlier.
Choose 'Install" and then navigate to your microSD and the zip you parked there.
Select it, swipe to flash it.
Now: I cringe, when someone on a perfectly fine and unlocked TF700 wants to flash back the Asus firmware. Ouch!
But I understand you only want to sell it and the buyer may not know how much better this tablet is on a custom ROM like CROMi-X. Sigh!
So, if you insist on flashing the latest firmware, go to the Asus support website, the download section, enter Transformer in the search box, select the TF700 and look for the 10.6.1.14.10 firmware. Make sure you select the one for your SKU, meaning US if you're on this continent (and I assume you are since you're awake at this time ), or WW or where ever you are.
Download the firmware and and on your computer, extract that zip file once - the result being another zip file.
It's that once extracted zip you want to copy to your SD, insert in your tab and flash in TWRP.
Ask if I left anything out.

Thanks. You're right, I'm in the US. But I am going to sleep. Will get on this in the AM.
You are correct to cringe. I rooted/C-romix'd a few months ago because I was frustrated by the constant lag on the tab. Figured if I bricked it, well, I wasn't happy with it anyway. I cringed when I went and did it because I knew I was taking a risk what with my capabilities. I've moved on to the Nexus 7 and just love it. Not just the performance. The small platform is just right....
Thanks for the rapid replies and the sophisticated yet understandable directions. Mostly, thanks for not calling me a knucklebrain even though I deserve it.

gmermel said:
Thanks. You're right, I'm in the US. But I am going to sleep. Will get on this in the AM.
You are correct to cringe. I rooted/C-romix'd a few months ago because I was frustrated by the constant lag on the tab. Figured if I bricked it, well, I wasn't happy with it anyway. I cringed when I went and did it because I knew I was taking a risk what with my capabilities. I've moved on to the Nexus 7 and just love it. Not just the performance. The small platform is just right....
Thanks for the rapid replies and the sophisticated yet understandable directions. Mostly, thanks for not calling me a knucklebrain even though I deserve it.
Click to expand...
Click to collapse
Not that long ago, I was exactly where you are now....:silly:

berndblb said:
Not that long ago, I was exactly where you are now....:silly:
Click to expand...
Click to collapse
Problem #1: When I opened the ROM.zip, I didn't get another zip, I got a folder with no zips in it (a blob.exe, several other .exe). When I moved that over to the SD and chose to install it TWRP returned a "failure" notification.
I'd like to get the stock ROM on for the buyer. What should I do
Problem #2: I still have CROM-X on the external card. It is installing, but which kernel should I use?
I'm going to use sbdags stock, and if you think that's a mistake I'll reflash.

gmermel said:
Problem #1: When I opened the ROM.zip, I didn't get another zip, I got a folder with no zips in it (a blob.exe, several other .exe). When I moved that over to the SD and chose to install it TWRP returned a "failure" notification.
I'd like to get the stock ROM on for the buyer. What should I do
Problem #2: I still have CROM-X on the external card. It is installing, but which kernel should I use?
I'm going to use sbdags stock, and if you think that's a mistake I'll reflash.
Click to expand...
Click to collapse
If you get the blob file you extracted once too often. The firmware is a zip inside a zip. You extract the downloaded file ONCE.
Stock kernel is fine.
Sent from my DROID4 using Tapatalk

Fixing a Hardbricked SCH-i535 / SCH-S968C Running Marshmallow 6.0.1

I have a Galaxy S3 model SCH-i535 (Verizon) running Marshmallow 6.0.1 which is now currently hard bricked as far as I can tell (can't turn on, no recovery mode, etc.).
I've been in a similar situation before while it was still running stock everything (the model was originally listed as SCH-S968C as I guess it's the same exact thing and was running 4.1.2 but changed once I updated), but I managed to save it by writing a debrick image onto the external SD which allowed the phone to boot. Cut forward to now and I'm unsure what to do.
The problem started when my phone wouldn't recognize my SIM card and I tried re-flashing nightly cyanogenmod builds with TWRP, but it didn't work. Eventually I was told to install a new modem and eventually found a ZIP file that I had to install through the recovery. Once I installed it (same way I installed any random ROM), I rebooted and at that point it wouldn't turn back on.
I've tried using the same image as before, but it didn't work and I haven't been able to find another image that's for Marshmallow and I don't believe you can somehow revert it to stock by booting it through the SD or something so I could use the old debrick image.
I'm not sure what else to do as Google so far hasn't turned up anything.

use 32 gb sdcard
what is your os befor hard brick

khiero said:
use 32 gb sdcard
what is your os befor hard brick
Click to expand...
Click to collapse
What do you mean by use a 32gb sdcard exactly?
Also it was running marshmallow 6.0.1 via Cyanogenmod, but if you mean before that it was 4.1.2 lollipop I think? Either way it was 4.1.2 something.

PastyBran said:
What do you mean by use a 32gb sdcard exactly?
Also it was running marshmallow 6.0.1 via Cyanogenmod, but if you mean before that it was 4.1.2 lollipop I think? Either way it was 4.1.2 something.
Click to expand...
Click to collapse
What exactly did you flash?

BadUsername said:
What exactly did you flash?
Click to expand...
Click to collapse
I believe it was the nightly build labeled "cm-13.0-20160510-NIGHTLY-d2vzw.zip" on the Cyanogen site (can't post links since I don't have enough posts I guess, but you should be able to find it easy).

You can't boot into download or recovery mode? Don't see a reason it should've been hard bricked.

BadUsername said:
You can't boot into download or recovery mode? Don't see a reason it should've been hard bricked.
Click to expand...
Click to collapse
What I think I did was replace the modem file directly (ie deleting the current modem and dragging and dropping the new one in to replace it).
I'm not sure why I did that but I did.

PastyBran said:
What I think I did was replace the modem file directly (ie deleting the current modem and dragging and dropping the new one in to replace it).
I'm not sure why I did that but I did.
Click to expand...
Click to collapse
Missed this somehow.
You're going to have to pull a debrick image from a 4.1 stock rom (whichever baseband you were on, not the actual rom you were using), write it to an sd card until it boots from that.
Once your phone boots, you can then move the debrick image to your internal storage and fix the modem, the hard brick repair guide should work for you.

BadUsername said:
Missed this somehow.
You're going to have to pull a debrick image from a 4.1 stock rom (whichever baseband you were on, not the actual rom you were using), write it to an sd card until it boots from that.
Once your phone boots, you can then move the debrick image to your internal storage and fix the modem, the hard brick repair guide should work for you.
Click to expand...
Click to collapse
How would I go about pulling a debrick image?
I downloaded the rom from here, but I'm not sure how to make a debrick image out of it.

PastyBran said:
How would I go about pulling a debrick image?
I downloaded the rom from here, but I'm not sure how to make a debrick image out of it.
Click to expand...
Click to collapse
I think that's too old, and if you look at the hardbrick repair guide it's posted in there.
I think the debrick image is a boot image, don't quote me on that though. I'm not really sure what it is because I never needed it.

BadUsername said:
I think that's too old, and if you look at the hardbrick repair guide it's posted in there.
I think the debrick image is a boot image, don't quote me on that though. I'm not really sure what it is because I never needed it.
Click to expand...
Click to collapse
Which one do you mean exactly?
One of the files in the OP or was it posted somewhere else in the thread? I saw this file here, but I wasn't sure which one you meant.

PastyBran said:
Which one do you mean exactly?
One of the files in the OP or was it posted somewhere else in the thread? I saw this file here, but I wasn't sure which one you meant.
Click to expand...
Click to collapse
The guide is stickied at the top :
http://forum.xda-developers.com/showthread.php?t=2581166&page=38
Follow those directions with the appropriate bootloader you have. I think you have 4.1.

BadUsername said:
The guide is stickied at the top :
http://forum.xda-developers.com/showthread.php?t=2581166&page=38
Follow those directions with the appropriate bootloader you have. I think you have 4.1.
Click to expand...
Click to collapse
You mean the one labeled "Debrick file if you bricked before the 4.3 OTA" correct?
Sorry if I seem a bit dense, I'm just trying to extra-cautious.
EDIT: Also one more question. Does it matter if you use use a USB micro SD reader (something that looks like a thumb drive, but you put a micro SD in a slot on the top), or is there a higher success rate using a SD card adapter and putting it into a SD card reader?
I heard that somewhere while looking up stuff, so I was curious if there was any merit to it.

PastyBran said:
You mean the one labeled "Debrick file if you bricked before the 4.3 OTA" correct?
Sorry if I seem a bit dense, I'm just trying to extra-cautious.
EDIT: Also one more question. Does it matter if you use use a USB micro SD reader (something that looks like a thumb drive, but you put a micro SD in a slot on the top), or is there a higher success rate using a SD card adapter and putting it into a SD card reader?
I heard that somewhere while looking up stuff, so I was curious if there was any merit to it.
Click to expand...
Click to collapse
Your phone has a microsd slot, put it in that.
Also if you use the wrong image nothing would happen, not really a risk to your phone.
Not sure why you'd need an adapter

BadUsername said:
Your phone has a microsd slot, put it in that.
Also if you use the wrong image nothing would happen, not really a risk to your phone.
Not sure why you'd need an adapter
Click to expand...
Click to collapse
Sorry, I meant as in an adapter to connect it to my PC in order to write the image onto the micro SD card.

PastyBran said:
Sorry, I meant as in an adapter to connect it to my PC in order to write the image onto the micro SD card.
Click to expand...
Click to collapse
O I see, ya you're going to need some way to get the file onto the sd card. That adapter should work.

BadUsername said:
O I see, ya you're going to need some way to get the file onto the sd card. That adapter should work.
Click to expand...
Click to collapse
I tried a few times over a couple days writing the debrick file from the guide to the card (specifically the labeled "Debrick file if you bricked before the 4.3 OTA"), following everything to the letter but to no avail.
I also noticed the light turns red when I plug it into my PC without the battery if that means anything.

I figure I should give a small update. I sent it into a local repair shop to get it JTAG'd and it's working fine now, so I don't need help anymore (for now at least).
Thanks to everyone whose helped me, and good luck to the guy reading this from a Google search like a year or two from now.

Help with Bricked phone

I need help fixing this problem I'm having, I've tried everything I can think of, in the first pic this is what the phone reboots to after flashing official firmware with Odin and the second pic is what I get when I try to factory wipe. Please help me!!!!

JrTech said:
I need help fixing this problem I'm having, I've tried everything I can think of, in the first pic this is what the phone reboots to after flashing official firmware with Odin and the second pic is what I get when I try to factory wipe. Please help me!!!!
Click to expand...
Click to collapse
Try first to install TWRP recovery instead of Samsung recovery using odin with the phone in the downloading mod
Then wipe every thing using Twrp
Then flash that rom using twrp

I installed twrp 3.0.3-0 and i still can't wipe anything, unable to mount data,storage and cache,tried changing the data partition type to vfat but no matter what I try it all ends with unable to mount data, storage and cache

Bro flash 4 firmware file that 100% it will be fix
---------- Post added at 04:44 PM ---------- Previous post was at 04:34 PM ----------
https://forum.xda-developers.com/galaxy-j7/development/j700h-marshmallow-update-method-rom-t3399433
---------- Post added at 04:45 PM ---------- Previous post was at 04:44 PM ----------
Just flash 4 firmware AP. CP. BL. CSC and tell me bro..

amarshah said:
Bro flash 4 firmware file that 100% it will be fix
---------- Post added at 04:44 PM ---------- Previous post was at 04:34 PM ----------
https://forum.xda-developers.com/galaxy-j7/development/j700h-marshmallow-update-method-rom-t3399433
---------- Post added at 04:45 PM ---------- Previous post was at 04:44 PM ----------
Just flash 4 firmware AP. CP. BL. CSC and tell me bro..
Click to expand...
Click to collapse
Hey thanks for the input, sorry I haven't replied, but believe it or not everything I do on the internet is with my mobile data and I had no data,I'm in a remote area at the moment but I should be in the city tomorrow, there I'll have access to the WiFi and I'll download and let you know what happens:fingers-crossed:

JrTech said:
Hey thanks for the input, sorry I haven't replied, but believe it or not everything I do on the internet is with my mobile data and I had no data,I'm in a remote area at the moment but I should be in the city tomorrow, there I'll have access to the WiFi and I'll download and let you know what happens:fingers-crossed:
Click to expand...
Click to collapse
Ok bro try it and say me?

Hey bro I tried it and got the same result, so here I go again downloading another one, will let u know what happens.

JrTech said:
Hey bro I tried it and got the same result, so here I go again downloading another one, will let u know what happens.
Click to expand...
Click to collapse
I'm beginning to think this is hardware related, I've already flashed four different firewares including the one you told me to use and the phone boots up rite back to the same error!!! I'm kinda sceptical though because the Odin flashing always goes well, everything loads until Odin says pass.

JrTech said:
I'm beginning to think this is hardware related, I've already flashed four different firewares including the one you told me to use and the phone boots up rite back to the same error!!! I'm kinda sceptical though because the Odin flashing always goes well, everything loads until Odin says pass.
Click to expand...
Click to collapse
Sounds like your partitions are jacked up, might try flashing a new pit file
Sent from my SM-J700P using Tapatalk

JrTech said:
I'm beginning to think this is hardware related, I've already flashed four different firewares including the one you told me to use and the phone boots up rite back to the same error!!! I'm kinda sceptical though because the Odin flashing always goes well, everything loads until Odin says pass.
Click to expand...
Click to collapse
Flash the firmware with the PIT file and check re-partition.
How did the device arrive at this state?

ashyx said:
Flash the firmware with the PIT file and check re-partition.
How did the device arrive at this state?
Click to expand...
Click to collapse
Hey thanks for the input guys, this phone got wet and when it was dried and turned on again this is the state its started in. I took out the logic board and checked for any damage from the water (corrosion) and its all clean, I even sprayed it with WD (water displacement), allowed it to drain and then heated it with the heat gun which vaporized the WD. I flashed with the pit file and all goes well, but it just reboots back to same errors. Fellas feel free to msg me on WhatsApp +5926792003 anytime. I'm just happy to know there is a place I can ask for help and get it! Here in Guyana the few phone techs I've talk to don't seem to be this in depth with some of the stuff I've learned from here, all these Guyanese tell me to do is change the board but I'd rather be sure that its beyond repair before I invest my hard earned money which is not easy to come by. The cost of the board is around 23000 Guyana dollars, which would be about 105 USD.
I forgot to mention, when I flashed twrp, in the advance wipe option, when I choose repair, I can see an actual size on the system and cache partition, but all other partitions show 0mb.

JrTech said:
Hey thanks for the input guys, this phone got wet and when it was dried and turned on again this is the state its started in. I took out the logic board and checked for any damage from the water (corrosion) and its all clean, I even sprayed it with WD (water displacement), allowed it to drain and then heated it with the heat gun which vaporized the WD. I flashed with the pit file and all goes well, but it just reboots back to same errors. Fellas feel free to msg me on WhatsApp +5926792003 anytime. I'm just happy to know there is a place I can ask for help and get it! Here in Guyana the few phone techs I've talk to don't seem to be this in depth with some of the stuff I've learned from here, all these Guyanese tell me to do is change the board but I'd rather be sure that its beyond repair before I invest my hard earned money which is not easy to come by. The cost of the board is around 23000 Guyana dollars, which would be about 105 USD.
I forgot to mention, when I flashed twrp, in the advance wipe option, when I choose repair, I can see an actual size on the system and cache partition, but all other partitions show 0mb.
Click to expand...
Click to collapse
Bro don't ever flash the pit. Go to www.sammobile.com and download the J700TUVU2APK6 firmware. Extract the zip on your PC and open Odin. Now go to Options (2nd tab) and unclick auto reboot. Click bootloader update, Nanderase all and reset time. Put the tar in the AP slot and flash it. When it completes flashing pull your battery. Boot into recovery holding the right buttons and let the phone erase and update the system. When it finishes it should boot into recovery by itself, if it doesn't pull your battery and boot into recovery again. Then let the phone boot and you're good to go. When you root this time and install TWRP make sure OEM unlock and USB debugging are ticked in developer options this time.

Metabolic12 said:
Bro don't ever flash the pit. Go to www.sammobile.com and download the J700TUVU2APK6 firmware. Extract the zip on your PC and open Odin. Now go to Options (2nd tab) and unclick auto reboot. Click bootloader update, Nanderase all and reset time. Put the tar in the AP slot and flash it. When it completes flashing pull your battery. Boot into recovery holding the right buttons and let the phone erase and update the system. When it finishes it should boot into recovery by itself, if it doesn't pull your battery and boot into recovery again. Then let the phone boot and you're good to go. When you root this time and install TWRP make sure OEM unlock and USB debugging are ticked in developer options this time.
Click to expand...
Click to collapse
Hey thanks bro, going to try this now, will post what happens.

Metabolic12 said:
Bro don't ever flash the pit. Go to www.sammobile.com and download the J700TUVU2APK6 firmware. Extract the zip on your PC and open Odin. Now go to Options (2nd tab) and unclick auto reboot. Click bootloader update, Nanderase all and reset time. Put the tar in the AP slot and flash it. When it completes flashing pull your battery. Boot into recovery holding the right buttons and let the phone erase and update the system. When it finishes it should boot into recovery by itself, if it doesn't pull your battery and boot into recovery again. Then let the phone boot and you're good to go. When you root this time and install TWRP make sure OEM unlock and USB debugging are ticked in developer options this time.
Click to expand...
Click to collapse
Please don't make statements when you're not sure what it is your advising.
Flashing the firmware hasn't worked as already posted.
The device is beyond simply flashing the firmware. It is fine to flash the PIT file with the state the device is already in.
@JrTech
It seems your partitions are damaged. There is hope if the system partition can be mounted which means the EMMC isn't totally dead.
Boot to TWRP and save the recovery log. Post the recovery.log file here (not the output).

ashyx said:
Please don't make statements when you're not sure what it is your advising.
Flashing the firmware hasn't worked as already posted.
The device is beyond simply flashing the firmware. It is fine to flash the PIT file with the state the device is already in.
Click to expand...
Click to collapse
I was just checking on the firmware he advised to download and wondering how would this be compatible with my j700h, because this is a T-Mobile update

JrTech said:
I was just checking on the firmware he advised to download and wondering how would this be compatible with my j700h, because this is a T-Mobile update
Click to expand...
Click to collapse
Exactly, it's the wrong firmware.
Did you ensure to check Re-partition when flashing?

ashyx said:
Please don't make statements when you're not sure what it is your advising.
Flashing the firmware hasn't worked as already posted.
The device is beyond simply flashing the firmware. It is fine to flash the PIT file with the state the device is already in.
@JrTech
It seems your partitions are damaged. There is hope if the system partition can be mounted which means the EMMC isn't totally dead.
Boot to TWRP and save the recovery log. Post the recovery.log file here (not the output).
Click to expand...
Click to collapse
Cool will post the log in a few mins

ashyx said:
Exactly, it's the wrong firmware.
Did you ensure to check Re-partition when flashing?
Click to expand...
Click to collapse
Yes I did, and I do think when I add the pit file Odin automatically checks re-partition, I checked to make sure and it is set to re-partition, all with the same result as before.

Hey ashyx I'm out running an errand, but I'll post the log as soon as I get back in. Thanks for your help and patience bro!

JrTech said:
Hey ashyx I'm out running an errand, but I'll post the log as soon as I get back in. Thanks for your help and patience bro!
Click to expand...
Click to collapse
No rush, I'm at work for the next few hours, so won't be able to examine the log until then.

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.