I have had the Umidigi One Max for almost 3 weeks now. I have rooted, installed TWRP, disabled-Force-Encryption and tried a variety of GSI Roms (see below). I have put back on stock for now, because I have been having a weird issue with the phone. Hopefully it will not start happening now that I have stock back on the phone.
I've had both LineageOS/ResurrectionRemix 9 GSI installed, that ended up with the same issue.
I had ResurrectionRemix on it yesterday. All working fine, all day long. Bluetooth, Android Auto, WiFi Etc. As I'm sitting in bed, all of a sudden the phone popped a warning "Powering down". It reboots, and then boots straight into twrp. I manually reboot it, and again, it boots straight into twrp. I tried doing a full wipe, and restore of my backup in twrp, reboot, and it does the same thing, boots into twrp.
Tried restoring stock via SPflash, when I start the download process in SPflash, power off the phone, and plug it in, instead of starting the transfer, the phone wakes up and boots straight into TWRP!
The only way, I was able to for stock back on was by doing this:
From my Ubuntu Linux machine, issued these commands:
adb reboot bootloader
(All Umidigi stock images)
https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
1. fastboot flash recovery recovery.img
2. fastboot flash boot boot.img
3. fastboot flash userdata userdata.img
4. fastboot flash system system.img
5. fastboot reboot
At this point the phone boots back into stock, De-Encrypt, Install TWRP, and all is working for now. However, what would cause the phone to power down abruptly, only boot into TWRP, and twrp backups to fail? I also tried to do a full wipe (type yes), and install a new ROM, and that finished, and booted straight into twrp.
Also, I had unlocked the bootloader via fastboot, so I'm not sure if that contributed to this issue. I have since re-locked the bootloader just in case.
Links:
https://twrp.me/umidigi/onemax.html
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
https://androidfilehost.com/?fid=1322778262904004415
Related
New AT&T HTC One 64M S-ON
Did the following (after trying the all-in-one toolkit and not being able to boot into recovery)
> fastboot flash boot boot.img
> fastboot reboot-bootloader
> fastboot flash recovery recovery.img
> fastboot erase cache
This got the recovery working. I installed supersu.zip from recovery. Verified root using root checker.
Tried to download and install a couple programs. Installing MyBackupPro and gave me an error relating to being unable to install.
Rebooted a couple of times and reset the phone to factory using the OS settings. At that point, wifi would not turn on. Says "turning on", and eventually says "error".
Any suggestions? I'm concerned that the boot.img was incorrect--for the international model? It was the one "made by Paul O'Brien"?
I am able to install and run both TWRP and CWM.
I've subsequently redone as follows:
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Everything works except wifi. Could it be just a hardware failure? I don't believe the failure was triggered immediately after any of my changes, but only after the "factory reset".
I have also tried disabling su from its settings menu.
Application installation error
This must be related? When I try to install My Backup Pro (I can download over 4G), I get the error "couldn't install on USB storage or SD card".
This is after a fresh factory "reset", including all user data.
You could install Android revolution from the Standard One Development section. Thats what im running. Works great. Remember to flash the kernel...http://forum.xda-developers.com/showthread.php?t=2183023
.
If you install Mikes Rom i linked above and the boot.img that goes with it you'll be fine. Right now you have a kernel from a different Firmware package so it isnt compatible.
This happened on one of my One's tonight as well. Turns out it was the boot.img that is most likely from the International One and a different version than what our stock AT&T Rom is (1.26 vs 1.27/8/9). I pulled the boot.img from my other One's nandroid and flashed it via fastboot and wifi was back.
I've posted it here.
Oh man, Thanks for the boot.img. Actually, I think that's the name of a song, right?
I want to try AR, but did want to keep it stock for a few days frist! Fortunately, at my bandwidth the download took several hours and by the time I looked your boot.img was here! Everything seems back to normal now.
EDIT: Apparently something on my device was interfering with something, after wiping with fastboot -w, I could install TWRP fine and then get LineageOS on the phone.
I've been trying to unlock the bootloader and root my phone ever since Huawei sent out the notification that they would be shutting down their unlock bootloader service. Everything went pretty smooth until I wanted to try to root my phone. I loaded a superSU ZIP onto the internal storage and loaded it in with TWRP, which then led me to booting about halfway and then sending me back to recovery. So I went ahead and factory reset, cleared cache and rebooted, where I got into a boot loop (stock OS was still loaded, but it wasn't loading correctly and rebooting). I went back into recovery and tried wiping my phone again, and that led me to this point. I am able to get into stock fastboot, or bootloop on the splash screen (no OS, I think). Stock fastboot is limited on this phone because it makes you open HiSuite to modify anything but it hasn't put it onto my computer like it normally does. I've tried flashing TWRP on my phone from fastboot but it doesn't seem to work as it still boots into stock fastboot.
I have TWRP, Android SDK, SuperSU and LineageOS for the 5X on my computer, but the issue is loading it onto the phone. Any help is appreciated, and don't be afraid to tell me that my phone is toast because nowadays it's not worth too much.
Thanks!
So I'm pretty new to the forums, and pretty new to the rooting scene in general, but I'd like to think I have a general idea what I'm doing (barely)
I'm trying to flash LineageOS on to my Pixel, and each time after flashing the ROM, I get stuck in a bootloop and can only access the bootloader, or I can access TWRP if I use "fastboot boot twrp.img"
Here's the tutorial I've followed to get root, I've followed it to a T:
-Flash stock image from google of whatever version you are going to be running (I went with ppr2 sailfish (as i have the pixel 1))
-Fastboot to twrp (I used version 3.2.3-1-sailfish)
-Flash TWRP.zip (NEXT STEPS ARE WHAT MADE THE DIFFERENCE)
-Do not just hit reboot after installing. Press the back button and go to the home screen of twrp again.
-Clcik the reboot there and click "Do Not Install" this is in reference to the TWRP application with which you don't want to install
-Now turn back off your device and go into twrp again
-Flash magisk 16.7 (NEXT STEPS ARE ALSO WHAT MADE THE DIFFERENCE)
-Do not hit reboot right after you intsall it or will be in a boot loop
-Go back to home screen, hit reboot then hit power off
-Wait a few seconds thens turn that ***** on.
Click to expand...
Click to collapse
And I've followed the directions directly from Lineage on how to flash the ROM. I've also tried flashing the verified boot signer afterwards, I've tried installing a different kernel that supposedly disables "dm-verity" (which seems like it might be the issue but I'm not sure)
I've tried changing the boot parameters from 'b' to 'a' with "fastboot set_active a"
I've tried numerous different steps and each time it's the same process. I get stuck in the bootloop with the bootloader, so I flash the stock image, then reinstall TWRP, Reinstall Magisk / Root, then try to install Lineage and get bootloops, rinse and repeat for the last 2 days. I'm completely at a loss. Any advice? It's much appreciated.
dylanfitz32 said:
So I'm pretty new to the forums, and pretty new to the rooting scene in general, but I'd like to think I have a general idea what I'm doing (barely)
I'm trying to flash LineageOS on to my Pixel, and each time after flashing the ROM, I get stuck in a bootloop and can only access the bootloader, or I can access TWRP if I use "fastboot boot twrp.img"
Here's the tutorial I've followed to get root, I've followed it to a T:
And I've followed the directions directly from Lineage on how to flash the ROM. I've also tried flashing the verified boot signer afterwards, I've tried installing a different kernel that supposedly disables "dm-verity" (which seems like it might be the issue but I'm not sure)
I've tried changing the boot parameters from 'b' to 'a' with "fastboot set_active a"
I've tried numerous different steps and each time it's the same process. I get stuck in the bootloop with the bootloader, so I flash the stock image, then reinstall TWRP, Reinstall Magisk / Root, then try to install Lineage and get bootloops, rinse and repeat for the last 2 days. I'm completely at a loss. Any advice? It's much appreciated.
Click to expand...
Click to collapse
i cant seem to flash any stock firmware on mine. keeps mentioning something about user data. i have tired ota and even factory images. did you get yours resolved? thanks
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/
EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.