I can flash clockworks recovery through adb and can get in but I'm getting some errors:
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
And a bunch few more which seem to repeat
I also tried to run the restore to stock from here but get an error right when I have to click to write the image.
When I just boot all I see is the unlocked lock and google. It used to boot into storage so I can mount it but not anymore. The only thing I have on the SD is the super user app, Netarchy kernel for 4G, CM7 latest stable for NS and thats it.
Need help
I can push something to the phone through the sdk but I don't know how to mount the sd card to do it.
ufff.... nevermind. I tried the factory restore one more time on another machine 32 bit and it works. It's restoring the image again. Will be locked again so I'll have to try again tomorrow. But the steps on rooting the NS4G don't really work well.
There is a bunch of stuff missing. Like the recovery gets overwritten each time. There are some links missing and dead.
Someone should fix that before we brick some phones.
OK, it restored but only gave me the sd card mount thing. I tried going back to fastboot and unlocked was still there. So I flashed recovery again and wanted to see if I can put the stock rom for 4G from here on it.
No go. I get:
assert failed: write_raw_image("/tmp/netharchy.img", "boot")
Installation aborted.
Help
ok, I'm not sure what ROM I have but I unplugged the cable and bam... sign in screen came in so I'm sighing in. Once I can get to the main menu I'll check versions and kernel but it looks like I have root. It's just that recover is not working well. I have 3.0.0.5. should I get a different one?
OK, I restored again because wifi didn't work. I think it was because I was trying to flash after the first restore and it wouldn't take. So now I checked and the lock when I boot showes up as unlocked but none of the root apps work so I don't think I have root. Not sure.
I also have to figure out what's up with that recovery. I know I need to rename the original so it doesn't flash it every time on boot but I think I need a new version. Anyone know which one is the latest and which one works on NS4G?
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
I think that's backwards. Roms might be compatible but kernels which these roms come with are not. So I believe that it I just flash netarchys kernel which now supports NS4G all should work ok.
Like I said, I'm back to stock and all looks like exactly like it was before ie. no root but the weird part is that fast boot menu says "unlocked". And I also get the lock which looks unlocked with the google sign during boot.
So how is that possible? Anyone?
When trying any app with root it tels me it has no access or it failed. Ie, su cmd says access denied.
BTW, why you attached two files? What is the difference between the two?
herbthehammer said:
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
Click to expand...
Click to collapse
Thanks for your help. I'm rooted and recovery is sticking ok. It was the old recovery. As soon as I flashed it all was good.
One is stock and the other is cwm that works with the ns4g. It wouldn't hurt to have the stock laying around. There might be a time when you need it.
Thanks for the stock recovery.
Sent from my Nexus S 4G using XDA App
Related
I have a NS unlocked and rooted. I have ROM Manager, busybox etc. I followed all the instructions but I can't update ROMs or the 2.3.3 update or CM7 nothing. Each time it starts to unpack or whatever it gets about 1/3 the way and aborts. Something about verifying signatures or something.
Very frustrating.
Thanx in advance
I Love The Smell Of Burnt Rubber Anytime
try to download the ROM again
sounds like the zip file is corrupted
What version Clockwork Recovery are you using? Try reverting back to a older version or something.
Verify the ROM's MD5 Hash using HashTab (Google it)
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
what's the latest clockwork recovery? did you try 3.0.0.5?
Ya. The new ver is 3.0.2.4
I Love The Smell Of Burnt Rubber Anytime
hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
Hmm... It sounds like clockwork isn't properly installed. ROM Manager should take you directly to clockwork recovery without you having to do anything.
the problem you are facing is that you are still on stock rom. so even if you flash clockwork recovery and then reboot to recovery, you'll always end up going to the stock recovery. this is a new feature implemented by google.
what you should do is...
1) go to bootloader
2)flash the clockwork recovery using fastboot
3)DO NOT reboot the phone or quit bootloader. immediately after flashing the rec. using fastboot, just enter recovery (through bootloader)
4)flash you new rom
just for u to have an idea. the recovery should be orange in colour.
option 2.
you also have the option of using a file manager with moun/root functions such as root explorer and rename the recovery script in etc folder but i guess step 1 is much easier for now.
OK I played alot today and this is what happened.
After fixing permissions and flashing the new CWM and wiping data/cache it finally worked. Unfortunately titanium and my backup didnt bring everything over. So I went back and forth between stock and CM7 several times but I just couldnt get all my stuff back in CM7. So I thought Id try the 2.3.3 update but not wiping stuff. That didnt work. Then I tried one more time with CM7 but not wiping. I couldnt get pastthe little CM7 droid on the skateboard. So went back to stock for now. Ill have more time on Sat to give things another try.
At least I can get in it now.
Any ideas/thoughts/
Thanks and sorry for the long post.
Well, okay, technically I'm not actually even totally sure what soft-bricked means, but while I can get to both a fastboot screen and into what appears to be CWM (orange recovery with more options than blue), my phone is hanging on the Google boot screen.
Here's what I did.
I have a rooted Nexus S that was running 2.3.3 stock. The OTA update notification came up today, so I allowed it. But then it seemed to hang for, like, half an hour.
So I pulled the battery and allowed it to reset. Which was fine, no biggie. I still had 2.3.3, but no longer had root. So I flashed the GRI40 superboot. Still fine. But I no longer had an update, and it was still 2.3.3.
So I flashed CWM and went to the 2.3.3 stock image. CWM downloaded said image, didn't seem to have any problems, and I clicked to wipe the cache and dalvik.
And now it won't boot beyond the Google screen. But like I said, I'm on fastboot screen now (unlocked) and seem to still have clockwork. Nothing else, though, and there's nothing on my sd card. I know, I know, the lack of back up is a noob mistake.
Help? I'd really just like to get to stock but rooted 2.3.4.
http://forum.xda-developers.com/showthread.php?t=947950
Use this i have got the same problem
that solved
prad1po said:
http://forum.xda-developers.com/showthread.php?t=947950
Use this i have got the same problem
that solved
Click to expand...
Click to collapse
A couple of the other threads by people with hard bricks (problem today?) mentioned Odin as problematic. It's okay to use?
Also, I have to admit, I see a lot of discussion of Odin in the forums, and have Googled it, but I don't actually know what it is or how to use it.
willentrekin said:
Also, I have to admit, I see a lot of discussion of Odin in the forums, and have Googled it, but I don't actually know what it is or how to use it.
Click to expand...
Click to collapse
Odin is the Fkash program from samsung to flash the lhine first time
you have CWM? no need of odin!
reboot into cwm --> mounts & storage --> mount usb
search a the deoxed 2.3.4 rom and download it..
also search the forum for superuser binary to flash
then wipe system and cache
flash zip first the rom then superuser
reboot
have fun
Okay. Almost there, I think.
You're right about CWM. I got it mounted okay, and get a drive on my computer, into which I can copy a zip and then unmount. At which point I get:
Installing {whichever zip I try. So far, I've tried Nandroid Stock 2.3.4_rooted and 2.3.2 GRH78c}
Finding update package...
Opening update package...
Installing update...
Installation aborted.
That's as far as I get right now. And I'm not touching anything. I wiped the data and cache. Do I have to further mount/unmount anything?
willentrekin said:
Okay. Almost there, I think.
You're right about CWM. I got it mounted okay, and get a drive on my computer, into which I can copy a zip and then unmount. At which point I get:
Installing {whichever zip I try. So far, I've tried Nandroid Stock 2.3.4_rooted and 2.3.2 GRH78c}
Finding update package...
Opening update package...
Installing update...
Installation aborted.
That's as far as I get right now. And I'm not touching anything. I wiped the data and cache. Do I have to further mount/unmount anything?
Click to expand...
Click to collapse
wipe system too? :/
do you have the latest recovery?
maybe you have a nandroid backup anywhere?
else download one at the dev section i think are enough backups
copy one to /clockwork/backup/***DATE***
hope that fixes your problem :S
Sent from my Nexus S using XDA App
willentrekin said:
Well, okay, technically I'm not actually even totally sure what soft-bricked means, but while I can get to both a fastboot screen and into what appears to be CWM (orange recovery with more options than blue), my phone is hanging on the Google boot screen.
Here's what I did.
I have a rooted Nexus S that was running 2.3.3 stock. The OTA update notification came up today, so I allowed it. But then it seemed to hang for, like, half an hour.
So I pulled the battery and allowed it to reset. Which was fine, no biggie. I still had 2.3.3, but no longer had root. So I flashed the GRI40 superboot. Still fine. But I no longer had an update, and it was still 2.3.3.
So I flashed CWM and went to the 2.3.3 stock image. CWM downloaded said image, didn't seem to have any problems, and I clicked to wipe the cache and dalvik.
And now it won't boot beyond the Google screen. But like I said, I'm on fastboot screen now (unlocked) and seem to still have clockwork. Nothing else, though, and there's nothing on my sd card. I know, I know, the lack of back up is a noob mistake.
Help? I'd really just like to get to stock but rooted 2.3.4.
Click to expand...
Click to collapse
Just download the 2.3.4 (stock rooted) file on here...in the de section...
its a nandroid back up
then just put it in the clockworkdmod/ folder on your phone
reboot into recovery and restore it
viola!
thats what i did to get mine rooted...its way easier than trying to actually root it!
edit: yeah what the post above mine said...lol..didnt see that posted yet!
Okay. Followed guidance. Still hanging but maybe getting closer.
I made a backup of the borked system, and then went into the clockwork folder and created a new folder within the backups. I unzipped the 2.3.4root ROM and renamed the folder to almost the same name as the borked system. I then tried to restore that.
I got an MD5 fail? I'm not sure what that means.
Maybe I should replace all the files in the legit-made backup with the files from 2.3.4?
Awesome! I got it! I went and got Axura's 2.3.3 stock/rooted and installed that from the zip. I don't know why the other two aborted, but this one worked. So it looks like I've got rooted stock 2.3.3 again!
I'm not so sure I'm going to try for 2.3.4 now.
Thanks for the help!
Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.
Me[kk]A said:
Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.
Click to expand...
Click to collapse
which cwm did u use
wich su file did u use
read this on rooting http://forum.xda-developers.com/showthread.php?t=1340526
but use this cwm http://forum.xda-developers.com/showthread.php?t=1566613
Me[kk]A said:
Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.
Click to expand...
Click to collapse
download procedure?
just put superuser on sd and install from cwm.
no root access means no su binary's installed. su binary's will not install from the superuser in the market that's just a front end.
wouldn't you also require busy box and then fix permissions using rom manager?
SeraldoBabalu said:
wouldn't you also require busy box and then fix permissions using rom manager?
Click to expand...
Click to collapse
no. busy box has nothing to do with su. and rom manager sucks and you will have nothing but trouble if you use it. just download odin and cwm and superuser thats all you need to root that expensive phone.
Try the super user file located here: http://forum.xda-developers.com/showthread.php?t=1565126
I had a similar issue as you and the su in the link worked fine. If it fails keep trying, took me like 3 tries.
Sent from my SAMSUNG-SGH-I727 using xda premium
vincom said:
which cwm did u use
wich su file did u use
read this on rooting http://forum.xda-developers.com/showthread.php?t=1340526
but use this cwm http://forum.xda-developers.com/showthread.php?t=1566613
Click to expand...
Click to collapse
I used this guide: http://forum.xda-developers.com/showthread.php?t=1340526
but used the newest tar file provided on one of the rogers ics rooting threads.
As nothing is visibly wrong at this point, could I simply retry to root? Or should I wipe everything first?
So i tried to reflash again and use the new hercules file in odin.
All went well until I went into cwm recovery to make a back up, it said the it couldn't mount and aborted.
I backed up onto the SD card and it proceeded, however, when trying to load the superuser file from the external sd, it also said it couldn't mount, and aborted there.
any way around this?
Me[kk]A said:
So i tried to reflash again and use the new hercules file in odin.
All went well until I went into cwm recovery to make a back up, it said the it couldn't mount and aborted.
I backed up onto the SD card and it proceeded, however, when trying to load the superuser file from the external sd, it also said it couldn't mount, and aborted there.
any way around this?
Click to expand...
Click to collapse
dont use a touch recovery, flash a non touch recovery then install superuser. or put the superuser zip on the emm(internal sd).
popcorn900 said:
dont use a touch recovery, flash a non touch recovery then install superuser. or put the superuser zip on the emm(internal sd).
Click to expand...
Click to collapse
use this touch from tpmullan http://forum.xda-developers.com/showthread.php?t=1566613
u used this one from sk8erwitskil, u have to mount the sdcard first, but he has fixed it now(in testing) http://forum.xda-developers.com/showthread.php?t=1472954&highlight=sk8erwitskils
dont read my sig
vincom said:
use this touch from tpmullan http://forum.xda-developers.com/showthread.php?t=1566613
u used this one from sk8erwitskil, u have to mount the sdcard first, but he has fixed it now(in testing) http://forum.xda-developers.com/showthread.php?t=1472954&highlight=sk8erwitskils
dont read my sig
Click to expand...
Click to collapse
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.
Me[kk]A said:
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.
Click to expand...
Click to collapse
weird, which method did u use to flash cwm
where is backup located, int or ext sdcard, which cwm version did u make backup
what do u mean it wouldnt read superuser, maybe redownload su and check the md5, running su in cwm has to b done a few times until it states that it has completed sucessfully
edit:try to mount sdcard from within cwm in "mounts and storage/mount sdcard" also mount emmc, i never had to do that but it might b that u have to do it once
Me[kk]A said:
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.
Click to expand...
Click to collapse
well if you would just try a non touch recovery you might be surprised.
http://forum.xda-developers.com/showthread.php?t=1725221
this recovery works and this is all the help i can muster up. so now if you cant figure it out then i guess you shouldn't be flashing phones.
I have the same phone this is what I did
Flash phone with CWM use this one
Clockworkmod Touch 5.8.1.3 Odin tar http://forum.xda-developers.com/show....php?t=1566613
Then wipe data/factory reset, format- system, data and cache, and clear the partition and dalvik caches, do that to all of them 3 times each, using touch cwm.
Then odin ICS download it from here http://www.sammobile.com/firmware/
(make sure only Auto Reboot is checked nothing else)
Once the phone loads go through the setup then leave it alone, let it sit for about 20min then flash back the CWM. Then download Superuser from here and put it on the root of your SD card then flash it in CWM if it fails just keep doing it until it works, it worked the second time for me.
Once superuser is installed install busybox from the market and everything will work.
This method worked perfect for me I was having the same problem like you. The key is to wait about 20min after you flashed ICS before you do anything else.
Hope this helps you.
Well, the final superuser file worked, everything backed up perfectly.
Wanted to thank you all for you assistance. Vincom, if I knew who you were in Bolton, id buy you a beer, as I'm in your town 3 times a week.
lol Cheers everyone.
Me[kk]A said:
Well, the final superuser file worked, everything backed up perfectly.
Wanted to thank you all for you assistance. Vincom, if I knew who you were in Bolton, id buy you a beer, as I'm in your town 3 times a week.
lol Cheers everyone.
Click to expand...
Click to collapse
cool, what was the solution? bad download
vincom said:
cool, what was the solution? bad download
Click to expand...
Click to collapse
I'm not entirely sure. After not being able to back up, I grabbed an external sd, put superuser on that.
The back up went through with no problems. Also, superuser installed on the 2nd try and all went well with permissions from there.
Friend of mine had picked a zip file labelled "root" to use with Odin, and I'm suspecting the tar files I had attempted with in the past weren't correct and this file was.
Either way, I have lots more reading to do to fully understand what is available to me now. Busybox, nandroid, ROM toolbox installed.
iv flashed my phone so many times that flashing stock and rooting seem tedious to me. glad you got it rooted, now make a nand backup so you don't have to do it again.
my 32 gig sd is filled with nand dumps lol i don't even have a game on it to play.
Hey guys new here. I've done a fair amount of searching and cant really find anything that describes my problem. Trying to root my AT&T HOX and failed to put CM10 on the drive before unlocking. Now I have TWRP up right now but when I go to mount and then mount USB storage my PC says that this drive needs to be formatted to work correctly. Honestly not sure what I should do here I tried using HASOON2000's all in one kit but couldn't find the data folder for it. So I started following Cursed4Eva's video tutorial. I have already went to HTC Dev and unlocked it. When I'm in the bootloader menu it says "unlocked" "tampered". Basically Im kinda stuck right now as to what I can do to get CM10 on the one x's drive. Sorry for the super noob questions. Thanks in advance!
Okay so I formatted my drive. I'm able to get into TWRP and Bootloader screen, I get stuck in an infinite loop of the HTC screen with a disclaimer on it if I try to turn my phone on normally. Not sure where to go from here. Do I need to put CM10 in a specific folder and then "install" it from TWRP? Really sorry for the newb questions but I thought that I could handle this and apparently I cant.
Inside of TWRP, there should be a Mount menu button that will allow you to mount your phone to your computer. Simply drop the ROM zip anywhere in that directory, unmount the phone, and choose the Install option on TWRP. Select the ROM zip file and see what happens. If you get errors of "unable to mount drive" or the like, you may have to reflash the factory RUU and start over. Did that my first time trying to flash, it's a little sucky.
You can also do this from the fast boot bootloader menu with adp push.
Well I forgot upload boot.img can I just do that right now and "install" it? Will it just install CM10 and I should be good from there? Not sure what the adb push is. I have a folder with the documents, boot.img, adb, adbwinapi.dll, and fastboot.
Okay update I got CWM-SuperSU-v0.96.zip installed so I have root access. I also have TWRP installed. I dont think that I have a Kernal on my phone or if it is then its not working correctly. In my bootloader screen it says **tampared** and **unlocked**
I might need to reflash the factory RUU (I assume Factory ROM?) and try again I guess.
You should just be able to select the entire zip and install that through TWRP. I've been told that if your hboot version is 1.14, you might have to fastboot the boot.img separately. The ROM/Kernel set I used both took care of that for me via Aroma installer, but it's something to keep in mind.
Well Im far to newb for this so I will try to put my phone back to RUU and try again another day! After doing more research I found some people say that TWRP 2.3 doesnt work for the AT&T 2.20 and that you have to use 2.2 TWRP. Can anyone confirm this? Also learned quite a bit from this failed attempt. Please tell me if Im correct, Need to unlock the phone with HTCDev, upload the boot.img via fastboot, install TWRP, mount the "sdcard" flash the rest of the rom? Does this sound correct?
I'm on 2.2 using twrp 2.3.1.0. From what I've read, different roms tend to recommend different recovery apps/versions.
As for the ordering of the install process, I would install the recovery first thing after rooting because you'll need that to flash superuser. A lot of installers will actually use superuser during the installation, so you'll want to make sure that's squared away first.
Sent from my HTC One X using xda app-developers app
So you just load the rom after you have your phone unlocked and the recovery app (TWRP) and SuperSU installed?
I really appreciate the help! Thank you!
Sounds like you got it, hope everything goes well. Good luck!
Sent from my HTC One X using xda app-developers app
Ran sunshine. it ran successfully, Currently S-off, unlocked and have TWRP installed. went to flash Paranoid android it failed saying something about error in updater binary, went to reboot(I hadn't wiped yet) since it failed. now stuck at HTC screen. I can get back into recovery. but keep getting "Error: unable to mount /system" currently downloading the latest stock rooted rom and gonna flash through fastboot. But would like some input as to what the hell is going on?
It IS Lupus said:
Ran sunshine. it ran successfully, Currently S-off, unlocked and have TWRP installed. went to flash Paranoid android it failed saying something about error in updater binary, went to reboot(I hadn't wiped yet) since it failed. now stuck at HTC screen. I can get back into recovery. but keep getting "Error: unable to mount /system" currently downloading the latest stock rooted rom and gonna flash through fastboot. But would like some input as to what the hell is going on?
Click to expand...
Click to collapse
Had you updated your firmware to current version yet when you flashed the ROM?
Internal memory showing zero? Flash the partition fix zip if it is. Also you didn't mention if you flashed supersu.
Htc One M8/Vanir/Excaliber#8
So, it's not a softbrick because of Sunshine? Hmmm, do what HG suggested.
Sent from my HTC6525LVW using Tapatalk
This sounds like a similar issue I've had with both my /system and /data partitions. It's quite similar to what the encryption bug on AOSP ROM's do.
Anyways my solution for this issue...if it is afterall the same issue I have had, enter TWRP and go to > Wipe > Advanced Wipe > Repair or change file system > change file system, check what it says your file system is and then select your file system in the options below then > Repair & do that.
Or you can try repair first as changing the file system wipes whatever partition you are changing. If repair doesn't work then change should do the trick...once more that is if this is the issue I think it is (sounds like it).
Oh and this is really more of an "if you can't flash the partition fixer zip or it doesn't work for you" sort of solution, I myself couldn't get the zip to work so this did the trick for me. Still though I would try bills solution before mine and see what happens, hope you get it fixed!
+1 to OP question, i'm in the same failboat. have most updated firmware. do not know what to do.
THEnglish said:
+1 to OP question, i'm in the same failboat. have most updated firmware. do not know what to do.
Click to expand...
Click to collapse
Multiple ruu solutions exist.
resolved
Don't know what ruu solutions are, but I resolved my issue and wanted to share that it had to do with the TWRP version I was using (2.8.0.1). Updated to the latest and flashed my new ROM fine. GL OP.
THEnglish said:
Don't know what ruu solutions are, but I resolved my issue and wanted to share that it had to do with the TWRP version I was using (2.8.0.1). Updated to the latest and flashed my new ROM fine. GL OP.
Click to expand...
Click to collapse
You should learn what an ruu is to an HTC phone before you need one.