Man, I think I have faulty hardware on my Umidigi One Max already. I was booted up in LineageOS, pulled up newpipe (third party youtube app) to watch videos, and out of nowhere my phone powered down, and booted straight into recovery (TWRP right now). I formatted, and restored the Umidigi stock ROM, and rebooted, and same thing, it boots straight into TWRP. No matter what I try, it boots directly into recovery. Anyone else had a similar issue?
Fixed .... See details
kgoerbig said:
Man, I think I have faulty hardware on my Umidigi One Max already. I was booted up in LineageOS, pulled up newpipe (third party youtube app) to watch videos, and out of nowhere my phone powered down, and booted straight into recovery (TWRP right now). I formatted, and restored the Umidigi stock ROM, and rebooted, and same thing, it boots straight into TWRP. No matter what I try, it boots directly into recovery. Anyone else had a similar issue?
Click to expand...
Click to collapse
Just for an update. I was able to get everything up and running. Some partition, I assume became very corrupt, or something along those lines. If someone runs into the situation where your Umidigi One Max only boots into recovery this might save you some time:
1. Firstly, from twrp I powered down.
2. I downloaded up the factory ROM, and extracted it.
https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
3. Loaded the scatter file in SPflash, but when I clicked download, and plugged in the OneMax the phone automatically powered up into TWRP recovery, and SPflash would time out (Ugh!). So I had to go OLD school. I run Ubuntu linux, but this can be done in windows too. Running adb commands to FORCE the images onto the phone. Run these commands:
Google how to install adb in windows...
A. adb reboot bootloader (this forces the phone in fastboot)
B. From dos / linux command-line change into the directory that contains Umidigi One Max factory images you downloaded/extracted.
C. Run these commands to force the important images onto the phone.
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
The system image contains the bulk of the OS (2GB).
If it gives you errors when you try to fastboot flash an image, you may need to unlock the bootloader to have access to write the images:
fastboot oem unlock
fastboot flashing unlock
fastboot flashing unlock_critical
To re-lock the bootloader at the later time, you issue these commands:
fastboot oem lock
fastboot flashing lock
fastboot oem relock
My phone booted happily, and retained IMEI keys too. Whew! Hope others find this helpful.
Happy you got your phone back
I had the recovery/bootloop issue also while attempting to put a gsi of Havoc 2.7 pie on here. Ended up with A Havoc 2.0 pie which is running great!!
I really enjoy this device, wondering if you have found a good camera app that eliminates some if not all of the pixel noise when using the back main camera?? Been looking for a while now and it's my only real issue with this phone.
prophetofthepath said:
I had the recovery/bootloop issue also while attempting to put a gsi of Havoc 2.7 pie on here. Ended up with A Havoc 2.0 pie which is running great!!
I really enjoy this device, wondering if you have found a good camera app that eliminates some if not all of the pixel noise when using the back main camera?? Been looking for a while now and it's my only real issue with this phone.
Click to expand...
Click to collapse
Hi prophetofthepath,
I have been using havoc 2.8 as my main driver, and have primarily used opencamera. Haven't had a ton of luck with the camera quality, as it is hit or miss on the quality.
I also use Magisk to fix other issues, including NFS. There is a Magisk module that activates nfc in custom ROMs.
For voice recognition feature to work with sms, I had to download a keyboard other than aosp's default keyboard (like Google's).
I'm not sure about your one max, but on my one max wifi speeds are awful! 30Mbps max download, even on 200Mbps networks! I've tried both stock and havok, and neither make a difference. Call reception is ok. Umidigi shouldn't skim costs where reception is concerned. I'm fairly certain, it's cheap internal antennas to blame. It gets me by though.
If you've picked up any tricks, be sure to comment.
Related
So, I've stupidly let my son try and flash a custom rom on his generic chinese tablet (Cambridge Sciences StarPAD 9 SE) and he found a few very similar spec tablet roms on the internet which said they require TWRP to be installed before flashing. So he's installed that, rebooted into recovery but the TWRP doesn't fit the screen in terms of resolution size. Now, that's not the main problem. The main problem is that the touch screen doesn't work at all within TWRP so I can't select any of the options. Whenever I power off the device and power it back up, it reboots to TWRP and doesn't boot to the main ROM. He said that it did originally reboot to the ROM whenever he first installed the TWRP because he said that it was the only way of getting to the recovery. So I thought that I could just use ADB and just force a reboot from there but off course, there is no ADB device driver to be found on the internet.. well not that I can find anyway.
I'll attach a photo for you guys and hopefully someone can help me with this as I've spent the best part of 2 days trying to figure out a fix but am now stuck.
I'm now able to access the device by adb however I don't know what to do from there.
Any help?
Does anyone have any firmware for this device? I can't find anything on the internet at all. If I could get a firmware img then the device will be fixed.
The build number from the firmware is: fiber_evb-eng 4.1.1 master 20130530
the command is "adb reboot" AFAIK
Did he take a nandroid backup before flashing? It looks like a version of twrp that is not compatible with the tablet was installed. Not every device supports touch screen recovery mode. Can you use the volume rocker to navigate?
I can almost guarantee you won't find the firmware for a Chinese tablet. I've just been trying to help someone in a similar situation but the best we could manage was a ROM that had lots of glitches.
Edit how did he flash TWRP if it was incorrectly flashed ie: fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img then that may produce a device that would boot straight into TWRP. I've heard of that happening on a nexus 7
Sent from my C5303 using xda app-developers app
Brush before you must see:
1. The brush machine package is based on the official closed beta leaked JUI 7.1 brush machine package production
2. Because it is inside the package must have some bugs, focusing on the main experience!
3. Please carefully read this post in the brush machine!
4. As long as you brush the rom any problems are not responsible, brush machine risk, play machine need to be cautious, although I have tested, but may be due to some unknown reasons will lead to brush machine failure!
First of all the rom for the crowd: Le pro3 (x720 x728) Cool s1
mod edit : links removed
installation:
Flash TWRP
Download the ROM
Clear Data and Cache
Flash ROM
Flash Gapps Beans
Reboot
ATTENTION: Only care for who install, I have not tested the downgrade to EUI again, I do not know if it's easy
gersonrsj said:
Brush before you must see:
1. The brush machine package is based on the official closed beta leaked JUI 7.1 brush machine package production
2. Because it is inside the package must have some bugs, focusing on the main experience!
3. Please carefully read this post in the brush machine!
4. As long as you brush the rom any problems are not responsible, brush machine risk, play machine need to be cautious, although I have tested, but may be due to some unknown reasons will lead to brush machine failure!
First of all the rom for the crowd: Le pro3 (x720 x728) Cool s1
LINK DOWNLOAD: https://drive.google.com/drive/folders/0BzifdSZRqGIsM3BWWkFGRUVrc3M
installation:
Download the ROM
Clear Data and Cache
Flash ROM
Flash Gapps Beans
Flash Supersu
Reboot
CREDITS BY: NAVIGATOR
Click to expand...
Click to collapse
Thank you
Basically eui6:laugh:
Are you Chinese?
linchanggui said:
Are you Chinese?
Click to expand...
Click to collapse
Chinese and English
哈哈哈哈。。。
Google Drive....
You need permission
Your request for access has been sent.
You will receive an email if and when your request is approved.
Wow looks very good. Nice UI
Looks like it's the first release (official-like) of Nougat update for our device Cool Changer S1 is basically LP3 brother. They have mostly the same hardware.
This google drive link requires permissions so I will upload it on MEGA for anyone who wants to try in few minutes and edit this post.
Edit: Mega
Nice!!!!
Thes1ev said:
Looks like it's the first release (official-like) of Nougat update for our device Cool Changer S1 is basically LP3 brother. They have mostly the same hardware.
This google drive link requires permissions so I will upload it on MEGA for anyone who wants to try in few minutes and edit this post.
Edit: Mega
Click to expand...
Click to collapse
Thanks very good
I'm impressed with the more fluid rom being alpha beta, some bugs but nothing that disrupts the use, tomorrow I'm going to test the battery apparently looks very good, Rom has multi-window
gersonrsj said:
I'm impressed with the more fluid rom being alpha beta, some bugs but nothing that disrupts the use, tomorrow I'm going to test the battery apparently looks very good
Click to expand...
Click to collapse
What bugs have you found?
Ascertion said:
What bugs have you found?
Click to expand...
Click to collapse
Is not getting root, and gps is giving some errors I have to test better
Guys what twrp did you use to flash this rom ? For me it replaced fastboot to some strange one. After flashing it bootlooped on the screen with CoolPod or w/e (first what you see after powering the phone).
Moreover when phone is in fast bootmode it make some squeaking noise...
I managed to flash it just now, lets see whats up.
@Thes1ev being carefull, I first extracted the recovery contained in the rom zip file, and flashed it to see it was a modified twrp, and able to decrpyt my storage (logic being, if it was faulty, I'd just fastboot flash darkos twrp back, and end the story there). Seeing as it was working, I then flashed the rom, it took a while longer than I expected, but it finished. Upon boot I did run into a problem, my keyboard wouldnt pop up to enter the decryption password lol, luckily I had my OTG adapter handy, and managed to input my pw with my usb keyboard
---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------
And, I see now there's no keyboard installed other than google voice typing, that explains it
trizex said:
I managed to flash it just now, lets see whats up.
@Thes1ev being carefull, I first extracted the recovery contained in the rom zip file, and flashed it to see it was a modified twrp, and able to decrpyt my storage (logic being, if it was faulty, I'd just fastboot flash darkos twrp back, and end the story there). Seeing as it was working, I then flashed the rom, it took a while longer than I expected, but it finished. Upon boot I did run into a problem, my keyboard wouldnt pop up to enter the decryption password lol, luckily I had my OTG adapter handy, and managed to input my pw with my usb keyboard
---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------
And, I see now there's no keyboard installed other than google voice typing, that explains it
Click to expand...
Click to collapse
I was on darkos twrp, flashed this room and it boot-looped at the beginning. Now I can't even turn off the phone as it automatically turns on and off and on etc... every few seconds on this fkn "Coolpad" screen. I can enter the recovery however can't transfer any rom into the card. Adb push stops after some time randomly before it manages to transfer any ROM into the sdcard...
Just realized it stopped rebooting when I plugged it into the charger.
Got root through SuperSU 2.79
Thes1ev said:
I was on darkos twrp, flashed this room and it boot-looped at the beginning. Now I can't even turn off the phone as it automatically turns on and off and on etc... every few seconds on this fkn "Coolpad" screen. I can enter the recovery however can't transfer any rom into the card. Adb push stops after some time randomly before it manages to transfer any ROM into the sdcard...
Click to expand...
Click to collapse
Fastboot and flash darkos twrp? Copy just the recovery.img through twrp, flash it, and then copy what you want?
trizex said:
Got root through SuperSU 2.79
Fastboot and flash darkos twrp? Copy just the recovery.img through twrp, flash it, and then copy what you want?
Click to expand...
Click to collapse
Fastboot is not working, power + vol down goes to black screen / turning off the phone.. I managed to flash another recovery 3.1.0.0 but still I need to push some rom to see if I can flash it.
And the thing is while pushing big files(it takes few minutes) it randomly stops responding in the middle of a transfer. So I have to start again. Tried maybe 10~ times and still stopping transfer randomly.
Commands in console like fastboot oem device info gives < waiting for any device >
adb reboot bootloader
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
Thes1ev said:
Fastboot is not working, power + vol down goes to black screen / turning off the phone.. I managed to flash another recovery 3.1.0.0 but still I need to push some rom to see if I can flash it.
And the thing is while pushing big files(it takes few minutes) it randomly stops responding in the middle of a transfer. So I have to start again. Tried maybe 10~ times and still stopping transfer randomly.
Commands in console like fastboot oem device info gives < waiting for any device >
adb reboot bootloader
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
Click to expand...
Click to collapse
I just reverted back to Omni, I had my twrp.img on the phone, flashed it, restored my backup, no problems. Also, i used fastboot to flash back zl1 original files (including bootloader itself), no issues there either. I know its silly, but its happened before, try another pc/usb cable?
I might hold off on flashing this. Seems like recovery and other partitions are included in this that may render certain devices unbootable.
Thanks for sharing though. Hopefully a Dev can make a more stable port.
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
nea102 said:
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
Click to expand...
Click to collapse
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
I had used that guide, was following that when I was getting the out of space errors.
However, I got it all sorted in the end - I just downloaded a different (older) version of the firmware and that worked.
Help for you
samlis said:
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
Click to expand...
Click to collapse
Hi good day.
I have been following your work from another page, and now in XDA.
I had not read your message, and, I changed the recovery for the stock, and, I was an idiot to close the bootloader.
What happened? Brick simple on my cell phone, did not come out (because I fixed it) of the image of erecovery (EMUI) without tabs or options, a rather rare image.
How do I solve it:
1. I did not enter fastboot, I did not correctly enter the stock recovery (I had deleted the twrp), I had closed the bootloader (my stupidity)
2. Be patient and wait for the battery to run out (wait a day for it).
3. Open cmd and place the command to open the bootloader (fastboot oem unlock) and execute.
4. Put the device in fastboot mode when connecting to the laptop (I did not work several times, the fastboot came out with error FUNC No 10 and NO 2), after numerous attempts and not to let it charge the battery too much (because it was restarted and towards brick in the EMUI logo), correctly enter the fastboot and unlock, when you enter step 3 automatically, it will be executed. I had an advance in removing the cell phone from the brick.
5. It reboots and wonderfully happened to the Rom (that had previously installed), that is to say, the erase was not executed when the bootloader had previously closed.
6. As I had little energy, it was turned off, but I connected it and entered charging mode without restarting (before I did it).
7. Wait for a load of at least 5%, and install the Catuva21 TWRP from the tutorial.
8. I put it by command to restart in fastboot, but I generate error (Error Func No 10 and No 2).
9. I turn off the cell phone and with volume up and power key
10. Enter the TWRP correctly, verify that it is installed.
11. Restart system and log in to the system. I had not deleted anything, but to avoid problems, I hope to load 55% and execute the steps to install the rom.
12. Enjoy and dry spilled tears.
Experience lived and I hope you do not do something that developers do not advise.
Grcias and happy day.
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
heindrix said:
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
Click to expand...
Click to collapse
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
yoni sofer said:
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
Click to expand...
Click to collapse
take a look here, mate.
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Didn't realize how common this was until I had to look around for a fix. Apparently when flashing a new rom (In this case it was Oxygen OS, Bliss, and Lineage I was trying) It's possible to screw up your Persist partition which govern your sensors. As a result me and a few other people when flashing new roms lose auto-rotate. So I was looking on ways to fix it, but the downloads were too old and broken.
So **** it, I decided to try flashing Miui global from the recovery tool.
So my system image, and recovery image are gone. That leaves me with just Fastboot with unlocked bootloader.
I explained my situation, but here's what I'm really asking. #1 I used to have a Xiaomi account that was authorized to unlock my bootloader. It's been over a year, but before the recovery tool bricked my Mi Pad, it said EDL not authorized. So do you lose your permissions over time? Anyway to get it back.
And #2, does anyone have, know, or would like to provide me backups to vendor, firmware, and/or persist so I can try to fix those? I don't have the time tonight, but even though I don't have a system or recovery, I'm assuming with an unlocked bootloader and fastbook, I can still flash twrp, and work my way from there...
Lastly #3, does anyone know how to bypass EDL not authorized in the recovery tool? This is my preferred way of recovery, since it would reflash all the partitions back to stock and I could just re-mod from there...
I have actually recovered from a destroyed system image, destroyed recovery image, with a locked bootloader. But didn't encounter the EDL issue in my memory, it's been so long I forgot how that happened
Just like to add that I discovered that I still have recovery access, so I could just flash a rom to get back into working order, but that still leaves my sensors not working. So if anyone has a link or backup for Persist partition that would be appreciated
Okay, I know no one replied or helped, but I resolved my own issue, and I'll describe how I messed myself up to get myself better.
1. Flashed a rom via TWRP, this somehow led to rotation not working. Learned rotation sensor data is in Persist partition. Assuming this partition overwritten, corrupted, or likely wiped due to negligence.
2. This led to me trying out Xiaomi recovery tool. I would find out that my account isn't authorized anymore. So flashing tool would always stop flashing when it came to flashing the kernel. Then I created this thread for help. Particularly to acquire a backup of someone's Persist. Help did not arrive
3. This led me to download the Chinese rom (flagship zip) of Miui for Xiaomi Mi Pad 4. This was going to overwrite my recovery and vendor partitions, so I was hoping it would flash my Persist partition as well.
4. System would not boot, softbrick/bootloop. Recovery reverted to stock Chinese. Bootloader still unlocked. Booted into Fastboot
5. ADB terminal, typed:
Code:
fastboot devices
Getting device ID, looking good. Then typed
Code:
fastboot flash recovery rec.img
(I renamed TWRP to rec.img for lazy reasons) ADB says writing flashed recovery successful.
I reboot into recovery. Recovery still Chinese stock ?️?️?
Back to Fastboot, repeat #5, same. Then I type
Code:
fastboot erase recovery
ADB confirms erased recovery, I type:
Code:
fastboot boot recovery
ADB does not detect recovery. So I'm thinking my recovery is gone now... Then I try booting into recovery through Vol Up + Power to make sure recovery had been destroyed... Recovery still Chinese stock ?️?️??
So my assumption was correct that I couldn't overwrite my recovery partition, and my fear was that I needed to enable USB debugging even though my system partition is destroyed
6. I boot back into Fastboot and I type
Code:
fastboot boot rec.img
This boots TWRP without flashing it to your recovery partition... Atleast this works.
7. Attempt to wipe System/Data/Cache/Internal, even though only half those weren't necessary. Could not wipe. Mounted, then repeated... Could not wipe. Assuming this was encryption related, I go back to Wipe and just Slide to format to factory conditions. Finally getting somewhere here.
8. Tired of this hole I dug myself into, I plug in my USB flash drive and flashed TWRP Permanently using TWRP, reboot into recovery to confirm -> looking good -> Flash Lineage + Gapps, with the acceptance that because I didn't have an authorized Xiaomi account anymore, and no one would share a Persist backup, that I was just gonna have to deal with no rotation and rely on an app-crutch
9. Boot into System, rotation working. ?️??️
I didn't think flashing the zippable Chinese rom would actually fix Persist. I originally intend to just use the Chinese Miui and setting up my Mi Pad 4 with my Xiaomi account to somehow re-authorize my account to try the flashing tool again. I did not expect the bootloop, and I damn sure didn't expect ADB telling me I successfully flashed recovery or erased it, only to find out stock recovery kept refusing to go away.
And my final question is:
Can anyone tell me how much usable storage the 32GB Mi Pad 4 should freaking have?!
I always used Micro SD flashed as Internal Storage so I'd always see 80GB free. But now on a fresh install on a new rom I see that I only have 22GB usable storage, on a 32GB device, Lineage less than 1GB, and gapps only 200MB. So all together OS should not exceed 2-3GB unpacked...
WHERE THE HELL IS THE REST OF MY STORAGE?!
I SHOULD HAVE 5 MORE GB, I SHOULD HAVE 26~27GB OF USABLE STORAGE BUT MY SYSTEM SAYS ONLY 22Gb
DOES anyone else have 10GB of storage missing?!
How much should I have?!
Thanks this is good read and may help someone in the future.
There is a persist.zip shared in the Miui 12 port thread.
I have the 64gb version but never took notice of how much remaining storage out of the box. Next time I flash a ROM I'll check and let you know.
scloss84 said:
Thanks this is good read and may help someone in the future.
There is a persist.zip shared in the Miui 12 port thread.
I have the 64gb version but never took notice of how much remaining storage out of the box. Next time I flash a ROM I'll check and let you know.
Click to expand...
Click to collapse
Yeah, I found persist zips but the link was broken.
This is actually the 2nd time I bricked my device, but the 1st time I bricked it, I had just got it around the same time I got the Poco F1, so I had a Xiaomi account, with authorization. So I assumed how I un-bricked my device the 1st time, would fix the brick the 2nd time. I never imagined my account would lose authorization. So flashing the Miui using the Xiaomi recovery tool was useless. So I had to learn/relearn other tricks.
I actually enjoy bricking my devices a little bit for the experience to learn new things. Like this time, I didn't know you could run a recovery on the side through fastboot commands without flashing it. I also didn't know that recovery partition would reject flashes because mi stock recovery was encrypted (or maybe it was a USB debugging thing) , I didn't know Mi Flash authorization could be revoked, and I didn't know what the Persist partition did.
My 1st brick happened because of the Mi recovery tool. No one told me that if you buy a Mi Pad 4 with unlocked bootloader from AliExpress, use the Mi recovery tool, the tool actually intentionally bricks your device and locks your bootloader. The fix for that was opening the mi pad up, shorting some contacts, force the pad into EDL mode, and use a patched bat file and run the tool again and pray it takes. Because I wasn't authorized it wouldn't run the tool.
Thank ****ing God my bootloader was still unlocked this time. I don't think I could have came back
Post 225 in the Miui 12 port thread, the persist.zip is still being shared I checked just now. Not that you really need it if flashing the full rom got your rotation back.
There was 1 time my twrp touch screen became unresponsive after flashing and trying different twrps, and then system touch screen also gone dead, so I can't restore persist even if I wanted to.
One question, lots of tutorials talk about extracting the persist.zip from the fastboot ROM, but I can't find it in the fastboot rom... But the MiFlash tool had never failed me so anything goes wrong I'll just MiFlash it.
it started with calyxOS then i tried Paranoid Andriod and now i am trying RiceDriod.
Specifically it happens trying to go into recovery mode to install updates via adb sideloading but it just takes me to the google screen then the "your devices bootloader is unlocked" warning.
I just flashed stock using andriod flash tools and it worked fine. not sure why it wont work for the others.
catcatjpg said:
it started with calyxOS then i tried Paranoid Andriod and now i am trying RiceDriod.
Specifically it happens trying to go into recovery mode to install updates via adb sideloading but it just takes me to the google screen then the "your devices bootloader is unlocked" warning.
I just flashed stock using andriod flash tools and it worked fine. not sure why it wont work for the others.
Click to expand...
Click to collapse
You have to flash a custom recovery so that you can flash custom ROMs.
Lineage OS has a up to date collection for device specific recoveries. However, you have to check the compatibility of them with the ROM you are intended to flash.
You should read the OP of that ROM more carefully regarding the compatibility issue.
aimsjahan said:
You have to flash a custom recovery so that you can flash custom ROMs.
Lineage OS has a up to date collection for device specific recoveries. However, you have to check the compatibility of them with the ROM you are intended to flash.
You should read the OP of that ROM more carefully regarding the compatibility issue.
Click to expand...
Click to collapse
I do flash the custom recovery so I can flash the ROM. I never had an issue before but now I do even though I have done everything correctly.
How do I clear cashe partition and dalvik cashe? The rest of the steps I have done but have not worked unfortunately. even with the different roms.
Do you have a visual of this? Pixel 6 does not have a physical home button when powered off haha. It would also help just for better understanding what to do
nothings working so far guess ill stick with graphene until i get a new phone or a solution pops up
catcatjpg said:
Do you have a visual of this? Pixel 6 does not have a physical home button when powered off haha. It would also help just for better understanding what to do
Click to expand...
Click to collapse
To manually boot recovery on a custom rom just hold power button down , keep holding it down and once your screen goes black hold volume down till you are in bootloader/fastboot mode, then use volume to select recovery and hit power. That should get you in recovery on custom roms. Or you can plug in to a PC with adb and enable USB debugging and dev options on device, disable screen lock and type: sudo adb devices (for Linux ) and when the box pops up on your phone check mark it really quick. Now your device can have commands sent to it. If on a custom rom from cli type: sudo adb reboot recovery or sudo adb reboot bootloader then use volume keys to go to recovery and power to select it.
The best way to get out of a bootloop is hold power and volume down until you are in bootloader/aka fastboot mode then execute the ./flash-all.sh script that's in factory image and let it flash and wipe your device. You can always sideload a rom again but the factory image script will get everything to normal. There are tons of videos on YouTube about flashing device's. Everything changed a few years ago when Google started making android A/B partition devices but if you check out YouTube just do a quick search for whatever it is and more than likely you'll find what you're looking for there. Lots of pixel 6 videos!!!
Please explain your "exact " installation technique step by step. The more details the better the answers you'll get. What rom are you installing and exact steps you are doing to get in a boot loop.. While there are some highly intelligent people here nobody can read minds. Every detail helps to get a solution that works. Must be specific.. For me I rarely have issues but i don't flash nearly as often as I used to but when I have had a loop I hold power and volume down then from bootloader screen plug up to PC and I flash factory image using the flash-all.sh script that comes in factory image. Check out YouTube for visuals. Lots of good videos there.
This will hopefully provide more information on my situation
Currently I am trying to install RiceDroid for the pixel 6.
How I am in stalling it is I extract the images from the payload bin using a guide. Get the vendor boot image. Flash it with 'fastboot flash vendor_boot 'path/to/vendor_boot.img' then I try to boot into recovery which doesn't work it loads into the the warning screen then to the Google boot up screen but I never get to the Andriod 'no command' screen I only get taken back to the warning screen then back to the boot screen again untill I manually boot into bootloader again (power button and volume down) and flash my stock firmware.
Other Roms are not working for me either and it started happening after I tried to flash calyxOS and that failed. Now I can't even flash lineageOS or Evolution X rom only web flashing with GrapheneOS and Android Flash Tool can successfully flash my device.
im not sure what i did but things are working again