Related
Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.
*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.
spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.
There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.
gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!
I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium
I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)
I am so glad to have found this thread. This problem was beginning to drive me nuts.
I've been using TWRP ever since I have rooted mt ONE. Over the last few days its been crashing while trying to install any zips at all.I can do a nandroid restore but nothing else. When I try to install any file it just goes to a black screen and reboots the phone.
Any ideas of what could be causing this and how to repair it also.
Thanks
I've also just replaced TWRP with clockwork mod touch and that is doing the same thing. I am now at a stage where I cannot install anything via the recovery method.
What is my bet options for starting afresh as my phone is unlocked with HTC dev and rooted also.
I'd like to go back to the beginning and start again.
Thanks
potsykate said:
I've also just replaced TWRP with clockwork mod touch and that is doing the same thing. I am now at a stage where I cannot install anything via the recovery method.
What is my bet options for starting afresh as my phone is unlocked with HTC dev and rooted also.
I'd like to go back to the beginning and start again.
Thanks
Click to expand...
Click to collapse
This seems to becoming a more and more recurrent event, though I cannot say for what the correct solution is, check these two threads:
http://forum.xda-developers.com/showthread.php?t=2435499
http://forum.xda-developers.com/showthread.php?t=2423817
one of them had to fix a corrupt partition, the other just reflashed and wiped again and again, and it worked.
If something works out for you do share!!
Thanks for that,I'll redownload my favourite Rom and try again without trying to update the Kernel,everything was fine as I remember before I tried the kernel update.
I'll let you know how I get on in a while.
potsykate said:
Thanks for that,I'll redownload my favourite Rom and try again without trying to update the Kernel,everything was fine as I remember before I tried the kernel update.
I'll let you know how I get on in a while.
Click to expand...
Click to collapse
Though the reasons are still unclear (at least to me ), it seems that flashing a custom kernel while still in recovery immediately after the ROM does work. Of course, make sure you're flashing a compatible kernel to the ROM; the version numbers of the custom kernels do not correspond to the ROM versions, and I've seen some that flashed an incompatible kernel, just because the version numbers looked similar.
Good luck & keep us posted
PS: If you do solve it, please update the main thread title to include [SOLVED]. thanks
Thanks for the two links,after reading them and doing a fresh install off my rom. Wiping cache,delvick and data I seem to be able to install zips again from recovery without the black screen and reboots.
Yep, so far all the zips that failed earlier are now installing.
A BIG THANK YOU :good::good:
potsykate said:
Thanks for the two links,after reading them and doing a fresh install off my rom. Wiping cache,delvick and data I seem to be able to install zips again from recovery without the black screen and reboots.
Yep, so far all the zips that failed earlier are now installing.
A BIG THANK YOU :good::good:
Click to expand...
Click to collapse
Excellent
Edit the main thread title to include [SOLVED] so that others can refer to it :victory:
Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,
ghane0 said:
Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,
Click to expand...
Click to collapse
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.
koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.
Click to expand...
Click to collapse
It is a 901s he said non Taiwan
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
seyidaga said:
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow
Click to expand...
Click to collapse
I have downloaded the Maximus ROM. I am open to doing this, but I cannot figure out how to use the stock recovery (there seem to be no controls).
koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Click to expand...
Click to collapse
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
koniiiik said:
If it was a 901S, I'd suggest installing the stock ROM from scratch
Click to expand...
Click to collapse
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,
daorderdillon said:
It is a 901s he said non Taiwan
Click to expand...
Click to collapse
Oh, okay, I think I'm getting lost in which area has which version of the phone. Never mind then and thanks for the correction.
ghane0 said:
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,
Click to expand...
Click to collapse
Well, to install custom ROMs, you'll have to use either TWRP or CWM, I don't know about a way to do that using stock recovery.
Ok, I did this:
Installed CWM Recovery
Flashed the Stock zip from koniiiik's archive
Rebooted successfully. Lots and lots of force closes, Everything from android.core to ...
Used Rom Manager to restore a backup made a month ago
Rebooted. All OK now
Flashed Stock Recovery (again, thanks koniiiik)
Booted. Checked OTA. Got a small update (1.x)
Applied. Rebooted, Checked OTA again
Got the 4.3 package. Applied.
All is well
Between Step #3 and #4, I got my entire backlog of SMS delivered, which I lost in the next step. But that is a small price to pay.
Thanks to all of you helped,
ghane0 said:
Used Rom Manager to restore a backup made a month ago
Click to expand...
Click to collapse
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.
Backup of /system, nearly stock
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
koniiiik said:
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.
Click to expand...
Click to collapse
I have three files in the directory:
system.ext4.tar (0B)
system.ext4.tar.a (954MB)
system.ext4.tar.b (500MB)
Is the split to avoid files greater than 1GB?
Will upload starting a few hours. Dropbox will do?
ghane0 said:
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
Click to expand...
Click to collapse
Don't worry about that, of these three, only root affects /system and it should be not too difficult to revert.
ghane0 said:
Is the split to avoid files greater than 1GB?
Click to expand...
Click to collapse
Most likely – FAT filesystems, depending on inode size and other factors, only support file sizes up to a certain limit. Sometimes it's 2 GB, sometimes 4 GB, sometimes probably as little as 1 GB.
ghane0 said:
Will upload starting a few hours. Dropbox will do?
Click to expand...
Click to collapse
That would be most helpful. Thanks.
Dropbox is back up, I have sent you a link.
Thanks
Wanting to get rid of bloatware I didn't want in the first place and explore more on the Android mobile operating system I decided to make the jump towards a custom ROM and here I am. I have been impressed with my first flash of CyanogenMod 12 so far but unfortunately have run into a various amount of problem which I have tried to explore before coming here. The only problem I've sorted so far is the normal "install core Google apps without additiona bloatwarel"... But that was easy.
I have the following problems:
1. No LTE.
I'm on o2 PAYG and have entered what I think are the correct settings for use of the Internet, but unfortunately I still have no Internet capabilities beyond WiFi. When going on search for networks it will spend time before going "error while searching for networks".
2. Audio and video.
-Most noticeably on Snapchat, when I record a video the phone goes haywire and may spend 5 seconds vibrating before spending the remainder of its time being generally slow until I restart it.
-When I bring up the music playing app, I press to play a song and the audio doesn't work, nor is the song actually playing. The track bar may go to 0:01 with no sound before going back to 0:00. The device also lag once again, but not as bad as SnapChat instance. The system audio works fine as button response audio is fine and calling works fine with ringing and hearing the recipients voice.
I have gone through a couple of threads to try and find answers so far, but unsuccessful. Any help would be appreciated.
My current set-up is:
Phone: Sony Xperia SP
Android version: 5.0.2
ROM version:12-20150120-UNOFFICIAL-Ibhuashan (would be happy to change up ROM if advised so)
Kernal version: 3.4.0
I would be happy to supply additional information to help.
I'm hoping to get to know my phone and start contributing in some what possible way on the forum, but for now I just want to find my feet in this exciting new adventure
Many thanks for all help given.
kiladu said:
Wanting to get rid of bloatware I didn't want in the first place and explore more on the Android mobile operating system I decided to make the jump towards a custom ROM and here I am. I have been impressed with my first flash of CyanogenMod 12 so far but unfortunately have run into a various amount of problem which I have tried to explore before coming here. The only problem I've sorted so far is the normal "install core Google apps without additiona bloatwarel"... But that was easy.
I have the following problems:
1. No LTE.
I'm on o2 PAYG and have entered what I think are the correct settings for use of the Internet, but unfortunately I still have no Internet capabilities beyond WiFi. When going on search for networks it will spend time before going "error while searching for networks".
2. Audio and video.
-Most noticeably on Snapchat, when I record a video the phone goes haywire and may spend 5 seconds vibrating before spending the remainder of its time being generally slow until I restart it.
-When I bring up the music playing app, I press to play a song and the audio doesn't work, nor is the song actually playing. The track bar may go to 0:01 with no sound before going back to 0:00. The device also lag once again, but not as bad as SnapChat instance. The system audio works fine as button response audio is fine and calling works fine with ringing and hearing the recipients voice.
I have gone through a couple of threads to try and find answers so far, but unsuccessful. Any help would be appreciated.
My current set-up is:
Phone: Sony Xperia SP
Android version: 5.0.2
ROM version:12-20150120-UNOFFICIAL-Ibhuashan (would be happy to change up ROM if advised so)
Kernal version: 3.4.0
I would be happy to supply additional information to help.
I'm hoping to get to know my phone and start contributing in some what possible way on the forum, but for now I just want to find my feet in this exciting new adventure
Many thanks for all help given.
Click to expand...
Click to collapse
do you have UBL ...if you want a stable and with almost no bugs lollipop ROM you have to Unlock you Bootloader
flash- said:
do you have UBL ...if you want a stable and with almost no bugs lollipop ROM you have to Unlock you Bootloader
Click to expand...
Click to collapse
Hi, I had a check and retraced my steps of unlocking and rooting before I installed CM12. The device is unlocked but is not rooted any more. The rooting method via towelroot no longer works for me and ends in constant rebooting.
Hope this helps!
kiladu said:
Hi, I had a check and retraced my steps of unlocking and rooting before I installed CM12. The device is unlocked but is not rooted any more. The rooting method via towelroot no longer works for me and ends in constant rebooting.
Hope this helps!
Click to expand...
Click to collapse
For root: goto settings, about phone, klick several times (8-10) on build number, goto settings, developer options, root acces, choose apps and adb. Done.
kiladu said:
Hi, I had a check and retraced my steps of unlocking and rooting before I installed CM12. The device is unlocked but is not rooted any more. The rooting method via towelroot no longer works for me and ends in constant rebooting.
Hope this helps!
Click to expand...
Click to collapse
the device is unlocked,,, that is good ......flash t-kernel with twrp or philz from here and then flash ROM ....cm12 is too old man there is now cm12.1 and a lot of lollipop ROMs ...the one that i suggest it for you will be good
good luck:good:
flash- said:
the device is unlocked,,, that is good ......flash t-kernel with twrp or philz from here and then flash ROM ....cm12 is too old man there is now cm12.1 and a lot of lollipop ROMs ...the one that i suggest it for you will be good
good luck:good:
Click to expand...
Click to collapse
Sorry for the late reply, I had only found the time to start this today.
What benefit do I gain from changing up my kernel? Is the ROM previously mentioned alongside the kernel update only available for devices running a particular kernel?
Many thanks for all help so far!
kiladu said:
Sorry for the late reply, I had only found the time to start this today.
What benefit do I gain from changing up my kernel? Is the ROM previously mentioned alongside the kernel update only available for devices running a particular kernel?
Many thanks for all help so far!
Click to expand...
Click to collapse
the benefit is like faux sound ...you can control your cpu and gpu and a lot of things ....last update of the ROM that i gave you is only working with costume kernel (t-kernel) so yes you have yo flash ROM then t-kernel and then reboot ....if want there are like cm12.1 ...it doesn't need a costume kernel ...just flash cm12.1 and reboot......so you can choose .....happy flashing
good luck :good:
Soft-bricked the device after I wiped,attempted to install the 12.1 ROM but failed due to it saying its not the right device, and then accidentally restarted not paying too much attention to the yes and no's of CWM. Sony logo starts up but nothing else at present. Trying volume{up, down} + USB but nothing at the moment vibration or light wise. Hopefully this is fixable, not too worried at this point in time unless I should be?
Currently following this thread for instructions. Unless you can advise me on better or even if you have to tell me its straight up gone...
kiladu said:
Soft-bricked the device after I wiped,attempted to install the 12.1 ROM but failed due to it saying its not the right device, and then accidentally restarted not paying too much attention to the yes and no's of CWM. Sony logo starts up but nothing else at present. Trying volume{up, down} + USB but nothing at the moment vibration or light wise. Hopefully this is fixable, not too worried at this point in time unless I should be?
Currently following this thread for instructions. Unless you can advise me on better or even if you have to tell me its straight up gone...
Click to expand...
Click to collapse
don't be afraid ...you tried to flash cm12.1 that mean you are UBL....flash t-kernel v2.2 twrp via fastboot mode and you will gain recovery to flash again the cm12.1
Fortunately kept calm and have gotten back to having an OS present. I've currently status quo'd back to CM12.
I have PhilZ, can I just use the PhilZ instructions for t-kernal?
kiladu said:
Fortunately kept calm and have gotten back to having an OS present. I've currently status quo'd back to CM12.
I have PhilZ, can I just use the PhilZ instructions for t-kernal?
Click to expand...
Click to collapse
yes of course ! .....if you want my opinion> wait until the AICP\ RR \ROMs to be up to date ...they will update it today or tmw(very soon)
Installed t-kernel and AICP. It boots and then gets to optimizing apps. Once it completes the 82 optimizations it goes "starting apps" it reboots... should I faactory reset & wipe the caches and reinstall? Almost there haha.
kiladu said:
Installed t-kernel and AICP. It boots and then gets to optimizing apps. Once it completes the 82 optimizations it goes "starting apps" it reboots... should I faactory reset & wipe the caches and reinstall? Almost there haha.
Click to expand...
Click to collapse
do as following
,,,,please do a full wipe and then flash AICP and flash t-kernel v3.0 and then reboot
Wiped data&caches, flashed AICP then flashed 3.0 t-kernel. It reaches starting apps and completely freezes instead of rebooting now. waited 15 mins hoping it was really slow but it's frozen. I then wiped and tried to reflash but that particular recovery setting doesn't like the checksum of the t-kernal so doesn't allow installing, so i flashed back to CM11 and reflashed AICP & t-kernel, completely following the steps given.. but once again freezes at starting apps.
Any more ideas? Thank you for all effort given so far!
kiladu said:
Wiped data&caches, flashed AICP then flashed 3.0 t-kernel. It reaches starting apps and completely freezes instead of rebooting now. waited 15 mins hoping it was really slow but it's frozen. I then wiped and tried to reflash but that particular recovery setting doesn't like the checksum of the t-kernal so doesn't allow installing, so i flashed back to CM11 and reflashed AICP & t-kernel, completely following the steps given.. but once again freezes at starting apps.
Any more ideas? Thank you for all effort given so far!
Click to expand...
Click to collapse
hahaha i'm sorry man this is weird !! for sure ....please try to flash cm12.1 and see what happen ...how about that
if it boot up and you like it stay on it ....want AICP and you want to try again then reboot to recovery and re-flash like the the steps given to you
just one more thing please quote my post so i can know that you need help or something happened with you
flash- said:
hahaha i'm sorry man this is weird !! for sure ....please try to flash cm12.1 and see what happen ...how about that
if it boot up and you like it stay on it ....want AICP and you want to try again then reboot to recovery and re-flash like the the steps given to you
just one more thing please quote my post so i can know that you need help or something happened with you
Click to expand...
Click to collapse
Once again... wiped entire user + cache and first installed 12.1, then gapps core and finally t-kernel 3.0. It gets to starting apps and freezes. I'm able to flash CM11 or CM12, but that would mean the original problems encountered which makes my phone half -useless. I've tried to boot into safe mode, not knowing if you can do that with an un-optimized android.
It's all getting a little bit weird now. Something is going wrong somewhere, but I don't know.
kiladu said:
Once again... wiped entire user + cache and first installed 12.1, then gapps core and finally t-kernel 3.0. It gets to starting apps and freezes. I'm able to flash CM11 or CM12, but that would mean the original problems encountered which makes my phone half -useless. I've tried to boot into safe mode, not knowing if you can do that with an un-optimized android.
It's all getting a little bit weird now. Something is going wrong somewhere, but I don't know.
Click to expand...
Click to collapse
man would you do this and let me know....boot into recovery the wipe (data/cache/system/dalvikcache) then flash cm12.1 and reboot....don't flash any thing with it ! ...just flash it and reboot and till what happen
flash- said:
man would you do this and let me know....boot into recovery the wipe (data/cache/system/dalvikcache) then flash cm12.1 and reboot....don't flash any thing with it ! ...just flash it and reboot and till what happen
Click to expand...
Click to collapse
wiped and attempted to reflash and the installation failed. Next I connected it to my pc and went into fastboot mode and wiped data/cache/system and flashed 12.1. It boots (sign of t-kernal is gone) but has so fa yet to do anything else, the current screen is blank b ut it is on.
I hope this information was useful to you. It seems to me to more up the current ROMs I go, the more they seem broken.
flash- said:
man would you do this and let me know....boot into recovery the wipe (data/cache/system/dalvikcache) then flash cm12.1 and reboot....don't flash any thing with it ! ...just flash it and reboot and till what happen
Click to expand...
Click to collapse
retried to flash through the device and the install failed due to :
E: Cannot load volume /misc
finding update package...
Opening update package...
Verifying update package
E: Failed to verify whole-file signiture
E: signiture verification faied
Installation aborted
E: cannot load volume /misc
Click to expand...
Click to collapse
hope this helps
kiladu said:
wiped and attempted to reflash and the installation failed. Next I connected it to my pc and went into fastboot mode and wiped data/cache/system and flashed 12.1. It boots (sign of t-kernal is gone) but has so fa yet to do anything else, the current screen is blank b ut it is on.
I hope this information was useful to you. It seems to me to more up the current ROMs I go, the more they seem broken.
Click to expand...
Click to collapse
this is far from weird ....the last hope for problems like these ...to start from scratch ....to flash ftf ROM via flashtool and re install recovery then twrp then reflash the ROM (5.1) ..only few users had this problem and solved it with flashing ftf ....sorry man for that but i think you have to do it or stick with cm11 or something
good luck ...if you need any further help i'll help you :good:
---------- Post added at 10:04 PM ---------- Previous post was at 09:52 PM ----------
you use twrp last version right ?....boot into any ROM you can go to ...install rashr app and flash via rashr this twrp recovery and from that recovery flash cm12,1
i'm sorry i have to go to sleep now ...but first try to flash twrp ....etc...if that didn't help flash ftf ....
good luck mate :good: ....i will see what happened with you tomorrow
I have been experiencing certain issues w my phone and decided to do a factory reset.
Originally i was getting the TWRP loop when my celluar phone provider was trying to push an update.
Well after doing the factory reset, it went into TWRP. I"m not sure why, but that's where I am. I currently do not have an OS installed.I tried downloading a purenexus_shamu-7.1.1-20170215-OFFICIAL rom through some thread that I read, hoping to get a rom installed (excuse my terminology)
The system updated the partition, flashed itself, but still boots into TWRP.
I was at times able to get into the Pure rom? But then it had no apps. not even google play for me to use to download more apps.
Can someone pls provide a step by step of what to do to get me back up and running and disable this TWRP program permanently?
Thank you.
kaiotes said:
I have been experiencing certain issues w my phone and decided to do a factory reset.
Originally i was getting the TWRP loop when my celluar phone provider was trying to push an update.
Well after doing the factory reset, it went into TWRP. I"m not sure why, but that's where I am. I currently do not have an OS installed.I tried downloading a purenexus_shamu-7.1.1-20170215-OFFICIAL rom through some thread that I read, hoping to get a rom installed (excuse my terminology)
The system updated the partition, flashed itself, but still boots into TWRP.
I was at times able to get into the Pure rom? But then it had no apps. not even google play for me to use to download more apps.
Can someone pls provide a step by step of what to do to get me back up and running and disable this TWRP program permanently?
Thank you.
Click to expand...
Click to collapse
Well, the question is:
Honestly... Did you ever read the PureNexus thread?
Check this post for a detailed install (Google apps links in first post):
https://forum.xda-developers.com/showpost.php?p=61653759&postcount=4
If you want to start fresh, just flash a factory image of your choice (I advise the latest)
Follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Backup your datas first...
Don't flash userdata partition if your phone is not a 32GB model...
Also, don't mess with your phone unless you read enough and know what you are doing otherwise you could break it for good...
i was able to install it and get the gapps running
the problem is it didnt fix anything
i still cant really work the dialup unless it is via bluetooth. (am forced to reboot to be able to use the phone during a call)
my front facing camera still does not work.
5.1 said:
Well, the question is:
Honestly... Did you ever read the PureNexus thread?
Check this post for a detailed install (Google apps links in first post):
https://forum.xda-developers.com/showpost.php?p=61653759&postcount=4
If you want to start fresh, just flash a factory image of your choice (I advise the latest)
Follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Backup your datas first...
Don't flash userdata partition if your phone is not a 32GB model...
Also, don't mess with your phone unless you read enough and know what you are doing otherwise you could break it for good...
Click to expand...
Click to collapse
Hi... I'm currently using PureNexus myself and never encountered such problems... I guess you'll have to report your issues in the PureNexus thread with proper logs...
5.1 said:
Hi... I'm currently using PureNexus myself and never encountered such problems... I guess you'll have to report your issues in the PureNexus thread with proper logs...
Click to expand...
Click to collapse
Follow the guide posted above to get it back to stock. There shouldn't be a calling issue on that rom. Must be something janky during the flash process. Just get back your phone e to stock and see if everything works.
kaiotes said:
I have been experiencing certain issues w my phone and decided to do a factory reset.
Originally i was getting the TWRP loop when my celluar phone provider was trying to push an update.
Well after doing the factory reset, it went into TWRP. I"m not sure why, but that's where I am. I currently do not have an OS installed.I tried downloading a purenexus_shamu-7.1.1-20170215-OFFICIAL rom through some thread that I read, hoping to get a rom installed (excuse my terminology)
The system updated the partition, flashed itself, but still boots into TWRP.
I was at times able to get into the Pure rom? But then it had no apps. not even google play for me to use to download more apps.
Can someone pls provide a step by step of what to do to get me back up and running and disable this TWRP program permanently?
Thank you.
Click to expand...
Click to collapse
Ya forgot your gapps...
Please read more... Flash less... Don't be a dummy... It's expensive... And it's supposed to be a phone