Database Info

Upgrading to Jellybean OTA, Red Triangle fix!

This is the same guide I posted in the OTA failure thread, but it got buried, so I decided to make it its own thread.
This will fix the red triangle when installing the OTA, when it is caused by a missing or mismatched /system file. Android OTAs usually check the integrity of /system, because when installing, it doesn't do a full wipe, just updates the parts that need to be updated. This guide reflashes the .30 update so you ill have all proper apks and other /system files (build.prop). You could extract each individual file from the blob, but if you have more than one file that needs replacing its a painstaking process of attempting the flash, getting an error and replacing it, this method just replaces all files in /system to stock.
Once you fail the OTA, you won't be able to receive it from the asus servers again, so you have to manually copy the update file (dlpkgfile) to the proper place, and create the correct command. I have heard that wiping cache and data on DMClient and CMClient will fix that issue, but it didn't work for me.
Another misconception is that doing a factory reset will fix the issue. It will fix not being able to download the OTA, but you will still won't be able to install it. A factory reset simply wipes /data, which all downloaded apps, and settings are stored, it doesn't affect /system or magically reinstall the apps in system.
I'm pretty sure you need a microSD card for this, but not 100% sure.
I had deleted(not frozen) some apks on .30, and when I got the ota it had the red triangle. I then tried copying dlpkgfile to /cache and doing it that way, it also gave the red triangle(because I hadn't restored the apps). After a few hours of fiddling with the .30 firmware I finally got it back to stock then used the dlpkgfile method. You also don't lose any data this way!
Steps 1-5 restores stock .30 if you have deleted any apps or can't figure out what changes are causing it to get the red triangle. Steps 6-11 are actually for installing Jellybean.
1. Download your SKU of .30 from the Asus Site
2. Unzip it once and place it on the external microSD card
3. Rename it to EP201_768_SDUPDATE.zip
4. Power off the device, then turn it back on while holding volume down
5. When the text appears hold down volume up to boot into recovery, it should recognize the .30 firmware and install it
6. Root your device, you will need this to copy files to cache, if you want to keep root, download SuperSU, run it, let it update the binary, then install and backup SU with OTA Rootkeeper
7. To install the Jellybean OTA, find a download link for your version of the dlpkgfile (Here is the US version, http://d-h.st/W8Y Thanks to bartleyg82 )
8. Copy to /cache and rename to dlpkgfile, if not already named that, NO EXTENSION
9. Create a file called command, under /cache/recovery, with the following text --update_package=/cache/dlpkgfile (I did this by doing echo "--update_package=/cache/dlpkgfile" >> /cache/recovery/command )
10. Power down the devices and power up using teh same volume down volume up technique as before
11. You should have Jellybean!
Sent from my ASUS Transformer Pad TF700T using xda premium

Can you give a little more explanation for "Create a file called command, under /cache/recovery, with the following text update_package=/cache/dlpkgfile (I did this by doing echo "update_package=/cache/dlpkgfile" >> /cache/recovery/command )"
Is this a simple .txt file?
Do you think you could upload the file you used?
I am having this same problem updating to jelly bean and I am hoping your fix will cure... Thanks!

I finally managed to find my mistake ...
I always tried to use the WW SKU dlpgkfile, because I bought it with WW SKU...
Just realized my tf700 changed from WW to US?? How is this even possible??
Can you give a little more explanation for "Create a file called command, under /cache/recovery, with the following text update_package=/cache/dlpkgfile (I did this by doing echo "update_package=/cache/dlpkgfile" >> /cache/recovery/command )"
Is this a simple .txt file?
Do you think you could upload the file you used?
I am having this same problem updating to jelly bean and I am hoping your fix will cure... Thanks!
Click to expand...
Click to collapse
You have to use ES Explorer. ( for free in Play Store)
Just navigate to "Cache/recovery" and add a new file.
Name this file "command"
Open and edit it with ES-Explorer to "--update_package=/cache/dlpgkfile"

Thank you very much for this guide !
Firmware upgrade to JB for WW versions (upgraded from .30)
(Thanks to Cryptopone, original post)

moah909 said:
4. Power off the device, then turn it back on while holding volume down
5. When the text appears hold down volume up to boot into recovery, it should recognize the .30 firmware and install it
Click to expand...
Click to collapse
its nice to see that it works 4 many people ... but i get stucked on point 5 .. starting and after 3-5 sec. red triangle ..
made everything: tried with factory reset, DM/CM .. really everything that is mentioned in forum .. fact is that a cant install .30 .. with and without root, with and without rootkeeper etc. ... no changes made on apps, no freeze etc. .. everytime this $%&// triangle
any suggestions?
{
"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"
}

Are you using an external microSD the errors appear to be about not being able to find /sdcard
Sent from my XT894 using xda premium

leberkas said:
its nice to see that it works 4 many people ... but i get stucked on point 5 .. starting and after 3-5 sec. red triangle ..
made everything: tried with factory reset, DM/CM .. really everything that is mentioned in forum .. fact is that a cant install .30 .. with and without root, with and without rootkeeper etc. ... no changes made on apps, no freeze etc. .. everytime this $%&// triangle
any suggestions?
Click to expand...
Click to collapse
try reformatting the sd card to fat32 the copy the EP201_768_SDUPDATE.zip back onto it.
this silly step has suddenly allowed me to reflash .30. Last night I tried many times to reflash to .30 and nothing worked.

moah909 said:
This is the same guide I posted in the OTA failure thread, but it got buried, so I decided to make it its own thread.
This will fix the red triangle when installing the OTA, when it is caused by a missing or mismatched /system file. Android OTAs usually check the integrity of /system, because when installing, it doesn't do a full wipe, just updates the parts that need to be updated. This guide reflashes the .30 update so you ill have all proper apks and other /system files (build.prop). You could extract each individual file from the blob, but if you have more than one file that needs replacing its a painstaking process of attempting the flash, getting an error and replacing it, this method just replaces all files in /system to stock.
Once you fail the OTA, you won't be able to receive it from the asus servers again, so you have to manually copy the update file (dlpkgfile) to the proper place, and create the correct command. I have heard that wiping cache and data on DMClient and CMClient will fix that issue, but it didn't work for me.
Another misconception is that doing a factory reset will fix the issue. It will fix not being able to download the OTA, but you will still won't be able to install it. A factory reset simply wipes /data, which all downloaded apps, and settings are stored, it doesn't affect /system or magically reinstall the apps in system.
I'm pretty sure you need a microSD card for this, but not 100% sure.
I had deleted(not frozen) some apks on .30, and when I got the ota it had the red triangle. I then tried copying dlpkgfile to /cache and doing it that way, it also gave the red triangle(because I hadn't restored the apps). After a few hours of fiddling with the .30 firmware I finally got it back to stock then used the dlpkgfile method. You also don't lose any data this way!
Steps 1-5 restores stock .30 if you have deleted any apps or can't figure out what changes are causing it to get the red triangle. Steps 6-11 are actually for installing Jellybean.
1. Download your SKU of .30 from the
2. Unzip it once and place it on the external microSD card
3. Rename it to EP201_768_SDUPDATE.zip
4. Power off the device, then turn it back on while holding volume down
5. When the text appears hold down volume up to boot into recovery, it should recognize the .30 firmware and install it
6. Root your device, you will need this to copy files to cache, if you want to keep root, download SuperSU, run it, let it update the binary, then install and backup SU with OTA Rootkeeper
7. To install the Jellybean OTA, find a download link for your version of the dlpkgfile (Here is the US version, ] Thanks to bartleyg82 )
8. Copy to /cache and rename to dlpkgfile, if not already named that, NO EXTENSION
9. Create a file called command, under /cache/recovery, with the following text update_package=/cache/dlpkgfile (I did this by doing echo "update_package=/cache/dlpkgfile" >> /cache/recovery/command )
10. Power down the devices and power up using teh same volume down volume up technique as before
11. You should have Jellybean!
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
trying to update using this method. still not working no matter what i do. tried putting files in /cache and even at the root of my sdcard. still nothing. i am rooted locked up tight and running .30 firmware. havent added or deleted anything just did a factory reset and everything. HELP PLEASE!

Keeps failing
I reloaded .30 with no problems and then tried the JB update manually. It fails every time.

Aski1 said:
I finally managed to find my mistake ...
I always tried to use the WW SKU dlpgkfile, because I bought it with WW SKU...
Just realized my tf700 changed from WW to US?? How is this even possible??
You have to use ES Explorer. ( for free in Play Store)
Just navigate to "Cache/recovery" and add a new file.
Name this file "command"
Open and edit it with ES-Explorer to "--update_package=/cache/dlpgkfile"
Click to expand...
Click to collapse
THIS worked, finally. The OP is missing the -- before update_package. I kept failing step 9 repeatedly.
If you are using ADB to create that command file it would be:
echo "--update_package=/cache/dlpkgfile" >> /cache/recovery/command
I sincerely thank the OP for the guide, but I was pulling my hair out trying to figure out what I was dong wrong... the file was missing those -- because I was copying and pasting the command from the OP.

moah909 said:
Are you using an external microSD the errors appear to be about not being able to find /sdcard
Sent from my XT894 using xda premium
Click to expand...
Click to collapse
using external SD .. tried to make a fresh format fat32 .. tried another SD .. same triangle .. i am just a littlebit unamused hmm
complete log of my last try .. my knowledge is not big enough to solve this .. and sry 4 the image, 2nd post, so not allowed to insert links ..

oh, I'm sorry for all the hair loss! Thanks for pointing it out, fixed it in the OP.
Sent from my XT894 using xda premium

moah909 said:
oh, I'm sorry for all the hair loss! Thanks for pointing it out, fixed it in the OP.
Sent from my XT894 using xda premium
Click to expand...
Click to collapse
LOL. Thanks. No problem at all. (I'm actually quite folliclely impaired already... so it was really tough to find hair to pull out of my head anyway. TLDR: I'm balding already, hence the joke.)
I was being sincere about the thank you for posting those instructions. They helped a lot... once I figured out what was missing.

cant explain it .. BUT: .. was still on .30 .. market gave me an update for "[email protected]" .. try 23. .. suddenly: .30 stock update ..
changed NOTHING .. only the update of this app ... now 15min later on JB ... root missing, but thats my fault, will come back sometimes ... so .. thanks 4 letting my cry ^^

Video
make a video showing all steps and you'll be a star

TeamWin Recovery Project TWRP Recovery V2.4 Blaze4G UPDATED 1/26

{
"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"
}
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
SOURCE: https://github.com/TeamWin/Team-Win-Recovery-Project
Submit Code Change: http://teamw.in/twrp2-gerrit
Live Support: http://webchat.freenode.net/?channels=twrp
Flash attached zip in recovery...
FIXED: mount internal and external in recovery... Huge Thanks to sidneyk

Thanks ! just flashed and rebooted just fine, I looked it over real good but didnt do any wipes or flash a rom with it yet but it seems very smooth clean and fast. I may do a backup and try flashing a rom with it soon and let you know how it goes.. I like the layout much better
thanks
---------- Post added at 06:54 PM ---------- Previous post was at 06:01 PM ----------
did a backup and was able to name it and choose to put it on external, did a full wipe and just flashed [ROM][UNOFFICIAL]Slim-3.1.0-t769 STRUCK (Updated 1/21/13) successfully useing TWRP even used the mount storage and coppied the files over while in recovery. did notice that recovery rebooted itself a couple times back into recovery. I could not get unmount to go so just unpluged usb and recovery rebooted. maybe that is normal?? overall so far is working great!
Thanks again

I just flashed this recovery over your previous TWRP recovery and looks pretty good. I haven't tried flashing anything yet or doing any backups, I'll get to that later on. One thing I did notice though is that I'm still not able to see the internal sdcard in this recovery no matter what I've tried, it always just shows external sdcard. I don't know if it will help or not, but VividBoarder has a working TWRP recovery, which he calls version 2.3.2.3, for the Asus TF101 tablet that is 4.2.1 JB compatible and sees both internal and external storage and can flash from or backup to either. Here is the link to his thread, in case you want to look for possible ideas. Thanks and keep up the good work.
http://forum.xda-developers.com/showthread.php?t=1818452

sidneyk said:
I just flashed this recovery over your previous TWRP recovery and looks pretty good. I haven't tried flashing anything yet or doing any backups, I'll get to that later on. One thing I did notice though is that I'm still not able to see the internal sdcard in this recovery no matter what I've tried, it always just shows external sdcard. I don't know if it will help or not, but VividBoarder has a working TWRP recovery, which he calls version 2.3.2.3, for the Asus TF101 tablet that is 4.2.1 JB compatible and sees both internal and external storage and can flash from or backup to either. Here is the link to his thread, in case you want to look for possible ideas. Thanks and keep up the good work.
http://forum.xda-developers.com/showthread.php?t=1818452
Click to expand...
Click to collapse
Im not sure what the difference is between our phones but I am able to choose to back up between the internal or external and can mount either of them and can choose which one to install from. I can see both and access both sdcard and was running AOKP when I flashed the TWRP over CWM.
it is running great on my blaze! Im not a dev so i have no clue as to why. I did not wipe anything when I flashing TWRP. just flashed and rebooted and into AOKP just fine then rebooted into recovery to backup and flashed Slim rom.
---------- Post added at 11:40 PM ---------- Previous post was at 11:08 PM ----------
woodyjlw said:
Im not sure what the difference is between our phones but I am able to choose to back up between the internal or external and can mount either of them and can choose which one to install from. I can see both and access both sdcard and was running AOKP when I flashed the TWRP over CWM.
it is running great on my blaze! Im not a dev so i have no clue as to why. I did not wipe anything when I flashing TWRP. just flashed and rebooted and into AOKP just fine then rebooted into recovery to backup and flashed Slim rom.
Click to expand...
Click to collapse
I guess I was wrong. I just went back in and double checked myself it shows the option for internal sd but when I choose to mount it with TWRP I get my external 16 gig instead. so I guess that is what your getting too??

woodyjlw said:
Im not sure what the difference is between our phones but I am able to choose to back up between the internal or external and can mount either of them and can choose which one to install from. I can see both and access both sdcard and was running AOKP when I flashed the TWRP over CWM.
it is running great on my blaze! Im not a dev so i have no clue as to why. I did not wipe anything when I flashing TWRP. just flashed and rebooted and into AOKP just fine then rebooted into recovery to backup and flashed Slim rom.
---------- Post added at 11:40 PM ---------- Previous post was at 11:08 PM ----------
I guess I was wrong. I just went back in and double checked myself it shows the option for internal sd but when I choose to mount it with TWRP I get my external 16 gig instead. so I guess that is what your getting too??
Click to expand...
Click to collapse
Yep, tried changing it in the mounts and there is a checkbox I think in advanced with unmount sdcard checked and it wouldn't let me uncheck it. I just have to remember to move anything I want to flash to external first and especially before wiping anything. I made that mistake with a CWM recovery on the tf101 and wiped everything, expecting the new ROM to be on external, and that one could only see internal so I had to find another way to flash an OS to get back online.
[EDIT] Just for clarity, I checked again and what I see is in the install option, when I click on 'Use external', it switches to /sdcard and shows everything on the external microSD card. When I click on 'Use internal', it switches to /emmc, but shows me an empty directory. I can go up a level and see things in the / directory of the internal memory, but changing to /sdcard directory still shows the external microSD and there isn't any directory pointing to what would normally be 'sdcard' where the Download folder normally is.

What I would need to figure it out - is from the tf101 I need their BoardConfig.mk file to see if I can figure out the TWRP mount points.

Racing19969 said:
What I would need to figure it out - is from the tf101 I need their BoardConfig.mk file to see if I can figure out the TWRP mount points.
Click to expand...
Click to collapse
I'll try to grab it from his github and post a link or something here. Wish I knew more on the development side, but I know about enough to be dangerous.
[EDIT] Here you go:
https://github.com/ViViDboarder/android_device_asus_tf101/blob/ics/BoardConfig.mk

sidneyk said:
I'll try to grab it from his github and post a link or something here. Wish I knew more on the development side, but I know about enough to be dangerous.
[EDIT] Here you go:
https://github.com/ViViDboarder/android_device_asus_tf101/blob/ics/BoardConfig.mk
Click to expand...
Click to collapse
Thanks, running a build right now and will let you know how it turns out...
updated OP with the following:
There doesn't seem to be an easy-to-use interface to mount the internal sdcard (emmc) - but you can still do it. Go into Advanced, then Terminal Command, select / as your starting folder (working directory - just hit select it'll likely be there as default), then type in the following:
/sbin/mount /dev/block/mmcblk0p28 /emmc
Then when you back out of there and get to the Install area, you can switch between the internal and external. Hope that helps!

Re: TeamWin Recovery Project TWRP Recovery V2.4 Blaze4G
Racing19969 said:
...There doesn't seem to be an easy-to-use interface to mount the internal sdcard (emmc) - but you can still do it. Go into Advanced, then Terminal Command, select / as your starting folder (working directory - just hit select it'll likely be there as default), then type in the following:
/sbin/mount /dev/block/mmcblk0p28 /emmc
Then when you back out of there and get to the Install area, you can switch between the internal and external. Hope that helps!
Click to expand...
Click to collapse
Glad to see I'm still helpful

dwitherell said:
Glad to see I'm still helpful
Click to expand...
Click to collapse
Yes you are.... I remembered you posting this back when I built the first TWRP recovery.. THANKS

Racing19969 said:
Yes you are.... I remembered you posting this back when I built the first TWRP recovery.. THANKS
Click to expand...
Click to collapse
No prob - I'm just happy I could come up with something useful from time to time
And fwiw - your build was my first experience with TWRP and I have yet to look back, so thanks for getting this together!

@Racing19969 - I unpacked your zip file and unpacked the recovery image with Android Kitchen and made just 1 change to the /sbin/postrecoveryboot.sh in the ramdisk to make it look like this:
Code:
#!/sbin/sh
# 0: charge
# 1: direct
# 2: recovery_enter
# 3: recovery_end
# 4: download_end
sleep 3
echo 3 > /dev/block/mmcblk0p12
#mount internal sdcard
/sbin/mount /dev/block/mmcblk0p28 /emmc
# Enable USB mass storage
echo 0 > /sys/class/android_usb/android0/enable
echo adb,mass_storage > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
Then I repacked, rezipped, pushed, flashed, rebooted to Android, rebooted to recovery and from 'Install' I can see both external sdcard from external button and 'emmc' from internal button and don't have to try to remember the command, and even worse, to type it in each time. I was looking for the least intrusive and easiest way to do it without resorting to trying to rebuild the whole thing. Now I can get to the 'Download' folder if I forget to move something to the external card before rebooting recovery. I am posting this for your consideration as I don't know for sure if it messes anything else up. Thanks again for your efforts.
[EDIT] I have changed the info above to match what actually worked. I accidentally left the change in the postrecoveryboot.sh when I thought I had reverted it to test the recovery.fstab change I spoke of earlier, which actually does nothing by itself. The command added in this script does work. Sorry everyone for the confusion.

sidneyk said:
@Racing19969 - I unpacked your zip file and unpacked the recovery image with Android Kitchen and made just 1 change to the /sbin/postrecoveryboot.sh in the ramdisk to make it look like this:
Code:
#!/sbin/sh
# 0: charge
# 1: direct
# 2: recovery_enter
# 3: recovery_end
# 4: download_end
sleep 3
echo 3 > /dev/block/mmcblk0p12
#mount internal sdcard
/sbin/mount /dev/block/mmcblk0p28 /emmc
# Enable USB mass storage
echo 0 > /sys/class/android_usb/android0/enable
echo adb,mass_storage > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
Then I repacked, rezipped, pushed, flashed, rebooted to Android, rebooted to recovery and from 'Install' I can see both external sdcard from external button and 'emmc' from internal button and don't have to try to remember the command, and even worse, to type it in each time. I was looking for the least intrusive and easiest way to do it without resorting to trying to rebuild the whole thing. Now I can get to the 'Download' folder if I forget to move something to the external card before rebooting recovery. I am posting this for your consideration as I don't know for sure if it messes anything else up. Thanks again for your efforts.
[EDIT] I have changed the info above to match what actually worked. I accidentally left the change in the postrecoveryboot.sh when I thought I had reverted it to test the recovery.fstab change I spoke of earlier, which actually does nothing by itself. The command added in this script does work. Sorry everyone for the confusion.
Click to expand...
Click to collapse
Definately works, Thanks for the fix.... Now I just need to figure out how to add it to the recovery build process..
UPDATED OP.. NEW BUILD UP WITH INTERNAL/EXTERNAL MOUNTS FIXED... HUGE THANKS TO SIDNEYK

