Database Develop

[Q] wtf. I just CAN NOT get my phone into recovery mode

I was on Continuum and decided to flash back to stock. Of course Odin would freeze, forcing me to break out my jig.
I finally got it into download mode and flashed back to stock
I used SuperOneClick (like I have so many times before) to root and enable non-market installations
Well, it rooted just fine, but I couldn't enable the non-market stuff, it says "reloc_library[1251]: 2738 cannot locate '_ZNK7android6Parcel15setDataPositionEj'... CANNOT LINK EXECUTABLE
I cant get my captivate into recovery through 3-button boot, and ROM manager is completely unresponsive. When I click "reboot into recovery" it just does nothing. Same with installing a rom, or restoring a back-up. Any ideas?

Hmmm... It sounds like you might need to reflash the phone...
Can you try this alternate method to put your phone into Download Mode?
1. Turn off your phone, pull out the battery.
2. Hold both volume UP and DOWN buttoms (and keep holding them until the end).
3. Put in your battery.
4. Plug in the USB. (You won't need to ever press the power button using this method).
If that doesn't work, you might need to get a USB Jig somewhere (either buying one or making one yourself).

this can help, 3 button fix http://forum.xda-developers.com/showthread.php?t=812434

I think you missed the point where he said Rom Manager or CWM Recovery isn't working.

venomio said:
I think you missed the point where he said Rom Manager or CWM Recovery isn't working.
Click to expand...
Click to collapse
omg. I love you for that comment. I KNEW, just knew some idiot was going to say that. "um..blah blah..3buttonfix...blah"

demonblod said:
omg. I love you for that comment. I KNEW, just knew some idiot was going to say that. "um..blah blah..3buttonfix...blah"
Click to expand...
Click to collapse
If you are not bricked (means phone-!-computer screen) then you can use ADB method to go into recovery then just reinstall CWM.zip folder...that works for me....see the link for youtube video tutorial. if u need Clockworkrecovery.zip..just hollar
http://www.youtube.com/watch?v=2fMk0PhA_qc&feature=relmfu

demonblod said:
omg. I love you for that comment. I KNEW, just knew some idiot was going to say that. "um..blah blah..3buttonfix...blah"
Click to expand...
Click to collapse
nothing to say. just want to help. if it's not, dont need that aggressive. hope u can fix it

viny2cool said:
If you are not bricked (means phone-!-computer screen) then you can use ADB method to go into recovery then just reinstall CWM.zip folder...that works for me....see the link for youtube video tutorial. if u need Clockworkrecovery.zip..just hollar
http://www.youtube.com/watch?v=2fMk0PhA_qc&feature=relmfu
Click to expand...
Click to collapse
Not really sure if it would work, but I guess it depends on if he can get the phone's USB Debugging menu to turn on.

venomio said:
Not really sure if it would work, but I guess it depends on if he can get the phone's USB Debugging menu to turn on.
Click to expand...
Click to collapse
He didnt brick it, just not able to flash recovery or enable non market apps...so he can turn on USB debugging

viny2cool said:
He didnt brick it, just not able to flash recovery or enable non market apps...so he can turn on USB debugging
Click to expand...
Click to collapse
It's the "non market app" part that's concerning me. If he gets an error with that, you can't say for sure that he won't get another error with USB Debugging.

venomio said:
It's the "non market app" part that's concerning me. If he gets an error with that, you can't say for sure that he won't get another error with USB Debugging.
Click to expand...
Click to collapse
that's him to answer now...lol

demonblod said:
I was on Continuum and decided to flash back to stock. Of course Odin would freeze, forcing me to break out my jig.
I finally got it into download mode and flashed back to stock
I used SuperOneClick (like I have so many times before) to root and enable non-market installations
Well, it rooted just fine, but I couldn't enable the non-market stuff, it says "reloc_library[1251]: 2738 cannot locate '_ZNK7android6Parcel15setDataPositionEj'... CANNOT LINK EXECUTABLE
I cant get my captivate into recovery through 3-button boot, and ROM manager is completely unresponsive. When I click "reboot into recovery" it just does nothing. Same with installing a rom, or restoring a back-up. Any ideas?
Click to expand...
Click to collapse
well if you're on stock you can't enable non market app it's not included in the package plain and simple. but if you can push update zip into your internal sd and flash cwm recovery you maybe able to flash an app apk's there. the problem is you have unresponsive button combos. solve the button combos first. you will likely need a jig or if you can get into download mode try installing the leaked froyo maybe it will solve your unresponsive buttons.

3.41 bootloader info from google support

Well I decided to call Google about the boot loader recovery not working as it should. I was hoping this call would help them to work on another update but they say that's the way its supposed to work. Here's the email Instructions:
1. Power down your device
2. Press and hold both volume keys and the power button to enter
Bootloader mode
3. Press the volume keys to cycle to the Recovery mode option
4. Press the power button to select Recovery mode
5. From the Recovery mode screen, press and hold the Power button then
press the Volume up button.
6. Use the volume buttons to select wipe data/factory reset.
7. Select Yes -- delete all user data.
8. The factory data reset process will now start. Once its finished,
select 'Reboot system now.'
The only option we have in the new recovery is to wipe data. Maybe for those having problems accessing twrp or cwm will be able to a access it with step 5. I don't know haven't rooted yet. So I decided to ask about nvflash and they said they're not going to release any nvflash tools or files.

um, yup. thats how stock bootloader and stock recovery work. lol
whats the issue? if your not even rooted, you wouldn't even know if you have an issue or not with the new bootloader.

Are you saying that you can't flash a different recovery? Or that when you do you still get the same stock recovery? I'm not quite sure what the issue is here, because that is exactly how the stock bootloader, and recovery are supposed to work.
Are you making sure to unlock fastboot before trying to flash recovery. I don't recall seeing or hearing anyone say anything about not being able to get to clockwork mod once its installed.

xjman said:
Are you saying that you can't flash a different recovery? Or that when you do you still get the same stock recovery? I'm not quite sure what the issue is here, because that is exactly how the stock bootloader, and recovery are supposed to work.
Are you making sure to unlock fastboot before trying to flash recovery. I don't recall seeing or hearing anyone say anything about not being able to get to clockwork mod once its installed.
Click to expand...
Click to collapse
No. I saw people posting they couldn't get go cwm and could only see the red exclamation point. And I was just saying maybe after choosing recovery then holding volume up and power it would then go to cWm or twrp. I was hoping for someone to try it who is still on 3.41 Recovery. A lot of people downgraded back to 3.39 or whatever version it was

kieso said:
I was hoping for someone to try it who is still on 3.41 Recovery. A lot of people downgraded back to 3.39 or whatever version it was
Click to expand...
Click to collapse
I can confirm that to get in to the stock recovery you hold down 'power' and then tap 'vol up'.
At present I am running the latest CWM touch recovery. This boots straight into it from the bootloader without any extra button presses.
My personal preference to go into CWM is from either QuickBoot or ROM Manager.
Sent from my Nexus 7 using xda app-developers app

smirkis said:
didn't know being informed makes me an asshole. stupid me, reading and understanding.
for what its worth, im on the newest bootloader, and selecting recovery goes straight to twrp. which is the recovery i installed.
Click to expand...
Click to collapse
I wonder why some on 3.41 can't go straight to twrp and some can. Sorry for the ahole comment I thought you were trying to be a smartass towards me. I'm just trying to find out as much info from people before I root. I am experienced at flashing and a little adb but I just read a lot of HELP BRICKED MY NEXUS posts. Did you use wugs toolkit or adb to unlock and root?

mr_tris said:
I can confirm that to get in to the stock recovery you hold down 'power' and then tap 'vol up'.
At present I am running the latest CWM touch recovery. This boots straight into it from the bootloader without any extra button presses.
My personal preference to go into CWM is from either QuickBoot or ROM Manager.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info. I'm going to try unlocking and rooting when I get home. I really want to use the OTG cable and the 720p mod.

kieso said:
I wonder why some on 3.41 can't go straight to twrp and some can. Sorry for the ahole comment I thought you were trying to be a smartass towards me. I'm just trying to find out as much info from people before I root. I am experienced at flashing and a little adb but I just read a lot of HELP BRICKED MY NEXUS posts. Did you use wugs toolkit or adb to unlock and root?
Click to expand...
Click to collapse
When I first flashed TWRP onto my Nexus 7 after that official 4.1.2 OTA update, I wasn't able to boot into it. I then flashed it again via fastboot, and then booted the TWRP image that was on my computer, and then TWRP loaded.
I believe TWRP does work normally now as well (I can boot into it and reboot into it).

kieso said:
I'm going to try unlocking and rooting when I get home.
Click to expand...
Click to collapse
Well if I was you I'd just use mskips toolkit, its absolutely epic it'll save you a lot of farting around. I take it that your fully updated? ( Not that it matters) You seem to know and understand your way around adb so just go for it and enjoy.
Its works smooth as silk and save you a lot off time. The options available to you are just staggering!
http://forum.xda-developers.com/showthread.php?t=1809195
Sent from my Nexus 7 using xda app-developers app

Thread Cleaned​
No need for personal insults, lets just try to help each other out and show each other some respect.​

going to recovery from bootloader works fine after 3.41.....wat r u talkin abt? (i m stock rooted+twrp)
oh yea...u hav 2 remove that recovery stock.p file thingy first.

There are plenty of people that are having issues with recovery on 3.41 bootloader.... Its confirmed some have it some don't.
The issue is that with 3.41 bootloader on some Nexus 7 Devices a custom recovery is unbootable no matter how you try, every time it will try to load recovery and fail at a black screen then reboot into the OS. It does not matter how you try from ADB reboot to recovery or from bootloader with USB attached or not.

psycho2097 said:
going to recovery from bootloader works fine after 3.41.....wat r u talkin abt? (i m stock rooted+twrp)
oh yea...u hav 2 remove that recovery stock.p file thingy first.
Click to expand...
Click to collapse
Ohh crap I read about that in some thread. Any idea exactly what has to be done. The only way I can get into cwm is with ROM toolbox but I have to reflash cwm every time then hit boot into recovery.

kieso said:
Ohh crap I read about that in some thread. Any idea exactly what has to be done. The only way I can get into cwm is with ROM toolbox but I have to reflash cwm every time then hit boot into recovery.
Click to expand...
Click to collapse
In your system folder there's a file called 'recovery-from-boot.p'
Go into a file manager with w/r access and rename it ' recovery-from-boot.p.bak'
When the system boots it reads that file and resets the recovery to stock, by changing the name you remove the problem.
Sent from my Nexus 7 using xda app- app developers

mr_tris said:
In your system folder there's a file called 'recovery-from-boot.p'
Go into a file manager with w/r access and rename it ' recovery-from-boot.p.bak'
When the system boots it reads that file and resets the recovery to stock, by changing the name you remove the problem.
Sent from my Nexus 7 using xda app- app developers
Click to expand...
Click to collapse
Thank you for all the help! I appreciate it.

kieso said:
Thank you for all the help! I appreciate it.
Click to expand...
Click to collapse
No problem, a click on the 'Thanks' button for me and my colleagues on this thread would really make our day. :thumbup:
I hope you get sorted mate, I wouldn't be able to sleep at night until I got custom recovery working properly on any of my devices!
Sent from my Nexus 7 using xda app-developers app

i tried changing the name of the file, but.. after reboot, the tablet gets stuck on google screen, recovery never loads... any suggestion? Thanks =)

