Database Develop

[FIX] Enable download mode by force adb push update.zip without permission

MY Phone Condition:
My phone was previously install with voodoo rom and use clockwork recovery to restore to my stock rom that i backup and it crash half way.
My phone was hardware lock this mean no matter how i press the volume and power button , i will never get into download mode. non of the method posted work !
My phone cannot use "adb reboot download" because there is no OS and it was stuck in the recovery loop.
It does not have clockwork recovery because i formatted my internal sdcard
If i do have clockwork recovery and i use restore image or install new from zip , i still stuck in the recovery mode after reboot several times.
My phone does not mount to internal sdcard because i don't even know what i did on this part.
I believe i screw up my partition of the phone.
DO IT AT YOUR OWN RISK.
You need the Samsung USB driver and you can get it from Here
http://forum.xda-developers.com/showthread.php?t=728929
First Part
1. Download update.zip from the link below. This was post by another member.
The post is here http://forum.xda-developers.com/showthread.php?t=804305
2. Place the update.zip in tools folder so you can push it into your phone by using adb command
3. Plug usb into the phone and your phone should be on the Android system recovery <2e>
4. Use your volume button to select reinstall package, don't press power button yet.
5. constant "adb push update.zip /sdcard" from computer , you will get permission denied.
6. While you are constantly pushing the adb command from computer. press the power button on the phone so it install update.zip from sdcard.
7. This is the part where it force adb push into sdcard without permission
8. once the update.zip install completed. unplug the usb cable from the phone and take the battery out.
9. put the battery back to the phone then press on both volume button.
10. While holding both volume button , plug in your usb cable and it will boot to download screen.
If you need use Odin to flash your phone to original stock rom. Go to the Second Part

Second Part:
If you get black screen with only 4 light on the bottom after flashing from Odin.
Follow http://forum.xda-developers.com/showthread.php?t=728698
There should be T959-PDA.tar,T959-CSC.tar and T959-Phone.tar within the package.
Check "Re-Partition" , "Auto Reboot" and "F.Reset Time" check box. Use the PIT 0512 version. Use "PDA", "PHONE" and "CSC" from the link above.
After flashing with Odin, you will loose the download mode. repeat the first part and you are good to go.
Here is the link on rooting the phone
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Samsung_Galaxy_S_(Vibrant)

If your phone is hardware locked, how are you able to get into recovery? Hardware locked phone means no recovery and download mode.
Sent from my SGH-T959 using XDA App

mr2t32 said:
If your phone is hardware locked, how are you able to get into recovery? Hardware locked phone means no recovery and download mode.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
my hardware lock mean cannot use the button method to get into download mode and using adb reboot download does not help too.

Im pretty sure hardware lock does not mean no recovery. Just no button download mode
Sent from my SGH-T959 using XDA App

you saved my life man. thank you so much. this was the only thing that worked, after days of frustration

No, it means both.
Sent from my SGH-T959 using XDA App

muncknr said:
you saved my life man. thank you so much. this was the only thing that worked, after days of frustration
Click to expand...
Click to collapse
i was about to give up. i was trying to push update.zip and do adb reboot download left and right and no luck untill i found this method. It took me a week to figure it out

wildklymr said:
No, it means both.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
my recovery was working because i was stuck in the a loop. ya , this update.zip pretty much do both download mode and recovery mode.

What the point of this? Does the other thread not cover this??

Master™ said:
What the point of this? Does the other thread not cover this??
Click to expand...
Click to collapse
Are you asking or you are insulting ?

jaex said:
Are you asking or you are insulting ?
Click to expand...
Click to collapse
probably asking. Considering there is another thread on the same topic that has been on the front page for over a week now, with several pages of replies.
http://forum.xda-developers.com/showthread.php?t=804305
EDIT: So you were bricked and hardware locked and got yourself out of it? If thats the case then yets its different than that thread and why didn't you just come out and say it?

