Related
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: HTC Droid DNA, One XL, One S, EVO 4G LTE, EVO 3D CDMA and GSM, Amaze, Vivid/Holiday, EVO 4G, EVO Shift, Nexus 4, Nexus 10, Nexus 7, Samsung Google Galaxy Nexus (GSM & CDMA), Nexus S/Nexus S 4G & LG Optimus
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Credits for HTC Droid DNA Testing:
Special Thanks for Testing and Screenshots: RLKirk
Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch.!
Thanks to SDX
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into kernel /sbin, etc).
Custom Recovery
Supports both CWM and TWRP recovery image flashing!
YouTube Video
https://www.youtube.com/watch?v=W7cNoMF4T1I&feature=youtu.be
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit more technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No. Use Kernel Manager!
Screenshots:
{
"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"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
HTC Unlock - User Guides for Flash Image GUI!!
HTC Unlock - Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using Official HTC method
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including Wifi!
HTC Unlock - Users Guide for flashing ONLY a Kernel (zip file):
1) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
2) Download kernel zip file to /sdcard.
3) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
3) Flash Image GUI will validate the kernel zip file is contains the minimum required files
4) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
5) Reboot
HTC Unlock - Users Guide for flashing boot.img with separate modules.zip:
1) Using Flash Image GUI, flash the boot.img file
2) Reboot to the custom recovery
3) From the custom recovery, flash the modules.zip file
4) Reboot
Basic Troubleshooting:
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel (or packaged ramdisk in the kernel) is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.
Glad you finally got the thread started. Now if anyone else is having bugs or issues I didn't have then the man can look at them haha
Does this only work on the listed devices or has only been tested on listed devices coming from an HTC incredible 4G owner?
Sent from my ADR6410LVW using xda app-developers app
RLKirk said:
Glad you finally got the thread started. Now if anyone else is having bugs or issues I didn't have then the man can look at them haha
Click to expand...
Click to collapse
Hope there aren't any issues, but if there are, please post up here and provide as much details as possible including screenshots!
Thanks for the support!
prairiedogn said:
Does this only work on the listed devices or has only been tested on listed devices coming from an HTC incredible 4G owner?
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Due to the unique hardware architecture and security structure of each HTC device, I prefer to confirm each and every function operates properly before officially adding support for a device.
I think for the Incredible S, during 6 hrs of testing, we were able to positively confirm HTC did not unlock the boot partition while booted in Android mode and subsequently prevented Flash Image GUI from properly operating.
If you're knowledgeable with ADB and the custom recovery, plus have some time to work on testing, please send me a PM. Thanks for the support and inquiry!
Thanks a bunch for the DNA support, you rock joey. Downloading now.
Bought the market version. Thanks for the dev effort and adding support for DNA!
Awesome App!!
Can it be useful in a HTC ONE V ??....cause you add ONE S ...so, it may be possible??
Thanks.
JTNiggle said:
Thanks a bunch for the DNA support, you rock joey. Downloading now.
Click to expand...
Click to collapse
elkay said:
Bought the market version. Thanks for the dev effort and adding support for DNA!
Click to expand...
Click to collapse
Thanks for the support! Always appreciate the 99 cent USD market purchases.
Please let me know if you have any issues or any feature requests!
sonrics1993 said:
Can it be useful in a HTC ONE V ??....cause you add ONE S ...so, it may be possible??
Thanks.
Click to expand...
Click to collapse
Unfortunately, the HTC Unlock process for the One V doesn't allow Flash Image GUI to work.
Thank you for adding support for both devices that I currently own! HTC EVO 4g LTE and Samsung nexus 10! Downloaded the market version and looking forward to flashing ktmanta on my nexus 10
Pretty amazing thank you
Sent from my HTC6435LVW using xda premium
So it may have just been my stupidity, but as a first time kernel flasher I used this and it screwed me up for a bit. I just downloaded the zipped files of the modules and boot.img (which I now realize I probably should have unzipped them) but this caused the device to not fully boot unless I did a factory reset, wiped system, and flashed the rom again from recovery. Just in case someone makes this same mistake I wanted to post this here. I simply re-flashed the kernel the normal way (fastboot the boot.img and flash the modules zip in recovery) and everything works now. My suggestion is to modify the directions if I am supposed to unzip the files. If I am not then something is wrong with the kernel flashing. Thanks for your hard work!
fast and safe method! Just had to flash the boot.img which I previousely put into my sdcard and the modules...first flashed the boot.img using GUI apk and then through recovery flashed the modules...it worked! Thanks a lot for this easy option!
bigdog2k7 said:
Thank you for adding support for both devices that I currently own! HTC EVO 4g LTE and Samsung nexus 10! Downloaded the market version and looking forward to flashing ktmanta on my nexus 10
Click to expand...
Click to collapse
fernando sor said:
Pretty amazing thank you
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
santacruzdz said:
fast and safe method! Just had to flash the boot.img which I previousely put into my sdcard and the modules...first flashed the boot.img using GUI apk and then through recovery flashed the modules...it worked! Thanks a lot for this easy option!
Click to expand...
Click to collapse
Thanks for all the positive feedback and support! Feel free to let me know if there are any areas I can improve!
Imacellist said:
So it may have just been my stupidity, but as a first time kernel flasher I used this and it screwed me up for a bit. I just downloaded the zipped files of the modules and boot.img (which I now realize I probably should have unzipped them) but this caused the device to not fully boot unless I did a factory reset, wiped system, and flashed the rom again from recovery. Just in case someone makes this same mistake I wanted to post this here. I simply re-flashed the kernel the normal way (fastboot the boot.img and flash the modules zip in recovery) and everything works now. My suggestion is to modify the directions if I am supposed to unzip the files. If I am not then something is wrong with the kernel flashing. Thanks for your hard work!
Click to expand...
Click to collapse
The root issue is that kernel developers do not always package the kernel and modules using the same methods. Given different kernel developers exposure to different HTC locking methods the challenge is to write a program that can handle the variation of methods kernel developers use to package their end product and provide directions for any special work around circumstances.
I attempted to outline these steps in the OP and I've pasted below for your convenience. Let me know if any of these steps seem vague or out of place and I can work to refine the directions and process!
joeykrim said:
HTC Unlock - Users Guide for flashing boot.img with separate modules.zip:
1) Using Flash Image GUI, flash the boot.img file
2) Reboot to the custom recovery
3) From the custom recovery, flash the modules.zip file
4) Reboot
Click to expand...
Click to collapse
I get this when I launch.
sent from my droid DNA
nev310 said:
I get this when I launch.
sent from my droid DNA
Click to expand...
Click to collapse
Have you modified your build.prop file?
Can you paste the output from:
adb shell getprop ro.product.device
Is there any possibility of this to be working in Xperia phones??
freaktechz said:
Is there any possibility of this to be working in Xperia phones??
Click to expand...
Click to collapse
I've wanted to add support for Xperia devices but haven't been able to afford purchasing them.
If you have knowledge of ADB, the custom recovery and are willing to help test, please send me a PM and we can work on adding support!
This goes for anybody with a device that isn't currently supported.
Thanks for the inquiry!
Noob questions....Can I use this to update CWM from 6.0.1.2 to 6.0.2.3? If so, how? Do I need a boot img? Or do I just select recovery and choose 6.0.2.3? Thanks.
redone0505 said:
Noob questions....Can I use this to update CWM from 6.0.1.2 to 6.0.2.3? If so, how? Do I need a boot img? Or do I just select recovery and choose 6.0.2.3? Thanks.
Click to expand...
Click to collapse
Yes! Just select recovery and choose the updated cwm-recovery.img file!
I use this feature personally when switching between TWRP and CWM or upgrading recovery versions.
joeykrim said:
Yes! Just select recovery and choose the updated cwm-recovery.img file!
I use this feature personally when switching between TWRP and CWM or upgrading recovery versions.
Click to expand...
Click to collapse
One more...So I need to extract the image file from the zip, correct? Thanks Again!
Karbonn Titanium S5
{
"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"
}
GENERAL
2G NetworkGSM 900 / 1800 - SIM 1 & SIM 2
3G NetworkHSDPA 2100
SIM Dual SIM (Mini-SIM)
Announced2013, March
DISPLAY
Type IPS LCD capacitive touchscreen, 16M colors
Size 540 x 960 pixels, 5.0 inches (~220 ppi pixel density)
Multitouch Yes
SOUND
Alert types Vibration, MP3, WAV ringtones
LoudspeakerYes
3.5mm jackYes
MEMORY
Card slot microSD, up to 32 GB
Internal 4 GB, 1 GB RAM
DATA
GPRS Yes
EDGE Yes
Speed HSDPA
WLAN Wi-Fi 802.11 b/g/n, Wi-Fi hotspot
Bluetooth Yes, with A2DP
USB Yes, microUSB v2.0
CAMERA
Primary 8 MP, 3264 x 2448 pixels, autofocus, LED flash
Features Geo-tagging
Video Yes
Secondary Yes, 2 MP
FEATURES
OS Android OS, v4.1 (Jelly Bean)
CPU Quad-core 1.2 GHz(Qualcomm S4 play msm 8625q)
Sensors Accelerometer, proximity, compass
Messaging SMS(threaded view), MMS, Email, Push Email, IM
Browser HTML
Radio FM radio
GPS Yes, with A-GPS support
BATTERY Li-Ion 2000 mAh battery
ROOTING
Rooting done with Framaroot
{http://forum.xda-developers.com/showpost.php?p=37508806}[thanks alephzain, joyprsinha]
Detailed Rooting explaination - http://forum.xda-developers.com/showthread.php?t=2235153[thanks zeyaan]
CWM/Stock Recovery
CWM Recovery image(non-touch) - http://www.mediafire.com/?k5rjak05jdb20c6
CWM Recovery image(touch) -[removed! NWIP]
Stock Recovery Image - http://www.mediafire.com/?72g5uofhnndzzef
Stock Boot Image - http://www.mediafire.com/?lcap0u03ymhlcm6
Unpacked Boot Image(ramdisk files included) - http://www.mediafire.com/?9x34bw6y2uhk9j9
ROMS
Stock Rom - http://sdrv.ms/17MDCjl{Attention-this will only work if you have not formattet your /system(basically for porting purpose only)}
[Update-script attached at the bottom.replace updarer-script on the stock rom(destination-stock.zip>META-INF>com>google>android>(drag and drop here,overwrite.))]
[new update script added-from device similar to s5.from this update script to work please use the stock boot.img and place inside the rom zip]
Hit thanks--if it works!!!!
Nemesis One-link-by Nemesis Devs
FLASHING CWM/STOCK RECOVERY
NEEDED - http://www.mediafire.com/?rqc3vi41z6xx439
#Copy the downloaded image file to the folder in your PC where you have set up ADB and fastboot.
#Rename the file to recovery.img
#Turn off your phone. Enter fastboot mode by holding the Power and Volume + button for some time.
#Release both buttons when you see a green screen on your phone.
#Plug in the phone to PC using USB cable, wait for the drivers to install and finish setting up.
#If you are in Windows XP, open command prompt and browse to the folder where you have setup ADB. Or if you are in Windows7/8, hold shift then right click in the ADB folder and click to open command prompt there.
#Type this in the command prompt :
Code:
fastboot devices
#This should display your device name in fastboot mode, if nothing is shown, then you have to check previous steps again.
#Type this command to flash CWM recovery to your phone :
Code:
fastboot flash recovery recovery.img
#It will show the progress and completion dialogue within seconds when it finishes successfully.
#That’s it! CWM Recovery has been installed successfully. Now you can try if CWM is working by entering recovery mode as follows :
#Remove battery of your phone and reinsert.
#Press Power and Volume+ buttons and keep holding it for some time.
#When you see a green screen, you can leave the power button but keep holding Volume+ button.
#Now you will shortly see a red screen, then press the Home button on your phone.
#You should see CWM now, otherwise try the whole process again. Once you are inside CWM, use your volume keys to navigate the options and power button to make selections.
FLASHING STOCK BOOT
#Go to fastboot mode as explained above.
#make sure your device is shown in command prompt
Code:
fastboot devices
#copy the boot.img to the fastboot folder
#flash the boot sector with the boot image
Code:
fastboot flash boot boot.img
##remember the last part of the code may be modiffied according to the boot image name
Code:
fastboot flash boot stockboot.img
MODS
#AwesomeBEATS v.5 by ...Awesome...(for better music quality) - official thread-http://forum.xda-developers.com/showthread.php?t=1728391 [tested on S5 by me- credits:...Awesome..]
Thanxxxx for this awesome work...
But Framaroot with "Gandalf" is not working.. Now Solved!!
Solved Post
Update : If you Do a wipe data/cache, Format Factory or Data, Clean Cache etc. Just Reinstall the Superuser.apk... No need to Do the rooting process Again. Thats Awesome!!!
Used - Factory Image Android And Installed CWM. however CWM does not reboot at the command "Reboot" in it. Don't know whats the problem.
does it fails or sucess but superuser does not start?
michael.the.don said:
does it fails or sucess but superuser does not start?
Click to expand...
Click to collapse
Thats Solved Brother... Check the above post... N Thankxxxx for your Work on the CWM and Stock n Boot Image... Thankxxxx a lot Brother...
Recovery was installed successfully via this method also with the help of terminal emulator.
http://forum.xda-developers.com/showthread.php?t=1924846
This method can also be updated by op.
will try and port cm10.1 soon
EDIT: can someone help me find a similar device...by similar i mean same hardware specs
lekhwani said:
Recovery was installed successfully via this method also with the help of terminal emulator.
http://forum.xda-developers.com/showthread.php?t=1924846
This method can also be updated by op.
Click to expand...
Click to collapse
Will update.presently on a journey
Sent from my Titanium S5 using xda app-developers app
anshsahajpal said:
will try and port cm10.1 soon
EDIT: can someone help me find a similar device...by similar i mean same hardware specs
Click to expand...
Click to collapse
Similar device is cherry mobile skyfire 2.0 but it is yet to be released.search for device with msm8625q processors.but you will not get the same screen size
Sent from my Titanium S5 using xda app-developers app
lekhwani said:
Recovery was installed successfully via this method also with the help of terminal emulator.
http://forum.xda-developers.com/showthread.php?t=1924846
This method can also be updated by op.
Click to expand...
Click to collapse
This method is not safe. You are lucky coz the mmcblk partition was same as the recovery partitions I extracted. If it were another partition then you could have bricked your device. Advisable is the fastboot method. It will already find the recovery partition for you
Sent from my Titanium S5 using xda app-developers app
michael.the.don said:
This method is not safe. You are lucky coz the mmcblk partition was same as the recovery partitions I extracted. If it were another partition then you could have bricked your device. Advisable is the fastboot method. It will already find the recovery partition for you
Sent from my Titanium S5 using xda app-developers app
Click to expand...
Click to collapse
Then it means I was really lucky.
Btw, though everything is fine in cwm recovery ( I even backed up my current Rom through cwm), rebooting through recovery takes about one minute. I mean when I click on reboot option in recovery, it says rebooting but this screen is there for about 1 minute then actually the reboot happens. Can this be associated with my method of flashing?
lekhwani said:
Then it means I was really lucky.
Btw, though everything is fine in cwm recovery ( I even backed up my current Rom through cwm), rebooting through recovery takes about one minute. I mean when I click on reboot option in recovery, it says rebooting but this screen is there for about 1 minute then actually the reboot happens. Can this be associated with my method of flashing?
Click to expand...
Click to collapse
Possibly it can be coz of the flashing method. Flash it with fastboot then see if it improves
EDIT:i clocked my reboot time to recovery. its around 45-50 sec. so its not a matter.may be it takes time to shutdown due to applications running.
Sent from my Titanium S5 using xda app-developers app
if someone has tested any mods sucessfully please post it here. i will update it in the OP
michael.the.don said:
Possibly it can be coz of the flashing method. Flash it with fastboot then see if it improves
EDIT:i clocked my reboot time to recovery. its around 45-50 sec. so its not a matter.may be it takes time to shutdown due to applications running.
Sent from my Titanium S5 using xda app-developers app
Click to expand...
Click to collapse
Buddy, I think u misunderstood. I am asking about time to reboot from recovery to karbonn logo and not the the time to reboot from main switched on os screen to recovery. Kindly reread my previous post.
Sent from my HTC Flyer P512 using Tapatalk 2
Sorry my bad. its a bug in the CWM recovery.mine takes more than 1 min.i am looking into it. its not only you i think everyone is experiencing that problem.
i have uploaded unpacked boot image files. can we get a developer here please and have it modded. coz i am not so much experienced in modding the boot image.
michael.the.don said:
Similar device is cherry mobile skyfire 2.0 but it is yet to be released.search for device with msm8625q processors.but you will not get the same screen size
Sent from my Titanium S5 using xda app-developers app
Click to expand...
Click to collapse
that is the problem i will try to customize the stock rom a bit for now...
till then people have patience and hope that some cool devs buy skyfire 2.0 and s5
well i am trying to port some roms myself. hope every thing works right. coz we only have the stock rom. no CM is available to us.
michael.the.don said:
well i am trying to port some roms myself. hope every thing works right. coz we only have the stock rom. no CM is available to us.
Click to expand...
Click to collapse
Good luck. Hope to taste New roms soon.
Sent from my GT-P3100 using xda premium
wi-fi not working in the stock rom.can some one tell me what permissions has to be set for "wpa_supplicant"and "wpa_cli"?
Hi,
I can't get out of the bootloop of my Honor 7. Here below the history:
1) Unlock bootloader: Success
2) Install TWRP: Success
3) Install SuperSU 2.65: Fail
From this point i tried to recover from a new original rom with Multi-tool, but still bootloop. I also wipe all caches but still same issues. I don't know what to do as i have the feeling i tried everything already.
If someones could help me it would be nice. I still have access to bootloader (volume - & power) and I sometimes get access to TWRP but screen freezes, i can't go into any of the settings.
Thanks for your support!
Download full rom 121 if you are in LP or 320/330 if you are in MM.
Put the rom .app file into dload folder in the SDcard
Flash stock recovery,flash the rigth rom with vol+,+,vol-,+,pwr, the flashing will start automatly.
Upgrade to 180 or 330.
The files:
http://www.modaco.com/forums/topic/...ck-rom-images-updated-1st-april-2016-plk-l01/
Flamenawer said:
Download full rom 121 if you are in LP or 320/330 if you are in MM.
Put the rom .app file into dload folder in the SDcard
Flash stock recovery,flash the rigth rom with vol+,+,vol-,+,pwr, the flashing will start automatly.
Upgrade to 180 or 330.
The files:
http://www.modaco.com/forums/topic/...ck-rom-images-updated-1st-april-2016-plk-l01/
Click to expand...
Click to collapse
That won't work sadly, PLK-L01 is totally different than PLK-TL01H in terms of software.
The updates is also named differently compared to the European version, in the EU (and elsewere?) it's 180, 320, 330 etc. but on the PLK-TL01H it's 6.3.16, 6.4.1 etc.
Hi,
indeed Flamenaver the link you post is for PLK-L01 only.
Can i use one of these firmware instead which are original ones for PLK-TL01H?
http://emui.huawei.com/cn/plugin.php?id=hwdownload&mod=detail&mid=170
How does this VOL UP + VOL DOWN + Power works exactly? Do I need the press the 3 together until i see the upgrade starting or do I relesea as soon as I see HONOR Welcome Screen ?
Because it is not working if i keep the 3 pressed until something happens, because then it is restarting and restarting for ever.
On the other side, just pressing 3 for 10 seconds and couple of seconds after it powers on doesn't work neither.
Thanks for the support.
Tabithalos said:
That won't work sadly, PLK-L01 is totally different than PLK-TL01H in terms of software.
The updates is also named differently compared to the European version, in the EU (and elsewere?) it's 180, 320, 330 etc. but on the PLK-TL01H it's 6.3.16, 6.4.1 etc.
Click to expand...
Click to collapse
Try to install LP or MM full rom (no ota o zip roms),from stock recovery, with the standard process for your phone, is a universal unbrick procedure for soft_bricked phones.
I can't get access to stock recovery. I can reinstall Stock recovery from Honor Multi Tools but i can't get in it.
If i keep vol+ & Power or Vol+, Vol- & Power pressed i get onl the honor welcome screen bootloop, nothing else
Hi, I got into this mode in the end. Is this the Force update mode?
{
"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"
}
It was not easy to get in. Keep you informed in a couple of seconds what the results are.
Thanks
Tried twice already and always stuck at 90%...
sebastien_be said:
Tried twice already and always stuck at 90%...
Click to expand...
Click to collapse
If it's stuck at 90% it's not working, believe me, I've had the same problem, I tried to update SuperSU and it bricked. Had to factory reset it and update the phone to the newest version which currently is 6.4.1, THEN go through the process of installing TWRP, SuperSU etc.
If you can't get the updates via the "Updater" option in the options, try to manually downgrade/upgrade it and see if it appears. You have to do some fancy google-translate to chinese to find the update packages on chinese forums.
Why U don't try the Honor 7 Multitool and the huawei update extractor combo???
That must be work!
Hi,
this is the latest status: https://youtu.be/QsPOg4lKkSc
I'm already using Multi-Tools and extracted a PLK-TL01H stock rom. I then used the unbrick option in multi-tools and restores this stock rom. But even though it starts fine, i can enter my pin code but when the language screens comes in, it makes a weird noise and reboots.
I then went into TWRP which works fine and could wipe cache and wipe dalvik cache. But I'm still stuck with welcome crash.
Any idea what to do? As reminder:
1) Bootloader is unlocked
2) Bootloader screen works fine (fastboot works but adb doesn't)
3) TWRP screen also works fine.
Thank you!
Did you try with an older or an other stock rom?
Yes I tried these two versions;
PLK-TL01H-C01B201
PLK-UL-TL-CL_EMUI3.1_Android5.1_5.12.1
Actually this version: PLK-TL01H-C01B201 works fine but only without sim card and SD card. If one of these is inside then i get automated reboot after entering pin code. But if i reboot without these two, then the phone works fine (i can get access to wifi, menu, and so on...).
WEIRD!
Hi,
My Honor 7 is still bricked and i can't get out of it. I tried to unbrick by flashing the following files from a stock rom:
fastboot flash boot .\Unbrick\BOOT.img
fastboot flash cust .\Unbrick\CUST.img
fastboot flash recovery .\Unbrick\RECOVERY.img
fastboot flash system .\Unbrick\SYSTEM.img
The flash of these 4 files works fine. I then get the welcome screen where i can choose the language, HiCloud settings and so on. As long as i do not get out of the flight mode it seems to be stable. But when i enter the pin code of my simcard (amongst others), then i get a crash and reboot.
So i have the feeling that there are still some conflicts. In the stock rom there are many other IMG files. Shouldn't I also flash them? I have the following IMG files: 3RDMODEM, CACHE, CRC, CURVER, DTIMAGE, EFI, FASTBOOT, MODEM, etc etc.
I have the feeling that if i flash them all, then it might work fine. But all files do not have a specific partition, so i don't know how to flash them.
Thanks for the support!
sebastien_be said:
Hi,
My Honor 7 is still bricked and i can't get out of it. I tried to unbrick by flashing the following files from a stock rom:
fastboot flash boot .\Unbrick\BOOT.img
fastboot flash cust .\Unbrick\CUST.img
fastboot flash recovery .\Unbrick\RECOVERY.img
fastboot flash system .\Unbrick\SYSTEM.img
The flash of these 4 files works fine. I then get the welcome screen where i can choose the language, HiCloud settings and so on. As long as i do not get out of the flight mode it seems to be stable. But when i enter the pin code of my simcard (amongst others), then i get a crash and reboot.
So i have the feeling that there are still some conflicts. In the stock rom there are many other IMG files. Shouldn't I also flash them? I have the following IMG files: 3RDMODEM, CACHE, CRC, CURVER, DTIMAGE, EFI, FASTBOOT, MODEM, etc etc.
I have the feeling that if i flash them all, then it might work fine. But all files do not have a specific partition, so i don't know how to flash them.
Thanks for the support!
Click to expand...
Click to collapse
The main problem that you were on MM version (6.3.16-DEV edition of ROM, no official update) of ROM and you're trying to flash Lollipop (B201, 5.12.1). It means that your problems are probably caused by this. Try to flash 5.12.16 then OTA update to 6.1.1 (using WiFi if possible) and then rollback from Emui 4 to Emui 3.1 if you want use Emui 3.1 and Lollipop. it's up to you. It's possible that your will be able to use SIM card when you would update to 6.1.1 (MM)
Sent from PLK-TL01H
SOLVED!
Thank you Lucki_X and Inside!Out ! Indeed i was trying to flash with Android 5.0 while i was already on Android 6.
Consequently I used the unbrick option from Multi-tools by using this version PLK-TL01H_EMUI4.0_Android6.0_6.2.1(B634).zip
Now everything works fine. Can anyone tell me how to install SuperSU? Because it is due to installation of SuperSU through TWRP that it caused the crash. I installed SuperSU 2.65 BETA.
How to do and which version to install to avoid bootloop?
Thanks very much,
Sebastien.
Hi All,
any idea why i now only have 3,87GB available as internal storage?
sebastien_be said:
Hi All,
any idea why i now only have 3,87GB available as internal storage?
Click to expand...
Click to collapse
Probably because you have multiple ghost systems as a result of previous still in memory. Factory reset will help.
Thank you! This is also solved now (Factory reset in TWRP + Calvik & Cache Wipes)!
Last question: Any advice on how to install SuperSU? Because by trying to install 2.65 BETA it caused the bootloop earlier.
Is there any version to propose instead of another one?
Thanks,
To answer my question: There is only the v2.62 that is working with Honor7 ! I Tried 2.49 and 2.65 both creates startup bootloop. Hopefully this time i got a full backup made in TWRP, was pretty easy to comeback to a working version.
i have a similiar brick as you. Flashed from B201 to B352 via the OTA. Had a boodloop, tried to erase cache and factory reset.
Tried to unbrick my phone with multi tool (first with the B201 udpate.app - now with B634 update.app). Now i'm in a bootloop again. What can I do?
EDIT: I'm in the ROM now, but can't enable my SIM card and WIFI is also not working
What can i do?
Avoid and pass by a fool and a madman
How to root Black Shark 2 Global (short way)
Avoid and pass by a fool and a madman
Avoid and pass by a fool and a madman
A few guide to fix your bricked or bad-conditioned phone
Avoid and pass by a fool and a madman
Avoid and pass by a fool and a madman
Thank you for this great guide, I'm sure it will help a lot of people.
The update file I used in my post was from this link, I just rename to make it easier to update.
KM7 said:
Thank you for this great guide, I'm sure it will help a lot of people.
The update file I used in my post was from this link, I just rename to make it easier to update.
Click to expand...
Click to collapse
Wow, thank you very much for the full name link. I think I found something great. I think, now, you can try to root directly on latest firmware, and save lots of time. I will test it... and post it soon.
How to download the latest update as full-sized, factory stock roms
Under Construction....
Sorry for deleting this post.
BS team never open the stock rom download site. I think we can build one, but I couldn't gather enough information.
I was able to find all my own factory stock rom OTAs including the latest, but not others due to lack of information. Further problem is that after I share how to find & download your own latest factory stock rom directly, that site is really slowed down now. Maybe lots read it, download, never share, or due to other reason... The region and ota link is enough to build the stock rom download site, but now the server is slowed down, no one shares... so I stop here.
I will re-open this if I could gather enough information.
wga0 said:
Hey guys, I realized that I neither need to provide a detailed explain nor can.
I can't attach any files, pictures, links... even I can write now. There are too much restriction.
(I must delete all links I included here You can search it in xda-dev forum)
So, here's the shortest and fastest way to root your black shark 2 global.
If anybody want a long detail, more safe way, let me know. I will add later if possible.
If something goes wrong, end to brick your phone, you can always revive that with safe way.
As you know, though safety is increased greatly (Thanks very much to a/b slot system),
but accident can happen anytime. It's on your own responsibility, at your own risk.
Pre-Requirements:
adb/fastboot drivers, Magisk Manager latest version, global OTA1 update
(I skip all the details of 3 firmware regions, payload_dumper, twrp, all others)
(Backup your data. It requires several factory reset)
Steps (also skip all detail. I wish you familiar with adb, fastboot, a/b slot)
1. Unlock the bootloader
1) fastboot oem bs2_unlock (Thanks greatly to Bave Lee)
2) fastboot oem bs2_unlock_critical (I'm not certain this is mandatory, I just do it at first)
2. flash the global OTA1 update and reboot
1) find and set active your not using slot
fastboot getvar all
fastboot set_active x
2) flash the global OTA1 images to that slot
fastboot flash partition_x partition.img (flash all of it, not partially)
fastboot reboot (It will be reboot again to do factory reset, than will boot successfully)
3. Patch the boot.img with Magisk Manager and flash it
Now, you have a working old version boot image. Patch it, flash it and reboot
4. Backup the latest, your own boot.img
Now, your phone is rooted with old version. Backup your original latest boot image
1) adb shell
su
dd if=/dev/block/bootdevice/by-name/boot_x(your using_latest slot) of=...(any folder you prefer)/boot.img
2) copy the boot.img to your PC (with adb pull or mtp)
5. patch your own latest boot.img
1) Set back the active slot to your original slot, reboot
2) do factory reset (because of using OTA1, OTA2 update request will be remained to your current slot)
3) push the magisk manager, boot.img again and repeat the job (patch, pull out, reboot, flash and reboot again)
6. Now, you have the latest updated, rooted phone with stock & modified boot image
7. Don't forget to backup all your stock ROM before doing anything!!
{
"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 you done well, you can check the root status. It's rooted with magisk systemless root, all function's normal.
And be careful. Don't share the patched or stock boot image directly. There's multiple global version.
This is the latest version from my own black shark 2 global. It definitely different from yours.
If you flash different region version, your phone will be bricked. That's why I didn't share it and write this long method.
(If anyone want, I will explain details later with more safe way, what I did. But It's quite long way, takes long time)
Click to expand...
Click to collapse
Here is my region skyw1991010Os00mp5,can u help me with this?
Avoid and pass by a fool and a madman
Flauros7 said:
Here is my region skyw1991010Os00mp5,can u help me with this?
Click to expand...
Click to collapse
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Need help
I am successful root my BS2
it run Magsik perfect
but the Build number is SKYW1908301CN00MP6 and wifi does not work, also i cant update build number to Build SKYW1910291CN00MP7
use *#*#1027#*#* to locall update with the
SKYW1907040OS01MP3 Stock Factory Image not work too, it said Error the package unauthorized
can u help me solve this problem,
does the Global OTA 1 boot can fix it?
Can u send me your boot file i cant find it
thank you very much!!!
Avoid and pass by a fool and a madman
The MP7 China OTA update...
IT'S WORKED!!!
thank you very much!
now i'm trying to root new version
exynos 540 said:
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Click to expand...
Click to collapse
Hi can you sent me the stock boot image for skw1991010Os00mp5? I really need it.
Hello , Please I need Stock boot.img for this region SKYW1902180OS00MP2 android version 9.
Mustafa9698 said:
Hello , Please I need Stock boot.img for this region SKYW1902180OS00MP2 android version 9.
Click to expand...
Click to collapse
Are you sure your revision SKYW1902180OS00MP2? Isn't it SKYW1904180OS00MP2?
exynos 540 said:
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Click to expand...
Click to collapse
Yes bro can u send me the file?
wga0 said:
You mean your revision is SKYW1911010OS00MP5. Right? If you didn't try anything to your roms, you'll have previous revision SKY1909192OS00MP4 at the inactive slot. Here is the factory boot image of it. How to root is similar as above.
Before doing, backup all your data and unlock the bootloader. In this time, unlock_critical is not needed.
1. adb reboot bootloader
2. fastboot getvar current-slot (let's assume it returns b)
fastboot set_active a <- set the opposite slot as active
3. fastboot reboot
After factory reset, this will bring you to previous revision SKYW1909192OS00MP4. Install Magisk Manager and patch the boot image.
4. adb pull /sdcard/Download/patch_boot.img (let's assume you save the image to Download directory)
5. fastboot flash boot_a patch_boot.img <- flash that patched image to same slot (you just set active)
Your phone is now rooted with previous revision. You can backup all of your latest stock rom.
6. adb shell
7. su
8. dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/Download/boot.img <- example of boot image. For insurance, just backup all your stock roms.
Now back to your original latest slot, root your own image.
9. fastboot set_active b
and repeat the rooting again with your own roms.
As you know, adb command can be used with USB Debugging, fastboot can be used in bootloader mode.
Or... if you need all of those images, let me know. I will upload full MP4 OTA factory images for your region. You can flash this to your inactive slot and it will fix all problems during updating to MP5 to your active slot.
Click to expand...
Click to collapse
Can u give me the file again because the link is dead?
Boot images, Factory(Full) OTA images for known regions/revisions
Avoid and pass by a fool and a madman
Hi,
I tried to update my P6 using the magisk OTA update method:
-Unistall / Restore image
-Install OTA, no reboot
-Install magisk on inactive slot
-Reboot
My phone was on the SQ3A.220705.001.B2 update, few months old.
When I rebooted, I was prompted with the "device corrupted" message. I pressed the power key to continue, and was stuck at the Google logo boot loop.
I forced turned off the phone (hold power + vol up a few sec), and the phone rebooted, no corruption message to my surprise, and booted correctly. However, my system did not update (still on SQ3A.220705.001.B2).
I'm a rookie on device rooting, but my understanding is that my inactive slot (partition b) as the update installed but is corrupted and goes in boot loop, while partition a is not updated but not corrupted either.
The thing is, I only did "install on inactive slot", so magisk was uninstalled on partition a, and rebooting made me lost root on that partition.
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
SleinBuyt said:
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
Click to expand...
Click to collapse
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
SleinBuyt said:
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
Click to expand...
Click to collapse
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
m_pastuszek said:
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
Click to expand...
Click to collapse
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Strephon Alkhalikoi said:
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Click to expand...
Click to collapse
I agree on this side, but actually editing script that makes something similar comes down to the same thing
That was the same case for me.
After latest OTA update, no matter how many time I tried to flash full factory image via fastboot, stil showing device corrupted.
A couple of things everyone having this issue should be aware of.
Currently, "Flash to Inactive Slot" breaks verification/dm-verity on the Pixel 6/7, and I believe that's responsible for the "Device corrupted" error. The Magisk devs are aware but don't have a fix yet. I haven't been able to test because there have been no OTAs since I disabled those myself (which PixelFlasher can do for you), but I believe disabling them should prevent that problem during OTAs, but be advised I think doing so requires wiping /data when you do it.
Also, if you're still getting "device corrupted" even after reflashing stock, first watch for any errors during flashing in PixelFlasher (I may have a fix for anyone that has USB issues on Windows devices, but it involves the registry so it makes some people nervous), but if it isn't working then try Google's Android Flash Tool by finding your device and desired firmware here and clicking Flash. You'll need to be using Chrome. That's never failed for me. Once you have it up and running again *then* use PixelFlasher to patch and flash the boot image.
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Jaitsu said:
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Click to expand...
Click to collapse
To root the Pixel 6 on QPR2 Beta 1 you can patch the Pixel 7 boot image and then flash that on the Pixel 6.
Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk
After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...
github.com
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
SleinBuyt said:
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
Click to expand...
Click to collapse
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Lughnasadh said:
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Click to expand...
Click to collapse
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
SleinBuyt said:
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
Click to expand...
Click to collapse
It's important if you don't want to brick your device. Did you read the link I gave you?
Lughnasadh said:
It's important if you don't want to brick your device. Did you read the link I gave you?
Click to expand...
Click to collapse
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
SleinBuyt said:
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
Click to expand...
Click to collapse
fastboot flash bootloader --slot=all <A13 bootloader image>
My situation is a bit bizarre. I'm on beta and recently got an update notification that was 190mb. I went to magisk to restore images and magisk says stock backup does not exist. From there and went ahead and use my PC to flash my stock boot image and rebooted. Once an Android it's still says the same thing but when I go back to the update it says installation problem Even though I am on stock. That's where I'm at right now. Haven't messed with it since just rolled with no root and stock boot image.
{
"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"
}
Lughnasadh said:
fastboot flash bootloader --slot=all <A13 bootloader image>
Click to expand...
Click to collapse
And it's done ! Thanks for potentially saving my phone later !