Database Develop

Help! Cant boot g1 after "danger spl"

I updated my phone's SPL to "Danger SPL" and now my phone wont turn back on! I press power and the black Android screen with the little green android next to it comes up but wont boot my phone! The only thing I can do is get the white screen with the 3 android's skateboarding by pressing camera + power.
Ontop of that, I had tried to update my phone's recovery image too, and I erased the old one and now it would let me upload the NEW one! So not only do I have NO PHONE but NO RECOVERY either!
What do I do!? HELP!

can you get into fastboot? (back+power)
if you can, get adb running and flash your recovery image with fastboot

you are gonna have to fast boot in the screen with the three androids on it, either a rom or a recovery
guess you betta learn how to use adb

Yea I can get into fastboot, thats the ONLY thing I can get into. How do I flash my recovery image?

http://forum.xda-developers.com/showthread.php?t=566669

boot your phone into fastboot. plug in your usb cable to your pc. this should change the fastboot icon on the screen to fastboot usb. from there, load up adb on your pc and make sure you have the fastboot option available by typing fastboot devices. it should list your phone. once that is good, type:
fastboot flash recovery and the correct name of your recovery file.
for example:
fastboot flash recovery recovery-RA-dream-v1.2.3.img
**also note...put the recovery image in your android sdk\tools folder**
this should give you a recovery to boot into.
if you dont have adb on your pc, read this and follow the instructions
http://forum.xda-developers.com/showthread.php?t=532719

I did that already, it wont work.
C:\Android>fastboot flash recovery recovery123.img
error: cannot load 'recovery123.img'

i am gonna be the one to ask this question but did you put .s between 123 like 1.2.3.

you need to be in the tools directory, not the android directory.
c:\Android\tools>fastboot flash recovery recovery-RA-dream-v1.2.3.img

and you need the recovery file IN your tools folder for it to be found as well.

No I didn't put .'s between each number I renamed my file recovery123.img so thats the way I put it in.

ok, so go to the correct directory and input what you had the first time, WITH the file IN that same folder. and then report back.

i justed rename my recovery the shortest way i can like for amon ra"s i just put amon, less typing is always better

It says C:\Android\tools is not recognized as an internal or external command, operable program or batch file.

from your c:\> prompt type this:
cd c:\android\tools
(this is assuming you have the android sdk in the c:\android folder on your pc)
if it is saying its not a folder, then that is not where you installed the android sdk.

knowfear said:
and you need the recovery file IN your tools folder for it to be found as well.
Click to expand...
Click to collapse
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
If you use the above SPL you will need new drivers for Windows. They are located here.
Click to expand...
Click to collapse
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).

what he said.
Binary100100 said:
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
Click to expand...
Click to collapse
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.

