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]Accessing Recovery With Broken Power Button

So I have a bit of an issue. Over the weekend my power button stopped working like it has for many people.
I finally got to a computer last night and was able to turn it on using a method I had read about.
I was using madaco's desire port but I didn't have the option for wake with trackball baked into it. Which I need to have my phone usable. So I had another ROM baked on his site with that option in it but I forgot to tick the option to have the .zip signed. (I'm using an older recovery, had been to lazy to update)
I didn't realized it wasn't signed until I had go into recovery, wiped everything and then attempted to flash at which time it said no because it wasn't signed. So I said F it I'll do it in the morning.
So today I realized I can't boot the phone up because I had wiped everything, including the ext partition. It just sits at the X screen with the unlocked paddle lock on it. Due to this I can't access it with ADB to get to recovery.
If I restart the phone and put it into HBOOT I can't select recovery because you have to press the power button to select the option.
I also tried finding a fastboot command to boot into recovery but didn't locate one.
SOO
Does anyone have a clue how I can get this damn thing into recovery? I'm normally really good with this stuff but I am stumped at this point.
And before anyone says it I can't exchange it because my screen is cracked.

If you can grab a kernel and and recovery image on your PC you can boot them using
fastboot boot <kernel image> <recovery image>

Is that going to get me to a point where I can flash a new rom on it? I was running all of my cache on SD so when I wiped it is messed the rom up.
It already has Amon_RA recovery on it, the release prior to the newest one. So do I really need to flash another one to it?

All I can think of is possibly reverting to stock via the passimg method, but I can't remember if you need to use the power button to confirm during the process?
Once you have a working ROM, you can root via superoneclick, and install superboot to boot into recovery.
Problem is, you'll then have a stock recovery...
Once you're booted and rooted though, you can always use adb, or ROM Manager right?
Sent from my Nexus One using XDA App

danger-rat said:
All I can think of is possibly reverting to stock via the passimg method, but I can't remember if you need to use the power button to confirm during the process?
Once you have a working ROM, you can root via superoneclick, and install superboot to boot into recovery.
Problem is, you'll then have a stock recovery...
Once you're booted and rooted though, you can always use adb, or ROM Manager right?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yeah that's the route I'm thinking about taking. But I think there are option you have to use the power button to confirm.
I'm messing around with different boot.img right now to try and get it to boot. If I could just get the damn thing to boot I'd be all set cause I can use adb from that point. But right now when it stops at the X screen ADB can detected the phone but if you try to access the shell you get "failed to link /system/bin/sh
Thanks for the input man

If your bootloader is unlocked, you can re-image with fastboot.
Also, if you're not unlocked, I'm pretty sure the passimg only selects options with the volume keys...
Sent from my Nexus One using XDA App

I went with the superboot method. When I ran the .bat files it restarted the device and put it into recovery. I flashed a fresh ROM from there.
It's made it to the boot animation so I'll see if it fully boots up in a minute .

Okay, I'm back in action. Thanks for the in put guys.

Great!
D'ya need an unlocked bootloader to use superboot (I've never used it)?
Sent from my Nexus One using XDA App

Just discovered this gem:
http://forum.xda-developers.com/showthread.php?t=825909
Sent from my Nexus One using XDA App

danger-rat said:
Great!
D'ya need an unlocked bootloader to use superboot (I've never used it)?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I'm pretty sure you do. It says you'll probably need to as a foot note in the directions for superboot.
I may be wrong, I haven't kept up on much relating to rooting the Nexus since it first came out.

I think you're probably right... Thanks!
Sent from my Nexus One using XDA App

Bootloader button combos does nothing.

Been trying to do this for two days straight now and I'm going bananas...
Got a GT540 with stock 2.1, now rooted with z4.
Gone thru a shipload of tutorials on how to flash a ROM onto this, downloaded lots of files to make winxp behave and find the drivers.
Somehow these tutorials miss something and I just float in space...
I can't get the phone into bootloader mode to even start the process.
- Camerabutton (all the way down) + Power does only normal boot.
- Camerabutton (all the way down) + USB cable insertion does normal boot.
(it's not even possible to have it to stay shut when USB is connected to PC, it restarts immediately)
- Home + Power does a boot in safe mode.
- VolDown + Power does a Download mode.
Please help me get past this step.
My aim is to get CM7 on it.

you need to install a fastboot rom to install clockwork and cm7
Sent from my GT540 using XDA Premium App

You could try this (but I think you need plenty of ram free):
1) install Terminal Emulator app from Market.
2) Copy the img file for Clockworkmod Recovery to the root of your sdcard and call it "recovery.img".
3) run Terminal Emulator and type in "su" and press enter. It will request SuperUser rights - accept this.
4) next type in "flash_image recovery /sdcard/recovery.img" and press enter
5) reboot into recovery (hold camera + press power)
6) back up your phone
It will either work or it won't but if it does you'll have recovery and from there you should be able to install a recovery image of CM7... But I've never tested it But you would have your backup if it didn't work...
Sorry it's speculative - others might have more experience.

eoghan2t7 said:
you need to install a fastboot rom to install clockwork and cm7
Sent from my GT540 using XDA Premium App
Click to expand...
Click to collapse
When entering this world as a newbie, there are -so- many details folks take for granted that I simply don't understand.
What's the difference between a fastboot rom and a flashed rom?
What and why clockwork?
The russian fastboot image found here does it come in any other language as v2.00?
@fishears: I'll try that if I don't run into lack of memory, as you pointed out.

would you like me to remote control your computer to get you up and going using CM7?

eoghan2t7 said:
would you like me to remote control your computer to get you up and going using CM7?
Click to expand...
Click to collapse
dude i want someone to help me remote! please!!! im more or less in the same boat as the op.

kdm212 said:
dude i want someone to help me remote! please!!! im more or less in the same boat as the op.
Click to expand...
Click to collapse
ok download teamviewer then pm me the password and id numbers

eoghan2t7 said:
would you like me to remote control your computer to get you up and going using CM7?
Click to expand...
Click to collapse
Sure, I'll post my ID and PW to you if you have the time.

eoghan2t7 said:
ok download teamviewer then pm me the password and id numbers
Click to expand...
Click to collapse
ok i will do that. anything i should download to speed this up while your logged in?

stompazorb is now with the CM7 users
kdm212 will be joining use tomorrow in the CM7 world

Ran into a brick wall when it came to mount the SD-card.
It was FAT, now it is FAT32 - no change.
Read something about activating adb thru debugging mode - but I must've missed something, it doesn't work.
What's wrong?

stompazorb said:
Ran into a brick wall when it came to mount the SD-card.
It was FAT, now it is FAT32 - no change.
Read something about activating adb thru debugging mode - but I must've missed something, it doesn't work.
What's wrong?
Click to expand...
Click to collapse
i thought you were helped? you dont have cm7?

kdm212 said:
i thought you were helped? you dont have cm7?
Click to expand...
Click to collapse
Yes I do, but it's not exactly flawless, and it was a truckload of work to get it running.
Still haven't been able to mount the sdcard, any suggestions?

try completely formating it in windows and if that doesn't work try formtting in android

eoghan2t7 said:
try completely formating it in windows and if that doesn't work try formtting in android
Click to expand...
Click to collapse
Nope, didn't work, not even after low-level formatting.
But I had a spare SD-card, put it in and it worked right away. Seems like cm7 not accepting every sdcard-brand.
I do not know what the brands are, None are known, and no logos.

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

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!