nermie said:
probably asking. Considering there is another thread on the same topic that has been on the front page for over a week now, with several pages of replies.
http://forum.xda-developers.com/showthread.php?t=804305
EDIT: So you were bricked and hardware locked and got yourself out of it? If thats the case then yets its different than that thread and why didn't you just come out and say it?
Click to expand...
Click to collapse
You figure it out after all. I already stated the condition of my phone ! My phone was pretty bricked at that point. There is way for me to push any files into the phone because i don't have permission and my phone will not go to download mode by using the volume button. It just stuck at recovery mode.
There are guide out there teach you to use "adb push download". This method only work if you are in your phone and you turn on debug mode. My phone crash at the clockwork recovery bootloader. Then i formated my internal sdcard that hold the clockwork. next i push a stock update.zip that does not have su and busybox so i lost the capability to push anything into the phone.
no download mode , no permission, no sdcard --> You tell me how can i use the method that post few week ago ?

muncknr said:
you saved my life man. thank you so much. this was the only thing that worked, after days of frustration
Click to expand...
Click to collapse
Thank You

Thank ! You save my phone !

unfortunately, i was one of those careless people to brick my phone via Voodoo.
Firstly, i tried to "FLASH" the disable_voodoo zip file via Clockwork, i put it in root, and never created any folders. i knew i had to disable voodoo before flashing but my steps were wrong.
sadly enough, my phone was also HW locked, so i got it exchanged. now im not using voodoo YET and i my new vibrant can handle OC and has the recovery/download mode via buttons.

atlaswingpasaway said:
unfortunately, i was one of those careless people to brick my phone via Voodoo.
Firstly, i tried to "FLASH" the disable_voodoo zip file via Clockwork, i put it in root, and never created any folders. i knew i had to disable voodoo before flashing but my steps were wrong.
sadly enough, my phone was also HW locked, so i got it exchanged. now im not using voodoo YET and i my new vibrant can handle OC and has the recovery/download mode via buttons.
Click to expand...
Click to collapse
i use shell to create the file that disable voodoo. after disable voodoo , i was able to do restore and install new rom unfortunately after restore or install new rom , it still reboot into recovery.

I also forgot to disable voodoo, and this was before there were fix instructions posted. So i basically effed up my phone to the point of being stuck in the samsung recovery loop, no hardware download mode, no clockwork recovery, no update.zp, no adb download.
I really thought I had completely bricked my phone, I tried this just out of desperation and what do you know, push update.zip over and over and click and it goes through, which allowed me to get into download mode.

muncknr said:
I also forgot to disable voodoo, and this was before there were fix instructions posted. So i basically effed up my phone to the point of being stuck in the samsung recovery loop, no hardware download mode, no clockwork recovery, no update.zp, no adb download.
I really thought I had completely bricked my phone, I tried this just out of desperation and what do you know, push update.zip over and over and click and it goes through, which allowed me to get into download mode.
Click to expand...
Click to collapse
nice , you just have to re-root and install the new rom again , if it brick again , just use this method and you are good again.many of us forgot to disable the voodoo before we restore or install new rom and this crashes the phone.

Need some help really bad
Ok so I have a similar situation as you did (OP), only mine is a bit worse... In my irrational "in the moment" fear of the situation, I used adb reboot recovery to get into recovery mode (HW locked phone) and I did the option that deletes all the **** on the phone and restores the phone to its original format (I think it reinstalled the OS or something, because it looks brand new). So now, whenever I boot up, it does the annoying black screen with the 4 glowing buttons thing for a while, and then eventually the OS actually shows up on the screen. Then it does "scanning media" thing over and over again, but thats not the main problem. I figured, hey this isnt so bad atleast I found your thread and would be able to use your method to help restore my phone... the problem is that somehow my "settings" button is totally gone from the app menu, and I cant get it into debug mode, so I cant use either adb or your method or ANYTHING!! My phone is practically bricked as I cant do anything because its constantly laggy and turns back to the black screen thing, and then when it is showing the homescreen I cant do **** because even swiping to another screen takes like 5 minutes to do cause its so laggy. So basically I ****ed up, and I really need some help.. Im kinda a noob at this whole thing and im really outa options as far as I can tell.. does anyone know what I can do to repair my phone? Thanks!

