Database Users

[Q] Already rooted but Qs about Custom ROMs

I'm rooted but have never ran anything but stock on my phone. Only having experience with flashing WinMo devices, what exactly do I need to know before flashing a custom ROM?
If I flash, do I lose the data on my phone now (does it do a factory wipe)?

Most times toy will need to do a wipe of the data and cache to get a full rom working correctly.
Sent from my DROIDX using XDA App

Yeah, thanks.. Just downloaded ROM manager and Clockworkmod Recovery ($2), kinda following the instructions from Gummys post.
How long does this process take? I installed from SD and did the reboot.. I must of waited a good fifteen minutes before pulling the battery assuming it was stuck. Now it's sitting on the Gummy Screen with the 4 rotating colored android pics.
Got into recovery but it's not allowing me to apply the update.zip (e:can't open/cache/recovery/command)?

Dang it! I was in the middle of posting the following instructions when I got interrupted (at work)
Code:
Flashing will wipe your phone. The nice thing with android is -anything you have purchased or installed from the market will automatically be restored to your phone after you log in using your gmail account.
Let me qualify my statement though - I have flashed a few roms and my free apps were not automatically installed for whatever reason. My purchased apps were not installed either - but they were available for installation at no charge.
Here is another important thing to remember - this will only happen if you chose the correct settings in -uh well- settings. There are some options in there to back up your data to google. If you did that then 95% chance it will all be good.
I recently switched from the DX to the D1 (gave my wife the DX bc I wanted to try some D1 roms) and all my apps were installed and somehow google even migrated my current wallpaper over! I was blown away by that.
Also -make sure your contacts are set up to sync with google. if they are just being added to your phone and not in sync with your google account you are going to loose them all.
Flashing roms:
1. You need to get the droidx bootstrapper app from the market (or I think you can get it for free if you search clockwork mod on google and go to Koush's website. I just bought it to help the developer.).
2. Open the app.
3. Press the "Bootstrap recovery button"
4. You should get a dialog box saying success (or something and then press ok).
5. Press "reboot recovery".
6. Your phone will reboot into clockwork recovery (not the stock phone recovery). It will be a black screen with old school green letters and a menu.
a. In recovery you do not have a touch screen.
b. The volume rocker is up/down.
c. The camera button is "Enter".
d. The physical back button will take you back one menu (also I believe the power button but I always used the power button.
7. The first thing you want to do before you do anything is make a nandroid (backup) of your phone.
8. The opening screen of recovery has the option to create a nandroid. do that.
9. It takes around 5 minutes then choose to reboot your phone when it says, ""complete".
10. To flash a rom put ti...
Wish I would have just posted what I had. Maybe you would have had a nandroid to revert to.
Dang.
Yea. It shouldn't take that long. Sounds like something got hosed. I am getting interrupter again. I will try and get back with some info.

Awesome info, thanks for this. Did a factory wipe and now it's booting up normally (or so it appears into Gummy), will definitely bookmark that info though, thanks again man!

Were you installing Gummy. And did you follow the instructions exactly?
****EDIT****
looks like you got it. glad to hear that.

[Q] Boot Loop on my MT4G

I'm new in this whole smart phones so pls be patient with me
So I have MT4G and i had before the cyanogenmod 7 system but I will shot itself down and i would get the boot loop. so I restored to manufacture settings worked ok i thing but then i tried to restore all the info with ROM Manager and it stuck again. played with it more and somehow got to my older system "Synergy Rom" and restored all the info with Titanium app (that i had as well)now its ok but it shot itself once in a wile. when i try to restart it i have 0% battery when the battery was 75% before. can someone tell me if there is any better system that i can download and what are the steps without erasing any info?
Thank you

Lital Lev said:
I'm new in this whole smart phones so pls be patient with me
So I have MT4G and i had before the cyanogenmod 7 system but I will shot itself down and i would get the boot loop. so I restored to manufacture settings worked ok i thing but then i tried to restore all the info with ROM Manager and it stuck again. played with it more and somehow got to my older system "Synergy Rom" and restored all the info with Titanium app (that i had as well)now its ok but it shot itself once in a wile. when i try to restart it i have 0% battery when the battery was 75% before. can someone tell me if there is any better system that i can download and what are the steps without erasing any info?
Thank you
Click to expand...
Click to collapse
erase/wipe everything.. EVERYTHING
install the virtuous unity ROM
and thats it. start from scratch.. its your best bet

DO NOT restore system data with Titanium. It might easily cause the problems you're describing. And of course, DO NOT restore /data partition from nandroid backup (the one you made using ROM Manager or directly in recovery), when it isn't a part of the ROM you've backed up and restored too.
You can selectively back up and restore SMS/MMS/Call log, and also WiFi/Bluetooth/bookmarks and some more useful settings. But it's hard in Titanium, you need to know which system app contains the info you need. You can search the internet and you'll see (these apps are marked in green in app list). The rest of system settings you should set up from scratch for any system, if you expect it to function trouble-free.
Wipe your phone clean, reinstall a ROM and restore user apps only, to begin with, and see if it stops the issues you're having (which will most likely happen). And if you like Sense, you'll be better off installing Virtuous Unity, as Grimey pointed above me. One ROM with virtually 0 bugs.

If u like Sense 3.0, LeeDroid has 0 bugs as well. Been usin it for weeks...
Sent from my HTC GLACIER using xda premium

Thank you, but could you tell me what are the steps to install me OS?

I cleaned the phone got back to the manufacturer setup but i can't find even the Market app (or google play app) to download the "Virtuous Unity ROM"

Lital Lev said:
I cleaned the phone got back to the manufacturer setup but i can't find even the Market app (or google play app) to download the "Virtuous Unity ROM"
Click to expand...
Click to collapse
you need to get s-off
you need to get root
you need to install a recovery
then you download the virtuous unity ROM from the development section or the virituousrom.com website. put it in your sd card. load recovery and wipe your system and cache and dalvik, then install the ROM..

So my phone is s-off and root i just don't know how to the install recovery if i can't find the market app and i don't know how to download it.

Lital Lev said:
So my phone is s-off and root i just don't know how to the install recovery if i can't find the market app and i don't know how to download it.
Click to expand...
Click to collapse
absolutely nothing to do with the market.
download the recovery image (clockworkmod or 4ext). rename it to recovery.img for easier access. place it in the same folder as adb/fastboot for easier access.
get into your bootloader, then get to fastboot mode, it should say something like "fastboot USB"
connect it to your PC
now in the adb/fastboot folder on your PC, hold shift and right-click then click on "open command window here"
finally, type "fastboot flash recovery recovery.img"
now when its done, you can reboot into the bootloader and get into the recovery, from there you just install the ROM

Thank you again, now could you tell me how i get the "adb/fastboot folder " i googled it and found an link to download(not sure if it was the right thing to do)
another thing i have the clockworkmod already on my phone but just in case downloaded the 4ext to my PC and saved it as "recovery.img" now what should i do?
thank you for ur petience

Lital Lev said:
Thank you again, now could you tell me how i get the "adb/fastboot folder " i googled it and found an link to download(not sure if it was the right thing to do)
another thing i have the clockworkmod already on my phone but just in case downloaded the 4ext to my PC and saved it as "recovery.img" now what should i do?
thank you for ur petience
Click to expand...
Click to collapse
if you already have clockwork mod, all you have to do is make sure you phone is off (pull the battery, or turn off hibernate mode)
hold down power + volume down
you will enter the bootloader, give it a few seconds to load
use the volume keys to scroll to recovery and hit power to select
then simply wipe everything and flash the rom
ps. youll need android SDK to get the latest adb and fastboot files

Lital Lev said:
Thank you again, now could you tell me how i get the "adb/fastboot folder " i googled it and found an link to download(not sure if it was the right thing to do)
another thing i have the clockworkmod already on my phone but just in case downloaded the 4ext to my PC and saved it as "recovery.img" now what should i do?
thank you for ur petience
Click to expand...
Click to collapse
Honestly, if I were you, I would go ahead & flash 4ext recovery. It is more stable & from the looks of things, you don't need any more problems than you already have. After you get recovery flashed, or if you choose to use cwm anyway, do this:
1- hold volume down + power you should enter the bootloader.
2- scroll down with the volume button until recovery is hilighted, & press power button to select.
3- You should be in recovery, and if so, choose "wipe data / factory reset" then "wipe cache" then "wipe dalvik"
4- Next, " format system, format data, format boot"
5 Next, choose install from sdcard.. choose zip from sdcard & find the Rom you have on your sdcard. Wait until it installs completely. Then reboot.
6. At this point be very patient and let it load. It could take several minutes...up to 5 or 6
And in a nutshell that is it..
Sent from my HTC Glacier

If I were the op I would leave my phone completely stock and do some more research before proceeding any further. If you break your phone you won't know how to fix it with your current android knowledge.
Sent from my HTC Glacier using xda premium

eqjunkie829 said:
If I were the op I would leave my phone completely stock and do some more research before proceeding any further. If you break your phone you won't know how to fix it with your current android knowledge.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I agree...I made that mistake & Jack_R1 helped me til he got pissed off,(rightfully so), & I realized it only takes a couple of days to read people's situations and you really learn more that way. I started off with an HTCDEV unlocked device, and it took me 2 days to figure out that I bootlooped it by flashing a 2.21 boot.IMG on a 2.34 Rom. I ended up figuring it out w/ jack_r1 helping me. Finally I relocked it and rooted it properly. Now, I can do it from start to finish in about 5 minutes or so...downgrading and all. But its best to read til u understand.
Sent from my HTC Glacier

Thank you all!!!
Would you believe me if i told you that it was a problem with the battery? I changed it to a new one and its all good (so far) i really hope that was the problem. If anything I'll do the steps that you adviced me ))
BUT I still have the problem to log in to the internet except google page and apps. I had it for a long time before but i don't know what causing it, i could log in with firefox thouh, what could be the problem?
thank you all again.

I would. A new battery fixed my co-worker's Desire S, that started crashing all around.

[HOW TO] Root and Install CWM without USB, Odin, or Computer: 2013 Version

Thanks to alephzain, bbelos/CMTeamEpic, DRockstar, koush, neldar, QBKing77, and toadlife!
See a change log of edits to this post at the bottom. Any corrections or suggestions are welcomed.
This How To will explain how you can root and install ClockworkMod on a stock Epic 4G (SPH-D700) running Gingerbread FC09 without a USB cable, Odin, and with or without a computer. My phones USB pins are busted, but otherwise it charges fine and works great. So I spent many determined days figuring out how I may eventually install CyanogenMod. This first requires getting ClockworkMod on the phone.
IMPORTANT NOTE: Be sure to follow the exact procedure below.
How will you get files onto your phones external sdcard?
Novice:
- Without a computer: Download files using a browser found in the Google Play Store: Firefox, Dolphin.
- With a computer: Email yourself the files and use your phones email app to save them to your sdcard.
- With a computer: Remove your external sdcard, insert it into an adapter, then insert/connect it to your computer to copy files to the sdcard.
Expert:
- With a computer: Its possible to access "offline files" with Google Drive, but its a bit cumbersome to find the file using a file manager.
- With WiFi and a computer: After gaining root, install the "WiFi ADB" app and download the Android ADB tools for your OS: Windows, Mac OS X, Linux
Transfer the following files to your sdcard (see attachments below):
- Framaroot-1.6.1.apk
- CleanGB_Kernel_0b28e9767b.zip
- cwm-5.0.2.7-epic4g.zip
Get Rooted:
- On your phone go to Settings -> Applications -> Check: Unknown Sources
- Install the Framaroot-1.6.1.apk package.
Install the following apps from the Google Play Store:
- SGS Kernel Flasher
- ROM Manager
Start SGS Kernel Flasher:
- Backup your stock kernel, but if you re-flash your stock kernel then you will need to repeat the following procedures.
- Choose Kernel -> Select CleanGB_Kernel_0b28e9767b.zip -> Flash Kernel
- Reboot
Start ROM Manager:
- Select Reboot into Recovery
Recovery Mode:
- Press the Settings icon: You should now be in CWM v3.1.0.1 (use volume up/down, camera to select, home to go back)
- Select: install zip from sdcard -> toggle signature verification -> choose zip from sdcard -> cwm-5.0.2.7-epic4g.zip
- Reboot
Verify CWM Installed:
- Power off phone, wait a few seconds after vibration indicates phone is powered off.
- Hold down: Volume Down, Camera, and Power On.
- Release when the icons light up.
- You should see "CWM-based Recovery v5.0.2.7" and the menu in blue text.
Congratulations you flashed ClockworkMod without USB or Odin!
What now? How about installing CyanogenMod? Well thats my next step and I highly suggest your phone already be activated, the PRL updated, data/contacts synced/backed up, and all services working before installing CyanogenMod stable. Otherwise, as of today (CM v10.1), you will need to temporarily boot into Samsungs FC09 in order to perform these functions.
I hope you find this How To helpful. Feel free to aks any questions, but please Google search for any "inbetween steps" that I have left out of this How To for the purpose of brevity.
Good luck!
Change Log:
12/08/2013: (Major Addition) Added important note. Added backing up stock kernel.
11/21/2013: (Minor Addition) Added email method for transferring files to your sdcard. Clean up.
11/20/2013: (Minor Addition) In case their sources disappear I have attached the required files.
11/18/2013: (Minor Correction) Improved links. Clean up.
11/17/2013: (Major Correction) Corrected spelling of Framaroot-1.6.1.apk filename.
11/16/2013: (Minor Correction) After installing CyanogenMod 10.1 (STABLE) I realized the above version CWM is not the latest.

Appreciate the effort and updated info.

Mr_You said:
Thanks to alephzain, bbelos/CMTeamEpic, DRockstar, koush, neldar, QBKing77, and toadlife!
See a change log of edits to this post at the bottom. Any corrections or suggestions are welcomed.
This How To will explain how you can root and install ClockworkMod (CWM) on a stock Epic 4G (SPH-D700) running FC09 without a USB cable, Odin, and with or without a computer. My phones USB pins are busted, but otherwise it charges fine and works great. So I spent many determined days figuring out how I may eventually install CyanogenMod. This first requires getting ClockworkMod on the phone.
How will you get files onto your phones external sdcard?
Novice:
- Without a computer: Download files using a browser found in the Google Play Store: Firefox, Dolphin.
- With a computer: Email yourself the files and use your phones email app to save them to your sdcard.
- With a computer: Remove your external sdcard, insert it into an adapter, then insert/connect it to your computer to copy files to the sdcard.
Expert:
- With a computer: Its possible to access "offline files" with Google Drive, but its a bit cumbersome to find the file using a file manager.
- With WiFi and a computer: After gaining root, install the "WiFi ADB" app and download the Android ADB tools for your OS: Windows, Mac OS X, Linux
Transfer the following files to your sdcard (see attachments below):
- Framaroot-1.6.1.apk
- CleanGB_Kernel_0b28e9767b.zip
- cwm-5.0.2.7-epic4g.zip
Get Rooted:
- On your phone go to Settings -> Applications -> Check: Unknown Sources
- Install the Framaroot-1.6.1.apk package.
Install the following apps from the Google Play Store:
- SGS Kernel Flasher
- ROM Manager
Start SGS Kernel Flasher:
- You may backup your kernel, but if you re-flash your stock kernel then you will need to repeat the following procedures.
- Choose Kernel -> Select CleanGB_Kernel_0b28e9767b.zip -> Flash Kernel
- Reboot
Start ROM Manager:
- Select Reboot into Recovery
Recovery Mode:
- Press the Settings icon: You should now be in CWM v3.1.0.1 (use volume up/down, camera to select, home to go back)
- Select: install zip from sdcard -> toggle signature verification -> choose zip from sdcard -> cwm-5.0.2.7-epic4g.zip
- Reboot
Verify CWM Installed:
- Power off phone, wait a few seconds after vibration indicates phone is powered off.
- Hold down: Volume Down, Camera, and Power On.
- Release when the icons light up.
- You should see "CWM-based Recovery v5.0.2.7" and the menu in blue text.
Congratulations you flashed ClockworkMod without USB or Odin!
What now? How about installing CyanogenMod? Well thats my next step and I highly suggest your phone already be activated, the PRL updated, data/contacts synced/backed up, and all services working before installing CyanogenMod stable. Otherwise, as of today (CM v10.1), you will need to temporarily boot into Samsungs FC09 in order to perform these functions.
I hope you find this How To helpful. Feel free to aks any questions, but please Google search for any "inbetween steps" that I have left out of this How To for the purpose of brevity.
Good luck!
Change Log:
11/21/2013: (Minor Addition) Added email method for transferring files to your sdcard. Clean up.
11/20/2013: (Minor Addition) In case their sources disappear I have attached the required files.
11/18/2013: (Minor Correction) Improved links. Clean up.
11/17/2013: (Major Correction) Corrected spelling of Framaroot-1.6.1.apk filename.
11/16/2013: (Minor Correction) After installing CyanogenMod 10.1 (STABLE) I realized the above version CWM is not the latest.
Click to expand...
Click to collapse
This rooting method works, but i have a problem.
The kernel has the su binary installed, nd thats the problem; with a root checker it says no root access. Now i cant do anything else because everytime i do something to fix this issue, it stays the same after a reboot
Please help me

TheKillah512 said:
This rooting method works, but i have a problem.
The kernel has the su binary installed, nd thats the problem; with a root checker it says no root access. Now i cant do anything else because everytime i do something to fix this issue, it stays the same after a reboot
Please help me
Click to expand...
Click to collapse
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.

Mr_You said:
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.
Click to expand...
Click to collapse
Mr_You said:
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.
Click to expand...
Click to collapse
Yes, im sorry that i have to make u go through all this trouble because maybe im doing this wrong..
What i was trying to say is that the kernel also has 'su' in /sbin (im not sure if this is the problem but in my galaxy s3 the 'su' is only located in /system/bin and /system/xbin)
I also read this article where it said that the 'su binary' isnt supposed to be in /sbin because in this case (what i think its saying is) that everytime it boots up the /sbin is part of the booting process. Here is the website link: htt p://a ndro idsu.co m (cant post links yet damn)
" People with the su binary located in /sbin have a much tougher time. I’ve found that these are mostly Samsung users (with the notable exception of the Nexus S). I don’t know why it’s done this way, and if anybody does know, please let me know, but for some reason kernel and ROM devs for these devices put su in /sbin. /sbin is part of the boot.img, and therefore any modifications to that directory will be erased on boot."
What i first did is installed Framaroot nd rooted the phone, then got excited because i had been trying to root it for like 2 years now with no success, so since i thought i knew what i was doing, i trailed off nd tried to install CWMR through Rom Manager then went into recovery nd for some weird reason it just put me in the stock android recovery so i knew something went wrong... Then i got scared nd tried to go back to your method nd installed the kernel flasher so i flashed the kernel, rebooted, nd then went into the superuser app. It said the SU binary needed to be updated (got surprised because it didnt say that before i flashed the kernel) i put continue nd it showed me an option to install it through TWRC/CWMR or install normally,so i chose through CWM nd it actually booted me up into CWM but then it said something about a command not working [it was some couple days ago so i cant remember what it said exactly] so i messed around with CWM and tried to installed CyanogenMod which i had downloaded previously, did the signature verification toggle off, but it still said installation aborted because of the command or something... Then i rebooted the phone nd then the problems started, in the superSU app i tried to install normally but it said installation failed... Got the root checker nd said su found in /sbin /system/bin and /system/xbin but i had no root access so i panicked nd tried to root it again with Framaroot, it said success nd i rebboted but it didnt work. I ran the root checker again nd it was the same. I tried to go back to a backup i did when i only had root without the kernel but(which by the way by the end of the backup it said couldnt make md5 sums)but idk why but it took me to the stock android recovery so i couldnt make a restore. I felt trapped cs i couldnt go back to before i had the kernel. With no root access i couldnt also do the restore to the stock kernel(SGS Kernel Flasher app) because i made a backup of it in case something went wrong.. Unfortunately it did so now with no root access i cant really do nothing anymore... I was thinking of using odin to go back to its original state, but then i remembered that it was impossible because odin never recognized my phone while in download mode... Im short in options on what to do please help, im still a noob

Can you try to do a factory reset from the stock recovery and start over?

Mr_You said:
Can you try to do a factory reset from the stock recovery and start over?
Click to expand...
Click to collapse
Yes, thats exactly what i did two times but it didnt work because once you flash something theres no way to go back unless you have a backup and a way to restore it or is there a way i dont know of?? I also checked right after the factory reset in the settings nd it still had the same kernel, and the root checker still said the su binaries were installed in the 3 places i mentioned earlier nd still without root access

TheKillah512 said:
Yes, thats exactly what i did two times but it didnt work because once you flash something theres no way to go back unless you have a backup and a way to restore it or is there a way i dont know of?? I also checked right after the factory reset in the settings nd it still had the same kernel, and the root checker still said the su binaries were installed in the 3 places i mentioned earlier nd still without root access
Click to expand...
Click to collapse
EDIT: If you have tried this procedure on a Galaxy S3 then I would suggest this discussion be continued on the appropriate forum.

Mr_You said:
EDIT: If you have tried this procedure on a Galaxy S3 then I would suggest this discussion be continued on the appropriate forum.
Click to expand...
Click to collapse
No, lets get this straight. I already rooted my gs3 a long time ago nd i didnt use this procedure with it. I used this procedure with my Epic

TheKillah512 said:
No, lets get this straight. I already rooted my gs3 a long time ago nd i didnt use this procedure with it. I used this procedure with my Epic
Click to expand...
Click to collapse
I assume you've already tried uninstalling any SU-type packages?

Mr_You said:
I assume you've already tried uninstalling any SU-type packages?
Click to expand...
Click to collapse
Yes i did.. In the SuperSU app in the settings section it has an option to Full Unroot, nd i think it works but it has to reboot, and at the time of reboot, the kernel overrides it and gets rid of any modifications like getting unrooted..
Looks like im going to have to bear with this nd just leave it like that, besides i already have a rooted gs3

TheKillah512 said:
Yes i did.. In the SuperSU app in the settings section it has an option to Full Unroot, nd i think it works but it has to reboot, and at the time of reboot, the kernel overrides it and gets rid of any modifications like getting unrooted..
Looks like im going to have to bear with this nd just leave it like that, besides i already have a rooted gs3
Click to expand...
Click to collapse
So your are running CleanGB? When you open ROM Manager and select "Boot into Recovery" does it boot into CWM v3 and are you able to flash CWM v5 or do you still get the error?

Mr_You said:
So your are running CleanGB? When you open ROM Manager and select "Boot into Recovery" does it boot into CWM v3 and are you able to flash CWM v5 or do you still get the error?
Click to expand...
Click to collapse
Yes i am running CleanGB nd when i use rom manager and select "Boot into Recovery" it does nothing because i dont have root access and that means it doesnt have permissions to boot into recovery, however i did also try to manually boot into recovery but it took me to the stock recovery.. Is this supposed to happen??

TheKillah512 said:
Yes i am running CleanGB nd when i use rom manager and select "Boot into Recovery" it does nothing because i dont have root access and that means it doesnt have permissions to boot into recovery, however i did also try to manually boot into recovery but it took me to the stock recovery.. Is this supposed to happen??
Click to expand...
Click to collapse
Yes that is normal.
I see you say you tried reinstalling Framaroot, but try reinstalling again. But don't reboot. Afterwards go straight into ROM Manager and select "Boot into Recovery" and if rooting was successful I believe it should boot into CleanGBs CWM v3 recovery.

It did boot up into CWM v3 nd i tried to flash the CWM v5 but there were these weird things, look ill show u a picture of it.
Sent from my SPH-L710 using XDA Premium 4 mobile app

TheKillah512 said:
It did boot up into CWM v3 nd i tried to flash the CWM v5 but there were these weird things, look ill show u a picture of it.
Click to expand...
Click to collapse
For some reason all the forums posts images are broken for me. It seems to be a 404 error.
Ok lets try this:
Make sure you are rooted (install Framaroot again if you need to, don't reboot) and start SGS Kernel Flasher and flash your backup backed up stock kernel and reboot. Then try following the procedure again from the top as described to try to install CWM. Rebooting your stock kernel may or may not fix these issues. If it doesn't then it may require finding a way to fix it via a Terminal app or other method.

I seem to be rooted in some ways but not in others
I installed Framaroot and it claimed success. However, that doesn't seem to be true according to the Root Checker app. I removed Framaroot, rebooted, reinstalled, and reran it with no difference. But what's weird is the first time it seemed to work, so I went ahead and tried to flash CleanGB and it worked. I'm currently running CleanGB.
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!

cdupree said:
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!
Click to expand...
Click to collapse
I would try reinstalling Framaroot (and don't reboot) then: Start ROM Manager->Reboot into Recovery

cdupree said:
I installed Framaroot and it claimed success. However, that doesn't seem to be true according to the Root Checker app. I removed Framaroot, rebooted, reinstalled, and reran it with no difference. But what's weird is the first time it seemed to work, so I went ahead and tried to flash CleanGB and it worked. I'm currently running CleanGB.
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!
Click to expand...
Click to collapse
Thats exactly what is happening to me too, friend...
Sent from my SPH-L710 using XDA Premium 4 mobile app

TheKillah512 said:
Thats exactly what is happening to me too, friend...
Click to expand...
Click to collapse
Sorry you're mistaken. You just posted a pic of CWM v3. So your "Reboot into Recovery" from ROM Manager worked.
Did you try what I suggested here to fix your errors?

Any one updated their nexus 4 to 4.4.3 yet? any issues?

So far I found out that if you flash Franco's kernel you will break WiFi. Any other I should know?

Fuzzy Taco said:
So far I found out that if you flash Franco's kernel you will break WiFi. Any other I should know?
Click to expand...
Click to collapse
For now i suggest stick to stock ! or else mod your stock 4.4.3 kernel using Dsixda's Android Kitchen....
or else wait for developers to upload new kernels !
otherwise no issues, performance got a bit low n battery life got better

I just did, via fasboot from Google's image. I don't have a working wi-fi now... Logged on 3G, but then automatic restore starts downloading apps which is not cool on my 3G. Also my N4 is not seen as 8GB, which is not a biggie, has happened before.

Nope, didn't work. Can't figure out why.
So I downloaded the factory image, unzipped it as I always used to, then run the "flash-all.bat" script. And I get this message:
error: cannot open radio-<rest of file name>
The same goes for all files except for the bootloader.
Bootloader is unlocked, was running stock until recently, then used CM for a while, now trying desperately (and in vain) to go back to stock.
Any help would be appreciated. No amount of searching seems to be taking me anywhere.
(Before you ask: I verified MD5 to make sure the file wasn't corrupted; there was no issue on that end.)

kittuboy said:
So I downloaded the factory image, unzipped it as I always used to, then run the "flash-all.bat" script. And I get this message:
error: cannot open radio-<rest of file name>
The same goes for all files except for the bootloader.
Bootloader is unlocked, was running stock until recently, then used CM for a while, now trying desperately (and in vain) to go back to stock.
Any help would be appreciated. No amount of searching seems to be taking me anywhere.
(Before you ask: I verified MD5 to make sure the file wasn't corrupted; there was no issue on that end.)
Click to expand...
Click to collapse
before running the *.bat file, you need to do two things to avoid a complete (including your SDCard) wipe.
1. edit the *.bat file with notepad and then delete the "-w" in the last line. This will prevent a fill wipe.
2. cd into the directory where the factory image and *.bat files are located, THEN run the script - this is why your terminal can't find the files to flash.
Hope this helps.

rickbosch said:
before running the *.bat file, you need to do two things to avoid a complete (including your SDCard) wipe.
1. edit the *.bat file with notepad and then delete the "-w" in the last line. This will prevent a fill wipe.
2. cd into the directory where the factory image and *.bat files are located, THEN run the script - this is why your terminal can't find the files to flash.
Hope this helps.
Click to expand...
Click to collapse
The SD card wipe is the least of my worries I have a full backup, so that's fine. Right now I'm trying to get my phone to boot up fully!
I edited the bat file to reflect the correct path. (Put shortcuts to the original adb and fastboot in the folder with the factory images, replace path in bat file and replace fastboot with "fastboot.lnk")
My strong doubt is that there is some issue with the phone. Will try a toolkit and let you know what happens.
UPDATE:
This is seriously good. I used Wug's NR and some fiddling later, all was well. I still suspect the phone, but ehhh.... 4.4.3. Cheers!

kittuboy said:
The SD card wipe is the least of my worries I have a full backup, so that's fine. Right now I'm trying to get my phone to boot up fully!
I edited the bat file to reflect the correct path. (Put shortcuts to the original adb and fastboot in the folder with the factory images, replace path in bat file and replace fastboot with "fastboot.lnk")
My strong doubt is that there is some issue with the phone. Will try a toolkit and let you know what happens.
Click to expand...
Click to collapse
Cool, but that's a very long way to do it. Just hold shift and right click in the folder where the file is "open command window here" and run the *.bat file. No editing or anything needed.

That's why I never use the bat. Just extract and flash all partitions via fastboot.
Sent from my Nexus 4 using XDA Free mobile app

rickbosch: Er, I should probably explain. My adb and fastboot programs (the entire sdk in fact) are deep inside one drive (the G: drive to be precise. Yes. Stop s******ing.) while the factory image is in the C: drive. So just opening a command prompt in the sdk folder will require me to navigate through to the download folder, and vice versa. So I changed the path in the bat, placed shortcuts in the folder and renamed commands to <command>.lnk. And that was all it took. (It's actually much quicker when done )
oxious119: Fastboot kept bawling that it was unable to flash the radio file. That was why I posted here in the first place. I was eventually forced to use a toolkit (Wug's NRT in case you want to know) and thankfully that solved it for me.
What happened was that I had flashed CM, then I could still go into bootloader and recovery modes. I made the mistake of relocking and unlocking the bootloader. This stopped the phone from booting completely. To make matters worse, for some reason, I was unable to flash the radio (though it was perfectly fine) The toolkit, much as I hate to admit it, did what I could not: it got my phone working. May the heavens praise Wug.

My notification led stop working after flash stock 4.4.3 on my nexus 4. I did a clean install, wiping everything 2 times and no success.
I rollback to 4.4.2 and the led is working again.

My N4 reboots while using camera, did clean flash of factory image an factory reset.

Matr1x kernel issue
Matr1x kernel was the best battery saving kernel I've used. It worked excellent till 4.4.2, but now, after updating to stock 4.4.3, wifi breaks down! Doesn't connect at all! Now running on stock kernel and the battery life has again gone to worse! I wish they'd update soon! Waiting for them to release an update!!!

thawfu said:
Matr1x kernel was the best battery saving kernel I've used. It worked excellent till 4.4.2, but now, after updating to stock 4.4.3, wifi breaks down! Doesn't connect at all! Now running on stock kernel and the battery life has again gone to worse! I wish they'd update soon! Waiting for them to release an update!!!
Click to expand...
Click to collapse
Try THIS, should work for Matr1x too.
Tapatalked from my N4

***Some Problems Still Persist***
I flashed the factory image of 4.4.3 available on Google site on my Nexus 4 and to my huge disappointment the battery drain issue was still there and the phone would shutdown when the battery level would reach below 60%
I was on stock 4.4.2 before I updated.
PS : If anyone out here got a fix to this, please tell me.

I've updated my N4 to 4.4.3, and my Galaxy On Fire 2 HD saves won't load I've baked up them via Titanium Backup PRo, but after restore, when I'm trying to load my game it says "an error occured. please try again later"... and I'm afraid I've lost 30h of gameplay :/

valkyrjur said:
My notification led stop working after flash stock 4.4.3 on my nexus 4. I did a clean install, wiping everything 2 times and no success.
I rollback to 4.4.2 and the led is working again.
Click to expand...
Click to collapse
Working again.

@meatboy371, thank you, thank you, thank you ... It worked ...
Sent from my Nexus 4 using XDA Premium 4 mobile app

Hybrid radio
Anyone know if there's a new hybrid LTE radio for this?

jbounds3 said:
Anyone know if there's a new hybrid LTE radio for this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/ref-mako-hybrid-modem-collection-v2-t2412052

I updated a few days ago and flashed fanco kernel #209 and everything seems to be working good! :laugh:

Android 6.0 for Nexus 7(2013) is live! [Root available], [Flashable zips]

EDIT: Flashable zips from AndroidPolice (just flash from recovery) ----> http://www.androidpolice.com/2015/1...gs-android-6-0-marshmallow-nexus-ota-roundup/
Steps:
1) Backup apps and data
2) Make an Nandroid backup
3) Factory Reset (optional but recommended)
4) Download and install Android 6.0 factory image through adb https://developers.google.com/android/nexus/images?hl=en
5) Flash latest TWRP 2.8.7.0 recovery
6) Flash ElementalX kernel 5.0 for Marshmallow or stock rootable kernel from @zaclimon through TWRP http://elementalx.org/devices/nexus-7-2013/ or http://forum.xda-developers.com/showpost.php?p=63158038&postcount=210
7) Flash latest supersu 2.46 zip https://download.chainfire.eu/696/SuperSU
8) Reboot

