Hello guys!
Im trying to change my stock kernel (2.3.3 stock rom) with the Paolo 2.6.35.14_v6-touch3 version (for overclocking purposes).
I have enabled Fastboot ok in my P500h phone (using this threads), and when i boot into it the screen show me:
Fastboot mode started
udc_start()
-- suspend --
-- reset --
-- portchange --
-- reset --
Click to expand...
Click to collapse
After that, i run a CMD command prompt (windows 7 x64) inside the "platform-tools" folder of the SDK, wich contains the fastboot.exe and the zImage too, and i put the following command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zimage
zImage
sending 'zimage' (2621 KB)...
OKAY [ 0.700s]
writing 'zimage'...
FAILED (remote: unknown partition name)
finished. total time: 0.744s
Click to expand...
Click to collapse
At this point i know that the zImage was send it successfuly to my P500h, but some problem occur with the "writing process". Can any of you help me with this?
Thanks a lot!!
Xmas comes Xmas comes...!
EDIT 1: I'm trying the "fastboot devices" command and the results on my CMD was this:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
? fastboot
Click to expand...
Click to collapse
Is strange, because i already have the drivers updated correctly...What appears to them after you apply the command "fastboot devices"?
EDIT 2: I tried another way, using the command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot boot recovery-ra-thunderg-3.06-gnm.img
downloading 'boot.img'...
OKAY [ 1.214s]
booting...
OKAY [ 0.239s]
finished. total time: 1.454s
Click to expand...
Click to collapse
and my P500 boot ok the recovery, but the menu doesnt work (with the volume key) and i cant enter to any option listed. With this way, i thought upgrading the kernel using the "zip method" (i refuse to install a permanent custom recovery) :[.
I thought the "FAILED (remote: unknown partition name)" bug appear because my P500 tries to write to the "zimage" partition...and that not exist. In which partition should I install?
EDIT 3: Hi Guys!, after the above...i decided to install the new kernel using the Custom Recovery but installed in my system (because the "live boot" doesn't work :[... too bad). So, i applied the following commands for doing that:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery-ra-thunderg-3.06-gnm.img
sending 'recovery' (4682 KB)...
OKAY [ 1.214s]
writing 'recovery'...
OKAY [ 1.286s]
finished. total time: 2.500s
Click to expand...
Click to collapse
and then...
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.085s
Click to expand...
Click to collapse
After that, my Custom Recovery works like a charm and now i have Franco Kernel for official 2.3.3 at [320,672]mhz with SmartAssV2 governor (upper frequencies hang up my P500h).
I hope we can discuss how to achieve "live boot" of recovery or flashing the kernel via Fastboot directly. Now, i dont know how uninstall the Custom Recovery (i never wanted permanently installed on my P500). Inside the Custom Recovery exist an option to "revert to de stock recovery" but doesn't work.
Best regards for all of you!
asrhael
Related
Hi
I want Going back to stock for official Jelly Bean update and I followed this tutorial:
http://forum.xda-developers.com/showthread.php?p=36138808 # post36138808
I try to flash the recovery with the attached file: http://forum.xda-developers.com/showpost.php?p=35031493&postcount=25
fastboot flash recovery recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.813s]
writing 'recovery'...
OKAY [ 1.609s]
finished. total time: 3.422s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.531s]
finished. total time: 0.531s
fastboot erase cache
erasing 'cache'...
OKAY [ 0.266s]
finished. total time: 0.266s
When I returned to the fastboot and I select "recovery" the phone gets stuck on the following picture: http://s13.postimage.org/6hy5sfs2f/IMG_20120530_193934_1.jpg (photo found on google on another device)
This is my configuration :
Desire X
--> Bootloader unlocked
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.12.40.03
eMMC-boot
Oct 30 2012,20:09:09
Android : 4.0.4
HTC sense 4.1
N° 1.18.401.3
API HTC SDK : 4.24
HTCExtension_403_1_GA_24
Kernel :
3.0.21-g6c11713
[email protected]#1
Radio : 10.21.40.06U_1.12.40.03
Build : 1.18.401.3 CL128557 release-keys
Anyone know why my recovery doesn't work ?
Have you tried another another links for recovery? or the one from hansoons kit?
you could have just bad luck and flash buggy one
btw your question is wrong, from what you said, recovery was flashed in ok way, so there must be something wrong with recovery you flashed
Eliastux said:
I want Going back to stock for official Jelly Bean update
I try to flash the recovery with the attached file: http://forum.xda-developers.com/showpost.php?p=35031493&postcount=25
When I returned to the fastboot and I select "recovery" the phone gets stuck on the following picture: http://s13.postimage.org/6hy5sfs2f/IMG_20120530_193934_1.jpg (photo found on google on another device)
Anyone know why my recovery can not be flashed?
Click to expand...
Click to collapse
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Thank you for this quick answer !
mindlesSheep said:
Have you tried another another links for recovery? or the one from hansoons kit?
you could have just bad luck and flash buggy one
Click to expand...
Click to collapse
Okey I have tried this one :
http://forum.xda-developers.com/attachment.php?attachmentid=1618686&d=1357387592
fastboot.exe flash recovery stock_recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.297s]
writing 'recovery'...
OKAY [ 1.641s]
finished. total time: 2.938s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.250s]
finished. total time: 0.250s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.648s]
finished. total time: 0.650s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture : http://s13.postimage.org/6hy5sfs2f/I...0_193934_1.jpg
And after 5 sec the phone reboot : Is it normal ?
mindlesSheep said:
btw your question is wrong, from what you said, recovery was flashed in ok way, so there must be something wrong with recovery you flashed
Click to expand...
Click to collapse
Ok I will edit my first post
mindlesSheep said:
or the one from hansoons kit?
Click to expand...
Click to collapse
Ok I try this immediately
ckpv5 said:
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Click to expand...
Click to collapse
When I want to apply the Jelly Bean 2.20.401.5 update the phone reboot on the buggy recovery and the phone gets stuck on the same picture
ckpv5 said:
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Click to expand...
Click to collapse
I thought I had to go back to stock recovery for the update of Jelly Bean I'm wrong?
Am I also wrong about the fact that we can apply the update without relock the bootloader?
Eliastux said:
I thought I had to go back to stock recovery for the update of Jelly Bean I'm wrong?
Am I also wrong about the fact that we can apply the update without relock the bootloader?
Click to expand...
Click to collapse
1. Must have stock recovery installed
2. Must have a complete stock ROM (nothing is deleted)
3. Not necessary to flash a stock boot.img but it is advisable to have one
4. Not necessary to relock bootloader
5. If no.4 still brings problem then relock the bootloader but you will lose all data when unlocking again.
Eliastux said:
Okey I have tried this one :
http://forum.xda-developers.com/attachment.php?attachmentid=1618686&d=1357387592
fastboot.exe flash recovery stock_recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.297s]
writing 'recovery'...
OKAY [ 1.641s]
finished. total time: 2.938s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.250s]
finished. total time: 0.250s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.648s]
finished. total time: 0.650s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture : http://s13.postimage.org/6hy5sfs2f/I...0_193934_1.jpg
And after 5 sec the phone reboot : Is it normal ?
Click to expand...
Click to collapse
--> When I apply the update with this recovery, the phone boot on the recovery and I see the same picture and after 5 sec the phone shut down (no picture on the screen)... and the only way to boot after this is to remove/put the battery.
ckpv5 said:
1. Must have stock recovery installed
2. Must have a complete stock ROM (nothing is deleted)
3. Not necessary to flash a stock boot.img but it is advisable to have one
4. Not necessary to relock bootloader
5. If no.4 still brings problem then relock the bootloader but you will lose all data when unlocking again.
Click to expand...
Click to collapse
1 --> NOK
2 --> OK
3 --> I have to install first a stock recovery if I want to flash a stock boot.img...
4,5 --> OK not necessary
Thanks for your reply
Eliastux said:
or the one from hansoons kit?
Ok I try this immediately
Click to expand...
Click to collapse
I've tried to install TWRP 2.4.3.0 from the HTC Desire X All-In-One Kit (Hasoons kit) :
(I made it with command line because v2.1 of this tool is a little buggy :
astboot.exe flash recovery TWRP.img
< waiting for device >
sending 'recovery' (6158 KB)...
OKAY [ 5.680s]
writing 'recovery'...
OKAY [ 6.375s]
finished. total time: 12.055s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.563s]
finished. total time: 0.563s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 1.834s]
finished. total time: 1.874s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture !! ( the phone gets stuck ! )
Is the recovery of my phone bricked ?
Ok guys I found the solution ( after 4hours of research ! ) flashing my phone with this RUU : RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed.exe
Unfortunately (grr) I was not able to use the RUU normally (maybe because my recovery was buggy, I had a signature error) and I follow theses steps to install it :
1) fastboot erase cache
2) fastboot oem rebootRUU
3) fastboot flash zip rom.zip --> the rom.zip was extracted from the RUU.exe
4) fastboot reboot-bootloader
5) fastboot reboot
After that I could make two consecutive updates ( 1.18.401.3 and Jelly Bean update )
I hope it can help others who have the same problem :good:
Hi.
After I've tried to install a custom rom, I've done a very big mistake. Now I can't boot the tab, and if I try to go in recovery or wipe data through fastboot i get the fatally error "unrecoverable bootloader error 0x00000000". I haven't any nvflash backup and have the JB bootloader (10.6.1.8). The only thing that works are the APX mode and the fastboot. I'm feeling a very idiot because i bought it yesterday.
Now, what can I do? Dump it and f**k myself? :crying:
Sorry for my bad english, thank you for your help.
I realized I'm screwed. But I've tried something...
When I go run the fastboot mode and delete a partition, for example:
Code:
fastboot erase recovery
works, and after I can run other command. But if I use:
Code:
fastboot flash recovery recovery.img
seems it works, in fact the output is
Code:
sending 'recovery' (5378 KB)...
OKAY [ 2.431s]
writing 'recovery'...
OKAY [ 1.739s]
finished. total time: 4.170s
but it's stucked and I need to reboot manually.
Any idea?
Kito92 said:
I realized I'm screwed. But I've tried something...
When I go run the fastboot mode and delete a partition, for example:
Code:
fastboot erase recovery
works, and after I can run other command. But if I use:
Code:
fastboot flash recovery recovery.img
seems it works, in fact the output is
Code:
sending 'recovery' (5378 KB)...
OKAY [ 2.431s]
writing 'recovery'...
OKAY [ 1.739s]
finished. total time: 4.170s
but it's stucked and I need to reboot manually.
Any idea?
Click to expand...
Click to collapse
I have the same. Im on an ICS bootloader due to having to run nvflash to get it back to that point.
I have fastboot access i can send a recovery image over to it (twrp 2.5 ics.img) however when i reboot it i dont see the recovery!
PLEASE PLEASE PLEASE Someone help
Root Lenovo Vibe P1M
This guide will help you to root Lenovo Vibe P1M without bricking it.
Check this first.
Take backup of your important data at safe place.
Device must adequately charged.
Install USB drivers of your device PC.
Enable USB Debugging from Developer Options in Settings.
Enable Unknown Sources from Security in Settings.
Install TWRP
Follow the steps below.
Download ADB fastboot drivers [from here] and install it on PC.
Download TWRP recovery for Lenovo Vibe P1M from here.
Extract the zip file and find recovery.img file. Copy this file to your PC where you installed ADB fastboot drivers.
Now open Command Prompt.
Go to directory where you have installed ADB fastboot drivers.
Now enter the following commands.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery.img [B]OR[/B] fastboot boot recovery.img
fastboot reboot
After first command your device will reboot in fastboot mode. The second command will flash recovery image on your device. The third command will reboot your phone.
Now TWRP recovery is get installed on your Lenovo Vibe P1M.
Root Lenovo Vibe P1M
After installing TWRP on Lenovo Vibe P1M, follow the given steps to root it.
Download SuperSU from here.
Place the downloaded SuperSu zip in your extetnal SD card.
Now go to command prompt again and type the following command.
adb reboot recovery
Now your device will reboot in recovery mode. Flash supersu.zip from TWRP.
Reboot your device.
process completed.
Warning: I am not responsible if anything goes wrong, bricked device.
Does this method work with firmware ver S029. I am already rooted with kingoapp. But Flashfire app shows boot loader partitions to be protected . I suspect bootloader to be Locked. In such senario will this method work or will it brick my phone.
I also have another question if flash TWRP recovery on locked bootloader anyway, will it only fail to boot into recovery mode or will device fail to boot normally altogether
and it does boot normally then if i reflash stock recovery back on locked bootloader will that fix the issue of booting into recovery mode.
junkhunzai said:
Does this method work with firmware ver S029. I am already rooted with kingoapp. But Flashfire app shows boot loader partitions to be protected . I suspect bootloader to be Locked. In such senario will this method work or will it brick my phone.
I also have another question if flash TWRP recovery on locked bootloader anyway, will it only fail to boot into recovery mode or will device fail to boot normally altogether
and it does boot normally then if i reflash stock recovery back on locked bootloader will that fix the issue of booting into recovery mode.
Click to expand...
Click to collapse
This method will work ver S029 also. To flash recovery you need unlocked bootloader.
Well, I'm getting an error - (remote: not allowed), every time I try to boot the recovery.
ᵀᴴᴱ HUИTΞR said:
Well, I'm getting an error - (remote: not allowed), every time I try to boot the recovery.
Click to expand...
Click to collapse
Have you unlocked it?
1st command may be this
Fastboot oem unlock
Sent from my Redmi Note 3 using XDA-Developers mobile app
prajj said:
Have you unlocked it?
1st command may be this
Fastboot oem unlock
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 7.103s]
finished. total time: 7.105s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
C:\Program Files (x86)\Minimal ADB and Fastboot>
P.S: And now I have reboot loop... Reboot> Logo> Reboot > Logo...to infinity with a non-removable battry - just perfekt
P.S.: I can't get to recovery anymore...
ᵀᴴᴱ HUИTΞR said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 7.103s]
finished. total time: 7.105s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
C:\Program Files (x86)\Minimal ADB and Fastboot>
P.S: And now I have reboot loop... Reboot> Logo> Reboot > Logo...to infinity with a non-removable battry - just perfekt
P.S.: I can't get to recovery anymore...
Click to expand...
Click to collapse
Have you extracted the zip file and copied recovery.img file from zip to your PC where you installed ADB fastboot drivers?? And use following command to flash recovery.img
Code:
fastboot flash recovery.img
Also take a look at this thread for reference --> http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
bravonova said:
Have you extracted the zip file and copied recovery.img file from zip to your PC where you installed ADB fastboot drivers?? And use following command to flash recovery.img
Code:
fastboot flash recovery.img
Also take a look at this thread for reference --> http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
Click to expand...
Click to collapse
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Nabil99 said:
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Click to expand...
Click to collapse
Hey bro use flashify app to flash recovery through phone...
Stock Recovery backup deleted.
Hi, my vibe p1m now is running twrp recovery, but i accidentally deleted my backup of stock recovery yeah i know im dumb, but if someone can provide a link.. please help me....
Can anyone share a boot.img plz.? I forgot to back up mine.. Thanks a ton!
mikkel19 said:
Hi, my vibe p1m now is running twrp recovery, but i accidentally deleted my backup of stock recovery yeah i know im dumb, but if someone can provide a link.. please help me....
Click to expand...
Click to collapse
http://firmwarefile.com/lenovo-vibe-p1m/
This link gives you stock firmware. I too have deleted my backup but used it to get it back. But however I faced problems like boot loop many times and even IMEI turned 000000000000000 for both sim slots but still it was recovered by using "MTK Engineering Mode" app which you can get from "Play Store" and follow the following steps.
Step 1) Open the the MTK Engineer mode app and swipe left side to go into Connectivity.
Step 2) In the Connectivity click on the CDS information.
Step 3) And then Tap on the Radio information.
Step 4) Then you will be able to see Phone 1 and Phone 2
Step 5) Just click on Phone 1 first. then enter the Command as AT +EGMR=1,7,"your first imei" (Put a Space between AT and +, Like AT +EGMR=1,10,"your imei") and then tap on SEND AT COMMAND it will show you that command sent,
Step 6) Now press back button and Tap on Phone 2 (if you have a Dual Sim phone) and Type AT +EGMR=1,10,"second imei" and tap on send at command.
Step 7) Now Just Restart you device and enjoy now Sim Card will Display the Network in the status bar.
And you are done!!!!!!!!!
You can see your IMEI by pressing *#06#
If you face boot loop problems again and again please inform me.
Just the problems I faced. They are the solutions. Please do reply to this message.
Okay thank you. I will try it. Thanks a lot
mikkel19 said:
Okay thank you. I will try it. Thanks a lot
Click to expand...
Click to collapse
Please do ask if you get any problems coz my device is same and I've tried with 3-4 different ROMs including stock so can help you with many problems.
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
You can also root Lenovo Vibe P1m using SP Flash Tool. I've done the same and changed recovery from stock to TWRP easily without using any commands. Device works flawlessly and currently have installed MiUI 8 custom ROM.
mikkel19 said:
Okay thank you. I will try it. Thanks a lot
Click to expand...
Click to collapse
Oh and one more thing that zip file isn't for installing. You have to first extract it then you will get the instructions for flashing stock ROM. Happy flashing!!!!!
Sharath Guddad said:
Oh and one more thing that zip file isn't for installing. You have to first extract it then you will get the instructions for flashing stock ROM. Happy flashing!!!!!
Click to expand...
Click to collapse
Thank you, My vibe p1m is running on stock rom now, many thanks )))
Nabil99 said:
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Click to expand...
Click to collapse
Fastboot command given for flash recovery is wrong.
The right command is
Fastboot flash recovery recovery.img
Second recovery is the name of your recovery. If your recovery name is twrp then command is
Fastboot flash recovery twrp.img
Guys... If your device is new version (s036 pre installed) , use TWRP3 only.
Ashwinrg said:
Fastboot command given for flash recovery is wrong.
The right command is
Fastboot flash recovery recovery.img
Second recovery is the name of your recovery. If your recovery name is twrp then command is
Fastboot flash recovery twrp.img
Click to expand...
Click to collapse
C:\Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (10642 KB)...
OKAY [ 1.063s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 1.078s
cuci8202 said:
C:\Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (10642 KB)...
OKAY [ 1.063s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 1.078s
Click to expand...
Click to collapse
use TWRP3 only.. or install via sp flash tool.. it's very easy.. check this.. u can also get TWRP 3 here..
http://forum.xda-developers.com/android/general/how-to-install-twrp-root-lenovo-vibe-t3538088/page1
Hello guys,
I tried to root my sony xeperia z4 tablet+ lte and I followed this instruction:
theunlockr.com/2015/09/19/how-to-root-the-sony-xperia-z4-tablet
After I unlocked the bootloader and I did the following step:
"6. Type in the following command into the Command Prompt Window and press Enter:
fastboot flash boot boot.img"
C:\Users\Gmer07\Desktop>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (17056 KB)...
OKAY [ 0.390s]
writing 'boot'...
OKAY [ 0.167s]
finished. total time: 0.562s
does my tablet not start anymore... I dont know what to do.. I bought the tablet this week
syrius007 said:
Hello guys,
I tried to root my sony xeperia z4 tablet+ lte and I followed this instruction:
theunlockr.com/2015/09/19/how-to-root-the-sony-xperia-z4-tablet
After I unlocked the bootloader and I did the following step:
"6. Type in the following command into the Command Prompt Window and press Enter:
fastboot flash boot boot.img"
C:\Users\Gmer07\Desktop>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (17056 KB)...
OKAY [ 0.390s]
writing 'boot'...
OKAY [ 0.167s]
finished. total time: 0.562s
does my tablet not start anymore... I dont know what to do.. I bought the tablet this week
Click to expand...
Click to collapse
Android version ?
Firmware version ?
@AndroPlus kernel version?(make sure you downloaded the correct version for you tablet model: SGP 771 for the LTE)
Windows version
In command prompt Type fastboot Devices, if there is no number the windows driver not correctly installed
After unlocking the bootloader did you make a reboot ? (If so you should not enable MyXperia)
you better follow the advice on Androplus' website
There are different kernels for SONYs ROMs.
You should first update to the latest SONY ROM.
Then flash a recovery (also from Androplus) and then the latest kernel (aka boot.img, easier from recovery).
You also need to flash SuperSU - follow the instructions on Androplus' website.
this is the first time i have owned an LG phone. I have the bootloaded unlocked and usb debugging enabled. I have read just about every guide i could find but i still cant manage to flash twrp.
i am trying to flash the latest twrp-3.2.1-0-h830.img
i am showing build number NRD90U and software version H83020a.
i am getting this error message trying to flash thru either adb or minimal adb and fastboot programs:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (18700 KB)...
OKAY [ 0.511s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.531s
any suggestions would be appreciated. thanks
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-20a-nougat-lg-g5-hard-t3542496 this should show you how
tensux said:
this is the first time i have owned an LG phone. I have the bootloaded unlocked and usb debugging enabled. I have read just about every guide i could find but i still cant manage to flash twrp.
i am trying to flash the latest twrp-3.2.1-0-h830.img
i am showing build number NRD90U and software version H83020a.
i am getting this error message trying to flash thru either adb or minimal adb and fastboot programs:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (18700 KB)...
OKAY [ 0.511s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.531s
any suggestions would be appreciated. thanks
Click to expand...
Click to collapse
If you already have TWRP before just use the app.
If its the first time you flash twrp using the Recowvery method, make sure you have a copy of the recovery.img on your internal memory. :good:
rflores said:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-20a-nougat-lg-g5-hard-t3542496 this should show you how
Click to expand...
Click to collapse
cheeze.keyk said:
If you already have TWRP before just use the app.
If its the first time you flash twrp using the Recowvery method, make sure you have a copy of the recovery.img on your internal memory. :good:
Click to expand...
Click to collapse
Hi thanks for the replies.
I finally got it to work after a couple days of a soft brick at lg firmware update. i used Easyrecowery and and for some reason needled to toglle between file transfer and phot transfer while getting stuck while the scripts were processing
https://forum.xda-developers.com/tmobile-lg-g5/how-to/guide-root-twrp-lg-g5-using-t3580264
now to flash lineageos