Develop Bugs

[Q] Reporting Issues with installation of Jelly Sandwich ROM 6.0 / 6.1

Hi
I am really thankful for the all the developers involved in the development of Jelly sandwich ROM (latest release), which is one of the most awesome custom ROM (I believe).
However, I've personally tried to install the ROM but failed several times, as my arc just gets stuck at SONY LOGO
I have also tried browsing different threads on this forum to locate a similar issue however could not find one stating the above issues with ROM installation. I am very sure there is something that I missing or failing to do right, therefore seek some help from the right team,
Unfortunately there is no list / screenshot made available by the developers to help understand the best option to select in the AROMA installer.
I am creating this thread here assuming some helping hand would be provided with the above issue.
Thank you.
Sony Ericsson Xperia Arc - Stock kernel (.587) .. Stock ICS 4.0.4 rom

I wanted to install the new 6.1 jelly sandwich. Followed instructions for people coming from older JB - just update via CWM but after doomkernel logo screen goes, and remains black.
Then i wiped everything and tried to install as I would be coming from other rom - the same result.
Then i went for the "if something goes wrong" option, again with the same result.
Now im restoring my previous 5.0 JS hoping it will work normally
Anyone else having similar issues?
Im running Lt15i on doomkernel, jelly sandwich 5.0 from maxio1998
thread: http://forum.xda-developers.com/showthread.php?t=1836993

Same problem here with JS, Remix and Pureness. Tried each one several time.
Every time get stuck on Sony logo and then I have to restart the long process for restoring 587 with root.
I carefully followed procedure for each ROM.
--------What I did before---------------------------
Rooted with this method : http://forum.xda-developers.com/showthread.php?t=1683957
Bootloader unlocked with s1tool and testpoint: http://forum.xda-developers.com/showthread.php?t=1551494&highlight=bootloader
... SimUnlocked with purchase code from cellunlocker (Rogers phone).
Was never able to boot in fastboot (tried a lot!!! no blue light except when cwm is installed with flashtool), so no custom kernel
And in Service info it says Bootloader unlock allowed : no (flashtool says its already unlock when I try to do it)
I'm discouraged

Jelly Sandwich
I had exactly the same issue as well. I was on locked bootloader. Tried several times. Got fed up trying because everytime i would flash the rom, CWM would get wiped off. So i decided to unlock the bootloader, root and flash kernel and rom. And VOILA! Success! But......The only issue im facing is that the Data network doesn't seem to be working. But i think its a kernel issue, not rom related. If anyone can help with my issue there then that would be great. Other than that the rom works Great!
RedWolff said:
Same problem here with JS, Remix and Pureness. Tried each one several time.
Every time get stuck on Sony logo and then I have to restart the long process for restoring 587 with root.
I carefully followed procedure for each ROM.
--------What I did before---------------------------
Rooted with this method : http://forum.xda-developers.com/showthread.php?t=1683957
Bootloader unlocked with s1tool and testpoint: http://forum.xda-developers.com/showthread.php?t=1551494&highlight=bootloader
... SimUnlocked with purchase code from cellunlocker (Rogers phone).
Was never able to boot in fastboot (tried a lot!!! no blue light except when cwm is installed with flashtool), so no custom kernel
And in Service info it says Bootloader unlock allowed : no (flashtool says its already unlock when I try to do it)
I'm discouraged
Click to expand...
Click to collapse

mastermjr2004 said:
I had exactly the same issue as well. I was on locked bootloader. Tried several times. Got fed up trying because everytime i would flash the rom, CWM would get wiped off. So i decided to unlock the bootloader, root and flash kernel and rom. And VOILA! Success! But......The only issue im facing is that the Data network doesn't seem to be working. But i think its a kernel issue, not rom related. If anyone can help with my issue there then that would be great. Other than that the rom works Great!
Click to expand...
Click to collapse
Looks like I will have to unlock my bootloader after hearing your story