[Q] Recovery not working and additional problems

Hi guys,
I have a few problems with my Motorola Milestone.
1. I can't get in to recovery. I only get an black screen (backlight is on)
2. I don't get any video in the bootloader. but RSD lite does recognizes it, and is able to flash it. When it's flashing I do get video only stating that there is software update busy.
3. When I boot up my phone I don’t get, a Motorola logo, but just a black screen (back light on) followed by the Android logo after a few minutes.
4. If I try to wake up the phone, the screen remains black, but the hardware keys to light up, I have to press the lock button multiple times to activate the screen. - Note when the screen remains black, it is responsive and I can unlock the phone, but it still remains black. And sometimes the colors are inverted, but when i make a screen of it with Screen Grabber (shoot me) it's in normal colors.
That kind of sums it up.
I have tried a few things to fix it. I have:
1. Cleared caches, and personal data
2. Flashed a different SBF en recovery
And since I can’t get in to recovery, I had to get Root via Z4 Root method and it works fine.
Afterwards I downloaden Rom-manger, and installed the ClockWork recovery, and tried to boot in Recovery via clockwork, but that didn’t work either. I also can’t get in to Recovery via a cold boot
I think the problems started when I was using CyanogenMod 7 RC4. It worked just fine, but after I installed it I couldn't get in to recovery.
Can I try something else to fix it? or should I flash it back to original state and RMA it?
Edit some additional information:
Frimware: 2.2.1
Frimware configuration: GAS_EMEA_UCAMS1FRYOQWRTEU_P005
Baseband version: 3GSMPU91A_U_91.09.00I
Baseband configuratuin version:UCALHLSMR2EMEAB1B806E.0R
Kernel Versuin: 2.6.32.9-ge635aa4 [email protected]#1
Build Number: SHOLS_U2_05.06.0
And is it possible to restore the orginal boot animation, without recovery?
TL.DR: Motorola Milestone --> CyanogenMod 7 RC4 --> no recovery & no video @ bootloader, plus additinal video problems --> back to orginal --> same problems.

BUMP: is there anyone with a possible soulution?

ClockWork recovery doesn't work on milestone.
So CM7 does boot up?

zeppelinrox said:
ClockWork recovery doesn't work on milestone.
So CM7 does boot up?
Click to expand...
Click to collapse
CM7 doesn't anymore as I removed it, and flashed a different SBF and recovery.
CyanogenMod 7 RC4 worked fine but I had a few video problems, and I could get in to recovery.
I will flash a different recovery tonight and try it out.

Only use androidiani open recovery
Sent from my Milestone using Tapatalk

zeppelinrox said:
Only use androidiani open recovery
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Flashed a different .sbf and placed the androidiani open recovery files on the Sd card root, but i still can't get in to recovery. I won't even get the /!\ screen. The phone does turn on, but will only get a black screen.

Which sbf?
Sent from my Milestone using Tapatalk

UK SHOLS_U2_02.36.0
I think I bricked it, I'm going to try to restore it or buy a new phone... >.<

BloemBlaster said:
UK SHOLS_U2_02.36.0
I think I bricked it, I'm going to try to restore it or buy a new phone... >.<
Click to expand...
Click to collapse
I don't think you bricked it... but damaged it in some way.
Could also be some hardware related stuff in the end.
Anyway try to wipe everything, that could be wiped.
Start into bootloader and try to install G.O.T. 2.2.1 using RSD again.
This one got the vulnerable recovery already integrated.
Then try to use the specific G.O.T. OpenRecovery on your sdcard to check system integrity.
Please try to take care of every single step and check out what happens....
If your hardware is doing fine, i'm pretty sure that you will get a working phone again.
P.S.: How about your bootloader version?
Good luck,
scholbert

