[Q] Running Recovery Installer Script - Verizon LG G2

How do I run the recovery installer script? It's a .zip file I downloaded from a link in the Malladus google doc.
I would like to do this in order to flash Malladus 2.0.

jonba said:
How do I run the recovery installer script? It's a .zip file I downloaded from a link in the Malladus google doc.
I would like to do this in order to flash Malladus 2.0.
Click to expand...
Click to collapse
Your original firmware is 11a right? If so, go through the directions in the google doc based on what you have. At the end, if you don't have recovery, use the flashify app to flash the file in the doc (under 9b in the directions)

Related

[Q] root problem

hello
im currently using an android 4.0.3 XXLQ3 rom
my main objective is to install PARANOIDANDROID rom:
http://forum.xda-developers.com/showthread.php?t=2115167
in order to get root+safe kernel + cwm i used phiz recommended method described here:
http://forum.xda-developers.com/showthread.php?t=1901191
after i flashed it i rebooted the device i now have cwm but i do not have root or supersu app and i dont know if im on safe kernel or not
i read on the forum that lq3 room has some sort of a space problem as described here
http://forum.xda-developers.com/showthread.php?t=1329360
saying:
1B.If you want just Root but not kernel, follow this
- Download Root_SuperSu 0.95
-Copy downloaded file to Ext SD card.
-Reboot into recovery (vol up+Home+power)
-Select install zip from ext SD card
-select 'root_SuperSU-*.zip' which you have copied to Ext card above
-Reboot device
-You can see superSU on appl drawer. open it and update.
-Now This will give you only SuperSU not busybox, though application which doesn't depends on system busybox will still works.e.g.Titanium Backup.
-To get full Root+busybox, Download Root_busybox *.zip
-Copy Root_busybox* only to Ext SD card
-Reboot into recovery, Select Install zip from Ext SD card. select Root_busybox* .zip and Flash.
-Done !
PS : If you can't see superSU after flashing above file(sometimes happen if there is too low space like in LQ3 ROM, then use this Root_superSU, followed by same above Root_busybox file.
Click to expand...
Click to collapse
so my questions are:
1. how do i get root from my current state? can i use the root_supersu in cwm instead of stock recover?
2. how can i tell if my kernel is safe atm? phiz is suppose to be safe but maybe if root failed the mmc_cap remove failed too?
soory for the long post
thanks in advance to all the helpers!
what is the name of the kernel( with extension) you flashed and how did you flash it?
nokiamodeln91 said:
what is the name of the kernel( with extension) you flashed and how did you flash it?
Click to expand...
Click to collapse
i flased PhilZ-cwm6-XXLQ3-OXX-3.99-signed.zip
i flashed it using stock recovery as the post described
that is correct file.. if you have cwm then the kernel has been installed... try to flash the kernel again from cwm... then reboot and see for a supersu app..
nokiamodeln91 said:
that is correct file.. if you have cwm then the kernel has been installed... try to flash the kernel again from cwm... then reboot and see for a supersu app..
Click to expand...
Click to collapse
i flashed it again using cwm i didnt see any error
still no root or supersu app i even downloaded root checker app and it says im not rooted
Hmmm. Try with the supersu zip that you mentioned earlier.
Try installing supersu from market (play store) and look if it works
Sent from my GT-N7100 using xda premium
dr.ketan said:
Try installing supersu from market (play store) and look if it works
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
it didnt work installling from the market.
i used Root_SuperSu -freespace and now im rooted
the last question i have now is my kernel safe?
phiz kernel suppose to be safe does super_su somehow overwrite the mmc_cap erase?
If your recovery is philz cwm then you have safe kern l
Sent from my GT-N7100 using xda premium
Nope. It's safe. Kernel is what has the erase command disabled and supersu just installs supersu
Thanks for everyone's help managed to root and install
u can close thread.
Ok

How to install latest GApps.zip on NativeSD ?

As in title.
BornToSowDeath said:
As in title.
Click to expand...
Click to collapse
I install like any zip. in recovery: choose the zip file to install. without rebooting install immediately after xboot.zip (x = is where you installed ROM native sd) for example, if the rom is sboot .... flash sboot.zip.

[Q] Tried to install TWRP, but failure