I think mount system and even format system solved the exact same issue you are having thou I'm now back to GB because of the extra ram it can offer and more games support without fc.

My phone sometimes crashes, how can I rule out a software issue?

Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks

I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
marcusabu said:
Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks
Click to expand...
Click to collapse

ahsanali.pk said:
I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
Click to expand...
Click to collapse
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.

marcusabu said:
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.
Click to expand...
Click to collapse
ok, if you want to get the total old look, relock the bootloader, and install official GNex image that comes straight from Google. Hope this sorts the issue out.
Yes, Custom ROMs are a bit time taking to setup in the start, but thats the whole point - a lot of options. I flashed alot of ROMs and luckily, I have had no boot issue still. I think following the proper instructions(which are simply wiping and formatting data, cache, and dalvik) are easily gonna keep the boot loops away.

You can rule out a sw issue by starting fresh.
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my i9250

[Q] Recovery gone and no LED's while Booting (Urgent!)

Hi,
i've been using and updating CM12 for quite some time. I had some problems a few weeks ago, where i had to reflash the whole device (soft bricked it, because i didn't notice i flashed TWRP and Kernel for Z1), but since then, i've been using CyanDelta to update about every 5-6 times and then doing one full update with the whole CM12 Zip...maybe it's superstition, but it worked perfectly...until now.
Today i wanted to update to the newest CM12 Nightly, but i noticed that my recovery is gone completely - even the LED's wont light up while booting. It just goes straight from the Sony Logo to the CM12 Bootscreen. There isn't even the "new" CWM based CM12 Recovery...
I've used TWRP most of the time, so i turned off the Recovery-Update in the CM12 Developer Settings
Flashing TWRP over Rashr into the FOTA-Partition also doesn't work - can i just flash it via fastboot? Or will i brick the device with that?
David

Flash again clock world mod With nut page

Nut Page? I've no clue, what you are talking about. Also: Flashing CWM with Flashr or something else doesn't work...

david320te said:
Nut Page? I've no clue, what you are talking about.
Click to expand...
Click to collapse
http://nut.xperia-files.com/

Flash "TWRP_multirom-amami_20150201-00.img" from this thread. It's working for me.
http://forum.xda-developers.com/showpost.php?p=58243315&postcount=2

Hi,
somehow i have flashed a wrong kernel before, that probably had no FOTA-Partition. I've flashed the kexec compatible kernel and had recovery (and the LED's ) back. Now my System-UI force closes, but i can manage with that^^
But that Multiboot thing was the right track...! Thanks
Maybe this would be nice to know for others?

Cant seem to get viper4android to work

I learned about viper4android and that is what made me start this crusade. I literally spend all of yesterday researching and learning how to root and troubleshooting viper4android and I still can't seem to get it to work.
I rooted my phone and flashed the latest version of TWRP, and installed superSU as well. I initially had a lot of trouble getting the busybox drivers to install but I finally managed to get the latest version installed. The app busybox on rails verifies that the current version of the busybox drivers are installed.
I tried different methods of installing viper4android and I don't have any luck with any. I get the app installed but once I launch the app it asks me which drives I to install, I try to install the super quality drivers but the drivers will not install. I've done a lot of googling of what the problems could be but the "fixes" people suggest dont work. The latest thing I tried was installing SELinux and changing the mode to permissive before trying to install the the drivers but the drivers will still not install.
Any ideas on what to try next? I've granted all these apps permanent permission through superSU. The other thing I've been wanting to do is to remove all the ATT bloatware, but even the app I got for that called "uninstall" will not uninstall all the bloatware which makes me wonder if something is incorrect. However in the bootloader it says my phone is "modified" and "unlocked".
Any help would be appriciated, and I should also mention I have lolipop 5.0.2.

