Related
Hi guys This is my first post in xda developer
Lets start rooting sm-a700h(galaxy a7)
REQUIRMENTS
1-BRAIN 2-INTERNET 3-ANDROID PHONE
STEPS
1-download latest vesion of kingroot from kingxteam @xda developers
2-root it With king root
3-download titanium backup from google play
4-go inside titanium/backup and restore
5- find SecurityLogAgent wipe data and freeze it (if you uninstall it you cant install apk packages)
6-download terminal Emulator and install it
7-extract zip file into your Device storage
8-go inside terminal Emulator
9-type su then app will require root permission allow it
9-type sh /sdcard/mrw/root.sh
10-after installation is finished - supersu will open automatically if not open it manually
11-update supersu binaries and reboot
credits
kingxteam
chainfire
me...
RULES
I have no responsibility for bricked devices and etc... i will just laugh at you
this method can work on other devices like galaxy a5 a3 a8 and...
PLZ THX MY POSTS
GOODBYE & PEACE
zip file link:mediafire.com/download/mxzbt42xypvn2ts
just copy address and paste and go
then download
[TAB][AMIR] said:
Hi guys This is my first post in xda developer
Lets start rooting sm-a700h(galaxy a7)
REQUIRMENTS
1-BRAIN 2-INTERNET 3-ANDROID PHONE
STEPS
1-download latest vesion of kingroot from kingxteam @xda developers
2-root it With king root
3-download titanium backup from google play
4-go inside titanium/backup and restore
5- find SecurityLogAgent wipe data and freeze it (if you uninstall it you cant install apk packages)
6-download terminal Emulator and install it
7-extract zip file into your Device storage
8-go inside terminal Emulator
9-type su then app will require root permission allow it
9-type sh /sdcard/mrw/root.sh
10-after installation is finished - supersu will open automatically if not open it manually
11-update supersu binaries and reboot
credits
kingxteam
chainfire
me...
RULES
I have no responsibility for bricked devices and etc... i will just laugh at you
this method can work on other devices like galaxy a5 a3 a8 and...
PLZ THX MY POSTS
GOODBYE & PEACE
zip file link:mediafire.com/download/mxzbt42xypvn2ts
just copy address and paste and go
then download
Click to expand...
Click to collapse
I can`t do step 9 it says no such file or directory. any help?
ghadeer221 said:
I can`t do step 9 it says no such file or directory. any help?
Click to expand...
Click to collapse
try this one it comes with supersu: http://forum.xda-developers.com/general/help/root-guide-sm-a700h-5-0-2-t3350540
I was success with old this rom : A700HXXU1BOI4.
but now i just update to new rom : A700HXXU1BOL3. And after step11 my phone bootloop. i must reflash by odin (factory reset doesnt wrok). i was try 3more times and same result bootloop.
Can u help me replace kinguser ?
NOTE:I AM NOT RESPONSIBLE FOR YOUR DEVICE
Proper root steps for cwm recovery
1. download kingoroot root with apk and restart
2. Download Replace_Kinguser_with_SuperSU.zip from https://forum.xda-developers.com/attachment.php?attachmentid=3926817&d=1478337705
3. Download prefered unzipping app and unzip to root of internel sd card
4.Download Terminal emulator from playstore
5. In terminal emulator run
HTML:
su
Then
HTML:
sh /sdcard/mrw/root.sh
6.wait for it to launch supersu then update using the normal option and reboot
To install cwm recovery simply follow this guide http://https://forum.xda-developers.com/showthread.php?t=2519432
P.s stay tuned to xda as i am working on a deodexed debloated stock rom for this device and possibly a cynogenmod port
Blu studio x8 hd ROM
Thank you... I've been staying tuned for the longest while now hopefully you didn't forget ;(
More detail please
Can you provide more detail for Step 1? I downloaded and installed the apk and then rebooted. When I get to Step 5, I get "su is not found" from the terminal.
Heterod0x said:
NOTE:I AM NOT RESPONSIBLE FOR YOUR DEVICE
Proper root steps for cwm recovery
1. download kingoroot root with apk and restart
2. Download Replace_Kinguser_with_SuperSU.zip from https://forum.xda-developers.com/attachment.php?attachmentid=3926817&d=1478337705
3. Download prefered unzipping app and unzip to root of internel sd card
4.Download Terminal emulator from playstore
5. In terminal emulator run
HTML:
su
Then
HTML:
sh /sdcard/mrw/root.sh
6.wait for it to launch supersu then update using the normal option and reboot
To install cwm recovery simply follow this guide http://https://forum.xda-developers.com/showthread.php?t=2519432
P.s stay tuned to xda as i am working on a deodexed debloated stock rom for this device and possibly a cynogenmod port
Click to expand...
Click to collapse
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
zbask said:
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
Click to expand...
Click to collapse
Hi, Congratulations for the help and thanks
After doing all the procedure I did the verification of the root and
Tells me it's not root.
It's possible?
Michele
mminfor said:
Hi, Congratulations for the help and thanks
After doing all the procedure I did the verification of the root and
Tells me it's not root.
It's possible?
Michele
Click to expand...
Click to collapse
you can check root trough adb
connect the watch and type this:
"adb shell"
"su"
you must have installed busybox on rails on the watch, you can try only booting the recovery with this command "fastboot boot twrp-3.1.1.0.img"
zbask said:
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
Click to expand...
Click to collapse
I can confirm that you are correct that the TWRP does flash correctly and that the normal reboot to recovery works properly and I thank you for that, but the SU does not flash properly I get error 2 which indicates it does not work for the device (through searching) google, I forgot what that error was, I tested through the only app I see on wear that allows root and works, Advanced Settings and anytime I change the processor settings and exit the app, the same standard non-root settings appear again. Indicating that root was un-successful. I will see what I can do for the SU zip, becuase it appears to be related to the updater binary, the updater scirpt is usually more straigt forward, but sometimes harder to figure out. I will try to do what I can in this regard, but power might go out (Harvey) and circumstances might becom unfavorable throught this weekend.
try this supersu
https://drive.google.com/open?id=0Bzk4DPXefDhrUjRLTXpPSkxVT2M
zbask said:
try this supersu
https://drive.google.com/open?id=0Bzk4DPXefDhrUjRLTXpPSkxVT2M
Click to expand...
Click to collapse
I also tried this but nothing to do still gives me "no root"
I will wait for better times.
thank you
MMinfor
Working.
mminfor said:
I also tried this but nothing to do still gives me "no root"
I will wait for better times.
thank you
MMinfor
Click to expand...
Click to collapse
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
physicistman said:
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
Click to expand...
Click to collapse
This solution seems to work.
Here's the check
thanks
zbask said:
Steps
Unlock bootloader
...
Click to expand...
Click to collapse
How exactly do you unlock the bootloader?
madsc13n41s4 said:
How exactly do you unlock the bootloader?
Click to expand...
Click to collapse
1.Unlock the bootloader if not already unlocked
(Make sure to set up device with phone after unlocking bootloader otherwise no boot!)
Code:
- adb reboot bootloader
- fastboot oem unlock
enjoy!
Is there any way we can pass SafetyNet for Android Pay using SuperSU?
???
Will this work with watch sport as well?
Can we then maybe fix APN settings after its rooted?
Grumps said:
Will this work with watch sport as well?
Can we then maybe fix APN settings after its rooted?
Click to expand...
Click to collapse
APN settings cannot be changed on AW2.0 because SquashFS is read-only. Howerver, if you edit APN settings manually in AW1.5 (using xml file edit from adb root shell, see this forum for tutorial), they remain & work after OTA update to AW2.0. They will be lost, however, if you disconnect your watch from the phone "the official way" (with hard reset). In order to always use APN settings, use this tutorial on how to pair AW watch to new phone without factory reset.
Drakosha said:
APN settings cannot be changed on AW2.0 because SquashFS is read-only. Howerver, if you edit APN settings manually in AW1.5 (using xml file edit from adb root shell, see this forum for tutorial), they remain & work after OTA update to AW2.0. They will be lost, however, if you disconnect your watch from the phone "the official way" (with hard reset). In order to always use APN settings, use this tutorial on how to pair AW watch to new phone without factory reset.
Click to expand...
Click to collapse
Isnt APN settings configured after you install a sim card from the provider? Surely it must then be stored somewhere else?
Did anyone succeed ?
what is about squashfs? is there anyway, to make /system/ writeable?
sebj84 said:
what is about squashfs? is there anyway, to make /system/ writeable?
Click to expand...
Click to collapse
Ok,
sorry wasn't on aw before. so sorry for my last question.
Anyhow. Did somebody managed to get XPosed running?
I've tried, but got an error of not enough place on /system. When i try to delete system apps, i get the same error.
Now using supersu.
before with magisk, got xposed and a few other packsages installed, but they never show up in magisk later
SQUASHFS is read only by default.
sebj84 said:
Ok,
sorry wasn't on aw before. so sorry for my last question.
Anyhow. Did somebody managed to get XPosed running?
I've tried, but got an error of not enough place on /system. When i try to delete system apps, i get the same error.
Now using supersu.
before with magisk, got xposed and a few other packsages installed, but they never show up in magisk later
Click to expand...
Click to collapse
You won't be able to do anything within the /system/ partition while it is mounted. I can't answer the question as to why specifically, because I am not as knowledgeable of it, but here is the wiki SQUASHFS info. and another one that gives more information as to the uses SQUASHFS HOWTO.. If I am correct in order to make any changes to the system one would have to have a backup or original system image unsquash the image make any changes from that then re-squash the image and flash it in custom recovery. I have already unsquashed the image of the original image from the newest update myself and have it on my laptop, but I have not been able to go much further (busy). There are workarounds to the system not being able to write, but those are mostly for other versions of the filesystem and on different devices along with it not being totally writable.
Ok. I see now.
Thanks for the link. I will check those infos first.
physicistman said:
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
Click to expand...
Click to collapse
I changed my phone and I have on LG Urban 2 started the Wear Recovery procedure.
after restart, it will start only on TWRP. what can I do??
Thanks in advance
mminfor
{ ROOT } Twrp & Magisk Installation in Official Oreo { (N2G47H.7.12.29 (Android O) }
Needed Files :
1. Fastboot Rom
Http://bigota.d.miui.com/7.12.29/tissot_images_7.12.29_20171228.0000.00_8.0_c9a6ea979b.tgz
2. Platform tools
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
3.Twrp recovery
https://androidfilehost.com/?fid=962157660013069602
4.. Twrp Installer
http://www.mediafire.com/file/338o7cl72z52rzz/twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
5. Magisk 15.2
http://www.stechguide.com/download-magisk-v15-2/
Flashing Guide:
Download all the needed files copy magisk zip file in your device.
1. Flash Fastboot rom using Mi flash tool. ( clean install recommended )
2. After flashing, complete setup and other setting.
( Note : Please Skip adding Finger print. if you are added by mistakenly kindly delete your finger print in settings. )
3. Enable oem unlocking & usb debugging in developor options.
4. Extract platform tool in your pc.
5. Paste the downloaded twrp recovery(3) & twrp installer(4) in platform tools folder.
6. Boot your device to fastboot Mode and connect to pc.
7. Open Command Window ( shift + right click ) and enter the following commands
fastboot oem unlock
fastboot boot recovery-3.2.1-1.img
8. Your device will be booting to Twrp. In twrp select Advanced -----> Adb sideload.
9. Type following command in command window
adb sideload twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
10. reboot to recovery.
11. your internal storage is available in twrp now.
12. Flash Magish 15.2 ( strictly use this version )
13. Goto to reboot option in twrp and select your current slot a or b . ( twrp will showing your current slot )
14. reboot system and enjoy.
***** Sorry for my bad english ****
will try soon and will update you.
please let me know if after following this method are we able to install Magisk modules and does it work?
Yes.
Did not work at first. I had installed magisk using patched boot method. Installed twrp using given method. Device was booting into twrp after selecting reboot system. Decided to install magisk again. As I already had magisk installed, tried flashing uninstaller.zip and got an error saying stock boot image was found which means that magisk was uninstalled. Flashed magisk 15.2 and it worked. I was able to boot into system with twrp installed.
Moral : Flashing magisk is a necessary step even if you are already rooted with magisk.
ota updates
after root by this method ..how to install ota updates
navneet1 said:
after root by this method ..how to install ota updates
Click to expand...
Click to collapse
1. Download and flash stock rom (same version that you are currently on) using mi flashtool with save user data option.
2. Your device will be in the same condition (including apps, settings, data etc.) but unrooted.
3. You'll have an ota notification. Install it with normal procedure.
4. Follow the op from step 3.
Apoorv AR said:
Did not work at first. I had installed magisk using patched boot method. Installed twrp using given method. Device was booting into twrp after selecting reboot system. Decided to install magisk again. As I already had magisk installed, tried flashing uninstaller.zip and got an error saying stock boot image was found which means that magisk was uninstalled. Flashed magisk 15.2 and it worked. I was able to boot into system with twrp installed.
Moral : Flashing magisk is a necessary step even if you are already rooted with magisk.
Click to expand...
Click to collapse
Follow the steps with clean flashed rom.
Spk1690 said:
Follow the steps with clean flashed rom.
Click to expand...
Click to collapse
It worked when I flashed Magisk again without loosing any modules or anything.
get block at
adb sideload twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
the first file i downladed got different name and when i put this command they tell me
No such file or directory
@Spk1690 SO this file twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip only for show internal storage?
edit
After enter this command fastboot boot recovery-3.2.1-1.img my device boot into system, not twrp, how to solve?
Does this work on the January Oreo STABLE patch??
KalolParty said:
Does this work on the January Oreo STABLE patch??
Click to expand...
Click to collapse
upp
KalolParty said:
Does this work on the January Oreo STABLE patch??
Click to expand...
Click to collapse
I have tried , it works, but do it on your own risks
root
i have problem. When i try to root phone i get command:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-kitkat sideload method...
adb: pre-kitkat sideload connection failed: no devices/emulators found
what im doing wrong?
Spk1690 said:
6. Boot your device to fastboot Mode and connect to pc.
7. Open Command Window ( shift + right click ) and enter the following commands
fastboot oem unlock
fastboot boot recovery-3.2.1-1.img
8. Your device will be booting to Twrp. In twrp select Advanced -----> Adb sideload.
Click to expand...
Click to collapse
My A1 reboor into system, not into TWRP.
What am I doing wrong?
I've already done all previous steps, and device is unlocked now.
These files are old, a new ones have been released some time ago:
An updated ROM file:
http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
An updated recovery:
https://www.androidfilehost.com/?fid=818070582850498337
Updated TWRP installer:
(check the attachment section)
Updated Magisk 16.0:
(Check the attachment section)
realtebo said:
My A1 reboor into system, not into TWRP.
What am I doing wrong?
I've already done all previous steps, and device is unlocked now.
Click to expand...
Click to collapse
Have you selected the partition you've installed your recovery to?
Because if not, boot the TWRP .img again and switch the partitions.
Reboot afterwards.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
cregen said:
i have problem. When i try to root phone i get command:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-kitkat sideload method...
adb: pre-kitkat sideload connection failed: no devices/emulators found
what im doing wrong?
Click to expand...
Click to collapse
You might want to try this: https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
Check steps 7-10. Read the whole instructions even if they aren't for your ROM. (Skip the copying process and other LOS related stuff.)
I have a problem while flashing twrp on march patch after flashing twrp on both slots android will automatically degrade to February patch ? I'm fed up of trying things please anyone help me
Im new in mi a1, why we need to flash new rom before flash twrp? My rom position on latest update
Hello
i make dump and convert it to recovery rom
it can be flashed by TWRP
this is last official EU version of Le2 x52x rom
this rom have complete translation (without english or chinese untranslated parts) of all EU languages
best way how to flash it if you havent got twrp
0. download rom https://webshare.cz/file/363v61oM3d/x527-5-9-21s-rar
1. extract downloaded package
2. go to bootloader by pressing and hold volume down and power button
3. open command promt and run:
3.1 fastboot oem unlock-go
3.2 fastboot boot twrp.img
4. now you are rebooted to twrp
5. copy rom (X527-5_9_21S.zip) to the phone
6. flash rom
7. wipe data factory reset
8. reboot phone
9. you are in official EU rom with stock recovery
veisen said:
Hello
i make dump and convert it to recovery rom
it can be flashed by TWRP
this is last official EU version of Le2 x52x rom
this rom have complete translation (without english or chinese untranslated parts) of all EU languages
best way how to flash it if you havent got twrp
0. download rom https://webshare.cz/file/363v61oM3d/x527-5-9-21s-rar
1. extract downloaded package
2. go to bootloader by pressing and hold volume down and power button
3. open command promt and run:
3.1 fastboot oem unlock-go
3.2 fastboot boot twrp.img
4. now you are rebooted to twrp
5. copy rom (X527-5_9_21S.zip) to the phone
6. flash rom
7. wipe data factory reset
8. reboot phone
9. you are in official EU rom with stock recovery
Click to expand...
Click to collapse
Can you make the same with the x522? I want to get stock again
nabelar82 said:
Can you make the same with the x522? I want to get stock again
Click to expand...
Click to collapse
yes you can
Thanks! Thats exactly what im looking for! Pefect stock ROM! Easy to install with twrp, working perfect in my x520.
veisen said:
yes you can
Click to expand...
Click to collapse
I mean if you can I don't have the stock backup I deleted by mistake
nabelar82 said:
I mean if you can I don't have the stock backup I deleted by mistake
Click to expand...
Click to collapse
you can flash this rom it is compatible
veisen said:
you can flash this rom it is compatible
Click to expand...
Click to collapse
The ROM is really good but i Tried everything to pass through safetynet but i cant do it.
Can I install regularly via stock update, w/o twrp? What's is date of security patch? Can you put homescreen there?
I'm on 5.9.021s for x526. I have x527.
google Drive
Can you upload it on google Drive and share the link please , cause google drive is faster and easier way to download
Owing all gratitude towards you
svsavic said:
Can I install regularly via stock update, w/o twrp? What's is date of security patch? Can you put homescreen there?
I'm on 5.9.021s for x526. I have x527.
Click to expand...
Click to collapse
You can not update it via stock recovery bcs leeco never release this rom it is installed on europe (Czech branded phones) i cannot post screen bcs im change phone i have Essential ph-1 for now
Can i flash it as a secondary rom (multirom)?
Does anyone have the stock modem for x527? because my signal keeps coming on and off constantly in every eui rom so I can't go back to stock, strangely I can use it on Nougat and Oreo. I've flashed this stock rom but no solution.
Hi @veisen !
Thanks for the ROM.
However - how can it be an official ROM if it shows a 'Le X527' but with a 'Snapdragon 820' (when it should be a Snapdragon 652)?
Cheers, raimerik
raimerik said:
Hi @veisen !
Thanks for the ROM.
However - how can it be an official ROM if it shows a 'Le X527' but with a 'Snapdragon 820' (when it should be a Snapdragon 652)?
Cheers, raimerik
Click to expand...
Click to collapse
Thats a bug with official rom itself. This rom is official, so chill
veisen said:
5. copy rom (X527-5_9_21S.zip) to the phone
Click to expand...
Click to collapse
can't copy X527-5_9_21S.zip (2,1GB) to /sdcard. Copy always stops after copying 140MB or so. I copy mounting USB storage from TWRP, and then through the file administrator with copy-paste (Ubuntu 16.04, linux). Filesystem is ok. I've done a factory reset before. What can I do?
xe7um said:
can't copy X527-5_9_21S.zip (2,1GB) to /sdcard. Copy always stops after copying 140MB or so. I copy mounting USB storage from TWRP, and then through the file administrator with copy-paste (Ubuntu 16.04, linux). Filesystem is ok. I've done a factory reset before. What can I do?
Click to expand...
Click to collapse
Try pushing it through adb
Rename the file to update.zip
Open terminal
cd "directory of the zip folder"
adb push update.zip /sdcard/
Wait for few minutes, it should be done.
bonsai.14 said:
Try pushing it through adb
Rename the file to update.zip
Open terminal
cd "directory of the zip folder"
adb push update.zip /sdcard/
Wait for few minutes, it should be done.
Click to expand...
Click to collapse
I've tried it already:
Code:
[email protected]:~/LeeecoLe2X527$ adb push -p X527-5_9_21S.zip /sdcard/Varis
Transferring: 15335424/2096207546 (0%)
Hanged up
xe7um said:
can't copy X527-5_9_21S.zip (2,1GB) to /sdcard. Copy always stops after copying 140MB or so. I copy mounting USB storage from TWRP, and then through the file administrator with copy-paste (Ubuntu 16.04, linux). Filesystem is ok. I've done a factory reset before. What can I do?
Click to expand...
Click to collapse
You can Sideload it enable sideload on twrp and use command
adb sideload "/your_dir/your_file.zip"
veisen said:
You can Sideload it enable sideload on twrp and use command
adb sideload "/your_dir/your_file.zip"
Click to expand...
Click to collapse
Ok, @veisen I'll try it. But do you have any reasonable explanation of why adb push stops copying?
Any one using this rom? How's battery life n camera ?
If possible post some screenshots