Hi, guys.
I'm new in this world of ROMs, kernels, etc, and I have a pair of questions (at the moment ) I flashed atis112's kernel on my Desire X and after that I flashed SkyDragon v1.0, and then v1.2.
Just after I flashed SkyDragon v1.2, I noticed the v2.0 update via OTA Updater, so I downloaded via PC and flashed v2.0 on my DX.
At first I have no problem with the ROM, but then some apps like Link2SD failed to obtain root permission, so I opened SuperSU and it asked to update Binaries (by normal update or CWM/TWRP recovery). Both of them failed.
What can I do?
P.S.: sorry about my english
AW: [Q] Problem with SuperSU on SkyDragon V.2.0
I had the same thing. I tried again and again and at some point it worked. Maybe try another SU app?
JoseluSpark said:
Hi, guys.
I'm new in this world of ROMs, kernels, etc, and I have a pair of questions (at the moment ) I flashed atis112's kernel on my Desire X and after that I flashed SkyDragon v1.0, and then v1.2.
Just after I flashed SkyDragon v1.2, I noticed the v2.0 update via OTA Updater, so I downloaded via PC and flashed v2.0 on my DX.
At first I have no problem with the ROM, but then some apps like Link2SD failed to obtain root permission, so I opened SuperSU and it asked to update Binaries (by normal update or CWM/TWRP recovery). Both of them failed.
What can I do?
P.S.: sorry about my english
Click to expand...
Click to collapse
Maybe ur system is still write protected.
neXus PRIME said:
Maybe ur system is still write protected.
Click to expand...
Click to collapse
You mean still S-ON? Or is kernel's stuff?
Just got some issues with superuser and checked in on this thread to see if same problem, which it doesn't seem like it is, if you update your Desire X to jellybean or maybe something to do with Skydragon rom and its jelly bean support (i don't know) then try this link https://plus.google.com/115635783790203857600/posts/bB6RypGD8QQ
JoseluSpark said:
You mean still S-ON? Or is kernel's stuff?
Click to expand...
Click to collapse
It's the kernel stuff and also need a correctly configured su binary in a ROM to have a perfect SuperSU.
There's only one kernel with the hTC write protection disabled. The rest you need a special module for it to work.
You have to do the TWRP option twice in a row, the first time it just reboots to recovery and the second time the recovery installs the binary and reboots back to system.
Have done this twice on a 2.0 clean flash.
Related
Hi there,
I downloaded the latest MIUI ROM available in the Development sectionand installed when i was on ICS, but it only booted and the BOOT.iMG was not flashed by fastboot because the hboot version was not sufficient for the MIUI jelly bean ROM. My phone was rooted earlier and i was running Sense Revolution 5 but after it was degrading i decided on installing your ROM.
Now, after long hours I updated the stock version via the OTA so the hboot version has now increased. But the problem now I am facing is that after flashing your ROM [After doing a factory reset which consists of Wiping cache,data and dalvik cache] and flashing the boot.img separately is that my Desire X is booting into stock jelly bean ROM even though i have wiped everything. I have tried this thing like for 2-3 times and my bootloader shows UNLOCKED. The phone starts like it has come from factory. Also during 3rd time i noticed that I got a message that Xiaomi Framework has closed. There are some apps of MIUI installed like Weather and gallery etc out of which few work and few don't. I did not get any kind of errors while installing your ROM as well. I have verified the md5 as well but it is not working.
also when I boot into bootloader, i get a green message
SD CARD CHECKING
PM66diag.zip no or wrong image
something like that.
Could you guys please help me out for this one?
Regards,
Pranav
Blueelvis_RoXXX said:
Hi there,
I downloaded the latest MIUI ROM available in the Development sectionand installed when i was on ICS, but it only booted and the BOOT.iMG was not flashed by fastboot because the hboot version was not sufficient for the MIUI jelly bean ROM. My phone was rooted earlier and i was running Sense Revolution 5 but after it was degrading i decided on installing your ROM.
Now, after long hours I updated the stock version via the OTA so the hboot version has now increased. But the problem now I am facing is that after flashing your ROM [After doing a factory reset which consists of Wiping cache,data and dalvik cache] and flashing the boot.img separately is that my Desire X is booting into stock jelly bean ROM even though i have wiped everything. I have tried this thing like for 2-3 times and my bootloader shows UNLOCKED. The phone starts like it has come from factory. Also during 3rd time i noticed that I got a message that Xiaomi Framework has closed. There are some apps of MIUI installed like Weather and gallery etc out of which few work and few don't. I did not get any kind of errors while installing your ROM as well. I have verified the md5 as well but it is not working.
also when I boot into bootloader, i get a green message
SD CARD CHECKING
PM66diag.zip no or wrong image
something like that.
Could you guys please help me out for this one?
Regards,
Pranav
Click to expand...
Click to collapse
Install a recovery meant for the JB hboot
GtrCraft said:
Install a recovery meant for the JB hboot
Click to expand...
Click to collapse
Thanks a lot dude. I tried the beta recovery from TWRP and it got flashed finally
Thanks and sorry for being such a noob.
Hello ,
since two days i am trying to install a custom rom on my htc desire x. I repeated every single step several times to make sure everything still is fine.
(unlook, flash boot, flash recovery / tried twmp and cwm, etc..)
The only rom which works for me ist the cM10-2-20138004-unofficial. But with restrictions. WLAN doesn't work, media manager isn't starting. Cant hear the partner when calls are incoming.
I tried mySense, Half_Sense, myOnedx, but after finishing installation the device hangs on startup. I waited hours and minutes but nothing happened.
I tried several RUU´s but can't find the right ones for me, or i got the 155 error message.
There is no OS installed on the device. How can i get the device up an running? I would be really happy if somebody can give me a hint whats going wrong.
Thx in advance
Dont worry all ****s can be fixed.Wha is ur hboot ? Or simply before to try to install custom rom U was with ICS rom or JB ?.You have to use the right recovery.Look what rom you want to flash, if you on ics hboot u cant just flash jb room (Some roms already have this funcion)
Ps:
After flasing the rom go in boothloader and flash boot.img And away do full wipe
What you need to make sure when installing a ROM: Install a suitable kernel. When installing a Sense ROM, install a Sense custom kernel or the stock kernel. Installing CM isn't advisable, because it's not ready for daily use yet. Also, make sure you use the right recovery for right hboot.
Good Morning,
thx for reply. I want to install the myOnedx_RC4.0 FX. I extracted the boot.img from zip. Installed the rom, wiped, reboot and installed the boot.img.
But that failed. Again, the cyanogen start up occurs for hours and hours. The device doesnt start.
Also tried the same wir the mySENSEdx5_RC4
I evem tried to install the nexuskernelv3.img
I am on hboot 1.25.002
Anyone an idea what wrong with my installation?
Thx
Again: Which custom recovery are you using? Please post a link to the thread here, so we can see what you've installed. Also, as first time user, you should check this and this.
Sorry i forgot. I am using TWRP 2.6.3.0 as custom recovery
Ok, strange, as this one works for me without problems. However, try the 2.5.0.0 version for JB and see if it goes without problems then. Also be sure to wipe system, dalvik cache, cache and data partition before installing a new ROM.
Same with version 2.5.0.0. I tried clockworkmod recovery, but as soon as i try to wip i got the error messages:
cant mount cache/recovery
cant open cache/revocery
So how can i get back to a stock rom? I tried the way described in here: http://forum.xda-developers.com/showthread.php?p=41327224
, but restore failed.
Any other ideas?
If you want to get back to stock, you need to know your CID first. After that, check this thread: http://forum.xda-developers.com/showthread.php?t=2324815
As you have JB hboot, you need to restore a JB backup. In the thread I linked you to are backups of several CIDs. If yours isn't there, you won't be able to return to stock.
Ok thanks. So it is not in there. I got the cid VODAP102.
Does that mean my device is gone? Or can i even try other workarounds?
Thanks
So i installed odexed rom and this one works fine. Do not know why all the other roms not working to me.
Maybe anyone an idea.
Otherwise thanks for your support.
Lastmenstanding said:
Does that mean my device is gone? Or can i even try other workarounds?
Thanks
Click to expand...
Click to collapse
Your hboot : 1.25.0002
Recovery to flash - JB recovery download from here : http://d-h.st/VjM
fastboot flash recovery command : fastboot flash recovery recovery.img
For a test ROM to flash, flash this stock ROM : http://forum.xda-developers.com/showthread.php?t=2239511
also make sure to fastboot flash boot boot.img
(boot.img is attached on OP)
Once everything run, it is up to you to try any other ROM and any other boot.img
Lastmenstanding said:
So i installed odexed rom and this one works fine. Do not know why all the other roms not working to me.
Maybe anyone an idea.
Otherwise thanks for your support.
Click to expand...
Click to collapse
It's either you flash ROM with wrong recovery type or wrong boot.img type or ROM which is not supported on your hboot.
Simple rules:
1) Recovery must be a recovery for JB.
2) Correct boot.img for correct ROM
ICS ROM that support hboot 1.25.0002
Recovery : JB recovery is a must
Boot.img : ICS boot.img is a must
JB ROM which should run fine on hboot 1.25.0002
Recovery : JB recovery is a must
Boot.img : JB boot.img is a must
ICS ROM that does not support hboot 1.25.002 - you need to manually change the mountpoint in updater-script, then
Recovery : JB recovery is a must
Boot.img : ICS boot.img is a must
Yeah, that was the problem, I see now... Have been blind a bit... The ROMs OP has installed on his phone are all ICS ROMs which need changing of updater-script mountpoints. That's why they won't work. @Lastmenstanding: Try any JB ROM available in Android Development section, should work without problems. The ROMs you tried were ICS ROMs especially written for ICS hboot, that's why they didn't work on your phone.
dansou901 said:
Yeah, that was the problem, I see now... Have been blind a bit... The ROMs OP has installed on his phone are all ICS ROMs which need changing of updater-script mountpoints. That's why they won't work. @Lastmenstanding: Try any JB ROM available in Android Development section, should work without problems. The ROMs you tried were ICS ROMs especially written for ICS hboot, that's why they didn't work on your phone.
Click to expand...
Click to collapse
OP mentioned about installing my ICS ROMs. Both ICS ROMs work on JB hboot without a need to edit the updater-script. My guess is he either use wrong recovery (ICS recovery is wrong) or wrong boot.img (JB boot.img is wrong) as it should be JB Recovery and ICS boot.img
..do not know how to use the thank meter, but..
Thank you guys for your excellent support.
Lastmenstanding said:
..do not know how to use the thank meter, but..
Thank you guys for your excellent support.
Click to expand...
Click to collapse
Just thank them at the bottom of their posts...
There is a thanks button at the bottom of every post.
Hi guys!
I finally unlocked my l9. Finally! And I flashed artas's cm11 for L9. It looks cool and works fine but i have one problem.
After flashing the rom and gaps i flashed SuperSU like in case of rooting stock (stupid me) and in system i have no root access on SuperSU.
Do i have to install other apps for it? Or I just have to reflash the whole rom and do not flash supersu? Plz Help me I am queit a noobster when it comes to custom rom's (this the first i've ever done)
With a rom with root, simply install SuperSu from the Playstore. If there's already a superuser app present, the zip install may break something, I would flash rom and Gapps anew, then go to the store.
Yea reflashed coz of another bug in the rom (the search pannel breaks the launcher) so it works now without the superSU. Thx for help
I have an HTC One M8 with ROM 4.16.1540.8 (5.0.1)
I'm trying to remove my SuperSU app so that i can downgrade it to a lower version(2.20) due to incompatibility with some of my apps (puzzle and dragons).
Bootloader is unlocked and it is s-on.
I have tried removing SuperSU through the app itself by using the reinstall, switch superuser app, and full unroot functions, but everytime I restarted the phone superSU would be back and in version 2.46. I also tried manually deleting the apk and su files in the bin and xbin folders in system using es file explorer but a restart just brought those back too.
Any help would be greatly appreciated. Thanks!
Find the flashable zip for the "older" version and flash in recovery. I would think that should do it.
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
ah46657 said:
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
Click to expand...
Click to collapse
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
how to unflash supersu zip
redpoint73 said:
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
Click to expand...
Click to collapse
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
rajkumar1221 said:
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
Click to expand...
Click to collapse
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
redpoint73 said:
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
Click to expand...
Click to collapse
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
rajkumar1221 said:
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
Click to expand...
Click to collapse
I don't personally use Lineage. I believe you will need to flash both of those, yes.
@redpoint73 , found this script made by osm0sis to "unSU". not sure if is relevant to earlier posts but thought maybe if you havent seen it yet would be worth looking at. maybe could help someone.?
http://forum.xda-developers.com/showthread.php?p=63615067
Hi,
I'm not allowed to post in the developer forum.
I tried to install the dark sense 1.2.2 kernel on the latest stock rom. The phone booted normal and it did not take a long time to boot. However the camera has a weird reddish tint... (maybe wrong installation).
Is it possible to use the dark sense kernel on the latest stock rom?
Phone info:
Latest stock 20170112 (rooted)
recovery: TWRP 3.0.2-8
Kind regards
Hexyl said:
Hi,
I'm not allowed to post in the developer forum.
I tried to install the dark sense 1.2.2 kernel on the latest stock rom. The phone booted normal and it did not take a long time to boot. However the camera has a weird reddish tint... (maybe wrong installation).
Is it possible to use the dark sense kernel on the latest stock rom?
Phone info:
Latest stock 20170112 (rooted)
recovery: TWRP 3.0.2-8
Kind regards
Click to expand...
Click to collapse
How did you install TWRP in that ROM? For me it's impossible
Fran Montero said:
How did you install TWRP in that ROM? For me it's impossible
Click to expand...
Click to collapse
See this forum:
https://forum.xda-developers.com/el...nofficial-twrp-elephone-p9000-t3426678/page14
post #133
Post from floydart:
I installed the 20170112 then TWRP 3.0.2.8 then flashed SU and successfully rooted. Decided to go back to CM13 FV3 though as I couldn't get Gravity Box to work
I followed the exact same steps as posted in that URL. First stock rom (and booted in stock rom). Then flashed only TWRP 3.0.2-8 with flashtools and then SU.
Hexyl said:
See this forum:
https://forum.xda-developers.com/el...nofficial-twrp-elephone-p9000-t3426678/page14
post #133
Post from floydart:
I installed the 20170112 then TWRP 3.0.2.8 then flashed SU and successfully rooted. Decided to go back to CM13 FV3 though as I couldn't get Gravity Box to work
I followed the exact same steps as posted in that URL. First stock rom (and booted in stock rom). Then flashed only TWRP 3.0.2-8 with flashtools and then SU.
Click to expand...
Click to collapse
Did the same but for me didn't work when flashing TWRP, Windows 10 show a preloader error
Fran Montero said:
Did the same but for me didn't work when flashing TWRP, Windows 10 show a preloader error
Click to expand...
Click to collapse
Weird, I also use Windows 10. Have no errors
Does the new stock rom have a different lk and preloader than the previous stock rom?
Fast charge (PE+) does not work properly in the latest stock ROM (I think). Charging takes almost 110 minutes. In other ROMs with custom kernels, charging takes about 1 hour (Started from 5%).