Related
SOLVED - see my last post in this thread
Hello
I was trying to install custom rom on my oneplus one and... don't ask me why but instead of format dalvik/system etc i choose full format (in this section you must enter "yes" before proceed).
I didn't realize that at the end I will not be able to enter fastboot menu! (vol up + power)...
Now all I can do is power on phone in "normal" mode but all I can see in oneplus logo and "powered by android"...
What can I do to re-install os?
Pls help.
Thanks!
I found that article on twrp website:
twrp.me /faq /noos
Code:
No OS Installed! Are you sure you wish to reboot?
If you’re seeing this message in TWRP, this usually means that, one way or another, you have wiped your system partition. How you can fix this issue depends on what device you have and how you want to go about fixing it.
If you have a backup, you may be able to restore your backup to reinstate a working system or OS.
You may be able to find a new “ROM” for your device at places like XDA or use Google to try to locate one. If you have TWRP 2.8.0.0 or newer you may be able to simply plug your device into your computer and use MTP to transfer files. If your device has a removable SD card you can use a card reader to easily transfer the flashable zip to the card then install it under the Install button in TWRP. On some devices you may also be able to use a USB thumb drive along with a special “On-The-Go” cable known as USB OTG to get the file installed. Some devices may support USB mass storage mode (found under the mount menu) to easily copy the file to the device. If all else fails, you can install ADB drivers and software to transfer files using adb push or pull. If you are using Windows (as most people do), it may be difficult to get your computer to properly recognize your device. Windows is really picky about its drivers. You may have to force install a driver or try something like universal or naked ADB drivers.
If the above does not work for you, you can search again on XDA or Google to locate a guide for returning your device back to stock. The process varies depending on what type and brand of device you have. For HTC devices search for “RUU back to stock” plus your device’s name. For Samsung search for “Odin back to stock” plus your device name. LG devices often use a “KDZ return to stock” plus your device name. Google posts factory images for Nexus devices here. Motorola posts factory images for some devices here.
If you still can’t get your device working, don’t bother using the Contact Us button on our web page. We won’t respond to these kinds of support requests.
Any ideas how I can transfer rom files into oneplus? :/
Ok, after connecting phone into computer via usb I can see under windows device manager: MTP USB Device (as unavaiable)
I think I need to install proper drivers for that (see "Windows 7 Portable Device Enabling Kit for MTP") and then I'll able to transfer files... (I don't know how yet...)
https://www.youtube.com/watch?v=NaK5OxUeDKM&index=22&list=LLbsbIuctMb9b87vHzSM8THQ
Got solution!:
([GUIDE] [UNBRICK] Unbrick Oneplus One)
forum.xda-developers.com /oneplus-one /general /guide-unbrick-oneplus-one-t3013732
Q tip if above link will disappear - google for "Qualcomm 2012 drivers, dseo13b, colorOS" phrases.
i was trying to root my phone i done it and i am trying to install a rom to it
after that i twrp and delete all files.
i have files still in my pc can someone help me how to put some zip in the phone because my pc cant detect my phone anymore.
thanks guys
Try re-installing the proper drivers for the device and also try to boot to fastboot and check if it detected. And if it does so, try restoring to official firmware.
If you can buy an OTG cable and try a pendrive. An OTG cable is a life saver in case of Mi4i since it doesn't have an MicroSD. If you haven't bought it yet, today maybe the time
If you have installed the driver. The copying from TWRP only works sometimes.
If you rooted then you must have used Fastboot so the drivers are there.
As hunkerpunk1 said install default ROM via fastboot using MiFlash.
Also if you are going to install CM12.1 or any custom roms here. You're phone must have MIUI 6 installed before not MIUI 7. So flash MIUI 6. Then root it and flash TWRP. Then install the ROM. This time copy the files inside the phone before hand
Please check if you're able to go into recovery (TWRP, NOT Stock), if answer is yes, you can use the mount option to copy those files again into your phone.
You simply need to :
1. Boot into TWRP
2. Connect the phone with PC (With Proper drivers installed)
3. Select the MOUNT option on TWRP Recovery
4. You'll see the prompt on your PC that Mi4i (with some Chinese words prepends) detected.
5. Copy the ROM & Gapps in phone.
6. BOOM (now I'm assuming you know how to move further)
STEP BY STEP GUIDE FOR LG V20 H918 UNLOCKING BOOTLOADER, DOWNGRADING, ROOTING AND INSTALLING CUSTOM ROMS (NOOB FRIENDLY)
DISCLAIMER: I'M NOT THE DEVELOPER OF ANY OF THE BELOW SOFTWARE'S AND YOU PROCEED WITH YOUR OWN RISK AS THIS INVOLVES BRICKING OR DAMAGING YOUR MOBILE IF THE PROCEDURE IS NOT FOLLOWED CORRECTLY. I'M JUST SHARING THE WHOLE PROCESS WHICH I HAVE FOLLOWED TO ROOT AND INSTALL TWRP IN MY LGV20 H918 UNLOCKED T MOBILE.
AND I HAVE TESTED THIS IN MY OWN DEVICE AND WAS ABLE TO ROOT AND ACHIEVE TWRP.
THIS IS ONLY FOR LGV20 H918 VERSION
ENSURE INTERNET IS UP AND RUNNING IN YOUR PC
EDIT: THE WHOLE PROCESS HAS NOW BEEN AUTOMATED IN TWO SIMPLE STEPS TO PREVENT ANY POTENTIAL DAMAGE TO YOUR DEVICE. THANKS TO THE LAFSPLOIT CREATOR BRIAN @runningnak3d.
JUST FOLLOW THE PROCEDURE BELOW AND YOU SHOULD HAVE YOUR DEVICE ROOTED IN NO TIME
1. BACKUP ALL YOUR IMPORTANT DATA BEFORE PROCEEDING.
2.MAKE SURE YOU HAVE CHARGED YOUR PHONE TO AT LEAST 90 PERCENT
CHECK YOUR PHONE SOFTWARE VERSION IN SETTINGS---ABOUT PHONE----SOFTWARE INFO
IF IT IS ANYTHING BETWEEN H91810P TO H91810U MEANS IT IS ARB1 (ANTI ROLL BACK 1) AND YOU NEED TO USE LAFSPLOIT METHOD TO ROOT AND INSTALL TWRP,
IF YOUR VERSION IS H91810O OR BELOW (ARB0), YOU CAN EITHER USE DIRTYCOW OR LAFSPLOIT METHOD FOR THE SAME.
IF YOU ARE ON ARB1, PLEASE FOLLOW THE METHOD BELOW,
PART 1: DOWNGRADING
IF YOUR VERSION IS H91810 (Q, R, S, T, U) YOU NEED TO DOWNGRADE TO A LOWER VERSION ( H91810P) TO EXECUTE LAFSPLOIT.
IF YOU ARE ALREADY ON H91810P, YOU STILL NEED TO RE FLASH THE H91810P KDZ AGAIN FOR THE LAFSPLOIT SCRIPT TO WORK CORRECTLY.
DOWNLOAD H91810P KDZ FILE FROM BELOW
https://androidfilehost.com/?w=files&flid=282709
DOWNLOAD AND INSTALL ALL THE FILES BELOW IN YOUR PC
UPPERCUT AND LGUP----
http://downloads.codefi.re/autoprime/LG/Flash_Tools/LGUP/
LG DRIVERS---
http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
CONNECT YOUR MOBILE TO YOUR PC IN DOWNLOAD MODE (SWITCH OFF YOUR MOBILE AND CONNECT THE USB FROM PC WHILE HOLDING THE VOLUME UP BUTTON SIMULTANEOUSLY)
RUN UPPERCUT.EXE WHICH WOULD OPEN LG'S UPDATER TOOL AUTOMATICALLY.
INSIDE THE LG UPDATER TOOL, CLICK ON BIN AND SELECT THE H91810P KDZ FILE DOWNLOADED EARLIER.
NOW SELECT UPGRADE AND FLASH
ENSURE THE USB CABLE IS CONNECTED THROUGH THE FLASHING PROCESS AND WAIT FOR YOUR PHONE TO REBOOT AND THEN REMOVE THE USB CABLE.
CHECK THE SOFTWARE VERSION AND ENSURE IT IS H91810P
PART 2: UNLOCKING BOOTLOADER
HEAD TO SETTINGS---ABOUT PHONE----SOFTWARE INFO (ENSURE IT IS H91810P)
ENABLE DEVELOPER OPTION IN YOUR PHONE BY CLICKING ON THE BUILD NUMBER MULTIPLE TIMES
NOW HEAD TO SETTINGS---DEVELOPER OPTIONS
TURN ON OEM UNLOCKING, ENABLE USB DEBUGGING AND DISABLE 'VERIFY APPS OVER USB'
NOW CONNECT YOUR PHONE TO PC AND OPEN ADB COMMAND CENTER PROMPT IN YOUR PC
adb devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN ADB
adb reboot bootloader--->THIS REBOOTS YOUR DEVICE IN FASTBOOT MODE
fastboot devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN FASTBOOT
fastboot oem unlock---->THIS COMMAND WOULD UNLOCK YOUR BOOTLOADER AND RESET's YOUR DEVICE.
fastboot oem device-info OR fastboot getvar unlocked ----->THIS WOULD CONFIRM IF YOUR BOOTLOADER HAS BEEN UNLOCKED OR NOT.
fastboot reboot-----> THIS WOULD REBOOT YOUR DEVICE
IF THE BOOTLOADER HAS BEEN SUCCESSFULLY UNLOCKED, THE DEVICE WILL SHOW AN UNLOCKED BOOTLOADER WARNING MESSAGE WHILE BOOTING (THIS CAN BE IGNORED OF COURSE)
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
PART 4: INSTALLING TWRP AND ROOTING USING LAFSPLOIT
BEFORE PROCEEDING ENSURE YOU BOOT YOUR PHONE AND DONE ALL THE BASIC SETTINGS
NOW HEAD TO THE DEVELOPER OPTIONS IN YOUR DEVICE AND ENSURE OEM UNLOCKING AND USB DEBUGGING ARE SWITCHED ON.
NOW CONNECT YOUR DEVICE TO THE PC (RUNNING LINUX OS FROM PENDRIVE) IN DOWNLOAD MODE (SWITCH OFF YOUR MOBILE AND CONNECT THE USB FROM PC WHILE HOLDING THE VOLUME UP BUTTON SIMULTANEOUSLY)
DOUBLE CLICK ON THE LG FOLDER INSIDE FWUL DESKTOP
INSIDE THAT, DOUBLE CLICK ON LGLAF(RUNNINGNAK3D) ICON WHICH WILL OPEN A TERMINAL
ENTER THE BELOW COMMANDS
git pull
git checkout h918-miscwrte
./step1.sh
THE ABOVE COMMAND FLASHES TWRP RECOVERY ONTO YOUR DEVICE.
WAIT AND PULL OUT YOUR DEVICE WHEN IT ASKS TO.
RECOMMENDED: NOW THAT TWRP HAS SUCCESSFULLY INSTALLED, YOU CAN MANUALLY FORMAT,FLASH LATEST TWRP RECOVERY AND USE ANY METHOD LIKE MAGISK OR SU FOR ROOTING.
INSIDE TWRP RECOVERY. FIRST FORMAT USING WIPE--ADVANCED FORMAT--TYPE yes AND FULL DO A FULL FORMAT, THEN FLASH MAGISK AND THE LATEST TWRP RECOVERY BELOW.
MAGISK ZIP DOWNLOAD:
https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
LATEST TWRP BY PHOENIX(H918):
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
OR
IF YOU ARE UNSURE ABOUT FORMATTING AND FLASHING, JUST USE THE BELOW COMMAND TO DO ALL THE WORK AUTOMATICALLY
CONNECT YOUR DEVICE AGAIN IN DOWNLOAD MODE AND ENTER THE FOLLOWING COMMAND
./step2.sh
THE ABOVE COMMAND FORMATS YOUR DEVICE AND FLASHES MAGISK TO ACQUIRE ROOT.
TIP : IF YOU FACE ANY ENCRYPTION ERROR AFTER USING STEP2. SH, DO A ADVANCED FORMAT WITHIN TWRP AND FLASH MAGISK AND LATEST TWRP BY PHOENIX MANUALLY.
YOU ARE NOW ROOTED WITH TWRP RECOVERY INSTALLED.
REMEMBER TO BACK UP THE CURRENT ROM BEFORE FLASHING ANYTHING..... DO CHECK POST #2 FOR OTHER TWEAKS
IF YOU WISH TO UPDATE TO LATEST STOCK (10U) AND KEEP ROOT AND TWRP, JUST FOLLOW THIS LINK AND DO REMEMBER TO ROOT USING MAGISK AFTER FLASHING THE ROM BEFORE YOU BOOT.
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
I WOULD LIKE TO THANK ALL THE DEVOLEPERS WHO HAVE CREATED THE ABOVE SOFTWARES WITHOUT WHICH THIS ISNT POSSIBLE.
CREDITS:
@autoprime FOR HIS UPPERCUT TOOL
@steadfasterX FOR HIS FWUL TOOL
@Phoenix591 FOR HIS WORKS ON TWRP RECOVERY
AND FINALLY, @runningnak3d FOR HIS EXCELLENT WORK IN ROOTING OUR DEVICE :good:
WHAT NEXT?
NOW THAT YOU HAVE ROOTED YOUR MOBILE, I WOULD RECOMMEND DOING THE BELOW TWEAKS FOR FURTHER ENHANCED EXPERIENCE....
1.THERMAL THROTTLING
IF YOUR ARE STILL ON A STOCK BASED ROM , I WOULD STRONGLY RECOMMEND TO RECONFIGURE YOUR THERMAL FILE TO PREVENT ANY POSSIBLE LAG WHEN USING EXTENSIVELY...
FIRST DOWNLOAD THE FILE BELOW:
https://drive.google.com/file/d/0B0W3xXHgfOxvLUpKNWhrWDE0TDg/view
USE A ROOT EXPLORER (PREFERABLY ES EXPLORER) AND GO TO ROOT/SYSTEM/ETC.
YOU SHOULD HAVE A FILE NAMED thermal-engine-8996.conf
RENAME IT TO thermal-engine-8996.conf.bak (JUST FOR A BACKUP IF ANYTHING GOES WRONG)
ENSURE THE ABOVE DOWNLOADED FILE IS IN .conf FORMAT
IF IT ISN'T , RENAME TO thermal-engine-8996.conf
NOW SAVE THE FILE TO THE SAME DIRECTORY VIZ ROOT/SYSTEM/ETC
GIVE PERMISSION TO THIS FILE TO rw-r--r-- USING THE ROOT EXPLORER ( SELECT FILE--->PERMISSION--->READ WRITE, READ, READ)
FINALLY SAVE AND REBOOT.
THIS WOULD OVERWRITE THE THERMAL LINKED PERFORMANCE OF THE CPU TO AVOID ANY LAG WHEN USING EXTENSIVELY.
2. RCTD REMOVER
ALSO I WOULD STRONGLY RECOMMEND TO REMOVE THE LG'S RCTD CCMD AND TRITON MONITORS AS THESE WOULD RUN CONTINUOUSLY IN A ROOTED LG PHONE AND CONSUME LOT OF RESOURCES...
JUST INSTALL THE RCTD REMOVER APP FROM BELOW LINK:
https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
GRANT SU PERMISSION AND CHECK THE DESIRED FILES (I CHOSE ALL THREE FILES) AND CLICK ON PATCH, FLASH IMAGE AND REBOOT (THIS WOULD PATCH THE BOOT FILE, SO AGAIN IT IS ADVISABLE TO CREATE A BACKUP OF THE CURRENT BOOT IMAGE USING TWRP OR WITHIN THIS APP ITSELF)
3. SCREEN CALIBRATION:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
INSTALL KERNAL AUDITOR APP FROM PLAY STORE AND GRANT SU ACCESS
CHANGE THE BELOW VALUES WITHIN THIS APP (SCREEN SETTINGS)
Minimum RGB value = 35
Saturation Intensity = 27
Screen Hue = 1520
Screen Value = 112
Screen Contrast = 132
THIS WOULD SOMEWHAT REDUCE THE BLUE TINGE AND GHOST APPEARANCES OF THE SCREEN
CREDITS: @Holyman007 for his thermal tweak @Zacharee1 for his rctd remover app
I was just about to create a post asking for a step by step for dummies so thank you very much for this! Going to do this sometime tomorrow or Tuesday and will update if I succeed or not. :good:
Got a question. Does this method stop the second screen from working?
turdbait said:
I was just about to create a post asking for a step by step for dummies so thank you very much for this! Going to do this sometime tomorrow or Tuesday and will update if I succeed or not. :good:
Got a question. Does this method stop the second screen from working?
Click to expand...
Click to collapse
this would end up with a stock rooted phone with twrp recovery if all the methods are correctly followed..
......final result would be.... you would end up with a rooted stock rom with a twrp recovery....
your second screen will work perfectly.....
please let me know if you need a different thread for installing custom rom, and to reduce the lag., install sound mod to get maximum sound output and customize second screen... i will create a noob friendly thread for these as well......
Also check the original lafsploit thread @
https://forum.xda-developers.com/v20/how-to/root-lafsploit-h918-version-t3773443
kish9046 said:
Also check the original lafsploit thread @
https://forum.xda-developers.com/v20/how-to/root-lafsploit-h918-version-t3773443
Click to expand...
Click to collapse
Thank you, I've been reading up on the main lafsploit thread for awhile but I was still not sure about the whole flashing KDZ file and stuff so when you posted this thread it was a motivator to try it out. Got a day off from work tomorrow so gonna try it then so I don't got to worry about the time.
I'm interested in the max sound output and second screen customization if you got the time and its not to much to ask. If you want to wait till either someone else comes along thats interested or till I root just so you don't waste your time I shall update hopefully sometime tomorrow. Thanks again.
kish9046 said:
sha256sum h918-twrp.img ----> THIS WOULD AGAIN THROW A HASH, CHECK IF BOTH THE HASHES ARE ABSOLUTELY SIMILAR
Click to expand...
Click to collapse
Excellent. Just a friendly suggestion, however. I would change the instruction above to use the word EXACT instead of SIMILAR, otherwise people may continue erroneously. The hash numbers must be exact.
onlineaces said:
Excellent. Just a friendly suggestion, however. I would change the instruction above to use the word EXACT instead of SIMILAR, otherwise people may continue erroneously. The hash numbers must be exact.
Click to expand...
Click to collapse
Thanks for the heads up.... Changed to EXACT...
I successfully have root now, thank you! If you're still interested in doing a guide on how to do the second screen customization I'd be grateful.
turdbait said:
I successfully have root now, thank you! If you're still interested in doing a guide on how to do the second screen customization I'd be grateful.
Click to expand...
Click to collapse
great to hear that u have root now.... will post soon on other mods including a step-by-step process on removing rct soon....
All this stuff can be found already in the forums so you posting guides is redundant js
Sent from my LG-H910 using XDA Labs
cnjax said:
All this stuff can be found already in the forums so you posting guides is redundant js
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Thanks for the suggestion... but i thought this would help noobs like me to explore more about our device without doing any harm to it.....
Glad someone actually laid it out step by step.
kish9046 said:
Thanks for the suggestion... but i thought this would help noobs like me to explore more about our device without doing any harm to it.....
Click to expand...
Click to collapse
so i just wanted to say thank for for the very noobie step by step guide. im soooo use to odion and adb flash commands.
just 1 thing i had trouble with was trying to push magisk and twrp over. I rooted by pushing magisk over with otg but no twrp on recovery. then i saw it said it was on download mode. from dl mode i just flashed twrp to recovery.
BROKEN1981 said:
so i just wanted to say thank for for the very noobie step by step guide. im soooo use to odion and adb flash commands.
just 1 thing i had trouble with was trying to push magisk and twrp over. I rooted by pushing magisk over with otg but no twrp on recovery. then i saw it said it was on download mode. from dl mode i just flashed twrp to recovery.
Click to expand...
Click to collapse
So i assume you have both TWRP and root now?..... And can i ask which version r u in now....ARB0 or 1
kish9046 said:
So i assume you have both TWRP and root now?..... And can i ask which version r u in now....ARB0 or 1
Click to expand...
Click to collapse
Abr1 yes I am rooted with twrp.
As I said, the commands to push magisk and twrp to sd did not work. I used usb otg in twrp to push magisk, but forgot to put twrp to flash as well.
I forgot that twrp had replaced download mode, so I was going a bit nuts trying to figure out how to get twrp to recovery. Lolol
Now I'm on latest update with rtcd removed thanks to the op who hosted it on xda as a flashable zip.
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
As you are in twrp, you can manually flash magisk zip and twrp recovery.....
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
Download magisk and twrp here https://androidfilehost.com/?fid=746010030569963731
While you are in the last step, in mount, select otg USB. You can push it to SD card and manual flash.
If you booted to system without magisk and flashing twrp, power off the phone, hold volume up, put in the USB, connect to PC. This will put you in twrp since download mode is replaced by twrp.
Now you can flash both files.
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
Download magisk and twrp here https://androidfilehost.com/?fid=746010030569963731
While you are in the last step, in mount, select otg USB. You can push it to SD card and manual flash.
If you booted to system without magisk and flashing twrp, power off the phone, hold volume up, put in the USB, connect to PC. This will put you in twrp since download mode is replaced by twrp.
Now you can flash both files.
Below you will find a download for my modification of a ported Team Hovatek TWRP file as their TWRP did not support OTG. Thanks to Team Hovatek for making a nice porting tool. Unfortunately it took some days and late nights of work to get the ported TWRP to actually be useful as this phone needs OTG support to use TWRP.
When I recently got the Unihertz Atom I didn't realize that it had no micro SD card slot for an external SD card like the Unihertz Jelly Pro had. However it does have OTG support unlike the Jelly Pro but I could not find any TWRP versions for the Atom. So I found a TWRP porting tool from Hovatek and I was able to create a TWRP version but USELESS unfortunately as that version of TWRP did not have OTG support for the Atom.
To make matters worse that TWRP can't deal with the encrypted internal storage of the Atom so there was no way to do a backup of your system. It was possible to format data in TWRP and do a backup to it but upon reboot all that data was gone and reset by the Atom as an essentially new phone being setup for the first time.
I needed a way to modify the ported TWRP so it would recognize an OTG flash drive or USB flash with an OTG cable. I used Image Kitchen to disassemble the original Atom Recovery image and also the modded TWRP recovery image so I could find what was missing from TWRP that was there in the original setup. After a whole lot of reassembling and reflashing various attempts to fix the OTG problem I finally got it. Had to add different lines of code to 3 different files within the unpacked TWRP recovery for it to finally recognize an OTG attached flash drive.
A couple notes on using your external flash drive with TWRP. First you want to insert the flash drive with an appropriate USB type C OTG adapter or cable. Or I see Sandisk (and possibly other brands) are now making a flash drive with USB and Type C dual setup for OTG use.
Bootup your regular phones Android system and look in the pull down notifications - it will ask if you want to use the flash drive as storage. Answer yes and it will then Format it to FAT32 0x0C type which is different than what it was fresh out of the package as most will be FAT32 0x0B type. Once formatted the way the Atom wants it you can use it. However if you put the drive back in your Windows computer it may not see the drive at all. The solution is to open Windows Disk Management and Assign it a drive letter. Once that is done you can read and write to it from both Android and Windows or Linux.
Once that is done you can turn off your phone (IMPORTANT). Do not use any apps that reboot into recovery after installing this TWRP or you will likely just get a black screen and it won't boot up until you reflash the preloader, boot and recovery.
To get into recovery hold down the Volume UP button and the Power button at the same time until you see Unihertz then release both. This is of course after you have flashed TWRP. More on that below. Once your are in TWRP you may have to remove your Flash drive if you had it plugged in during recovery boot up - then reinsert it for TWRP to see it. You can then see it when you mount storage or select storage and it should show the size of your flash drive.
You can then backup your Boot, Recovery, EMMC, System and cache. However the data on the Atom seems to be encrypted in a way that this TWRP does not see it so it will be best to use something like Titanium backup for your Apps and their data. The TWRP though will ensure a complete backup of your system and it's settings as well as the other items mentioned above. I am still looking into why it can't see the encrypted data part of the phone but for now it's nice to have an image of all the rest of the phone. If anyone can help with that I would appreciate it. So far I've tried several 'no encrypt scripts' and ones to turn off DM verity I found on XDA but none of them worked on this phone.
Here is the download of my modded TWRP and also a link for the SHA-256 of it:
TWRP mod: TWRP mod by droidzer1
SHA-256 for file above: SHA-256 for TWRP mod Love the Atom - fast Octacore 4GB Ram - 64GB Internal storage, rugged and tiny as an underfed mouse. :silly: Enjoy !
Notes on Installing this TWRP on your Atom
There are two ways I have used to install this TWRP onto the Atom. One way (and the best way IMO) is to use the SP Flash tool version 5.1828. The other is to use Fastboot. I believe for both methods you need to enable developer options on your phone and turn on OEM unlocking. But if you use Fastboot you also have run the line: "fastboot oem unlock" to install TWRP and that will wipe your phone to a new reset condition plus you will see the 5 second "Orange State" pause screen every time you turn on the phone. To eliminate the "Orange State you can run : "fastboot oem lock" but that will once again totally reset your phone wiping everything including apps and settings. So I prefer using SP Flash tool to avoid all that.
When installing with SP Flash tool I always flash the preloader, boot and recovery (the TWRP modded one) and of course the scatter file. It seems if you don't flash all of those it sometimes doesn't want to boot up.
Also this mod is for the official Unihertz 11-30-2018 ROM version which is the latest update I've seen as of a week ago. I don't know if it will work for other versions. You will want to download that ROM to get the scatter file that is needed by SP Flash tool and it's always good to have an original ROM just in case. Link for the new 11-30-2018 Atom ROM here: 11-30-2018 Atom ROM If you are not on that version you could backup your apps and data with Titanium backup and then install the new ROM while flashing my modded TWRP all at the same time. Just make sure the TWRP you download is named "recovery-verified.img" when you replace the stock one in the SP Flash tool list on the Download page. Also make sure on the tools 'Connections' setting that you check 'Battery installed'.
IMPORTANT!!! - Every version of SP Flash tool I've used shows up as having a virus or trojan and although it may probably be a False positive to be safe I always run Shadow Defender before starting the SP Flash tool. There may be other similar programs but I found this to be one of the best as it totally freezes your computer and hard drive(s) so nothing can be changed or written permanently to them while in Shadow mode. Once you reboot everything is back to a normal state and any changes that may have been made are gone. SP Flash tool available here: SP Flash tool v5.1828 I strongly suggest you use this latest version as previous ones had some issues in completing this project.
A couple quick notes on using the SP Flash tool: It is best to start the tool, have all your items in the check boxes loaded (select scatter file location first) check and locate preloader, boot and recovery - the preloader and boot are from the original ROM you downloaded from the above link. Unzip it and you'll see the needed files inside along with the scatter file.
Once that is ready turn OFF your phone and hook it up with the original USB-C cable to your computer. Wait for it to show the battery charging screen and wait till all that disappears and you have nothing but the black screen. (Or per user SepticFuddy you can hold the Volume Up key while inserting the USB cable and it will connect quickly - I have not tested it this way). Then click on the Flash tool download button. After that you need to push the Atom Power button once briefly - not long enough to turn it on - just a brief click. After that you should see the Flash process going on - it only takes a few seconds to load the preloader, boot and recovery and then you will see a "done" with a big check mark. Remove your phone then and boot into your regular Android OS or use Volume Up and the Power key to boot into your TWRP. :highfive:
Why TWRP doesn't work with Encryption - from TeamWin
I guess this may explain why it is unlikely to get TWRP to work with the encrypted data partition - straight from Teamwin's TWRP website:
"Why doesn't TWRP support encryption on my device?
TWRP encryption is supported in 2 phases. The first item is keeping up with the newest support from AOSP, which can require lot of changes and integration with the new AOSP release. This can take time especially if we have to wait for reference devices to test with. The second item is custom blob support and integration with device OEM firmware.
Even if your device supports AOSP encryption and decryption, it usually requires custom blob support. The process of figuring this out may take time and may never be done. Some vendors such as Samsung use their own encryption techniques. Without heavy deconstruction/decompiling of custom library blobs, and successful ports by an active maintainer, this may never be done. Encryption support is a nice thing to have in TWRP, and not a must have support option. We feel that the ability to backup system and install custom firmware can outweigh having no TWRP support at all."
From: TWRP Website FAQ on Encryption
How I fixed TWRP
For anyone who wants to try the mods their self if you don't trust using the recovery I uploaded I believe these are the changes I made to the ported TWRP. You need of course the porting tool from Hovatek and after you have ported your original recovery you will want to use Image Kitchen to make these mods to the ported image:
Use Image Kitchen to unpack the ported TWRP recovery. In the Ramdisk folder this line "ro.agui.otg_usbdisk=yes" orginally found in the prop.default of the original recovery needs to be put into the file "default.prop" which is a different file name than the original but I am sure is the same purpose and was referenced in the original by a small file with that name.
Then this line "/dev/mt_otg_test(/.*)? ubject_r:mt_otg_test_device0" from the original recovery image in the file "nonplat_file_contexts" I believe I copied into the file "file_contexts" in the TWRP image in the Ramdisk folder.
Note - the above code line that has a smiley in it is because there is the letter "o" followed by a colon. Replace the smiley with "o" and : no spaces between it and the letter 'u' before it or between 'o' and :
I think the third file I modified was found in the unpacked folder /ramdisk/etc in the file 'recovery.fstab' and I took this line "/devices/platform/mt_usb* auto vfat defaults voldmanaged=usbotg:auto " from it to add to the same file in the ported TWRP. Then just repack everything in Image Kitchen and you should have a TWRP recovery that works with OTG.
If you aren't familiar with how to use Image Kitchen it would be best to google how to use it. I have left out some of the basics such as needing to Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the unpacked stock recovery and overwrite those two files in ported TWRP folder. Best to look for an instruction article on techora.net about porting TWRP on mediatek devices.
Thank you, it's awesome! But how did you manage to flash Magisk? I can't flash it as /data and /storage can't be mounted.
You should be able to flash it with Fastboot by using command:
fastboot flash boot /path/to/patched_boot.img OR simply put it in the fastboot folder and type:
fastboot flash boot boot.img (the patched boot image)
You may want to review info on the Magisk thread here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This method of course is done with you computer and USB cable attached to the Atom. Make sure you have correct drivers for it to fully recognize your phone.
A bit more info from topjohnwu's Magisk thread mentioned above:
Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/Download/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
If the above method fails for some reason you should also be able to flash to patched boot image with SP flash tools as long as you have the scatter file for the ROM you have installed on your phone. As I mentioned if you flash the patched boot image that way I found it best to also flash the preloader and recovery at the same time.
Cannot mount /data
What you did here was remarkable. I love the Atom so I never tried to tinker with recovery since I might end up with a bootloop. I hope we find a solution soon on how to mount /data.
post-root network failure
First off thank you for doing the research and posting in the thread to help us root this awesome little device.
I followed your steps to the "T" and I was able to successfully patch magisk and re-download it back onto my atom and it was rooted BUT, there seems to be some sort of network issue that I'm stuck on, I'm unable to turn on the wi-fi and bluetooth and every few seconds I keep getting an error message that says "bluetooth keeps stopping" consistently whenever I have the phone on.
I was wondering If you had any idea on what might be causing this, or if you had this problem.
thank you, and I look forward to hearing back from you
droidzer1, Finally got to post now and wanted to thank you for your work on the Atom. I got it rooted and got TWRP working too with only some frustrations because I got in a hurry and missed a detail the first try. I haven't found any problems and have had it running about 2 weeks now with root and TWRP. Nice to have root and of course great to be able to do a whole system backup now!
---------- Post added at 03:08 AM ---------- Previous post was at 03:02 AM ----------
hayestak said:
First off thank you for doing the research and posting in the thread to help us root this awesome little device.
I followed your steps to the "T" and I was able to successfully patch magisk and re-download it back onto my atom and it was rooted BUT, there seems to be some sort of network issue that I'm stuck on, I'm unable to turn on the wi-fi and bluetooth and every few seconds I keep getting an error message that says "bluetooth keeps stopping" consistently whenever I have the phone on.
I was wondering If you had any idea on what might be causing this, or if you had this problem.
thank you, and I look forward to hearing back from you
Click to expand...
Click to collapse
Were you able to get this fixed? Doesn't look like droizer1 has been on here recently. Mine didn't have either of those issues. Have you tried doing a factory reset and doing the whole process over? I think sometimes just a computer PC might glitch something on your phone so doing it over might skip the hiccup.
---------- Post added at 03:48 AM ---------- Previous post was at 03:08 AM ----------
Since droidzer1 first posted this in early January you might try using the version of Magisk that was available at that time as I think by later March when you posted there was a newer version out and I've found some versions of Magisk to not work a hundred percent and had to use an older version on some phones.
The latest Magisk (19100) + Xposed (v90 beta 3) work fine for me using the TWRP posted above, in case people were wondering about it.
R
Lost in reboot ...
Hi
I urgently need some help. I seem to be lost...
I have successfully installed TWRP on my Unihertz atom. And I can manage to go into either TWRP mode or into fastboot mode.
I can also successfully unlock the Unihertz atom with:
fastboot oem unlock-go
But what is next?
If I reboot, my phone constantly reboots. It cycles into reboot without Android coming up.
(perhaps I made something wrong).
What I actually want is: The phone should boot including Magisk.
Can anyone please help me what commands I have to issue (with the phone connected to my linux computer via USB) in order
to recover to a normal reboot? Which image-file should I use (please provide URL)?
Can anyone please help me what commands I have to issue to flash Magisk?
Which image-files I should use (please provide URL)?
If somebody has a custom rom or lineageOS rom I would be even happier ...
Thanks a lot.
Thank you
Confirmed working with the Android 9 Pie 2019082617 ROM, latest Magisk 19.3 (19300), latest Riru core v19.5, latest Riru- EdXposed v0.4.5.1b (4463) (SandHook). EdXposed seems hit or miss after a reboot though, getting it to stick may take a few installations.
To get SP Flashtool to work, I had to hold the Volume Up key while inserting the USB cable and it would instantly connect, rather than following the OP's instructions of just inserting the cable and waiting for a black screen.
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.
SepticFuddy said:
Confirmed working with the Android 9 Pie 2019082617 ROM, latest Magisk 19.3 (19300), latest Riru core v19.5, latest Riru- EdXposed v0.4.5.1b (4463) (SandHook). EdXposed seems hit or miss after a reboot though, getting it to stick may take a few installations.
To get SP Flashtool to work, I had to hold the Volume Up key while inserting the USB cable and it would instantly connect, rather than following the OP's instructions of just inserting the cable and waiting for a black screen.
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.
Click to expand...
Click to collapse
Thanks for the mention of a quicker method. I've updated my post to include your info.
LineageOS for Uniherz Atom?
SepticFuddy said:
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.
Click to expand...
Click to collapse
Me too!! LineageOS for the Unihertz Atom would be great!
The hadrware of the Uniherz Atom is just great, is is small and it is dual-sim. This is unique in the market.
I would be even willing to contribute with 100,- EUR if somebody delivers a working LineageOS ROM.
Any body interested? :highfive:
SepticFuddy said:
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.
Click to expand...
Click to collapse
The main problem is that unihertz never released their source code (despite being obliged to do so according to the android licensing contract).
There are some bits in the official mediatek kernel source tree (https://android.googlesource.com/kernel/mediatek/) but I doubt that this would be enough to build something stable out of it.
@droidzer1 Hey there, what is the difference between your modded TWRP and this test release by the TWRP Builder Project asside from the TWRP version?
J-Kos said:
@droidzer1 Hey there, what is the difference between your modded TWRP and this test release by the TWRP Builder Project asside from the TWRP version?
Click to expand...
Click to collapse
I'm not sure what the difference is except I came out with mine in January and theirs came out in March. Theirs is about 4 Megabytes bigger - maybe a newer version (mine is 3.2.1-0). I contacted 'bigbiff' at TWRP about mine when I had it working but they were not interested unless I had a device tree which I didn't so they didn't want to post it on their site.
Great, thanks for your reply. I am satisfied with you version, so I will just keep using it.
Windows 10 64bit vs RSD Lite 6.2.4
I was unable to get my Moto G7 Power ocean xt1955-5 recognized by RSD
Lite 6.2.4 and was wondering if there is a line I can edit in an .inf file (or a
registry edit) which will let it recognize my phone? In devices, it shows up
as Android Device/Motorola ADB Interface
I've tried not using the Motorola_End_User_Driver_Installation_6.4.0_64bit,
but this gets the phone recognized by the OS, Fastboot (when in
bootloader/fastboot mode), and ADB (when running regularly but in
developer mode with USB debugging on). Without the driver package,
I've been unable to get the phone recognized as a Fastboot device using
MotorolaDeviceManager_2.5.4 and
rescue_and_smart_assistant_v5.4.0.18_signed_setup
but using the Motorola_End_User_Driver_Installation_6.4.0_64bit gets
both fastboot and ADB working. (Just RSD Lite can't see it)
I've tried mainly my single USB 2.0 port, but my USP 3.0 ports seem to
work just as well for ADB and Fastboot... just not for RDS Lite.
Usually I have a device under android called either Ocean S or
Android (Motorola?) ADB Device. In ADB and Fastboot ive seen
the devices serial number in response to devices and I believe
I saw Ocean S as a response also with the same driver loaded.
(Motorola v2.0.2.0 from 7/7/2013) no other driver seems to
have affinity to my phone.
I'm trying to get setup to flash something other than factory, having
experienced limitations in the original load and the first update which
I find daunting.
I find RSD Lite highly recommended, but am ready to do without it as
long as I understand that RSD Lite is unneeded to unbrick, etc.
I've flashed a few Samsung phones many years ago, and am hoping
to use the preferred tools for my foray into Moto (/ Lenovo?) territory.
Ideas of where to hang out and read posts will help... I've been a few
places (on XDA and a couple other forums) but have only read a
couple hundred posts.
Erbid
Success w/o need for RSD Lite (though it could be handy!)
I resolved that with ADB and Fastboot (and acces to the experts here on XDA) I could recover from almost anything.
I booted TWRP using Fastboot without installing it (from the official site for my current version (9.0)).
it worked well.
Using info from the Installation Instructions at download.lineageos.org/oceanwent and downloaded copy-partitions-20200903_1329.zip LineageOS and LineageOS recovery (nightly from 2.6.2021) and installed them using Fastboot commands per the Ocean Installation Instructions linked at the top of lineage for Ocean download page.
I also flashed a lite version of OpenGAPPS from opengapps.org/?api=10.0&variant=micro on and it is working well after a prolonged initialization (and a reboot).
That all done I was happy until I learned "root" was no longer part of LineageOS!!!
So I learned about Magisk from their site, installed the manager, installed Migisk by downloading the zip file... tried to install it from "LineageOS recovery" but could see only and empty downloads directory on my SD card. I rebooted and copied the Magisk zip file to my SD card \downloads directory, rebooted to Lineage recovery and installed it from there.
Things seem to be working as desired so far. Will experiment with a sim card soon but WiFi is working well.
So far... 100% (Titanium backup and Torque both seem happy along with my email client of choice and much more)
Erbid