THIS IS NOT MY WORK. I AM MERELY PUTTING IT HERE FOR OTHERS TO SEE, THE WORK IS FROM USER 'Hashcode' AND THE OP IS HERE.
==============================================================================================================
*** DISCLAIMER ***
This may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad, the community will feel bad, and hopefully we'll find a way to get you going again. But, the very nature of this project involves a certain amount of risk taken by YOU. By using the project, you've accepted that fact.
NOTE:CURRENTLY THERE IS A KNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
CURRENT PROJECT STATUS: BETA RELEASE
KNOWN ISSUES (PLEASE READ CAREFULLY):
For locked users: there is a process that happens when you click "Reboot Recovery" from the APK or use the "Recovery" button during the splash screen. Safestrap checks the device for write_protect and if it's enabled will automatically reboot the device to recovery (write_protect disabled) mode. You will see this as a screen with ORANGE text reading: "PLEASE WAIT THE DEVICE IS REBOOTING TO RECOVERY". Followed by the bootloader screen again. You may also see the splashscreen for Safestrap. If you see the splashscreen hit "Recovery" again. It's supposed to automatically take you to into recovery, but it doesn't work correctly yet.
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (2-3 depending on your internal space size) for flashing ROMs. These ROM-slots allow for 3 different sizes of /data partitions: 1GB, 2GB and 3GB. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Be Rooted (Look for PWNMYMOTO by JCase)
Reboot into the Write-Protect Off (recovery) Android OS
Make sure in "Settings" -> "Security" you have "Unknown Sources" checked
Download the Safestrap APK to your device
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM". Press
"RECOVERY" to enter Safestrap Recovery or "CONTINUE" booting.
If you're in a ROM, you can install the Safestrap APK and use the "Reboot Recovery" button.
WHAT SHOULD I DO NOW THAT I HAVE CUSTOM RECOVERY?
Make a backup while on the STOCK rom slot
Create a new rom-slot (and leave it active)
Restore your backup to the new rom-slot
Flash, tweak, mod, theme till your hearts content
DOWNLOADS:
ATTENTION: IF UPGRADING FROM v3.62 or EARLIER USE "REMOVE RECOVERY" IN THE APK BEFORE INSTALLING THE NEW VERSION. I CHANGED THE HIJACK IN v3.63 -- DIFFERENT FILES ARE BEING CHANGED NOW.
MAXX / ULTRA:
http://goo.im/devs/Hashcode/motox/xt1060-vzw/safestrap
note: this does work with our devices but was designed for the motox xt1060-vzw
Click to expand...
Click to collapse
As of version 3.6x, Safestrap Recovery is now based on TWRP 2.6.3.x. For more on TWRP you can visit their website: http://www.teamw.in/ Feel free to donate to them.
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Contributors
Hashcode (Safestrap), DeesTroy & TeamWin for such an awesome recovery in TWRP.
Like I said in th OP, this is not my work and honestly, I do not normally make posts like this.
I use the MAXX as my personal phone though, there is no dedicated MAXX section so I frequent this one and was curious as to why there wasn't a thread that made this option plain to see, so here it is.
Does this version break Bluetooth connectivity?
53N7 FR0M M4 DMAXX V1A 7A9A7A7K
inkdaddy66 said:
Does this version break Bluetooth connectivity?
53N7 FR0M M4 DMAXX V1A 7A9A7A7K
Click to expand...
Click to collapse
no.
Thank you! I'll be getting this going later
53N7 FR0M M4 DMAXX V1A 7A9A7A7K
Hmmmm might have to give this a go after work. I need this to install email with no exchange security.
Sent from my XT1080 using xda app-developers app
Went for it. Everything is as good as pie. I patently waited for this. Now some more waiting for an unlocked bootloader. Thanks for the links OP
53N7 FR0M M4 DMAXX V1A 7A9A7A7K
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
known issue with safestrap? Or possibly something else?
53N7 FR0M M4 DMAXX V1A 7A9A7A7K
---------- Post added at 06:21 AM ---------- Previous post was at 05:28 AM ----------
Disregard. Confirmed as a separate issue. Restored backup and found it was an inverted app that I had installed. Google now works properly now.
53N7 FR0M M4 DMAXX V1A 7A9A7A7K
inkdaddy66 said:
known issue with safestrap? Or possibly something else?
53N7 FR0M M4 DMAXX V1A 7A9A7A7K
---------- Post added at 06:21 AM ---------- Previous post was at 05:28 AM ----------
Disregard. Confirmed as a separate issue. Restored backup and found it was an inverted app that I had installed. Google now works properly now.
53N7 FR0M M4 DMAXX V1A 7A9A7A7K
Click to expand...
Click to collapse
Good deal!
Sent from my XT1080 using xda app-developers app
I think it was the inverted play store that I flashed. I was also having errors when trying to like videos on YouTube.
53N7 FR0M M4 DMAXX V1A 7A9A7A7K
So just to confirm; you do not need a developer device for this, and also that it works on droid maxx yes?
Kickbut101 said:
So just to confirm; you do not need a developer device for this, and also that it works on droid maxx yes?
Click to expand...
Click to collapse
Correct x2
53N7 FR0M M4 DMAXX V1A 7A9A7A7K
It's actually not intended for developer devices at all.
Can someone attach the vzw apk? Link is dead.
Sent from my XT1080 using Tapatalk 2
xjack said:
Can someone attach the vzw apk? Link is dead.
Sent from my XT1080 using Tapatalk 2
Click to expand...
Click to collapse
+1
How is this working for XT1080M? Worth the install?
Is backup working?
Sent from my XT1080 using Tapatalk
Working perfect for me. Yes. Backup does work. Only problem I had was Google Now not working but that was because I was flashed an inverted app that conflicted with it. Restored my backup and I was good to go
53N7 FR0M M4 DMAXX V1A 7A9A7A7K
No link for VZW yet?
Sent from my XT1080 using xda app-developers app
See post #293 for mirror. I grabbed 3.63a and its working fine.
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v363-2013-10-14/page-30
Sent from my XT1080 using Tapatalk 2
Post need updated with 3.63a
<:GeeK:> said:
THIS IS NOT MY WORK. I AM MERELY PUTTING IT HERE FOR OTHERS TO SEE, THE WORK IS FROM USER 'Hashcode' AND THE OP IS HERE.
==============================================================================================================
*** DISCLAIMER ***
This may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad, the community will feel bad, and hopefully we'll find a way to get you going again. But, the very nature of this project involves a certain amount of risk taken by YOU. By using the project, you've accepted that fact.
NOTE:CURRENTLY THERE IS A KNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
CURRENT PROJECT STATUS: BETA RELEASE
KNOWN ISSUES (PLEASE READ CAREFULLY):
For locked users: there is a process that happens when you click "Reboot Recovery" from the APK or use the "Recovery" button during the splash screen. Safestrap checks the device for write_protect and if it's enabled will automatically reboot the device to recovery (write_protect disabled) mode. You will see this as a screen with ORANGE text reading: "PLEASE WAIT THE DEVICE IS REBOOTING TO RECOVERY". Followed by the bootloader screen again. You may also see the splashscreen for Safestrap. If you see the splashscreen hit "Recovery" again. It's supposed to automatically take you to into recovery, but it doesn't work correctly yet.
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (2-3 depending on your internal space size) for flashing ROMs. These ROM-slots allow for 3 different sizes of /data partitions: 1GB, 2GB and 3GB. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Be Rooted (Look for PWNMYMOTO by JCase)
Reboot into the Write-Protect Off (recovery) Android OS
Make sure in "Settings" -> "Security" you have "Unknown Sources" checked
Download the Safestrap APK to your device
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM". Press
"RECOVERY" to enter Safestrap Recovery or "CONTINUE" booting.
If you're in a ROM, you can install the Safestrap APK and use the "Reboot Recovery" button.
WHAT SHOULD I DO NOW THAT I HAVE CUSTOM RECOVERY?
Make a backup while on the STOCK rom slot
Create a new rom-slot (and leave it active)
Restore your backup to the new rom-slot
Flash, tweak, mod, theme till your hearts content
DOWNLOADS:
CHOOSE YOUR SAFESTRAP FILE BY MODEL / CARRIER BELOW:
LATEST FILE: Safestrap-XT####-3.63.apk (updated 10/14/2013)
ATTENTION: IF UPGRADING FROM v3.62 or EARLIER USE "REMOVE RECOVERY" IN THE APK BEFORE INSTALLING THE NEW VERSION. I CHANGED THE HIJACK IN v3.63 -- DIFFERENT FILES ARE BEING CHANGED NOW.
[XT1060] Verizon Wireless:
http://goo.im/devs/Hashcode/motox/xt1060-vzw/safestrap
[XT1058] AT&T:
http://goo.im/devs/Hashcode/motox/xt1058-att/safestrap
As of version 3.6x, Safestrap Recovery is now based on TWRP 2.6.3.x. For more on TWRP you can visit their website: http://www.teamw.in/ Feel free to donate to them.
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Contributors
Hashcode (Safestrap), DeesTroy & TeamWin for such an awesome recovery in TWRP.
Click to expand...
Click to collapse
Post should be updated with a link for safestrap 3.63a for the droid ultra/maxx, hashcode explained that the system partition on the ultra/maxx was bigger than the moto X, which is why he created 3.63a for the ultra/max.
Related
ClockworkMod Recovery for Samsung Galaxy S2 HD LTE (SGH-I757M)
Bell Canada released the Galaxy S2 HD LTE (SGH-I757M), which is a slight upgrade from its original Galaxy S2 GT-I9100M released the summer before, with now a bigger display and HD resolution. I have ported ClockworkMod (CWM) Recovery to the SGH-I757M, which allows you to make backups/restores of your device and also to flash custom ROMs and ZIPs.
(If you still don't know what ClockWorkMod Recovery or a custom recovery menu is, Google it or search XDA.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
WARNING! Do not flash this to a different device model from the one it's meant for - YOU MAY BRICK YOUR PHONE IF YOU DO. It will not work with the other Galaxy S2 iterations like the I9100, so don't try it with the Bell Galaxy S2 I9100M (non-HD). DO NOT flash it on the Asian variant of the GS2 HD (SHV-E120) either, as it uses slightly different internal hardware - the ROM will be unstable and the phone component will not work. If you are sure you have the CANADIAN Bell Galaxy S2 HD LTE (SGH-I757M), then click on the button below:
(For questions about ClockworkMod for the SHV-E120, contact skysbird on Twitter or GitHub. I will not discuss that device in my thread, it's not compatible with this ClockworkMod.)
NOTE FROM dsixda:
I SOLD MY SGH-I757M IN SEPTEMBER 2012. PLEASE DO NOT MESSAGE ME FOR TECH SUPPORT. DIRECT YOUR QUESTIONS TO THIS THREAD ONLY. STOCK FIRMWARE AND MORE ARE IN POST #3.
DOWNLOAD HERE
Go to the Dev-Host link above and navigate to the "Bell SGS2 HD LTE" folder, and then the "clockworkmod" sub-folder to access the files required for the following steps. Please read the installation instructions carefully.
Support my work:
DONATE / FOLLOW ME
To install CWM Recovery:
If you don't already have Odin, download it from the link above, and extract the zipped file to a folder. Ensure both the .EXE and .INI file have been extracted.
Download the TAR file for ClockWorkMod Recovery (e.g. cwm_recovery_xxxx.tar, or if you want the version that uses finger touch input: cwm_touch_recovery_xxxx.tar). Do not extract the file out of it, keep the TAR file as it is.
Turn off the phone
Put it into Download mode by pressing Power and Volume Down at the same time. The device will vibrate and soon you will see a Warning screen, where you will need to press Volume Up to enter Download mode. (NOTE: You can also use the Galaxy S2 USB Jig to go straight to Download mode. I recommend you get one from eBay just in case.)
While in Download mode, start up Odin and connect your phone to the PC via USB. You should see a status message in Odin saying your device was "added".
In Odin, press the BOOTLOADER button and select the CWM TAR file you just downloaded.
In Odin, press Start. Your custom recovery should be flashed completely in a span of a few seconds, and then it should say "PASS" in Odin. If it doesn't finish and is stuck, then your file was either corrupted during the download or there was an MD5 mismatch (this is not a regular TAR file, it has an MD5 signature).
IMPORTANT: If you downloaded the "Touch" version of CWM, *avoid* using the "Reboot to Recovery" option in the ROM or apps like Quick Boot to boot into recovery. I have found that using such apps with Touch Recovery causes every subsequent reboot to go back into recovery rather than to the system. If you are stuck in this state, re-flash the recovery image so that it boots back to the system. Next time, if you want to get into recovery, use the button combination mentioned in the steps below instead. If you have the non-touch (normal) version of CWM, this issue won't happen.
To enter CWM Recovery:
Turn off the phone
Hold down the Power button to turn the phone on, and then immediately hold down Volume Up + Volume Down at the same time.
The device will then show the word "Samsung". Let go of the buttons at the exact moment you see this.
If you did it on time, you will enter CWM Recovery. Use the Volume keys to move up and down, and press Power to select. The capacitive buttons do this: Menu = DOWN, Back = BACK to main menu, Search = SELECT
NOTE: If you had flashed CWM but are still seeing the stock recovery image, then click here for a solution.
Make sure you make a Nandroid backup of everything the first time you use custom recovery. The backup will be stored under the 'clockworkmod' folder of your SD card.
UPDATE: I sold off my device back in September 2012, so please do not message me for tech support. Use this thread instead, which is its intended purpose. Thanks!
To root your device through CWM:
This step is only if you want to root the stock firmware that is currently on your device. If you are going to flash a ROM like CyanogenMod, then you can skip this section, since most custom ROMs already have root installed.
You need to first download root_sgs2hdbell.zip from the Dev-Host site linked above. Copy it to your device's internal or external SD card.
Then go back into CWM and flash the ZIP. You should now be rooted, you don't need to do anything else to your stock ROM.
Factory/stock firmware images, custom ROMs, change log, source code, acknowledgements, etc.:
See next two posts!
.
Change Log
Version 6.0.1.1 (the first Touch version for SGH-I757; August 16, 2012)
Built using ClockworkMod Recovery Builder (also required hex-edit of ramdisk load address)
Version 6.0.1.1 (Non-Touch version - August 15, 2012)
Latest version of CWM, updated from CyanogenMod sources
Version 5.5.0.4b (July 3, 2012)
In kernel, enabled CONFIG_MMC_BLOCK_BOUNCE which helps with SD read/write performance (may fix SD card flashing issues)
Version 5.5.0.4a (June 22, 2012)
Using ICS kernel based off MSM 8660 sources
Fixed issue where if someone uses an app to reboot into recovery, the device will never be able to reboot back into system (would always boot into recovery unless you re-flash recovery image). "Boot to recovery" apps will now work.
Contains proper device name info (SGH-I757M, not full_galaxys2hdbell)
Version 5.5.0.4 (June 12, 2012)
First build based off stock Gingerbread kernel
Custom ROMs:
There is already development undergoing for this device:
If you only want a rooted stock Gingerbread or ICS ROM with all the Bell apps removed, see the Dev-Host link in post #1, under the SGS2 HD LTE / Other Custom ROMs folder.
markdexter's DexROM - strips down the above ROM even more and adds a theme
Try my CyanogenMod 9 - this is stock Android 4.0 (Ice Cream Sandwich). It is good enough to use every day.
Try my CyanogenMod 10 - this is stock Android 4.1 (Jelly Bean).
Copy the ROM to your SD card and then go back into CWM and flash the ZIP.
Factory images and related files:
If you want to reset the flash counter found in Download Mode so that it doesn't mention a custom ROM was flashed or was flashed multiple times, then try this mod, courtesy of mangelok: Flash counter reset
For the original stock 2.3.6 and 4.0.4 firmware for SGH-I757M, see the Dev-Host link in post #1 - under the "SGS2 HD LTE / factory images" folder. You can flash this in Odin to restore your phone to original state. Just do a factory reset of your phone, then open Odin and place the tar.md5 file in the PDA slot and then start the flash. This also flashes the stock recovery image.
If you just want the Bell ICS modem (MUGLH2), it is found in the 'factory images' folder. You need to flash this under CWM.
There is also a stock 2.3.6 firmware + stock recovery, which has Superuser (root) files injected in it, so it's already rooted (but without CWM). It's at the Dev-Host link in post #1 (rooted_I757MUGLCA_I757MOYCLCA_I757MUGLCA_HOME .tar)
If you just want to go back to stock recovery, download the stock recovery image (stock_gb_recovery.tar) at the Dev-Host link and repeat the steps in post #1 for installing the recovery image (but this time use stock recovery instead of custom recovery).
More discussion:
Participate in the Bell Samsung Galaxy SII HD LTE user group on xda-developers
Other useful links:
Mount points and other info for this device
Original Discussion on rooting this device
All my source files for this device at GitHub, including those for ClockworkMod, ICS kernel, and CM9 device tree ("celoxhd").
Android Kitchen by dsixda - SGH-I757M is now supported
Article about this recovery image on the XDA portal - by willverduzco
Acknowledgements:
Thanks to Koush (for ClockworkMod), Cyanogen, Chainfire (inspiration), rxulan (link to rooted stock firmware), adlx.xda (for the custom graphics help), testers (you know who you are) and my awesome Twitter followers (continual help and encouragement).
One more
Link to Modded Bell Rom Thread: http://forum.xda-developers.com/showthread.php?p=27331138#post27331138
Android 4.0?
Is it possible that you could make an android 4.0 Rom for this device since bell seems to take their sweet time rolling out ICS to phones. Also thanks for porting CWM to my phone I've been looking everywhere for it.
B.Moreira said:
Is it possible that you could make an android 4.0 Rom for this device since bell seems to take their sweet time rolling out ICS to phones. Also thanks for porting CWM to my phone I've been looking everywhere for it.
Click to expand...
Click to collapse
Bell will likely release it at the end of the month, I'm probably not able to do any work on CM9 due to health and family reasons.
dsixda said:
Bell will likely release it at the end of the month, I'm probably not able to do any work on CM9 due to health and family reasons.
Click to expand...
Click to collapse
Alright, that's ok. Ill just make a thread for custom roms for this phone.
B.Moreira said:
Alright, that's ok. Ill just make a thread for custom roms for this phone.
Click to expand...
Click to collapse
You probably won't get a stable ICS custom rom until Samsung releases the sources for the phone. Also you should ask that question in the Q&A section of the forum not in General device section.
Thanks! love this =D
Will flashing the recovery menu to my bell s2 help me root and unlock it easily like superclick or would i still have to flash my russian rom? Thank you for the work though.
singh99 said:
Will flashing the recovery menu to my bell s2 help me root and unlock it easily like superclick or would i still have to flash my russian rom? Thank you for the work though.
Click to expand...
Click to collapse
Make sure you read the section in post #1 for rooting the S2 HD. Just flash the ZIP, you don't need the Russian ROM. Do not flash this to the old Bell S2, this is for the HD LTE variant.
Hi dsixda, can I use this CWM recovery for SII HD LTE model E120L (korea version)
theanh6 said:
Hi dsixda, can I use this CWM recovery for SII HD LTE model E120L (korea version)
Click to expand...
Click to collapse
Refer to the big warning on page 1 directly above the download link...
I have no idea what will happen.
If someone here as the Bell SGH-I757M update for Android 4.0 (from Kies or stock), please get in touch with me via PM or Twitter. There is a test ROM floating around.
has it been released??
Yes if u have a dev unit the Kies will detect it and show update to 4.0
Oh, pretty sure mine isnt a dev unit
Dsixda not too sure if you seen this!!
http://www.xda-developers.com/tag/samsung-galaxy-s-ii-hd-lte/
markdexter said:
Dsixda not too sure if you seen this!!
http://www.xda-developers.com/tag/samsung-galaxy-s-ii-hd-lte/
Click to expand...
Click to collapse
Someone's been living under a rock..
It's already linked on post #1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey folks, here I look forward to guide the Google Nexus S users of the XDA Community to go custom with their Samsung Nexus S. I shall try to put forth the most prevailing steps to make my way to your minds. Also I will use the fastboot method to accomplish custom during this entire guide. Before we put our hands on the device and begin with the instructions, I would like to state some general terms, for your ease. :good:
Terms & Understanding
What is Bootloader and Why do we need to Unlock?
A bootloader is a boot initializing component which is generally locked by the device manufacturer to avoid any messing around with the OS. We need to unlock it for the same reason. Once unlocked it will allow us to change the boot sequence and modify the OS in accordance of our needs.
What is Rooting?
It is a process of gaining root privileges over an Android subsystem. Rooting an Android device is easy in most cases. If you will to Install custom ROMs, kernels, other patches or addons to your Android device, rooting is what you will need. It can be achieved in two ways; either by manual method (using fastboot) or by automatic method (using toolkit or software) . Here, I am going to follow the manual method by using fastboot commands.
ClockworkMod, what is it?
In short, CWM; It is a secondary recovery system created by Koush (Koushik Dutta), which adds enormous features like wiping partitions, flashing flash able .zip files like ROMs, kernels, patches etc to the stock AOSP recovery. Visit ClockworkMod website for more.
What does Custom ROM means?
These are the aftermarket Android firmware which are not official supported by the OEM (Original Equipment Manufacturer). They are made available to the Android public by Android developers and contributors all around the world. Custom ROMs are either built from Google’s source code i.e AOSP (Android Open Source Project) or are modified versions of the device manufacturer’s ROM (Stock ROMs or Factory ROMs) with additional tweaks and extend functions which are not delivered with the Stock ROMs. Some of the popular Custom ROMs include CyanogenMod (CM), Android Open Kang Project (AOKP), MIUI, Codename Android (CNA), Oxygen, ParanoidAndroid and many more.
What is Custom Kernel?
A Kernel is a bridge between the applications and the actual data processing done at the hardware level, In simple words, it is the communication between the hardware and software of an Operating System. In Android world, Custom Kernels play a vital role since they provide the users with several features including changing CPU frequencies, modifying the boot sequence and boot scripts and other features too.
What are Google Apps (Gapps)? The name speaks for itself. Gapps are Google apps for Android available in flash-able zip format. Most of these applications can now be found and updated via the Google Play Store.Some of the apps include the Google Play Store itself, Google Talk, Google Sync (for adding and synchronizing Google accounts), Google Backup Transport, Car Home, Gmail, Google Maps, YouTube, Google Search, Google Voice Search, Google Music, and Google Docs. In some Custom ROMs, the Google Apps are included. These are usually stock ROMs, smaller or less-common ROMs, or those from areas where intellectual property laws are less commonly obeyed. But many AOSP ROMs, most famously CyanogenMod and AOKP, do not include the Google Apps due to licensing issues. They are after all proprietary code owned by Google and not included in the Android Open Source Project.
Disclaimer
I am not at all responsible for any damage to your device but I can provide confirmation for this method to be working. If you are held in any issues during this guide, I will certainly not replace your device but will give my best shot to help you, recover it.
You should be aware that rooting or going custom voids your warranty.
Click to expand...
Click to collapse
Early necessary requirements
At least 60% of battery to ensure no random shutdowns due to low battery.
Backup your storage manually. Also your text messages and contacts using some backup app.
Install Google and Samsung USB drivers from here
A compatible USB data cable for undisturbed connection between PC and device.
Enable USB Debugging in your device’s settings [Settings > Developer Settings > USB Debugging].
A PC with Windows OS.
Download Required files
Extract the downloaded NexusS_files.zip to the desktop. So now you will have a folder named "NSFiles" on your desktop which beholds all the needed files during the process.
Please make sure to follow every single instruction mentioned during the guidelines. This will resist you from any mishaps during the process. Lets begin!
Unlock Bootloader
NOTE: Unlocking the bootloader will erase all the data on the phone as well as SD storage. So be sure to back everything up.
Reboot your Nexus S into bootloader mode by pressing volume up + power buttons simultaneously until you see the bootloader screen.
Connect your device to the PC via the USB data cable.
Open the extracted folder "NSFiles" that we have have on the desktop. On an empty space inside the folder, press shift and right click and then select "Open command prompt here". This will execute a new CMD window which is already cd'ed to the folder's location.
Type in CMD:
Code:
fastboot oem unlock
You will now receive a message on the screen. Use the volume keys to highlight "Yes" and select it using the power button.
Your bootloader is now unlocked.
Highlight and select "Reboot" to reboot your device.
You have successfully unlocked your Nexus S bootloader.
Installing Custom Recovery
Reboot your phone into bootloader mode by pressing volume up + power buttons altogether.
Connect it to the PC via USB data cable.
While in the "NSFiles" folder on your desktop, press shift + right click on an empty space and go to "Open command promopt here". This will execute a command window which is already cd'ed to your current location.
To Install ClockworkMod touch 6.0.1.0
Type in CMD:
Code:
fastboot flash recovery CWM-T.img
To Install ClockworkMod non-touch 6.0.1.0
Type in CMD:
Code:
fastboot flash recovery CWM.img
To Install TWRP 2.3.1.0
Type in CMD:
Code:
fastboot flash recovery TWRP.img
The CMD prompt will indicate when the flashing is complete, it barely takes a few seconds.
Do not exit the bootloader mode, since this is the way to boot into recovery.
Now to boot into your new custom recovery, highlight "RECOVERY" and select it using the power button.
Rooting the Nexus S
If you plan to use the stock (factory) ROM, it is preferable to root. Otherwise, all the Custom ROMs out there already have root access.
The mentioned process is recommended to carry out using ClockworkMod Recovery.
Download the latest SuperSU flash-able root package. [Chainfire's SuperSU Thread]
Power off your device and boot into the bootloader mode by pressing volume up + power buttons simultaneously until you see the bootloader screen. Highlight"RECOVERY" using the volume buttons and select it using the power button.
Now, your Nexus S is in recovery mode.
Go to "mounts and storage" > scroll to the very last and select "mount USB storage".
This will mount your device's storage to the PC.
Drag the downloaded "CWM-SuperSU-v0.98.zip" to the root of your storage.
Select "unmount" to exit the USB storage mode.
Go to "install zip from sdcard" > "choose zip from sdcard" > select the "CWM-SuperSU-v0.99.zip" you placed in the storage and flash it.
Once flashed, select "reboot system now"
.
You now have your device rooted. You can officially declare yourself as the true master of your device.
Install Custom ROMs
Installing a ROM is quiet a simple process, you can say that it is the easiest of all.
First, you need to choose a suitable ROM that meets your requirements.
Once you have chosen, download the ROM's .zip (flash able zip file) as provided by the Author/ Developer .
Also make sure to download specific Gapps and other add-on if provided by the developer himself. [If not, download generic Gapps from here]
Put the downloaded files to your SD storage either by using USB mass storage directly or by mounting USB storage in recovery mode.
Reboot your Nexus S into Recovery mode. Power off your device and boot into the bootloader mode by pressing volume up + power buttons simultaneously until you see the bootloader screen. Highlight"RECOVERY" using the volume buttons and select it using the power button.
Using CWM:
wipe data/factory reset.
Go to "mounts and storage" > "format /system".
Go to "install zip from sdcard" > "choose zip from sdcard" > select your ROM .zip file that you placed in step #6. Flash it.
Gapps are the next to be flashed just after flashing the ROM. So, flash Gapps following the same way as the ROM. further if your are provided any add-on in a flash able zip format you can flash it the same way after flashing the ROM and Gapps successfully.
Once everything has flashed successfully, select "reboot system now".
Using TWRP:
Go to "Wipe" > "System" and "Factory Reset".
Go to "Install" > choose the ROM .zip file and flash it.
Gapps are the next to be flashed just after flashing the ROM. So, flash Gapps following the same way as the ROM. further if your are provided any add-on in a flash able zip format you can flash it the same way after flashing the ROM and Gapps successfully.
When flashed, go to "Reboot" > "System".
Your phone will now boot into the custom ROM.
Install Custom Kernels
Download the flashable zip package of your desired Custom Kernel.
Connect your device to PC via USB cable in USB Storage Mode.
Drag the downloaded kernel zip package to the root of your device's storage.
Disconnect the device from PC.
Power off, now press the volume up button and the power button altogether until you see the bootloader screen. Use the volume keys to highlight "Recovery" and select it using the power button.
Your device shall now be in recovery mode.
Flash using CWM:
"advanced" > "Wipe Dalvik Cache"
"install zip from sdcard" > choose zip from sdcard" > now browse and select the kernel zip package that you placed in your storage root during step #3.
Select "Yes".
Your Kernel will now flash to your OS and replace your current kernel.
When it has successfully flashed, select "reboot system now".
Flash using TWRP:
"Wipe" > "Dalvik Cache"
"Install" > now browse and select the kernel zip package that you placed in your storage root during step #3.
Your Kernel will now flash to your OS and replace your current kernel.
When it has successfully flashed, go to "Reboot" and select "System".
You now have Custom Kernel installed on your Nexus S.
NOTE: Before choosing any Custom Kernel, do verify that the Kernel is meant to be flashed on your present Android OS version.
Congratulations! You shall now enjoy the full packed potential of your wonderful Nexus S.
If you have got any questions/ queries or you're stuck anywhere in the mid process, comment here. I will try my best and provide you an helping hand.
Visit the full pictured guide at DroidViews.com
Click to expand...
Click to collapse
Nice tutorial, very well done :good:
Maybe you could add something about custom kernels as well, since they're part and parcel of a custom ROM?
gunner49 said:
Nice tutorial, very well done :good:
Maybe you could add something about custom kernels as well, since they're part and parcel of a custom ROM?
Click to expand...
Click to collapse
Thanks for the appreciation :good:
And yes, I would look into the kernel part too, very soon :victory:
DJBhardwaj said:
Thanks for the appreciation :good:
And yes, I would look into the kernel part too, very soon :victory:
Click to expand...
Click to collapse
Nice one Look forward to reading it!
gunner49 said:
Nice one Look forward to reading it!
Click to expand...
Click to collapse
UPDATED!
Updated "Terms & Understanding".
Added "Install Custom Kernels".
DJBhardwaj said:
UPDATED!
Updated "Terms & Understanding".
Added "Install Custom Kernels".
Click to expand...
Click to collapse
Brilliant! :good:
gunner49 said:
Brilliant! :good:
Click to expand...
Click to collapse
Thank you for the support, its very much appreciated
Thanks for the tutorial.
Needed it for a friends phone
Works perfectly!
can this tutorial flash the factory img?
sorry for my bad english
Sent from my Nexus S using
ryuken80 said:
can this tutorial flash the factory img?
sorry for my bad english
Sent from my Nexus S using
Click to expand...
Click to collapse
The tutorial to flash Jelly Bean 4.1.2 Factory Image is here: Click to visit
Very welldone!
Should be sticky.
_hito_ said:
Very welldone!
Should be sticky.
Click to expand...
Click to collapse
Once we get enough popularity and user support , we may request a moderator to do so :fingers-crossed:
very useful thread,,,many thanks:good:
alfhie said:
very useful thread,,,many thanks:good:
Click to expand...
Click to collapse
Thank you for the support. :good:
How To Root Nexus S i9023 Jellybean 4.1.2
I really want to know and understand the perfect way to root my nexus s i9023 running jellybean 4.1.2
I have searched pretty much everywhere but just cannot find a proper way to root my nexus s..
If u guys have the perfect guide regarding the above then plz help me with the same...
azcol said:
I really want to know and understand the perfect way to root my nexus s i9023 running jellybean 4.1.2
I have searched pretty much everywhere but just cannot find a proper way to root my nexus s..
If u guys have the perfect guide regarding the above then plz help me with the same...
Click to expand...
Click to collapse
Follow this guide. You can also find the pictured guide here. :good:
Hi guys!
Have some noob questions
yesterday installed this rom - http://forum.xda-developers.com/showthread.php?t=2041851
and i couldnt find [Settings > Developer Settings > USB Debugging]! There are no Develepor Settings tab.
Sorry if I'm posting in wrong forum thread.
Thanks
I'm found answer in Google (5 taps on build number
Hey guys,
A friend of mine with a GSM Nexus S asked me to root his phone, and I saw this amazing thread. I just have one doubt, does the bootloader need to be unlocked in order to follow the "Rooting the Nexus S" procedure?
Thank you very much!
eddie_gordo said:
Hey guys,
A friend of mine with a GSM Nexus S asked me to root his phone, and I saw this amazing thread. I just have one doubt, does the bootloader need to be unlocked in order to follow the "Rooting the Nexus S" procedure?
Thank you very much!
Click to expand...
Click to collapse
Yes, its essential to unlock the bootloader first if you are willing to perform any custom action :good:
Creating A backup using Rom Manager
Hey There ,Thanks For your Guide..:good:
I was successfully able to root my nexus s i9023 running 4.1.2..
Now i want to create a backup of my 4.1.2 using rom manager , as i want to flash cyanogenmod 10..
Can U help me with the same again...
Thanking u in advance..
[Unofficial] TWRP 2.8.7.0 for HTC m9+ (m9pw, m9 plus, htc_hiau_ml_tuhl) English version
Credit:
TWRP / @Dees_Troy
Theme: Materialised Play @z31s1g topic
Xiaolu: this version is based on xiaolu's repositories and original compilation and device tree https://github.com/xiaolu?tab=repositories
Repositories: https://github.com/tbalden/android_device_htc_htc_hiau_ml_tuhl https://github.com/tbalden/android_bootable_recovery-twrp
Hit the Thanks button if you like the work being done, or donate to the dev:
DONATION HEREhttp://forum.xda-developers.com/donatetome.php?u=3088420http://forum.xda-developers.com/donatetome.php?u=3088420http://forum.xda-developers.com/donatetome.php?u=3088420
Default theme (please download the primary recovery image below):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Materialised Theme (please download the second recovery image below):
Tested on a Chinese M9+
Issues:
- ADB doesn't work. You need to copy flashable files to the device while phone is in normal mode over MTP, not in the recovery.
- external sd card: doesn't work properly, DON'T try flashing from it, I had to restore a backup when I tried
- in Materialised Theme mode, on theme/splash creation screen: creation and flashing of own theme/recovery image fails
WARNING: As usual, use it at your own risk! This comes without any warranties, by downloading and using it you are taking all responsibilities on yourself.
STOCK RECOVERIES: if you want to go back to your Stock recovery some Carriers (regions) some recovery versions for different official firmware versions are available in this thread: http://forum.xda-developers.com/one-m9/one-m9-general/firmware-stock-recoveries-regions-t3120826
ALSO BE AWARE: for some regions the Stock Recovery Image of the phone is not available. So basically, if you flash the recovery as long as there's no official image to extract the original, you won't be able to flash back to stock recovery, meaning that you might have problem with flashing official updates!
SO AGAIN: YOU WON'T BE ABLE TO FLASH BACK TO STOCK RECOVERY, meaning you most probably won't be able to upgrade on the official OTA updates till someone gets an official RUU for your device's carrier from which the stock recovery can be extracted Some carriers some firmware versions are already covered in the thread mentioned above (STOCK RECOVERIES)
You'll need:
- Unlocked bootloader (e.g. proceed as detailed here: http://www.htcdev.com/bootloader)
- Fastboot tool
- Better use a USB 2.0 port, might work to flash with USB 3, but there were reports of issues with that
INSTALLATION:
Code:
- Unlock bootloader
- Boot your device into Download mode: POWER OFF, then long press [Volume Down + Power]
- Hook up USB with PC and the phone
- with fastboot:
fastboot flash recovery recovery-twrp-2.8.7.0-htc_m9pw-english.img
Example:
Code:
c:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery-twrp-2.8.7.0-htc_m9pw-english.img
target reported max download size of 800000000 bytes
sending 'recovery' (13996 KB)...
OKAY [ 1.454s]
writing 'recovery'...
(bootloader) HOSD CL#534001
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.272s]
finished. total time: 2.728s
DOWNLOAD:
TWRP (unmodified, Default Theme):
2.8.7.0: http://d-h.st/BEYh (Use Download Now button on the site)
TWRP with Materialised Light Play theme and light blue material splash precompiled:
2.8.7.0 - material_play: http://d-h.st/16Ec
Unlock tutorial for materialised twrp version:
2.8.6.0 v2: http://d-h.st/OXFu (Use Download Now button on the site)
2.8.6.0 v1: http://d-h.st/MZh6
ACCESS RECOVERY
Power off. Long press Power + Vol Down. In Download mode with volume buttons navigate to reboot to bootloader, press power.
In bootloader navigate with volume buttons to BOOT TO RECOVERY MODE, press Power.
Rooting guide thread: http://forum.xda-developers.com/one-m9/one-m9-general/howto-rooting-m9-m9pw-htchiaumltuhl-t3116327
reserved for versioning post
VERSIONS
2.8.7.0 - 2015-07-18 - Changes from official TWRP release bump (like the option of keeping System partition readonly, for stock backups)
2.8.6.0 v2 - 2015-07-11 - Removed unnecessary touch logging which slowed down recovery and spammed log window
2.8.6.0 v1 - 2015-05-23 - Initial English version
==========
Also I'll try to get root access on the device now with this recovery. Will post it in a separate thread when it's done.
UPDATE:
Root access flashing from TWRP:
Yes it works.
With TWRP recovery flash the SuperSU update zip from here https://download.chainfire.eu/735/SuperSU
Code:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]_hiau_ml_tuhl:/ $ su
su
[email protected]_hiau_ml_tuhl:/ #
Rooting guide thread: http://forum.xda-developers.com/one-m9/one-m9-general/howto-rooting-m9-m9pw-htchiaumltuhl-t3116327
Thanks for the great work you've been doing so far! I really appreciate dev's like you who manage to do so much with little resources or help available. Cheers!
thanks for this recovery
Thanks for this it was a life saver. I was getting nowhere trying to use TWRP 2.8.7.*
I found that when it runs, there are a lot of red warning messages - E: touch-drag and E: touch-hold. Dont get these message with other versions of TWRP, or is it just something with my M9Plus?
joe97113 said:
Thanks for this it was a life saver. I was getting nowhere trying to use TWRP 2.8.7.*
I found that when it runs, there are a lot of red warning messages - E: touch-drag and E: touch-hold. Dont get these message with other versions of TWRP, or is it just something with my M9Plus?
Click to expand...
Click to collapse
I want to compile a new one without that, also of 2.8.7.0 but I cannot seem to have it booted. If I succeed I'll get back with it.
2.8.6.0 updated with v2 for m9+, it's just cosmetic changes, but makes the navigation faster. Check original post for new download link.
2.8.6.0 v2 - 2015-07-11 - Removed unnecessary touch logging which slowed down recovery and spammed log window
I still have issues with booting my new compilation for 2.8.7.0, so for now this is just a minor update for 2.8.6.0 specifically for the m9+ unofficial english twrp recovery
tbalden said:
2.8.6.0 updated with v2 for m9+, it's just cosmetic changes, but makes the navigation faster. Check original post for new download link.
2.8.6.0 v2 - 2015-07-11 - Removed unnecessary touch logging which slowed down recovery and spammed log window
I still have issues with booting my new compilation for 2.8.7.0, so for now this is just a minor update for 2.8.6.0 specifically for the m9+ unofficial english twrp recovery
Click to expand...
Click to collapse
Many Thanks tbalden. I will give the new version a go.
Hi tbalden,
I have run into a bit of a problem with your latest recovery and wondering if you or anyone else may have an idea what's causing this problem which is, the bootloader unlocked fine and I flashed v2.img via fastboot and all went fine also then booted into recovery and I am getting the error E:Unable to mount '/system' when trying to flash CleanSlate which actually seems to flash fine, I went into Mount and tried to mount the system partition but it won't check and the same error come up in the dialogue.
I now can't reboot into the system and it hangs at the splash screen so I'm guessing this error is the problem with the ROM being flashed correctly and everything is messed up now.
It may be a simple fix but if you or anyone else knows what may be causing this I would appreciate some help please, thanks.
Update: Everything is installed correctly and working now.
@Sojourner353 Are you by chance installing the rom from external sdcard ? That doesn't work, and caused me same issue (I've it in the first post of this thread as known issue). Do you have a back up? Restore, boot, and move the zip to internal storage and try that.
If you don't have a backup, you might need a RUU zip for your CID, and as I see that is Hong Kong (CID 708 based on your post in the rom thread). I don't have a HK RUU zip base 1.09, maybe @xiaolongzi?
tbalden said:
@Sojourner353 Are you by chance installing the rom from external sdcard ? That doesn't work, and caused me same issue (I've it in the first post of this thread as known issue). Do you have a back up? Restore, boot, and move the zip to internal storage and try that.
If you don't have a backup, you might need a RUU zip for your CID, and as I see that is Hong Kong (CID 708 based on your post in the rom thread). I don't have a HK RUU zip base 1.09, maybe @xiaolongzi?
Click to expand...
Click to collapse
Thanks for the reply, I do have a nandroid but it's giving me the same result after restoring it, I am also installing from the internal memory, there is no external SD in the unit at all.
The only thing I can think of is there is some sort of corruption in the recovery caused by the PC I flashed it from (Surface Pro 3 USB3), never used this PC on previous devices so today I will use my Server that has USB2 and has done many devices in the past without issue.
If I still have a problem I will just have to wait for a RUU to become available I guess.
Sent from my HTC One M8x using Tapatalk.
UPDATE: I've done some thorough testing, multiple flashing of full ROM and backup / restore, v2 seems to be OK on my side, so adding back link.
===
I didnt have the time to properly invevstigate, but the V2 might have some instability issues, sorry guys, removed for now till I investigate the issue.
Please revert back to V1 !
Finally did a test with v2, much better than the previous version - did not find any issues. Thanks.
2.8.7.0+ m9+ english version soon to upload. Testing it some more.
Those who wish to backup intact System.img (remount Read/Write issue circumvention when going back to stock recoveries and trying OTAs failed with remounted System partitions) should be able to use Read-Only system mode with this:
With 2.8.7.0 TWRP i'll soon release, I've tested 2.8.7.0 theme from this thread: http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584 Nicely working. (Through 1440x2560 Themes Folder, Material Light theme, name 287x-v1-1440_play)
Tho I had a hard time with Swipe right to unlock, before I found out that i need to swipe the lower screen part, and there's no actual graphical slider, just colored text (you'll understand it if you try installing it yourself )
new update
2.8.7.0 - 2015-07-18 - Changes from official TWRP release bump (like the option of keeping System partition readonly, for stock backups)
new addition:
TWRP with Materialised Light Play theme and light blue material splash precompiled recovery image version.
Check first post for download in Downloads section
i repacked 286 with system read only to backup unmodified system image before. If i could rename the name system.emmc.win to system_image.emmc.win to restore with your new version 287, i will test it. Thank your new versin 287 and this make M9+ perfect if someone still want to keep OTA.
Sent from my HTC_M9pw using XDA Free mobile app
Help.
"Swipe right to Unlock" does not work for me, any suggestions. Tried to volume down+ power button with no luck. Occasionally the screen goes black then the text comes back.
---------- Post added at 08:39 PM ---------- Previous post was at 08:23 PM ----------
joe97113 said:
Help.
"Swipe right to Unlock" does not work for me, any suggestions. Tried to volume down+ power button with no luck. Occasionally the screen goes black then the text comes back.
Click to expand...
Click to collapse
Managed to reboot. Might go back to previous version at least the unlock works.
joe97113 said:
Help.
"Swipe right to Unlock" does not work for me, any suggestions. Tried to volume down+ power button with no luck. Occasionally the screen goes black then the text comes back.
---------- Post added at 08:39 PM ---------- Previous post was at 08:23 PM ----------
Managed to reboot. Might go back to previous version at least the unlock works.
Click to expand...
Click to collapse
Which version? material Themed or the default?
In Material themed you either need to swipe over the low area of the screen (the text will go gray as you progress), or in settings set alternative lock screen to make it more visible
In default theme version very occasionally it happened to me, I had to try unlock it and wait about ten seconds till it unlocked in the end. But this happened on 2.8.6.0 not the new version
Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
1. On the tablet, download the Stump app from http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
Credit and thanks @jcase, IOMonster , @autoprime and @PlayfulGod. Credit and thanks azureflux for the music although personally I turn the volume down all the way.
2. Install the Stump app you downloaded. Android should prompt you that it's an app from an unknown source since you didn't download it from the Play Store. It should direct you to the Security Settings option "Unknown sources" which you should checkmark and then attempt again to install the Stump app.
3. Launch the Stump app.
4. Turn the volume all the way down if you want because the music can be annoying for the duration necessary to root the VK810.
5. Choose "Grind".
6. Choose "Brute Force".
7. On the VK810, it can take up to 20 minutes at which time the Stump app should say to reboot the device to implement the root.
8. Once the device is rebooted, go to the Play Store and install SuperSU from https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Alternatively you can download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053), extract the zip and install the SuperSU app, or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
You'll also need this SuperSU.zip for step 8 of the fourth post "Flash to the latest stock ROM so that you can have it with root".
Credit and much thanks to @Chainfire !!!
9. Launch SuperSU, confirm the prompt to update binaries.
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=3
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
1. On the tablet, download the "VK810_twrp_2.7.0.1.zip" from http://forum.xda-developers.com/showthread.php?t=2726707
Credit and thanks teamwin , @Drgravy , @djrbliss , @Dees_Troy , @id10terror and @traccdma !
The link is in the "DOWNLOAD" section below the "DISCLAIMER" towards the bottom of the first post.
Credit @Drgravy for the original instructions but I prefer to run the commands directly on the device instead of from a PC via USB Cable and ADB.
2. Download TWRP v2.8.7.0 from http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-7-0-t3150812
Credit and thanks @AndroidUser00110001 !
3. Install "X-plore File Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en
Credit and thanks Lonely Cat Games!
4. While you're in the Play Store, install "Terminal Emulator for Android" https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
5. Launch X-plore.
6. Enable root mode in X-plore:
6A. Click the three-dot menu button in X-plore's upper right corner.
6B. Choose "Configuration".
6C. In the "Root access" section, click the gray area below it and choose "Superuser + mount writable".
6D. Give X-plore SuperUser permissions by choosing "Grant" in the SuperSU prompt that pops up. It might not open this prompt until a later step when you actually access root.
7. Find the "VK810_twrp_2.7.0.1.zip" file you downloaded in step 1 above. It should be on your internal storage in the Download folder.
8. Click once on the zip file - this will show you the files contained in it.
9. Navigate to the other file manager pane by choosing "SWITCH PANE" in the upper right corner.
10. Choose "Internal storage".
11. Navigate to the original pane by choosing "SWITCH PANE" again.
12. Select all the files inside the zip.
13. Choose the "Copy" icon in the toolbar on the right or left side of the screen. Choose "OK" at the confirmation prompt.
14. Now navigate to root. Give X-plore SuperUser permissions by choosing "Grant" in the SuperSU prompt that pops up.
15. From root, navigate to data/local/tmp.
16. "SWITCH PANE" to where you extracted the files from the zip.
17. Select "loki_flash" and "twrp.lok".
18. Choose the "Copy" icon in the toolbar on the right or left side of the screen. Choose "OK" at the confirmation prompt.
19. Launch "Terminal Emulator" installed in step 4 above.
20. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/twrp.lok
reboot recovery
Instead of "reboot recovery" you can use an app such as "Quick Reboot" from the Play Store at https://play.google.com/store/apps/details?id=phongit.quickreboot to reboot to recovery.
21. For getting to custom recovery with the tablet off, press and hold the Down Volume button. While continuing to hold the Down Volume button, press and hold the Power Button. The screen should come on in the stock-looking recovery and you can let go of both buttons). "Factory Reset" will no longer perform a Factory Reset. That's what you choose to get into custom recovery.
22. Update to to the latest TWRP v2.8.7.0 that you downloaded in step 2 above by (in TWRP v2.7.0.1) choosing "Install", navigating to where you downloaded the TWRP v2.8.7.0 zip (probably in internal storage in the Download folder), and choosing to flash the zip.
You can put a different custom recovery on the same way.
23. You can reboot into the newer TWRP by choosing the reboot recovery option.
Flash to the latest stock ROM so that you can have it with root:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=4
Flash to the latest stock ROM so that you can have it with root:
1. Download my ROM from my signature at the bottom of this post. I use ADM "Advanced Download Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.dv.adm&hl=en, especially for downloading larger files like ROMs.
2. Check the MD5 Hash of the ROM zip:
2A. Copy (to the clipboard) the MD5 hash that I have in the filename of the ROM zip you downloaded in step 1 above.
2B. Install @scary alien 's "AFV File Verifier for Android" from the Play Store at https://play.google.com/store/apps/details?id=sa.afvx&hl=en.
2C. Run the AFV app.
2D. Choose "Input checksum for comparison".
2E. Paste the MD5 hash previously copied to the clipboard in step 2A above.
2F. Choose "Select File".
2G. Navigate to where you have the ROM zip.
2H. Long-press on the ROM zip and choose "Calc MD5 Checksum".
2I. When it's done calculating the MD5 hash of the ROM zip, it'll automatically compare it to the MD5 hash you pasted in step 2E above.
If the hashes match, the downloaded ROM zip is non-corrupt. If the hashes don't match, you have to re-download the ROM zip.
3. Optionally download one or more of my debloat zip files in the third post of my ROM thread in my signature below. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
4. If you didn't already do so in step 8 of the second post "Rooting VK810 official stock release 11A", download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053) or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
5. Copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections.
6. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
7. Flash my ROM.
8. Flash SuperSU.zip (downloaded in step 4 above). This step is VERY IMPORTANT if you want to get back into custom recovery without having to re-flash a stock ROM and go through the whole process again.
9. Optionally flash one or more of my debloat zip files. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
Flashing the debloat zip(s) before the first boot of the ROM will give the advantage of never having the data/cache entries or internal storage folders for the debloated apps created, the latter is why I recommend a wipe of internal storage.
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=5
Thanks to @JBurch/cry for the monetary motivation to finally put this all together in one place!
There are THREE variants of the G Pad 8.3: The Verizon VK810.4G which has LTE, and the V500 and V510 WIFI-only models. These instructions are ONLY for the VK810.4G.
Please don't quote the whole OP.
FAQ: If you use files meant for anything else other than the VK810, you'll brick your tablet. This will be exhibited by the tablet showing up in Windows' Device Manager under "Other devices" as "QHSUSB-BULK". You will have to Google for "QHSUSB-BULK" to find out how to fix that. I've read about some having success doing so and others not. I haven't ever had to fix that so I have no personal experience with it and can only lead you to Google about it.
This requires a Windows PC, preferably Windows 7 or newer, to first downgrade your VK810 variant of the G Pad 8.3 to LG build 11A / Jellybean 4.4.2, to make it easiest to root and to put a custom recovery on.
Disclaimer: I am not responsible for whatever you do to your device. This is my preferred method and what I recommend.
Note: These instructions are still working in order to downgrade from official stock release 36B on the VK810 (codename "altev"), Verizon LG G Pad 8.3 LTE, to official stock release 11A in order to make it easiest to both root and install TWRP. You can then install any ROM you like including my newest stock ROM in my signature at the bottom of this post.
Downgrading/resetting to 100% official stock unrooted release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
1. On a Windows PC, preferably with Windows 7 or higher, download the latest Verizon-LG driver at http://www.lg.com/us/support-mobile/lg-LGVK810 (current version 4.0.3, direct download link if still working http://18d5a.wpc.azureedge.net/8018D5A/tool/dn/downloader.dev?fileKey=UW00520120427).
2. Install the driver.
3. Reboot the PC.
4. While you're continuing to follow the rest of the directions, might as well get the installed driver "loaded":
4A. Put the VK810 in Download mode:
4A1. Preferably using the original USB cable, or alternatively possibly a high-quality cable, connect the one end preferably to a USB 2.0 port on your Windows PC. Note: not all, but most USB 3.0 ports (to avoid for this process under normal circumstances) are blue in color whereas USB 2.0 ports are usually black.
4A2. Turn the VK810 off (within Android, long press the power button and choose "Power off").
4A3. The following is different from other G Pad 8.3 variants:
4A3a. Press and hold the Up Volume button.
4A3b. While continuing to hold it, insert the tablet end of the USB cable.
4A3c. You should feel the tablet vibrate and you can see a very dim, very faint graphic in the very center of the screen that says "Download Mode":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credit and thanks @sevoan for posting the screenshot at http://forum.xda-developers.com/showthread.php?t=2782066
4A3d. Let go of the Up Volume button.
4B. Windows may take up to 10 minutes to finish loading the driver you previously installed. Every time you connect any USB device to a new/different USB port on a PC, Windows will have to take a longer loading the driver process.
5. Download the official stock release 11A KDZ for the VK810: https://www.androidfilehost.com/?fid=23991606952610809 (file name "5. VK81011A_01 - Jellybean 4.2.2.KDZ - MD5 hash inside - recommended for both ease of rooting and one less step to install the initial TWRP v2.7.0.1.7z")
If the previous link doesn't work, you can find it in my signature at the bottom of this post.
6. Download and install the free 7-Zip Windows program from ttp://www.7-zip.org"]http://www.7-zip.org[/URL]. Any version should work although you can only install the 64-bit version on 64-bit versions of Windows.
7. Use 7-Zip to extract the KDZ from the 7-Zip (7z) file downloaded in step 5 above. If you want to extract the 7-Zip on an Android device instead for some reason, use ZArchiver from the Play Store at https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver&hl=en
8. LG Flash Tool 2014:
8A. On the Windows PC, download "LG Flash Tool 2014" from http://forum.xda-developers.com/showthread.php?t=2797190
Credit and thanks @quangnhut123
The MediaFire link is in step "3. Tutorial"
8B. Run "LGFlashTool2014.exe" as Admin: Right-click on "LGFlashTool2014.exe" and choose "Run as administrator". Provide Administrator credentials if necessary. If you get a UAC (User Account Control) prompt, click "Yes".
8C. If the program doesn't run, install the Visual C++ Runtime Library, also available in step "3. Tutorial" at the link in step 8 above, then repeat step 9.
8D. Screenshots also available at the link in step 8.
8E. "Select Type" should already be at the correct default "CDMA". Same for "PhoneMode" is "DIAG" and "Reset time" is "33000".
8F. Click the yellow folder icon to the right of the "Select KDZ file" field and choose the 11A KDZ file extracted from the 7-Zip archive you downloaded in step 5 above.
For reference: "CSE Flash" is what you should normally always use. "CSE Flash" will wipe your user data including your internal storage so be sure to move/copy anything you want to keep that's currently on your internal storage. "Normal Flash" is like a dirty flash. Your device will be restored completely to stock but will keep all of your user data including your internal storage. If you're downgrading stock ROM versions, you can expect "Normal" to result in a device that'll crash. If you do so, you can attempt a "Factory Reset" from the stock recovery (with the device off - long press the power button for 10 or so seconds until the device shuts off - press and hold the Down Volume button. While continuing to hold the Down Volume button, press and hold the Power Button. The screen should come on in the stock recovery and you can let go of both buttons). "Factory Reset" will of course wipe all user data including Internal Storage.
8G. Click "CSE Flash".
8H. On the "Read Phone Information" dialog which appears, do NOT press the "Read Phone Information" button. This has always crashed for me.
8I. Click "Start".
8J. On the next dialog, you can change the Country and Language if you like - either way doesn't make a difference. Click "OK".
VERY IMPORTANT: Once you click "OK", ignore any error dialogs that pop up. I mean every single one. Don't click any buttons in them, just drag them out of your way if necessary. 99.9% of the time, given enough time the device will be flashed successfully anyway. On the VK810, usually within 20 minutes. For comparison, on the VS985 Verizon LG G3, usually within 10 minutes.
Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=2
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=3
Flash to the latest stock ROM so that you can have it with root:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=4
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=5
General thanks to, for my previous experience:
@AndroidFileHost for the Android File Host website and especially their changes allowing for the reorganization of already uploaded files.
@KyPbP for letting us know it's availability and giving the link to download the VK810 35A_08 KDZ. http://forum.xda-developers.com/showpost.php?p=60851710&postcount=108
@Revoe for letting us know the availability of the VK810 36B_00 OTA. http://forum.xda-developers.com/lg-g-pad-83/general/verizon-lg-g-pad-8-3-vk810-altev-ota-t3182449
@hsbadr for giving me permission to kang his Verizon G3 VS985 JasmineROM 7.0 update script for this use. http://forum.xda-developers.com/showpost.php?p=56005236&postcount=1
@rant for giving a link to the official Verizon PDF detailing 35B. http://forum.xda-developers.com/showpost.php?p=60857092&postcount=1 http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-g-pad-83-5-20-15.pdf
@DeanGibson for giving a link to the official Verizon PDF detailing this release. http://forum.xda-developers.com/showpost.php?p=62413430&postcount=2 http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-8-17-15.pdf
@Chainfire for SuperSU! http://forum.xda-developers.com/showthread.php?t=1538053
@Hnk1 for continued support, advise and ideas, and for experimenting to find out how to root 35A_08 without downgrading.
@xdabbeb for further knowledge about the partitions!
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
1. Download the corresponding "aboot only" (aboot is the bootloader) found in the same place to download as my ROM zip. Corresponding means if you installed the latest 36B VK810 stock ROM, then download the 36B VK810 aboot zip file.
2. Download the 4.2.2 aboot package from http://forum.xda-developers.com/showpost.php?p=54533937&postcount=2
Credit and thanks @paperWastage !
The download link is about three quarters down in that second post.
3. Move this aboot.4.2.2.img file into the top of the internal storage (meaning, not in a folder).
4. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
dd if=/sdcard/aboot.4.2.2.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
5. You can now reboot into recovery via your preferred method.
6. Once you're finished in TWRP, you need to re-flash the newer aboot zip downloaded in step 1 above. If you forget, the ROM won't boot. You should be able to long-press the power button to force the device off, then use the manual method to get back into TWRP mentioned in step 22 in the previous section above. Re-flash the newer aboot zip, then reboot from TWRP and the ROM will boot.
You can alternatively dirty flash my ROM zip instead of just the aboot. You'd have to re-flash SuperSU.zip and any debloat zips too.
Reserved
Update
Ok, so I installed TWRP and flashed the new version. I then cleaned out my internal memory and loaded several files to the external SD card for the final process. I flashed "ViKtory810ROM_v36B_00+5.0.2+with+36B+aboot+[no+custom+recovery+after]+-+MD5+50fe66dfd0b57a50694accef47263a94" first. Then I flashed "UPDATE-SuperSU-v2.46". Next I flashed "VK810.4G+36B_00+5.0.2+-+no+OTA+-+MD5+b031ab290cde9f6fa0e30db8ef61223a". Then flashed "VK810.4G+36B_00+5.0.2+debloat+-+all+EXCEPT+still+has+OTA+-+MD5+e215ad72cb4fc9d5841217faa5048444". Then I flashed "VK810.4G+36B_00+5.0.2+debloat+-+LG+apps+&+UI+sounds+-+MD5+9a15512ed7754ef7fccf8b017c631199". I flashed them in that order from TWRP v2.8.7.0. After reboot the new ROM loads up and it seems to be working ok except for one issue. I keep getting an error popping up that says "Unfortunately, the process com.android.phone has stopped. Then it shows activation complete and shows my phone number listed under that. After that the pop up appears and say Unfortunetly, the process com.android.phone has stopped. I clear the pop up and it says activating tablet again, then shows the activation complete with my phone number all over again. Then the pop up appears again. This is an endless cycle of happening. I haven't done anything on the tablet as of yet. I want to know what your thinking. Is there something I need to do with one of the settings? I'm also noticing its not connecting to the cell towers. Ok, hope you can help. Thanks again!
JBurch/cry said:
Ok, so I installed TWRP and flashed the new version. I then cleaned out my internal memory and loaded several files to the external SD card for the final process. I flashed "ViKtory810ROM_v36B_00+5.0.2+with+36B+aboot+[no+custom+recovery+after]+-+MD5+50fe66dfd0b57a50694accef47263a94" first. Then I flashed "UPDATE-SuperSU-v2.46". Next I flashed "VK810.4G+36B_00+5.0.2+-+no+OTA+-+MD5+b031ab290cde9f6fa0e30db8ef61223a". Then flashed "VK810.4G+36B_00+5.0.2+debloat+-+all+EXCEPT+still+has+OTA+-+MD5+e215ad72cb4fc9d5841217faa5048444". Then I flashed "VK810.4G+36B_00+5.0.2+debloat+-+LG+apps+&+UI+sounds+-+MD5+9a15512ed7754ef7fccf8b017c631199". I flashed them in that order from TWRP v2.8.7.0. After reboot the new ROM loads up and it seems to be working ok except for one issue. I keep getting an error popping up that says "Unfortunately, the process com.android.phone has stopped. Then it shows activation complete and shows my phone number listed under that. After that the pop up appears and say Unfortunetly, the process com.android.phone has stopped. I clear the pop up and it says activating tablet again, then shows the activation complete with my phone number all over again. Then the pop up appears again. This is an endless cycle of happening. I haven't done anything on the tablet as of yet. I want to know what your thinking. Is there something I need to do with one of the settings? I'm also noticing its not connecting to the cell towers. Ok, hope you can help. Thanks again!
Click to expand...
Click to collapse
You're welcome! Everything debloated in the LG/etc debloat zip is also debloated in the debloat All, FYI.
Sorry you're having trouble. I haven't had that experience at all. Did you wipe Data, Cache and Dalvik too? Sadly, without being able to fully use Android you won't be able to get back into TWRP since you have to temporarily redowngrade the bootloader (aboot.img) to get into it (the last section "In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs").
I know there's a way in Android to boot in a "safe mode" but I've only done it by accident and can't recall how. I don't know if that would make any difference anyway.
If you can use the hardware keys to get into the stock-looking recovery you could try re-wiping Cache but I wouldn't have much hope of that doing the trick, either.
I hate to say but if none of these things work the only way to get back into TWRP without the use of Android is to use LG Flash Tool 2014 to re-flash the 11A KDZ and start over.
I guess I'm going to have to write the detailed instructions for how to check MD5 hashes and add that into the OP, as that would be something I would ask if was done when anyone has problems after a flash.
@JBurch/cry I wrote up directions for checking MD5 hashes on Android - they're in the section for flashing my ROM. I realized that this won't help you in your current situation unless you take the MicroSD card out and put it in another Android device and check the hash on there.
I'm debating whether I should write up directions for checking MD5 hashes on Windows too.
So uh ya
roirraW "edor" ehT said:
You're welcome! Everything debloated in the LG/etc debloat zip is also debloated in the debloat All, FYI.
Sorry you're having trouble. I haven't had that experience at all. Did you wipe Data, Cache and Dalvik too? Sadly, without being able to fully use Android you won't be able to get back into TWRP since you have to temporarily redowngrade the bootloader (aboot.img) to get into it (the last section "In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs").
I know there's a way in Android to boot in a "safe mode" but I've only done it by accident and can't recall how. I don't know if that would make any difference anyway.
If you can use the hardware keys to get into the stock-looking recovery you could try re-wiping Cache but I wouldn't have much hope of that doing the trick, either.
I hate to say but if none of these things work the only way to get back into TWRP without the use of Android is to use LG Flash Tool 2014 to re-flash the 11A KDZ and start over.
I guess I'm going to have to write the detailed instructions for how to check MD5 hashes and add that into the OP, as that would be something I would ask if was done when anyone has problems after a flash.
Click to expand...
Click to collapse
So um ya, I failed to do what you stated on task 3 of your Rom installation. You told me to do this before installation:
3. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Obviously, first copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections. Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
So.... I pulled a stupid.....When reading this I thought you meant to go into my folders "on the tablet" and manually delete the things I put in there. I didn't realise you meant to do it through TWRP before installation lol. So after coming to grips with the idea that I now need to start completely over,,,, I rebuilt the entire thing correctly in 20 minutes. Sad this took me 3 days to learn everything by reading over countless forums. Your help was absolutely necessary to bring it all together. My tablet is fully upgraded and that was the best money I've spent in along time. The next time i get a device, you'll get first crack at helping me. If everything goes well, I'll make sure to double the donation next time. Your experience is valuable and should come at a cost. Thank you and I look forward to talking with you in the future. Take care! Now to get busy using this thing.
JBurch/cry said:
So um ya, I failed to do what you stated on task 3 of your Rom installation. You told me to do this before installation:
3. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Obviously, first copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections. Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
So.... I pulled a stupid.....When reading this I thought you meant to go into my folders "on the tablet" and manually delete the things I put in there. I didn't realise you meant to do it through TWRP before installation lol. So after coming to grips with the idea that I now need to start completely over,,,, I rebuilt the entire thing correctly in 20 minutes. Sad this took me 3 days to learn everything by reading over countless forums. Your help was absolutely necessary to bring it all together. My tablet is fully upgraded and that was the best money I've spent in along time. The next time i get a device, you'll get first crack at helping me. If everything goes well, I'll make sure to double the donation next time. Your experience is valuable and should come at a cost. Thank you and I look forward to talking with you in the future. Take care! Now to get busy using this thing.
Click to expand...
Click to collapse
Cool! Glad at least it was something simple, even if a little bit painful to fix. You must at least be a fast learner.
Maybe I'll separate that into two steps to distinguish them.
Enjoy! I hope we get 5.1.1 someday because 5.1.1 on the G3 is so much better than 5.0.x was. You're welcome and thank you! I never even took donations until a few months back when one or two people wanted me to.
Most of the time I enjoy just seeing someone successfully do whatever they're trying to do.
Thank you, I felt so much better using this than some sketch chinese program.
FL4NKENSTEIN said:
Thank you, I felt so much better using this than some sketch chinese program.
Click to expand...
Click to collapse
You're welcome! I know what you mean.
Hey. Not sure if I am posting in the correct thread so apologises if warranted.
I recently rooted my vk810 with king root. Seemed to be the only thing to work. Only after I rooted did I realize that king root probably was not the wisest way to go.
So I'm about to attempt to unroot and hopefully get this thing rooted and a decent rom working. I like the tablet but all the verizon crap and associated bloatware are driving me nuts.
A little background, I've used linux distros for a while now, but not comfortable with command line stuff. I'm that copy and paste guy...
Any ideas on where to begin? I see Mr warrior seems to be the guy. Just about all related searches end with a post by him. Kudos for helping everyone he has so far. People like him are the reason why the linux/android world is such a great place!
Thanks in advance!
Soundsofsublime said:
Any ideas on where to begin? I see Mr warrior seems to be the guy. Just about all related searches end with a post by him. Kudos for helping everyone he has so far. People like him are the reason why the linux/android world is such a great place!
Thanks in advance!
Click to expand...
Click to collapse
Just follow all of the directions in the first through fifth posts and they'll get you there. You'll need a Windows PC.
Some people have told about an app called "SuperSU Me" (not by @Chainfire) to replace Kingroot with SuperSU. I have no experience with that or links to it, however.
Thanks and you're welcome!
Lost on step 3.20
i think i messed up somewhere in the "VK810_twrp_2.7.0.1.zip" copy/paste section using X-PLORE. when i type in the "cd /data/local/temp" command in the emulator it
returns "sh: cd: /data/local/temp: no such file or directory". any help would be greatly appreciated.
for the record, this is my first time trying any type of root process.
thanks
***********************
update: i figured it out.
Slingb1ade said:
i think i messed up somewhere in the "VK810_twrp_2.7.0.1.zip" copy/paste section using X-PLORE. when i type in the "cd /data/local/temp" command in the emulator it
returns "sh: cd: /data/local/temp: no such file or directory". any help would be greatly appreciated.
for the record, this is my first time trying any type of root process.
thanks
***********************
update: i figured it out.
Click to expand...
Click to collapse
Thanks for the update. What did you figure out was the trouble? Didn't do the "SU" command first?
How to unlock boot loader anyone suggest me
zaccheo said:
How to unlock boot loader anyone suggest me
Click to expand...
Click to collapse
No one has done it. Someone more knowledgeable than I would have to tackle it.
roirraW "edor" ehT said:
Thanks for the update. What did you figure out was the trouble? Didn't do the "SU" command first?
Click to expand...
Click to collapse
i didn't pay attention to the provided instructions "20. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure)"
i was typing temp, needed to type tmp.
Unofficial release -TWRP recovery for the Galaxy J3 Emerge - SM-J327P, Qualcomm MSM8937
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 15/3/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.0-1_j327p_14317
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @Doctur, @infixremix, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.
Reserved
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Doctur said:
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Click to expand...
Click to collapse
Thanks for the heads up with the other member and your support. I'll report it.
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
JUSMEJOSE said:
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
Click to expand...
Click to collapse
No sorry i don't own this device.
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
View attachment 4081849
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Sent from my Nexus 5X using XDA-Developers Legacy app
rekids said:
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Click to expand...
Click to collapse
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Thank you so much ?, will let you know how it goes.
Sent from my Nexus 5X using XDA-Developers Legacy app
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
joeyjojojjjjjj said:
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
Click to expand...
Click to collapse
Pin request? Never heard of that before. Have you set a pin/password on your device?
Nevermind, my daughter pit an unlock pin on it. Got it now going to try this.
Everything went smooth! Thank you so much!
rekids said:
Everything went smooth! Thank you so much!
Click to expand...
Click to collapse
Thanks for the click, out of 141 downloaders only 3 were clickers.
I find it amsusing that the author of the thread below using stolen files from this one has just as many clicks.
https://forum.xda-developers.com/an...-j3-emerge-t3573551/post71443474#post71443474
.
No problems at all... Everything went perfect!
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Cyclic said:
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Click to expand...
Click to collapse
Yes I'd advise disabling Knox.
need help!!!!
ashyx said:
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Click to expand...
Click to collapse
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
pumkinhead13 said:
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
Click to expand...
Click to collapse
There's no way the patch did that. You must have wiped the system partition in twrp.
https://www.androidfilehost.com/?fid=817550096634755921
ashyx said:
There's no way the patch did that. You must have wiped the system partition in twrp.
Click to expand...
Click to collapse
uuuh no, so I did all the above said to do and everything was fine, it booted up (before i flashed the patch) then I went back into recovery, flashed the patch and selected "boot to system" it booted to samsung logo then at the top in small yellow writing just said "kernal" it sat there for 15 mins, before i pulled the battery, then flashed again....this time upon finish it stated "NO OS"