[Recovery] & [Root] [T211] TWRP 2.7.1.0.KK Unofficial

READ THIS POST BEFORE INSTALLING ANY CUSTOM RECOVERY
Updated to version 2.7.1.0.KK on 10-28-14. Now works with KitKat (and older JB) bootloaders.
Now properly supports all set_metadata functions in newer updater-scripts.
Click HERE for the latest version.
Please report any bugs here in this thread.
Please take a moment to say thanks and/or donate to @ketut.kumajaya for helping us out.
I have a T210R, so I haven't tested on a T211.
Credits go to:
@ketut.kumajaya for working kernel
@Jamison904 for giving us root
@hkjr for getting ketut to help
and of course the Team Win group
Instructions for ODIN
1. Download ODIN on your computer.
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program. Un-check Auto Reboot. See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them).
7. Select "PDA" then choose the recovery file you want to flash.
8. Hit "START". Wait for Odin to finish (~10-15 seconds). The message area will display "RES OK" when finished.
9. Wait for device to restart. Skip this step if you unchecked auto reboot.
10. Restart directly to recovery mode before rebooting into OS.(Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen).
After you get the custom recovery working, you can flash the latest SuperSu zip to get root.
Your internal SDcard will get mounted as "/data/media". So look there for any files saved to the internal card.
Notes about ODIN
--Make sure that "Re-Partition" is NOT checked.
--Auto Reboot can be un-checked if TWRP doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 10).
Instructions for recovery flashable version:
Boot into your previously installed custom recovery.
Select the Install Zip option.
Find the recovery zip.
Flash.
Reboot recovery.
Enjoy your new recovery.
Flash at own risk!!!!
+++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++
Click HERE for the latest version.