Hope that someone creates a zip to flash...
My USB port is not reliable, and i'm kind of lazy.

Booting now... I'll report when it boots
Edit: First boot takes even longer than lollipop :/ (~10 minutes)

Just finished flashing the factory image. Waiting for it to boot also.

noahvt said:
Booting now... I'll report when it boots
Edit: First boot takes even longer than lollipop :/ (~10 minutes)
Click to expand...
Click to collapse
I waited about 8 mins. but nothing happend! No "optimising apps/system" message, so I wiped again....
Is that normal?

It booted !!! took what it felt like about 10-15 minutes (wasn't watching the clock, only my Flo's screen). Runing the Setup Wizzard now.
Feels snappy. I will be entertained for the next couple of hours

idCyber said:
It booted !!! took what it felt like about 10-15 minutes (wasn't watching the clock, only my Flo's screen). Runing the Setup Wizzard now.
Feels snappy. I will be entertained for the next couple of hours
Click to expand...
Click to collapse
I hope someone is already working on a custom kernel to support root lol

takes a long time to bootup first then its ok...all animationa re optimised and more of material animations are visible.. just enables system tuner (by pressing and holding settings icon until it spins on the notification tray and removed the aeroplane ,mobile data and torch mode).. i didnt find the restore from old nexus option.. but i did get sync data via bluetooth from existing android device...nice

