Hello I need a little bit of help.
My problem:
I've LineageOS 16 on my Samsung Galaxy S5 (SM-G900F) and I want to change the boot image BUT if I make exaktly that what I saw in a video my phone just boot in the bootloader. So now i want first the stock boot image to have a back up, so that I can make a different boot image. (Btw I need help with that too. Do i just need to go to twrp and install it as "image" "boot" and install it?)
Related
Hope that sounds enough interesting to get you here
to my problem:
I have a Huawei MediaPad 10 Link+ and theres NOTHING out there for it. So i decided to make it on my own.
belive me theres no recovery or rom for this tablet.
i had a long journy so dont think this is my first problem
i dumped my boot.img, recovery.img and system.img
i used this tool to unpack my recovery modified it, repacked it and flashed it. but the recovery wont boot up. just stuck at the first mediapad logo.
Even if i NOT touch it. ( just unpack / repack )
my problem is not to restore it. i want a modifyd recovery. maybe sobody here can help me.
thanks in advance
PS: the best would be if somebody could port me CWM or TWRP
i tried to make it on my own but ubuntu says no and punchd me in the face
The Author of the tool stated, that it won't work on every device.
But if you plan to build cwm or twrp for your device, you will need ,sooner or later, linux.
So save yourself some trouble and time and install linux in a virtualbox.
It will make numerous things easier for you :good: .
Hey everyone!
I own a BluBoo X6 (MT6732) and have been having some difficulty installing a custom recovery on my device. As the title explains, after I flash a custom recovery onto the device I am presented with a blank black screen for about 10-20 seconds and the the phone will boot like normal to the Android lock screen. This phone seems to have little to no support at all that I could find online, so I've only been working off the stock ROM. My attempts to have been as follows:
Using MTKDroidTools with the stock Boot.img to create a CWM recovery (Flashed from that application) - Blank screen then boots
Using MTKDroidTools with the stock Boot.img to create a CWM recovery (Flashed via SP Flash Tools) - Blank screen then boots
Using MTKDroidTools with the stock Boot.img to create a CWM recovery (Flashed via Android app) - Blank screen then boots
Using TWRP Setup with to create a TWRP recovery (Flashed from that application) - Doesn't install anything and stock recovery works perfectly
I haven't found any other one-click form of applications so my next step will likely be to try and port a recovery from a different phone but I thought I'd post my current issue incase it's something craz obvious that I don't know about as I'm 100% noob and trying to learn.
Thanks in advance!
Hi guys, here is a boot logo switcher for the Galaxy A3 2016. It works on all rooted SM-A310Fs on Marshmallow.
DOWNLOAD
bit.ly.2pnYH3a (replace the dot after y with a slash)
METHOD
I strongly recommend taking a nandroid backup and a backup of your existing boot.img before you attempt this (you can do this either through TWRP recovery or by pulling it from adb)
1. Extract the zip to a separate folder. You should have two files, META-INF and tar.
2. Copy your logo.jpg to this folder. It should be 1280x720.
3. Select all three files (Hold down ctrl and click on the files) and select send to - zip.
4. Copy this zip to the root of your SD card and flash in recovery (I recommend ashyx TWRP). When you reboot you should see a shiny new boot logo!
IMPORTANT
- The logo MUST be .jpg, and it must match the screen resolution of the device. In my case this is 1280x720.
- If something goes wrong, flash this .zip to restore the original boot logo. This is the white stock bootlogo. You can find the .zip at bit.ly.2p5koBX (again, remove the dot after ly and replace with a /)
- If you have no bootlogo, try flashing the zip above. If the problem persists, try to restore the backup you made earlier.
I am not responsible for any damage that may occur to your device by doing this.
This may work on other Samsung devices, however I have not tested it. It works on my SM-A310F rooted on Marshmallow. Let me know if it works on other devices. This method may work on other samsung devices, however it is pointless to try it on other devices, as it is much easier on those. Samsung, as you may know use a custom format for boot logos and animations, hence requiring custom scripts to change them.
A3 & A5 2016 already got threads for boot logo change.
[mod][a310f][bootlogo]
[MOD] Flashable Custom Bootup charging & Splash screens for A5 (A510F)
VARNING
This thread also lacks very important information about image properties, what can go wrong, and how to restore the original logo.
The partition you modify is part of the bootloader, so please don't just try on any device unless you know what you're doing.
Correct resolution and dpi for your device logo.jpg, correct partition path etc.
Otherwise it's a good chance it will brick.
Hello
I have the L22 variant, with TWRP installed and CM12.
Bootloader is unlocked.
I want to upgrade to CM13. It won't flash because I need to upgrade to a marshmallow (MM) bootloader first.
I extracted boot.img from an official MM rom using the update extractor.
Questions:
1. If I flash it, do I need to go again thru the procedure of bootlader unlook? (getting the code from the huawei site)
If so, I'd assume the code I used first will work, for some reason CM12 is now reporting different serial number. Though I saved the original values.
2. If I flash it, will CM12 boot? Or I will need to also flash system.img, which I also extracted.
3. If I flash it, will I loose TWRP? I guess no...
4. What is cust.img for? I am more a Samsung guy, not familiar with that file.
Thanks in advance.
i would restore to latest stock rom available and install from there to be safe, careful when wiping boot.img
Thank you...
Here is how I fixed, and put some answers if helpful for anyone else in the future.
1. Bootloader and Boot are different. During the startup process the bootloader calls either boot for a normal startup or call recovery.
Messing with boot won't touch the bootloader or the recovery areas.
2. I did not flash boot at the end, I used the ResurrectionMix which already comes with its own boot image. It took me to Marshmallow (MM).
In theory, this boot image will support any other MM ROM. I did not try because I ended up liking it.
3. As explained in (1). Flashing boot wont touch recovery
4. I haven't found an answer to this one. Anyway, I did not touch it.
Cheers.
boot only contains kernel and ramdisk , recovery its a separate paritition alternative to boot, at startup depending on what is pressed bootloader either calls boot partition or recovery parition or fastboot
Hello
I have honor 5x KIW-L22 & suddenly my mobile shows no service what should i do.
My sim is working in another phone and since i checked in the phone information option while using the ussd code to dispaly the details radio signal button is not showing
in the menu and when i call someone it shows radio off.
Please help me to sort out this.
Figured it out.
Dear all,
I am trying to replace the stock OS on my Lenovo tablet with some more open alternative, like LineageOS. I got as far as installing a modified version of TWRP on it and got root access.
I also found some unofficial gis LOS images but I couldn't install them via TWRP as the SYSTEM partition does not show up when I have to select which partition I want to install the image to. Mounting (ticking) the system partition in TWRP makes no difference. These are the partitions listed:
Boot
Vendor Image
Recovery
Modem (Image)
Persist (Image)
Splash
So I went ahead, and installed it from fastboot like this:
fastboot flash system image.img
Click to expand...
Click to collapse
The command succeeded, but when restarting, the device gets back to fastboot. I can boot into TWRP as well, but no matter what image I try to install, I get the same result.
I wonder what I am doing wrong... A few years back I have converted several phones to LOS and others with no problem. But I have no experience with gis. Maybe that's the problem.
Could someone more experienced help me? maybe I am trying the wrong gis images.
Thanks for any pointers in advance!