Related
C:\Users\Jason\Downloads>moto-fastboot devices
TA20705TET fastboot
C:\Users\Jason\Downloads>moto-fastboot erase recovery
erasing 'recovery'... FAILED (remote: (00180001))
C:\Users\Jason\Downloads>moto-fastboot flash recovery recovery-green-atrix3.2.im
g
sending 'recovery' (4780 KB)... OKAY [ 0.498s]
writing 'recovery'... FAILED (remote: (00180002))
C:\Users\Jason\Downloads>
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
Ok so I'm not sure why but it wouldnt let me type anymore on original post. Anyways, i am trying to flash using fastboot the atrix unlocked CWM. However when i type the commands i keep getting errors. Any ideas on what this is?
jason.hamilton said:
C:\Users\Jason\Downloads>moto-fastboot devices
TA20705TET fastboot
C:\Users\Jason\Downloads>moto-fastboot erase recovery
erasing 'recovery'... FAILED (remote: (00180001))
C:\Users\Jason\Downloads>moto-fastboot flash recovery recovery-green-atrix3.2.im
g
sending 'recovery' (4780 KB)... OKAY [ 0.498s]
writing 'recovery'... FAILED (remote: (00180002))
C:\Users\Jason\Downloads>
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
Ok so I'm not sure why but it wouldnt let me type anymore on original post. Anyways, i am trying to flash using fastboot the atrix unlocked CWM. However when i type the commands i keep getting errors. Any ideas on what this is?
Click to expand...
Click to collapse
Did you find your solution because I'm stuck at the same thing. I had touch screen issues after flashing a ROM. So I RSD back to stock but the touch screen problem persist. I read of the PDS fix in a post and I'm getting the same error but with trying to erase/write my PDS backup to the phone.
Make sure you put the image you are trying to flash in the same folder as your fastboot.
Vangelis13 said:
Make sure you put the image you are trying to flash in the same folder as your fastboot.
Click to expand...
Click to collapse
OP said it fails when trying to erase as well. So it's not file placement issues.
Speedily sent from CM7 Beta
Having same problem here... any solution?
why not just flash the one from rom manager then flash the zip to the one you want through that. thats what i did works perfect!
Hi,
I followed this article -> phandroid DOT com/2014/11/05/how-to-root-nexus-9/ (Sorry, new account, can't link) to the letter, and everything seemed to go well, until the last step where I ran "fastboot reboot" which returned "error: device not found" I thought nothing of this as there was a reboot option on the devices screen, so I rebooted, I get the google logo, followed by the four orbs, then it says "Optimising app x of 99" once this is done, its back to the orbs again and it just repeats.
I tried restoring to factory defaults from the recovery menu, that did nothing, then sometime after I noticed I actually cant turn the device off any more, if I hold the power button it turns off, but reboots instantly. I tried going through the steps again, but no luck, the only change was that I didn't have the error at the end, and the first Optimising dialogue said 104 apps, not 99, but all the rest afterwards have said 99.
I'm not sure what do do from here, any advice?
Here's my cmd output:
Code:
## First attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot bootloader
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
...
(bootloader) ability is 1
(bootloader) RUU_frame_buffer_enable_flag=0
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Unlock device successfully!
OKAY [ 23.489s]
finished. total time: 23.489s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot nexus9\inject.img
downloading 'boot.img'...
OKAY [ 0.783s]
booting...
OKAY [ 0.156s]
finished. total time: 0.939s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot nexus9\patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.541s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.798s]
finished. total time: 1.339s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
## Second attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
< waiting for device >
...
(bootloader) ability is 1
(bootloader) Device stete is unlock already
OKAY [ 0.141s]
finished. total time: 0.141s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
downloading 'boot.img'...
OKAY [ 0.749s]
booting...
OKAY [ 0.158s]
finished. total time: 0.908s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.539s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.787s]
finished. total time: 1.326s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot reboot
rebooting...
finished. total time: 0.066s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Try returning to stock and trying again. See method 2 of this, http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 9 using XDA Free mobile app
That root method is for the old 5.0 Android; it doesn't work anymore with 5.1.1. Go back to stock using jd1639's link, then run Chainfire's Auto-root and you should be good to go. Link is here: https://download.chainfire.eu/595/CF-Root/CF-Auto-Root/CF-Auto-Root-flounder-volantis-nexus9.zip. There's supposedly an update coming in the next week or so to fix the stagefright vulnerability, make sure you do NOT take it in case it does weird things that could cause you to lose root.
(I know it says Volantis and not flounder but the Nexus 9 is known by both names, just to keep things confusing)
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
TheShryke said:
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
Click to expand...
Click to collapse
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
bynarie said:
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
Click to expand...
Click to collapse
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
bynarie said:
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
Click to expand...
Click to collapse
Just take notice that this will wipe everything on your device, so make a backup first.
dictionary said:
Just take notice that this will wipe everything on your device, so make a backup first.
Click to expand...
Click to collapse
cobyman7035 said:
...
Click to expand...
Click to collapse
Yes, my apologies... I forgot to mention this. You will definitely want to pull any pictures or other files you might want to keep from the /sdcard partition. Or anything else because ALL DATA WILL BE WIPED.
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU? do i need to wipe dalvik or cache?
im installing that huge android SDK studio setup into my laptop for prep
cobyman7035 said:
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU?
Click to expand...
Click to collapse
Here > https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
ok i just unlocked my bootloader....so i rebooted in android again...i have to go back and enable usb debugging and developers again?
---------- Post added at 10:16 AM ---------- Previous post was at 10:01 AM ----------
when i typ adb reboot fastboot. ...my n9 reboots into the android o.s and NOT into fastboot?
---------- Post added at 10:23 AM ---------- Previous post was at 10:16 AM ----------
nm i installed and flash twrp and SU! i didn't do a dalvik cache wipe...is that ok? booting in android o/s again to setup!
my next step is to go unencrypted... don't wanna setup too many apps cuz its just gonna be all deleted again
Hi all,
I have an LG G5 H850. I'm trying to install TWRP using ADB. I've had it previously and it worked fine. I'm pretty sure the bootloader is unlocked. Anyway, when I do "fastboot flash recovery twrp-3.1.1.1-0-h850.img" I get the following output:
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.345s]
finished. total time: 0.781s
To me, that looks as though thats worked fine. Now when I try fastboot boot twrp-3.1.1.1-0-h850.img I get the following:
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.456s
Has anyone got any ideas on this?
Same here
I am having the same problem, please help
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
lywyn said:
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
Click to expand...
Click to collapse
Don't happen to know where I could get a rom that it would work with do you?
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Barsbeh said:
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Click to expand...
Click to collapse
That is the required way of doing it. You have to boot into recovery after flashing the recovery or it gets reset.
Hi,
Having a similar problem since trying to update my ROM ... and the Magisk install failed. Now I can only get to fastboot, can't get to recovery. And, tried this,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-h830.img
target reported max download size of 536870912 bytes
sending 'recovery' (18644 KB)...
OKAY [ 0.439s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.461s
Help!?! ... and thanks!
Note- This is tested on BKL-L09 C675 Indian variant and BKL-L09 C432 EU variant but will work on any variant of V10.
Hi Folks,
As I shared my experience on the issues I faced while moving back to stock from custom ROMs here , in this thread, I will share the detailed steps to go back to on stock avoiding any issues.
If you are on any custom ROM i.e. with Android/EMUI 8.1 TWRP backup will not work except BKL-L04. And only way that comes handy is fastboot (haven't tested the dload method myself yet as didnt had the SD card when I faced the issue but you can follow that, it will not break anything).
So before you start moving further to stock, please have these 3 files handy-
1- Stock recovery ramdisk
2- Stock boot ramdisk
3- system.img
Case 1- Custom ROM + Stock Boot + Stock Recovery (Applicable for new Open Kirin ROMs- RR and LOS which needs stock Ramdisk and if you are not using magisk)
On custom ROM, connect your phone with USB debugging enabled. (please make sure all the drivers are installed, it will already be as you may have the same which flashing the custom ROM)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Case 2- Custom ROM + Stock Recovery + Magisk (Root) ( applicable for New open Kirin ROMs- RR and LOS which needs stock ramdisk and if you are using magisk)
I forgot that I had magisk and had to gone through more issues as post boot, my IMEI was missing and no SIM service but if you have magisk installed, please be more careful and flash stock boot (attached for BKL-L09 EU version)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash the stock boot ramdisk.img as
Code:
fastboot flash ramdisk BKL-L09_ramdisk.img
Or fastboot flash ramdisk <ramdisk_File_Name>
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Case 3- Custom ROM + Custom Recovery + (Stock Ramdisk/ modified Ramdisk with Magisk) (Applicable for any custom ROM installed with TWRP and on stock boot or Magisk)
I forgot that I had magisk and had to gone through more issues as post boot, my IMEI was missing and no SIM service but if you have magisk installed, please be more careful and flash stock boot (attached for BKL-L09 EU version)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash the stock Recovery Ramdisk as
Code:
fastboot flash recovery_ramdisk recovery_ramdisk_bak.img
Or fastboot flash recovery_ramdisk <Recovery_File_Name>.img
If you have stock Boot Ramdisk, proceed to flashing system image and skip flashing the boot ramdisk.
If you have installed magisk, flash the stock boot ramdisk.img as
Code:
fastboot flash ramdisk BKL-L09_ramdisk.img
Or fastboot flash ramdisk <ramdisk_File_Name>
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Once booted on any of the case, you will be on full stock with unlocked bootloader. (you need to either dload to lock the bootlaoder or run the command - fastboot oem urelock <16 digit bootlaoder code> to relock the bootlaoder).
Working and tested myself and confirmed by one more user(Sandeep Dash). So, if you follow the steps correctly, you should not face any issue but in case you get stuck anywhere or not clear with steps and I will try to help as much as I can.
Attached files for BKL-L09 EU version. I will add other files as an when I get it.
Stock Ramdisk for BKL-L09 EU version - Thanks to @topjohnwu for sharing here
Stock Recovery for BKL-L04 EU version -I extracted this but thanks to @shihabsoft for sharing the step which helped me doing this.
Stock system image for BKL-L09 EU Version - Thanks to @surdu_petru for sharing here
Will these method work on bkl l09 model (indian variant)?
Really nice guide! Just one thing: Aren't you missing a
Code:
fastboot flash recovery_ramdisk <recovery_ramdisk_file>
step somewhere?
mondalakash said:
Will these method work on bkl l09 model (indian variant)?
Click to expand...
Click to collapse
Yes it will, 100%. The case 1 confirmation from Sandeep is for Indian variant only.
Smaehtin said:
Really nice guide! Just one thing: Aren't you missing a step somewhere?
Click to expand...
Click to collapse
Thanks. Nope buddy, as you already have stock recovery (for new Open Kirin ROMs) and only boot ramdisk was modified (for Magisk)
But yes, if you flashed twrp then you need it. Thanks for highlighting it, i will fix this.
shashank1320 said:
Yes it will, 100%. The case 1 confirmation from Sandeep is for Indian variant only.
Click to expand...
Click to collapse
Thanks for the confirmation...one question should i use the official twrp or the unofficial one for installing custom roms , decrypting internal storage and so on...
shashank1320 said:
Thanks. Nope buddy, as you already have stock recovery and only boot ramdisk was modified.
But yes, if you flashed twrp then you need it. Thanks for highlighting it, i will fix this.
Click to expand...
Click to collapse
Oh, I see. I was just a little confused about this part then:
shashank1320 said:
So before you start moving further to stock, please have these 3 files handy-
1- Stock recovery ramdisk
2- Stock boot ramdisk
3- system.img
Click to expand...
Click to collapse
mondalakash said:
Thanks for the confirmation...one question should i use the official twrp or the unofficial one for installing custom roms , decrypting internal storage and so on...
Click to expand...
Click to collapse
FOr me it was unofficial as I was using OpenKirin ROM as per requirement it should be stock recovery only.
for other ROMs or backup, you can try the unofficial one as official doesnt work on Android 8.1 and it will show random content or character in TWRP so you can not restore or say access the stuffs on your internal memory. I used the unofficial one given here
shashank1320 said:
FOr me it was unofficial as I was using OpenKirin ROM as per requirement it should be stock recovery only.
for other ROMs or backup, you can try the unofficial one as official doesnt work on Android 8.1 and it will show random content or character in TWRP so you can not restore or say access the stuffs on your internal memory. I used the unofficial one given here
Click to expand...
Click to collapse
Did you try dirty unicorn RC latest build?
Smaehtin said:
Oh, I see. I was just a little confused about this part then:
Click to expand...
Click to collapse
Fixed in OP. Added one more case for custom recovery users.
Thanks for valuable input buddy.
mondalakash said:
Did you try dirty unicorn RC latest build?
Click to expand...
Click to collapse
Nope buddy. Did you? Any feedback?
shashank1320 said:
Nope buddy. Did you? Any feedback?
Click to expand...
Click to collapse
using this method relocks bootloader?
mondalakash said:
using this method relocks bootloader?
Click to expand...
Click to collapse
No. It wont
Only dload or manual relock does
shashank1320 said:
No. It wont
Only dload or manual relock does
Click to expand...
Click to collapse
Thanks buddy
shashank1320 said:
No. It wont
Only dload or manual relock does
Click to expand...
Click to collapse
Same bootloader unlock can be used multiple times for unlocking? Any idea
mondalakash said:
Same bootloader unlock can be used multiple times for unlocking? Any idea
Click to expand...
Click to collapse
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
shashank1320 said:
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
Click to expand...
Click to collapse
Thanks buddy for these quick reply..I guess these recovery issues rom bootlopping issues will be fixed if huwaie gave l09 variants 8.1 update
---------- Post added at 07:07 PM ---------- Previous post was at 06:53 PM ----------
shashank1320 said:
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
Click to expand...
Click to collapse
Bro if flash system IMG of EU variant will this mean that I will on the EU update cycle?..I mean the dev pulled the system IMG from his V10 EU variant.…
mondalakash said:
Thanks buddy for these quick reply..I guess these recovery issues rom bootlopping issues will be fixed if huwaie gave l09 variants 8.1 update
---------- Post added at 07:07 PM ---------- Previous post was at 06:53 PM ----------
Bro if flash system IMG of EU variant will this mean that I will on the EU update cycle?..I mean the dev pulled the system IMG from his V10 EU variant.…
Click to expand...
Click to collapse
It will not allow to flash or wont boot.
You may need to flash the oeminfo file first and then system img. Had this been this easy, i would have rebranded to Indian version. See one of my debranding guide in signature
shashank1320 said:
It will not allow to flash or wont boot.
You may need to flash the oeminfo file first and then system img. Had this been this easy, i would have rebranded to Indian version. See one of my debranding guide in signature
Click to expand...
Click to collapse
Or I can pull my system ,boot,ramdisk by ADB since I haven't messed with the device apart from unlocking it
---------- Post added at 08:19 PM ---------- Previous post was at 08:11 PM ----------
mondalakash said:
Same bootloader unlock can be used multiple times for unlocking? Any idea
Click to expand...
Click to collapse
Using erecovery would be easier if u have fast internet and I heard it doesn't relock the bootloader
I mean the relock doesn't matter according to u as we can just use the code several times ...then I guess dload is easier only need a SD card...I mean it doesn't even matter which one of the scenarios we are in as mentioned by u in the OP.
mondalakash said:
Or I can pull my system ,boot,ramdisk by ADB since I haven't messed with the device apart from unlocking it
---------- Post added at 08:19 PM ---------- Previous post was at 08:11 PM ----------
Using erecovery would be easier if u have fast internet and I heard it doesn't relock the bootloader
I mean the relock doesn't according to u as we can just use the code several times ...then I guess dload is easier only need a SD card...I mean it doesn't even matter which one of the scenarios we are in as mentioned by u in the OP.
Click to expand...
Click to collapse
Erecovery download is difficult and give error many times.
Dload actually lock the bootloader and you will be on full stock.
In my case, i had to relock the bootloader as it was in bootloop and i knew relocking will give me erecovery to download.
NEW TWRP-3.2.3-0-scorpio(Mi note 2)
DOWNLOAD twrp-3.2.3-0-scorpio.img: https://dl.twrp.me/scorpio/twrp-3.2.3-0-scorpio.img
Regards
vcx77 said:
NEW TWRP-3.2.2-0-scorpio(Mi note 2)
DOWNLOAD twrp-3.2.2-0-scorpio.img: https://mega.nz/#!3BUkSSbT!r_okak_V21oNGpW7ArdiR2njcxR0VQtYOvY_b02xCu0
Regards
Click to expand...
Click to collapse
Why the hell should you put the mega link? Did you customized it? If not just give the official twrp link. Thx
https://dl.twrp.me/scorpio/
I can not install Android 8.0 Oreo with TWRP 3.2.2
After installing TWRP, Android is not restarted. It remains on the reset screen. How do I solve this problem?
NEW TWRP-3.2.3-0-scorpio(Mi note 2)
Alexurso said:
I can not install Android 8.0 Oreo with TWRP 3.2.2
After installing TWRP, Android is not restarted. It remains on the reset screen. How do I solve this problem?
Click to expand...
Click to collapse
Make sure you have flashed the correct oreo firmware first if coming from Nougat.
---------- Post added at 06:21 PM ---------- Previous post was at 06:06 PM ----------
Tried to flash the new recovery but it wont load. Phone just powers off. How can i roll back on previous version? Do i need adb and commands? Feel a little naked without a recovery
Edit : looks like the twrp file downloaded was incomplete so recovery was wiped. Tried to download it tru official site on my phone but was getting incomplete files everytime. Downloaded and flashed tru official twrp android app.
how to install this twrp from hermes?
vcx77 said:
NEW TWRP-3.2.3-0-scorpio(Mi note 2)
Click to expand...
Click to collapse
I have same proble on my mi note 2 8.0
---------- Post added at 07:44 PM ---------- Previous post was at 07:36 PM ----------
hello sir , i have error or says : C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery.img "C:\XiaoMi\MiPhoneManager\Download\twrp-3.2.2-0-scorpio.img" target reported max download size of 536870912 bytes sending 'recovery.img' (25240 KB)... OKAY [ 0.560s] writing 'recovery.img'... FAILED (remote: partition table doesn't exist) finished. total time: 0.584s
rah_asia said:
Why the hell should you put the mega link? Did you customized it? If not just give the official twrp link. Thx
https://dl.twrp.me/scorpio/
Click to expand...
Click to collapse
Valko67 said:
I have same proble on my mi note 2 8.0
---------- Post added at 07:44 PM ---------- Previous post was at 07:36 PM ----------
hello sir , i have error or says : C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery.img "C:\XiaoMi\MiPhoneManager\Download\twrp-3.2.2-0-scorpio.img" target reported max download size of 536870912 bytes sending 'recovery.img' (25240 KB)... OKAY [ 0.560s] writing 'recovery.img'... FAILED (remote: partition table doesn't exist) finished. total time: 0.584s
Click to expand...
Click to collapse
have you unlock the bootloader? did the downloaded file corrupted?
Yes bootloader is unlock , yes it is possible i downloaded from corrupt file after problems om my computer i haves to clean up all the mess i did )) yes this could happened when your knowledge is just to less , hahahaha , no madder , i have my Mi Note i preferred to work with , much easier to , hate this MTK , never would take again , it is not that it aint good , but so complicated to me than the Qualcomm Version's i enjoy your few words dear rah_asia , many thanks for that ; wish you sweet day Sir
what about twrp-3.4.0-1??