As a disclaimer, I have already searched and found some people with the same issue. What I haven't found is someone that arrived at this problem in the same way I did. I am scared ****less of bricking my phone (and hope I haven't already). So at this point, I am looking for some help to figure out my best course of action.
I recently updated to JF1.5 using his updater app, and everything worked. Today when I received my new SDcard, I started the process to get apps on my SD following this tutorial: http://forum.xda-developers.com/showthread.php?t=512743
I got as far as partitioning my card using the Apps2SD application as described, doing everything the tutorial says. I began the partition on my phone, and let it sit.....and sit, and sit. It sat frozen on the partitioning screen (the one with the slider to select the size) for almost an hour before i pulled the battery. I selected 1444mb for the ext2 after reading that it was not a good idea to go higher than 1500mb.
Now, as stated the phone boots to the G1 splash and goes nowhere. I am however still able to boot in recovery mode using Home+Power. Interestingly, it says at the top:
"Android system recovery utility
Build: JFv1.42"
Not sure if this means that 1.5 didn't install correctly or what, but that's what it says.
I have no idea what to do at this point, and am scared to go on without some candid advice. Sorry for the noobishness of my description - if there is anything else needed to give accurate advice please let me know. Also thanks in advance for any help I can get!
Same thing happened to me, you have to reflash. I tried using that method and it never worked for me, although I already had the partition. So reflash jf 1.51 and you are golden. BTW that text you see in recovery is the recovery image version, until you switch to another it will say that.
meoshe said:
Same thing happened to me, you have to reflash. I tried using that method and it never worked for me, although I already had the partition. So reflash jf 1.51 and you are golden. BTW that text you see in recovery is the recovery image version, until you switch to another it will say that.
Click to expand...
Click to collapse
Thanks for the response. I'll have to find a way to get that image onto my SD card. I just bought a 16BG card and that was the card I was using when I ran into this problem.....oh wait a sec....
I'm assuming that the JF1.51 update.zip will still be on my old 1GB card from when I updated to JF1.51 via his updater app last week? If so then my life will be a lot easier, and I'll just swap back to that card, boot up in Recovery, flash from update.zip, and that should be it?
Just want to make sure before I put that old card back in and try to flash....
try wiping before you update? Also to mount your SDcard (if you need to) press alt-x in recovery (or in adb shell) and type
Code:
echo /dev/blockl/mmdblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
x2 that's what i had to do since my computer stopped reading sd cards.
Wipe then update.
I'd also recommend using CMv3.4 because the apps2sd is automated. It runs a2sd by itself
And with Cyanogen Recovery v1.2 you can move apps to sd card
First off, just want to thank everyone for the help. I successfully reflashed with jf1.51, but now I can't seem to sign in. I'm on the welcome screen, skipped the tutorial, entered my Gmail account and it sits for awhile trying to contact the server and then says there's a problem with the service or my sim card.
I know my sim card is provisioned for data, so not sure what's happening here...any ideas?
EDIT: Forgot I had to enter the Rogers APN settings, trying that now (Duhhh)
Abolfazl said:
Wipe then update.
I'd also recommend using CMv3.4 because the apps2sd is automated. It runs a2sd by itself
And with Cyanogen Recovery v1.2 you can move apps to sd card
Click to expand...
Click to collapse
I'm interested in this Cyanogen stuff, but no idea where to start. Any good tutorials? I was following this scene for awhile but kinda lost touch a few months ago - turns out there's been lots of developments.
t3mp3st said:
First off, just want to thank everyone for the help. I successfully reflashed with jf1.51, but now I can't seem to sign in. I'm on the welcome screen, skipped the tutorial, entered my Gmail account and it sits for awhile trying to contact the server and then says there's a problem with the service or my sim card.
I know my sim card is provisioned for data, so not sure what's happening here...any ideas?
EDIT: Forgot I had to enter the Rogers APN settings, trying that now (Duhhh)
I'm interested in this Cyanogen stuff, but no idea where to start. Any good tutorials? I was following this scene for awhile but kinda lost touch a few months ago - turns out there's been lots of developments.
Click to expand...
Click to collapse
It is pretty cut and dry. Cyanogen's Mod unleashes the G1 to its max. Apps2sd is automated and is working before you can even turn your phone on.
CMv3.4
CM Recovery v1.2
Abolfazl said:
It is pretty cut and dry. Cyanogen's Mod unleashes the G1 to its max. Apps2sd is automated and is working before you can even turn your phone on.
CMv3.4
CM Recovery v1.2
Click to expand...
Click to collapse
Cool, I guess I'll try it out now before trying to restore everything. I don't see a tutorial for it though, or am I to just follow the previous "How to root" tutorial and just use his image as the update.zip?
t3mp3st said:
Cool, I guess I'll try it out now before trying to restore everything. I don't see a tutorial for it though, or am I to just follow the previous "How to root" tutorial and just use his image as the update.zip?
Click to expand...
Click to collapse
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
alritewhadeva said:
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
Thanks a lot, going to try that now with my 16GB card. And just to be clear (last questions in this thread, I PROMISE!), I should flash with CM3.4 and THEN install the recovery image, or vice versa?
Also, with CM3.4, will I have to go through to steps again to try to partition my card (which is where i ran into the problem from post #1), or is there some automatic process built into his super-de-duper ROM?
Thanks again to all for the speedy responses!!
t3mp3st said:
Thanks a lot, going to try that now with my 16GB card. And just to be clear (last questions in this thread, I PROMISE!), I should flash with CM3.4 and THEN install the recovery image, or vice versa?
Also, with CM3.4, will I have to go through to steps again to try to partition my card (which is where i ran into the problem from post #1), or is there some automatic process built into his super-de-duper ROM?
Thanks again to all for the speedy responses!!
Click to expand...
Click to collapse
Don't worry asking questions is good as long as they are intelligent. You should flash CM3.4 and then the recovery image, as that is what i did. However, i don't think it really matters. To be safe, flash CM3.4 and then the recovery image.
And to your question pertaining to partitioning your SDcard, you can try MarcusMaximus' Apps2SD2 app which formats the card for you here
Unzip it to your sdcard and install it using ASTRO file manager or some other file manager.
If you have adb working,
Code:
adb install AppstoSD2.apk
if you have other questions you can always contact me on AIM- roflzbrianxdd
alritewhadeva said:
Don't worry asking questions is good as long as they are intelligent. You should flash CM3.4 and then the recovery image, as that is what i did. However, i don't think it really matters. To be safe, flash CM3.4 and then the recovery image.
And to your question pertaining to partitioning your SDcard, you can try MarcusMaximus' Apps2SD2 app which formats the card for you here
Unzip it to your sdcard and install it using ASTRO file manager or some other file manager.
If you have adb working,
Code:
adb install AppstoSD2.apk
if you have other questions you can always contact me on AIM- roflzbrianxdd
Click to expand...
Click to collapse
Thanks a ton, I'll get to this right after i finish this delicious sub! I'll also add you so I can IM if i have any more questions..
t3mp3st said:
Thanks a ton, I'll get to this right after i finish this delicious sub! I'll also add you so I can IM if i have any more questions..
Click to expand...
Click to collapse
Cool, Best of Luck with the flashing
alritewhadeva said:
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
Alright...I successfully partitioned my card, flashed with CM 3.4, but now when I try this instruction to install the new recovery, i get this error msg in Terminal:
error writing recovery: Permission denied
Any ideas?
You have to enter su before the code..
Code:
su
then
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
meoshe said:
You have to enter su before the code..
Code:
su
then
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
I did not enter the su, I will try that now thanks. In the mean time I also performed this step:
13. My /system/sd is read only and/or didn't upgrade to ext3!
Your filesystem is probably corrupt. Boot into recovery and open a console. Run "mount /system" then "/system/bin/e2fsck /dev/block/mmcblk0p2" and fix your filesystem. Reboot.
from: http://forum.xda-developers.com/showthread.php?t=518851
So I hope that didn't hurt anything...ill try with the su now. Thanks!
edit: out of curiosity, what does the "su" stand for? I feel if I know this it may help me to remember to enter it before any commands.
edit #2: does it stand for "Super User" to allow super user permissions? I gathered this after entering SU prompted me to allow superuser access
New recovery.img successfully installed! Thanks again to everyone that helped me with this.
I know I can transfer apps to SD easily from recovery now, but is there also a similar way to do it from the phone (or do they install to the SDcard by default now?)
Hey T3MP3ST... how did it go with upgrade to cm3.4
I had the same problem as you mentioned start of the post....
(stuck at g1, after partition).
this cm3.4 sounds like the solution for me to have apps2sd..
as it is in the ROM automatically, if i understood correctly.
dynamisoz said:
Hey T3MP3ST... how did it go with upgrade to cm3.4
I had the same problem as you mentioned start of the post....
(stuck at g1, after partition).
this cm3.4 sounds like the solution for me to have apps2sd..
as it is in the ROM automatically, if i understood correctly.
Click to expand...
Click to collapse
Hey there, with the help from everyone in this thread, along with the partitioning instructions using Ubuntu (if you still need to partition your card) from tubaking182 found here: http://forum.xda-developers.com/showthread.php?t=523648, It was great.
I just finished flashing with that ROM and then installing CM's recovery image (which is AWESOME...trackball selection, Apps2SD in one click)
I HIGHLY recommend it. If you have any problems, I'm sure you'll find most of the answers in this thread. If not, try PMing one of the helpful respondents, or I may be of SOME help with some minor questions or assurances.
Related
I managed to wipe data/factory reset but on dalvik-cache and SD: ext partition, it says theres an error and I have to run both of them via adb. This is my first time actually wiping and the only video I could find was for a mytouch3g. Any help would be grateful.
Does anyone know? Im trying to get his wiped and install a custom ROM asap because Ive already had my phone out of commission for a few hours now.
a bidet may help.
actually I read on these forums that even though you get the error on dalvik that it wiped successfully completed. don't know about the other.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
flash a new recovery image
works everytime
PawkChop said:
Having trouble wiping
Click to expand...
Click to collapse
Sounds like a personal problem.
Just kidding, try flashing another one like was already suggested.
Im currently on version 1.5.2 and I got it from a guide I followed earlier to root my phone. I dont know where I'd get another one from though
The guide for rooting in the sticky is the exact one I followed and that brings the version I have. Unless Im not looking in the right place. Im sorry that Im a total noob at this, just trying to finally use some custom stuff on my phone.
http://rapidshare.com/files/360288584/recovery-RA-heroc-v1.6.2.img
Thank you very much. Now this is where its get even noobier. Where exactly do I put the file. Ive never flashed a ROM or a recovery image unless that guide involved it so Im kinda at a loss here.
I sent you a PM
If anyone else could help, when I run the code in the terminal in order to flash the newer recovery image, it says that there isnt a recovery partition.
PawkChop said:
If anyone else could help, when I run the code in the terminal in order to flash the newer recovery image, it says that there isnt a recovery partition.
Click to expand...
Click to collapse
This is how you do it. Put the recovery on the root of your SD (name it recovery.img for easiness and laziness) then eject the phone and run these commands:
Code:
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
Done.
Also, if you're having trouble wiping, check this out: http://www.youtube.com/watch?v=PZeJZs2fdYo
HeroMeng said:
This is how you do it. Put the recovery on the root of your SD (name it recovery.img for easiness and laziness) then eject the phone and run these commands:
Code:
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
Done.
Also, if you're having trouble wiping, check this out: http://www.youtube.com/watch?v=PZeJZs2fdYo
Click to expand...
Click to collapse
Haha I will check out those wipes...
Anyways, im sorry for being a complete noob, but where do I input those commands. In command propmt? cause if so it doesnt work
PawkChop said:
Haha I will check out those wipes...
Anyways, im sorry for being a complete noob, but where do I input those commands. In command propmt? cause if so it doesnt work
Click to expand...
Click to collapse
In ADB. If it shows a $ sign after you type adb shell, then type su. That might be your problem.
What you did .. .. ..
Okay so you've rooted your newly bought MyTouch4G, and you've made sure that s=off and you've flashed Clockwork ROM manager's recovery image that you got from the market. That is all the correct order. But when you flashed a ROM you got stuck in a bootloop.
Am i screwed???
Don't worry you are just in a "soft brick mode", or "limp mode" if you will.
What happened? Why is it doing this?
The Image that you downloaded and installed 3.0.0.5 is for 2.3 (Gingerbread) based ROMs only. [n3rd note] these are ext4 style ROMS. They act and store information differently than 2.2 which are Ext3 ROMs[/n3rd note].
This could also be caused by trying to flash a 2.3 using a older 2.x.x.x version of the Recovery Image. Those will only support the Ext3 style ROMs, which are FroYo (2.2) based ROM.
Okay what do i need to do to fix it, there are two methods.
This is Method one it's the older version.
You must use this method if you do not have the engineering screen
If you are using the 3.0.0.5 Recovery image
To fix your problem you need to flash any 2.3 based ROM, for time sake i will recommend Cyanogen(mod). Link to Cyanogen(mod)'s CM7RC4. While you are there you need to also store the G/Apps.
If you are using the 2.x.x.x Recovery Image
To fix your problem you need to flash any 2.2 based ROM, for time sake i will recommend RoyalGlacier Thread can be found here
- Question: How do i find out what Recovery image i am using
- Answer: Boot the phone into the recovery mode. We'll touch on that in a little bit
Now when you download both of those files you also need to store them to SDCard.
NOTE: If you are using 2.x.x.x and going to flash RoyalGlacier you will not need the g/apps. They have included this in their ROM, and MAKE sure to follow their specific directions for installing the ROM.
- Question: Now how in the world i am going to do that since my phone is in bootloop.
Answer:
Two ways one can do that
1) use a SDcard reader and just plug the card into a main USB port.
2) Mount the SDCard in the phone via the Recovery Image. *** i'd recommend this method since you are going to need to be in recovery anyway ***
Pull the battery from the phone an put it back in, then put the back on the phone. turn the phone on holding the power button along with the volume down rocker button. That will boot the phone into the HBoot (Engineering) Screen. From there you will see an option that says "recovery" [this is what i mentioned earlier, about the different versions] use the volume rocker to select it, then tap the power button to select it. The phone will reboot into what is called the recovery image. From there you will select "mount" then USB. That will mount the SDCard to the Computer.
If you are using the 3.0.0.5 Recovery image
Once you have move Cyanogen(mod) and the g/apps to the SD card unmount the SDCard.
Then navigate to "wipe data/factory reset" you will want to wipe the phone. That will format everything to a fashion that can be written over w/o problems.
Then navigate to "install .zip from sdcard" > " choose .zip " > then flash the main Cyanogen(mod) ROM. Then do the same but flash the g/apps that you downloaded.
Once those are done you can re-boot the phone. That will boot you into cyanogen.
If you are using the 2.x.x.x Recovery image
Please use the link i supplied above to get that ROM up and running once it is done, according to their instructions come back here.
Now i understand that may or may not want Cyanogen nor RoyalGlacier on your phone. Well take care of that
What can i do to prevent this from Happening again?
Once you are up and running (make sure to log into your Google Account) go to the market and download Clockwork ROM manager again, and re-flash the recovery image.
Once you are done with that i HIGHLY suggest upgrading to the newest 3.0.0.6 Recovery image. You can do that one of two ways.
one way is to flash True_Blues method for installing 3.0.0.6 recovery image. Use this thread..
This is the way that i would personally recommend.
The second way is download the 3.0.0.6 recovery image, which i've attached and flash it via the ADB commands. If you want to do it this way you do not need to download Clockwork Rom Manager, you can "just flash it". If you need help with that, if you are using Windows or Mac, see my signature for True_Blue's method on EZ ADB. If you are using Unbutu 10.10 use this This Method to get ADB running. This is the method i used to ADB running on my Linux NetBook.
Download the file that i've attached and store just the recovery image from the .zip to the SDCard, from the ADB commands type
adb shell
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
More information on this process can be found here
That will flash the newest recovery image to your phone
Once you have installed the 3.0.0.6 ROM Manager you can wipe and flash ANY MyTouch4G ROM that you want. It will handle both 2.2 (ext3) and 2.3 (ext4) ROM formats.
This is the New Method - Which is a little easier.
AND YOU MUST HAVE THE ENGINEERING HBOOT
Thanks to TeeJay for inspiring this.
I am going to assume that since you have the Engineering Screen you are more familiar with what you are doing so i'll be more to the point with this walk-through.
you will need to have ADB up and running for this method.
1) Download the attached file and store just the .img to your folder from which you preform all of your ADB commands
2) plug the phone into the computer
3) boot the phone into HBoot
4) from the ADB commands change the drive to the folder where you stored the recovery image.
5) type these commands
Code:
fastboot flash recovery recovery.img
the screen should say something to the degree of
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
6) then select "bootloader"
7) navigate to "reboot recovery"
8) flash your ROM of choice.
9) enjoy your ROM of choice.
Please feel free to use this in your signature or link people back to. If you feel i made an error in this post please PM and i'll edit it accordingly.
If this thread has helped you solve your problem please hit the "thanks" button.
THE RECOVERY IMAGE HAS BEEN UPDATED TO THE NEWEST ONE.
good summary. originally when i flashed cm7 I had to search a bit to come up with what you said above. one addition, CWM lets you mount sd storage to usb so you can copy files to sdcard (say the recovery image). then update CWM 3.0.0.6 with ADB.
leo221 said:
good summary. originally when i flashed cm7 I had to search a bit to come up with what you said above. one addition, CWM lets you mount sd storage to usb so you can copy files to sdcard (say the recovery image). then update CWM 3.0.0.6 with ADB.
Click to expand...
Click to collapse
Added that method as well.
May want to mention that the opposite could be true as well > same boot loop but from flashing 2.3 rom with recovery 2.5.1.2
Thank you for this!! Exactly what I needed...!
austengeist said:
Thank you for this!! Exactly what I needed...!
Click to expand...
Click to collapse
Glad it helped, just make sure to hit the "Thanks" button in the first post.
dang man you're the Q&A champ, every time i'm on this you're answering questions.
well this worked like a charm, idk why people on xda always make things more complicated than it has to be.
option94 said:
May want to mention that the opposite could be true as well > same boot loop but from flashing 2.3 rom with recovery 2.5.1.2
Click to expand...
Click to collapse
Added.
aalsmadi1 said:
dang man you're the Q&A champ, every time i'm on this you're answering questions.
well this worked like a charm, idk why people on xda always make things more complicated than it has to be.
Click to expand...
Click to collapse
Well i work in the Imported Automotive parts. My job requires me to basically sit around and answer the phone when it rings. We have our own "call center" room. I just pick up the phone and answer question and sell parts. Like right now i'm working on a engine rebuild kit for a 1975 2Ton Mercedes Bens..... so i get some free time from time to time, and XDA is one of a few sites they allow me to visit.... BGR/ Android and Me, Android Central are the others....
I can see why some people blow up, spend +$200.00 on a phone then turn around and blow through something w/o taking the time to read something and then you get stuck in a bootloop.... i can see why people go bonkers. But slowing down and reading would solve alot of problems. Heck i've got 3 great threads in my signature that would solve alot question that one could have with a new device.
fixed my problem
Thread stuck.
Great guide!
Same issue, except i flashed 3.0.0.6 beforehand to prevent any problems. Iced Glacier flashed okay, I just didn't care for it much. Ive wiped all the necessary parts prior to flashing as I would before flashing any roms. Ive managed to retrieve and restore a previous back (I can haz backups) so Im not stuck. I would like to be in the cool kids cyanogen club. Any ideas?
DHSdrone said:
Same issue, except i flashed 3.0.0.6 beforehand to prevent any problems. Iced Glacier flashed okay, I just didn't care for it much. Ive wiped all the necessary parts prior to flashing as I would before flashing any roms. Ive managed to retrieve and restore a previous back (I can haz backups) so Im not stuck. I would like to be in the cool kids cyanogen club. Any ideas?
Click to expand...
Click to collapse
Meaning you want to run Cyanogen(mod)? Well jump over to their site and download the ROM of your picking; Nightlies are alpha builds, and the RC's are beta builds. I've ran both and both are extremely stable. I have links supplied in the first post. and directions for that matter. just make sure to do a nandroid backup before wiping and flashing.
Thanks ....Saved ME LIFE
Posting so I can see the "thanks" button. Doubley thanks you saved my bacon....err phone!! Hmmmm bacon!
Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!
b0rnsusp3ct said:
Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!
Click to expand...
Click to collapse
Pull the battery. Hold vol down power on them restore cm7. Then flash cwm 3.0.0.6.
Sent from my Inspire 4G using XDA Premium App
b0rnsusp3ct said:
Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!
Click to expand...
Click to collapse
What button are you pressing to select the option? you should just use the trackpad.
Loll...wow, I am such a noob i def. shouldn't be rooting or anything.
Thanks so much!
b0rnsusp3ct said:
Loll...wow, I am such a noob i def. shouldn't be rooting or anything.
Thanks so much!
Click to expand...
Click to collapse
Why do you say that?
hello,
i rooted my Huawei and then used Root Tools to flash a font on it (don't remember which one it was).
Now my device seems to start, the hard buttons light up, but i get an infinite boot loop!
i can get into recovery, but i don't know how to get into fastboot.
I have already done a factory reset via recovery, but it keeps happening.
can anyone help me?
EDIT: also, since i cant get into the phone, i can't enable usb debugging to get to adb either... is there any way to force this or something?
Have you tried to wipe all phone-data and flash it with a rom?
Yeah, i've tried the flash all in recovery. i want the stock ROM though, do you have an update.zip for that? i'm pretty sure i can borrow a microSD card and put it on there.
jerry00 said:
Yeah, i've tried the flash all in recovery. i want the stock ROM though, do you have an update.zip for that? i'm pretty sure i can borrow a microSD card and put it on there.
Click to expand...
Click to collapse
So does it work with the rom you tried?
You can find the stock-rom on the huawei-device webpage if you haven't done a backup..
Edit: for ROMS check this:
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800
sentiment said:
So does it work with the rom you tried?
You can find the stock-rom on the huawei-device webpage if you haven't done a backup..
Click to expand...
Click to collapse
oh, no, i have the stock recovery, i just did the "wipe data/factory reset"
i can't found the stock rom on the webpage... could you please link me to where it is?
jerry00 said:
oh, no, i have the stock recovery, i just did the "wipe data/factory reset"
i can't found the stock rom on the webpage... could you please link me to where it is?
Click to expand...
Click to collapse
you should install perfect recovery, you can find it here on the ideos x5 development section and then wipe data and apply the rom you wan't, i think that should fix your phone
sentiment said:
you should install perfect recovery, you can find it here on the ideos x5 development section and then wipe data and apply the rom you wan't, i think that should fix your phone
Click to expand...
Click to collapse
well, i'd want it to be as stock as possible, in case it needs to go to service once... but as for the stock rom, is that the kernel-2.6.32-U8800-Froyo file on huaweis website? should i just rename that to update.zip and use it?
EDIT: i saw your edit now, when i have downloaded the right .zip file(in this case the norway retail one), i'm going to rename that to be update.zip and upgrade with it, am i right?
EDIT2: okay, i'm just going to follow the instructions in the zip folder one final question: how do i check my build number?
yes you can rename it, but it's not even necessary because you can choose the file (rom) you want to install later in perfect recovery. Or are you using something else then perfect recovery?
I have no idea about the instructions in the zip folder, because i haven't installed any stock roms on my phone, and can't understand what you need the build number for?
I suggest you to try to install that stock rom because you have nothing to lose and it's easy to wipe data again and try with other roms again..
sentiment said:
for ROMS check this:
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800
Click to expand...
Click to collapse
Thanks! i downloaded the corresponding zip file for my carrier, unzipped, and just followed the instructions in the pdf file
The phone works great now! i am very happy now
This happened to me this morning!! Is there anyway to fix this in Recovery mode by mounting /system or something and rename the backup of the font back?
I don't want to delete everything off the phone! I have been customizing it for the past 2 or 3 weeks.. and was getting it exactly how I wanted it.. Don't want to do it all over again
EDIT: PHEW.. I fixed it. All you have to do is rename every font back to how it was originally (hope you have a backup) and set the permissions back to how they were originally CHMOD 644
If you need more help let me know, tell me which OS you have.. if you have Ubuntu / Linux I can help you.. no problem, as for windows.. I don't know
for windows the procedure is pretty much the same, i guess you used adb
That is what I love about ubuntu.. no I did not have to use adb. It automatically mounted the drives when I booted in recovery mode, then browsed system partition as root user (using natalius script.. or you can use a terminal) then set the permissions of the fonts to 644, make sure all the fonts are named exactly (CASE SENSITIVE).
Reboot and it will work.
Hi, i'm new here so i can't post in the development section.
I have a xoom wi-fi only US version and things have gone terribly wrong. I had unlocked bootloader + Android 3.2 rooted and i was trying to install a theme by using the clockwork mod recovery, but after I did it just kept replaying the boot animation and would not actually start. I freaked out and used clockwork recovery to format user data, cache, /system and the like. Now i can't get off the Motorola screen and i was wondering if there is a way to reinstall (the latest rooted version of) android on my device. Someone please help me, and if you can can you walk me through it. Any help would be greatly appreciated!!
have you tried downloading another version, put it on your SD card and flash it from CWM recovery?
This forum may be able to help you as well...
http://forum.xda-developers.com/showthread.php?t=1209341
i suggest u to flash a new rom instead.
Ok, I have the latest rooted version of android here on my PC.
How exactly do I get it installed onto my xoom? I am aware that you can use adb but can you please go over the exact procedure? (i got it here http://forum.xda-developers.com/showthread.php?t=1242524) Thanks that would be very helpful. I just want my device back
How do u do that using ADB? Please help!
Neardood1 said:
How do u do that using ADB? Please help!
Click to expand...
Click to collapse
ok first off just relax and you posted this in the right section... General or Q&A is where you post questions not Development so you are ok. Now on to your issue, download another rooted rom preferably Tiamat from here. Follow instructions on how to flash the file and that should get you back up and running. Now no need to ask for specifics and wait for it since all OP's in Development will instruct you on what to do.
Also did you make a backup, if you did it would be easier to just flash that. Hope it helps and dont panic. Next time make a backup before flashing themes. Oh yea if you still have the original rom you were running on your sd card just flash that again. If you still have an issue after flashing then do a factory reset wipe in CWM and try and reboot.
So basically your gonna try and flash a rom to see what happens... Any rom you have...
Ok, so i've copied it onto the micro SD card from my phone, there's a lot of other crap in there but I've just put it on into root (not in any folders). Now, how exactly do i install it because the thread just says to "install rom". i'm in clockwork recovery now, what do i select to get it to install?
I have ClocworkMod Recovery v4.0.0.4, and there doesn't seem to be an external sd card option, just the /sdcard directory from within android. Does this mean that I have to find a way to flash the rom into that directory using fastboot or something? If so, pleese just tell me how.
Neardood1 said:
I have ClocworkMod Recovery v4.0.0.4, and there doesn't seem to be an external sd card option, just the /sdcard directory from within android. Does this mean that I have to find a way to flash the rom into that directory using fastboot or something? If so, pleese just tell me how.
Click to expand...
Click to collapse
My friend this is why I told you to follow OPs instruction. How did you flash your last rom or get rooted in the first place. This procedure is no different, relax and read the options in clockwork and it with will all come to you. You are installing/flashing a rom so it would be install from zip. Since I may not be on here to help you when your ready this is why I stress reading the intructions. They will give your answers
?,
Sent from my Xoom using xda premium
You're still not helping me, and neither is the other posts; their not specific enough. just tell me how to flash a rom to my /sdcard directory so i can use it in clockwork mod. What commands from my PC do i enter to transfer the .zip???
Hooray!!!
Yay! I've managed to fix my xoom by flashing a stock android 3.0 rom to it. Thank you to everyone involved who took the time to help me, although none of your advice was relevant to the way i fixed it.
For the sake of anyone who was in the same predicamant as me, the steps I took to fix it were:
1) Go to this http://developer.motorola.com/products/software/ link and download the US release (122 mb, down the bottom of first table)
2) Unzip it and extract the contents (should be a set of .img files) to your android-sdk/tools folder
3) Put your xoom into fastboot mode (power on and during the motorola logo repeatedly press volume down until the menu appears in top left of screen, press volume down until you see fastboot, then press volume up, will show starting fastboot protocols)
4) Open a command window in your /tools directory (select tools folder and shift+right click and choose it from the menu that appears in windows)
5) Type the following: fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
6) Once that is done, type fastboot reboot or hold power+volume up (reboots device). you are now done and it should boot into android
IF ANYONE FOUND THIS HELPFUL, PLEASE SAY SO!
the story goes like this, I flash TWRP 2.2.0 did a nandroid and deleted all the necessary partitions to install the new rom, I put the rom in the SD card, TWRP is not mounting the sd card wich happens to work flawlessly in my phone, and pc, now i cant access the internal storage nor the sdcard, Please I dont know what to do anymore i cant get my cpuid because my tablet does not have an os so i cant select usb debugging, i cant access my internal storage either from the pc, im using skrilax-oz bootloader v7, the computer only recognizes the tablet in fastboot, how can i put a recovery in it via the bootloader in fastboot if posible.
If your PC will recognize Fastboot (you should have it listed in Device manager when you go to fastboot with Skirlaz Bootloader), then the easiest thing would be to get the proper recovery .img file. I suggest EZTerry Public revovery, or CWM. Most recent versions of both. Your choice. You can find CWM recovery image at tegraowners, or get the Public Recovery from the XDA Dev forum.
Boot your tab to fastboot.
Make sure the xxxxxxxxrecovery.img file is in the same folder as your Android/Android-sdk/Platform-tools folder. (has to be in the same folder as fastboot.exe)
Then open a Command window in that folder
Type fastboot flash recovery xxxxxxxrecovery.img
Then hit enter
Remember, where xxxxxxxrecovery,img is the name of the recovery image.
This should hook you up.
TWRP has some issues,
MD
cubanghost said:
the story goes like this, I flash TWRP 2.2.0 did a nandroid and deleted all the necessary partitions to install the new rom, I put the rom in the SD card, TWRP is not mounting the sd card wich happens to work flawlessly in my phone, and pc, now i cant access the internal storage nor the sdcard, Please I dont know what to do anymore i cant get my cpuid because my tablet does not have an os so i cant select usb debugging, i cant access my internal storage either from the pc, im using skrilax-oz bootloader v7, the computer only recognizes the tablet in fastboot, how can i put a recovery in it via the bootloader in fastboot if posible.
Click to expand...
Click to collapse
Can you still go into recovery by power+volume down? If yes, then go back into trwp recovery and do the following. Mount option >click mount sd card and using external sd. Once you have those options clicked, go back to install option. There you will be able to access your external sd card. I think the best recovery to use now is thor 1.7.3.
Good luck,
Sent from my A500 using Tapatalk 2
10507 said:
Can you still go into recovery by power+volume down? If yes, then go back into trwp recovery and do the following. Mount option >click mount sd card and using external sd. Once you have those options clicked, go back to install option. There you will be able to access your external sd card. I think the best recovery to use now is thor 1.7.3.
Good luck,
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
it wont mount, that is why im having such a big issue trying to install a new recovery or flash the rom in the external sd card.
Ok, you have 2 different threads going. In this thread, you didn't mention anything about formatting your internal storage. This is why XDA has a rule about posting the same thing in multiple forums. Chances are you say something in one, and not the other. And what you will get is sometimes not good info, or even worse, no response.
Dees-troy and I have posted possible solutions. Problem is, other people get confused when they see it.
That little bit of missing info between the multiple posts can mean a big thing.
I will let it slide this time. Next time, I will delete one or the other.
MD
cubanghost said:
it wont mount, that is why im having such a big issue trying to install a new recovery or flash the rom in the external sd card.
Click to expand...
Click to collapse
Did you fastboot a new recovery image like I directed?
MD
Moscow Desire said:
If your PC will recognize Fastboot (you should have it listed in Device manager when you go to fastboot with Skirlaz Bootloader), then the easiest thing would be to get the proper recovery .img file. I suggest EZTerry Public revovery, or CWM. Most recent versions of both. Your choice. You can find CWM recovery image at tegraowners, or get the Public Recovery from the XDA Dev forum.
Boot your tab to fastboot.
Make sure the xxxxxxxxrecovery.img file is in the same folder as your Android/Android-sdk/Platform-tools folder. (has to be in the same folder as fastboot.exe)
Then open a Command window in that folder
Type fastboot flash recovery xxxxxxxrecovery.img
Then hit enter
Remember, where xxxxxxxrecovery,img is the name of the recovery image.
This should hook you up.
TWRP has some issues,
MD
Click to expand...
Click to collapse
Thank you, thank you thankyou, you have no idea the headhache you have saved me, I'm very greatfull for your help, it work like a charm, no more TWRP recovery for me.
cubanghost said:
Thank you, thank you thankyou, you have no idea the headhache you have saved me, I'm very greatfull for your help, it work like a charm, no more TWRP recovery for me.
Click to expand...
Click to collapse
Hey, don't forget the THANKS Button
MD
cubanghost said:
Thank you, thank you thankyou, you have no idea the headhache you have saved me, I'm very greatfull for your help, it work like a charm, no more TWRP recovery for me.
Click to expand...
Click to collapse
TWRP is a good recovery. And it works for most. As with most recovery systems, it will have times when things don't work correctly. Call it a "hic-cup". And the only thing to do, is totally install something else. Works most of the time.
Dees Troy is a darn good Dev. And we're grateful to have him around. In this case, you had to do something radical to shock the system. Works every time
Also, throw a Thanks to Skirlax_CZ for the bootloader and the fastboot capability. If you didn't have that, your "stuff would be hanging in the breeze" about now.
MD
Moscow Desire said:
TWRP is a good recovery. And it works for most. As with most recovery systems, it will have times when things don't work correctly. Call it a "hic-cup". And the only thing to do, is totally install something else. Works most of the time.
Dees Troy is a darn good Dev. And we're grateful to have him around. In this case, you had to do something radical to shock the system. Works every time
Also, throw a Thanks to Skirlax_CZ for the bootloader and the fastboot capability. If you didn't have that, your "stuff would be hanging in the breeze" about now.
MD[/QUOTE
most defenatly im greatful for Skirlax and his boot loader it totaly saved me. and TWRP i use it on my skyrocket and works very well, thus why i flash it with out looking for the thread.
Click to expand...
Click to collapse