Database Info

[Recovery] ClockworkMod 2.5.1.7 offmode charging

thanks go to damien667 for the method, brswattt and ladios for being brave and testing.
DOWNLOAD:
View attachment clockworkmod-2.5.1.7-liberty-offmode-charging.zip
Instructions:
unzip the recovery image and use your specific devices installation procedure for recovery.
This is a custom clockworkmod recovery 2.5.1.7 that allows you to finally turn off your phone and allow it to charge instead of it booting right back into clockwork.
a detailed explanation on how this is acheived is HERE
This recovery only has a modified ramdisk, functionality and use is the same as clockworkmod 2.5.1.7 official.
enjoy.
now i'm off to fix the DHD recovery.
EDIT: manually installing is the only option at the moment, thanks gruss.
stupid s-on.
ROM MANAGER should have the latest recovery image available with a fix for powering off and charging, thread will stay up for hostorical reference but these images are no longer required, it is always recommended to upgrade to the current version of rom manager and cwm that your rom requires

amazinglarry311 said:
I need one experienced user to test this recovery image.
The mod performed is the same one done to the the g2 and mt4g and works flawlessly on the recovery images I have posted altering recovery to allow charge while the phone is off and not boot to clockworkmod.
If you do not know how to flash recovery images manually through fastboot or from a rom do not continue.
If you do not know how to recover from a bad recovery flash do not continue.
This image is untested as I do not have access to an aria. Be warned.
Danger should be low, please understand I do not accept liability in the very very small chance something goes horribly wrong.
If you are not sufficiently scared yet, please test and let me know if it works, if not working please stand by, flash back to your previous recovery image, and I will post a fix.
Thanks go to damien667 for figuring it out.
View attachment 562769
if people are using cwm 3.x i can modify that as well.
Click to expand...
Click to collapse
Lots of views - no takers yet...
I'm sure many would find this very useful. If anyone has a "spare" Aria, or is really brave (I have neither a spare nor the guts), please check it out.
.

Bad recovery flash won't kill your phone.
Oh well.

we cant replace the recovery with out unrooting and redoing unrevoked
still need s-off

I thought you could do a temporary flash that doesn't stick. I suppose that's problematic as the device has to be turned off to test the mod. Go figure. The threads here for when someone wants to try it out, I can only think of two potential issues that would cause this not to work. Does anyone have a link to an OTA recovery image in img form for the aria? I'll google it, but if anyone knows please answer.

Flashed, not working. When it booted into recovey, it stayed on the htc screen, no menu was shown. `adb devices` showed that it's in recovery mode, though. Used adb shell to look around, everything's there but no /etc/fstab... can't mount anything.
hk-froyo-ota-recovery-image.zip md5sum: 0d44b10cbb8f1d6d40e68b522e578042
Although I did unroot in order to flash it, I think it might be ok to run unrevoked on sense 2.1 or 2.2 rom to do the job.
edit: wow, ota pops up! never throught i would see that again.
INFO/htcCheckinService(80): Started a new update download: http://fotadl.htc.com/OTA_Liberty_F...4_P_release_138425_15969388mnzxpm7szkle1k.zip

ladios said:
Flashed, not working. When it booted into recovey, it stayed on the htc screen, no menu was shown. `adb devices` showed that it's in recovery mode, though. Used adb shell to look around, everything's there but no /etc/fstab... can't mount anything.
hk-froyo-ota-recovery-image.zip md5sum: 0d44b10cbb8f1d6d40e68b522e578042
Although I did unroot in order to flash it, I think it might be ok to run unrevoked on sense 2.1 or 2.2 rom to do the job.
Click to expand...
Click to collapse
Thank you for testing this, Ladios!

Awesome, thanks for the test. I'm guessing it's the ueventd binary that isnt needed. i'll know in about five seconds after i pull apart the OTA recovery.
Thanks for testing, i'll have another one up in a jiffy.

