Related
[ THIS POST IS TEAMWIN'S STOCK TWRP POSTING. USE OF THE WORDS "US" AND "OURS" MEANS "DEES_TROY AND TEAMWIN" NOT HASHCODE ]
*** ALL CREDIT FOR TWRP BELONGS TO DEES_TROY AND TEAMWIN. ***
They do a BANG UP job on making a fantastic customizable touch-based recovery.
SEE BOTTOM OF THIS POST FOR DOWNLOAD / INSTALL INSTRUCTIONS
Donate to TeamWin:
http://www.teamw.in/project/twrp2
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2128848
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Tablet look:
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
** THIS IS A FLASHABLE .ZIP FILE FOR INSTALLING IN YOUR CURRENT VERSION OF TWRP **
DOWNLOAD:
[ DO NOT DOWNLOAD ANY FILES FROM TEAMWIN'S WEBSITE.
IN GENERAL, THEY ARE MEANT TO BE FLASHED TO UNLOCKED DEVICES AND WON'T WORK FOR KINDLE FIRE HD'S ]
You can download a flashable recovery zip and place in your SDCARD area on the device:
ON THE FOLLOWING DEV-HOST LINK
USE THE BLUE "DOWNLOAD NOW" BUTTON
-- DO NOT INSTALL AN EXECUTABLE DOWNLOADER TO YOUR SYSTEM! --
I'LL LOOK FOR A BETTER HOST WHEN I GET MORE TIME.
Mirror 1 : Download recovery zip from Dev-Host
INSTALL INSTRUCTIONS:
While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button)
Select "Install"
Navigate to where you placed the file on your device
Select the .zip filename
Swipe to confirm flash
Reboot
KNOWN ISSUES:
[07/08] Disabled the screen blank due to a display issue where screen doesn't come back on well.
BUGS:
First: I'd read through this thread and see if your issue isn't answered.
Second: Try googling for it
Third: If it seems like a Kindle Fire HD issue, then post in the thread.
Lastly: If you have found a bug, please consider posting it to TeamWin's github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #kindlefire-dev or #twrp on Freenode with your IRC client or just click this link.
error
im ending up with this error when i try to flash
Can you check the md5sum on that file and make sure it matches 4056520ee7b13be01d42d785cca2b15e?
Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.
Hashcode said:
Can you check the md5sum on that file and make sure it matches 4056520ee7b13be01d42d785cca2b15e?
Click to expand...
Click to collapse
the md5 does match
tried it again and this time it worked thanks hashcode
seokhun said:
Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.
Click to expand...
Click to collapse
Yes, I can probably do a .zip update. I'll need a night or 2. Been pretty busy.
Hashcode said:
Yes, I can probably do a .zip update. I'll need a night or 2. Been pretty busy.
Click to expand...
Click to collapse
and how is the kernel goings man?, good job with this
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery for KFireHD 7" [2013-04-02]
seokhun said:
Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.
Click to expand...
Click to collapse
Hey you can install the new version through fireflash also I just did with no problem
Sent from my KFTT using xda premium
As in, plugging in the .img recovery file Hashcode provided, leave everything else blank and just flash? Are you sure? Seems a little risky to me. If someone else can verify that, I'll do it, but I'm willing to wait for Hashcode's .zip, no offense.
seokhun said:
I'm willing to wait for Hashcode's .zip, no offense.
Click to expand...
Click to collapse
+1
Sent from my KFHD using xda premium
I promise u it works will post a video of proof by about 12 tonight if everyone would do this and leave hash code alone about petty crap maybe we would have cm 10.1 and custom kernel by :screwy:
Sent from my LG-E970 using xda premium
Respectfully disagree,
If people start bricking their devices because of unnecessary flashes, the threads will be overwhelmed with people griping and begging for help...
Personally I am waiting for cm10 as well and have not even installed recovery yet on my device due to this..
But I do understand that twrp allows a proper backup and honestly is something all android devices should have installed
Sent from my GT-P3110 using xda app-developers app
mrkhigh said:
Respectfully disagree,
If people start bricking their devices because of unnecessary flashes, the threads will be overwhelmed with people griping and begging for help...
Personally I am waiting for cm10 as well and have not even installed recovery yet on my device due to this..
But I do understand that twrp allows a proper backup and honestly is something all android devices should have installed
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.
Jester6 said:
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.
Click to expand...
Click to collapse
:good:+1
Jester6 said:
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.
Click to expand...
Click to collapse
You got wrong what he said. The user above stated that we're wasting hashcode's time by making him do zip updates for twrp (instead of flashing them), and he (the one you quoted) added that is better to update twrp with ZIPs since its less risky.
Sent from my KFTT using xda app-developers app
jailuis said:
You got wrong what he said. The user above stated that we're wasting hashcode's time by making him do zip updates for twrp (instead of flashing them), and he (the one you quoted) added that is better to update twrp with ZIPs since its less risky.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Either way, it makes little to no sense. I understand that hashcode has a lot on his plate but update zips are a simple enough process and take a small amount of time/work, now I don't know that about twrp as its not officially supported (to my knowledge) but an update zip for a ROM is a very easy process, I'm sure there's a bit involved in making twrp work for the kfhd but I don't imagine its crazy.
Thank You Hashcode for your efforts. An update zip would be sweet. Keep up the great work!
This is a Kinology HD using XDA Premium
video with instructions and proof of concept
seokhun said:
As in, plugging in the .img recovery file Hashcode provided, leave everything else blank and just flash? Are you sure? Seems a little risky to me. If someone else can verify that, I'll do it, but I'm willing to wait for Hashcode's .zip, no offense.
Click to expand...
Click to collapse
yes that's correct i need no one else to verify this but there's a video on my channel here>http://www.youtube.com/user/choppedncut79cutlass/videos <as for the rest of these space wasting comments i reply in the morn nite all work in the morning
So I got brave and decided to work with fastboot, and I can flash with the standard platform-tools procedure. I know I have fastboot using Hashcode's "getvar product" command, and booted into fastboot successfully. However, I don't know how to flash using the "fastboot -i 0x1949" command. Do I first CD to the folder that the file is placed in? A little help for a noob will be greatly appreciated, Hashcode, or anyone else well-versed in fastboot. Thank you!
I'd also like to know if the standard procedure will also work here. In other words, if I place the file in \platform-tools and ran the "fastboot flash <filename>.img", would it work? I'm afraid it would fail because of the Kindle's locked bootloader and how we're working with a 2nd one. Sorry, I'm very new to this whole bootloader thing and willing to learn.
Where ever fastboot is, I think.
This is a Kinology HD using XDA Premium
Dear Owners,
Discontinued
In this post you can find a multilingual (mainly European) modified rom for the smartphone Lenovo A820.
IMPORTANT NOTE!
The newer phones do not work well with S138 or older kernel (no info about S147).
The sympthom is that the touch screen works on inappropriate way: after the first screenlock it does not work again.
For this reason it is highly recommended that update your kernel if you have got this issue.
The kernel changer to S150 zip can be run from modified recovery (CWM, TWRP, COT, Carliv, etc...).
Note that all the things in this thread you do with your phone can be dangerous. I cannot take responsibility for your phone damage.
So, do it at your own risk.
Before you do anything, I recommend you to save your current ROM (I would say it is mandatory!)
There are many ways to save and I highlight some (links will be added later):
1, for non-rooted phones:
- SP_Flashtool, readback option.
- CWM (or TWRP) backup, if it is available on your phone
2, for rooted phones:
- MTKDroidTools backup
- command line dd-backup
In order to install this ROM, you need to have CWM recovery on your phone.
If you have not got this recovery or you do not know which recovery you have got, you have to read post#3 before you do anything.
If you get error during the installation of the ROM, see post#4.
The restore option of the CWM rcovery is not as good as it could have been expected, so please read post#4 carefuly for CWM restoration issues, tricks.
Update: CWM 6.0.4.0 with S150 stock kernel.
Just to clarify the power-on modes:
Normal phone mode: press the power button
Meta mode: VOLUME DOWN + POWER
Factory mode: VOLUME UP + POWER
Recovery mode: VOLUME DOWN + VOLUME UP + POWER
Consider the warranty issues, you need to backup you rom.
In addition, I always suggest to do a backup before install any new ROM to your phone.
You can do it with CWM recovery in backup menu.
About installation in general.
Pre-requisites: CWM recovery menu installed on your phone. (This ROM can be installed from CWM recovery.)
The ROM file must be saved on your physical SD card.
Enter into CWM recovery.
In CWM recovery you can go up/down with the volume up/down keys. The “enter” is the power button.
Choose the “install zip from SD card” menu item.
Choose the “choose zip from SD card” menu item.
Select the rom you want to install.
Choose “OK” in the menu item.
If you need a detailed explanation of its use, see the tutorial : http://bm-smartphone-reviews.blogspot.com/2012/02/complete-guide-to-clockworkmod-recovery.html
Right after the ROM installation has been finished, you can install gapps as well, before restart.
Windorws driver installation:
Please do not ask me about it. I use mainly Linux, which is more friendly.
What I did in XP under Virtualbox was:
Downloaded the Lenovo drivers from here: <link>
Manually added the com ports in control panel.
MOD CP4.0
V1
The modified rom has got the stock kernel - Lenovo A820_ydss_S135_130403
This completely changes your phone appearance, your Lenovo UI will be disappeared.
Also Lenovo applications are not integrated to this rom.
It will look like the stock Jelly Bean.
Main features:
-The firmware is rooted.
-Boot logo, boot/shutdown animations and sounds are changed to Lenovo.
-Minimalist appearance and content, for this reason you have to install google applications manually, from CWM recovery <link>. After gapps installation everything works well (many people wants to have mainly Google Play. It do work.)
-Slide unlock.
-Multilingual. For supported languages, see the screenshots.
-The default language/region is Hungarian, but you can easily choose your one.
Known bugs:
- I found was that the charging logo with turned off phone is not proper.
-the camera does not work adequately in video-camera mode.
-the default setting in some of the application is V987.
V2
The modified rom has got the stock kernel - Lenovo A820_S135_130403
The camera was changed to a non-multilingual one. It looked that the black screen in camcorder mode solved.
But after googleapps something went wrong... black screen again.
V3
The modified rom has got the stock kernel - Lenovo A820_S135_130403
In V3 there is not any significant changes (camera app was changed back to the multilingual one), but I modified the gapps, which caused the camcorder issue.
So, for this modified rom you need to use this gapps.
V3 download link: CP4.0-by-cappa72-v3 - dropbox
or
CP4.0-by-cappa72-v3 - 4shared
Bug: Still, the camera has got green lines in the case of playback.
CP4.1
V1
The kernel has changed to A820_YDSS_S130_130324.
The camera application does not generate green bands in playback.
The default language was set to English, default time zone was set to London.
CP4.1-by-cappa72-v1
You can use the googleapps mentioned for CP4.0-v3
CP4.2
V1
The kernel has changed to A820_S138_130419
CP4.2-by-cappa72-v1
Bug list
#3 - CP4.2-v1 - Wen try to choose themes, the laucher is Force Closed (FC) - Settings was modified to resolve this issue.
#4 - CP4.2-v1 - Serial number is 0123456789ABCDEF instead of the original S/N - not a real bug
#5 - CP4.2-v1 - Under the battery level of 15% the SystemUI is Force Closed (FC) - was a user error, when people deleted the necessary ui files.
CP4.3
This release will be the continuation of the 4.2, but with the newest available kernel (S150) and will (plan) contain all the things that are included in the 5.3.
This will not be with Aromainstaller and will contain the gapps.
Hopefully comng within two weeks.
MOD CP5.3
Available now (25.11.2013.)
CP5.3
V1
Change log; what’s new compared to CP4.2
Aromainstaller is used for optional installation possibilities.
- still Jelly Bean 4.1
- kernel is the stock S150
- Modified systemUI by [email protected] (1% battery signal; automatic hide function for non-used sim signal)
- Modified Settings by apeelme (sloving bug #3)
- Baseband is from the stock ROM S150.
- gps.conf is set to EU by default
- apns.xml is modified for Telenor-HU from “net” to “online”
- gps-tracker solver added to build.prop (dalvik.vm.execution-mode=int:fast)
- libvcodecdrv.so replaced to solve green bars in case of video playback.
- updated MobileUncleTools (2.9.5) in case of 3rd party SW.
There is no default ringtone set! Right after the installation you have to set the ringtone, message alert and so on... otherwise your phone will not play sound...
Important feature!
If you have already repartitioned with the script, you can simply install this ROM, it will recognise that the repartition had been done; and you do not have to run "disable internal SD card" script from CWM.
But please note that this function is onyl available with the repartition script; with Meteos rom editor repartitioning this function is not available.
Right after the installatio, there is not any sound set. Nor the ringtone, nor the message an alert. So, you have to set it first.
Available on mediafire : Link
md5sum: 86e241fcac6faf4fa6baf0f9cc4a18a0
Additional possibility:Change of FM radio
The FM radio can be changed back to Lenovo’s one with this script. It was requested by some people due to the fact that Lenovo’s FM radio can work without connecting the earphone.
The link is here. http://data.hu/get/6494163/FM-radio-change.zip
You can install it from CWM recovery, with the same method that you used during the installation of the ROM. This script does not affect any other part of the ROM, but the FM radio.
Repartition
Please DO NOT USE IT for Lenovo-based ROMs. Sometimes it can cause bootloop or other inconvenience.
The repartition of internal memory of the Lenovo A820 phone has been solved already.
With this action youd intednal SD card will be disappeared and will be added to the /data partition.
Before you do anything, make a CWM backup, and save all your data from internal SD card!
The easiest way is to use this CWM script, if you want to have the maximum available size (2,7GB) for the /data partition.
You have to install it from CWM recovery.
After the installation you need to do a factory reset.
After the factory reset, you have to disable your internal SD card, with CWM script.
And then, you can reboot your phone to check if yo have got the new size of /data partition:
settings --> storage
"internal data storage; full capacity 2,7GB"
"internal SD card; full capacity <your physical SD card capacity"
If the above data appear, you have successfully repartitioned you phone's internal memory!
If you want to have your data back, go into CWM recovery, and choose
backup and restore --> advanced restore --> <choose your save> --> Restore data
And then, your data are available again, after the reboot.
Please do not use it, if you do not want to have the 2,7GB of /data partition!
For Lenovo-based ROMs you need to use Meteos-apk for repartition of A820.
Internal/external SD card exchanger
If you want to use your physical SD card as the default one, and still want to use your emmc-SD card (aka internal SD card by default), you can change it by this CWM script.
Important link in summary:
The driver what works is here.
The original stock recovery is here
The autoroot package can be found here.
The preferred CWM is here.
The root script is here, you can install is from CMW, and your phone will be rooted.
The usable Flashtool is here.
The scattel file for Flashtool is here.
Credits:
bgcngm for the base of the ROM (BM1.0 for ZTE V987), and his amazing tutorials
iBotPeaches and brut.all for apktool
dsixda for his ROM kitchen which is really helpfull for easy-deodexing
Koush for his wonderfull CWM recovery
amarullz for his amazing AROMA installer
...and finally to all the devs whose apps, tweaks and scripts I have used on my custom ROMs
Very nice Thanks for your hard work and good luck
CWM recovery
Installing CWM on your phone
You need to install proper drivers to your computer.
Available (ported) CWM recoveries:
With newest kernel:
CWM recovery 6.0.1.2 - S150 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.4.0 - S150 - ported from [email protected] ZTE V967S recovery.
CWM recovery 6.0.1.2 - S138 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.1.2 - S135 - ported from [email protected] ZTE V970 recovery.
Option 1, with SP Flashtool
Download the SP_Flashtool software to your computer. Extract it to a directory, where you want to run it from.
Download the scatter file, which you will need if you want to use SP_Flashtool.
Download the CWM
(5.5.0.4, 6.0.1.2, 6.0.2.8; it is your decision)
Run the SP_Flashtool.
Browse your scatter file.
Choose only the recovery.
Tick the “DA DL all with checksum” (you can find it close to the download button). It is a really important point!
If your phone is connected, let’s disconnect it from the computer.
Turn off your phone. Take the battery out from your phone for 5 sec. Insert the battery to you phone. Keep it still turned off.
In the flashtool press the Download button.
Choose OK to the warning message.
Connect your phone to the computer.
The flashtool will flash the recovery into your phone.
When the green circle appears, wait for 5-10 secs, and the unplug your phone.
If everything went well, you can enter into the recovery menu (see 1st post, power-on modes)
Option 2, on rooted phone, with MobileUncleTools.
Install MobileUncletools 2.8.x or higher from the Play Store.
Save one of the CWM I linked to the root directory of your physical SD card.
- select menuitem Recovery Update. The program will list the available recovery images.
- choose the one, what you want to install
- It asks back: "Are you sure flash recovery!" - Use recovery file: <name of the recovery what you choose previously>. Tap to OK.
- After the flashing process it offers you to reboot into recovery. If you tap OK, it will automatically reboot your phone to recovery. If you tap cancel, you can use your phone as a phone.
- Before you tap to "reboot to recovery", I suggest you to wait approx. 5-10sec.
Use of the CWM.
If you enter into the CWM (6.x.x.x) recovery, the following buttons can be used:
- Power button : “enter”
- Volume down : step down in the menu
- Volume up : step up in the menu
- Soft key “option”: step down in the menu
- Soft key “back” : step back in the menu
In 5.x.x.x you cannot use soft keys, but the physical buttons works on the same way as in the case of 6.x.x.x
CWM restoration
I experienced failures in restoration of the CWM backup.
This was a real surprise for me because I have not faced this issue with other MTK phones.
So, the issue is that the CWM restoration does not work immediately.
In details:
-I saved the stock rom by CWM 6.0.1.2 (CWM was complied by Bruno, and I modified it for A820)
-For checking the restore function, I did a factory reset: the phone stopped working.
-I did the CWM restoration, but still the phone stopped at the boot animation. And stayed it for 15min. I removed the battery then.
In order to solve the issue, the following method was done:
-In the advanced restore I choose the restore /system (only!)
-After restoring the /system I turned off the phone took the battery out, waited 5 secs, inserted the battery back.
-Turning on the phone it worked again with the restored data, BUT the internal SD card was injured! I formatted the internal SD card – with this action I lost all my data that were saved on the internal SD card.
So, please be careful using it! Save your internal SD card data before the CWM restoration!
This was experience in case of all the available CWM (5.5.0.4, 6.0.1.2, 6.0.2.8).
Installation issues
Post#4 troubleshooting
If you cannot install the ROM by an error:
Code:
assert failed: getprop("ro.product.model") == "Lenovo A820"
E:Error in /sdcard/Lenovo-a820-update-CP4.0-v1.zip (status 7)
This is a safety feature, not a bug.
This error message is a warning that you have not got the proper CWM. (Most of the available CWMs are based on ZTE, STAR phones and contain improper model description.
My CWMs contain the proper one, I modified them, so you need to install a CWM I mod for Lenovo A820.
In this case you have to update your CWM to a ported one that I did.
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
ebsbow said:
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
Click to expand...
Click to collapse
If you have got CWM recovery on your phone (or a chinese one that has got "xx SD yyy ZIP" menuitem), then you can use root-zip, installing it from CWM recovery.
Thanks
Thanks
Where are the screenshots?
please add some screenshots.
deathhand said:
please add some screenshots.
Click to expand...
Click to collapse
I tried to upload some, but the server was down that time.
I will try it again tomorrow.
Thanks for this rom, I flashed it succesfull on the Lenovo A820, it also takes away that terrible skin from Lenovo.
Gapps link
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
1. Are you sure you downloaded the Gapps for Android 4.1.x? You should have this gapps version: gapps-jb-20121011-signed, this the right version you should flash. I first flashed the rom and after that the gapps.
I have reproduced your issue and you need to update the Google search app in the playstore, after that the errors are gone.
2. I have reproduced what you reported, I want to try if I can grab the original camera app from Lenovo and see if it still has the issue, but I don't think its a big problem, I bought the phone for someone else, but this issue is not to big, I don't suppose people often record with an smartphone and this rom at least got Dutch in, the original phone firmware was bloated with China Unicom bloatware, Lenovo skin and had no Dutch support.
3. Try GPSfix, ussualy this kinda works, but the MT6577 chip was know for having GPS problems, perhaps its the same with MT6589? But there are many apps out there that can help you fix it.
I think this in a great rom, Lenovo is a big brand in China, so many will choose Lenovo and with this rom you get rid off the terrible lephone skin, I mentioned this rom in my review about this phone
Oh here you got some screenshots.
Feel free to use them in the OP.
Don't know about you but I do use my device a lot for video recording.
I think it is imperative that all basic functions work flawlessly.
The custom rom's with android 4.2 also have an video bug at this time, which is a bit unacceptable.
I'm sure it will be sorted out :victory:
Well yes, but having fully Dutch support is better, you can always flash new update off the custom rom when it get fixed. I only recorded a few time video with my own smartphone.
Lebrija said:
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
Click to expand...
Click to collapse
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
cappa72 said:
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
Click to expand...
Click to collapse
Thank you for your time. I will try the new version. But, why have you used an older kernel?
By the way, with version 3 I also had some problems with the gyroscope when playing Real Racing 3.
Great work
Its great you released the update so fast, you brought us really good work. I think new owner off this phone is going be thankful, they requested me to buy a phone for them while I'm in China, and when I got it it was not fully Dutch supported, had the terrible skin.
So its great have this phone, because this way I can deliver it without the Chinese bloatware and with full Dutch language and ofcourse Google apps.
EDIT
The newest release gives me a black screen after I boot it up after having it flashed, so I have reverted back to your previous release.
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
TheTen said:
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
Click to expand...
Click to collapse
Update, I think I sorted it...
Bit of imagination (and could have totally done the wrong thing, but it seems to be making progress...)
I decided to take a known ROM install that I've tested and that works, which has a recovery.img included, and I renamed the recovery.img to recovery_bak. I then renamed my 'new' CWMRecovery image to recovery.img and dumped it in the directory with the ROM data that I got off NeedRom. I loaded up SPFlashTool and loaded the scatter file from that ROM, then deselected every component except 'recovery' and flashed it.
End result is that I have a phone which recovery-boots to the version 6 cappa-modded CWMR which I found on the Hungarian site, and in turn that CWMR has just installed both the required ZIP updates outlined in Post 1, and Cappa's ROM is now sat on my second A820 awaiting setting up...
I hope I did the right thing, and this won't come back to bite me in the ass later... The newer recovery.img was slightly larger than the old one, but I'm assuming that the scatter file isn't about storing specific pieces of the ROM in specific places based on exact size of file, and thus perhaps all things will continue to work swimmingly.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device specific page for i9500
Mirror 1
Mirror 2
Special thanks to SamerDiab for helping test.
TWRP Flasher BUILD 1.0 Noob EditionWhat Do You Get With TWRP Flasher ?
1. The Most Easiest Way To Flash TWRP Recovery.
2.A Full Guide on HOW To Flash TWRP Recovery.
What Do you Need To DO To USE The TOOL ?
1.Enable USB Debugging.
2.On S4 No Need To Install Drivers.
3.Plug in Your Phone And Sit Down And Realx.{Just Follow The Command Prompt}
Downloads :
TWRP Flasher Build 1 Noob Edition{WINDOWS Edition}
How To USE ?
1.Download And Extract To A Folder.
2.Copy TWRP.tar To Place-Recovey-Here Folder That Comes With The Tool.
3.Run TWRP Flahsher.
And Please Hit The Thanks Button.
KingCobra Rom's Run's Best With TWRP
It is not working for me.
I have just tried the GooManager method, it downloaded the openscript for the i9500 and installed. I then rebooted through a Restart>Recovery from inside Android OS it rebooted but it was not able to boot to TWRP, instead it rebooted twice and went back to Android OS.
I have not tested booting using 3 button combination yet. Will give it a try and report back.
Update: So if I try to boot with Volume Up + Home + Power then it does boot to TWRP with no problem. Weird. I am on Wanamlite 1.8 if it works.
Update: Disregard after a second reboot it did go to TWRP when rebooted into recovery from within the power menu in the ROM. All is working fine now. Thanks for the great work. I used to work with CWM but TWRP rulez!!!
Great!!! Working well for me...
Sent from my Octa using New Tapatalk 4
Guti1977 said:
It is not working for me.
I have just tried the GooManager method, it downloaded the openscript for the i9500 and installed. I then rebooted through a Restart>Recovery from inside Android OS it rebooted but it was not able to boot to TWRP, instead it rebooted twice and went back to Android OS.
I have not tested booting using 3 button combination yet. Will give it a try and report back.
Update: So if I try to boot with Volume Up + Home + Power then it does boot to TWRP with no problem. Weird. I am on Wanamlite 1.8 if it works.
Update: Disregard after a second reboot it did go to TWRP when rebooted into recovery from within the power menu in the ROM. All is working fine now. Thanks for the great work. I used to work with CWM but TWRP rulez!!!
Click to expand...
Click to collapse
Well wanam apm is working so it should be working
Yay TWRP! Welcome, Deestroy
Sent from my GT-I9500 using Tapatalk 5.0.203 Alpha
1700Mhz A15 and 1500Mhz A7 running together with 640Mhz GPU.
Mate - I was missing TWRP for so much time on I9500. It`s really cool that atleast some developers are brave enough to stay with I9500
Thanks bro...just flashed using SGS4 Flasher app from playstore and it works...yeahhhh....no need pc odin...missed twrp on my note2 and s3.
Sent from my GT-I9500 using xda premium
hazri1974 said:
Thanks bro...just flashed using SGS4 Flasher app from playstore and it works...yeahhhh....no need pc odin...missed twrp on my note2 and s3.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
GooManager can download the correct file and flash it for you automatically as well.
And the tool does to its easy to flash with it
Sent from my GT-I9500 using xda premium
When i install super wipe.zip of mike, to the finish this reboot in recovery, so no enter in recovery and have continue loop in galaxy i9500 logo.
Thank you very much, excelent work.
(i dont have this problem in any other recovery)
-Sorry for my bad english.
kirabyte said:
When i install super wipe.zip of mike, to the finish this reboot in recovery, so no enter in recovery and have continue loop in galaxy i9500 logo.
Thank you very much, excelent work.
(i dont have this problem in any other recovery)
-Sorry for my bad english.
Click to expand...
Click to collapse
You mean super wipe frim mike1986 right ?
I dont see a ARHD Here you must be rong this is Gt_i9500 forum not i9505
Sent from my GT-I9500 using xda premium
I really appreciate having this in my i9500.
I was missing it a LOT!
Thanks for your work.
I have tried and I can reboot into recovery, and boot from power off too.
Working great.
BTW, I'm using wanam's 1,8 and it works.
S.a.M.e.R_d said:
You mean super wipe frim mike1986 right ?
I dont see a ARHD Here you must be rong this is Gt_i9500 forum not i9505
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Of course, but the .zip is in phoenix rom 4.0, and i use for install a lot of roms...
I have I9500..
Thank you.
Awesome
Sent from my GT-I9500
Thanks a lot for bringing TWRP for I9500.. That's a solo thing which was being missed by many since many days! :victory:
Thanks for updating it on i9500. Tried almost all the options except themes and everything is working great. Just for info what is the cpu usage on recovery as I noticed phone getting a little more hot than usual.
Sent from my GT-I9500 using Tapatalk 4 Beta
Question regarding the restore
Hi All,
I haven't used it ever. I was on Philz. So just wanted to know if I can restore Nandroid backup created with Philz(which is CWM basically) using TWRP..
Help would be much appreciated..
sozofriend1234 said:
Hi All,
I haven't used it ever. I was on Philz. So just wanted to know if I can restore Nandroid backup created with Philz(which is CWM basically) using TWRP..
Help would be much appreciated..
Click to expand...
Click to collapse
No you canf restore but i highley request that u use twrp it faster loveleiyer to use full touch and more andriid os like si use it
Sent from my GT-I9500 using xda premium
*** DISCLAIMER ***
I work on projects that 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 my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
[SM-N9005] Samsung Galaxy Note 3 Safestrap
CURRENT PROJECT STATUS:
BETA
I had an XDA user request a build of Safestrap for the SM-N9005, and figured I might as well share it.
NOTE: Safestrap will not trip KNOX, because it doesn't not flash kernels
I know that the N9005 is an unlockable device but some users may want to save the warranty and only mess around with TW-based ROMs. That's what Safestrap is for. If you're unlocked you probably want CWM / TWRP installed as your recovery so that you can flash AOSP-based ROMs.
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.7.1.x (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 on the N3 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for different sizes of /system, /data and /cache partitions. The defaults *SHOULD* be good enough for flashing the stock-based ROMs.
NOTE: The bigger you make these 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?
Requirement: Root
[NEW FOR v3.75+ KK Safestrap] Requirement: busybox. If your stock ROM doesn't have it built-in you need to grab "Busybox" from the Play Store and run the installer.
Requirement: External SD card
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
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
INSTALL VIDEO by DMX: https://www.youtube.com/watch?v=_RZIyeUMK-Y&feature=youtube_gdata_player
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 the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Go into your old Safestrap app and use the "Uninstall Recovery" button
THEN, open a "file explorer" of some sort (even TW "My Files" will work)
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK
Grant SU access
Use the "Install Recovery" button
All set, now you can reboot and re-activate whatever rom-slot you were using
KNOWN ISSUES:
SEE POST #2
DOWNLOADS:
CONFIRM THAT YOU ARE USING AN SM-9005 SAMSUNG GALAXY NOTE 3
FIND YOUR STOCK OPERATING SYSTEM VERSION BELOW AND USE THAT FILENAME:
[KITKAT:ND3]
LATEST BETA FILE: Safestrap-HLTEXX-ND3-3.75-B01.apk
[JELLYBEAN]
LATEST FILE: Safestrap-HLTEXX-3.71-B02.apk
XDA Downloads
Mirror 1 (Crackflashers)
CHANGELOG
[2014-06-26] Updated hijack for KK bugs
[2014-06-26] Fixed ROM-SLOT support
[2014-06-26] Fixed internal storage mount issue
[2014-06-26] TWRP 2.7.1 base update
[2014-01-11] Initial SM-9005 release
As of version 3.6x, Safestrap Recovery is now based on TWRP 2.7.1.x. For more on TWRP you can visit their website: http://www.teamw.in/
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.
Special Thanks To
DeesTroy, bigbiff & TeamWin for all their hard work making TWRP such a fantastic recovery
XDA:DevDB Information
Safestrap Recovery v3.71 (JB) / v3.75 B01 (KK/ND3), Tool/Utility for the Samsung Galaxy Note 3
Contributors
Hashcode, DeesTroy, bigbiff & TeamWin
Version Information
Status: Beta
Current Beta Version: v3.75 B01
Beta Release Date: 2014-06-26
Created 2014-01-12
Last Updated 2014-06-26
Reserved
KNOWN ISSUES:
PLEASE USE STOCK TOUCHWIZ FROM SAMSUNG FOR YOUR STOCK ROM -- FLASH TO ROM-SLOTS
If you install Safestrap on a rom-slot it will show "not installed". *DO NOT INSTALL SAFESTRAP ON A ROM-SLOT*
Rebooting from a rom-slot will end up at a blank screen. Battery pull and re-power on.
Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again. (DEBUGGING THIS AS I GET TIME)
If you don't see files on "Micro SDcard" for some reason try tapping that area and swapping to "Internal Storage" and then back again.
No Aroma installer support. This is due to the stock S5 kernel framebuffer. To build a recovery which worked, it needed QCOM patches. So will Aroma.
If you try a .zip file with an Aroma installer, it will most likely just hang.
If you use the "4way reboot" mod, then "Reboot Recovery" button in the Safestrap APK won't work correctly.
Reserved
wonderfull work.
My knox is 0x1 but i think lot of people like your work.
Thanks
never thought it would be released for hltexx.
i read about it some time ago and was really surprised about the rom slots feature.
i like the idea of having an alternative rom on my device.
downloading it now, will give some feedback later.
Thank you Hashcode!!!
Atm i can say that backuping works fine....looking for an second rom to test with X-Note as Stock, Aroma installer is not supported for now.....
Sent from my Safestraped SM-N9005 BlackBox
i successfully installed echoe rom 5 into rom slot 1 !
i like safestrap very much, easy to use and self explaining.
if you already have twrp installed, you do not loose it but you don´t need it anymore.
booting to recovery brings up your original twrp, a normal reboot shows the splash screen from where you can launch safestrap.
trying to install a rom with aroma installer of course doesn´t work but i tried just to see what happens :
the screen just freezes and you need to reboot by holding down the powerbutton, thats all.
you can restore a twrp backup of an aroma based rom, that you made from the stock rom slot, to another rom slot (i did it with a backup of bobcatrom).
but it looks like it uses the internal storage directory of the stock rom slot.
edit: seems like the original storage/emulated/0 is always used. i can see all the files from stock rom after installing a complete new rom.
so this isn´t really good for having 2 totally seperate operating systems installed, is it ?
have to read some more about it...
thanks a lot hashcode !
edit:
from the safestrap blog:
DON’T RESTORE A CUSTOM ROM-SLOT BACKUP TO THE STOCK ROM. THIS WILL MOST LIKELY BRICK YOUR PHONE.
Great Job
Thanks Hashcode, great tool!
Using it on a SM N-9005 without problems except I have a couple of ROMs that do not activate Wi-Fi.
Any clues?
I would love to be able to use this on the N900T
Sent from my SM-N900T using Tapatalk
ktetreault14 said:
I would love to be able to use this on the N900T
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I've been using the AT&T Safestrap Recovery on my Tmobile N900T and it works perfect. I flashed the AT&T X-Note ROM port (in slot 1) that they have and it works fine on the N900T. It does install the AT&T CSC, but installing the TMO one causes crashing in the dialer (which also happens in the international rom currently out in the TMO forum). So, just keep the ATT CSC like it is. For Wi-Fi calling, I just boot back into the Stock slot and use the stock ROM.
The AT&T Safestrap: http://forum.xda-developers.com/showthread.php?t=2572978
The AT&T X-Note Port ROM: http://forum.xda-developers.com/showthread.php?t=2579773
sounds intresting...
Hashcode said:
...
CURRENT TESTS:
...
TEST #7: Restore stock ROM backup to stock slot: TESTING
TEST #8: Initial 2nd-init ROM installation on rom-slot RESULT: TESTING
TEST #9: Custom ROM flash on rom-slot: TESTING
...
Version Information
Status: Testing
Created 2014-01-12
Last Updated 2014-01-11
Click to expand...
Click to collapse
If I understand correctly right now all ROM slots boot using (all of them) the same kernel (which of course must be stock Samsung kernel in order to keep knox 0x0).
This means that with kernel 4.3 (and corresponding bootloader) all slots must also be 4.3, while with kernel 4.4.2 (and corresponding bootloader) all slots must also be 4.4.2 - is that correct?
Will existing version work with 4.4.2 or a new version will be needed?
Will this ever be able to backup efs like the official twrp? Also will this ever support aroma? I know you said the kernal doesn't support it, but I was wondering how mobile Odin can do it without tripping knox
Love your work, it is working like a charm
Sent from my SM-N9005 using XDA Premium 4 mobile app
Hi Hashcode
Yipee!!!
I'm so glad you decided to release this on the n9005.
i'm off on the weekend, will test this and let you know the outcome!!!
Again
Do not download. Please give another link.
@nguyenson318
Mirror 1: Goo.im Download <--- not working
Mirror 2: Crackflashers Download <--- is working
So far this is working perfectly on my note 3 n9005.
Have backup my stock (actual it a custom rom!!) and installed a couple of roms in the free slots and all is working.
Still testing the software out but its very good, esp. if you want to try all the rom being released without messing with your main system.
Still need to test whether restore works and at the moment i have notice that i still have CWM as my recovery but when booting to Safestrap TWRP takes over.
Like i said i'm still testing this great piece of software but Hashcode has done a great job making this work on the n9005
Well Done
I download from n9005 note 3 (Next Browser) but only 0.1KB is stopped.
nguyenson318 said:
I download from n9005 note 3 (Next Browser) but only 0.1KB is stopped.
Click to expand...
Click to collapse
Here is the file
To mods, please remove this post if it violates the forum rules
To Hashcode, if you prefer people to download from your links provided i shall remove this post, i do not wish to cause you any offense.
Thanks for creating a killer app and i hope you keep on improving this product
If you wish me to test any aspect of your software on my handset, please let me know
I'm sorry if i sound like an absolute noob...but this requires root.
Afaik rooting the Note3 trips the Knox warranty flag......thus no more warranty.
Am I wrong?
Nirak said:
I'm sorry if i sound like an absolute noob...but this requires root.
Afaik rooting the Note3 trips the Knox warranty flag......thus no more warranty.
Am I wrong?
Click to expand...
Click to collapse
This is for people who have rooted via kingo or URDLV etc that don't trip counter.
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
Installation Instructions
It will wipe your entire SD card! In order to make things work better, I've set it up to use the entire SD card as /data as opposed to having two partitions. The advantage is that you don't have to pick a size of /data.
If on a BML rom (stock-based GB)...
Untested, but is setup to hopefully work. If it doesn't flash my 6.0 Omni first
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. First time will fail and let you know its repartionning. Second time it will reboot a couple of times, don't be worried.
4. If you want gapps, reboot to recovery, wipe data+cache and install gapps.
5. If you want root, flash according to instructions in Post #3
If on an MTD rom (CM7 and all ICS+)
1. Reboot to recovery
2. Wipe data, dalvik/art cache, system, and cache partitions
3. Install zip. First time will fail and let you know its repartionning. Second time it will reboot a couple of times, don't be worried.
4. If you want root or Gapps, install them now.
The first boot can take several minutes. Be patient. If it takes 20+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess.
If you're coming from either the last Lollipop build or the initial pre-release Marshmallow build, there is a bug in TWRP that will prevent flashing anything but the ROM. To get around this, please flash the Marshmallow zip, then reboot to recovery, and then follow the typical instructions.
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
If you come across a bug, feel free to let me know by posting in this thread. I will not be working non-stop on this project, but will try to fix bugs that affect me as this is still my main phone (out of choice, not necessity).
This build is very close to the official AOSP source code. Recovery is TWRP but otherwise there aren't any added "features"
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully. Opengapps pico works on the latest 7.0 build, untested on 7.1 but should work just fine
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Camera (built-in app needs workaround, see below)
RIL
SMS
Recovery
Bluetooth - first time it won't enable if enabling through settings, back out and then second time it will. Works just fine from status bar pulldown
Wifi
Vibration
Automatic Brightness
Compass
GPS on T959P, untested on T959V
Headset Buttons
SElinux in enforcing mode - this may have broken the T959V's gps...
Partially working
Camera and Browser apps need to have all their permissions manually enabled through settings for full functionality. This is because I've used the older Camera app (which hasn't been updated for dynamic permissions) and the older Browser app as the new one is simply a test shell with no features (thanks Google!)
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+
Everything else is not tested!!!
XDA:DevDB Information
AOSP 7.x for Galaxy S 4G, ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99
Source Code: https://github.com/xc-racer99/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Created 2016-10-22
Last Updated 2016-10-21
Thanks Time!
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to the OMAP4 AOSP team for their work on porting CMA to a 3.0 kernel.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow https://source.android.com/source/initializing.html. The branch you want when you run repo init is the latest tag from https://source.android.com/source/build-numbers.html#source-code-tags-and-builds for your desired android version (7.0 or 7.1). Before you run repo sync, from the WORKING_DIRECTORY/.repo folder, run "git clone https://github.com/xc-racer99/local_manifests -b BRANCH" where BRANCH is either aosp-7.0 or aosp-7.1. Continue on with the build guide, the device codename you want is "galaxys4gmtd".
If you want to build the kernel, follow the instructions in WORKING_DIRECTORY/kernel/samsung/aries/AOSP_README. Put the resulting arch/arm/boot/zImage in device/samsung/galaxys4gmtd-kernel
Other aries devices (captivate, i9000, i9000B, vibrant) should be fairly easy to do (ie the galaxysmtd on my github as well as the captivate trees work). The fascinate and p1 would need a fair bit of work.
Changelogs
Changelog for 2016-12-19
December security patches
goes back to the older graphics drivers so hardware recording works but has a kernel patch to prevent crashes
Tweaked the graphics drivers options so it seems a little bit faster
Tweaked the RIL a little bit for better stability
Other things I've forgotten about, see github for details
Changelog for 2016-12-19-V2
Kernel without slowdowns....
Changelog for 2017-1-19
selinux to enforcing - this may break the T959V's GPS - if it does, let me know and send me a dmesg and I'll fix it
Update to the interactive governor - should have less slowdowns if using the default governor
Slightly better RIL reliability (I think)
Better low memory killing - we now don't run out of memory as often
Hardware decoding re-enabled
Slightly less intensive background services
Based on 7.1.1_r13
Source Code, Downloads, Root Options
Main Source
https://android.googlesource.com/
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see aosp-7.x branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see aosp-7.x branch).
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see aosp-7.x branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see aosp-7.x branch)
http://github.com/xc-racer99/android_patches for all the patches necessary for the device to work properly (see aosp-7.x branch)
Downloads!
All builds can be downloaded from AndroidFileHost at https://www.androidfilehost.com/?w=files&flid=58191
Gapps
The smallest http://opengapps.org/ package for 7.0 is known to work, but any small 7.0 gapps package should work. However, they will cause the device to slowdown significantly as they use a fair bit of RAM. Gapps are untested on 7.1
This ROM is compatible with MicroG (https://microg.org/ and http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616) gapps. This is an open-source reimplementation of Google Play Services that doesn't track you and uses way less battery than the original.
Root
Root is achieved via Magisk or SuperSU.
MagiskDue to our odd partition layout, you need to use my custom Magisk install zip (source code here) attached to this post and not the official install or the Magisk Manager install. Then follow the instructions on how to root/install other modules from http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Also, don't try to use the official Magisk uninstall tool as it won't work.
SuperSU
Please note: I've been told this doesn't work any more, YMMV
Again, we need a custom SuperSU install zip for it to work due to our partition scheme. It should be an all-in-one zip so it's simplier than Magisk (but not open source). This is based off of the latest (at time of writing) 2.79SR1 release, the diff is below
Code:
diff --git a/META-INF/com/google/android/update-binary b/META-INF/com/google/android/update-binary
index d437f6f..3a312bf 100644
--- a/META-INF/com/google/android/update-binary
+++ b/META-INF/com/google/android/update-binary
@@ -642,16 +642,23 @@ detect_systemless_required() {
find_boot_image
CONTINUE=true
+if false ; then
if [ -z "$BOOTIMAGE" ]; then
# no boot image partition detected, abort
return
fi
+fi
# extract ramdisk from boot image
rm -rf /sutmp
mkdir /sutmp
+if false ; then
check_zero "" "" "" "LD_LIBRARY_PATH=$RAMDISKLIB $BIN/sukernel --bootimg-extract-ramdisk $BOOTIMAGE /sutmp/ramdisk.packed"
+else
+ mount /ramdisk
+ cp /ramdisk/ramdisk.img /sutmp/ramdisk.packed
+fi
check_zero "" "" "" "LD_LIBRARY_PATH=$RAMDISKLIB $BIN/sukernel --ungzip /sutmp/ramdisk.packed /sutmp/ramdisk"
if (! $CONTINUE); then return; fi
@@ -1331,6 +1338,8 @@ else
ui_print_always "Boot image patcher"
ui_print "******************"
+if false ; then
+ # SGS Modification - we don't have a "real" boot image
ui_print "- Finding boot image"
find_boot_image
@@ -1357,6 +1366,10 @@ else
fi
check_zero_def "- Extracting ramdisk" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --bootimg-extract-ramdisk $BOOTIMAGE /sutmp/ramdisk.packed"
+else
+ mount /ramdisk
+ cp /ramdisk/ramdisk.img /sutmp/ramdisk.packed
+fi
check_zero_def "- Decompressing ramdisk" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --ungzip /sutmp/ramdisk.packed /sutmp/ramdisk"
if ($CONTINUE); then
@@ -1545,6 +1558,7 @@ else
check_zero_def "- Calling user boot image patch script" "sh /data/custom_boot_image_patch.sh /sutmp/boot.img"
fi
+if false ; then
if ($CONTINUE); then
DEV=$(echo `resolve_link $BOOTIMAGE` | grep /dev/block/)
if [ $? -eq 0 ]; then
@@ -1564,6 +1578,10 @@ else
dd if=/sutmp/boot.img of=$BOOTIMAGE bs=4096
fi
+else
+ cp /sutmp/ramdisk.packed /ramdisk/ramdisk.img
+ umount /ramdisk
+fi
rm -rf /sutmp
fi
Link for the download ROM is not working... it is private... ?!?
Here is the link to the rom that is not private https://www.androidfilehost.com/?w=files&flid=58191
pickandrew said:
Link for the download ROM is not working... it is private... ?!?
Click to expand...
Click to collapse
Shaggy_thecat said:
Here is the link to the rom that is not private https://www.androidfilehost.com/?w=files&flid=58191
Click to expand...
Click to collapse
Thanks, I used the link that I would use if I was already logged in, my bad. OP is now updated.
It's been a while, no home internet and very busy life lately but the time I did get The 7.0 zip to flash (0930) it was running very well, no random reboots and limited freezes (just 1 really)
BUT. I always reinstall a new ROM to get the process down and- I haven't been able to get it running again. Let alone with root which I haven't managed to do. When I install the ROM now it gives me a quick first boot however it says encryption unsuccessful and asks me to reset. Resetting and factory resetting as well as formatting won't help it.
Excellent work ^_^ you're becoming the new SGS4G guru around here
As for a new setting in the dev options, labeled Consistent Logging-- if I turn this on is it A: Safe in terms of information vulnerability and B: Will it fill up my SD card quickly with a mass amount of logging data?
graycow9 said:
It's been a while, no home internet and very busy life lately but the time I did get The 7.0 zip to flash (0930) it was running very well, no random reboots and limited freezes (just 1 really)
BUT. I always reinstall a new ROM to get the process down and- I haven't been able to get it running again. Let alone with root which I haven't managed to do. When I install the ROM now it gives me a quick first boot however it says encryption unsuccessful and asks me to reset. Resetting and factory resetting as well as formatting won't help it.
Excellent work ^_^ you're becoming the new SGS4G guru around here
As for a new setting in the dev options, labeled Consistent Logging-- if I turn this on is it A: Safe in terms of information vulnerability and B: Will it fill up my SD card quickly with a mass amount of logging data?
Click to expand...
Click to collapse
Hmm, flash the ROM, go into recovery, change the filesystem of /data to ext4 or f2fs. The error sounds as if the sdcard is formatted as fat while it shouldn't be. If that doesn't work, please send me the contents of /sdcard/aries_mtd.log after you've installed it.
Hadn't noticed the new "persistent logging" section. I suspect that what it does it keep the logcat contents over a reboot. Since the logcat does have a max size, it is probably safe to enable it. I highly doubt it contains any more info than a regular logcat.
Thanks for keeping this device alive in this community! My kids wanted to use it for simple games so I dusted it off and came here to see if anything was still in development and sure enough there was!
I tested going from BML stock and it worked! I had to restart the install 5 times, but it ultimately took. The first two times installed TWRP, then it rebooted into TWRP. Then it took 3 additional times before it went through the whole install. It booted up fine, but I had messed up and forgot to do a full reset before install gapps. So it would boot the encryption screen telling me it was interrupted and I had to reset the phone. Unfortunately at that point no matter what I did it would always boot to that encryption error screen. So I wiped completed and started over but mistakenly flashed the 7.1 build. It went through but was stuck on a boot loop. So now i can't install 7.0 because it keeps telling me it can't install over newer builds. Is there anything I can do to fix this or do i have to start from stock all over again?
Edited* Update
I went ahead and started from scratch but still ran in to the same problem with the encryption. Didn't install gapps this time.
Domunus said:
Thanks for keeping this device alive in this community! My kids wanted to use it for simple games so I dusted it off and came here to see if anything was still in development and sure enough there was!
I tested going from BML stock and it worked! I had to restart the install 5 times, but it ultimately took. The first two times installed TWRP, then it rebooted into TWRP. Then it took 3 additional times before it went through the whole install. It booted up fine, but I had messed up and forgot to do a full reset before install gapps. So it would boot the encryption screen telling me it was interrupted and I had to reset the phone. Unfortunately at that point no matter what I did it would always boot to that encryption error screen. So I wiped completed and started over but mistakenly flashed the 7.1 build. It went through but was stuck on a boot loop. So now i can't install 7.0 because it keeps telling me it can't install over newer builds. Is there anything I can do to fix this or do i have to start from stock all over again?
Edited* Update
I went ahead and started from scratch but still ran in to the same problem with the encryption. Didn't install gapps this time.
Click to expand...
Click to collapse
Ok, sounds like a messed up somewhere. I'll do some testing and try to release an updated build. Could you please post the output of /sdcard/aries_bml.log and /sdcard/aries_mtd.log? The "Encryption Unsuccessful" message sounds as if the SD wasn't properly formatted to ext4/f2fs.
Hi xc-racerr99, I found what the issue was. Apparently I had an extra partition on the sdcard. After removing it and running the install script again everything booted up and i'm now using the ROM! It's awesome I have Nougat on this old Galaxy S. Without Gapps it's been running really stable and very responsive..
However, at this point, I've tried opengapps pico and TKgapps pico and neither work. The script runs and says update completed, but it's too fast. When I boot to the ROM no gapps were installed. Is there another gapps you would recommend trying?
Domunus said:
Hi xc-racerr99, I found what the issue was. Apparently I had an extra partition on the sdcard. After removing it and running the install script again everything booted up and i'm now using the ROM! It's awesome I have Nougat on this old Galaxy S. Without Gapps it's been running really stable and very responsive..
However, at this point, I've tried opengapps pico and TKgapps pico and neither work. The script runs and says update completed, but it's too fast. When I boot to the ROM no gapps were installed. Is there another gapps you would recommend trying?
Click to expand...
Click to collapse
Odd, I thought my install script removed the extra partition.
Anyways, it sounds as if there's some issue with recovery. You could try replacing the ramdisk-recovery.img in the ROM zip you downloaded with the one from https://www.androidfilehost.com/?fid=457095661767105384. Then reboot to recovery and flash your gapps package again.
Doesn't work....
I'll try to do some more testing with gapps and from stock with 1 or 2 partitions when I get a chance.
I figured out a sure fire way to boot 7.0, I'm running it as I respond with XDA app right now. But to keep it short if possible, I just fix permissions then factory wipe before I run the zip- do this while on CWM right after you heimdall to BML.
So to recap:
1- Flash to stock via heimdall
2- Fix permissions + factory wipe
3- Flash 7.0 zip
4- TWRP should boot- so flash ROM once more - wipe caches
5- Reboot and chew some nougat
Will follow up with a log next time I try to get the 7.1 rolling. ?
Oh! And when I add my email (hotmail) I get a bad handshake everytime. Do I need gapps to sync my contacts?
Sent from my SGH-T959V using XDA-Developers mobile app
graycow9 said:
I figured out a sure fire way to boot 7.0, I'm running it as I respond with XDA app right now. But to keep it short if possible, I just fix permissions then factory wipe before I run the zip- do this while on CWM right after you heimdall to BML.
So to recap:
1- Flash to stock via heimdall
2- Fix permissions + factory wipe
3- Flash 7.0 zip
4- TWRP should boot- so flash ROM once more - wipe caches
5- Reboot and chew some nougat
Will follow up with a log next time I try to get the 7.1 rolling.
Oh! And when I add my email (hotmail) I get a bad handshake everytime. Do I need gapps to sync my contacts?
Sent from my SGH-T959V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, I get a bad handshake as well. Only happens with hotmail/oulook accounts, my gmail and my other email work just fine.
I figured out what was causing the issues with install from BML - on TWRP boot, it wasn't setting up the sdcard properly. I've now fixed it so that it should work regardless (in the next build, obviously).
Anyways, it sounds as if there's some issue with recovery. You could try replacing the ramdisk-recovery.img in the ROM zip you downloaded with the one from https://www.androidfilehost.com/?fid=457095661767105384. Then reboot to recovery and flash your gapps package again.
Click to expand...
Click to collapse
Gave this a try and still no luck.
Update **
It actually killed the recovery. Recovery just keeps crashing and rebooting when trying to get in to it. Tried it from the a clean install and same results. Will wait for your next build. Thanks for putting time in to this!
Odd, it lets me add my gmail but only syncs my emails- no option for contacts still. I ought to keep a vcf from my other device jic.
The performance is even better than M and it doesn't have the weird battery glitch anymore ?? (I think the new partition layout helped a lot.)
Another thing I noticed, sometimes my SIM won't register or gives me a no signal indicator. I can't get root still either[emoji14]still poking around. Looking forward to the next build ?
Edit: Another bug I noticed is the inability to save files through the browser or Tumblr app for example.
(By the way, just wanted to add, I hope I'm still being more help than a nag or something. I aim to be helpful. So I look for things that seem astray. Heh)
Sent from my SGH-T959V using XDA-Developers mobile app
graycow9 said:
Odd, it lets me add my gmail but only syncs my emails- no option for contacts still. I ought to keep a vcf from my other device jic.
The performance is even better than M and it doesn't have the weird battery glitch anymore (I think the new partition layout helped a lot.)
Another thing I noticed, sometimes my SIM won't register or gives me a no signal indicator. I can't get root still either[emoji14]still poking around. Looking forward to the next build
Edit: Another bug I noticed is the inability to save files through the browser or Tumblr app for example.
(By the way, just wanted to add, I hope I'm still being more help than a nag or something. I aim to be helpful. So I look for things that seem astray. Heh)
Sent from my SGH-T959V using XDA-Developers mobile app
Click to expand...
Click to collapse
I've never used the contact sync.
With SIM not registering, it's because Google introduced a bug and the workaround the bug causes the SIM to occasionally not work. One of the problems with legacy devices I guess.
With the files not saving, manually grant the storage permission in Settings->Apps - it doesn't seem to automatically update for most apps.
With root, sounds like I should modify the SuperSU install zip as it's easier to use (but not open-source). For the PHH Superuser, you need
1) The Magisk-7-SGS.zip from my thread.
2) The phh-superuser-r259.zip from the Magisk root thread (link in OP)
3) The PHH Superuser app from the Play Store or FDroid
Even then, it only works for certain apps as it doesn't mount anything to /system/xbin/su which is what some apps look for
Edit: And I have no issues if you keep posting here with the problems you find, it's good to know.
bootloop
just tried to flash this 7.1 rom from your omnirom 6.0. Seemed to flash ok as described. couldn't get pico opengapps to flash but ignored it. Now it's stuck in a bootloop and I can't get into recovery using hardware buttons. Any guidance as to how I should proceed? As a relative novice, can I push a new recovery through ADB and try again?
asmalldharma said:
just tried to flash this 7.1 rom from your omnirom 6.0. Seemed to flash ok as described. couldn't get pico opengapps to flash but ignored it. Now it's stuck in a bootloop and I can't get into recovery using hardware buttons. Any guidance as to how I should proceed? As a relative novice, can I push a new recovery through ADB and try again?
Click to expand...
Click to collapse
Well, it depends on where you are bootlooping. If you're stuck at either of the first two splash screens, then you're out of luck with ADB as it isn't available yet. If you're bootlooping but getting to the bootanimation, then you can. To do so, run
Code:
$ adb root
$ adb shell mkdir /data/ramdisk
$ adb shell mount /dev/block/mtdblock5 /data/ramdisk
$ adb push ramdisk-recovery.img /data/ramdisk
$ adb reboot recovery
where ramdisk-recovery.img is from the AOSP 7.0 zip.
If you're stuck at the first or second splash screens, then you need Odin or Heimdall. With heimdall, you can do
Code:
$ heimdall flash --KERNEL boot.img
where the boot.img is the one from Omni 6.0, the one from 7.x won't work on its own as the recovery is not stored in it. You can use Odin to go back to stock.
I haven't tried gapps so I guess I should sometime and see what the issue with them is.
Gets to the second splash screen. I'll give that a shot when i have some free time. I'm really looking forward to getting this working as I'm amused by the idea of my oldest android phone running the newest OS before my other two.
Update: couldn't get it to work with my cheap laptop. Kept throwing up the libusb 12 error. Then when i finally gave up and pulled the battery, I noticed it was starting to bulge a little. I think I'm out for a while. I'm hoping i can come back to this soon.
Sent from my A0001 using XDA-Developers mobile app