Related
My Moto G survived the elements for a year now, with abuse, drops, water and a llot of flashing.
Yesterday, i decided to use Lollipop Brazil rom from here. It all went well but after some testing and just checking out new features i downgraded to 4.4.2 rom. Lollipop is imho not very fast compared to latest 4.4.x...
The device worked without problems, until i got the OTA update for 4.4.4. When it was installing in the stock recovery, the screen went dark. Since that moment no life at all! The LED works a few minutes when i charge it, but other than that. I have a nice black -not working- device.
Then I tried this & this without any luck.
I'm booted with driver verification disabled, installed "qhsusb_bulk" driver from Riffbox Jtag. It can see the device but can't flash a new bootloader.
Fastboot don't work, because I can't even power on the device....
I'm fed up, this is my main device and I didn't expect this. After all, I flashed CM12 5.0 builds in the past and reversed to 4.4.x without any hassle!!
Can I do something? I have the right torx screwdrivers.... something... *sigh* It can't be that just a few lines of code f*ck up this device....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You should have just installed one of the custom roms instead. As far as I can tell, there's no difference between those and the official rom other than a few extra features. The brazillian rom you installed came with the new bootloader and that makes it likely to hard brick your phone if you try to downgrade back to kitkat.
jman1234 said:
You should have just installed one of the custom roms instead. As far as I can tell, there's no difference between those and the official rom other than a few extra features. The brazillian rom you installed came with the new bootloader and that makes it likely to hard brick your phone if you try to downgrade back to kitkat.
Click to expand...
Click to collapse
I tought the official rom was the most stable one...
So what is plan B?
dwensch said:
I tought the official rom was the most stable one...
So what is plan B?
Click to expand...
Click to collapse
I believe there is a guide to "un" hard brick your phone somewhere around this forum. Try searching [guide] moto g hardbrick or something similar... But since you upgraded the bootloader this most likely will not work. Sorry for the bad news... Wait for new methods or jtag your phone. Or send it in to motorola... Try running the qboot.exe in windows xp sp3 compatibility mode.
skyguy126 said:
I believe there is a guide to "un" hard brick your phone somewhere around this forum. Try searching [guide] moto g hardbrick or something similar... But since you upgraded the bootloader this most likely will not work. Sorry for the bad news... Wait for new methods or jtag your phone. Or send it in to motorola... Try running the qboot.exe in windows xp sp3 compatibility mode.
Click to expand...
Click to collapse
XP SP3 mode didn't work... and I don't think Motorola will fix it for free, since i replaced the screen 2 times already...
Gonna need to save money for new phone now, damnit
Is there a way to extract 5.0 bootloader and force "install" to my device?
dwensch said:
XP SP3 mode didn't work... and I don't think Motorola will fix it for free, since i replaced the screen 2 times already...
Gonna need to save money for new phone now, damnit
Is there a way to extract 5.0 bootloader and force "install" to my device?
Click to expand...
Click to collapse
The bootloader should be in the zip file you got the rom from. It should be called motoboot.img
But you need to be able to blank flash your phone to flash a new bootloader if its hard bricked. Your best bet at this point in time would a jtag. Just be patient and wait a few weeks, theres bound to be a solution soon...
OKay, i will have patience. Still, very anoying.. But i understand it, because the new ART software changes everything... I hope somebody will take the time and make some solution...
dwensch said:
OKay, i will have patience. Still, very anoying.. But i understand it, because the new ART software changes everything... I hope somebody will take the time and make some solution...
Click to expand...
Click to collapse
No it is not because of ART. That doesn't have anything to do with your problem. When you flashed firmware to upgrade to Lollipop you must have also flashed the new bootloader. You might have used a command called "fastboot flash motoboot motoboot.img" When you do this, the updated bootloader will not boot to kernels below android 5.0. So when you tried reflashing 4.4.4 or lower on your device, you must have used a command like "fastboot flash boot boot.img" Since you flashed a kernel that the bootloader does not support your phone became "hard bricked" more or less.
I did the exact same procedures and having the same problem.Someone please help
sauravbiswas said:
I did the exact same procedures and having the same problem.Someone please help
Click to expand...
Click to collapse
The bootloader should be in the zip file you got the rom from. It should be called motoboot.img
But you need to be able to blank flash your phone to flash a new bootloader if its hard bricked. Your best bet at this point in time would a jtag. Just be patient and wait a few weeks, theres bound to be a solution soon...
I'll help you: PM me I'm Dutch also!
Boot into some custom recovery and wipe system.
Then install some custom ROM or stock 4.4.4
harshhemnani said:
Boot into some custom recovery and wipe system.
Then install some custom ROM or stock 4.4.4
Click to expand...
Click to collapse
My bootloader is'nt working so can't load a custom recovery
He can't do that if the phone does not even turn on...
I just hope to get a working solution fast....coz this is my daily driver and I m screwed
harshhemnani said:
Boot into some custom recovery and wipe system.
Then install some custom ROM or stock 4.4.4
Click to expand...
Click to collapse
I wish it was that simple! Did you even read the topic?
I hope somebody can fix mine and others problem. Because i spent allot of money on this phone *sigh*, there is nothing wrong with the hardware.
In the past year i replaced the LCD 2 times, 1 cover and 1 backhousing. So the hardware is functioning perfect now. It makes me sick that just a few lines of code destroy the bootloader software!!!
Why was this not stated in OP from Brazil Lollipop? Yeah, it says it can "brick the phone', but that warning is so generic..... I wish he was more specific?
Im gonna buy a new phone in the coming weeks, because IMHO, this phone is RIP. But if somebody is able to get it working again, i would be very grateful.
Well to be fair, you should have known that flashing an OTA meant for xt1033 on xt1032 would have caused problems.
dwensch said:
I wish it was that simple! Did you even read the topic?
I hope somebody can fix mine and others problem. Because i spent allot of money on this phone *sigh*, there is nothing wrong with the hardware.
In the past year i replaced the LCD 2 times, 1 cover and 1 backhousing. So the hardware is functioning perfect now. It makes me sick that just a few lines of code destroy the bootloader software!!!
Why was this not stated in OP from Brazil Lollipop? Yeah, it says it can "brick the phone', but that warning is so generic..... I wish he was more specific?
Im gonna buy a new phone in the coming weeks, because IMHO, this phone is RIP. But if somebody is able to get it working again, i would be very grateful.
Click to expand...
Click to collapse
jman1234 said:
Well to be fair, you should have known that flashing an OTA meant for xt1033 on xt1032 would have caused problems.
Click to expand...
Click to collapse
No there is no problem with the ota stuff. Its the fact he flashed new boot loader and tried to downgrade. That is the root cause of the problem. As I said be patient and wait a few weeks, there's bound to be a new solution. If you want I can send some partitions from my phone if you want. Lollipop is very new so solutions are scarce.
Exactly, wait a while until the right files are out and you'll be able to revive your phone.
The same problem here, we have to wait for Mbm-ci 5.0 for bootloader 41.18 right?
i installed lollipop to my xt1034 GPE and try to be root, the phone stuck on boot animation and i tried go back to 4.42 and works, but when i update from ota to 4.4.4 some go wrong and my phone death, also i cant enter to bootloader
I need to reset my phone (not just factory reset or hard reset, but also the OS, so i need the rom image). Also I am a newbie, so can you also explain step by step how i would go about reinstalling android for my honor 8? I have heard that there is this thing called the bootloader lock which locks you out of putting on a custom rom, but i have heard that it still should work when installing official rom. I have tried this (very scetchy) link: http://huawei-firmware.com/?load_page=search&q=&page=1 and then: http://huawei-firmware.com/rom/huawei-honor-8/frd-l19/4160 and then that download link just goes to a page where you need to wait a set amount and then finally here: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1276/g104/v61398/f1/full/update.zip , but that page right now atleast just displays "An error occurred.", because i think that the website is down for some reason according to this: https://forum.xda-developers.com/t/is-update-hicloud-com-down.4239623/#post-84561851 . Does someone have the rom? Thanks in advance for the help!
Everybody knows that after upgrading to C_07, we lost access to mtkclient, root, and many more, and Oneplus support sucks.
So, this guide will help you go back to Android 11 and back to root.
This rollback install will wipe all your data, so make a backup first. I did it on my own device and took the risk of bricking it, and I did it once because I'm not nuts to do it again. Only do it if you are comfortable. I'm not responsible for any damage to your device.
I was on C_10 (Android 12) and downloaded the rollback package for Android 13 from https://community.oneplus.com/thread/1267587167833030657 (I posted the links from the source below because Oneplus has the bad habit of removing the links). Download the appropriate file to your device. If you don't know, you have to download all three and try them.
Links:
ROM IN: https://oxygenos.oneplus.net/11011_oplus_ota_downgrade.zip
ROM EU: https://oxygenos.oneplus.net/21342_Beta1__downgrade_ota_CPH2409.zip
ROM GLO: https://oxygenos.oneplus.net/21342_Beta1__downgrade_ota_CPH2409_10100111.zip
Go to update, and if you do not see the local install, you need to go to the build number and click seven times to enable developer options.
After downloading, rename the file to oplus_ota_downgrade.zip. Go to update, select local update, and install this package. When the install finishes, the device will reboot and will be wiped. After that, you need to configure your device. At this time, the device will be on C_09.
Go to update, and a third option will be available, the option to join the beta or something like that. Click on that, and after requesting to join the beta test, go back and click again on update, and a new update to (Android 13) F.45 will show if I remember correctly. Once done, download the rollback package to Android 11, available on https://www.droidwin.com/downgrade-oneplus-nord-ce-2-from-android-12-to-android-11/.
ROM IN: https://oxygenos.oneplus.net/oplus_ota_downgrade_Rollback.zip
ROM EU: https://oxygenos.oneplus.net/oplus_ota_downgrade_Rollback_EEA.zip
ROM GLO: https://oxygenos.oneplus.net/oplus_ota_downgrade_Rollback_GLO.zip
Remember to rename it to oplus_ota_downgrade.zip. Go to update, select local install, and choose the zip file. After applying this update (which will take more time than before, it looks like it's broken at 94%, but just wait), the device will be wiped again. Done with the setup again (now you are on A_13 Android 11), power off the device, and press Vol- and Power, and you will have access to fastboot. Yes, now we have fastboot back! On a computer, plug in your device (supposedly, you had installed drivers before).
Execute:
fastboot devices
And, if it returns something like this: SOMERANDOMCARACTERS(Serial number of your device) fastboot
Execute:
fastboot flash preloader preloader_oplus6877.bin (this preloader is attached to this post).
And you're done! Now you can use mtkclient again. Just remember not to update your device until we find a way to keep the preloader vulnerable to the mtkclient exploit.
Thank you so much for posting this!
Hi @brunowm perfect guide... and thank you in advance for your patience and understanding as I am not an expert on these things and I only want to rollback to Android 11... few (perhaps silly) questions (I am in android 12 build number IV2201_11_C. 10) at the moment:
- do i need to be connected to wifi when doing these operations?
- What am i doing wrong that sometimes goes to "safe mode" and I can't get it out from there at all, only by trying to install the rollback (which fails, look next).
- I wish to understand better why when I try directly to install this: oplus_ota_downgrade_Rollback_EEA.zip (your second set of links) it starts installing but stops at 16%, then reboots and says that the update failed. Is it because of missing the beta installation that you pointed first?
- However, I tried with the beta file (21342_Beta1__downgrade_ota_CPH2409.zip) but the verification fails.... it says that package is not compatible with your system ... could this be because I am in Android 12 and this is the rollback from Android 13? Nonetheless you do mention this situation, so I am a bit confused :-(
- Also, it seems that one of those downgrade.zip files helps you to downgrade first from 12.1 to 12. This file is verified, recognized but similarily to the one that goes from 12-->11 it stops at 16%, reboots and then it shows message that it failed...
I'm really desperate so, any light at the end of the tunnel is highly appreciated!
ps.
- is there any possibility to rollback to earlier oxygen versions for example 1.2 or so?
burningcreation said:
Thank you so much for posting this!
Click to expand...
Click to collapse
Very quick question, do you think now is possible to downgrade this device from Android 12 ->11?
k.whatamidoing said:
Hi @brunowm perfect guide... and thank you in advance for your patience and understanding as I am not an expert on these things and I only want to rollback to Android 11... few (perhaps silly) questions (I am in android 12 build number IV2201_11_C. 10) at the moment:
- do i need to be connected to wifi when doing these operations?
- What am i doing wrong that sometimes goes to "safe mode" and I can't get it out from there at all, only by trying to install the rollback (which fails, look next).
- I wish to understand better why when I try directly to install this: oplus_ota_downgrade_Rollback_EEA.zip (your second set of links) it starts installing but stops at 16%, then reboots and says that the update failed. Is it because of missing the beta installation that you pointed first?
- However, I tried with the beta file (21342_Beta1__downgrade_ota_CPH2409.zip) but the verification fails.... it says that package is not compatible with your system ... could this be because I am in Android 12 and this is the rollback from Android 13? Nonetheless you do mention this situation, so I am a bit confused :-(
- Also, it seems that one of those downgrade.zip files helps you to downgrade first from 12.1 to 12. This file is verified, recognized but similarily to the one that goes from 12-->11 it stops at 16%, reboots and then it shows message that it failed...
I'm really desperate so, any light at the end of the tunnel is highly appreciated!
ps.
- is there any possibility to rollback to earlier oxygen versions for example 1.2 or so?
Click to expand...
Click to collapse
Hi, you have renamed the downloaded file 21342_beta1__downgrade_ota_cph2409.zip to oplus_ota_downgrade.zip ? It's better doing with internet (wifi or 5G) off. After this install you will be able to update to Android 13 and from this version (F_45) you can rollback to Android 11
Hey @brunowm, I followed your first step and was able to roll back to C_09. However, there are no available beta programs to update my phone to Android 13. Should I bite the bullet and proceed with step 2 or is there a known issue that the second step will not work with Android 12?
Hi, I just wanted to give an update @brunowm . I was able to downgrade the OS to C_09 from C_10, by following your first step. However, the option to join the beta program is not available to me, hence I cannot join the Android 13 beta yet.
I can't execute your second package since I am experiencing the same issue as @k.whatamidoing where the downgrade terminates at 16%.
Do you have any idea if there is any criteria I need to meet for joining the beta program? I have already enabled developers option.
Atest117 said:
Hi, I just wanted to give an update @brunowm . I was able to downgrade the OS to C_09 from C_10, by following your first step. However, the option to join the beta program is not available to me, hence I cannot join the Android 13 beta yet.
I can't execute your second package since I am experiencing the same issue as @k.whatamidoing where the downgrade terminates at 16%.
Do you have any idea if there is any criteria I need to meet for joining the beta program? I have already enabled developers option.
Click to expand...
Click to collapse
You have enabled developer mode ?
brunowm said:
You have enabled developer mode ?
Click to expand...
Click to collapse
Atest117 said:
Hi, I just wanted to give an update @brunowm . I was able to downgrade the OS to C_09 from C_10, by following your first step. However, the option to join the beta program is not available to me, hence I cannot join the Android 13 beta yet.
I can't execute your second package since I am experiencing the same issue as @k.whatamidoing where the downgrade terminates at 16%.
Do you have any idea if there is any criteria I need to meet for joining the beta program? I have already enabled developers option.
Click to expand...
Click to collapse
I don't know but maybe with only avaliable for indian rom version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
Code:
/*
* Your warranty is... still valid?
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are the one choosing to make these modifications.
*/
IMPORTANT
This ROM is only for the Amazon Fire HD 10 2019 (maverick) Do not try to flash it on any other device.
This ROM requires the temporary bootloader unlock found here. Read the instructions carefully and come back once you have a working temporary unlock.
This thread will be updated should another unlock method be available.
This ROM requires that you be on the 7.3.1.0 launch firmware. If you have temp unlocked your device, you should already be on this firmware.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
This is a custom build of LineageOS for the Amazon Fire HD 10 9th generation (maverick) which is 64-bit, allowing you to run 64-bit applications and benefit from better performance, unlike the stock OS which is 32-bit.
Working
Audio
Bluetooth
Camera
DRM L1 (playback not tested)
DT2W (double-tap-to-wake)
Media Playback (Hardware OMX)
Sensors
SDcard
USB (MTP, PTP, etc)
Wi-Fi
Not Working
SELinux is Permissive
Deep Sleep (?)
Hotspot
Notes
The stock gallery app has some issues playing media which is higher than 1920x1080, if you face this issue please try a third-party gallery app.
If you have flashed GApps, you should wait for the device to "settle" after completing setup wizard. During the first 10-ish minutes of use, the tablet could heavily lag and freeze.
Since this is a beta build, you should be prepared to face bugs and issues, along with possible stutters and lags.
You are free to use any recovery to flash this ROM, however, I recommend using the attached recovery (Lineage Recovery) to flash this ROM in order to avoid any potential issues.
How to Flash?
Spoiler: Flashing Instructions
It's important to note that you will have to boot your device with mtkclient every time you reboot!
First of all, boot the device into fastboot mode. Once you see something like => FASTBOOT mode... appear on your devices display, you can flash the Lineage Recovery image with the following fastboot command:
Code:
fastboot flash recovery lineage-18.1-XXXXXXXX-UNOFFICIAL-maverick-recovery.img
fastboot reboot recovery
This flashes the custom recovery to the devices recoverypartition, and then tells it to reboot into recovery mode.
To make sure the device boots into recovery upon the next reboot, hold the volume up button on the device after sending the preloader again with mtkclient.
DO NOT let the device boot back into FireOS at this point, as it will flash the old recovery back to the device, and you will need to start from the beginning again.
The unlocked LK indicates which mode the device will boot into, you should see something like lk boot mode = 2 on the devices display, meaning it is booting into recovery mode.
Once in Lineage Recovery, tap on "Apply Update", and then tap on "Apply from ADB". There are also options to apply updates from external storage if you wish.
Now, it's time to actually install the ROM. We are going to sideload the Lineage ZIP to our device using adb with the following command.
Code:
adb sideload lineage-18.1-XXXXXXXX-UNOFFICIAL-maverick.zip
At this point, all you need to do now is wait for the flashing process to complete.
Once finished, you will be brought back to the apply update menu. Simply press the back button to go back to the main menu.
Now, tap on factory reset and tap on the option Format data/factory reset. This is going to erase all of the old FireOS userdata from the device.
If you do not wish to install GApps, skip to the finishing up process below the GApps flashing instructions.
Optional: Flashing GApps
To install Google Services to your new ROM, you will want to start by downloading the recommended GApps package (see Downloads section).
Once downloaded, you can follow a similar process that you did for installing the ROM ZIP.
Tap on "Apply Update" again, and "Apply from ADB".
Once you have done that, you can sideload the GApps package with the following command:
Code:
adb sideload MindTheGapps-11.0.0-arm64-XXXXXXXX_XXXXXX.zip
If you wish to install other addons (e.g. Magisk), repeat the same steps, substituting the GApps package file name with the Magisk zip file name.
Finishing Up
Once you have done everything you need to do in Lineage Recovery, it's time to boot into the new ROM.
It's important to note that the reboot system now option does not work correctly, so follow these steps to workaround it.
Tap on Advanced, and then tap on Reboot to bootloader.
Once you see => FASTBOOT mode... on the devices display once again, type the following fastboot command to reboot.
Code:
fastboot reboot
After a short while, you should see the LineageOS boot animation on your device. First boot usually takes 5-10 minutes, especially if you have installed Google Services.
Wait for the device to boot and you should be presented with the setup wizard. Enjoy!
Downloads
ROM
Recommended GApps
Source Code
Device
Kernel
Vendor
Screenshots attached below.
Reserved #3
Amazing job.
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
The device tree is currently private for whatever reason. I will let bengris know through Telegram.
JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
Hey, currently the new device tree is not open source yet, I will make it open source once I fix the remaining issues (mainly getting SELinux Enforcing). Kernel tree is open due to the GPL license.
Hi there, I'm having issue with this ROM as it is bootlooping after install with TWRP or provided LOS Recovery. For what it's worth, I have a maverick that is permanently bootloader unlocked, so as far as I know I do not have to use mtkclient. I'm not sure if this is a hard requirement. Flashing via TWRP or provided LOS recovery does not work for me. Am I missing something?
I will pay $1,000 or more to anyone who can open bootloader to the new systems amazon
jasonjohn95 said:
Hi there, I'm having issue with this ROM as it is bootlooping after install with TWRP or provided LOS Recovery. For what it's worth, I have a maverick that is permanently bootloader unlocked, so as far as I know I do not have to use mtkclient. I'm not sure if this is a hard requirement. Flashing via TWRP or provided LOS recovery does not work for me. Am I missing something?
Click to expand...
Click to collapse
Hello, interesting to say you have "a maverick that is permanently bootloader unlocked", is it an engineering unit? Could you provide more details such as the firmware version you are on? Also, which kind of boot loop, does it at least get past the Amazon logo or just reboot? Or do you see LineageOS boot animation which never ends?
JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
FYI, I have open sourced the device tree, so feel free to build it yourself! You SHOULD be able to compile a booting build this time, just make sure to sync the device tree, kernel tree and vendor tree.
Hello, how are you? I have a question regarding the installation of the ROM. If I have the OS in the Fire OS 7.3.2.7 version, can I still install the ROM without any problem? Greetings from Chile, sorry for use google translate
ＤＥＭＯＮ said:
Hello, how are you? I have a question regarding the installation of the ROM. If I have the OS in the Fire OS 7.3.2.7 version, can I still install the ROM without any problem? Greetings from Chile, sorry for use google translate
Click to expand...
Click to collapse
no, you have to be on 7.3.1.0. Only the first 3-4 months of release of the device was rootable and available to any exploits. Before jan 2020.... If your was bought before that, you might be able to downgrade...
Michajin said:
no, you have to be on 7.3.1.0. Only the first 3-4 months of release of the device was rootable and available to any exploits. Before jan 2020.... If your was bought before that, you might be able to downgrade...
Click to expand...
Click to collapse
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
ＤＥＭＯＮ said:
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
Click to expand...
Click to collapse
Depends on when you bought your tablet.... When released it had a exploit. The bootrom was available to do some things..... If the device was released from amazon after about jan 2020, you are probably out of luck. The biggest problem here is even if you have the root access, you have to plug it in to a PC and run the script to get it to boot every time. It is still partially locked down.... Temp unlock (and temp root, which you have to run after boot every time) means you can get access but have to run the script every time....
ＤＥＭＯＮ said:
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
Click to expand...
Click to collapse
that being said, i hope you have updates disabled, because there might be another root option coming.
bengris32 said:
Hello, interesting to say you have "a maverick that is permanently bootloader unlocked", is it an engineering unit? Could you provide more details such as the firmware version you are on? Also, which kind of boot loop, does it at least get past the Amazon logo or just reboot? Or do you see LineageOS boot animation which never ends?
Click to expand...
Click to collapse
I'm not sure exactly what you're looking for (or how to find it on the current ArrowOS 13 build I'm running), so I'm attaching my entire getprop dump. Sorry!
The Maverick I have is a retail Maverick, but has been bootloader unlocked by "official" means for development as I am an Amazon employee/engineer on some of their Android products, so I guess I'm cheating on that front
The device will get to the Amazon logo, and then reboot after some time back again to the Amazon logo. I am able to boot into recovery with the vol+ key.
Another thing that might be an issue, I failed to check if I was originally on 7.3.1.0 before flashing, which could be the cause of the issues...oops
Michajin said:
Depends on when you bought your tablet.... When released it had a exploit. The bootrom was available to do some things..... If the device was released from amazon after about jan 2020, you are probably out of luck. The biggest problem here is even if you have the root access, you have to plug it in to a PC and run the script to get it to boot every time. It is still partially locked down.... Temp unlock (and temp root, which you have to run after boot every time) means you can get access but have to run the script every time....
Click to expand...
Click to collapse
Thank you very much for your answers, I don't know when I bought the Tablet, I forgot, but I imagine that it is possible to downgrade to Fire OS 7.3.1.0 in some way which I don't know, apart from I don't understand the tutorials that I found on XDA, I really have 2 days and my head hurts a lot because I do not understand the explanations of the users, if there was even the slightest possibility that you could contact me and tell me step by step what I should do and I will show you with screenshots how I progress and do everything to have a guide, I promise to pay you if I succeed in installing this ROM by PayPal
jasonjohn95 said:
I'm not sure exactly what you're looking for (or how to find it on the current ArrowOS 13 build I'm running), so I'm attaching my entire getprop dump. Sorry!
The Maverick I have is a retail Maverick, but has been bootloader unlocked by "official" means for development as I am an Amazon employee/engineer on some of their Android products, so I guess I'm cheating on that front
The device will get to the Amazon logo, and then reboot after some time back again to the Amazon logo. I am able to boot into recovery with the vol+ key.
Another thing that might be an issue, I failed to check if I was originally on 7.3.1.0 before flashing, which could be the cause of the issues...oops
Click to expand...
Click to collapse
Let's try to dump pstore from the device when it's trying to boot then.
Wait for the device to reboot after being on the amazon logo, immediately on the next boot up, go into recovery mode. Then, enable ADB.
You can dump pstore with the following adb command (adbd should run as root in recovery):
adb pull /sys/fs/pstore
Hopefully there should be some logs in there which you can attach here, if not, keep retrying until you get something in there. If you are 100% nothing is being dumped to pstore, just let me know.
As a side note, I am using the kernel source and blobs from the 7.3.2.7 firmware, so I'm not sure why it's not seeming to boot on later firmware.
bengris32 said:
FYI, I have open sourced the device tree, so feel free to build it yourself! You SHOULD be able to compile a booting build this time, just make sure to sync the device tree, kernel tree and vendor tree.
Click to expand...
Click to collapse
It works!
Completed a Lineage build using the info on "amazon-mt8183-devs" repo - now installed & working fine.
Many Thanks
Hi everybody
I am really fed up with searching to find a method to root a51 android 13, so please anyone can help me to sort it out would be appreciated. (Tried almost everything no way every time failed in recovery, and not accepted unofficial TWRP)
Thanks in advanced
hamidmrako said:
Hi everybody
I am really fed up with searching to find a method to root a51 android 13, so please anyone can help me to sort it out would be appreciated. (Tried almost everything no way every time failed in recovery, and not accepted unofficial TWRP)
Thanks in advanced
Click to expand...
Click to collapse
Have a look at Magisk's official Installation Instructions. Let me know if you need any help.
ethical_haquer said:
Have a look at Magisk's official Installation Instructions. Let me know if you need any help.
Click to expand...
Click to collapse
Hi Thanks for your reply. I've done almost every method .After providing pached flash through odin failed. It happened even to flash recovery .I also try to downgrade (success to Android 12 but cannot downgrade it to android 11).any suggestions will appreciate.
Thanks
hamidmrako said:
Hi Thanks for your reply. I've done almost every method .After providing pached flash through odin failed. It happened even to flash recovery .I also try to downgrade (success to Android 12 but cannot downgrade it to android 11).any suggestions will appreciate.
Thanks
Click to expand...
Click to collapse
How did the flash fail? What error messages were you getting? I'll try my best to help you. Also, what are you rooting for? I am rooted, so I know the benefits, but why not just flash a custom ROM and root it?
ethical_haquer said:
How did the flash fail? What error messages were you getting? I'll try my best to help you. Also, what are you rooting for? I am rooted, so I know the benefits, but why not just flash a custom ROM and root it?
Click to expand...
Click to collapse
Hi
Thanks again.to be honest I am also take the benefits of apps which only work on rooted and also using to spoof location for games an sp on .I am using rooted phones fir years but I am mot a developer. About the error I didn't realise if it cime with an error the thing is as I heard from someone else after upgrading to android 13 it is prevented to change boot.img , not 100% sure but it looks like correct as I am unable to flash rom,recovery and so on always fail.there was a website showing how to root A51 android 11 DUBI using vbmeta.img but as I said cannot downgrade to official android 11 as its prevented when it is on newer boot.img.
For flashing TWRP error always says can't use unofficial twrp,even pached not working .this is the whole story I will appreciate if anyone can find a solution.
Thanks again
hamidmrako said:
Hi
Thanks again.to be honest I am also take the benefits of apps which only work on rooted and also using to spoof location for games an sp on .I am using rooted phones fir years but I am mot a developer. About the error I didn't realise if it cime with an error the thing is as I heard from someone else after upgrading to android 13 it is prevented to change boot.img , not 100% sure but it looks like correct as I am unable to flash rom,recovery and so on always fail.there was a website showing how to root A51 android 11 DUBI using vbmeta.img but as I said cannot downgrade to official android 11 as its prevented when it is on newer boot.img.
For flashing TWRP error always says can't use unofficial twrp,even pached not working .this is the whole story I will appreciate if anyone can find a solution.
Thanks again
Click to expand...
Click to collapse
First of all, is your boot-loader currently unlocked?
hamidmrako said:
Hi
Thanks again.to be honest I am also take the benefits of apps which only work on rooted and also using to spoof location for games an sp on .I am using rooted phones fir years but I am mot a developer. About the error I didn't realise if it cime with an error the thing is as I heard from someone else after upgrading to android 13 it is prevented to change boot.img , not 100% sure but it looks like correct as I am unable to flash rom,recovery and so on always fail.there was a website showing how to root A51 android 11 DUBI using vbmeta.img but as I said cannot downgrade to official android 11 as its prevented when it is on newer boot.img.
For flashing TWRP error always says can't use unofficial twrp,even pached not working .this is the whole story I will appreciate if anyone can find a solution.
Thanks again
Click to expand...
Click to collapse
Also, you don't have to flash TWRP, you can keep the stock recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also can not reach stock recovery mode
Update I can reach recovery mode now
hamidmrako said:
Update I can reach recovery mode now
Click to expand...
Click to collapse
Alright, I have some time to help you now.
First of all, is your boot-loader unlocked?
Hi
Sorry for late reply .you were right .the bootloader wasn't properly unlocked and made me confused. I've got everything sorted now.just want to ask if TWRP available for A51 android 13 ?
Thanks for your help
hamidmrako said:
Hi
Sorry for late reply .you were right .the bootloader wasn't properly unlocked and made me confused. I've got everything sorted now.just want to ask if TWRP available for A51 android 13 ?
Thanks for your help
Click to expand...
Click to collapse
Alright, all you have to do is follow the official instructions. Let's do it!
Before you start:
This tutorial assumes you understand how to use adb and fastboot
If you plan to also install custom kernels, install it after Magisk
Your device’s bootloader has to be unlocked
Next, do this:
Download and install the latest Magisk app. In the home screen, you should see:
hamidmrako said:
Hi
Sorry for late reply .you were right .the bootloader wasn't properly unlocked and made me confused. I've got everything sorted now.just want to ask if TWRP available for A51 android 13 ?
Thanks for your help
Click to expand...
Click to collapse
Don't worry about TWRP, if you're trying to root your phone you do not need it.
@ethical_haquer i have a question, i get a error in download mode saying "Error verifying vbmeta: HASH_MISMATCH (3) VERIFICATION_DISABLED bit is set"
SaiMonicL said:
@ethical_haquer i have a question, i get a error in download mode saying "Error verifying vbmeta: HASH_MISMATCH (3) VERIFICATION_DISABLED bit is set"
Click to expand...
Click to collapse
This happened when?
ethical_haquer said:
This happened when?
Click to expand...
Click to collapse
litteraly today when i tried installing the magisk custom AP, i dont know how to make it work.
hello?
SaiMonicL said:
hello?
Click to expand...
Click to collapse
Sorry for the late reply! When I researched the error it sounds like the only way to fix the problem is to re-flash the stock ROM and then retry rooting it. At least it's not bricked! To re-flash it I recommend following this tutorial. It has worked for me in the past when I needed to re-flash my device. Let me know if you have any questions!
ethical_haquer said:
Sorry for the late reply! When I researched the error it sounds like the only way to fix the problem is to re-flash the stock ROM and then retry rooting it. At least it's not bricked! To re-flash it I recommend following this tutorial. It has worked for me in the past when I needed to re-flash my device. Let me know if you have any questions!
Click to expand...
Click to collapse
okay thank you, i already reflashed the original firmware and i am now trying to copy the new magisk AP to my pc, hope it works this time, otherwise i will need some serious help lol