Your problem is the stock kernel. It has write protection enabled.
You need a custom kernel where the write protection is disabled.
Try ElementalX for a start : http://forum.xda-developers.com/showthread.php?t=2705613
or any Sense based kernel.

ckpv5 said:
Your problem is the stock kernel. It has write protection enabled.
You need a custom kernel where the write protection is disabled.
Try ElementalX for a start : http://forum.xda-developers.com/showthread.php?t=2705613
or any Sense based kernel.
Click to expand...
Click to collapse
Do I need to install skydragon before installing elementx? Or will installing elementX sense 5.0.2 version be ok?
Edit: I read on a blog that you need to install skydragon first, but I saw no mention of it in the official elemtnx thread so I ended up installing elementx and it worked by I kept getting hung on the HTC logo on boot, I did a reset and it fixed it with the eleX kernel running. viper works no but it looks like I've lost data. lol. Always something. Now it's time to figure this out.

Sep1911 said:
Do I need to install skydragon before installing elementx? Or will installing elementX sense 5.0.2 version be ok?
Edit: I read on a blog that you need to install skydragon first, but I saw no mention of it in the official elemtnx thread so I ended up installing elementx and it worked by I kept getting hung on the HTC logo on boot, I did a reset and it fixed it with the eleX kernel running. viper works no but it looks like I've lost data. lol. Always something. Now it's time to figure this out.
Click to expand...
Click to collapse
Did I mentioned any ROM ? I said and talked about ElementalX kernel only and your problem has nothing to do with ROM. I didn't ask what ROM that you have, right ? Because you already mentioned it has lollipop 5.0.2

ckpv5 said:
Did I mentioned any ROM ? I said and talked about ElementalX kernel only and your problem has nothing to do with ROM. I didn't ask what ROM that you have, right ? Because you already mentioned it has lollipop 5.0.2
Click to expand...
Click to collapse
Like I said in my edit it's something I read online. I am new to this stuff and at the time I thought you would need a new ROM in order to install a kernel. I was trying to research what I need to do so I dont go in screwing something up and there was a how to blog that specifically mentioned you need a new ROM inorder to install the element X kernel. But that turned out do be flawed information. Anyways I've since read a lot about ROMs, kernels and what not and now have a better understanding of what each piece of the puzzle does.
Anyways, the phone has been kind of unreliable. I had previously used the phone since it's launch before rooting it. I figured it might not be a bad idea to clean everything out hoping that would solve some of the problems. I relocked the phone and did an RUU. I then rooted the phone again and installed elementX. I cant send or receive multimedia texts, GPS does not work at all, and data works on and off. If I reboot the phone chrome will load any page but then after a few mins it stops and sometimes it will load certain websites and at other times it wont load anything at all. I am having good reception of course. Could elementX be the culprit here?

Sep1911 said:
Anyways, the phone has been kind of unreliable. I had previously used the phone since it's launch before rooting it. I figured it might not be a bad idea to clean everything out hoping that would solve some of the problems. I relocked the phone and did an RUU. I then rooted the phone again and installed elementX. I cant send or receive multimedia texts, GPS does not work at all, and data works on and off. If I reboot the phone chrome will load any page but then after a few mins it stops and sometimes it will load certain websites and at other times it wont load anything at all. I am having good reception of course. Could elementX be the culprit here?
Click to expand...
Click to collapse
I searched info on AT&T with ElementalX .. what I've found they worked.
So not sure why it didn't work for you. You tried ElementalX-m8-4.05-Sense, right ?
Your first post was asking about Viper4Android, you need a custom kernel with write protection disabled for it to work.
You can RUU it back and try different kernel and see how it goes.
BTW ... what's the RUU version no. ? 4.28.502.2 ?

