Related
So I have the Razr M Retail, and I was rooted with Safestrap and running Hashcode0f's CM10, completely stable. Yesterday I decided to move to TWRP with the bootloader unlock, so I backed up my ROM to an external SD, and also separately used TiBu to backup my apps, and then used mattlgroff's Razr M Utility to unlock the BL and flash TWRP, which all went fine. Then I wiped internal storage and restored my backup from TWRP. It restored and booted fine, but the Wi-Fi and camera didn't work. The Wi-Fi is stuck to a toggled off position in the settings, and it's greyed out so I can't change it. If I click to see networks, it gets stuck in "Turning Wi-Fi on..." and I never see anything. The camera force closes with "Can't connect to camera." Since I hadn't been sure from the start that a restore would work, I was expecting trouble at this point, so I flashed a fresh version of CM10 from Hashcode's goo.im with the intention of restoring my apps with TiBu. It booted, but it seemed like it was running slow and the Wi-Fi didn't work, with the same issue as before. I didn't try the camera. I messed around with a few things trying to get it to work, and although nothing worked, I tried doing all of these separately and then reflashing:
a) Flash stock Moto 4.1.2 with the utility
b) Restore my stock rooted Moto 4.1.1 with safestrap (Just sayin, this gets weird, I end up with both TWRP and Safestrap)
c) Restore to b) and then restore my CM10 backup as a Safestrap ROM-slot 1
d) Dial *#*#526#*#* to reset Wi-Fi driver (did nothing afaik)
ALSO, I charged the phone last night and this morning at 8:30 it was at 100% battery. 3 hours later, with wi-fi, data, and GPS all off, and using the phone very very lightly, it was at 46%, so there is significant battery drain coming from somewhere.
Any help or suggestions would be greatly appreciated.
First off, you need to fastboot back to stock and start over. TWRP didn't break your phone, restoring a backup from SS did. If you flash a fresh CM10 build, not a backup, you should be okay and you should only get the bugs that are associated with CM10.
Ok, now you're going to ask why the backup didn't work. SS is designed to work on top of the stock boot.img, but CM10 has its own boot.img and that's the reason that CM10 builds were so buggy when used with SS. When you saved CM10 with SS, it probably saved the stock boot.img with it and the stock boot.img is not going to make CM10 happy. If you had saved a stock based ROM and tried to restore it, you probably would have been okay.
Now, with all that being said, if you fastboot back to 4.1.2, then you'll need to use a 4.1.2 based ROM or a CM build. If you want to use a 4.1.1 based ROM, you'll need to flash the 4.1.1 boot.img, prior to flashing the ROM. You battery is probably dying so quickly because CM10 is trying to fight with the stock kernel. You need to fastboot and flash clean.
Tmfle from
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\
VoraciousGhost said:
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\
Click to expand...
Click to collapse
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.
RikRong said:
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.
Click to expand...
Click to collapse
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.
VoraciousGhost said:
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.
Click to expand...
Click to collapse
Yeah, definitely use Mic's builds, they are more current. TWRP shows that the sytem is mounted, but it is fact not. That's why you need to reboot recovery. When you reboot, you'll see that it's not mounted.
Mic's CM10 is very, very stable. Very good build.
10.1 is a little more buggy but still a good build.
Sounds like you're either using one of Hash's old builds or new, buggy ones. Mic is the way to go for now
Sent from my Nexus 7 using Tapatalk HD
I am trying to get Ktoonsez kernel running on MDOB ROM so i can create a perfect sRGB profile and FULLY eliminate screen flicker/color shift, running into some problems.
I am rooted with TWRP recovery and debloated via Motochopper CASUAL R527b
I also have Nottach Xposed mod installed.
I attempted to flash version 1.7 of the TouchWiz version of MDOB
Here is where i have a problem; i have a FULL backup of AT&T ROM with the above all installed and running PERFECTLY (which im running on again). I reboot into TWRP recovery, have the aforementioned full backup, i swipe to factory reset, davlik/system/data/cache wipe, then flash the ROM
I did NOT perform a full system/data wipe the first 2 times, and the ROM worked but not on second reboot (had to reboot system via recovery but it worked afterwords. I also got Ktoonsez TouchWiz kernel working, but it would not fully boot unless i booted from TWRP).
I cannot get past the Custom/padlock screen when i hit reboot system, so i cannot flash the kernel and then clear davlik and cache (which i am supposed to do in that order, correct?)
If someone could give me a complete step by step i would appreciate it. i have been waiting to fix the damn screen flicker and create the first perfect sRGB settings for this phone; i cant get this figured out or working, and i dont want to screw something up.
I have linked to EVERY bit of root/hack/ROM/kernel software i have downloaded, only difference is the ROM i have is version 1.7 instead of version 1.8. I believe perhaps something to do with the previous mods ive done may be inhibiting my ability to boot properly. i DID have it running, both MDOB, and later MDOB with Ktoonsez kernel, but i had to reboot from TWRP every time, which i knew was not right, so i flashed the backup AT&T ROM with all system/user/apps/data, the Motochopper Casual R527b Root/debloat mod, and Nottach Xposed mod which are part of my only backup (works flawlessly, im happy with it but i want to perfect an sRGB profile for these phones, its in my area of work and i would love to be able to show stuff that is absolutely correct to clients).
Everything should be annotated correctly, and i flashed everything correctly as per the directions found in appropriate threads, ie reset, davlik/data/system/cache wipe, flash ROM, reboot (worked twice, second reboot i installed Ktoonsez kernel, wiped davlik/cache, rebooted, got in, enjoyed it, rebooted, and it hung at custom/padlock screen). Now after i flash the same MDOB file, it will NOT boot, just hangs at custom/lock screen. i DID fully wipe the device to try to reset everything (via TWRP), and flash the new ROM.
Thanks!
anyone? this is really frustrating; same issue trying to flash v1.8 of MDOB
Hi, I'm just another android semi-noob who made a silly mistake, and has now spent the whole day in the library researching my problem, as I don't have internet at my new flat yet.
Here's what happened, as concisely as possible:
I have a Nexus 4, on 4.2.2, running a version of PA 3+, with Franco Kernel. I felt like another PA nightly update, after having not updated for a couple of weeks, so I chose the latest one, which was PA 3.92. Did the usual - recovery, install rom, install gapps, install kernel, wipe cache, wipe dalvik cache.
Then, the phone wouldn't boot, was stuck on the Google logo. I went to bed. Today, I realised (although I could still be wrong) that the 3.92 PA update was for Jelly Bean 4.3. Is this even correct? Well, assuming it was, I managed to connect phone to my mac, go into terminal, use adb-mac, which I had downloaded months ago when I first rooted, and send the PA 3.69 zip to the phone. Installed that, then gapps then kernel, wiped cache and dalvik cache, and rebooted. I've now done this a few times and each time, I get stuck at the Paranoid Android boot logo.
Most of the other threads I see suggest wiping data. I really don't want to wipe my data, is there a solution?
If I do, really, have to wipe my data to get any further, how would I go about backing EVERYTHING up beforehand, given that I only have access to fastboot and recovery? Would I need to follow this tutorial (which doesn't backup SMS...) - http://forum.xda-developers.com/showthread.php?t=1420351 ? Also, when I've backed up, how exactly do I go about wiping data and then getting back to exactly where I was before all of this?
Was I correct in thinking that PA 3.92 is only for JB 4.3 and that PA 3.69 is for 4.2.2? Was I correct in thinking that this is why my phone got stuck?
Please, please help me, it will be much appreciated, my laptop is almost out of battery now so I'm going home, then coming back to the library in an hour as I haven't eaten all day
Depressed noob.
Flash PA again but do not flash the kernel. looks like PA is using jss build and maybe the kernel you are flashing is using jwr build.
PA is having some problems now with root, i suggest you to stay in 4.2.2 or use another 4.3 rom.
Did you flash the Android 4.3 baseband and radio?
Sent from my Nexus 4 using Tapatalk 4
leandronb said:
Flash PA again but do not flash the kernel. looks like PA is using jss build and maybe the kernel you are flashing is using jwr build.
PA is having some problems now with root, i suggest you to stay in 4.2.2 or use another 4.3 rom.
Click to expand...
Click to collapse
Yeah, I do intend to say in 4.2.2, do you think I should try an older PA? I think 3.69 is for 4.2.2, which is the one I've flashed, several times. OK, I'll try flashing the rom, then gapps but not Franco Kernel as you suggest, but I think I may have tried that already and it didn't work.
andyabc said:
Did you flash the Android 4.3 baseband and radio?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
No, I don't even know what radio is, all I did was try to flash the PA 3.92 update zip, on it's own (plus gapps and franco kernel)
Yep, you have to wipe data since you're switching between Android versions.
Sent from my Nexus 4
Nigeldg said:
Yep, you have to wipe data since you're switching between Android versions.
Sent from my Nexus 4
Click to expand...
Click to collapse
But I only installed the PA rom corresponding to JB 4.3, I never updated to stock 4.3 or anything beforehand, it was just a mistaken update to PA 3.92 which I think is for JB 4.3 only. Anyway I think I'm clutching at straws here, so if I do have to wipe, 1) how can I make the fullest backup possible of everything on my phone and, 2) how do I go about wiping and finally, 3) after I wipe, what exactly do I do??
Thanks so much to you three for taking an interest in my problem so far!
12ian34 said:
But I only installed the PA rom corresponding to JB 4.3, I never updated to stock 4.3 or anything beforehand, it was just a mistaken update to PA 3.92 which I think is for JB 4.3 only. Anyway I think I'm clutching at straws here, so if I do have to wipe, 1) how can I make the fullest backup possible of everything on my phone and, 2) how do I go about wiping and finally, 3) after I wipe, what exactly do I do??
Thanks so much to you three for taking an interest in my problem so far!
Click to expand...
Click to collapse
I had exactly the same issue you had at first boot, it remained at Google logo forever when i first flashed PA 3.92. This issue came because i was flashing PA 3.02 with Franco nightly 165, franco nightly 165 is for 4.2.2m and if you were in 4.2.2 then you will never know new releases as that one was the last 4.2.2 kernel. I suggest you flash PA 3.92 + gapps from 0802, without Franco, it will boot fine. Also, as explained in big letters in PA download, first step is to download radio and bootloader for the update, i did not have to wipe my memory for the upgrade.
I don't recommend downloading Franco 175 for 4.3, as it has conflicting issues with PA, so use PA with the stock kernel and you should be good meanwhile this gets solved.
12ian34 said:
Yeah, I do intend to say in 4.2.2, do you think I should try an older PA? I think 3.69 is for 4.2.2, which is the one I've flashed, several times. OK, I'll try flashing the rom, then gapps but not Franco Kernel as you suggest, but I think I may have tried that already and it didn't work.
No, I don't even know what radio is, all I did was try to flash the PA 3.92 update zip, on it's own (plus gapps and franco kernel)
Click to expand...
Click to collapse
Go here and flash the baseband and radio and flash it before flashing the rom and make sure it is wiped clean: http://forum.xda-developers.com/showthread.php?t=2147194
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Go here and flash the baseband and radio and flash it before flashing the rom and make sure it is wiped clean: http://forum.xda-developers.com/showthread.php?t=2147194
Click to expand...
Click to collapse
But how do I go about backing it up before I wipe it give that I can only access fastboot and recovery (CWM) ?!?!
OK, I've found a way to do it using
./adb-mac pull /sdcard/0/ sdcardbackup
do I need to backup anything else?
Also, I've downloaded the link you sent me, just to be clear, first, I wipe data, factory reset, then I send the radio and baseband to my phone using adb, then flash them in recovery and then flash PA 3.69, GApps, Franco Kernel r165 then wipe cache, dalvik cache, then reboot, then go about restoring all my data. Is this correct?
Mee too
I just wiped my Nexus 4, flashed the new jb 4.3 bootloader and radio, and flashed PA 3.94 to check out the experience.. Except for the time taken by boot logo to start up the first time, I was happy using it for a couple of hours.. Only till the time I rebooted it.. Since then, it's just stuck at the PA animation / logo and NOT MOVING AHEAD !! Please help!!
jsmonu said:
I just wiped my Nexus 4, flashed the new jb 4.3 bootloader and radio, and flashed PA 3.94 to check out the experience.. Except for the time taken by boot logo to start up the first time, I was happy using it for a couple of hours.. Only till the time I rebooted it.. Since then, it's just stuck at the PA animation / logo and NOT MOVING AHEAD !! Please help!!
Click to expand...
Click to collapse
just do what is written on the xda page, do not deviate from that.
get up to date, that means get the latest TWRP and make sure you are running googles newest radios
1. factory reset, perhaps format partitions: system, data, cache, dalvik
2. install the latest PA, thats 3.94
3. install the latest PA gapps, thats 0805a
4. wipe caches, reboot
5. do no mess around with things like titanium backup - at least dont restore system apps
6. if you make a clean install root will work out of the box.
when developing i must go through that process hundreds of times, i can vouch that it will work.
molesarecoming said:
just do what is written on the xda page, do not deviate from that.
get up to date, that means get the latest TWRP and make sure you are running googles newest radios
1. factory reset, perhaps format partitions: system, data, cache, dalvik
2. install the latest PA, thats 3.94
3. install the latest PA gapps, thats 0805a
4. wipe caches, reboot
5. do no mess around with things like titanium backup - at least dont restore system apps
6. if you make a clean install root will work out of the box.
when developing i must go through that process hundreds of times, i can vouch that it will work.
Click to expand...
Click to collapse
Moles! Help me! I refer you to my first post in this thread, I want to stay on 4.2.2 and PA 3.69 for the moment, and preferably not wipe everything. I accidentally updated to PA 3.92 and then stuck at the PA logo on boot forever. Now I've tried to go back to 3.69 many times and still get stuck at PA logo. currently using adb pull to get all my important stuff off phone.
Is there a shortcut for me, which doesn't involve wiping??
EDIT:
... OK, I just downloaded the 4.3 radio and bootloader, pa 3.94, gapps and sent them to my phone, flashed each one in turn and then wiped caches, reboot. I skipped the wipe, and now my phone is working for the first time in three days - [optimising apps]. Let's see if this works....
Yep, phone works absolutely fine, didn't have to wipe and now have 4.3 and PA 3.94, which wasnt my original intention, but it had to happen sometime! Thanks for all the help people, I think we can consider this one solved
12ian34 said:
Hi, I'm just another android semi-noob who made a silly mistake, and has now spent the whole day in the library researching my problem, as I don't have internet at my new flat yet.
Here's what happened, as concisely as possible:
I have a Nexus 4, on 4.2.2, running a version of PA 3+, with Franco Kernel. I felt like another PA nightly update, after having not updated for a couple of weeks, so I chose the latest one, which was PA 3.92. Did the usual - recovery, install rom, install gapps, install kernel, wipe cache, wipe dalvik cache.
Then, the phone wouldn't boot, was stuck on the Google logo. I went to bed. Today, I realised (although I could still be wrong) that the 3.92 PA update was for Jelly Bean 4.3. Is this even correct? Well, assuming it was, I managed to connect phone to my mac, go into terminal, use adb-mac, which I had downloaded months ago when I first rooted, and send the PA 3.69 zip to the phone. Installed that, then gapps then kernel, wiped cache and dalvik cache, and rebooted. I've now done this a few times and each time, I get stuck at the Paranoid Android boot logo.
Most of the other threads I see suggest wiping data. I really don't want to wipe my data, is there a solution?
If I do, really, have to wipe my data to get any further, how would I go about backing EVERYTHING up beforehand, given that I only have access to fastboot and recovery? Would I need to follow this tutorial (which doesn't backup SMS...) - http://forum.xda-developers.com/showthread.php?t=1420351 ? Also, when I've backed up, how exactly do I go about wiping data and then getting back to exactly where I was before all of this?
Was I correct in thinking that PA 3.92 is only for JB 4.3 and that PA 3.69 is for 4.2.2? Was I correct in thinking that this is why my phone got stuck?
Please, please help me, it will be much appreciated, my laptop is almost out of battery now so I'm going home, then coming back to the library in an hour as I haven't eaten all day
Depressed noob.
Click to expand...
Click to collapse
Download the nexus 4 toolkit and flash stock rom from it
Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.
trent4071 said:
Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.
Click to expand...
Click to collapse
Same here I tried it, and it did the same for me also...
Sent from my SM-N920F using Tapatalk
These are the Gapps that worked for me
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
Thank you for the help wikked26, but it didn't work. Those Gapps still crash for me. I think it's something incorrect in the way my phone is configured, not a case of downloading the wrong Gapps.
If anyone has any other ideas, please share them! I haven't cracked the case just yet
I know I was having issues with the Slimroms version where I booted into CM and set it up before installing Gapps. Fixed it by reinstalling/wiping the cache and installing Gapps before booting anything. Don't know if that helps, but I'm running fine now.
I'm hoping this is similar to the issue I'm having. Do you get it where you can factory reset in TWRP, then flash CM13, but when you go to flash Slim Gapps? Because I figured out that after factory resetting TWRP will only successfully flash 1 zip file. I also tried to wipe the cacher, dalvik, data, and system, then flash cm13 but Gapps still wouldn't flash. Maybe its a bug with TWRP 3.0.2? I'm going to try to use a different version of TWRP and I'll update with my results
EDIT: TWRP 2.8.5 did not do anything different
Wow, thanks for all the great responses. I made sure to try and install CM13 and Gapps at the same time, before boot, after wiping everything one last time. It worked flawlessly, and I can now use Google Play Services.
I hope this thread helps anyone else who is also a little stuck. I also found that TWRP didn't have any issues flashing multiple zips at the same time, not sure whats going on with you, Orange Officer. Perhaps try removing your battery after CM13 flashes, and then boot into TWRP again and flash Gapps without booting up CM13 at all?
Alright, so I'm thinking my problem was that i initially had supersu installed when attempting to install this kernel, and thus causing that bootloop.
Can anyone provide insight as to whether this is true. I had a nandroid backup of my stock rom and even though I "restored" it, it was still stuck in bootloop regardless :/. I don't want to keep restarting and reinstalling everything over and over without knowing what the problem is.
I currently run Resurrection Remix with xposed. I'm fearing if I make another nandroid backup for this and try to flash the rom again, it won't work and I have to start again.
FYI: I was on RR when I attempted the kernel install.
Try downloading the kernel again and dirty flash it. If that doesn't work try dirty flashing some other kernel. And if that doesn't work dirty flash your rr rom. And if still not working then restore your backup
billamin said:
Try downloading the kernel again and dirty flash it. If that doesn't work try dirty flashing some other kernel. And if that doesn't work dirty flash your rr rom. And if still not working then restore your backup
Click to expand...
Click to collapse
well what i did was following:
round 1. RR rom already installed
wipe cache and delvik, install kernal, bootloop
attempt to restore nandroid., still bootloop,
attempt 2:
wipe everything and install RR, SU, Gapps
did setup
installed franko r25
attempt 3.
wipe and factory reset
restore nandroid
bootloop
attempt 4
DONT install franco and install ak. after everything
works
Franco kernel needs to be installed twice to work. flash kernel, dont restart, just flash again
feis said:
Franco kernel needs to be installed twice to work. flash kernel, dont restart, just flash again
Click to expand...
Click to collapse
omg thanks! that worked perfectly. Now a new problem is specifically when I'm using tugapower, while typing on my swiftkey into the xda forum. I'm noticing a lag. I've made it so then both apps are operating on performance with franco. Not sure what's causing the lag. Is it possibly the theme?
Dunno whats the problem, but im pretty sure if you just flashed franco, didnt change anything and used those apps, they wouldnt lag
didn't figure out what caused the lag but its gone now