Does anyone know if it's possible to build an update.img but to just update the kernel and recovery? I'm pretty sure it must be possible.
Yes, it should be possible to just update these.
I guess you should look at how they build an image to install recovery only. Like when they install custom recoveries.
robertut said:
Yes, it should be possible to just update these.
I guess you should look at how they build an image to install recovery only. Like when they install custom recoveries.
Click to expand...
Click to collapse
Yeah I thought so. I'll be brave and try it as it'll be a damn sight easier to build the update with just recovery and kernel when I'm doing the 1st boot logo's and easier for everyone that wants a boot logo.
Goose247 said:
Does anyone know if it's possible to build an update.img but to just update the kernel and recovery? I'm pretty sure it must be possible.
Click to expand...
Click to collapse
Yes, you can !! Simply replace kernel and recovery Everything will be fine. But all the rest should be for your processor RK3188 or RK3066. ( system.img and boot.img )
Malaysk said:
Yes, you can !! Simply replace kernel and recovery Everything will be fine. But all the rest should be for your processor RK3188 or RK3066. ( system.img and boot.img )
Click to expand...
Click to collapse
We're thinking about creating an update.img containing only the kernel.img and recovery.img, and without the system and boot. Just to replace the boot logo, and not the whole system completely.
robertut said:
We're thinking about creating an update.img containing only the kernel.img and recovery.img, and without the system and boot. Just to replace the boot logo, and not the whole system completely.
Click to expand...
Click to collapse
Oh I understand - it will not work, I think. In recovery is to check if all the files - kernel , recovery.img, system.img and boot.img.
Malaysk said:
Oh I understand - it will not work, I think. In recovery is to check if all the files - kernel , recovery.img, system.img and boot.img.
Click to expand...
Click to collapse
It should be possible. The recovery will only update the files that exist. If it doesn't find boot.img for example, it will skip it.
It should be possible. At least when using custom recovery.
Anyway, There is a way to flash a recovery IMG without using recovery using a shell script, maybe this should work for kernel also...stg like this http://forum.xda-developers.com/showthread.php?t=2102679
I have use that method before on an android tv box. You should find a correct recovery.IMG for those devices though
If the kernel could not be flashed that way, you can install a custom recovery and install the kernel and the stock recovery.img using a flashable zip.
Unfortunately, this is the only Android system I've worked on where updates have to be done with .img updates. It's not really for my benefit, it's for all the peeps I'm creating boot logo's for. Asking them to use a custom recovery or installing it using terminal emulator is more hassle than the way they have to do it at the minute. Not to worry
how do you guys compile the update.img ?
I tried few times with
RK3xxx_firmware_tools_5.99.07.00
extract, change kernel, build
the update.img does not install
RK3188
doctorman said:
how do you guys compile the update.img ?
I tried few times with
RK3xxx_firmware_tools_5.99.07.00
extract, change kernel, build
the update.img does not install
RK3188
Click to expand...
Click to collapse
RK3066 IMG Mod Tool
works, despite it's name it will unpack and pack the update.img for both RK3066 and RK3188, since they are packed the same.
jakejm79 said:
RK3066 IMG Mod Tool
works, despite it's name it will unpack and pack the update.img for both RK3066 and RK3188, since they are packed the same.
Click to expand...
Click to collapse
any link to it?
found this
http://rockchipfirmware.com/developer-tools
but I guess that program is only for linux and not windows
doctorman said:
any link to it?
found this
http://rockchipfirmware.com/developer-tools
but I guess that program is only for linux and not windows
Click to expand...
Click to collapse
There is lot resources on rk3188 around there
https://www.entertainmentbox.com/droidsticks-latest-rk3188-q7-firmware-download/
http://www.cnx-software.com/2014/11/10/android-5-0-lollipop-now-boots-on-rockchip-rk3188-tablets/
http://www.rockchipfirmware.com/forum-library
I used first two links and played with some generic Lollipop AOSP. Managed to install kernel and system partitions and to boot.
In third link you have rs232 low level integration described. It is used for MCU integration.
Didnt bother to extract libs and stock apps and try to rebuild with them. It would take some time and I have none to spare.
Anyhow, LP (and even MM) is not hard to get running on these units. Problem is with mumbo-jumbo stock apps that need to be rebuilt in order to comply with changed API and security model in LP/MM.
But even that is not too hard. Reverse engineer, get code / libs for rs232 and just change handlers in apps to confirm with new standards.
---------- Post added at 08:11 AM ---------- Previous post was at 08:00 AM ----------
doctorman said:
any link to it?
found this
http://rockchipfirmware.com/developer-tools
but I guess that program is only for linux and not windows
Click to expand...
Click to collapse
Here you have Windows tools
http://www.rockchip.nl/downloads/
Also you may contact their NL division. They are I EU so they should provide more support in accordance to good business practices.
doctorman said:
any link to it?
found this
http://rockchipfirmware.com/developer-tools
but I guess that program is only for linux and not windows
Click to expand...
Click to collapse
See attached, you can ignore the parameter file in the archive. If you want to mount the system.img files or others then you will want linux to mount them.
doctorman said:
how do you guys compile the update.img ?
I tried few times with
RK3xxx_firmware_tools_5.99.07.00
extract, change kernel, build
the update.img does not install
RK3188
Click to expand...
Click to collapse
My problem seems to be the image I was using had white background and in ASCII PPM format that increases the size and kernel does not install
made the background black
and indexed the colors to 224 colors in the image and the kernel was created without error
but after install my own logo nor malaysk logo shows
it now reverts to the original head units boot logo.
A note to anyone considering cooking an update.img for RK3188 800x480 devices in particular ('cos that's what I've got) but for any 2DIN car stereo head unit device really. It's more a request, but something I feel is a must-have for every ROM.
ADD A NOTIFICATION BAR SHORTCUT
THAT SWITCHES OFF THE SCREEN!
Essentially what I'm looking for is what came with the OEM KitKat 4.4.2 ROM preinstalled in my Eonon G2110F. During night driving, I could slide the Notification bar down, tap an icon that looked like a X in a box, and the screen would switch off. If I had a music app. or the AM/FM radio going, they would continue to play, and turning a knob or clicking a button on the unit would light the screen.
Thanks for listening!
djshotty said:
A note to anyone considering cooking an update.img for RK3188 800x480 devices in particular ('cos that's what I've got) but for any 2DIN car stereo head unit device really. It's more a request, but something I feel is a must-have for every ROM.
ADD A NOTIFICATION BAR SHORTCUT
THAT SWITCHES OFF THE SCREEN!
Essentially what I'm looking for is what came with the OEM KitKat 4.4.2 ROM preinstalled in my Eonon G2110F. During night driving, I could slide the Notification bar down, tap an icon that looked like a X in a box, and the screen would switch off. If I had a music app. or the AM/FM radio going, they would continue to play, and turning a knob or clicking a button on the unit would light the screen.
Thanks for listening!
Click to expand...
Click to collapse
It is called Malaysk ROM.. does what you want with screen saver and button
now please reduce the size of the font you used
jakejm79 said:
See attached, you can ignore the parameter file in the archive. If you want to mount the system.img files or others then you will want linux to mount them.
Click to expand...
Click to collapse
how do I use that in windows?
I just heard back from the developer of RK3xxx_firmware_tools_5.99.07.00 that the update.img I make with that tool can not be flashed in Recovery. and that is my problem, so I can use RK3xxx_firmware_tools_5.99.07.00 to modify the logo in kernel.img and package it all up with another program I guess
so what is the easiest way to repackage the update.img for flash in recovery of the device?
Question for our developers that have made recovery flashable update.img @Goose247 @Malaysk @dsa8310
Watched few videos on how to use the mod tool and they all use RK batch tool to flash the image... can the .img be flashed in recovery?
doctorman said:
It is called Malaysk ROM.. does what you want with screen saver and button
now please reduce the size of the font you used
Click to expand...
Click to collapse
Well that's just silly! I've gone through every Settings menu in the latest Malaysk ROM I'm still to find how to place a 'button' on the Notifications bar to switch the screen off. I only ask questions when I've exhausted all avenues of research. With that, do you have a way of enabling such a shortcut on my unit's Home screen, or even better, the Notification bar?
doctorman said:
how do I use that in windows?
I just heard back from the developer of RK3xxx_firmware_tools_5.99.07.00 that the update.img I make with that tool can not be flashed in Recovery. and that is my problem, so I can use RK3xxx_firmware_tools_5.99.07.00 to modify the logo in kernel.img and package it all up with another program I guess
so what is the easiest way to repackage the update.img for flash in recovery of the device?
Question for our developers that have made recovery flashable update.img @Goose247 @Malaysk @dsa8310
Watched few videos on how to use the mod tool and they all use RK batch tool to flash the image... can the .img be flashed in recovery?
Click to expand...
Click to collapse
When I did the boot logo changing service (when it worked), everyone I did it for installed the rom through recovery. I did a LOT of boot logos for other people and they all installed through recovery (choosing not to wipe to keep their settings, installed apps etc.) and I am pretty sure I had a 100% success rate with no complaints.
Perhaps the problem is you are trying to change the boot logo for a new rom and it simply won't work. Trying to change the boot logo for any Malaysk rom built after Feb (I think), it simply won't work. If you try mix and match and use stock kernel's and/or recovery's with Malaysk's rom you run the risk of bricking your unit. You are just going to have to accept the fact that you cannot change the boot logo on newer built roms.
I personally use an older rom so that using a custom boot logo will work.
Related
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
The problem with flashing oem firmware
medwatt said:
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
Click to expand...
Click to collapse
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
mtyler7807 said:
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
Click to expand...
Click to collapse
When you say "update", do you mean clearing the OS and installing a new one from scratch ? Does that mean after the update all the consumer cellular additions will go away and there will be no trace of it ?
If updating seems difficult now for the consumer cellular versions, what will we do when they release Lollipop ?
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Assuming they release the CC version of lollipop, will there be any problem if some of the system files have been changed? For example, I've deleted some system apps that I never use and changed the boot- and flash-screen files. Will the update fail because of that ? I'm asking this because I saw a video made by one of the forum members here when he was trying to install the v148 update. He had to uninstall everything and return the system to default before updating. If that is so, then I guess no Lollipop crying::crying for me !!
Given that Lollipop is still some months away and the lack of any meaningful activity on the HAM2, why don't we prepare our HAM2 for who-knows-what. I'd like to get a grip on a my phone now instead of getting swamped by error messages when Lollipop gets released or we get custom firmware.
There's this thread [http://forum.xda-developers.com/showthread.php?t=2315547] which explains how to extract the individual image files from the huawei update app.
Do you have the CC version of HAM2 ? If so, will you be trying to flash the image files because extracting the image files seem straight-forward ? I'm actually a bit nervous doing it myself because I've always flashed my other devices when it has been confirmed to work. What I'm wary of is I'm not sure that the device software in the v148 update app is 100% compatible with the CC variant that I own ! How can one be sure of that ?
I've downloaded v148 update file and extracted the files you mentioned. Instead of taking screenshots of the contents of the image files, I've recorded a small video. I can see the boot.img and system.img but no recovery.img. There are also other files. Take a look at the video. The question now is what to do with these files and more importantly what are my chances of unbricking the phone if it bricks !!
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you seen the video I uploaded ? Is it the "full download"? Can I flash it ? Will the phone brick ?
I read your posts on the subject. But it seems you have changed some system apps and the camera is not working as it should. I have already downloaded the 148 file and extracted the system.img and boot.img files. Can I flash these or do I have to use the files you uploaded on google drive ?
The question is why didn't you use the v148 stock ? I already have the v148 stock. Will it brick my phone if I flash the image files ? If not, why did you have to add extra files there such that the camera is 8MP instead of 13MP. Also, why is the hotspot always enabled ? Is that the case with people with the original stock ?
Man, I'm still waiting for your reply !
medwatt said:
Man, I'm still waiting for your reply !
Click to expand...
Click to collapse
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
290 said:
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
Click to expand...
Click to collapse
"For whatever reason mtyler7807 is trying to reinvent the wheel", Ha Ha. I spent about 2 weeks working on this phone when I first got it. With this phone it has more partitions than what is included in the backup with TWRP. TWRP is made for backup and restoring the files that get changed, the other partitions don't change. So when I first started experimenting with this phone I got a full 148 backup with no data and installed it. I had problems, the custom.bin points to a different cust/us/ folder (because it is for a different carrier) , I had to rename that folder and found I have no more 4glte only H/H+, So I had to get the original cust folder from the guy and copy it to the phone. Still and only H/H+. It was okay for then because I testing. Next Viewed my system specs and saw that pretty much half half phone was 148 and the other half was 132.
I have Redone my complete back since I posted the last one with google camera with 13mp support( rather have border transparency). I made a post asking people summit backups. You have to do a little research, did my research and got help from the forum guys. If you want 148 on your CC version you will have to extract the update and fastboot img files (ex.fastboot flash system system.img). The name of the file is the partition name.
From my understanding twrp does a nand backup. Which is more like an image of nand. So restoring an image from a stock phone would also give you the stock partition table no?
It has been a while since ive played with android on such a low level. When it came time to update my HP Touchpad to JB i had to manually create the partition table manually to make it fit. Eventually a script was created that automatically made the changes to the file system. Perhaps a solution along those lines could be useful in getting the stuck firmware on the CC phones? The file system would only need to be created on initial flash to the stock firmware.
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
medwatt said:
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
Click to expand...
Click to collapse
Here is what k2thejx5 said after flashing a backup from a stock phone.
k2thejx5 said:
What's weird is when I flashed the stock file and tried to upgrade, it wouldn't work. The kernels were different so I had to go back to stock consumer rom. Also, while using the rom you posted.. I lost my toggles and had to use a different app. What also was very weird, after flashing back to the stock consumer rom, I had tethering! Don't get it lol.
Click to expand...
Click to collapse
-Do what I did makes your phone a complete oem, All that is need to be done is to flash a splash screen.
-How would I know if updates will work since 148 is the latest version for oem, can't test that tell lollipop.
-I'm not pushing anyone to install my image, I got about 30 pm's to post my recovery to enable hotspot and to get those toggles backup at the top. Alot of people messed up and lost them flashing that original twrp recovery under developer. Alot of others wanted the hotspot without the head ache of going through the research.
And for the people with problems with there phone that want 148 and updates with no problems, You should have brought a OEM and stayed away from sears or target or took it back to the store if you were not ready to take on the challenge of fabbing up your phone. Or just deal with the factory image and hope for lollipop.
---------- Post added at 02:14 PM ---------- Previous post was at 02:06 PM ----------
Me and k2thejx5 was trying to fix the problem with the twrp recovery originally posted on this site. That one is not mine. Read the post. That firmware took our toogles away. You have to read this forum a little more.
Ok man, thanks for the reply. Two last question:
-For as long as you've been using your phone with your image files, have you been noticing problems like "unexpected crashes", trying to launch something and its unresponsive lie APN
-Is this the latest file you recommend : [https://drive.google.com/file/d/0BwnSk8BOQp3wV0JMWnJGc3RBTzQ/view]
Thanks.
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
mtyler7807 said:
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
Click to expand...
Click to collapse
All right then. Upload it when you're ready !
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Laitas said:
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Click to expand...
Click to collapse
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Aerieana said:
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Click to expand...
Click to collapse
Well i spend best part of this morning trying to a different aproach , i managed to find a ROM file (in kdz format, whitch woulve been useless for mtk tools anyway) whitch i extracted for a Recovery.img and tried to port the various recovieries with no awail for now. From what i've seen the filesystem inside the rom is a mess some of the files have the MTK headers others have the android ones and I'm trying to make this work entirely by trial and error.. If I'll manage to boot into the recovery I'll let you know. Wish me luck
Ok I managed to make a port from K10 that actually boots to recovery. I'll post updates as I work on it (all trial and error~)
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
what K8 do you have? MTK or Qualcomm Version?
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery :
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
how you extract the recovery img from the kdz? thanks.
tomi.gutierrez.i said:
how you extract the recovery img from the kdz? thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Laitas said:
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Click to expand...
Click to collapse
i flash the image you give, and it cant mount system, so it cant flash supersu, the lg k10 have the same problem that this recovery (it might be for the port), so we have to wait a super su version for lg k10 and k8 and a functional TWRP
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : LINK
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Yasser Da Silva said:
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Click to expand...
Click to collapse
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Have u found a way to root a lg k8
Maveroik said:
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Click to expand...
Click to collapse
Have u found a way to root a lg k8
Declan nalced said:
Have u found a way to root a lg k8
Click to expand...
Click to collapse
Nope man :'c
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : xxxxxxxxxxxxxxxx
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
hackwilliam said:
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
Click to expand...
Click to collapse
That was step 1 you have to go to fastboot form adb and unlock it from there
I've got the k8 us375 model today and its running 6.0 with an update waiting to install. I'm sure it won't matter much but I'm going to avoid updating anytime soon.
With little research into the device I'm reading people trying kingroot and getting stuck with a semi brick and error. From what I've read about marshmallow is the root needs to be accepted from the boot.img which also needs to be insecure.
So unlocking the bootloader is first.
Second is modifying the kernel and
Then recovery needs to be made so that superSu can be flashed.
I'm no expert but neither am i a newbie to this process, however I'm a little rusty. If anyone knows a better way to describe the processes needed please enlighten me. I'll be away from my PC till this weekend but have a laptop i can tinker with tonight. Until i completely understand what needs to be done I'll continue to do research. Thanks
Sent from my LGUS375 using Tapatalk
justlovejoy said:
If anyone knows a better way to describe the processes needed please enlighten me.
Sent from my LGUS375 using Tapatalk
Click to expand...
Click to collapse
I've been trying to root my k8 (k350n) - european version the last few weeks... so far i got:
(here i try to post a url i can't yet... you can find my topic on chinaphonearena - i describe everything there - search "lg k8 k350n twrp" on google - it will be the second result)
the twrp boots but i'm afraid it's not a perfect port so it migth not handling the partitions well... i mean when i try to install supersu i think it cannot find the boot.img (it seems to find but can't patch it).
The newest supersu supposed to patch the boot.img automatically so i believe the only thing we should manage to get a working twrp...
if you want to try i have to warn you that sometimes when i mess with the twrp i have to make a hard reset the get my phone working again. When you boot to the twrp it asks if you want to make your system writeable - you don't have to do that in order to install supersu - however if you allow twrp to make your system writeable you might lose data (i only lost data if i did a format in the twrp but only writeability doesnt clear data in my case...)
edit1:
so i found that supersu can only patch boot images compress by "gzip". The boot im. of our k8 is compress using "lz4" method. I also realized that my twrp works so far as the supersu tries to decompress the boot image... so
We either wait till supersu deals with lz4 or if we could somehow take (dump to pc) the boot image in fastboot "re"compress to gzip - flash back to the device - restart twrp (not boot to android yet - which obviously would not work), install supersu - restart to fastboot take the boot image "re"compress to lz4 and flash the patched boot.img back to the device.
well it's just an idea which actually stucks at dumping the image without root and who knows what other reasons...
or if we knew what tweaks needs to be done to the boot image and we could just make it on pc and flash it in fastboot (i have the stock boot image - i have the whole firmware actually)...
Any advice would be appriciated
Here we go guys...
http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
I actually had to return it. It was brand new in the box but the imei was linked to a delinquent account and I couldnt activate it. I'm subscribed if anything.
Hello there,
as you may know you can change the oem splash screen on the OnePlus 3, as provided in this thread by @makers_mark here.
That program only needs minor fixes to work with OnePlus 3T splash partitions, and I have attached the source code and a windows binary below.
To use it, extract the "OnePlus3TInjector.zip" and run the commands in the command prompt in the folder you extracted the zipfile into.
To decode use:
Code:
OP3TInject -i LOGO.bin -D
After having changed the image files, use
Code:
OP3TInject -j fhd -i LOGO.bin
I have tested this and it works on my phone, but you still have to USE THIS ON YOUR OWN RISK.
If you want to see how this looks, take a look at this video here: https://www.youtube.com/watch?v=DWj2WRpcoqI
If you want a custom bootlogo but can't use the tool you can pm me an image file or post one here down below. I will send you a zip file that you can flash in recovery.
To use this, get the "Stock" zip from below, and replace the modified.logo.bin in it with the one produced by the injector, then flash in your recovery.
If you do not want to use your recovery use a terminal emulator on your phone and run the command as root:
Code:
dd if=/sdcard/Downloads/modified.logo.bin of=/dev/block/platform/soc/624000.ufshc/by-name/LOGO"
To go back to stock logo.bin, flash the zip file attached below.
Please note that this does not remove the warning that your phone is unlocked.
Finally a big shoutout to @prmcmanus who tested this for me. Leave him a like!
I also thank @makers_mark for all the work he has done on the OnePlus 3 and the original OP3Injector.
Jo_Jo_2000 said:
Hello there,
as you may know you can change the oem splash screen on the oneplus 3, as provided in this thread here:
That program only needs minor fixes to work with OnePlus 3T splash partitions.
Unfortunately I cannot provide a compiled program here because the original program was not published under a proper license, but I can tell you that you just need to change line 35 of the file "src/LogoInjector.v1.4.c" from the zip archive linked in the thread below to be "#define MAXOFFSETS 32" instead of "#define MAXOFFSETS 28" and recompile the program.
I have not yet tested it, so I do not know whether this works or just bricks your phone, so USE THIS ON YOUR OWN RISK.
If you want to test this for me, but do not want to compile the program yourself, you can flash my "beta-test" version linked below. Follow the instructions from the original thread above. Remember to backup your current LOGO partition.
Note to moderators:
I know that this should rather belong into the development section, but I do not yet have enough posts to post there, so I put it in here. Sorry about that but I do not want to randomly spam other threads to get the 10 responses needed.
Click to expand...
Click to collapse
Thanks. I put in a bit of time trying to figure this out with a 3t and git code. First: I wasn't interested in the "logo" partition exactly, but more about that "unlocked bootloader" and it's associated tag warning and timeout that comes up each boot after unlocking bootloader. I found the timeout and the text that goes on the screen here in the code (the bootable bootloader code) : ~/sandbox/oneplus3t/bootable/bootloader/lk/app/aboot/aboot.c : I even tested changing that, but there was no easy way to to "give it out" aside from as part of a custom ROM done from source.
Are we talking about the same thing? Or : are you talking about just replacing one logo partition content with another and it has nothing to do with the unlocked tag warning & timeout (5 sec.)?
Thanks.
---------- Post added at 05:06 AM ---------- Previous post was at 04:48 AM ----------
OK: I checked it out and it has nothing to do with the unlocked bootloader warning, which I'm working on as said above and have gotten rid of on my own phone (which I no longer have..). That's completely about the file I mentioned above "aboot.c" in bootable/bootloader/... tree.
But nice going anyway, -- thanks.
Nope, these are different things. I'm refering to the logo partition which stores images while the warning message is hardcoded into the bootloader which you probably cant change because it's signed by OnePlus.
Also OnePlus hasn't released their bootloader sources (I think) and the bootloader in the source tree is just the generic base for all quallcomm bootloaders (aka Little Kernel).
So sorry to disappoint you but you won't be able to remove that warning with LOGO editing.
Jo_Jo_2000 said:
Nope, these are different things. I'm refering to the logo partition which stores images while the warning message is hardcoded into the bootloader which you probably cant change because it's signed by OnePlus.
Also OnePlus hasn't released their bootloader sources (I think) and the bootloader in the source tree is just the generic base for all quallcomm bootloaders (aka Little Kernel).
So sorry to disappoint you but you won't be able to remove that warning with LOGO editing.
Click to expand...
Click to collapse
So the rom I built from their 3t sources must have used boot.img as a "prebuilt"? Does that sound right? I guess I could unpack boot.img and figure out how to get rid of the delay with a binary overwrite. (I wouldn't look forward to testing that ;
It's in the bootLOADER which is not a prebuilt nor a thing you build yourself when you build a custom rom. Its build, maintained and signed by OnePlus so they and only they can alter the bootloader (I think so, maybe "flashing unlock_critical" does the trick here, but dont try it or you will irreversibly hard brick your phone).
Also good luck with a binary overwrite, I hope you know ARM assembly.
To get that clear, the warning message has got _nothing_ to do with boot.img, they are two completely different things and no matter what you do with a boot.img, you won't get rid of that warning!
I know there's a flashable .bin that gets rid of that exact same unlocked bootloader msg and delay on the moto x pure 2015 (XT1575). Maybe it's similar. I've attached the file.
I doubt that this will work... the original logo.bin is about 16mb and even if I just repack it with the original images it's only about 700kb
noahvt said:
I doubt that this will work... the original logo.bin is about 16mb and even if I just repack it with the original images it's only about 700kb
Click to expand...
Click to collapse
Good that you are concerned and looking for errors I might have made!
However I am very certain that the file indeed is only .7 MB large because:
1. That program (without mods) works on the oneplus 3, whose file is also only about that large
2. The first 786432 bytes (the size of the recoded file) of the original LOGO.bin dump are identical
3. the remaining 16 mb are zeroed out and contain no data
4. the program produces correct images
I would be happy to try it out, because I do not have access to a PC where I can run the MSM Downloader in case I brick things!
Greetings.
g96818 said:
I know there's a flashable .bin that gets rid of that exact same unlocked bootloader msg and delay on the moto x pure 2015 (XT1575). Maybe it's similar. I've attached the file.
Click to expand...
Click to collapse
The OnePlus 3t's warning is hardcoded into the bootloader, so unless you find a bug in sbl1 or break rsa you won't get around that.
I compiled this and got it working, but can't share for the same reasons as OP.
If anyone wants a custom logo, PM me the picture and I'll make an image file for you
prmcmanus said:
I compiled this and got it working, but can't share for the same reasons as OP.
If anyone wants a custom logo, PM me the picture and I'll make an image file for you
Click to expand...
Click to collapse
So you can use this without bricking your phone?
Jo_Jo_2000 said:
So you can use this without bricking your phone?
Click to expand...
Click to collapse
Yep, working on mine
Hey, @prmcmanus... PM'ed you!
@Ker~Man did you get my reply? It doesn't look like Quick Reply works :-S
prmcmanus said:
@Ker~Man did you get my reply? It doesn't look like Quick Reply works :-S
Click to expand...
Click to collapse
I sure did, and thank you! How do I install these, though? Flash in TWRP? I'm not too keep with .bin files. Thanks again!
Ker~Man said:
I sure did, and thank you! How do I install these, though? Flash in TWRP? I'm not too keep with .bin files. Thanks again!
Click to expand...
Click to collapse
look in my opening post, I've written two methods there.
Ker~Man said:
I sure did, and thank you! How do I install these, though? Flash in TWRP? I'm not too keep with .bin files. Thanks again!
Click to expand...
Click to collapse
Put the phone in fastboot mode and flash:
Code:
fastboot flash LOGO filename.bin
Jo_Jo_2000 said:
look in my opening post, I've written two methods there.
Click to expand...
Click to collapse
That 2nd method, I didn't know you could do that in the terminal! Nice
Jo_Jo_2000 said:
Hello there,
as you may know you can change the oem splash screen on the OnePlus 3, as provided in this thread here:
That program only needs minor fixes to work with OnePlus 3T splash partitions.
Unfortunately I cannot provide a compiled program here because the original program was not published under a proper license, but I can tell you that you just need to change line 35 of the file "src/LogoInjector.v1.4.c" from the zip archive linked in the thread below to be "#define MAXOFFSETS 32" instead of "#define MAXOFFSETS 28" and recompile the program.
Click to expand...
Click to collapse
I apologize for not responding to you soon enough. When I figure out an encoding, I release the source code for the encoder and decoder that I build for a couple of reasons. And one of those reasons is so you can do like you did! And you did it right! Thanks for asking and giving a link which in my book is good enough for proper credit. Feel free to share the binary with whoever:good:
I replaced the logo injector .zip file because it created an error when executed by some people.
You can use it now.
Jo_Jo_2000 said:
I replaced the logo injector .zip file because it created an error when executed by some people.
You can use it now.
Click to expand...
Click to collapse
Does my device have to be "Critical Unlocked"? I have an unlocked bootloader but when I try "fastboot flash LOGO" I get "FAILED (remote: Partition flashing is not allowed)"
EDIT: flashing it with dd works though
I have an Alcatel Tetra running Android 8.1, June 2018 update, and I would like to root it. It was only released in September 2018, though, so there seems to be no common solution.
Some specs are:
480x854 resolution on 5" screen @ 70hz
1.1ghz MediaTek MT6739WM CPU
2gb ram
4G LTE GSM on AT&T
WIFI A/B/G/N 2.4ghz
Bluetooth 4.2 LE
Android 8.1, June 2018 update
16gb internal storage with support for 128gb sd card
GE8100 GPU
5MP front camera & 2MP back
USB 2.0 port, 3.5mm jack
Root
clcombs262 said:
I have an Alcatel Tetra running Android 8.1, June 2018 update, and I would like to root it. It was only released in September 2018, though, so there seems to be no common solution.
Some specs are:
480x854 resolution on 5" screen @ 70hz
1.1ghz MediaTek MT6739WM CPU
2gb ram
4G LTE GSM
WIFI A/B/G/N 2.4ghz
Android 8.1, June 2018 update
16gb internal storage with support for 128gb sd card
GE8100 GPU
5MP front camera & 2MP back
Click to expand...
Click to collapse
I have one also id like to root
I also have this phone. Almost cobbled together a twrp but just need the correct recovery-kernel & offset file to repack it. As it stands right now the twrp build will boot loop, but I know all the other pieces are solid ( correct resolution set, correct prop.default, fstab files, .rc files and so on) unfortunately so flash tools is useless until we can get a custom DA file that works with the Tetra. This whole process has been quite a pain lol but I'm close. If I can get it figured out I'll make a thread here upload all relevant files
Update: I'm currently using a few different RATs to pull any and all files possible while also trying to see what exploits (if any) I may be able to leverage with them. currently still lacking the recovery.fstab, but all other files needed for the ramdisk folder section of the recovery.img is set (put together the prop.default from scratch as I can't pull it from the phone). Still need all files outside of the ramdisk folder though (mostly just a proper recovery-kernel and offset, think I may be able to substitute the other files from a similar Alcatel MT6739 phone, the 3x/5058, which I have a stock firmware for). I also have the source code for the 4.4.95+ kernel that's on the Tetra, digging through it to see if I can use anything from it. If anyone has any thoughts about what could be done with all this stuff I have please feel free to share, as I could use some fresh eyes on this.
MICHAEL(SMHOS.ORG) said:
Just use magisk to root ,or ONE click root for PC is easy bro??
Click to expand...
Click to collapse
#1. There is no publicly available fw for this device as of this moment to patch with Magisk.
#2. Sp flash tool cannot currently readback or download to this phone, as the necessary DA file is unavailable. That means no way to get the boot.img or recovery.img to make magisk root/port TWRP
#3. NO ROOTING APPS WHETHER THEY BE APK OR PC BASED, WORK WHATSOEVER ON THIS PHONE, AND 80% OF THEM ARE BORDERLINE MALICIOUS (HERE'S LOOKING AT YOU KINGROOT)
#4 please kindly ****post elsewhere.
Root Alcatel Tetra
MICHAEL(SMHOS.ORG) said:
Just use magisk to root ,or ONE click root for PC is easy bro
Click to expand...
Click to collapse
I know for a fact One Click Root has no support, and Magisk is unreliable in my experience. I think I may have a way to apply a root patch, but obviously I need the patch first. I believe I can exploit the "apply update from sd card" function but haven't really tested it.
MICHAEL(SMHOS.ORG) said:
OK try it and check if any patch or so,because I use Flashing tools like Gsm alladin cracked or android adb multi tool since it support adb function for root
Click to expand...
Click to collapse
There is currently no adb exploit to gain root that works on this device. Trust me, I've tried. There is not an easy fix for this phone. The only options I see, is for someone who has access to the most recent NCK box, or Miracle thunder MT2 ( which added support for the mt6739 chip set) to dump the firmware and share It with the public, or for the Download Assistant file for this phone to be released, at which point SP flashtools can be used to dump the firmware, at which point a custom TWRP can be ported, root can be gained, and bob's your uncle. I've spent the last month going over every possible way to crack this phone open, and aside from finding/developing an as of yet unknown exploit, the only options available require a firmware dump (which currently can only be made with the 2 aforementioned box tools). I've been using every method I can think of to get a functioning TWRP without the stock recovery, with no luck yet. Ive taken every possible amount of info and files accessable from the phone using adb shells, mtk based tools, and RATs. I've got ahold of pretty much all publicly available firmwares and TWRPs for other Mt6739 phones that are already cracked, to see if I could take the files/Info and modify them to fill in the gaps and get a functional TWRP. Hasn't worked yet and while I've narrowed the reasons why down, those reasons seem to be hard blocks that could only be overcome through root access/access to the Tetras specific firmware. Which as you see is a catch 22 where you would need root to get root. I've even tried to get ahold of an ota update directly from AT&Ts cdn to try and exploit. I have the dl address but am not sure how to use it, as trying to connect to it from phone browser or PC just returns as forbidden. I'm honestly a little burnt out with it at the moment and am gonna go mess with some other phones I have and come back to this later when/if hopefully some new resources become available.
Tlr ; the easy and common solutions aren't gonna cut it, so save your breath
cthulu_rises said:
There is currently no adb exploit to gain root that works on this device. Trust me, I've tried. There is not an easy fix for this phone. The only options I see, is for someone who has access to the most recent NCK box, or Miracle thunder MT2 ( which added support for the mt6739 chip set) to dump the firmware and share It with the public, or for the Download Assistant file for this phone to be released, at which point SP flashtools can be used to dump the firmware, at which point a custom TWRP can be ported, root can be gained, and bob's your uncle. I've spent the last month going over every possible way to crack this phone open, and aside from finding/developing an as of yet unknown exploit, the only options available require a firmware dump (which currently can only be made with the 2 aforementioned box tools). I've been using every method I can think of to get a functioning TWRP without the stock recovery, with no luck yet. Ive taken every possible amount of info and files accessable from the phone using adb shells, mtk based tools, and RATs. I've got ahold of pretty much all publicly available firmwares and TWRPs for other Mt6739 phones that are already cracked, to see if I could take the files/Info and modify them to fill in the gaps and get a functional TWRP. Hasn't worked yet and while I've narrowed the reasons why down, those reasons seem to be hard blocks that could only be overcome through root access/access to the Tetras specific firmware. Which as you see is a catch 22 where you would need root to get root. I've even tried to get ahold of an ota update directly from AT&Ts cdn to try and exploit. I have the dl address but am not sure how to use it, as trying to connect to it from phone browser or PC just returns as forbidden. I'm honestly a little burnt out with it at the moment and am gonna go mess with some other phones I have and come back to this later when/if hopefully some new resources become available.
Tlr ; the easy and common solutions aren't gonna cut it, so save your breath
Click to expand...
Click to collapse
/
+1 on the no easy solutions. In theory, there is a utility built in to flash an update from an sd card from fastboot menu, or if you have an activity launcher.... exploitable, maybe?
Also, you must remember that those people are just people like you and me, with more experience. Since this phone was released September of this year, it may be awhile. So we may be on our own since the Tetra is a lower end device. I got a system dump, which I know can be used ro make firmware, but am not sure how to do so
clcombs262 said:
/
+1 on the no easy solutions. In theory, there is a utility built in to flash an update from an sd card from fastboot menu.
I got a system dump
Click to expand...
Click to collapse
Only way to use stock sideload would require you to sign the zip with the manufacturer private keys. I did pull some keys & certs from the phone but never got a chance to see if they were the proper ones.
And pls upload your system dump
Dont use this, see next post
Last post was the wrong file.
Here you'll find:
*DA file
*Auth file
*Preloader
*.mbn
*.sca
All specific for the 5041c, direct from Alcatel
https://drive.google.com/file/d/1FS0MFuoFSRlSncuUUtsZM808fqypUmue/view?usp=drivesdk
Yo OP what's up with that system dump?
cthulu_rises said:
Yo OP what's up with that system dump?
Click to expand...
Click to collapse
It ll be awhile. My ssd took a dump and died last night and I don't get paid for 2 weeks, so can't afford a new one.
That zip wasn't backed up unfortunately. So right now I have no pc
clcombs262 said:
It ll be awhile. My ssd took a dump and died last night and I don't get paid for 2 weeks, so can't afford a new one.
That zip wasn't backed up unfortunately. So right now I have no pc
Click to expand...
Click to collapse
Dang sorry to hear that brotha. Do you remember what method you used to get the system dump? I can try my hand at it
cthulu_rises said:
Dang sorry to hear that brotha. Do you remember what method you used to get the system dump? I can try my hand at it
Click to expand...
Click to collapse
See next post
cthulu_rises said:
Dang sorry to hear that brotha. Do you remember what method you used to get the system dump? I can try my hand at it
Click to expand...
Click to collapse
The primary code I used was
Code:
adb pull /system
adb pull /data
I may have used other code; I don't remember. It's been awhile.
Also, so my friends will stop asking, will you post how to root/flash recovery with what you provided? It'll be easier to link to the post then explain it 500 times, since I end up their IT guy a lot. Thanks in advance
Take the Da file, auth file, and scatter file provided and load them in the latest version of SP Flash Tool, use the readback function to dump the recovery img. If memory serves me correctly, mmcblk0p18 is the location for it. (use the scatter file to locate the begining address and the length for it). Once you have the stock recovery img, manually port twrp to it using carliv image kitchen. Then fastboot to flash twrp. If you did it right then you can boot into twrp and flash supersu or magisk for root. Make sure to boot directly into recovery after flashing, because the recovery gets replaced by stock after a normal boot
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
I would have posted more already but have no access to PC for a while. I haven't even had a chance to do this for myself yet
cthulu_rises said:
Take the Da file, auth file, and scatter file provided and load them in the latest version of SP Flash Tool, use the readback function to dump the recovery img. If memory serves me correctly, mmcblk0p18 is the location for it. (use the scatter file to locate the begining address and the length for it). Once you have the stock recovery img, manually port twrp to it using carliv image kitchen. Then fastboot to flash twrp. If you did it right then you can boot into twrp and flash supersu or magisk for root. Make sure to boot directly into recovery after flashing, because the recovery gets replaced by stock after a normal boot
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
I would have posted more already but have no access to PC for a while. I haven't even had a chance to do this for myself yet
Click to expand...
Click to collapse
I have access to a library pc, but youre not allowed to install anything. No adb or sp flash tool. Though i do have a theory about using stock recovery...
Probably wont work, but hey. YOLO. Still waiting for my ssd to be in stock
Well here's the stock ROM. Cut SP flash Tool and all its hassles out and use this. Just extract the recovery.img and port twrp, or extract boot.img and patch with magisk. Am gonna do this when I get home, I have a beater laptop I can use but no internet there, so I'll post my work the next time I can come to town and get cell service.
https://mega.nz/#!dpFmBIgI!4FXN0VYjTYSyMp608BCCDOtEVABHqOwoJPBx_OkaKrE
This zip contains the magisk patched boot.img, happy rooting!
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
RngrYogi said:
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
Click to expand...
Click to collapse
Also using your method would it require a user data wipe?
RngrYogi said:
Also using your method would it require a user data wipe?
Click to expand...
Click to collapse
yes, of course. it's like any standard boot loader unlocked. Which is why you do it first thing when you get the device.
Edit: I didn't see the question how to apply it -
just OEM unlock the device, and then
adb reboot bootloader
(wait for it too boot to boot loader)
fastboot flashing unlock
(accept unlocking voiding warranty, etc by pressing volume down and power)
fastboot flash boot <the boot.img>
Note that they don't recognize "fastboot boot" , which is my favorite way of rooting since it leaves the original image intact - and thus flashing is irreversible unless you get the stock OTA at a later time and flash it over. But this will not bring back the warranty and warnings.
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
greetings bro thanks for sharing the vbmeta.img file? didn't you use it?
few questions:
1. were did you find the stock firmware to pull the clean boot.img? Can you link it, I would like to have a backup if anything goes wrong
2. Is the patched boot.img for the North American Version?
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
morpheus______ said:
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
Click to expand...
Click to collapse
nice, thanks for the quick reply
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
On which rom you use it? Aparently its taken out from a Ianuary rom, latest being v2.32 afaik
Just whichever random firmware image I found. But you're overlooking one major thing which is - the kernel barely, if at all, changes between firmware versions . You can use this book image with any other firmware image of any date, earlier or later, and there's no reason why it wouldn't work. The Android OTA images are user mode, this is just the kernel + Ramdisk - and so are largely independent of each other. Only exception would be if there's some kernel vulnerability in that particular version of the kernel, which as far as we know now - there isn't.
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
LeonFresh said:
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
Click to expand...
Click to collapse
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Hi I just joined the TG but got banned any chance of unbanning me?
User is Indiana_Gems on TG I'm looking to change my RM7 CN to global
morpheus______ said:
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
Click to expand...
Click to collapse
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
LeonFresh said:
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
Click to expand...
Click to collapse
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
LeonFresh said:
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
Click to expand...
Click to collapse
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Morrovoker said:
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Click to expand...
Click to collapse
Not yet, I guess we just have to wait
LeonFresh said:
Not yet, I guess we just have to wait
Click to expand...
Click to collapse
any news yet i wanna switch from global to cn lol