ckpv5 said:
I searched info on AT&T with ElementalX .. what I've found they worked.
So not sure why it didn't work for you. You tried ElementalX-m8-4.05-Sense, right ?
Your first post was asking about Viper4Android, you need a custom kernel with write protection disabled for it to work.
You can RUU it back and try different kernel and see how it goes.
BTW ... what's the RUU version no. ? 4.28.502.2 ?
Click to expand...
Click to collapse
Yeah I was initially trying to get V4A to work, and flashing elemental X allowed me to resolve my problems with that, but now I'm having phone functionality problems. And yes, that is the RUU number that I used on my phone. Any kernels you recommend ? Also, as far as reliability and avoiding problems goes do I need to revert back to stock kernel everytime before flashing a new kernel or would clearing the caches and flashing a new kernel over another custom kernel suffice?

Can't help much on Kernel as I don't use custom Kernel.
You need to try some of them and find out which work best for your device.
Maybe asking in AT&T sub-forum will get you better respond.
The main point here is you need write protection disabled kernel to have that viper4android running and also to remove some bloatware that you want to get rid off.

ckpv5 said:
Can't help much on Kernel as I don't use custom Kernel.
You need to try some of them and find out which work best for your device.
Maybe asking in AT&T sub-forum will get you better respond.
The main point here is you need write protection disabled kernel to have that viper4android running and also to remove some bloatware that you want to get rid off.
Click to expand...
Click to collapse
Sorry for digging old thread but i have face the same situation like in the OP . My m8 has root access and ElementEX kernel installed but when i try to install viper4android it was asking to reinstall drivers again again . can you help me to figure this out ??????

I have finally found a method to get the Viper4Android working on HTC M8 (6.0)
1. Download viper4android apk from this Link - http://vipersaudio.com/blog/?page_id=48 (credit - zhuhang ) and install
2.Flash this zip in recovery Link - http://forum.xda-developers.com/showpost.php?p=64855827&postcount=5675 ( credit - Flar2)
3.Install drivers and reboot
4.Go to the system/etc and find the .conf file called "htc_audio_effects.conf" rename it to the "htc_audio_effects.bak" (this made file inactive but keep a backup in case something went wrong ) (Use Solid explorer or Root explorer for this )
4.Restart your device
5.Voila !! Now you have working Viper4Android
My Device Info
ROM - stock sense ( marshmallow)
Kernel - ElementX 7.0.0.11
Bootloader status - Unlocked (btw S-ON)

[bricked device] OP3 shows yellow screen

Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?

Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.

Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
EDIT: I see that Puddi Puddin beat me to it.

Puddi_Puddin said:
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.
Click to expand...
Click to collapse
tnsmani said:
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
Click to expand...
Click to collapse
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
tnsmani said:
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
Click to expand...
Click to collapse
I am using the newest (twrp-3.1.1-2-oneplus3.img) but the problem is that I can't see anything in recovery or elsewhere :/

Peybro said:
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
Click to expand...
Click to collapse
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence

Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post

Puddi_Puddin said:
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence
Click to expand...
Click to collapse
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
Renosh said:
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post
Click to expand...
Click to collapse
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on

Peybro said:
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on
Click to expand...
Click to collapse
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.

tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
I can give it a try later (and in the future when everything works again) but I do not think (at least I can't imagine) that the problem I have comes from recovery.

I know the reason!
I found other people who also had a static screen and they said they could fix it by pressing the screen back on its contacts...
I did so and it worked!... A bit... For a few minutes...
So the static definitely wasn't the result of rooting and stuff but the repair company's fault.
I hope they accept their mistake and fix it. Thx for everyone here trying to hel me!
P.S.
tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
And as soon as I can I will try this TWRP
-------------------------------- Edit: --------------------------------
(Just in case people get same problem)
[after Mega Unbrick Method 2 finally worked (I put the stock zip in the tool's folder)]
This morning I restarted the phone just because and I could see what was going on on the phone - but the display was still crazy with yellow tint and colorful stripes etc.). After setup it asked me to download & install newest stock rom; I did and after reboot everything was fine again....
Don't know what happened here but it seems to work again.