Marshall London - Root, recovery and system images. - KB-1501 - Megathread - General Topics
The Marshall London is no longer supported by Zound Industries and has been discontinued. Anything further will have to be done by developers and that seems unlikely. This thread and the files linked in this thread will remain online for those who have a Marshall London phone and need to restore and/or root their device.
---
Why this thread?
I have finally made enough progress with the Marshall London to where I feel comfortable enough posting a thread for this device. I doubt this device will ever get its own section considering how niche and relatively unknown it is... Aside from a couple of questions about root for this device, there's basically next to zero support on XDA (or anywhere else)... and I hope to change that. Hopefully people will be able to find this thread.
Some notes:
Extra special thanks to Dees_Troy for getting a working TWRP recovery for me to test out and use. Also extra thanks to autoprime. This basically wouldn't have happened without either of you two putting up with me on IRC.
Also thanks to Zound Industries for providing the stock fastboot flashable images for those who would be unable to take OTAs, as I wasn't able to for some reason.
I'm not a developer, just the one who managed to find the awesome folks to help me with all of this.
What is the Marshall London?
The Marshall London is a phone designed by Zound Industries with design elements licensed from Marshall. There was an emphasis put on sound quality and to be able to use the phone as a multi function media device. Two headphone jacks, front facing speakers that actually sound pretty good and are loud, Cirrus Logic Wolfson DAC, the ability to control volume levels for each headphone jack independently, the ability to use both headphone jacks as stereo INPUTS and to do 4 track recording on the device... It's a nifty little device hampered by poor performance from the Snapdragon 410 SOC in it. The phone is actually pretty awesome... and most of the issues go away once you make some tweaks.
Unfortunately, likely due to out of the box performance issues and cost... the phone never really took off. Even just using the phone as a high quality mp3 player resulted in issues (mostly lag) until I was able to find a way to pare down the system to only what I needed. My aim is to give people access to the tools they will need to be able to do this for themselves as well... but also to help people fix their device should something have been done that necessitates a return to stock.
Some reviews about the device to digest:
https://www.engadget.com/2015/09/12/marshall-london-review/
https://www.digitaltrends.com/cell-phone-reviews/marshall-london-review/
http://www.androidauthority.com/marshall-london-review-659269/
https://www.theverge.com/2015/7/16/8976561/marshall-london-smartphone-images
One of the best things about the device is its near completely stock Android software. Aside from visual tweaks (wallpapers, icons, word clock) the software is largely as you would find it from Google. As far as I know, the only real proprietary aspect of the phone is the audio DAC and "M-Button."
Specs:
Snapdragon 410 SOC in 64 Bit Mode (MSM8916)
2GB Ram
16GB Storage/NAND
Nano Sim Slot
MicroSD Slot that supports 128+GB cards
1280x720 Screen at 320 DPI
Cirrus Logic Wolfson DAC Hub
Dual Front Facing Speakers
Dual Headphones/Input Jacks
Programmable Shortcut "M-Button"
Volume Wheel
Removable Battery
8MP Rear Camera, 1080p Video recording mode
1.9MP Front/Selfie Camera, 720p Video recording mode
So yes, low average specs, even for when it was announced in 2015.
Where is it available?
Europe, mostly. It appears (in internal software memos) the device was tentatively planned for release in the US as an AT&T exclusive and it just never happened. If you're in the States like I am, you will have to import it or buy it used. Some ... ahem ... opportunistic people thought the relative scarcity of the product meant they could just buy one and try to resell it for double. You can easily import order (on eBay or Amazon) this device, brand new, for about $400 USD. I got mine from a store in Italy called E-Commerce World/Ghz Wireless and it arrived in 5 days. They were nice enough to include an EU to US power adapter in the package. Wherever you do find one, don't pay more than $500 for it. Marshall still has it for sale on their own site.
Where is it compatible?
Europe, mostly.
https://www.frequencycheck.com/models/vq2a7/marshall-london-4g-lte
https://www.marshallheadphones.com/mh_us_en/faq-london
GSM: 850, 900, 1800, 1900MHz
WCDMA Bands: 1/2/4/5/8
LTE Bands: 1/3/4/7/17/38/40
You might have some luck in the US with AT&T (bands 2, 4, 12, 17 for LTE) and AT&T based MVNOs or T-Mobile (bands 2, 4 and 12 for LTE) but I wouldn't count on it. Trying the phone in Colorado on an AT&T MVNO left me with only 2G service. I am unsure if additional bands are supported by the hardware but locked/limited in software. Hopefully this thread will spur some development and we can find out.
http://www.androidguys.com/2016/07/12/reference-guide-to-us-carrier-bands-and-networks/
Accessories?
Sadly, next to none. There's a nice leather flip case with a red velvet interior that was made for the phone (you don't slip it in, but rather another battery cover is stitched into the wallet itself)... but good luck finding one. Headphones, like the one that was boxed in with the phone itself, are available separately through Marshall's site.
What then?
Due to the lack of support, ANYWHERE, for this device, I enlisted the help of some folks to try to remedy that.
Here's what I know about the device:
It is not bootloader locked.
Fastboot is 100% standard. It shows up as a Google device and all commands are supported.
It is rootable. (I used Kingoroot initially, not recommended because it brought the system down to its knees with its bundled crapware)
A working custom recovery now exists for the device. As a result, this means you can root it from within recovery instead of relying on shady root tools.
This also means you can now use XPosed.
Goals for this device:
Stock images for flashing device back to 100% stock :good:
Rooted images for flashing (though may break OTA) :good:
100% working TWRP Recovery for backing up, flashing other roms, rooting the device with Magisk. (Magisk, since it modifies boot.img, also may break OTA) It will be mentioned several times, because it's that important, DO NOT use the TWRP built-in root/SuperSU installer. There is a reason the instructions say to use Magisk instead. :good:
Enough resources to allow for people to start developing custom roms for this device should anyone feel inclined. :good:
All goals met. :highfive:
Known issues:
Changing the DPI with build.prop editors won't work.
Changing the DPI using ADB (adb shell wm density ### && adb reboot) works but will break all Marshall apps: The onscreen buttons render right but cannot be activated. This means that if you want to use the device for music, you'll have to replace the stock music app (and freeze it to keep it from hijacking audio playback) for another one if you change the DPI to show more on the screen. I find 260 or 280 to be a reasonably good DPI value for both size and density of information. Default is 320.
This device cannot be rooted using the internal tool in TWRP Recovery. It will cause the device to hang on boot. Use Magisk instead.
To flash these images, you will need to use Fastboot. If you don't already have Fastboot installed, you can install Minimal ADB and Fastboot from this thread: https://forum.xda-developers.com/showthread.php?t=2317790
System Images
These are raw, stock, flashable in Fastboot only images. If you already have a custom recovery installed, then you can use that to flash these images instead. Bear in mind that flashing recovery.img while in recovery will replace your custom recovery with stock recovery.
The device ships with version R313.
persist.img : https://www.androidfilehost.com/?fid=745425885120742754
persist.img : md5 : 682275ff830598fa42a05250002cc02f
splash.img : https://www.androidfilehost.com/?fid=961840155545573563
splash.img : md5 : 1d56e5e62f27baf837084165694db52c
boot.img : https://www.androidfilehost.com/?fid=961840155545573562
boot.img : md5 : fe044e9ca9ccf7bdc4819500cfbffcda
recovery.img : https://www.androidfilehost.com/?fid=889764386195907755
recovery.img : md5 : 6b3b9e3b171a8f1151a60ae14e410b93
system.img : https://www.androidfilehost.com/?fid=745425885120740418
system.img : md5 : 4f6fef214ed162d921c85c5369f3454d
Version R403:
persist.img : https://www.androidfilehost.com/?fid=673368273298965596
persist.img : md5 : 10f983ad12dcf8452527bef513951ea5
splash.img : https://www.androidfilehost.com/?fid=817550096634777452
splash.img : md5 : 1d56e5e62f27baf837084165694db52c
boot.img : https://www.androidfilehost.com/?fid=745425885120740107
boot.img : md5 : e1d7f8875afb3a4a00602890a5b94ee7
recovery.img : https://www.androidfilehost.com/?fid=745425885120740108
recovery.img : md5 : 1d4da69e929119e85c68117fadc0484f
system.img : https://www.androidfilehost.com/?fid=817550096634777453
system.img : md5 : 7078ca8cd3ba8b7ba4e5baa94112e570
Version R412 is currently the latest version for the device:
persist.img : https://www.androidfilehost.com/?fid=817550096634780185
persist.img : md5 : 40e0e812ea0645fcd46c3136dc8f85a9
splash.img : https://www.androidfilehost.com/?fid=817550096634777468
splash.img : md5 : 1d56e5e62f27baf837084165694db52c
boot.img : https://www.androidfilehost.com/?fid=889764386195907458
boot.img : md5 : dac5a75fa41ddfe9da9186ea475ed707
recovery.img : https://www.androidfilehost.com/?fid=889764386195907459
recovery.img : md5 : 71aed500e670b7a81d6a7a43b7ae9ed0
system.img : https://www.androidfilehost.com/?fid=817550096634777469
system.img : md5 : a5b5001f9417ccc7e237661a01b2da38
How to flash:
1) Download all of the files for the version you want to flash.
2) Power off the device completely.
3) Enter fastboot mode by holding down the M-Button top of the phone and then holding down power until "FASTBOOT MODE" screen shows up.
4) Connect your phone to your computer. (This assumes you already have Fastboot and ADB installed and generally know how these tools work)
5) Use fastboot to flash each of the images to the correct partition: eg,
Code:
fastboot flash persist KB15_3_R403_160608_persist.img
fastboot flash splash KB15_3_R403_160608_splash.img
fastboot flash boot KB15_3_R403_160608_boot.img
fastboot flash recovery KB15_3_R403_160608_recovery.img
fastboot flash system KB15_3_R403_160608_system.img
6) Reboot.
First boot after flashing the system images will take some time as "Android is upgrading..." If you flashed version R412, you will be on the latest version. The older versions are provided for those who may have preferred them.
Custom Recovery
Before you install this recovery, it is very important to know that you MUST NOT let TWRP install SuperSU.
Download the latest TWRP from here: https://twrp.me/devices/marshalllondon.html
Older/Test build:
TWRP v3.1.1-0 : https://www.androidfilehost.com/?fid=745425885120740158
TWRP v3.1.1-0 : md5 : 05e61cbeb1afbc479d85f260acf52d3e
1) Download the TWRP image linked above.
2) Power off the device completely.
3) Enter fastboot mode by holding down the M-Button top of the phone and then holding down power until "FASTBOOT MODE" screen shows up.
4) Connect your phone to your computer. (This assumes you already have Fastboot and ADB installed and generally know how these tools work)
5) Use fastboot to flash:
Code:
fastboot flash recovery Marshall_London_TWRP_3_1_1-0.img
6) When fastboot is done, DO NOT reboot. Doing a fastboot reboot or fastboot reboot-bootloader will cause the system to overwrite TWRP with stock recovery. Pop the battery out instead.
7) Feel free to boot into recovery at this point to root or make backups. (Volume Wheel + Power for 4 seconds after you feel the power on buzz)
Rooting
Whatever you do, DO NOT allow TWRP to install SuperSU/Superuser/Root. Your device will fail to boot.
You must use Magisk. Magisk is systemless root and does not result in files being installed in /system, preventing the hang on boot.
Note: The versions that work for me are Magisk 13.3 and MagiskManager 5.1.1. If the latest don't work for you, download these older versions and try those instead.
Magisk 13.3: https://github.com/topjohnwu/Magisk/releases/download/v13.3/Magisk-v13.3.zip
Magisk Manager 5.1.1: https://github.com/topjohnwu/Magisk/releases/download/manager-v5.1.1/MagiskManager-v5.1.1.apk
Click to expand...
Click to collapse
1) Download both the Flashable ZIP and Magisk Manager APK.
2) Put both the ZIP and APK on a MicroSD card.
3) Turn off the phone, put the MicroSD card in.
4) Boot into TWRP Recovery by holding volume wheel down and power button down for about 4 seconds after you feel the power on vibration. Release the buttons.
5) TWRP Splash screen should pop up. Swipe to allow write.
6) Press "Install", "Select Storage", "Micro SDCard", "OK", scroll down to find Magisk-13.3.zip, press the file name and them Swipe to confirm Flash.
7) Reboot.
8) Once booted, you will need to use a file browser app, like Explorer by Speed Software, to find MagiskManager.apk on your MicroSD and install it. (Why? Cause it was removed from the Play Store.) This will require that Unknown Sources is enabled under Settings/Security.
---
Edit for 2021:
I have revived my London for some projects and ran into some issues trying to use modern methods/versions for the device.
I wanted to upgrade what I could and using Magisk v23 on the boot.img bootloops the device. I tried some lower Magisk versions and was met with the same result... so instead of fiddling with it I went back to my known working config on my second London and ripped the files to fix my first device.
As such, it is HIGHLY advised that you stick with v13.3 (known working version on both of my devices) for the image and v5.1.1 for Manager.
The necessary files for this config have been mirrored here:
Modified Marshall London R412 Boot Img with Magisk v13.3 (no recovery) applied:
https://www.androidfilehost.com/?fid=14943124697586343614
MD5: 23426a4a1d82f9a7465ba9a7cdf30e1f
Magisk Manager v5.1.1:
https://www.androidfilehost.com/?fid=14943124697586343616
MD5: 790c9d412e7afbd76566ee47f24cd3b8
To flash:
From a power-off state, hold M-Button and Power until "FASTBOOT MODE" shows up on the screen.
Connect phone to PC
"fastboot flash boot MLondon_Magisk_Boot.img"
You *MUST* be on Lollipop version R412 for this boot image.
This now means that if you are on version R412, all you need to do is flash the modified boot.img file to root your device instead of flashing recovery and applying the Magisk.zip inside TWRP. I do not have fastboot flashable files for the last firmware version for the Marshall London (titled "Tom Petty").
The alternative, of course, is to use TWRP and go through the steps listed above, but honestly, I've found TWRP to be largely unnecessary when you already have a Magisk patched boot image. This all is just being put here to preserve a working config.
Success!!
{
"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"
}
New notes for the "Tom Petty" final system update:
All of the above steps will work for flashing Magisk and getting root. No changes at all.
If you are having trouble booting after installing Magisk, reflash boot.img and use an older version. v13.3 worked best for me.
Thanks!
I own a london and I just want to thank you for putting this all together. I love the device, and use it as an audio player. I was also lucky enough to find one that came with the leather flip case.
There's an update availiable, and I'm assuming that it would prevent me from attempting the above modifications. Am I correct to hold off on "KB15_3_R412_170324"?
caltemus said:
I own a london and I just want to thank you for putting this all together. I love the device, and use it as an audio player. I was also lucky enough to find one that came with the leather flip case.
There's an update availiable, and I'm assuming that it would prevent me from attempting the above modifications. Am I correct to hold off on "KB15_3_R412_170324"?
Click to expand...
Click to collapse
The R412 update will not prevent you from being able to flash in Fastboot. They, thankfully, have not locked down the device. Some people had better luck with an older version and held off on updates but you now are able to revert to an older version if you feel like an update you took introduced issues. (eg, Lag)
If you need to up or downgrade, just use Fastboot to flash system.img and boot.img and reboot. I've been able to 'dirty flash' between system versions without having to wipe data.
Hello !
I am looking forward to root my Marshall London but I'm pretty new to android programmation & stuff
Is TWRP installed by default or do I need to install it myself ? Because when I hold the volume wheel and the power button, I get on "Android system recovery" and not TWRP.
If I have to install TWRP by myself, can someone send me a link for a tutorial or something ?
That's been more than a year I'm trying to root my phone, that'd be very kind of you if you can help me.
Lastly, I'd like to apologize if I made some mistakes as English isn't my native langage.
Thanks for anyone that is willing to help me !
Update : I have sucessfully rooted my London, any ideas where I can find custom ROMs for it ?
Can the 410 be over clocked and is anyone doing that?
Also, anyone installing apps on the microSD successfully?
Thanks!
Sent from my XT1095 using Tapatalk
Sancora said:
Update : I have sucessfully rooted my London, any ideas where I can find custom ROMs for it ?
Click to expand...
Click to collapse
There aren't any. This thread is the first to provide anything for this device.
eKeith said:
Can the 410 be over clocked and is anyone doing that?
Click to expand...
Click to collapse
Not without a custom kernel. There isn't one due to the lack of kernel source from Zound.
Thanks for the sharing. Your posting is very useful.
This is great, i did try to get hold of initial rom from the support, because with every update my phone broke more and more, but according to them they did not save old roms.
But for some reason i cant flash the files, only get "error: cannot load 'KB15_3_R403_160608_persist.img'" and the same for the other files.
Did forget that there is usually problem with long names, fixed by renaming.
The links to the system images doesn't seem to work they only say "no mirrors found"
Thanks!
Is it possible to build a own kernel for the phone?
I also tried to get the source from Zound Industries a few months ago with no luck.
I'm interested in creating a port to Ubuntu touch but I think a source for the kernel is required to do this.
This is something I would like to try to learn how it all works.
please new uploading brothers firmware version R412
i cant flashing system.img KB15_3_R412_170324_system error !!!!!!!!
please brothers can you help my please
this error
C:\adb> fastboot flash system C:\adb\KB15_3_R403_160608_system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.100s]
sending sparse 'system' (259594 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 11.399s
stuck on magisk manager
Hello and thank you for the great guide. I managed to do all the steps, but it seems my Marshall London is still not rooted. Am I supposed to open magisk manager and press install? If so it is not working, I get error: Unable to unpack boot image.
Thankful for all the help I can get.
Woah, seems like a nice thread to play with! Time to DIY repair my London?!
One question - how's yout GPS, guys? Been through 5 Latvia devices with nonexistent GPS performance. Please advise what can be done to solve this.
Hello,
i have marshall london with restart on logo
tried flash , wipe data
flashed ok but same condition
how to fix it ??
Code:
C:\Users\Syed Mobile\Desktop\marshall london>fastboot flash persist 1.img
target reported max download size of 268435456 bytes
sending 'persist' (4708 KB)...
OKAY [ 0.141s]
writing 'persist'...
OKAY [ 0.531s]
finished. total time: 0.688s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot flash splash 2.img
target reported max download size of 268435456 bytes
sending 'splash' (2700 KB)...
OKAY [ 0.094s]
writing 'splash'...
OKAY [ 0.109s]
finished. total time: 0.203s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot flash boot 3.img
target reported max download size of 268435456 bytes
sending 'boot' (24994 KB)...
OKAY [ 0.797s]
writing 'boot'...
OKAY [ 2.188s]
finished. total time: 2.985s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot flash recovery 4.img
target reported max download size of 268435456 bytes
sending 'recovery' (25692 KB)...
OKAY [ 0.828s]
writing 'recovery'...
OKAY [ 0.422s]
finished. total time: 1.250s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot flash system 5.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.531s]
sending sparse 'system' (259594 KB)...
OKAY [ 15.721s]
writing 'system'...
OKAY [ 17.299s]
sending sparse 'system' (261941 KB)...
OKAY [ 15.720s]
writing 'system'...
OKAY [ 20.596s]
sending sparse 'system' (259218 KB)...
OKAY [ 15.144s]
writing 'system'...
OKAY [ 21.081s]
sending sparse 'system' (251451 KB)...
OKAY [ 14.486s]
writing 'system'...
OKAY [ 19.768s]
sending sparse 'system' (257536 KB)...
OKAY [ 15.064s]
writing 'system'...
OKAY [ 19.924s]
sending sparse 'system' (258042 KB)...
OKAY [ 15.220s]
writing 'system'...
OKAY [ 21.252s]
sending sparse 'system' (206561 KB)...
OKAY [ 11.783s]
writing 'system'...
OKAY [ 16.252s]
finished. total time: 240.857s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot reboot
rebooting...
finished. total time: 0.000s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.251s]
finished. total time: 6.266s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.125s]
finished. total time: 0.141s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot reboot
rebooting...
finished. total time: 0.000s
C:\Users\Syed Mobile\Desktop\marshall london>
sorry ,
I did it wrong
i flashed it with lower version R313
let me download new version and post result here......
Hello,
flashed with latest version also , but same
restarting on logo...........
Code:
C:\Users\Syed Mobile\Downloads>fastboot flash persist KB15_3_R412_170324_persist
.img
target reported max download size of 268435456 bytes
sending 'persist' (4708 KB)...
OKAY [ 0.156s]
writing 'persist'...
OKAY [ 0.109s]
finished. total time: 0.266s
C:\Users\Syed Mobile\Downloads>fastboot flash splash KB15_3_R412_170324_splash.i
mg
target reported max download size of 268435456 bytes
sending 'splash' (2700 KB)...
OKAY [ 0.078s]
writing 'splash'...
OKAY [ 0.391s]
finished. total time: 0.469s
C:\Users\Syed Mobile\Downloads>fastboot flash boot KB15_3_R412_170324_boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24940 KB)...
OKAY [ 0.797s]
writing 'boot'...
OKAY [ 2.031s]
finished. total time: 2.829s
C:\Users\Syed Mobile\Downloads>fastboot flash recovery KB15_3_R412_170324_recove
ry.img
target reported max download size of 268435456 bytes
sending 'recovery' (25636 KB)...
OKAY [ 0.984s]
writing 'recovery'...
OKAY [ 3.033s]
finished. total time: 4.705s
C:\Users\Syed Mobile\Downloads>
Code:
C:\Users\Syed Mobile\Downloads>fastboot flash system KB15_3_R412_170324_system.i
mg
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.486s]
sending sparse 'system' (259594 KB)...
OKAY [ 15.912s]
writing 'system'...
OKAY [ 18.228s]
sending sparse 'system' (257537 KB)...
OKAY [ 16.395s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262070 KB)...
OKAY [ 14.659s]
writing 'system'...
OKAY [ 20.581s]
sending sparse 'system' (253004 KB)...
OKAY [ 13.408s]
writing 'system'...
OKAY [ 19.851s]
sending sparse 'system' (257537 KB)...
OKAY [ 13.347s]
writing 'system'...
OKAY [ 20.599s]
sending sparse 'system' (258041 KB)...
OKAY [ 13.892s]
writing 'system'...
OKAY [ 19.853s]
sending sparse 'system' (250899 KB)...
OKAY [ 13.236s]
writing 'system'...
OKAY [ 20.315s]
finished. total time: 242.416s
C:\Users\Syed Mobile\Downloads>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Users\Syed Mobile\Downloads>
syed tuqeer said:
Hello,
flashed with latest version also , but same
restarting on logo...........
Click to expand...
Click to collapse
Try flashing the earliest version first and see if you can take updates within the phone itself. You may need to shorten filenames and ensure that none of the files you flash have spaces in the filename.
..
Related
Honor 8 impossible to flash system.img
Hey guys having some problem flashing a stock system.img to my phone. I try to get back to Mashmellow to get my phone back to stock. Currently its rooted and unlocked. I downloaded the following zip: Honor 8_Firmware_FRD-L09_Android 6.0_EMUI 4.1_C432B131_Western Europe.zip I unzipped it and extracted all Images from the UPDATE.APP file. Flashing cust.img, recovery.img, and recovery2.img is no problem. Problem is when flashing system.img It always says Code: [[email protected] honor8]# fastboot flash system SYSTEM.img target reported max download size of 471859200 bytes sending sparse 'system' 1/6 (435393 KB)... OKAY [ 11.022s] writing 'system' 1/6... FAILED (remote: sparse flash write failure) finished. total time: 11.056s [[email protected] honor8]# [[email protected] honor8]# fastboot --version fastboot version 7.1.1_r13 Phone is unlocked FRP is unlocked Flashing recovery works: Code: [[email protected] Downloads]# fastboot flash recovery twrp-3.1.0-0-frd.img target reported max download size of 471859200 bytes sending 'recovery' (24884 KB)... OKAY [ 0.630s] writing 'recovery'... OKAY [ 0.327s] finished. total time: 0.957s TWRP tells me, that it cannot mount system. When restoring a backup with TWRP it works: it writes the system to the flash. After restore I can reboot into Android again. Unfortunately I tried to installe the latest OTA (B380) which bricked my camera for some reason and makes the system itself kinda buggy. Does anyone have an idea, how I get out of this situation? Current Version: FRD-L09C432B360
It won't work this way. I wasted so much time trying. You have to use the rollback procedure to get your phone working again. Search the forum for it, it's been documented pretty well. Good luck
Never seen a brick this hard to solve...
So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario: *Can't access ADB anymore, doesn't show up in devices *Can access fastboot, however: I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files. *eRecovery tells me "Getting Package Info Failed" *Don't have access to TWRP anymore *Have tried multiple firmwares using the dload method, either they can't install or simply do nothing *I've tried Huawei Multi Tool and got the following output: Code: RNV0216B29003646 fastboot target reported max download size of 471859200 bytes sending 'boot' (15440 KB)... OKAY [ 0.332s] writing 'boot'... OKAY [ 0.370s] finished. total time: 0.710s target reported max download size of 471859200 bytes sending 'cust' (252389 KB)... OKAY [ 5.407s] writing 'cust'... FAILED (remote: partition error) finished. total time: 5.418s target reported max download size of 471859200 bytes sending 'recovery' (36976 KB)... OKAY [ 0.791s] writing 'recovery'... OKAY [ 0.879s] finished. total time: 1.675s target reported max download size of 471859200 bytes sending sparse 'system' 1/6 (424496 KB)... OKAY [ 9.894s] writing 'system' 1/6... FAILED (remote: sparse flash write failure) finished. total time: 9.945s *I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed. I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
This is really bad. The solution to your first problem was to simply remove encryption by formatting data.
Jdelacrix said: So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario: *Can't access ADB anymore, doesn't show up in devices *Can access fastboot, however: I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files. *eRecovery tells me "Getting Package Info Failed" *Don't have access to TWRP anymore *Have tried multiple firmwares using the dload method, either they can't install or simply do nothing *I've tried Huawei Multi Tool and got the following output: Code: RNV0216B29003646 fastboot target reported max download size of 471859200 bytes sending 'boot' (15440 KB)... OKAY [ 0.332s] writing 'boot'... OKAY [ 0.370s] finished. total time: 0.710s target reported max download size of 471859200 bytes sending 'cust' (252389 KB)... OKAY [ 5.407s] writing 'cust'... FAILED (remote: partition error) finished. total time: 5.418s target reported max download size of 471859200 bytes sending 'recovery' (36976 KB)... OKAY [ 0.791s] writing 'recovery'... OKAY [ 0.879s] finished. total time: 1.675s target reported max download size of 471859200 bytes sending sparse 'system' 1/6 (424496 KB)... OKAY [ 9.894s] writing 'system' 1/6... FAILED (remote: sparse flash write failure) finished. total time: 9.945s *I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed. I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it. Click to expand... Click to collapse I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered. If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package. If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible let me know if that gets you started.
sonicscrewup said: I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered. If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package. If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible let me know if that gets you started. Click to expand... Click to collapse i was in a similar situation and this method worked! connect the phone to pc in switched off condition, press power+vol down and get into fastboot and then oem unlock, install twrp and tried to installed the zips.. worked and phone booted!!
Stuck in bootloader nothing loads
Update: Of course... bad abd files quick update and everything went smooth. Tried to root with magisk and got stuck in bootloop so I tried to install factory image and just be done with it and now its stuck in bootloader. trying to boot recovery just reboots into bootloader trying to use deuces script doesnt work and the flash-all script just fails its bootloader .0059 and its in boot-slot B and wont change to slot a. Havent had the phone long so im desperate to try and fix it if at all possible. example of the flash-all Code: < waiting for any device > target didn't report max-download-size sending 'bootloader' (38728 KB)... FAILED (remote: Uploaded data exceeds max-download-size) finished. total time: -0.000s rebooting into bootloader... OKAY [ 0.002s] finished. total time: 0.003s target didn't report max-download-size sending 'radio' (60428 KB)... FAILED (remote: Uploaded data exceeds max-download-size) finished. total time: 0.003s rebooting into bootloader... OKAY [ 0.002s] finished. total time: 0.002s extracting android-info.txt (0 MB) to RAM... extracting boot.img (32 MB) to disk... took 0.153s target didn't report max-download-size error: Failed to identify current slot Press any key to exit... tried flashing twrp and got Code: C:\Users\coolp\Downloads>fastboot flash recovery twrp-3.2.1-0-walleye.img target reported max download size of 536870912 bytes sending 'recovery' (32768 KB)... FAILED (remote: Uploaded data exceeds max-download-size) finished. total time: 0.000s
Coolpente said: Update: Of course... bad abd files quick update and everything went smooth. Tried to root with magisk and got stuck in bootloop so I tried to install factory image and just be done with it and now its stuck in bootloader. trying to boot recovery just reboots into bootloader trying to use deuces script doesnt work and the flash-all script just fails its bootloader .0059 and its in boot-slot B and wont change to slot a. Havent had the phone long so im desperate to try and fix it if at all possible. example of the flash-all Code: < waiting for any device > target didn't report max-download-size sending 'bootloader' (38728 KB)... FAILED (remote: Uploaded data exceeds max-download-size) finished. total time: -0.000s rebooting into bootloader... OKAY [ 0.002s] finished. total time: 0.003s target didn't report max-download-size sending 'radio' (60428 KB)... FAILED (remote: Uploaded data exceeds max-download-size) finished. total time: 0.003s rebooting into bootloader... OKAY [ 0.002s] finished. total time: 0.002s extracting android-info.txt (0 MB) to RAM... extracting boot.img (32 MB) to disk... took 0.153s target didn't report max-download-size error: Failed to identify current slot Press any key to exit... tried flashing twrp and got Code: C:\Users\coolp\Downloads>fastboot flash recovery twrp-3.2.1-0-walleye.img target reported max download size of 536870912 bytes sending 'recovery' (32768 KB)... FAILED (remote: Uploaded data exceeds max-download-size) finished. total time: 0.000s Click to expand... Click to collapse Try new platform tools. Then try different computer and usb cable. Preferably the usb c to c cable.
enzyne said: Try new platform tools. Then try different computer and usb cable. Preferably the usb c to c cable. Click to expand... Click to collapse I did the new platform tools and it worked. I was not capable of using another cable since I dont have an adapter for the c to c.
How odd. Latest platform tools from google. Two computers. Two pixel2 phones. Yes, TWO phones! Four cables. All the exact same result. The deuces script wiped twrp and I'm beginning to believe it installed a borked bootloader: fastboot flash recovery twrp-3.2.1-0-walleye.img target reported max download size of 536870912 bytes sending 'recovery' (32768 KB)... FAILED (remote: Uploaded data exceeds max-download-size) finished. total time: 0.000s fastboot --version fastboot version 0.0.1-4500957 Installed as /usr/bin/fastboot
dattaway said: How odd. Latest platform tools from google. Two computers. Two pixel2 phones. Yes, TWO phones! Four cables. All the exact same result. The deuces script wiped twrp and I'm beginning to believe it installed a borked bootloader: fastboot flash recovery twrp-3.2.1-0-walleye.img target reported max download size of 536870912 bytes sending 'recovery' (32768 KB)... FAILED (remote: Uploaded data exceeds max-download-size) finished. total time: 0.000s fastboot --version fastboot version 0.0.1-4500957 Installed as /usr/bin/fastboot Click to expand... Click to collapse Are you flashing the proper factory image? Have you tried re downloading?
enzyne said: Are you flashing the proper factory image? Have you tried re downloading? Click to expand... Click to collapse How do I tell which is the proper factory image? There are 15 listed for the Pixel 2. Since I bought my two Pixel phones directly from Google, there appears to be 5 that might work, so I tried each one with identical results. SHA-256 Checksums match.
dattaway said: How do I tell which is the proper factory image? There are 15 listed for the Pixel 2. Since I bought my two Pixel phones directly from Google, there appears to be 5 that might work, so I tried each one with identical results. SHA-256 Checksums match. Click to expand... Click to collapse I just wanted to make sure there wasn't any data corruption. The most recent one which was .19 should do the trick if that's not working and you've tried everything else it may be time to do an RMA.
Sorry to piggyback on a thread, but I seem to be having the same problem (I think). All I did was update Magisk to 16.0, then reboot my phone now I'm stuck in bootloader, none of the options do anything except make the screen go black for a minute then go back to the bootloader screen (assuming the bootloader screen is the one with the Android laying on it's back). Is the main fix to re-flash a google factory image? OP said something about bad abd files, but I haven't even tried to push anything with adb since I rooted my phone last month. Or should i use the fix bootloop script in the other thread?
Rookx said: Sorry to piggyback on a thread, but I seem to be having the same problem (I think). All I did was update Magisk to 16.0, then reboot my phone now I'm stuck in bootloader, none of the options do anything except make the screen go black for a minute then go back to the bootloader screen (assuming the bootloader screen is the one with the Android laying on it's back). Is the main fix to re-flash a google factory image? OP said something about bad abd files, but I haven't even tried to push anything with adb since I rooted my phone last month. Or should i use the fix bootloop script in the other thread? Click to expand... Click to collapse What your talking about is the android stock recovery not the bootloader.
Bricked Honor 8 [SOLVED]
Hello, it seems i have bricked my phone. The model is FRD-L09C432. I've been trying to restore it to stock but to no avail. I've tried flashing various build numbers via the Unbrick funtion of Huawei Multi Tool, but it always gave an error when it was flashing cust.img and system.img, reporting that I'm trying to flash the wrong image. I've also tried the 2-step method in which you load a rollback package in the sdcard and then try to flash the old firmware, but that also doesn't work as when I am in the first step of the progress, trying to install the rollback package, the installer stops immediately at 5% reporting that the installation failed as the update package does not exist. I wonder if this is an error with the SD card - maybe the phone can't read it properly. What should the SD card be formatted to? Right now, it's a single FAT partition. Any ideas or tips are welcome. Edit: when I try to unbrick with HMT i always get something like this: Code: 13:43:35: Unbricking started. Your computer may freezes during the process. 13:43:35: flash boot "C:\Users\svart\Desktop\unbrick\boot.img" 13:43:37: The Boot image is flashing successfully 13:43:37: flash system "C:\Users\svart\Desktop\unbrick\system.img" 13:45:28: target reported max download size of 471859200 bytes sending sparse 'system' 1/6 (435393 KB)... OKAY [ 16.234s] writing 'system' 1/6... FAILED (remote: sparse flash write failure) finished. total time: 16.281s 13:45:28: Error#1 13:45:28: flash cust "C:\Users\svart\Desktop\unbrick\cust.img" 13:45:45: Error! You are trying to flash the wrong image! 13:45:45: flash recovery "C:\Users\svart\Desktop\unbrick\recovery.img" 13:45:48: The Recovery image is flashing successfully 13:45:48: flash userdata "C:\Users\svart\Desktop\unbrick\userdata.img" 13:45:55: target reported max download size of 471859200 bytes sending 'userdata' (143361 KB)... OKAY [ 3.468s] writing 'userdata'... (bootloader) success to erase cryypt info in oeminfo OKAY [ 2.000s] finished. total time: 5.469s 13:45:56: Error#1 13:45:56: Completed 13:45:56: Something went wrong (((
I solved it. There was a problem with the SD card that's why it wasn't doing the rollback I think. I found the correct rom (B360 from here) which I flashed with HMT.
[Guide] How to flash stock ROM on Redmi Go
If you're reading this, you must've messed up with your device or you don't want to use custom ROMs anymore and want to revert back to stock ROM. Going back to stock ROM is not easy on Redmi Go as Xiaomi is not providing the right ROM files. The one (Version: V10.2.6.0.OCLMIXM) that is available on their ROM download site is not flashable on Mi Flash Tool or via fastboot. It will give you an error. But, there is a way! Follow the steps below and you can surely get back to stock ROM. (At least it worked for me every time) CAUTION! Please proceed at your own risk. You are solely responsible for what you're doing. I will not be responsible for any kind of damage to your device. Requirements - Unlocked Bootloader - Xiaomi USB drivers installed on your PC - PC/TWRP - microSD Card - Minimal ADB & Fastboot (If using PC) - V10.2.6.0.OCLMIXM ROM zip file (Download here -V10.2.7.0.OCLMIXM (Download here At first, unzip the V10.2.6.0.OCLMIXM zip file. You will find a folder named images. Open it and look for "recovery.img". Copy it to a safe place (you will need it later). Then, copy the V10.2.7.0.OCLMIXM zip file to your sd card. Steps, if you're using PC 1. Install Minimal ADB & Fastboot (Download here) 2. Copy the "recovery.img" file that you extracted earlier, to the directory where your "Minimal Adb & Fastboot" is installed. 3. Run "cmd-here" and type fastboot flash recovery recovery.img 4. Turn on recovery mode on your device by pressing and holding Volume+ and power button together. 5. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu. 6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file. 7. Select "Yes" 8. Reboot system. Steps, if you're using TWRP 1. Copy the "recovery.img" file that you extracted earlier, to your SD Card. 2. Boot TWRP 3. Select Install 4. Select Install Image 5. Locate the "recovery.img" file in your SD Card and install it. 6. Go back to main menu and reboot into recovery. 7. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu. 6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file. 7. Select "Yes" 8. Reboot system. Your device should now be running clean stock ROM and recovery. Don't forget to hit Thanks Button if you found this useful.
As I am writing here, Redmi Go doesn't yet have any official, nor nonofficial custom recovery that doesn't have major bugs. The easiest way to root Redmi Go, as I found, is to do it without custom recovery with Magisk, with adb and fastboot. The problem I personally faced was that I installed the OTA updates, and in such case the stock rom's boot.img does not match with the new updated/altered rom that is installed through OTA update. So before patching stock boot.img with magisk, and flashing the patched boot.img, which is based on that stock rom, you have to have stock rom, instead of OTA updated one. Before doing you probably have to also install xiaomi usb driver, and of course you have to unlock redmi go bootloader (as instructed here in xda forum in this redmi go section , - simply doing it by going to fastboot mode and typing a few words to cmd window through adb - meaning that can ignore any official long time-consuiming instructions that are actually obselete or doesn't work without possible bugs on the way for this particular device, as I tried). Here are official stock roms: https://en.miui.com/download-365.html or search "go" here https://en.miui.com/download.html This is the procedure (from official Magisk installation guide, source here https://topjohnwu.github.io/Magisk/install.html ): Boot Image Patching This is the “cool” way to install Magisk on your device. Either your device does not have proper custom recoveries, your device is using the A/B partition scheme and you don’t want to mix recovery and boot images together, or you have other concerns (e.g. OTA Installation), you should use this method instead. In order to use this method, you are required to obtain a copy of the stock boot image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, someone on the Internet might share it somewhere. The following instructions will guide you through the process after you have the copy of boot image. Copy the boot image to your device Download and install the latest Magisk Manager Press Install → Install → Select and Patch a File, and select your stock boot image file Magisk Manager will install Magisk to your boot image, and store it in [Internal Storage]/Download/magisk_patched.img Copy the patched boot image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB: adb pull /sdcard/Download/magisk_patched.img Flash the patched boot image to your device and reboot. Here is the command if using fastboot on most devices: fastboot flash boot /path/to/magisk_patched.img ----------------- Here's some slightly longer guide: https://c.mi.com/thread-1444861-1-0.html Here is if you want to know how to easily restore stock rom (like in case of flashing boot.img that doesn't match with the rest of the rom like I did getting stuck at booting up, or you simply don't have stock rom currently for whatever reason, like having already updated through OTA). https://www.foldertips.com/en/unbrick-all-xiaomi-snapdragon/ And after installing XiaoMiFlash and before flashing, have to reboot computer as well which was not said in the above instruction. I would have made separate thread on how to root Redmi Go, here in this forum section, as it is obviously most secure way to rooting Redmi Go (secure, as for using official/legit tools instead of potentially installing something shady somebody has altered in ways of unfavorable to you, as well as secure that it is not really possible to hard brick it even if not following instructions properly) but I don't have enough posts in this forum to make thread here in this section so whatever.
Actually tried an easier way: Just download the tgz file from mi website tiare_global_images_V10.2.6.0.OCLMIXM_20190218.0000.00_8.1_66cc42a821.tgz If you are on linux it is easy tar xvf filename Code: tiare_global_images_V10.2.6.0.OCLMIXM_8.1$ ls -R .: flash_all.bat flash_all_except_data_storage.sh flash_all_lock.sh flash_gen_crc_list.py flash_gen_resparsecount md5sum.xml flash_all_except_data_storage.bat flash_all_lock.bat flash_all.sh flash_gen_md5_list.py images misc.txt ./images: adspso.bin crclist.txt gpt_both0.bin NON-HLOS.bin prog_emmc_firehose_8917_lite.mbn sbl1.mbn userdata.img boot.img devcfg.mbn gpt_main0.bin partition.xml rawprogram0_BLANK.xml sparsecrclist.txt vendor.img cache.img elf_path.txt keymaster64.mbn patch0.xml rawprogram0.xml splash.img cmnlib_30.mbn emmc_appsboot.mbn keymaster.mbn persist.img recovery.img system.img cmnlib64_30.mbn gpt_backup0.bin lksecapp.mbn prog_emmc_firehose_8917_ddr.mbn rpm.mbn tz.mbn $ chmod +x flash_all_lock.sh $ ./flash_all_lock.sh tiare Fastboot Tool Ver 3.0 product: tiare target reported max download size of 535822336 bytes sending 'partition' (33 KB)... OKAY [ 0.004s] writing 'partition'... FAILED (remote: Critical partition flashing is not allowed) finished. total time: 0.010s target reported max download size of 535822336 bytes sending 'crclist' (0 KB)... OKAY [ 0.002s] writing 'crclist'... OKAY [ 0.006s] finished. total time: 0.009s target reported max download size of 535822336 bytes sending 'sparsecrclist' (0 KB)... OKAY [ 0.002s] writing 'sparsecrclist'... OKAY [ 0.006s] finished. total time: 0.008s target reported max download size of 535822336 bytes sending 'tz' (1503 KB)... OKAY [ 0.055s] writing 'tz'... FAILED (remote: Critical partition flashing is not allowed) finished. total time: 0.062s target reported max download size of 535822336 bytes sending 'sbl1' (342 KB)... OKAY [ 0.014s] writing 'sbl1'... FAILED (remote: Critical partition flashing is not allowed) finished. total time: 0.020s target reported max download size of 535822336 bytes sending 'rpm' (180 KB)... OKAY [ 0.009s] writing 'rpm'... FAILED (remote: Critical partition flashing is not allowed) finished. total time: 0.015s target reported max download size of 535822336 bytes sending 'aboot' (559 KB)... OKAY [ 0.024s] writing 'aboot'... FAILED (remote: Critical partition flashing is not allowed) finished. total time: 0.030s target reported max download size of 535822336 bytes sending 'tzbak' (1503 KB)... OKAY [ 0.056s] writing 'tzbak'... OKAY [ 0.064s] finished. total time: 0.120s target reported max download size of 535822336 bytes sending 'sbl1bak' (342 KB)... OKAY [ 0.015s] writing 'sbl1bak'... OKAY [ 0.024s] finished. total time: 0.040s target reported max download size of 535822336 bytes sending 'rpmbak' (180 KB)... OKAY [ 0.009s] writing 'rpmbak'... OKAY [ 0.021s] finished. total time: 0.030s target reported max download size of 535822336 bytes sending 'abootbak' (559 KB)... OKAY [ 0.023s] writing 'abootbak'... OKAY [ 0.034s] finished. total time: 0.057s target reported max download size of 535822336 bytes sending 'devcfg' (60 KB)... OKAY [ 0.004s] writing 'devcfg'... OKAY [ 0.014s] finished. total time: 0.018s target reported max download size of 535822336 bytes sending 'cmnlib' (208 KB)... OKAY [ 0.010s] writing 'cmnlib'... OKAY [ 0.022s] finished. total time: 0.032s target reported max download size of 535822336 bytes sending 'cmnlib64' (262 KB)... OKAY [ 0.012s] writing 'cmnlib64'... OKAY [ 0.023s] finished. total time: 0.035s target reported max download size of 535822336 bytes sending 'keymaster' (265 KB)... OKAY [ 0.012s] writing 'keymaster'... OKAY [ 0.023s] finished. total time: 0.035s target reported max download size of 535822336 bytes sending 'devcfgbak' (60 KB)... OKAY [ 0.004s] writing 'devcfgbak'... OKAY [ 0.014s] finished. total time: 0.018s target reported max download size of 535822336 bytes sending 'cmnlibbak' (208 KB)... OKAY [ 0.010s] writing 'cmnlibbak'... OKAY [ 0.023s] finished. total time: 0.033s target reported max download size of 535822336 bytes sending 'cmnlib64bak' (262 KB)... OKAY [ 0.013s] writing 'cmnlib64bak'... OKAY [ 0.023s] finished. total time: 0.036s target reported max download size of 535822336 bytes sending 'keymasterbak' (265 KB)... OKAY [ 0.012s] writing 'keymasterbak'... OKAY [ 0.025s] finished. total time: 0.038s target reported max download size of 535822336 bytes sending 'dsp' (16384 KB)... OKAY [ 0.584s] writing 'dsp'... OKAY [ 0.550s] finished. total time: 1.134s erasing 'boot'... OKAY [ 0.016s] finished. total time: 0.016s erasing 'apdp'... OKAY [ 0.013s] finished. total time: 0.013s erasing 'msadp'... OKAY [ 0.013s] finished. total time: 0.013s target reported max download size of 535822336 bytes sending 'modem' (86016 KB)... OKAY [ 3.050s] writing 'modem'... OKAY [ 3.022s] finished. total time: 6.072s target reported max download size of 535822336 bytes erasing 'system'... OKAY [ 0.160s] sending sparse 'system' (502636 KB)... OKAY [ 19.755s] writing 'system'... OKAY [ 17.618s] sending sparse 'system' (523260 KB)... OKAY [ 20.561s] writing 'system'... OKAY [ 18.747s] sending sparse 'system' (115276 KB)... OKAY [ 4.530s] writing 'system'... OKAY [ 4.084s] finished. total time: 85.454s target reported max download size of 535822336 bytes erasing 'cache'... OKAY [ 0.011s] sending 'cache' (140 KB)... OKAY [ 0.008s] writing 'cache'... OKAY [ 0.015s] finished. total time: 0.033s target reported max download size of 535822336 bytes sending 'userdata' (192 KB)... OKAY [ 0.009s] writing 'userdata'... OKAY [ 0.023s] finished. total time: 0.033s target reported max download size of 535822336 bytes sending 'recovery' (20207 KB)... OKAY [ 0.717s] writing 'recovery'... OKAY [ 0.670s] finished. total time: 1.387s target reported max download size of 535822336 bytes sending 'boot' (15547 KB)... OKAY [ 0.554s] writing 'boot'... OKAY [ 0.581s] finished. total time: 1.135s target reported max download size of 535822336 bytes sending 'splash' (10802 KB)... OKAY [ 0.380s] writing 'splash'... OKAY [ 0.366s] finished. total time: 0.747s target reported max download size of 535822336 bytes sending 'vendor' (278000 KB)... OKAY [ 9.794s] writing 'vendor'... OKAY [ 9.957s] finished. total time: 19.751s ... OKAY [ 0.057s] finished. total time: 0.057s rebooting... finished. total time: 0.061s System fresh as NEW.
Note that there is a newer version: 10.2.12
Sadly the phone even AOSP with just whatsapp and email becomes very slow. Flashed stock return to retailer!
hello. weareinwarwithbugs said: As I am writing here, Redmi Go doesn't yet have any official, nor nonofficial custom recovery that doesn't have major bugs. The easiest way to root Redmi Go, as I found, is to do it without custom recovery with Magisk, with adb and fastboot. The problem I personally faced was that I installed the OTA updates, and in such case the stock rom's boot.img does not match with the new updated/altered rom that is installed through OTA update. So before patching stock boot.img with magisk, and flashing the patched boot.img, which is based on that stock rom, you have to have stock rom, instead of OTA updated one. Before doing you probably have to also install xiaomi usb driver, and of course you have to unlock redmi go bootloader (as instructed here in xda forum in this redmi go section , - simply doing it by going to fastboot mode and typing a few words to cmd window through adb - meaning that can ignore any official long time-consuiming instructions that are actually obselete or doesn't work without possible bugs on the way for this particular device, as I tried). Here are official stock roms: https://en.miui.com/download-365.html or search "go" here https://en.miui.com/download.html This is the procedure (from official Magisk installation guide, source here https://topjohnwu.github.io/Magisk/install.html ): Boot Image Patching This is the “cool” way to install Magisk on your device. Either your device does not have proper custom recoveries, your device is using the A/B partition scheme and you don’t want to mix recovery and boot images together, or you have other concerns (e.g. OTA Installation), you should use this method instead. In order to use this method, you are required to obtain a copy of the stock boot image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, someone on the Internet might share it somewhere. The following instructions will guide you through the process after you have the copy of boot image. Copy the boot image to your device Download and install the latest Magisk Manager Press Install → Install → Select and Patch a File, and select your stock boot image file Magisk Manager will install Magisk to your boot image, and store it in [Internal Storage]/Download/magisk_patched.img Copy the patched boot image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB: adb pull /sdcard/Download/magisk_patched.img Flash the patched boot image to your device and reboot. Here is the command if using fastboot on most devices: fastboot flash boot /path/to/magisk_patched.img ----------------- Here's some slightly longer guide: https://c.mi.com/thread-1444861-1-0.html Here is if you want to know how to easily restore stock rom (like in case of flashing boot.img that doesn't match with the rest of the rom like I did getting stuck at booting up, or you simply don't have stock rom currently for whatever reason, like having already updated through OTA). https://www.foldertips.com/en/unbrick-all-xiaomi-snapdragon/ And after installing XiaoMiFlash and before flashing, have to reboot computer as well which was not said in the above instruction. I would have made separate thread on how to root Redmi Go, here in this forum section, as it is obviously most secure way to rooting Redmi Go (secure, as for using official/legit tools instead of potentially installing something shady somebody has altered in ways of unfavorable to you, as well as secure that it is not really possible to hard brick it even if not following instructions properly) but I don't have enough posts in this forum to make thread here in this section so whatever. Click to expand... Click to collapse Hi, I have a doubt. My phone has the update of May 1, so I decided to do it root. Now unlock the bootloader, install twrp and flash magisk. the apps recognize me as root and everything is normal, so I did the right thing? or am I at risk of a problem? sorry for the question, what happens to understand your comment I had to translate in google and really only understood 80%, do not finish understanding why you had problems with your computer. could you help me? I already worry
a rdz said: Hi, I have a doubt. My phone has the update of May 1, so I decided to do it root. Now unlock the bootloader, install twrp and flash magisk. the apps recognize me as root and everything is normal, so I did the right thing? or am I at risk of a problem? sorry for the question, what happens to understand your comment I had to translate in google and really only understood 80%, do not finish understanding why you had problems with your computer. could you help me? I already worry Click to expand... Click to collapse I didn't use twrp at all. I used Miflash instead of twrp as I told above, in order to restore previous state of the device. If you did update, as one of the ways I see then, is to replace it with stock rom from which you are going to take the boot image from, to patch with magisk. Do no update. Root first. I have not updated so I don't know how the updating after rooting is going to work. No twrp needed if you just want root. ---------- Post added at 10:58 AM ---------- Previous post was at 10:07 AM ---------- There's slightly different address now: http://c.mi.com/oc/miuidownload/index. Going mi.com or https://en.miui.com/ and clicking downloads if doesn't get there.
RafiAhmed said: If you're reading this, you must've messed up with your device or you don't want to use custom ROMs anymore and want to revert back to stock ROM. Going back to stock ROM is not easy on Redmi Go as Xiaomi is not providing the right ROM files. The one (Version: V10.2.6.0.OCLMIXM) that is available on their ROM download site is not flashable on Mi Flash Tool or via fastboot. It will give you an error. But, there is a way! Follow the steps below and you can surely get back to stock ROM. (At least it worked for me every time) CAUTION! Please proceed at your own risk. You are solely responsible for what you're doing. I will not be responsible for any kind of damage to your device. Requirements - Unlocked Bootloader - Xiaomi USB drivers installed on your PC - PC/TWRP - microSD Card - Minimal ADB & Fastboot (If using PC) - V10.2.6.0.OCLMIXM ROM zip file (Download here -V10.2.7.0.OCLMIXM (Download here At first, unzip the V10.2.6.0.OCLMIXM zip file. You will find a folder named images. Open it and look for "recovery.img". Copy it to a safe place (you will need it later). Then, copy the V10.2.7.0.OCLMIXM zip file to your sd card. Steps, if you're using PC 1. Install Minimal ADB & Fastboot (Download here) 2. Copy the "recovery.img" file that you extracted earlier, to the directory where your "Minimal Adb & Fastboot" is installed. 3. Run "cmd-here" and type fastboot flash recovery recovery.img 4. Turn on recovery mode on your device by pressing and holding Volume+ and power button together. 5. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu. 6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file. 7. Select "Yes" 8. Reboot system. Steps, if you're using TWRP 1. Copy the "recovery.img" file that you extracted earlier, to your SD Card. 2. Boot TWRP 3. Select Install 4. Select Install Image 5. Locate the "recovery.img" file in your SD Card and install it. 6. Go back to main menu and reboot into recovery. 7. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu. 6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file. 7. Select "Yes" 8. Reboot system. Your device should now be running clean stock ROM and recovery. Don't forget to hit Thanks Button if you found this useful. Click to expand... Click to collapse Thank you, this really saved me. A couple of days ago the hotspot stopped working properly after a security update (September 1, 2019). My computer would connect to my phone but it would say "No Internet, Secured". USB tethering also didn't work. I tried restoring to factory defaults, didn't help. So I figured I need to reflash it. The app used to unlock the bootloader didn't work, had to do it manually. The app used for flashing also didn't work, tried a manual approach - almost bricked the phone. Then I found this and it totally worked, thank you. PS: Now after the reflash it shows there's an update available with the size of 183,7MB. How safe is it to update this, since the original firmware(V10.2.9.0.ocleuxm) got screwed up by a security update? edit: I have installed both updates 10.2.13.0.oclmixm and 10.2.14.0.oclmixm. It's working great. And locked the bootloader.
Request for miui custom ROM for Redmi go Can anyone built new miui custom ROM port for e Redmi go:good:
Like it, thank you
matador84 said: Note that there is a newer version: 10.2.12 ? V10.2.13.0.OCLMIXM - https://mirom.ezbox.idv.tw/en/phone/tiare/ Click to expand... Click to collapse
fmcgorenc said: Thank you, this really saved me. A couple of days ago the hotspot stopped working properly after a security update (September 1, 2019). My computer would connect to my phone but it would say "No Internet, Secured". USB tethering also didn't work. I tried restoring to factory defaults, didn't help. So I figured I need to reflash it. The app used to unlock the bootloader didn't work, had to do it manually. The app used for flashing also didn't work, tried a manual approach - almost bricked the phone. Then I found this and it totally worked, thank you. PS: Now after the reflash it shows there's an update available with the size of 183,7MB. How safe is it to update this, since the original firmware(V10.2.9.0.ocleuxm) got screwed up by a security update? edit: I have installed both updates 10.2.13.0.oclmixm and 10.2.14.0.oclmixm. It's working great. And locked the bootloader. Click to expand... Click to collapse Glad to know that it helped you. And yes, you can update every time after restoring by using this method. It actually takes you to 100% stock condition.
JonnyTech said: matador84 said: Note that there is a newer version: 10.2.12 ? V10.2.13.0.OCLMIXM - https://mirom.ezbox.idv.tw/en/phone/tiare/ Click to expand... Click to collapse The one I mentioned is targeted to take the phone back to the state it was in, after you purchased it. Click to expand... Click to collapse
Failed to installing while applying update from sd card it's failing to install. Anything can i do? plz help if there is any idea
How out of date this guide really is?
dustojnikhummer said: How out of date this guide really is? Click to expand... Click to collapse It still works.
Hakhim said: while applying update from sd card it's failing to install. Anything can i do? plz help if there is any idea Click to expand... Click to collapse I'm sorry, I might've been busy or didn't notice when you posted this. Did you manage to fix it?
Xiaomi Firmware Updater The ultimate script that provides firmware packages for Xiaomi devices. xiaomifirmwareupdater.com Guys, download the Firmware from here. And if you have TWRP installed, just flash this. If TWRP is not installed, try using fastboot and boot to TWRP
Sid160706 said: Xiaomi Firmware Updater The ultimate script that provides firmware packages for Xiaomi devices. xiaomifirmwareupdater.com Guys, download the Firmware from here. And if you have TWRP installed, just flash this. If TWRP is not installed, try using fastboot and boot to TWRP Click to expand... Click to collapse this worked perfectly. i cleared system, dalvik, cache, data in twrp, then flashed latest V10.2.25.0.OCLMIXM, phone rebooted and showed encryption unsuccessful, i clicked on erase everything then it encryted and booted successfully.