Hello, I'm fairly new here. I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV Box: https://www.androidtv-guide.com/pay-tv-provider/united-group-eon-ott-smart-box/
Fzloop said:
Hello, I'm fairly new here.
Click to expand...
Click to collapse
Fairly? You joined yesterday. You could hardly be fairer.
Fzloop said:
I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again.
Click to expand...
Click to collapse
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
Fzloop said:
How do i fix that?
Click to expand...
Click to collapse
One way is to flash the original recovery partition back to the device using burn mode.
Fzloop said:
How do i access the recovery mode?
Click to expand...
Click to collapse
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
goapy said:
Fairly? You joined yesterday. You could hardly be fairer.
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
One way is to flash the original recovery partition back to the device using burn mode.
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
Click to expand...
Click to collapse
I did join yesterday, but I've been using this forum for a while without posting.
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Fzloop said:
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Click to expand...
Click to collapse
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
goapy said:
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
Click to expand...
Click to collapse
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Fzloop said:
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Click to expand...
Click to collapse
Hi @Fzloop,
can you share the ROM?
xfenixxx said:
Hi @Fzloop,
can you share the ROM?
Click to expand...
Click to collapse
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Fzloop said:
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Click to expand...
Click to collapse
Thank you very much, I'll still give it a try.
Hello, I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV BOX https://www.androidtv-guide.com/pay-tv-provider/dhiraagu-tv-joybox/
box connected AMLOGIC usb burn tool. but error uboot/getresult/Diskinitial error
Related
After many lost hours of sleep, I finally give up and come to the community for help. I've seen the problems I'm having posted a lot, but I've not yet found a solution.
To start, all was well with my KitKat 4.4 ROM, except that my SIM would not read. So in my troubleshooting process, I did a full system wipe of everything through TWRP v2.6.3.0 (including internal memory), knowing that my ROM and other necessary files were saved on my SD card. The problem now is that TWRP will not show that I actually have an SD, so I'm stuck with no OS now. I've tried everything I've seen, such as formatting and properly "ejecting" the SD from my computer after doing so. I've tried three different SD cards, two 16gig and one 2 gig. Still won't read.
The only other thing I can think to do is use ADB to push or sideload - my device does not show at all when I try. Same result with fastboot. I'm suspecting that the issue with this is the driver. So far, after searching for hours and hours, the only driver I've found to use with the E970 is the usb_driver downloaded through SDK Manager. When I use this driver, it shows my phone as Google Galaxy Nexus ADB Interface in the Device Manager. But still no luck with ADB or Fastboot.
So I apologize if either of these has been solved one or more times before, but I'm desperate for help. Thanks!
AFAIK , there is a special modded TWRP version for KK Geeb that is patched to read SD Cards.
You'll have to search it or wait till someone who has it posts it here. But I have read about that somewhere , it's just that I am not able to recall. If I find it , I'll post asap.
Rishi. said:
AFAIK , there is a special modded TWRP version for KK Geeb that is patched to read SD Cards.
You'll have to search it or wait till someone who has it posts it here. But I have read about that somewhere , it's just that I am not able to recall. If I find it , I'll post asap.
Click to expand...
Click to collapse
As of right now, my phone has no ROM installed. I'd be willing to bet that it wouldn't read from an SD even before I tried my first ROM, but I don't really know since I never tried. Stupid on my part for not doing so before the wipe. I'll look into the modded TWRP, and hopefully it'll get me somewhere. Thanks for the help!
I assume it shouldn't be hard to push the modded recovery to the phone via ADB. Then you would be able to get the SDcard recognized and flash the rom of your choice.
Or second choice stands as LGNPST , then flash alt./orig. teenybins , which'll give you TWRP 2.5.0.0 or something similar to it. You can flash the new modded TWRP using that as well.
Rishi. said:
I assume it shouldn't be hard to push the modded recovery to the phone via ADB. Then you would be able to get the SDcard recognized and flash the rom of your choice.
Or second choice stands as LGNPST , then flash alt./orig. teenybins , which'll give you TWRP 2.5.0.0 or something similar to it. You can flash the new modded TWRP using that as well.
Click to expand...
Click to collapse
The problem with this is that I can't get ADB to find my device. If that were the case, I'd just push the ROM straight to my internal memory since that's the only one it sees. I've tried and double checked many times to make sure I was doing the ADB process properly. As far as I can tell, I am. Which leads me to think its not the proper driver for my phone. But I can't find any others.
I thought about LGNPST, but I can't get the phone into download mode without an OS. And that's the only way I know to use LGNPST.
You can get the phone to download mode , even without a ROM. The Download mode is initiated , right at phone start up. I think you may be doing it in a wrong way or so , that's why it's not booting up in dload mode. Check the TeenyBins thread , and see if you are doing it right way.
If your phone is booting then LGNPST will work most probably.
Rishi. said:
You can get the phone to download mode , even without a ROM. The Download mode is initiated , right at phone start up. I think you may be doing it in a wrong way or so , that's why it's not booting up in dload mode. Check the TeenyBins thread , and see if you are doing it right way.
If your phone is booting then LGNPST will work most probably.
Click to expand...
Click to collapse
You're absolutely right! I had entered download mode more than a few times before, so I knew how to do it. But I guess in my sleep-deprived and frustrated state, I must have been forgetting something. Just got it into download mode on the first try. I feel like starting fresh with a stock ROM is best, so it's working on that right now.
Thanks coming your way!
SmithZ33 said:
You're absolutely right! I had entered download mode more than a few times before, so I knew how to do it. But I guess in my sleep-deprived and frustrated state, I must have been forgetting something. Just got it into download mode on the first try. I feel like starting fresh with a stock ROM is best, so it's working on that right now.
Thanks coming your way!
Click to expand...
Click to collapse
Take enough sleep , before flashing next time. Last time I remember when I was sleep deprived and did some flashing , I ended up with a partial brick. :lol:
Start fresh with teeny bins. Then FLash the stock rom using recovery. ( Don't LGNPST the stock .tot file.( Use LGNPST just to throw in the correct TWRP recovery and update partitions with TeenyBins ). I would recommend flashing the stock JB .zip file using TWRP recovery . (Created by SnowLeopardJB ). ) Check his thread.
Post if you face any issues. ::highfive:
Rishi. said:
Take enough sleep , before flashing next time. Last time I remember when I was sleep deprived and did some flashing , I ended up with a partial brick. :lol:
Start fresh with teeny bins. Then FLash the stock rom using recovery. ( Don't LGNPST the stock .tot file.( Use LGNPST just to throw in the correct TWRP recovery and update partitions with TeenyBins ). I would recommend flashing the stock JB .zip file using TWRP recovery . (Created by SnowLeopardJB ). ) Check his thread.
Post if you face any issues. ::highfive:
Click to expand...
Click to collapse
Well, I opted to use LGNPST to flash TeenyBins and a TWRP that read my SD. Flashed the KitKat ROM just to try it, and it boots perfectly but I'm back to no SIM. So I'll be moving on to this new issue... haha
So you didnt slept...huh .. lol.
Sent from my LG-E970 using Tapatalk
Rishi. said:
So you didnt slept...huh .. lol.
Sent from my LG-E970 using Tapatalk
Click to expand...
Click to collapse
Haha, no I didn't. Between work and travel, I'm still trying to figure out this sim issue. It won't detect my sim on this ROM, or others it seems. I tried on a LiquidSmooth 4.3.1 ROM just now and it had the same issue. It's almost as if it has the detection set backwards. When I insert the sim, it thinks I've removed it and says ”sim removed." Then when removed, it says ”sim inserted” or something along those lines, and wants to restart. I'm at a loss, and I'm wondering why it could be doing this.
Hard brick for OPT happens when you change critical partitions. It will follow improper firmware flash or accidental erase of certain partitions. The phone won't show any response when hardbricked.
The solution for OPT is similar to OPO - you just need a Qualcomm driver and a recover package. The only full recovery package available is very big and it restore the phone to Hyrdogen OS, with everything wiped. So it would not be very attractive.
Fortunately, thanks to this post from Chinese supporting forum, a minimal version of restore package is provided. It does not wipe user data and guarantee a recovery entry. you would normally be freed using this package. if not, please use the full package in the end of the post
Download link for driver
Download link for Recovery tool
uncompress the files to a local folder.
First step, turn off drive signature enforcement in windows 8/8.1/10. Tutorial Here
Second step, hold the power key for 20 seconds to force turn off power. connect OPT to usb, hold volume+ and power until your PC finds a new hardware (if it doesn't work, try hold volume+ and volume- together)
Third step, go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics 9006" device. Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Fourth step, when the driver is installed properly, run MSM8994DownloadTool.exe in the recover tools folder, using admin privileges . Clear start in top left corner and wait for it to finish.
Now your OPT should be able to enter TWRP recovery. It still won't boot but you can manually flash anything again (like the full Oxygen OS package).
The procedure is tested by me twice. Enjoy!
p.s: sorry the recovery image in the A2001_save_brick_mini.rar is Chinese. Please download this file, change the name to recovery.img and substitute the file in the recovery tool before flashing.
UPDATE：full Oxygen OS 150805 restoration package for those who experience recovery entry problem. Note that this package wipes everything including internal storage!
Awesome, I will go ahead and make a full recovery tool that includes these files as well as the latest version of OxygenOS as I did with the Oneplus one.
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
CoreGaming said:
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
Click to expand...
Click to collapse
Like i did before with my mod of the toolkit
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
okay and were can i get this package for the OPT?
CoreGaming said:
okay and were can i get this package for the OPT?
Click to expand...
Click to collapse
Havn't made it yet, still need to work on it. It is a little different than OPO so it might take some time.
okay this will be great. Take your time i'm ready
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Lord Boeffla said:
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Click to expand...
Click to collapse
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Zyxxeil said:
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Click to expand...
Click to collapse
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Click to expand...
Click to collapse
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Click to expand...
Click to collapse
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Lord Boeffla said:
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Click to expand...
Click to collapse
HydrogenOS definitely has the option because it is how I flashed TWRP in the first place
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
Without recovery how do you flash hydrogenOS?
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Wow thanks, I was trying to do it with the one you posted but I couldn't since it was missing the info for system sectors. Now i can make my tool
Zyxxeil said:
Without recovery how do you flash hydrogenOS?
Click to expand...
Click to collapse
Using this tool and the full recovery package? Or am I missing something here?
khr0n0s said:
Using this tool and the full recovery package? Or am I missing something here?
Click to expand...
Click to collapse
The tool posted does not contain a system, but he is going to post the full one soon.
Zyxxeil said:
The tool posted does not contain a system, but he is going to post the full one soon.
Click to expand...
Click to collapse
Precisely, that is exactly what I meant. Fingers crossed that will solve this.
It could be I successfully recoverd following a hint by user @Zyxxeil (many thanks for the help).
If all works I will post soon what I did.
But - have everything running now again. Next I try to flash twrp again and root. If that worked, I will post the steps.
Andi
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Very nice. Wait for it...
Is a Version with Oxygen OS also aviable?
Hi,
so, I got my Honor 5x rooted and CM 13 installed a few months ago from this thread: http://forum.xda-developers.com/hon...-unofficial-cyanogenmod-13-0-nightly-t3344499.
Last week or so some apps just didn't exist any more on my phone. Also I wasn't able to download any kinds of things, like apps, documents, pictures or whatever. After some time I figured out, that it was because of my SD-card being dead. When I removed it, all was fine again.
Another problem, that I got from the beginnning of having this ROM installed, I wasn't able to do updates, still don't know why exactly.
So I decided to wipe my phone and reinstall a newer version of CM in hope, that all would be fine again.
After performing backups and so on, I downloaded the latest build of CM from the official website (the one from 1st october) and GApps with ARM64, pushed it on my device and tried to install it with TWRP 3.0.2. I did a full wipe before, also deleting internal storage and System.
Error 7 occured and after some Internet research I read about this "assert" line. Figured out, that I got 2 oft them in this file and deleted the second telling something about the TB number, because it was also named in the error of TWRP.
Then pushed it on the device again and tried to install it. There was no error while installing, but after optimizing the apps, I got bootloops. Tried flashing other ROMs, including the one I got two days before, but it still got the same problem.
Also this huawei eRecovery thingy couldn't help me.
Now I don't know how to get an OS on my phone again, it would be very nice if someone could help me.
I also don't know whether there is a thread, that already deals with this topic, but I didn't know how to search for this.
If there is anything left unclear I'm very sorry, it's my first time posting, please excuse.
Thank you!
MrKnight230 said:
Hi,
so, I got my Honor 5x rooted and CM 13 installed a few months ago from this thread: http://forum.xda-developers.com/hon...unofficial-cyanogenmod-13-0-nightly-t3344499.
Last week or so some apps just didn't exist any more on my phone. Also I wasn't able to download any kinds of things, like apps, documents, pictures or whatever. After some time I figured out, that it was because of my SD-card being dead. When I removed it, all was fine again.
Another problem, that I got from the beginnning of having this ROM installed, I wasn't able to do updates, still don't know why exactly.
So I decided to wipe my phone and reinstall a newer version of CM in hope, that all would be fine again.
After performing backups and so on, I downloaded the latest build of CM from the official website (the one from 1st october) and GApps with ARM64, pushed it on my device and tried to install it with TWRP 3.0.2. I did a full wipe before, also deleting internal storage and System.
Error 7 occured and after some Internet research I read about this "assert" line. Figured out, that I got 2 oft them in this file and deleted the second telling something about the TB number, because it was also named in the error of TWRP.
Then pushed it on the device again and tried to install it. There was no error while installing, but after optimizing the apps, I got bootloops. Tried flashing other ROMs, including the one I got two days before, but it still got the same problem.
Also this huawei eRecovery thingy couldn't help me.
Now I don't know how to get an OS on my phone again, it would be very nice if someone could help me.
I also don't know whether there is a thread, that already deals with this topic, but I didn't know how to search for this.
If there is anything left unclear I'm very sorry, it's my first time posting, please excuse.
Thank you!
Click to expand...
Click to collapse
No problem mate, Community is Here to help!
The matter is, ROMs built after 18/8/2016 requires that you upgrade to Marshmallow stock ROM that means EMUI 4.0.
then you can flash the custom ROMs without problems.
If you're on bootloop, can you boot to fastboot or TWRP manually?
MrKnight230 said:
Hi,
so, I got my Honor 5x rooted and CM 13 installed a few months ago from this thread: http://forum.xda-developers.com/hon...unofficial-cyanogenmod-13-0-nightly-t3344499.
Last week or so some apps just didn't exist any more on my phone. Also I wasn't able to download any kinds of things, like apps, documents, pictures or whatever. After some time I figured out, that it was because of my SD-card being dead. When I removed it, all was fine again.
Another problem, that I got from the beginnning of having this ROM installed, I wasn't able to do updates, still don't know why exactly.
So I decided to wipe my phone and reinstall a newer version of CM in hope, that all would be fine again.
After performing backups and so on, I downloaded the latest build of CM from the official website (the one from 1st october) and GApps with ARM64, pushed it on my device and tried to install it with TWRP 3.0.2. I did a full wipe before, also deleting internal storage and System.
Error 7 occured and after some Internet research I read about this "assert" line. Figured out, that I got 2 oft them in this file and deleted the second telling something about the TB number, because it was also named in the error of TWRP.
Then pushed it on the device again and tried to install it. There was no error while installing, but after optimizing the apps, I got bootloops. Tried flashing other ROMs, including the one I got two days before, but it still got the same problem.
Also this huawei eRecovery thingy couldn't help me.
Now I don't know how to get an OS on my phone again, it would be very nice if someone could help me.
I also don't know whether there is a thread, that already deals with this topic, but I didn't know how to search for this.
If there is anything left unclear I'm very sorry, it's my first time posting, please excuse.
Thank you!
Click to expand...
Click to collapse
Try to get back to stock firmware, to do that download the latest firmware, extract to get dload folder containing UPDATE.APP, use Huawei update extractor to extract recovery, Cust, boot and system images.
Flash them to your phone using fastboot, put dload folder in the root of an SD, insert it in your phone and press and hold vol up + vol down + power until the phone boots up to force an update.
Have you already tried this? If not, do this please.
If yes, please elaborate "erecovery could not help me*...
Sent from my PLK-L01 using XDA Labs
mumith3 said:
No problem mate, Community is Here to help!
The matter is, ROMs built after 18/8/2016 requires that you upgrade to Marshmallow stock ROM that means EMUI 4.0.
then you can flash the custom ROMs without problems.
If you're on bootloop, can you boot to fastboot or TWRP manually?
Click to expand...
Click to collapse
Thanks for the fast reply!
Just got a softbrick, can still enter fastboot and so on.
I already found a stock version, but didn't know how to install it 'cause it wasn't a zip... :3
MrKnight230 said:
Thanks for the fast reply!
Just got a softbrick, can still enter fastboot and so on.
I already found a stock version, but didn't know how to install it 'cause it wasn't a zip... :3
Click to expand...
Click to collapse
What file did you get (link) ?
theirs no need to use the HuaweiUpdateExtractor, unless you need the stock recovery from it.
all you need is Stock recovery (installed) and the Update.app for your current version
Update.app goes in a folder named dload on the sdcard, now simply shut the phone off and restart it while holding power + volup + voldown
after 5 seconds let go of the power button and continuing holding the vol buttons till you see the update begin (around 25 seconds)
MrKnight230 said:
Thanks for the fast reply!
Just got a softbrick, can still enter fastboot and so on.
I already found a stock version, but didn't know how to install it 'cause it wasn't a zip... :3
Click to expand...
Click to collapse
Is it an update.app file?
Then you have to force update. Refer to @clsA 's thread.
Cheers.
clsA said:
What file did you get (link) ?
theirs no need to use the HuaweiUpdateExtractor, unless you need the stock recovery from it.
all you need is Stock recovery (installed) and the Update.app for your current version
Update.app goes in a folder named dload on the sdcard, now simply shut the phone off and restart it while holding power + volup + voldown
after 5 seconds let go of the power button and continuing holding the vol buttons till you see the update begin (around 25 seconds)
Click to expand...
Click to collapse
mumith3 said:
Is it an update.app file?
Then you have to force update. Refer to @clsA 's thread.
Cheers.
Click to expand...
Click to collapse
muradulislam said:
Try to get back to stock firmware, to do that download the latest firmware, extract to get dload folder containing UPDATE.APP, use Huawei update extractor to extract recovery, Cust, boot and system images.
Flash them to your phone using fastboot, put dload folder in the root of an SD, insert it in your phone and press and hold vol up + vol down + power until the phone boots up to force an update.
Have you already tried this? If not, do this please.
If yes, please elaborate "erecovery could not help me*...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Got it from this page for KIW-L21: stech guide.com/honor-5x-stock-marshmallow-firmware/ (I'm not allowed to post links yet because I'm new.. You just need to delete the space, should work then)
Sadly I got the file deleted and have to download it again, but right now my Internet is slow af.. Gonna need at least 5 hours to go...
MrKnight230 said:
Got it from this page for KIW-L21: stech guide.com/honor-5x-stock-marshmallow-firmware/ (I'm not allowed to post links yet because I'm new.. You just need to delete the space, should work then)
Sadly I got the file deleted and have to download it again, but right now my Internet is slow af.. Gonna need at least 5 hours to go...
Click to expand...
Click to collapse
Well, Wait, Honor 5x has many variants. So download only your device variant
Search this thread >>> http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
Hope it helps.:highfive:
Cheers! :good:
mumith3 said:
Well, Wait, Honor 5x has many variants. So download only your device variant
Search this thread >>> http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
Hope it helps.:highfive:
Cheers! :good:
Click to expand...
Click to collapse
got the right one now, download worked faster than expected.
Is there any possibility to install the dload file without using a sd-card?
MrKnight230 said:
got the right one now, download worked faster than expected.
Is there any possibility to install the dload file without using a sd-card?
Click to expand...
Click to collapse
No mate, You'll need a SD card.!!!
mumith3 said:
No mate, You'll need a SD card.!!!
Click to expand...
Click to collapse
clsA said:
What file did you get (link) ?
theirs no need to use the HuaweiUpdateExtractor, unless you need the stock recovery from it.
all you need is Stock recovery (installed) and the Update.app for your current version
Update.app goes in a folder named dload on the sdcard, now simply shut the phone off and restart it while holding power + volup + voldown
after 5 seconds let go of the power button and continuing holding the vol buttons till you see the update begin (around 25 seconds)
Click to expand...
Click to collapse
muradulislam said:
Try to get back to stock firmware, to do that download the latest firmware, extract to get dload folder containing UPDATE.APP, use Huawei update extractor to extract recovery, Cust, boot and system images.
Flash them to your phone using fastboot, put dload folder in the root of an SD, insert it in your phone and press and hold vol up + vol down + power until the phone boots up to force an update.
Have you already tried this? If not, do this please.
If yes, please elaborate "erecovery could not help me*...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Phone works again now! I love all of you!!!
MrKnight230 said:
Phone works again now! I love all of you!!!
Click to expand...
Click to collapse
Enjoy and do come back
Just kidding...
Sent from my PLK-L01 using XDA Labs
Hi all,
I recently got a new Axon 7 (A2017U) and wanted to root it just like my old G3. I tried following DrakenFX's instructions (Here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), but I got lost. I ended up with a password being requested at the android startup screen. In a panic, I clicked Format Data when I got back into TWRP, that made it worse and I went into EDL to see if that might help. Eventually I got back into TWRP and that's where I am now, desperately trying to get my new phone working again. All the threads I read only add another layer of confusion. Would someone be willing to walk me through the steps of fixing my phone? I really don't want to RMA/have $400 to go down the drain. I'd own you a big one.
-RG
video_dewd said:
Hi all,
I recently got a new Axon 7 (A2017U) and wanted to root it just like my old G3. I tried following DrakenFX's instructions (Here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), but I got lost. I ended up with a password being requested at the android startup screen. In a panic, I clicked Format Data when I got back into TWRP, that made it worse and I went into EDL to see if that might help. Eventually I got back into TWRP and that's where I am now, desperately trying to get my new phone working again. All the threads I read only add another layer of confusion. Would someone be willing to walk me through the steps of fixing my phone? I really don't want to RMA/have $400 to go down the drain. I'd own you a big one.
-RG
Click to expand...
Click to collapse
Hi,
so you have access to the TWRP. Thats good. Do you have access to a stock ROM from your manufacturer? In case yes, you could simply flash the stock.
For this, the rom has to be on a SD card or on the internal memory of the phone.
In TWRP go to "Install", than navigate to the file and swipe to install (it comes a zip file).
mugel2110 said:
Hi,
so you have access to the TWRP. Thats good. Do you have access to a stock ROM from your manufacturer? In case yes, you could simply flash the stock.
For this, the rom has to be on a SD card or on the internal memory of the phone.
In TWRP go to "Install", than navigate to the file and swipe to install (it comes a zip file).
Click to expand...
Click to collapse
I'm looking for one. Some threads pointed to an OTA update that ZTE has on their site. However, when I try to install things on TWRP, I get an error about "dev/block/sde14" being read-only. (It sometimes says "sde13" too.)
video_dewd said:
I'm looking for one. Some threads pointed to an OTA update that ZTE has on their site. However, when I try to install things on TWRP, I get an error about "dev/block/sde14" being read-only. (It sometimes says "sde13" too.)
Click to expand...
Click to collapse
Dis you go on Advanced
Wipe dalvik-chace
Wipe /cache
Do you have access to fastboot?
mugel2110 said:
Dis you go on Advanced
Wipe dalvik-chace
Wipe /cache
Do you have access to fastboot?
Click to expand...
Click to collapse
Yes and I'm not sure. I can boot to system, recovery, and bootloader.
video_dewd said:
Yes and I'm not sure. I can boot to system, recovery, and bootloader.
Click to expand...
Click to collapse
I am far from being a pro. I once had the problem that I was caught in bootloop and could not install a new rom. But I was able to re-flash TWRP (via Minimal adb and fastboot) and than everything was fine.
Maybe someone else can comment on that. On your own risk...
Just a tip. Never panic and press any button
mugel2110 said:
Just a tip. Never panic and press any button
Click to expand...
Click to collapse
I figured haha
Has anyone done a ROM backup (preferably scatter, but a fastboot backup may do) for these things? Been trying to get this demo unit to cooperate with SP Flash Tool lately, but I end up with a DA DOWNLOAD FAIL error. @diplomatic says this may be due to a restricted bootloader or something along the lines of it (MTK bootloaders by design are able to restrict access to SPFT afaik), but does anyone have or know how to get this off a working device?
blakegriplingph said:
Has anyone done a ROM backup (preferably scatter, but a fastboot backup may do) for these things? Been trying to get this demo unit to cooperate with SP Flash Tool lately, but I end up with a DA DOWNLOAD FAIL error. @diplomatic says this may be due to a restricted bootloader or something along the lines of it (MTK bootloaders by design are able to restrict access to SPFT afaik), but does anyone have or know how to get this off a working device?
Click to expand...
Click to collapse
Have you already tried holding volume up and/or volume down while inserting the cable? Or even disconnecting the battery? This might force it into boot ROM mode (Mediatek USB Port).
diplomatic said:
Have you already tried holding volume up and/or volume down while inserting the cable? Or even disconnecting the battery? This might force it into boot ROM mode (Mediatek USB Port).
Click to expand...
Click to collapse
Hmm, let me try that. I can more or less rule out the battery method as I have to crack this thing open i.e. heat up the touchscreen to gain access to the battery. :/
Bumping in case someone with a Nabi SE can do a ROM dump.
Anyone?
Would you be able to flash the original room if your getting bootloops after putting twrp recovery on it?
Gigabuster said:
Would you be able to flash the original room if your getting bootloops after putting twrp recovery on it?
Click to expand...
Click to collapse
Yup, and it would be prudent for you to have made an SP Flash Tool backup of the SE first before you even mess with it.
Sorry to bother. My digitizer seems a little better after wipe with twrp, but now I am unable to get system to mount to install different ROM. I know there is a backup posted but I am unsure if that will work for the se. Also, if I can find it after moving I have a twrp backup I made of nabi se if it helps with any type of development
Q is will that backup suffice for the se nabi2? running 3.0 sw I believe... Thx in advance
remarkablecow913 said:
Sorry to bother. My digitizer seems a little better after wipe with twrp, but now I am unable to get system to mount to install different ROM. I know there is a backup posted but I am unsure if that will work for the se. Also, if I can find it after moving I have a twrp backup I made of nabi se if it helps with any type of development
Q is will that backup suffice for the se nabi2? running 3.0 sw I believe... Thx in advance
Click to expand...
Click to collapse
Try flashing system.img and boot from this backup I made using SP Flash Tool, or perhaps the Flash Image feature built into TWRP:
Code:
https://www.4shared.com/rar/UzxacJrUfi/NBTY07SMKG_160823_ForFlashtool.html
Nm. I was able to download. Thank you very much for the help.
blakegriplingph said:
Try flashing system.img and boot from this backup I made using SP Flash Tool, or perhaps the Flash Image feature built into TWRP:
Click to expand...
Click to collapse
remarkablecow913 said:
Nm. I was able to download. Thank you very much for the help.
Click to expand...
Click to collapse
You're welcome!