I am getting an infinite loop on the android screen after I set up the 4.5 build and reboot.
Basically it lets me install the build, set it up, but when the phone restarts, it gets stuck on the android screen.
The android animation doesn't even cycle, the word android and the little android bot come up, but instead of flashing, it just freezes, then about 10 seconds later it disappears and then comes back again doing the same thing.
I did a search on the forums and everyone's solution to this kind of thing was to format their sd card because of apps, but I don't put my apps on my sd card.. in fact all I have on the sd card right now is update.zip.
I adb shell'd in and then rebooted it into recovery, did a wipe, but then it did the same thing. I then tried the 4.9 build but after restart I still got the infinite loop.
Does anyone have ANY idea on how to fix it? Thanks.
EDIT: I am not using the apps-to-sd build, I am just using the regular one (with camera fix)
Please do this for me:
Code:
adb shell logcat -d V > output.txt
and either upload output.txt somewhere, or copy its contents EXACTLY to www.pastebin.com and post the URL.
EDIT: also check the md5 sum of the file you are updating with.
http://pastebin.com/f39e42873
MD5 sum is good.
Hope this helps.
Payne IV said:
http://pastebin.com/f39e42873
MD5 sum is good.
Hope this helps.
Click to expand...
Click to collapse
hmm.. this doesn't seem to show any signs of crashing..
did you do this while you were in the loop?
My bad, here is the output during the loop:
http://pastebin.com/f60bd35af
Code:
error opening /system/recovery.img: No such file or directory
Does this have anything to do with it?
Code:
E/dalvikvm( 66): Unknown type '
I/DEBUG ( 64): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 64): Build fingerprint: 'tmobile/kila/dream/trout:1.1/PLAT-RC33/126986:user/ota-rel-keys,release-keys'
I/DEBUG ( 64): pid: 66, tid: 76 >>> system_server <<<
I/DEBUG ( 64): signal 11 (SIGSEGV), fault addr 00000000
the new build.prop seems to be causing a crash on you...
hmm... you can play with it by doing:
Code:
adb pull /system/build.prop build.prop
change what you'd like then
Code:
adb push build.prop /system/build.prop
Thanks but honestly I don't even know where to start. I'm probably just going to have to revert back to JF RC33
nevermind, redundant answer
I think you didn't wipe your phone before trying to flash the new haykuro's ROM. I have tried this too and my phone was looping like yours. When i do the WIPE (alt +w), then reflash the ROM again, everything goes to normal and my phone do normal boot. Hope this will help you.
I did wipe, I even said that in the first post. I tried flashing again today to 4.5 and still had the same problem.
Related
Here's the thread for tech details. No questions in this thread, please.
My input:
Rooting the Rogers Dream
Download the tools required
Extract to anywhere on your computer.
Place update.zip on the root of your sd card.
Reboot the device into SPL (power off, hold camera button, boot, press "back" or "send" [check prompt on device] to enter "FASTBOOT" instead of "HBOOT")
Code:
fastboot boot recovery.img
Apply update, wait until phone idles, press HOME+BACK, it will reboot, finish writing hboot, then reboot again into recovery by itself. Do not interrupt it at all until it's done.
HOME+BACK to reboot into regular device.
Power off, hold camera, boot, go back into FASTBOOT
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash boot boot.img
Code:
fastboot reboot
that's it!
Rooting the HTC Magic / Sapphire: http://android-dls.com/wiki/index.php?title=Magic_Rooting
Developer notes (for devs and rom builders):
Dev's (cyanogen, i'm looking at you [you requested this info ]) you can download my hacked up mkbootimg and some other tools here: http://www.mediafire.com/?njl4x5ozldm
these are all baked up by me in a flurry of rush and etc, so excuse the sloppiness
You will have 2 tools to use now, compileboot and compilebootmagic.
compileboot creates a regular g1 boot img (and the vodafone magic as well supports these old boot locations)
compilebootmagic has 2 options.
compilebootmagic -1 will create an image supported by the HTC Dream (rogers), all new magic devices, and most likely the hero and etc (these new locations are based on ram size pretty much)
compilebootmagic -2 will create an image with user supplied arguments (it says dream but disregard it, i made it before finding out the new codes matched -1)
Discovering new boot locations!
This is a fun (and easy) bit.
Just grab a boot.img from the device you'd like to learn about, and follow the chart below:
Code:
0xf-0xc (backwards): kernel addr
0x17-0x14 (backwards): ramdisk addr
0x1f-0x1c (backwards): second addr
0x23-0x20 (backwards): tags addr
you can also use this script (linux users):
Code:
#!/usr/bin/php
<?php
function bootloc($file) {
$handle = fopen($file, 'rb');
$data = stream_get_contents($handle);
fclose($handle);
$text = "";
for($a = 0; $a < 8; $a++) {
$text .= $data[$a];
}
if($text == "ANDROID!") {
$out = sprintf("Kernel addr : 0x%02x%02x%02x%02x", ord($data[hexdec('f')]), ord($data[hexdec('e')]), ord($data[hexdec('d')]), ord($data[hexdec('c')]))."\n";
$out .= sprintf("Ramdisk addr: 0x%02x%02x%02x%02x", ord($data[hexdec('17')]), ord($data[hexdec('16')]), ord($data[hexdec('15')]), ord($data[hexdec('14')]))."\n";
$out .= sprintf("Second addr : 0x%02x%02x%02x%02x", ord($data[hexdec('1f')]), ord($data[hexdec('1e')]), ord($data[hexdec('1d')]), ord($data[hexdec('1c')]))."\n";
$out .= sprintf("tags addr : 0x%02x%02x%02x%02x", ord($data[hexdec('23')]), ord($data[hexdec('22')]), ord($data[hexdec('21')]), ord($data[hexdec('20')]))."\n";
return $out;
} else {
return false;
}
}
if($argc < 2) {
echo "Usage:\n";
echo $argv[0]." <img file/s>\n";
echo "example:\n";
echo $argv[0]." boot.img boot-new.img recovery.img recovery-new.img\n";
} else {
for($a = 1; $a < $argc; $a++) {
$out = bootloc($argv[$a]);
if($out) {
echo $argv[$a],":\n";
echo $out;
} else {
echo $argv[$a]," is not a boot/recovery img!\n";
}
}
}
usage: bootlocations.php <boot.img, more than one can be supplied>
example: bootlocations.php boot.img boot-new.img
NOTE: i will try to keep adding to this until it's full. any information that isn't in here, feel free to request via pm.
Reserved for future postings
Once again, great work Haykuro
Okay, I see the trickery now.
Thanks for this info, I'll build a version of CM for Rogers later
Another thing.. Does this device use the same libhtc_ril.so as the G1 ROM and/or does it need different RIL properties in build.prop? I am thinking it does because of the different radio, but I've only seen G1 "ports" of the ROM.
cyanogen said:
Another thing.. Does this device use the same libhtc_ril.so as the G1 ROM and/or does it need different RIL properties in build.prop? I am thinking it does because of the different radio, but I've only seen G1 "ports" of the ROM.
Click to expand...
Click to collapse
lol the g1 ports of the rom never changed the lib much (if not at all [do an md5sum ;P])
the phone is practically identical to ours, aside some physical things (crystals, etc)
thx for the tools
cheers
Thanks again Haykuro! This is great information.
thank you for this! Hopefully intructions on how to root the mytouch will come soon!
Tried to make a version of CM-3.6 for the Rogers Dream and it isn't booting according to the testers.. Doesn't even get adbd started.
I set the boot.img up properly.
Code:
Kernel addr : 0x19208000
Ramdisk addr: 0x1a200000
Second addr : 0x1a100000
tags addr : 0x19200100
Something else has to be different, or that device hates my kernel.
EDIT:
Haykuro sent me the kernel config from a running Dream device, and there are some options enabled in it that aren't part of any Linux kernel.
CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1=y
CONFIG_CPU_FREQ_GOV_MSM7K=y
So we are going to need whatever they patched in to be able to build custom kernels. Interestingly, the device is also using cpufreq settings of 384MHz/528MHz by default.
Great job haykuro, but ive been hearing reports that you cannot flash any rom (only rogers based roms) Any news on this? Thanks again!
I commend your turn around, Steve, and am quite impressed.
cyanogen said:
EDIT:
Haykuro sent me the kernel config from a running Dream device, and there are some options enabled in it that aren't part of any Linux kernel.
CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1=y
CONFIG_CPU_FREQ_GOV_MSM7K=y
So we are going to need whatever they patched in to be able to build custom kernels. Interestingly, the device is also using cpufreq settings of 384MHz/528MHz by default.
Click to expand...
Click to collapse
That is my stumbling block too. It's not just those two options, config diff is quite significant. I've sent a couple of emails to htc kernel devs a few weeks ago, but got no response. HTC must release the patched source, though, to comply with GPL2. I'm not sure what's be the best way to persuade them to.
Can't ender code in SPL
Once I boot into SPL how do I enter the code. nothing happens when I press the keys on my keyboard.
stongest said:
Once I boot into SPL how do I enter the code. nothing happens when I press the keys on my keyboard.
Click to expand...
Click to collapse
Wow this was pretty dead and you just revived it from its slumber among the dead.
Theres no code to enter
You have to install once you get a custom rec.
Ace42 said:
Wow this was pretty dead and you just revived it from its slumber among the dead.
Theres no code to enter
You have to install once you get a custom rec.
Click to expand...
Click to collapse
At least he searched for it
stongest said:
Once I boot into SPL how do I enter the code. nothing happens when I press the keys on my keyboard.
Click to expand...
Click to collapse
through adb
ok.. I am getting closer to understanding this!
But, still no luck.
I downloaded this file
http://sapphire-port-dream.googlecode.com/files/spl-signed.zip
then saved it to my SD card and renamed it to update.zip
Then I do this
Reboot the device into SPL (power off, hold camera button, boot, press "back" or "send" [check prompt on device] to enter "FASTBOOT" instead of "HBOOT")
and nothing happens.. any ideas?
You install .zip things like that, like the SPL and new roms in the recovery mode, not bootloader. You'll start up with home + power to get to that.
However, given that you don't know this yet, I'd spend a *lot* more time getting comfortable with the whole flashing roms/messing with your phone stuff before installing that SPL, that's a pretty good way to brick your phone if you don't know a bit more about what you're doing.
Sorry for necro posting, i'm new to the whole rooting thing. My phone info is:
Firmware: 1.5
Baseband Version: 62.59S.20.23U_3.22.26.17
Kernel Version: 2.6.27-d5acf552
Build Number: 1.89.631.1 146733 CL#94714
I have a rogers HTC dream for Canada.
What files do i exactly need, and once acquiring them I just follow the instructions in the first post?
Hello everyone,
I'm facing a quite strange and annoying issue on a TF700T.
No matter which ROM I'm running with, Google Play tells me updates need to be done, which is normal. When I start the updates, the downloads pause at 4% for most of them, and will never end, even after 4 days of activity.
A tablet on which you cannot download content to, or install apps is not very usefull.
The problem is the same with other download types (if I browse on the navigator, to download a ROM.zip, download starts and stops at 4%)
A friend gave me this tablet with Cromi-X insttaled on it. I first thought it was a ROM issue, so I flashed CM11 stable version, just to see.
Problem is the same.
I tried with different google accounts, I cleared Google Play cache services.
No effect.
I also flashed the ASUS original firmware using the SD card mthod, and problem is still there.
I'm short on ideas now, I've looked in XDA forum, but never found a thread with similar issues.
Tablet is currently running Android 4.1.1 WW10.4.4.25-20121228 A03 and unlocked
Thank you very much for your help or advices,
Nicolas
Hi again,
I have made progress on this strange issue.
I finally managed to get google play and downloads to work, but I have to use a vpn client so it can work.
I tried VPN Hideninja.
And, I have the issue no matter which rom/ android version I use.
So, it's a workaround, but at least it allows the tablet to be "usable".
Does someone has any ideas where the problem could come from? (bad kernel version?...)
Or, maybe someone knows a tool to check Android configuration issue, network configuration (I've searched but didnn't find something yet, but I keep trying )
Thank you for your help
Nicolas
Hi,
I installed cromi-X on the tablet and combi-kk as rom2Sd. Bith rom start, but I still have the issues with the playstore.
Does anyone know a tool to perform a hardware check?
If I want to completely clean the tablet, what would you advise ? Right now I'm trying to figure out if the problem is hardware or software.
Thank you for your help
Nicolas
nvuillem said:
Hi,
I installed cromi-X on the tablet and combi-kk as rom2Sd. Bith rom start, but I still have the issues with the playstore.
Does anyone know a tool to perform a hardware check?
If I want to completely clean the tablet, what would you advise ? Right now I'm trying to figure out if the problem is hardware or software.
Thank you for your help
Nicolas
Click to expand...
Click to collapse
Search how to do a logcat over adb and post the resulting text file. Do it after you attempted to download something.
sbdags said:
Search how to do a logcat over adb and post the resulting text file. Do it after you attempted to download something.
Click to expand...
Click to collapse
Hi Sdbags, first of all thank you for your interest.
I've made 3 logcatfiles:
#1 on the rom2sd crombi-kk before downloading. logcatkkStartUp.txt
#2 after stopping downloading as it was frozen. logcatkkDLFails.txt
#3 same as #2 but running on cromi-X on the internal memory of the pad logcatX.txt
I believe this is not looking good:
W/NetworkManagementSocketTagger( 1280): untagSocket(94) failed with errno -22
I/qtaguid ( 1280): Failed write_ctrl(u 56) res=-1 errno=22
I/qtaguid ( 1280): Untagging socket 56 failed errno=-22
Thanks again for your help,
Thank you
Nicolas
nvuillem said:
Hi Sdbags, first of all thank you for your interest.
I've made 3 logcatfiles:
#1 on the rom2sd crombi-kk before downloading. logcatkkStartUp.txt
#2 after stopping downloading as it was frozen. logcatkkDLFails.txt
#3 same as #2 but running on cromi-X on the internal memory of the pad logcatX.txt
I believe this is not looking good:
W/NetworkManagementSocketTagger( 1280): untagSocket(94) failed with errno -22
I/qtaguid ( 1280): Failed write_ctrl(u 56) res=-1 errno=22
I/qtaguid ( 1280): Untagging socket 56 failed errno=-22
Thanks again for your help,
Thank you
Nicolas
Click to expand...
Click to collapse
Well there are some hints in there. As this happens on every rom I'm going to stick my neck out and say it's nothing to do with the ROM you in stall
The below appears to be trying to update Google Street View.
Code:
I/GoogleHttpClient( 832): Falling back to old http client 0 java.lang.NoSuchMethodException: <init> [class android.content.Context, class java.lang.String, boolean]
D/SurfaceControl( 622): Excessive delay in blankDisplay() while turning screen off: 107ms
W/ActivityThread( 832): ClassLoader.loadClass: The class loader returned by Thread.getContextClassLoader() may fail for processes that host multiple applications. You should explicitly specify a context class loader. For example: Thread.setContextClassLoader(getClass().getClassLoader());
I/auditd ( 9847): Starting up
E/auditd ( 9847): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9847): Exiting
I/auditd ( 9850): Starting up
E/auditd ( 9850): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9850): Exiting
I/auditd ( 9853): Starting up
E/auditd ( 9853): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9853): Exiting
I/auditd ( 9858): Starting up
E/auditd ( 9858): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9858): Exiting
I/auditd ( 9863): Starting up
E/auditd ( 9863): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9863): Exiting
D/Finsky ( 2075): [1] DownloadQueueImpl.notifyProgress: com.google.android.street: onProgress 185420/264451 Status: 192.
D/MarketUpdateReceiver( 9689): market is downloading (0%): com.google.android.street
I/DownloadManager( 1842): Download 22 starting
D/MarketUpdateReceiver( 9689): market is downloading (0%): com.google.android.street
I/auditd ( 9871): Starting up
E/auditd ( 9871): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9871): Exiting
I/auditd ( 9876): Starting up
E/auditd ( 9876): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9876): Exiting
I/auditd ( 9879): Starting up
E/auditd ( 9879): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9879): Exiting
I/auditd ( 9882): Starting up
E/auditd ( 9882): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9882): Exiting
D/MarketUpdateReceiver( 9689): market is downloading (0%): com.google.android.street
W/DownloadManager( 1842): Aborting request for download 22: Failed reading response: java.net.SocketTimeoutException
I/DownloadManager( 1842): Download 22 finished with status WAITING_TO_RETRY
auditd is the Selinux logging facility... Protocol not supported means Linux kernel is missing the SELinux protocol...
So possibly you are on an older bootloader that doesn't support the right kernel ....
What bootloader and version of TWRP are you on exactly?
AH WE HAVE A WINNER
Tablet is currently running Android 4.1.1 WW10.4.4.25-20121228 A03 and unlocked
You need to update your bootloader and TWRP. Flash my update package from the CROM-X first post and then follow the instructions to move to a later TWRP if you want to try a CM11 base
Hi Sdbags,
upon startup, bootloader version shows "WW_epad-10.6.1.14.4-20130329" A03, and TWRP is v2.6.3-that3.
I can atach pictures if you want.
Ciould it be that a part of the tablet has the right bootloader version, and another part d not have that correct version?
Thank you for your help
Nicolas
nvuillem said:
Hi Sdbags,
upon startup, bootloader version shows "WW_epad-10.6.1.14.4-20130329" A03, and TWRP is v2.6.3-that3.
I can atach pictures if you want.
Ciould it be that a part of the tablet has the right bootloader version, and another part d not have that correct version?
Thank you for your help
Nicolas
Click to expand...
Click to collapse
Do me a favour and flash my package and then upgrade to TWRP 2.6.3-that3. There is flashable version of that in my CROMBi-kk thread. Then we know you are on the latest bootloader and recovery.
Also you seem to be using bluetooth at the same time. That doesn't work well on these devices. Turn off bluetooth as well and let's get the wifi working.
51189868998
sbdags said:
Do me a favour and flash my package and then upgrade to TWRP 2.6.3-that3. There is flashable version of that in my CROMBi-kk thread. Then we know you are on the latest bootloader and recovery.
Also you seem to be using bluetooth at the same time. That doesn't work well on these devices. Turn off bluetooth as well and let's get the wifi working.
Click to expand...
Click to collapse
Hi,
So I went to recovery, wiped everything except external SD. transfered using adb :
cm-4.4-20140309-CROMBikk4.4.2-tf700t_Signed.zip
install it, restart to crombikk (normal installation, not in rom2SD)
restarted to Android, and made a logcat.
Rebooted to recovery and flashed twrp-2.6.3-that3_Signed 1.zip
Rebooted to android and made a logcat
Finally, rebooted to recovery, installed crombi_kkgapps_20140312_Signed.zip and reboot to Android system, connected a google account and tried to download an app from Google. Bluetooth is off (I never switched it on in my previous logcats.)
I then started the playstore application, and Android Terminal Emulator installed correctly.
I then wanted to install a Google product, Chrome Browser in the logcat attached. Download starts and freezes at 9% for 2 minutes then increases to 24% and freezes again. The download is still pending.
I'll post the logcat of the tablet when download stops by itself or it completes. (let's hope it does but it is hanging for 10 minutes now)
Try clearing data and cache on the Play Store and Google Play Services and reboot.
nvuillem said:
Hi,
So I went to recovery, wiped everything except external SD. transfered using adb :
cm-4.4-20140309-CROMBikk4.4.2-tf700t_Signed.zip
install it, restart to crombikk (normal installation, not in rom2SD)
restarted to Android, and made a logcat.
Rebooted to recovery and flashed twrp-2.6.3-that3_Signed 1.zip
Rebooted to android and made a logcat
Finally, rebooted to recovery, installed crombi_kkgapps_20140312_Signed.zip and reboot to Android system, connected a google account and tried to download an app from Google. Bluetooth is off (I never switched it on in my previous logcats.)
I then started the playstore application, and Android Terminal Emulator installed correctly.
I then wanted to install a Google product, Chrome Browser in the logcat attached. Download starts and freezes at 9% for 2 minutes then increases to 24% and freezes again. The download is still pending.
I'll post the logcat of the tablet when download stops by itself or it completes. (let's hope it does but it is hanging for 10 minutes now)
Click to expand...
Click to collapse
Are you sure it's not your router?
sbdags said:
Are you sure it's not your router?
Click to expand...
Click to collapse
Hi,
I tried to download from 3 different locations, with 3 different ISP and modems, and the problem is the same.
I also tried to Clear cache and data of Google services and PlayStore. I still have the problem.
Yesterday, when I flashed everything to reinstall the Rom and the recovery on proper basis, I noticed that some directories are not wiped.
Maybe some files are missing?
Is there any way to restore those directory? (maybe doing a wipe data from the bootloader, but I read at many places that it is not advised...
I also tried to find an application or a thread to test the hardware of the tablet without any success
Thank you for your help
Nicolas
nvuillem said:
Hi,
I tried to download from 3 different locations, with 3 different ISP and modems, and the problem is the same.
I also tried to Clear cache and data of Google services and PlayStore. I still have the problem.
Yesterday, when I flashed everything to reinstall the Rom and the recovery on proper basis, I noticed that some directories are not wiped.
Maybe some files are missing?
Is there any way to restore those directory? (maybe doing a wipe data from the bootloader, but I read at many places that it is not advised...
I also tried to find an application or a thread to test the hardware of the tablet without any success
Thank you for your help
Nicolas
Click to expand...
Click to collapse
You could try a full internal sd card format from inside twrp - warning it can take up to 2 hours to complete. Make sure you have everything you want to keep and rom.zips on external sd as well.
sbdags said:
You could try a full internal sd card format from inside twrp - warning it can take up to 2 hours to complete. Make sure you have everything you want to keep and rom.zips on external sd as well.
Click to expand...
Click to collapse
Hi,
I did the full wipe from the factory (took 90 minutes )
I reinstalled the rom, and I stil have the problem (erro 495 most of the time)
I then downloaded and installed a VPN client and it works. ( I attached the logcat.txt)
There is still something I can't figure out, as it works using a VPN, the issue is probably not related to hardware, but software, and it is not related to the Rom or recovery.
Do you know if Google checks something like device ID when apps are dowloaded from the store?
Thanks
Nicolas
nvuillem said:
Hi,
I did the full wipe from the factory (took 90 minutes )
I reinstalled the rom, and I stil have the problem (erro 495 most of the time)
I then downloaded and installed a VPN client and it works. ( I attached the logcat.txt)
There is still something I can't figure out, as it works using a VPN, the issue is probably not related to hardware, but software, and it is not related to the Rom or recovery.
Do you know if Google checks something like device ID when apps are dowloaded from the store?
Thanks
Nicolas
Click to expand...
Click to collapse
If it works on a VPN then it is more likely related to your country and / or ISP and Google servers.
Hey,
I just got COS12 for my Oneplus One via fastboot. Everything worked fine, I rooted my device and flashed TWRP. I installed Xposed Framework and tried various modules.
As I now wanted to enable the modules Xprivacy and GravityBox [LP] and rebooted my device because of that, I got stuck into a bootloop.
I didn't like COS12 (because some Xposed modules are not fully working) anyways, so I decided to get my WhatsApp backup via adb pull /sdcard/WhatsApp C:\... and go back to CM11S.
The problem is, that my PC doesn't recognize my OPO; when I type adb devices it says "List of devices attached", but there is no device at all. ADB Drivers should be installed, because one day ago, I was perfectly able to flash COS12 and so on...
Thanks for your answers
Oneplus One 64GB------Windows 7
likemil said:
Hey,
I just got COS12 for my Oneplus One via fastboot. Everything worked fine, I rooted my device and flashed TWRP. I installed Xposed Framework and tried various modules.
As I now wanted to enable the modules Xprivacy and GravityBox [LP] and rebooted my device because of that, I got stuck into a bootloop.
I didn't like COS12 (because some Xposed modules are not fully working) anyways, so I decided to get my WhatsApp backup via adb pull /sdcard/WhatsApp C:\... and go back to CM11S.
The problem is, that my PC doesn't recognize my OPO; when I type adb devices it says "List of devices attached", but there is no device at all. ADB Drivers should be installed, because one day ago, I was perfectly able to flash COS12 and so on...
Thanks for your answers
Oneplus One 64GB------Windows 7
Click to expand...
Click to collapse
Go into fastboot mode or bootloader mode and type
fastboot devices
If you see the serial number of your device, then you are good to proceed ahead, else there is problem with the drivers.
likemil said:
Hey,
I just got COS12 for my Oneplus One via fastboot. Everything worked fine, I rooted my device and flashed TWRP. I installed Xposed Framework and tried various modules.
As I now wanted to enable the modules Xprivacy and GravityBox [LP] and rebooted my device because of that, I got stuck into a bootloop.
I didn't like COS12 (because some Xposed modules are not fully working) anyways, so I decided to get my WhatsApp backup via adb pull /sdcard/WhatsApp C:\... and go back to CM11S.
The problem is, that my PC doesn't recognize my OPO; when I type adb devices it says "List of devices attached", but there is no device at all. ADB Drivers should be installed, because one day ago, I was perfectly able to flash COS12 and so on...
Thanks for your answers
Oneplus One 64GB------Windows 7
Click to expand...
Click to collapse
You can rather dirty flash the COS12 rom through recovery, then go and backup the apps you want via titanium back. Change the rom you want.
Isn't there a DISABLE-XPOSED.zip which you can flash from recovery? I might be wrong with Lollipop, but when installing xposed on KitKat, there was such a .zip avaialble.
On the other hand maybe there is none, since you have to flash also the framework from recovery.
OnePlus soft bootloop with Xposed and XPrivacy backout
I have a OnePlus One running the current OTA CM12 with root and SuperSU installed.
Using the XPrivacy installer and recovery I managed to get the xposed framework to install and it seemed happy, then I enables XPrivacy and rebooted.
At this point it would boot past the bootloader into the startup ( displaying the rotating hex icon animation ) and state 'Updating apps, 0 of 164' which would slowly work through about 30 apps until that popup disappeared and it restarted the init process ( soft reboot ) and came back 'Updating apps, 0 of 132' and so on until it finished eventually. Then it would just sit there spinning the hex forever.
Reboot to fastboot and recovery both worked but normal booting just did the spin thing.
I pulled a couple of logcats and found that it was crashing on a segfault.
Code:
E/art ( 5077): Tried to mark 0xffffffff not contained by any spaces
E/art ( 5077): Attempting see if it's a bad root
E/art ( 5077): Found invalid root: 0xffffffff with type RootJavaFrame
F/libc ( 5077): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x37 in tid 5091 (GCDaemon)
I/libc ( 5077): Suppressing debuggerd output because prctl(PR_GET_DUMPABLE)==0
W/GCDaemon( 5091): type=1701 audit(0.0:2222): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj=u:r:system_server:s0 reason="memory violation" sig=11
With different formatting, another example:
Code:
5-27 07:43:30.479 F/libc ( 5897): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x37 in tid 5911 (GCDaemon)
05-27 07:43:30.468 W/GCDaemon( 5911): type=1701 audit(0.0:2640): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj=u:r:system_server:s0 reason="memory violation" sig=11
This crashloop was fairly consistent and pretty quick although it didn't always indicate 'beginning of crash ' in the logs
Code:
05-27 07:41:09.467 F/libc ( 817): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x37 in tid 831 (GCDaemon)
05-27 07:41:20.663 F/libc ( 1380): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x37 in tid 1394 (GCDaemon)
05-27 07:41:32.952 F/libc ( 1796): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x37 in tid 1810 (GCDaemon)
...
I'm including the zipped log files both before and after the fix I used below.
First I tried the elsewhere mentioned /system/bin/app_process32_xposed move but that did not fix the bootloop.
Using these logs I found the locations of the xposed framework and xprivacy apps and deleted them.
Code:
rm -f /system/framework/XposedBridge.jar
rm -rf /data/app/biz.bokhorst.xprivacy-1/
rm -rf /data/system/xprivacy
I know rm -f is dangerous but I already had backups and was on the verge of wiping anyway.
Reboot and the phone came up normally. Log showed that the system cleaned up some of the stuff.
I don't expect this to be a long term perfect solution but it saved me a few hours of download / reboot time.
Try putting Xposed in safe mode
Credits: Tungstwenty.
Quick explanation of the safemode: It was developed by @Tungstwenty and makes it possible to disable Xposed by repeatedly pressing one of the hardware buttons during early startup. The phone will vibrate twice when the first key press has been detected. Then you have five seconds to press the same button four more times. Each key press will be confirmed with a short vibration; the final one with a long vibration. It creates /data/data/de.robv.android.xposed.installer/conf/disabled, which prevents most of Xposed's actions (e.g. no hooks are made and no modules are loaded). There's no 100% guarantee that this will get you out of a bootloop, but in most cases it should.
Same thing happened once with my Xperia Z.
Sent from my A0001 using XDA Free mobile app
Well guys i started working on Roms For the galaxysmtd i was compling normaly after an hour i got that error (Luckywise i didnt go to sleep haha)
Code:
make: *** No rule to make target '/home/dos-developers/android/omni/out/target/product/galaxysmtd/obj/SHARED_LIBRARIES/libpac_intermediates/export_includes', needed by '/home/dos-developers/android/omni/out/target/product/galaxysmtd/obj/SHARED_LIBRARIES/libjni_pacprocessor_intermediates/import_includes'. Schluss.
I synced the OmniROM sources freshly ....... Need Help thanks
'm trying to build AOSP for a supported device (sony Xperia z5) (aosp_mips64-eng) I follow the instruction here: https://forum.xda-developers.com/t/...sp-pie-custom-rom-for-xperia-devices.3921641/ After download the source, Initializing device type for ROM building. I Encounter an error while trying to build the custom ROM:
I there anything i could do? Have I done something wrong? I'm pretty sure i did the previous steps correctly.
============================================
ninja: no work to do.
ninja: no work to do.
No need to regenerate ninja file
No need to regenerate ninja file
ninja: error: 'device/generic/common/nfc/libnfc-nci.conf', needed by 'out/target/product/generic/system/etc/libnfc-nci.conf', missing and no known rule to make it
10:29:40 ninja failed with: exit status 1
build/make/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
helloguys2489574 said:
build AOSP for a supported device (sony Xperia z5) (aosp_mips64-eng)
Click to expand...
Click to collapse
You have to build for your device, not for a mips64 device as you can read in your mentioned instruction:
Code:
source build/envsetup.sh && lunch aosp_[device_model]-userdebug
Please take a closer look into the numerous tutorials available at the internet.
Please don't ask for further assistance if you don't know exactly what you're doing!