scholbert said:
I don't think you bricked it... but damaged it in some way.
Could also be some hardware related stuff in the end.
Anyway try to wipe everything, that could be wiped.
Start into bootloader and try to install G.O.T. 2.2.1 using RSD again.
This one got the vulnerable recovery already integrated.
Then try to use the specific G.O.T. OpenRecovery on your sdcard to check system integrity.
Please try to take care of every single step and check out what happens....
If your hardware is doing fine, i'm pretty sure that you will get a working phone again.
P.S.: How about your bootloader version?
Good luck,
scholbert
Click to expand...
Click to collapse
I think my boatloader is 90.47 I'm not sure as I won't get any video in the boatloader.
I flashed the G.O.T 2.2.1but I can't get in to recovery, there is still no video only a blackscreen.
Is it posible the may have deleted the files for the logo?

BloemBlaster said:
I think my boatloader is 90.47 I'm not sure as I won't get any video in the boatloader.
I flashed the G.O.T 2.2.1but I can't get in to recovery, there is still no video only a blackscreen.
Is it posible the may have deleted the files for the logo?
Click to expand...
Click to collapse
You can try upgrading your bootloader to 90.78 from here.
Then try flashing GOT 2.2.1, then see if AOR boots up.

sileshn said:
You can try upgrading your bootloader to 90.78 from here.
Then try flashing GOT 2.2.1, then see if AOR boots up.
Click to expand...
Click to collapse
I flashed 90.78, and then reflashed GOT 2.2.1, but is still can't get into te recovery. I getting the same result, no motorola logo and a black screen with no /!\ logo

If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.

I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/

Hi guys,
sorry for the late reply, but I'm also moving at the moment.
I have tired numerous things.
If I flash the 2.2.1 Firmware SHOLS_U2_05.26, I can get to the recovery selection screen, with the /!\ screen.
But if apply update.zip I will get an error message, stating "EOCD marker occurs after start of EOCD E:signature verification failed", something like that, I don't know the specific message out of my head
And if I flash a vurnable recovery only sbf, with the SHOLS_U2_05.26 I can't get the recovery screen, only a black screen.
zeppelinrox said:
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Click to expand...
Click to collapse
I will try thiss when I get home.
sileshn said:
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
Click to expand...
Click to collapse
I will try this if zepplelinrox method fails becaus I don't have any experince with adb. But the phone is recognised.

...........strange....
BloemBlaster said:
If I flash the 2.2.1 Firmware SHOLS_U2_05.26, I can get to the recovery selection screen, with the /!\ screen.
But if apply update.zip I will get an error message, stating "EOCD marker occurs after start of EOCD E:signature verification failed", something like that, I don't know the specific message out of my head
Click to expand...
Click to collapse
This is standard error, if vulnerable recovery is not installed and you try to start OpenRecovery.
BloemBlaster said:
And if I flash a vurnable recovery only sbf, with the SHOLS_U2_05.26 I can't get the recovery screen, only a black screen.
Click to expand...
Click to collapse
This is strange behaviour...
My last guess is, that something might be wrong with your vulnerable recovery sbf file (file corruption ???). There should have been some errors during flash...
Anyway, you might grab it here and try again:
http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
Good luck!
scholbert

sileshn said:
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
Click to expand...
Click to collapse
Still trying this, no luck yet. ADB isn't my strongest point
zeppelinrox said:
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Click to expand...
Click to collapse
The same goes for you, no luck yet. QtADB, work and it recognise my phone, but i can't any (re)boot commands.
scholbert said:
This is standard error, if vulnerable recovery is not installed and you try to start OpenRecovery.
This is strange behaviour...
My last guess is, that something might be wrong with your vulnerable recovery sbf file (file corruption ???). There should have been some errors during flash...
Anyway, you might grab it here and try again:
http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
Good luck!
scholbert
Click to expand...
Click to collapse
I actually have no idea how to download the sbf, form the site you have provided.
nevermind, I found it out . but now if my phone to connect to windows it doesn't recognizes it :S

