Related
I was trying to root and nand unlock my gfs phone and now Im at a point where usb and nothing is working. All i want do is go back to stock and make it like nothing happened. And no i dont have a nandroid backup. Im screwed. Please help.
i have the sd card error and usb error similar to here: http://forum.xda-developers.com/showthread.php?t=695243
but I cant get into adb because it says device not found.
when I connect USB it says error setting up new hardware in windows.
http://forum.xda-developers.com/showthread.php?t=695243
Sent from my PC36100 using XDA App
she's going to cut his..... SOMEBODY HELP HIM!!!!!
gatorran said:
she's going to cut his..... SOMEBODY HELP HIM!!!!!
Click to expand...
Click to collapse
Yes why is this so much more difficult compared to winmo?
[email protected] said:
http://forum.xda-developers.com/showthread.php?t=695243
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes read above, I can't get into adb shell to do that. Thanks!
riotburn said:
Yes why is this so much more difficult compared to winmo?
Yes read above, I can't get into adb shell to do that. Thanks!
Click to expand...
Click to collapse
Was adb working for you before? You may need to install some drivers
yes it was. I need this fixed fast she just got it yesterday!, i rather like my testicles, kind of attached to them. I humbly accept all flaming and newbie calling.
riotburn said:
Yes why is this so much more difficult compared to winmo?
Yes read above, I can't get into adb shell to do that. Thanks!
Click to expand...
Click to collapse
so the first part of the commands using fastboot you don't do from adb shell. when you get the phone into fastboot, attach to your computer, you then open command prompt on computer and navigate directories until you are in the android sdk tools folder on your computer wherever it is (most people it is somewhere like c:/android-sdk-windows/tools/)
THEN you type
fastboot oem enableqxdm 0
fastboot reboot
Click to expand...
Click to collapse
no adb shell.
most people have installed adb in such a way that they can access it's tools from any directory. however, at least on my computer, fastboot commands will only work from within the android tools folder where fastboot is located.
hope this helps.
riotburn said:
yes it was. I need this fixed fast she just got it yesterday!, i rather like my testicles, kind of attached to them. I humbly accept all flaming and newbie calling.
Click to expand...
Click to collapse
Did you download the drivers??? they are not the same as the ones installed when you connect the phone....
yea also try pulling the battery and sometimes thats all it takes to get the use to be seen
then tell ur girl to mod the evo her self in case something like this happend my wife rooted and mods her's she love's to tinker
Lol at ruining your girlfriends phone. What tutorial were you following?
Sent from my HTC EVO via XDA App
i love how this is like, atleast the 4th thread someone has ruined there GFs evo due to inexperience, or the inability to read.
seriously, im not even trying to flame. i love reading this stuff.
its like general information for what NOT to do, for us that do read.
if you find the answer that works for you, mind mentioning said message?
i like to see threads that answer the questions at least, rather than have 10 suggestions, and no final response
Dam that sucks
Sent from my PC36100 using XDA App
how do i transfer the files for the second part of the usb is broken?
I was following the one that has pic by pic, and got to the point where pc36 wouldn't work. Saw that with the newest version this method wouldn't work. Went to the tutorial for that workaround and started following that. I think it got mixed up in there and thought i had nand unlocked it. Went to install the new radio, checked the system info and it wasnt the new one and started to get the problems.
Think it is rooted though because i get the # in adb shell.
How does one check to see if they did unlock nand, besides of the problem causing method i did?
I believe i ****ed up the custom recovery part. When I would load custom recovery it would flicker back and forth to the stock recovery, dont know if thats normal.
update: with more searching i found this http://forum.xda-developers.com/showpost.php?p=7136621&postcount=128 to use a update to fix the usb.
I did this and at least now it is charging, still not connecting to computer though it will charge through comp.
Can i flash back to the stock rom now? Will that fix it? How do i flash the stock rom?
Laughed at the thread title. Is the phone messed up, or the girlfriend? Gotta love misplaced modifiers.
If in fact you are rooted, you can use this method. It will put you back to "stock" with root and all the latest updates. If your computer wont mount your phone, you may have to get a micro sd card reader and plug it directly to your usb on your computer to download the files you need. Just make sure the phone is off or you unmount the sd in settings before you remove it. Or you can download them from your phone's browser, but you'll need a file manager to move the files to the root of your sd. If that wont work, your sd card might be corrupted.
http://forum.xda-developers.com/showthread.php?t=715915
dglowe343 said:
If in fact you are rooted, you can use this method. It will put you back to "stock" with root and all the latest updates. If your computer wont mount your phone, you may have to get a micro sd card reader and plug it directly to your usb on your computer to download the files you need. Just make sure the phone is off or you unmount the sd in settings before you remove it. Or you can download them from your phone's browser, but you'll need a file manager to move the files to the root of your sd. If that wont work, your sd card might be corrupted.
http://forum.xda-developers.com/showthread.php?t=715915
Click to expand...
Click to collapse
THANKS! I got it now. I had root but not nand so that prob f'ed it up. The link you sent me requires nand and has go do toasts method. I did that with no problems and had nand unlocked. So I installed the 2.0.... radio and freshevo with no problems. Thanks to everyone who helped, I will post in the first post what I did, at least what i can remember. I love xda, thanks so much guys.
Okay i have a big problem...
I have rooted my device, however didn't run the ENG build, so my recovery is dependent on the pushing of the update.zip...
I flashed the myfroyo5 after pushing the update.zip... and ADB worked great, found the device in HBOOT and recovery.
Now after flashing this ROM, when i try and reboot back HBOOT no devices found.. however when i'm at the home screen with Myfroyo5 booted up, it sees the device..
Now i can't run any update, or get into clockwork recovery because i can't push the update.zip, because ADB can't see my device....
Please help! Any idea how i can get it to see my device with Myfroyo5? Otherwise i'm stuck with Myfroyo5 and can't reverse or do anything with it
Before all i did was change the option from device storage, to charge only, and that's how it worked...
again any ideas are appreciated!
wow 58 views and no one has any ideas? Please help!
Try turning on USB debugging mode?
Yes its always on, always check marked
I feel like I did have a similar problem at one point, but I don't remember how I resolved it. Sorry.
gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build
tubaking182 said:
gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build
Click to expand...
Click to collapse
Must your replies always, ALWAYS have some snarky bit about how the person asking the question screwed up?
Humans are prone to error. You have valuable insight but beating someone's ego up before you give it really offsets your kindness.
Sent from my T-Mobile myTouch 3G Slide using XDA App
They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I see your point but, as I recall, the ENG build came after root had been put out there for a day or so. I'm also pretty sure it came after SlideMeRoot1.
Things like this, along with simple mistakes, can cause these errors. You are helpful but I just find the "hey, dummy" tone to be overkill.
Not everyone who screws up is out to **** up your day, ya know? I've been having my own ENG build problems because I made a mistake. It doesn't mean I don't know how to follow directions, it just means I made a mistake, the way every human on the planet does.
I apologize, as well, because my own real life smiley fun tone doesn't translate well to the forum. IE: you good kid.
tubaking182 said:
They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile myTouch 3G Slide using XDA App
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
Just use CR new root method for the ota update and then follow the steps to flash ENG build. wouldnt that work? cause its unneccessary for the device to be recognized in hboot in adb that way =\ just guesing
i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...
javolin13 said:
i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...
Click to expand...
Click to collapse
do u have root in the shell script when u try to push the files over?
yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...
javolin13 said:
yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...
Click to expand...
Click to collapse
i mean u could always just unroot and start from square one
can't unroot if my device is not seen with adb in hboot / recovery
javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps
Suntar said:
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps
Click to expand...
Click to collapse
Thanks for the idea, but flashing the ENG build is pointless unless i can push the flash_image, and mtd0.img to /data/local... which for some reason my phone will not allow me to do this part;
Code:
type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.
Thanks in advance to/for any and all help, long story short: I need a genius workaround to Root my Evo 4G
What's Wrong: (Keep in mind I've tried and am aware of the necessary settings/steps)
1. PC doesn't detect USB connected/debug enabled Evo
2. USB selection on Evo seems broken. Only the 'Debug Enabled' notification alerts of activity
3. All update.zips fail Signature Verification in Recovery
4. HBOOT 'SD Whatever' it said doesn't say it anymore when HBOOT loads and scans the SD card
5. HBOOT USB does nothing when the Evo and PC are connected. There's more, but minor I think.
What Works:
1.This fast ass processor, hells yeah! If you haven't, try 'My Paper Plane2' from the Market. Stellar.
Assumed/Possible Solution Routes: (Cue the Elite, at least one of these could work, right?)
1. Fix Signature Verification(s) for Recovery update.zips
- About this, I got error 'E: Error in cache/recovery/command' in Recovery, so with Root Explorer I made recovery and command folders with their respective permissions and now get 'Error in CACHE: recovery/command (Bad file number). Was my guess at all close to fixing that?
2. Somehow reflash HBOOT with S-ON in Recovery
3. Android executed 1-click/auto/apk permanent Rooter
4. S-OFF during z4Root's temporary Root
5. Manual missing/broken system file replacement in Root Explorer
6. Terminal Emulator - USB Debug or .img flash?
Thanks again for the help, I'm not new but I did break some of this myself. Using a rooted Huawei Ascend (I've done 4, everyone around me has this stupid phone), I guess I just assumed I was a developer and jumped right in. Lesson Learned=D
No rooted roms will work until you're rooted "s-off" but im assuming you're on the comp right now right? If so maybe this could help you!
http://noobgui.de/wiki/index.php?title=Main_Page
No usb or hboot, ouch.....
Usb fix :-(
http://forum.xda-developers.com/showthread.php?t=695243
Sent from my PC36100
Yeah, Im on now. i have seen both pages, but the Evo Root Wiki i had lost in the sea of links earlier, so thanks.
log3an said:
Yeah, Im on now. i have seen both pages, but the Evo Root Wiki i had lost in the sea of links earlier, so thanks.
Click to expand...
Click to collapse
Last I saw the EVO root wiki was way outdated.
Sent from my PC36100 using XDA Premium App
go to unrevoked.com and download the unrevoked forever tool and make sure you have the adb & hboot usb drivers installed on you pc. Everything you need can be found at unrevoked site for usb drivers, etc. Boot into Hboot on your evo. Connect to your pc with usb cable and choose charge only. Then select Fastboot or Hboot on your evo and press power button. Then run the unrevoked reflash package you have already downloaded. Let it do it's thing and you will have a new Clockwork custom recovery.
Thanks, but Ive tried all the easy options, im going to need to command line some crap. Im going to generalize my problem and edit this post.
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
simple29 said:
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
Click to expand...
Click to collapse
what guide are you using? the recovery img has to be in the same folder as fastboot unless you point it towards a different folder
In the same boat as the OP, I've done everything right and I get this error message in cmd with the black screen and white HTC text.
BTW OP - You can go back to using your phone. Take out the battery (with the usb plug out of the phone or computer) and put it back in and turn the phone on normally. You'll just have to go through the process again of fastboot oem rebootRUU to get back to the black screen with white HTC text.
I'm using the CyanogenMod Wiki HTC Incredible 2 Full Update Guide (since I cannot link it in my post), I dunno what the OP is using. Also, the recovery file is in the appropriate location(s) in the android-sdk-windows folder.
im using the cyanogenmod wiki and i tried putting the recovery image for clockwork into the same folder as fastboot and adb and it still gives me that error and i dont have the technical savvy to figure this out
edit: that would be the platform-tools folder in the android sdk folder, thats what i found people did by googling this
and to finalassault, i took out my battery and tried turning it back on normally i just get stuck at the white screen with the green htc lettering so i clearly messed something up unless i just have to wait a few minutes
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
nothing is working and im completely lost, thanks for the help though
also i still cant turn my phone on normally
drcrawfo said:
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Same error, except it's just coming up as not able to load this file instead of the other one. Maybe I possibly screwed up whilst doing AlphaRev?
Edit - I just did it a different way and I didn't get an error message:
sending 'recovery' (5022 KB)...
OKAY [ 25.776s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 28.030s
I guess that worked.
Edit 2 - It "worked" but didn't really do anything else. Might have done something wrong on the AlphaRev step. Actually I'll shut up now, something else showed up.
Edit 3 and final edit - Done and done. That was fun.
how did you get it too work???
simple29 said:
how did you get it too work???
Click to expand...
Click to collapse
It sounds like you may have borked your stock rom....if you can boot to hboot and select fastboot then you should be able to flash the CWM from this link http://forum.xda-developers.com/show...php?p=14947083
Follow the instructions on the link not the one from CM Wiki. Make sure you have fastboot.exe and CWM image from the link in the same folder as your adb. If you're using windows 7 64bit then you'll need to run adb in compatability mode (at least that's what I had to do to get it working in 64bit).
You should then be able to flash a rooted, deodexed stock froyo sense rom from this link by Jcase http://forum.xda-developers.com/showthread.php?t=1138274 or use XGunthers Incredibly Debloated Rom here http://forum.xda-developers.com/showthread.php?t=1138202
That should get you up and runnning. Or you could just jump straight into the GB ASOP roms CM7, MIUI, etc.
Let me know if this works for you....
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
edit: got it in compatibility mode, i suppose i didnt install it right because it looks like it does something for a few seconds then seems to stop
simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
Use the link in my post above.
Sent from my Incredible 2 using Tapatalk
simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
It's okay don't worry...I'm pretty new to this stuff too since I just got into rooting about 2 weeks ago.
Compatability mode is an option in windows 7. Right click on the adb.exe file and select Properties. Once that comes up, you'll need to select the compatability tab on top and choose run in 'Windows XP Service Pack 2' mode (sorry I'm at work and don't have access to my win7 machine). Then click ok and it should run in compatability mode.
Then just follow the flash instructions from the link drcrawfo posted up and you should be good to go!
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
ok so idk why but i decided to try taking out the sd card and then when i did the flash recovery cwm thing a whole list of commands came up in the command prompt and i have no clue if thats good or bad or what command i should pick
ill list a few just to see if that helps you guys in helping me out
update <filename>
flashhall
flash <partition> [ <filename> ]
and a few more then there were options that followed
edit: and now for somereason it doesnt flash again but if i do fastboot recovery i still get all those options so is there a way to get the cwm to flash through that way
simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
Hmmm..so you have all your files setup in the same folder and when running the commands from cmd they don't do anything? Does it saying anything is being sent?
This may be beyond my expertise. Have you tried posting in the clockwork mod thread in the development section?
Sent from my Incredible 2
I just want to mention that I didn't end up using the exact commands that are given from the wiki, that didn't seem to work for me. I had to mess around with it (including manually pointing cmd to where it was) to get it to work for me. Had all of the drivers, SDK stuff, the path and everything where they should have been. I hope you get this resolved.
nothing is working out for me this is not fun
same boat as you simple but I can still use my phone. I just gave up as none of the methods seemed to work.
simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
You need to open a command window, change the working directory to where adb/fastboot are located and then type adb.exe at the command prompt.
It sounds like you are trying to double-click the adb.exe from Windows Explorer.
yea i was double clicking, im not too savvy with this stuff, how do you change the directory and all that
First off I'd like to preface this by saying that I love having an Android & I am so grateful for the devs out there that put in endless hours of work for the community.
I am a n00b, but have successfully flashed ROMs on various devices... moto backflip, triumph, nook color...
I currently have an HTC Wildfire S on VMUSA.
Here are other stats:
MARVELC PVT SHIP S-OFF RL
HBOOT-1.06.000
MICROP-0354
RADIO-0.94.00.0824
AUG 15 2011,22:34:38
CWM v5.0.2.8
32gb SD CARD [FAT32/EXT-2 VIA MINI PARTITION TOOL ON WIN7]
MAC OSX LION
WINDOWS 7 [VIA PARALLELS]
Attempted the following:
wipe data/factory reset in CWM
wipe dalvik cache
ran SuperWipeMarvelcEdition.zip (completed successfully)
then tried to install "simonsense3.5v.2.zip" and the following happens:
"--Installing: /sdcard/ROMs/simonsense3.5v2.zip
Finding update package...
Opening update package... (it will either hang here or...)
Installing update..." (it will hang here and then reboot itself into CWM recovery)
I tried flashing simon's v.1 of this ROM a few weeks ago and gave up because I couldn't get it to work and it took me many tries to get it back to the stock ROM. I tried searching on the forums for any issues like mine but haven't found any, and I tried all of the recommendations I could find.
Please let me know if you need any additional information!
Thanks so much!!
You may want to try just redownload the zip file (if you haven't already.)
Also, how did you get S-OFF? Was it Goldcard method or did you receive the phone as S-OFF?
And finally, thank you for detailed information about your phone, computer, and the steps you have tried to fix the issue. It makes troubleshooting much easier!
kalaker said:
You may want to try just redownload the zip file (if you haven't already.)
Also, how did you get S-OFF? Was it Goldcard method or did you receive the phone as S-OFF?
And finally, thank you for detailed information about your phone, computer, and the steps you have tried to fix the issue. It makes troubleshooting much easier!
Click to expand...
Click to collapse
I haven't tried re-downloading it, I will do that right now. 9:23PM redownloaded and flashed another copy...still hangs at "opening update package..."
I used the Goldcard method from this thread: (google: 452087-tutorials-roms-team-marvelusc-everything-you-need it won't let me post a link because i'm new to the forum)
and you're welcome! I appreciate the time that experienced users take to help out people like me and want to make it as quick & painless as possible!
EDIT: i attached a zip of the recovery.log from CWM from one of the first times I tried to flash the ROM...don't know if it helps.[/COLOR]
heatherelane said:
I haven't tried re-downloading it, I will do that right now. I used the Goldcard method from this thread: (google: 452087-tutorials-roms-team-marvelusc-everything-you-need it won't let me post a link because i'm new to the forum)
and you're welcome! I appreciate the time that experienced users take to help out people like me and want to make it as quick & painless as possible!
EDIT: i attached a zip of the recovery.log from CWM from one of the first times I tried to flash the ROM...don't know if it helps.[/COLOR]
Click to expand...
Click to collapse
Thank you for that link. And if you would, just post back on how the re-download goes. Personally, I didn't see anything in the recovery.log, but maybe a more experienced user would.
kalaker said:
Thank you for that link. And if you would, just post back on how the re-download goes. Personally, I didn't see anything in the recovery.log, but maybe a more experienced user would.
Click to expand...
Click to collapse
still hangs at "Opening update package..."
Are you downloading from your computer then putting it on your SD then flashing or are you using ROM Manager?
Have you tried any other ROMs? Try flashing CM7 (make a backup in Recovery first).
CM7 Link
kalaker said:
Are you downloading from your computer then putting it on your SD then flashing or are you using ROM Manager?
Have you tried any other ROMs? Try flashing CM7 (make a backup in Recovery first).
I first downloaded on my phone and flashed using ROM manager, but this time I downloaded from computer and transferred to SD card using a usb sdcard reader.
downloaded CM7 now. I had CM7 on my Triumph, is this build ok for daily use?
Click to expand...
Click to collapse
heatherelane said:
I first downloaded on my phone and flashed using ROM manager, but this time I downloaded from computer and transferred to SD card using a usb sdcard reader.
downloaded CM7 now. I had CM7 on my Triumph, is this build ok for daily use?
Click to expand...
Click to collapse
This build is pretty good. It has some MMS and WiFi issues, but until Sense 3.5, this was the only ROM I'd use. In fact, I'm using it right now. You'll need to flash the gapps package from Recovery if you do CM7 (which I'm sure you know, since you had CM7 before.)
kalaker said:
This build is pretty good. It has some MMS and WiFi issues, but until Sense 3.5, this was the only ROM I'd use. In fact, I'm using it right now. You'll need to flash the gapps package from Recovery if you do CM7 (which I'm sure you know, since you had CM7 before.)
Click to expand...
Click to collapse
awesome, I might just stick with this. I don't use MMS anyway...what wifi issues are there? I barely get any service in my apartment so I am usually on wifi here.
heatherelane said:
awesome, I might just stick with this. I don't use MMS anyway...what wifi issues are there? I barely get any service in my apartment so I am usually on wifi here.
Click to expand...
Click to collapse
I actually haven't had many Wi-Fi issues, but they've been reported. The thread can be found here. Usually I'll lose WiFi if the phone has been locked for awhile. A quick fix I'll do is Settings>Wireless & Networks>WiFi. Then I'll toggle it off then on and it'll work fine.
Did it flash or have you tried yet?
kalaker said:
I actually haven't had many Wi-Fi issues, but they've been reported. The thread can be found here. Usually I'll lose WiFi if the phone has been locked for awhile. A quick fix I'll do is Settings>Wireless & Networks>WiFi. Then I'll toggle it off then on and it'll work fine.
Did it flash or have you tried yet?
Click to expand...
Click to collapse
just downloaded, flashing now. it's currently on "Installing update..."
latest gapps is still 20110828?
heatherelane said:
just downloaded, flashing now. it's currently on "Installing update..."
latest gapps is still 20110828?
Click to expand...
Click to collapse
Hopefully it works! And yes, 20110828 is still the latest. If you need the download link:
http://goo.im/gapps/gapps-gb-20110828-signed.zip
kalaker said:
I actually haven't had many Wi-Fi issues, but they've been reported. The thread can be found here. Usually I'll lose WiFi if the phone has been locked for awhile. A quick fix I'll do is Settings>Wireless & Networks>WiFi. Then I'll toggle it off then on and it'll work fine.
Did it flash or have you tried yet?
Click to expand...
Click to collapse
it restarts in the middle of installing should I try a newer version of CWM? I'm on 5.0.2.8.
heatherelane said:
it restarts in the middle of installing should I try a newer version of CWM? I'm on 5.0.2.8.
Click to expand...
Click to collapse
What happens if you just reboot the phone? Is it the previous ROM or does it fail to boot?
5.0.2.8 is the latest official version for the Marvelc. I am using a not-so-stable touch recovery koush made before realizing Marvelc is mdpi.
kalaker said:
What happens if you just reboot the phone? Is it the previous ROM or does it fail to boot?
5.0.2.8 is the latest official version for the Marvelc. I am using a not-so-stable touch recovery koush made before realizing Marvelc is mdpi.
Click to expand...
Click to collapse
It fails to boot . tried again and now it's hanging at "Opening update package..."
Alright, let's try redownloading the recovery (http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvelc.zip). Then re-flashing the recovery.
Download that file.
Power off phone.
Reboot to HBOOT (Power + Vol. Down)
Choose Fastboot
Open Terminal/Command Prompt
Code:
fastboot flash recovery <path-to-file>
Where, of course, <path-to-file> is the actual path and don't actually put the angle brackets.
kalaker said:
Alright, let's try redownloading the recovery (http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvelc.zip). Then re-flashing the recovery.
Download that file.
Power off phone.
Reboot to HBOOT (Power + Vol. Down)
Choose Fastboot
Open Terminal/Command Prompt
Code:
fastboot flash recovery <path-to-file>
Where, of course, <path-to-file> is the actual path and don't actually put the angle brackets.
Click to expand...
Click to collapse
>< sorry...can you back up a few steps...I think I need to install your scripts first from your signature?
If you do not have ADB and Fastboot installed on your computer, then yes, you will need to run those scripts.
Simply open Terminal (they're Mac- and Linux-only) and drag and drop the "ADB Install Mac.sh" into the window. Then hit enter.
Edit: Do the following ONLY if you get a permssion error.
If it says something about permission denied, type
Code:
chmod 755 <path-to-directory>/*
chmod 755 <path-to-directory>/*.*
Note, do not do the file, but the directory their in. For example, if they're on your desktop, do "chmod 755 ~/Desktop/Android/*".
I had problems with koush recovery. So I've stuck with alquez unofficial recovery. No problems at all and I do a ton of flashing. It's better imho
Sent from my HTC_A510c using XDA App
kalaker said:
If you do not have ADB and Fastboot installed on your computer, then yes, you will need to run those scripts.
Simply open Terminal (they're Mac- and Linux-only) and drag and drop the "ADB Install Mac.sh" into the window. Then hit enter.
Edit: Do the following ONLY if you get a permssion error.
If it says something about permission denied, type
Code:
chmod 755 <path-to-directory>/*
chmod 755 <path-to-directory>/*.*
Note, do not do the file, but the directory their in. For example, if they're on your desktop, do "chmod 755 ~/Desktop/Android/*".
Click to expand...
Click to collapse
ok it installed no problem, no permissions error. but now I get this error...
hlane$ fastboot flash recovery /Users/hlane/Downloads/recovery-clockwork-5.0.2.8-marvelc.zip
sending 'recovery' (2014 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s