Related
Hi
I followed this tutorial (http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/) to root my Nexus S (GTi-9023). Like a bunch of other people on this site my phone got stuck on the "Google with a pad lock" boot screen (I should have come to xda first). So to get past this i downloaded the stock rom (from here: http://forum.xda-developers.com/showthread.php?t=1056062) and extracted boot.img and then flashed the stock boot image and booted with it as below.
>fastboot flash boot boot.img
>fastboot boot boot.img
This fixed fixed my booting problem and i then used rom manager to install clockwork recovery. I can boot into clockwork recovery from rom manager but not from fastboot. i get an android with an exclamation mark. Any idea why and/or how to fix this?
Thanks in advance.
boozelclark said:
Hi
I followed this tutorial (http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/) to root my Nexus S (GTi-9023). Like a bunch of other people on this site my phone got stuck on the "Google with a pad lock" boot screen (I should have come to xda first). So to get past this i downloaded the stock rom (from here: http://forum.xda-developers.com/showthread.php?t=1056062) and extracted boot.img and then flashed the stock boot image and booted with it as below.
>fastboot flash boot boot.img
>fastboot boot boot.img
This fixed fixed my booting problem and i then used rom manager to install clockwork recovery. I can boot into clockwork recovery from rom manager but not from fastboot. i get an android with an exclamation mark. Any idea why and/or how to fix this?
Thanks in advance.
Click to expand...
Click to collapse
Rename /etc/install-recovery.sh to install-recovery.sh.bak, then reflash the recovery.
DONT use rom manager to flash the recovery it hardly ever works [for me],
If you have 'Android SDK' and 'ADB' then,Download a decent recovery file and place it in your 'Android-SDK/tools" directory, then go to your 'cmd' [command prompt] and navigate to your android-sdk/tools directory ,,example below.
''cd C:/android-sdk/tools'' [cd meaning 'change directory']
Then type, "adb devices" it should list your devices ith a load of numbers and letters, if it does then proceed, if not re-plug your device into the USB [in the bootloader]
Then type,
"fastboot flash recovery recovery.img" and let it do its thing. [if it does not work , make sure you renamed you recovery file to 'recovery.img'
Hope this helps!!
XDA_Badman said:
DONT use rom manager to flash the recovery it hardly ever works [for me],
...
Click to expand...
Click to collapse
The problem is that with the stock rom the stock recovery gets flashed after boot up (by /etc/install-recovery.sh). Search for install-recovery.sh in the nexus s forums.
So it seems I have messed up my phone decently bad
decided to go back and reload everything from scratch but unfortunately flashed back a CWM version thats 3.0.1 and when I try to flash my old recovery (ICS CM9) it gives me error 7
I am guessing thats because I have to install 5.0 CWM can anyone explain to me how to do this?
Thank you so much all!
Yan
More Info:
Ok so heres the deal.
I was originally running CM9 from Nexus MV ICS rom with a Franco Kernel.
All was well and phone was rock solid for weeks since he released with everything working.
as the update came out I was told I should revert back to 2.3.6 and wait for the OTA update that way I could have the true OEM ICS. It is pretty much 90% of why I originally Rooted and unlocked my phone.
I used this link.
http://forum.xda-developers.com/showthread.php?t=1063664
and downloaded
Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
That I flashed using CWM
Phone rebooted fine but had no SuperUser file and seemed like it no longer was rooted so though if I go back and re-root it should be fine.
Went to.
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
and went straight to instruction 5) Open up a command prompt by typing “cmd” under Start->Search Programs and files.
Then type “cd \nexussrootnew” to browse into the directory in Windows. For Linux and Mac, should be similar to “cd /nexussrootnew“.
Then type “fastboot oem unlock“.
Thats when I went back to CWM 3.1.0.1 and tried to install any rom or backup and it just seems to give me Status 7 error.
I hate that I cant figure this out alone but I am a little lost.
Here's a link: http://forum.xda-developers.com/showthread.php?t=1382624
Use the search next time, it took less than 10 seconds for me to find the page.
063_XOBX said:
Here's a link: http://forum.xda-developers.com/showthread.php?t=1382624
Use the search next time, it took less than 10 seconds for me to find the page.
Click to expand...
Click to collapse
Actually I tried this originally
http://forum.xda-developers.com/showthread.php?t=1248760
Still get Status 7!
Sorry I usually search before just forgot to write that in!
Download CWM 5.0.2.0 and rename the .img to recovery.img
(i'll assume you have phone drivers and everything working, and fastboot)
Put the recovery.img into the same directory as your fastboot.exe
Boot into your bootmanager (vol up+power)
Plug phone into PC
Open up CMD prompt and change to the directory where you have fastboot.exe
(cd c:\android\tools) for example
type in:
> fastboot flash recovery recovery.img
reboot to recovery
seriosbrad said:
Download CWM 5.0.2.0 and rename the .img to recovery.img
(i'll assume you have phone drivers and everything working, and fastboot)
Put the recovery.img into the same directory as your fastboot.exe
Boot into your bootmanager (vol up+power)
Plug phone into PC
Open up CMD prompt and change to the directory where you have fastboot.exe
(cd c:\android\tools) for example
type in:
> fastboot flash recovery recovery.img
reboot to recovery
Click to expand...
Click to collapse
I tried that and unfortunately it gives me an error when I try it
says
"Error: cannot load recovery.img"
Used the download from this link!
http://forum.xda-developers.com/showthread.php?t=988686&highlight=recovery
Looks like someone else is having the same issue as me.
http://forum.xda-developers.com/showthread.php?t=996914&page=4
Try to just boot the newer cwm recovery with fastboot
Fastboot boot recovery recovery name.img
albundy2010 said:
Try to just boot the newer cwm recovery with fastboot
Fastboot boot recovery recovery name.img
Click to expand...
Click to collapse
Same error as earlier....
Can Not load
Darn this is frustrating!
sspikey said:
Same error as earlier....
Can Not load
Darn this is frustrating!
Click to expand...
Click to collapse
SWEET just got this phone to boot up again! No network right now for some reason but wifi works!
Here is what I used.
http://forum.xda-developers.com/showthread.php?t=884093
Where should I go from here? Ideas? I am guessing I have to install super user Zip through the current 3.0XX CWM right?
MORE PROGRESS!!!!!
Got CWM 5.0.2.0 loaded on to it by flashing the IMG through CMD
Worked after what I did earlier!
Progressing forward!!!!
Final cherry on top of the cake!!!
works perfectly again accepted my nandroid backup and shes running at 100%
ah feels good!
please help me i am also having the same problem i tried everything nothing seemed to work out and please check my thread ( http://forum.xda-developers.com/showthread.php?t=1533346 ) thnx.
Well, Last night i tried franco kernel over my stock rom and now i want to go back to stock kernel itself. So to flash Franco kernel, i had to unlock the bootloader and installed TWRP Recovery and also rooted the phone with normal super su from chainfire website. I dunno what is systemless root cause i'm new here and never had any issues before with my old nexus device.. i'm little in knowledge regarding the Nexus 6P. So please guide me with a proper link to follow.. I googled and coudnt find the real sources.
Flash boot.img from bootloader using fastboot flash boot boot.img
sam razzy said:
Well, Last night i tried franco kernel over my stock rom and now i want to go back to stock kernel itself. So to flash Franco kernel, i had to unlock the bootloader and installed TWRP Recovery and also rooted the phone with normal super su from chainfire website. I dunno what is systemless root cause i'm new here and never had any issues before with my old nexus device.. i'm little in knowledge regarding the Nexus 6P. So please guide me with a proper link to follow.. I googled and coudnt find the real sources.
Click to expand...
Click to collapse
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I solved it by installing wugs toolkit on my PC.. Thank you..
Sent from my Nexus 6P using Tapatalk
Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Should I lose TWRP by doing this command. I seem to always loose my recovery doing android updates, or now when I went back to stock kernel using your instructions, on NEXUS 6P. I just flash the recovery back, but it's still weird.
GogoAkira said:
Should I lose TWRP by doing this command. I seem to always loose my recovery doing android updates, or now when I went back to stock kernel using your instructions, on NEXUS 6P. I just flash the recovery back, but it's still weird.
Click to expand...
Click to collapse
No TWRP is in the recovery partition. This command flashes the boot partition. On losing TWRP, try flashing SU immediately following TWRP before booting to the System for the first time. Then TWRP will stick.
I did per Heisenberg's instructions, it sticks, but still I lost it after this command that's why it's weird
Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
To keep root and the custom recovery (TWRP) you need to do additional steps
Code:
fastboot reboot-bootloader
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot-bootloader
start recovery from bootloader
install SuperSU from TWRP
Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
What's in the boot.img? Will it not reset or do something on the rom? Because I just wanted to restore the kernel .
Pawnzer said:
What's in the boot.img? Will it not reset or do something on the rom? Because I just wanted to restore the kernel .
Click to expand...
Click to collapse
It is the kernel.
Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Can it be executed via recovery, install>select image file (boot.img)>choose boot partition>swipe
Or must via fastboot mode?
EASIEST way:
(No need to connect to PC & use fastboot)
— Extract your stock rom .zip,
— Copy 'boot.img' somewhere else on internal or external SD,
— In TWRP select 'flash .img',
— Flash 'boot.img', (DO NOT REBOOT!)
— Now flash your 'recovery.img' again in recovery.
DONE.
Now if you 'reboot to recovery' you still have TWRP, when you 'reboot' you are using the stock boot.img (kernel) too, no need for PC/Fastboot.
KEEP IN MIND!.... After flashing stock boot.img you will need to flash root again AND (depending on device) may trigger 'DM-verity' and/or 'Forced Encryption' (Oxygen OS and others) if you reboot straight away, so make sure if you do NOT want this to flash/re-flash 'DM-verity & force encryption disabler' .zip (search google/the forums here - zackptg5)
Hope this helps anyone in the future.
ErbDroid said:
EASIEST way:
(No need to connect to PC & use fastboot)
— Extract your stock rom .zip,
— Copy 'boot.img' somewhere else on internal or external SD,
— In TWRP select 'flash .img',
— Flash 'boot.img', (DO NOT REBOOT!)
— Now flash your 'recovery.img' again in recovery.
DONE.
Now if you 'reboot to recovery' you still have TWRP, when you 'reboot' you are using the stock boot.img (kernel) too, no need for PC/Fastboot.
KEEP IN MIND!.... After flashing stock boot.img you will need to flash root again AND (depending on device) may trigger 'DM-verity' and/or 'Forced Encryption' (Oxygen OS and others) if you reboot straight away, so make sure if you do NOT want this to flash/re-flash 'DM-verity & force encryption disabler' .zip (search google/the forums here - zackptg5)
Hope this helps anyone in the future.
Click to expand...
Click to collapse
Thank you so much for your instruction, Doing it step by step and karnel restored to stock!
Hi All,
I've deodexed the systems from 34.0.A.2.292 and 34.0.A.2.301.
How to use:
1. download zip
2. flash with flashfire or custom recovery
3. enjoy
Download links:
F5121_34.0.A.2.292_Deodexed.zip
F5121_34.0.A.2.301_Deodexed.zip
nice work bro
Pandemic said:
nice work bro
Click to expand...
Click to collapse
we need a kernel with recovery or at least sony init, so we can use recovery on its proper partition..
kick-start development on X/suzu ...
ive compiled a boot img from .292 copyleft sources and added ramdisk/twrp..
https://drive.google.com/open?id=0B2Ayh5ZFCqa8RVI1cHJwYk5BeE0
if someone with a unlocked bootloader could try, it would be great.
infected_ said:
we need a kernel with recovery or at least sony init, so we can use recovery on its proper partition..
kick-start development on X/suzu ...
ive compiled a boot img from .292 copyleft sources and added ramdisk/twrp..
https://drive.google.com/open?id=0B2Ayh5ZFCqa8RVI1cHJwYk5BeE0
if someone with a unlocked bootloader could try, it would be great.
Click to expand...
Click to collapse
i flashed it on my german .292, and its booting.
but im not sure how to enter twrp?
adb reboot recovery results in a 'melting' sony screen and after some second the phone reboots into system.
mstrack said:
i flashed it on my german .292, and its booting.
but im not sure how to enter twrp?
adb reboot recovery results in a 'melting' sony screen and after some second the phone reboots into system.
Click to expand...
Click to collapse
did you flashed a twrp recovery on the recovery partition?
try this one:
https://drive.google.com/file/d/0B2Ayh5ZFCqa8UkxzYnhIazlZenM/view?usp=sharing
and try enter recovery again with that kernel/boot img above.
infected_ said:
did you flashed a twrp recovery on the recovery partition?
try this one:
https://drive.google.com/file/d/0B2Ayh5ZFCqa8UkxzYnhIazlZenM/view?usp=sharing
and try enter recovery again with that kernel/boot img above.
Click to expand...
Click to collapse
so, flashed it, reboot, lands in twrp.
asks for encryption password but doesnt accept my pwd.
edit: doesnt boot into system, only in twrp
edit2: i have to flash the recovery via flashtool -> flash kernel ? or did i something wrong?
hell...i miss my nexus...
mstrack said:
so, flashed it, reboot, lands in twrp.
asks for encryption password but doesnt accept my pwd.
edit: doesnt boot into system, only in twrp
edit2: i have to flash the recovery via flashtool -> flash kernel ? or did i something wrong?
hell...i miss my nexus...
Click to expand...
Click to collapse
You can press cancel when twrp asks for password. It will bring you to the main menu, but a lot of stuff isnt working yet. Currently there is no working twrp yet for our xperia X, follow this thread for more info: http://forum.xda-developers.com/xperia-x/development/root-xperia-x-34-0-2-292-modified-t3449708
edit: did you flash it with flashtool or adb?
kistigun said:
You can press cancel when twrp asks for password. It will bring you to the main menu, but a lot of stuff isnt working yet. Currently there is no working twrp yet for our xperia X, follow this thread for more info: http://forum.xda-developers.com/xperia-x/development/root-xperia-x-34-0-2-292-modified-t3449708
Click to expand...
Click to collapse
yes, got it, thx.
edit: i used flashtool
kistigun said:
You can press cancel when twrp asks for password. It will bring you to the main menu, but a lot of stuff isnt working yet. Currently there is no working twrp yet for our xperia X, follow this thread for more info: http://forum.xda-developers.com/xperia-x/development/root-xperia-x-34-0-2-292-modified-t3449708
edit: did you flash it with flashtool or adb?
Click to expand...
Click to collapse
the person who gave me that recovery, ill assure you that is working... it came from one member of omni core dev's, which owns a suzu...
you dont have access to the rest of the twrp options, cause of the encryption.
remember the first time you booted up your X on stock? it asked to encrypt/set a password on the device because if it got stolen or lost, etc...
fastboot erase boot, fastboot erase system && fastboot erase userdata should get rid of the encryption and you can try twrp.
all this is helpless ofc unless we can get a stock boot image working with sony init, so we can enter recovery when flashed on recovery partition.
if you hotboot the twrp it works right? so it is working.
infected_ said:
the person who gave me that recovery, ill assure you that is working... it came from one member of omni core dev's, which owns a suzu...
you dont have access to the rest of the twrp options, cause of the encryption.
remember the first time you booted up your X on stock? it asked to encrypt/set a password on the device because if it got stolen or lost, etc...
fastboot erase boot, fastboot erase system && fastboot erase userdata should get rid of the encryption and you can try twrp.
all this is helpless ofc unless we can get a stock boot image working with sony init, so we can enter recovery when flashed on recovery partition.
if you hotboot the twrp it works right? ok then.
Click to expand...
Click to collapse
Thanks for the tip will try it out tonight and report back!
kistigun said:
Thanks for the tip will try it out tonight and report back!
Click to expand...
Click to collapse
try ramdisk of the recovery also. extract it and try to add it to your .292 boot.img
infected_ said:
try ramdisk of the recovery also. extract it and try to add it to your .292 boot.img
Click to expand...
Click to collapse
will do, just wondering: what files/folders of the ramdisk are needed for TWRP? I ask because I use a kernel with allready a modified ramdisk(DM-verity/Sony RIC/DRM-fix/SU?busyBox) so I want to know what files need to be replaced to implements TWRP
infected_ said:
the person who gave me that recovery, ill assure you that is working... it came from one member of omni core dev's, which owns a suzu...
you dont have access to the rest of the twrp options, cause of the encryption.
remember the first time you booted up your X on stock? it asked to encrypt/set a password on the device because if it got stolen or lost, etc...
fastboot erase boot, fastboot erase system && fastboot erase userdata should get rid of the encryption and you can try twrp.
all this is helpless ofc unless we can get a stock boot image working with sony init, so we can enter recovery when flashed on recovery partition.
if you hotboot the twrp it works right? so it is working.
Click to expand...
Click to collapse
So when i try to hotboot the f5121_recovery.img for the first time it flashes the image, after that it boots but it gets stuck on a black screen. I did a hard reset and flashed the image with adb and tried to reboot to recovery but it just rebooted. After that i tried again to hotboot the recovery image and after this it finally booted into TWRP. indeed it's asking for password
Will i loose my system and userdata when i use fastboot erase boot, fastboot erase system && fastboot erase userdata?
kistigun said:
So when i try to hotboot the f5121_recovery.img for the first time it flashes the image, after that it boots but it gets stuck on a black screen. I did a hard reset and flashed the image with adb and tried to reboot to recovery but it just rebooted. After that i tried again to hotboot the recovery image and after this it finally booted into TWRP. indeed it's asking for password
Will i loose my system and userdata when i use fastboot erase boot, fastboot erase system && fastboot erase userdata?
Click to expand...
Click to collapse
yes, it will all be wiped.
you can also try adding sony init to your ramdisk. you just need to extract it from boot.img, add the sony init files, rename a file and make a symlink, repack again to boot.img
ill provide the files in a minute.
edit:
after extracting contents of ramdisk, rename "init" to "init.real", and place the files on the root of the extracted ramdisk dir.
symlink is already created, pointing at /sbin/init_sony
https://drive.google.com/open?id=0B2Ayh5ZFCqa8N3pIQjZMY0ZzdU0
infected_ said:
yes, it will all be wiped.
you can also try adding sony init to your ramdisk. you just need to extract it from boot.img, add the sony init files, rename a file and make a symlink, repack again to boot.img
ill provide the files in a minute.
edit:
after extracting contents of ramdisk, rename "init" to "init.real", and place the files on the root of the extracted ramdisk dir.
symlink is already created, pointing at /sbin/init_sony
https://drive.google.com/open?id=0B2Ayh5ZFCqa8N3pIQjZMY0ZzdU0
Click to expand...
Click to collapse
cant extract the init file, getting an error(cant create a symbolic link: access denied)
Edit: hmm just discovered that the tool i was using for unpaking & repacking boot.img isn't working.... Need to find a new tool first, anyone got a good suggestion?
kistigun said:
cant extract the init file, getting an error(cant create a symbolic link: access denied)
Edit: hmm just discovered that the tool i was using for unpaking & repacking boot.img isn't working.... Need to find a new tool first, anyone got a good suggestion?
Click to expand...
Click to collapse
delete the symlink and recreate it:
ln -s /sbin/init_sony init
infected_ said:
delete the symlink and recreate it:
ln -s /sbin/init_sony init
Click to expand...
Click to collapse
Sorry it took me a while, had to set-up a new linux enviorment. Repacked kernel, it boots but sony init still doesnt work
Hy can i install the deodexed System as a regual normal System?
I mean if i break my System does IT work as a normal "Rom"
KOALAaufPILLEN said:
Hy can i install the deodexed System as a regual normal System?
I mean if i break my System does IT work as a normal "Rom"
Click to expand...
Click to collapse
No, it only flashes the deodexed files so it does not contain a ´full rom´
Could you make a full rom ? Cause right now i must use aosp rom but there are some features missing like sony themes and others
I accidentally wiped off everything with TWRP.
I have no backups.
I'm really having trouble finding ANY rom for this phone,custom or stock.
I've only found firmware that can update my OS not install it completely.
Could anyone find the correct ROM for me?
Anything will do.
Please help!
If you have a second device, donwload Huawei firmware finder from Play store. Enter your model number and donwload a full package. Doesn't really matter which one. Then just flash it in TWRP without extracting.
Vinnipinni said:
If you have a second device, donwload Huawei firmware finder from Play store. Enter your model number and donwload a full package. Doesn't really matter which one. Then just flash it in TWRP without extracting.
Click to expand...
Click to collapse
Is there any way to know my exact phone model number without having access to the OS?
Using the pc version I have to enter some kind of G and F values,what should i put in there?
EDIT:I've narrowed it down to WAS-LX1 and WAS LX1A,any way of distinguishing between those?
EDIT 2 : I seem to fail to flash literally any ROM,I get a zip verification error if i try to check that,if not I just get:
Updater process edned with ERROR : 9,and E: unknown command [errno] before that
Justkill43 said:
Is there any way to know my exact phone model number without having access to the OS?
Using the pc version I have to enter some kind of G and F values,what should i put in there?
EDIT:I've narrowed it down to WAS-LX1 and WAS LX1A,any way of distinguishing between those?
Click to expand...
Click to collapse
Shouldn't your phone model number be beneath the battery?
Michael24884 said:
Shouldn't your phone model number be beneath the battery?
Click to expand...
Click to collapse
Well yeah,it should.
But this is one of those phones that can't really be opened with special tools that I don't really have,and even if i did have them I wouldn't mess with the phone's insides because it's one of those types of phone....
Update:It may have something to do with the roms i have downloaded,I've tried 3 of them and none of them had ANY .img files
No boot.img no recovery.img etc,what am I doing wrong?
Justkill43 said:
Update:It may have something to do with the roms i have downloaded,I've tried 3 of them and none of them had ANY .img files
No boot.img no recovery.img etc,what am I doing wrong?
Click to expand...
Click to collapse
Huawei uses some special archiving, there should be an UPDATE.APP inside the downloaded files. You need a tool called Huawei Update Extractor to get the .img files.
Vinnipinni said:
Huawei uses some special archiving, there should be an UPDATE.APP inside the downloaded files. You need a tool called Huawei Update Extractor to get the .img files.
Click to expand...
Click to collapse
Oh I see,and should I just get the .imgs out of the update.app and then flash the rom?
Because so far I can't flash any of them,I get these errors:
E: unknown command [errno]
And
Updater process ended with ERROR : 9
Justkill43 said:
Oh I see,and should I just get the .imgs out of the update.app and then flash the rom?
Because so far I can't flash any of them,I get these errors:
E: unknown command [errno]
And
Updater process ended with ERROR : 9
Click to expand...
Click to collapse
What did you type?
Ohh and where are you from?
Vinnipinni said:
What did you type?
Ohh and where are you from?
Click to expand...
Click to collapse
What did i type??
Serbia.
Justkill43 said:
What did i type??
Serbia.
Click to expand...
Click to collapse
Yeah, mean the fastboot command you used
Vinnipinni said:
Yeah, mean the fastboot command you used
Click to expand...
Click to collapse
Kinda confused now,as I don't think I've used any fastboot commands at all.
Justkill43 said:
Kinda confused now,as I don't think I've used any fastboot commands at all.
Click to expand...
Click to collapse
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img
Vinnipinni said:
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Oh so I should just flash those 3 imgs instead of the whole zip?
Also there is no cust.img
I'll list all the imgs here so you can see what i should be able to flash:
-Boot
-Crc.img
-Curver.img
-DTS.img
-EFI.img
-FASTBOOT.img
-FW_HIFI.img
-FW_LPM3.img
-MODEM_FW.img
-PACKAGE_TYPE.img
-PRODUCT.img
-RECOVERY.img
-RECOVERY2.img
-SENSORHUNB.img
-SHA256RSA.img
-SYSTEM.img
-TEEOS.img
-TRUSTFIRMWARE.img
-VENDOR.img
-VERLIST.img
-XLOADER.img
Justkill43 said:
Oh so I should just flash those 3 imgs instead of the whole zip?
Also there is no cust.img
I'll list all the imgs here so you can see what i should be able to flash:
-Boot
-Crc.img
-Curver.img
-DTS.img
-EFI.img
-FASTBOOT.img
-FW_HIFI.img
-FW_LPM3.img
-MODEM_FW.img
-PACKAGE_TYPE.img
-PRODUCT.img
-RECOVERY.img
-RECOVERY2.img
-SENSORHUNB.img
-SHA256RSA.img
-SYSTEM.img
-TEEOS.img
-TRUSTFIRMWARE.img
-VENDOR.img
-VERLIST.img
-XLOADER.img
Click to expand...
Click to collapse
Yes! You can't flash most of it, it's not possible.
Flash Boot, Recovery, System and Vendor. Of that doesn't work, Put the UPDATE.APP into the dload folder on your SD and hold Power, Volume + and Volume -. That should force the flash of the update.
And if that still doesn't work, ask for a TWRP update on the P10 Forums. Then Restore everything except Data.
Vinnipinni said:
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Alright,I'm getting the hang of this.
But what did you mean with the exact filename of system.img?How do i find that out?
Justkill43 said:
Alright,I'm getting the hang of this.
But what did you mean with the exact filename of system.img?How do i find that out?
Click to expand...
Click to collapse
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG
Vinnipinni said:
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG
Click to expand...
Click to collapse
Got it,flashed system,recovery and boot
Trying to flash vendor I get an error when it's trying to write vendor:
FAILED (remote:Command not allowed)
Still stuck in a boot loop.
I'm gonna put the update.app in the sdcard.
I just create a dload folder in the sd card,put it in,wipe off everything I've flashed and do the 3 button thing,right?
Vinnipinni said:
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG
Click to expand...
Click to collapse
UPDATE: Failed the 3 button thing,maybe I got the wrong ROM,i'll try it with another one,I have a question though
My friend has the same phone as me(p10 lite) and when he goes to about phone and checks out the model number he only sees WAS-LX1
I'm pretty sure i have that same model number now but I can't find a ROM that's specifically WAS-LX1,it's always WAS-LX1 And something added on there like WAS-LX1C02,should I even worry about that?
Vinnipinni said:
Yes! You can't flash most of it, it's not possible.
Flash Boot, Recovery, System and Vendor. Of that doesn't work, Put the UPDATE.APP into the dload folder on your SD and hold Power, Volume + and Volume -. That should force the flash of the update.
And if that still doesn't work, ask for a TWRP update on the P10 Forums. Then Restore everything except Data.
Click to expand...
Click to collapse
After trying the first 2 methods I can't even boot into twrp anymore,I'm super screwed...