BloemBlaster said:
but now if my phone to connect to windows it doesn't recognizes it :S
Click to expand...
Click to collapse
Before or after flashing the vulnerable recovery again?
Confusing...
scholbert

scholbert said:
Before or after flashing the vulnerable recovery again?
Confusing...
scholbert
Click to expand...
Click to collapse
Sorry for being confusing, it was after flashing vulnerable recovery, but my I'm flashing with a different system now and it working just fine.
If I try the .sbf you provided RSD gives a error "Failed flashing process. failed flashing process (0x17100);phone connected"

BloemBlaster said:
Sorry for being confusing, it was after flashing vulnerable recovery, but my I'm flashing with a different system now and it working just fine.
Click to expand...
Click to collapse
No problem...
BloemBlaster said:
If I try the .sbf you provided RSD gives a error "Failed flashing process. failed flashing process (0x17100);phone connected"
Click to expand...
Click to collapse
O.K. seems that something went wrong during download grab it here:
http://forum.xda-developers.com/showpost.php?p=13039348&postcount=17
BTW the link points to the OpenRecovery developers git rep... so this file is absolutely save.
Cheers,
scholbert

Help - Lost everything trying to update Kernel - Captivate

I was trying to install Serendipity 7. I followed the directions for the Kernel and flashed it from the SpeedMod menu, Install from SDCard. I chose the kernel zip that I downloaded for the 7.0 and it looked like it was working, I think. It was announcing in a "computer voice" that it would take 2 minutes. The screen was messed up like "snow" during this time.
It then rebooted, I saw the AT&T splash screen and then it cleared. I saw about 2 lines of "snow" in the middle of the screen, and it rebooted.
I managed to get it into recovery mode, but there is nothing on the screen. Using ADB devices, it tells me its in recovery but the screen is blank.
Now what do I do??? yikes!

You didn't flash gingerbread bootloaders.
follow the directions exactly...

MarkWorsnop said:
I was trying to install Serendipity 7. I followed the directions for the Kernel and flashed it from the SpeedMod menu, Install from SDCard. I chose the kernel zip that I downloaded for the 7.0 and it looked like it was working, I think. It was announcing in a "computer voice" that it would take 2 minutes. The screen was messed up like "snow" during this time.
It then rebooted, I saw the AT&T splash screen and then it cleared. I saw about 2 lines of "snow" in the middle of the screen, and it rebooted.
I managed to get it into recovery mode, but there is nothing on the screen. Using ADB devices, it tells me its in recovery but the screen is blank.
Now what do I do??? yikes!
Click to expand...
Click to collapse
Not sure exactly, there are many in this forum that can answer you more correctly. But maybe to get you started, there are a couple of boot loaders, 'boot.bin' and 'sbl.bin' that need to match, whether they are gingerbread or froyo. Sounds like yours are mismatched. Only thing I know to do would be to ODIN-1-click back to stock eclair (2.1) and reflash the S7 rom per instructions in the OP. Don't know if this helps or not, maybe some of the others will help clarify.
edit: Yeah, studacris is one of those I was talking about

I must be blind. I went to the Serendipity 7 web site and followed the directions on the download page. That didn't seem to do anything so I then tried to install the kernel. This is where I went to the recovery menu and told it to install a zip. I guess that was wrong.
The good part is I can get to the recovery mode using ADB.
Can you please tell me how I flash the gingerbread bootloaders? there must be something that shows how to do this from adb?

I am able to change the modes using ADB. I put the phone into Download mode. The DOWNLOADING screen is on the phone. I start ODIN and click START.
It says
(0 succeeded / failed 0)
ADB does not see the phone in download mode, not sure if it should.
Can I do a flash_image using ADB or what do I need to do?
I have ODIN3 One Click Instraller

