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

Droid 3 Stuck at M Logo - Bricked?

Hey guys,
I just recently got a refurb Droid 3 after my old one had the backlight go out, I hand't had a chance to bootstrap it and put ICS on it. But I was able to get it rooted. I restarted my phone today and ever since it has been stuck at the M logo screen and I've tried everything I can find to remedy this.
I updated this morning to the most recent OTA update (5.7.906 I believe) and then rooted it.
To fix the issue I've tried a few different things. I tried Pete's SBF to 5.7.890 but I was getting an error about the cbt.bin file. I found that with the recent changed to 5.7.906 you aren't able to directly flash over it to go back to 5.7.890. I then found another post on here which had a script to go back to 5.7.890 from 5.7.906. I ran that and still had the same result.
Any other ideas or anything that I am missing?
I can get into fastboot, I've been using the scripts with moto-fastboot. Normal boot is just leaving me at the M logo, booting into recovery yields the same result.
Any help would be appreciated since I have no clue what else I can do at this point...

seems like a soft brick... should be fixable...
With the phone off, hold me, then the power button... then go down to BT TOOLS and select it ( volume up is the select button _ so when u do that it doesnt go to it?
try following this thread
http://forum.xda-developers.com/showthread.php?t=1336980
heres a download link
http://minus.com/lbkaxv58pO5MDp

Juicy555 said:
seems like a soft brick... should be fixable...
With the phone off, hold me, then the power button... then go down to BT TOOLS and select it ( volume up is the select button _ so when u do that it doesnt go to it?
try following this thread
http://forum.xda-developers.com/showthread.php?t=1336980
heres a download link
http://minus.com/lbkaxv58pO5MDp
Click to expand...
Click to collapse
I don't have a BT Tools selection. I do have BP Tools though. I selected it and it just sits there on the M logo as well...
I've tried a few of Pete's scripts with no luck so far (worked on the old Droid 3 when I put it back to stock before shipping it back).

Juicy555 said:
seems like a soft brick... should be fixable...
With the phone off, hold me, then the power button... then go down to BT TOOLS and select it ( volume up is the select button _ so when u do that it doesnt go to it?
try following this thread
http://forum.xda-developers.com/showthread.php?t=1336980
heres a download link
http://minus.com/lbkaxv58pO5MDp
Click to expand...
Click to collapse
Gave the one that you linked a try, get "Preflash validation failure" for Recovery and Boot.
Any other ideas?

imperpetual said:
Gave the one that you linked a try, get "Preflash validation failure" for Recovery and Boot.
Any other ideas?
Click to expand...
Click to collapse
it will not flash if your phone is not charged to at least 50%.. make sure its charged...

Juicy555 said:
it will not flash if your phone is not charged to at least 50%.. make sure its charged...
Click to expand...
Click to collapse
It is charged. When it's not charged it gives the "LOW BATTERY" error.

click the link in my signature
and follow the directions in my thread and you will be fine
you updated your phone to. 906 all of the older sbf's wont work..but mine will as it is specifically for. 906

ovelayer said:
click the link in my signature
and follow the directions in my thread and you will be fine
you updated your phone to. 906 all of the older sbf's wont work..but mine will as it is specifically for. 906
Click to expand...
Click to collapse
Your 1 Click SBF ran fine and completed without errors but I'm still getting the same result, stuck at M logo.
Is there something I could be missing which is making it not boot that most SBFs don't include? That's the only thing I can think of at this point.

imperpetual said:
Your 1 Click SBF ran fine and completed without errors but I'm still getting the same result, stuck at M logo.
Is there something I could be missing which is making it not boot that most SBFs don't include? That's the only thing I can think of at this point.
Click to expand...
Click to collapse
okay right after you use the 1click sbf
go HERE
download the. 906 update
place it on your external sdcard..
reboot into STOCK recovery and install the update
reboot
try that

ovelayer said:
okay right after you use the 1click sbf
go HERE
download the. 906 update
place it on your external sdcard..
reboot into STOCK recovery and install the update
reboot
try that
Click to expand...
Click to collapse
I'm fairly certain that could work, if I could ever get into the Stock recovery....I'm not able to boot into anything. Going to try a few other things, if nothing else works I'll just take it in and see if I can get yet another warranty replacement.
Thanks for the responses, if you have any other ideas just let me know.
I think the main thing that needs to be addressed is that I need to be able to get into recovery and then I will be set to fix it. Right now it just sits at the M logo for Recovery (and any other options from the boot menu).

build.prop mistake

Hey all My friend gave me his Droid Bionic running ICS update and he said he was trying to get it to work with att BUT while in the process he tried to put in a different build.prop but he deleted the one out of his system folder. The phone boots on a black screen and will not connect to the pc he said he also tried doing the recovery thing to it,
So. No build.prop
Black screen boot.
And no way to mount.
Any ideas?

midgetgnome said:
Hey all My friend gave me his Droid Bionic running ICS update and he said he was trying to get it to work with att BUT while in the process he tried to put in a different build.prop but he deleted the one out of his system folder. The phone boots on a black screen and will not connect to the pc he said he also tried doing the recovery thing to it,
So. No build.prop
Black screen boot.
And no way to mount.
Any ideas?
Click to expand...
Click to collapse
do you still have the original rom zip?
if have then copy the zip in sd card using another phone or card reader and then do the fresh flash again.
if dont have then re download the zip and do the fresh flash..
hit thanks button if i helped you somehow.
and u need to be more specific on what device you are talking about..
you havent mention the device you are using..

midgetgnome said:
Hey all My friend gave me his Droid Bionic running ICS update and he said he was trying to get it to work with att BUT while in the process he tried to put in a different build.prop but he deleted the one out of his system folder. The phone boots on a black screen and will not connect to the pc he said he also tried doing the recovery thing to it,
So. No build.prop
Black screen boot.
And no way to mount.
Any ideas?
Click to expand...
Click to collapse
If the data on this phone is no longer needed, you could alway flash a stock JB 4.1.2 using RSD.
That'll surely fix all the problem except data loss.

the hellboy said:
do you still have the original rom zip?
if have then copy the zip in sd card using another phone or card reader and then do the fresh flash again.
if dont have then re download the zip and do the fresh flash..
hit thanks button if i helped you somehow.
and u need to be more specific on what device you are talking about..
you havent mention the device you are using..
Click to expand...
Click to collapse
I dont have anything I did download the ICS SBF but RSD wont see the device for some reason. And I did tell you what device I said DROID Bionic in my first post. Any other specifics I cant give because I cant get into my phone to see them.

midgetgnome said:
I dont have anything I did download the ICS SBF but RSD wont see the device for some reason. And I did tell you what device I said DROID Bionic in my first post. Any other specifics I cant give because I cant get into my phone to see them.
Click to expand...
Click to collapse
You didn't state that you did this. So, I'll start with the obvious.
1. Fully charge and then power off the phone.
2. Press & hold the volume + and volume -.
3. Power on the phone.
4. Once the boot menu comes up, use volume - to move to AP Fastboot & select wit volume +.
5. Plug in the phone to your PC and run RSD Lite. Click Config>Flash modes>Fastboot Mode.
6. Flash the phone with ICS or JB.
If you choose BP SBF Flash, on the menu, RSD may not work right. If you try to downgrade it, you can brick it.
Let me know how it goes.

pmrmx774 said:
You didn't state that you did this. So, I'll start with the obvious.
1. Fully charge and then power off the phone.
2. Press & hold the volume + and volume -.
3. Power on the phone.
4. Once the boot menu comes up, use volume - to move to AP Fastboot & select wit volume +.
5. Plug in the phone to your PC and run RSD Lite. Click Config>Flash modes>Fastboot Mode.
6. Flash the phone with ICS or JB.
If you choose BP SBF Flash, on the menu, RSD may not work right. If you try to downgrade it, you can brick it.
Let me know how it goes.
Click to expand...
Click to collapse
I would definitely not recommend flashing JB. Stay with ICS.
Once you go to JB you are locked down with lots of restrictions.
If you stay with ICS you can root easier, and you have more choices of custom roms that you can use.
If you go JB, you can only use JB custom roms.
You can use either safestrap or bootstrap if you stay with ICS. If you do JB, you are stuck with safestrap.
Stay with ICS! If you want JB, only use custom JB roms, don't flash them through RSD.

pmrmx774 said:
You didn't state that you did this. So, I'll start with the obvious.
1. Fully charge and then power off the phone.
2. Press & hold the volume + and volume -.
3. Power on the phone.
4. Once the boot menu comes up, use volume - to move to AP Fastboot & select wit volume +.
5. Plug in the phone to your PC and run RSD Lite. Click Config>Flash modes>Fastboot Mode.
6. Flash the phone with ICS or JB.
If you choose BP SBF Flash, on the menu, RSD may not work right. If you try to downgrade it, you can brick it.
Let me know how it goes.
Click to expand...
Click to collapse
RSDLite does noto see the phone at all. Making it impossible to flash. I have tried 6 different cords including the one that came with the phone. And if you read one of my earlier posts you will see where I said rsd isn't working. I cant seem to figure out how to get it to work either. Ive done the drivers several times along with new cords..

midgetgnome said:
RSDLite does noto see the phone at all. Making it impossible to flash. I have tried 6 different cords including the one that came with the phone. And if you read one of my earlier posts you will see where I said rsd isn't working. I cant seem to figure out how to get it to work either. Ive done the drivers several times along with new cords..
Click to expand...
Click to collapse
Do you see a device in Windows Device Manager? Can you get to the menu I talked about on the phone. RSD won't see the phone if Windows doesn't load the drives correctly. Do you have the Android SDK loaded? That can help w/ manual flashing... and drivers. It's important to get the phone in the AP Fastboot mode to get the proper connectivity.

UnBrick Memo PAd me176cx

Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:

clapper66 said:
Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:
Click to expand...
Click to collapse
Dont bother, I have tried for a week straight trying to unbrick mine. I did a factory reset and it destroyed my whole filesystem. :/

i just got mine so i just got a replacement from amazon

Mine was a present and I have no idea where they got it and they tossed the receipt. I'm sol. I'm broke so RMA may take a while as well! xD
Sent from my Galaxy Nexus
---------- Post added at 02:41 AM ---------- Previous post was at 02:36 AM ----------
Also for getting into recovery follow these steps. Turn off. Hold volume down and also power. When Asus pops up release power and keep hold of volume until the bootloader appears. On bootloader go down to boot recovery. When it reboots to an android guy hold volume up and down at the same time. Let go of volume up and do this r over and over until it goes to recovery. The steps are ridiculous but I know it for sure because my last week of trying to fix mine has been hell.
Sent from my Galaxy Nexus

the there is a way
applerulez1 said:
Mine was a present and I have no idea where they got it and they tossed the receipt. I'm sol. I'm broke so RMA may take a while as well! xD
Sent from my Galaxy Nexus
---------- Post added at 02:41 AM ---------- Previous post was at 02:36 AM ----------
Also for getting into recovery follow these steps. Turn off. Hold volume down and also power. When Asus pops up release power and keep hold of volume until the bootloader appears. On bootloader go down to boot recovery. When it reboots to an android guy hold volume up and down at the same time. Let go of volume up and do this r over and over until it goes to recovery. The steps are ridiculous but I know it for sure because my last week of trying to fix mine has been hell.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/help/asus-memo-7-me176cx-t2814046/post57408037#post57408037

clapper66 said:
Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:
Click to expand...
Click to collapse
what update are you trying to flash?

Steps to unbrick (if you can get into fastboot)
clapper66 said:
Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:
Click to expand...
Click to collapse
I bricked mine, but I am adventurous so found a method to recover to factory.
I'm not providing links as they are searchable here on XDA.
The steps are:
1) Get the factory image from Asus
2) Get FB Tethered Recovery Launcher
3) boot into fastboot mode
4) Hook up to computer
5) ensure the device is listed with correct drivers
6) Run ADB (from your platform tools, there is a copy in FBRL folder)
8) copy the zip file from Asus to the device (adb push /path/to/local/file /mnt/sdcard/path/to/file)
9) Run launcher from FB recovery
10) Choose T2 option, follow prompts to let it do it's thing
11) You should boot into CWM on the device
12) install from zip and point to the zip file you pushed earlier
13) Follow the prompts, and presto, restored to factory and can root/update etc.

