Hello.
First of all, I tried searching for a similar problem but I haven't found anything quite like this.
I have a SG S3 with a stock 4.3 Rom (but I was on cyanogenmod 11 before that).
And I wanted to try Android Revolution (ARHD), so I added CWM and downloaded ARHD 51.0 from here. I then proceed to install it via the SD card in recovery mode (after wipe) like it's recommended. The installation goes on, the phone restarts. And I'm back to my stock rom (rooted mind you), like I did not even try installing ARHD.
My current version is I9300XXUGNA8, I guess I should be on I9300XXUGNB6 after install, but there's absolutely no change whatsoever. I tried this 3-4 times with always the same results.
Has anyone ever had this problem? Do you know why I can't seem to install this ROM?
Many thanks in advance for any help on this!
Related
Hi everyone.. first post here.
I just successfully rooted my Nexus S (GT-I9020T, 2.3.4, GRJ22) using adb, recovery clockwork herring and su 2.3.6.1.
ROM Manager is working fine but I do have a couple of issues.
The recovery doesn't always stick and reverts back to the stock one from time to time (I have to flash again then from inside ROM Manager). Which could be a problem due to the next issue..
I've been trying to install some ROMs (Cynogen for instance) but in one version I get a looping boot screen and in an other it keeps going to the recovery screen. Luckily, it's the right one and I can restore a backup. I'm afraid it might revert to the stock recovery at some point and screw me.
Any thoughts on this?
I should have read some more threads first..
I fixed the recovery issue by renaming install-recover.sh using Root Explorer
So I guess I should just experiment to find good ROMs now.
Can anyone suggest a good ROM? I'm looking for improved battery use, slimmed down system, needs email apps (all google apps probably)
Sorted it all out (mount/unmount, delete caches, etc.)
It's working swimmingly now.
Running Cynogenmod 7 and loving it.
I am using Infinity 1.0.0, stable, fast and great battery life, it is a 2.3.4 rom
installed new rom from rom manager and now i get a continual android.process.media. i had cyanogen mod 7.0.0 stable. installed the old rom to no avail. i have tried various roms and nothing. where is the error?
Firstly don't use rom manager, you are much better off booting in recovery and flashing manually. Rom manager has been known in some cases to cause issues
Secondly make sure you wipe system/data/cache when moving from one rom to another.
Thirdly if doing neither of the above helps, re download the rom. You may have got a bad download.
HEY NOOB, WATCH THIS
OHH, BOOBIES
Ok guys I have been at this for over 5 hours now and I'm turning to you for help. I have had the phone since its release and have done research on rooting. I used ace hack v11a to root and s-off about 5 hours ago. After this, I had the well known issue with wifi (connecting to network, but no internet access). I searched and found the thread detailing the fix, which was to use rom manager to flash cyanogenmod 7. I used rom manager to create a backup and then set it to task installing the rom. Rom manager sent me to the load screen and acted like it was installing. The phone booted up, but it was still the downgraded rom. I have tried several things, including booting the phone into recovery and flashing the rom manually. I have received the status 7 error message, and also noticed rom manager saying something about sd-ext not being found. I have searched the forum and found the fixes i mentioned that worked for others, but I am having a problem. I am currently using ace to restore the phone to its original state and will wait for some help before I try this again. Any help would be greatly appreciated.
razorbackinspire said:
Ok guys I have been at this for over 5 hours now and I'm turning to you for help. I have had the phone since its release and have done research on rooting. I used ace hack v11a to root and s-off about 5 hours ago. After this, I had the well known issue with wifi (connecting to network, but no internet access). I searched and found the thread detailing the fix, which was to use rom manager to flash cyanogenmod 7. I used rom manager to create a backup and then set it to task installing the rom. Rom manager sent me to the load screen and acted like it was installing. The phone booted up, but it was still the downgraded rom. I have tried several things, including booting the phone into recovery and flashing the rom manually. I have received the status 7 error message, and also noticed rom manager saying something about sd-ext not being found. I have searched the forum and found the fixes i mentioned that worked for others, but I am having a problem. I am currently using ace to restore the phone to its original state and will wait for some help before I try this again. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Alright, SD-EXT won't be found unless you have created an EXT partition on your SD card, I get that error with every wipe. Are you using the newest ROM manager? Are you using the newest CWM? Have you tried just flashing a radio/ RIL?
I'm just spittballing here, based on common solutions.
Also don't flash through ROM manager, as there is a bug, and will not do a full wipe. When ever you flash a rom/theme/mod do it through Clock Work Mod.
Ok. I will not try to flash through rom manager. A couple of questions:
1) I ran the return to stock option on ace v11a. When I do this again should I use v11b?
2) Is partitioning absolutely necessary?
3)Is there a particular radio you recommend?
Thanks for your reply!
razorbackinspire said:
Ok. I will not try to flash through rom manager. A couple of questions:
1) I ran the return to stock option on ace v11a. When I do this again should I use v11b?
2) Is partitioning absolutely necessary?
3)Is there a particular radio you recommend?
Thanks for your reply!
Click to expand...
Click to collapse
1)probably dosent matter much
2)not unless you want to put apps on your sd card witch i wouldnt recommend unless you have a large sd card
3)it completely varies from where you live o go check out the inspire only radio thread and try some out
Hey guys,
My phone keeps rebooting and says that I have blank SD card after I installed new roms. At first I thought the rom caused it but then when I installed a different rom even stock rom, the problem is still there. Is it because of a bad root?
Thanks
Hmm no that doesnt seems like a root problem.
1.- What ROM you installed when it all started?
2.- Did you installed a new Modem, Kernel or another kind of mod? Some ROMS are only compatible with 1 kernel e.g MIUI
3.-You tried this:
http://forum.xda-developers.com/showthread.php?t=1116251&highlight=stock
or
http://forum.xda-developers.com/showthread.php?t=1092021&highlight=stock
And still got problems?
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.