Hi all,
I've long since stopped messing with custom ROMs as software has, largely, been quite good from the get-go on newer devices.
I tried playing around with my Honor 9 a few days back and I've managed to royally screw it up it seems - help is required
Here's where I am right now:
When I boot the phone I get a "Google" splash screen followed by the warning that my device is unlocked.
It then loops around again, shows the same splash screen and warning, but dumps me into eRecovery
I've tried flashing numerous TWRP images via bootlader/fastboot, but cannot ENTER any of them
I've tried flashing a number of Custom ROMs using the bootloader/fastboot, but again, I end up in the same position, dumped into eRecovery.
What am I missing here? I've tried stock kernels and custom ones, stock firmware and custom firmware, as well as TWRP. All to no avail currently.
I've long since left my fiddling days behind and as such I'm struggling here. The only good news is I can get into fastboot at will (bootloader unlocked and FRP unlock)
Any ideas? Please be kind
So, after writing this and 3 hours of fiddling myself, I finally managed to get into a custom recovery and used the HuUpdater to get back to a stock image (I think, just setting it up now).
Please delete
Related
So I got my X5 today and immediately set about rooting it.
To start I tried to flash TWRP and that put it into a boot loop! Just the initial splash screen.
I managed to get it to boot by flashing via fastboot to what I thought is the correct firmware from the Doogee support site, however the screen is just horizontal bars.
Looking into why it seems clear the lk.bin which contains display drivers must be wrong, but for the life of me I can't find the right one! Every one I flash I get the same result.
The phone came with Marshmellow pre-loaded and build date 20170904, however I can't find this version available to download ANYWHERE! So I'm thinking either I have a new revision of X5 that no one else has properly played with and Doogee have not even put the firmware/revision info up yet, or for some odd reason I got a phone that the seller had flashed themselves with a custom ROM (it came from Amazon and the seller is 'Doogee Official Store' so I don't think this can be the case).
Anyway, any ideas are most welcome. I'm really thinking/hoping I just need the right lk.bin and can flash it alone!
Thanks!
Why don't you contact with doogee to identify which device you have and to direct you to a suitable rom file download?
I have.
Though I’ve since realised the Bootloader is set to locked and USB Debugging is disabled, so even if I get the right load I’m not sure how I will applie it!
I can get to fastboot blind, and to stock recovery blind, but then I can’t see what I’m doing to get to a point I can allow ADB or any other kind of flash.
If I had a screenshot of the stock recovery screen and the steps you can go through from there to allow flashing that might help.
I’ve tried going into the full OS and getting to settings/developer/OEM unlock blind but no joy! Again, screenshots of this process might allow me to press the right bits of the screen (along with a truck load of luck!).
I have a Redmi Note 4x (Global) SnapDragon, 3GB/32GB, stable ROM . I have never rooted it, or modified anything from the system, just left it untocuched as it came from the factory. I have updated it accordingly whenever the system requested me to do so (last update about a month or two ago). I have bought and been using this phone for about 5 months. Right now is has MIUI 10 OS.
In these 5 months about 4 times it has got stuck at boot with the MI logo and nothing else. After hours, the only way to come back to the system is letting it run out of batteries and start to the system normally. I became less and less successful to reach the system, but when I did I was able to start the unlock process permission. I guess I was lucky as before it would allow to go the system after several tries, but only allowed me once again, and then it get stuck on boot loop with the MI logo permanently.
After 66 hours I successfully finished the unlock process, I restarted to Fastboot mode and was able (with the latest MiFlash) to install the corresponding Official ROM and reported successful. However after restart it keeps on getting stuck at boot logo.
I don't really get how successfully flashing the Official ROM does not bring the cell as its original state.
Any suggestions?
PS: If I can avoid the TWRP route, I'd rather do as it would cancdel my warranty. Hopefully there is another way out, if there is not a way out the TWRP route, then I'd appreciate if someone could point me to a TWRP installation guide compatible with my current device (RN4X Snapdragon stuck on boot, with no access to the OS, but with Bootloader unlocked)
Hello,
The last week or so I have been trying to flash TWRP onto my Samsung Galaxy A40 (SM-A405FN) to install LineageOS. However, as I started following different guides and methods I have run into several problems that I can't get around and I was wondering if anyone here has had a similar experience or knows the solution.
The first problem I ran into was that when trying to flash onto the phone, neither ADB nor Fastboot detected the phone in download mode (when it was turned on normally they did). I tried various things to solve it: uninstalling and reinstalling different drivers, trying to find the device in device manager (it wasn't there) and nothing worked. I got around it, however, using Odin to flash. Odin did recognize the phone. I had already unlocked the bootloader and made sure VaultKeeper didn't lock it again. I believe it is fully unlocked now, I have even waited the week period to remove the RMM thing (I'm not entirely sure what it is and if I've done it properly, it's been a while since I've messed with android, but it used to display "KG state: checking" and now it's gone).
So, with Odin recognizing the phone I tried to flash the official TWRP recovery for it, following the instructions on the website. However, after flashing it, the phone bricks and boots into download mode all the time, with the error "Error validating footer (6)" on the top left corner. I have googled far and wide and the only solution I find is to reflash the stock ROM. Of course, this works, but I would like to be able to install LineageOS on the phone.
Thank you for in advance and let me know if you need more information or pictures of some sort.
Bump
Hello,
You can try the tuto on the following link:
It's for samsung A20, but you can apply the same practice for the samsung A40.
The first part of this tuto is woking for me (TWRP) but not the last one: "Rmm bypass"
Best regard's, Gregory
Hi all
First off I'm definitely a noob and it might be in the wrong place?
I'll start off by saying thanks for any support I my get.
Tryed to make a / i.e put in a TWR recovery
and got sent into a crash dump.
Now when I turn on the phone it stays in fast food Mode.
I've tried a multitude of tutorials to no avail.
The phone does have an unlocked bootloader done correctly, pretty sure. It's not rooted that was what I was trying to do. I'm running Ubuntu the latest version on a laptop and I'm seeking help to unbrick my poor new phone. I can perform tasks like getting log files and have even tried reflashing boot.images etc with success but not booting back into recovery where I could flash its oos, just end up in fast boot mode again.
I used bugjaeger at first with an OTG cable and another phone to flash custom recovery.
If somebody has a tutorial assuming that the partitions may be harshed on or needing something I'm unaware of or whatnot I'd be beyond appreciative...
Thank you for your time!
Hi,
I tried to follow the instructions to convert my device from Chinese rom to global.
I was struggling a bit, but eventually managed to get all the steps done without an error.
However, my device does not get booted to the OS at all.
I noticed everyone mention a boot loop but mine just switched off (so it seems).
So my first question is did I brick my device?
I can still boot recovery / bootloader., my boorloader is also unlocked.
What can i do to fix it?
Is it possible to go back to the Chinese rom?
Do I need to contact the mystery guy from instegram?
Thanks,
Bar1
If you still have Fastboot/recovery you are fine