You must be a busy busy Dev! Many thanks for the updates!
AWESOME!

Racing19969 said:
Definately works, Thanks for the fix.... Now I just need to figure out how to add it to the recovery build process..
UPDATED OP.. NEW BUILD UP WITH INTERNAL/EXTERNAL MOUNTS FIXED... HUGE THANKS TO SIDNEYK
Click to expand...
Click to collapse
Assuming you're building with cm sources, as per the instructions, it seems to be pulling the 'postrecoveryboot.sh' from 'android_devices_samsung_msm8660-common'. You could try to make the change there (at least for your local build repo) or maybe there is some other device specific file somewhere in the process to echo that 1 line to the file just before the build? Just ideas, I haven't done much coding since the days of BASIC and that's been a while back.

Possible wipe issues?
I've been playing around with a few different ROMs since rooting and noticed yesterday that I had hardly any space left because there was a bunch of stuff from previous installs still there that I thought I wiped out in TWRP. I was getting ready to flash PACman JB again and went into TWRP to try and wipe as much clean as possible and noticed some errors and looking around in the file manager it didn't seem to be really wiping much. Factory reset probably cleaned some data out, but otherwise stuff was still there. Can someone else test and see if this is the case, especially if someone is well versed with Samsung's file and partition schemes. For now, I'm back with CWM which does seem to get rid of stuff, even the external sdcard, if you aren't careful. Thanks.

I am going to flash the lates AOKP back on and I updated twrp the other day and I have cm10 on here now. I want to back up my cm10 to my external 16 gig before I flash the new AOKP. What can I do to help?
just give me the instructions/how to of what you need and I will do my best to help.
Thanks

@sidneyk, another sure fire way to clean out unwanted junk and caches is go into settings/storage and erase SD card. This clears out all files leaving the bare minimal and most of your Google apps. I only had to reinstall about 8 apps, but my problem was saying I had no USB storage due to gallery,pics etc. . Nothing was there to delete, erased SD, problem solved plus got rid of all those extra folders I didn't know if I needed or not.

Using the newest build 1/26 did my first backup and the recovery rebooted prior to the backup finishing. The second backup went ok. Just wanted someone to know. I don't know if this is an issue with the 2.4 alpha or not, perhaps it is. I believe the backup stopped when generating the md5 for the data partition. If it happens again I will post what exactly went wrong (I was getting ready to leave when it happened).

Yes I can confirm that there are random reboots, and also the internal file sys is not mounting, it keeps showing the external SD regardless which one is mounted. Just wanna add that the internal file manager does show both correctly only when I mount it and try to browse it on the computer is when there's an issue. Im running plain stock ics.

[Q] Nexus 7 Bricked No OS stuck on Google screen

Good Afternoon
The other day I was having an issue with my Nexus 7 so I inadvertently went into TWRP on my device and wiped everything including the OS so when it starts up I just get the Google screen with the unlocked padlock on it.
I have tried several things so far
I have downloaded Nexus root Toolkit 1.7.3 and several stock images, I choose the option to flash stock + Unroot but it doesn't seem to do anything I just get the following screen as per attached screenshot, from looking around it looks like it should run something before I get that screen but nothing happens.
I really don't know where to go from here I have tried so many different things but just don't seem to be getting anywhere, any help would be soooooooo much appreciated, I can’t even send it back as I have unlocked it and I believe that voids the warranty.
I have managed to get into the TWRP section by choosing the custom recovery in the advanced section menu but when it loads up it asks me for a password on my Nexus and the password I had it keeps on saying password failed.
Is there anything I can do, I have literally spent hours searching around and I cant seem to get anything to work, as I say I have inadvertently wiped everything!!!!!!:crying:

davechampion said:
Good Afternoon
The other day I was having an issue with my Nexus 7 so I inadvertently went into TWRP on my device and wiped everything including the OS so when it starts up I just get the Google screen with the unlocked padlock on it.
I have tried several things so far
I have downloaded Nexus root Toolkit 1.7.3 and several stock images, I choose the option to flash stock + Unroot but it doesn't seem to do anything I just get the following screen as per attached screenshot, from looking around it looks like it should run something before I get that screen but nothing happens.
I really don't know where to go from here I have tried so many different things but just don't seem to be getting anywhere, any help would be soooooooo much appreciated, I can’t even send it back as I have unlocked it and I believe that voids the warranty.
I have managed to get into the TWRP section by choosing the custom recovery in the advanced section menu but when it loads up it asks me for a password on my Nexus and the password I had it keeps on saying password failed.
Is there anything I can do, I have literally spent hours searching around and I cant seem to get anything to work, as I say I have inadvertently wiped everything!!!!!!:crying:
Click to expand...
Click to collapse
Try reflashing TWRP first, then reply if you still have the password problem. We can work from there. Remember, you have a N7 - nexus devices are practically unbrickable (if you know what I mean)