innerspace said:
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
Click to expand...
Click to collapse
No problem. I just hate it when something this simple drags onto multple pages. Call it a peev. So many people get intimidated by the "Danger SPL" because they don't want to risk bricking their phones. The odds of bricking your phone are extremely small if you follow directions and read everything. And sure the possibility of accomplishing this by different means exists. But when you try to tell someone to put this file in that folder and type in the full names of the files to include all the dots and dashes, it's going to get confusing and intimidating and thus these posts keep popping up.
If someone follows those very short and simple directions they shouldn't have any problems. Granted that "**** happens" and things don't always go as they should. So in that case, search for your answer. If you've searched on XDA then search Google. Out of the MILLIONS of G1's that have been sold, I am fairly certain that someone out there has had a similar problem. If not then you and your phone are literally "1 in a million" (technically it was 1 in 1.5 million a year ago so you can bet that it's well over 2 if not 3 million by now). And if you really fall into that catagory then please post a new thread (in the appropriate catagory of course) .

well the good news is u didnt brick ur phone but try a enter adb and do a nadroid back up if u hav 1 that will bring u back 2 the way u want it

either flash a nadroid or flash dreaming.nbh....i had the same problem and a nadroid worked just fine

donating paypal for recovery help...

Hello everyone,
I have a N1...just got OTA updated to FROYO 2.2...
Just opened the boot loader for the first time...
then I just rooted it...
Now I am trying to get the AMON RA RECOVERY on their so I can use a cool rom like modaco ect...
I have been reading and having a hard time with this on the mac...I was using the terminal ect...and I keep trying to do the steps but it won't work...I must be doing it wrong...
Can anyone please give a picture tutorial or good step by step on what to do once you open the terminal...
I have put the RA recovery on the sd card and tried getting it to write to the sd card...
I also put the recovery in the fastboot folder trying to do it that way but no luck...
If anyone can help this newb I will donate paypal...
THANKS!

All commands using your mac should be preceded by ./
ie: ./adb
and fastboot is: ./fastboot-mac
./fastboot-mac flash recovery recovery.zip
Did you download the mac version of the sdk?
Make sure the files adb-mac and fastboot-mac are in the same folder as your recovery zip file. These files are in the tools sub folder in the sdk folder (or just put the recovery.zip in the tools folder).
You need to change directory (cd) so you are running all commands from the folder with adb-mac, fastboot-mac and your recovery.zip (could just be your tools folder in the sdk).
When you hook your phone up via usb, power on while holding the trackball to get into fastboot. Then apply the commands as shown above or in the tutorials (http://forum.xda-developers.com/showthread.php?t=611829).

Thanks so much buddy...I didn't think you needed the SDK stuff for the mac because I didn't see it in my tutorial =) thats probably why its not working duh! Well I was able to unlock bootloader/root without the sdk but I guess I need it now...I will download all of it and keep you posted on what happens my friend thank you!
Is it also possible to add the recovery via a windows pc as well? I might try that because I already have sdk on my windows 7...if so do you have a tutorial for doing it on windows?
THANKS!

rayman121985 said:
Thanks so much buddy...I didn't think you needed the SDK stuff for the mac because I didn't see it in my tutorial =) thats probably why its not working duh! Well I was able to unlock bootloader/root without the sdk but I guess I need it now...I will download all of it and keep you posted on what happens my friend thank you!
Is it also possible to add the recovery via a windows pc as well? I might try that because I already have sdk on my windows 7...if so do you have a tutorial for doing it on windows?
THANKS!
Click to expand...
Click to collapse
Windows is the same as I said above. Check out the link I posted for a tutorial:
via fastboot
Code:
Copy recovery-RA-nexus-v1.7.0.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-nexus-v1.7.0.1.img

[Q] Stuck at Fastboot usb screen

I installed the new zen2.2 rom today and had a working clockwork recovery. Here is where I went stupid, I downloaded the kernel update but rather than running it via update.zip I flashed it using flash_image recovery via adb shell.
Now my phone comes up to fastboot usb and never goes any further, been waiting hours! I have tried booting into fastboot/hboot and it does nothing. I have booted to hboot before successfully but now nothing.
If I run adb devices it shows no devices. If I run fastboot devices it does show my device.
Whats next?

If you cant get into fastboot and you cant get into recovery then you m ight have bricked your phone. Did you try a hard reset?

How do you do a hard reset?
Here is a little more info. I believe it does actually get to fastboot usb as it says so on the top left of the screen and I can run fastboot commands but most commands say error. If I do fastboot devices it shows the device connected.
Little more info - when I try doing a back to basics RUU update it connects, shows the rom version, starts the update and then at about 88% every time, it goes right to a error [171] usb connection error. So its communicating but never finishes. Tried with the sprint RUU stock rom, another that was built by one of the devs in the Hero community and still both do the same.

I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.

ASimmons said:
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
Click to expand...
Click to collapse
Right, I also believe that if I could get a recovery back on the phone I would be good as gold! Here is the problem though. I have tried running "fastboot flash recovery [recovery.img]" but it gives me the below error. I have tried multiple key combination's to get into hboot but nothing works. If anyone has any other key combination's I could try please let me know!
Code:
D:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3720 KB)... FAILED (remote: not allow)
finished. total time: 0.001s

1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img

unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Yeah I think he knows now not to flash kernels... atleast I hope so. +1 for your post.

unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Click to expand...
Click to collapse
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.

casualonejp said:
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
Click to expand...
Click to collapse
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
edit: sorry i dont think fastboot will see the sdcard but try anyways.

ASimmons said:
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
Click to expand...
Click to collapse
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.

casualonejp said:
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
Click to expand...
Click to collapse
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.img
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.

ASimmons said:
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.fimg
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
Click to expand...
Click to collapse
Negative on the fastboot commands. Also did have a nandroid but on old sdcard which died. I read that I could use anothers nandroid backup but I am currently trying to find one to test.
Tried doing the RUU method with stock/custom roms and it gets as far as seeing the image but when I click on "ok" to start the recovery, it goes to "waiting on bootloader" and then at 88% it errors to a 171 error stating usb connection error.

I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.

ASimmons said:
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
Click to expand...
Click to collapse
Ya I have been researching non stop all yesterday evening and today so far all day. I just cant get it to do anything. I will keep researching though. Thanks

