Related
Yesterday afternoon I upgraded my C6802/Z Ultra to 14.4.A.0.108 aka 4.4.4 and to persuade the Sony PC Companion program on windows to download the update, I used flashtool to lock my bootloader.
I've used the phone happily all day but I want to root it so I can use Titanium Backup Root/Pro, and hack the platform.xml file so as to allow full use of the microSDHC card.
I went to the service menu with the *#*#7378423#*#* and it says my bootloader is unlockable. I then put the phone into fastboot mode and ran the unlock sequence, but it failed the first time and reported device already unlocked.
I am using the tools from the full Android SDK
Code:
$ ./fastboot -i 0x0fce getvar version
< waiting for device >
version: 0.5
finished. total time: 0.003s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Command did not succeed)
finished. total time: 0.018s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
So then I tried to flash Jackie's 108 Dual Recovery kernel and it failed; I tried again as root just to make sure:
Code:
# ./fastboot flash boot ~/download/android/sony/xperia_z_ultra/C68xx_kernel_108_DualRec_Jackie099.bin
sending 'boot' (17728 KB)...
OKAY [ 0.557s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.560s
I get the same result if I use FlashTool's built-in tools. I have tweaked the phone's configuration to allow/disallow USB ADB debugging, allow/disallow side-loading, verification of apps etc etc, makes no difference.
I suspect that the phone is falsely reporting its bootloader is already unlocked, but where do I go from here?
thanks for any ideas
Paul
first off you may have lost your DRM keys by not doing a TA backup before unlocking the bootloader.
try and flash doomkernel's boot.img and see if that works? (unpack the zip)
I think I can remember someone not beinf able to flash jackie's .bin but doomlord's boot.img worked?
blueether said:
first off you may have lost your DRM keys by not doing a TA backup before unlocking the bootloader.
try and flash doomkernel's boot.img and see if that works? (unpack the zip)
I think I can remember someone not beinf able to flash jackie's .bin but doomlord's boot.img worked?
Click to expand...
Click to collapse
thanks, I'll give the doomkernel a go.
I lost my DRM keys the same day I received my XZU.. what you've never used you don't miss
Looks like the problem that I had:
http://forum.xda-developers.com/xperia-z-ultra/help/reunlocking-bootloader-error-t2808395
Root Lenovo Vibe P1M
This guide will help you to root Lenovo Vibe P1M without bricking it.
Check this first.
Take backup of your important data at safe place.
Device must adequately charged.
Install USB drivers of your device PC.
Enable USB Debugging from Developer Options in Settings.
Enable Unknown Sources from Security in Settings.
Install TWRP
Follow the steps below.
Download ADB fastboot drivers [from here] and install it on PC.
Download TWRP recovery for Lenovo Vibe P1M from here.
Extract the zip file and find recovery.img file. Copy this file to your PC where you installed ADB fastboot drivers.
Now open Command Prompt.
Go to directory where you have installed ADB fastboot drivers.
Now enter the following commands.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery.img [B]OR[/B] fastboot boot recovery.img
fastboot reboot
After first command your device will reboot in fastboot mode. The second command will flash recovery image on your device. The third command will reboot your phone.
Now TWRP recovery is get installed on your Lenovo Vibe P1M.
Root Lenovo Vibe P1M
After installing TWRP on Lenovo Vibe P1M, follow the given steps to root it.
Download SuperSU from here.
Place the downloaded SuperSu zip in your extetnal SD card.
Now go to command prompt again and type the following command.
adb reboot recovery
Now your device will reboot in recovery mode. Flash supersu.zip from TWRP.
Reboot your device.
process completed.
Warning: I am not responsible if anything goes wrong, bricked device.
Does this method work with firmware ver S029. I am already rooted with kingoapp. But Flashfire app shows boot loader partitions to be protected . I suspect bootloader to be Locked. In such senario will this method work or will it brick my phone.
I also have another question if flash TWRP recovery on locked bootloader anyway, will it only fail to boot into recovery mode or will device fail to boot normally altogether
and it does boot normally then if i reflash stock recovery back on locked bootloader will that fix the issue of booting into recovery mode.
junkhunzai said:
Does this method work with firmware ver S029. I am already rooted with kingoapp. But Flashfire app shows boot loader partitions to be protected . I suspect bootloader to be Locked. In such senario will this method work or will it brick my phone.
I also have another question if flash TWRP recovery on locked bootloader anyway, will it only fail to boot into recovery mode or will device fail to boot normally altogether
and it does boot normally then if i reflash stock recovery back on locked bootloader will that fix the issue of booting into recovery mode.
Click to expand...
Click to collapse
This method will work ver S029 also. To flash recovery you need unlocked bootloader.
Well, I'm getting an error - (remote: not allowed), every time I try to boot the recovery.
ᵀᴴᴱ HUИTΞR said:
Well, I'm getting an error - (remote: not allowed), every time I try to boot the recovery.
Click to expand...
Click to collapse
Have you unlocked it?
1st command may be this
Fastboot oem unlock
Sent from my Redmi Note 3 using XDA-Developers mobile app
prajj said:
Have you unlocked it?
1st command may be this
Fastboot oem unlock
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 7.103s]
finished. total time: 7.105s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
C:\Program Files (x86)\Minimal ADB and Fastboot>
P.S: And now I have reboot loop... Reboot> Logo> Reboot > Logo...to infinity with a non-removable battry - just perfekt
P.S.: I can't get to recovery anymore...
ᵀᴴᴱ HUИTΞR said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 7.103s]
finished. total time: 7.105s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
C:\Program Files (x86)\Minimal ADB and Fastboot>
P.S: And now I have reboot loop... Reboot> Logo> Reboot > Logo...to infinity with a non-removable battry - just perfekt
P.S.: I can't get to recovery anymore...
Click to expand...
Click to collapse
Have you extracted the zip file and copied recovery.img file from zip to your PC where you installed ADB fastboot drivers?? And use following command to flash recovery.img
Code:
fastboot flash recovery.img
Also take a look at this thread for reference --> http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
bravonova said:
Have you extracted the zip file and copied recovery.img file from zip to your PC where you installed ADB fastboot drivers?? And use following command to flash recovery.img
Code:
fastboot flash recovery.img
Also take a look at this thread for reference --> http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
Click to expand...
Click to collapse
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Nabil99 said:
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Click to expand...
Click to collapse
Hey bro use flashify app to flash recovery through phone...
Stock Recovery backup deleted.
Hi, my vibe p1m now is running twrp recovery, but i accidentally deleted my backup of stock recovery yeah i know im dumb, but if someone can provide a link.. please help me....
Can anyone share a boot.img plz.? I forgot to back up mine.. Thanks a ton!
mikkel19 said:
Hi, my vibe p1m now is running twrp recovery, but i accidentally deleted my backup of stock recovery yeah i know im dumb, but if someone can provide a link.. please help me....
Click to expand...
Click to collapse
http://firmwarefile.com/lenovo-vibe-p1m/
This link gives you stock firmware. I too have deleted my backup but used it to get it back. But however I faced problems like boot loop many times and even IMEI turned 000000000000000 for both sim slots but still it was recovered by using "MTK Engineering Mode" app which you can get from "Play Store" and follow the following steps.
Step 1) Open the the MTK Engineer mode app and swipe left side to go into Connectivity.
Step 2) In the Connectivity click on the CDS information.
Step 3) And then Tap on the Radio information.
Step 4) Then you will be able to see Phone 1 and Phone 2
Step 5) Just click on Phone 1 first. then enter the Command as AT +EGMR=1,7,"your first imei" (Put a Space between AT and +, Like AT +EGMR=1,10,"your imei") and then tap on SEND AT COMMAND it will show you that command sent,
Step 6) Now press back button and Tap on Phone 2 (if you have a Dual Sim phone) and Type AT +EGMR=1,10,"second imei" and tap on send at command.
Step 7) Now Just Restart you device and enjoy now Sim Card will Display the Network in the status bar.
And you are done!!!!!!!!!
You can see your IMEI by pressing *#06#
If you face boot loop problems again and again please inform me.
Just the problems I faced. They are the solutions. Please do reply to this message.
Okay thank you. I will try it. Thanks a lot
mikkel19 said:
Okay thank you. I will try it. Thanks a lot
Click to expand...
Click to collapse
Please do ask if you get any problems coz my device is same and I've tried with 3-4 different ROMs including stock so can help you with many problems.
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
You can also root Lenovo Vibe P1m using SP Flash Tool. I've done the same and changed recovery from stock to TWRP easily without using any commands. Device works flawlessly and currently have installed MiUI 8 custom ROM.
mikkel19 said:
Okay thank you. I will try it. Thanks a lot
Click to expand...
Click to collapse
Oh and one more thing that zip file isn't for installing. You have to first extract it then you will get the instructions for flashing stock ROM. Happy flashing!!!!!
Sharath Guddad said:
Oh and one more thing that zip file isn't for installing. You have to first extract it then you will get the instructions for flashing stock ROM. Happy flashing!!!!!
Click to expand...
Click to collapse
Thank you, My vibe p1m is running on stock rom now, many thanks )))
Nabil99 said:
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Click to expand...
Click to collapse
Fastboot command given for flash recovery is wrong.
The right command is
Fastboot flash recovery recovery.img
Second recovery is the name of your recovery. If your recovery name is twrp then command is
Fastboot flash recovery twrp.img
Guys... If your device is new version (s036 pre installed) , use TWRP3 only.
Ashwinrg said:
Fastboot command given for flash recovery is wrong.
The right command is
Fastboot flash recovery recovery.img
Second recovery is the name of your recovery. If your recovery name is twrp then command is
Fastboot flash recovery twrp.img
Click to expand...
Click to collapse
C:\Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (10642 KB)...
OKAY [ 1.063s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 1.078s
cuci8202 said:
C:\Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (10642 KB)...
OKAY [ 1.063s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 1.078s
Click to expand...
Click to collapse
use TWRP3 only.. or install via sp flash tool.. it's very easy.. check this.. u can also get TWRP 3 here..
http://forum.xda-developers.com/android/general/how-to-install-twrp-root-lenovo-vibe-t3538088/page1
I'm familiar with ADB and fastboot and all the rooting stuff, but I have no idea how to create a TWRP build for this device. Someone had a similar problem with a similar model (U673C) here: https://forum.xda-developers.com/android/help/umx-u673c-root-t3719328 . If I can post my stock recovery (which is extracted through fastboot, right?), could someone make a TWRP build from it? Then I could just send over magisk or something to remove all the bloatware, right?
Sorry for being a pain. Thanks for your time.
EDIT: This phone has an unlockable bootloader and I'm already in fastboot, if that helps.
EDIT 2: Running "fastboot oem unlock" gives me
...
FAILED (remote: unknown command)
finished. total time: 0.002s
Am I boned?
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
Hello,
- In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
Hello,
- In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
Hi, thanks for your fast answer!
fastboot oem get-build-number
Code:
(bootloader) :System 8.0.0.046(09B8)
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem get-product-model
Code:
(bootloader) ANE-LX1
OKAY [ 0.011s]
finished. total time: 0.011s
fastboot getvar vendorcountry
Code:
vendorcountry: ti/it
finished. total time: 0.012s
fastboot oem oeminforead-CUSTOM_VERSION
Code:
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.019s
fastboot oem oeminforead-SYSTEM_VERSION
Code:
(bootloader) :ANE-LX1 8.0.0.151(C55)
OKAY [ 0.013s]
finished. total time: 0.014s
I don't know why but the CUSTOM_VERSION reading failed...
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
-Alf- said:
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
Click to expand...
Click to collapse
I think it's C55 , correct me if I'm wrong...
-Alf- said:
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
Click to expand...
Click to collapse
I tried, but doesn't work at all...
-Alf- said:
I think it's C55 , correct me if I'm wrong...
Click to expand...
Click to collapse
Yeah, it is C55. I don't know what to do anymore
andreasaracino said:
I tried, but doesn't work at all...
Yeah, it is C55. I don't know what to do anymore
Click to expand...
Click to collapse
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
I did this once to my kiwi (5x) then it went totally blank when i tried flashing an Huawei related system flashing tool. Do not try that.
-Alf- said:
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
Click to expand...
Click to collapse
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
andreasaracino said:
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
Click to expand...
Click to collapse
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
-Alf- said:
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
Click to expand...
Click to collapse
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
andreasaracino said:
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Click to expand...
Click to collapse
andreasaracino said:
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
Click to expand...
Click to collapse
then it is not FULLOTA-MF but Service ROM, bro ...okay, it doesn't matter now.
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