After a bunch of research I finally decided to take the plunge to try and move to Lineage OS.
Phone is a Google unlocked 128GB 2 XL.
I was able to get through the unlock portion but after that all the guides went different directions. I was following the process from TWRP and at one point had the TWRP recovery app showing via fastboot but now all I get is the "device is corrupt" warning which then ends up in the white screen with Google logo and small unlocked icon.
Any chance I can get back to scratch or press forward to LineageOS/other ROM or is this thing a brick?
*Update* Not sure what key combination I used but I can get to the following TWRP screen. However the touchscreen does not respond and after the screen hibernates any key returns it to this state:
{
"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"
}
Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.
Strephon Alkhalikoi said:
Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.
Click to expand...
Click to collapse
Not sure how I can do that.
I can get to the default green START option. If I selection that the system boot to a white screen adn stops.
If I select BOOTLOADER the device pops back to the green START.
If I select RECOVERY it gets to the TWRP screen but the touchscreen nor buttons work.
I've tried connecting the phone via USB to my PC but no matter what mode I put it in ADB never detects it.
The "green Start" is where you want to be here. That's the bootloader. You need to make sure the driver - assuming Windows - is set to ADB Bootloader Interface in Device Manager as well as make sure you have the latest version of the ADB / Fastboot package.
Related
Hi, I am reading whole day forum, but cannot find the solution, please help me guys.
My story:
I was made succesfull root, than i putted TWRP recovery, made a backup, and full wipe, than i realize, that i forgot to load CM11 rom... So i restarted device, enter TWRP, and make a restore of backup...
After that, there was no KindleFire blue logo...
After reboot, the device just show static orange kindlefire logo...and that is all.
Only thing I can do - is to enter * using CMD line * to the fastboot mode.
Now i am trying to restore kindle using KFFirstaide - but i get errors because of that there is no files to download from dropbox...
{
"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"
}
also tried SRT ( I am confused, which is the best/last version of this software ?) , and it looks like it works, something was loaded, but after that, still have static logo, nothing more..
Is there any hope ?
HELP
ok, finally
i manage to push system, recovery and reboot via KFHD System.img Recovery Tool
I run the device with 8.4.1, and i manage to check , that device is still rooted ( via rootchecker ).
After that, i try to again push the twrp into the kindle, doing as it was last time, by the fire flash, but after that - i had no TWRP, and again - I stuck on the kindle fire logo...
What is wrong ?
I'm guessing you forgot to check something off in fireflash like apply stack override.
Sent from my Amazon Tate using Tapatalk
id fallen into like this case, and i did restore using KFFA type 1 on my kindle,
but it output like that error,.. and stuck on boot logo,...what can i do?
and i dont have original boot.bin, recovery.img and system.img, where can i get it?
PLEASE HELP ME!
Hi All,
First off, this is what I did that led to this problem:
*** Beforehand, phone is unlocked, rooted, and updated to latest OTA OOS version (I think 3.2.7)
*** Unlock, recovery, root and NFS backup was implemented using this guide
*** OEM unlocking was turned off in the Developer Options
1. DPI was changed using the [email protected]_radaideh as recommended by some in Reddit -- this was OK
2. DPI was changed again using Le DPI Changer (found in play store), but used "EDIT BUILD.PROP" option
3. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
4. Booted into TWRP, and restored NFS backup (pre-root) and it was successful according to TWRP
5. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
Now after this moment, I tried Method 1 of the mega unbrick guide, but I encountered multiple md5 check failures upon boot. I then tried Method 2, and the md5 check failures were reduced to just one: system: failed.
{
"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 can boot into fastboot, but I can't boot into recovery and system because of said error. Please help!
flash stock system.img
I already tried that using:
system.img from FULL unbrick tool -- doesn't work
system.img from 3.2.5 found somewhere here in XDA -- doesn't work
As mentioned above, the OOS version was at 3.2.7. I couldn't find it in the OP downloads site, but I did download the 3.2.6 image. That, however, did not contain any system.img.
did you find a solution
Try method 2 unbrick tool as per what they said, again. No other choice.
Hi, did you find a solution for this ? I have a similar issue and even after several flashes, i still have the failed md5 failure on system.img.
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"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"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma
Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.
Facing the same issue. Tried everything but no success.
Do it at your own risk.
Share tutorial to help others.
This error happens because the ROM is not the correct one for the device;
Example:
PCAMIXM, OCACNXM, OCACNFK, OCAMIFH, and ETC.
If you remember what you were using before installing the rom that gave the problem just install again.
Example: I remember I was using PCAMIXM and installed OCACNXM.
Just go back to PCAMIXM.
If you do not remember you will have to test with existing, the correct rom will not display the message(Find device storage corrupted).
D̶o̶ ̶n̶o̶t̶ ̶u̶s̶e̶ ̶t̶h̶e̶ ̶u̶p̶d̶a̶t̶e̶ ̶R̶O̶M̶ ̶b̶e̶c̶a̶u̶s̶e̶ ̶i̶t̶ ̶d̶o̶e̶s̶ ̶n̶o̶t̶ ̶w̶o̶r̶k̶!̶
Fastboot ROM only.
First set up the device even with the message: Find device storage corrupted.
{
"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"
}
Enable OEM Mode
Whebever you change ROM, enable this option first before writing the new ROM!!!
[*][font=ProximaNova, Arial, sans-serif]Unlock[/font] the boot, don't worry it will be locked again when we pass the ROM.
Please follow the steps below:
Step 1. Download Mi Unlock application on PC and sign in with your Mi account;
http://miuirom.xiaomi.com/rom/u1 ... k-en-3.5.910.35.zip
Step 2. Turn off the phone manually and hold down the Volume down key and the power button to enter fastboot mode;
Step 3. Connect your phone to the PC using the USB cable and click "Unlock".
There we have the boot unlocked.
Download the program:
XiaoMiFlash
Links to roms in fastboot mode;
V10.4.1.0.PCAMIXM:
https://bigota.d.miui.com/V10.4.1.0.PCAMIXM/sagit_global_images_V10.4.1.0.PCAMIXM_20190714.0000.00_9.0_global_dbd26e5a5e.tgz
V10.3.4.0.OCAMIXM:
https://bigota.d.miui.com/V10.3.4.0.OCAMIXM/sagit_global_images_V10.3.4.0.OCAMIXM_20190527.0000.00_8.0_global_cc4f15601b.tgz
V10.0.1.0.OCAMIFH:
https://bigota.d.miui.com/V10.0.1.0.OCAMIFH/sagit_global_images_V10.0.1.0.OCAMIFH_20180905.0000.00_8.0_global_7ce4be65b4.tgz
Extract the rom:
sagit_global_images_V10.4.1.0.PCAMIXM_20190714.0000.00_9.0_global (Do not leave subdirectories, only the folder without subfolders).
Open the program click select and select the extracted rom.[attachimg]4808252[/attachimg]
Then select the option: clean all and lock(This option is at the bottom of the program.).
Then click flash.
Wait for the process to finish...
If you get the lock state message go to next rom.
This message may also be displayed when OEM mode is disabled.
Or bootlocked, fix [font=ProximaNova, Arial, sans-serif][color=#0800]Unlock[/color][/font] the boot
Click to expand...
Click to collapse
After the flash is over you will have your cell phone working again.
Being able to repair my device like this, I can't guarantee it will work with everyone!
Hope it helps anyone who is experiencing this issues.
Here are other ROMS for other models.
MIUI Global ROM All Devices
Additional information:V10.4.2.0.PCAMIXM(Latest)
V10.4.1.0.PCAMIXM(Rolled back)
V10.3.4.0.OCAMIXM
V10.3.1.0.OCAMIXM(Rolled back)
Got any tips? post to help your friends.
Sorry for any mistakes, my time is short.
Good luck.
EDIT: RESOLVED
I was in TWRP and decided to format-all (checked all the boxes).
Then, for some reason I decided to switch to the other side (Boot_B) and do the same there.
But the TWRP on that side was broken.
And now I'm stuck with no OS installed.
And my PC won't recognize my phone when I plug it in.
I've tried all three of my known-working cables and both of my computers.
Windows Device Manager doesn't see anything being plugged in.
It's not even coming up as an unrecognized device. Windows pretends like I haven't plugged anything in.
So, no ADB device, no Fastboot device, no Qualcomm device, no unrecognized device.... simply NOTHING.
Now the phone just boots to "The bootloader is unlocked" or to the broken (frozen) TWRP where even a USB-OTG mouse won't work.
With phone plugged in:
{
"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"
}
FINALLY got it to boot into fastboot mode!
First, power it all the way off.
Wait a minute then press & hold all three buttons.... Volume (+) & (-) and Power-button until you see fastboot.
And finally my computer sees it.
Cool, and I was able to do a "fastboot set-active a" and then reboot to the properly-working TWRP.
I should be good to go now!
EDIT:
Actually, I still can't get into MSM (nothing in device manager).
And ADB sideload or ROM install from TWRP ends in “kInstallDeviceOpenError”
EDIT 2:
I remembered that TWRP has a "reboot to EDL" option, so I used that and I'm now MSM'ing just fine.
Don't use TWRP on these devices. Even on A11 it doesn't work right. ROM devs post a recovery that's meant to be used with their ROMs, use that.
EtherealRemnant said:
Don't use TWRP on these devices. Even on A11 it doesn't work right. ROM devs post a recovery that's meant to be used with their ROMs, use that.
Click to expand...
Click to collapse
I use TWRP for full ROM backup & restore purposes.
And it works fine as long as I don't try to get too fancy.