Did you fix this yet?

Anyone figure this out yet...I have the same issue and haven't been able to resolve it yet. Still with a brick at this point!

Hey guys,if your stuck at fastboot(As I just was tonight), try in your CMD(if running Windows) fastboot reboot-bootloader or fastboot reboot to reboot as normal,I'll try to keep you updated to get through all this. I am at a loss right now but searching for answers first before i go about asking.
Answer to MY problem(maybe not yours): OK,I have come to the conclusion here tonight that I had a soft brick. What I did was remove the battery,put the battery back in,restarted the phone normally,then I ran the HTC Sprint Hero MR 2.27.651.6 on my computer(essentially restoring back to unrooted factory settings). This worked for me. I am totally refreshed and happy that my phone is ok and all. Yes I may have to go back and re-root but this only take me bout 20 minutes most to root and re-flash a CyanMod7 Nightly Rom. Hope my info can help out somebody!

[Recovery] ClockworkMod 5.0.2.0 Official

I just noticed it now, grab it here:
S-OFF
recovery-clockwork-5.0.2.0-buzz.img
S-ON / fake-flash
recovery-clockwork-5.0.2.0-buzz.zip
Haven't tested it, try it at your own risk but should be safe
S-OFF: flash with fastboot with
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
S-ON: simply rename to update.zip and put it on your SD card

Eh!!! Confused!!!!! cwm 5.0.2.0 been around for ages????
"sent from me2u"

I just didn't see it posted lol, did a search and didn't see the official 5.0.2.0, only older and customized versions

Can anyone help me install it?
I've installed v4.0.1.4, but I can't install it
I want install from Ubuntu please...
Regards!!

Cwm can be flashed when s-on?
I don't have wildfire... my friend has...
If it works ill flash it from his s on hboot...
Edit: his hboot is 1.01.0002
Sent from my MB525 using xda premium

So...what's new in this version?
(Also, is there a way to change the color of text in the recoveries, I want the orange color back )

Qarl said:
Can anyone help me install it?
I've installed v4.0.1.4, but I can't install it
I want install from Ubuntu please...
Regards!!
Click to expand...
Click to collapse
Assuming you have S-OFF, install the Android SDK and just boot into the bootloader, then select fastboot and use the command in the first post...
nogoodusername said:
Cwm can be flashed when s-on?
I don't have wildfire... my friend has...
If it works ill flash it from his s on hboot...
Edit: his hboot is 1.01.0002
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
With S-ON, you can only use the fake flash by renaming the .zip to update.zip and "flash" it from the stock recovery to launch CWM...
nejc121 said:
So...what's new in this version?
(Also, is there a way to change the color of text in the recoveries, I want the orange color back )
Click to expand...
Click to collapse
No idea

Kwen said:
Assuming you have S-OFF, install the Android SDK and just boot into the bootloader, then select fastboot and use the command in the first post...
Click to expand...
Click to collapse
Yes, I've S-OFF.
Turn ON my device on Fastboot, it's connected to computer obviously!
If I run:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
The console says that "fastboot" isn't a valid command.
If I am in Android SDK directory and run:
Code:
./adb devices
The console don't found any device.
Where is the problem?? Is this usable on Ubuntu? I'm use it.
Regards and sorry my bad English

See http://developer.android.com/guide/developing/device.html
"If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux:"

Qarl said:
Yes, I've S-OFF.
Turn ON my device on Fastboot, it's connected to computer obviously!
If I run:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
The console says that "fastboot" isn't a valid command.
If I am in Android SDK directory and run:
Code:
./adb devices
The console don't found any device.
Where is the problem?? Is this usable on Ubuntu? I'm use it.
Regards and sorry my bad English
Click to expand...
Click to collapse
This word in'valid
Change Legend to buzz
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
Click to expand...
Click to collapse

If you're on Windows, have you that in the recovery installation folder?:
AdbWinApi.dll, adb.exe, fastboot.exe and recovery-X.img

Good call, copy paste error
Also if you don't have the fastboot command, you'll need to download the "Android SDK Platform Tools" (under "Tools") from the SDK manager (how did you get adb working though without the platform tools?!)
Should be under the same directory...

Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"

First, I go to "android-sdk/platform-tools" with the terminal.
Then, run this command:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
And the terminal return this:
Code:
< waiting for device >
What's happen? If I run "adb devices", my HTC Wildfire is founded.
Regards!

Did you highlight fastboot in the bootloader/hboot and pressed power to select it?
It should say fastboot usb plug or something like that