MarkWorsnop said:
I must be blind. I went to the Serendipity 7 web site and followed the directions on the download page. That didn't seem to do anything so I then tried to install the kernel. This is where I went to the recovery menu and told it to install a zip. I guess that was wrong.
The good part is I can get to the recovery mode using ADB.
Can you please tell me how I flash the gingerbread bootloaders? there must be something that shows how to do this from adb?
Click to expand...
Click to collapse
Don't need to from adb. After you flash back to stock, check out forums on GB bootloaders. Those for S7 and there's a 1-click out there as well, I897 GB bootloaders, all will work with S7.

How do I flash back to stock? ODIN doesnt seem to work???

MarkWorsnop said:
How do I flash back to stock? ODIN doesnt seem to work???
Click to expand...
Click to collapse
Here's 3 methods...
Method 1: Key Combination 1 (recommended)
1. Remove your battery, external SD card and SIM card
2. Reinsert battery and battery cover.
3. Hold down both volume buttons and while holding them down plug the phone in.
Method 2: Key Combination 2 (if method 1 doesn't work)
1. Remove your battery, external SD card and SIM card
2. Reinsert battery and battery cover.
3. Hold down both volume buttons and the power button.
Method 3: ADB (for advanced users.)
1. Download the android SDK from http://developer.android.com/sdk/index.html (NOT THE .EXE VERSION)
2. Drag it into the ROOT (top-most directory) of your hard drive.
3. Open the Command Prompt and navigate to the tools folder in the android SDK.
4. type adb shell then press enter
5. type adb reboot download then press enter
I've also had some success with using 'adb reboot recovery' if you've still got a good update.zip file in there somewhere.
edit: Then use ODIN to flash back to stock...

back to 6.4 again,
I managed to run flash_image from ADB and then I was able to get back to the recovery menu on the phone.
I reinstalled my original kernel using CWM and then reinstalled Serendipity 6.4 and now the phone appears to be ok again.
Now... what should I have done in the first place to get Serendipity 7 on this phone?
I have the kernel zip. I originally used CWM to install the zip from the SDCard and that is what trashed everything.
What is the proper procedure?

MarkWorsnop said:
I managed to run flash_image from ADB and then I was able to get back to the recovery menu on the phone.
I reinstalled my original kernel using CWM and then reinstalled Serendipity 6.4 and now the phone appears to be ok again.
Now... what should I have done in the first place to get Serendipity 7 on this phone?
I have the kernel zip. I originally used CWM to install the zip from the SDCard and that is what trashed everything.
What is the proper procedure?
Click to expand...
Click to collapse
Go back to S7 site and follow steps 1-16 very closely! redownload the file in step 1 in case the one you have is corrupted some how, and start over. These are the steps that work, so if not for you maybe you got a file messed up or something. You're back to 6.4 so this should work, if not it's now beyond me. Hope you get up and running!

Do I need to do anything with the Kernel first? Or just do everything from the download instructions?
I have ODIN open and the phone in in download mode. I choose the 4 files and hit start. All the files say "0 succeded"
Should there be anything listed in the boxes at the top of ODIN? Seem like ODIN does not connect.
ADB doesnt see the phone in download mode, not sure if it should?

Moving to a new thread as the phone is back up again... in the old rom

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 =)

corrupted recovery

First thank you for all the wonderful work there to help us make the best out of this phone.
Yesterday, I tried to install the CM10 ROM (cm-10-20121126-UNOFFICIAL-ancora_tmo) but encountered a serious problem. Since I flashed a custom ROM last time in Aug., I haven't updated the recovery (CWM-base Recovery v5.5.0.4b). When I booted into the recovery, I found it lost all its functionality. To be specific, any selection on menu options (reboot system now, ROMwipe, wipe cache, etc.) yielded no result but a screen with a circling arrow covered by a hat. After that only the power button worked and it would simply bring you back to the main menu. I tried to communicate with the phone in ADB mode and it worked (by that I mean I can reboot it from windows command shell: adb reboot recovery). Now I have no way to update the recovery and install new ROM from there.
Any help would be highly appreciated.

