Hi there,
I have rooted kindle fire hdx 7.
I can't install twrp, so i decide to do it from flashify.
After Reboot, bootloop issue came
Help me till i decide to kill myself for stutipdness.
arshileus said:
Hi there,
I have rooted kindle fire hdx 7.
I can't install twrp, so i decide to do it from flashify.
After Reboot, bootloop issue came
Help me till i decide to kill myself for stutipdness.
Click to expand...
Click to collapse
Attempting to flash a custom recovery (TWRP) on a HDX with with 'standard' bootloader destroys the stock recovery which is required for FireOS to boot. Restoration is not easy and essentially involves rebuilding the device. There are posts throughout this forum that outline what needs to happen but no dedicated threads or step-by-step process. You'll either need to do a ton of reading or simply accept the device is borked and move on.
Davey126 said:
Attempting to flash a custom recovery (TWRP) on a HDX with with 'standard' bootloader destroys the stock recovery which is required for FireOS to boot. Restoration is not easy and essentially involves rebuilding the device. There are posts throughout this forum that outline what needs to happen but no dedicated threads or step-by-step process. You'll either need to do a ton of reading or simply accept the device is borked and move on.
Click to expand...
Click to collapse
or simply can kill myself, cause i spent a lot of money :/ oh, god... jesus...
arshileus said:
or simply can kill myself, cause i spent a lot of money :/ oh, god... jesus...
Click to expand...
Click to collapse
Sorry dude, flashify only works to upgrade/downgrade TWRP on this device, not to make a fresh intall
You forgot unlock bootloader first,neccesary to install TWRP, thats why your device its bricked, if you can get ADB connectivity on the PC using USB Cable, you could have some chance to revive the device.
The easy way : Find a used Kindle with dead display/battery or a new motherboard , to replace the bricked one.
Before do something in your device, always read about the necessary tools/ instructions/ procedures, and make all your questions here.
Tossing out a few clarifications for future readers:
Yousucks2 said:
Sorry dude, flashify only works to upgrade/downgrade TWRP on this device, not to make a fresh intall
Click to expand...
Click to collapse
Flashify can be used for a fresh install if bootloader is unlocked (always) or in special cases (eg: signed image).
Yousucks2 said:
You forgot unlock bootloader first,neccesary to install TWRP, thats why your device its bricked, if you can get ADB connectivity on the PC using USB Cable, you could have some chance to revive the device.
Click to expand...
Click to collapse
Yep - a real boneheaded move. Recovery is also possible by dumping device into 'bulk mode' which is an advanced recovery technique that requires both patience and some technical experience (not to mention attentive reading skills).
Yousucks2 said:
The easy way : Find a used Kindle with dead display/battery or a new motherboard , to replace the bricked one.
Before do something in your device, always read about the necessary tools/ instructions/ procedures, and make all your questions here.
Click to expand...
Click to collapse
HDX disassembly is not for the faint of heart due to copious use of glue; cracked screens are common trying to pry open the clam shell. Probably best to go the 'bulk mode' route first which itself is not easy. My recommendation is to sell the device for parts and pickup up another on an auction site.
Davey126 said:
Tossing out a few clarifications for future readers:
Flashify can be used for a fresh install if bootloader is unlocked (always) or in special cases (eg: signed image).
Yep - a real boneheaded move. Recovery is also possible by dumping device into 'bulk mode' which is an advanced recovery technique that requires both patience and some technical experience (not to mention attentive reading skills).
HDX disassembly is not for the faint of heart due to copious use of glue; cracked screens are common trying to pry open the clam shell. Probably best to go the 'bulk mode' route first which itself is not easy. My recommendation is to sell the device for parts and pickup up another on an auction site.
Click to expand...
Click to collapse
Can you show me any guidelines to understand how hard is it....
arshileus said:
Can you show me any guidelines to understand how hard is it....
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
Not sure...
Davey126 said:
https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
Click to expand...
Click to collapse
This will only work if adb or fastboot can still connect,
but in that case I'd suggest to try 1-Click pre-release to
click through a web-UI. No reading required... (-;
BTW, is recovery _really_ checked/needed for FireOS to boot?
I suspect that flashify (or the OP) did more than just overwrite recovery,
which can be _really_bad_ if the bootloader is still locked, since the key
combo to enter fastboot doesn't work...
draxie said:
BTW, is recovery _really_ checked/needed for FireOS to boot? I suspect that flashify (or the OP) did more than just overwrite recovery, which can be _really_bad_ if the bootloader is still locked, since the key combo to enter fastboot doesn't work...
Click to expand...
Click to collapse
In my experience 'yes' to boot although there are obviously exceptions including those running FireOS with a custom recovery on a locked (but still vulnerable) device. Whether the stock recovery contents are actually used or something else happens is unknown...at least to me. Symptom wise a borked recovery is almost always leads to boot issues.
draxie said:
BTW, is recovery _really_ checked/needed for FireOS to boot?
I suspect that flashify (or the OP) did more than just overwrite recovery,
which can be _really_bad_ if the bootloader is still locked, since the key
combo to enter fastboot doesn't work...
Click to expand...
Click to collapse
Seems the issue I'm experiencing
I have got another fire hdx 7.
How i can unlock bootloader? Where is guideline?
arshileus said:
I have got another fire hdx 7.
How i can unlock bootloader? Where is guideline?
Click to expand...
Click to collapse
Same thread as previously linked (here). It is NOT a step-by-step idiot proof guide. You will need to do some advance reading. Suggest digesting the OP then reviewing the last 2-3 months of posts to get a 'feel' for what is required and the questions you may have.
I have done this before on windows 10 . But i am on windows 7 now.
After i clicking on unlock.bat, device goes to fastboot mode. At this time i cant find "android" with warning sign in device manager. I have unrecognised usb device, so i cant set it to usb composite.
What to do? what i miss?
p.s when i am trying use google or amazon drivers set up after fastboot manually selecting from device manager, it says: incompatible.
arshileus said:
I have done this before on windows 10 . But i am on windows 7 now.
After i clicking on unlock.bat, device goes to fastboot mode. At this time i cant find "android" with warning sign in device manager. I have unrecognised usb device, so i cant set it to usb composite.
What to do? what i miss?
p.s when i am trying use google or amazon drivers set up after fastboot manually selecting from device manager, it says: incompatible.
Click to expand...
Click to collapse
Can you help me?
arshileus said:
Can you help me?
Click to expand...
Click to collapse
Could be a borked device, unstable usb interface (either device) or bad cable. Work backwards by trying different cables, different ports on the host (avoid USB3 and hubs) and different hosts. If results are the same you may have a bad device. Good luck.
Related
Q&A for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)
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 [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42). 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!
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
hhzznn said:
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
Click to expand...
Click to collapse
Hello there,
If not using the "adbsetup" drivers or the ones off the ASUS website (sorry, couldn't find the ASUS drivers when I looked ), use one of the above. If using one and still not connecting, try the other option.
Also, check your USB ports to make sure you are not connecting via a USB 3.x standard. Android (or at least some Android devices) don't like those.
If all else fails, you may need a Linux build
Hope this provides a head start.
Sent from my LG-D520 using XDA Free mobile app
help me please
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
hhzznn said:
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
Click to expand...
Click to collapse
Looks you got a little further... :good:
From what I remember when I followed the guide, there was no feedback (nothing on the screen, and tablet remains black) on when you issue the unlock commands - which by the way, are:
Code:
fastboot oem unlock61646
fastboot oem unlockD696E
Then, reboot the bootloader and install CWM (first line may be substituted with rebooting into fastboot by hand):
Code:
fastboot reboot-bootloader
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
You shouldn't get a write-protect error this time around. Hope this helps.
By the way, your SKU is WW version, right? If not, my ROM may not help you (without going the long way around of instead of flashing the ROM, copying the odex files back into /system/app using CWM's ADB push command). Just a warning. If you are not WW, and insist on flashing anyway, I would highly recommend a nandroid backup (and probably copied) to MicroSD to protect your original (broken) ROM.
help me
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
hhzznn said:
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
Click to expand...
Click to collapse
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
the code:fastboot unlock oem61646 worked but fastboot oemD696E not working
in stock recovery i cant install rom.zip
and in fastboot when install recovery cwm answer bootloader lock
any offer for me?
---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------
**you may need a Linux build **
i have a linux base ,, may you help me??
hhzznn said:
**you may need a Linux build **
i have a linux base ,, may you help me??
Click to expand...
Click to collapse
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
i have ubuntu....what should i do?
hhzznn said:
i have ubuntu....what should i do?
Click to expand...
Click to collapse
In a terminal...
apt-get install android-tools-fastboot
...would be a good start. You may need to register the device vendor in your configuration, which I can research later if...
fastboot devices
...lists nothing. Hope this helps.
Sent from my LG-D520 using XDA Free mobile app
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Syncline said:
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Click to expand...
Click to collapse
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
joel.maxuel said:
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
Click to expand...
Click to collapse
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Syncline said:
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Click to expand...
Click to collapse
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
joel.maxuel said:
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
Click to expand...
Click to collapse
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Syncline said:
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Click to expand...
Click to collapse
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
joel.maxuel said:
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
No I wasn't encrypted before but from what I read it seems to involve a failure to mount the DATA partition correctly, and the Android OS erroneously assumes it's encrypted. I'm not overly concerned about setting up apps by hand, I do have a titanium backup of my apps and data. As I'm still at work, I can't do too much playing around on my tablet. I don't have access to my personal computer that has all my tools like adb, fastboot, etc. until the work day is done. I've said it a couple of times, but I truly appreciate the assistance that you've provided.
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Syncline said:
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Click to expand...
Click to collapse
That's an interesting side effect...never had that happen before.
You can try it, and let me know. Hopefully your CWM is still kicking around, or else you will have to reinstall via fastboot. Or alternatively, just re-root normally (like with Kingo).
By the way, before you do that, does /system/xbin/su exist? Or what you could answer, is you could download Voodoo OTA RootKeeper and report back which values are not checked off. I think SuperSU update.zip places the su binary, nothing else. But we shall see.
Sorry Joel, I didn't see your reply before I flashed the SuperSU zip but it did work, my tablet is rooted again.
I would like to know how to upgrade to a new ROM (Lollipop or better) on my Verizon HTC One Max with the option to return to stock. Software Information: 4.4.2, Sense 6.0, 3.09.605.3, 6.20, 4.60_002, 15432, 5
I was told to use (and did) Sunshine and then downloaded SuperSU from Google Store (per very detailed instructions and was told to not choose TWRP when the question popped up to choose one or the other (common/normal?)).
My phone is now UNLOCK and S-OFF as well as Rooted (but I'm having a lot of problems with blank screens, etc. and even had the black screen with the red ! in a red triangle (and I don’t know how I got it to boot up again (pushed pwr buttons, vol +/-, etc.)). However, that is as far as I’ve gotten. Confused am I.
I don’t know how to flash; however, I’ve been trying to figure it out, but I’m lost.
I’ve downloaded a lot of files from other threads, but the instructions, while detailed, didn’t say HOW to flash or add TWRP where I (a NEWBORN NEWBIE/NOOBIE) could understand, etc. Is there a place where all this is together?
Am I out of luck or would someone PLEASE help me fix and upgrade it with the option to return to stock if needed? I would love to have Sense 7.0, if possible. I apologize for such a long post/thread.
THANK YOU SO VERY MUCH!!!!!
P. S. My phone is now Prepaid Verizon (was Postpaid). Don't know if that matters. I have pics of the files I downloaded from one of your great guys, but they are on my computer. Not sure how to upload. I AM GLAD THAT I FOUND YOUR SITE!!!!!
@LoveSpock I am going to make this short and simple...
First off the Verizon Max software only goes up to 4.4.2. If you want to upgrade you'll need a custom rom which is why you S-OFF and unlocked...
You will need to get familiar with fastboot commands. Google is your friend on how to use if you don't know how to. Here is the link to the TWRP image for your device. http://flyhalf205.com/recoveries/openrecovery-twrp-2.8.7.1-t6univ.img Once you get fastboot setup you will type in the command fastboot flash recovery openrecovery-twrp-2.8.7.1-t6univ.img Make sure you have everything in the same directory when executing the command.
From there you are free to wipe then flash anything you would like. Wiping will delete your data so text, contacts that are stored on local phone(not sim or google) will be deleted.
@Flyhalf205
Thank you for your response and instructions. Does this mean I don't need to do anything to the SUPERSU that is already on the phone (and what it did)?.... Following your instructions will wipe everything?
I'll definitely need to take out my sd card. I've saved a ton of stuff on it. ...and backup my contacts and text messages.
I have some more googling and try to learn what you wrote for me to learn. I'll also have to find out what ROM to use....
Your Padawan thanks you.
LoveSpock said:
@Flyhalf205
Thank you for your response and instructions. Does this mean I don't need to do anything to the SUPERSU that is already on the phone (and what it did)?.... Following your instructions will wipe everything?
I'll definitely need to take out my sd card. I've saved a ton of stuff on it. ...and backup my contacts and text messages.
I have some more googling and try to learn what you wrote for me to learn. I'll also have to find out what ROM to use....
Your Padawan thanks you.
Click to expand...
Click to collapse
Shouldn't worry about supersu. Most custom ROMs are going to have that prebuilt into it. Once you get TWRP we will go further into detail about how stuff works.
If you use twrp no need to take your SD card out just go to setting and unchecked SD card and like lovespoke said make sure to dl the right file you can dl right fastboot files here on xda just search it
Hey! Don't mean to hijack the thread but I'm in the same boat. I've never rooted and I'm looking to root my Verizon HTC one max. I'd also like to maybe install a custom Rom but I'm a noob so I'm not quite sure what I'm doing. Ok so it's my understanding that sunshine will root, s-off, AND unlock my boot loader? Btw I have no idea what those terms mean. Anyway, if someone could please confirm that about sunshine, it would really help me out. I've already downloaded and installed sunshine on my phone but I haven't paid the $25 yet.
Xx Moe, I strongly suggest you READ the various threads on XDA about unlocking bootloaders, gaining S-OFF and rooting. You can easily brick a device and there's much less support for the Max now than there was when it came out more than two years ago.
I don't believe Verizon HTC One Max's can be rooted without unlocking bootloader/gaining S-OFF and the exclusive method for that is Sunshine (unless you know someone with a Java card). Once you're bootloader unlocked and S-OFF, you can then "flash" any partition on the device and that's how to brick the device.
Once you are bootloader unlocked and S-OFF, you start by flashing a 'recovery', which is usually the latest version of TWRP for the HTC One Max. Don't flash a recovery for a different device. (Google "Team Win Recovery Project"). Once you have a custom recovery you can "wipe" your device and flash a new ROM.
Wiping deletes all data, or some data, depending upon how you wipe, and there are not very many Verizon HTC One Max ROMs out there that are fully functional. Check the threads, one sticky thread has a listing of ROMs.
Finally, I don't believe anyone has gotten Marshmallow going on a Max, so expect the "best" you'll be able to do is a Lollipop ROM or a Cyanogen Mod equivalent.
Awesome! Thanks for the super quick reply. So yes, sunshine will s-off and unlock boot loader. That seemed to be the million dollar question since (like you said) the one max doesn't have very much support anymore. I'm definitely going to keep reading the forums because I don't want to brick my phone. I've also been watching some tutorials on YouTube. Everything (so far) seems pretty straight forward now, but you can never be too careful. Thanks for your help hgoldner!
Flyhalf205 said:
@LoveSpock I am going to make this short and simple...
First off the Verizon Max software only goes up to 4.4.2. If you want to upgrade you'll need a custom rom which is why you S-OFF and unlocked...
You will need to get familiar with fastboot commands. Google is your friend on how to use if you don't know how to. Here is the link to the TWRP image for your device. http://flyhalf205.com/recoveries/openrecovery-twrp-2.8.7.1-t6univ.img Once you get fastboot setup you will type in the command fastboot flash recovery openrecovery-twrp-2.8.7.1-t6univ.img Make sure you have everything in the same directory when executing the command.
From there you are free to wipe then flash anything you would like. Wiping will delete your data so text, contacts that are stored on local phone(not sim or google) will be deleted.
Click to expand...
Click to collapse
Hey flyhalf, is there a thread on here on how to learn about adb fastboot, and flash the custom recovery for noobs? I cant seem to find it. I'm trying to install a custom rom on my htc one max but this is my first time ever rooting/unlocking an android. Ive searched the site but i cant find a tutorial on how to install the custom recovery or learn about adb yet. I have sunshine already on my phone but i havent used it yet because i want to know exactly what im doing before i pay the $25. Any help is appreciated. I already know how to get into the bootloader by pressing the power and volume down buttom at the same time while the phone is turned off.
Xx MOE said:
Hey flyhalf, is there a thread on here on how to learn about adb fastboot, and flash the custom recovery for noobs? I cant seem to find it. I'm trying to install a custom rom on my htc one max but this is my first time ever rooting/unlocking an android. Ive searched the site but i cant find a tutorial on how to install the custom recovery or learn about adb yet. I have sunshine already on my phone but i havent used it yet because i want to know exactly what im doing before i pay the $25. Any help is appreciated. I already know how to get into the bootloader by pressing the power and volume down buttom at the same time while the phone is turned off.
Click to expand...
Click to collapse
I'm heading to bed now. If I get time tomorrow I'll try to explain. If not we can setup team viewer and I can just set your computer up for you.
Sent from my Nexus 9 using Tapatalk
Flyhalf205 said:
I'm heading to bed now. If I get time tomorrow I'll try to explain. If not we can setup team viewer and I can just set your computer up for you.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
That would be awesome, but i think i found something from google. https://twrp.me/devices/htconemaxverizon.html
I downloaded the sdk and corresponding java that the site recommended. I attached a screenshot of my pc to show where im at in that process.
Xx MOE said:
That would be awesome, but i think i found something from google. https://twrp.me/devices/htconemaxverizon.html
I downloaded the sdk and corresponding java that the site recommended. I attached a screenshot of my pc to show where im at in that process.
Click to expand...
Click to collapse
I also downloaded the android-sdk_r24.4.1-windows.zip file but i moved it out of my downloads file, so it didn't show up on my screenshot
Xx MOE said:
I also downloaded the android-sdk_r24.4.1-windows.zip file but i moved it out of my downloads file, so it didn't show up on my screenshot
Click to expand...
Click to collapse
Download the platform tools and the android usb driver. Don't need anything else.
But basically if your s-off yet. Boot into HBOOT. Power off phone and hold down both power button and the volume down button. Select fastboot using the power button. Your computer should hopefully automatically pick up drivers and call the device "My HTC" in the device manager. If not you'll need to go in and manually assign the downloaded driver using the link above to the Android device in device manager.
Download twrp image file into the same directory as the platform tools downloaded to. In windows, right click while holding down shift anywhere on the white blank area in platform tools and click on "open command window here".. From there you will type in the command fastboot flash recovery recoveryFileName.img
If it says waiting for device. Check device manager and make sure the driver is installed right.
Flyhalf205 said:
Download the platform tools and the android usb driver. Don't need anything else.
But basically if your s-off yet. Boot into HBOOT. Power off phone and hold down both power button and the volume down button. Select fastboot using the power button. Your computer should hopefully automatically pick up drivers and call the device "My HTC" in the device manager. If not you'll need to go in and manually assign the downloaded driver using the link above to the Android device in device manager.
Download twrp image file into the same directory as the platform tools downloaded to. In windows, right click while holding down shift anywhere on the white blank area in platform tools and click on "open command window here".. From there you will type in the command fastboot flash recovery recoveryFileName.img
If it says waiting for device. Check device manager and make sure the driver is installed right.
Click to expand...
Click to collapse
Ok, so if im doing this correctly, the twrp img should be in the platform tools folder and my computer should recognize my phone as "my htc" as shown in my attached screenshot...
Xx MOE said:
Ok, so if im doing this correctly, the twrp img should be in the platform tools folder and my computer should recognize my phone as "my htc" as shown in my attached screenshot...
Click to expand...
Click to collapse
Yes. That is correct so far.
Flyhalf205 said:
Yes. That is correct so far.
Click to expand...
Click to collapse
Perfect! Thank you so much! now all i have to do is use sunshine to s-off/unlock bootloader and follow this thread: http://forum.xda-developers.com/showthread.php?t=2498746 to install custom recovery and i should now be able to flash custom roms! Thanks for your help! A donation will be coming your way soon! :good::good::good::highfive:
Almost Ready....
Flyhalf205 said:
Shouldn't worry about supersu. Most custom ROMs are going to have that prebuilt into it. Once you get TWRP we will go further into detail about how stuff works.
Click to expand...
Click to collapse
I've been out of commission... Sorry about the long wait.
I'm sure you've been very busy.
I found the fastboot.exe file and placed it and your twrp file into a folder on my desktop. Before I run fastboot and add your twrp img file, what would the next step be? .... I don't have have a ROM yet to add to the phone. Should I have that first? Would you please direct me to the right one for me? I noted in one of your replies to another member that there isn't a Marshmallow one, yet.
Do I need the ADB file?
Thank you,
Your Padawan.
Flyhalf205 said:
Yes. That is correct so far.
Click to expand...
Click to collapse
Would you recommend uninstalling the HTC program that automatically picks up the phone?
LoveSpock said:
I've been out of commission... Sorry about the long wait.
I'm sure you've been very busy.
I found the fastboot.exe file and placed it and your twrp file into a folder on my desktop. Before I run fastboot and add your twrp img file, what would the next step be? .... I don't have have a ROM yet to add to the phone. Should I have that first? Would you please direct me to the right one for me? I noted in one of your replies to another member that there isn't a Marshmallow one, yet.
Do I need the ADB file?
Thank you,
Your Padawan.
Click to expand...
Click to collapse
I forget if you were s-off or s-on but you will need to be s-off or your bootloader will need to be unlocked.. You don't need a rom just yet. You could flash recovery and flash root for starters. But once you get it flashed we can start on what to do next.
Update...
Flyhalf205 said:
Shouldn't worry about supersu. Most custom ROMs are going to have that prebuilt into it. Once you get TWRP we will go further into detail about how stuff works.
Click to expand...
Click to collapse
Flyhalf205 said:
I forget if you were s-off or s-on but you will need to be s-off or your bootloader will need to be unlocked.. You don't need a rom just yet. You could flash recovery and flash root for starters. But once you get it flashed we can start on what to do next.
Click to expand...
Click to collapse
Sorry... I started the thread back in January. I've been out of commission and starting over.
I had used Sunshine to S-off and Unlock. I used SU to root. I knew nothing about flashing or fastboot and am still learning. One of your original responses to my original post said that google was my friend, so I googled per your advice and found some information on fastboot.
I don't know what flash root means in your response above.
You had also gave me the link to the TWRP image for my phone. You also wrote "Make sure you have everything in the same directory when executing the command." I've added 2 of the pics again as well as one of your img file in the directory I created when I loaded Android Studio.
The Android Studio I downloaded is the latest. Does that make a difference? I did find info on this site about a minimal adb and fastboot. Would that have been better?
I'm imagining my phone will be out of commission until the new ROM is installed, right? (See how I'm still such a Newbie/Noobie!)
Thank you!
Your Padawan
Welcome to Twrp 3.0.0.0 for our Zenwatch 2's
This release I was able to flash the recovery, flash the supersu zip, and flash some others, so far I have not encountered our wild soft brick madness.
Thanks to @acbka for showing me how to get into log files, essentially helping me figure out why the partitions were not mounting correctly when I compiled and recompiled.
Here is TWRP 3.0.0.0
Directions:
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot flash recovery twrp3.img
OR load up your tethered twrp and flash the image under that.
Hope you guys enjoy! So far I have not encountered soft bricks so it should be safe and sound
thank you, will test now
---------- Post added at 09:21 PM ---------- Previous post was at 09:01 PM ----------
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
okaay3D said:
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
Click to expand...
Click to collapse
That im not sure, it might, wouldnt hurt to fastboot boot it and see if itll start twrp. I have the 501
Root will go with modifying the Momentum kernel so you wont have much lag on the watch, and any other root modifications that can go with it, like maybe xposed?
Next step in development is fixing twrp so it can be flashed, then maybe modifying the wear os? Or maybe porting some stuff
T10NAZ said:
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting
Click to expand...
Click to collapse
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
matze19999 said:
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Click to expand...
Click to collapse
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Awesome! Got supersu flashed and was able to use Advanced Settings to disable some of the built-in bloatware apps. I'll have to try out the kernel but I'm currently at work and don't want to spend all day messing around with my watch (well... I want to, but I like not getting fired).
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I do have the 5.0.1 wear downloaded and installed! And as far as i know, Its working ok
okaay3D said:
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
Click to expand...
Click to collapse
You can tell twrp to preserve the system protection, back every single thing up that you can in the twrp option, push that backup to your computer, and then you can disable system protection. twrp itself wont do anything, however playing with options will modify the watch.
OR you can fastboot pull things off the watch, the system.img and boot.img yourself, in case the ones uploaded in my general thread didnt have the protection enabled.
If you want to hang tight until 1.4 comes out, that can be a good thing too
And im not sure if there is something like that on the watch. I have not seen anything about it before
My attempt was a failure on my WI502Q. I got the following messages. And, OP, how do you pull system.img from a device through fastboot? I thought you needed root permission to do that through adb.
"
C:\adb\zw2>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.834s
"
Thanks for this! I was losing hope on any development for this watch but now we have the most crucial component to modifying anything on android, a custom recovery. Going to perform a backup, root and flash your custom kernel you kindly released as well!
T10NAZ said:
Hello everyone, I have been working hard last night to make twrp run on our watches, and this I think is a good representation on what itll be like with actual development going on
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting, and I was able to flash some zips and kernels successfully, and I fixed the UI to look better and actually usable on the watch
Also, I was able to flash this puppy, and I got android wear to boot with it flashed, however most of the time, it goes haywire and only boots into recovery. Same thing applies, this shall be a Tethered recovery only until I know why its going crazy.
As always, problems can arise on your watch, so be careful!
read the entire instructions, This is a known way to get system protection off, and to flash zips/kernels when need be. Do not flash please.
Here is the link to the updated twrp
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot boot recovery.img like the other one.
I also have a kernel underway if people would like to try it out and test it in the next couple days
Click to expand...
Click to collapse
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
yash92duster said:
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
Click to expand...
Click to collapse
it could lead to that, yea, since this is the only root method basically, it adds a few extra steps to do it
can we root with regular supersu .zip, or do we need a special build for wear devices?
slothdabski said:
can we root with regular supersu .zip, or do we need a special build for wear devices?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view?usp=sharing there ya go. dunno if the regular supersu works. havent tried that out. this one does. and alrdy has a busybox installer wear app included which u need anyway sooner or later.
there is no supersu manager app in it though like on phones. apps requiring root just have it. tested advanced settings so far for disabling built-in stuff and a reboot option. but maybe there is a supersu-wear.apk somewhere?
not my link. taken from here: http://forum.xda-developers.com/showpost.php?p=65759835&postcount=14 he took it from the G watch R forums iirc.
zenwatch2
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
mehdi.ahmadi said:
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
Click to expand...
Click to collapse
Let me know the steps you took from when you downloaded it, to when it sits on the asus logo, and do you have the 502 or the 501 watch?
mehdi.ahmadi said:
after the flash twrp recovery
Click to expand...
Click to collapse
guess that means he flashed it. now his watch is bricked. not that it hasent been mentioned NOT to flash it just fastboot boot ...
flash the stock images via fastboot or tethered (NOT flashed) twrp and you should get your watch working again.
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
matze19999 said:
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Click to expand...
Click to collapse
found it about 2 weeks ago somewhere here on xda and alrdy linked it to several ppl here in the thread.
but thx
I did a search on XDA and didn't find anyone quite with this problem. I have other HDX both 7" and 8.9" that I have unlocked bootloader, installed TWRP, and installed ROM's on so I am not new to it.
However, I acquired an 8.9" HDX and it is stuck on the Nougat logo and just stays there. I can boot into fastboot as well as TWRP. When I booted into TWRP I tried factory reset (as it will come up on my computer to where I can access the storage using my Windows 10 machine) as well as Advanced Wipe but it will not wipe the Internal Storage. It still shows all the files that were on there before. How do I go about completely getting it clean to install a nice fresh custom ROM on it?
Any help would be greatly appreciated thanks all!
alias4ever said:
I did a search on XDA and didn't find anyone quite with this problem. I have other HDX both 7" and 8.9" that I have unlocked bootloader, installed TWRP, and installed ROM's on so I am not new to it.
However, I acquired an 8.9" HDX and it is stuck on the Nougat logo and just stays there. I can boot into fastboot as well as TWRP. When I booted into TWRP I tried factory reset (as it will come up on my computer to where I can access the storage using my Windows 10 machine) as well as Advanced Wipe but it will not wipe the Internal Storage. It still shows all the files that were on there before. How do I go about completely getting it clean to install a nice fresh custom ROM on it?
Any help would be greatly appreciated thanks all!
Click to expand...
Click to collapse
There's a chance the eMMC is damaged or a prior owner botched an unlock attempt. Might try booting a freshly downloaded TWRP image from fastboot in case the one that is installed has an issue. This will only work if the bootloader is unlocked.
fastboot boot <twrp.img>
Davey126 said:
There's a chance the eMMC is damaged or a prior owner botched an unlock attempt. Might try booting a freshly downloaded TWRP image from fastboot in case the one that is installed has an issue. This will only work if the bootloader is unlocked.
fastboot boot <twrp.img>
Click to expand...
Click to collapse
If the bootloader is indeed still locked and I have access to the bootloader can I unlock it still and start fresh? I take it the above I do inside the platform-tools folder correct? Thanks Davey so much for your help. I did this multiple times but it's been a while so I'm just trying to refresh my brain!
alias4ever said:
If the bootloader is indeed still locked and I have access to the bootloader can I unlock it still and start fresh? I take it the above I do inside the platform-tools folder correct? Thanks Davey so much for your help. I did this multiple times but it's been a while so I'm just trying to refresh my brain!
Click to expand...
Click to collapse
Consider following the steps in this post which nicely sumarizes the unlock procedure. Not for the faint of heart nor excessively difficult. Ability to closely follow instructions and troubleshoot issues are the keys to success...assuming hardware is ok.
Before jumping in try booting a twrp image to rule out a borked install in the recovery partition. Unlikely, but also easy to check.
Davey126 said:
Consider following the steps in this post which nicely sumarizes the unlock procedure. Not for the faint of heart nor excessively difficult. Ability to closely follow instructions and troubleshoot issues are the keys to success...assuming hardware is ok.
Before jumping in try booting a twrp image to rule out a borked install in the recovery partition. Unlikely, but also easy to check.
Click to expand...
Click to collapse
So to check I would just do what you suggested above with the Fire HDX in Fastboot and connected to my PC correct? Which was:
fastboot boot apollo_twrp-3.2.3-1.img in CMD correct? I just want to make sure I have "all my ducks in a row."
alias4ever said:
So to check I would just do what you suggested above with the Fire HDX in Fastboot and connected to my PC correct? Which was:
fastboot boot apollo_twrp-3.2.3-1.img in CMD correct? I just want to make sure I have "all my ducks in a row."
Click to expand...
Click to collapse
Yup. No damage can come from this attempt. It will either work or not.
Davey126 said:
Yup. No damage can come from this attempt. It will either work or not.
Click to expand...
Click to collapse
This is what I get when I try that:
FAIL: boot not allowed for locked hw.
Any suggestions please? Thanks again!
alias4ever said:
This is what I get when I try that:
FAIL: boot not allowed for locked hw.
Any suggestions please? Thanks again!
Click to expand...
Click to collapse
Indicates bootloader is locked. See previous posts for path forward. Note cautions; don't expect a lot of hand holding if uncomfortable with tools/procedures. Good luck.
Davey126 said:
Indicates bootloader is locked. See previous posts for path forward. Note cautions; don't expect a lot of hand holding if uncomfortable with tools/procedures. Good luck.
Click to expand...
Click to collapse
Hey Davey, one last question I hope. I can't boot into a ROM (I can do either Fastboot or TWRP) to get the unlock code doing the following from the instructions:
2. Turn on ADB-Debuging Mode in Developer Mod by tapping 7 times the build numbers in settings and connect to your computer + trust your device.
3. Excecute "get_code.bat" in the folder above, you will get a new file: unlock.code in the folder.
I can't copy a ROM to TWRP as it won't let me. I have searched and searched and I am stuck again. Please if you don't mind helping me as I remember how to do most everything (it is coming back to me more and more the more I read and what not) but I have never been stuck with the unlock code. Thanks so much.
alias4ever said:
Hey Davey, one last question I hope. I can't boot into a ROM (I can do either Fastboot or TWRP) to get the unlock code doing the following from the instructions:
2. Turn on ADB-Debuging Mode in Developer Mod by tapping 7 times the build numbers in settings and connect to your computer + trust your device.
3. Excecute "get_code.bat" in the folder above, you will get a new file: unlock.code in the folder.
I can't copy a ROM to TWRP as it won't let me. I have searched and searched and I am stuck again. Please if you don't mind helping me as I remember how to do most everything (it is coming back to me more and more the more I read and what not) but I have never been stuck with the unlock code. Thanks so much.
Click to expand...
Click to collapse
Don't worry about the unlock code; you can grab that later. The more immediate task is to install a vulnerable bootloader (aka 'aboot') and update twrp. Keep in mind this may not help if your newly acquired device is severely borked or has a hardware issue.
Davey126 said:
Don't worry about the unlock code; you can grab that later. The more immediate task is to install a vulnerable bootloader (aka 'aboot') and update twrp. Keep in mind this may not help if your newly acquired device is severely borked or has a hardware issue.
Click to expand...
Click to collapse
Well so I followed this thread: https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
Then I started here (just past the unlock code):
5. On the Computer go to Device-Manager and change driver in "Other Android" to "Fire Devices - Android Adb Composite Driver" . It should say "Ready" on the Kindle.
6. Now we need to enter Bulk-Mode like the instruction in this thread: Bulk Mode
Type:
Quote:
Code:
fastboot -i 0x1949 erase aboot
fastboot -i 0x1949 reboot
CMD shows that everything was successful but upon the reboot it just tried to boot into the OS instead of Bulk Mode that is installed that it can't boot into. I can still boot back into TWRP 3.1.1-1 as well as Fastboot.
ARGH! Any other suggestions Davey? I'm sorry to keep bugging you I just don't understand what is happening.
alias4ever said:
Well so I followed this thread: https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
Then I started here (just past the unlock code):
5. On the Computer go to Device-Manager and change driver in "Other Android" to "Fire Devices - Android Adb Composite Driver" . It should say "Ready" on the Kindle.
6. Now we need to enter Bulk-Mode like the instruction in this thread: Bulk Mode
Type:
Quote:
Code:
fastboot -i 0x1949 erase aboot
fastboot -i 0x1949 reboot
CMD shows that everything was successful but upon the reboot it just tried to boot into the OS instead of Bulk Mode that is installed that it can't boot into. I can still boot back into TWRP 3.1.1-1 as well as Fastboot.
ARGH! Any other suggestions Davey? I'm sorry to keep bugging you I just don't understand what is happening.
Click to expand...
Click to collapse
Sounds like the device/firmware is borked. You can try to issue the erase cmd wothout "-i 0x1949" (fastboot erase aboot) although that too will likely fail. At that point you're pretty much out of options short of a deep technical dive that is fraught with risk. Such travels are above my pay grade; you'd want to reach out to @draxie.
Davey126 said:
Sounds like the device/firmware is borked. You can try to issue the erase cmd wothout "-i 0x1949" (fastboot erase aboot) although that too will likely fail. At that point you're pretty much out of options short of a deep technical dive that is fraught with risk. Such travels are above my pay grade; you'd want to reach out to @draxie.
Click to expand...
Click to collapse
I did send a PM to @draxie so hopefully he can help me and we can get this Fire HDX up and running. Thanks for all your help though @Davey. I really appreciate it. I am going to keep my fingers crossed still though in hopes that draxie can help me. :good::fingers-crossed:
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