[Q&A] [REPAIR] E970 TeenyBin -- Soft Brick Quick Fix, Bootloader Unlock and RPM/TZ U - AT&T LG Optimus G

[Q&A] [REPAIR] E970 TeenyBin -- Soft Brick Quick Fix, Bootloader Unlock and RPM/TZ U
Q&A for [REPAIR] E970 TeenyBin -- Soft Brick Quick Fix, Bootloader Unlock and RPM/TZ Update
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [REPAIR] E970 TeenyBin -- Soft Brick Quick Fix, Bootloader Unlock and RPM/TZ Update. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

LGNPST.. will my phone become locked again?
autoprime said:
LGNPST E970 TeenyBin
DO NOT USE THIS ON NEXUS 4 CONVERTED PHONES!! BRICK CITY
TeenyBins do not help restore your N4 converted phones either.
Don't give me all the credit. Just as much goes to artlan for figuring out the tables and table offsets.
Special thanks to xonar_ for his LG Bin Firmware Extractor and releasing his source code.
Thank you Shelnutt2 for everything you do for the entire LGOG community.
Thank you k7raid for testing the first bin with major SBL changes.
And last and also least.. ha ha.. sawdey21 for suggesting the "updated" name change.
TeenyBin. Patent Pending.
Be sure to show them all thanks.
Background
After seeing tons of soft bricks on both the forums and IRC we have decided to look into how LG .bin files work. We've "cracked the code" and have been able to rebuild the .bins.. making the repair process both faster and easier. Normally the user must download a large .tot/.bin file(1GB+) to repair the phone. After a long download and 5+ minute LGNPST flash the phone is then completely stock... requiring a "re-root" and running the FreeGee unlock again.
TeenyBins are meant to do the bare minimum... fix your soft bricked LG OG and get you back into your rom.. or custom recovery to flash a new rom. These new .bins are as small as 32MB depending on what we build into the .bin. This means smaller files, shorter download times and a phone that's back up and running within minutes.
Other perks include...
Unlocking the bootloader.
SBL partitions safely flashed.
Preinstalled TWRP Recovery.
RPM/TZ partitions safely updated to support the latest AOSP roms.​
Directions
E970 TeenyBins will quickly repair your soft bricked device. They will also unlock your phone, install the latest TWRP recovery and update your RPM/TZ partitions... which are needed to run the new AOSP roms based on the Mako kernel. These .bins are safe for any E970.
1. Download TeenyBin .zip and extract. You are going to use the .bin file inside along with LGNPST. LGNPST can be found in the "Additional Info" section at bottom of this post.
2. The TeenyBin LGNPST flash should take 30 seconds or less... your phone will reboot at either 67% or 85%. The flash is complete. All finished.. maybe...
3. Your phone still may not boot up!! If so you must reboot the phone.. boot into fastboot. No fastboot still? Flash the TeenyBin "AltBin" instead!!
4. From fastboot, boot into recovery. In recovery you can flash a rom. All fixed.
5. Nothing working? You're doing it wrong. Did you read this entire post... including everything under the "Additional Information" section at bottom?
Fastboot = Volume up + power
Recovery = once in fastboot.. press volume down, pause, volume down then power button​
TeenyBins
These TeenyBins will repair a soft brick, unlock the bootloader, install custom recovery and upgrade rpm 'n' tz.
Remember to try the AltBin if the normal TeenyBin doesn't work. If you can't boot.. fastboot has to work. If you can't get to fastboot you're doing it wrong.
Fastboot = Volume up + power
Recovery = once in fastboot.. press volume down, pause, volume down then power button
DOWNLOAD:
E970 Original TeenyBin - This is the default TeenyBin every E970 user should LGNPST flash
E970 Original TeenyBin[AltBin] - Use this TeenyBin if your E970 still can't boot or get to fastboot
Current included recovery: TWRP 2.5.0.0 - Thank you Dees_Troy!
​
Additional Info
Q: Can you make *custom .bin here*?
A: Maybe... but I am lazy so make a good point.
Q: I flashed the small bin and still can't boot back into my phone.
A: First of all... it's a TeenyBin... but anyway.. booting directly back up into the rom may not always be possible. Your /system or boot.img may be damaged. You were soft bricked remember... how do you think the soft brick happened? In this scenario you will have to reboot into fastboot.. then enter recovery... and reflash a rom .zip
Q: How do I know if I'm soft bricked or perm bricked?
A: For most soft bricks you will see a LG or Google logo and then a black screen. You can also still get into download mode. If you think download mode may not even work, connect phone to a Windows computer and check device manager... if the phone is detected in a "QHSUSB-DLOAD" then there's a good chance you're perm bricked. Otherwise.. you may just be a n00b and aren't doing download mode correctly.
Q: Where's that LGNPST info you mentioned?
A: Hit the "Show Content" button below
LGNPST Guide
DO NOT ASK HOW TO USE LGNPST OR A VIRTUAL MACHINE IN THIS THREAD.
THIS IS A TEENBIN THREAD. THE FILES AND GUIDES BELOW ARE A BONUS ONLY. RESEARCH. READ. APPLY.
Downloads + basic guide HERE
Update - added a virtual machine with pre-installed LGNPST to the link above. This will be for those that aren't on Windows.. or just having install issues. Thanks to k7raid for that! Some files may need a password to extract... PW = lgog
BELOW IS A MORE DETAILED GUIDE FOR THOSE CONFUSED OR STUCK.
READ IT ALL AND MOST QUESTIONS SHOULD BE ANSWERED
{
"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"
}
Notice at the top it says LGNPST ACG and not some other weird version? And notice the version numbers. If yours don't match up then you installed the wrong version!!
1. COM port will show up if phone is connected properly in Download Mode. LGNPST will switch and say Emergency Mode.
2. Press the DLL button towards the bottom of Emergency tab.
3. Press the BIN button towards the bottom of Emergency tab. You should now see both both file names scrolling in LGNPST like the screenshot.
4. Press that START button.
5. A windows will pop up saying you will lose data.. you will NOT lose any personal data.. hit OK.
6. If LGNPST is working properly it will take 20 seconds or so before LGNPST hits 67% and reboots your phone. DONE. After your phone reboots at 67% or 85% it's safe to unplug and use phone.
7. If you still can't boot up, try booting into fastboot. Can't get into fastboot.. try flashing the AltBin. Still can't get into fastboot? you're doing it wrong.
Q: LGNPST Won't open and says "usb dongle not detected"
A: In the lgnpst folder where u ran the .bat to install it should be a lgnpst_acg.exe file somewhere. Copy it to your program files > lg electronics > lgnpst folder overwriting the current exe in that folder. Should work now.
Q: There's no LGNPST_LS970.dll file to select in LGNPST.
A: The install.bat should have registered your dlls but something went wrong. Check the link in the next answer.
Q: I still can't install LGNPST... help?
A: Check out this link.
​
​
Code:
[B]My other E970 thread..[/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2161611"][GUIDE] Backup/Restore LG Optimus G EFS Partitions[/URL][/B]
[B]My other LS970 threads..[/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2161498"][GUIDE] Backup/Restore/Repair Your EFS Partition [LS970][/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2049701"][HOW-TO] Enable DIAG mode without Service Code(MSL)[/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2052816"][INFO] LS970 Hidden Dialer Codes[/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2058506"][INFO] Optimus G AT Commands[/URL][/B]
Click to expand...
Click to collapse
SO if I LGNPST my sim unlocked e970 will it become locked again?

Basic Question
Hi- I'm a big newb, so I just wanted to ask this: My LG G2 is not bricked, but I tried to install TWRP via TWRP manager. It didn't work, and when I try to boot into recovery it says "demigod crash handler: critical error!" i then tried installing CWM via the app, ROM Manager, same problem, then finally twrp again via an automated script. Same problems remain. Otherwise, the phone is running android 5, rooted on stock firmware.
So basically, before I brick, will this tool work?
Thanks,
Suneel

soft bricked or perm bricked - LG E970
Hello,
I need some help.
I was trying steps as mentioned here - http://forum.xda-developers.com/showthread.php?t=2230994
However, it appears that I am having an issue as mentioned in Q&A: (See highlighted)
Q: How do I know if I'm soft bricked or perm bricked?
A: For most soft bricks you will see a LG or Google logo and then a black screen. You can also still get into download mode. If you think download mode may not even work, connect phone to a Windows computer and check device manager... if the phone is detected in a "QHSUSB-DLOAD" then there's a good chance you're perm bricked. Otherwise.. you may just be a n00b and aren't doing download mode correctly.
If I press power button for some time then I see a charging icon and that goes away in 4-5 seconds. Sometimes after trying volume + and power keys I do get Google logo but that also goes away in 2-3 seconds.
I have tried - E970 Original TeenyBin and E970 Original TeenyBin[AltBin]
But after 85% I could see only black screen.
I can not go into download, even though I tried it multiple times. I am sure that I am doing it correct as I have done that many times.
I do not see "QHSUSB-DLOAD" in my device manager. PFA screenshot. However, I remember that, there was one green colored window that showed up when I kept phone to wall charging with message - "ap watchdog bark detected" Same image as here - http://forum.xda-developers.com/showpost.php?p=53114390&postcount=8
At this point of time I am not sure what happened and what needs to be done. I am not even sure if I could get my phone back.
Please help.
Thanks in advance!

E970_Original_TeenyBin[AltBin]-AA.bin worked for me u can unplug at 30 seconds it'll be a black screen. Hold power for some time and wait for a vibrate then press volume up. It's extremely stupid the mix of power volume up etc etc it's not super straight forward. When black screen it responds to nothing except a long power press until vibrate and quickly press volume up the second you feel it vibrate. If you sit and hold volume up and power you'll sit there until the end of eternity because the device won't do a gosh darn thing.
Anyway I used E970_Original_TeenyBin[AltBin]-AA.bin and I just can't find not one rom all give error executing updater .bin and it doesn't matter which TWRP I use or which rom. So far had to adb push/ sideload 20 roms/ 20 versions of twrp all with a miserable failure on installation.
I'm certain the cause of the problem is in some way the TeenyBin unless someone can chime in why not one rom will install? It seems TeenyBin shafted the partition table. So now I have to OTA and start all over avoiding TeenyBin so I don't get stuck again.
There's a lot more to it then vaguely described in the directions. Pre-req's galore I'm sure that were never discussed. TeenyBin seemed to "Succeed" yet all roms give "FAILED EXECUTION OF UPDATER .BIN". Even if adb sideload succeeded on the computer it always fails on the phone.

lg e970 problem
my phone is in download mode but windows cant instaling correct driver, and LGNPST cant see my phone, what can i do pls help

TwO-x said:
my phone is in download mode but windows cant instaling correct driver, and LGNPST cant see my phone, what can i do pls help
Click to expand...
Click to collapse
After you download the USB driver from the LG website for your phone and install it on your computer with your phone attached via the USB Cable you should be able to get into download mode by powering the phone off and then once it is off, holding down both the up and down volume buttons at the same. You would then plug in the USB cable to your phone that is connected to your computer. The phone should be recognized by your computer and detected by the LGNPST program you have installed on your computer. From there you can install the stock ROM back on your phone assuming you have the stock ROM downloaded and change the file extension from .tot to .bin The process I just described work for me with no issues.

Related

[SOLVED] Need to flash System partition through fastboot

Hello.
I recently sold this phone and went to factory reset. no problem. However, i forget i deleted the STOCK home app. THere is no launcher on the device so LG Setup Wizard simply crashes when finished setting it up. There is NO ADB since the setting has been erased. I need to re-enable it in settings but can't get that far since LG Setup Wizard keeps crashing..
I think i'm screwed.. what a stupid way to brick..
Device is: LG Optimus L9 P769 T-Mobile variant. Thanks guys!
you should be able to put your device on download/emergency mode and flash a kdz file with lg tool, you tried it?
if don't try yet, take out your battery, hold + volumen botton and put your battery again holding even + volumen key, and conect your to your computer, it must show the yellow screen with the legend download/emergency mode, and in your computer must be install the drivers, to exit the download/emergency mode just take out the battery or hold the power button, and for flash a kdz file, search a tuto, there are many, and many videos to make it easy . All this process let your device as new, all applications and configurations
I am aware of that mode but when attempting to flash that way before, after upgrading to jellybean, it would never flash for me. So I didn't even try it. I'll give it a shot though. I also was able to download one of the cwm backup zips posted in the other thread and extracted the system partition then created a .img image out of it and will try both your method and flashing that img file when I get home from work. Thank you for your post!
Sent from my SM-G900T using Tapatalk
SOLUTION
Installed the ICS uboot.
Booted to SW Upgrade mode via plug USB, hold volume up button, place battery into device
Launched KDZ update tool and it connected and went smoothly!
If you have the JellyBean uboot, it won't connect in SW Upgrade mode if booted manually.

[Guide]How to Root and Install TWRP Touch Recovery for Tianshi-Digiland DL701Q Tablet

DL701Q/Root Guide, Install TWRP Touch Recovery
SECURITY UPDATE: Some of the executable programs in this guide may be mistakenly quarantined as a virus by your antivirus program. There are workarounds for this but it is outside the scope of this guide. You can find instructions on how to add temporary exceptions to your antivirus program within its respective documentation. If you make these types of adjustments to your security program in order to install and execute these programs, you do so at your own risk.
Disclaimer: This guide assumes that this is the first attempt to accomplish root and fresh drivers will be installed during the process; if you have already attempted to root your device without success, you may have apps, scripts or drivers on your PC or Tablet which will render this method unsuccessful. Start with a clean tablet, without previous driver installs for the device on your PC.
{
"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"
}
Aside from the root apps you see here, XPOSED Framework is also functional after root.
If you choose to update your system, go ahead and system/wireless update your tablet to 4.4.0/A86V_004, (System Settings -->About Phone -->System Update/Wireless Update), The wireless update does include some security patches, however this root method and recovery installation are still successful. Further test results will be posted as updates are available. Please feel free to add feedback if you have updated your system/wireless settings beyond this guide and attempted the process. -Thank you.
Download/Install SuperSU app from the play store.
Download/extract the iroot installer to your DESKTOP. (Warning: Rooting or modifying your software may void your warranty, proceed at your own risk)
iRoot Download Page Notice: This guide applies ONLY to the PC VERSION, not to the mobile APK.
1. On your Tablet, activate Developer Options (System Settings-->About Tablet-->Build Number (tap 7 times)-->System Settings-->Developer Options-->USB Debugging.
2. Connect your Tablet to your PC, run iRoot as Administrator and wait for iRoot to detect your device and install drivers. Please use a quality USB cable that was made to transfer data, not a standard charging cable.
3. After drivers are installed, click the green root button in the program to initiate rooting sequence, (during the sequence the program should temporarily put your device into Fastboot mode and download the MT65 driver automatically. (If the driver fails to install you may need to boot into fastboot (hold volume down/power until menu comes up, use volume key to select fastboot and connect to pc), mode seperately in order to get the(MT65XX) driver, if the iroot program doesn't automatically install, start back at step two after rebooting into normal mode.)
4. When the program is completed it will indicate that you have root, disconnect your device and open the SuperSU app. This should prompt the Chinese SU app on your tablet to notify you to grant su permissions to the English version, click the grant icon in the notification, SU should now be administering root on your device. If the SuperSU app doesn't successfully update the binary, you most likely do not actually have root and will need to restart the process.
Two Chines apps will be installed along with root, you can delete them after you are administering root from SuperSU without any adverse affects.
Housekeeping:
It has been reported that a couple of activities in the program are inconsistent; you may not get the Chinese notification to grant root privileges to the English version. This would indicate that although the program sees all the flags for root on your PC, there may be a problem with the install. In this case you can attempt to Un-root/Re-root, or try to locate the Chinese app (the installed SU app, not the mobile installer apk), and try to activate it manually.
Currently there is no translation available for the functions so you will need to investigate this.
OK on to the tricky stuff, (well, hopefully not for you)
1. Again go ahead and download/extract this to your desktop. WARNING: There are different versions of the installer, confirm that you only use the installer compatible with MTK Devices with UBIFS system!
Easy Magic TWRP Install Tool
2. Connect your tablet to PC w/USB Debugging on.
NOTE: In some cases users are reporting issues with the manual prompts not being available in the process below. Please run the TWRP in automatic mode initially, then repeat the process in Manual mode. If this doesn't work, it is recommended that you uninstall/re-install the drivers for the tablet, delete the the new recovery image files created by the program and restart the process from scratch. Please report any findings you may have.
3. Run the executable as Administrator. You will need to run this install MANUALLY in order to get the touch screen orientation correct the first time. UPDATE: You may need to run in Automatic mode first run through, it will install but orientation will be incorrect. Re-run program in manual after rebooting tablet and run in manual mode in order to select correct orientation, follow steps 5-8.
4. Download and copy the stock recovery from the link below somewhere on your pc.
stock recovery image
5. Start the MTK-TWRP program and follow the prompts, select NO for manual install. Follow the prompts using the settings below.
6. You will be prompted to place stock recovery in the STOCK folder in the program, go ahead and copy it in there.
7. Follow the rest of the prompts, if the program does not detect your resolution it is; 1024X600.
You will be asked if you have a flipped screen, click YES
You will be asked if you have touch screen problems, click YES
You will then be presented with a selection of screen orientation options, click the radio button for , EDIT: Flipped Screen Swap XY Flip Y. Thanks @IamNWar) UPDATE: This screen orientation confirmed to be working, and recovery is functional. There seems to be a weird glitch after performing an operation that the screen orientation temporarily flips, but this does not appear to affect performance of the recovery.
8 The program will then continue with the installation and boot into recovery (TWRP Touch). If everything is correct, you should have fully functional touchscreen functionality (although it seems upside down, buttons on left).
IMPORTANT: NAND BACKUP TO EXTERNAL SD CARD IS NOW AVAILABLE TO YOUR RECOVERY, BEFORE YOU DO ANYTHING ELSE IT IS ADVISED TO GO AHEAD AND PERFORM A BACKUP AND KEEP IT IN A SAFE PLACE! EVEN IF YOUR DEVICE BECOMES BRICKED LATER, IF YOU HAVE ACCESS TO THE TWRP RECOVERY YOU CAN STILL RESTORE YOUR SYSTEM FROM THE BACK UP. I HAVE TWO OF THESE TABLETS FOR TESTING AND HAVE SUCCESFULLY REMOVED THE OPERATING SYSTEM AND RESTORED IT THROUGH TWRP.
Use the stock recovery below for unpack/repack if you get into trouble and lose stock (English) recovery, (you won't effect the actual chinese stock recovery): Follow the prompts and you will be asked if you want to install the repacked recovery, click yes and your device should reboot to stock recovery.
stock recovery image
Don't forget that this device has a reset button on the back which will assist you to boot up normally, should you run into problems.
If you feel that you have hosed up your recovery through any attempts, I will assist you in returning to stock, which can also be pushed by the TWRP installer. Please give credits/thanks to the great teams that created the iroot and Easy Magic installers. This is simply a guide, I created none of the programs or processes.
Disclaimer: What you do with your device is your own responsibility, modifications may result in voiding your warranty, these instructions are offered as a guide, this guide is in no way endorsing one root/recovery method over another, this is simply the path I found to accomplish the task, please post any shortcuts or errors you may find for the benefit of the community..
Excellent, thanks for documenting the way you did that. I've got my DL701Q upgraded and re-rooted, and will give your TWRP instructions a try.
Are you aware of a custom ROM available for these tablets yet? If not, at least having TWRP will let us make nandroid backups of the stock ROM in the mean time.
sq5 said:
Excellent, thanks for documenting the way you did that. I've got my DL701Q upgraded and re-rooted, and will give your TWRP instructions a try.
Are you aware of a custom ROM available for these tablets yet? If not, at least having TWRP will let us make nandroid backups of the stock ROM in the mean time.
Click to expand...
Click to collapse
Awesome! Not aware of any custom ROM's, but maybe with a working custom recovery, we will move in that direction. I'm not sure what boot-loader issues may be a barrier to that process though.....
Protocol 9 said:
I'm not sure what boot-loader issues may be a barrier to that process though.....
Click to expand...
Click to collapse
Good point. I'm not certain either, but if getting TWRP on is already doable, then that bodes well. Certainly, being able to make backups through TWRP at least makes it more feasible to try other things out.
Did you get installed with the correct orientation?
Sent from my iPhone using Tapatalk
I plan to try the TWRP install out tomorrow.
Guide updated, any feedback regarding content or process corrections would be appreciated.
Thanks,
Proto
Protocol 9 said:
Guide updated, any feedback regarding content or process corrections would be appreciated.
Thanks,
Proto
Click to expand...
Click to collapse
Thanks to your guide and the developers of the softwares, i was able to get my device rooted, Thank you!
However, i do have an issue with the installation of MTK-TWRP and it's screen orientation. After selecting
1024X600 option, i receive no other prompts after selecting Yes to "do you have a flipped recovery screen".
After the device reboots, all the buttons in the TWRP are displayed landscape style, but it's as if the touch sensor
areas for the top half of them are offset of the physical screen.
If i touch in the area near "Reboot" it opens the "Wipe" menu, if the screen is reversed, that is to be expected.
However, if i touch in the "Wipe" button area, expecting to see the "Reboot" menu, nothing happens.
The Home, Back, and Menu buttons are also not accessible if i touch the opposite side of the screen.
It the tablet goes to sleep and i press the power button to wake it, i get a "Swipe to unlock" TWRP screen.
I've tried swiping every which way on the screen to unlock it, but with no success. I have to use the reset button.
I even tried selecting a smaller resolution, but it only makes the TWRP screen smaller and offset, the top rows of options are still unavailable.
Any ideas?
[Guide]How to Root and Install TWRP Touch Recovery for Tianshi-Digiland DL701...
Repeat the process, it will give you the orientation options. If it doesn't, run it in automatic, then in manual.
Sent from my DL701Q using Tapatalk
Protocol 9 said:
Repeat the process, it will give you the orientation options. If it doesn't, run it in automatic, then in manual.
Sent from my DL701Q using Tapatalk
Click to expand...
Click to collapse
Thanks!
I'll give automatic a try. I've gone through the manual setup 3-4 times with the same results.
SockRamen said:
Thanks!
I'll give automatic a try. I've gone through the manual setup 3-4 times with the same results.
Click to expand...
Click to collapse
Interesting, let me know if doing the automatic method first works first go, it may ask the questions regarding resolution and flip screen, but will not give you options to change orientation. It will back up your recovery however, I will update the instructions on your feedback....thanks for the input.
Still having the same issue as before, even with automatic setup, it says it is unable to determine the resolution,
I select the 1024X600 and it askes me if i have a flipped recovery screen. If i select Yes or No, the TWRP button touch response positions are scrambled, and if it goes to the slide to unlock screen, i cannot unlock it, i have to reset it.
Here is the map if i say yes to flipped recovery
Install : Press Settings
Backup : Press Restore
Restore : Press between Restore and Advanced
Wipe : Press Advanced
Mount : Press unknown
Settings : Press Install
Advanced : Press between Install and Mount
Reboot : Press Mount (Reboot menu touch positions are scrambled too)
Home Icon opposite corner area below reboot
back Icon opposite corner area below reboot
Menu Icon opposite corner area below reboot
Ha! to unlock swipe from Install to Mount !
Well, it's sorta mapped, but even if i select Reboot and then Power Off in the Reboot menu screen, it still boots back into TWRP. To get it to boot to the OS, i have to use the reset button.
Is there an option to remove TWRP. I know it's usefull, i have it on my N4, but for this tablet, its not really necessary, stock ROM is fine, as long as i can stop some services with Ti backup.
Edit: I can get out of TWRP with a long press of the power button and then power it up to the OS normally.
Once you run the program on automatic, you should run it in manual mode. It should give you options to select your orientation if you follow the prompts. Not sure why you're not seeing those menu options.
Sent from my DL701Q using Tapatalk
Oops...
Hi protocol. I hope you can help me. I had this tablet rooted. I downloaded an app that didn't play nice and tried to reboot. Now it won't go past the digiland screen.the little blue animation doesn't pop up or anything.I have tried factory resetting but no luck. Any ideas on how to fix? If I could somehow get the stock update.zip I could probably flash that in stock recovery but I haven't been able to find the firmware. Any help would be appreciated.thanks
Sent from my SCH-I605 using Tapatalk 4
UPDATED: Added warning regarding UBIFS system installer for TWRP. If you are not aware, the DL701Q Tablet utilizes the UBIFS file system. You must use the the correct version of the installer, (MTK Devices w/UBIFS).
You can flash the stock recovery image from my post, but you may need to factory reset in the actual Chinese stock recovery.
Sent from my DL701Q using XDA Free mobile app
I can't get booted up. I know a little about android and it's like the system is hosed somehow. I'm trying to find the stock Rom update.zip which I'm not exactly sure exists. I never had twrp recovery on it. It's got factory recovery.
Sent from my SCH-I605 using Tapatalk 4
Try booting into recovery (power/volume down buttons), and attempt to factory reset from there.
After a break, i picked this back up again today.
I was able to initiate the correct selections to do a factory wipe via TWRP
and started over. I re-ran Iroot, and it verified i already/still had root.
I then ran MTK-TWRP in auto and then in manual.
(i do get a verification that i have UBIFS)
This time i did get a screen that asked me if i had touch problems
and then asked me to select the orientation. :good:
I thought got the orientation incorrect though, it was flipped opposite diagonally, but
at least i knew where to press to activate the intended button.
I rebooted it and re-ran TWRP in manual again to see if i had selected the incorrect orientation.
screenshot (no outside links for noobs evidently) httpee://i.imgur.com/sqQE3NL.jpg (remove the ee)
But the buttons were still flipped diagonally (Mount = Wipe, Install = Reboot and vice-versa)
I will still consider it a success, atleast i know where to press and will play around with selecting
different orientation options later and update you if i find a combo that works. Thanks again for all your help!
Protocol 9 said:
Try booting into recovery (power/volume down buttons), and attempt to factory reset from there.
Click to expand...
Click to collapse
I've factory reset in recovery already. No luck booting.
Sent from my SCH-I605 using Tapatalk 4

[Recovery][Exynos][G550T/T1] Official TWRP for on5ltetmo (Galaxy On5)

Team Win Recovery Project 3.0.2-0
This is for the Exynos SM-G550T and SM-G550T1 models only!
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxyon5tmobile.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR OBTAINING ROOT
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for on5ltetmo.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can pull the battery then place the battery back in. Now hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Initial build on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_samsung_on5ltetmo (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_on5ltetmo (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy On5 T-Mobile, Tool/Utility for the Android General
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_on5ltetmo
Version Information
Status: Beta
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-07-20
Created 2016-07-21
Last Updated 2016-07-29
Works great
Verified working, of course.
Will this trigger a bootloop bc of KNOX?
I just got the on5, which immediately upgraded to 6.0.1. How do you check if your bootloader is unlocked? Whenever I adb reboot into bootloader it just reboots into the normal system and my googlfu is failing to find a way to see it. THe debug info shows
[ro.bootloader]: [G550TUVU1APF1]
i followed this guide and it worked but today after rebooting my device it says custom binary blocked by frp and i cant access recovery mode, only download mode. i need a rom of the vanilla firmware i think. can anyone please help
if you do this and brick your phone (On5) you are ****ed no on has other roms or the stock firmware this is the only twrp i have found (other are outdated) i successfully rooted my phone but when i tried to install xposed my **** bricked :crying: i thought twrp will do it but no .....
Thought I would post a tip for anyone else trying to get this to work as I was completely unable to get my phone to boot into recovery on the first boot up after using Odin (I probably tried 20+ times).
Before pressing Start in Odin, turn off the auto-reboot setting. Once the log shows success on the computer, simply pull the battery to turn off the device. Replace the battery and use the normal Volume Up+Home combination when turning on the phone to go straight to recovery.
This worked like a charm for me and removed a huge headache in the process!
killereddie said:
if you do this and brick your phone (On5) you are ****ed no on has other roms or the stock firmware this is the only twrp i have found (other are outdated) i successfully rooted my phone but when i tried to install xposed my **** bricked :crying: i thought twrp will do it but no .....
Click to expand...
Click to collapse
I have one of these phones from T-Mobile fresh out of the box that I got from a promotion. Is there a way to dump the roms without rooting or unlocking? I already have a Galaxy S5 so it's not going to be touched really and used as a backup, but I also don't want to brick it and not have a backup phone.
Model: SM-G550T
Build: MMB29K.G550TUVU1APED
Kernel: 3.10.9-8180604
That's currently what it has running Android 6.01 straight from the box. If there's a way I can help here let me know because I eventually want to root/unlock this thing safely if possible. Until then it's going to sit nice and safe in it's place. :laugh:
That's super nice of you to offer.
Disclaimer: I have no idea what I'm talking about
I think ADB should work for this. Ive tried this with my wife's phone which is identical to mine but I couldn't flash the system.img.. anyways. It'd be nice if someone who knew more than me could confirm if this will work.
1. Enable usb debugging in dev options
2. Get ADB on your pc and go into console in the adb directory
3. Plug the phone in to your computer
4. Type adb shell
5. Type dd=/dev/block/bootdevice/by-name/RECOVERY of=/external_sd/recovery.img
6. That should put it on your removable SD
7. Type dd=/dev/block/bootdevice/by-name/SYSTEM of=/external_sd/system.img
The thing is I'm pretty sure this won't work but maybe it will. I have a G550T1 so I doubt it'd help me but it maaay work for the T-Mobile versions. They'd just convert the img into a tar and flash with Odin.
I dont think system.img can be flashed from using dd but it's worth a shot if you don't mind. It is a large file, however, at least 2.5gb.
Hi jcadduono,
thanks for the instruction ....... Seems like all works well, Odin says PASS !, except I am not able to perform the following step :
"Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery."
I tried like 20 times, but after holding "Volume Up + Home", my phone just reboots normally, but does not go into recovery.....
Can you please narrow down for me when I have to push them together to get into TWRP ?
Thx, Good work
bandtab said:
That's super nice of you to offer.
Disclaimer: I have no idea what I'm talking about
I think ADB should work for this. Ive tried this with my wife's phone which is identical to mine but I couldn't flash the system.img.. anyways. It'd be nice if someone who knew more than me could confirm if this will work.
1. Enable usb debugging in dev options
2. Get ADB on your pc and go into console in the adb directory
3. Plug the phone in to your computer
4. Type adb shell
5. Type dd=/dev/block/bootdevice/by-name/RECOVERY of=/external_sd/recovery.img
6. That should put it on your removable SD
7. Type dd=/dev/block/bootdevice/by-name/SYSTEM of=/external_sd/system.img
The thing is I'm pretty sure this won't work but maybe it will. I have a G550T1 so I doubt it'd help me but it maaay work for the T-Mobile versions. They'd just convert the img into a tar and flash with Odin.
I dont think system.img can be flashed from using dd but it's worth a shot if you don't mind. It is a large file, however, at least 2.5gb.
Click to expand...
Click to collapse
Jcadduono is working with me to help provide something for people with something they can use right now. Took me a bit to understand ADB shell and everything along with the phone compiling these img files for hours. After this if all goes well there will be a stock .tar for people to flash their soft bricked phones and fix everything hopefully. So you can pretty much thank them for working with my newbieness for hours to make this possible.
jce2005 said:
Hi jcadduono,
thanks for the instruction ....... Seems like all works well, Odin says PASS !, except I am not able to perform the following step :
"Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery."
I tried like 20 times, but after holding "Volume Up + Home", my phone just reboots normally, but does not go into recovery.....
Can you please narrow down for me when I have to push them together to get into TWRP ?
Thx, Good work
Click to expand...
Click to collapse
A couple posts above gives good advice here to uncheck the auto reboot box in Odin before you flash then hold the buttons which I think is PWR+Vol-up+Home all together. You'll have to pull your battery ONLY AFTER it finishes and says success along with disconnecting the USB which can still power your phone.
Hi there, thanks for the advise...... I'll try it in the morning.....
At what point do I need to pull the battery and power cable ? Before or after going into TWRP Recovery ? I am a bit confused right now... LOL
jce2005 said:
Hi there, thanks for the advise...... I'll try it in the morning.....
At what point do I need to pull the battery and power cable ? Before or after going into TWRP Recovery ? I am a bit confused right now... LOL
Click to expand...
Click to collapse
When you uncheck the box to not auto-restart after flashing it will just sit there after it flashes TWRP onto your phone. You pull the battery out AFTER it successfully flashes so your phone will power off giving proper time to hold PWR+Vol-Up+Home which will boot into TWRP.
DANG ! Root on Galaxy On5 !
All worked perfect, TWRP installed with Odin and then flashed SuperSU via TWRP and recovery as well as root sticks !!! Perfect,
Thanks to all of you.
PS: the instructions in the OP should be updated so people know to UNCHECK the Auto Reboot, remove battery and USB cable and do the "Volume Up + Home + Power to get into TWRP to flash SuperSU. Also, might be a good idea ( I did it this way ) to download SuperSU before starting the procedure and putting it in the root of Main Memory........ It's easier to flas this way once TWRP is installed.
For those who need to restore full stock, I have Odin flashable firmware for G550T here thanks to a user who worked with me to back it all up from their device: https://idlekernel.com/flash-tools/firmware/on5ltetmo_SM-G550T/G550TUVU1APF1/
It's missing BL (sboot.bin) as BOOTLOADER partition was unavailable for access by kernel.
Do not flash the OPT tar.md5 unless you're absolutely bricked. It contains all the other flashable partitions, ex. EFS.
jcadduono said:
For those who need to restore full stock, I have Odin flashable firmware for G550T here thanks to a user who worked with me to back it all up from their device: https://idlekernel.com/flash-tools/firmware/on5ltetmo_SM-G550T/G550TUVU1APF1/
It's missing BL (sboot.bin) as BOOTLOADER partition was unavailable for access by kernel.
Do not flash the OPT tar.md5 unless you're absolutely bricked. It contains all the other flashable partitions, ex. EFS.
Click to expand...
Click to collapse
Is there a G550T1 one?
I made an update.zip of stock metro pcs (G550T1) apps (system apps that is) if anyone has a need for it. I'll upload it to mega and post a link if people want it send me a message or I can just post it on here. What do you guys think?
---------- Post added at 10:00 AM ---------- Previous post was at 09:46 AM ----------
https://mega.nz/#!PEgSyQSA
Here ya go for anyone who wants it
System apps for G550T1
jce2005 said:
Hi jcadduono,
thanks for the instruction ....... Seems like all works well, Odin says PASS !, except I am not able to perform the following step :
"Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery."
I tried like 20 times, but after holding "Volume Up + Home", my phone just reboots normally, but does not go into recovery.....
Can you please narrow down for me when I have to push them together to get into TWRP ?
Thx, Good work
Click to expand...
Click to collapse
It's volume-up + home + power...three things to hold
zgauthier8286 said:
I made an update.zip of stock metro pcs (G550T1) apps (system apps that is) if anyone has a need for it. I'll upload it to mega and post a link if people want it send me a message or I can just post it on here. What do you guys think?
---------- Post added at 10:00 AM ---------- Previous post was at 09:46 AM ----------
https://mega.nz/#!PEgSyQSA
Here ya go for anyone who wants it
System apps for G550T1
Click to expand...
Click to collapse
what's the pw for the download? gonna try throwing this at my phone and seeing what happens. but if its the OTA update.zip i think i already tried that, pulled it off another phone
https://mega.nz/#!PEgSyQSA!J5FyBKL2oswW3NG1okZft9epKbhLwwkqobHHzn8okX8
Try that link instead
---------- Post added at 01:27 AM ---------- Previous post was at 01:17 AM ----------
Here's a link for stock boot, sbl1, and emmc partitions as well. You'll need 7zip or some archive extractor to unzip it. It's in raw img format after you decompress it.
https://mega.nz/#F!CAgila5T!toHgR8YtirBHK6ZjB4ZLzA

"Erasing" Loop - Tried Returning to Stock After Converting to US998 from H933

"Erasing" Loop - Tried Returning to Stock After Converting to US998 from H933
I rooted my phone using LGUP and tried to switch back to stock; hoping to keep root. I flashed all items except "recovery" but then tried to re-flash just the stock recovery, as stated in on one of the posts I found, and now I think I have a paper weight. I made sure to read the instructions a few times before doing things, but guess I missed something, or the instructions I followed aren't for my version or may be outdated?!
I can't get into download mode. The PC doesn't recognize I've even plugged it in. And now it just keeps boot looping showing the Erasing Circle over and over and over.
Anyone here know if I have any hope that once the battery dies, I could plug it in, holding the volume up, and be able to get into download mode? I'm hoping I can... Not a happy camper right now.
I see the thread title now. Let me respond in a few minutes.
---------- Post added at 07:40 PM ---------- Previous post was at 07:31 PM ----------
ColtonYYZ said:
I rooted my phone using LGUP and tried to switch back to stock; hoping to keep root. I flashed all items except "recovery" but then tried to re-flash just the stock recovery, as stated in on one of the posts I found, and now I think I have a paper weight. I made sure to read the instructions a few times before doing things, but guess I missed something, or the instructions I followed aren't for my version or may be outdated?!
Click to expand...
Click to collapse
You didn't root your phone with LGUP. You rooted your phone with TWRP and Magisk. You used LGUP to convert to US998 so you would have fastboot flash commands to unlock bootloader and install TWRP, so you could then root with Magisk.
Why don't you ask in thread where you were following the directions? Yes, it is tedious and complicated for the H933 -- but the end result is you WANT TWRP custom recovery and Magisk, but you want to eradicate all traces of US998 firmware.
I still don't have any answer to my question though...
ChazzMatt said:
I see the thread title now. Let me respond in a few minutes.
---------- Post added at 07:40 PM ---------- Previous post was at 07:31 PM ----------
You didn't root your phone with LGUP. You rooted your phone with TWRP and Magisk. You used LGUP to convert to US998 so you would have fastboot flash commands to unlock bootloader and install TWRP, so you could then root with Magisk.
Why don't you ask in thread where you were following the directions? Yes, it is tedious and complicated for the H933 -- but the end result is you WANT TWRP custom recovery and Magisk, but you want to eradicate all traces of US998 firmware.
Click to expand...
Click to collapse
I appreciate you taking the time to reply. You are correct in saying I didn't root with LGUP. I mistyped/misspoke. There are so many threads that I read, I can't find the one I was following. I had 15 tabs opened; I freaked out, and so I created a new thread for my problem. My problem doesn't really involve any particular thread now because it's not even booting up - in order for me to do anything.
I see the LG logo.. then sometimes I see the stupid bootloader warning, then back to LG logo for a few seconds and then it says "Erasing" in bold vibrant colouring.. then it shades out barely visible for 10-15 secs. Turns off, then basically repeats.
I know about all the flashable zips for H933.... but ALL of them say NOT to use them to convert back from US998 to H933.
Here is a thread (step 5) which basically everyone else posts also, that says you flash the kdz - everything except recovery - and twrp should be installed. This is not true. I did this about 6 times and could never boot into recovery afterwards. It would erase the phone and go back into setup mode each and every time.
I couldn't find any article to explain how to get back to stock firmware without using the kdz, which I did, and unselecting recovery. When doing so, twrp was gone - despite me not selecting recovery or even recovery.bak sometimes. So what I did was, use LGUP again with the kdz and uncheck everything except recovery and recovery.bak the 2nd time around and bam... now I am stuck.
ColtonYYZ said:
I appreciate you taking the time to reply. You are correct in saying I didn't root with LGUP. I mistyped/misspoke. There are so many threads that I read, I can't find the one I was following. I had 15 tabs opened; I freaked out, and so I created a new thread for my problem. My problem doesn't really involve any particular thread now because it's not even booting up - in order for me to do anything.
I see the LG logo.. then sometimes I see the stupid bootloader warning, then back to LG logo for a few seconds and then it says "Erasing" in bold vibrant colouring.. then it shades out barely visible for 10-15 secs. Turns off, then basically repeats.
I know about all the flashable zips for H933.... but ALL of them say NOT to use them to convert back from US998 to H933.
Here is a thread (step 5) which basically everyone else posts also, that says you flash the kdz - everything except recovery - and twrp should be installed. This is not true. I did this about 6 times and could never boot into recovery afterwards. It would erase the phone and go back into setup mode each and every time.
I couldn't find any article to explain how to get back to stock firmware without using the kdz, which I did, and unselecting recovery. When doing so, twrp was gone - despite me not selecting recovery or even recovery.bak sometimes. So what I did was, use LGUP again with the kdz and uncheck everything except recovery and recovery.bak the 2nd time around and bam... now I am stuck.
Click to expand...
Click to collapse
Who said you couldn't use H933 after US998? You're fine if you use partition DL.
I have gone from US998 to H933 several times.
I'm currently on my commute to work but let me read your issues and see if we can't get you back to normal.
( I'm pretty active in modding our H933 )
Don't touch recovery.bak; only deselect recovery.
So where are you currently?
And after you pull your phone from PC after not selecting recovery are you pulling your phone and trying to master reset to access recovery or letting LGUP auto boot into twrp? Should happen as soon as H933 attempts to boot.
ColtonYYZ said:
I see the LG logo.. then sometimes I see the stupid bootloader warning, then back to LG logo for a few seconds and then it says "Erasing" in bold vibrant colouring.. then it shades out barely visible for 10-15 secs. Turns off, then basically repeats.
Click to expand...
Click to collapse
Have you tried Master Reset to stop the boot looping? Master Reset is not factory reset.
Master Reset -- using buttons:
1. Unplug phone and turn it OFF.
2. Press and hold the Power and Volume down buttons.
3. When the LG logo appears, quickly release the Power button only -- then immediately press Power button again, while STILL pressing the Volume down button until you see the screen to select Yes to erase and reset everything.
4. Release both buttons so you can make your choices.
With your device powered off, press and hold the Power button and Volume Down buttons simultaneously for a few seconds.
When the LG logo appears, quickly release and then re-hold the Power button while keep holding the Volume Down button.
Let go of the buttons when the onscreen menu appears.
When you see the option to Delete all user data (including LG and carrier apps) and reset all settings message prompt, press the Volume Down button to highlight Yes.
Then press the Power button to reset the device.
Wait until the reset is complete then reboot your device. If it’s able to boot up successfully, proceed with the initial setup.
Click to expand...
Click to collapse
You can even do it if you can not power the device off, but you just have to time it right.
This is the most complete guide of what you were probably trying to do, if trying to go back to stock and keep root:
seadersn said:
@christopherrrg wrote a "little guide" for the peoples, who may ever have thought about going back to h33 original (rooted or not) sw. Give him some thanks pls, he's now a few nerves lost in this procedure i can imagine :good: thanks!
Here it is:
Okay so the steps below are for AFTER using the WTF thread to convert device and unlock bootloader; these steps are for canadian model users who would prefer to go back to stock canadian kdz with working root and twrp intact.
Step 1 - Attach converted US998 (bl unlocked and twrp installed) to LGUP.
Step 2 - PARTITION DL the canadian kdz but do not include recovery.
Step 3 - Let phone boot right from kdz flash and it will automatically boot TWRP.
Step 4 - While in TWRP; 1st factory reset AND AFTER format data then reboot recovery. (If not done TWRP has mount issues with cache and or system.)
Step 5 - After TWRP is rebooted flash no-verity-opt-encrypt-6.0.zip + lg-rctd-disabler-1.0.zip and afterwards flash magisk.
Step 6 - While still in TWRP use the option to power device down.
Step 7 - Attach device to PC while holding vol+ and it will automatically start download mode.
Step 8 - PARTITION DL the canadian kdz again EXCEPT uncheck everything BUT stock recovery; let it flash and reboot.
Step 9 - Should reboot 3 - 4 times.
Step 10 - Once booted to setup; get past then activate USB debugging, also open magisk and click yes as many times as it asks you. (Magisk remains because only RECOVERY is flashed at this point)
Step 11 - Download TWRP and rename to just twrp then place it in the root directory of your internal storage.
Step 11 - Connect device to android debug bridge, and start a shell with 'adb shell' command.
Step 12 - then type 'su' and hit enter in order to gain root privilege. (Will have to click accept on super user on device)
Step 13 - then type 'dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery'
If done correctly you should see flashing (almost like fastboot) however you will not have anything happen to your device graphically SO open magisk and click modules then click reboot to recovery and profit!
You should be on H933 kdz with TWRP and root.
However for some weird reason, cloud is correct as the battery drain is abysmal. My phone used to go from 9am 100% to about 60% by the time I get home at 5pm. Today it's gone down to 22% from 100% at 9am and it's only 2pm. @cloud1250000's brain was mostly picked for this so he deserves any and all credit; I just confirmed and wrote this up for reference.
Enjoy!
Credits to @cloud1250000 ​
Click to expand...
Click to collapse
Also; I realize my guide in seadersn posts need a bit of an update so I will message him today and have him update as a ton of people are using it for reference and that guide has battery issues. (Without doing dd etc)
Try following this guide to the letter.
https://forum.xda-developers.com/lg-v30/how-to/canadian-h933-compatibility-h930-roms-t3897586
Just replace the latest with 20i (h933)
Make sure to read my post inclusive at the end of that thread; feel free to PM me as well if you can't get anything the way you want it.
Unfortunately I can't do anything with the phone when I connect to my PC with the USB cable - except when holding power and both Cole buttons, i can get it to load a page with the imei number etc.
I can also (by holding power and toggling both volumes) get it to recognize on my PC, but it shows up at QSLoader 9008 (or something like that - I'm at work right now so can't type exactly what it shows up as - but know 100% it says 9008).
I installed QPST and will see if I can flash it this way, after I figure out a way to create/find the firehouse. I found a YT video showing how to create the files needed so will give it ago when I get home.
I am grateful of the replies. I'm sure you get many idiots like myself who do stupid crap - so thank you for always still wanting to help. It must be annoying but us idiots are truly grateful!!
ColtonYYZ said:
Unfortunately I can't do anything with the phone when I connect to my PC with the USB cable - except when holding power and both Cole buttons, i can get it to load a page with the imei number etc.
I can also (by holding power and toggling both volumes) get it to recognize on my PC, but it shows up at QSLoader 9008 (or something like that - I'm at work right now so can't type exactly what it shows up as - but know 100% it says 9008).
I installed QPST and will see if I can flash it this way, after I figure out a way to create/find the firehouse. I found a YT video showing how to create the files needed so will give it ago when I get home.
I am grateful of the replies. I'm sure you get many idiots like myself who do stupid crap - so thank you for always still wanting to help. It must be annoying but us idiots are truly grateful!!
Click to expand...
Click to collapse
This sounds like what had happened to me with the RSA after flashing modem.bin. I only got lucky because my TWRP flashed successfully and I was able to restore using seadersn stock method. I've never gone as far as actually putting my device into 9008 brick (yet) so unfortunately I'm not much help there and for that I'm sorry. However there is a gent on ebay who will TeamViewer to your PC and fix it for you. A lot of people report it has a different device firmware but they do report success.
Also don't beat yourself up and call yourself an idiot.
Us humans are curious creatures! While it does suck for your device; it's just a speed bump!

Boot loop - Can't power off, no recovery, won't boot

Hello,
I've got a Realme 7. Tried to update a ROM, something happened, lost recovery, not it's boot looping.
I understand what I need to do - Reflash stock rom and recovery.
However, I can't get my phone to power off, I can't get the USB filters installed, I can't do anything...
Holding power does nothing, holding vol + and power does nothing...It just keeps looping back to the realme logo.
I assume, if I can get it powered off, I can then hold volume up and down to get libusb to recognize it and then go from there. However, I'm at a loss...
Thanks.
tazz131 said:
Hello,
I've got a Realme 7. Tried to update a ROM, something happened, lost recovery, not it's boot looping.
I understand what I need to do - Reflash stock rom and recovery.
However, I can't get my phone to power off, I can't get the USB filters installed, I can't do anything...
Holding power does nothing, holding vol + and power does nothing...It just keeps looping back to the realme logo.
I assume, if I can get it powered off, I can then hold volume up and down to get libusb to recognize it and then go from there. However, I'm at a loss...
Thanks.
Click to expand...
Click to collapse
Open the USB filters wizard, and pay attention when the device is trying to boot, you could install it, see which item is added. To completely power off the device, you just have to press the three buttons simultaneously.
Yeah, can't get it to the point where
SubwayChamp said:
Open the USB filters wizard, and pay attention when the device is trying to boot, you could install it, see which item is added. To completely power off the device, you just have to press the three buttons simultaneously.
Click to expand...
Click to collapse
Yeah, can't get it to the point where the device gets added.
The 3 buttons doesn't seem to work either. Just black screen, then Realme logo - Orange state - Your device will boot in 5 seconds.
It just goes black again, and back to the realme logo.
Can't get to do anything.
tazz131 said:
Yeah, can't get it to the point where
Yeah, can't get it to the point where the device gets added.
The 3 buttons doesn't seem to work either. Just black screen, then Realme logo - Orange state - Your device will boot in 5 seconds.
It just goes black again, and back to the realme logo.
Can't get to do anything.
Click to expand...
Click to collapse
In the short time it is going to blank screen it is power off, then immediately it is trying to boot, I faced the same a lot of times. A variant, pressing vol up + PWR also device gets off, when device is trying to boot, tap on the item newly added and install it, open firstly the libUSB wizard and keep it open, and visible to you.
Yeah, I can't get it. Doesn't seem to detect that the phone is connected to my computer at all. Nothing shows up in the USB filters...Doesn't seem to matter when I press volume up and down throughout the process...
Can't seem to do anything. Just looping...Ugh - I guess I'm out of luck?
tazz131 said:
Yeah, I can't get it. Doesn't seem to detect that the phone is connected to my computer at all. Nothing shows up in the USB filters...Doesn't seem to matter when I press volume up and down throughout the process...
Can't seem to do anything. Just looping...Ugh - I guess I'm out of luck?
Click to expand...
Click to collapse
Install all the previous drivers needed.
Also you have this tool to flash recovery and see from there https://github.com/bkerler/mtkclient
To get it work you don´t need the LibUSB32, you have to find the short time device is trying to reboot to press the volume buttons to connect to the tool.
SubwayChamp said:
Install all the previous drivers needed.
Also you have this tool to flash recovery and see from there https://github.com/bkerler/mtkclient
To get it work you don´t need the LibUSB32, you have to find the short time device is trying to reboot to press the volume buttons to connect to the tool.
Click to expand...
Click to collapse
OK, looking at MTK Client - Can't seem to get it to run in a GUI...No idea how to flash anything in it...This is beyond my pay grade...Hah
tazz131 said:
OK, looking at MTK Client - Can't seem to get it to run in a GUI...No idea how to flash anything in it...This is beyond my pay grade...Hah
Click to expand...
Click to collapse
Well, man, you need to follow instructions to get it to work properly, anyway if you already installed properly the UsbDK 64 then you can invoke the graphical interface, typing in a CMD (open in this path) python mtk_gui
Yeah, I've followed the instructions, and a YouTube tutorial - I have everything installed. However, I'm not getting the gui...
Thanks for the help by the way. Getting there...
tazz131 said:
Yeah, I've followed the instructions, and a YouTube tutorial - I have everything installed. However, I'm not getting the gui...
Thanks for the help by the way. Getting there...
Click to expand...
Click to collapse
Open a terminal in the same mtk-client main directory and type python mtk_gui or directly through the command line, use python mtk w recovery drag&drop your image
SubwayChamp said:
Well, man, you need to follow instructions to get it to work properly, anyway if you already installed properly the UsbDK 64 then you can invoke the graphical interface, typing in a CMD (open in this path) python mtk_gui
Click to expand...
Click to collapse
OK, phone is dead now...Hah - Time to do some more research.
I assume that once I get it loaded up in MTK Client I can just flash recovery.img from the stock rom?
Or do I need to flash something else completely?
tazz131 said:
OK, phone is dead now...Hah - Time to do some more research.
I assume that once I get it loaded up in MTK Client I can just flash recovery.img from the stock rom?
Or do I need to flash something else completely?
Click to expand...
Click to collapse
No, it's not dead, I had bricked my device even in a state of no signal of life at all, but I have completely working now, just I lost IMEI cause a bad flashing and back up gone.
You should start by flashing only the stock recovery, so you can try to flash an ozip from there, be sure your device has some charge now and check all the drivers you have installed.
Open device manager in Windows, and connect your PC while you are pressing buttons and so, and check how it is listed there.
This is preloader mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And this is BROM mode:
SubwayChamp said:
No, it's not dead, I had bricked my device even in a state of no signal of life at all, but I have completely working now, just I lost IMEI cause a bad flashing and back up gone.
You should start by flashing only the stock recovery, so you can try to flash an ozip from there, be sure your device has some charge now and check all the drivers you have installed.
Open device manager in Windows, and connect your PC while you are pressing buttons and so, and check how it is listed there.
This is preloader mode:
View attachment 5561119
And this is BROM mode:
View attachment 5561121
Click to expand...
Click to collapse
OK, I will check the drivers. MTK Client can't see it - So there must be something wrong with the drivers...
tazz131 said:
Hello,
I've got a Realme 7. Tried to update a ROM, something happened, lost recovery, not it's boot looping.
I understand what I need to do - Reflash stock rom and recovery.
However, I can't get my phone to power off, I can't get the USB filters installed, I can't do anything...
Holding power does nothing, holding vol + and power does nothing...It just keeps looping back to the realme logo.
I assume, if I can get it powered off, I can then hold volume up and down to get libusb to recognize it and then go from there. However, I'm at a loss...
Thanks.
Click to expand...
Click to collapse
hold volume + and power button for while, as soon as the screen turns off leave the button. your phone will successfully turn off. and to solve the problem. you need to download the official firmware which have scatter file and Remember to backup your NV data OR any NV RAM before flashing or you will loose IMEI number because of which many people are facing IMEI problem including me.. So after backup Flash the firmware with format all or re-partition and will successfully boot up. remember to restore NV DATA/NV RAM. you can use unlock tool to flash the firmware.
Same problem here... I change my Chinese GT2 Pro to Global, everythings fine, but when I tried to lock the bootloader a message apears saying the flash was broken or something and now it keeps flashing the "realme Powered by android" for 0,5 a sec and rebooting again and again and again... can't do absolute nothing...
tazz131 said:
Yeah, I can't get it. Doesn't seem to detect that the phone is connected to my computer at all. Nothing shows up in the USB filters...Doesn't seem to matter when I press volume up and down throughout the process...
Can't seem to do anything. Just looping...Ugh - I guess I'm out of luck?
Click to expand...
Click to collapse
hey, tazz, have you solved the problem yet? i'm currently on the same predicament as you are, just on a C12 instead of a 7.
Any one could recovery the phone after this problem? Seems that this problem is common, but I do not find any one that tells that fixed it and how did it...
barenko said:
Any one could recovery the phone after this problem? Seems that this problem is common, but I do not find any one that tells that fixed it and how did it...
Click to expand...
Click to collapse
Recover from what? There are many users including me that recovered the 99% of its functionalities. If you are referring to the IMEI, then, yes, and not, it´s not possible by any tools that available for end users, but it can be done through specialized hardware tools.
SubwayChamp said:
Recover from what? There are many users including me that recovered the 99% of its functionalities. If you are referring to the IMEI, then, yes, and not, it´s not possible by any tools that available for end users, but it can be done through specialized hardware tools.
Click to expand...
Click to collapse
Recover that:
Bash:
fastboot flashing unlock
fastboot.exe flash recovery corrupted_recovery.img
fastboot.exe flash vbmeta corrupted_vbmeta.img
fastboot.exe boot corrupted_recovery.img
After this, the phone is on boot looping, and because the looping, the usb is reconfiguring all the time (I was unable to get time enough to connect using adb or fastboot)
EDIT: I forgot to mention that the physical buttons does not respond after this procedure. I'm unable to use power; power+down; power+up...
barenko said:
Recover that:
Bash:
fastboot flashing unlock
fastboot.exe flash recovery corrupted_recovery.img
fastboot.exe flash vbmeta corrupted_vbmeta.img
fastboot.exe boot corrupted_recovery.img
After this, the phone is on boot looping, and because the looping, the usb is reconfiguring all the time (I was unable to get time enough to connect using adb or fastboot)
EDIT: I forgot to mention that the physical buttons does not respond after this procedure. I'm unable to use power; power+down; power+up...
Click to expand...
Click to collapse
Just search in the forum, there is not a guide all-in-one, but everything you need is here.
From unlock the bootloader, either officially or unofficially, using mtk-client, updating the drivers through Lib-USB, device filter, flashing every partition using the same tool or SP Flash tool.
Just a side note, Physical button don´t have to do with software issues, device not entering to a specific mode, is not because physical buttons are supposedly, not responding, but this stage is missing or unavailable. There are many posts and guides about unbricking this device, just search thoroughly through the forum.

Categories

Resources