Related
im not sure what im missing- i have smooth maximus x, rom manager, and it has the recovery or whatev- but when i boot into recovery it boots the stock one- wtf! the menu for rom manager is not flashing the img. it says it is. just erased everything for nothing!problem?
If its going to the stock recovery, its working fine! when you are on stock recovery menu, choose install packages (or whatever it is) and that will get you into clockwork recovery.
But its not loading to clockworks revovery. It just goes to standard start up when that option is selected.
correction
Sorry correction- I try that, and it says "signature verififaction failed- installation aborted." Why?
cpkfolief2 said:
im not sure what im missing- i have smooth maximus x, rom manager, and it has the recovery or whatev- but when i boot into recovery it boots the stock one- wtf! the menu for rom manager is not flashing the img. it says it is. just erased everything for nothing!problem?
Click to expand...
Click to collapse
why are you using ROM manager to flash the recovery if your on SMX ? SMX has bali 2.2 in it wich has CWM built into the kernel so your recovery should be the RED voodoo CWM recovery by default. and if stock blue recovery is coming up for some reason yu should be able to reinstall packages cause SMX has the modded stock recovery already
No no no, I'm not on smx- I'm trying to install the darn thing. I'm still on the stock rom. When I boot into recovery there are 4 options-
Reboot now
Wipe data
Wipe cache
Install packages
When selecting install packages, it fails via signature verification. There are no cwm recovery options available, either.
ooh .. your problem is you have to be rooted which im sure you already are ..
then go to the CWM thread in the DEV section and apply the modded recovery to system/bin . this will make the recovery ignore the signature check so you can flash CWM then SMX
use root explorer or adb push this file
http://dl.dropbox.com/u/2993191/recovery
to /system/bin
then put this file on the root of ur sd
http://dl.dropbox.com/u/2993191/update.zip
and put maximus x rom on ur sd
reboot recovery
reinstall packages
now ur in cwm
- Wipe Data/Factory Reset
- Wipe Cache Partition
Go to mounts and storage
UNMOUNT CACHE
MOUNT DATA
MOUNT SDCARD
UNMOUNT SYSTEM
install zip from sd
choose zip from sd
look for maximus x rom install and u should be good
after you flash, go back to mounts and storage (before rebooting) and make sure your mounts look like this
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
this is as easy as i can put it
Thank you very muych for your persistence to help! I am a noob and cannot find the ty button. I'm a newb, I know.HOWEVER....…I am not a newb to this in general, and I have tried that already. I read that forum . Duh!this is what happens when trying to move the file to sys.bin:
Root explorer says:
Paste operation failed-
Does not say why. I found a solution! Another forum says to downgrade to stock recovery e2, then cwm will work. But I have to get odin and crap. So if there is something I'm STILL missing, and can't move the file there for that reason, don't hesitate to enlighten me.
you need to move the modded recovery to /system/bin/recovery, anything that tells you to downgrade is not correct, as we do not have anything to 'downgrade' to. The modded recovery from Krylon does the same thing. you should be following this:
1. download the recovery.zip from krylon
2. extract the .zip and copy the recovery file to your sdcard
3. use root explorer to copy the recovery from the sdcard to /system/bin/recovery
if it fails, make sure that /system is mounted as read write, rather than read only, there should be a button in root recovery to mount read/write.
Thank you sir! I was comitting a syntax error... maybe by attempting to copy the file from the wrong directory. No, the downgrade works... I was reffering to e2 recovery for samsung rather than e3 which requires signature ver. But that takes waaaaaay longer. So thank you. I was trying to copy the whole zip, rather than the actual file because I thought I had extracted it(stupid). But yeah. Ty! Will see if cwm works now.
Glad to hear that it worked for you, let me know how cwm works out for you, as well as whatever parts come after that for you. Don't forget the Thanks button if someone helps you
The files are in their proper places, all is right.
But when I boot into recovery, I am startled with fright!
For its still normal, its still stock-
So help me ill throw this phone like a rock!
Haha. But seriously. Still same issue.
FAILS TO INSTALL ANYTHING
"Signature verification failed- installation aborted."
It seems I will have to do it the hard way by installing e2. This was this issue for the galaxy s.
Why does no one else with a sidekick have to do this!!!!? Why is it not giving y'all signature verification errors! Why is there no video yet?
Sig verification issues relate to the recovery. it should still look like stock, as the original CWM is a fake flash. Make sure you have the cwm update.zip from Krylon's thread in your sdcard.
It is!!!!!! I think I'm going to cry.
Recovery is saved (overwrite) as instructed.
Update is on sd card as instructed.
Can't be corrupted, deleted files and tried again.
Boot into recovery and stock shows (as it should.)
Re-install from package (only option other than data wipe and reboot)
Whole signature failure
Signature verification failure
Installation aborted. :'(
i'll make you a script and a zip of everything to do this for you later, but that won't be until a bit later, still have to drive my girl home. in the meantime, can you try redownloading the cwm from ayo's original post? also, have you tried the rom manager version of cwm?
Roger that.
And it would be greatly appreciated. If it is, however, just another list of the instructions as mentione previously in this thread, or in the original rom post, forget it. But if there's something new then sure. Heck, a video would be great. I'm sure I wouldn't be the only one watching it either. And I will redownload all of it again(non-existant jesus christ) and try again in the meantime. Thank you again for your effort and supporth surely it must be that I am the only on with this issue. So I am unique on xda! Silly video...
i could even go so far as to skype someone to SHOW them ive got it right or what i have done, in which case i would hope for an "ah ha!now that thurz ya problem right thur neow."
Ok, I have a script for you, it's semi-tested? I already have root in my adb, so I can't test it as well, but it should work. let me know what happens. just unzip this, and run the run.bat.
this will reboot you into recovery after it's done, so make sure you're not doing anything on your phone when you run it.
https://sites.google.com/a/stephenduvick.com/www/files/sk4gtestoneclickroot.zip?attredirects=0&d=1
Credit to Noobnl for the original script, and krylon for the fake flash.
So how exactly do I run the run.bat? Its not an exe or script file... is there a command list I need to put in? (Gawd, the last custom rom I installed(cliq xt) was so much easier, before there even was a clockwork mod. It was easier, and that was when it was the hard way!) And my phone is already rooted, sure that doesn't matter though.
Hi,
I checked through many threads to see if anyone had a similar problem but couldn't find anything unfortunately.
Background :
I was running a Lite'ning ROM on my Samsung Galaxy S2. You're probably familiar with this ROM, but for those who aren't it gets flashed with ODIN and comes rooted and pre-installed with CWM.
I forget which version of Lite'ning ROM it was, but I am fairly certain it was pre-1.5 as the bundled CWM was definitely version 3.x.x.x (later versions I found had 4.x.x.x and 5.x.x.x).
I wanted to try a version of GalnetMIUI for something a bit different and hadn't changed ROMs in quite some time, so I booted into CWM 3.x.x.x (maybe 3.0.0.2?) and did a backup to the internal SD. This came in at around 1.4 GB and comprised of 4 files :
cache.img
data.img
nandroid.md5
system.img
I copied these to my PC too, just in case they somehow got erased from my phone.
Once I'd done this, I then copied the new ROM .zip file (latest version of GalnetMIUI) to the root of the internal SD, booted the phone into CWM, wiped user data and Dalvik cache, then proceeded to install it.
The problem :
I can't get my apps or data back. I was under the false impression that my Google account was automatically backing this up for me, and would restore everything once logged in as it had in the past (factory resets etc.). So once this didn't happen, I tried using CWM to revert back to how things were before installing the new ROM but although the restore appears to work I end up with issues.
I've tried a number of different ROMs and they either get stuck in 'boot loops' or a black screen after running through the restore procedure. I've tried restoring just data via the 'Advanced' option but this doesn't help.
I was under the impression that I'd be able to fully restore the ROM backup if I needed to, and have the phone running exactly how it was prior to messing around. It would seem this is not the case.
In desperation I tried flashing every Lite'ning ROM from version 1.0 to 4.2, restoring my backup each time but as mentioned I always get boot issues.
Have I lost my data? I hope not, as I had 'To Do' lists and all sorts of things that would cause problems if they were not retrievable. I realise this is a lack of knowledge and foresight on my part. I'm thinking now that I should have run Titanium Backup prior to this, and not assumed that CWM was going to provide a complete solution.
Hope all this makes sense and if any of you have the time to read through and offer advice it would be greatly appreciated. I am currently running a very pretty and slick GalnetMIUI without any of my data!
Thanks in advance.
download cwm 2.5.x.x its better
[email protected] said:
download cwm 2.5.x.x its better
Click to expand...
Click to collapse
Thanks for that, I'll give it a go tonight after work. Am I right in thinking that if it doesn't work I can extract the individual files and insert them manually to get my app data back?
OK, so after hours of searching I'm still no wiser as to how to install CWM 2.5.1.2
I found a zip file that was apparently version 2.5.1.2 but when I tried to install it from inside CWM 5.0.2.6 (included with GalnetMIUI) it sometimes gives an error, sometimes it reboots CWM and sometimes it simply says it has successfully installed (it lies). No matter what it says or does, it doesn't seem to actually replace version 5.0.2.6 with the older one and every time I do the three-finger boot it loads up the latest version like nothing changed.
I'm just so lost. All I want to do is restore my old backup, get my data back and move on. Please someone help me before I go insane from all this research!
[EDIT] In case any more information is needed, my exact procedure for installing version 2.5.1.2 of CWM went like this :
Download 2.5.1.2 zip file
Copy zip file to root folder on internal SD
Boot into CWM 5.0.2.6
Select "install zip from sdcard"
Select "choose zip from sdcard"
Navigate to 2.5.1.2 zip file, select and confirm
Can anyone help me at all?
In particular I'd like to know how I can downgrade to CWM 2.5.1.2 or similar in order to give [email protected]'s suggestion a go.
Failing that, if anyone has any suggestions whatsoever about how I can get my backup data restored it would be greatly appreciated. After spending some time with MIUI - in particular the Galnet ICS build - I have nothing but praise, but I really have to get my data back!
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Sorry for the delayed reply, for some reason I didn't get an email notification that my thread had been updated.
lowandbehold said:
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Click to expand...
Click to collapse
For some reason, when I select "All ClockworkMod Recoveries" the only two options are 4.0.1.4 and v4.0.1.4. I'll have to look into "fastboot" flashing as I've never heard of that.
By the way, if I boot into CWM via ROM Manager the version that loads is 4.0.1.5, but if I perform the three-button combo when switching my device on I get version 5.0.2.6.
EmoBoiix3 said:
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I didn't, is that something I should try?
Edit - Just tried this and at first it rebooted CWM and the version number hadn't changed. Doing this again yielded me the following error with no change in version number :
Code:
E:Error in /sdcard/CM V 2.5.1.2_update.zip
(Status 0)
Installation aborted.
I found out that I can extract the contents of my backed up .img files using unyaffs.exe.
Unless I'm doing something wrong, it would appear that my backup is corrupt somehow. When trying to extract data.img, it processes for a while and does bring back a lot of files but I also get the following :
Code:
read image file
: Bad file descriptor
read image file
: Bad file descriptor
data.img is around 1.2GB but the files I extract only amount to around 190MB.
It would appear that I don't have my contacts database in there which is annoying as for some reason there were quite a few that didn't get synced to Google's servers.
Hello,
I am unable to load cm10 and I am unsure what I am doing something wrong.
Let me first say, I corrupted all my emmc partitions and with Leapinlar's forum on repair and a personalized zip file, all partitions, with the possible exception of partition 3 are repaired.
When the NC boots now, I go directly into CMR 5.5.04 (again, courtesy of Leapinlar). As for flash files, I have so many versions of the cm10 conversions and they may not be compatible or could be corrupt.
Which versions of CWM, CM10 and gapps should I be using together?
Thanks for all your help!
Ms.Y
msy4moment said:
Hello,
I am unable to load cm10 and I am unsure what I am doing something wrong.
Let me first say, I corrupted all my emmc partitions and with Leapinlar's forum on repair and a personalized zip file, all partitions, with the possible exception of partition 3 are repaired.
When the NC boots now, I go directly into CMR 5.5.04 (again, courtesy of Leapinlar). As for flash files, I have so many versions of the cm10 conversions and they may not be compatible or could be corrupt.
Which versions of CWM, CM10 and gapps should I be using together?
Thanks for all your help!
Ms.Y
Click to expand...
Click to collapse
This is the wrong Q&A section. This is general Q&A. I hate to make you do this, but you need to repost this on the Nook Color Q&A. Then I can help you.
msy4moment said:
Hello,
I am unable to load cm10 and I am unsure what I am doing something wrong.
Let me first say, I corrupted all my emmc partitions and with Leapinlar's forum on repair and a personalized zip file, all partitions, with the possible exception of partition 3 are repaired.
When the NC boots now, I go directly into CMR 5.5.04 (again, courtesy of Leapinlar). As for flash files, I have so many versions of the cm10 conversions and they may not be compatible or could be corrupt.
Which versions of CWM, CM10 and gapps should I be using together?
Thanks for all your help!
Ms.Y
Click to expand...
Click to collapse
just go here and follow the direction: get.cm/
Thread closed, question has been asked in the correct forum.
Hi guys
It has been a long time since my phone has been this bad.
So last night I go to charge my phone because I had ZERO battery. So I turned it on and then plugged it in. The phone booted fine but then I noticed that the screen was not shutting off. I even tried hitting the "Go to sleep" button from the pull down menu and nothing happened. I also realized the phone was not loading my calendar. When I went into the file manager it didn't show SDCARD 1 or 2.
I decided to clear the memory (dalvik + cache) = SAME PROBLEM
I did a factory restore = same problem
Finally I cleared the system = now i have no OPERATING SYSTEM ON THE PHONE
I went to the external sd card and tried to install the latest version of OMNI....IT SAYS IT CANT READ FROM THE SD CARD.
I also tried to copy the file from external sd to internal sd card and it says FAILED
I don't' know what to do...
I am using Team Win Recovery Project 2.6.3.0
I have the latest omni rom on my external sd card. I can see it but install fails.
Please help :crying:
mfisher0 said:
Hi guys
It has been a long time since my phone has been this bad.
So last night I go to charge my phone because I had ZERO battery. So I turned it on and then plugged it in. The phone booted fine but then I noticed that the screen was not shutting off. I even tried hitting the "Go to sleep" button from the pull down menu and nothing happened. I also realized the phone was not loading my calendar. When I went into the file manager it didn't show SDCARD 1 or 2.
I decided to clear the memory (dalvik + cache) = SAME PROBLEM
I did a factory restore = same problem
Finally I cleared the system = now i have no OPERATING SYSTEM ON THE PHONE
I went to the external sd card and tried to install the latest version of OMNI....IT SAYS IT CANT READ FROM THE SD CARD.
I also tried to copy the file from external sd to internal sd card and it says FAILED
I don't' know what to do...
I am using Team Win Recovery Project 2.6.3.0
I have the latest omni rom on my external sd card. I can see it but install fails.
Please help :crying:
Click to expand...
Click to collapse
Calm down dear. Same happened with me. I formatted /system and find that I don't have any operating system in my mobile.
Just pluggin your mobile in recovery mode to your PC. transfer the file-> Flash the ROM-> Gapps -> BINGO..
BTW, wrong area for creating a thread.
Don't worry. Do what D™ said.
Alternatively you can use "adb sideload" method. I used it once with Philz recovery. In sideload method, you won't need to copy the file in Sdcard. File existing on pc can be directly flashed. This would help if you still face problems copying file to Sdcard. Search it on google. You will find steps for it.
A bit more clear please...
D™ said:
Calm down dear. Same happened with me. I formatted /system and find that I don't have any operating system in my mobile.
Just pluggin your mobile in recovery mode to your PC. transfer the file-> Flash the ROM-> Gapps -> BINGO..
BTW, wrong area for creating a thread.
Click to expand...
Click to collapse
Hey
Ok I am a bit calmer knowing I didn't brick my phone or anything...
But when I connect my phone to my computer I know it is connected (I see GTi9103 in device manager with an "!" ) but I cant transfer files.
Could someone provide a link to the adb method or maybe give a bit more advice on this problem..
Thank you guys!
mfisher0 said:
Hey
Ok I am a bit calmer knowing I didn't brick my phone or anything...
But when I connect my phone to my computer I know it is connected (I see GTi9103 in device manager with an "!" ) but I cant transfer files.
Could someone provide a link to the adb method or maybe give a bit more advice on this problem..
Thank you guys!
Click to expand...
Click to collapse
It must installed drivers.. If u cant access the storage, just flash ics via odin and further known actions.
Sent Using my MOTO© G® from Tapatalk Pro - D™
Thanks dude! I will give it a try and post a response! It was just so strange that I couldn't see any of the drives (sdcard 1 or 2) in filemanager. I guess something must have got corrupted? Right now I am trying to push from adb method mentioned from Nikhil.
I am following this procedure.
http://hackerspace.lifehacker.com/how-to-install-a-rom-via-sideload-1505153925
PS. the android SDK is massive!
ADB FAIL
ADB IS WAY TOO complicated for me right at this moment (actually exhausted).
********Can someone provide me with a ICS download link? *******************
I'm going to try out the ODIN method
http://forum.xda-developers.com/showthread.php?t=1406664
again thanks to ALL who are constantly helping out!
mfisher0 said:
ADB IS WAY TOO complicated for me right at this moment (actually exhausted).
********Can someone provide me with a ICS download link? *******************
I'm going to try out the ODIN method
http://forum.xda-developers.com/showthread.php?t=1406664
again thanks to ALL who are constantly helping out!
Click to expand...
Click to collapse
Download Stock Indian ICS
Btw, adb sideload method is as follows.
0. Install adb for windows (assuming you have windows). (There shouldn't be any driver missing)
1. Enter into sideload mode in recovery
2. Open cmd in computer with the directory in which zip file is kept. (shift + right click -> open command prompt here would do)
3. Enter adb sideload xyz.zip
Thats it.
I've tried it with TWRP recovery in my friend's phone. It didnt work. But When I tried with Philz recovery, It worked well.
Anyway, if you are finding it complicated, flash stock ics.
Edit : Did you try "mount usb storage" in recovery? because it is required to do. else computer won't recognize your device.
success!
OK so I successfully flashed via ODIN....Can I directly flash omni now? I am assuming yes...Can I flash it through ODIN?
Also can you recommend any good versions of ICS? It is really quite a bit faster than omni...
AGAIN thank you all
mfisher0 said:
OK so I successfully flashed via ODIN....Can I directly flash omni now? I am assuming yes...Can I flash it through ODIN?
Also can you recommend any good versions of ICS? It is really quite a bit faster than omni...
AGAIN thank you all
Click to expand...
Click to collapse
Omni is best until now.
you can't flash omni via odin. Flash Philz or TWRP first and then flash omni.
Lv5 ZCLPD is best ICS Rom. But I would choose Omni over Lv5,
reinstall twrp?
Nikhil said:
Omni is best until now.
you can't flash omni via odin. Flash Philz or TWRP first and then flash omni.
Lv5 ZCLPD is best ICS Rom. But I would choose Omni over Lv5,
Click to expand...
Click to collapse
Do I need to reinstall TWRP>??
mfisher0 said:
Do I need to reinstall TWRP>??
Click to expand...
Click to collapse
Reinstall!
Not if you already installed it.
Read OP of discussion thread. Instructions are there. You will find everything you need.
ICS will faster for few days and then it slow down.. hang.. GB is best for our device..
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.