I have the original Milestone 2.1 update on my phone. I rooted it with Universal androot. After some days I downloaded Eris market fix. And then I had to restart, but after the Motorola logo nothing happened.
Hard Reset didnt change anything, but new flashing worked.
I did the exact same mistake (market fix)... after first reboot device did not boot anywhere after the M -logo. I used that as a good sign to get into cutom ROM's and with some nice quides here and little bit googling (to find the right bootloader) my device is now amazing... I love the G.O.T -menu and Nandroid is a must... even for backin up before doing any stupid moves, like market fix...
Related
So I decided that I wanted Android 2.2 Froyo on my sanyo zio and after many hours and tons of work I finally thought I found a way to do it. Rooted the device with Z4 root then ran clockworks rom manager in order to "update" my device. Well I did not see my device on the list and just as I went to click the back button my touch screen decided to be picky and pick one of the random phones on that list. It started the flash and I began to relax a bit (figuring if it was going to brick it would have done it right away) and near the end the phone shut off and still will not boot past the "sanyo" screen.
Is there any way to boot it into a recovery mode so i can put the factory OS back on it? And if so is there a way to put 2.2 froyo on this device?
yes and no
im thinking you can go to boot loader mode by hiting power button and holding a a few bottons randomly i found differnent types of loaded pages by doing this in different ways so if you can get in the correct boot loader you could probely get a spf or something
dzthemachine said:
So I decided that I wanted Android 2.2 Froyo on my sanyo zio and after many hours and tons of work I finally thought I found a way to do it. Rooted the device with Z4 root then ran clockworks rom manager in order to "update" my device. Well I did not see my device on the list and just as I went to click the back button my touch screen decided to be picky and pick one of the random phones on that list. It started the flash and I began to relax a bit (figuring if it was going to brick it would have done it right away) and near the end the phone shut off and still will not boot past the "sanyo" screen.
Is there any way to boot it into a recovery mode so i can put the factory OS back on it? And if so is there a way to put 2.2 froyo on this device?
Click to expand...
Click to collapse
Power off the phone, hold volume up, end, trackball and power. that should get you in to fastboot mode.
Hopefully you have or can get a hold of the boot.img and system.img for your zio (is it sprint? cricket? if it's cricket, i can help you out with the img files).
google for the fastboot binary and put it in your tools folder of the android sdk.
"fastboot -h" will give you commands you can use to reflash the boot and system img.
I have to say though, after reading your OP, the carelessness at which you went after "getting Froyo", you're going to have a tough time of this.
Sanyio ZIO on Cricket
I want to Root my Kyocera Sanyio ZIo on Cricket's service. This is something that I have never done before. My andriod software has been updated. I have been looking all over the interent and there are a million links and blogs but they are all designed for some one who has actually done this before. There is not real "rooting for dummies" guide that goes step by step and really explains each step. I have download all sorts of apps (busybox, file browesr, ROM Manager and system app remover) but none of these grant me superuser access.
My latest research make me believe I need to enter the phone form a "Safe Mode" to upload a zip (su-2.3.1-bin-signed.zip) that my new File browesr will not open as it says it is "broken file can not be opened".
Can some one please assist me wit this? my email is [email protected]
Thank you for your time,
Joshua
Hey all,
I have been a long time flasher of phones however I did a bonehead move and need to see what if anything can be done. Here is what happened.
I have an Optimus M and I have successfully upgraded and downgraded the phone before. Today I was trying a downgrade and as I was flashing I was deleting some files to make some room on my netbook and deleted the .cab flash file. So I tried many times to get the image to take to no avail. I went to my other netbook and tried to flash with the upgrade file and no go there either. What I get when I try to turn the phone on is a very quick LG logo and then nothing. When I hook up the phone on usb with no battery I get a s/w screen however no recovery or reboot sequence I have been able to find works either. Here is a list of what I have already tried. Please let me know if there is anything else you can think of.
-Downgrade flash with Kp500
-pulled out battery and allowed to sit
-connected to other cpu to try upgrade flash via lg upgrader (no go)
-tried recovery sequence
-tried hard reset sequence
Man after all of these years of hacking phones I would hate to think I finally have had the bad luck to make a stupid mistake and brick one.
Thanks everyone!
Ok so here is the deal. I have had my Droid X rooting and I was running Liberty 1.5 for about a month or two now. I decided i wanted to try out fission. so i backed up the phone using clockwork, and proceeded the install process in clockwork, i wanted to reset the fone prior to doing so as well so i wiped data/restore to factory. that completed. i installed fission. that complete. i tried to boot the fone and i still had the liberty boot screen that replaced the motorola boot screen. then the words android came up on the screen and flashed for about an hour. i figured the install didnt work and i didnt feel like figuring out why exactly at that time. i pulled the battery rebooted into clockwork and restored the back up i had made prior to trying to install fission. now i get the Liberty boot screen that replaced the motorola boot logo and nothing else. I can no longer get into clockwork. I can enter the screen like clockwork by holding the power and home button, home button then hitting the search button. in there i have 4 options. i have tried to install update zip from sd and i had the liberty 1.5 rom zip file on the sd card but it fail. i assume i am doing something wrong there. If i could just get into clockwork i know i could fix it. I just dont know how to. so as a last resort before i order a new fone i am asking on here if anyone could help me i would GREATLY appreciated it. Im sorry for this message being so ling
never mind. I finally let the fone sit with the battery out long enough and when i put the battery in i managed to get the fone to bootloader and i sbf it. incase anyone else has this problem here are the files i used. thank you so much for reading this forum.
droidmodderx.wordpress.com/how-to-sbf-your-droid-x-full-2-3-340/
(i am a new user so i cant post links. just copy and paste the link in your url)
its a shame that companies like motorola go so far to prevent damage from happening to their phone via security hacking... and it only leads to destruction :/
[SOLVED]
MESSAGE TO DEVELOPERS/ANYONE WHO CAN HELP
Long story short, i edited my build.prop incorrectly and reset (yes i know very stupid) now my motorola cliq opens up to the motoblur screen but repeated messages saying "Sorry! the process X has shut down" show up.
Literaly, nearly nothing can open up but i am able to enter usb mode if i fight with the endless popups. i can also enter recovery mode because my phone was rooted before this. The problem is that my recovery image doesnt have any options that could help me
(reboot, apply sd card:update.zip, and wipe data/factory reset)
i've tried putting an official motorola update.zip onto my sd card then running the apply.. but like i told you before my build.prop is messed up a little so an error shows up saying:
Installing update...
E/:Failure at line 1: assert file_contains("SYSTEM:build.prop", "ro.build.fingerprint=motorola/morrison_two_us/morrison/morrison:1.5/CUPCAKE/1.4.8:user/rel-keys" == "true" || file_contains("SYSTEM:build.prop", "ro.build.prop", "ro.build.fingerprint=MOTO/morrison_two_us/moInstallation aborted
Press Menu+Back to reboot
All i need to do is fix the line of code i messed up but i cant reach my systems files,...i attached my original build.prop and a copy of my corrupted one to show you.. I also cannot use the phone service or network service (even wifi) because like i said, nearly ALL the services are unable to stay on, they immediately shut off at startup.
Ways to fix this would be to REACH/EDIT THE SYSTEMS FILES
1. I cant use an app like root explorer since i cant access any apps on my phone even things like my settings
2. Turn on usb debugging somehow (I cant access my settings app so im lost on this one)
1. ingenious DESKTOP program that can somehow access my phone's system files without adb (if it can access the sd there has to be a way..)
3. Ive looked around to maybe find a custom image recovery that had options like editing system files (shouldn't be hard to make..) but ive found none with that option and im not sure how i would install it without adb...
What i CAN do
1. ENTER USB MODE (that has to count for something so Developers Please help me)
2. I can play with the motoblur intro screen to some degree to make it go away, then a blank black home menu appears. If i wait a while for the popups to stop at the motoblur screen, i follow the instructions but it gets stuck at registering a new account or existing one since you need network access.
3. ENTER REVOVERY MODE (but the only option that looks helpful is the sdcard update which gave me an error...) I havent tried the wipe data/factory reset because the factory reset doesnt touch the build.prop so its pointless
WHat should I do? WHoever sees this please give me advice or direct me somewhere to get it... THANK YOU
[EDIT]
BTW what i was trying to do on the build.prop was replace this line (ro.build.fingerprint=generic/sdk/generic:3.2/HTJ85B/140714:eng/test-keys)
with (ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys)
but i messd up and put
(ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/rel)
youll see this in the attachments...what this does is unlock my 1.5 firmware market to ALL the apps (updating to the official 2.1 using recovery wouldve handled this but i didnt even know of this update till after my mistake)
I just thought id mention...
if you have adb abilities you can push the old build.prop. If you do not know a out this then post back and I will help you.You said you can enter recovery, but that is stock original recovery that anyone can get access to. If you ever bootstrapped your phone you can try pull the battery out, wait about 10 seconds, then plug your phone charger in without the battery in. If your bootstrappped this will pull you into a more advanced recovery mode. The last option is to use rsd lite to flash an sbf to your phone if nothing else works. If you have never done this just look up sbfing motor cliq to stock.
Good luck, and remember to thank me if this helped
SOLVED!!
I fixed my phone on my own but THANKS to rootfan for being the first to answer.
HERES HOW:
I was able to access recovery mode and from there i discovered the sd update option.
It took hours of research and work but i learned alot about adb,motorola, cliq, etc.
Anyway, i originally found the Blur_Version.2.1.5.MB200.T-Mobile.en.US.zip and i tried to put that in my sd card (i could get into it from the phone) but when i tried to update using recovery it gave me an error so i decided to try the "latest 1.5 with Blur 1.6.1" which was actually very hard to find... you can get it here
motorola. com/staticfiles/Support/Experiences/sdcards/US-EN/tmo/cliq/downgrade-to-cupcake .html
Lastly, i put that on my sd as update.zip, went into recover, and the update was SUCCESSFUL! MY PHONE REBOOTED AND NOW IS ACTING NORMAL AGAIN. Now, im trying to update to the Android™ 2.1 (Eclair):
motorola. com/staticfiles/Support/Experiences/sdcards/US-EN/tmo/cliq/2-1_index. html
but im still getting that error whether i update using recovery or the settings/about phone/system update option... Thats strange but my phone is still working normally and ill find a way to update to 2.1...
ONCE AGAIN THANKS TO ROOTFAN AND HOPEFULLY THIS POST WILL WORK FOR SOMEONE ELSE WHO MAY BE HALF-BRICKED (no adb, no usb debug, no root explorer) THERS STILL HOPE IN RECOVERY+USB DRIVE+BLUR VERSION SOFTWARES
Thanks man, now this is probabaly a redicilous reply, since im sure you would have already tried this, but you can try going into settings, about phone, and click on update and see if the 2.1 eclair ota update will work on your phone.
i've got a simila problem on my samsung Galaxy S5570...
... and i need to prepare an update.zip .
Can you help in this, or you only downloaded a new rom ?
stepph said:
i've got a simila problem on my samsung Galaxy S5570...
... and i need to prepare an update.zip .
Can you help in this, or you only downloaded a new rom ?
Click to expand...
Click to collapse
You can reflash a stock rom back if you wanna get it done easily - or even a updated gingerbread one from samfirmware.com
Search for S5570 in these fora for some guides
Hello,
Recently (about two weeks ago) a friend of mine accidentally dropped his Galaxy Ace Plus into his toilet,
after he got it out, the phone was still on, but when he turned it off it wouldn't start up anymore.
I offered to have a look at the thing, although he already bought a new phone last week. Today he handed his Ace Plus over to me, and I mentioned that it still give a vibrate-feedback when trying to turn it on. I also found out the phone could still open in Download mode, and later I found the shortcut to the recovery (although stock's recovery has very limited options). When I went out of recovery the phone somehow started.
I went home and flashed the stock firmware of the phone (also flashed CWM and rooted the device to make some backups of data to move to his new phone), but now when I turn it off, it will still not start up when using the power button. And again, when I go to recovery and reboot the phone that way, it DOES start up).
My guess is that somehow the boot (partition?) is messed up.
I tried everything that's in my knowledge of Android 2.* phones (I've got an Sony 4.0 ICS phone myself, it works quite a bit different). I can't find a way to fix it myself, so I turned to this forums in the hope that one of you guys could help me fix his phone.
Regards, Drago
ALSO: to add, does flashing kernels work the same on these phones? Like, via fastboot with command line? I might want to try to re-flash stock kernel, hoping it fixes the boot.
Dragoboss said:
Hello,
Recently (about two weeks ago) a friend of mine accidentally dropped his Galaxy Ace Plus into his toilet,
after he got it out, the phone was still on, but when he turned it off it wouldn't start up anymore.
I offered to have a look at the thing, although he already bought a new phone last week. Today he handed his Ace Plus over to me, and I mentioned that it still give a vibrate-feedback when trying to turn it on. I also found out the phone could still open in Download mode, and later I found the shortcut to the recovery (although stock's recovery has very limited options). When I went out of recovery the phone somehow started.
I went home and flashed the stock firmware of the phone (also flashed CWM and rooted the device to make some backups of data to move to his new phone), but now when I turn it off, it will still not start up when using the power button. And again, when I go to recovery and reboot the phone that way, it DOES start up).
My guess is that somehow the boot (partition?) is messed up.
I tried everything that's in my knowledge of Android 2.* phones (I've got an Sony 4.0 ICS phone myself, it works quite a bit different). I can't find a way to fix it myself, so I turned to this forums in the hope that one of you guys could help me fix his phone.
Regards, Drago
ALSO: to add, does flashing kernels work the same on these phones? Like, via fastboot with command line? I might want to try to re-flash stock kernel, hoping it fixes the boot.
Click to expand...
Click to collapse
Try flashing some custom rom in recovery mode.
or try flashing stock rom using Jtag.
If nothing works then you should go to service center.
kk9999gada said:
Try flashing some custom rom in recovery mode.
or try flashing stock rom using Jtag.
If nothing works then you should go to service center.
Click to expand...
Click to collapse
Thank you, the first method indeed solved the problems.
I flashed the "Slimbean" ROM that has actually been released today, haha.
After that I restored a CWM Nandroid backup I created before flashing the ROM. The phone now starts normally.
Thank you very much.
Regards, Drago