Nexus 7 2013
Thanks for that will give it a try later.
I have also come across the website below
forums.androidcentral.com/google-nexus-7-2012-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.
It gives a guide on how to reinstall the stock software, the only thing that I can see they have that I dont are a few files and I dont know where you get them from.
the files in the guide are
Bootloader-Grouper 3.34
Flash-all.sh
Flash-Base.sh
The image file I am fine with as I downloaded that from the site below.
developers.google.com/android/nexus/images
sorry I dont have enough privaleges to include link have to paste it manually

Nexus 7 2013
Also in regards to you last comment about TWRP
could you give step by step instructions on how to reinstall it, I am just paranoid that I may do something wrong again, I cant activate usb debugging so would need to do it via the bootlader and Command prompt ideally.

Nexus 7 2013 Re flash TWRP
Not to worry about steps I have managed to find some that will do the job
theunlockr.com/2013/03/25/how-to-install-twrp-recovery-on-the-asus-nexus-7/

davechampion said:
Thanks for that will give it a try later.
I have also come across the website below
forums.androidcentral.com/google-nexus-7-2012-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.
It gives a guide on how to reinstall the stock software, the only thing that I can see they have that I dont are a few files and I dont know where you get them from.
the files in the guide are
Bootloader-Grouper 3.34
Flash-all.sh
Flash-Base.sh
The image file I am fine with as I downloaded that from the site below.
developers.google.com/android/nexus/images
sorry I dont have enough privaleges to include link have to paste it manually
Click to expand...
Click to collapse
Have you used 7z to unpack the files? Google puts all the files within an archive which is within another archive. In case you aren't able to successfully follow your guide, let me know and I will post steps. And btw, using CMD is actually quite easy once you get used to it... You just need to put in the effort! :good:

[GUIDE] How to install/reinstall/flash stock Nexus 7 Image from Google
I just saw your other thread mate! Seems like you're really worried about your device. And so I thought I'll give you step by step instructions;
1) Install, then open and navigate 7-zip to the location where you have the factory image file downloaded from google with the ".tgz" extension.
2) Unpack the .tgz file by selecting it and clicking extract (with the big blue negative sign).
{
"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"
}
3) Now, navigate to the extracted folder, you will see another file with the extension ".tar"
4) Repeat step 2 for the ".tar" file.
5) Now open this folder using windows. You should see the following files in your directory;
6) From here, you can either follow the instructions on the webpage you have or follow these instruction (using CMD and fastboot);
* Remember, after doing this you will not have any files/setting left on your N7.
1) Boot your N7 into bootloader.
2) Open cmd.exe and enter the following commands;
3) cd "put here without quatation marks, the directory of where the .img files are" (the last pic above)
4) fastboot devices (note: after entering this command your device should be displayed below)
5) fastboot erase boot
6) fastboot erase system
7) fastboot erase recovery
Perform steps 8 & 9 only if you have the 3G version of the N7:
8) fastboot erase radio
9) fastboot flash radio "put here without the quotation marks, the FULL name of a file that will look similar to this: radio-razor-m9615a-cefwmazm-2.0.1700.84.img"
10) fastboot update -w image-razor-jss15q.zip
11) fastboot reboot
Remember, because you have freshly flashed your N7, it will take little longer than usual to boot up.
​

Thank You!!!!!!!!!!
Thank you so much you are a LEGEND - I am all up and running again, just a quick question I re flashed the standard stock file which was listed as JSS15J (it wasn’t on the official factory image website) but my Nexus root toolkit seems to be playing ball after a re install, can I flash a later version over what I have without causing issues as I assume they have bug fixes.
I am unable to do an OTA update as I am in an unlocked state.
I have seen online that you can use the following code in CMD to flash newer factory images without wiping data, Is this correct?
here is the code they suggest to use
Code:
fastboot update <Filename>.zip
I suppose you could back up all data first and then re flash.
Again a massive thank you for all you help:victory:

[GUIDE] Reinstall/Update Android without loosing your Userdata (media Directory)
davechampion said:
Thank you so much you are a LEGEND - I am all up and running again, just a quick question I re flashed the standard stock file which was listed as JSS15J (it wasn’t on the official factory image website) but my Nexus root toolkit seems to be playing ball after a re install, can I flash a later version over what I have without causing issues as I assume they have bug fixes.
I am unable to do an OTA update as I am in an unlocked state.
I have seen online that you can use the following code in CMD to flash newer factory images without wiping data, Is this correct?
here is the code they suggest to use
Code:
fastboot update <Filename>.zip
I suppose you could back up all data first and then re flash.
Again a massive thank you for all you help:victory:
Click to expand...
Click to collapse
I'm glad to be of assistance. If you want to update your rom without loosing your data, I recommend you follow these steps (however, there is a catch: read the second last paragraph);
1) Boot into TWRP and wipe everything except "Internal Storage".
Reboot into bootloader and erase the following using CMD:
2) fastboot erase system
3) fastboot erase boot
4) Now unpack the <filename>.zip file. You will find that there are a multitude of <filename>.img files in there.
Flash two of the files named system.img and boot.img (this contains the Kernel) using CMD (remember CMD must be open in the folder containing these files):
2) fastboot flash system system.img
3) fastboot flash boot boot.img
And the other file (again is if you have the mobile version of the N7), is to flash the radio as given in my previous instructions (remember to erase radio first before flashing it).​
When you're done, you will have updated your N7 without losing your data (i.e. the files you see when you plug your N7 to the computer). However, following this method, you will not retain any Apps or settings (remember: Backing up apps and restoring them to a different ROM is a BAD idea). I have to say also that given you cannot use OTA, I am not aware of any other method that will keep your apps and settings untouched. I may be wrong, and if I am please do let me know. :good:
Finally as a personal note, I wouldn't flash anything to a Nexus but the latest stock files provided from Google until they stop providing updates to that particular device.

..
..

How to root the S7 EDGE

