So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16
ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).
Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:
ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.
Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse
It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it
ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.
Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?
Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
It now says Relocked then underneath security warning. Is that good?
ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.
Will i have to re unlock the boot-loader for the RUU.exe to work?
ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.
Yeah it says updating 0 out of 7 sending ........................
ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.
This is what comes up
It send that 1 had been sent then it said error
Related
I think I have bricked my phone. I followed the instructions listed here:
http://forum.xda-developers.com/showthread.php?t=834228
but have when i restart the phone, it is just stuck on the words HTC
doesn't load into anything else.
What should I do?
Well as your phone powers on its not a proper brick, when it powers on and gets to the first boot screen like you say there is usually like a 99% chance it can be recovered.
Edit: stupid thanks button!
How long do you leave it on the htc bit before you power down again? maybe your just not waiting long enough.
left it on for 10 minutes.
all it says is "HTC" in green...
Are you able to get into hboot? Try holding the volume down key while you turn on the phone.
One easy thing to try would be to flash an RUU, make sure you find the correct one for your phone (Z or G2) and make sure its the latest one around.
That will return your phone to stock so you can attempt to root again.
yes, yes i can get into HBOOT.
my phone is a g2. How do I flash a RUU?
yukei said:
my phone is a g2. How do I flash a RUU?
Click to expand...
Click to collapse
my mistake, wasn't aware there appears to be no way to flash a new firmware on a g2 unless its by ota.... sucks
edit: just bare with us we will have an answer for you soon.
What about recovery? There should be a recovery option in the hboot menu.
Thank you so much!!
Have you got a custom recovery?
If so, flash a new rom
I tried recovery. It turns into a blackscreen with a phone in the middle and a read triangle with a ! on top of it.
I dunno if that is telling me to not turn off the phone.
MacaronyMax said:
Have you got a custom recovery?
If so, flash a new rom
Click to expand...
Click to collapse
I do not think I have a custom recovery.
How do I check?
yukei said:
I do not think I have a custom recovery.
How do I check?
Click to expand...
Click to collapse
no, from your description above, you just have stock.
I have an idea that you should be able to fasboot install a new recovery, then from there you will be able to flash a new rom.
Lennyuk said:
no, from your description above, you just have stock.
I have an idea that you should be able to fasboot install a new recovery, then from there you will be able to flash a new rom.
Click to expand...
Click to collapse
Oh ok. I think I'm a bit more calm now. So is there anything you need to know? In regards to the blackscreen with the red triangle warning sign in the middle. Can reset my phone?
yukei said:
Oh ok. I think I'm a bit more calm now. So is there anything you need to know? In regards to the blackscreen with the red triangle warning sign in the middle. Can reset my phone?
Click to expand...
Click to collapse
I take it you know how to use adb (based on the root process you were trying to do)?
Lennyuk said:
I take it you know how to use adb (based on the root process you were trying to do)?
Click to expand...
Click to collapse
I know some. But not everything. Only the very basics. I have had a rooted hero before. I have had some experience with it.
I am not able to use adb tho. (As in, can't get it to work currently)
when i type "adb remount"
it says "error: device offline"
I have plugged in the USB cable.
basically all you need to do is find the clockwork mod recovery image file
put it in your adb folder
turn phone on hboot, and select fastboot
then type the following into your pc
"fastboot flash recovery [recovery.img]"
obviously replace [recovery.img] with whatever your recovery is called (and no [])
then you should be able to boot into clockwork mod recovery and from there you can install a new rom.
before I really do anything wrong here, would you be able to direct me to an image file?
http://forum.xda-developers.com/showthread.php?t=834731&highlight=cwm+recovery
i have found this thread. however, there is no option to download the recovery file.
yukei said:
before I really do anything wrong here, would you be able to direct me to an image file?
Click to expand...
Click to collapse
use this one for now, you can update with a newer one after your booted back to a rom
http://forum.xda-developers.com/showthread.php?t=834731
Hello. I just tried to unlock the bootloader on on Verizon Galaxy nexus. Now it's stuck at the bootscreen with the lock image. I did a search and couldn't find a exact answer for my issue. I hope I haven't bricked my phone. Anyway, any help would be appreciated.
I wasn't trying to root just unlock the bootloader. It appeared everything went ok but, now I'm stuck. I used the same method for unlocking the bootloader on my GSM G-nex and it worked.
I know I've done something wrong or this may be something simple. I just need help so I can use my phone.
are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.
same thing here... I posted a request for a LTE boot.img since can still get into the bootloader
Goat_For_Sale said:
are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.
Click to expand...
Click to collapse
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"
Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
qnet said:
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"
Click to expand...
Click to collapse
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot
Goat_For_Sale said:
Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot
Click to expand...
Click to collapse
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.
qnet said:
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.
Click to expand...
Click to collapse
you should have let the animation run for like 10 minutes the phone has to rebuild the first boot can take like 15 minutes sometimes.
try booting into the bootloader see if that works still
Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.
qnet said:
Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.
Click to expand...
Click to collapse
you could try fastboot oem lock and see if that works but if the phone wasn't booting i don't know if that will fix it but worth a shot.
try it out and see. it shouldn't do any harm to try
I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.
GirLuvsDroid said:
I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.
Click to expand...
Click to collapse
Thank you, I'll try that.
I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?
qnet said:
I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?
Click to expand...
Click to collapse
you could download the recovery image from
http://forum.xda-developers.com/showthread.php?t=1392336
then when connected in fast boot flash it with
fastboot flash recovery recovery.img
(rename the file from the linked thread to recovery.img)
this should write your custom recovery partition.
once you have that though you are still not going to be able to boot but it would allow you to flash a nandroid backup if someone made one for you or a LTE based rom
EDIT: you could also try a factory data reset and wipe dalvk cache from withing cwm. that may fix your boot problem
I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen. All of the files I'd put on my internal storage were wiped (during the oem unlock, I assume) but I'm in the stock rom but Superuser was installed and I have root access.
Hope it helps.
EDIT: looks like this is the same thing Goat_For_Sale posted above, but his command flashes CWM where mine temporarily boots into it. Since most of us will be installing CWM anyway I'd recommend using his command instead.
mixedlemon said:
I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen.
Hope it helps.
Click to expand...
Click to collapse
where did you get the lterecovery_cwr.img ? could you link to it please
I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg
mixedlemon said:
I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg
Click to expand...
Click to collapse
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.
Goat_For_Sale said:
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.
Click to expand...
Click to collapse
Ahh no problem.
I got pretty worried for a second that I'd already broke my shiny new Nexus, so I'm really hoping I can help out someone else that had the same problem.
Solved
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.
qnet said:
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.
Click to expand...
Click to collapse
So you were just able to go through the Rootzwiki method? Were you stuck at "Downloading...Do not turn off target !!" screen when you went to boot screen originally? My device still can't be detected :/
The screen of my HTC Desire (Gsm, slcd-version, I believe) got hit, and broke. The touch digitizer was broken but works, lcd is black. I bought a new (s)lcd screen (should be slcd, like the original one), but no picture there either. After it broke unlocking it would make the edges of the screen flash green.
Is the main board broken (I couldnt see clear physical damage), did I assemble it wrong (tried two time in case of some cable left loose), or could my new display be broken?
Phone does boot up, sound, wifi, buttons, and even the somewhat cracked touch digitizer do work, so its not that it gets stuck in boot or anything. I have tried some of those functions by taking a screenshot with adb, and the estimating where I have to tap the screen.
Q1. Is there any hope to revive the screen? I have pretty much given up on the screen though...
I have thought of using it as a part of a UAV-project(GPS,camera,Acc and gyro sensors,... Pretty nice ). The problem is that I would like to interface it to some other hardware using the Accessory Development Kit, which requires 2.3.something, and my Desire is 2.2. I have tried to flash CM7 using various tools without success (Hard without the screen). My phone was, and is rooted though. It has CWM 2.x.x(I don't remember the exact ver).
Q2. What is the preferred way to flash a new ROM without access to the screen?
updated
I've updated the questions to be a bit clearer...
Anyone?
Take a look at ..
http://tjworld.net/blog/htc-desire-tear-down
Hope it helps
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
Its for a AMOLED screen, but might give you some pointers.
There is only one cable that connects the screen to the main board, so I don't believe assembly is the problem... Do you think putting it into a oven for a while to reflow the solder would help, in case it is the connector that is the problem? In case the board is electronically broken there is not much I can do
Sent from my Nexus S using XDA App
I read from somewhere about it being possible to make some kind of script for the recovery to execute. I think some tablet had such script installed at the factory to keep users from accessing the recovery-menu manually. Can I do this with CWM 2 to make it flash a rom without user interation, and if possible, where could I find instructions on how to do it?
To flash a new rom you could execute the steps on another phone, write them down and do it on your phone - as long as the volume and power buttons still work. Or just use the 2.3.3 RUU, if you don't need root for your plans.
muellersmattes said:
To flash a new rom you could execute the steps on another phone, write them down and do it on your phone - as long as the volume and power buttons still work.
Click to expand...
Click to collapse
Nobody I know has a android phone with CWM, so I can't really do that... I tried to google for images and etc., but cant really find enough. Have the menus changed from CWM v2 (compared to v5)?
muellersmattes said:
Or just use the 2.3.3 RUU, if you don't need root for your plans.
Click to expand...
Click to collapse
I don't think I will need root, but the library I'd like to use is introduced in 2.3.4, so anything below that will sadly not work.
Use this guide:
http://forum.xda-developers.com/showthread.php?t=1096430
It's pretty old, but might still work. There's another similar guide somewhere (read it lately), but i can't find it now.
If you have a Nexus S, look at its recovery, the menu items should be the same. (reboot now, apply update ...)
muellersmattes said:
Use this guide:
http://forum.xda-developers.com/showthread.php?t=1096430
It's pretty old, but might still work. There's another similar guide somewhere (read it lately), but i can't find it now.
If you have a Nexus S, look at its recovery, the menu items should be the same. (reboot now, apply update ...)
Click to expand...
Click to collapse
I dont see that guy telling what recovery he is using, it wont work if its not the same one?
I do have a nexus S, but have the menus changed in different versions of CWM, because my NS has v5.something and Desire was v2.something?
Then just flash the same version of cwm onto the desire? Don't need a display for that...
muellersmattes said:
Then just flash the same version of cwm onto the desire? Don't need a display for that...
Click to expand...
Click to collapse
Of course! I didn't think
I have never installed a recovery to a phone that has already been unlocked, so every time I have flashed a recovery, it included unlocking the bootloader or something similar, and required some kind of interaction on the phone. I guess that is the reason why I never even thought about updating the recovery.
I just saw that fastboot can also flash an update.zip. The command for that would be
Code:
fastboot update <update.zip>
(replace <update.zip> with actual filename.) Don't know if that works well, but you might give it a try.
muellersmattes said:
I just saw that fastboot can also flash an update.zip. The command for that would be
Code:
fastboot update <update.zip>
(replace <update.zip> with actual filename.) Don't know if that works well, but you might give it a try.
Click to expand...
Click to collapse
Thanks, will try that later...
muellersmattes said:
I just saw that fastboot can also flash an update.zip. The command for that would be
Code:
fastboot update <update.zip>
(replace <update.zip> with actual filename.) Don't know if that works well, but you might give it a try.
Click to expand...
Click to collapse
fastboot flash recovery recovery.img -> Fails because image is not signed (is my phone s-on?)
fastboot update update-...-desire.zip -> errorackage has no android-info.txt or android-product.txt
tried to run unrevoked3 to s-off, flash recovery and so on... -> Internal error: installing package failed
varesa said:
fastboot flash recovery recovery.img -> Fails because image is not signed (is my phone s-on?)
fastboot update update-...-desire.zip -> errorackage has no android-info.txt or android-product.txt
tried to run unrevoked3 to s-off, flash recovery and so on... -> Internal error: installing package failed
Click to expand...
Click to collapse
On which stage do you get Internal error: installing package failed?
Did you manage to S-OFF your device?
Alaa said:
On which stage do you get Internal error: installing package failed?
Did you manage to S-OFF your device?
Click to expand...
Click to collapse
Something about "installing service" flashes on the screen before the error...
EDIT: Still FAILED (remote: signature verification fail)
Sent from my Nexus S using XDA
Does anyone have any ideas?
Am I doing something wrong, or is my phone broken somehow?
As your display does not work, you can't tell if you're s-off, right? But you could try to run AlphaRev again to make sure. Unr3voked just roots.
Looks like the fastboot update command is not designed for recovery flashable images. As said, i never tried.
muellersmattes said:
As your display does not work, you can't tell if you're s-off, right? But you could try to run AlphaRev again to make sure. Unr3voked just roots.
Looks like the fastboot update command is not designed for recovery flashable images. As said, i never tried.
Click to expand...
Click to collapse
Well atleast "fastboot getvar security" returns security: on, so I guess I am still s-on. I thought unr3voked also s-offs. Atleast that is the utility I used to flash a custom recovery and root a completely stock phone. I have never used AlphaRev, but I'll look into it...
Hello Members
I need a Official recovery.img dump for this ICS version
ACER_AV041_A100_0.002.00_ww_GEN1 link >>http://vache-android.com/v1/download.php?fileID=116
my recovery does not install update.zip patches and power key does not select any opition
http://youtu.be/CWFlA1W08wE
this is my bootloader version
Bootloader v0.03.11-ICS: Starting Fastboot USB download protocol
help me please
You Can make a backup this IMG with "Acer recovery tool" downloaded from the google play store
thanks
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
I just noticed something, you are aware that image you linked to is a A101 image, right?
masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
thanks now works
u save my tab
rollidark said:
thanks now works
u save my tab
Click to expand...
Click to collapse
I'm glad it worked out for you, but if this fixed your device that you made a previous bricked thread about, could you please to back, and post an update to that thread discribing what you did, and how you did it, to get the device back up again? It'll definatly help anyone else with this same issue.
You're welcomed, we are here to help each other after all. You should follow pio's advice and describe what you did so others can benefit from your experience. We have to make such info as readily available as possible.
Having the same issue described
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.
citricube said:
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.
Click to expand...
Click to collapse
He had a brick not a locked bootloader, you can't flash a bootloader directly if its locked with fast boot.
Tapatalked from my Galaxy S II.
Awesome
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:
citricube said:
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:
Click to expand...
Click to collapse
Wow that's a pretty bad run, what's wrong with either one?
Yes I know holy threadjack Batman
Tapatalked from my Galaxy S II.
masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks
liltyke said:
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks
Click to expand...
Click to collapse
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
adb reboot bootloader
Click to expand...
Click to collapse
once in fastboot
fastboot erase recovery
Click to expand...
Click to collapse
then
fastboot flash recovery "recovery.img file location"
Click to expand...
Click to collapse
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
fastboot reboot
Click to expand...
Click to collapse
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
Nicely done, masr1979!:good:
masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
thank you very much for the detailed explanation masr1979. I'll give it a shot when I get home from work.
Basically I got the rear camera replaced, it was working great. About a couple weeks later It's running sluggishly because I was running too many apps at once. So I decided to press the reset button while It was lagging out, next thing I know It's stuck at the silver android logo forever. I tried using some update.zip's but that just made the problem worse.
Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.
liltyke said:
Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.
Click to expand...
Click to collapse
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.
pio_masaki said:
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.
liltyke said:
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.
Click to expand...
Click to collapse
So...you flashed the bootloader to get back to HC and now it won't use update.zip? What about booting into android, does that still work? Or fast boot? Or uhm...I seem to recall having to do a hard reset to get the downgrade to work, have you done this too? I never downgraded just seemed pointless when I was already on ics so I'm not experienced with it, just recall seeing the boot loader needing a hard reset to work.
Tapatalked from my Galaxy S II.
No, I never flashed the bootloader, not unless that happens while trying to run an update.zip. adb and fastboot seem to be working. Based on the earlier instructions 'adb reboot bootloader' does restart the A100 and gives me the bootloader message at the top left of the screen. When I run the ' fastboot erase recovery' command I get the FAILED message in the command prompt window and also get a message in red text on the A100 saying 'Fastboot: not support the command in lockmode, failed to process command erase: recovery error (0x2)'. When I run the 'fastboot reboot' command the A100 does restart. So all that leads to believe that the communication from my computer to the A100 is ok.
Booting into Android. The A100 starts and works fine if that is what you are referring too. As far as the hard reset, if that's the process of holding down the volume button while powering up and flipping the lock switch back and forth to reset the unit, then yes I have done that and it does work. My whole goal here is to get the unit to running ICS legitimately and get updates from ACER. I don't care what I have to do, it's just a couple of the other threads mentioned the need to go back to HC to get the official ICS update. So that's why I tried that. But the last time a update.zip worked was when I flashed the leaked ICS. I have got the dead android logo every time since.
Sorry if some of this info is redundant from my earlier post, I just wanted to get it all in the same place.
Thanks again for your help.
hi everyone,
I am in a quite a pickle here. I tried updating my phone with ARHD43 and after doing it couldn't get the WIFI to turn on. I read a bit and found that this is becuase I do not have the latest firmware. So I tried going back to stock through RUU (flashed stock recovery and boot.img) and in the process flashed new recovery and boot images. Now the my phone keeps booting into stock recovery with the red triangle continuously and I can't boot into the OS. From recovery when I select apply from SD card I throws CID error and reboots into recovery again!
I cannot connect to fastboot so I am stuck bad. :crying:
did I brick my device? can I save it? I am S-ON with unlocked boot loader. region is .707
Appreciate your help.
<I have posted a similar question in the ARHD43 thread but haven't recevied a response so posting in here in the general forum again>
simplyaha said:
I cannot connect to fastboot so I am stuck bad. :crying:
Click to expand...
Click to collapse
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
simplyaha said:
So I tried going back to stock through RUU (flashed stock recovery and boot.img) >
Click to expand...
Click to collapse
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?
redpoint73 said:
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?
Click to expand...
Click to collapse
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.
simplyaha said:
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.
Click to expand...
Click to collapse
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
simplyaha said:
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
Click to expand...
Click to collapse
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.
redpoint73 said:
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.
Click to expand...
Click to collapse
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
I will try again and reply.
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..
simplyaha said:
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
Click to expand...
Click to collapse
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
simplyaha said:
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..
Click to expand...
Click to collapse
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.
redpoint73 said:
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.
Click to expand...
Click to collapse
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning :victory:
yes, no more messing around, promise.. :angel:
simplyaha said:
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning
Click to expand...
Click to collapse
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.
redpoint73 said:
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.
Click to expand...
Click to collapse
ccol thank! I will try this tonight and share the outcome.. :good:
eureka! got my phone up and running now. the ruu was perfect. but got my memory card messed up (showing as raw format on the pc). gotta look for a solution for this now :banghead:
but my phone is back! thank you for all the help. much appreciated. :thumbup:
Sent from my HTC One_M8 using XDA Free mobile app