Kwen said:
Did you highlight fastboot in the bootloader/hboot and pressed power to select it?
It should say fastboot usb plug or something like that
Click to expand...
Click to collapse
Problem solved!!!
I believed that the device reboots to fastboot when the command executed it.
Sorry ¬¬
Thank you very much!

slymobi said:
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
Click to expand...
Click to collapse
I think you'll need a flashable zip, the one koush provides is just a img and a fake flash .zip

@Kwen, yes copy/past error xD

how can i call the yes/no event in this recovery with an updater-script?
other phones have recovery that have a list of comand,that you can add to an updater-script to call some recovery functions.
also this?

slymobi said:
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
Click to expand...
Click to collapse
How do I do this if the OS itself is crashed and I get a white screen and HTC logo???

[Q] I updgrade my ME176CX, now didn't start

I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.

fran1563 said:
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Click to expand...
Click to collapse
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop

I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.

Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.

fran1563 said:
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
Click to expand...
Click to collapse
Just say what you do not understand, I can explain

Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
Mis012 said:
Just say what you do not understand, I can explain
Click to expand...
Click to collapse
Thank you mate, I'm going to try. I'll write you wherever going to happens. I aprecciate!

Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
tried fastboot boot droidboot.img several times, device just reboots to fastboot and throws the same errors
Fastboot Starting....
Fastboot Starting....#1
Fastboot Starting....#2
Fastboot Starting....#3
i've searched and found different ways of flashing ME176CX but never a complete solution. With the INtel flash tool I can't find the DNX or IFWI files, with the Asus Flash Tool, cant find the raw firmware file. Can you help???

christelle868 said:
tried fastboot boot droidboot.img several times, device just reboots to fastboot and throws the same errors
Fastboot Starting....
Fastboot Starting....#1
Fastboot Starting....#2
Fastboot Starting....#3
i've searched and found different ways of flashing ME176CX but never a complete solution. With the INtel flash tool I can't find the DNX or IFWI files, with the Asus Flash Tool, cant find the raw firmware file. Can you help???
Click to expand...
Click to collapse
I can try to. Firstly, the droidboot.img has to be the one from ASUS firmware update downloaded from their site. If it doesn't work with it, well I don't know. Ask the support, take it to the store, or - if you really want to dig into it (it should be possible in your situation), then:
Firstly, buy this: (or something similar, but this is known to work well) http://www.amazon.de/gp/product/B00...qid=1440605402&ref_=sr_1_fkmr0_1&sr=8-1-fkmr0
Then, connect it to your tablet and connect usb keyboard to it. Also power it with another USB.
While starting your tablet, spam F2 key to get in UEFI setup. Then, follow some "tutorial" (search this forum for it, I saw it somewhere there) to run Windows/Ubuntu from flash disk. Run any linux distribution, and ask some kind person on lollipop to make an img with dd of entire mmcblk0 . Then use dd to copy it on your mmcblk0.
Warning! this is theoretical. It should work, but I cannot test it. CHECK MULTIPLE TIMES THAT THE img IS NOT CORRUPTED!!!
Lot of luck (even mine, luck will not help my problem anyway)
Sincerely, Mis012

Mis012 said:
I can try to. Firstly, the droidboot.img has to be the one from ASUS firmware update downloaded from their site. If it doesn't work with it, well I don't know. Ask the support, take it to the store, or - if you really want to dig into it (it should be possible in your situation), then:
Firstly, buy this: (or something similar, but this is known to work well) http://www.amazon.de/gp/product/B00...qid=1440605402&ref_=sr_1_fkmr0_1&sr=8-1-fkmr0
Then, connect it to your tablet and connect usb keyboard to it. Also power it with another USB.
While starting your tablet, spam F2 key to get in UEFI setup. Then, follow some "tutorial" (search this forum for it, I saw it somewhere there) to run Windows/Ubuntu from flash disk. Run any linux distribution, and ask some kind person on lollipop to make an img with dd of entire mmcblk0 . Then use dd to copy it on your mmcblk0.
Warning! this is theoretical. It should work, but I cannot test it. CHECK MULTIPLE TIMES THAT THE img IS NOT CORRUPTED!!!
Lot of luck (even mine, luck will not help my problem anyway)
Sincerely, Mis012
Click to expand...
Click to collapse
i think he got lost on your tutorial XD

fastboot starting
Please, Please advice ..
And I'm one of those tablets which displays a message starting fastboot 1,2,3. I tried almost everything. Well at least I think that everything is okay or if vv. Please advice how to try it changed. Thank you in advance for answers