yup. init.rc was calling a binary (ueventd) that isnt required.
try this one out:
EDIT: removed see bottom of the post
Sorry guys, this would be way easier if i had one.
These are the same changes aligned with the other mods i've done:
basically the OTA recovery contains four binaries not found in CWM
detect_key
power_test
offmode_charging
choice_fn
the init.rc on the original OTA recovery calls these binaries when plugged in and off, the recovery kernel should load but keeping the phone off and in a charging state. adb will should available in this mode as well.
a better explanation was in the mt4g thread: http://forum.xda-developers.com/showpost.php?p=12513699&postcount=3
EDIT: removed, found resources needed.
please test. and thank you. this mod is in response to a request by gruss at the CM forum to see if the same mod could be applied.
EDIT: the OTA recovery that was posted did not contain some resources, give me five minutes... i found the original RUU and the recovery image there has everything i need. filesize increase is due to inclusion of offmode_charging_images that i found in the original OTA recovery.
EDIT: REMOVED - test succesful see first post.
this one really should work. i have pretty good faith in it..
If not, it looks like the mod works with some recoveries and not all. i may attempt one more time, but i dont want to waste people's time here.

amazinglarry311 said:
yup. init.rc was calling a binary (ueventd) that isnt required.
try this one out:
EDIT: removed see bottom of the post
Sorry guys, this would be way easier if i had one.
These are the same changes aligned with the other mods i've done:
basically the OTA recovery contains four binaries not found in CWM
detect_key
power_test
offmode_charging
choice_fn
the init.rc on the original OTA recovery calls these binaries when plugged in and off, the recovery kernel should load but keeping the phone off and in a charging state. adb will should available in this mode as well.
a better explanation was in the mt4g thread: http://forum.xda-developers.com/showpost.php?p=12513699&postcount=3
EDIT: removed, found resources needed.
please test. and thank you. this mod is in response to a request by gruss at the CM forum to see if the same mod could be applied.
EDIT: the OTA recovery that was posted did not contain some resources, give me five minutes... i found the original RUU and the recovery image there has everything i need. filesize increase is due to inclusion of offmode_charging_images that i found in the original OTA recovery.
View attachment 563263
this one really should work. i have pretty good faith in it..
If not, it looks like the mod works with some recoveries and not all. i may attempt one more time, but i dont want to waste people's time here.
Click to expand...
Click to collapse
This does indeed work The screen is a little dim though when it's charging.

brswattt said:
This does indeed work The screen is a little dim though when it's charging.
Click to expand...
Click to collapse
Excellent, I will update the first post. About the screen being slightly dim - the stock aria recovery image used to actually load pictures showing the charging status while the phone is off, this would draw the images on the phone and the background was never a solid black, go figure. Cwm doesn't display them correctly as the resources are there but it was never written into the recovery itself or it's a frame buffer issue our something along those lines.
EDIT: see first post for download.

amazinglarry311 said:
thanks go to damien667 for the method, brswattt and ladios for being brave and testing.
DOWNLOAD:
View attachment 563834
Instructions:
unzip the recovery image and use your specific devices installation procedure for recovery. TESTERS - see below.
This is a custom clockworkmod recovery 2.5.1.7 that allows you to finally turn off your phone and allow it to charge instead of it booting right back inot clockwork.
a detailed explanation on how this is acheived is HERE
This recovery only has a modified ramdisk, functionality and use is the same as clockworkmod 2.5.1.7 official.
enjoy.
now i'm off to fix the DHD recovery.
TESTER NEEDED: Now the instructions to install the recovery are to do it manually and unzip the file. the zip itself is actually flashable, i just need to know if the capability exists for the aria to flash a recovery image while booted into recovery. The way that some OTA updates usually work (or used to) allowed raw images to be flashed while in recovery. I know the nand is locked when you are booted, but does the same apply to recovery? My assumption is no. if someone would like to test the zip from their current recovery and flash it, and reboot to recovery, turn off and try to charge to see if it sticks. possible things that can happen testing this: it doesnt stick and you keep your old recovery and flash manually, or you lose your recovery image (doubtful and highly unlikely)
it occurs to me that the flashable might not work, are your devices the kind that write the recovery image every time the phone is turned off?
Click to expand...
Click to collapse
Cannot flash the zip:
Code:
-- Installing: SDCARD:2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
Opening update package...
I:Update file path: /sdcard/2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
Installing update...
I:Trying update-binary.
E:Error in /sdcard/2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
(Status 0)
Installation aborted.
I tried to use flash_image before, it can't be read/write. Except one time, unrevoked failed its attempt and stopped right before its last couple of stages, flash_image worked for once. In other times, it failed and then rebooted, left me no chance to run flash_image.

