Okay, the other night when the ADP 1.5 came out, I downloaded the bits from HTC's site, and followed the directions to the T, not realizing that i was going to lose my recovery partition with Nandroid in it. When I fastbooted my nandroid backup back onto the phone, the recovery partition never came back. How do I put that back on? I redownloaded it, put it on my SD card, and tried to go through the root directions again, but when i type cat recovery.img > /system/recovery.img" it comes back with an error about not enough space on the phone. Also typing "flash_image recovery recovery.img" is too fast for my taste. it's almost instantly back to the bash prompt, no delay like it did the first time i rooted my phone. So uhh, yeah, what do i do to get that back??? I didn't stay on the official ADP 1.5 because I forgot that I couldn't download my paid apps... I tried, wouldn't work, and I thought I had read a news article a while back that the Holiday update fixed that... but maybe I'm just going crazy or have been out of the loop too long (have a new iPod Touch and been playing with iPhone OS 3.0 beta on it, and WOW does that give Android a run for its money, but the 1.5 upgrade is definitely making Android all the more relevant)
when you first made a nandroid backup there were several files, recovery.img was one of them, or you could go get the recovery.img from when you rooted you phone. then just fastboot it to your phone and you will be all better
Yeahhh i did that... the original one i rooted with, i tried fastbooting that one onto the phone, 3 diff times now, doesn't work. And if i still had my nandroid backup i'd be golden.... (had deleted it).
did you try putting the recovery.img on your sdcard and flash_image recovery /sdcard/recovery.img like when you rooted the phone?
Yup. Used the Terminal program in JF 1.42 (which I've now noticed isn't the latest according to the JFUpdater???)... and i did su to get up to root, then mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system, cd sdcard, flash_image recovery recovery.img, and finally the cat. Ran through the same steps over and over, rebooted the phone over and over. NOTHING is working. And yes, the recovery.img is in the root of my SD card.
flamingblue8z said:
Yeahhh i did that... the original one i rooted with, i tried fastbooting that one onto the phone, 3 diff times now, doesn't work. And if i still had my nandroid backup i'd be golden.... (had deleted it).
Click to expand...
Click to collapse
had the same problem..
boot to fastboot - fastboot erase recovery....OK
now put the recovery image on the sdcard and flash from shell...this shoudl fix it.
AH, thank you SOO much. I'll try it now. Gosh, what would happen if it wouldn't boot to the shell LOL then you're stuck fastbooting it. But thank you SOOO much!
Uhhhh, uh oh... something didn't work....... OH, THE JF RECOVERY ENVIRONMENT IS WHAT'S MISSING!!! AH HAH! How do we get the recovery.img out of the JF update?
flamingblue8z said:
Uhhhh, uh oh... something didn't work....... OH, THE JF RECOVERY ENVIRONMENT IS WHAT'S MISSING!!! AH HAH! How do we get the recovery.img out of the JF update?
Click to expand...
Click to collapse
Here you go: http://rapidshare.com/files/227806623/recovery.img.html
this is the md MD5: B0290DB8D554E1378620023E0C5A93DB
hope that helps!
Related
Since some people were interested I've made a stock update zip from the RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe so you can flash via recovery.
This is just for those who want a completely stock rom to work off of or those that can't or don't want to run the RUU. If you want something already tweaked then use DamageControl. I'm not trying to start a custom rom I just did this for a couple people that wanted it.
It does not include the new hboot or radio.img included in the RUU and the system is stock except for adding busybox, patched su and sh.
To use su you need to install Superuser.apk.
Busybox is not installed by default you can do that through a terminal app or adb executing su and running "busybox --install /system/xbin".
You must be rooted and flash via Amon_ra recovery. Recommend nandroid backup and wipe/factory reset before flashing.
Here is a link to my post on how to make an update zip from the RUU.
Download link for the update/rom:
http://dl.dropbox.com/u/6022412/zen-hero_0.1b.zip
The link might be down since dropbox just suspended my public links due to excessive traffic.
Alternate download:
http://www.4shared.com/file/YqMmKAzL/zen-hero_01b.html
This is a link to my google code site where i put up some of the binaries/scripts that I use for rom making. These are linux binaries. If you download them put them in your path so you can execute them from anywhere. Also make sure you chmod them to executable. If you don't know how the google can tell you.
http://code.google.com/p/zen-droid/downloads/list
Due to recent events I just want to say that the devs here put a lot of work into getting you guys these leaked roms. They risk their credibility and their sources risk their jobs. So have some respect and remember it's just a phone.
Thank you,I'm sure a lot of people were wanting this.
What is the point of making a zip when you can just use the RUU?
My RUU just got done booting!
Roman G said:
What is the point of making a zip when you can just use the RUU?
My RUU just got done booting!
Click to expand...
Click to collapse
For people not running windows and for people that don't want to risk flashing hboot or the radio.img.
See I did not know it came with the radio image!
Just booted up fine and got the new radio image and a knew PRI# and was able to update my PRL as well!
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
obelisk79 said:
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
Click to expand...
Click to collapse
crazy, his link says zendroid in it too
http://code.google.com/p/zen-droid/downloads/list
obelisk79 said:
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
Click to expand...
Click to collapse
Yea I thought that was kind of funny. Nice name for a rom though
yeah well, I thought it had a nicer ring to it than fengshuidroid.... was going for a rom which was also centered around a nice clean theme to the sense ui. I'm still making headway on the project.
Re: [ROM] Stock 2.1 Hero Update.zip
Maybe this is a stupid question but, The phone needs to be rooted to install this rom?
Sent from my HERO200 using xda app
theclawpr said:
Maybe this is a stupid question but, The phone needs to be rooted to install this rom?
Sent from my HERO200 using xda app
Click to expand...
Click to collapse
yes you need root and a recovery image
Roman G said:
See I did not know it came with the radio image!
Just booted up fine and got the new radio image and a knew PRI# and was able to update my PRL as well!
Click to expand...
Click to collapse
Interesting! What is the new PRI that you have now?
raynda said:
Interesting! What is the new PRI that you have now?
Click to expand...
Click to collapse
2.10_003 I believe it's the one that damage had that no one could figure out where he got it other than the official release!
okay i have a question, i was trying to update the recovery image to the 1.6.2 . but i get an error ..
The img file is in the sd card and when i do flash_image recovery recovery-RA-heroc-v1.6.2.img i get flash_image not found error ...
i tired to go from scratch and do the factory 1.5 image (RUU) but now says can not start bootloader ...any ideas?
rgildoss said:
okay i have a question, i was trying to update the recovery image to the 1.6.2 . but i get an error ..
The img file is in the sd card and when i do flash_image recovery recovery-RA-heroc-v1.6.2.img i get flash_image not found error ...
i tired to go from scratch and do the factory 1.5 image (RUU) but now says can not start bootloader ...any ideas?
Click to expand...
Click to collapse
adb shell
cd /sdcard
flash_image recovery blah.blah.blah
smw6180 said:
adb shell
cd /sdcard
flash_image recovery blah.blah.blah
Click to expand...
Click to collapse
error
flash_image: not found
rgildoss said:
error
flash_image: not found
Click to expand...
Click to collapse
Thats because the flash images is not called blah.blah.blah
VinceOB said:
Thats because the flash images is not called blah.blah.blah
Click to expand...
Click to collapse
i know that ...lol
ever i try i can not load the damn recovery image ...
power + menu gives me a picture of the phone with ! .....
how can i load the recovery image ?
The phone is rooted but just wont take the revory image
Now this might be a stupid question, but do we need Root for this? I have a friend who's terrified of Rooting but really wants 2.1, so could he just Flash this through the Stock Recovery Image, or should I force him to Root?
Edit: NVM sorry I just read the 1st post on page 2. Told you it was a stupid question.
It seems like the flash_image command is missing.
I am interesting in finding out how to root the RUU 2.1 Sprint Leak, I tried to root my 1.5 to install damagecontrol 2.06, but I had the newest patch and flashrek and other methods wouldn't root it.
Any Suggestions or Links to help me figure out how to load damagecontrol 2.06 rom and root the RUU 2.1 Sprint Leak.
Thanks so much
amdme127
I guess you missed the sticky at the top.
http://wiki.xda-developers.com/index.php?pagename=CDMA Hero Guides
Thanks so much I appreciate it
amdme127 said:
I am interesting in finding out how to root the RUU 2.1 Sprint Leak, I tried to root my 1.5 to install damagecontrol 2.06, but I had the newest patch and flashrek and other methods wouldn't root it.
Any Suggestions or Links to help me figure out how to load damagecontrol 2.06 rom and root the RUU 2.1 Sprint Leak.
Thanks so much
amdme127
Click to expand...
Click to collapse
Well, the leaked RUU comes with root. Are you trying to root your stock hero on 1.5 to be able to flash things?
regaw_leinad said:
Well, the leaked RUU comes with root. Are you trying to root your stock hero on 1.5 to be able to flash things?
Click to expand...
Click to collapse
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
becuase when you used the ruu, it overwrote the custom recovery image with the stock test 2.1 recovery image.
You'll have to load the flash_image file on the phone and chmod it. Then flash the custom recovery again. I think I saw a guide somewhere in here.
Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
If you run the .exe it rewrites the recovery.
Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
Already answered
So is it true that you can gain root access through ADB!
danknee said:
If you run the .exe it rewrites the recovery.
Click to expand...
Click to collapse
not only the recovery, but the radio, bootloader, well, everything.
It's quite the long process to go back, don't know if anyone has tried it yet. Don't know if some of the things can go back a version.
Roman G said:
So is it true that you can gain root access through ADB!
Click to expand...
Click to collapse
Yeah, but, you don't have busybox installed, so you can't do really anything in adb shell.
regaw_leinad said:
not only the recovery, but the radio, bootloader, well, everything.
It's quite the long process to go back, don't know if anyone has tried it yet. Don't know if some of the things can go back a version.
Click to expand...
Click to collapse
I did it for the 2.10 radio and went back to flipz after.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
danknee said:
I did it for the 2.10 radio and went back to flipz after.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
oh yeah, i've seen that post all over like 3 times already. whoops. well has anyone else tried it?
regaw_leinad said:
oh yeah, i've seen that post all over like 3 times already. whoops. well has anyone else tried it?
Click to expand...
Click to collapse
SMW did, plus he posted a link on how to RUU back to 1.56 after doing it as well....without the RUU...lol.
The bootloader is modified, so you can't just RUU the old fashioned way.
smw6180 said:
If it doesn't work, try this post: http://forum.xda-developers.com/showpost.php?p=6013606
It's basically going to stock without using the RUU.
Click to expand...
Click to collapse
danknee said:
SMW did, plus he posted a link on how to RUU back to 1.56 after doing it as well.
Click to expand...
Click to collapse
cool thanks
http://forum.xda-developers.com/showthread.php?p=6142928#post6142928
I wrote up a tutorial on how to root any 1.5 based Hero using the Sprint 2.1 leaked test RUU. This might help.
Any ideas:
I have gone and tried a few tutorials on this site for putting on Amon's image and I always get a denied for the flash_image command when running in adb shell.
This is where I keep getting stopped at in all these tutorials.
Thanks for the help
amdme127 said:
Any ideas:
I have gone and tried a few tutorials on this site for putting on Amon's image and I always get a denied for the flash_image command when running in adb shell.
This is where I keep getting stopped at in all these tutorials.
Thanks for the help
Click to expand...
Click to collapse
he posted how to fix that right above you...
http://forum.xda-developers.com/showpost.php?p=6151388&postcount=12
Thanks so much, I missed that post, so thanks for pointing it out to me.
Putting DamageControl 2.06 rom right now, thanks so much for the help again
amdme127 said:
Thanks so much, I missed that post, so thanks for pointing it out to me.
Putting DamageControl 2.06 rom right now, thanks so much for the help again
Click to expand...
Click to collapse
No problem
ok so I have done some searching and found nothing that actually resolves my problem.
I have tried time and again to flash a newBoot.img, with different images. I always either get "no such file or directory" or "mtd: read all-zero block at 0x0000000; skipping"
the image will never actually flash. it either boot loops on the "htc" screen or freezes on the "htc" screen. it never gets to the animation.
I used the following commands to flash the newBoot.img:
adb push newBoot.img /sdcard/newBoot.img
adb shell
cat /dev/zero > /dev/mtd/mtd2
flash_image boot /sdcard/newBoot.img
reboot
I did this all in the Recovery console.
am I missing something?!
please help, thanks
gmelchert said:
I did this all in the Recovery console.
am I missing something?!
please help, thanks
Click to expand...
Click to collapse
....What exactly are you trying to flash??
pseudoremora said:
....What exactly are you trying to flash??
Click to expand...
Click to collapse
the "newBoot.img" for DarchDroid 2.1 jit
gmelchert said:
the "newBoot.img" for DarchDroid 2.1 jit
Click to expand...
Click to collapse
You are talking about this thread, right? And if so, you are downloading the STABLE ROM, correct?
yes and no, I'm trying the AOSP jit enabled one
gmelchert said:
yes and no, I'm trying the AOSP jit enabled one
Click to expand...
Click to collapse
Let me check something.
gmelchert said:
the "newBoot.img" for DarchDroid 2.1 jit
Click to expand...
Click to collapse
Wow...for a moment there, I thought you were flashing a Darktremor A01 kernel. I was about to ask you where you got that since I never released it.
gmelchert said:
ok so I have done some searching and found nothing that actually resolves my problem.
I have tried time and again to flash a newBoot.img, with different images. I always either get "no such file or directory" or "mtd: read all-zero block at 0x0000000; skipping"
the image will never actually flash. it either boot loops on the "htc" screen or freezes on the "htc" screen. it never gets to the animation.
I used the following commands to flash the newBoot.img:
adb push newBoot.img /sdcard/newBoot.img
adb shell
cat /dev/zero > /dev/mtd/mtd2
flash_image boot /sdcard/newBoot.img
reboot
I did this all in the Recovery console.
am I missing something?!
please help, thanks
Click to expand...
Click to collapse
Nothing I see is incorrect. Try putting a delay of about 10 seconds between erasing the mtd2 device and flashing the ROM. This is especially true if you are flashing from recovery.
tkirton said:
Wow...for a moment there, I thought you were flashing a Darktremor A01 kernel. I was about to ask you where you got that since I never released it.
Click to expand...
Click to collapse
I thought he was flashing a kernel as well... I'm downloading the AOSP file now and then going to check what it is... its a zip file, so I presume it's just a flashable update, but I'll double check.
it is, but later on in the thread there are a few "newBoot.img" to download. one is clocked @ 710mhz and the other is 787mhz i think
pseudoremora said:
I thought he was flashing a kernel as well... I'm downloading the AOSP file now and then going to check what it is... its a zip file, so I presume it's just a flashable update, but I'll double check.
Click to expand...
Click to collapse
He's flashing a kernel...newBoot.img actually comes from a guide that was posted here sometime back on how to compile your own kernel. What tripped me was that newBoot.img is the name of many iterations of my Darktremor kernel, which I never released but do use for testing (I have it currently on my phone on top of FreshToast to test ext4 patches).
His instructions are the same instructions I use to flash...the difference is that I actually flash while in a working ROM (not smart, but it works). He's doing it from recovery. Last time I did from recovery was a couple of days ago, and I got a bunch of errors unless I waited around 10 seconds between clearing /dev/mtd/mtd2 and flashing the kernel.
If he gets the errors, he can try to flash again...it seems to work when I did it.
gmelchert said:
it is, but later on in the thread there are a few "newBoot.img" to download. one is clocked @ 710mhz and the other is 787mhz i think
Click to expand...
Click to collapse
tkirton said:
He's flashing a kernel...newBoot.img actually comes from a guide that was posted here sometime back on how to compile your own kernel. What tripped me was that newBoot.img is the name of many iterations of my Darktremor kernel, which I never released but do use for testing (I have it currently on my phone on top of FreshToast to test ext4 patches).
His instructions are the same instructions I use to flash...the difference is that I actually flash while in a working ROM (not smart, but it works). He's doing it from recovery. Last time I did from recovery was a couple of days ago, and I got a bunch of errors unless I waited around 10 seconds between clearing /dev/mtd/mtd2 and flashing the kernel.
If he gets the errors, he can try to flash again...it seems to work when I did it.
Click to expand...
Click to collapse
Really? Okay, cause I downloaded the AOSP file and it's definitely a custom ROM... but I'm glad it's sorted out now.
still no luck with the waiting. I tried it on stable when it was booted and I got "could not write file" or something like that where "skipping" was. I'm back to "sticking" now. argh
gmelchert said:
still no luck with the waiting. I tried it on stable when it was booted and I got "could not write file" or something like that where "skipping" was. I'm back to "sticking" now. argh
Click to expand...
Click to collapse
Don't do the step that erases your mtd2 partition. Just ran into the same problem with an automated script. 10 seconds doesn't seem to cut it, but I noticed I can just flash without erasing first.
tkirton said:
Don't do the step that erases your mtd2 partition. Just ran into the same problem with an automated script. 10 seconds doesn't seem to cut it, but I noticed I can just flash without erasing first.
Click to expand...
Click to collapse
I just tried that and all I got was a repeat command line
"# flash_image boot /sdcard/newBoot.img
flash_image boot /sdcard/newBoot.img
#
http://forum.xda-developers.com/showpost.php?p=5447589
Try that post use #9
It's not a flashable zip, needs to be unziped and placed into the sdk tools folder!
Also make sure you are not using the one with file ext.bat I believe if you are you need to change it to .img!
If ya need some help hit me up!
Roman G said:
http://forum.xda-developers.com/showpost.php?p=5447589
Try that post use #9
It's not a flashable zip, needs to be unziped and placed into the sdk tools folder!
Also make sure you are not using the one with file ext.bat I believe if you are you need to change it to .img!
If ya need some help hit me up!
Click to expand...
Click to collapse
I used that post in the first place. Basically what I'm trying to do is get AOSP DarchDroid to actually boot so I want to try one of the kernels darch posted. I have not yet been able to get them to flash (what is the correct outcome in cmd when I type "flash_image boot /sdcard/newBoot.img"?) I know you were on of the people who got the jit working, what did you do to get it to work? the rom I mean...
is there a way to unroot and lock the bootloader again ?
quattro_rs said:
is there a way to unroot and lock the bootloader again ?
Click to expand...
Click to collapse
Yes.
Several discussions about it already in here.
To relock the bootloader is as simple as "fastboot oem lock" command.
There's a couple of different ways to get the root out, they're all mentioned in the thread for it.
but as of now no way to flash the stock recovery
slowz3r said:
but as of now no way to flash the stock recovery
Click to expand...
Click to collapse
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
distortedloop said:
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
Click to expand...
Click to collapse
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
slowz3r said:
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
Click to expand...
Click to collapse
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
can someone explain how to do it step by step im new at this ?
ok i managed to lock the bootloader but im still not sure how to unroot the device !
distortedloop said:
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
Oh, alright
google hasnt released a full OS for flashing have they?
quattro_rs said:
can someone explain how to do it step by step im new at this ?
Click to expand...
Click to collapse
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Click to expand...
Click to collapse
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
slowz3r said:
Oh, alright
google hasnt released a full OS for flashing have they?
Click to expand...
Click to collapse
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
distortedloop said:
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
Click to expand...
Click to collapse
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
slowz3r said:
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
Click to expand...
Click to collapse
Ditto.
Ditto.
Ditto (for the most part, CWM isn't bad, but I also prefer Amon_RA).
distortedloop said:
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
Click to expand...
Click to collapse
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Requirements:
-Clockwork recovery or other custom recovery
Click to expand...
Click to collapse
quattro_rs said:
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Click to expand...
Click to collapse
the stock recovery does not allow you to flash custom/unsigned roms or other files for that matter.
so a custom Recovery is required, as of now the only one I believe is available is ClockWorkMod
got it all working now thanks to you and distortedloop .
thanks a lot guys.
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
roadblock217 said:
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
Click to expand...
Click to collapse
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
Tried..doesnt work for me
I can get it to boot past the recovery area, but only stays on the white screen with the green HTC logo...
EDIT:::
I want to try it again, but now somehow I have S ON....and it says TAMPERED, below that UNLOCKED in fastboot..
Really frustrated..
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
You can get into recovery...it won't let you restore a back up or nothing ?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
---------- Post added at 12:22 AM ---------- Previous post was at 12:17 AM ----------
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
Maybe sonic can get you s-off if all else fails with his java card. I'm not sure in your situation but I know he can do it as I used it. But I would use that as last resort
Sent from my HTC6525LVW using XDA Premium 4 mobile app
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
andybones said:
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
Click to expand...
Click to collapse
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
roadblock217 said:
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2725001
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
roadblock217 said:
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
Click to expand...
Click to collapse
because of this, it most likely will not flash the nandroid then as system is a big part of the ROM and needs to be mounted.
you may have to do what was explained earlier and wipe the Internal, and then you may be able to re-do these steps.
so first try it out.
if it doesnt work, I would then wipe the 5 things instead of the 4
1) data
2) cache
3) dalvik cache
4) system
5) Internal storage (this will remove all your internal storage!)
then reboot from recovery into bootloader, then back into recovery and see if system is mounted, if it is, you can go ahead and either do the nandroid backup or an adb sideload. -- your choice
now,
if NONE of that works,
download the "RUU" that was put together and that *should* fix you right up.
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
roadblock217 said:
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
Click to expand...
Click to collapse
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
andybones said:
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
Click to expand...
Click to collapse
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
roadblock217 said:
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
Click to expand...
Click to collapse
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
andybones said:
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
Click to expand...
Click to collapse
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
roadblock217 said:
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
Click to expand...
Click to collapse
It's possible after so long you didn't give the ROM long enough to boot up?
Sounds like RUU might be a cause from flashing AOSP, threads like this are good to warn people, and for when it happens to others, they can read this and know what to do. Maybe think of a new title that could help those in a search to find this thread?