If you can communicate via windows then install Odin and flash from it. Full instructions is on the wiki page
http://forum.xda-developers.com/wiki/Samsung_Exhibit_II_4G
Sent from my CM10 Linero Odexed Powered by Evil

ywhui30 said:
First thank you for all the wonderful work there to help us make the best out of this phone.
Yesterday, I tried to install the CM10 ROM (cm-10-20121126-UNOFFICIAL-ancora_tmo) but encountered a serious problem. Since I flashed a custom ROM last time in Aug., I haven't updated the recovery (CWM-base Recovery v5.5.0.4b). When I booted into the recovery, I found it lost all its functionality. To be specific, any selection on menu options (reboot system now, ROMwipe, wipe cache, etc.) yielded no result but a screen with a circling arrow covered by a hat. After that only the power button worked and it would simply bring you back to the main menu. I tried to communicate with the phone in ADB mode and it worked (by that I mean I can reboot it from windows command shell: adb reboot recovery). Now I have no way to update the recovery and install new ROM from there.
Any help would be highly appreciated.
Click to expand...
Click to collapse
This may seem stupid but how are you selecting something? You should use home capacitive not the power to select. This symptom is the result of tapping the power button, its kinda like sleep
Sent from my Nexus 7 using xda app-developers app

afwolfpacked said:
If you can communicate via windows then install Odin and flash from it. Full instructions is on the wiki page
http://forum.xda-developers.com/wiki/Samsung_Exhibit_II_4G
Sent from my CM10 Linero Odexed Powered by Evil
Click to expand...
Click to collapse
I'd followed the instruction and found the Odin rebooted to the exact recovery! There it showed a few lines like:
Galaxy Exhibit CWM-based Recovery v5.5.0.4b
Finding update package ...
Opening update package ...
Verifying update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Now the phone can not boot into the original ROM.

When booted into recovery use volume keys to navigate in cwm. Also retry to download the ROM and try cwm before Odin.
Odin is on computer and phone is hooked via USB cable. It cannot boot into cwm if followed Odin. You ha e to download Odin and drivers for cell to be recognized.
Do a YouTube search for Odin and watch the vid it will show you. Be it noted that cell will need to be set into download mode and USB enabled.
Sent from my CM10 Linero Odexed Powered by Evil and or DemonsBlood

theAPANT said:
This may seem stupid but how are you selecting something? You should use home capacitive not the power to select. This symptom is the result of tapping the power button, its kinda like sleep
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I used the home capacitive to select those options on the main menu. No matter what I choose, however, the power button can get me the circling arrow with a hat. Another push on the button, you are back on the main menu.

You are deffeinitly booted into cwm so I suspect from the install error that the signature verification is what's failing. Try another ROM or redownload and try again
Sent from my CM10 Linero Odexed Powered by Evil and or DemonsBlood

afwolfpacked said:
You are deffeinitly booted into cwm so I suspect from the install error that the signature verification is what's failing. Try another ROM or redownload and try again
Sent from my CM10 Linero Odexed Powered by Evil and or DemonsBlood
Click to expand...
Click to collapse
I've redownloaded the uvlg3.odin.zip package and checked its MD5. Everything is OK. Then followed the instruction on the Wiki page, but ended on the same CWM recovery screen with the same error message.
The problem is: it seems like the phone boots successfully into the recovery, but it only shows the main menu with no option functioning (like I described before).
Has anyone read about similar problem anywhere before?

ywhui30 said:
I've redownloaded the uvlg3.odin.zip package and checked its MD5. Everything is OK. Then followed the instruction on the Wiki page, but ended on the same CWM recovery screen with the same error message.
The problem is: it seems like the phone boots successfully into the recovery, but it only shows the main menu with no option functioning (like I described before).
Has anyone read about similar problem anywhere before?
Click to expand...
Click to collapse
Are you running Odin with your phone in Download mode? Like they said, Odin shouldn't re/boot into recovery automatically.
Also make sure the auto reboot option in odin is cleared.
Sent from my GT-P5110 using XDA Premium HD app