Related
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,
Firstly, excuse my english...
I'm in OOS in version 2.1.3 (yea, old) with custom recovery and root. I have followed this guide : http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
I have recently decided to upgrade in OOS 3.x and suprised...... Impossible to boot on TWRP.
$ adb reboot bootloader
Click to expand...
Click to collapse
→ fastboot mode OK
$ sudo fastboot devices
[sudo] Mot de passe de torlik :
4c6f1504 fastboot
Click to expand...
Click to collapse
detected, nice !
$ sudo fastboot boot twrp-2.8.7.0-onyx_f2fs_r9.img
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.606s
Click to expand...
Click to collapse
WOOT ?
$ sudo fastboot flash recovery twrp-2.8.7.0-onyx_f2fs_r9.img
target reported max download size of 1073741824 bytes
sending 'recovery' (12130 KB)...
OKAY [ 0.684s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.686s
Click to expand...
Click to collapse
WHAT ?
With VOL- (+) POWER, I boot in Oxygen Recovery, nothing else.
$ sudo fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
(bootloader) Device unlocked: false
How my unlock has been lost ? My phone is yet rooted. SuperSu works correctly.
Can you tell me how it is possible to lost twrp ? I have never upgrade since my unlock.
And now, my only solution is to do a 'fastboot oem unlock' and lost my data ?
Thank you
Not sure whats going on there but easy way is to fastboot flash old stock recovery. Then install 3.1.3 with no problems. Rename file and delete .tar .
Your device bootloader is locked.
Why do you want to flash old TWRP.
To install OOS 3.1.3, you should better flash old OOS stock recovery.
But not sure it wil work.
Now, when you try to reboot recovery, on what recovery are you?
Always TWRP? None?
You should flash Oxygen one, so you can try to flash OOS 2.2.3 full rom zip to start.
Kéno40 said:
Your device bootloader is locked.
Why do you want to flash old TWRP.
To install OOS 3.1.3, you should better flash old OOS stock recovery.
But not sure it wil work.
Now, when you try to reboot recovery, on what recovery are you?
Always TWRP? None?
You should flash Oxygen one, so you can try to flash OOS 2.2.3 full rom zip to start.
Click to expand...
Click to collapse
Thanks for answers.
The issue is exactly that:
"Now, when you try to reboot recovery, on what recovery are you?"
I boot on stock recovery... oxygen recovery instead of twrp. Why?? How??
However I had flash my recovery with twrp last months ago and root my phone.
My problem is I do not want to lost my data... Indeed I can unlock again bootloader but all data will be lost.
How could you flash TWRP if your bootloader is locked? :-S
I don't think you ever get re-locked upon any update..
And yes, you probably have to unlock boot and lose all your user data.. Unless you don't have a backup handy of course :I
You can flash oos 3.1.1 through stock recovery no matter if your bootloader locked or unlocked.
Just download the full rom zip of oos 3.1.1 and place this zip in internal storage and flash with stock recovery. After installing oos3.1.1 you can backup your data and after that you have to go to the developer settings and allow the OEM Unlocking and now you can follow same procedure to unlock bootloader.
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
prasannazx said:
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
Click to expand...
Click to collapse
Use mega unbrick guide if you tried all other procedure.
I was caught up in the same situation. Follow the mega unbrick guide and your phone will be back to normal.
link to the mega unbrick please..
Asmmahin said:
link to the mega unbrick please..
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Is mega unbrick or hard unbrick is same ?
amgh said:
Is mega unbrick or hard unbrick is same ?
Click to expand...
Click to collapse
Both are same.some call it hard unbrick or some mega that's it.
1.) Make sure driver signature enforcement is disabled.
2) Download this :- http://www.mediafire.com/download/4aqwyi3g1d6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
4) press vol up button for 10s and plug it in pc keeping pressed
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
5) now flash it with msmtool u can downloa th 47mb one in comments
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6) the phone now should have the stock recovery
---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------
sabrinano24 said:
1.) Make sure driver signature enforcement is disabled.
2) Download this :- http://www.mediafire.com/download/4aqwyi3g1d6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
4) press vol up button for 10s and plug it in pc keeping pressed
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
5) now flash it with msmtool u can downloa th 47mb one in comments
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6) the phone now should have the stock recovery
Click to expand...
Click to collapse
ps= remove the space in the frist link
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
did you install a rom after the fix ?
After fix, it's the official ROM so déveloper > OEM and USB debuging
adb reboot bootloader
Adb oem unlock ans After the command i write
prasannazx said:
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
Click to expand...
Click to collapse
That is because the kernel and boot loader used for 14.1 is different you need to update the kernel.
Follow Mega unbrick guide carefully to unbrick the phone.
sabrinano24 said:
did you install a rom after the fix ?
Click to expand...
Click to collapse
After the fix, i've OOS, and that all.
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
I had same issue you need to flash different TWRP. If your on 2.X.X TWRP 3.0.2 . If you have updated to 3.X.X then 3.0.3. If you have issues with 3.0.3 you can try twrp 3.0.2-0 or bluesparks 3.0.2-1 V41.
just flash the arsenic-kernel everything will be fine.. https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
The problem is not the kernel but the bootloader so how to change/update recovery?
Bjr49000 said:
The problem is not the kernel but the bootloader so how to change/update recovery?
Click to expand...
Click to collapse
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
I used to have this problem. You need to flash the new bootloader, sometimes updates and whatnot doesn't flash it for you. If the zip doesn't work you can try finding the fastboot partition image and flashing to aboot (instead of fastboot flash recovery recovery.img when flashing a twrp build for example, it would be fastboot flash aboot emmc_appsboot.mbn). There was a post on the oneplus forums where the files could be found, just google dtb not found error.
I tried to install lineage OS 17.1 on a Moto-Z with Android 6.0.1, and failed.
Here is one error I'd like to solve - this command:
fastboot flash recovery twrp-3.3.1-0-griffin.img
Results in:
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20536 KB) OKAY [ 0.443s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.481s]
Finished. Total time: 0.932s
twrp-3.3.1-0-griffin.img is the lastest image, from here.
The same error appears when I try to flash the lineage recovery:
fastboot flash recovery lineage-17.1-20201211-recovery-griffin.img
So what is wrong here?
I've been flashing a Moto e5 Plus today, and the ADB messages were the same, except without the "has slot" line. I think they are standard.
I also had trouble getting TWRP to "stick". What ended up working was booting into the bootloader, flashing TWRP and instead of rebooting I selected "recovery" with the volume buttons.
The TWRP site says this in its instructions:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
but holding Power + Volume Up after reboot didn't seem to work for me.
mfs-ness said:
What ended up working was booting into the bootloader, flashing TWRP ...
Click to expand...
Click to collapse
How did you flash TWRP - from the bootloader?
Or from the PC via fastboot - in which case there is always the above error, not just with TWRP images.
This is how I flashed TWRP from a linux desktop:
Code:
./adb -d reboot bootloader
sudo ./fastboot flash recovery ~/Downloads/twrp-3.4.0-0-hannah.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (19798 KB) OKAY [ 0.795s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.552s]
Finished. Total time: 1.352s
The first line results in the screen with the open-chested android. Then I ran the fastboot command. Then I selected "recovery mode" on the phone.
mfs-ness said:
This is how I flashed TWRP from a linux desktop:
...
Click to expand...
Click to collapse
Not different from my technique.
So we seem to have different conditions on the phone, firmware, whatever.
I am new here and this was my first time actually trying any of this. I have my bootloader code, if that helps.
Phone turns on to erecovery mode if powered on normally. Running erecovery downloaded and installed RNE-L21 8.0.0.355(C185). It then asked me to Factory reset, after which it booted back in to erecovery. I can put phone in FASTBOOT&RESCUE MODE by plugging it in to PC and holding power + vol. down.
About Phone
-code
DC-unlocker:
manufacturer - Huawei phones
model - Huawei phone in fastboot mode
Found Phone : RNE-L21
Model : Huawei phone in fastboot mode
IMEI : 868859036054492
Serial NR. : FFY5T18224032295
Firmware : RNE-L21 8.0.0.355(C185
IMEI1:868859036074508
FB LockState: LOCKED
I wanted to downgrade from Oreo to Nougat.
To unlock bootloader, I used Potatonv:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
I installed the TWRP in this post:
TWRP For Mate 10 lite 8.0 Oreo Version For RNE-L21C185
Here is twrp for HUAWEI MATE 10 LITE. Who want? Comment Here. :p
forum.xda-developers.com
I booted in to TWRP with
-code
adb reboot recovery
I made a backup using TWRP but I lost it and couldn't make another one because of some error in TWRP.
I then installed magisk .zip file through TWRP.
The phone would boot in TWRP no matter which option I chose in the Reboot menu of TWRP. Being really impatient, I decided to flash another version of TWRP on recovery partition, with SD card, through TWRP itself. I got this 2nd TWRP from:
How to Install TWRP Recovery and Root Huawei Mate 10 Lite
In this article, we will guide you on how to root Huawei Mate 10 Lite and Install TWRP Recovery.
clickitornot.com
The new TWRP doesn't work and phone does not show bootloader unlocked warning anymore. Upon rebooting after new TWRP, phone showed this error first few times.
I'm not really sure what to do but I figured I'd run some commands that might help someone figure out what I should do.
fastbootoem get-product-model:
(bootloader) RNE-L21
OKAY [ 0.025s]
finished. total time: 0.026s
fastboot getvar vendorcountry:
vendorcountry: hw/meafnaf
finished. total time: 0.025s
fastboot oem get-build-number:
(bootloader) :RNE-L21 8.0.0.355(C185)
OKAY [ 0.026s]
finished. total time: 0.027s
fastboot getvar rescue_enter_recovery:
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.063s
fastboot oem oeminforead-SYSTEM_VERSION:
(bootloader) :RNE-L21 8.0.0.348(C185CUSTC185D1)
OKAY [ 0.031s]
finished. total time: 0.031s
I believe the rom for my phone is
RNE-L21 8.0.0.348(C185CUSTC185D1)I have downloaded it from https://gsmfreehelperteam.blogspot.com/2020/04/rne-l21-800348c185custc185d1-file-by.html but I really don't know what to do with it and I don't want to mess it up any further. Sorry for the long read, any help would be great.
brokenpotato said:
Upon rebooting after new TWRP, phone showed this error first few times.
Click to expand...
Click to collapse
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
brokenpotato said:
I wanted to downgrade from Oreo to Nougat
Click to expand...
Click to collapse
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
-Alf- said:
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
Click to expand...
Click to collapse
"fastboot flash recovery RECOVERY_RAMDISK330.img" gives:
target reported max download size of 471859200 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.055s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.067s
brokenpotato said:
Command not allowed
Click to expand...
Click to collapse
= Locked bootloader or FRP lock
-Alf- said:
= Locked bootloader or FRP lock
Click to expand...
Click to collapse
IT does say "FRP Unlock" in red on fastboot&rescue screen. Should i try fastboot oem unlock?
brokenpotato said:
Should i try fastboot oem unlock?
Click to expand...
Click to collapse
Why not?
Fastboot oem unlock *************** worked, the phone booted up in to android and is working normally. Thank you so much!!
brokenpotato said:
Fastboot oem unlock *************** worked, the phone booted up in to android and is working normally. Thank you so much!!
Click to expand...
Click to collapse
No problem.
-Alf- said:
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
Click to expand...
Click to collapse
When trying to flash the TWRP, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'recovery' (24790 KB)...
OKAY [ 0.794s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.809s
brokenpotato said:
fastboot flash recovery TWRP-oreo-smart.img
Click to expand...
Click to collapse
Read carefully.
brokenpotato said:
When trying to flash the TWRP, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'recovery' (24790 KB)...
OKAY [ 0.794s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.809s
Click to expand...
Click to collapse
Just realized I had to flash twrp on recovery_ramdisk and not on recovery. It works like a charm