Amaze 4g T-mo
Android 4.0.4
Build: Speed Rom 8.0 by ElclipseRemix
Kernel: 3.0.16-ga4fb38c [email protected]#1
S-OFF
Rooted
I have a "rooted" Amaze with 4EXT recovery- I cannot install a new rom, recovery or check for root as it always says root is not there.
I don't know what else to say except it was rooted, now it's not. I've tried to RE-root to no avail. What would you guys/gals recommend?
So why can't you install a new Rom when you're running a dom and have 4ext recovery? Just download and flash it.
jowofoto said:
I have a "rooted" Amaze with 4EXT recovery- I cannot install a new rom, recovery or check for root as it always says root is not there
Click to expand...
Click to collapse
Well, you don't need root to flash a new Rom or recovery so that shouldn't be a problem.
I actually had the same thing happen the other day, running a different setup (NRG with Faux kernel, when suddenly I lost root. What you can try doing is just reflashing the same you are running, without wiping data, just try wiping cache and dalvik, and then flash it right over the top of your current Rom. Reboot and see if its fixed. If not, do a full wipe, then flash whatever Rom u want
sent from my
NRGized amaze
powered by Faux
Try updating the Su binaries or update busybox..??
Related
so, I've had my SG2 for like a month now, rooted and all, but the problem is , i can't flash any other ROMs(but stock ROMs) or kernels (except for CF root,stock and siyah kernels ) on it via CMW... each time i tried to flash anything, i end up stuck at "galaxy s2 GT-I9100" boot-up logo.... I've tried flashing CM7 then i got the boot-loop ( even with double flash, or triple didn't work for me) and i can't get into CWM when i got the boot-loop....
someone please help me.. i read alotta threads and none of them got similar issue like mine...
i guess its true what they say : every galaxy s2 is different from the rest.
Hmm....must be something you're doing wrong. Nothing to do with Galaxy S2 being different.
Have you always followed the dev's instructions while flashing roms?
Wiping data, cache? Matching up the kernels and roms?
As far as I know, there hasn't been a single person who completely failed to install VillainROM on their SGS2.
I would advise you to give it a go.
Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
tomascunill said:
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
Click to expand...
Click to collapse
If your phone has cf-root/kernal and cf cwm can you just flash over top codeworkx's kernel and do you have to re-root?
InFa_ReD_1 said:
If your phone has cf-root/kernal and cf cwm can you just flash over top codeworkx's kernel and do you have to re-root?
Click to expand...
Click to collapse
If you already have root then you won't loose it.
geko95gek said:
Hmm....must be something you're doing wrong. Nothing to do with Galaxy S2 being different.
Have you always followed the dev's instructions while flashing roms?
Wiping data, cache? Matching up the kernels and roms?
As far as I know, there hasn't been a single person who completely failed to install VillainROM on their SGS2.
I would advise you to give it a go.
Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
Click to expand...
Click to collapse
I used to use VR 3.0 but could only work with stock kernel or cf root kernel has never booted with the ROM's kernel..
tomascunill said:
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
Click to expand...
Click to collapse
My phone came with CM7, but i flashed it with rooted stock coz i wanted to have a feel of it... but now i'm done with it but i can't get any roms to work... so frustrating.
i literally have tried flashing ALL Roms (ligtnung, gingerbread,vr, cm7), during the 1st few days that i got my phone it worked with VR 2.5 and 3.0, even MIUI.. but after i flashed with some Asian stock ROM via odin... nothing would work through cmw anymore...
i seriously don't know what i did wrong...
btw, right now im using basebad ver: I9100XXXKI4, kernel: 2.6.35.7-siyah [email protected]#20, build number GINGERBREAD.ZSKI3.
I really don't know. YOu should try to go the closest possible to stock and try from there. DO a full wipe, wipe data, wipe system, everything and flash a stock ROM from your country and carrier (there is a thread from infratech where you can get carrier specific ROMS). THen connect your phone to kies (maybe yo get an oficial update) and then do everything from scratch, root, install CWM, etc...
That's what I'd do but I really don't now if it's the best option.
i have almost the same problem,but me i can flash any rom,but the problem is with the kernel my phone refuse to boot on any other kernel else than cf-root and the speedmod,it freezes in the kernel loading so i must turn it off and reflash via odin cf-root or speedmod to get it works again.
tomascunill said:
I really don't know. YOu should try to go the closest possible to stock and try from there. DO a full wipe, wipe data, wipe system, everything and flash a stock ROM from your country and carrier (there is a thread from infratech where you can get carrier specific ROMS). THen connect your phone to kies (maybe yo get an oficial update) and then do everything from scratch, root, install CWM, etc...
That's what I'd do but I really don't now if it's the best option.
Click to expand...
Click to collapse
well, i'm gonna try that and see if it works, am also goin' try to see if downgrading to 2.3.4 or something would work too...
but please if you got any more ideas, just keep it coming..
thanks
Phew! NOW I HAVE CM7 RUNNING ON MY PHONE!!
I'm gonna try to explain how i fixed my issue, as clear and explanatory as i can..
lucky i didn't brick my phone during all this, because I tried so many things and none worked.I unsuccessfully tried downgrading to XWkI4, ZCKI4, and alot others via Odin... after flashing all i get is tons of error messages(on 3e recorvery) E: can't open/cache or E:failed blah bla bla to load /efs... i thought OMG! my phone is bricked! then i recalled reading somewhere that flashing the 3 tar (PDA,MODEM,CSC) files usually should work(maybe better than flashing a 1 tar file), so i found a 3 files xxKI3 rom, flashed it and BAM! it booted up this time without any error. so now i went ahead and rooted it since the tar files came unrooted, then went into CWM to flash cm7 ROM, flashed it twice and ofc i got stuck on boot logo.....i didn't panic much, i pulled out the battery, and restarted to CWM where i cleared cache/ dalvik/ and did wipe/factory reset, then i reflashed CM7 again (twice) and it worked!!!! YES, CM7 is fiannly working on my SG2!
thanks for everyone for helping, and i hope this can help others on the same boat as me..
Hi, I'm a new to rooting, but long time jailbreaker, and man this is way harder than I thought!
I think I'm on the right track, I've uploaded Rom (Super Nexus 3.0 i9100 ect), CWM-SuperSU v0.97 and Google apps (gapps-jb-20130813 ect)
But, I've unfortunately had a couple of failed attempts, originally coming from 4.1.2, I'm now back to 'stock' 4.0.3 and can't update, so I'm going to try again.
So I wanted to know, using Odin, is 6.0.2.9 the latest version of ClockwordMod and/or for the Galaxy S II (if it matters?) I've already got it on there, but I've also got a Siyah on there too, so just want to do another flash to a CWM.
And yes, no quarms about completely wiping the phone, I've backed up all the music, pics, call logs, ect, so just want to learn how to root to the latest version of android, and this version looks great.
Mm it's really not harder than you thought. You're over complicating things.
2 current options :
Have you flashed & are currently running siyah? If so, then boot into recovery and flash supernexus & gapps. Done.
Not currently running siyah? Flash siyah via Odin in download mode. Reboot then into recovery and flash your rom and gapps. Simple. Rooted and new rom.
As far as using CWM on its own (ie just flashing the recovery) it'll only be temporary. Every reboot it will reset to stock recovery. Hence why you need to flash siyah to keep the permanent recovery & be able to flash a new rom.
Sent from a galaxy far, far away
Hopper8 said:
Mm it's really not harder than you thought. You're over complicating things.
2 current options :
Have you flashed & are currently running siyah? If so, then boot into recovery and flash supernexus & gapps. Done.
Not currently running siyah? Flash siyah via Odin in download mode. Reboot then into recovery and flash your rom and gapps. Simple. Rooted and new rom.
As far as using CWM on its own (ie just flashing the recovery) it'll only be temporary. Every reboot it will reset to stock recovery. Hence why you need to flash siyah to keep the permanent recovery & be able to flash a new rom.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Thanks Hopper,
I decided to use CWM 6.0.2.9 (so now there are three kernals, 2 CWMs and 1 Siyah, wish I knew how to clear them out).
First time I tried to use Super Nexus 3.0, it looked ok, but wouldn't reboot, but then I just re-installed eveything again (both times CWM), and now I've rebooted twice no problems? I think I read somewhere that it had to be done twice, I have no idea why that would be.
Oh yeah, but now I need to get Swype back on there, forgot it was a Samsung exclusive, I'll see how I go from the Google Play, but I'm guessing I could get a custom .apk from the internet anyway.
My phone is EVO 4g lte, s-on Hboot 2.09 radio 1.13.11.0830 with twrp 2.7.1 rooted and unlocked. I flashed cyanogenmod 10.2 and flashed kernel using adb. I cannot get Gapps to install at all, it says it flashed correctly in twerp, when I reboot the apps are not there. what am I doing wrong?
Try doing a full wipe, install the ROM and kernel, then reboot the phone. Once the OS loads, reboot to recovery and flash the Gapps. Then reboot again and see if they're there. I also suggest installing a stock rooted ROM and gaining S-off in the near future.
hey everyone.i have a att m8.s-off unlocked rooted.i was running twrp 2.8.01 i think.dirty unicorns for the rom.i was getting ready to flash viper.so i went to recovery to flash just started wiping stuff did the fist wipe cant remember the name of what it was.it wasnt something i wasnt suppost to just one of the normal wipes it did it then the phone rebooted.i think because i started the wioe process the rom wouldnt boot.so i tried to go back and finish everthing.about 30 seconds into recovery the phone tries to reboot.i tried flashin g recovery though fastboot it said it worked but recovery is unusable any help is appreciated.thanks.
Did you try to flash recovery again?
If it dosent work try flashing the RUU and then flash the viperone rom
Ya I flashed recovery it took but recovery just keeps rebooting phone.which ruu should I try.im a little confused with those.thanks for the help.
jhzzer said:
Ya I flashed recovery it took but recovery just keeps rebooting phone.which ruu should I try.im a little confused with those.thanks for the help.
Click to expand...
Click to collapse
4.4.3 is the RUU you'd want to use. Not causing the problem, but are you trying to use 3.2.1 or 2.5.0 viper?
Viper 3.2.1 is there a problem with that version.the problem was my sd card when I pluggedit into computer to load up firmware the computer ask me to format it.when I plugged it back into phone I went to recovery and it worked.thanks for all your help.
jhzzer said:
Viper 3.2.1 is there a problem with that version.the problem was my sd card when I pluggedit into computer to load up firmware the computer ask me to format it.when I plugged it back into phone I went to recovery and it worked.thanks for all your help.
Click to expand...
Click to collapse
You can only run 3.2.1 if you're on build 3.28.401.9 which hasn't been released for AT&T yet. Latest AT&T build is 2.23.502.3 which can only be used with Viper 2.5.0. Flashing Viper 3.2.1 while not on the correct build will cause your WiFi to stop working and probably a few other bugs. You can either flash Viper 2.5.0 or you can flash the 3.28.401.9 International build and run 3.2.1 and Viper will update you to 4.4.4. So you can use the RUU to get back to 4.4.3 (build 2.23.502.3) and run Viper 2.5.0 and wait for the officials AT&T update for 4.4.4 (build 3.28.401.9) or you can flash the International build (3.28.401.9) and run Viper 3.2.1. If you decided to update and want to flash International here is a guide to do it http://venomroms.com/viperonem8_3-0-0-requirements/
I wasn't aware 3.28.401.9 was international that's the one I flashed when it came out.but for whatever reason my sd card was causing recovery not to work right.I'm running viper 3.2.1 now.everything seems to be working good.I only changed Roms because du isn't supporting lollipop when it comes out so I'm trying different ones.
fastboot erase cache and install recovery with fastboot again.
Than restore nandroid. Didn't make one, why the heck not?
If that is the case, flash a known good ROM. adb push the ROM to the phone, or put it on SD with a USB card reader connected to your computer.
The above steps will get you out of a no boot situation from bad recovery or bad flash 99% of the time.
---------- Post added at 11:52 AM ---------- Previous post was at 11:48 AM ----------
jhzzer said:
so i went to recovery to flash just started wiping stuff did the fist wipe cant remember the name of what it was.it wasnt something i wasnt suppost to just one of the normal wipes
Click to expand...
Click to collapse
There is only one default wipe in TWRP (data, Dalvik and Cache). It says "most the time this is the only wipe that you need" and it means what it says. If you picked to go into Advanced (again, its labelled that way for a reason) you better know what you are doing and make sure before you confirm the wipes.
I'M confused as to why I can't flash older roms.. I have a Sprint Htc one Max with the latest Stock Rom and Hboot. I have root access and Twrp recovery installed with S-On.. Whenever i go to install an older rom the recovery just reboots... Any help would be greatly appreciated!
Stevesteve64 said:
I'M confused as to why I can't flash older roms.. I have a Sprint Htc one Max with the latest Stock Rom and Hboot. I have root access and Twrp recovery installed with S-On.. Whenever i go to install an older rom the recovery just reboots... Any help would be greatly appreciated!
Click to expand...
Click to collapse
Have you tried using a older recovery?
I've tried once, and it was it was like Twrp 2.7 something.... So everything I'm doing is right, as far as my phone being rooted, Bootloader unlocked etc.... You think it's the recovery?
Stevesteve64 said:
I've tried once, and it was it was like Twrp 2.7 something.... So everything I'm doing is right, as far as my phone being rooted, Bootloader unlocked etc.... You think it's the recovery?
Click to expand...
Click to collapse
Could be the installer script doesn't like the new recovery. What rom?