I tried to install TWRP from Goo Manager. After when the Touchpad rebooted, I had lost my ClockworkMod and there was no TWRP item. The only recovery left was WebOS recovery. Any suggestions?
Thanks
Gil1957 said:
I tried to install TWRP from Goo Manager. After when the Touchpad rebooted, I had lost my ClockworkMod and there was no TWRP item. The only recovery left was WebOS recovery. Any suggestions?
Thanks
Click to expand...
Click to collapse
Extract the zip and place the uImage.TWRP into the boot folder. Delete uImage.Clockworkmod if it's there. Then reboot.
Is there any instructions on how to install CWM or TWRP recovery? I installed milaq's build using instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2542353
But someone I don't have the CWM or TWRP installed. As a result, in the moboot menu, I can't see a reboot into recovery and can't install any updates either.
I just answered that in the above post. Unzip the install zip. Name the image file.... In your case uImage.TWRP copy it into boot folder.
vishnumrao said:
Is there any instructions on how to install CWM or TWRP recovery? I installed milaq's build using instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2542353
But someone I don't have the CWM or TWRP installed. As a result, in the moboot menu, I can't see a reboot into recovery and can't install any updates either.
Click to expand...
Click to collapse
/boot is possibly too full
Either choose CWM or TWRP and remove one or the other (be sure to employ the recovery specific to the ROM... see the specific ROM thread for more info)
You can use 'Root Browser' in ROM Toolbox Lite app (to copy, paste, move, delete uImage files from the recovery zips to or from /boot)
woodytrain said:
/boot is possibly too full
Either choose CWM or TWRP and remove one or the other (be sure to employ the recovery specific to the ROM... see the specific ROM thread for more info)
You can use 'Root Browser' in ROM Toolbox Lite app (to copy, paste, move, delete uImage files from the recovery zips to or from /boot)
Click to expand...
Click to collapse
If /boot has adequate then you may want to to copy the TWRP installer zip file into the /cminstall folder in WebOS and use ACMEInstaller on your PC to reinstall it.

How to correctly install Xposed Installer?

hello devs
i wanted to install xposed installer on htc one m7 . last tme when i did it I stuck in a bootloop and then i had to flash a new rom. so can any one help me to install xposed installer without getting into any trouble.
[*]Download and install this APK - http://loadbalancing.modaco.com/download.php?file=XposedInstaller_2.1.4.apk
[*]In the app do 'Install / Update'
[*]Download this zip file and copy to your internal SD card - http://loadbalancing.modaco.com/download.php?file=xposedinstall-2.1.4.zip (ROMraid)
[*]Install the downloaded zip from your custom recovery
That's it, you're done! To uninstall, use the 'Clean Up' option in the app and then run the uninstall zip from the main Xposed Framework app.
Enjoy!
masterleron said:
[*]Download and install this APK - http://loadbalancing.modaco.com/download.php?file=XposedInstaller_2.1.4.apk
[*]In the app do 'Install / Update'
[*]Download this zip file and copy to your internal SD card - http://loadbalancing.modaco.com/download.php?file=xposedinstall-2.1.4.zip (ROMraid)
[*]Install the downloaded zip from your custom recovery
That's it, you're done! To uninstall, use the 'Clean Up' option in the app and then run the uninstall zip from the main Xposed Framework app.
Enjoy!
Click to expand...
Click to collapse
again got into bootloop and I did all steps correctly
Which ROM are you currently on?
masterleron said:
Which ROM are you currently on?
Click to expand...
Click to collapse
viper 9.0.0
amir_khan007 said:
viper 9.0.0
Click to expand...
Click to collapse
and what framework version did you flashed? Viper 9 is android SDK 21 and the M7 is using an ARM cpu so you must use the sdk21-arm.zip version.
and btw @masterleron linked you an outdated installer (2.1.4). You need 3.0
Official and up-to-date xposed thread and files here. Remove everything you just installed, then install the 3.0-a4 xpsoed installer and then reboot in recovery and flash the xposed-v80-sdk21-arm.zip framework.
alray said:
and what framework version did you flashed? Viper 9 is android SDK 21 and the M7 is using an ARM cpu so you must use the sdk21-arm.zip version.
and btw @masterleron linked you an outdated installer (2.1.4). You need 3.0
Official and up-to-date xposed thread and files here. Remove everything you just installed, then install the 3.0-a4 xpsoed installer and then reboot in recovery and flash the xposed-v80-sdk21-arm.zip framework.
Click to expand...
Click to collapse
Are sure I wont get into a bootloop again
because i have now flashed the rom 3 times once due a "unfornately playStore has stopped" error.
Twice because of bootloops.
amir_khan007 said:
Are sure I wont get into a bootloop again
Click to expand...
Click to collapse
There are always some risks of softbrick/bootloop when modding your phone, its easily recoverable with a simple nandroid backup made before any modification. Learning to mod your phone = sometime making errors = need to reflash. This is the game you agreed to play when you first unlocked your bootloader. The only thing I'm sure is that you were not using the correct installer and possibly not the right framework (you didn't confirmed) and that using the right files should reduce the chances of bootloop

[Solved!] I want to update TWRP, but ...

Hi!
I have a Nook HD+ running CM 12.1 (Android 5.1.1). The tablet is not rooted. Right now I have TWRP v2.7.1.0 installed, but would like to update to a newer version.
Installing v2.7.1.0 was a breeze. I booted into recovery mode (ClockWorkMod at the time), then flashed an Ovation TWRP ZIP file that I downloaded online. Looking for the most recent Ovation version, it seems it's only available as an IMG file. I can't find a version of TWRP more recent than v2.7.1.0 for Ovation in a ZIP format. Since the tablet is not rooted, I can't flash the newer version using Flashify or similar apps (as far as I can tell, that is) since they all require root access. And I can't flash an IMG file with v2.7.1.0, since that feature wasn't included until a later version (v2.8.5.0 I think). Therein lies the problem. I need a newer version to update, but I can't update until I have a newer version!
I've struggled with the suggested methods of installing TWRP from an IMG file, and would really like to simply flash a ZIP file (I'm already pretty good at doing that). So I've come up with a possible method that sounds too easy and too good to be true. Examining the ZIP folder for v2.7.1.0 (using Linux Archive Manager), I can see that there is a recovery IMG file and a folder labeled META-INF. If I replaced the v2.7.10 recovery IMG file with a more recent TWRP IMG file and left the META-INF file as is, would that work? Or, does the META-INF folder only support v2.7.1.0?
Thanks for your help ... and for not laughing at my possibly nutty idea
MaydayMalone said:
Hi!
I have a Nook HD+ running CM 12.1 (Android 5.1.1). The tablet is not rooted. Right now I have TWRP v2.7.1.0 installed, but would like to update to a newer version.
Installing v2.7.1.0 was a breeze. I booted into recovery mode (ClockWorkMod at the time), then flashed an Ovation TWRP ZIP file that I downloaded online. Looking for the most recent Ovation version, it seems it's only available as an IMG file. I can't find a version of TWRP more recent than v2.7.1.0 for Ovation in a ZIP format.
Click to expand...
Click to collapse
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
...
I've struggled with the suggested methods of installing TWRP from an IMG file, and would really like to simply flash a ZIP file (I'm already pretty good at doing that). So I've come up with a possible method that sounds too easy and too good to be true. Examining the ZIP folder for v2.7.1.0 (using Linux Archive Manager), I can see that there is a recovery IMG file and a folder labeled META-INF. If I replaced the v2.7.10 recovery IMG file with a more recent TWRP IMG file and left the META-INF file as is, would that work? Or, does the META-INF folder only support v2.7.1.0?
...
Click to expand...
Click to collapse
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
digixmax said:
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
Click to expand...
Click to collapse
Thanks for your response. You told me exactly what I needed to know.
I have viewed D. Andrei Măceș dropbox in the past, but I neglected to check it for TWRP updates (my bad). I'll keep this in mind the next time I want to explore new possibilities for my HD+.
The idea of creating my own zip was a temptation that I couldn't resist (since I was now feeling confident that I wouldn't brick my tablet, blow up Pittsburgh, or be responsible for something equally catastrophic). So, instead of downloading a zip file from the dropbox, I used Linux Archive Manager (I switched to Linux Mint some time ago to escape the more-frequent-than-I-could-bear crashes with Windows), to delete the file named recovery.img in the v2.7.1.0 zip, then inserted a recovery.img file for TWRP v3.1.1.0 in it's place. It worked perfectly, and I feel like a genius (I'm very easily impressed)!
Thanks for letting me know that my idea wasn't as dumb as I feared it might be.
digixmax said:
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
Click to expand...
Click to collapse
Hello,
I tried using the TWRP 3.0.1.0 - ovation and 2.8.7.5. and they both receive the status 7 error:
"This package is for device: ovation ; this device is .
E: Error in /external+sd/twrp-3.0.1-0-ovation.zip
(Status 7)
Installation aborted"
I currently run on CWM Recovery 6.0.4.6, with cyanogenbootloader, lineage os 14.1. Unfortunately I cannot turn off my device (Nook HD+) no matter what, it keeps turning itself on until it empties battery (if I don't pay attention).
I keep trying to install the zips from CWM Recovery but I cannot do it.
Is there any way for me to install TWRP from CWM?
Thank you
pnkye said:
Hello,
I tried using the TWRP 3.0.1.0 - ovation and 2.8.7.5. and they both receive the status 7 error:
"This package is for device: ovation ; this device is .
E: Error in /external+sd/twrp-3.0.1-0-ovation.zip
(Status 7)
Installation aborted"
Click to expand...
Click to collapse
Did you use one of the flashable TWRP zip files from https://www.mediafire.com/#6a4rivb8kkdfu?
I currently run on CWM Recovery 6.0.4.6, with cyanogenbootloader, lineage os 14.1. Unfortunately I cannot turn off my device (Nook HD+) no matter what, it keeps turning itself on until it empties battery (if I don't pay attention).
Click to expand...
Click to collapse
Did you tried holding down the power button for 30+ sec?
Thank you for the answer.
1. The link doesn't work (https://www.mediafire.com/#6a4rivb8kkdfu?) leads me to an upload page.
2. I tried all the options I could find online. If I let it be for 1 week (I use it for reading and sometimes youtube) it turns itself on at some point and the battery goes empty. And it is so hard to turn it on again. When I plug it for charging the battery and is completely empty, the led stays green - instead of orange - for a long time and is not responsive to anything I do until it reaches 80%+ , so I let it be for 2hrs while plugged.
3. What I try to do is actually root it for overclocking or make it a little bit faster because it lags in every thing I do with it. Although in some variants of the Android which I installed over the years it used to be more responsive.
Unfortunately I cannot root it because CWM doesn't recognize the install of SuperSU zip from Lineage website. Do you have any advice on that?
Thanks
pnkye said:
...
The link doesn't work (https://www.mediafire.com/#6a4rivb8kkdfu?) leads me to an upload page.
Click to expand...
Click to collapse
Try this link: https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook+HD+
digixmax said:
Try this link: https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook+HD+
Click to expand...
Click to collapse
Thank you very much! You really helped me with this one!
I just did it! Flashed it with the cwm.flashable.twrp zip from your link!
I run now the TWRP 3.0.1-0.
I couldn't flash any higher versions (3.2.x) directly from this installed version
Anyway my booting time is faster and so far (1min time) the turning on/off procedure works normal, as it should be.
What lineage OS version is the best one for the nook hd+?
I just installed the 14.1 version from the lnos-ovation-ota-NJH47F.181223.zip found at: https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
This version, however, has landscape mode as default viewing mode and it keeps spinning here and there.
At the moment I find myself in the latest stage of my process: rooting the device so I can try and overclock it.
Trying to install the official lineage "addonsu-14.1-arm-signed.zip" , from their website (https://download.lineageos.org/extras), but it doesn't work.
I mean it installs it successfully in the TWRP recovery. It is enabled in the developer options for both Apps and Adb. But the root checker app says it is not rooted.
Is there a proper way to root it? If so could you please share a solution when you have time?
Also any ideas on how to properly overclock (make the tablet a little snappier, besides the animation scale option from dev options)?
Cheers!
pnkye said:
I just did it! Flashed it with the cwm.flashable.twrp zip from your link!
I run now the TWRP 3.0.1-0.
I couldn't flash any higher versions (3.2.x) directly from this installed version
Click to expand...
Click to collapse
There should be an option in TWRP to "flash image" you can use to directly flash .img binary of a newer TWRP version.
What lineage OS version is the best one for the nook hd+?
I just installed the 14.1 version from the lnos-ovation-ota-NJH47F.181223.zip found at: https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
This version, however, has landscape mode as default viewing mode and it keeps spinning here and there.
Click to expand...
Click to collapse
You should be able to disable auto-rotation in Settings->Display.
At the moment I find myself in the latest stage of my process: rooting the device so I can try and overclock it.
Trying to install the official lineage "addonsu-14.1-arm-signed.zip" , from their website (https://download.lineageos.org/extras), but it doesn't work.
I mean it installs it successfully in the TWRP recovery. It is enabled in the developer options for both Apps and Adb. But the root checker app says it is not rooted.
Click to expand...
Click to collapse
Try disabling and exit Settings->Developer Options, then come back and re-enable it.
digixmax said:
There should be an option in TWRP to "flash image" you can use to directly flash .img binary of a newer TWRP version.
You should be able to disable auto-rotation in Settings->Display.
Click to expand...
Click to collapse
My device is with default landscape. If I disable it it stays in landscape and never goes to portrait.
digixmax said:
Try disabling and exit Settings->Developer Options, then come back and re-enable it.
Click to expand...
Click to collapse
It still doesn't work.
Thanks for the overall guidance!

Categories

Resources