Hello, I have a problem after S-OFF my One S, describing a problem:
I decide to s-off my one s, I'm on stock rom jb witch newest hboot, do everything like in tutorial, supercid etc. and finely got S-OFF :good:
On stock is no problem everything works fine. I want to flash custom rom (device is S-OFF status unlocked, rooted, supersu working fine, with flashed newest TWRP). I turn on TWRP chose instal zip and it starting and after 2 second stopped with failed operation. I tried for rom thickdroid and viper checked md5 and file is OK. After failed flashing the phone cannot start, helps flashing stock ruu jb from .exe file and it flash without any problem and then work but if I try ones more the problem is still happen. Any idea what is happen ??? thanks for any idea and helps
Use older version of TWRP or use latest CWM recovery instead - TWRP version 2.4.3.0 does not work well, not sure about 2.4.4.0.
you've got a right, on CWM everything working and I can flash rom
Related
Can someone suggest a decent s ON rom for this phone ????Im unlocked but it seems all the roms are for s-off THANKS
Any ROM, listed for ur device (ville-S4 or villeC2-S3) can be flashed even if you have S-ON.
With S-ON, after installing your ROM from your phone custom recovery (TWRP or CWM), you will have to manually flash the 'boot.img' file within your ROM zip from a PC. Guides are available for that.
With S-OFF, installing the ROM takes care of the boot.img file as well; no PC needed.
That's the only difference as far as I know.
Hi... im currently running
CROMi-X v5.2.2, which is based on rom 10.6.1.27.5 with twrp 2.5.0.0 and my bootloader says is the one that came with us10.6.1.15.3-20130416...
To install omni kitkat, im been asked to have the latest bootloader, to avoid screwing up im planning on insalling the latest stock from asus...
However, each time i install a stock through twrp or cwr, the new image not only updates the bootloader and deletes all my data, but rewrites my recovery, for which then i have too reupload using fastboot to upload the recovery...
Is there any way to make sure i dont loose the recovery after flashing a stock firmware... or a way to flash the recovery from the recovery before rebooting after flashing the stock?
Thanks everyone!
mertonv said:
Hi... im currently running
CROMi-X v5.2.2, which is based on rom 10.6.1.27.5 with twrp 2.5.0.0 and my bootloader says is the one that came with us10.6.1.15.3-20130416...
To install omni kitkat, im been asked to have the latest bootloader, to avoid screwing up im planning on insalling the latest stock from asus...
However, each time i install a stock through twrp or cwr, the new image not only updates the bootloader and deletes all my data, but rewrites my recovery, for which then i have too reupload using fastboot to upload the recovery...
Is there any way to make sure i dont loose the recovery after flashing a stock firmware... or a way to flash the recovery from the recovery before rebooting after flashing the stock?
Thanks everyone!
Click to expand...
Click to collapse
Flashing the stock ROM reverts the tablet back to stock, so the recovery must go. Luckily, the bootloader you are on is compatible with the KitKat recovery (10.6.1.15.3) so you shouldnt have to flash the stock ROM at all. If you were on 10.6.1.8, you would have had to upgrade.
cmendonc2 said:
Flashing the stock ROM reverts the tablet back to stock, so the recovery must go. Luckily, the bootloader you are on is compatible with the KitKat recovery (10.6.1.15.3) so you shouldnt have to flash the stock ROM at all. If you were on 10.6.1.8, you would have had to upgrade.
Click to expand...
Click to collapse
Thanks, then guess i only need to flash the kitkat twrp...
Asked the same question about my bootloader at the omni thread to be sure, if they say that it works too, will go ahead and give it a try
I'm not being able to flash recent roms. I keep getting error status 7. For JB 4.2 and later, I can't flash them. I can flash rom 4.1.2 and earlier.
I'm on 3.18 firmware (latest i think). unlocked and rooted. BUT I have S-ON, is that the problem? If I S-Off. will I be able to flash recent roms? I want kitkat on my phone Sorry im noob
What recovery version are you using?
Sent from my Evita
2.5.0.0 i think, ye. that's it. but I tried with both CWM and TWRP, non work. I suppose S-off is the problem right?
Your recovery is the problem. If you want to flash KitKat ROMs you need the modified TWRP 2.6.3.0 by jrior001, you'll find that in our Original Android Development section. Any other ROM you want the official TWRP 2.6 which you'll find here:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita
Ok, this is weird, a while ago i didnt had any problems installing any kind of custom rom, used CWM while wiping everything... eveything was OK, ROM worked OK, etc... But one time i installed a ROM (Slimkat) and i lost signal, tried to use my recovery of stock android but it didnt work, so i tried a lot of things untill i got bootlop without being able to install anything since some files were missing, bad luck
After that, i just reflash stock 4.3 and upgrade from there 4.4.2, everything fine again... except that i cant install any kind of ROM, every ROM says "installation succesful" but everyone is stuck into bootloop.
While i havent tried ALL ROMS i have tried the same ones i was using (Nexus G+, LiquidSmooth and CM11), so i guess this problem is coming from my device.
On a side note, i tried to factory reset, but no luck... it shows the Android working but it inmediately turns the screen off, and then it shows it again and then off again... in an infinite loop
Same problem!
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Liberr said:
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Click to expand...
Click to collapse
Hmmm... Pay attention to which version of Bootloader you are using.
You might want to try both 4.3 and 4.4 to see which one would work.
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Good luck!
neozen21 said:
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Liberr said:
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Click to expand...
Click to collapse
Hmmm.. I see there is a version number on mine, 41.05 dated 2013-12-06, but I'm not sure if that's the version or not.
And yeah... if changing the bootloader doesn't help, you probably would have to restore from the stock image and start over..
Got root and custom roms working after I 1.) downgraded to 4.3 and 2.) flash TWRP (instead of CWM).
So I'm not sure what the problem was. Besides the two main rooting methods (superboot and custom recovery), there are some other methods described on the forum specifically for people who already did a international variant OTA to 4.4.2. and one that is absolete (here) but apparently works for some when the two main methods fail.
However I'm still not sure if this solved everything. I am not sure if I can flash Cyanogenmod (which is 4.4.2) over a 4.3 firmware. Maybe I need to manually flash a 4.4.2 radio or something... Gonna check that out next...
EDIT: No need to downgrade. Not sure how it works but two main root methods (superboot and custom recovery) didn't work for me. Somehow I got stuck in boot animation. Just installed TWRP instead of CWM after Kitkat firmware (EU Retail) and rooted (/installed Super Su) from there. Everything works fine now.
Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?
muqy said:
Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?
Click to expand...
Click to collapse
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.
chairsz said:
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.
Click to expand...
Click to collapse
Hey man, worked a charm thanks!
For users who may have the same problem:
After flashing 4.3 onto the device it did NOT boot.
- However I then went into the bootloader flashed custom recovery, I used cwm.
- Then I went into recovery, used adb to push the rom and gapps onto sdcard
- Full wipe and then installed rom. Then installed gapps
Working fine.
Cheers chairsz :good::good: