Related
Hi
After trying to install crombi on tf700 using twrp 2.7 something went wrong and now tablette is bootlooping on twrp screen.
Cpnnected the tablette to laptop and nothing appears in the M'y Computer Windows.
Checked on device manager and found 'transformer' writen there with yellow exclamation Mark.
Tried to update driver with nô success.
Any help Will be greatly appreciated
Thanks
We need more information.
What did you come from?
What's your bootloader and rom versions?
Did you do a full wipe?
Describe in detail the procedure you followed.
berndblb said:
We need more information.
What did you come from?
What's your bootloader and rom versions?
Did you do a full wipe?
Describe in detail the procedure you followed.
Click to expand...
Click to collapse
Hi and thanks for the reply.
The tablet was on the latest Cromi-x and bootloader.
Did a full wipe and begun installing crombi
The tablet was stuck a long time on formatting so I had to regoot
After the reboot it was unable to moiunt E,
Tried to do another full wipe and now the tablet is just bootlooping on the TWRP splashscreen.
Any suggestion?
Formatting with TWRP 2.7 can take 90 minutes. You should not have interrupted it.
Can you get into fastboot?
Or alternatively you can try to get an adb connection when the tablet is looping.
berndblb said:
Formatting with TWRP 2.7 can take 90 minutes. You should not have interrupted it.
Can you get into fastboot?
Or alternatively you can try to get an adb connection when the tablet is looping.
Click to expand...
Click to collapse
Thanks for the answer so just connect the tablet, open cmd and do adb devices ?
Will try it in 30 min as I am not home
Tried the adb devices on a command windows in the platform-tools directory and nothing comes after hitting enter
Anything else to try?
What about fastboot? Boot with Volume Down and Power. Then try
'fastboot devices'
Sent from my DROID4 using Tapatalk
allotesting said:
Thanks for the answer so just connect the tablet, open cmd and do adb devices ?
Will try it in 30 min as I am not home
Tried the adb devices on a command windows in the platform-tools directory and nothing comes after hitting enter
Anything else to try?
Click to expand...
Click to collapse
Nothing? something must come up. What does it say? Command not found? No devices found?
sbdags said:
Nothing? something must come up. What does it say? Command not found? No devices found?
Click to expand...
Click to collapse
Hi
When I try the fastboot devices command it comes back to the invite with nothing written
When I try the adb devices nothing after list of devices attached
And the tablet keeps on bootlooping on the teamwin splash screen
And as already stated in device manager I find the mention transformer with yellow mark
Hi
Something new after I tried to update driver
Tried the fastboot command and it found something
It gives me s bunch of numbers and letters and recovery at the end
Is it good doctor?
Tried to install TWRP using fastboot -I 0x0B05 flsh recovery TWRP.blob and it sots there with the message <waiting for device> and tablet is still bootlooping:crying:
allotesting said:
Tried to install TWRP using fastboot -I 0x0B05 flsh recovery TWRP.blob and it sots there with the message <waiting for device> and tablet is still bootlooping:crying:
Click to expand...
Click to collapse
Are you in the boot loader when you issue that command?
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
allotesting said:
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
Click to expand...
Click to collapse
Yes that is normal. What happens when you flash twrp with fasboot. What does it report back?
allotesting said:
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
Click to expand...
Click to collapse
Ok, I think we need to clear up some things:
If the tablet is bootlooping it cannot be in the bootloader and fastboot mode (you are in the bootloader menu when you see the 3 icons: RCK, Android, Wipe Data). But if you see the adb interface in Device Manager while it is looping you should have an adb connection and
Code:
adb devices
should return a similar but different string of numbers and letters.
Code:
adb reboot-bootloader
should boot you into the bootloader which is also fastboot mode.
In fastboot you should be able to flash TWRP with the command you posted, minus the typos naturally.
It has to be
Code:
fastboot devices
and it has to return the string of letters and numbers, then:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Try that and report back
Hi there, I have the exact same problem. I tried searching all over about the time for a full wipe and couldn't find anything. So after about an hour I hard powered down. Of course, when I started researching the recovery look, I found the info (roughly 90-120 minutes). Here is what I have done to try to rectify, perhaps you can help. I booted into the bootloader and ran the following commands:
C:\>fastboot devices
015d2bbcc413ea10 fastboot
C:\>cd adb
C:\adb>dir
Volume in drive C has no label.
Volume Serial Number is 48F6-D102
Directory of C:\adb
04/29/2014 11:49 PM <DIR> .
04/29/2014 11:49 PM <DIR> ..
04/25/2014 06:59 AM 819,200 adb.exe
04/25/2014 06:59 AM 96,256 AdbWinApi.dll
04/25/2014 06:59 AM 60,928 AdbWinUsbApi.dll
04/25/2014 06:59 AM 160,256 fastboot.exe
04/29/2014 11:49 PM 6,443,112 openrecovery-twrp-2.7.0.0-tf700t.blob
5 File(s) 7,579,752 bytes
2 Dir(s) 672,096,153,600 bytes free
C:\adb>ren openrecovery-twrp-2.7.0.0-tf700t.blob twrp.blob
C:\adb>dir
Volume in drive C has no label.
Volume Serial Number is 48F6-D102
Directory of C:\adb
04/29/2014 11:50 PM <DIR> .
04/29/2014 11:50 PM <DIR> ..
04/25/2014 06:59 AM 819,200 adb.exe
04/25/2014 06:59 AM 96,256 AdbWinApi.dll
04/25/2014 06:59 AM 60,928 AdbWinUsbApi.dll
04/25/2014 06:59 AM 160,256 fastboot.exe
04/29/2014 11:49 PM 6,443,112 twrp.blob
5 File(s) 7,579,752 bytes
2 Dir(s) 672,096,088,064 bytes free
C:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
OKAY [ 2.459s]
writing 'recovery'...
OKAY [ 7.564s]
finished. total time: 10.023s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.022s
Click to expand...
Click to collapse
When I reboot into the bootloader and click RCK I get the TEAMWIN logo (blue screen). About every 2-3 seconds the screen goes black and the TEAMWIN logo shows again.
Thoughts?
---------- Post added 30th April 2014 at 12:16 AM ---------- Previous post was 29th April 2014 at 11:56 PM ----------
I decided to play around a little more to see what I could do. I pushed TWRP v2.6.3.2 to the device replacing v2.7. Finally I was able to get into TWRP. However, now I am stuck. TWRP asks me for a password that was never set (I don't have one). I hit cancel and the main menu and I show as having -1mb of internal storage.
If I try any commands, I am told that there aren't permissions to access the partitions. I feel like I am getting closer.
If I tell TWRP to FORMAT DATA in the WIPE menu, recovery restarts and asks me for my password again.
Thoughts?
BigKenW said:
Hi there, I have the exact same problem. I tried searching all over about the time for a full wipe and couldn't find anything. So after about an hour I hard powered down. Of course, when I started researching the recovery look, I found the info (roughly 90-120 minutes). Here is what I have done to try to rectify, perhaps you can help. I booted into the bootloader and ran the following commands:
When I reboot into the bootloader and click RCK I get the TEAMWIN logo (blue screen). About every 2-3 seconds the screen goes black and the TEAMWIN logo shows again.
Thoughts?
---------- Post added 30th April 2014 at 12:16 AM ---------- Previous post was 29th April 2014 at 11:56 PM ----------
I decided to play around a little more to see what I could do. I pushed TWRP v2.6.3.2 to the device replacing v2.7. Finally I was able to get into TWRP. However, now I am stuck. TWRP asks me for a password that was never set (I don't have one). I hit cancel and the main menu and I show as having -1mb of internal storage.
If I try any commands, I am told that there aren't permissions to access the partitions. I feel like I am getting closer.
If I tell TWRP to FORMAT DATA in the WIPE menu, recovery restarts and asks me for my password again.
Thoughts?
Click to expand...
Click to collapse
It seems as if TWRP thinks your data partition is encrypted.
Boot into recovery, make sure you have an adb connection with
Code:
adb devices
if that returns a string of letters and numbers try
Code:
adb killall recovery
This should get you back to recovery and then try to format data again.
Good luck
berndblb said:
It seems as if TWRP thinks your data partition is encrypted.
Boot into recovery, make sure you have an adb connection with
Code:
adb devices
if that returns a string of letters and numbers try
Code:
adb killall recovery
This should get you back to recovery and then try to format data again.
Good luck
Click to expand...
Click to collapse
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
Click to expand...
Click to collapse
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
---------- Post added at 01:18 AM ---------- Previous post was at 12:55 AM ----------
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
Click to expand...
Click to collapse
Alright, nothing I can do will fix this thing. The internal drive shows 0mb. I even tried installing CWM and I can't mount any partitions. I would like to return to full stock. I can't seem to find anything like an RUU or other tool to do this. Can someone please direct me to the best thread to do so?
After I am back stock I will unlock the bootloader again.
I will follow all the commands when I will be back from work. It's 3:30 here in Montreal thanks guys
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
---------- Post added at 01:18 AM ---------- Previous post was at 12:55 AM ----------
Alright, nothing I can do will fix this thing. The internal drive shows 0mb. I even tried installing CWM and I can't mount any partitions. I would like to return to full stock. I can't seem to find anything like an RUU or other tool to do this. Can someone please direct me to the best thread to do so?
After I am back stock I will unlock the bootloader again.
Click to expand...
Click to collapse
To return to stock just download the Asus firmware, unzip it once and flash the resulting zip in recovery.
Your bootloader will stay unlocked. You just have to flash a custom recovery again, reboot and then flash the rom.
allotesting said:
I will follow all the commands when I will be back from work. It's 3:30 here in Montreal thanks guys
Click to expand...
Click to collapse
Hi all
Back from work but all the commands were uselee
In device manager I have ASUS android ADB interface after updating manually the 'transformer' that I had with the yellow matk
When trying adb devices it comes with 0123456789ABCDEF all the hexadecimal digits so seems to me that the machine does not recognize the tablet itself
When trying fastboot devices and hit enter it comes back to the >invite
When trying adb reboot-bootloader it just sits there with even no >invite
Forgot to mention that the word recovery comes after the 0123456789ABCDEF on the adb devices
Anything else to try? Thanks
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
DarkDarwin said:
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
Click to expand...
Click to collapse
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
_that said:
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
Click to expand...
Click to collapse
Im afraid I wiped everything.I think my mistake was wiping in stock recovery instead of TWRP..thus it only boots to TWRP now.
I tried those commands but my machine was hanging like it was waiting for the device so I am going to uninstall and reinstall the windows drivers and ADB/Fastboot and do the commands again ,Ive been at work since this morning so ive got some honey dos then I can start trying it again.
Thanks so much!
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
DarkDarwin said:
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
Click to expand...
Click to collapse
So am I correct in saying that you can get to fastboot ?
lj50036 said:
So am I correct in saying that you can get to fastboot ?
Click to expand...
Click to collapse
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
DarkDarwin said:
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
Click to expand...
Click to collapse
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
berndblb said:
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
Click to expand...
Click to collapse
Thanks for trying to help me yesterday bro!
lj50036 said:
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
Click to expand...
Click to collapse
Any chance we could get a step-bystep on that? Pleeeaaase?
berndblb said:
Any chance we could get a step-bystep on that? Pleeeaaase?
Click to expand...
Click to collapse
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
lj50036 said:
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
Click to expand...
Click to collapse
I went out and got a bigger SD card (64) to try and implement the DATA2SD script.I think I was successful as I now have new folders there named Android and Data that I didn't have before...However,I wonder if I was supposed to wipe anything before I re-flashed the ROM after inserting the formatted , partitioned SD...
I have to admit the I/O issue is extremely aggravating..I cant believe Asus marred an otherwise excellent device like that.
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
Ok, when I boot up in android, I can use adb command reboot bootloader to boot in the bootloader.
When i then try fastboot erase system, it's still hangs with waiting for device..
The bootloader is not stuck, i can again boot up android..
it's impossible to open terminal, because the touch is going crazy..
Hmm, i'm trying something else.
I still had 10x tf300 for repair. there are multiple cracked with 5184n version.
I installed the cracked display assembly on this one, then i just can normally use the keyboard.
Will try again in terminal
edit: what command to use in terminal?
Dont forget, i flashed the recovery, but didnt install supersu zip yet..
The strange thing is, when im in the bootloader, i can use fastboot flash recovery command, and write the right recovery.
It's also succesfull (sending recovery OK, writing recovery OK)
But, the transformer hangs in the bootloader after finished (freeze)
When trying to reboot, it's automaticaly going again booting up twrp (enter password)
So it didnt write the recovery, by example if i write twrp 2.7, it still gives me 2.6.3.0 (installed first time)
extra information:
If i'm booted up, and then adb reboot bootloader, then try fastboot commands, they don't work. it keeps saying waiting for devices.., the fastboot commands like flash works for 1 second then the tablet freezes.
Click to expand...
Click to collapse
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Wow what a difference DATA2SD and ROM2SD make!
lvrijn said:
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Click to expand...
Click to collapse
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
DarkDarwin said:
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Click to expand...
Click to collapse
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
lj50036 said:
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
Click to expand...
Click to collapse
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
lvrijn said:
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
Click to expand...
Click to collapse
LOL, looking for help but you know what you got...
WOW
lj50036 said:
LOL, looking for help but you know what you got...
WOW
Click to expand...
Click to collapse
Sorry, I dont understand what you mean. What do you know I got?
lvrijn said:
Sorry, I dont understand what you mean. What do you know I got?
Click to expand...
Click to collapse
Sounds like you know more about this then any of us.
Not all Transformer tablets use the same drivers.
Window is very picky about what driver it will use for what device ...
Hello guys i have Nokia 3 and i want to root it can i root it without any problems and after root can I recieve updates and am able to install it successfully?
I need help
I unlocked the bootloader, Thanks to the_laser, but... I can´t install any recovery, I´ve looking many options, and I can´t
Can yo help me, giving me the link here or by private message.
I need to root my nokia 3 ta-1028 please.
Thanks a lot
xdrucsix said:
I unlocked the bootloader, Thanks to the_laser, but... I can´t install any recovery, I´ve looking many options, and I can´t
Can yo help me, giving me the link here or by private message.
I need to root my nokia 3 ta-1028 please.
Thanks a lot
Click to expand...
Click to collapse
twrp is available only for ta-1032, sorry about that, you need to wait for someone to port it.
SkaboXD said:
twrp is available only for ta-1032, sorry about that, you need to wait for someone to port it.
Click to expand...
Click to collapse
Oh, Ok I can see, I have to wait :/
is there any difference between ta-1028 and ta-1032 in TWRP view ?
it is easy to try just boot into recovery - "fastboot boot <recovery.img>"
the_laser said:
is there any difference between ta-1028 and ta-1032 in TWRP view ?
it is easy to try just boot into recovery - fastboot boot recovery <recovery.img>
Click to expand...
Click to collapse
i know that ta-1032 is for EU dual sim, ta-1028 is american single sim version but i think that there is no difference in hardware. he can try that command to see is that recovery works @xdrucsix
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img
then you will see does it boot or not. twrp will disappear completely after you exit twrp.
I did every step that you say, nothing happened :/
something should definitely happen
at least show all fastboot.exe output during your tries
SkaboXD said:
twrp is available only for ta-1032, sorry about that, you need to wait for someone to port it.
Click to expand...
Click to collapse
The twrp dint even work for 1032..
Mithra siva said:
The twrp dint even work for 1032..
Click to expand...
Click to collapse
it worked for me and others, which method you tried?
SkaboXD said:
it worked for me and others, which method you tried?
Click to expand...
Click to collapse
The method you have mentioned only.. it was showing writing ..'recovery' failed..
---------- Post added at 12:53 PM ---------- Previous post was at 12:49 PM ----------
SkaboXD said:
it worked for me and others, which method you tried?
Click to expand...
Click to collapse
The method you have mentioned only..
It was showing ." Writing 'recovery'...failed (remote size too large)... Please help
SkaboXD said:
it worked for me and others, which method you tried?
Click to expand...
Click to collapse
Bro say something
Mithra siva said:
Bro say something
Click to expand...
Click to collapse
try this
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img
SkaboXD said:
try this
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img
Click to expand...
Click to collapse
How to type location..I have kept it in root folder of (E)
---------- Post added at 05:16 AM ---------- Previous post was at 05:00 AM ----------
SkaboXD said:
try this
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img
Click to expand...
Click to collapse
Can you please send again...how to install twrp..with twrp link indetail.. I go for a last try..
Mithra siva said:
How to type location..I have kept it in root folder of (E)
---------- Post added at 05:16 AM ---------- Previous post was at 05:00 AM ----------
Can you please send again...how to install twrp..with twrp link indetail.. I go for a last try..
Click to expand...
Click to collapse
link for twrp
https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
when downloaded, copy twrp to folder platform-tools and rename it to recovery.img
to type platform-tools location, type this:
chdir C:/Users/John/Desktop/platform-tools (this is just a example, you need to type your own location of platform-tools)
reboot to recovery
adb reboot recovery
then reboot to bootloader (fastboot) by pressing volume keys.
to flash recovery type this command:
fastboot flash recovery recovery.img
then reboot, fastboot reboot
if it didn't worked, use this command just to boot to twrp (you need to do this everytime when you are connected to PC)
fastboot boot recovery.img
To install root, first disable system modification on twrp then flash this zip for root.
This is not the latest version of SuperSU, but newest releases have some problems and crashes. (at least for me). This is last version that works for me.
That is it.
SkaboXD said:
link for twrp
https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
when downloaded, copy twrp to folder platform-tools and rename it to recovery.img
to type platform-tools location, type this:
chdir C:/Users/John/Desktop/platform-tools (this is just a example, you need to type your own location of platform-tools)
reboot to recovery
adb reboot recovery
then reboot to bootloader (fastboot) by pressing volume keys.
to flash recovery type this command:
fastboot flash recovery recovery.img
then reboot, fastboot reboot
if it didn't worked, use this command just to boot to twrp (you need to do this everytime when you are connected to PC)
fastboot boot recovery.img
To install root, first disable system modification on twrp then flash this zip for root.
This is not the latest version of SuperSU, but newest releases have some problems and crashes. (at least for me). This is last version that works for me.
That is it.
Click to expand...
Click to collapse
Thanks man it's done..
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
Mithra siva said:
Thanks man it's done..
Click to expand...
Click to collapse
Now can I relock my Bootloader with root..if i can please instruct me
And again thanks a lot
Mithra siva said:
Thanks man it's done..
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
Now can I relock my Bootloader with root..if i can please instruct me
And again thanks a lot
Click to expand...
Click to collapse
no, you can't have locked bootloader and root, after locking bootloader you need to reflash .nb0 file with OST because locking bootloader don't just remove data, it removes whole ROM.
SkaboXD said:
no, you can't have locked bootloader and root, after locking bootloader you need to reflash .nb0 file with OST because locking bootloader don't just remove data, it removes whole ROM.
Click to expand...
Click to collapse
I can't able to remove the system apps even after root..I used system app remover (root) ..
Help
Mithra siva said:
I can't able to remove the system apps even after root..I used system app remover (root) ..
Help
Click to expand...
Click to collapse
did you rebooted after uninstalling system apps?
SkaboXD said:
did you rebooted after uninstalling system apps?
Click to expand...
Click to collapse
It was showing uninstalling failed
LineogeOS for microG is there for our wonderful device. Its basically official Lineage with signature spoofing and build in microg (open source, battery friendly alternative for Google Framework).
More details at: https://lineage.microg.org
Download: https://download.lineage.microg.org/tissot/
radogost said:
LineogeOS for microG is there for our wonderful device. Its basically official Lineage with signature spoofing and build in microg (open source, battery friendly alternative for Google Framework).
More details at: https://lineage.microg.org
Download: https://download.lineage.microg.org/tissot/
Click to expand...
Click to collapse
Did you manage to install it? I get the same Error in twrp which was also reported in LOS official thread recently.
Tim1909 said:
Did you manage to install it? I get the same Error in twrp which was also reported in LOS official thread recently.
Click to expand...
Click to collapse
Unfortunately I am experiencing same issue. Waiting for a fix
radogost said:
Unfortunately I am experiencing same issue. Waiting for a fix
Click to expand...
Click to collapse
I got the solution but my post got flagged for some reason... Pm me while i sort this out with the admins.
Is any of the LOS Team a part of this fork, or completely separate?
ekistece said:
I got the solution but my post got flagged for some reason... Pm me while i sort this out with the admins.
Click to expand...
Click to collapse
What was the solution?
luizlef said:
What was the solution?
Click to expand...
Click to collapse
I managed to install it, it got really tricky. The thing is that the new Lineageos releases somehow fail the verification on twrp and the old lineageos recovery. I found out after hours of investigating that you need the *new* Lineageos recovery to flash the new lineageos. I know, it's pretty absurd.
SOLUTION:
I extracted the boot.img from lineage-15.1-20180724-microG-tissot.zip extracting the payload.bin from the zip and using this tool https://androidfilehost.com/?fid=818070582850510260.
You can download the boot.img I extracted myself here: https://drive.google.com/file/d/11jjAErjSmP-duaWvt8pLElIsgGtNuUp5/view?usp=sharing
Put the phone on fastboot mode, connect via usb and type:
Code:
fastboot boot boot.img
while pressing the volume-up button to enter the Lineageos recovery.
From there do a factory reset, wipe system, and now you can flash lineage-15.1-20180724-microG-tissot.zip.
To flash it, it gets tricky. First of all you can't flash from the sdcard because it shows up an error. So you go to update, and press install from ADB or something like that. Now you have the phone on adb sideload mode.
Download https://developer.android.com/studio/releases/platform-tools. Adb from XDA's "Minimal ADB and Fastboot" doesn't work for some reason.
Unzip the file, open a command prompt on that folder and type:
Code:
adb devices
It has to show up as something like this:
Code:
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
xxxxxxxxxxx sideload
Where xxxxxxx is the phone id.
Then you can proceed to flash. Just type:
Code:
adb sideload lineage-15.1-20180724-microG-tissot.zip.
Wait until it completes, it seems to freeze at 47% or so but wait some minutes until the progress bar on the recovery finishes and reboot.
Now you should be booting lineageos and set up it as usual. I hope this guide helped, took me some hours to figure it all out.
EDIT: I posted the boot.img since the tool i used to extract it is flagged by some AV (probably false positives). https://drive.google.com/file/d/11jjAErjSmP-duaWvt8pLElIsgGtNuUp5/view?usp=sharing
ekistece said:
I managed to install it, it got really tricky. The thing is that the new Lineageos releases somehow fail the verification on twrp and the old lineageos recovery. I found out after hours of investigating that you need the *new* Lineageos recovery to flash the new lineageos. I know, it's pretty absurd.
SOLUTION:
I extracted the boot.img from lineage-15.1-20180724-microG-tissot.zip extracting the payload.bin from the zip and using this tool
Put the phone on fastboot mode, connect via usb and type:
Code:
fastboot boot boot.img
while pressing the volume-up button to enter the Lineageos recovery.
From there do a factory reset, wipe system, and now you can flash lineage-15.1-20180724-microG-tissot.zip.
To flash it, it gets tricky. First of all you can't flash from the sdcard because it shows up an error. So you go to update, and press install from ADB or something like that. Now you have the phone on adb sideload mode.
Adb from XDA's "Minimal ADB and Fastboot" doesn't work for some reason.
Unzip the file, open a command prompt on that folder and type:
Code:
adb status
It has to show up as something like this:
Code:
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
xxxxxxxxxxx sideload
Where xxxxxxx is the phone id.
Then you can proceed to flash. Just type:
Code:
adb sideload lineage-15.1-20180724-microG-tissot.zip.
Wait until it completes, it seems to freeze at 47% or so but wait some minutes until the progress bar on the recovery finishes and reboot.
Now you should be booting lineageos and set up it as usual. I hope this guide helped, took me some hours to figure it all out.
Click to expand...
Click to collapse
I can´t boot into lineage recovery as you wrote. The phone reboot on stock as usual
luizlef said:
I can´t boot into lineage recovery as you wrote. The phone reboot on stock as usual
Click to expand...
Click to collapse
Did you use the LineageOS-microg boot.img? You have to hold the volume-up button while your are on fastboot and keep holding it until you enter recovery. Try with the one I extracted https://drive.google.com/file/d/11jjAErjSmP-duaWvt8pLElIsgGtNuUp5/view?usp=sharing
ekistece said:
Did you use the LineageOS-microg boot.img? You have to hold the volume-up button while your are on fastboot and keep holding it until you enter recovery. Try with the one I extracted
Click to expand...
Click to collapse
Man...I got the lineage recovery, i did the steps you wrote and now when i type adb status appears: adb: usage: unknown command status
I can´t install the zip file :crying:
ekistece said:
I managed to install it, it got really tricky. The thing is that the new Lineageos releases somehow fail the verification on twrp and the old lineageos recovery. I found out after hours of investigating that you need the *new* Lineageos recovery to flash the new lineageos. I know, it's pretty absurd.
SOLUTION:
I extracted the boot.img from lineage-15.1-20180724-microG-tissot.zip extracting the payload.bin from the zip and using this tool https://androidfilehost.com/?fid=818070582850510260.
You can download the boot.img I extracted myself here: https://drive.google.com/file/d/11jjAErjSmP-duaWvt8pLElIsgGtNuUp5/view?usp=sharing
Put the phone on fastboot mode, connect via usb and type:
Code:
fastboot boot boot.img
while pressing the volume-up button to enter the Lineageos recovery.
From there do a factory reset, wipe system, and now you can flash lineage-15.1-20180724-microG-tissot.zip.
To flash it, it gets tricky. First of all you can't flash from the sdcard because it shows up an error. So you go to update, and press install from ADB or something like that. Now you have the phone on adb sideload mode.
Download https://developer.android.com/studio/releases/platform-tools. Adb from XDA's "Minimal ADB and Fastboot" doesn't work for some reason.
Unzip the file, open a command prompt on that folder and type:
Code:
adb status
It has to show up as something like this:
Code:
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
xxxxxxxxxxx sideload
Where xxxxxxx is the phone id.
Then you can proceed to flash. Just type:
Code:
adb sideload lineage-15.1-20180724-microG-tissot.zip.
Wait until it completes, it seems to freeze at 47% or so but wait some minutes until the progress bar on the recovery finishes and reboot.
Now you should be booting lineageos and set up it as usual. I hope this guide helped, took me some hours to figure it all out.
EDIT: I posted the boot.img since the tool i used to extract it is flagged by some AV (probably false positives). https://drive.google.com/file/d/11jjAErjSmP-duaWvt8pLElIsgGtNuUp5/view?usp=sharing
Click to expand...
Click to collapse
I got stuck in the part of "Signature verification failed. Install anyway". What are we supposed to do in that part? Wait or touch in "Yess"?
Btw, sorry for my bad english.
luizlef said:
Man...I got the lineage recovery, i did the steps you wrote and now when i type adb status appears: adb: usage: unknown command status
I can´t install the zip file :crying:
Click to expand...
Click to collapse
Are you using this adb? https://developer.android.com/studio/releases/platform-tools
The one from https://forum.xda-developers.com/showthread.php?t=2317790 doesn't work. I told that on my initial post xD
If that still doesn't work, try another usb port or enable disable the adb thing from the recovery. Eventually it will wotk, lineageos recovery is super buggy atm...
---------- Post added at 06:07 PM ---------- Previous post was at 06:03 PM ----------
jmpa07 said:
I got stuck in the part of "Signature verification failed. Install anyway". What are we supposed to do in that part? Wait or touch in "Yess"?
Btw, sorry for my bad english.
Click to expand...
Click to collapse
I don't remember that part... I should have taken photos or something. Are you flashing it through adb?
ekistece said:
Are you using this adb? https://developer.android.com/studio/releases/platform-tools
The one from https://forum.xda-developers.com/showthread.php?t=2317790 doesn't work. I told that on my initial post xD
If that still doesn't work, try another usb port or enable disable the adb thing from the recovery. Eventually it will wotk, lineageos recovery is super buggy atm...
---------- Post added at 06:07 PM ---------- Previous post was at 06:03 PM ----------
I don't remember that part... I should have taken photos or something. Are you flashing it through adb?
Click to expand...
Click to collapse
Yes, i´m using this files...
Now the error appears: no devices/emulators found
@ekistece Thank you for a great workaround!
We have new TWRP which should successfully flash newest LOS:
https://kremowka.xyz/files/twrp-3.2.2-0-tissot-lineage.img or https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-2-2-1-touch-recovery-t3821469
If you want to try it by yourself, put your device into Fastboot mode, open ADB and type:
fastboot boot twrp-3.2.2-0-tissot-lineage.img (if you downloaded first file)
Then wipe system, data, cache and flash ROM.
Click to expand...
Click to collapse
I will try to flash by myself using those tomorrow.
EDIT: I tried those recoveries, unfortunately both are not working for me (first one throws error 7, second one error 1).
radogost said:
@ekistece Thank you for a great workaround!
We have new TWRP which should nail flashing newest LOS:
https://kremowka.xyz/files/twrp-3.2.2-0-tissot-lineage.img or https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-2-2-1-touch-recovery-t3821469
I will try to flash using those tomorrow.
Click to expand...
Click to collapse
That's nice to know! It's pretty disappoiting that Lineageos changed the update format without them releasing the recovery images nor waiting for twrp implementing it... Also their official guide points to use the twrp from the official page that didn't even work before (had to use mohancm's one). Between this and the April Fools "joke" that affected the builds for 2 weeks or so, I'm starting to think that this project is not even serious. Btw the guys from Micro-G are doing a great work, it would be nice that they made their own distro from scratch using AOSP or something.
ekistece said:
That's nice to know! It's pretty disappoiting that Lineageos changed the update format without them releasing the recovery images nor waiting for twrp implementing it... Also their official guide points to use the twrp from the official page that didn't even work before (had to use mohancm's one). Between this and the April Fools "joke" that affected the builds for 2 weeks or so, I'm starting to think that this project is not even serious. Btw the guys from Micro-G are doing a great work, it would be nice that they made their own distro from scratch using AOSP or something.
Click to expand...
Click to collapse
I was surprised too, Lineage Team is known for their professional approach - this time they failed. I am trying to flash using first link right now - will report later.
Again, thank you for your research!
radogost said:
I was surprised too, Lineage Team is known for their professional approach - this time they failed. I am trying to flash using first link right now - will report later.
Again, thank you for your research!
Click to expand...
Click to collapse
Thanks! It seems that I'm the only one that flashed it succesfully in this thread. Remember to use the lastest adb from here https://developer.android.com/studio/releases/platform-tools
radogost said:
@ekistece Thank you for a great workaround!
We have new TWRP which should successfully flash newest LOS:
https://kremowka.xyz/files/twrp-3.2.2-0-tissot-lineage.img or https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-2-2-1-touch-recovery-t3821469
If you want to try it by yourself, put your device into Fastboot mode, open ADB and type:
I will try to flash by myself using those tomorrow.
EDIT: I tried those recoveries, unfortunately both are not working for me (first one throws error 7, second one error 1).
Click to expand...
Click to collapse
With this recovery now I get Error 18 (ErrorCode: :kDownloadPayloadPubKeyVerificationError).
Best regards,
---------- Post added at 07:21 PM ---------- Previous post was at 07:18 PM ----------
ekistece said:
Are you using this adb? https://developer.android.com/studio/releases/platform-tools
The one from https://forum.xda-developers.com/showthread.php?t=2317790 doesn't work. I told that on my initial post xD
If that still doesn't work, try another usb port or enable disable the adb thing from the recovery. Eventually it will wotk, lineageos recovery is super buggy atm...
---------- Post added at 06:07 PM ---------- Previous post was at 06:03 PM ----------
I don't remember that part... I should have taken photos or something. Are you flashing it through adb?
Click to expand...
Click to collapse
Yes, I tried with adb
jmpa07 said:
With this recovery now I get Error 18 (ErrorCode: :kDownloadPayloadPubKeyVerificationError).
Best regards,
---------- Post added at 07:21 PM ---------- Previous post was at 07:18 PM ----------
Yes, I tried with adb
Click to expand...
Click to collapse
I got the error 18 with mohancm recovery, thats why i looked for an alternative method of flashing. Try to press yes to skip the verification and flash it anyways. Do it at your own risk, I don't remember if i skipped it. It may be my bad memory or you have corrupt zip. Check the hashes from the microg webpage and flash it pressing yes on your phone if they match. The hashes are:
Code:
MD5: bd753bd9128f045df2e5dcaf63efb6e8 lineage-15.1-20180724-microG-tissot.zip
SHA256: 5137d0b4e510d4a45c733f9453ce62ac08bf6f8c3e1c84bd08a1f9e2a9ba03d9 lineage-15.1-20180724-microG-tissot.zip
Worst case scenario, you **** up your system and boot partition, but that's not a big issue, you can boot normal twrp and flash another rom.
---------- Post added at 08:30 PM ---------- Previous post was at 08:08 PM ----------
luizlef said:
Man...I got the lineage recovery, i did the steps you wrote and now when i type adb status appears: adb: usage: unknown command status
I can´t install the zip file :crying:
Click to expand...
Click to collapse
Ok i read my guide again and it wasn't status it is
Code:
adb devices
try it again with that
Tried all possible ways, nothing works except @ekistece workaround. Also ekistece modified recovery doesn't boot for me - you must do all steps by yourself.
Waiting for a Lineage fix!
Hey guys,
VIDEO TUTORIAL:
https://youtu.be/ylBSZk7EqcA o
Someone written a better tutorial or you can follow my video tutorial
https://docs.google.com/document/d/1fdeO9jmm8ewwRX_G0MaGHsVfIVtxgh0yRK0-Yypcl_E/edit?usp=drivesdk
Credits:
@loonycgb2 for the bootloader tutorial
@jsergan[/MENTION] for the root tutorial
@Zackptg5p and whoever helped him for this DM Verity and forceencrypt disabler
Where "21ULMD Kdz file"
I can't found it on web
Ahmed Ismael said:
Where "21ULMD Kdz file"
I can't found it on web
Click to expand...
Click to collapse
https://lg-firmwares.com/downloads-file/20303/G710ULM21d_00_NAO_US_OP_0711
---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------
Before I flash it I wanted to ask if you notice any performance difference between 11g (oreo) and 21d. Is it just as fast?
ninjamirage said:
https://lg-firmwares.com/downloads-file/20303/G710ULM21d_00_NAO_US_OP_0711
---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------
Before I flash it I wanted to ask if you notice any performance difference between 11g (oreo) and 21d. Is it just as fast?
Click to expand...
Click to collapse
I Cross-Flash G710ULM20 GFI
Performance increases
I cross-flashed G710pm to G710ulm20e USA. Thanks OP and lge.fun
I only have to ask if you should let magisk manager download and install the updated zip (20.1). I decided not to because it may break the rooted boot image.
ninjamirage said:
I cross-flashed G710pm to G710ulm20e USA. Thanks OP and lge.fun
I only have to ask if you should let magisk manager download and install the updated zip (20.1). I decided not to because it may break the rooted boot image.
Click to expand...
Click to collapse
Nah it works you can update it via twrp or direct install it.
Awesomeslayerg said:
Nah it works you can update it via twrp or direct install it.
Click to expand...
Click to collapse
Thanks. I don't think I need fastboot yet. I am not sure how to erase the LAF partition.
ninjamirage said:
I cross-flashed G710pm to G710ulm20e USA. Thanks OP and lge.fun
I only have to ask if you should let magisk manager download and install the updated zip (20.1). I decided not to because it may break the rooted boot image.
Click to expand...
Click to collapse
ninjamirage said:
Thanks. I don't think I need fastboot yet. I am not sure how to erase the LAF partition.
Click to expand...
Click to collapse
To zero it out use adb shell or the termrnial app then su
The do:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
To get into download mode:
Theres two ways#
1. Get into fastboot mode and set current slot to b
Code:
fastboot --set-active=b
then reboot and hold the up button while its connectrc to your pc and you should be able to get into download mode
2. Boot into twrp, then tap reboot in the menu and on the bottom it should say slot a or b and select b. Then reboot. Dont worry about not being able to mount.
Awesomeslayerg said:
To zero it out use adb shell or the termrnial app then su
The do:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
To get into download mode:
Theres two ways#
1. Get into fastboot mode and set current slot to b
Code:
fastboot --set-active=b
then reboot and hold the up button while its connectrc to your pc and you should be able to get into download mode
2. Boot into twrp, then tap reboot in the menu and on the bottom it should say slot a or b and select b. Then reboot. Dont worry about not being able to mount.
Click to expand...
Click to collapse
Is that for installing a custom rom?
Then do you need to do this?
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_a.img
ninjamirage said:
Is that for installing a custom rom?
Then do you need to do this?
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_a.img
Click to expand...
Click to collapse
Yes
This tutorial is trash, I'm tried everything but my device keep getting bricked and bootloop, pls delete it!
CyborgSG said:
This tutorial is trash, I'm tried everything but my device keep getting bricked and bootloop, pls delete it!
Click to expand...
Click to collapse
One person got it to work. I
Can you show the full details of your method, as I'm tried patch both img and it's work, but when I boot to download mode and connect to PC and open LGUp, it's always show unknown model, try flash the img it in fastboot many time, it's always happen like that
CyborgSG said:
This tutorial is trash, I'm tried everything but my device keep getting bricked and bootloop, pls delete it!
Click to expand...
Click to collapse
CyborgSG said:
Can you show the full details of your method, as I'm tried patch both img and it's work, but when I boot to download mode and connect to PC and open LGUp, it's always show unknown model
Click to expand...
Click to collapse
First don't call a tutorial trash cause you didn't do it properly and you didn't even detail the problem properly. . Second, make sure you're still on 11g firmware or go back to 11g firmware via download mode of you're not and then flash the abl partition from the unlocked bootloader tutorial if you havent used that abl. Then fastboot flash rooted 11g boot_a and boot_b file then reboot to firmware and make sure it boots all the way up and restart your PC then try going into download mode again if it works go into fastboot flash the 21ulmd booted rooted image both a and b then immediately restart to download mod
I'm on g710ulm11g and I'm rooted, updated the magisk to 20.1, now do I have to boot to fastboot and boot the twrp20ulmrooted img to boot_a and boot_b and then boot to download mode?
CyborgSG said:
I'm on g710ulm11g and I'm rooted, updated the magisk to 20.1, now do I have to boot to fastboot and boot the twrp20ulmrooted img to boot_a and boot_b and then boot to download mode?
Click to expand...
Click to collapse
Noo. Fastboot flash 21ulmrooted to both a and b then reboot to download mode.
question: I am rooted with magisk and on ULM21d. I have extracted the image file and renamed it "twrp21ulmdroot.img" and put this file on my internal storage /sdcard. When I run the command dd if=/sdcard/twrp21ulmdroot.img of=/dev/block/bootdevice/by-name/boot_a in adb shell (as root #) it keeps giving me a response of dd: /sdcard/twrp21ulmdroot.img: No such file or directory. The file is actually there. Any ideas?
way2aware said:
question: I am rooted with magisk and on ULM21d. I have extracted the image file and renamed it "twrp21ulmdroot.img" and put this file on my internal storage /sdcard. When I run the command dd if=/sdcard/twrp21ulmdroot.img of=/dev/block/bootdevice/by-name/boot_a in adb shell (as root #) it keeps giving me a response of dd: /sdcard/twrp21ulmdroot.img: No such file or directory. The file is actually there. Any ideas?
Click to expand...
Click to collapse
Are you sure you didn't name it twrp21ulmd.img.img? Or reboot the device.. Make sure it's where the Download, pictures etc.. folders are.
Awesomeslayerg said:
Noo. Fastboot flash 21ulmrooted to both a and b then reboot to download mode.
Click to expand...
Click to collapse
When I'm try to boot the twrp20ulmrooted to boot a and boot b, bcoz I want to root on g710ulm20e, then in command it's show up: cannot boot a boot.img *and* ramdisk, so what exactly command I have to use in adb and fastboot?
Awesomeslayerg said:
Are you sure you didn't name it twrp21ulmd.img.img? Or reboot the device.. Make sure it's where the Download, pictures etc.. folders are.
Click to expand...
Click to collapse
sir, your tutorial worked perfectly for me- I now for the first time since owning this phone have a custom recovery. Thank you for your help :good:
Edit: my problem earlier was that the image file was not installing to my internal storage in the right place for whatever reason... /sdcard was not available when searching my int storage. So I dropped the file into 'Download', then used Advanced tools pro file manager to grab it and paste it into the parent directory. At that point the shell commands worked