for now manual flash looks like the way to go. you can check the OP again, there's a slim possibility a LIBEIMG.zip will load from hboot. it's in the first post. this kind of thing works for mt3g/dream/g2/mt4g but these suckers are all s-off as well. sigh. lame.

amazinglarry311 said:
for now manual flash looks like the way to go. you can check the OP again, there's a slim possibility a LIBEIMG.zip will load from hboot. it's in the first post. this kind of thing works for mt3g/dream/g2/mt4g but these suckers are all s-off as well. sigh. lame.
Click to expand...
Click to collapse
Hboot loaded the zip, showed a vertical status bar on the top-right corner, said checking the zip, and then stopped.
Seems unrevoked is the only way...

yeah i just finished updating the original post. thanks to everyone who tested.
s-on sucks big time.
just to be clear though the image is reported to work and charge while off.

Thanks for all the work.
Sent from my Liberty using XDA Premium App

amazinglarry311 said:
yeah i just finished updating the original post. thanks to everyone who tested.
s-on sucks big time.
just to be clear though the image is reported to work and charge while off.
Click to expand...
Click to collapse
So if I understand this correctly:
1. Connect phone to computer whilst booted up
2. Run Unerevoked, but use the included ".img" file from the OP file
3. Install the new recovery image
4. Reboot phone (if it doesn't do it on its own)
Or do I flash the entire .zip file from the phone's recovery menu?
Sorry if these are "dummy" questions...

Thanks for this little modification of the recovery! I actually see a little battery on the screen when charging now. However, Recovery still says 2.5.0.7, but charging while off works with no problems. I also flashed CM7 using the recovery I downloaded in this thread, so the recovery has no issues as well! Thanks again!

DanGeorges said:
So if I understand this correctly:
1. Connect phone to computer whilst booted up
2. Run Unerevoked, but use the included ".img" file from the OP file
3. Install the new recovery image
4. Reboot phone (if it doesn't do it on its own)
Or do I flash the entire .zip file from the phone's recovery menu?
Sorry if these are "dummy" questions...
Click to expand...
Click to collapse
I actually had to first unroot before Unrevoked actually installed the new recovery image. Something is weird about the Aria about not flashing recoveries directly...

foreign_legion said:
I actually had to first unroot before Unrevoked actually installed the new recovery image. Something is weird about the Aria about not flashing recoveries directly...
Click to expand...
Click to collapse
So if I unroot, then use Unrevoked, how do I get unrevoked to use the new recovery? Is there a file somewhere on my computer that should be swapped out first?

Xoom bricked

Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.

Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.

If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.

Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?

Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.

Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?

eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App

sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.

Root SM-T210/R using Heimdall

I took a little time playing around with Heimdall. It's....... different.
I have taken the time to simplify some of the steps for everyone, and built the required file myself.
I used TWRP 2.8.0.0 "img" file from their website. All development credit go to TeamWin, I've just converted it to the proper file format for Heimdall.
edit: The file use is actually a port to the Tab 3 by gr8nole. I was wrong about a couple of things. So, credit goes to TeamWin for original dev, and to gr8nole for porting it to the Tab 3 for us
Before reading farther, please remember:
ALL FLASHING IS DONE AT ONE's OWN RISK, I'M NOT RESPONSIBLE.
Please take adequate precautions to be able to recover your device from a soft brick.
This method is for KitKat users.
I used the Pit mapping for the T210. The recovery partition is "mmcblk0p10." I checked the partition info on my T210R using Partition Table by Lakshman. The T210R also has its Recovery partition on "mmcblk0p10," so I expect it to work no problem. And TWRP Odin flashables tend to be compatible with several 7.0 variants.
1. Open Heimdall. Reboot your device into download mode (power+volume down+home, then volume up).
2. Attach tablet to computer.
3. Select "Load Package" tab if it isn't already.
4. Click the "Browse" button under "Heimdall Firmware Package."
5. Select the ".tar.gz" file attached to this thread.
6. Click "Load/Customize." This will jump you to the "Flash" Tab.
7. Make sure that the "Repartition" check-box is unselected.
8. Click "Flash."
9. After flashing, reboot into your new recovery and install SuperSU and BusyBox.
As of this point, I have not been able to test this. I hope it goes well for anyone who tries it
Update:
As of now, I have been able to test this file on my own T210R. I already had this version of TWRP installed, so can't confirm actual update, but Heimdall said it flashed, and it didn't brick it, so I'd say good to go! (Take appropriate precautions anyways, because you never know what will happen.)

Worked well, thanks

Greaper88 said:
I took a little time playing around with Heimdall. It's....... different.
I have taken the time to simplify some of the steps for everyone, and built the required file myself.
I used TWRP 2.8.0.0 "img" file from their website. All development credit go to TeamWin, I've just converted it to the proper file format for Heimdall.
Before reading farther, please remember:
ALL FLASHING IS DONE AT ONE's OWN RISK, I'M NOT RESPONSIBLE.
Please take adequate precautions to be able to recover your device from a soft brick.
I used the Pit mapping for the T210. The recovery partition is "mmcblk0p10." I checked the partition info on my T210R using Partition Table by Lakshman. The T210R also has its Recovery partition on "mmcblk0p10," so I expect it to work no problem. And TWRP Odin flashables tend to be compatible with several 7.0 variants.
1. Open Heimdall. Reboot your device into download mode (power+volume down+home, then volume up).
2. Attach tablet to computer.
3. Select "Load Package" tab if it isn't already.
4. Click the "Browse" button under "Heimdall Firmware Package."
5. Select the ".tar.gz" file attached to this thread.
6. Click "Load/Customize." This will jump you to the "Flash" Tab.
7. Make sure that the "Repartition" check-box is unselected.
8. Click "Flash."
9. After flashing, reboot into your new recovery and install SuperSU and BusyBox.
As of this point, I have not been able to test this. I hope it goes well for anyone who tries it
Update:
As of now, I have been able to test this file on my own T210R. I already had this version of TWRP installed, so can't confirm actual update, but Heimdall said it flashed, and it didn't brick it, so I'd say good to go! (Take appropriate precautions anyways, because you never know what will happen.)
Click to expand...
Click to collapse
You say you took TWRP from TeamWin's website? Can you show me that, because I'm pretty sure they don't support this device.

gr8nole said:
You say you took TWRP from TeamWin's website? Can you show me that, because I'm pretty sure they don't support this device.
Click to expand...
Click to collapse
Maybe not their official website... oops.
The file I used you've uploaded... my mistake, thought you were part of their project.

Well the TWRP image file worked well enough for me... Either way...
I think this is the main way to root the T210(R) if updated to KitKat. Since it is quite possible that it's the last update it's ever going to see, I'd say it's good time to root it now and put Xposed on it for good measure.

xaueious said:
Well the TWRP image file worked well enough for me... Either way...
I think this is the main way to root the T210(R) if updated to KitKat. Since it is quite possible that it's the last update it's ever going to see, I'd say it's good time to root it now and put Xposed on it for good measure.
Click to expand...
Click to collapse
This version of TWRP is still compatible with JellyBean. I restored and booted my stock OS using this flash. And this is the same method that I had used to root before the update. (using Odin rather than Heimdall though.)

@Greaper88 did you test other files to confirm that functionality is working well (just curious) ?
Heimdall is interesting tool but i haven't tested it myself.

mkaymuzik said:
@Greaper88 did you test other files to confirm that functionality is working well (just curious) ?
Heimdall is interesting tool but i haven't tested it myself.
Click to expand...
Click to collapse
Do you mean other Heimdall installer files?
I've not tested other files as I've only messed with my Tab 3, and any flash files have to be built from a raw ".img" (image) file and the device's PIT (Partition Information Table). This presents challenges that I haven't tried to overcome.
I saw a request somewhere in another thread for a walkthrough on rooting the Tab 3 with Heimdall, and I figured out and posted this since it was only the recovery, and that much was actually somewhat easy.
My idea was, if you get custom recovery, you can then install your choice of ROM. Although I don't know if there is a TWRP flashable stock KK ROM yet...
I'm confident that the method in this thread for mentioned devices works based on my own flash and on "xaueious'" posts.
To port this method to other devices, one just needs the device's PIT and the recovery image file, "recovery.img" for example in order to build a flash file. The process is actually easy once you know how.
Full ROMs would be more difficult I think because there are other files besides ".img" files that have to be written to the flash, and a XML file has to be built as well to handle all of that. I haven't had time to mess with all of that...

Greaper88 said:
Do you mean other Heimdall installer files?
I've not tested other files as I've only messed with my Tab 3, and any flash files have to be built from a raw ".img" (image) file and the device's PIT (Partition Information Table). This presents challenges that I haven't tried to overcome.
I saw a request somewhere in another thread for a walkthrough on rooting the Tab 3 with Heimdall, and I figured out and posted this since it was only the recovery, and that much was actually somewhat easy.
My idea was, if you get custom recovery, you can then install your choice of ROM. Although I don't know if there is a TWRP flashable stock KK ROM yet...
I'm confident that the method in this thread for mentioned devices works based on my own flash and on "xaueious'" posts.
To port this method to other devices, one just needs the device's PIT and the recovery image file, "recovery.img" for example in order to build a flash file. The process is actually easy once you know how.
Full ROMs would be more difficult I think because there are other files besides ".img" files that have to be written to the flash, and a XML file has to be built as well to handle all of that. I haven't had time to mess with all of that...
Click to expand...
Click to collapse
Thx for the info mate. Going test this out.

I'm lost, I was working on my hubby's tablet and somehow the backup I made got wiped when I tried to Samsung Galaxy Tab 3 7.0 WiFi SM-T210/T210R Performance Upgrade MOD. I'm assuming that it doesn't work under KitKat as I was running TranchidaKat v2.2 [4.4.2 SM-T210/R Rom. Anyway whatever I did no matter what I wipe I keep getting one error from Odin, ""can't mount ES' I'd sure appreciate a hand on this thing if your around. I've been trying to run Heimdall but it always fails in Odin. What really confused me on your directions is you saying to open the package and select Load the Package. I'm not sure exactly what that means but I have Odin 3.07 through 3.10 and I don't see anything like that, could you clarify. I can load the regular 2.8 TWRP using the img file that has nothing to do with Heimdall so I can get into recovery but that's where I'm stuck. Any thoughts???
Krissy

Odin is leaked Samsung Software. Heimdall is an open source substitute, and is not related to Odin. Heimdall requires the TWRP file posted in the OP in this thread to work, but it will not work in Odin.
If you have a custom recovery installed that you can boot into, check out:
http://forum.xda-developers.com/gal...-stock-sm-t210r-4-1-2-jellybean-twrp-t2951850
If you've lost your backup files, then these ones might work for you unless the device flash has been overly corrupted.
If that doesn't work, check out:
http://forum.xda-developers.com/galaxy-tab-3/general/tab-3-7-0-sm-t210-r-stock-4-4-2-kitkat-t2930075
That's intended to be flashed directly from Odin, and will make the device stock KitKat.
I then like to use the Werewolf Kernel, since it overclocks the Tablet and improves overall speed that way.
Other thoughts: have you tried another USB cable/port? I've had similar errors simply because Odin didn't like my USB cable, or the USB port I was connected to.

OPO can't boot into custom recovery CM11.0

Hello all!
Newly registered here, has been lurking around for some time though.
I just received my replacement OnePlus due to the death of the first one and wanted to do a custom recovery and install Oxygen or Carbon for a little better battery life and back up possibilities.
My problem is: I can't get the phone to boot into recovery.
I did some research and people mentioned trying TWRP and PhilZ's recoveries - those had no result for me.
I have followed official video from OnePlus and also tried C4ETech's way for those two mentioned above.
The ones I tried were PhilZ's 6.50.2 and 6.58.8, for TWRP I used 2.8.5.1 and 2.8.4.1
Tried to do it with OPO toolbox and that didn't work either (TWRP, CWM, PhilZ tested)- all the functions would work, but once I flash the phone - it would boot into stock CM11.
When I try to boot it into recovery, it would stay on the first logo for 7-8 seconds, after that vibrates again and goes into stock CM11.
The same would happen if I go to advanced boot and boot into recovery.
I have changed the options under Developers folder as required already.
I have tried flashing the phone on two computers - win7 x64 and Win 8.1 x64.
Any help would be appreciated.
I have the phone for almost two weeks already and still can't ring myself to setting it up because of previous experience of data loss. (not worried about pictures - those are on Gdrive )

format c:\ said:
Hello all!
Newly registered here, has been lurking around for some time though.
I just received my replacement OnePlus due to the death of the first one and wanted to do a custom recovery and install Oxygen or Carbon for a little better battery life and back up possibilities.
My problem is: I can't get the phone to boot into recovery.
I did some research and people mentioned trying TWRP and PhilZ's recoveries - those had no result for me.
I have followed official video from OnePlus and also tried C4ETech's way for those two mentioned above.
The ones I tried were PhilZ's 6.50.2 and 6.58.8, for TWRP I used 2.8.5.1 and 2.8.4.1
Tried to do it with OPO toolbox and that didn't work either (TWRP, CWM, PhilZ tested)- all the functions would work, but once I flash the phone - it would boot into stock CM11.
When I try to boot it into recovery, it would stay on the first logo for 7-8 seconds, after that vibrates again and goes into stock CM11.
The same would happen if I go to advanced boot and boot into recovery.
I have changed the options under Developers folder as required already.
I have tried flashing the phone on two computers - win7 x64 and Win 8.1 x64.
Any help would be appreciated.
I have the phone for almost two weeks already and still can't ring myself to setting it up because of previous experience of data loss. (not worried about pictures - those are on Gdrive )
Click to expand...
Click to collapse
Are you checking the md5 of the recovery files after downloading to ensure that they haven't become corrupt during the download? Exactly which recoveries have you flashed (full filenames please)? Also, is the flash with fastboot definitely succeeding? I'd suggest not using a toolkit because they inevitably cause problems.

Heisenberg said:
Are you checking the md5 of the recovery files after downloading to ensure that they haven't become corrupt during the download? Exactly which recoveries have you flashed (full filenames please)? Also, is the flash with fastboot definitely succeeding? I'd suggest not using a toolkit because they inevitably cause problems.
Click to expand...
Click to collapse
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.

format c:\ said:
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.
Click to expand...
Click to collapse
Forgot to add philz_touch_6.50.2-bacon and philz_touch_6.58.8-bacon were used.

format c:\ said:
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.
Click to expand...
Click to collapse
Is there any reason you're flashing older versions of TWRP? They're pretty outdated now. Grab the latest version from here:
https://dl.twrp.me/bacon/twrp-2.8.7.0-bacon.img.html
As long as it says it's successful in the terminal window it should have flashed ok. What build of CM is currently on your phone?

Heisenberg said:
Is there any reason you're flashing older versions of TWRP? They're pretty outdated now. Grab the latest version from here:
As long as it says it's successful in the terminal window it should have flashed ok. What build of CM is currently on your phone?
Click to expand...
Click to collapse
It did work! Now I'm a happy camper Trying to install Oxygen right now.
It was on 11.0. My old phone was running that OS as well, but it was having issues with screen artifacts I have upgraded to 12.0 and system was running fine for 2 day, after that screen died completely. Buttons at the bottom of the phone were working, but it looked like just the back light was on.
Huge thanks to you, Heisenberg!

I was flashing older versions, because I found only those from the official video link. It sent me to techerrata page and the latest one over there was and still is 2.8.5.1

format c:\ said:
It did work! Now I'm a happy camper Trying to install Oxygen right now.
It was on 11.0. My old phone was running that OS as well, but it was having issues with screen artifacts I have upgraded to 12.0 and system was running fine for 2 day, after that screen died completely. Buttons at the bottom of the phone were working, but it looked like just the back light was on.
Huge thanks to you, Heisenberg!
Click to expand...
Click to collapse
format c:\ said:
I was flashing older versions, because I found only those from the official video link. It sent me to techerrata page and the latest one over there was and still is 2.8.5.1
Click to expand...
Click to collapse
Awesome, very glad to see you got it working. I realised after my post that your current CM version is in the title of the thread, lol, oops. That Techarrata site doesn't get updated anymore as they have a new site now, so the latest builds can always be found here:
https://dl.twrp.me/bacon/

Desperately Trying to Port TWRP on this Stock Recovery !

Hey Guys,
I've been spending hours & hours to try to port TWRP (or PhilZ) to the stock recovery from my rugged BlackView BV5000.
Not going to explain the reasons here, as everyone knows them already (my top-of-the-list reason being the ability to ghost & root my device), but I've managed to get the stock recovery from the manufacturer, and have been using some tools to *auto-port* CWM/TWRP/PHILZ to the stock recovery.img file without success.
File available here: https://mega.nz/#!y1plzQgR!irTUJbdpHYuqGJ3dV8ACOXZBlvuTK1S-pag_EbZJETU
I am asking for all people with more experience than me in porting or coding Android files for some kind help... Hope someone could bring light on us! ^_^
Cheers!
Nick.

Surfeur-des-Reves said:
Hey Guys,
I've been spending hours & hours to try to port TWRP (or PhilZ) to the stock recovery from my rugged BlackView BV5000.
Not going to explain the reasons here, as everyone knows them already (my top-of-the-list reason being the ability to ghost & root my device), but I've managed to get the stock recovery from the manufacturer, and have been using some tools to *auto-port* CWM/TWRP/PHILZ to the stock recovery.img file without success.
File available here: https://mega.nz/#!y1plzQgR!irTUJbdpHYuqGJ3dV8ACOXZBlvuTK1S-pag_EbZJETU
I am asking for all people with more experience than me in porting or coding Android files for some kind help... Hope someone could bring light on us! ^_^
Cheers!
Nick.
Click to expand...
Click to collapse
I hope you are aware of this tool: Easy TWRP Installer
It creates TWRP and auto flashes it to your phone with 1 click.
Just plug your phone in and press start.
Violla. You have TWRP.

janekmuric said:
I hope you are aware of this tool: Easy TWRP Installer
It creates TWRP and auto flashes it to your phone with 1 click.
Just plug your phone in and press start.
Violla. You have TWRP.
Click to expand...
Click to collapse
Hi
Of course I tried this one you mention, as well as several others (for PhilZ, CWM...) and the result was same, it ends up with some errors and impossible to continue the operation. Moreover, most of these tools require a rooted device, and this one cannot be rooted at the moment by any automatic tool.... This is also one of the reasons I request a custom recovery

Surfeur-des-Reves said:
Hi
Of course I tried this one you mention, as well as several others (for PhilZ, CWM...) and the result was same, it ends up with some errors and impossible to continue the operation. Moreover, most of these tools require a rooted device, and this one cannot be rooted at the moment by any automatic tool.... This is also one of the reasons I request a custom recovery
Click to expand...
Click to collapse
You are requesting a custom recovery which to be flashed requires root.

janekmuric said:
You are requesting a custom recovery which to be flashed requires root.
Click to expand...
Click to collapse
Not really, I can always flash with SP Flash Tools, as I have the full factory ROM, the scatter & original stock recovery.img
Link is here: https://mega.nz/#!y1plzQgR!irTUJbdpHYuqGJ3dV8ACOXZBlvuTK1S-pag_EbZJETU
I wish someone skilled in the process could help us...

Surfeur-des-Reves said:
Not really, I can always flash with SP Flash Tools, as I have the full factory ROM, the scatter & original stock recovery.img
Link is here: https://mega.nz/#!y1plzQgR!irTUJbdpHYuqGJ3dV8ACOXZBlvuTK1S-pag_EbZJETU
I wish someone skilled in the process could help us...
Click to expand...
Click to collapse
The Magic TWRP Installer can create a recovery.img file which you can flash with SP Flashtool. Could you please explain what exactly errors are you getting? I think there is a higher chance of success if we try to resolve the issue with TWRP installer, than if you just kept asking for help.

janekmuric said:
The Magic TWRP Installer can create a recovery.img file which you can flash with SP Flashtool. Could you please explain what exactly errors are you getting? I think there is a higher chance of success if we try to resolve the issue with TWRP installer, than if you just kept asking for help.
Click to expand...
Click to collapse
There were 2 kinds of errors; the first one being about "regions overlapping", and the second one being with "magic headers"...

BV5000 Root
Surfeur-des-Reves said:
this one cannot be rooted at the moment by any automatic tool
Click to expand...
Click to collapse
Hey, it is extremely easy to root the BV5000. Just copy this attached file to an external SD (it might work if in internal memory but I haven't tried it).
Settings => About Phone => Wireless Updates => 3 dots (Menu Key) => Local Updates => Browse and select the update.zip file and wait till the phone reboots.
The file and method are taken from a thread in movilesdualsim.com.
Enjoy

I made Philz and carliv CWM ages ago for this phone

bigrammy said:
I made Philz and carliv CWM ages ago for this phone
Click to expand...
Click to collapse
Probably it was part of your secret project ( or your are Hanuma50.... ? ).....because obviously working custom recovery is downloadable only from 4pda.ru - if you know the Russian numbers what is needed for the registration....
The above mentioned update.zip method does not work on newer firmwares ( t.e. v.1.5.) of BV5000.
For those who are not familiar with the soul of MTK devices here is a description of the installation process to get TWRP and thereafter root on the phone:
( use google translator):
http://mdforum.ru/showthread.php?t=26183
(It does not matter that description relates to MT6592 devices!)
custom recovery + scatter file of firmware v.1.5 + SuperSu ( + some others, t.e. SP Flashtools, etc):
https://drive.google.com/file/d/0BzkbIWPgNcg7VlNiWHNWOG5iQ0E/view?usp=sharing

bandino said:
Probably it was part of your secret project ( or your are Hanuma50.... ? ).....because obviously working custom recovery is downloadable only from 4pda.ru - if you know the Russian numbers what is needed for the registration....
The above mentioned update.zip method does not work on newer firmwares ( t.e. v.1.5.) of BV5000.
Click to expand...
Click to collapse
I wanted to see how long it would take them to make their own working recovery. :laugh:
A lot of the time 4PDA and other forums seem to give no credit or links to the original dev's.
Lucky for them they have @hanuma who is a Great dev so credit to him for getting the TWRP working. Well done bro. :highfive:
You should link to @hanuma or one of his posts so people can give him Thanks also you should really asked his permission to post the mirror link to the recovery.

bigrammy said:
I wanted to see how long it would take them to make their own working recovery. :laugh:
A lot of the time 4PDA and other forums seem to give no credit or links to the original dev's.
Lucky for them they have @hanuma who is a Great dev so credit to him for getting the TWRP working. Well done bro. :highfive:
You should link to @hanuma or one of his posts so people can give him Thanks also you should really asked his permission to post the mirror link to the recovery.
Click to expand...
Click to collapse
I have got his permission for public his work here.
Direct link for downloading and for thanks:
http://4pda.ru/forum/index.php?showtopic=685816&st=840#entry44610609