Database Info

NS4G Wont boot need help!

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

Flashing new rom

My buddy has the inspire 4g. He bought it rooted by somebody else. I've flashed cynogenmod for him aqnd several updates over the past few months. We are trying to flash new roms and its constantly aborting. Ive rooted my droids and always flash roms and never run into this problem.
He has the newest clockwork mod should we possible get a different recovery?
I don't do anything with flashing a new radio, is that necesary and whats causing the problem?
I am trying to flash core droid or revolution, he wants the best sense rom any suggestions?
I would appreciate any help. If there is no way to fix it I planned to totally reset and unroot and then root it myself and make sure everything is done right, does that sound right?

dieseldank said:
If there is no way to fix it I planned to totally reset and unroot and then root it myself and make sure everything is done right, does that sound right?
Click to expand...
Click to collapse
Though probably not necessary, the peace of mind that comes with knowing what's been done to the phone from the ground up might be worth it.
As for a fix to your current issue, please provide a little more detail as to the error.

It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip

dieseldank said:
It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip
Click to expand...
Click to collapse
Is this the same SD card for every try? It might be a flakey SD card. Try a different card if you can.

I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.

dieseldank said:
I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.
Click to expand...
Click to collapse
Radio is not usually flashed as part of the ROM. As long as you have a valid radio, it should work. If you somehow managed to get an invalid radio flashed, then you've have bigger problems that you indicate (i.e. hard bricked).
The fact that you can boot into recovery indicates that all it well with the device from that perspective. That leaves only the ROM zip to be flashed which is why I suggested trying a different SD card (since you tried several, it's not likely that you always got a bad download).
If it still messes up with a new SD card, try complete wipe, then format system from nandroid before running the update.zip. System partition doesn't get formatted during a complete wipe, but most ROMs should format it as a matter of course before installing. It's unlikely, but it could be a corrupt system partition which should clean up with a format.

dieseldank said:
I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.
Click to expand...
Click to collapse
Wanna Save yourself some time and maybe some future headaches? Like posted above It helps when you know what has been done. I would start from the ground up. Get back to a stock base and go from there, this way you are not trying to track down something you may not have done but was done before he got it.
As for your issue, If a radio is recommended then it will/should state so in the thread.

I have threads on how to root his inspire but can anyone forward a link of how to completely unroot and reset. When i reset in recovery it still keeps cynogenmod on.

dieseldank said:
I have threads on how to root his inspire but can anyone forward a link of how to completely unroot and reset. When i reset in recovery it still keeps cynogenmod on.
Click to expand...
Click to collapse
There's no good reason to go through all that trouble. If you have S-OFF, then you're good to go as far as being rooted is concerned. Since you appear to have recovery too, then you're 95% rooted no matter what the current ROM is doing.
If you have S-OFF already, then going back to stock and rerooting is just going to waste time.

dieseldank said:
It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip
Click to expand...
Click to collapse
In cwm are you trying to "apply update from sdcard" or "install zip from sdcard"
install zip is what you want.... then choose the ROM. IF you're applying update.... it's gonna abort.
You could also try reflashing recovery in Rom Manager or flashing an older version of recovery.
Sent from my time waster.

Gene Poole said:
There's no good reason to go through all that trouble. If you have S-OFF, then you're good to go as far as being rooted is concerned. Since you appear to have recovery too, then you're 95% rooted no matter what the current ROM is doing.
If you have S-OFF already, then going back to stock and rerooting is just going to waste time.
Click to expand...
Click to collapse
Since it has s-off and is rooted correctly what do you advise I do to fix my abort problem? Didn't see an answer in there, thanks.
Nickovtyme said:
In cwm are you trying to "apply update from sdcard" or "install zip from sdcard"
install zip is what you want.... then choose the ROM. IF you're applying update.... it's gonna abort.
You could also try reflashing recovery in Rom Manager or flashing an older version of recovery.
Sent from my time waster.
Click to expand...
Click to collapse
I tried both ways and its aborts both ways. And Ive reflashed recovery in rom manager, should I maybe try a different recovery?

Since you are already rooted and having trouble flashing thru rom manager, why not try flashing to stock rooted thru bootloader? It's my understanding that attn1's Ace_Cingular_US rom will automatically do a full wipe and take you to the latest stock rom and radio. If that works, then you can install the latest rom manager and flash a custom rom. It's worth a shot.
Sent from my Desire HD using Tapatalk

dieseldank said:
Since it has s-off and is rooted correctly what do you advise I do to fix my abort problem? Didn't see an answer in there, thanks.
I tried both ways and its aborts both ways. And Ive reflashed recovery in rom manager, should I maybe try a different recovery?
Click to expand...
Click to collapse
It's not gonna hurt. it sounds like the recovery is having issues with the script so it's aborting... an older recovery may resolve that issue.
But that's a good idea also... flash the lastest stock rooted ROM thru hboot. Then reflash recovery. see If that don't solve it
Sent from my time waster.

Aroma semi-bricked my phone?!

I saw that the new CleanROM was using the Aroma installer for both versions of the ROM, so I figured I'd give it a shot. I don't have any experience with Aroma, but it all seemed to be working at first. However, I guess the file may have been corrupt because it just stuck at "Installing ROM" and never finished.. I hit the next button and it said it was finished even though I never got a status update. Stuck at HTC load screen, and will NOT boot into recovery even from the bootloader.
Since I can still load the bootloader, but not recovery, I still have some hope, right?
All I should have to do is run the AT&T RUU, right?
Halp!

infamousjax said:
I saw that the new CleanROM was using the Aroma installer for both versions of the ROM, so I figured I'd give it a shot. I don't have any experience with Aroma, but it all seemed to be working at first. However, I guess the file may have been corrupt because it just stuck at "Installing ROM" and never finished.. I hit the next button and it said it was finished even though I never got a status update. Stuck at HTC load screen, and will NOT boot into recovery even from the bootloader.
Since I can still load the bootloader, but not recovery, I still have some hope, right?
All I should have to do is run the AT&T RUU, right?
Halp!
Click to expand...
Click to collapse
Relock then try the RUU

http://forum.xda-developers.com/showthread.php?t=1761429
Sent from my HTC One X

Or push twrp recovery and flash again.

Thanks for the responses -- was able to boot into recovery (CWM)... Not sure why it wouldn't work before.
Now it says it cannot mount the sdcard...
doesn't sound good.
Waiting on RUU to finish downloading, then I'll relock and try that.

infamousjax said:
Thanks for the responses -- was able to boot into recovery (CWM)... Not sure why it wouldn't work before.
Now it says it cannot mount the sdcard...
doesn't sound good.
Waiting on RUU to finish downloading, then I'll relock and try that.
Click to expand...
Click to collapse
You should not use cwm, use twrp, CleanROMs op stated that, try pushing twrp, and flashing before you ruu, it causes issues that hasn't been fixes yet.
Sent from my HTC One X

Can't use clock work. Use team win.

If everybody is saying use TWRP and the person is still using CWM; one has to wonder how intelligent that person is.

mankind 0 monkey 1

infamousjax said:
Now it says it cannot mount the sdcard...
Click to expand...
Click to collapse
This is a known issue with CWM, mount SD simply does not work. Use TWRP like everyone is saying.
Did you try wiping anything in Aroma? Because that is a known issue as well (results in soft bricks). Only wipe in recovery, and use Aroma only for picking the various ROM options (not for wiping anything).

Got it working -- used fastboot to flash TWRP and formatted SD card and now everything is lovely.
I've been flashing CleanROM since the beginning before there was TWRP and never bothered to switch recoveries. I guess I should have read the notes more closely.. oh well, no harm done
thanks for the replies and help

[Q] Problems with MD5 file trying to flash CD10 rom

I have an ATT HTC One X 2.20 Hboot 1.14 using twrp 2.4.1 and have been trying to install roms but continue to have an issue with the MD5 file. I have followed the instructions about flashing the boot.img of CM10 but it seems no matter what I do, it can't find the MD5 and says it is skipping MD5. I know just enough not to get out of a bootloop but I am quite new to this. The one odd thing I see is when I go to mount my phone in order to copy the CM10 zip file into the phone, the options I get are different than others I see online: Mount System (unchecked), Mount Data,(unchecked), Unmount Cache (checked), Unmount SD Card (checked). Any help would be awesome.

quick update; same problem
SWell, going through some of other posts and videos, I tried using goo manager to download the CM 10 zip file. But Im still stuck on boot loop. And it still says that the MD5 file was not found. I used the onexroot.com tutorial to root my phone and have superuser and twrp. Not sure what else to try. Ideas on other stable JB roms I could try? Thanks again.

In TWRP, when you install the ROM, do you have the option checked to force MD5 checked?

force check
redpoint73 said:
In TWRP, when you install the ROM, do you have the option checked to force MD5 checked?
Click to expand...
Click to collapse
I'm pretty sure I do. I have always left it unchecked. Should I check it and try again?

I've always left it unchecked (no MD5 check). If its a bad download, all that will happen is the phone will get stuck on boot, anyway.
I'd go into TWRP, and see if its checked or not. And if so, uncheck and try to flash again.

Update: No Luck
I just tried wiping system, factory reset, and cache, flashing the cm10 boot.img and then installing the CM10 zip file and checking the force MD5 and then the entire process and unchecking the force MD5 and with both attempts I get right back to the same issue. All I can say is that I'm so thankful that I created a backup in twrp. I've restored my phone at least 20 times today, haha. Learning is definitely a process. Ill take any more ideas.

Download the ROM again, may just be a bad download.

Will try
I will try to download the rom again from the CM website. If I were to try another rom (viper xl), the process should be the same correct? Thanks for the help.

alemcc said:
If I were to try another rom (viper xl), the process should be the same correct?
Click to expand...
Click to collapse
Put the ROM on your SD.
Boot into hboot, go into TWRP
In TWRP, factory reset, wipe cache, wipe Dalvik
Install ROM
Reboot
ViperXL should flash boot.img in AROMA, although its not foolproof. If the phone doesn't boot (may take about 5 min first time), then flash boot.img using fastboot.
For most ROMs, you will need to flash boot.img manually. ViperXL is one of the few exceptions (also CleanROM 5.1, I think).

Still no luck
I just tried aokp JB 4.1 with no luck. I do everything I've been told or that I have read on these forums (copy zip to SD, flash boot image, install rom...) but i continue to get the same problem: MD5 not found, skipping MD5 and so on. If anyone has any ideas I'll be happy to give any other info needed. At this point I have a rooted phone but cannot install roms. Argh!

He's not the only one. I'm on viper 3.2.3 but when trying to flash any Rom based off of AOSP or anything similar I bootloop. Yes I flash the boot.img then the Rom to no avail . I started a thread in this department called weird problem if the OP would like to take a look there.
Sent from my HTC One X using xda app-developers app

I'm new to all this, but I don't understand why certain people have this issue but most don't. Aren't all att one x phones pretty much the same?

Same thing i'm wondering
Sent from my HTC One X using xda app-developers app

you dont check any md5 checking for custom roms in twrp
you only rom i know of that you will have a md5 without anything selected is evervolv 4.2 i found a fix where you copy the CERT.SF from evervolv 4.1 to evervolv 4.2 and it will install and boot.
also always remember to "fastboot flash boot boot.img" if you are on hboot 1.14 or newer. if you going changing from sense to aosp always do full wipes no matter what. never factory reset in bootloader.

Yes I've done this countless times as I was on jellybam before going to jokers sense 4+ Rom then viper . I know the processes but something is wrong.
Sent from my HTC One X using xda app-developers app

alemcc said:
I used the onexroot.com tutorial to root my phone and have superuser and twrp.
Click to expand...
Click to collapse
I hate websites like that one. They just ripoff content from XDA, repackage it, and give little or no credit to the actual developer or XDA.
Stupid question, your bootloader is unlocked, right? In bootloader, it says UNLOCKED?
It must, for you to have TWRP. But it doesn't hurt to cover all the possibilities.

Cannot Flash Any Rom Besides CM11 (set_perm: some changes failed)

Hey guys, just looking for some help with this. For the record, I was using TWRP 2.8. Last night I tried to install NuSenseSIX from the development forum, only to have this error: set_perm: some changes failed. Thinking it was just a problem with the download, I downloaded a second copy, checked the MD5 (which was the same), flashed it, same error. I then tried flashing DigitalHigh's GPE Rom, but the same error had came up. I RUU'd the phone back to stock (credit for the RUU goes to dottat), installed TWRP, flashed:failed. Flashed CWM, Rom flash:failed (every Rom I mentioned before failed to flash). Everything had the same error, although CWM reported it as Error 7. The only Rom that installs successfully and boots is CM11, I have no clue as to why. I'm stuck, I don't know what to do. Any help would be greatly appreciated.
EDIT: Only the CM11 M10 Snapshot will flash, I just tried to flash the latest nightly (10/5/14) and it gave me "assert failed: run program("/system/bin/makelinks.sh") == 0"

RealROGWaffle said:
Hey guys, just looking for some help with this. For the record, I was using TWRP 2.8. Last night I tried to install NuSenseSIX from the development forum, only to have this error: set_perm: some changes failed. Thinking it was just a problem with the download, I downloaded a second copy, checked the MD5 (which was the same), flashed it, same error. I then tried flashing DigitalHigh's GPE Rom, but the same error had came up. I RUU'd the phone back to stock, installed TWRP, flashed:failed. Flashed CWM, Rom flash:failed (every Rom I mentioned before failed to flash). Everything had the same error, although CWM reported it as Error 7. The only Rom that installs successfully and boots is CM11, I have no clue as to why. I'm stuck, I don't know what to do. Any help would be greatly appreciated.
EDIT: Only the CM11 M10 Snapshot will flash, I just tried to flash the latest nightly (10/5/14) and it gave me "assert failed: run program("/system/bin/makelinks.sh") == 0"
Click to expand...
Click to collapse
Try doing another ruu. Then boot to hboot and chose factory reset. Make sure you do not flash twrp before doing the factory reset.

dottat said:
Try doing another ruu. Then boot to hboot and chose factory reset. Make sure you do not flash twrp before doing the factory reset.
Click to expand...
Click to collapse
Hey dottat! Sorry I forgot to give you credit for the ruu. I'll give that a shot after work tomorrow. Thanks for the reply. By the way, what does flashing TWRP before doing the factory reset do? I flashed mine without even doing that.

RealROGWaffle said:
Hey dottat! Sorry I forgot to give you credit for the ruu. I'll give that a shot after work tomorrow. Thanks for the reply. By the way, what does flashing TWRP before doing the factory reset do? I flashed mine without even doing that.
Click to expand...
Click to collapse
Factory reset using stock recovery can fix things twrp sometimes can't.

dottat said:
Factory reset using stock recovery can fix things twrp sometimes can't.
Click to expand...
Click to collapse
Alright, thanks. As I said, I'll try it tomorrow. I'll report back with new info.

By the way, what's the difference between the old ruu you made and the new one? I flashed the old one and I want to know if that might be why it didn't fix my issue.

Well... same issue after doing what you said. I'm honestly really sad right now.

RealROGWaffle said:
Well... same issue after doing what you said. I'm honestly really sad right now.
Click to expand...
Click to collapse
I have one more thing I'm going to pm you to try.