Caution when modifying your phone, although you can revert 99% of issues you may come across, be cautious.
I take no credit other than compiling info and making a guide. All credit goes to http://forum.xda-developers.com/member.php?u=4911585 (br3w3r, Chainfire and Princecomsy)
http://forum.xda-developers.com/att-galaxy-s7/how-to/g935a-root-t3410403
Well, root has been achieved on all of the variants. All the information is spread, therefore I will compile it.
It is confirmed working for the G935T/A/ (All firmwares so far) can anyone verify it works for Verizon?
DOWNLOAD LINKS
Complete Package with all needed files ( http://d-h.st/am7i - click the blue download link to avoids the ads. (Credit to billa)
ADB Files http://forum.xda-developers.com/showthread.php?t=2588979
Samsung Device Drivers http://developer.samsung.com/technical-doc/view.do?v=T000000117#none
http://d-h.st/gsDA Modified ODIN
http://d-h.st/lQY8 EngBootIMG
https://download.chainfire.eu/968/SuperSU/SuperSU-v2.74-2-S7QC.zip Chainfire's SuperSU
MAKE SURE TO BACKUP YOUR PHONE, YOU MAY NEED TO FACTORY RESET AFTER FLASHING THE ENGBOOT FILE. ( MAY BE FOR THOSE WHO HAVE DISABLED SYSTEM APPS)
1- Put your device in to download mode ( Power off--- Hold Down arrow + Home + Power button)
2-Open the provided ODIN and where it says "AP" select and open the file "Samsung_G935x_QC_Rooted_BOOT.TAR" -- FLASH it--
3- The phone should now reboot
Installing SuperSU
easiest way to put it for flashing su.
https://www.youtube.com/watch?v=nLvRuzQMPLk
1- make sure you have the adb toolkit installed( place it in the root of the "C:/" drive. Mine is "C:/adb"
2- place the superuser folder you downloaded in to c:/adb and rename it "super" to make things easier
3- open the command prompt. Either search for it or press windows key + r and type in "cmd"
4- once cmd is open, navigate to the "super" folder. To do so type cd c:/ , then type cd adb and finally type cd super
5- type in root.bat
You should now be rooted.
To remove the security warning, use a package disabler like titanium backup and disable SecurityLogAgent
NOTE
For those having lag, heat, and battery drain issues. Try doing this.
I had those issues on PD6.
What I did was, ODIN'd a factory PD8 file and rerooted, then I used KERNEL TOOLKIT and changed to the ONDEMAND Governor, next I increased the CPU(small cores / and large cores) to max FREQUENCY allowed and reduced the min core frequencies to the lowest setting. Be sure to apply settings on boot so they stick.
The phone is very fast now.
I disabled the KNOX packages and tmobile package.
It fixed 95% of my issues, im even running xposed

For anyone that needs the complete firmware from Sammobile:
http://www.sammobile.com/firmwares/database/SM-G935T/
I also attached the root files necessary in the zip file here.
BUT... you also need to unrar it. Stinking forum set the zip limit to 20MB for zip files but it zips to about 23MB.
Rar limit is 8MB but in a rar it was reduced to about 18. So... rar'ed it up, hid it in a zip.

Will this work on PC8? That's the one I'm on.

mrlugo88 said:
Will this work on PC8? That's the one I'm on.
Click to expand...
Click to collapse
No guts, no glory. Try it and let us know. Root hasn't been out but for a couple of hours so it's hard to know for sure. Make a backup with Smart Switch and try it out! My guess is that you shouldn't have any issue.
If anyone has disabled any of their apps, make sure you re-enable them.
If you get stuck at the white T-Mobile screen for longer than 5 minutes then reboot back to stock recovery and factory reset. Sucks... but some of us had to do it. Afterwards, it should boot fine.
By the way... HAPPY INDEPENDENCE DAY!!!
{
"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"
}

Binary100100 said:
No guts, no glory. Try it and let us know. Root hasn't been out but for a couple of hours so it's hard to know for sure. Make a backup with Smart Switch and try it out! My guess is that you shouldn't have any issue.
If anyone has disabled any of their apps, make sure you re-enable them.
If you get stuck at the white T-Mobile screen for longer than 5 minutes then reboot back to stock recovery and factory reset. Sucks... but some of us had to do it. Afterwards, it should boot fine.
Click to expand...
Click to collapse
I'm all in. Thanks. Will go for it.

mrlugo88 said:
I'm all in. Thanks. Will go for it.
Click to expand...
Click to collapse
May the root be with you.

Does it work on tmo S7 edge on PD7?
Sent from my SM-G935T using XDA Free mobile app

Do I need a laptop for this. I'm so sorry about my super noobish question. Don't kill me

Lmax579 said:
Does it work on tmo S7 edge on PD7?
Sent from my SM-G935T using XDA Free mobile app
Click to expand...
Click to collapse
It's been confirmed to work.
Chocolatetai said:
Do I need a laptop for this. I'm so sorry about my super noobish question. Don't kill me
Click to expand...
Click to collapse
A Windows machine with administrative rights to install device drivers are required.

Thankyou for your nice reply. I guess I have to wait till my brother gets home

whats the weird icon in the status bar and anybody found lag after they flash the boot file?

Binary100100 said:
No guts, no glory. Try it and let us know. Root hasn't been out but for a couple of hours so it's hard to know for sure. Make a backup with Smart Switch and try it out! My guess is that you shouldn't have any issue.
If anyone has disabled any of their apps, make sure you re-enable them.
If you get stuck at the white T-Mobile screen for longer than 5 minutes then reboot back to stock recovery and factory reset. Sucks... but some of us had to do it. Afterwards, it should boot fine.
By the way... HAPPY INDEPENDENCE DAY!!!
Click to expand...
Click to collapse
How would I boot back to stock recovery?
Sent from my HTC 10 using XDA Free mobile app

That's for compiling the info.
Might be a good idea to add a list of builds it's been confirmed working on.

Lmax579 said:
How would I boot back to stock recovery?
Sent from my HTC 10 using XDA Free mobile app
Click to expand...
Click to collapse
Switch your Samsung Galaxy S7 or S7 edge completely.
Boot into Galaxy S7 recovery mode by pressing and holding Volume Down, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S7 screen flickers and you see a warning sign.
Press Volume Up to continue to the main screen of Recovery mode. Or, press Volume Down if you aren’t sure and want to go back to the normal mode.
That’s just about it!
Read more: http://wccftech.com/how-to-enter-galaxy-s7-recovery-mode/#ixzz4DORIJ3Dx
http://wccftech.com/how-to-enter-galaxy-s7-recovery-mode/

Chocolatetai said:
Do I need a laptop for this. I'm so sorry about my super noobish question. Don't kill me
Click to expand...
Click to collapse
Yes, specifically the root.bat is Windows based, but you could read the .bat and figure out how to do it in linux. Either way, yes.
Worked flawlessly with the guide. Thanks for compiling it
Edit/Update:
I am getting the same lag that others have reported previously. One thing I'm seeing that stands out in logcat is Secure Storage Daemon throwing warnings and then an error "Kernal binary has been changed. Please use the same version of platform/kernel binaries"

uaktags said:
Yes, specifically the root.bat is Windows based, but you could read the .bat and figure out how to do it in linux. Either way, yes.
Worked flawlessly with the guide. Thanks for compiling it
Click to expand...
Click to collapse
So just followed the guide? Do I need anything else? I just follow the guide and download what the guide says? Do I need to turn my phone off? Do I need a specific app on my phone for anything? Sorry for the questions

Chocolatetai said:
So just followed the guide? Do I need anything else? I just follow the guide and download what the guide says? Do I need to turn my phone off? Do I need a specific app on my phone for anything? Sorry for the questions
Click to expand...
Click to collapse
If you follow the guide, you'll have everything you need and there wouldn't be any questions needed.
I guess more specific to ask, where are you getting hung up?
On a windows machine:
Download all the files listed and get them installed
Follow the instructions (boot phone into download mode, put adb folder into c:\, rename the SuperSU folder from the zip archive to "super" for easy access, execute the cd's and then execute root.bat)

uaktags said:
If you follow the guide, you'll have everything you need and there wouldn't be any questions needed.
I guess more specific to ask, where are you getting hung up?
On a windows machine:
Download all the files listed and get them installed
Follow the instructions (boot phone into download mode, put adb folder into c:\, rename the SuperSU folder from the zip archive to "super" for easy access, execute the cd's and then execute root.bat)
Click to expand...
Click to collapse
How would I put my phone in download mode

Chocolatetai said:
How would I put my phone in download mode
Click to expand...
Click to collapse
It's in the guide.
Please just read the guide and understand it before you move forward. Ask what you don't understand from the guide so that the writer could make it more clear if it's needed. But what you just asked is literally written clearly with what to do.

Damn can't wait to do this and install xposed only got another hour left
T-Mobile S7 Edge
Latest Update PD8
Eng Boot - System Custom
Knox 0x0

Ulefone Power 3 - TWRP 3.2.1-0 & Root (SuperSU)

This is a thread for the rooting and install of TWRP for the Uefone Power 3
Code:
/*
* Your 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.
*/
TWRP 3.2.1-0: https://drive.google.com/file/d/1cLqcDrun5f6h1BHjUFfXDdlhwEWwM-49/view?usp=sharing
SuperSU: https://drive.google.com/file/d/1sZwahrodGJmYWzaIohxEETeIAabCOPfb/view?usp=sharing
Steps to install TWRP and SuperSU
Copy the above SuperSU to your SDCard.
First of all, you will be required to unlock your bootloader.
There is an option for this under Developer Options in the settings menu. Activate this.
Also activate USB Debugging. This makes this a whole lot easier.
Now, open a terminal, if on Linux, or command prompt if on windows, and enter the following:
Code:
adb reboot bootloader
Code:
fasboot oem unlock
Follow the onscreen instructions to unloack your bootloader. THIS WILL WIPE YOUR DEVICE!!!
Once this is complete, it will go back to the fastboot screen.
Now, from within your terminal/command prompt, navigate to the folder where you have downloaded the above recovery.img to.
Enter the following command once there:
Code:
fastboot flash recovery recovery.img
This will flash TWRP to your device, overwriting the stock recovery.
Once this is complete, there will be a screen telling you how long it took etc. Now you need to hold down your volume up button, and power button. Keep holding these untill you reach the menu for recovery, fastboot or normal mode.
Select Recovery.
This will boot into TWRP for the first time. when you get there, you will be prompted with a screen asking for a password. Cancel this.
WHAT EVER YOU DO, DO NOT FORMAT DATA LIKE IT ASKS YOU!"" YOU WILL LOSE TWRP!!!
Your then presented with the main TWRP screen, go ahead and tap on Install. Next, hit Select Storage, and select Storage 1. This is your SDCard.
Now flash SuperSU.
When this is installed, reboot to your main system, and update the SuperSu binary.
Now proceed to reboot back to recovery, how ever you wish.
Once in recovery, go into Wipe, and hit Format Data, this will wipe your phone again, but youve just done this anyway so it doesnt matter
Now flash SuperSU again, just to be safe, the same way as above.
Reboot to your system, and your done!
You will have to go through the setup of the whole android system again, but its worth it your now rooted and have TWRP to install the Custom ROMs that will be coming shortly
Have Fun!

Reserved

wow, that was quick thank you
will try it now and update as soon as it's done!

alright, so i tried to flash super su, but i never get to access the storage partitions (i think they are not mounted).
so i tried to factory reset / wipe the phone to get rid of the encryption, but i still cant select storage 1 from the menu.
here some more detail:
- i have already had the bootloader unlocked
{
"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"
}
- then i come to this screen when twrp starts, and select "swipe to allow modifications"
- then i press install and want to select "storage 1", this however doesnt work. (due to encryption?)
- i tried to mount it, but cant even mark it active. just gets gray for half a second and then nothing
- tried to do a wipe via twrp as well, with no success
any ideas?

tbst1337 said:
alright, so i tried to flash super su, but i never get to access the storage partitions (i think they are not mounted).
so i tried to factory reset / wipe the phone to get rid of the encryption, but i still cant select storage 1 from the menu.
here some more detail:
- i have already had the bootloader unlocked
- then i come to this screen when twrp starts, and select "swipe to allow modifications"
- then i press install and want to select "storage 1", this however doesnt work. (due to encryption?)
- i tried to mount it, but cant even mark it active. just gets gray for half a second and then nothing
- tried to do a wipe via twrp as well, with no success
any ideas?
Click to expand...
Click to collapse
Your third screenshot - what's the last option, under Microsd?
Also, when going through install, can u see "external SD"?

ukhellfire666 said:
Your third screenshot - what's the last option, under Microsd?
Also, when going through install, can u see "external SD"?
Click to expand...
Click to collapse
the last one is USB OTG, also showing 0MB - i actually tried flashing supersu through the usb as well, with no luck
i can see external_sd but there dont seem do be ANY contents
do you think it is the encryption? because everything shows 0MB in brackets
EDIT:
i just thought what the hell i try again to flash it via usb. havent changed anything but suddenly SUCCESS
appreciate your time thanks

tbst1337 said:
the last one is USB OTG, also showing 0MB - i actually tried flashing supersu through the usb as well, with no luck
i can see external_sd but there dont seem do be ANY contents
do you think it is the encryption? because everything shows 0MB in brackets
EDIT:
i just thought what the hell i try again to flash it via usb. havent changed anything but suddenly SUCCESS
appreciate your time thanks
Click to expand...
Click to collapse
So what did you do differently? If you can explain a bit more, I'll change/add it to the guide. Maybe as a second option or something...?

ukhellfire666 said:
So what did you do differently? If you can explain a bit more, I'll change/add it to the guide. Maybe as a second option or something...?
Click to expand...
Click to collapse
i just booted again into twrp and suddenly my 4gb usb was showing up as the only thing not 0mb, so the usb otg partition was mounted. from there on i just pressed install and located the zip file on the usb drive. had some errors. below some pics i took with my old phone:

tbst1337 said:
i just booted again into twrp and suddenly my 4gb usb was showing up as the only thing not 0mb, so the usb otg partition was mounted. from there on i just pressed install and located the zip file on the usb drive. had some errors. below some pics i took with my old phone:
Click to expand...
Click to collapse
Ahhh brilliant! I don't suppose u found that he sdcard was mounted too did you?
Have the errors gone now your rooted? The rest of the guide should still count...?

ukhellfire666 said:
Ahhh brilliant! I don't suppose u found that he sdcard was mounted too did you?
Have the errors gone now your rooted? The rest of the guide should still count...?
Click to expand...
Click to collapse
yes i am indeed rooted!
everything else, including internal storage was 0mb as well. usb otg was literally the only one.
i have not gone back into recovery since, but rebooted several times and also used root apps (adaway). everything seems to work great and the rest of the guide still counts!
in total, everything seems stable until now :good: my goal is to not touch twrp anymore until android 8.1 will be released

tbst1337 said:
yes i am indeed rooted!
everything else, including internal storage was 0mb as well. usb otg was literally the only one.
i have not gone back into recovery since, but rebooted several times and also used root apps (adaway). everything seems to work great and the rest of the guide still counts!
in total, everything seems stable until now :good: my goal is to not touch twrp anymore until android 8.1 will be released
Click to expand...
Click to collapse
The official 8.1 update with overwrite TWRP.
I am now working on a cm14.1 build. As im having to use a prebuikt kernel, this is as far as I can go.
As soon as I have a beta ROM I'll upload.
Don't suppose you could boot to recovery and just double check that everything is as it should be? Put my mind at ease, make sure it works for you, as it does for me...

ukhellfire666 said:
The official 8.1 update with overwrite TWRP.
I am now working on a cm14.1 build. As im having to use a prebuikt kernel, this is as far as I can go.
As soon as I have a beta ROM I'll upload.
Don't suppose you could boot to recovery and just double check that everything is as it should be? Put my mind at ease, make sure it works for you, as it does for me...
Click to expand...
Click to collapse
sure man, maybe joining me on discord would make this process faster https://discord.gg/jPZqn4

Hi.
Thank you for twrp.
I am trying to use SuperSu with SuHide, i wipe data with this twrp to be able to install supersu in BINDSBIN mode to /data but data partition stay unencrypted to be mountable with thw twrp.
How to encrypt it back with own known password keeping supersu and suhide working?
TWRP has no option to reformat with password, no way to get origin password for stock recovery formated partition.
Any idea?

MioCZ said:
Hi.
Thank you for twrp.
I am trying to use SuperSu with SuHide, if i wipe data with this twrp to be able to install in BINDSBIN mode to /data but data partition stay unencrypted.
How to encrypt it back with keep supersu and suhide working?
TWRP has no option to reformat with password, no way to get origin password for stock recovery formated partition.
Any idea?
Click to expand...
Click to collapse
No idea I'm afraid. Sorry.

I used encryption in system Setup, i works, but with unknown password stored somewhere in nvdata partition. I am worry about loose root after OTA update and without pasword for twrp no way to get again to data partition.

I'm thinking of buying this phone. It's great to see that root already seems to work and that there might be a CM/LineageOS Rom soon. Root and custom recovery is crucial so one reason less to not buy it.
Are you guys happy with it in general? Does the dual camera work with bokeh and shoot good photos with low lag required to capture playing kids? Good value?

I can not install Snap Chat
Thank you ukhellfire666
The recovery was successfully installed
My question:
is there any idea to fully remove superSu to install snapchat
A full system backup has been taken.

DaF1974 said:
I'm thinking of buying this phone. It's great to see that root already seems to work and that there might be a CM/LineageOS Rom soon. Root and custom recovery is crucial so one reason less to not buy it.
Are you guys happy with it in general? Does the dual camera work with bokeh and shoot good photos with low lag required to capture playing kids? Good value?
Click to expand...
Click to collapse
good day to you.
in general i am happy with it, but the camera really blows. it is - without a doubt - the worst camera i had since my LG VX-5200. iphone 6s and galaxy s6 have way better cameras.
i am really frustrated, because they advertised the 4 cameras ..." " heavily, but they really suck. maybe it's just with the stock app and another app would make it better (but somehow i doubt that)
tomorrow i will go on holiday and was stoked that the phone arrived before, so i could take it with me to take pictures etc. seems like i will need to get the old digital camera out....

alshyib said:
Thank you ukhellfire666
The recovery was successfully installed
My question:
is there any idea to fully remove superSu to install snapchat
A full system backup has been taken.
Click to expand...
Click to collapse
Is possible to flash un-supersu package. Is somewhere in SuperSu topic. Or you can flash clean ROM / your backups (boot.img, recoovery.img, system.img).
Because this i have used supersu in BINDSBIN mode and suhide. So i have hiden su, locked bootloader, working OTA and all root sensitive apps.

bootloop
Hello, I followed the instructions but my phone bootloop on twrp, it does not start the system can you help me please?
---------- Post added at 02:23 AM ---------- Previous post was at 02:21 AM ----------
Hello, I followed the instructions but my phone bootloop on twrp, it does not start the system can you help me please?