Reserved

sormat1 from 4PDA reported:
Sorry, qiuck Translate by Google:
Loaded, but the buttons do not match the strong places of pression, which will invoke the appropriate menu button.
The same is within of menu: you press on an arbitrary place, but opens something another.
Click to expand...
Click to collapse
See: http://4pda.ru

Dasdranamin said:
sormat1 from 4PDA reported:
Sorry, qiuck Translate by Google:
See: http://4pda.ru
Click to expand...
Click to collapse
Thanks for the report, will look into it.

Hey @ketut.kumajaya, it seems the touchscreen needs to be rotated for this one. I would attempt to fix it, but we all know you can do it much, much better (and I don't want to start all over without your kernel source)
EDIT: I used the new zImage from the 1.8 T210(R) version in my T210(R) TWRP and the touchpoints are off in it as well. Looks like the previous touch orientation fix you made got overwritten with the new update.
Looks like it only needs to be rotated clockwise 90 degrees (not flipped, just rotated).

gr8nole said:
Hey @ketut.kumajaya, it seems the touchscreen needs to be rotated for this one. I would attempt to fix it, but we all know you can do it much, much better (and I don't want to start all over without your kernel source)
EDIT: I used the new zImage from the 1.8 T210(R) version in my T210(R) TWRP and the touchpoints are off in it as well. Looks like the previous touch orientation fix you made got overwritten with the new update.
Looks like it only needs to be rotated clockwise 90 degrees (not flipped, just rotated).
Click to expand...
Click to collapse
Did you set the touchscreen orientation to landscape?
Code:
write /sys/devices/virtual/sec/tsp/orientation 6

ketut.kumajaya said:
Did you set the touchscreen orientation to landscape?
Code:
write /sys/devices/virtual/sec/tsp/orientation 6
Click to expand...
Click to collapse
How do I set that for the recovery? init.rc?
Sent from my DROID RAZR MAXX HD

gr8nole said:
How do I set that for the recovery? init.rc?
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
Like this: http://forum.xda-developers.com/showpost.php?p=39935850&postcount=89

ketut.kumajaya said:
Like this: http://forum.xda-developers.com/showpost.php?p=39935850&postcount=89
Click to expand...
Click to collapse
Ha...it was already in there, but it was commented out.:laugh:

Dasdranamin said:
sormat1 from 4PDA reported:
Sorry, qiuck Translate by Google:
See: http://4pda.ru
Click to expand...
Click to collapse
New version uploaded with touchscreen orientation fixed.

gr8nole said:
New version uploaded with touchscreen orientation fixed.
Click to expand...
Click to collapse
Thank You.
All works properly! :good:

It works for me.
Thank you very much.

only worked with external sd attached....without it, the recovery cannot read internal sdcard...cmiiw...

godh3ll said:
only worked with external sd attached....without it, the recovery cannot read internal sdcard...cmiiw...
Click to expand...
Click to collapse
Not true...your internal SDcard is mounted as "/data/media". Navigate to that folder and you will find everything on your internal card. You will have to hit the "Up one level" button to find it.
EDIT: I will add a note to the OP about this.

Now that there's root and recovery, has anyone flashed a successful ROM for the T211?

gr8nole said:
Not true...your internal SDcard is mounted as "/data/media". Navigate to that folder and you will find everything on your internal card. You will have to hit the "Up one level" button to find it.
EDIT: I will add a note to the OP about this.
Click to expand...
Click to collapse
Yup my mistaken...the zip was there in media folder..
BiG JeW said:
Now that there's root and recovery, has anyone flashed a successful ROM for the T211?
Click to expand...
Click to collapse
Off course, I flashed the only ROM for T211, infamous combined with black hawk kernel..
Sent from my SM-T211 using Tapatalk 4 Beta

godh3ll said:
Yup my mistaken...the zip was there in media folder..
Off course, I flashed the only ROM for T211, infamous combined with black hawk kernel..
Sent from my SM-T211 using Tapatalk 4 Beta
Click to expand...
Click to collapse
you did how does this rom work any performance improvements any issues .. i want to flash it myself

jetboss said:
you did how does this rom work any performance improvements any issues .. i want to flash it myself
Click to expand...
Click to collapse
Didnt test all the function yet...but stable for daily use, still laggy sometimes, I wonder when we got official 4.2 or skip to 4.4? Anyhow, just test the rom yourself based on cuŕiosity..
Sent from my SM-T211 using Tapatalk

godh3ll said:
Didnt test all the function yet...but stable for daily use, still laggy sometimes, I wonder when we got official 4.2 or skip to 4.4? Anyhow, just test the rom yourself based on cuŕiosity..
Sent from my SM-T211 using Tapatalk
Click to expand...
Click to collapse
might just have to do that well from seeing the requirements on kit kat i believe we will get an official update but when i dont know Samsung kinda slow when releasing updates so just hoping some devs do something soon

sorry sir, i try using this cwm but fail in progress. Now my startup just say "firmware upgrade encountered an issue. please select recovery mode in kies & try again".
Would shut i do sir.
Thanks

xposed on Samsung tab G SM-t810 ANdroid v5.1.1

Hi,
My device is : Samsung Galaxy Tab S2 , Android 5.1.1.
MY question is : How Do I install xposed on this device and android Version.
I am Root, I tested it with the root tester.
I tryed to go in recovery mode by pressing Power + Volume up + Home button ----: That bring me to a Blue-green screen who said " Downloading, Do not turn off target "
I have xposed installer apps installed, cant click on Install/Update, because I have a red message " Xposed isn't compatible with android SDK version 22.
So i try to flash it, so as I said, I cant go to recovery mode, to flash this framework :
" http://forum.xda-developers.com/xposed/xposed-android-5-1-successfully-t3074586 "
can some1 help me with this? because I dont understand what is a " TWRP Recovery"
Thanks

help?
any1 can help me ?

If this helps great, if not oh well. To note I have the WiFi only version t810 and you have maybe a typo gsm in tittle. As much help I'm willing to offer. Google does wonders if you get stuck.
I guess you arent rooted.
Click on the guide link in post to get rooted and twrp recovery.
http://forum.xda-developers.com/showthread.php?p=62520653
After all that install xposed. used sdk 22 arm
http://forum.xda-developers.com/showthread.php?p=62377731

hi
Torrentula81 said:
If this helps great, if not oh well. To note I have the WiFi only version t810 and you have maybe a typo gsm in tittle. As much help I'm willing to offer. Google does wonders if you get stuck.
I guess you arent rooted.
Click on the guide link in post to get rooted and twrp recovery.
http://forum.xda-developers.com/showthread.php?p=62520653
After all that install xposed. used sdk 22 arm
http://forum.xda-developers.com/showthread.php?p=62377731
Click to expand...
Click to collapse
i am root and the xposed sdk 22 arm version didnt work cuz I can't go into the flash menu when I restart my menu, like I said in the post message.

Then instal twrp so you can instal it like I said in my message. Didn't know one could root without a recovery. Not very smart at all. With exposed you can actually hide apps from the system itself like removing you're keyboard and all menu options it ever existed. You will NEED a recovery period. So instal twrp like said in the post or stop asking for help.
Sent from my SM-T810 using XDA-Developers mobile app

thx
Torrentula81 said:
Then instal twrp so you can instal it like I said in my message. Didn't know one could root without a recovery. Not very smart at all. With exposed you can actually hide apps from the system itself like removing you're keyboard and all menu options it ever existed. You will NEED a recovery period. So instal twrp like said in the post or stop asking for help.
Sent from my SM-T810 using XDA-Developers mobile app
Click to expand...
Click to collapse
I dont know what a recovery is , is it the menu when I restart my devive with holding power + home + volume down ?

hi
salopes said:
I dont know what a recovery is , is it the menu when I restart my devive with holding power + home + volume down ?
Click to expand...
Click to collapse
anyone?

salopes said:
I dont know what a recovery is , is it the menu when I restart my devive with holding power + home + volume down ?
Click to expand...
Click to collapse
TWRP is easy to find if you look.
http://forum.xda-developers.com/tab-s2/development/recovery-twrp-2-8-7-x-lollipop-5-1-1-t3205686
You may want to do a lot more research though before doing any of this. You can mess up your device so you may want to learn how to get it back to stock in case you have a problem.

Boot in root mode by default

Hi
At first Magisk app launch, it asked for download files for model than auto rebooted phone in root mode.
There is any way to boot in root mode by default?
Or wich command to use for reboot in root mode?

I would be interested in this, as well as not having to press the power button to pass the initial boot warning message.

LEENO said:
Hi
At first Magisk app launch, it asked for download files for model than auto rebooted phone in root mode.
There is any way to boot in root mode by default?
Or wich command to use for reboot in root mode?
Click to expand...
Click to collapse
thats bcuz ur already rooted so magisk is able patch n update itself directly then reboot or reboots recovery

elliwigy said:
thats bcuz ur already rooted so magisk is able patch n update itself directly then reboot or reboots recovery
Click to expand...
Click to collapse
But is there no way to patch for this to happen automatically each time do we're don't need the key combo?

riso123 said:
But is there no way to patch for this to happen automatically each time do we're don't need the key combo?
Click to expand...
Click to collapse
if u cant find it by searching then i assume not.. if theres a way im sure some ppl would post about it

elliwigy said:
if u cant find it by searching then i assume not.. if theres a way im sure some ppl would post about it
Click to expand...
Click to collapse
I did think that was the case. Judy thought I'd check as it seems like something people would want to work toward fixing.