I'd like to say thanks to the good info posted here and in other threads. I got stuck in a boot loop tonight and had no idea if I'd be able to fix it. Here's what I did (combination of this thread and others)
My method requires an micro SD card and an Internet connection
1. Confirm you can boot into fastboot:
---->Reboot into fastboot (droid boot) by powering device off (hold power button down), then holding down volume up while powering on. I released the up button once the screen went blank. It should eventually present options to reboot into droidboot, reboot, update from SD, etc.
2. Download the newest firmware from ASUS
YOU NEED THE WW version most likely (worldwide?)
3. Save this to the root of your SD card
4. rename file to MOFD_SDUPDATE.zip
5. Insert card into tablet.
6. While in droidboot/fastboot Choose the option to update from SD. It reboots and uploads the firmware. I was pleasantly surprised that I got my tablet back so easily.
Hope this helps some other poor soul.

There are other methods, but in simplicity, yours seems to win the match. Thank you very much.

How did you get cwm?
Sent from my K013 using XDA Free mobile app

JarrelStudios said:
How did you get cwm?
Sent from my K013 using XDA Free mobile app
Click to expand...
Click to collapse
I do not get the option to Update from SD while in DroidBoot...why is that? I get the other options...REBOOT, REBOOT DROIDBOOT, RECOVERY, POWER OFF.
Please help! I've already sent this back to Asus, and they just sent it right back to me.