Can someone test if there is kind of the multiwindow feature that we saw in the M Previews?

I have installed it using the app flashfire beta by chainfire. Still booting up but since it shows the android m boot animation, looks like a success

Installed fine for me, booted in what felt like a normal amount of time.
Problems may have begun trying to root though.
Use NRT... first problem: it didn't actually copy the root files over so when it rebooted into TWRP they weren't there. I just rebooted and manually copied them over, then back into TWRP and I was able to install them. But, now I'm sitting here at the startup animation for about 10 minutes now, far longer than after initial install, so I'm starting to think boot loop.
I'll give it a few more minutes and then re-flash the system partition, should get it working again. NRT naturally doesn't know about this version yet, using the *.*.* option, but I'm starting to get the feeling root isn't straight-up on M. I'll repost if it happens to start up, but anyone else try rooting yet? If so, how'd it go for you?
EDIT: Another thread seems to support the conclusion that root isn't working yet, someone else had a boot loop too (something to do with stock recovery replacing TWRP and TWRP trying to save itself, or some such).

moliverac8 said:
Can someone test if there is kind of the multiwindow feature that we saw in the M Previews?
Click to expand...
Click to collapse
Yes, not enabled by default:
pull build.prop from recovery and change release from user to userdebug
push build.prop
chmod 644 build.prop
reboot device and find it in dev options under drawing

