Q&A for deoxed NXA8QC116 rom, nextbook Ares 8
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for deoxed NXA8QC116 rom, nextbook Ares 8. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
After installing the deox zip my nextbook wont boot past the flashing nextbook logo.
Ares8 said:
After installing the deox zip my nextbook wont boot past the flashing nextbook logo.
Click to expand...
Click to collapse
How did you install it? Where you rooted and encryption turned off using supplied boot.img. did you make a backup?
Sent from my NXA8QC116 using XDA Free mobile app
vampirefo said:
How did you install it? Where you rooted and encryption turned off using supplied boot.img. did you make a backup?
Sent from my NXA8QC116 using XDA Free mobile app
Click to expand...
Click to collapse
I copied the .zip file to my external sd card and then installed using twrp, then rebooted. I dont have a backup file. I just followed your guide to root install supersu and decrypt device and then went to install this.
Thanks for the response.
Ares8 said:
I copied the .zip file to my external sd card and then installed using twrp, then rebooted. I dont have a backup file. I just followed your guide to root install supersu and decrypt device and then went to install this.
Thanks for the response.
Click to expand...
Click to collapse
You need to install provided boot.img.
Sent from my BLU STUDIO 5.0 C using Tapatalk
---------- Post added at 01:58 AM ---------- Previous post was at 01:51 AM ----------
Anyway early here, tomorrow, I will upload a zip to reverse this but you are still going to have to flash the boot.img before your tablet can boot.
From power off press and hold volume down plus power, when you see next book release power keep holding volume down.
Use fastboot to flash boot.img.
Or during bootloop type adb reboot bootloader then flash boot.img
Sent from my NXA8QC116 using XDA Free mobile app
vampirefo said:
You need to install provided boot.img.
Sent from my BLU STUDIO 5.0 C using Tapatalk
Click to expand...
Click to collapse
That tablet was rooted, decrpyted and running fine before i tried install the deox.zip.
Ares8 said:
That tablet was rooted, decrpyted and running fine before i tried install the deox.zip.
Click to expand...
Click to collapse
OK then you should have no problem typing adb reboot recovery, you did install twrp?
Sent from my NXA8QC116 using XDA Free mobile app
---------- Post added at 02:03 AM ---------- Previous post was at 02:00 AM ----------
In recovery wipe cache, and David cache, then reboot. I will get you the stock files in a few hours, you just install via twrp.
Sent from my NXA8QC116 using XDA Free mobile app
vampirefo said:
OK then you should have no problem typing adb reboot recovery, you did install twrp?
Sent from my NXA8QC116 using XDA Free mobile app
Click to expand...
Click to collapse
I can get into recovery mode, i just cant get past the nextbook logo when trying to run the device normally after installing the deox.zip
Ares8 said:
I can get into recovery mode, i just cant get past the nextbook logo when trying to run the device normally after installing the deox.zip
Click to expand...
Click to collapse
Good, twrp right? You will just need to flash the stock files, I upload when I get home.
Sent from my NXA8QC116 using XDA Free mobile app
vampirefo said:
Good, twrp right? You will just need to flash the stock files, I upload when I get home.
Sent from my NXA8QC116 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, sounds good. Is there any reason you can think of for the deox.zip file causing bootloop. All of your other files were running perfectly on my tablet.
Ares8 said:
Ok, sounds good. Is there any reason you can think of for the deox.zip file causing bootloop. All of your other files were running perfectly on my tablet.
Click to expand...
Click to collapse
No, must be some conflict with apps you have installed, just guessing can't say without logcat.
Sent from my NXA8QC116 using XDA Free mobile app
vampirefo said:
No, must be some conflict with apps you have installed, just guessing can't say without logcat.
Sent from my NXA8QC116 using XDA Free mobile app
Click to expand...
Click to collapse
The entire tablet is stock. I just bought it. No aftermarket apps. Im not sure if me not having busy box could of been the problem.
Ares8 said:
The entire tablet is stock. I just bought it. No aftermarket apps. Im not sure if me not having busy box could of been the problem.
Click to expand...
Click to collapse
No, busybox isn't a half to have, could of been a bad download hard to say.
Sent from my NXA8QC116 using XDA Free mobile app
---------- Post added at 03:11 AM ---------- Previous post was at 02:14 AM ----------
here you go, place on sdcard, factory reset then flash via twrp.
https://www.androidfilehost.com/?fid=24052804347766870
vampirefo said:
No, busybox isn't a half to have, could of been a bad download hard to say.
Sent from my NXA8QC116 using XDA Free mobile app
---------- Post added at 03:11 AM ---------- Previous post was at 02:14 AM ----------
here you go, place on sdcard, factory reset then flash via twrp.
https://www.androidfilehost.com/?fid=24052804347766870
Click to expand...
Click to collapse
The tablet is still stuck in bootloop. Should it be skipping the md5 check because no md5 file is found?
Ares8 said:
The tablet is still stuck in bootloop. Should it be skipping the md5 check because no md5 file is found?
Click to expand...
Click to collapse
Yes, did you do factory reset.
vampirefo said:
Yes, did you do factory reset.
Click to expand...
Click to collapse
Yes, when i first load into bootloader it says e: no valid installer medium found.
When flashing the rom, it is saying failed to mount /dev/block/by-name/system at /system: device or resource busy but then it will say successful after a few minutes.
Ares8 said:
Yes, when i first load into bootloader it says e: no valid installer medium found.
When flashing the rom, it is saying failed to mount /dev/block/by-name/system at /system: device or resource busy but then it will say successful after a few minutes.
Click to expand...
Click to collapse
Are you using twrp 2.8.7.0, sounds like you are trying to flash rom from tethered recovery, you need to have twrp 2.8.7.0 installed.
vampirefo said:
Are you using twrp 2.8.7.0, sounds like you are trying to flash rom from tethered recovery, you need to have twrp 2.8.7.0 installed.
Click to expand...
Click to collapse
Im trying to install it from twrp on the device, but i only have 2.8.6 installed.
Ares8 said:
Im trying to install it from twrp on the device, but i only have 2.8.6 installed.
Click to expand...
Click to collapse
Open this zip and flash recovery and boot.img via fastboot, then boot into recovery format system, data, cache then install, it will take sometime to install when done it will tell you to reboot system.
on new install it can take 10 minutes or so for first boot.
https://www.androidfilehost.com/?fid=24052804347764290
How long are you giving tablet to boot? needs at least 10 minutes on first boot.
vampirefo said:
Open this zip and flash recovery and boot.img via fastboot, then boot into recovery format system, data, cache then install, it will take sometime to install when done it will tell you to reboot system.
on new install it can take 10 minutes or so for first boot.
https://www.androidfilehost.com/?fid=24052804347764290
How long are you giving tablet to boot? needs at least 10 minutes on first boot.
Click to expand...
Click to collapse
This link is broken.
Related
Hi all, I finally got a test built for note 3 neo n7502: http://techerrata.com/bigbiff/openrecovery-twrp-2.8.2.0-hl3gdsxx.img.tar
Please let me know if it works. Flash in Odin, make sure auto-reboot is not selected, then boot TWRP manually.
bigbiff said:
Hi all, I finally got a test built for note 3 neo n7502: http://techerrata.com/bigbiff/openrecovery-twrp-2.8.2.0-hl3gdsxx.img.tar
Please let me know if it works. Flash in Odin, make sure auto-reboot is not selected, then boot TWRP manually.
Click to expand...
Click to collapse
Hi dear friend.
I've downloaded it but it's img file.
How do I have to flash it using Odin?
Do I have to change it to .tar or do something else?
Sent from my SM-N7502 using XDA Free mobile app
---------- Post added at 01:07 PM ---------- Previous post was at 12:25 PM ----------
bigbiff said:
Hi all, I finally got a test built for note 3 neo n7502: http://techerrata.com/bigbiff/openrecovery-twrp-2.8.2.0-hl3gdsxx.img.tar
Please let me know if it works. Flash in Odin, make sure auto-reboot is not selected, then boot TWRP manually.
Click to expand...
Click to collapse
Hi
I've downloaded the file and flashed it (the zip file) by Odin as you said.
Unticked the auto-reboot and after the Odin process was done, I manually turned off my phone and boot into recovery by holding down home, power and volume up bottom.
but the phone after booting automatically goes to download mode.
It's not working.
Please guide me if I did any thing wrong.
Mersad_Maral said:
Hi dear friend.
I've downloaded it but it's img file.
How do I have to flash it using Odin?
Do I have to change it to .tar or do something else?
Sent from my SM-N7502 using XDA Free mobile app
Click to expand...
Click to collapse
Sent from my SM-N7502 using XDA Free mobile app
Mersad_Maral said:
Hi dear friend.
I've downloaded it but it's img file.
How do I have to flash it using Odin?
Do I have to change it to .tar or do something else?
Sent from my SM-N7502 using XDA Free mobile app
---------- Post added at 01:07 PM ---------- Previous post was at 12:25 PM ----------
Hi
I've downloaded the file and flashed it (the zip file) by Odin as you said.
Unticked the auto-reboot and after the Odin process was done, I manually turned off my phone and boot into recovery by holding down home, power and volume up bottom.
but the phone after booting automatically goes to download mode.
It's not working.
Please guide me if I did any thing wrong.
Sent from my SM-N7502 using XDA Free mobile app
Click to expand...
Click to collapse
Use Odin to flash stock recovery then you can boot again. If you can, please boot the bad version of TWRP, then reboot into download mode, reflash stock recovery, then boot android and look for /proc/last_kmsg
bigbiff said:
Use Odin to flash stock recovery then you can boot again. If you can, please boot the bad version of TWRP, then reboot into download mode, reflash stock recovery, then boot android and look for /proc/last_kmsg
Click to expand...
Click to collapse
I have stock recovery but it is .img file.
How do I have to flash it using Odin?
Do I have to zip it and change its name to "stock recovery. img.Md5.tar"?
"/proc/last_kmsg"
What is this????
Is this the command that I have to run in terminal or that's file or folder?
Please guide me step by step to do my job correctly.
Thanks alot.
Sent from my SM-N7502 using XDA Free mobile app
Mersad_Maral said:
I have stock recovery but it is .img file.
How do I have to flash it using Odin?
Do I have to zip it and change its name to "stock recovery. img.Md5.tar"?
"/proc/last_kmsg"
What is this????
Is this the command that I have to run in terminal or that's file or folder?
Please guide me step by step to do my job correctly.
Thanks alot.
Sent from my SM-N7502 using XDA Free mobile app
Click to expand...
Click to collapse
Not sure how to hand hold these things over XDA. Sorry but you need some familiarities.
bigbiff said:
Use Odin to flash stock recovery then you can boot again. If you can, please boot the bad version of TWRP, then reboot into download mode, reflash stock recovery, then boot android and look for /proc/last_kmsg
Click to expand...
Click to collapse
Hi bigbiff,
last_kmsg lost under /proc. There is only kmsg. What should I use to look?
ahbecan said:
Hi bigbiff,
last_kmsg lost under /proc. There is only kmsg. What should I use to look?
Click to expand...
Click to collapse
You have to boot the bad twrp for it to be generated in android.
bigbiff said:
You have to boot the bad twrp for it to be generated in android.
Click to expand...
Click to collapse
Hi bigbiff
When I want to boot into recovery, it goes to recovery just for 1 second and then boot into download mode so quickly.
I can't find the file that you said.
Sent from my SM-N7502 using XDA Free mobile app
bigbiff said:
You have to boot the bad twrp for it to be generated in android.
Click to expand...
Click to collapse
OK bigbiff.
Reboot again. I found last_kmsg. I converted it txt format for upload. Below.
ahbecan said:
OK bigbiff.
Reboot again. I found last_kmsg. I converted it txt format for upload. Below.
Click to expand...
Click to collapse
Did you restart by holding power? Does it give you a black screen at all?
bigbiff said:
Did you restart by holding power? Does it give you a black screen at all?
Click to expand...
Click to collapse
Yes, I restarted by holding. It didn't give me a black screen at all.
ahbecan said:
Yes, I restarted by holding. It didn't give me a black screen at all.
Click to expand...
Click to collapse
Please describe more what you saw exactly.
bigbiff said:
Please describe more what you saw exactly.
Click to expand...
Click to collapse
Hi, bigbiff.
I tried several times and saw black screen before download mod. On black screen, it seems "Wait. Done!" Below.
Recovery reboot during on with black screen to download mod
http://youtu.be/nRz6Ymg4mzA
Recovery reboot during off without black screen to download mod
http://youtu.be/K4CaYgge-mg
Normal reboot no black screen
http://youtu.be/nrxpgMgvyC8
ahbecan said:
Hi, bigbiff.
I tried several times and saw black screen before download mod. On black screen, it seems "Wait. Done!" Below.
Recovery reboot during on with black screen to download mod
http://youtu.be/nRz6Ymg4mzA
Recovery reboot during off without black screen to download mod
http://youtu.be/K4CaYgge-mg
Normal reboot no black screen
http://youtu.be/nrxpgMgvyC8
Click to expand...
Click to collapse
In the black screen can you see if adb works by typing adb devices on the command line?
bigbiff said:
In the black screen can you see if adb works by typing adb devices on the command line?
Click to expand...
Click to collapse
I tried several times. I didn't see again black screen. I see "device attached" after normal starting.
ahbecan said:
I tried several times. I didn't see again black screen. I see "device attached" after normal starting.
Click to expand...
Click to collapse
What happens when you boot, can you take a video?
bigbiff said:
What happens when you boot, can you take a video?
Click to expand...
Click to collapse
I see a blue writing very quickly. I guess, "Recovery booting". And Download mod is beginning. There is "Could not do normal boot" above "Odin Mode"
http://youtu.be/K4CaYgge-mg
http://youtu.be/nRz6Ymg4mzA
ahbecan said:
I see a blue writing very quickly. I guess, "Recovery booting". And Download mod is beginning. There is "Could not do normal boot" above "Odin Mode"
http://youtu.be/K4CaYgge-mg
http://youtu.be/nRz6Ymg4mzA
Click to expand...
Click to collapse
When it says
Wait...
Done
Does adb report a device at all?
@bigbiff
Do i need to root my N3N to try this?
How to backup my current stock recovery?
I want to test and report too
Thanks in advance
Best Regards
Sent from my SM-N7502 using XDA Free mobile app
bigbiff said:
When it says
Wait...
Done
Does adb report a device at all?
Click to expand...
Click to collapse
Sorry bigbiff. I can't see again black screen.(Wait... Done)
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
Recently Huawei released the official Marshmallow update for Honor5x. I followed the update from setting but only to be restarted and brought to TWRP recovery without any updates. So, I downloaded the updated manually ( so I can flash via TWRP ) only to find the update is not in .image but .app, which means TWRP won't be able to flash the update.
So I took alternatives to install back the stock recovery from Huawei, which I succeeded and I got back my Huawei Stock Recovery. I then try updating via setting update, it downloaded the update, and installed it via stock recovery. But halfaway updating I got ' System Failed to Update '. I suspect it might have to do with my Cyanogen Mod that I installed 2 months ago.
Any idea how I can update to official Marshmallow?
A_J97 said:
Recently Huawei released the official Marshmallow update for Honor5x. I followed the update from setting but only to be restarted and brought to TWRP recovery without any updates. So, I downloaded the updated manually ( so I can flash via TWRP ) only to find the update is not in .image but .app, which means TWRP won't be able to flash the update.
So I took alternatives to install back the stock recovery from Huawei, which I succeeded and I got back my Huawei Stock Recovery. I then try updating via setting update, it downloaded the update, and installed it via stock recovery. But halfaway updating I got ' System Failed to Update '. I suspect it might have to do with my Cyanogen Mod that I installed 2 months ago.
Any idea how I can update to official Marshmallow?
Click to expand...
Click to collapse
Download latest firmware on a PC, use huawei update extractor to extract boot, system, Cust and recovery images.
Flash them in fastboot mode and then do a forced update.
(UPDATE.APP in dload folder in root of SD, turn off phone, press and hold power + vol up + vol down until boot)
YOU WILL LOSE ALL YOUR APPS AND DATA so make a backup before doing this.
muradulislam said:
Download latest firmware on a PC, use huawei update extractor to extract boot, system, Cust and recovery images.
Flash them in fastboot mode and then do a forced update.
(UPDATE.APP in dload folder in root of SD, turn off phone, press and hold power + vol up + vol down until boot)
YOU WILL LOSE ALL YOUR APPS AND DATA so make a backup before doing this.
Click to expand...
Click to collapse
Do I need to flash all 4 of them? I've flash the boot image and when I tried to flash the other files it gave me' size of image is larger than target devices '
A_J97 said:
Do I need to flash all 4 of them? I've flash the boot image and when I tried to flash the other files it gave me' size of image is larger than target devices '
Click to expand...
Click to collapse
Yep, you need to flash all and as I don't know anything about this error so I can't help you more. Sorry...
I have the same problem .
Waiting for any body to help
saifooon said:
I have the same problem .
Waiting for any body to help
Click to expand...
Click to collapse
What are the exact steps you made?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
What are the exact steps you made?
Click to expand...
Click to collapse
Error in 20% while updating
After that
I copied the update.zip in sd dload folder and try to local update but the same error .
saifooon said:
Error in 20% while updating
After that
I copied the update.zip in sd dload folder and try to local update but the same error .
Click to expand...
Click to collapse
Have you rooted your phone before?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
Have you rooted your phone before?
Click to expand...
Click to collapse
Yes and I installed official B140 and im back to stock .
saifooon said:
Yes and I installed official B140 and im back to stock .
Click to expand...
Click to collapse
Looks like stock refuses to receive OTAs if there is a root history.
Sent from my Galaxy Tab 3 using XDA Labs
So how can we solve this problem
Or there is any way to cleat this history ?
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
adriansticoid said:
Looks like stock refuses to receive OTAs if there is a root history.
Click to expand...
Click to collapse
saifooon said:
So how can we solve this problem
Or there is any way to cleat this history ?
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
Click to expand...
Click to collapse
Maybe by flashing full images in fastboot.
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
Maybe by flashing full images in fastboot.
Click to expand...
Click to collapse
Any links please and thanks alot for your efforts :good:
Any ideas here
saifooon said:
Any ideas here
Click to expand...
Click to collapse
Download you phone's stock firmware(refer to the file depot thread). After that, use Huawei Update Extractor and extract the files in update.app, you should get system.img, recovery.img, boot.img and flash them all using fastboot.
Sent from my Galaxy Tab 3 using XDA Labs
I followed the steps given in a post ( not able to post url) and after installing the Supersu the phone is stuck on the boot loop.
I saw posts where the users want to go back to the stock image however i need the phone to be rooted, any suggestions what might be causing the boot loop and how i can fix it.
PS: I have twrp backup and last resort will be to give up rooting and restrore from it. Appreciate your expertise in advance!
Atul Chadha said:
I followed the steps given in a post ( not able to post url) and after installing the Supersu the phone is stuck on the boot loop.
I saw posts where the users want to go back to the stock image however i need the phone to be rooted, any suggestions what might be causing the boot loop and how i can fix it.
PS: I have twrp backup and last resort will be to give up rooting and restrore from it. Appreciate your expertise in advance!
Click to expand...
Click to collapse
URL: http://www.androidinfotech.com/2016/12/root-huawei-honor-7-marshmallow-twrp.html
Atul Chadha said:
URL: http://www.androidinfotech.com/2016/12/root-huawei-honor-7-marshmallow-twrp.html
Click to expand...
Click to collapse
That is way outdated man. And avoid following guides from 3rd party sites. Always search here in XDA. You flashed an outdated TWRP. Flash THIS latest version. Restore your backup for the moment, then flash the latest SuperSU. 2.82. The site you gave both give outdated TWRP and SuperSU.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
That is way outdated man. And avoid following guides from 3rd party sites. Always search here in XDA. You flashed an outdated TWRP. Flash THIS latest version. Restore your backup for the moment, then flash the latest SuperSU. 2.82. The site you gave both give outdated TWRP and SuperSU.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Lemme try the above, will keep you posted.
Atul Chadha said:
Lemme try the above, will keep you posted.
Click to expand...
Click to collapse
Alright.
Sent from my Honor 8 using XDA Labs
Atul Chadha said:
Lemme try the above, will keep you posted.
Click to expand...
Click to collapse
I was able to run the supersu however the phone is not booting and says "Attention, please update system again"
Error!
Func No: 10 ( Boot image)
Error No: 2 (load Failed)
adriansticoid said:
Alright.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I was able to run the supersu however the phone is not booting and says "Attention, please update system again"
Error!
Func No: 10 ( Boot image)
Error No: 2 (load Failed)
Atul Chadha said:
I was able to run the supersu however the phone is not booting and says "Attention, please update system again"
Error!
Func No: 10 ( Boot image)
Error No: 2 (load Failed)
Click to expand...
Click to collapse
Did you restore your backup first?
adriansticoid said:
Did you restore your backup first?
Click to expand...
Click to collapse
I restored my backup and then put the new supersu package in sd card. I have a backup however now i am not able to access TWRP.
Atul Chadha said:
I restored my backup and then put the new supersu package in sd card. I have a backup however now i am not able to access TWRP.
Click to expand...
Click to collapse
To add: I also cleared the cache and data and it was successful. The Supersu mentioned something about writing on boot loader and said it would reboot the phone.
After that, the phone didnt came up
Atul Chadha said:
To add: I also cleared the cache and data and it was successful. The Supersu mentioned something about writing on boot loader and said it would reboot the phone.
After that, the phone didnt came up
Click to expand...
Click to collapse
i think you flashed wrong su ,
venugopalu007 said:
i think you flashed wrong su ,
Click to expand...
Click to collapse
How can i get the right one ( How do i decide the correct version, i am using honor 7 running B360 version bought from flipkart if it makes any difference)
Atul Chadha said:
How can i get the right one ( How do i decide the correct version, i am using honor 7 running B360 version bought from flipkart if it makes any difference)
Click to expand...
Click to collapse
I installed SuperSU-v2.82-201705271822
Atul Chadha said:
I installed SuperSU-v2.82-201705271822
Click to expand...
Click to collapse
Still in bootloop? Dafuq.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Still in bootloop? Dafuq.
Click to expand...
Click to collapse
So i restored the backup i had because i needed my phone. Is there a specific version of twrp and supersu i need for honor 7.
Here is what i am trying:
I have my supersu on sd card.
I restart phone to goto twrp
i go-to wipe>advanced>wipe the cache
Go back to twrp main menu and hit install
Locate supersu and install it
reboot
Am i missing any step ?
EDIT: I tried using "SuperSU-v2.82-201705271822" latest version and same results. The phone is in rescue mode with error
Error! Func No: 10 ( Boot image) Error No: 2 (load Failed)
Atul Chadha said:
So i restored the backup i had because i needed my phone. Is there a specific version of twrp and supersu i need for honor 7.
Here is what i am trying:
I have my supersu on sd card.
I restart phone to goto twrp
i go-to wipe>advanced>wipe the cache
Go back to twrp main menu and hit install
Locate supersu and install it
reboot
Am i missing any step ?
EDIT: I tried using "SuperSU-v2.82-201705271822" latest version and same results. The phone is in rescue mode with error
Error! Func No: 10 ( Boot image) Error No: 2 (load Failed)
Click to expand...
Click to collapse
EDIT2: I flashed the stock ROM and tried the same thing again.
Same results, either i am doing something wrong or its sheer luck i guess!
Atul Chadha said:
EDIT2: I flashed the stock ROM and tried the same thing again.
Same results, either i am doing something wrong or its sheer luck i guess!
Click to expand...
Click to collapse
Actually man I have no idea why it doesn't boot when it should. How about Magisk? Can you try that?
adriansticoid said:
Actually man I have no idea why it doesn't boot when it should. How about Magisk? Can you try that?
Click to expand...
Click to collapse
Trying it now.
Atul Chadha said:
Trying it now.
Click to expand...
Click to collapse
No luck , same results. I guess i should try to restore the backup and give in for now. There is something wrong with the boot sequence which i cant seem to figure.
The rooting apps write on the boot sequence and then it gives the error i mentioned. I really appreciate your help though, if you find something interesting please update here.
Atul Chadha said:
No luck , same results. I guess i should try to restore the backup and give in for now. There is something wrong with the boot sequence which i cant seem to figure.
The rooting apps write on the boot sequence and then it gives the error i mentioned. I really appreciate your help though, if you find something interesting please update here.
Click to expand...
Click to collapse
I will man. I'm really sorry for this.
Sent from my Honor 8 using XDA Labs
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?