Related
Hey!
This is the issue: when I try to turn the phone on by just pressing the red button it goes directly to the fastboor menu. If I try to go to the recovery from there shows "TATTOO" for hours. If i try to go to the recovery dirctly by pressing HOME+ red button, it firsto shows the fastmenu for a second and tries to boot unsuccessfully. During this boot tries, I try to get some info with adb logcat, but the device is not casting anything. And well, if a picture is worth a thousand words, I guess a video is way better:
youtube.com/watch?v=zAejyMIVNGk (newbie, no urls!)
sorry for my english
And well, I have no idea how I got to this, this used to be my phone, but I bought a Nexus One and gave this to my sister, who has no idea what happened (as usual). Oh, this morning somehow I managed to get to the recovery menu, and booted until the android bootscreen, then vibrated and died again. I got to the recovery again, made a nandroid backup and wiped all data, it booted successfully, but the rom had no home application and ran really bad.
I was about to try to make a goldcard and install the stock RUU rom, but if I have no adb I cannot make one...
Any idea?
PS: the rom was nFinity 1.18 (2.2 Froyo) and the recovery was the lastest Clockwork.
PS2: I just realized that in every place I say fastboot I mean HBOOT, sorry again
sounds like recovery is still there, if you hold home + menu when phone if off , and then click red power button you should get recovery menu.
Then hopefully you can try full wipe and install a rom , rember the first time u boot a rom might take a few minutes
let me know how it goes
Yup, not using that method but I can manage to get to recovery sometimes. I'm trying to flash another ROM, but for some reason it doesn't let me. I've tried KalimochoAz (gingerbread) and HDCR (donut) and says something about assertion failed when checking if the device was click on the first case and in the second, complains about unsupported stuff...
I was about to try another roms by random but the SD does not refresh or even mounts, there must be something really messed up with this phone...
You can try to flash your stock rom from fastboot.
You don't need a goldcard, just run the update utility on pc, go to your temp directory and take the rom.zip file, rename it to CLICIMG.zip, copy it to sd card, put card on device and on fastboot menu pres vol down to start flashing the rom. I is the same version with the rom that device has before rooting, you will not get any errors.
I think there's a little misunderstanding here, mainly because of my confusion, it's not the fastboot menu qhat I get, but the HBOOT menu, and pressing the back button in order to access fastboot doesn't work...
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
manutenfruits said:
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
Click to expand...
Click to collapse
Of course will not work like this.
You must first run the RUU utility on pc and while is open to search your temp directory(maybe is inside another folder) for rom.zip file. This is the rom, the executable is an installation program which contain the rom and the app to flash the rom from pc packaged. You need only the rom.zip for flashing from sd card.
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
manutenfruits said:
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
Click to expand...
Click to collapse
You don't need to go so far. Just run the ruu utility and when the first screen appears go to temp dir(c:\users\you user's name\local\appdata\temp on windows 7). The executable is an encrypted package and when you run it extracts all included files and then starts the installation program. These files will deleted after this program exits(when the installation complete or an error occurs)
Cool! I just renamed it to CLICLIMG.zip and I finally loaded. The problem now is that when it finishes, instead of asking me to flash it, says
"CID Incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No"
While running the RUU I made sure that it was for HTC Tattoo since it showed me the device during the steps. And I got it from a post describing the steps to flash it using the goldcard.
Furthermore, this error is something similar to what happened when I tried to flash from the recovery. This is REALLY weird...
Probably this isn't the sama as your device's stock rom. I think goldcard needed for flashing any htc original rom, but without goldcard only the device's version will be flashed successfully. Try to download other original roms if you don't know which you had before.
Here is a site with shipped roms for tattoo:
http://www.shipped-roms.com/index.php?category=android&model=Click
The RUU wasn't a problem, I tried now with a goldcard and flashed successfully! I could not get ADB connection to make it, but I once made one and still had the .img in my mail inbox.
But still nothing has changed...
pressing on drives me to the HBOOT screen, whose only options that work are "simlock" to flash CLICIMG.zip, and recovery (freezes on "TATTOO")
EDIT: does not freeze, but goes back to HBOOT after a while... ¬¬
You say that now you have the stock HTC rom and again you cannot boot it and instead the device reboots again to HBOOT?
Then maybe you have a hardware problem which leads to this behaviour.
OK, now I guess it still has warranty, but the problem is that I rooted it.
But now that I flashed somehow the original rom, should be no problem right?
Yes, if you successfully flash the stock rom, you're not root any more.
had that problem to, but theres easy fix for it without doing all whats being sayd here
Even tho phone dont boot annymore and stays on logo plug in the usb cable
and work with adb shell and reflash recovery (to be good tattoo-hack.ko etc tricks need to be done before doing it or you get errors)
http://forum.xda-developers.com/showthread.php?t=716282 step 1.5 and tools from step 1.3
and ether get Amon RA recovery or clockworkmod and use
Code:
./flash_image recovery /sdcard/recovery.img
then reboot into recovery
HTML:
adb shell "reboot recovery"
mount usb put in a custom rom and flash it
if all done well should work (had same problem)
bascly adb still work even if you think you bricked phone just have to let it "startup"
Greetings
I'm afraid that won't work. I've been trying all the time with adb logcat and adb devices unsuccesfully. I thought that the TATTOO bootscreeb would give me some feedback in all cases, but now doesn't seem to work...
I've had similar problems when trying to flash nfinityGB.
My problem was that I missed something on the way from
- creating a gold card
- rooting device
- installing recovery
- flashing rom
All I did was to download and execute "RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe" (or any other ruu).
Be shure to have SDK with all drivers installed properly.
After this your device is in unrooted (original) state as dancer_69 already told you.
Now you can decide whether to claim warranty or properly follow the guides on xda to get root and flash custom roms.
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
manutenfruits said:
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
Click to expand...
Click to collapse
Something like this thought when I said that maybe is a hardware problem.
I'm having an irritating problem.
I've rooted my wife's Gen 1 Orange SF with Androot, even repeated it when I started having problems to make sure the root had worked. SuperUser is installed and working so I know it has gone OK.
I've installed Recovery Manager v0.36, which has root access.
The current recovery is listed as "unrecognised"
I flashed the following CWM - recovery-clockwork-3.1.0.1-blade-gen1.img (MD5 checksum correct)
I get an "installing" message, then back to the Recovery screen and the recovery is still listed as "unrecognised".
One of the guides I found on Modaco is quite specific about using Recovery Manager v0.34 (though I suspect it just hasn't been updated with the latest release) so I've also tried this using that version and no joy.
So... I thought I'd try the FASTBOOT method. I turn the phone off, remove and replace the battery. Turn the phone on whilst holding the up volume button, and the phone just boots up normally. I've tried this repeatedly, I don't get the big grey square that people report when FASTBOOT fails, I just get no response at all.
Grrrrr!
Any thoughts?
Hmm, when you power up holding volume up key (held for a couple of seconds) does you phone show a static green android logo, or does it boot up fully to the lockscreen?
If only to the android logo, means you're in fastboot.
Edit: you can replace the green android logo with Orange's logo in the above comment if you haven't flashed an alternate ROM on the phone as yet.
I also had the same while trying to flash a recovery to my friend's Blade. I understood that i have been flashing the wrong recovery all this time (though it showed for gen1 and i had a gen1). I used the given recovery(link provided below), and it worked for me like a charm. Use the link download on root of sd card. Use recovery manager to install it. If the recovery manager shows that it has identified the cwmod version then its done or else if it again says unrecognised try different versions of cwmod.
Preferably after getting cwmod to working convert your gen1 to gen2 (wbaw method). Then you can flash a custom rom and use ROM manager to upgrade your cwmod recovery.
http://android.podtwo.com/recovery/archived/recovery-clockwork-3.0.2.8-v9-gen1.img
To Convert gen1 to gen2:
http://forum.xda-developers.com/showthread.php?t=1103096
harmohn said:
Hmm, when you power up holding volume up key (held for a couple of seconds) does you phone show a static green android logo, or does it boot up fully to the lockscreen?
If only to the android logo, means you're in fastboot.
Edit: you can replace the green android logo with Orange's logo in the above comment if you haven't flashed an alternate ROM on the phone as yet.
Click to expand...
Click to collapse
He hasnt been able to install CWmod yet so no green logo will appear. Due to unrecognised version only DELL logo appears and hangs or it reboots normally. And yes FASTBOOT is not enabled in gen1 devices so thats why i say to convert to gen2 as soon as possible.
Hi Be4con,
I flashed a batch of 10 blades the other day, and wrote my own little guide for it. I had exactly the same problem as you with the first two i tried to flash.
The guide on modaco does work, but i found i had to use a much older version of clockwork mod. I used 2.5.0.8 (if i remember correctly) not at work just now so cant see my notes. This was picked up by the recovery no problems and i was able to move on from there.
Hope that helps
Hi
You have try to flash directly to your device with a terminal emulator
type SU
accept SuperUser autorisation
type flash_image recovery /sdcard/recovery_xx_xx.img (you find the good version on the recovery on internet)
reboot your phone with volume + down
if you have any problem to find the fine recovery or to flash the recovery contact me on pv . this method work with my zte gen1
Hi I am a noob, so please be gentle.
I tried to install the cyanogen for ZTE blade 7.02 (gingerbread) on my android which was running a froyo by cyanogen.
First I unzipped the gen1-gen2 on my PC and moved the image folder to my phone, then copied the cyanogen zip and the Google apps (gapps)zip to the phone
I used clockwork to install the cyanogen and google apps, wiped the data and cache and rebooted.
Found no google apps and no market on the phone.
Tried reinstalling gapps - no difference.
tried reinstalling cyanogen and got the following message:
Installing://sdcard/(the cyanogen).zip
finding update package
opening update package
E:can't open / (the cyanogen) public.zip
(bad)
Installation aborted(I had the ss3 rom name in there so have changed it.)
I tried installing 3 other gen 2 roms, and they all give the same message, but the gapps zip will install.
I also notice that though I have repeatedly wiped everything (including the davix) I still see (in clockwork and through the PC ) all my old data on the sd card
I wondered if
The reason it won't install is because it is still gen 1
Can you answer this, please?
Thing is I dare not install a gen 1 rom because it might brick it.
I can't use mr pigfish to find out if it is still gen 1, because I can't download it as market on my PC won't send it. I cannot install market or any other google apps on my rather functionless phone. I have no contacts, and my email is set up by imap.
Not only that but the Home key won't work except in clockwork mode.
I am due to go away in two days and need my phone by then.
I have searched the forums, and have trie solutions, but am stumped. Any ideas.
Oh, I haven't tried using TPT before apart from the gen 1-gen2, and understand that it is non-recoverable. should I try that?
When you put the gen2 image on the root of your SD card did to press power, vol + and menu at the same time?, you should see some green writing.
sent using tapatalk
Thank you for your help.
I didn't do that at the time, though I have tried doing that since but I get the green android even though I hold it for ages, and when I let go it still stays on the green man.
someone else suggested holding just the volume up and power, but that does exactly the same.
Should I copy it over again and try again, do you think?
I tried it again, again only the green android, nothing more.
Your phone is still gen1 then, this is why you are stuck at the android picture.
You probably will need to restore your nandroid first.
Try this:
Download gen1 to gen2 (there is a download link in this section) http://forum.xda-developers.com/showthread.php?t=1258855
Unzip the file and place the image ( the image is called image, not gen1 to gen2) on the root of your sd card (ideally it is best to do this on a pc)
Also download and place the Rom you wish to use on the root of your SD card (cyanogenMod 7.1.0 stable release works well) http://forum.xda-developers.com/showthread.php?t=1297776
DO NOT UNZIP THE ROM at this stage.
Put the SD card back into the phone.
Power off the phone, hold menu & vol + (up) & power at the same time, you should see some green writing, wait until it is finished (well done your phone is now gen2)
You should now arrive at the clockwork recovery screen, if not power off the phone, then hold vol - (down) and power (together), clockwork will boot.
Now using clockwork recovery, clear data/factory reset, then install your rom from the zip, that is all there is to it, obviously you'll have to enter your login details to use the market and sync your contacts etc, but your phone should now be working.
Don't forget to make a nandroid backup.
Goodluck 
sent using tapatalk
sent using tapatalk
Thank you.
Firstly I cannot copy the files on my PC as my cardreader will not read the sdcard (it is limited to 4gb,) and I have the same problem with my laptop.
Having transferred (by usb) the appropriate files (image, mod zip and gapps zip) I tried to do exactly as you said, but when it gets to the holding home, power and volume up I am still stuck at the green robot.
In fact I realised as I started to type that I had been holding the menu key rather than the home key, so I tried again, this time doing as you advised and holding the home key(as well as the power and volume up) I am still stuck at the green robot.
So I assume that the phone is still gen 1?
Do you think I should just give up and try a gen 1 rom. Or is that to make assumptions and risk bricking it?
Caddi
Aef 101, Many thanks - you linked upthread to a thread about gen1 and gen2 and later in the thread, there is a reply which I had missed reading, which states:
"Some sd cards seem incompatible & wont perform a tpt flash."
I wonder if that is the problem here with mine?
Considering that initially I didn't do a tpt, and then when I did it didn't work, I might still have the gen1.
I won't hold anyone responsible, but I would love an opinion on whether you or anyone would risk trying a gen 1 mod.
It may be an idea to try a different SD card, I use the cyanogenmod 7.1.0 Rom, if you want to try a gen1 Rom you'll be happy with the last ginger stir fry rom also found on this site.
As I have said, I think you are trying to run a gen2 Rom on a gen1 phone, just boot into recovery and reinstall your old backup.
sent using tapatalk
Place the image on the root of your sd card.
Press menu, vol up, and power at the same time, if you see green writing then you are doing it correctly, then use recovery to install the Rom.
sent using tapatalk
Thanks I think I am going to try the stir fry rom. Your help has been much appreciated
(PS I really fancy ginger stir fry for tea too!)
I am delighted!
Thanks everyone. I am now running Ginger stirfry, and quite importantly I have learned a lot about installing Roms in the process.
caddi
My tf101 cannot enter recovery anymore
when i try to enter recovery ,
there is a " ! " on the robot , then tf101 reboot automatically
then freeze on the ASUS logo page
I cannot boot up the machine in normal mode too !
my tf101 is B70 version, someone help..thanks
! with the Android guy is recovry, stock recovery.
instead of Vol up to get into revovery, wait till you get options to cold boot or wipe device.
try booting that way.
also what were uou doing when it gotvstuck at that screen?
baseballfanz said:
! with the Android guy is recovry, stock recovery.
instead of Vol up to get into revovery, wait till you get options to cold boot or wipe device.
try booting that way.
also what were uou doing when it gotvstuck at that screen?
Click to expand...
Click to collapse
i tried cold boot , but it said cold booting up linux .. but no response
i tried wipe device , but it still freeze on ASUA screen too
yesterday, i try to root and install CWM via Prime V4.5
then the device comes this .....
Thanks ...
Never heard of that root utility before. You may not have used the right rooting utility for your device which can cause a brick situation. Also, are u sure u dont have the tf 101 and not thr tf prime? The vipermod utility found in the tf prime forum will root ics for both the 101 and prime. My suggestion is that u make sure u have the right device and search the right forum for brick recovery, unroot, or return to stock threads. They are usually found in the development sections.
Sent from my SGH-I777 using XDA
viperMod PrimeTime 4.5 will only root the TF101 and shouldn't be used to install CWM. That's why it bricked.
cholywell said:
viperMod PrimeTime 4.5 will only root the TF101 and shouldn't be used to install CWM. That's why it bricked.
Click to expand...
Click to collapse
i had an issue that was caused by lack of sleep last night that i might be able to help this guy out.he never used it to flash CWM.. he rooted it and never flashed from within the CWM app. The stock recovery doesn't have options for choosing files ect..
victor1144 said:
My tf101 cannot enter recovery anymore
when i try to enter recovery ,
there is a " ! " on the robot , then tf101 reboot automatically
then freeze on the ASUS logo page
I cannot boot up the machine in normal mode too !
my tf101 is B70 version, someone help..thanks
Click to expand...
Click to collapse
I might be able to help you... I saw your post around 4am. I had the same problem kinda. Was asleep most the day (got done at 6am).
I rooted with viperMod PrimeTime and it worked !
BUT i forgot to FLASH CWM RECOVERY from inside the app and proceeded to install the new ROM after root was made USING the CWM app. What happened in my case , the CWM app restarted trying to flash the new ROM, WITHOUT CWM being my recovery instead rebooted to STOCK recovery and something glitched up. I had the same thing as you stuck on Eee pad never re-starting. Cold boot wouldn't work or full wipe..In my case something conflicted.
Below is the NVFlash of the 3.2 Build of 8.6.5.13 (Latest Build). You need to re-flash again using APX threw your USB connected to a PC (it self installs) :
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
the links are in Grey btw and says US version, ect ..read everything but its very straight forward... ill explain what i did toward the end of the post to simplify it since it took awhile to figure it out. Ill add side comments threw the process that explains better than the link.
Attention: These tools are designed to bring your device back to working condition. They are great for getting back to stock if you need to send your device in for repair or you need to downgrade to stock in order to root your device, etc.
Instructions for Windows users:
1. download the file from the original link i gave above. NVFlash of the 3.2 Build of 8.6.5.13 (Latest Build) USWindows
2. unpack zip to desktop.
3. Press Volume up and Power at the same time on your Transformer to enter APX mode, connect to pc (hold for about 7 seconds). Basically, Power off.. THAN, power and Volume up at the same time to enter APX mode. IMPORTANT!! the screen remains BLACK like its frozen ,with no writing or indication something is happening. that's normal and the original poster in the link never mentioned it. That is APX mode..
4. drivers for APX are in there if you need them..inside the windows downloaded file its called NVFLASH towards the bottom
On your PC go Device manager.. if APX is working correctly and the Transformer is in APX mode it will appear as an exclamation on the device manager named APX.. you cant miss it.. it stands out. On my Windows 7 PC it changed and said Asus USB (or something like that)
5. double click Run Download.bat file and let run! everything is prepackaged so no copying files, etc. In the same file you downloaded that you unzipped named Windows its the 4th file that says "download" with a gear looking icons.
Your Transformer (based on what happened with mine) will go threw a self install like its pushing files and flashing it..the black screen looks like its being pushed the files and reflashing without a recovery. Your going back to stock. if you dont see anything on your Transformer screen after running/double clicking the Download.bat file ....Right click on APX in the device manager , properties, Drivers, update Firmware, choose manual install and find the Downloaded.bat file and click it. That should do the trick..I did both and only noticed the Transformer lighting up after manually pushing it threw APX.
6. After the device reboots power it off. Then hold vol- and power until you get the option to erase your data.... Select the option to wipe data.
7. Download the latest update from the Asus website if applicable and follow the manual instructions. This step may not be necessary if your OTA update worked or my nvflash is the latest version. US update on there site is 9.2.1.17.Its the only one...
What i did was go back to stock since i didn't see any interesting ROMS..Point is THAT unbricked my device by flashing it in APX mode when it was connected to the PC.
I did use ViperMod again to Root, but used the Clockwork mod app in my Transformer to FLASH CWM RECOVERY to try a few ROMS out.
After trying a few of them out i choose to revert everything to stock, unrooted and reflashed STOCK recovery.
Hopefully that helps you out.. it did work for me...
Thank you so much it worked great
Lantek23 said:
Thank you so much it worked great
Click to expand...
Click to collapse
Glad i could help
Sorry to dig up slightly old threads, but I have a question for you. I have a TF101 that I was trying to update to ICS. It is currently running 3.2 courtesy of the unbricking tool listed in this thread. I had to unstore it as it was bricked from a bad install. That was many moons ago. It won't show an updaate listed, so I decided to go with the manual route. I downloaded the appropriate update (my device lists WW version) loaded it on an SD card had the install prompt come up and rebooted to install... For a split second it shows the android with the gears like it is installing the update and then shows the android with a triangle and exclamation mark. After that, nothing. I have to reboot to get it off that screen. Upon booting, I get a message saying system update failed (2) unknown error. Any ideas?
If Im not mistaken, the zip file you download (I guess from asus?) contains another zip.
Thats the zip you should place on your SD card, did you do that?
Also try renaming that zip to EP101_SDUPDATE.zip (the one extracted)
I already had the zip extracted, and renaming didn't do anything.
Killa357 said:
I already had the zip extracted, and renaming didn't do anything.
Click to expand...
Click to collapse
Are you rooted? Did you remove any system apps?
Another thing to try is on your micro sd card, make a folder name ASUS and inside that folder another folder call Update, inside the Update folder put the extracted zip file (don't rename). Turn off TF and turn it back on, see if it will detect the update file.
If that fail, you did mentioned you use the unbricking tool, use that NVFlash to flash a compatible ICS ROM
It isn't rooted anymore since I ran the unbricking tool, and no system files were modified. Placing it in Asus>Update folder didn't work. I may end up having to really do things manually...
Killa357 said:
It isn't rooted anymore since I ran the unbricking tool, and no system files were modified. Placing it in Asus>Update folder didn't work. I may end up having to really do things manually...
Click to expand...
Click to collapse
You don't need to be root to use NVFlash.
Just when with a slightly older version of the update and it worked. There may be something wrong with the file Asus has hosted.
Hi
I have a slightly different problem. I have rooted my B60 serial number, it has the ICS from ASUS on it and it boots fine, its rooted and it works. Now the problem is I thought lets try a clockwork mod and play with custom roms.
So I set my win 7 up to adb etc, and pressed power button volume button - and off to recovery I went...
but all I got was a little green android on its back chest open and an exclamtion mark. No adb fastboot devices command.
I seem not to have a recovery nor a way of forcing a custom recovery.
Should I NV flash or just be happy the tab works and leave well alone?
Any other answers since a lack of recovery may come back to haunt me sooner or later.
I also tried the power button vol uyp for 7 secs and nothing happens I can get to the cold boot erase data option on power down, don't want to do that yet since Im not sure what data gets erased and I may have a totally non working tab.
Use RecoveryInstaller to install cwm recovery
Use RecoveryInstaller to install cwm recovery
This is my problem I can't get recovery - nor can I get adb to see the device. It shows as a hard drive/storage device but not in adb.
A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David
Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!
Thanks
Darth said:
Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!
Click to expand...
Click to collapse
Thanks. Unfortunately the site won't let me post there. I'm a new member.
Ah, There's no Q&A section. Normally now if you post in a development thread it automatically creates or posts in a thread in your device section Q&A.... But this won't work cause your section has no Q&A.
I will have your thread moved to your devices General section.
Good luck!
More on 'bricked' Milestone 2
datatone said:
A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David
Click to expand...
Click to collapse
I am going to journal my experiences with this, in the hope that it will be useful to someone else.
Possibly the mistake that I made when flashing the CM11 (see above) is that I didn't put the md5 sum file onto the SD card with the archive. Note that all downloads have a .zip and a .zip.md5sum file. The phone output a message to say that it couldn't find a checksum, but that it was going ahead anyway. Possibly, had I put the md5sum file in, a fault with the zip file would have been detected and I may have been saved from this issue.
I have found references to a 'Motorola factory cable' which is a cable that is wired to persuade the phone not to worry about battery state and to operate the flashing utility from the usb cable power. this is obviously useful in the factory for programming the phone without a battery. See this link for information:
[unfortunately the site didn't allow me to attach a url to 'www dot droidforums dot net' where you might find a posting 'how-why-to-make-your-own-motorola-factory-cable', which is a well-writen and informative article]
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
My technique for putting the archives onto the SD card is to take the card out of the phone and put it into my laptop, so that I can simply manage the files on it with standard Windows file browser.
I can get to a very promising recovery utility by holding down the 'X' key on the keyboard whilst switching the phone on. The Motorola 'M' logo comes up and the screen then displays a 3D orange triangle with an exclamation mark and a little green Android man. If I press the keyboard '@' at this point, I jump into a recovery menu.
The recovery menu has options:
* 'reboot system now'
* 'apply sdcard:update.zip'
* 'wipe data/factory reset'
* 'wipe cache partition'
The 'apply sdcard:update.zip' seems to offer the promise of recovery.
I have tried placing both:
* cm-10.2-20140312-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
and
* cm-11-20141003-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
onto the sdcard (renamed as 'update.zip' and 'update.zip.md5sum').
In both cases the recovery utility says:
---
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/caller
-- Install from sdcard...
Finding update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
---
If I remove the update.zip.md5sum file, the result is identical. Therefore I don't think that this utility is using the md5sum for archive file verification. The problem that I seem to have at the moment is that I need an archive in the right format for the factory recovery utility.
I will be researching this and will add to this thread when I find an answer.
As a little bit of extra information, whilst fiddling about with the buttons during power up, I did manage to get a screen that said:
---
Bootloader
70.12
Battery OK
OK to Program
Connect USB
Data Cable
---
I guess that this is a lower stage in the bootloader chain, and suggests that there is hope if your phone is screwed up to the extent that you can't get the factory recovery utility. Thankfully, I don't seem to need to investigate what is required at the PC end to make use of this low level programming aid. (If anyone knows, it would be good to hear the details, for future reference and help to others).
Alas, I'm not sure what I did to bring this screen up - I fiddled with the volume, camera, and power buttons whilst the phone was starting up.
Regards,
David
Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.
Progress
rabinhood said:
Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.
Click to expand...
Click to collapse
Thank you very much. I have spent all day researching this.
I have discovered 'RSD Lite' and the ability to get the phone into the bootloader mode that I described by starting the phone and keeping the camera and volume buttons pressed.
I can boot to the stock recovery mode by powering up with the 'X' key pressed and then pressing '@'
I don't think that I can access TeamWinRecovery. There may be some way to do this that I don't know.
I did do a complete 'Nandroid?' backup of the system before I started this, so I guess that if I can get TeamWinRecovery or clockworkmod recovery back, I can restore to my previous working state.
What I have tried is 'G.O.T.’s OpenRecovery' to get a recovery installed. I put the OpenRecovery folder and the update.zip onto the SDcard and tried to flash it with the stock recovery utility. I got the "E:EOCD marker occurs after start of EOCD E:signature verification failed" error. I read that this means that I am not properly rooted (I thought I was) and I need to install 'vulnerable recovery' using an sbf file and RSD Lite. I have tried 'vulnerable_recovery_only_RAMDLD90_78.sbf' but the process errors, and what I read suggests that this might be due to the older bootloader version.
I tried to find an old stock android sbf for the phone, but all the links to such things seem to be dead.
I did try the factory reset from the stock recovery as a means to fix the bootloop. It didn't work.
You clearly know a lot about this. I would appreciate help to get back to something that works, maybe the last backup that I did.
I am also puzzled by why the upgrade to the CM11 from the CM10.2 failed. Did I do something wrong, or is there some compatibility issue with my phone? I never had a problem updating from the original motorola software to the cyanogenmod, then to the CM10.2.
I think I became a little over-confident.
Thank you in anticipation,
David
---------- Post added at 06:20 PM ---------- Previous post was at 05:59 PM ----------
rabinhood said:
Hello.
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key).
Click to expand...
Click to collapse
Ah! the penny drops. The stock recovery that I can access will only install archives signed by Motorola. Hence the signature errors that I get when I try anything else. So I understand that if I can only get to the stock recovery, I can only use it to reinstall a stock android.
So the problem is where to find a stock sbf file to reinstall Motorola android as a first step to getting back to CM.
I guess that this is the only way to get back to clockworkmod recovery or teamwin recovery?
If I can get one of these recoverys running, I can simply restore to the last working system, I guess?
Regards,
David
---------- Post added at 07:07 PM ---------- Previous post was at 06:20 PM ----------
david.datatone said:
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
Click to expand...
Click to collapse
I realise that I was mistaken about this. There is no image of a battery filling up. The white LED by the USB socket lights when the charger is plugged in, but I can't be sure that the battery is charging.
Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.
1000 Thanks
rabinhood said:
Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.
Click to expand...
Click to collapse
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David
david.datatone said:
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David
Click to expand...
Click to collapse
recommend you return the original rom using RSDlite and start doing it all over again putting the rom CM10 and then cm11