Related
hello guys, apologies if this has been asked before, I just can't find the answer to this anywhere, not directly anyhow.
anyhow, i'm trying to install cyanogenmod 11 on my note 10.1. I have already done this on my galaxy s 3, so i am basically aware of the process. I have rooted the note,and that works fine. and had initially installed the latest version of CWM, the version recompiled for the note 10.1
i've installed the CM11 and gapps zip files to the root of my sd card (that's internal btw, I don't have a external SD) I can see the file on the device in any file manager when the device is booted up. i can move it, and root browser can see it too.
here's my problem. when i actually boot into CWM to actually install the zips, CWM can't see them. the /sdcard folder has nothing in it. this is the same even if i put the file in another location. but when i boot the device back up, there it is! it hasn't gone anywhere, it just can't be seen when the phone is in CWM mode.
thinking that it might be a issue with CWM, since the version is an unofficial recompiled version, I decided to try TWRP instead, as they have an official version for the 10.1. I installed it through odin, and it works fine, but.... IT HAS THE SAME PROBLEM! it can't actually see the files to install them.
I've even tried running a rom manager on the device. if i load up the rom manager while the device is booted up normally, it can see the files, and when i press to reboot the device into recovery mode to install the files, the device reboots, it enters TWRP, and then gives an error message that basically translates to file not found!!
I just don't understand why it can see the file in normal mode, but not when in recovery, and bear in mind this is BOTH the CM11 zip, AND the gapps zip, so really it's just ALL files it can't see!
can anyone help me with this? sorry to ask, but it's got me
I know it's another L thread but bare with me!
I'd like to figure out (without all the other chat getting mixed up with the other threads) the sdcard missing error issue as it's bugging the hell out of me and others...
disclaimer - yes i know it's a preview! But.... We all have the same device coming from the same firmware to the same firmware...
when I first flashed L from vomer's zip, with the then modified boot.img and su zip everything was fine. I could use the camera, see my files and pictures in the photos app etc.
Then I went back to 4.4.4, ever since if I try to flash L. Either with the new su zip not needed modified boot.img. Or the original way including it. I just get sdcard missing in camera. No files seen in photos or any file exporer.
And I know others have too.
I've tried the 3 different restorecon commands in terminal emulator that's been floating around etc but always nothing..
So what's the defining difference??
Why could i see it fine the first flash but never again since??
I know some have no issues what so ever where as others have had to do full wipes for it to be seen.
But we all have the same phone, same hardware and same firmware??
Sent from my Nexus 5 using Tapatalk
I flashed L, got tired of it, restored my backup 4.4.4 ROM and had no issues. Flashed L again, but this time I didn't restore a backup, just clean flashed my 4.4.4 ROM and now I'm getting the no SD card error as well.
I did the same thing. Ran L for a couple of days, made a backup and restored slimkat just fine. Went to restore L backup and it wouldn't boot and it screwed up my partitions. So now I just backed up my SD card (the one showing my stuff actually in it lol) and will be restoring to stock and starting over tonight to hopefully fix partitioning issue
That's why I use MultiRom
first time I flashed, it was a dirty flash, and all was fine, just the pulldown wouldn't go down all the way. second time i flashed, I "lost" my storage. but I was in recovery(twrp) playing around with their file explorer, and accidentally found all my storage/files. I booted up, used root explorer to move all my files manually from the original location that got moved, to the new location where they should be. everything was fine after.
Don't know y exactly but flashing the user data.img works to get SD card corrected. I'd wipe everything including data then flash vomers zip and the user data.img that's posted I believe on page 23..
momulah said:
Don't know y exactly but flashing the user data.img works to get SD card corrected. I'd wipe everything including data then flash vomers zip and the user data.img that's posted I believe on page 23..
Click to expand...
Click to collapse
I know we can do that. But this is more to figure out why second time flashing screws the internal memory up?
Sent from my Nexus 5 using Tapatalk
Same exact problem as me. @Ben36 I played around with Restorecon /data/media/0/* and it bit me. I wasn't able to boot up in MultiROM. Mananged to boot into 4.4.4 by way of erasing internal ROM. Backed up my install, and flash-all L image.
I'll agree that the Sdcard issue is HELLA confusing. Good thread man.
This is preview software. There is going to be issues. Please use the dedicated thread to discuss: http://forum.xda-developers.com/google-nexus-5/help/android-l-developer-preview-help-t2796217
If you have questions or comments, please PM me or another Mod on this team.
Closed.
Hello,
I recently was having major issues with my os., so I wanted to just share some of the information I found that was scattered all over in several different places. First of all, I had TWRP custom recovery and super su installed. I don't know how to do the following process without it. If you have root, GET TWRP NOW!!!!!! You will hate yourself if you do not have a backup.
In twrp app, under install twrp there is no lg tribute. I used the ls-990 when selecting my phone. It worked for me and looks like ls-660 upside down anyways. I picked the build 2.8.5.0.
Ok, so I downloaded the stock rom. Jmurphy posted in tribute development thread for a virgin mobile stock rom on page 125 (cant post links here yet due to newness.)
When my phone went bad, I booted automatically into recovery. I still have no idea how to get in there when all is well, but an internet search might prove useful. I booted in TWRP automatically.
Ok, one thing to mention about TWRP, It makes recovery folders when you do a TWRP backup. Do a backup on the sd. Even if you lost your os. If just to get the folder structure it makes. I went ahead and put my sd card in my laptop chip reader and navigated to the folder that had my recovery. I unpacked the zip files and overwrote the files with the same names on the sd card in the TWRP backup folder that was created when doing a backup. I then put the sd back into phone and did a recovery after wiping my os (while making sure to mount all the directories in TWRP.)
Afterwards lo and behold, I was into my os again. My phone was harassing me to make an update. I listened and updated. Then I got stuck in a TWRP bootloop.
The cure for this bootloop is a script from twrp terminal.
Carefully enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter
this got me out of the bootloop. I hope it will work for you too. Good luck
Is there any way I can get TWRP 2 for my LG tribute?? I'm on 4.4.2 Kit Kat. Boost Mobile. Ty in advanced##???
I'm trying to get twrp for the lg665 Boost mobile. I rooted on dev with king root but I'm not sure it did a complete root. Root Checker basic says it does but the root Explorer in es file manager won't activate and when using a root Explorer in 3c tools I ran into an issue.
I was trying to replace the platform. xml file to fix the lollipop write to sd issue. I renamed it to platform. old and now I can't rename it again or copy a new xml file to the folder
Do you have SuperSU installed? You would need something to give the root permissions to your file explorer. Also, don't forget to allow access on the Developer Settings.
equitube said:
I rooted on dev with king root but I'm not sure it did a complete root.[/QUOTE ] It doesn't. The bootloader and recovery are still inaccessible. However, with KingRoot you should have the permissions to do what your attempting; (accessing the xml file).
---------- Post added at 05:51 PM ---------- Previous post was at 05:47 PM ----------
I'd make sure to use the version from the KingRoot site: http://KingRoot.net/wap
Click to expand...
Click to collapse
Update:
I replaced the Kingroot with a different root method, an app I found but don't recall. I did put super su on. All worked fime, but I sold that phone a few weeks ago
Sent from my SM-T350 using XDA Labs
I have no OS.
Hermosa_Tabby said:
Hello,
I recently was having major issues with my os., so I wanted to just share some of the information I found that was scattered all over in several different places. First of all, I had TWRP custom recovery and super su installed. I don't know how to do the following process without it. If you have root, GET TWRP NOW!!!!!! You will hate yourself if you do not have a backup.
In twrp app, under install twrp there is no lg tribute. I used the ls-990 when selecting my phone. It worked for me and looks like ls-660 upside down anyways. I picked the build 2.8.5.0.
Ok, so I downloaded the stock rom. Jmurphy posted in tribute development thread for a virgin mobile stock rom on page 125 (cant post links here yet due to newness.)
When my phone went bad, I booted automatically into recovery. I still have no idea how to get in there when all is well, but an internet search might prove useful. I booted in TWRP automatically.
Ok, one thing to mention about TWRP, It makes recovery folders when you do a TWRP backup. Do a backup on the sd. Even if you lost your os. If just to get the folder structure it makes. I went ahead and put my sd card in my laptop chip reader and navigated to the folder that had my recovery. I unpacked the zip files and overwrote the files with the same names on the sd card in the TWRP backup folder that was created when doing a backup. I then put the sd back into phone and did a recovery after wiping my os (while making sure to mount all the directories in TWRP.)
Afterwards lo and behold, I was into my os again. My phone was harassing me to make an update. I listened and updated. Then I got stuck in a TWRP bootloop.
The cure for this bootloop is a script from twrp terminal.
Carefully enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter
this got me out of the bootloop. I hope it will work for you too. Good luck
Click to expand...
Click to collapse
I also have SU super user and TWRP recovery installed, in fact, I've been stuck at TWRP recovery with no OS installed ever since I installed one of the updates on my device. I have an Lg Tribute 1 with an SD card slot. It was (before the OS was wiped) running on v 4.4.2 Kitkat. I've heard that if you have a SD card slot, it should be pretty easy to reinstall your operating system, but so far all the sites I've seen show complicated ways of doing it without using an SD card slot. Do I actually have to bootload my Lg Tribute to install another rom even with an SD card?
By the way, I've already installed the .zip file for Kitkat v 4.4.2, I would really appreciate it if you could show me how to install the operating system using this rom. Thanks!
Recently, I found a repack of Cyanogenmod 12 for the Gionee M3. I decided to install it, but all that happened was that it wiped my system partition and spat out this error:
Code:
"ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:systemset_metadata_recursive: some changes failed"
According to the TWRP file manager, there was nothing at all in the system partition but a folder called "bin" (which I suspect was added when TWRP asked me if I wanted to root it). I went through the installer script, but I was having some trouble because I can't tell what half of it actually does. From what I can tell, though, it copied the releasekey, then formatted the partition, then went through a big long list with "symlink" a lot of times and what looked like a list of every file that would be in the new system partition. It quit, from what I can tell, after it got down to the "metadata" section which began with a "set_metadata_recursive" command.
Does anybody know what this means, and how I can work around it?
(I'd experienced an error with this same ROM before, but it told me to do a factory reset. Now I'm having this error instead.)
Hello,
To better assist you, your thread will be moved to your device forum linked below.
http://forum.xda-developers.com/t/gionee-m3
The experts there may be able to help.
Okay, I've installed PhilZ instead of TWRP and I can now flash Lollipop ROMs. But CyanogenMod is still failing. It still just says (when I try installing SuperSU immediately after flashing) that there is no system or data partition. But the first zip (the Cyanogenmod one) doesn't throw any errors.
I got the zip from blu-dev.com.
Below are links to full backups that can be restored in TWRP for the H910 after the Dirty Santa exploit. This is useful for restoring a bad install once you have access to TWRP. I will outline three methods for install below that will help in putting back the TWRP backups, a good method for installing it, and a few suggestions I have from restoring my device about 10 times now. So without further ado.
UPDATE: I bricked my device and had to send it off for repair (turns out I can't just flash US996 firmware for funsies) I received my phone back with the still rootable OTA 10L and yesterday I rooted it again and uploaded the new firmware. So if you're an AT&T user who wants the second latest update (10M dropped 04-15 but it isn't rootable as far as I know) then you can grab this and run it along with the stock kernel I made a backup of. I'll update the links below to reflect this. Stock 10L kernel located in tips section. Not flashable, you must extract and install as image and immediately install SuperSU 2.79 or greater or your device won't boot!
How to Install and Restore Stock Images and Boot (Kernel) Image
1.) DOWNLOAD - https://www.androidfilehost.com/?fid=673368273298948069 (Updated to 10L) download the file and verify the MD5sum of the zip matches the file you downloaded. (System image link for devs posted at the bottom)
1a) Download the latest SuperSU 2.79 flashable zip from here: http://www.supersu.com/download
2.) EXTRACT --This is not a flashable zip-- extract the zip file wherever you would like so that it can be copied to the device
3.) COPY - The extracted folder to TWRP > BACKUPS > (paste here) on either the MicroSD card (preferable) or internal storage (This will be wiped when you format data)
4.) REBOOT TO RECOVERY - Once the folders are copied to the backup directory you can reboot to TWRP to begin the restore process.
5.) WIPE - This is getting two sections in order to account for two situations
5a) MICROSD - If you have a MicroSD card and copied the restore files to it wipe everything: Data, Cache, Dalvik/ART, Internal Storage, and System.
5b) INTERNAL STORAGE - If you don't have a MicroSD card installed only wipe the following: Data, Cache, Dalvik/ART, and System.
6.) REBOOT TO RECOVERY - Once you have wiped everything, especially if you wiped internal storage, you should reboot TWRP before you start the restore process
7.) RESTORE - Back in TWRP Choose Restore from the main menu and if you can't see your restore file choose "Select Storage" at the bottom and inside that folder uncheck RECOVERY unless you want to overwrite TWRP (which I recommend against).
7a) I would recommend checking the box "Enable MD5 Verification of Backup Files" which is a little slower but ensures a good restoration
8.) SWIPE - Swipe to begin the operation and it will alert you upon completion. You will need a very large amount of space on your card to do it since the system image is split into 3 packages
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo.
10.) REBOOT TO SYSTEM - The phone will reboot itself! Don't panic, this is part of the standard rooting procedure. Now, see tips at the bottom for best performance.
TIPS!
- This is the 10L update stock kernel made during dirty santa method. This kernel has all features working minus the static on boot being gone, but Wifi calling, comfort view, FM radio, etc are fixed using this kernel. https://www.androidfilehost.com/?fid=817550096634762281 (You must flash SuperSU 2.79 or greater after flashing this kernel before you reboot! Not Flashable, must extract)
- To use the above kernel, download his ROM and extract the boot.img file from that archive. Save it to your device, boot to TWRP, choose Install, Install Image, and click the boot.img file. Then choose the checkbox for "boot" and swipe to flash. Really important to install SuperSU again after installing the custom kernel.
- Boot-up static can be cleared by allowing phone to boot to screen off, placing it face down to turn of second screen, and then flipping it back over. Static will be gone until next boot.
- Using fstrim after wiping in TWRP is good for increasing flash drive performance. Go to TWRP > Advanced > Terminal and type fstrim -v /data/
- You can do fstrim on /system and /cache as well to get all three partitions running clean
- Some of the AT&T apps that you can remove with TiBu are tied to bootup. Be careful what you remove if you like to get past the AT&T logo.
- The button combo to get into TWRP from powered off is Vol Down + Power until the LG Logo appears then let go of power and immediately press power again.
- That button combo boots you to a screen asking it you want to wipe your device. Answering 'yes' to both questions boots you to TWRP.
10L System Image Link for ROM creation (In TWRP emmc format): https://www.androidfilehost.com/?fid=745425885120724506
THANKS!
Google - Because, Android
@me2151 for the unlock and root method (and bricking his phone for us; sorry that happened to your device)
@glitschi667 for the work he did on Dirty Santa with me2151
@jcadduono for getting TWRP ready for us despite not having a V20 at all
@Tilde88 for compiling the kernel sources and creating an excellent ROM for all rooted variants of the device!
@EMSpilot for the debug phone!
@elliwigy for helping everyone troubleshoot and test everything recently
If I forgot you, and believe me a lot of people deserve to be here, let me know and I'll add you
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo. [/QUOTE] What exact method of rooting do you mean, without rebooting? Do you mean just flashing SuperSU? Can you clarify? THANKS for everything! Hoping this gets me out of my semi-brick. No matter what I flash...it keeps reverting back to TWRP.
EDIT: I did this, exactly...and yet again...I'm stuck in the phone autobooting back to TWRP. Any suggestions? Is this bricked?
jreed3786 said:
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo. What exact method of rooting do you mean, without rebooting? Do you mean just flashing SuperSU? Can you clarify? THANKS for everything! Hoping this gets me out of my semi-brick. No matter what I flash...it keeps reverting back to TWRP.
EDIT: I did this, exactly...and yet again...I'm stuck in the phone autobooting back to TWRP. Any suggestions? Is this bricked?
Click to expand...
Click to collapse
If you do a battery pull and can get to TWRP you are not bricked. However, I have no idea what you did to get a bootloop. What kernel did you install: the stock one from TWRP or Tilde88's kernel from his ROM? Either way, if you did this:
Wipe > Restore (Boot and System) > Install SuperSU 2.79 zip > Reboot
then you did the correct steps. The issue of not having SuperSU installed on my device was not booting past the LG logo and never rebooting. However, the method I most recently followed was:
Wipe > Restore (boot and system) > Install Tilde88 kernel > Flash SuperSU > Reboot
and my phone has been running extremely well. I need way more info from you before I can help you further.
AlkaliV2 said:
If you do a battery pull and can get to TWRP you are not bricked. However, I have no idea what you did to get a bootloop. What kernel did you install: the stock one from TWRP or Tilde88's kernel from his ROM? Either way, if you did this:
Wipe > Restore (Boot and System) > Install SuperSU 2.79 zip > Reboot
then you did the correct steps. The issue of not having SuperSU installed on my device was not booting past the LG logo and never rebooting. However, the method I most recently followed was:
Wipe > Restore (boot and system) > Install Tilde88 kernel > Flash SuperSU > Reboot
and my phone has been running extremely well. I need way more info from you before I can help you further.
Click to expand...
Click to collapse
Shoot...I think I followed your instructions in Tilde88's thread....and hit reboot instead of flashing his kernel. I then went back in to TWRP to reflash the entire thing...and the kernel...and I was given crap about encryption. Then, that's when the bootloop started. Right now, I'm sitting on TWRP. I've tried flashing everything, per instructions....but I guess, what I'm asking, is...since I'm on TWRP...and it's bootlooping because of encryption...what would you personally do? Shoot...I'll pay ya if you can fix this! LOL. I just really never dealt with the encryption thing until this phone...never really had problems till now.
---------- Post added at 09:28 AM ---------- Previous post was at 09:12 AM ----------
FLASHED EXACTLY THE WAY YOU DID (WITHOUT THE REBOOTING TO RECOVERY IN THE OP)...NOW, IT GETS TO STATIC, THEN LG SCREEN, REBOOTS ONCE TO STATIC THEN BOOTS UP!!! YAY!!! :good::highfive:
I guess there's no need to REBOOT TO RECOVERY if a person faces encryption issues and is trying to fix their phone. Even after decrypting, I came up with issues. Now let's see if this this asks for my PIN on reboot. THAT was another issue!
IT WORKED!!! THANKS! I'LL now try to go back into TWRP and flash the Tilde's boot.img
So...by flashing your STOCK TWRP backup...per your instructions, I was TOTALLY FIXED...I then didn't even flash Tilde88's kernel...I immediately rebooted back to TWRP, and DID NOT WIPE...but immediately flashed his ROM....and BOOM! Google Now/Always On works flawlessly, zero lag! AWESOME!
So, to all that are having issues with no Google Now/Always On...follow this instructional on this thread and DO NOT wipe after flashing Tilde's rom.
BTW, I shot you a PM, bro! :highfive::good:
jreed3786 said:
So...by flashing your STOCK TWRP backup...per your instructions, I was TOTALLY FIXED...I then didn't even flash Tilde88's kernel...I immediately rebooted back to TWRP, and DID NOT WIPE...but immediately flashed his ROM....and BOOM! Google Now/Always On works flawlessly, zero lag! AWESOME!
So, to all that are having issues with no Google Now/Always On...follow this instructional on this thread and DO NOT wipe after flashing Tilde's rom.
BTW, I shot you a PM, bro! :highfive::good:
Click to expand...
Click to collapse
Nothing like some good news to start the day. I wanted to let you know that the reason this worked is that it is essentially a dirty flash that replaces the stock kernel and adds his ROM tweaks into my stock system. So once it had booted and you flashed over it you were able to keep the stock files needed to get screen off Google Now working while adding his audio tweaks and build.prop because they overwrite the stock files. Since my stock files are odexed and his are not I'm not sure how well all your system files will function since they've been overwritten but if you have no issues then no harm, no foul.
I'm glad this got sorted and to anyone else if you follow this guide and you have any confusion about the instructions just do an @AlkaliV2 and I will do my best to help and I will also fix up the guide so that it is less confusing. Just let me know.
Stuck again....in TWRP.
Delete please
Same issue
i followed it to the letter yet i still keep being returned to team win recovery no matter what i do.
Great step by step instructions. Thanks!
sikiro said:
i followed it to the letter yet i still keep being returned to team win recovery no matter what i do.
Click to expand...
Click to collapse
Try booting into your bootloader (fastboot) and type:
fastboot erase misc
fastboot erase cache
fastboot erase fota
fastboot reboot
See if that helps you at all. Make sure you have a valid ROM flashed correctly though.
im having trouble, i downloaded the file, and i put the extracted folder into TWRP>BACKUPS but when i go to restore on TWRP theres no files to be open, am i supposed to keep the file as a zip or?
prlatorre said:
im having trouble, i downloaded the file, and i put the extracted folder into TWRP>BACKUPS but when i go to restore on TWRP theres no files to be open, am i supposed to keep the file as a zip or?
Click to expand...
Click to collapse
I was having the same issue, do a backup(choose something small) from TWRP. It will create the TWRP>Backups Folder for you and then you can place the extracted zip. from this thread into that folder and it will see it.
ajairola said:
I was having the same issue, do a backup(choose something small) from TWRP. It will create the TWRP>Backups Folder for you and then you can place the extracted zip. from this thread into that folder and it will see it.
Click to expand...
Click to collapse
i've tried what you suggested, and still nothing seems to show up, i made a back up in both internal and micro sd
prlatorre said:
i've tried what you suggested, and still nothing seems to show up, i made a back up in both internal and micro sd
Click to expand...
Click to collapse
So you created a backup of let's say the EFS partition in TWRP. You backed it up once to the internal SD card and once to the external sd card. Then you extracted the zip from step one, placed the folder inside of the backups folder and it does not appear?
how can i use this file if i i'm not rooted? My phone is being weird and i would like to reload the stock software on it.
truwrxtacy said:
how can i use this file if i i'm not rooted? My phone is being weird and i would like to reload the stock software on it.
Click to expand...
Click to collapse
You cant all you can do is factory reset on stock
jerrycoffman45 said:
You cant all you can do is factory reset on stock
Click to expand...
Click to collapse
Does the factory reset to stock also reset the recovery? Want to root phone but will most likely trade in to ATT once I'm eligible for upgrade(with trade in).
Manbot27 said:
Does the factory reset to stock also reset the recovery? Want to root phone but will most likely trade in to ATT once I'm eligible for upgrade(with trade in).
Click to expand...
Click to collapse
right now the root method for the h910 does not allow you to go back to stock
My 8gb sdcard ran out of space during step #8. Can I copy the contents of the sdcard to a bigger card and redo the full restoration from step 1?
---------- Post added at 01:27 PM ---------- Previous post was at 01:06 PM ----------
AlkaliV2 said:
So you created a backup of let's say the EFS partition in TWRP. You backed it up once to the internal SD card and once to the external sd card. Then you extracted the zip from step one, placed the folder inside of the backups folder and it does not appear?
Click to expand...
Click to collapse
Having the same issue. I copied the folder over to the microsd card and the folder I copied over isnt showing up in restore. I cant do anything or wipe anything if I cant see a backup right?
Im going to try and do the internal storage copy. No other choice.
cwis said:
My 8gb sdcard ran out of space during step #8. Can I copy the contents of the sdcard to a bigger card and redo the full restoration from step 1?
---------- Post added at 01:27 PM ---------- Previous post was at 01:06 PM ----------
Having the same issue. I copied the folder over to the microsd card and the folder I copied over isnt showing up in restore. I cant do anything or wipe anything if I cant see a backup right?
Im going to try and do the internal storage copy. No other choice.
Click to expand...
Click to collapse
If you create a backup of anything on the Microsd card before you attempt to put the folder in it, it will create the directories for you and all you have to do is copy and paste at that point.