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.
Related
Hi,
I've got some trouble to get a proper root mod on my phone. After i used some of the hints which can be found in this forum i didn't managed to get it running.
History of my mod-trys:
I got it running until i patched my stock Rom to the latest version via fota. (the feature pack for German roms)
Then i tried to go back to a stock Rom here at the forum - but with little success. I installed it but important not able to get the root mod running without errors.
This is a screenshot of superuser:
{
"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"
}
If i try to update i am getting an error.
Sadly i don't know what to do now to get this fixed. Iused many fresh installs / cleanup etc but everytime i install the update.zip via recovery - its messed up.
gesendet mit Tapatalk 2
try to flash CWM with ODIN.. do not use adb shell because it needs root.. the try flash another ROM.. IT'S VERY RISKY.. I'M NOT RESPONSIBLE IF YOUR PHONE BRICKED
i've got cwm at the moment installed. As far as i understood the "root / unroot" thread it's not recommended to use this while rooting via recovery.
i used cwm to create a backup of my system and i rolled back it many times - so - thats working fine.
But my problem is that i don't find a suiteable custom rom for me - because it has to be "as stock as possbile". Meaning - i'm doing much development and testing with that phone - so it's not good if the mod can do things which i can't do with a stock rom. (Rooting is ok - i can handle that "mod" - if it works )
But i'm not firm enough with android core development to fix the root problem right now. Are there any manuals to use the "USB Debugging" Shell? I'm able to use that, too.
OR - if exsists - is there any _german_ stock rom out including the "value pack" addon? I just found a stock rom which is missing that. I guess there's coming with the value pack that causes rooting via update.zip going mad
i cant also root mine and i also have the value pack update but before i had the value pack i can still root my phone :CC
Hello everyone and have a Merry Christmas,
I'm trying to update my TWRP recovery because I want to go 100% stock. I'm still running TWRP 2.7.0.2. The most recent version of TWRP is 2.8.3.0.
I downloaded the TWRP manager app from the Play store and easily selected the last available version of the recovery to install.
After downloading the .img file, I get a pop up that looks like this:
{
"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"
}
The pop up says: "Be sure that the listed path is correct for your device. An uncorrect check may result in bricking your device. You can't flash a recovery directly on Android on some devices. If you can't flash through Android, please choose a different method".
It looks like a "routine" alert, but nonetheless it sounds very alarming. How can I say if the listed path is the correct one for my device (HTC One M8 unbranded GSM international version)?
Thank you for helping.
why update twrp ? twrp is not stock ! and you can also fastboot flash it. oldskool way
Because the procedure to go stock requires some flashing and it was adviced to have the latest version running.
I'm not such an expert, I'm more the type who tries to read as much as possible before trying anything, and upgrading TWRP was a sort of "pre-step".
Also I'm not very keen to use fastboot: I got that it is great, but it is not very straightfoward for beginners.
The tool from the Play store seemed to do the job pretty good and easily.
Mr Hofs said:
why update twrp ? twrp is not stock ! and you can also fastboot flash it. oldskool way
Click to expand...
Click to collapse
What if I flash a custom recovery over a custom recovery? Is it possible to simply flash it and overwrite an already existing custom recovery?
there is no other way, the recovery will always overwrite the old one. its impossible to run 2 recoveries
Hi,
I am a complete newbie when it comes to this so please explain in simple terms.
So I will explain as briefly as possible:
- I have Windows 10 x64
- Bought LG G3 last week, it had Android 4.4.2 (and was already rooted)
- It had overheating issues and battery died fast so I tried to update Android via LG PC Suite -> Did NOT work
- I read that having root access blocked it, but that I could update manually
- I installed USB drivers
- I setup ADB and Fastboot
- I tried using LG Flash Tool 2014 and the Android 6.0 KDZ but it did NOT work (always said there was connection error)
- I tried using lgg3rootdotcom's method to reset the phone back to STOCK ROM without root and followed their instructions to the letter (set COM to 41 etc)
- I did everything, but then it keeps coming up with an error on LG Flash Tool (at 6%)
- It repeats "LAF : Bin_User_Mode" three (3) times whereas in the instructional video it only showed ""LAF : Bin_User_Mode" once (1)
- Then "[ERROR] : Partition Change factory Partition (Phone!=tot)"
(I want to share images but I can't because I am a new member with restrictions, I will post images later today)
- I downloaded the .tot and .dll from lgg3rootcom's website
- I tried D855 Europe, Hongkong, and Taiwan .tot but NONE worked
- Now my phone ONLY boots into Download mode :crying:
- I cannot get into Recovery mode or Normal boot...
- I REALLY just want to get it back to stock right now... Please HELP!
Any help will be much appreciated! Thanks in advance!
I used exact instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2772199
But it ERROR appears at 6% with "[ERROR] : Partition Change factory Partition (Phone!=tot)"
Also, please ask any questions if you want to know more so you can help me..
{
"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"
}
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.
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.