I wanted the new update so that I could move my apps to my SD card. I also wanted TWRP.
I followed this guide to install TWRP.
TWRP was successfully flashed. So I try to boot into it using 'fastboot boot recovery.img' to boot into it.
I get the 'ERROR: Remote DTB not found' message. So booting into recovery using fastboot doesn't work.
I try booting into recovery manually (volume down + power). That doesn't work either. It freezes up at the OnePlus logo.
So, since TWRP isn't working, I flash stock recovery. That worked fine, and booted into it successfully (manually).
I boot into stock recovery and followed this guide to try updating manually using stock recovery. Of course, the update fails.
I then try flashing the full dump here. I factory reset, then flashed the full dump.
"Update successful."
Now, it refuses to boot into system AND recovery.
Okay, I'll just reflash stock recovery?
ERROR: Remote DTB not found
Booting into recovery manually freezes up too, just like TWRP did earlier.
Is there something I'm doing wrong to get this error? Google tells me dtb errors are caused by corrupt IMGs, but I downloaded all the IMGs twice and from all available mirrors to try them out. I see that some other users in the OnePlus forums and in XDA are having the same problems when flashing TWRP.
I really just need to be able to boot into at least one recovery so I can flash a system dump again.
I am not sure if this is the cause of the problem, but I've noticed most OnePlus X users have the E1003 model, while I am using a E1005.
Any help is appreciated.
mechanity said:
I wanted the new update so that I could move my apps to my SD card. I also wanted TWRP.
I followed this guide to install TWRP. Like a few others in the thread, I had the problem that when I try to boot manually into recovery, the screen shows the OnePlus logo with the android logo. Then the android logo disappears, and no matter how long I hold the down button while booting, the screen freezes at the OnePlus logo.
Fine, I'll just use fastboot boot recovery.img .
Nope, I get the 'ERROR: Remote DTB not found' message. Still stuck on the fastboot screen.
Great, I'll just flash stock recovery. Cool, it worked.
I booted into stock recovery and followed this guide to try updating manually using stock recovery. Of course the update fails.
Maybe I can just flash the full dump here. I factory reset, then flashed the full dump. Now it refuses to boot into system AND recovery.
Okay, I'll just reflash stock recovery?
ERROR: Remote DTB not found
Booting into recovery manually gives me the same results as flashing TWRP did earlier. So now, I can neither flash stock recovery nor TWRP to install any OxygenOS.
Is there something I'm doing wrong to get this error? Google tells me dtb errors are caused by corrupt IMGs, but I downloaded all the IMGs twice and from all available mirrors to try them out. I really just need to be able to boot into at least one recovery so I can flash a system dump again.
I am not sure if this is the cause of the problem, but I've noticed most OnePlus X users have the E1003 model, while I am using a E1005.
Any help is appreciated.
Click to expand...
Click to collapse
When you try do go in recovery manually(volume up+power) what does it show
mohammedtabish said:
When you try do go in recovery manually(volume up+power) what does it show
Click to expand...
Click to collapse
Well, pressing volume up + power actually takes me to bootloader mode.
Volume down + power, on the other hand, shows the OnePlus logo and the Android logo for a split second. Then the android logo disappears, the OnePlus logo stays, and it freezes there.
In case my post wasn't very clear, the same thing happens even if I don't attempt to boot into recovery (as in, it does the same thing if I just press the power button to boot into the system).
In bootloader try to go in fastboot mode then flash the recovery using fastboot
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
In bootloader try to go in fastboot mode then flash the recovery using fastboot
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
That is exactly what I said I did in the OP. I have tried this multiple times.
Yes its softbrick and to solve this prob the only thing that i can think is install usb drivers again and tell me you that you have checked the debugging before getting softbricked and try f2fs recovery from eng_stk kernel thread
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
Yes its softbrick and to solve this prob the only thing that i can think is install usb drivers again and tell me you that you have checked the debugging before getting softbricked and try f2fs recovery from eng_stk kernel thread
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
I tried the f2fs recovery from blu_spark eng.stk thread just now. I am still getting the remote: dtb not found error.
Still freezing when I boot manually into the recovery.
I think change the pc you are using and start every thing from new in other thats the last hope
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
I think change the pc you are using and start every thing from new in other thats the last hope
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Tried all of these steps on two other PCs already, on both Windows 8 and Windows 7. It's not a driver issue or OS issue.
Guess I'll have to wait until the system IMGs are out, unless anyone else has any other suggestions.
System image ??? If you mean stock then its available bro
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
System image ??? If you mean stock then its available bro
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
It's available as a .zip, which means you need a working recovery to install it.
There is image also if you cant find it i can upload that i have backed up that or i will try to find that link
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
There is image also if you cant find it i can upload that i have backed up that or i will try to find that link
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Please do find that link or upload it, I cannot find it at all.
Thank you very much.
[/COLOR]
mechanity said:
Please do find that link or upload it, I cannot find it at all.
Thank you very much.
Click to expand...
Click to collapse
There you go bro
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
Sent from my ONE E1003 using Tapatalk
Hit thanks if helped
mohammedtabish said:
[/COLOR]
There you go bro
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
Sent from my ONE E1003 using Tapatalk
Hit thanks if helped
Click to expand...
Click to collapse
Sorry, I think you misunderstood me. I stated in the original post that I already have the stock recovery img, and have already tried flashing it.
I am talking about a full system image that can be flashed via fastboot or odin.
Ooooooo i think thats not available sorry for waisting you time though
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
Ooooooo i think thats not available sorry for waisting you time though
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
It's okay, thanks for your help.
mechanity said:
Tried all of these steps on two other PCs already, on both Windows 8 and Windows 7. It's not a driver issue or OS issue.
Guess I'll have to wait until the system IMGs are out, unless anyone else has any other suggestions.
Click to expand...
Click to collapse
been having the exact issue...now people wont think im crazy.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
mechanity said:
Sorry, I think you misunderstood me. I stated in the original post that I already have the stock recovery img, and have already tried flashing it.
I am talking about a full system image that can be flashed via fastboot or odin.
Click to expand...
Click to collapse
You can boot to stock.img?
I have the same dtb error when I try any twrp image I have attempted to flash...exactly like your issue, but stock works fine.
If you can get into stock you can flash the full rom zip of 2.1.2 and then flash the ota to 2.1.3 after.
You have to flash the full zip first.
joho5 said:
been having the exact issue...now people wont think im crazy.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
You can boot to stock.img?
I have the same dtb error when I try any twrp image I have attempted to flash...exactly like your issue, but stock works fine.
If you can get into stock you can flash the full rom zip of 2.1.2 and then flash the ota to 2.1.3 after.
You have to flash the full zip first.
Click to expand...
Click to collapse
Originally, I could boot to the stock recovery. However after flashing that full 2.1.3 dump that I linked to, I can't boot to system or recovery. Flashing stock recovery now gives me the same remote:dtb not found error.
i have the same problem
i can't get into adb but can get into fastboot
Related
Ok so yesterday morning I woke up to my phone being dead of charge. I plugged in the charger and proceeded to powering it on. This is where the problem begins. The HTC logo with red text would appear and then the screen would go black. So basically it was in a bootloop. I waited for like 5 minutes and it was still in the loop. So, I went into recovery and wiped the cache and dalvik cache. I rebooted the phone, still in a bootloop. I did a factory reset from TWRP recovery, rebooted, and still bootlooping. Then, I took out the SD Card, did another factory reset, still BOOTLOOPING! Lastly, this is what caused me to be where I am now. I wiped system, data, dalvik cache, and cache. So now, everytime I want to reboot or turn off the phone, TWRP tells me there is NO OS Installed. NOW I AM DESPERATE FOR ANY HELP ON THIS SITUATION! PLEASE REPLY WITH ANY SOLUTION YOU HAVE!
KingAirman said:
Ok so yesterday morning I woke up to my phone being dead of charge. I plugged in the charger and proceeded to powering it on. This is where the problem begins. The HTC logo with red text would appear and then the screen would go black. So basically it was in a bootloop. I waited for like 5 minutes and it was still in the loop. So, I went into recovery and wiped the cache and dalvik cache. I rebooted the phone, still in a bootloop. I did a factory reset from TWRP recovery, rebooted, and still bootlooping. Then, I took out the SD Card, did another factory reset, still BOOTLOOPING! Lastly, this is what caused me to be where I am now. I wiped system, data, dalvik cache, and cache. So now, everytime I want to reboot or turn off the phone, TWRP tells me there is NO OS Installed. NOW I AM DESPERATE FOR ANY HELP ON THIS SITUATION! PLEASE REPLY WITH ANY SOLUTION YOU HAVE!
Click to expand...
Click to collapse
just so you know, you yourself deleted the os. when you wipe system, you delete the os, always. what can you do? you can go find your os(google it), and reflash it.
simms22 said:
just so you know, you yourself deleted the os. when you wipe system, you delete the os, always. what can you do? you can go find your os(google it), and reflash it.
Click to expand...
Click to collapse
Can you please help me find the OS that matches my phone? Does it have to match my CID and MID or something like that? I never ever flashed a rom or os before so can you please explain in detail what i have to look for? Please reply as soon as possible.
KingAirman said:
Can you please help me find the OS that matches my phone? Does it have to match my CID and MID or something like that? I never ever flashed a rom or os before so can you please explain in detail what i have to look for? Please reply as soon as possible.
Click to expand...
Click to collapse
whats the exact model of your phone, model number if you can..
simms22 said:
whats the exact model of your phone, model number if you can..
Click to expand...
Click to collapse
The phone is a HTC One M9 Sprint version. Please reply as soon as possible.
KingAirman said:
The phone is a HTC One M9 Sprint version. Please reply as soon as possible.
Click to expand...
Click to collapse
htc one m9 factory image, for sprint, with instructions and a download link http://www.htc.com/us/support/rom-downloads.html#sprint
instructions http://www.htc.com/us/support/htc-one-a9-sprint/news/
download http://dl3.htc.com/application/RUU_...51.4.exe?_ga=1.11270260.1317973123.1475524644
simms22 said:
htc one m9 factory image, for sprint, with instructions and a download link http://www.htc.com/us/support/rom-downloads.html#sprint
instructions http://www.htc.com/us/support/htc-one-a9-sprint/news/
download http://dl3.htc.com/application/RUU_...51.4.exe?_ga=1.11270260.1317973123.1475524644
Click to expand...
Click to collapse
How will I be able to install the RUU if I have no OS? Also, do I need my bootloader to be locked to do it?
KingAirman said:
How will I be able to install the RUU if I have no OS? Also, do I need my bootloader to be locked to do it?
Click to expand...
Click to collapse
you are talking about a custom recovery, like twrp? if so, twrp now flashes the system.img file(if its in that update). extract it and try twrp.
simms22 said:
you are talking about a custom recovery, like twrp? if so, twrp now flashes the system.img file(if its in that update). extract it and try twrp.
Click to expand...
Click to collapse
I have TWRP as a custom recovery. So, I just have to flash the system.img and I will have my OS back?
KingAirman said:
I have TWRP as a custom recovery. So, I just have to flash the system.img and I will have my OS back?
Click to expand...
Click to collapse
should be. in twrp, when selecting what to flash, choose .img files first, then you will see it(if not, you only see zips). but yes, the system.img file is what youll need to boot up. are you on latest twrp? you should be to flash img files.
simms22 said:
should be. in twrp, when selecting what to flash, choose .img files first, then you will see it(if not, you only see zips). but yes, the system.img file is what youll need to boot up. are you on latest twrp? you should be to flash img files.
Click to expand...
Click to collapse
I am on TWRP 2.8.7.1 Is that good? and where can I find the system.img file?
KingAirman said:
I am on TWRP 2.8.7.1 Is that good? and where can I find the system.img file?
Click to expand...
Click to collapse
twrp is on 3.0.1/3.0.2 now-a-days.. your version is too old and cant flash img files. youll need to update it.
---------- Post added at 07:11 PM ---------- Previous post was at 07:11 PM ----------
KingAirman said:
I am on TWRP 2.8.7.1 Is that good? and where can I find the system.img file?
Click to expand...
Click to collapse
download that file, then open it to see if theres a system.img file inside.
simms22 said:
twrp is on 3.0.1/3.0.2 now-a-days.. your version is too old and cant flash img files. youll need to update it.
---------- Post added at 07:11 PM ---------- Previous post was at 07:11 PM ----------
download that file, then open it to see if theres a system.img file inside.
Click to expand...
Click to collapse
What file are you talking about and how can I update TWRP?
simms22 said:
twrp is on 3.0.1/3.0.2 now-a-days.. your version is too old and cant flash img files. youll need to update it.
---------- Post added at 07:11 PM ---------- Previous post was at 07:11 PM ----------
download that file, then open it to see if theres a system.img file inside.
Click to expand...
Click to collapse
Please reply as soon as possible. Ive been waiting all day for you to reply since you have been the only one to help me so far.
KingAirman said:
What file are you talking about and how can I update TWRP?
Click to expand...
Click to collapse
update twrp using flashify app. and that file is the download i linked on the previous page.
simms22 said:
update twrp using flashify app. and that file is the download i linked on the previous page.
Click to expand...
Click to collapse
I already updated TWRP to 3.0.2. The file you linked is an RUU.exe download from the official HTC website. How am I going to get the sytem.img file or get my OS back like that? Please reply as soon as possible.
KingAirman said:
I already updated TWRP to 3.0.2. The file you linked is an RUU.exe download from the official HTC website. How am I going to get the sytem.img file or get my OS back like that? Please reply as soon as possible.
Click to expand...
Click to collapse
download that file, then check inside if there is a system.img in it.
simms22 said:
download that file, then check inside if there is a system.img in it.
Click to expand...
Click to collapse
Can you please send me the link to the file you are talking about again? Please reply as soon as possible.
KingAirman said:
Can you please send me the link to the file you are talking about again? Please reply as soon as possible.
Click to expand...
Click to collapse
from post #6 http://dl3.htc.com/application/RUU_...51.4.exe?_ga=1.11270260.1317973123.1475524644
simms22 said:
from post #6 http://dl3.htc.com/application/RUU_...51.4.exe?_ga=1.11270260.1317973123.1475524644
Click to expand...
Click to collapse
This is an exe file. How am I going to find a system.img from this?
Now supports among other things back up to pc. I've installed and tested and works.
https://dl.twrp.me/ailsa_ii/twrp-3.1.0-0-ailsa_ii.img
Edit: the original article https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/
Edit: seems flashing via TWRP image flash is providing better success than via TWRP app. Recommend updating via TWRP flash.
thanks
Do not work.
Get a black screen if i try to Boot in to twrp.
Must go back to 3.0.4.1..
Eller1987 said:
Do not work.
Get a black screen if i try to Boot in to twrp.
Must go back to 3.0.4.1..
Click to expand...
Click to collapse
u sure ur bl is unlocked?
MaxRink said:
u sure ur bl is unlocked?
Click to expand...
Click to collapse
Yes.
I am in LOS 14.1 and twrp 3.0.4.1. works fine.
Flashed 3.1.0.0. whit Flashify.
Worked great for me! I always flash in TWRP, I guess that a I am old school. Thanks for pointing out the new version. I will have to try out the new ADB backup feature later. Although I am not sure if we are still having problems restoring backups like we used to on this phone. I haven't been able to keep up with the forum's lately.
Wrong thread, this needs to be in General
Mod please move.
I flashed the image file in recovery and I still ended up with a black screen.
borijess said:
I flashed the image file in recovery and I still ended up with a black screen.
Click to expand...
Click to collapse
Weird man i got it working flashing it feom twrp it self
borijess said:
I flashed the image file in recovery and I still ended up with a black screen.
Click to expand...
Click to collapse
Maybe you should also write from which TWRP version you come and which Axon 7 model(US/Chinese/European?) you own?
redandr said:
Maybe you should also write from which TWRP version you come and which Axon 7 model(US/Chinese/European?) you own?
Click to expand...
Click to collapse
i have a A2017G and come from twrp 3.0.4.1..
Which partion must i flash for the update to 3.1.0.0.?
I flashed this 3.1 on my chinese b13 with twrp 3.0.4-1 and everything is fine. Flashed it thru twrp btw.
---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------
Eller1987 said:
i have a A2017G and come from twrp 3.0.4.1..
Which partion must i flash for the update to 3.1.0.0.?
Click to expand...
Click to collapse
Flash it in twrp install and choose img. Flash it for recovery partition.
redandr said:
maybe you should also write from which twrp version you come and which axon 7 model(us/chinese/european?) you own?
Click to expand...
Click to collapse
twrp 3.0.41 axon 7 us version.
Ok I flashed TWRP through fastboot and it worked. I think my first DL was bad. It was half the size of the second one I downloaded.
Success here too. Thank you.
Its all ok with Axon Zte A2017 Chinese.
The last TWRP I conscioulsy installed was 3.0.4.1 but it now shows 3.0.N1-1, what is that? Could it have been updated automatically from the TWRP app?
Also, before I noticed that my boot partition disappeared from TWRP, I can no longer make backups of it or restore the ones I had. Why could that happen? I get something like "unable to locate boot". Thanks
0Kajuna0 said:
The last TWRP I conscioulsy installed was 3.0.4.1 but it now shows 3.0.N1-1, what is that? Could it have been updated automatically from the TWRP app?
Also, before I noticed that my boot partition disappeared from TWRP, I can no longer make backups of it or restore the ones I had. Why could that happen? I get something like "unable to locate boot". Thanks
Click to expand...
Click to collapse
I am guessing you used EDL mode to install TWRP as that is the modified version, as I saw that too. I used TWRP to flash the 3.0.4-1 image and all is normal.
EDIT: TWRP 3.0.4-1 on A2017U Running modified Stock B15 (lots of APKs frozen). Flashing TWRP 3.1 both from TWRP and from "Official App" results with black screen for Recovery. TWRP 3.0.4-1 re-flashed OK from app.
N1-1 is from unjustified devs bootstack.
lafester said:
N1-1 is from unjustified devs bootstack.
Click to expand...
Click to collapse
N1-1 & 3.0.4-1 both work fine, but 3.1 boots to black screen. Why?
Twrp 3.1.0 worked fine on my Axon 7 US version A2017U
Flashed via fastboot over stock recovery.
Will edit this thread and report back if issue is discovered.
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
it seems like u dint have an proper boot.img
try flashing ftf
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
macjagger said:
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
Click to expand...
Click to collapse
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
altvolt74 said:
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
Click to expand...
Click to collapse
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
macjagger said:
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
try flash e5823 lates nougat e5823_32.3.A.0.376_R2R_AU instead of (e5803) firmware
also to enter flash the rom using kernel partition
off phone . ...hold vol down and power release power when see sony keep holding volume down all the way till recovery
format system
flash zip
i will update intrustions since theres people having issues while flashing an rom using e5823 on e5803 or probably ur flashing it wrong using the recovery that is integrated to the boot.img
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
also sorry for late reply been cooking xperia xz rom to our z5 compact also finish is uploading it now
I'll give it a try in a couple of days. Need my phone as a daily driver currently. Appreciate your help
macjagger said:
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
To me it seems like you are just flashing twrp to the wrong partition.
How do you flash it?
You have to flash it with command:
Fastboot flash recovery "twrp.img"
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
oh hai
just wanted to link you in on this:
https://forum.xda-developers.com/z5...m-fix-twrp-t3560135/post71433741#post71433741
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
macjagger said:
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
Click to expand...
Click to collapse
Have you tried to do a restore yet?
Just wanted to ask so I can isolate twrp with rootkernel
Hello everyone! I'm new on XDA and this is my first thread.
So, I've been messing around with my Honor 7 lately. I've flashed a custom recovery (TWRP), flashed a custom ROM (Unofficial CM13 for Honor 7: https://forum.xda-developers.com/honor-7/development/unsupported-cyanogenmod-13-honor-7-plk-t3542627) and root (SuperSU) and I've started to regret all of my decisions so I would like to take a fresh start (AKA flashing the STOCK ROM/Firmware)
Now, before anyone starts redirecting me to other (similar) threads, I've tried a lot. I tried to flash the stock recovery (a lot of different versions) but still when I try to boot into the stock recovery, my phone just reboots. I tried to do the force update thing (holding both power + & - buttons: http://www.gogorapid.com/flash-stock-rom-huawei-honor-7/), but this combination just boots my phone into TWRP. Could it be that I'm doing something wrong or that I'm missing something, like some requirements that are not being met? Please help me, I would appreciate it a lot! Thanks in advance.
LoRikU said:
Hello everyone! I'm new on XDA and this is my first thread.
So, I've been messing around with my Honor 7 lately. I've flashed a custom recovery (TWRP), flashed a custom ROM (Unofficial CM13 for Honor 7: https://forum.xda-developers.com/ho...upported-cyanogenmod-13-honor-7-plk-t3542627) and root (SuperSU) and I've started to regret all of my decisions so I would like to take a fresh start (AKA flashing the STOCK ROM/Firmware)
Now, before anyone starts redirecting me to other (similar) threads, I've tried a lot. I tried to flash the stock recovery (a lot of different versions) but still when I try to boot into the stock recovery, my phone just reboots. I tried to do the force update thing (holding both power + & - buttons: http://www.gogorapid.com/flash-stock-rom-huawei-honor-7/), but this combination just boots my phone into TWRP. Could it be that I'm doing something wrong or that I'm missing something, like some requirements that are not being met? Please help me, I would appreciate it a lot! Thanks in advance.
Click to expand...
Click to collapse
It seems that you didn't flash the stock recovery properly.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
It seems that you didn't flash the stock recovery properly.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply!
Could it be? I booted my phone into bootloader (unlocked) and flashed stock recovery with adb using the command "fastboot flash recovery recovery.img". I tried a variety of versions (from B100 up to B330 I think), but none of them seemed to work. What am I doing wrong?
LoRikU said:
Thanks for the reply!
Could it be? I booted my phone into bootloader (unlocked) and flashed stock recovery with adb using the command "fastboot flash recovery recovery.img". I tried a variety of versions (from B100 up to B330 I think), but none of them seemed to work. What am I doing wrong?
Click to expand...
Click to collapse
did you tried the offical TWRP of ypur device?
venugopalu007 said:
did you tried the offical TWRP of ypur device?
Click to expand...
Click to collapse
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
LoRikU said:
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
Click to expand...
Click to collapse
Download stock recovery and boot your phone to fastboot and
in command --- Fastboot flash recovery xxxfilenamexxx.img
LoRikU said:
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
Click to expand...
Click to collapse
Grab the stock recovery file for your device. You can flash inside TWRP itself.
adriansticoid said:
Grab the stock recovery file for your device. You can flash inside TWRP itself.
Click to expand...
Click to collapse
Koriki extract the firmware using huaweiupdateextractor
venugopalu007 said:
Koriki extract the firmware using huaweiupdateextractor
Click to expand...
Click to collapse
Koriki?
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Koriki?
Click to expand...
Click to collapse
Loriki is user name of op
Sorry my keyboard auto corrected it to koriki
venugopalu007 said:
Download stock recovery and boot your phone to fastboot and
in command --- Fastboot flash recovery xxxfilenamexxx.img
Click to expand...
Click to collapse
I tried that, read my second post on this thread. It didn't work, I didn't know which version I had to use. I ended up with a bootloop on various versions as mentioned in one of my first posts.
adriansticoid said:
Grab the stock recovery file for your device. You can flash inside TWRP itself.
Click to expand...
Click to collapse
Alright, I will try this. As soon as I get back home since the wifi here sucks.
venugopalu007 said:
Koriki extract the firmware using huaweiupdateextractor
Click to expand...
Click to collapse
I planned on doing this though I don't know where I can get the firmware for my H7... Could you perhaps provide me a link? It would be very kind of you (+ The wifi here sucks, so I will try downloading firmwares when I get home)
As you know, TWRP still doesn't support FBE, so in-case if you wanna flash another system.img the Wipe data/factory reset in TWRP wouldn't work (at least didn't work for me).
That would force you to get back to stock recovery, which allows a successful factory reset.
Steps are pretty straight forward, if you already have a backup of your stock recovery just do the below steps, if else you could download one from the below link.
Put the device into fastboot mode. There are two ways to do that.
1)By long pressing the power button and volume down button whilst the USB is connected.
2)Just do a adb reboot bootloader command if you could boot into the system.
Then just do
Code:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Then disconnect the USB and long press the power and volume up button until you see the "The device is booting now" message.
Downloads
- Stock recovery for BKL-L09
Thanks, you saved me.
Thanks
Just created a md5sum of your recovery and my backed up recovery. It's exactly the same size but the md5sum is different.
A quick look with a hex editor also shows some big differences. Is that expected?
Copperhead100 said:
Just created a md5sum of your recovery and my backed up recovery. It's exactly the same size but the md5sum is different.
A quick look with a hex editor also shows some big differences. Is that expected?
Click to expand...
Click to collapse
MD5 hash wouldn't possibly match, because the backup was taken using dd and there might be some config files modified or added when I used the stock recovery once. But, hey the thing would work if you have BKL-L09 device
Thanks. This works!
shihabsoft said:
As you know, TWRP still doesn't support FBE, so in-case if you wanna flash another system.img the Wipe data/factory reset in TWRP wouldn't work (at least didn't work for me).
That would force you to get back to stock recovery, which allows a successful factory reset.
Click to expand...
Click to collapse
Mate, will this stock recovery work in Indian model(BKL-L09-C675)?
atf2m4 said:
Mate, will this stock recovery work in Indian model(BKL-L09-C675)?
Click to expand...
Click to collapse
Ofc it does
shihabsoft said:
Ofc it does
Click to expand...
Click to collapse
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
atf2m4 said:
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
Click to expand...
Click to collapse
Not sure, as it might check integrity before giving updates. Just download Firmware Finder app and check for updates constantly.
atf2m4 said:
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
Click to expand...
Click to collapse
You will receive the updates but you won't be able to install them with TWRP. Simply flash the stock recovery and the updates will self install when they come. You'll have to root again with Magisk after the updates, but that's a simple process.
Sent from my Honor View 10 using XDA Labs
Hie,
How can I get back from lineage OS to stock using this? I guess I'm on the same boat as a lot of people out there and could really use some help here. I'm on Cosmos OS and can't go back to stock. I tried flashing this recovery.img but can't figure out a way back.
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Can you help me with the commands please?
---------- Post added at 09:20 PM ---------- Previous post was at 09:12 PM ----------
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Wildfire, can you please help me with the commands? I believe there's an inclusion of ramdisk in the commands now.
---------- Post added at 09:52 PM ---------- Previous post was at 09:20 PM ----------
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoys.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Apparently, there isn't any system.img file in the Indian firmware I downloaded. The rest are there but not the system.img.
Someone please help me out
I can't flash system.img as I was told in an earlier reply, it returns me an error that says 'Error: Cannot load System.':crying: I tried using -P and 256M commands to see the space divided and none of these worked either. CAN SOME PLEASE HELP ME OUT WITH THIS?
I cannot find system.img in the Indian firmware either, that is making things tough for me.
ankan1993 said:
I can't flash system.img as I was told in an earlier reply, it returns me an error that says 'Error: Cannot load System.':crying: I tried using -P and 256M commands to see the space divided and none of these worked either. CAN SOME PLEASE HELP ME OUT WITH THIS?
I cannot find system.img in the Indian firmware either, that is making things tough for me.
Click to expand...
Click to collapse
You should have made a backup before you started "tinkering" with your device. Lesson learned, hopefully.
Sent from my Honor View 10 using XDA Labs
Einwod said:
You should have made a backup before you started "tinkering" with your device. Lesson learned, hopefully.
Sent from my Honor View 10 using XDA Labs
Click to expand...
Click to collapse
Indeed! Can you please help me this one time?
ankan1993 said:
Indeed! Can you please help me this one time?
Click to expand...
Click to collapse
I cannot help you as I do not have your firmware or know anything about the Indian version. Where did you get this firmware from?
Einwod said:
I cannot help you as I do not have your firmware or know anything about the Indian version. Where did you get this firmware from?
Click to expand...
Click to collapse
I downloaded this from https://www.getdroidtips.com/huawei-honor-view-10-b160-oreo-firmware/#Downloads.
ankan1993 said:
I downloaded this from https://www.getdroidtips.com/huawei-honor-view-10-b160-oreo-firmware/#Downloads.
Click to expand...
Click to collapse
What device do you have exactly?