Shaundiesel said:
I do not get the option to Update from SD while in DroidBoot...why is that? I get the other options...REBOOT, REBOOT DROIDBOOT, RECOVERY, POWER OFF.
Please help! I've already sent this back to Asus, and they just sent it right back to me.
Click to expand...
Click to collapse
Click on recovery. Inside recovery you'll get a "no command" screen. Hit the center of the volume rocker (it'll take a few tries) and you'll see the update command.

jerbear294 said:
Click on recovery. Inside recovery you'll get a "no command" screen. Hit the center of the volume rocker (it'll take a few tries) and you'll see the update command.
Click to expand...
Click to collapse
thanks Jerbear (Love the name, Deadhead!), I did this which brings up regular Android recovery, but no option to update except through ADB.

Shaundiesel said:
thanks Jerbear (Love the name, Deadhead!), I did this which brings up regular Android recovery, but no option to update except through ADB.
Click to expand...
Click to collapse
Try this, then.
In the main thread somebody linked a temporary cwm session. Try booting into it and installing the update from there (Nandroid while you're at it )

Why would I not even have the option though??

Shaundiesel said:
Why would I not even have the option though??
Click to expand...
Click to collapse
I'm not exactly sure.

I need some help. I have average experience with ADB and cannot get ADB to recognize my device. Debugging on of course, and I dowloaded the zip for the drivers. I don't really know where to go from here. Any help will be greatly appreciated! I need to get this thing back up and running!!

gcballard said:
I'd like to say thanks to the good info posted here and in other threads. I got stuck in a boot loop tonight and had no idea if I'd be able to fix it. Here's what I did (combination of this thread and others)
My method requires an micro SD card and an Internet connection
1. Confirm you can boot into fastboot:
---->Reboot into fastboot (droid boot) by powering device off (hold power button down), then holding down volume up while powering on. I released the up button once the screen went blank. It should eventually present options to reboot into droidboot, reboot, update from SD, etc.
2. Download the newest firmware from ASUS
YOU NEED THE WW version most likely (worldwide?)
3. Save this to the root of your SD card
4. rename file to MOFD_SDUPDATE.zip
5. Insert card into tablet.
6. While in droidboot/fastboot Choose the option to update from SD. It reboots and uploads the firmware. I was pleasantly surprised that I got my tablet back so easily.
Hope this helps some other poor soul.
Click to expand...
Click to collapse
I'm at the Android System Recovery, however, there's no option to apply update from SD...only apply update from ADB...

jhenehj said:
I'm at the Android System Recovery, however, there's no option to apply update from SD...only apply update from ADB...
Click to expand...
Click to collapse
In this case use the Intel Atom temporary ClockWorkMod to flash it.

jerbear294 said:
In this case use the Intel Atom temporary ClockWorkMod to flash it.
Click to expand...
Click to collapse
Thanks for your reply...I'm not really sure what you're referring to, but is this about ADB sideloading? I already tried but this comes up...
Now I don't know what to do...so I badly need anyone's help here...thanks in advance!