Related
My buddy got this phone I want to hook it up as he's not great with tech stuff i rooted with z4root and just need to know how to access recovery cause i didn't see a reinstall packages option in standard recovery ? Any help would be awesome thanks guys
I just rooted with Z4root... then I installed Titanium Backup and then ROM Manager, giving both apps root access (which I verified with the SuperUser app). In ROM Manager I did "Flash ClockworkMod Recovery" and chose the Fascinate option and was told that it downloaded the latest ClockworkMod Recovery. What's my next step?... Choose "Reboot into Recovery" within ROM Manager or do it another way. (My goal is to install Voodoo5 using the stock ROM for now. I have the Voodoo5 file on the SD card.)
EDIT: Whoops. I just realized that I had downloaded the two files to get CWM working but hadn't followed the unzipping, etc. instructions. I'd better go back and read that CWM thread again...
First get CWM working
Then check out this ROM
Or this ROM
and if you really wanna get fancy check out this kernel
Just in case you screw up
If you need more help on each specific topic, just ask in the appropriate areas and there is usually someone around that can answer questions.
Thanks for the quick links... really appreciate it.
BTW - Titanium Backup asks for USB Debugging to be enabled... do you have to do this? It creates issues for me when connecting the phone as mass storage to my PC.
ALSO - I'm assuming I should take an initial backup with Ti before I get too far into this, right? Not having done a backup before... is Ti the best to use? (Do I just choose batch and pick an option(s)? Does choosing "Backup user apps + system data" backup game save data?) EDIT: Just did this and it ran fine but it switched my Live wallpaper back to stock?!? WTF?
monthlymixcd said:
Thanks for the quick links... really appreciate it.
BTW - Titanium Backup asks for USB Debugging to be enabled... do you have to do this? It creates issues for me when connecting the phone as mass storage to my PC.
ALSO - I'm assuming I should take an initial backup with Ti before I get too far into this, right? Not having done a backup before... is Ti the best to use? (Do I just choose batch and pick an option(s)? Does choosing "Backup user apps + system data" backup game save data?)
Click to expand...
Click to collapse
Quick links are awesome! They save time, for sure.
Check the box to ask each time for mass storage and kies. Then you can have debugging enabled, and yes you have to have it enabled or TB won't do it's thing properly. You can switch it back and forth also. That's what I do.
I use TB to do my app and system data backups. Just run a batch backup on user apps and system data, like you said. That's the best option to start with. This isn't the same as a nandroid backup, but it's a good second choice for if you need to wipe data and restore apps quickly like a ROM install that requires you to wipe data/factory reset.
phidelt82 said:
Check the box to ask each time for mass storage and kies. Then you can have debugging enabled, and yes you have to have it enabled or TB won't do it's thing properly. You can switch it back and forth also. That's what I do.
Click to expand...
Click to collapse
Perfect. Thanks! Only thing is... USB dubugging doesn't stay ticked, it's ticked and Ti says it's not, or the connection still triggers a missing driver error message with Vista on the PC. Oh well.
phidelt82 said:
This isn't the same as a nandroid backup, but it's a good second choice for if you need to wipe data and restore apps quickly like a ROM install that requires you to wipe data/factory reset.
Click to expand...
Click to collapse
Easiest way to do a Nandroid backup? BTW - Ti backup ate up 5GB of my sd card?!? Yikes!
Also, regarding this thread:
phidelt82 said:
First get CWM working
Click to expand...
Click to collapse
I get "adb: not found"?
monthlymixcd said:
Perfect. Thanks!
Easiest way to do a Nandroid backup?
Also, regarding this thread:
I get "adb: not found"?
Click to expand...
Click to collapse
Nandroid backup will be there once you get CWM working.
You can do everything from the phone, just read down through the pages to find the people that have done it. They have left instructions using terminal emulator and root explorer. You will find that in a lot of instances many problems will have different ways of dealing with them. You probably don't have the Android SDK which is how you get ADB working on your computer. This isn't critical, it just makes it so that you will have to either install it or use the other means available. (ie terminal emulator and root explorer)
Still getting errors after trying several of the things in the thread... Q:I never did get a robot voice when I ran Z4root and never saw a place to choose permanent... should I run Z4root again? I mean, I was able to install Ti, etc. so I must have root, right? But I think my issues stem from not being able to get redbend_ua into the /system/xbin folder. Astro can't paste it there, Root Explorer can't paste it there, but in the terminal it appears like chmod worked... thoughts?
monthlymixcd said:
Still getting errors after trying several of the things in the thread... Q:I never did get a robot voice when I ran Z4root and never saw a place to choose permanent... should I run Z4root again? I mean, I was able to install Ti, etc. so I must have root, right? But I think my issues stem from not being able to get redbend_ua into the /system/xbin folder. Astro can't paste it there, Root Explorer can't paste it there, but in the terminal it appears like chmod worked... thoughts?
Click to expand...
Click to collapse
Root explorer needs to be mounted RW. There is a button at the top that will say RO or RW.
Sent from my SCH-I500 using XDA App
phidelt82 said:
Root explorer needs to be mounted RW. There is a button at the top that will say RO or RW.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
"Mounted as r/w"
I tried this. Used root explorer to finally get redbend_ua into system/xbin but when I try to run the commands in the post it cannot find redbend_ua. I also cannot cd into xbin within the emulator to ls ... says xbin not found. Explorer can see it there... what gives? do you have to restore redbend_ua inside the xbin directory or will it work to restore it elsewhere?
EDIT: cd to /system/xbin worked and an ls shows the redbend_ua there but the chmod 777 redbend_ua fails to "Unable to chmod redbend_ua: No such file or directory
EDIT to the EDIT: Hang on... think I may have found where I went wrong. What's the terminal command for delete?
monthlymixcd said:
"Mounted as r/w"
I tried this. Used root explorer to finally get redbend_ua into system/xbin but when I try to run the commands in the post it cannot find redbend_ua. I also cannot cd into xbin within the emulator to ls ... says xbin not found. Explorer can see it there... what gives? do you have to restore redbend_ua inside the xbin directory or will it work to restore it elsewhere?
Click to expand...
Click to collapse
Are you doing /system/xbin? The first / is important. You don't need to cd to xbin, though.
Sent from my SCH-I500 using XDA App
Isn't there anyway to flash a rom using odin ? If not are the codes the same for terminal emulator as they are for adb to get cwm working? I'm from the vibrant section of this site running nero v4 right now I have a good understanding of odin for the most part but this not having an easy recovery is bs lol
willsnews said:
Isn't there anyway to flash a rom using odin ? If not are the codes the same for terminal emulator as they are for adb to get cwm working? I'm from the vibrant section of this site running nero v4 right now I have a good understanding of odin for the most part but this not having an easy recovery is bs lol
Click to expand...
Click to collapse
I've never flashed a ROM using Odin, but that doesn't mean that it can't be done. The process should be the same using terminal emulator or adb, just more of a pain. I agree it would be nice to have full CWM Recovery support (or any full recovery support) but I don't have the money to spend on a phone to send to Koush right now to get that done. As soon as I do, this will be done and then I'll have a tester phone for firmware builds. It really isn't that difficult to get it working, though. I've done it probably 30-40 times now and even the first time the only flub was in a typo for the second to last character (thought it was a 1 and not an L)
So you type this stuff in all in one line or what?
willsnews said:
So you type this stuff in all in one line or what?
Click to expand...
Click to collapse
Depending on which parts you are talking about, yes. Each new line is a line of code. If it moves to a new line, hit enter.
phidelt82 said:
Are you doing /system/xbin? The first / is important. You don't need to cd to xbin, though.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.
monthlymixcd said:
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.
Click to expand...
Click to collapse
I can't remember if Astro has R/W options for the root directory. That may be the problem.
phidelt82 said:
Depending on which parts you are talking about, yes. Each new line is a line of code. If it moves to a new line, hit enter.
Click to expand...
Click to collapse
I just ned to get a custom recovery how did you type it in to terminal emulator? Like extacy how?i just dont want to mess up my buddies phone I want yo hook him up not **** him up lol
monthlymixcd said:
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.
Click to expand...
Click to collapse
You guys are confusing the hell outta me I don't know who's answering me and who's answering you I know this pertains to this thread but im right in the middle of this process and its not even my phone
I apologize for the derail... I got mine working. I had a typo. I'm off to voodoo.
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.
Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things
Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.
Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks
What recovery are you using? I suck with adb so I got nothing on that front.
It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied
BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.
So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium
For those who have been living under a rock, problematic leaked builds of ICS were released for several different Samsung devices a few months ago. Users of those Devices for instance soon discovered that their devices were being ffected by what came to be known as the MMC_CAP_ERASE bug. Shortly after this*occurred, XDA Senior Member hg42 came up with a way to revive downed devices.
Now thanks to some more ingeniuty on his part, hg42 has also developed a companion application known as Partition Scanner to assist in this process.*The application features:
emmc_scan_all_partitions_once.zip
emmc_scan_all_partitions_infinitely.zip
these allow fast scanning of all blocks of all emmc partitions in 1MiB steps.
The main purpose is to access each emmc block to find any bricked block in the partitions after repartitioning.
The “infinitely” variant runs checks infinitely, which may help to find emmc brick effects which only occur sporadically (if such effect really exists). Run this as long as you want. Reboot to finish.
If this freezes the last partition shown may have a bricked block inside.
emmc_find_brick_start.zip
emmc_find_brick_end.zip
these scan the whole emmc device.
emmc_find_brick_start starts scanning from the beginning of the device upward.
emmc_find_brick_end searches the end of the device and then scans downward.
If this runs up to the end or down to zero (showing a message with “completed –> OK”), no bricked block was found.
If it freezes, the block shown last with “…” at end of line is the first bricked block in that direction.
The line before with “-> ok” is the first usable block before/after the brick.
The application has received excellent reviews, so if you’re one of those people currently facing an EMMC issue, or you had the issue previously and gave up on your device, head on over to the companion thread and give this a go.
Click to expand...
Click to collapse
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
@Bad2hold - have you tried this yourself as I am desperate for help in unbricking my device that Samsung refuse to repair as it is the P-6200L (non-UK model).
I can't use ADB as my pc won't recognise the Tab, have tried flashing the .pit file and firmware but no joy, can't use the partition scanner as I can't get it to scan the internal memory (it scans the external SD card instead).
I can install CWM recovery and also get to stock recovery but the Tab will not go past the white Galaxy Tab logo.
Any help is highly appreciated
There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..
chrisrotolo said:
There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..
Click to expand...
Click to collapse
Thanks for the advice mate.
Am going to flash it with the honeycomb firmware it came with from Sammobile and try a few factory resets to see if that works.
If not have found a place in the UK that will JTAG it for £38 if all else fails...:good:
UPDATE: Honeycomb doesn't let me access recovery so no way to wipe from there. Recovery is available on an ICS rom but am reluctant wipe in stock recovery as that's how I go in this mess to begin with :crying:
I currently cant help, as iam travelling without a pc... but this guy who developed this scanner, has pit files available for our device. So there is a good chance to get help from him. And iam sure, with some hours off every week, where u get bored, u can actually fix it by yourself as u already figured out that much... i would love to help, its a challange you know? maybe iam gonna buy a laptop... =p
Update: just curious, is it scanning without a external sd inserted? Because internal and sd are swapped in cwm recovery since 3 versions too...
Sent from my GT-P6200 using xda app-developers app
@Bad2hold - Thanks for the reply, have tried flashing the .pit file but no joy.
Can't get the scanner to scan internal card as it's loaded on my external sd and can't push it to the internal which then means I can't remove the external sd.
Have tried flashing various honeycomb and ICS firmwares with a combination of .pit files, the process flashed fine without errors but still no boot past the white Samsung writing
Sent from my GT-I9300 using xda premium
Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...
unclefab said:
Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...
Click to expand...
Click to collapse
I think we cannot remove the brickbug on stock ICS...that pit file just for solving hardbrick issue...
Sent from my GT-P6200 using xda premium
U can actually remove the brick bug issue, this is, what this post is about.
Basically, you just have to find the bad blocks in your sd partition.
After you found them, all is left, is to repartition your sd around the bricked blocks, which you have to delete from your partition.
He mentions several methods to use adb and other tools, helping to do this.
And i really recommend reading a bit through his first post, found the same problem after a minute:
I also had the following problem:
I couldn't format my internal sdcard with the cm9 recovery. I think it's too big for the mkfs.vfat tool of current cm9. So I installed another recovery, formatted the internal sd (I thought).
This erased all my current backups and downloads, because in reality it was my external sd. Fortunately I had a backup of the external sdcard from before rescuing my phone.
So, you may want to create a backup of your external sdcard first.
Then double check which is your internal sdcard (the UMS partition) and which is your external sdcard.
Or you could remove the external sd completely. But think about when to remove it, because you might need it for some files (e.g. to use the emmc partition scanner).
Click to expand...
Click to collapse
Of course, if u r not familiar with linux, u probably wont fix it in an hour.
But you can learn a lot within an hour. First of all, figure out how to connect your device to adb. (Which is still possible, if you didnt smash your tab against the wall or so...) After that, it should be lot easier to follow his instructions.(not just because u have adb working, but because you know what he is actually talking about.)
And he is really willing to help, so figure out as much as possible after connected to adb and just ask in his post if you get stuck.
Dont forget: if its not a issue by malfunctioning/broken hardware, then you actually can fix everything with your pc, you just need to know how.. so dont give up!!!
here his post again: http://forum.xda-developers.com/showthread.php?t=1667886
And @kersey: what pit file did u flash? The pits he provides are to repartition your SD AFTER you located the bricked blocks. But you cant know, if you cant get his scanner running..? You have to format data partition in recovery after flashing one of those, because of missing file system.
Note: Never flash a stock ICS after you fixed it. It will brick your device again. But u r safe with cm9 and others.
Sent from my GT-P6200 using xda app-developers app
Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too :good:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd
Happy Boy
Hi all
While trying to root and install custom rom I bricked my friends phone. I have been going crazy trying everything I could to get this brick back to life.
ITS ALIVE AGAIN!!!!!!!!
Thank you kersey for your post on how you got your Tab back.
This is what I did.
I installed the 5 files on the SD card.
120824-151927-emmc_find_brick_end
120824-151927-emmc_find_brick_start
120824-151927-emmc_scan_all_partitions_infinitely
120824-151927-emmc_scan_all_partitions_once
120824-220105-emmc_scan_write
I put the phone into recovery mode and ran 120824-151927-emmc_find_brick_start.
The program started scanning the memory and first froze on 2188.
I got back into recovery and ran 120824-151927-emmc_find_brick_end
once again the program started counting down and froze about 3189.
For this phone the correct pit files were in " pits-N7000_16GB "
I unzipped pits-N7000_16GB and looked for the nearest pit file , which was
N7000_16GB_Q1_20110914--patched--brick-between-1174-and-3321-MB--DATAFS-moved-by-2048-MiB.pit
I then put the phone back into download mode and using Odin flashed the patched pit file above.
Disconnecting the phone from computer I went back into recovery and ran120824-151927-emmc_scan_all_partitions_once
For the first time I was able to do a full scan without the program freezing.
Next step was installing Abyss Kernel 4.2. I then did the regular data wipe/cache wipe/dalvik wipe.
And finally I installed Rocketrom 11.
The phone rebooted and then came back to life.
I checked the internal memory and it was down to 9gb, but who cares as long as its ALIVE AGAIN !!!!
hg42 you sir are an absolute legend. Donation coming your way.
This method definitely works . Just be patient. I hope This helps others aswell
EDIT:
Is there any not so hard way to install the original rom with the pit i need? cm10 works, but i dont like it so much.
p6201dbtlpc_p6201xxlpc_p6201xxlp3_home.tar i would like to use
but i only know to flash this in odin, becouse it is no zip, i have no clue how to flash it in cwm
thanks for an answer!
-----------------
Your post should be on first post added =)
And in http://forum.xda-developers.com/showthread.php?t=1807002 !
Thanks for it!
kersey said:
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd
Click to expand...
Click to collapse
ICS update and emmc bug
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
doaft said:
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
Click to expand...
Click to collapse
If you chose to do a factory restore via stock recovery, which is what you have due to not being rooted and not having CWM installed there is a very big chance you may brick your device. I speak from experience!!!
If you are that worried I would flash back to honeycomb rather than risking having an expensive paperweight
Sent from my GT-I9300 using xda premium
A little of my own experience with superbrick
Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it
P6200
Hello man... I saw your post ''Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too'' ... I have the same problem with my P6200. Please give me that scanner to fix it or tell me how to put my tablet back On... Thanks
Androguide.fr said:
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it
Click to expand...
Click to collapse
hey dude it's my first post in xda
i've succeded to unbrick my device but my internal memory is shrink a lot into 700+ mb but i don't understand how to use the script so
can u explain step by step ?
one can help me ??
hai everybody.... i'm from indonesia.., my friend just give me samsung galaxy tab 7 plus... ( GT-P6200 ) without any boxes, last day i try to get ICS update from kies , but the application won't update my firmware , so i try the alternative direction.
i try another application - Odin3-v1.85 and download the firmware..., but the fact is after few second running it self , the prosess can't continues get fail after
Note : i;m using : P6200OXALQ1_P6200XXLQ1_P6200XXLQ1_HOME.tar.md5 firmware
<ID:0/017> Firmware update start..
<ID:0/017> cache.img
<ID:0/017> NAND Write Start!!
<ID:0/017> factoryfs.img
<ID:0/017> hidden.img
<ID:0/017> recovery.img
<ID:0/017> Sbl.bin
<ID:0/017>
<ID:0/017> Complete(Write) operation failed. >>> FAIL...
anyone can help me .... please
Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
TwistedPoet said:
Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
Click to expand...
Click to collapse
Ok, Can you boot to Odin mode (dowload mode)?
TwistedPoet said:
Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
Click to expand...
Click to collapse
I doubt you'll bore us here, after all we dwell in the minutiae and tiniest of details for fun. Hmm, from what I see you have a bootloader hard brick since you tried using EZ Unlock. TW 4.3 prevents downgrading the rom to pre-4.3, flashing an unlocked bootloader, and installing a custom recovery using 4.1.2 methods. Your best option will be to try the steps detailed in this bootloader/hardbrick thread by SpyroDazee.
buhohitr said:
Ok, Can you boot to Odin mode (dowload mode)?
Click to expand...
Click to collapse
No. Once I used EZ Unlock, I was bricked.
SlimSnoopOS said:
I doubt you'll bore us here, after all we dwell in the minutiae and tiniest of details for fun. Hmm, from what I see you have a bootloader hard brick since you tried using EZ Unlock. TW 4.3 prevents downgrading the rom to pre-4.3, flashing an unlocked bootloader, and installing a custom recovery using 4.1.2 methods. Your best option will be to try the steps detailed in this bootloader/hardbrick thread by SpyroDazee.
Click to expand...
Click to collapse
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img. http://angelfirenetworks.servegame.com/XDA/S3 Debrick IMG_s/
And then I can seem to make that run either.
I also have bricked S3 different circumstances but still hard bricked. Nothing I've tried here on xda or anywhere else has worked. I'm going to try this http://www.ebay.com/itm/281217379767?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649 . It is probably the cheapest and easiest way.
TwistedPoet said:
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img. http://angelfirenetworks.servegame.com/XDA/S3 Debrick IMG_s/
And then I can seem to make that run either.
Click to expand...
Click to collapse
It usually takes a few tries to get it to work, but if you really can't then you can always send it in for a jtag repair.
Mobile tech videos will do it, and there's someone on eBay who will do it for $30. Not too expensive.
Sent from my SCH-I535 using Tapatalk 2
TwistedPoet said:
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img.
And then I can seem to make that run either.
Click to expand...
Click to collapse
So I just downloaded the debrick.zip and Win32 program from my link onto my laptop. I saved the unzipped debrick folder onto my desktop and found the debrick.bin once I switched the "Files of type" to "." then I just wrote the debrick.bin to a 512 mb sdcard with no problems. I'm not going any further cuz I have no need for this though. Are you saying that Win32 doesn't find the bin file at all?
Edit: I just ran it again and it worked a second time. My backup laptop is a 2006ish (maybe older) with a very outdated version of Windows and my sdcard has been unused since 2008. I don't know what else to tell you but it worked surprisingly well for me.
SlimSnoopOS said:
So I just downloaded the debrick.zip and Win32 program from my link onto my laptop. I saved the unzipped debrick folder onto my desktop and found the debrick.bin once I switched the "Files of type" to "." then I just wrote the debrick.bin to a 512 mb sdcard with no problems. I'm not going any further cuz I have no need for this though. Are you saying that Win32 doesn't find the bin file at all?
Edit: I just ran it again and it worked a second time. My backup laptop is a 2006ish (maybe older) with a very outdated version of Windows and my sdcard has been unused since 2008. I don't know what else to tell you but it worked surprisingly well for me.
Click to expand...
Click to collapse
The Win32 program finds the debrick.bin file when I switch to "." as well. But when I click WRITE, I get an error message and the file doesnt't write to the sd card. I'm using a HP Windows 7 Pro (2009) and I have a 32gb, class 10 sd card. I will run it again to double check.
Follow Up: I figured out what I was doing wrong. I was attempting to pull the "bin" file through Win32 and should have been pulling the "zip" file instead. I was able to write the debrick.zip file onto my SD card but wasn't (on first attempt) able to load my phone. Are there any other steps I may have misunderstood or overlooked?
TwistedPoet said:
The Win32 program finds the debrick.bin file when I switch to "." as well. But when I click WRITE, I get an error message and the file doesnt't write to the sd card. I'm using a HP Windows 7 Pro (2009) and I have a 32gb, class 10 sd card. I will run it again to double check.
Click to expand...
Click to collapse
Have you tried formatting the sdcard and running the program again? Set it to Fat32. I'm thinking it may be the sdcard and not the program itself but I'm not certain.
SlimSnoopOS said:
Have you tried formatting the sdcard and running the program again? Set it to Fat32. I'm thinking it may be the sdcard and not the program itself but I'm not certain.
Click to expand...
Click to collapse
VICTORY!!!!!!! - I made several mistakes in getting to this point but i have successfully retrieved my phone from it's previous HardBrick status. The steps it took me to get to this point were, make sure the sd card is formatted (FAT32) and empty, unzip the debrick.zip file, run the Win32 program, select the unzipped debrick.bin file and upload it to the F drive, then click Write. So, more or less, exactly what the instructions told me to do. Sometimes, it's the simple things that we're most often missing or not understanding.
THANK YOU to everyone and especially SlimSnoopOS for talking me through it and SpyroDazee for making such a comprehensive guide to work with. (although, it's simplicity was too complex for me. ).
TwistedPoet said:
VICTORY!!!!!!! - I made several mistakes in getting to this point but i have successfully retrieved my phone from it's previous HardBrick status. The steps it took me to get to this point were, make sure the sd card is formatted (FAT32) and empty, unzip the debrick.zip file, run the Win32 program, select the unzipped debrick.bin file and upload it to the F drive, then click Write. So, more or less, exactly what the instructions told me to do. Sometimes, it's the simple things that we're most often missing or not understanding.
THANK YOU to everyone and especially SlimSnoopOS for talking me through it and SpyroDazee for making such a comprehensive guide to work with. (although, it's simplicity was too complex for me. ).
Click to expand...
Click to collapse
Haha I love the enthusiasm my friend! Great way to start the weekend! All it took was another perspective, it's all good. You are most definitely welcome.
Edit: and while I'm here, if you have any inquiries about TW 4.3 or want to read up on some info then here's our TW 4.3 discussion thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Haha I love the enthusiasm my friend! Great way to start the weekend! All it took was another perspective, it's all good. You are most definitely welcome.
Edit: and while I'm here, if you have any inquiries about TW 4.3 or want to read up on some info then here's our TW 4.3 discussion thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I'm not turning away knowledge. I'm still very new to this and obviously have a hard time following directions. I was looking at the next steps on that guide and am all ready confused enough to not do anything yet.
What is your phone doing after you inserted your sdcard and what size card and class were they. If you got it to go into download mode or some call it Odin mode by pressing volume down, home button and power button then your off to a great start to bringing your phone back from the dead. If only it worked for mine
Where did you get the debrick.zip file? Every time I download the file it comes as debrick.img not a .zip
Always_Jonezen said:
What is your phone doing after you inserted your sdcard and what size card and class were they. If you got it to go into download mode or some call it Odin mode by pressing volume down, home button and power button then your off to a great start to bringing your phone back from the dead. If only it worked for mine
Where did you get the debrick.zip file? Every time I download the file it comes as debrick.img not a .zip
Click to expand...
Click to collapse
Edit: My SD Card is a 32gb class 10. Once I got Win32 to extract the file properly, I put the SD card back into the phone, put the battery in, and plugged phone into computer. Pushed the power button and the phone came back on.
When you go to download that file with Win32, change the file type to "." - then you'll be able to select the debrick.zip
All files were obtained here - http://forum.xda-developers.com/showthread.php?t=2581166
I hope that helps.
TwistedPoet;49543890. Edit: My SD Card is a 32gb class 10. Once I got Win32 to extract the file properly said:
http://forum.xda-developers.com/showthread.php?t=2581166[/url]
I hope that helps.
Click to expand...
Click to collapse
Thanks I hope it works too. Am I supposed to change the file type of the debrick.img to debrick. and or change the file type in win32
Always_Jonezen said:
Thanks I hope it works too. Am I supposed to change the file type of the debrick.img to debrick. and or change the file type in win32
Click to expand...
Click to collapse
They did exactly what I posted, which was: unzip the debrick.zip, open Win32 and change the file type to ".", find the unzipped debrick folder and select the debrick.bin, and write to the sdcard.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
They did exactly what I posted, which was: unzip the debrick.zip, open Win32 and change the file type to ".", find the unzipped debrick folder and select the debrick.bin, and write to the sdcard.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
As stated earlier when I download the debrick file it downloads as debrick.img not a zip file am I missing something
Always_Jonezen said:
As stated earlier when I download the debrick file it downloads as debrick.img not a zip file am I missing something
Click to expand...
Click to collapse
Did you brick BEFORE 4.3? I hovered over this link in SpyroDazee's post: "Debrick if you bricked before 4.3 OTA" and that's the only one that would download as an IMG. Press "Debrick if you took the 4.3 OTA" and it will download as a zip.
Or change the browser that you're using. I downloaded it using Chrome on my MBP.
Sent from my SCH-I535 using Tapatalk 4
I did brick on 4.1.2 and I am using chrome as my default browser
Hi, Im new to this device but right after I got it I did the right thing and voided my warranty Rooted and installed a custom recovery. The recovery has been a bit of a pain but that is a story for another thread.
The problem I am having is that when I try to take a backup from recovery it errors (I forget the error, sorry. ) however the backup is still right there in the backup directory. I tried a second attempt at a backup (to see if it would error again) and these two backups filled my remaining memory. lI of course used my file explorer to delete these extraneous backups-- only to see that they are not deletable. I also tried on the PC. The folder lists read and write in the permissions. I am kind of at a loss as to what to do. IIRC correctly from a while back with this issue the answer lies somewhere in CHMOD, but I cant quite seem figure it out. CD to the directory in a terminal emulator and then CHMOD 777? Thanks for your help in advance.
knoober said:
Hi, Im new to this device but right after I got it I did the right thing and voided my warranty Rooted and installed a custom recovery. The recovery has been a bit of a pain but that is a story for another thread.
The problem I am having is that when I try to take a backup from recovery it errors (I forget the error, sorry. ) however the backup is still right there in the backup directory. I tried a second attempt at a backup (to see if it would error again) and these two backups filled my remaining memory. lI of course used my file explorer to delete these extraneous backups-- only to see that they are not deletable. I also tried on the PC. The folder lists read and write in the permissions. I am kind of at a loss as to what to do. IIRC correctly from a while back with this issue the answer lies somewhere in CHMOD, but I cant quite seem figure it out. CD to the directory in a terminal emulator and then CHMOD 777? Thanks for your help in advance.
Click to expand...
Click to collapse
If you are using TWRP, It is not possible to delete twrp backup images using normal ways. Either you can install esfile explorer and navigate to device/data/media/0/twrp/backups/ and delete from there. Or use file manager in TWRP to delete the backups. I think there is also another option in twrp to view or delete backups.
Sent from my Moto G using Tapatalk 2
Ill check out the other things you said, but Im actually getting this problem in ESfile... Ill report back if I can get at it through the recovery.
Edit: ESfile works. I followed the path you laid out ad got there just fine I didnt realize Id have to take such a roundabout path. Thank you.