Related
i am trying to flash amon ra,s recovery image on my nexus one. i have unlocked it and rooted. for some reason it keeps on telling me file not found. iam doing this thru the treminal app. is there any other way of doing it ?
go to Amons recovery page.... he has posted lot of ways to flash it...... if all fails come back here and ask.......
chowdarygm said:
go to Amons recovery page.... he has posted lot of ways to flash it...... if all fails come back here and ask.......
Click to expand...
Click to collapse
ive already did that still wont install
go to Amons recovery page.... he has posted lot of ways to flash it...... if all fails come back here and ask.......
Click to expand...
Click to collapse
ive already did that still wont install
Click to expand...
Click to collapse
Oh... thats really sad... did u rename the recovery image as per the commands u r giving ?
-------------------------------------
Sent via the XDA Tapatalk App
chowdarygm said:
Oh... thats really sad... did u rename the recovery image as per the commands u r giving ?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
yea is there a way of flashing it thru terminal on mac? like the way i unlocked it and rooted
helpppppppp
flashboot-mac flash recovery recovery-RA-nexus-v1.7.0.img
is this wrong?
Hey man, it sounds like either you don't know how a filesystem works, or how a terminal works. Unless you skipped the step on downloading fastboot-mac. If you didn't skip that step, you need to actually change into the directory where you downloaded that file to be able to run it.
If you have fastboot installed. Make sure you have the recovery.img file in the same directory as fastboot to flash. Preferable in the 'tools' directory.
timal said:
If you have fastboot installed. Make sure you have the recovery.img file in the same directory as fastboot to flash. Preferable in the 'tools' directory.
Click to expand...
Click to collapse
Or you can just do fastboot-mac flash recovery *drag image onto terminal window*
I believe when you flash through terminal on mac it should be ./fastboot flash recovery ./recovery-RA-nexus-v1.7.0.img
mich11128 said:
I believe when you flash through terminal on mac it should be ./fastboot flash recovery ./recovery-RA-nexus-v1.7.0.img
Click to expand...
Click to collapse
I completely forgot about that! I modified my bash_profile so all I have to do is type adb or fastboot and then the command.
Instructions here:
http://forum.xda-developers.com/showpost.php?p=5691126&postcount=319
oh ok I hadn't tried that when I first rooted so I just stuck to typing out "./" but that's good I'll give that a try in the future
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...
I need vendor.img for mi A1 .I flashed Android P ..now I back to stock but it shows pixle xl vendor
hamzaag49 said:
I need vendor.img for mi A1 .I flashed Android P ..now I back to stock but it shows pixle xl vendor
Click to expand...
Click to collapse
There is no vendor image for Mi A1.....?
Unless you mean unofficial one, which you can get from RR thread.
Flash stock ROM in EDL mode to revert fully back to stock after Treble stuff.
CosmicDan said:
Flash stock ROM in EDL mode to revert fully back to stock after Treble stuff.
Click to expand...
Click to collapse
Mi Flash shows "can not found programmer file", and it's not flashing
My device is showing COM10 instead of COM30, is this the problem?
Btw May fastboot image was working for me but the July one isn't
Hugwalk said:
Mi Flash shows "can not found programmer file", and it's not flashing
My device is showing COM10 instead of COM30, is this the problem?
Btw May fastboot image was working for me but the July one isn't
Click to expand...
Click to collapse
Programmer file probably means firehose. Did you choose the right directory? You need to select the "images" folder in stock firmware.
MiFlash will detect the correct COM port. Just make sure you press refresh, and it will show the com port in the MiFlash window.
CosmicDan said:
Programmer file probably means firehose. Did you choose the right directory? You need to select the "images" folder in stock firmware.
MiFlash will detect the correct COM port. Just make sure you press refresh, and it will show the com port in the MiFlash window.
Click to expand...
Click to collapse
The one I'm using is tissot-F-OPM1.171019.019.V9.6.3.0.ODHMIFE, and there's no image folder in it, original zip was unzipped without corruption.
Found another download, will test now.
Thanks for replying!
Edl mode need my mobile to disassemble?
Or using just cable?
hamzaag49 said:
Or using just cable?
Click to expand...
Click to collapse
First you can try in fastboot <fastboot oem edl>
Not working ot boot for while then goes of
hamzaag49 said:
Not working ot boot for while then goes of
Click to expand...
Click to collapse
If you do fastboot oem edl and you receive an error, it's normal. If you're phone reboot and you have a black screen with blinking led, you are in edl mode, if not, then try with cable, if cable not work dissamble and do testpoint
I'm having update issues...update failed after reverting back to stock.........
Hugwalk said:
The one I'm using is tissot-F-OPM1.171019.019.V9.6.3.0.ODHMIFE, and there's no image folder in it, original zip was unzipped without corruption.
Found another download, will test now.
Thanks for replying!
Click to expand...
Click to collapse
Download stock firmware from official site. That doesn't look like an official filename (what is the "F" for.... If that's a flashable TWRP ZIP then that won't work, you need ORIGINAL firmware package).
Did you unTreblelize yet?
If not, try to boot in Treble twrp and do it, then reflash rom in MiFlash or anything else.
There is no need to do anyrhing just flash official firmware via edl
I think that flashing via fastboot also revert back to original state cause of gpt will write
Not even going to keep this for the learning experience, it's not worth it.
Hi! Tks for you suport.
I have 2 questions if you can help me. I´m a noob for this phone, but i used to update mu Xperia with Remix and i unsdestand a little bit of installing costum firmware.
1- Do we need after this to install again stock boot.img? Because i read in were and MIUI forum that patch boot.img will not give OTA updates.
But installing stock will not remove Camera2api also?
2- I Have V9.6.13.0.ODIMIFE ( second september update) i try to seach for patch boot.img for A2 in were, but i only find the full stock image
in https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
I read what you said about teaching to fishing rather give a fish, but if for this thime you could put the link, in future updates we all will be more confortable do do other updates.
Kind regards
ki69 said:
1- Do we need after this to install again stock boot.img? Because i read in were and MIUI forum that patch boot.img will not give OTA updates.
But installing stock will not remove Camera2api also?
Click to expand...
Click to collapse
Ki, this is a great example of where one needs to look carefully at the command, and do some research. If you look closely the code says "boot" patched_boot. The point there is that it doesn't say "flash". Booting it won't flash it. That command will read it from your hard drive into rom memory of the device, and NOT write it to the flash memory of the device. I.E. The boot.img on the device will not change, so no reason to flash it again.
ki69 said:
2- I Have V9.6.13.0.ODIMIFE ( second september update) i try to seach for patch boot.img for A2 in were, but i only find the full stock image
in https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
Click to expand...
Click to collapse
Bring up all the topics in the MiA2 Guide(s) forum. At the top right is "Search This Forum". So... obviously... type in; patched_boot.
The first thread, OTA Jasmine (etc) has many posts with links to specific versions of (magisk) patched_boot images. (hint; search that thread also if you don't want to page through the posts!) - and don't forget to thank (use thank button!) cpkv5 for his efforts of extracting the boot.img and patching it for everyone, and making it available for easy download!
AsItLies said:
So to enable Cam2API w/out root, and continue to get OTA updates;
1) You need to be familiar with using ADB and FASTBOOT. Pls look at easily searchable documentation for them. Have them installed and usable on your pc / laptop. Try some of the commands out before using this guide, to get use to them / verify working.
2) You have to unlock the bootloader, which will wipe the device. It will also have to stay unlocked, which means your phone will be considered 'uncertified' in Play Store. Because we don't have NFC, and I don't do any banking apps on my phone... no worries for me.
3) You need the patched_boot.img for your current software version. The patched image (and the original boot image) are readily available. Just search the MiA2 forums and you'll find numerous links to new and previous images for the various software versions that have existed for our MiA2's.
So, you should already know how to enable adb and to OEM unlock in developer options (pls SEARCH if not!). So make an adb connection to do:
Code:
adb devices
The above will verify your pc sees the phone, obviously.
Code:
adb reboot bootloader
The above is an easy way to get to fastboot mode.
Code:
fastboot devices
The above will verify fastboot sees our device
Code:
fastboot oem unlock
The above unlocks the bootloader and wipes / reboots device. Again recheck to be sure in Dev options adb is on.
Code:
adb reboot bootloader
Above to get back to fastboot mode.
Code:
fastboot boot patched_boot.img
The above will now boot the device. Be sure the patched boot image is in the directory you are issuing the command from, and again, it needs to be the patched image that corresponds to the current software version you are using.
At this point, I'd recommend to not do anything with the device. It should be booted and appear normal. Back at our command prompt;
Code:
adb devices
Assuming we still see our device:
Code:
adb shell
The above will now put our command prompt into a linux shell, and then type the following:
Code:
setprop persist.camera.HAL3.enabled 1
and then
Code:
setprop persist.camera.eis.enable 1
At this point, it's about done. The above settings will get propagated to the appropriate tables after rebooting the device. They won't change system settings. So OTA updates should work.
Next, we just type 'exit' in the command prompt to exit the adb shell. Lastly we again issue 'adb reboot bootloader' and once we're back into fastboot, just issue 'fastboot reboot'.
That's it. We never flashed anything, only booted the patched image. So nothing really gets touched, that could inhibit OTA updates. When we do the reboot, it will read the original (untouched) boot image and boot as normal. This also keeps us from touching the other 'Slot' (not really needed). This is much simpler than using TWRP imho.
Click to expand...
Click to collapse
THANKS MATE, I REACHED TO FINAL STAGE & BOOTED IN TO THE PATCHED IMAGE BUT
AFTER putting command prompt into a linux shell it gives error failed to set property. please help i am awiting your reply.
Abbey Bhatt said:
THANKS MATE, I REACHED TO FINAL STAGE & BOOTED IN TO THE PATCHED IMAGE BUT
AFTER putting command prompt into a linux shell it gives error failed to set property. please help i am awiting your reply.
Click to expand...
Click to collapse
Yes I saw that Abbey, just updated the original post. At this point pls use the TWRP method I mentioned in similar thread. That works for sure.
I thought the Magisk patched boot image would have the same abilities (in this sense) as twrp, but it seems it does not. Will update if I find a solution.
Abbey Bhatt said:
THANKS MATE, I REACHED TO FINAL STAGE & BOOTED IN TO THE PATCHED IMAGE BUT
AFTER putting command prompt into a linux shell it gives error failed to set property. please help i am awiting your reply.
Click to expand...
Click to collapse
hey mate after rebooting, magisk appeared in app drawer, did i flashed patched boot image. by using this code? please advise
AsItLies said:
Ki, this is a great example of where one needs to look carefully at the command, and do some research. If you look closely the code says "boot" patched_boot. The point there is that it doesn't say "flash". Booting it won't flash it. That command will read it from your hard drive into rom memory of the device, and NOT write it to the flash memory of the device. I.E. The boot.img on the device will not change, so no reason to flash it again.
Click to expand...
Click to collapse
Yes, i didn´t read carefully, but my question has because i read that we need magisk after put patche boot.img, then enable, then remove magisk then flash stock boot.img
I read that you update the firt post informing of the need of that.
AsItLies said:
Bring up all the topics in the MiA2 Guide(s) forum. At the top right is "Search This Forum". So... obviously... type in; patched_boot.
The first thread, OTA Jasmine (etc) has many posts with links to specific versions of (magisk) patched_boot images. (hint; search that thread also if you don't want to page through the posts!) - and don't forget to thank (use thank button!) cpkv5 for his efforts of extracting the boot.img and patching it for everyone, and making it available for easy download!
Click to expand...
Click to collapse
Sorry, i only find this one:
https://forum.xda-developers.com/showpost.php?p=77295065&postcount=22
that have magisk, but with that like i said before i will mess with system/root, the thing i did´t want. so for me is not the path i want to take. I prefer the patch you give in:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
And because is a diferente path i think that that thread should be reopen by mods.
Abbey Bhatt said:
hey mate after rebooting, magisk appeared in app drawer, did i flashed patched boot image. by using this code? please advise
Click to expand...
Click to collapse
It shouldn't have flashed it, should have just booted it. I just uninstalled the magisk in app drawer myself. It looks as though a part of the magisk patched boot image installs that 'stub' part of magisk, to then allow a full install I'm sure. So that seems to happen whether you flash it or boot it.
ki69 said:
Yes, i didn´t read carefully,
Sorry, i only find this one:
Click to expand...
Click to collapse
You're looking in the ROM forums, not the indicated GUIDES forum.
AsItLies said:
It shouldn't have flashed it, should have just booted it. I just uninstalled the magisk in app drawer myself. It looks as though a part of the magisk patched boot image installs that 'stub' part of magisk, to then allow a full install I'm sure. So that seems to happen whether you flash it or boot it.
Click to expand...
Click to collapse
hey i am now wish to follow method presented in this thread
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
but at stage of fastboot getvar currdent-slot
it showing failed. no any partition showed
Abbey Bhatt said:
hey i am now wish to follow method presented in this thread
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
but at stage of fastboot getvar currdent-slot
it showing failed. no any partition showed
Click to expand...
Click to collapse
Not sure what's going on. When I do the same the result is:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
Did you flash it by mistake instead of boot it? Have you tried to do a 'fastboot set_active' ?
AsItLies said:
Not sure what's going on. When I do the same the result is:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
Did you flash it by mistake instead of boot it? Have you tried to do a 'fastboot set_active' ?
Click to expand...
Click to collapse
Humble request,
If you don't know about device or appropriate procedure don't post irrelevant things. As I know this device is tricky and more chances for hard brick if something goes wrong.
Abbey Bhatt said:
Humble request,
If you don't know about device or appropriate procedure don't post irrelevant things. As I know this device is tricky and more chances for hard brick if something goes wrong.
Click to expand...
Click to collapse
out and out flagrant request, if you can't follow directions, don't even try what is suggested.
There's no way anything I indicated would brick a phone. I've done it. Mine is not bricked. As indicated the setprop commands won't work with patched boot image. Then all you have to do is exactly what the procedure says and it's back to normal.
You're the reason people don't bother to post guides.
I do know about device and relevant procedure, it's not irrelevant. Your inability is what's irrelevant.
AsItLies said:
out and out flagrant request, if you can't follow directions, don't even try what is suggested.
There's no way anything I indicated would brick a phone. I've done it. Mine is not bricked. As indicated the setprop commands won't work with patched boot image. Then all you have to do is exactly what the procedure says and it's back to normal.
You're the reason people don't bother to post guides.
I do know about device and relevant procedure, it's not irrelevant. Your inability is what's irrelevant.
Click to expand...
Click to collapse
Hero how's your age how long been in this you are the people who doesn't know things and phones and wage all around being as op. Now cut this crappy out and first learn and then come for advice.
Abbey Bhatt said:
Hero how's your age how long been in this you are the people who doesn't know things and phones and wage all around being as op. Now cut this crappy out and first learn and then come for advice.
Click to expand...
Click to collapse
I'm sorry you screwed up your device. But it's not my fault. Nothing I indicated, if followed, would have caused that.
I'd suggest quitting the childish attempts at personal attacks. Your problems are not my fault.
@oka1 Hi again, sorry, this is the 2nd time! Please close this thread, and delete if possible. It' no longer provides any benefit.
Thanks! Won't happen again.
Here's the obligatory unroot/factory reset instructions, since the unlocked version is getting Pie next week
1) Since you need to unroot, you already have the firmware unzipped. Boot into fastboot (Vol Down + Power).
2) Type this in Terminal/Command Line on your computer:
fastboot flash boot boot.img
Click to expand...
Click to collapse
3) After you flash boot, type this in:
fastboot flashing lock
Click to expand...
Click to collapse
and it's just that easy
blackknightavalon said:
Here's the obligatory unroot/factory reset instructions
1) Since you need to unroot, you already have the firmware unzipped. Navigate to the root of the unzipped firmware directory and run the flash-all bat/sh.
2) Step 1 caused a bootloop, so I had to flash the unaltered boot and system images separately. The Treble partitions didn't give me any problems in this step
Click to expand...
Click to collapse
Would it be possible to get a step by step set of instructions?
kirschdog1 said:
Would it be possible to get a step by step set of instructions?
Click to expand...
Click to collapse
I should be detailed enough in my edit. Did it help?
blackknightavalon said:
I should be detailed enough in my edit. Did it help?
Click to expand...
Click to collapse
How do you individually flash image and boot?
kirschdog1 said:
How do you individually flash image and boot?
Click to expand...
Click to collapse
fastboot flash boot path/to/boot.img
what the hell do i do if fastboot is not detected on my razer phone 2!?!?!? i have reinstalled windows 5 times factory reset my razer phone 11 times and nothing is working
smithmunki said:
what the hell do i do if fastboot is not detected on my razer phone 2!?!?!? i have reinstalled windows 5 times factory reset my razer phone 11 times and nothing is working
Click to expand...
Click to collapse
Make doubly sure you have the fastboot drivers as detailed by Razer's flashing guide here: https://developer.razer.com/razer-p...0.2034022508.1549703537-1609614234.1544074767
If push comes to shove, you can perhaps use a Linux bootable image (Which I've found is many times more reliable).
smithmunki said:
what the hell do i do if fastboot is not detected on my razer phone 2!?!?!? i have reinstalled windows 5 times factory reset my razer phone 11 times and nothing is working
Click to expand...
Click to collapse
Use the latest platform-tools download from Google, unzip the file, put the ADB and Fastboot binaries in a different folder, then use this link (if you're on Windows) to get the command line to read ADB and Fastboot from any directory. If you're on Linux or Mac, drop the Unix binaries into /usr/bin then chmod their permissions to a+rwx to get the Terminal to read it from any folder
Instructions updated due to incoming Pie
does this remove the warning message at boot?
2me3 said:
does this remove the warning message at boot?
Click to expand...
Click to collapse
Yep!
CurtisMJ said:
Make doubly sure you have the fastboot drivers as detailed by Razer's flashing guide here: https://developer.razer.com/razer-p...0.2034022508.1549703537-1609614234.1544074767
If push comes to shove, you can perhaps use a Linux bootable image (Which I've found is many times more reliable).
Click to expand...
Click to collapse
use minimal adb installer. it fixed my fastboot issues...
CurtisMJ said:
Make doubly sure you have the fastboot drivers as detailed by Razer's flashing guide here: https://developer.razer.com/razer-p...0.2034022508.1549703537-1609614234.1544074767
If push comes to shove, you can perhaps use a Linux bootable image (Which I've found is many times more reliable).
Click to expand...
Click to collapse
lol i just ordered was looking and saw this aid well thats differnt glad i chooise to be smart . thats a diferent pollicy then samsung.
Where are you getting the stock boot.img ?
cory733 said:
Where are you getting the stock boot.img ?
Click to expand...
Click to collapse
Extract it from official factory image zip package
Just flashing boot.img won't allow OTA updates.
Better off following this one:
https://forum.xda-developers.com/razer-phone-2/how-to/razer-phone-2-unroot-step-step-t3896529