Related
OK people, so i bring another (hopefuly helpful to someone) exprecience with BOOTLOOP.
Problem: I had stock B200 firmware (5.0.2). I wanted to try beta update of marshmallow, so i decided to try it. It was told me i can update directly from B200 one, so i just copied update.zip to DLOAD folder, went to settings and run local update. The phone restarted, booted into recovery and started flashing. BUT, i forgot that i had custom TWRP recovery and not stock one, anyway, TWRP started flashing the zip, error after error, but some files still copied and bricked the phone. I couldnt start any recovery, just fastboot and some mode that should download online file and reflash system, but it would be very easy so it has error too.
Here is what i did:
1. Download the update zip of marshmallow you were trying to flash and unpack UPDATE.APP
2. Extrac: RECOVERY.img and BOOT.img
3. set phone to fastboot mode and flash extracted BOOT.img, then RECOVERY.img
4. after that, you need somehow copy whole B200 firmware into sdcard / dload folder (i took micro sd and inserted into another phone, then copied it)
5. now you can boot into force flashing mode (power + volume up + volume down buttons) and it automaticaly reflash whole system.
6. after reboot you can use your P8
OK, i got it work!
00471 said:
OK, i got it work!
Click to expand...
Click to collapse
Great to hear that, can you please answer how you did it,as this might help someone having the same problem
Salman Al-Badgail said:
Great to hear that, can you please answer how you did it,as this might help someone having the same problem
Click to expand...
Click to collapse
of course, i wanted to do it but didnt have time, ill update OP with solution
00471 said:
of course, i wanted to do it but didnt have time, ill update OP with solution
Click to expand...
Click to collapse
Thanks :good:
00471 said:
OK people, so i bring another (hopefuly helpful to someone) exprecience with BOOTLOOP.
Problem: I had stock B200 firmware (5.0.2). I wanted to try beta update of marshmallow, so i decided to try it. It was told me i can update directly from B200 one, so i just copied update.zip to DLOAD folder, went to settings and run local update. The phone restarted, booted into recovery and started flashing. BUT, i forgot that i had custom TWRP recovery and not stock one, anyway, TWRP started flashing the zip, error after error, but some files still copied and bricked the phone. I couldnt start any recovery, just fastboot and some mode that should download online file and reflash system, but it would be very easy so it has error too.
Here is what i did:
1. Download the update zip of marshmallow you were trying to flash and unpack UPDATE.APP
2. Extrac: RECOVERY.img and BOOT.img
3. set phone to fastboot mode and flash extracted BOOT.img, then RECOVERY.img
4. after that, you need somehow copy whole B200 firmware into sdcard / dload folder (i took micro sd and inserted into another phone, then copied it)
5. now you can boot into force flashing mode (power + volume up + volume down buttons) and it automaticaly reflash whole system.
6. after reboot you can use your P8
Click to expand...
Click to collapse
Tried exactly as you say, STILL Software install failed.
Can you send me link which system you are trying to flash? Maybe you have just bad package
Odoslané z HUAWEI GRA-L09 pomocou Tapatalku
Can't get it to work
00471 said:
OK people, so i bring another (hopefuly helpful to someone) exprecience with BOOTLOOP.
Problem: I had stock B200 firmware (5.0.2). I wanted to try beta update of marshmallow, so i decided to try it. It was told me i can update directly from B200 one, so i just copied update.zip to DLOAD folder, went to settings and run local update. The phone restarted, booted into recovery and started flashing. BUT, i forgot that i had custom TWRP recovery and not stock one, anyway, TWRP started flashing the zip, error after error, but some files still copied and bricked the phone. I couldnt start any recovery, just fastboot and some mode that should download online file and reflash system, but it would be very easy so it has error too.
Here is what i did:
1. Download the update zip of marshmallow you were trying to flash and unpack UPDATE.APP
2. Extrac: RECOVERY.img and BOOT.img
3. set phone to fastboot mode and flash extracted BOOT.img, then RECOVERY.img
4. after that, you need somehow copy whole B200 firmware into sdcard / dload folder (i took micro sd and inserted into another phone, then copied it)
5. now you can boot into force flashing mode (power + volume up + volume down buttons) and it automaticaly reflash whole system.
6. after reboot you can use your P8
Click to expand...
Click to collapse
I did exactly the same mistake as you and the same steps to fix it. I flashed those 2, places the update.app + the other files to dload and then 3 button update and I got to the huawei music and animation. Then it restarted.
mega:///#!IEhCRaRR!GT6Ds9EywDoW5Dd8ZdKVesyQUItbiSwCPaapFhAenEY
is the file I use.
Is there any advice you could give?
T1mb3 said:
I did exactly the same mistake as you and the same steps to fix it. I flashed those 2, places the update.app + the other files to dload and then 3 button update and I got to the huawei music and animation. Then it restarted.
mega:///#!IEhCRaRR!GT6Ds9EywDoW5Dd8ZdKVesyQUItbiSwCPaapFhAenEY
is the file I use.
Is there any advice you could give?
Click to expand...
Click to collapse
Actually i do, i bricked my phone one after that later, and this helped: http://www.huawei-info.de/p8-mm-rollback flash B300 rollback zip with 3 buttons combination, then flash B200 full zip. I hope it will help :good:
00471 said:
Actually i do, i bricked my phone one after that later, and this helped: xx flash B300 rollback zip with 3 buttons combination, then flash B200 full zip. I hope it will help :good:
Click to expand...
Click to collapse
I'll give it a try.
Thank you!
It says Software install failed when trying to flash rollback.. I'll try to install the b200 full zip now
T1mb3 said:
I'll give it a try.
Thank you!
It says Software install failed when trying to flash rollback.. I'll try to install the b200 full zip now
Click to expand...
Click to collapse
okay, do this:
in fastboot flash those files from Marshmallow B313: recovery.img, boot.img and cust.img
then try to flash rollback, the CUST.img is very important to flash
00471 said:
okay, do this:
in fastboot flash those files from Marshmallow B313: recovery.img, boot.img and cust.img
then try to flash rollback, the CUST.img is very important to flash
Click to expand...
Click to collapse
There is no cust in the update.app
T1mb3 said:
There is no cust in the update.app
Click to expand...
Click to collapse
Okay have chaos in this all files, maybe it was B200 cust, or B170 cust, try one of them, but boot.img and recovery.img must be from Beta
00471 said:
Okay have chaos in this all files, maybe it was B200 cust, or B170 cust, try one of them, but boot.img and recovery.img must be from Beta
Click to expand...
Click to collapse
I think I'll get it working as soon as I get a large enough sdcard..
Thanks for your help!
I'll comment here if I face more problems
T1mb3 said:
I think I'll get it working as soon as I get a large enough sdcard..
Thanks for your help!
I'll comment here if I face more problems
Click to expand...
Click to collapse
No problem, let me know if you solve it
00471 said:
No problem, let me know if you solve it
Click to expand...
Click to collapse
Awesome, I got it working.
I used b170 cust, if someone has trouble.
Thank you so much!
T1mb3 said:
Awesome, I got it working.
I used b170 cust, if someone has trouble.
Thank you so much!
Click to expand...
Click to collapse
Glad it worked!
Offtopic: if i root after reverting to 5.0.1 using twrp should i then flash stock recovery from b200 or b313 or which one? I mean when the non beta marshmallow update is available
Qqman55 said:
Offtopic: if i root after reverting to 5.0.1 using twrp should i then flash stock recovery from b200 or b313 or which one? I mean when the non beta marshmallow update is available
Click to expand...
Click to collapse
If you are on 5.0.1 with root and twrp then you are good, or do you want try BETA? if yes then you need stock recovery flash before flashing beta
00471 said:
OK people, so i bring another (hopefuly helpful to someone) exprecience with BOOTLOOP.
Problem: I had stock B200 firmware (5.0.2). I wanted to try beta update of marshmallow, so i decided to try it. It was told me i can update directly from B200 one, so i just copied update.zip to DLOAD folder, went to settings and run local update. The phone restarted, booted into recovery and started flashing. BUT, i forgot that i had custom TWRP recovery and not stock one, anyway, TWRP started flashing the zip, error after error, but some files still copied and bricked the phone. I couldnt start any recovery, just fastboot and some mode that should download online file and reflash system, but it would be very easy so it has error too.
Here is what i did:
1. Download the update zip of marshmallow you were trying to flash and unpack UPDATE.APP
2. Extrac: RECOVERY.img and BOOT.img
3. set phone to fastboot mode and flash extracted BOOT.img, then RECOVERY.img
4. after that, you need somehow copy whole B200 firmware into sdcard / dload folder (i took micro sd and inserted into another phone, then copied it)
5. now you can boot into force flashing mode (power + volume up + volume down buttons) and it automaticaly reflash whole system.
6. after reboot you can use your P8
Click to expand...
Click to collapse
can you upload stock recovery of b313?
Hi there.
I have been flashing ROMS since ICS (Ice Cream Sandwich) but for the last 18 months I have been a bit disconnected from it.
I am also new to everything Huawei.
I find a lot of times people referring to the eRecovery.
Where does this terminology (eRecovery) differ from the normal recovery, be it stock recovery or TWRP?
Is this eRecovery a Huawei thing or am I missing something?
Thanks in advance.
It is nothing to really worry or even think about. I don't think you can get rid of it or even if you could there is no reason. It's just second recovery which does a different things than the normal stock recovery. I think the eRcovery is needed for the stock update, but normal recovery isn't(not completely sure about this).
It is just good to know that device also has eRecovery, because there are some users who install TWRP and then they boot to eRecovery and then they think the TWRP installation failed.
I don't know is it just huawei thing.
Hope this helps a bit, even though it's a bit messy info.
keikari said:
It is nothing to really worry or even think about. I don't think you can get rid of it or even if you could there is no reason. It's just second recovery which does a different things than the normal stock recovery. I think the eRcovery is needed for the stock update, but normal recovery isn't(not completely sure about this).
It is just good to know that device also has eRecovery, because there are some users who install TWRP and then they boot to eRecovery and the they think the TWRP installation failed.
I don't know is it just huawei thing.
Hope this helps a bit, even though it's a bit messy info.
Click to expand...
Click to collapse
Thanks for the information.
It has definitely given me a much better idea regarding what is eRecovery.
Much appreciated.
it's basically useless on this phone. it will never fetch any package nor restore your device. most people either just keep it and dont bother using it or flash TWRP over it. by having stock recovery as 'recovery' and TWRP as 'recovery2' you can have access to official OTA updates yet still being able to do everything you could do with TWRP
Carkai said:
...by having stock recovery as 'recovery' and TWRP as 'recovery2' you can have access to official OTA updates yet still being able to do everything you could do with TWRP
Click to expand...
Click to collapse
Nice! I am interested in that!
Keeping both recoveries and not loosing OTA sounds good to me.
Have you any idea how to accomplish this please? Any link or for that matter where could I download stock recovery for PRA-LX1?
Thank you!
droidbits said:
Nice! I am interested in that!
Keeping both recoveries and not loosing OTA sounds good to me.
Have you any idea how to accomplish this please? Any link or for that matter where could I download stock recovery for PRA-LX1?
Thank you!
Click to expand...
Click to collapse
flash this as recovery (fastboot flash recovery RECOVERY.img) and this as recovery2 (fastboot flash recovery2 twrp-3.1.1-2-v1-prague.img)
Carkai said:
flash this as recovery (fastboot flash recovery RECOVERY.img) and this as recovery2 (fastboot flash recovery2 twrp-3.1.1-2-v1-prague.img)
Click to expand...
Click to collapse
Thank you!
I was really trying to find the stock recovery for PRA-LX1 from somewhere. Very handy!
Now, having both recoveries flashed, I gather that there will be also the need to unroot when I want to receive OTA or not?
droidbits said:
Thank you!
I was really trying to find the stock recovery for PRA-LX1 from somewhere. Very handy!
Now, having both recoveries flashed, I gather that there will be also the need to unroot when I want to receive OTA or not?
Click to expand...
Click to collapse
nope! you can install OTAs with root and unlocked bootloader (although you have to download and install FULL-OTA packages. basically just clicking three dots when you've received an update and selecting 'download full package' or something like that)
Hello! My Y9 2018 FLA-LX3 uses fastboot flash recovery_ramdisk for TWRP, but it removes stock recovery. Can I flash TWRP to the recovery2/erecovery slot? And if so, what is the command? I have ramdisk, so to flash TWRP I'd use recovery_ramdisk instead of recovery. So, do I use recovery2_ramdisk? Thx!
RustyBl0ck said:
Hello! My Y9 2018 FLA-LX3 uses fastboot flash recovery_ramdisk for TWRP, but it removes stock recovery. Can I flash TWRP to the recovery2/erecovery slot? And if so, what is the command? I have ramdisk, so to flash TWRP I'd use recovery_ramdisk instead of recovery. So, do I use recovery2_ramdisk? Thx!
Click to expand...
Click to collapse
Yes, you can flash TWRP over eRecovery.
Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP:
- Copy TWRP file to the SD card
- Boot in TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- reboot .
-Alf- said:
Yes, you can flash TWRP over eRecovery.
Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP:
- Copy TWRP file to the SD card
- Boot in TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- reboot .
Click to expand...
Click to collapse
Oh thx! But I don't like it bc my goal is to leave stock recovery INTACT. So, I've been also trying to use fastboot to use fastboot boot "TWRP".img That's my goal, even though it hasn't worked. That is my ideal solution. Thx"!
RustyBl0ck said:
Oh thx! But I don't like it bc my goal is to leave stock recovery INTACT. So, I've been also trying to use fastboot to use fastboot boot "TWRP".img That's my goal, even though it hasn't worked. That is my ideal solution. Thx"!
Click to expand...
Click to collapse
And what's stopping you from installing TWRP instead of eRecovery and then installing Recovery back?
No matter what your ideal solution is, this is the only way.
Okay. So, I can an have tried to install TWRP just normally using fastboot flash recovery_ramdisk twrp.img That works, but the issue is that I can't find the stock/original recovery.img to replace it with when I'm finished. I extracted the UPDATE.APP and found a recovery_ramdisk.img. I am kinda scared to try to flash it using the same command for twrp, so I haven-t tried it. Can u pls tell me if I shall do it So in theory, fastboot flash recovery_ramdisk recovery_ramdisk.img
Oh and FYI, that image was extracted from a working UPDATE.app I used for my particular phone and it has always worked, just that it restores EVERYTHING. I just want the recovery back when I finish with TWRP. I-m giving it away and dont want the new owners messing with TWRP, since it can do harm to the phone if misused. Thx!!!
RustyBl0ck said:
. I am kinda scared to try to flash it using the same command for twrp, so I haven-t tried it. Can u pls tell me if I shall do it So in theory, fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
Sure, you can flash recovery_ramdisk using command
RustyBl0ck said:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
Or, you can flash it in TWRP ("install image" option).
How do I uninstall TWRP and unroot my Honor 9 Lite so i can update the phone to LLD-L31 8.0.0.128(C432) with face unlock?
I have already locked bootloader.
When i reboot the phone it automatically brings me to eRecovery and when i "Download latest version and recovery" it says "Getting package info failed". Please help
OmaroOmaro said:
How do I uninstall TWRP and unroot my Honor 9 Lite so i can update the phone to LLD-L31 8.0.0.128(C432) with face unlock?
I have already locked bootloader.
Click to expand...
Click to collapse
Looks like you "played" a bit to much with your phone. There is no official TWRP yet and no official Firmware Image. So, this looks very bad for you to get out of this again.
Maybe try HiSuite from Huawei or MultiTool
https://forum.xda-developers.com/devdb/project/dl/?id=28734
Probably this could help as long as you can connect via ADB or HDB from HiSuite.
Good luck...
Hey, I've faced the exact same issue. After playing even a bit more, I manged to revert my device (LLD-L31) back to stock.
I've uploaded all the files I used, for you.
It passes SafetyNet check successullfy!
Download required files here
Here is was I did:
Format data using TWRP (Wipe -> Format data)
Enter fastboot mode (Connect to PC, power+ VolDown)
fastboot flash ramdisk ramdisk.emmc.win
fastboot flash kernel kernel.emmc.win
fastboot flash system SYSTEM.img
fastboot reboot
Click to expand...
Click to collapse
Please tell me, if it worked!
Note:
The SYSTEM.img is extracted from the UPDATE.APP from this site.
Kernel and ramdisk are from a LOS-15.1 TRWP backup. Not sure if they're required, but it didn't work for me without flashing them.
error while extracting update.app
hello sir, I'm getting this error while extracting update.app.. recovery ramdisk.img invalid header crc - Expected: 18707 Got:56582
creativeanand said:
hello sir, I'm getting this error while extracting update.app.. recovery ramdisk.img invalid header crc - Expected: 18707 Got:56582
Click to expand...
Click to collapse
Why exactly do you need to extrac the update.app? I've already uploaded all required files and linked them in my previous post.
Also, which program did you use? Which operating system did you use?
now my phone is looping
MateUserHHTT said:
Why exactly do you need to extrac the update.app? I've already uploaded all required files and linked them in my previous post.
Also, which program did you use? Which operating system did you use?
Click to expand...
Click to collapse
now my phone is looping on off, on of
and i can't go to fastboot
creativeanand said:
now my phone is looping on off, on of
and i can't go to fastboot
Click to expand...
Click to collapse
In order for me to help you, I need to know exactly what you did.
So what did you do before your phone went into bootloop? (And don't worry, my Honor 9 lite has been in bootloops 100 of times, we can fix that! )
And how did you try to enter fastboot?
Make sure your phone is connected to a computer via USB!
Then press and hold Volume DOWN and Power button until phone reboots.
Release power when you see the blue honor screen.
Release volume down key, when you are in fastboot.
MateUserHHTT said:
In order for me to help you, I need to know exactly what you did.
So what did you do before your phone went into bootloop? (And don't worry, my Honor 9 lite has been in bootloops 100 of times, we can fix that! )
And how did you try to enter fastboot?
Make sure your phone is connected to a computer via USB!
Then press and hold Volume DOWN and Power button until phone reboots.
Release power when you see the blue honor screen.
Release volume down key, when you are in fastboot.
Click to expand...
Click to collapse
after flash shall i wipe data/ factory reset?
creativeanand said:
after flash shall i wipe data/ factory reset?
Click to expand...
Click to collapse
Again, I need to know whay you did!
You don't necessarily need to factory reset after a flash. But it probably won't make things worse.
But if you are switching the ROM (stock to a custom Rom) you indeed have to format data in twrp.
MateUserHHTT said:
Again, I need to know whay you did!
You don't necessarily need to factory reset after a flash. But it probably won't make things worse.
But if you are switching the ROM (stock to a custom Rom) you indeed have to format data in twrp.
Click to expand...
Click to collapse
i unlocked my phone bcoz the sound of h9l was lower then Redmi note 5 so i wanted to boost the sound with aris sound system and dolby atmos app.
after flashing 'SUPERSU' phone was not starting freeze at honor logo and then i wiped & rested in twrp...
now i did fastboot as you said now eRecovery is asking download latest version, wipe data/ f rest, reboot, shoutdown what shall i do now,,....thank you for helping
creativeanand said:
i unlocked my phone bcoz the sound of h9l was lower then Redmi note 5 so i wanted to boost the sound with aris sound system and dolby atmos app.
after flashing 'SUPERSU' phone was not starting freeze at honor logo and then i wiped & rested in twrp...
now i did fastboot as you said now eRecovery is asking download latest version, wipe data/ f rest, reboot, shoutdown what shall i do now,,....thank you for helping
Click to expand...
Click to collapse
Ok, now I can help you.
First of all, install TWRP. Use img2 (the experimental test build) if img #1 just stucks at the TWRP screen and won't enter the recovery.
Tell me when you succeed
You can get TWRP from here
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
MateUserHHTT said:
Ok, now I can help you.
First of all, install TWRP. Use img2 (the experimental test build) if img #1 just stucks at the TWRP screen and won't enter the recovery.
Tell me when you succeed
You can get TWRP from here
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
Click to expand...
Click to collapse
i did now?
creativeanand said:
i did now?
Click to expand...
Click to collapse
Great!
Now just follow my instructions from my earlier post
Make sure to put the files you download in the same folder as you run fastboot commands, so fastboot can find these files.
Good luck!??
MateUserHHTT said:
Great!
Now just follow my instructions from my earlier post
Make sure to put the files you download in the same folder as you run fastboot commands, so fastboot can find these files.
Good luck!
Click to expand...
Click to collapse
i did as you said .. now phone is not starting stoped at huawei eRecovery
whan i go to twrp phone reboots itshalf after 10sec
If you can boot to bootloader
and bootloader = unlocked
and FRP = unlock
then you can reset the phone to stock-rom
you need download with HuaweiFirmwareFinder 1 FULL-Update from YOUR build
i see in FF "LLD-L31C432B131 FullOTA-MF
download the 3 files, extract with HuaweiUpdateExtractor
- ramdisk.img
- recovery_ramdis.img
- system.img
the extractor do automatik for all *.img 1 *.img.header
copy this 6 files to your ADB-Folder
For reset to stock-rom
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
after this reboot the phone, eRecovery format low-level "data", phone reboot and start as "new" phone (initial settings)
before you do this you can do 1 test :
- fastboot flash recovery_ramdisk recovery_ramdis.img
why?
format low-level "data" work ONLY with stock-recovery, NOT with TWRP
after this is your "data" encrypt !
Only 1 TWRP work with encrypt/decrypt : https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
if phone work set PIN for Screen-open (this PIN need TWRP by start for encrypt/decrypt "data")
if you need, you can now flash recovery_ramdisk TWRP.img
if you need install OTA-Updates : if OTA-Update on your phone "install update now ?" answer "NO, later" and
- fastboot flash recovery_ramdisk recovery_ramdis.img (stock-recovery)
and install Update now.
if all work and you need : flash TWRP
i hope you understand this "way"
the advantage : you can install with TWRP OR flash developer-system.img and if anything not work - reset phone to stock-rom
i use ONLY TWRP with encrypt. this is security-question. if phone lost - data is encrypt !
TWRP without encrypt work only
- boot to TWRP
- format data
- boot from TWRP to TWRP
- data have now NO encrypt
Doesn't Android use FBE by default since Android O, so the data is always encrypted no matter what TWRP was used?
JamesBott said:
If you can boot to bootloader
and bootloader = unlocked
and FRP = unlock
then you can reset the phone to stock-rom
you need download with HuaweiFirmwareFinder 1 FULL-Update from YOUR build
i see in FF "LLD-L31C432B131 FullOTA-MF
download the 3 files, extract with HuaweiUpdateExtractor
- ramdisk.img
- recovery_ramdis.img
- system.img
the extractor do automatik for all *.img 1 *.img.header
copy this 6 files to your ADB-Folder
For reset to stock-rom
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
after this reboot the phone, eRecovery format low-level "data", phone reboot and start as "new" phone (initial settings)
before you do this you can do 1 test :
- fastboot flash recovery_ramdisk recovery_ramdis.img
why?
format low-level "data" work ONLY with stock-recovery, NOT with TWRP
after this is your "data" encrypt !
Only 1 TWRP work with encrypt/decrypt : https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
if phone work set PIN for Screen-open (this PIN need TWRP by start for encrypt/decrypt "data")
if you need, you can now flash recovery_ramdisk TWRP.img
if you need install OTA-Updates : if OTA-Update on your phone "install update now ?" answer "NO, later" and
- fastboot flash recovery_ramdisk recovery_ramdis.img (stock-recovery)
and install Update now.
if all work and you need : flash TWRP
i hope you understand this "way"
the advantage : you can install with TWRP OR flash developer-system.img and if anything not work - reset phone to stock-rom
i use ONLY TWRP with encrypt. this is security-question. if phone lost - data is encrypt !
TWRP without encrypt work only
- boot to TWRP
- format data
- boot from TWRP to TWRP
- data have now NO encrypt
Click to expand...
Click to collapse
sir shall i go to service center i have warrenty
creativeanand said:
sir shall i go to service center i have warrenty
Click to expand...
Click to collapse
By unlocking the bootloader you've void your warranty.
They will probably charge you for the repair.
What happens if you install this version of TWRP?
It's on Chinese, click the little icon in the top right corner and select "English".
If it doesn't crash, try this one.
Make sure to follow the correct steps for flashing.
fastboot flash recovery_ramdisk [filename.img]
fastboot flash reboot
QUICKLY unplug USB and before it fully reboots, hold press Volume up key
If it fails, check out this guide:
https://forum.xda-developers.com/9-lite/how-to/guide-unbrick-device-recover-bootloop-t3772563
My hon or 9 lite is in teaming page and it won't open I have tried to update via erecOvery but it won't work and I cannot go to recovery mode please help me.
@Prabin99
what you build ?
what have you do before start the update ?
have you anything flashed ?
Hello everyone :laugh:!
Tried rooting the Nokia 4.2, did not know which img to use exactly so I tried one from some other shady site and messed up. Luckily, the recovery partition was still working. After trying to boot lots of images, I got tired and accidentally even flashed a Nokia 6.2 TWRP image to my recovery partition. Then I completely messed up. The phone only gets into fastboot now. May I please ask some help of you? I've been trying for days to fix things. I just wanted to root the original firmware. Now when I try to flash TWRP, it even says that the 'recovery' partition has no partition table! I can still write to boot_a and boot_b though. The phone originally had the October patch level, but before bricking it I upgraded it to the December level.
Kind regards,
Alexander47u
Search on google and try do download and flash the stock firmware (unrooted)
Phone does not get detected by QFIL
thegamingcat13 said:
Search on google and try do download and flash the stock firmware (unrooted)
Click to expand...
Click to collapse
I have tried this using QFIL, however the phone is not detected. The phone also goes into fastboot as soon as the cable is plugged in, even when the phone is off.
Have also installed appropiate drivers for QFIL, but no luck.
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Works, Thank you!
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Thank you! This worked flawlessly.
#metoo
Haha, I have done the EXACT same thing as you. Now I can only enter fastboot mode and when I try to flash anything I have downloaded I get an error about missing partitions. I have looked everywhere for details on the partition sizes, mount points and so on but nobody has uploaded the information. In the end I went and purchased a second device in order to dump the entire stock ROM in order to fix the first phone. I've got the second phone running in ADB-mode but I can only backup to an .ab file so now I am back at square one. All of the guides I can find on how to dump the ROM involves flashing TWRP recovery but THERE IS NONE FOR THE 4.2 :crying: And after researching Android forensics I have found a guide to dumping the ROM but it needs root access in the phone shell. All I wanted was root (and LineageOS). Does anyone feel like patching the stock ROM and making a zip-file containing the img-files from all of the partitions?
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
alexander47u said:
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
Click to expand...
Click to collapse
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
alexander47u said:
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
Click to expand...
Click to collapse
I was able to succesfully patch boot.img with magisk, then I copied the patched boot image to my computer with linux. Fastboot flash boot boot.img worked but upon reboot I got an error message saying "corrupt data" and offered to do a factory reset. Any chance you can upload your patched boot image so I can use yours?
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Posted
alexander47u said:
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Click to expand...
Click to collapse
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Oslokalle said:
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Click to expand...
Click to collapse
Up to March. I used the stock rom that is floating around on the internet. Not sure if I am allowed to post stock roms.
I was able to update to April using Magisk but not any further than that.
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Tried this using a user_update.zip file from www[.]getdroidtips[.]com/stock-rom-nokia-4-2-firmware/. My phone boots again, but Wi-Fi doesn't work. My model # is TA-1133. What should I do?
Edit: tried to install the latest security OTA from t[.]me/nokiarepoen/379, V2.29C, but I get
Code:
E:Package is for source build 00WW_2_29B but expected 00WW_1_17I
. Is there a base user_update for build 00WW_2_29B floating around?
Oslokalle said:
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
Click to expand...
Click to collapse
Kindly provide me that zip too.
Hi everyone, and a happy new year
I need some light please, i don't understand what i'm doing wrong :/
To follow this post, i can't install EU ROM anymore (via TWRP) and i don't know why...
1) i flash the EEA Global via MiFlashTool, all ok
2) i make sure to unlock bootloader, all ok
3) i flash TWRP (official 3.6), all ok
Finally i want to flash 12.5.20.0, or 12.5.17.0 of EU ROM via TWRP/install, the process end up nicelly, no error so reboot, now everytime /data is lost, so it only boot on twrp and nothing is here anymore, need to go back at 1)
That is so frustrating :/
Can anyone enlight me please ?
did you format data after flashing 12.5.20.0
marcel112 said:
did you format data after flashing 12.5.20.0
Click to expand...
Click to collapse
nope, i need to ?
(if i format data, then i'll need to reflash the rom, right ?)
Only fastboot Version available right now bro. Already using it.
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
marcel112 said:
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
Click to expand...
Click to collapse
Thanks both of you !
Ok, but when i see files like 12.5.20.0 with a twrp flashing procedure labelled Mi11 Ultra, that let me think i can do it that way, it's misleading, at least :/
So, i flashed the latest 12.6 xiaomi eu rom and it worked
New problem, i then try to use twrp to flash magisk, i do fastboot boot twrp.img and then, /data lost again, so impossible to flash magisk :/
I tried both 3.6 official and 3.5.1 unofficial
p.s.: never set security pin/pass or whatever atm, so it's not a problem with the password
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
marcel112 said:
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
Click to expand...
Click to collapse
Oh my god, i totally forgot this method
Thank you very much, seems to work !
Solved