my 32gb nexus7 is showing only 16gb of space...
i see this in other users when lollipop is out...

Flashed insecure boot.img, flashed root = bootloop So I REPEAT ROOT DOES NOT WORK

http://www.androidpolice.com/2015/1...es-are-live-for-the-nexus-5-6-7-9-and-player/
In the comments there are people saying that they're doing this:
"Unlocked bootloader + Change flash script to remove -w = Never wait for OTA again"
What is the remove -w? Apparently it makes it so it doesn't wipe userdata. that would be helpful but how would one accomplish that?

skyrocketeer said:
What is the remove -w? Apparently it makes it so it doesn't wipe userdata. that would be helpful but how would one accomplish that?
Click to expand...
Click to collapse
You just edit the batch file (.bat) or shell script (.sh) that comes with the factory image download with a text editor and remove the '-w' part from the fastboot line.

Waiting to try it using Multiboot (zip image and root)

Looks like we are not getting root until google decides to release the source code, what a bummer...

NO Gallery app as it was in Lollipop, now we need to use Photos ad main app for photos... :/, got old app drawer with black background scrolling is left-right not up-down. Shame they didn't add percentage battery too

Luk45z said:
NO Gallery app as it was in Lollipop, now we need to use Photos ad main app for photos... :/, got old app drawer with black background scrolling is left-right not up-down. Shame they didn't add percentage battery too
Click to expand...
Click to collapse
Hold settings icon in quick settings until it starts spinning and then release, system ui tuner will open, then enable show embedded battery percentage