Related
When booting the Nexus One I get an Android with an explanation point, then I am able to toggle the volume key and power to get into "Android system recovery <2e>" screen which gives me the options
-reboot system now
-apply sdcard:update.zip
-wipe data/factory reset
-wipe cache partition
when it's in this screen I can NOT access it through fastboot or adb.
It looks like it is only allowing me to push "officially" signed update.zip files to it and nothing else.
I cannot get it in to hboot or anything else it ONLY boots into "Android system recovery <2e>"
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
irishrally said:
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
Click to expand...
Click to collapse
Yes, with no luck, it just goes straight to the Android and explanation point
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
hyperandy said:
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Click to expand...
Click to collapse
Heres a thread that contains the official 2.1 update1 zip.
http://forum.xda-developers.com/showthread.php?t=627823
Maybe the volume key or trackball is stuck/damaged?
irishrally said:
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
Click to expand...
Click to collapse
ya at this point I was kinda figuring that but I am hopeful ...I unlocked the boot loader and everything was going great until I partitioned the sd in the recovery image, then I started getting a weird MISC error and couldn't boot up at all, only in recovery but fastboot and everything still worked. Then I saw a post about applying the original image to the device via fastboot, preformed that and ever since then I have had a $500 brink that lights up
I don't think you can brick the N1 by just flashing a ROM, usually this only happens when changing the radio or spl.
I would try taking out your sd card, copy all your files you your computer, format your sd card, copy your files back to your sd card and see what that does for you. Maybe some issue arose when you partitioned your sd card, although you said fastboot still worked until you flashed the ROM. Worth a shot though.
If you can access fastboot then, I would flash Amon Ra's custom recovery image via fastboot and take it from there.
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
hyperandy said:
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
Click to expand...
Click to collapse
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
irishrally said:
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
Click to expand...
Click to collapse
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
hyperandy said:
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
Click to expand...
Click to collapse
Did you try copying the .zip file in the link below to your sd card and trying to flash it in recovery?
http://forum.xda-developers.com/showthread.php?t=627823
Thank you, ya I didn't see the link the first time. duh. Yep I tried that and I get a build.prop error (although this update says installing for a second and i see a progress bar, I have tried that same file from a few download locations to make sure it wasn't a bad download too):
file_getprop: Failed to stat "/system/build.prop": No such file or directory
E:Error in /sdcard/update.zip
(status 7)
Installation aborted
Thank you for all your help!! but I am afraid this isn't looking to good.
I also tried creating that file just to see but since it wasn't officially signed it gave me an error about that
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
hyperandy said:
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
Click to expand...
Click to collapse
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
irishrally said:
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
Click to expand...
Click to collapse
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
hyperandy said:
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
Click to expand...
Click to collapse
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
martin0285 said:
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
Click to expand...
Click to collapse
No haven't tried those checking the Help Brick post I will see what I can find. No adb and not fastboot devices, just says waiting for device if I try anything.
Since you have unlocked the bootloader have you tried a complete reload?
fastboot: flash boot, flash recovery
recovery: wipe everything, reset, install latest CM.
Did you ever figure this out?
Dear members, Like always i first of all would like to thank you all for the great effort and hard work all of you have put into this wonderful site.
I am a noob with a rooted nexus one. ( i was begining to think of myself a step above noob recently but trying to update my phone to froyo made me realize i still am a noob.
I so want to update to froyo NOW without waiting for the OTA update but i just cant figure out how to. i downloaded the FR50 ( with and without radio ) but both failed. SO i figured it must be due to stock recovery. So i went to Amon Ra's thread to flash the new recovery image using terminal but after placing the image on the sdcard when i enter the flash image command , it says " image not found " when its most definitely there on the sdcard and i checked the spellings over and over again but it just wont flash and as a result i still cant enjoy froyo
I am sooooo sorry if i posted this thread in the wrong section but i really could use some guidance from the most intelligent Android people i know .
Regards,
Nadeem
It's basically a 4 step process, but make sure you did all of them.
1) Unlock Bootloader
2) Apply Root. I used this method, quick and painless: http://android.modaco.com/content/g...-erd79-frf50-superboot-rooting-the-nexus-one/
3) Flash Recovery using ADB.
3a) Recommended: Do a Nandroid backup image of your Stock 2.1u1, just in case something wierd happens during your flash.
4) Flash FRF50 ROM w/Radio. You want the version with the new Radio, as I believe 2.2 won't work with the 2.1 radio without tinkering.
ATnTdude said:
as I believe 2.2 won't work with the 2.1 radio without tinkering.
Click to expand...
Click to collapse
It works for the most part, but you'll get a crash if you try to record video without updating the radio.
Wait...you put the Recovery image on your SDCard? It should be on your harddrive. You push the the image from the HDD to the phone. Unless there's some other way I don't yet know about.
caliwolv said:
It works for the most part, but you'll get a crash if you try to record video without updating the radio.
Click to expand...
Click to collapse
Well, I'm glad I at least the gist of the material is sticking. I browse this place just about every day trying to keep myself from bricking my phone. If I do, it's back to my Nokia E71, and being forced to use Symbian after Android 2.2...not pleasant at all.
I highly appreciate the super quick response ATnTDUde
The first two steps in your method describe how to get root i presume....
Actually i already rooted my Nexus 1 and i am fairly certain the bootloader is unlocked too ( i see a small padlock unlocked every time i turn my N1 on)
Oh so i am going to have to flash the AMon Ra recovery image using ADB. actually on Amon's thread there was another method of flashing the image using terminal which i tried and failed at. I'll most definitely try ADB method once i get back home.
Just wanted to ask you a quick question Sir.
Once i flash Amon Ra's recovery image i assume i wont be getting any OTA updates from google ???? right ....
Also if i want to go to the stock recovery image ( is there a way to do so ? ) will i start getting OTA updates
Please some one help with the two questions above coz i cant start the process without knowing.
nadeemhasnaat said:
......
Once i flash Amon Ra's recovery image i assume i wont be getting any OTA updates from google ???? right ....
Also if i want to go to the stock recovery image ( is there a way to do so ? ) will i start getting OTA updates
Click to expand...
Click to collapse
1) right
2) yes
ATnTdude said:
Wait...you put the Recovery image on your SDCard? It should be on your harddrive. You push the the image from the HDD to the phone. Unless there's some other way I don't yet know about.
Click to expand...
Click to collapse
Yeah, its very easy.
adb shell flash recovery /sdcard/Amon-Ra.img
or whatever the thing is.
or you can
fastboot flash recovery C:\android\tools\wha\tev\er\Amon-Ra.img
The path just has to be correct wheter o
I'm a relatively new user to root, with my htc hero cdma rooted since Feburary 2010, but I've been having some problems as of late with my custom recovery image.
When I try to load the Image from fastboot, I get the error "Wrong or no image," (Among others of the same nature), as fastboot tries to load the image several times, it fails with the same general error. It happens very quickly, so I can't post many details, but if a picture or two is needed for more information, I can provide a few for refrence. I am running Darchdroid 2.6.2, great rom, and I would love to update to the newest image(And Rom). I've tried booting into recovery several times, but it bootloops at the HTC logo. I've tried booting from fastboot and DS updater, but the same bootloop occurs, probably because the error is ongoing at fastboot. I've tried flashing multiple images and from using flashrec, I get a command line error. I've flashed many through command line, and the same error occurs.
Can Anyone help me out, or knows what's going on?
PS: If it helps, I have all of the fastboot device stock, EX: radio is the stock 1.0.4 and the touch panel is the stock touchpanel, etc.
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Broken Root???????
Kcarpenter said:
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Click to expand...
Click to collapse
I tried it, but unfortunately, it didn't work. Instead, the same error came up again several times, and I tried with many different images, even with my last two working images.
Can you ask or message anyone who you know who might know whats going on, and can help me???
Ryoma Echizen said:
Can you ask or message anyone who you know who might know whats going on, and can help me???
Click to expand...
Click to collapse
What error message is it giving when you try to flash a new image?
I would also try a different SD card.
EDIT:
NVM I assume that you are getting the run via adb error.
Try a different card. Your current ROM should have absolutely no effect on nandroids.
Broken Root???????
Kcarpenter said:
What error message is it giving when you try to flash a new image?
I would also try a different SD card.
EDIT:
NVM I assume that you are getting the run via adb error.
Try a different card. Your current ROM should have absolutely no effect on nandroids.
Click to expand...
Click to collapse
Ok I will try it, thanks. That could be the problem, since I switched sd cards recently. I am not getting the run via adb error, I am getting an error on fastboot that says; wrong or no image. My image started to freeze when I tried to flash when I switched sd cards to an 8gb. I will try this, and thanks a lot. I probably wouldn't have thought of this way of solving the problem!
Broken Root???????
Welllll.......
I still can't get the image to work...
Can you give me any help, like direct message anyone who you know who might know how to solve this problem??? The error is as follows: "finding name of image, some element in the said image,"
"Wrong or no image!"
Can you message zenulator or anyone who you know who might be experienced in this problem.
Kcarpenter said:
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Click to expand...
Click to collapse
Do this:
Code:
adb remount
adb shell
cd \sdcard\
flash_image recovery recovery.img
Thats actually what I always have to do for some reason the other does not work.
Broken Root???????
For some reason, I get the same error.
Here are some more specific details (my approximate translation because it went by so fast, and not even the full 15 or so lines, but the gist of it...) :
Checking sdcard...
Opening HCTDIAG.zip...
No image!
checking HCTDIAG.nhb...
Wrong or no image!
If you think the log would help, I can email or message it to you. I have been trying all kinds of commands for the last three hours, and no luck...
If anyone knows any solution to my problem, it would be a great help...
ADB works fine, anyway, so I don't think that's the problem.
Broken Root???????
Anyways, if it helps, I'm just trying to get back to the damagecontrol 2.1 stock sprint leaked rom. I might be able to get away with a wipe and then leaving the only data on my sdcard as the backup from the stock sprint leaked. I don't mind any method, as long as I can get back to default and sense, I'll even take the official update with the low ram of 40 mb, rather then 80.
Best advice right now is to start over. Run the ruu, then reroot. It only takes fifteen minutes at most. I know you probably don't want to but sometimes you gotta instead of wasting hours
Broken Root???????
There may be one error though...
When I try to install apks (I have a mac), I get the error as follows, ex: can't find Browser.apk to install.
Maybe has to be in the operating system area, not sdcard?
Anyways, forget about this. I just need to get a working recovery image. Any advice on how to access recovery via adb, like maybe, "reboot recovery" though I doubt this will work, considering that it is just another way to boot into my broken recovery mode w/out an image, or the apparent, "wrong image!"
Broken Root???????
How do I do this, since I am running a rom that doesn't have htc sync??? Should I factory data reset and place a backup folder w/stock sprint 2.1 leaked on the sdcard so the boot will retrieve that and boot that data, since the whole operating system is extracted onto that backup? I don't really know how to run ruu's, and I don't want to run the risk of bricking my phone.
(Running darchdroid 2.6.2, and I do not blame darch for my current situation, just trying to avoid any misunderstandings there.) (O.O)
Broken Root???????
Sorry about the situation I'm in. Definitely the worst possible situation, and I really, really appriciate any help that anyone is willing to provide me.I'm clearly in a sticky situation...
go here and download the sprint hero 2.27.651.5 ruu. You need htc sync get that from sprint site in support and downloads. First run the sync then run the ruu exe with your phone plugged in and usb debugging turned on. Actually just follow the root guide from regaw
I found another way, it worked for me:
http://forum.xda-developers.com/showpost.php?p=6879703&postcount=953
Just realized you were on MAC I don't know much bout that but I have heard you can dualboot it with windows. Definitely something you want to do if you can and plan on messing with android
-------------------------------------
Sent via the XDA Tapatalk App
Broken Root???????
Well, I do have a windows vista laptop.
However, the sprint support section of the site is down for repairs, (TT.TT) so I can't download htc sync for the moment...
Broken Root???????
YESSSSSSS
The clockwork recovery option worked!!!
Special thanks to davec1234 for providing a working solution!!!
Thanks to thatguydid for providing another solution, and thanks to everyone who has replied to my problem that I created this thread to solve.
Just in case anyone else has this problem, then try clockwork recovery, and I think that Rom Manager is a great app from the market that helped me fix my problem, as well as improve my device speed and fixed my permissions to slow down force closes.
THANKS TO EVERYONE ON XDA WHO PARTICIPATES AND MAKES THIS FORUM GREAT!!!
I couldn't ever have fixed my problem without everyone's help!!!
STAY AWAY from GOD SPEED
i thought it was cool but it wouldnt let me flash new recoverys and froze phone after nandroideds on cm6... i also think it wouldnt let me flash the newest zen exp but im testing the above posts method
Is there a way to remove your recovery in ADB when youre not rooted?
I did it, but i had to clash CWM 3.0.2.4 and format recovery, then when it rebooted. i did adb reboot recovery, it went to fastboot (which makes sense)
then i entered fastboot erase recovery. which might have been pointless but still did.
But my question is if i can erase my recovery through ADB when im rooted or even unrooted?
davidevan said:
Is there a way to remove your recovery in ADB when youre not rooted?
I did it, but i had to clash CWM 3.0.2.4 and format recovery, then when it rebooted. i did adb reboot recovery, it went to fastboot (which makes sense)
then i entered fastboot erase recovery. which might have been pointless but still did.
But my question is if i can erase my recovery through ADB when im rooted or even unrooted?
Click to expand...
Click to collapse
I have no idea if you can adb remove recovery.img or not, you probably could though. You would have to have r/w access to it's mtdblock. Even so, it sounds like you got it. You can always RUU which removes recovery as well. If you are really "unrooted" you wouldn't have a recovery to remove fyi. Also, most adb codes only work with r/w access to your /system partition, so unrooted would likely kill off adb, for what it's intended to do anyway. I am curious though, why do you ask/want to do this?
il Duce said:
I have no idea if you can adb remove recovery.img or not, you probably could though. You would have to have r/w access to it's mtdblock. Even so, it sounds like you got it. You can always RUU which removes recovery as well. If you are really "unrooted" you wouldn't have a recovery to remove fyi. Also, most adb codes only work with r/w access to your /system partition, so unrooted would likely kill off adb, for what it's intended to do anyway. I am curious though, why do you ask/want to do this?
Click to expand...
Click to collapse
Well here was my story, i wanted to go to Sprint to get a new hero cause my hardware was a little bit sticky/not working right, like the volume rocker and call button. So i unrooted with z4 (thats how i rooted). I double checked to see if i had root or busybox. through root checker in the Market. So i made my marry way over there, and these guys have all there phones rooted so they know what they are doing and if it might be rooted. he couldnt find the # or busybox, but he found my recovery img, by going into it manually. AND I WAS SCREWED. haha. so apparently z4 doesnt remove the recovery. To my knowledge thats the only way he found out i had prior root, and it took him bout 20 min to figure that out, so i thought i did a good job, except for having the recovery img
davidevan said:
Well here was my story, i wanted to go to Sprint to get a new hero cause my hardware was a little bit sticky/not working right, like the volume rocker and call button. So i unrooted with z4 (thats how i rooted). I double checked to see if i had root or busybox. through root checker in the Market. So i made my marry way over there, and these guys have all there phones rooted so they know what they are doing and if it might be rooted. he couldnt find the # or busybox, but he found my recovery img, by going into it manually. AND I WAS SCREWED. haha. so apparently z4 doesnt remove the recovery. To my knowledge thats the only way he found out i had prior root, and it took him bout 20 min to figure that out, so i thought i did a good job, except for having the recovery img
Click to expand...
Click to collapse
So what you really needed to do was run the Rom Update Utility to get back to the stock recovery image, not erase the recovery image.
davidevan said:
Well here was my story, i wanted to go to Sprint to get a new hero cause my hardware was a little bit sticky/not working right, like the volume rocker and call button. So i unrooted with z4 (thats how i rooted). I double checked to see if i had root or busybox. through root checker in the Market. So i made my marry way over there, and these guys have all there phones rooted so they know what they are doing and if it might be rooted. he couldnt find the # or busybox, but he found my recovery img, by going into it manually. AND I WAS SCREWED. haha. so apparently z4 doesnt remove the recovery. To my knowledge thats the only way he found out i had prior root, and it took him bout 20 min to figure that out, so i thought i did a good job, except for having the recovery img
Click to expand...
Click to collapse
Oh, now it makes sense. Yeah what Jason said, run the RUU. Did they help you or just say "bugger off you hacker" lol. If you RUU just go to a DIFFERENT store, they might help.
il Duce said:
Oh, now it makes sense. Yeah what Jason said, run the RUU. Did they help you or just say "bugger off you hacker" lol. If you RUU just go to a DIFFERENT store, they might help.
Click to expand...
Click to collapse
Thats the thing i cant run any damn RUUs haha
i always get a bootloader error. i think i literally done every RUU imaginable, except (i forgot the dev) came with a flashable RUU
davidevan said:
Thats the thing i cant run any damn RUUs haha
i always get a bootloader error. i think i literally done every RUU imaginable, except (i forgot the dev) came with a flashable RUU
Click to expand...
Click to collapse
I bet it's error 140 right? look here if I am right: http://forum.xda-developers.com/showthread.php?t=843544
il Duce said:
I bet it's error 140 right? look here if I am right: http://forum.xda-developers.com/showthread.php?t=843544
Click to expand...
Click to collapse
Hhaha oh god this looks technical (for me) i get a lot, but itll probably take me a day to understand the meaning of what it does and how to execute properly
Thanks to the the both of you!
davidevan said:
Hhaha oh god this looks technical (for me) i get a lot, but itll probably take me a day to understand the meaning of what it does and how to execute properly
Thanks to the the both of you!
Click to expand...
Click to collapse
What is a region version exactly? and do i HAVE to set a different path, or will it typically go where it needs too?
davidevan said:
What is a region version exactly? and do i HAVE to set a different path, or will it typically go where it needs too?
Click to expand...
Click to collapse
I don't think you need to worry about the region. I think you just flash the first zip there....... REVISION ........ looks like the dude pulled the zip I would send him a pm to see if he'll give it to you, and if he does, send the zip to me too. FYI I have never actually done that, never needed to.
il Duce said:
I don't think you need to worry about the region. I think you just flash the first zip there....... REVISION ........ looks like the dude pulled the zip I would send him a pm to see if he'll give it to you, and if he does, send the zip to me too. FYI I have never actually done that, never needed to.
Click to expand...
Click to collapse
Iactually got it!
like 15 min ago and i flashed it, ran regaws RUU he uses for unrooting and BAM,
back to stock. Thanks so much =]
Im not sure what your issue was about removing the zip? maybe i got extremely lucky before he removed it haha. if you want it i can send you it via PM
davidevan said:
Iactually got it!
like 15 min ago and i flashed it, ran regaws RUU he uses for unrooting and BAM,
back to stock. Thanks so much =]
Im not sure what your issue was about removing the zip? maybe i got extremely lucky before he removed it haha. if you want it i can send you it via PM
Click to expand...
Click to collapse
Dkd you get my PM?if you ever need anything else ill try to find it for you!
davidevan said:
Dkd you get my PM?if you ever need anything else ill try to find it for you?
Click to expand...
Click to collapse
LOL yeah I got it. I got confused reading that thread and thought the "unneeded" one was still there and the "needed" one was was missing, I think I was wrong. I downloaded it anyway - safety first. I usually don't need help finding anything, I have a BUNCH of threads saved in my userCP, and a crapload of zips/apps/roms/themes/tweaks/kernels/etc that I'll probably never need, lol. Thanks though.
il Duce said:
LOL yeah I got it. I got confused reading that thread and thought the "unneeded" one was still there and the "needed" one was was missing, I think I was wrong. I downloaded it anyway - safety first. I usually don't need help finding anything, I have a BUNCH of threads saved in my userCP, and a crapload of zips/apps/roms/themes/tweaks/kernels/etc that I'll probably never need, lol. Thanks though.
Click to expand...
Click to collapse
screw his threa i got confused too too haha
the. zip i sent is all you nedd and it flashed you is flashed through recovery; I used a stock rom to do this but i guess it doesnt matterwhich rom, guess it just fixed the boot loader entirely (the zip that is) and here is the RUU i persoanlly used... you might use a different one, but this was sufficient for me
http://www.mediafire.com/file/zoutcenvr20udwu/RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.exe
What recovery do you guys prefer?
I've seen a lot of Vivids with WCX these days.
Post your experience with each one!
Stock CWM ftw
CWM still has a lot of issues. It's been causing quite a few hard bricks. Anyone that still has it, I would highly suggest switching to WCX recovery. I have yet to try TWRP but from what I've heard from all the devs, it still has a few kinks. I wouldn't recommend anything other than WCX at the moment.
I don't really see it as whats "preferred". You don't want something on your device that can potentially cause a hard brick. A recovery is something you don't use very often, so it's best to go with the one that just works.
Nice answer, right now I'm on the stock RUU ICS rom with an unlocked bootloader and I want to flash the WCX recovery, I just have to put the wcxrecovery.img in the microSD root, enter in Hboot, select recovery and then flash it with "fastboot flash recovery wcxrecovery.exe"?
Do I have to make a backup of something after doing this?
Thanks in advance for your answer.
Archector said:
Nice answer, right now I'm on the stock RUU ICS rom with an unlocked bootloader and I want to flash the WCX recovery, I just have to put the wcxrecovery.img in the microSD root, enter in Hboot, select recovery and then flash it with "fastboot flash recovery wcxrecovery.exe"?
Do I have to make a backup of something after doing this?
Thanks in advance for your answer.
Click to expand...
Click to collapse
Actually, just put the wcxrecovery on your computer where you have adb and fastboot set up. If you don't know where that is, just download the wcxjb root zip from the guide in my signature and unzip it to your desktop. Enter hboot on your phone and select fastboot. Shift + right click on your computer inside the folder you just unzipped and select open a command window here. THEN, type in the command "fastboot flash recovery wcxrecovery.img" and you're good to go.
slapshot30 said:
Actually, just put the wcxrecovery on your computer where you have adb and fastboot set up. If you don't know where that is, just download the wcxjb root zip from the guide in my signature and unzip it to your desktop. Enter hboot on your phone and select fastboot. Shift + right click on your computer inside the folder you just unzipped and select open a command window here. THEN, type in the command "fastboot flash recovery wcxrecovery.img" and you're good to go.
Click to expand...
Click to collapse
Crap I moved back to linux after I s-off'ed, is there anyway I can use fastboot without having to dig out my aging Pentium 4?
Brand New said:
Crap I moved back to linux after I s-off'ed, is there anyway I can use fastboot without having to dig out my aging Pentium 4?
Click to expand...
Click to collapse
I know it's possible, but I've never tried it. The best tip I've picked up from the guide was this
- Tip 3: On Linux, remember to run fastboot under sudo
Click to expand...
Click to collapse
If you have any idea what that means, it may be of help to you.
Stock CWM. Never used anything else, never had problems, never plan to use anything else.
Brand New said:
Crap I moved back to linux after I s-off'ed, is there anyway I can use fastboot without having to dig out my aging Pentium 4?
Click to expand...
Click to collapse
Just download and install the Android SDK for linux, what distribution are you using?
I suppose you're using Ubuntu or some .deb based distribution, this tutorial may serve for you:
Running something on "sudo" is giving superuser attributes to the processes and services that a program or whatever you are running needs to have to function properly. Yes it's important when you flash with fastboot.
If you can flash on a laptop will be better for you, a friend of mine bricked his galaxy sII when he was flashing and there was an electricity short.
Archector said:
What recovery do you guys prefer?
I've seen a lot of Vivids with WCX these days.
Post your experience with each one!
Click to expand...
Click to collapse
I use the recovery-beta2 recovery from thecubed. I tried WCX but I couldn't get any ROM's to flash with it... nothing but bootloops for some strange reason (yes I fastboot flashed the boot.img first people). I reflashed thecubed's recovery right after having issues and flashing ROM's worked again. I'm sticking with what works and I've had zero issues with thecubed's recovery after using for several months.
I know I sound redundant, but does anyone have a link to the latest WCX recovery?
You have to download from WildChild's website.... It's included in his ROM zip. You have to have 10 posts on his site before you can download anything so be prepared to "earn" the download.
Sent from my HTC PH39100 using xda premium
dusty2422 said:
I use the recovery-beta2 recovery from thecubed. I tried WCX but I couldn't get any ROM's to flash with it... nothing but bootloops for some strange reason (yes I fastboot flashed the boot.img first people). I reflashed thecubed's recovery right after having issues and flashing ROM's worked again. I'm sticking with what works and I've had zero issues with thecubed's recovery after using for several months.
Click to expand...
Click to collapse
Did you use the recovery un-installer to get rid of CWM before you tried the WCX recovery? I remember some people having issues trying to use WCX over one of the previous CWMs without un-installing it first.
Actually your incorrect,its available freely from the rooting flashing thread on here...as far as earning something....dont like participation dont use my work either way tomorrows another day and life goes on now doesnt it....theres no entitilement to [email protected] "earned" comment....
WC
dusty2422 said:
You have to download from WildChild's website.... It's included in his ROM zip. You have to have 10 posts on his site before you can download anything so be prepared to "earn" the download.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Some people just throw stuff out like they know what's going on... Wow get facts right first bro
Y'know if CWM loops, it's because your rom of choice had a useless ext4 performance tuning script in it that changed some of the mount options of /cache.
If you have CWM and find that after flashing a ROM that does weird things to your Vivid, just reboot to fastboot, then issue "fastboot erase cache" then boot to recovery and format /cache.
CWM hasn't caused any hard bricks, it's ROM developers that aren't properly checking their 'init.d tweaks' and updater-scripts. Now that we have s-off, a bad tweak or updater-script can and WILL make your phone hard to fix.
just used TWRP on my Sprint Gnex and love the interface! I used CWM on my old Epic 4G and it worked great too. To me, seeing all the options on that screen is easier....seems stable.
---------- Post added at 11:27 AM ---------- Previous post was at 11:23 AM ----------
Great point but how would the average Joe know that about a rom before a flash? I'd love to be able to know that and avoid bricking altogether (but wouldn't we all). any tips?
Wild Child said:
Actually your incorrect,its available freely from the rooting flashing thread on here...as far as earning something....dont like participation dont use my work either way tomorrows another day and life goes on now doesnt it....theres no entitilement to [email protected] "earned" comment....
WC
Click to expand...
Click to collapse
I don't mind participation... I just find it hard to participate in a forum where I can't download anything. Kind of hard to comment on something that you can't download IMO.
robertmoore208 said:
Some people just throw stuff out like they know what's going on... Wow get facts right first bro
Click to expand...
Click to collapse
Not sure if this was directed at me but I'll assume it is. WC closed all of his dev threads on XDA (Vivid forum at least) which is why I assumed it wasn't here anymore (yes I searched before replying). Not sure that I've ever seen dev related content stuck in a [GUIDE] thread (maybe a link to the thread that has it) so not sure why this was the place chosen and probably why I missed it. Apparently I'm not the only one since I've seen multiple people asking who can't find it. I appreciate you keeping me honest though "bro".
Archector said:
What recovery do you guys prefer?
I've seen a lot of Vivids with WCX these days.
Post your experience with each one!
Click to expand...
Click to collapse
WCX all the way, ROM's, Recovery, & Kernel. Now, I'm not trying to say that CWM doesn't work, I used it alot when I was rooting & flashing my Aria... but I've had nothing but 100% success using WCX Recovery & ROM's since before I started beta testing for him (along with all the other dedicated members).
I've never used TWRP before, & all I think about when I see that word is Big Booty Shaking!!! ;-)
WCX! I have to say that EVERYTHING that he and his team put out is top notch!