Related
I Was Helping another member get a rom working for the 6.35 radio sapphire and thought I'd look into making cm7 run better on our new radio magics, I've had it compiling for a long time now but it was slow and laggy and several things were broken. So I concentrated on DietGingerbread.
Well I succeeded this weekend at making it run ok and everything is working as it does on any other cm7 phone install.
It has my 710 kernel with 245/528 as default. (updated kernel, added 352000 to cpu freq table)
You must have 1.76.2007 spl
You should have 6.35.16.19 radio
cwm-carz-v4.0.1.4-0820-recovery, RA's hero recovery on sapphire does not work
install the rom
install gapps (optional)
Custom MTD explained below. (optional)
________
New Sept 30
Fixed merge issue in frameworks/base, fixes settings for lockscreen and a few other quirks
2.3.7 now
cm-7.1.0-09302011-6355Sapphire
________
New Sept 28
Latest cm7 source, a few changes, unlock bubbles are nice
New kernel with many changes, it has great battery life again, only 3% drop overnight now, 40 hours 35 minutes on battery and I have 18% left still, no problems over a weeks use.
Gapps package has the new market now, the old one auto updated to the new one every time for me anyways
Everything is on Andriodspin now, nice fast servers
cm-7.1.0-09262011-6355Sapphire (I didn't wipe and it works perfectly, your mileage my vary)
--------------
Aug 20
2.3.5, CM teams updates merged and tested
New kernel
Updated power profile (not sure if it affects battery or not)
Incall ui off by default, you can enable in settings
Off animation is not on by default anymore, you can turn it on in settings (it's still buggy for me anyways, I need to rewrite the code so it isn't using gles2.0)
Led settings are back (not that a lot of you noticed it gone lol, I didn't notice either)
Many tweaks for more speed, mostly in ADW
Fast enough now that I don't even overclock at all now
I forgot to add, I fixed gles1.1, neocore now works
Finally, here is the update!
cm-7.1.0-08202011-6355Sapphire-signed
This is the gapps you should use, the minimal package that way all is updated and current from the market
gapps-gb-20110613-signed.zip
*Optional*
This is the newest recovery, 4.0.1.4,(in fastboot usb mode: fastboot flash recovery cwm-carz-v4.0.1.4-0820-recovery.img )
cwm-carz-v4.0.1.4-0820-recovery (unzip and use the fastboot binary in the zip to flash, you can not flash the zip from recovery!)
--------------
New July 10 (fixed)
This is the version I have in a post in this thread (over 350 downloads and only one issue so far)
Updated kernel with camera speed improvement (not in the previously posted rom, I'll post an update package for you guys)
Fixed audio issue after taking pictures
Recovery 4.0.0.5
Rom:
CyanogenCARZ-7.1.0-07102011-6355Sapphire-signed (todays build downloaded and tested)
gpsshim replacement for wake issue http://www.multiupload.com/DKOFY5UNR3
Kernel: (update zip for those already running the july version)(not needed for above rom)
carz-2.6.34.4-07072011-signed
Google apps:
gapps_mdpi_gb_20110613_S(go to market and update)
Recovery: (fixes a wipe issue)
carz-clockworkmod-v4.0.0.5-recovery
--------------
June 21
Updated to latest cm/aosp sources, new kernel with updated usb and audio, fastest version yet. Also 4.0.0.2 recovery is working great so far.
Testing reports are good, wipe if you have issues.
CyanogenCARZ-7.1.0-06192011-6355Sapphire-signed
Carz-Clockworkmod-4.0.0.2-recovery
gapps_mdpi_gb_20110307_S
--------------
June 08
A very stable and fast release so far
New kernel with updated usb, tethering and debug notification working now
New recovery (optional)
I did not wipe but I was coming from builds that were only 1 day old, If in doubt wipe and format system.
on off animations may or may not work for you, still looking into it
cm-CyanogenCARZ-7.1.0-06062011-6355Sapphire-signed
This is not needed for anything but testing for you guys, tethering involved rom changes also.
carz-2.6.34.2-06052011-signed (flashable zip with new kernel and modules)(modules are sqf)
Recovery coming, v3.2.0....
--------------
May 23
Many updates from both the cm team and aosp (close to RC I think)
Smoother and more responsive
Updated kernel
If you have any boot issues you have to fully wipe and format system from recovery
update-cm-CyanogenCARZ-7.1.0-05232011-6355Sapphire
MD5SUM: cf815615f72cf5df900e2f8f73b57c5d
Clockworkmod-Carz-recovery-v3.1.0.1-05-23-2011.zip (newest recovery compiled with rom)
--------------
May 14 Consider this a Nightly
No wipe update if coming from may 08 version
update-cm-CyanogenCARZ-7.1.0-05142011-6355Sapphire
p
md5sum 8f3fda6dbb4b47ac3098ab28b3f29181
--------------
May 08 Stable
Sorry about the wait, I had real life work to do, also several things quit working with the cm7.1.0, 2.3.4 update, it's all good now I believe and seems much faster, This is on a clean install without custom mtd that I tested.
update-cm-CyanogenCARZ-7.1.0-05092011-6355Sapphire for mtd use, everything else is the same as the version below
update-cm-CyanogenCARZ-7.1.0-05072011-6355Sapphire
MD5SUM 137e6ec97d0498c5097bce4e42bfe102
I also started compiling clockworkmods recovery with the rom for our devices, it has all the options plus a few I've never seen before.
Clockworkmod-Carz-recovery-v3.0.2.8-05-04-2011
It's a zip with the recovery and the fastboot binary, unzip, cd to directory and:
Code:
fastboot flash recovery Clockworkmod-Carz-recovery-v3.0.2.8-05-04-2011.img
--------------
April 24
You must wipe all for this release, I used google to save settings and apps before wiping and then used it to restore everything, works now on mtd also.
If you use seo's 2.0 recovery (as I do) you have to use fastboot to erase system, as the recovery does not. (I'm looking in to fixing it)
Code:
fastboot erase system -w
Cyanogen-CARZ-7-6355sapphire-signed
Here is a new boot mtd flasher for custom MTD, I fixed cm7 so it doesn't bind data/local/download to cache/download anymore, market fixed for good on MTD
DGB-boot-v1.5.8-CustomMTD_S
(I will have a newer compile out later today with a few changes like the kernel)
--------------
Cyanogen-7-RC4-6355Sapphire
MD5SUM
Cyanogen-7-RC4-6355Sapphire-MTD
--------------
Cyanogen-7-RC3-6355Sapphire
CM7 RC3 carz v03.27.2001.2-MTD
--------------
gapps
Limited support as I'm only pulling in cm teams changes. Enjoy! Big props to all of Cyanogenmods team.
For market to work on AutoMTD for now, open terminal
on phone
Code:
su
cp -a /dev/cache/download /cache
on comp
Code:
adb shell
su
cp -a /dev/cache/download /cache
New Nightlies
--------------
update-cm-CyanogenCARZ-7-04062011-2-NIGHTLY-DS-signed.zip
MD5SUM f005d14bd708403ff92dafba475837ff
update-cm-CyanogenCARZ-7-04062011-2-NIGHTLY-DS-signed-AutoMTD.zip
MD5SUM ce91ba7861de46e9e52bd12c8d39ecb9
I have no long movies, please check and see if they work now
--------------
update-cm-CyanogenCARZ-7-04022011-NIGHTLY-DS-signed.zip
MD5SUM
update-cm-CyanogenCARZ-7-04022011-NIGHTLY-DS-signed-AutoMTD.zip
MD5SUM
--------------
update-cm-Carz2-Cyan-7-04012011-NIGHTLY-signed.zip
MD5SUM
update-cm-Carz2-Cyan-7-04012011-NIGHTLY-signed-AutoMTD.zip
--------------
update-cm-Carz2-Cyan-7-03302011-NIGHTLY-signed.zip
MD5SUM
update-cm-Carz2-Cyan-7-03302011-NIGHTLY-signed-AutoMTD.zip
MD5SUM
Custom MTD: Please know what you are doing here, read and then read some more.
first before anything run this either in term or using adb (only "df" in term)
Code:
adb shell df
you should get something like this
Code:
[email protected]:~/androidgb/system$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98096 32 98064 0% /dev
tmpfs 98096 0 98096 0% /mnt/asec
tmpfs 98096 0 98096 0% /mnt/obb
/dev/block/mtdblock3 174080 [COLOR="Red"]139540[/COLOR] 34540 80% /system
/dev/block/mtdblock5 169728 19832 149896 12% /data
/dev/block/mtdblock4 133120 39968 93152 30% /cache
/dev/block/loop0 1024 1024 0 100% /system/lib/modules
/dev/block/loop1 4352 4352 0 100% /system/xbin
/dev/block/mmcblk0p2 468331 8226 435120 2% /sd-ext
/dev/block/vold/179:1
7216340 7148400 67940 99% /mnt/sdcard
/dev/block/vold/179:1
7216340 7148400 67940 99% /mnt/secure/asec
look at "/dev/block/mtdblock3 174080 139540 34540 80% /system"
I used "mtd 140 3" in my mtdpartmap.txt
Download DGB-recovery-v1.5.8-CustomMTD_S.zip
These instructions are from firerats thread (recommended reading material) modified a little for my use.
Install Instructions:
Download DGB-recovery-v1.5.8-CustomMTD_S.zip
Create mtdpartmap.txt and put on /sdcard/ (use 140 3) see configuration above or in Firerats thread < recomended
reboot to recovery
nandbackup
wipe (I also "fastboot erase system -w" )
flash DGB-recovery-v1.5.8-CustomMTD_S.zip
reboot to recovery ( reboot and hold Home )
wipe again
Flash any of my custom MTD roms
reboot
Click to expand...
Click to collapse
For market to work on AutoMTD for now, open terminal
on phone
Code:
su
cp -a /dev/cache/download /cache
on comp
Code:
adb shell
su
cp -a /dev/cache/download /cache
The above is what I did and I'm running fine right now,
Below is with 130 3 mtdpartmap, I trimmed some stuff out
Code:
[email protected]:~/androidgb/system$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98096 32 98064 0% /dev
tmpfs 98096 0 98096 0% /mnt/asec
tmpfs 98096 0 98096 0% /mnt/obb
/dev/block/mtdblock3 133120 131772 1348 99% /system
/dev/block/mtdblock5 340736 83740 256996 25% /data
/dev/block/loop0 1024 1024 0 100% /system/lib/modules
/dev/block/mmcblk0p2 468331 10053 433293 2% /sd-ext
/dev/block/mmcblk0p2 468331 10053 433293 2% /cache
/dev/block/mtdblock4 3072 780 2292 25% /dev/cache
/dev/block/vold/179:1
7216340 7138144 78196 99% /mnt/sdcard
/dev/block/vold/179:1
7216340 7138144 78196 99% /mnt/secure/asec
169 > 340 on data
Great job!
Thank you for all your effort. I will test it right away.
May i get your permission to post this ROM in other forum? With all the credits and with a link to these thread. Only for promoting purpose.
Unkjcr said:
Thank you for all your effort. I will test it right away.
May i get your permission to post this ROM in other forum? With all the credits and with a link to these thread. Only for promoting purpose.
Click to expand...
Click to collapse
Sure but can you wait till it gets tested out a little bit first?
carz12 said:
Sure but can you wait till it gets tested out a little bit first?
Click to expand...
Click to collapse
Sure! I was thinking in testing the ROM first before doing that. Thanks
Awesome, downloading asap
Hi Carz,
Do i need to change my SPL and recovery?
Dexreyes said:
Hi Carz,
Do i need to change my SPL and recovery?
Click to expand...
Click to collapse
Not if it's what is in your sig.
carz12 said:
Not if it's what is in your sig.
Click to expand...
Click to collapse
Thanks Carz, I'm downloading it right now, will test this, looks promising!
So far it works as any other GB ROM out there. But with 2 differences for now: It doesn´t support App2SD (i really hope you enable this feature) and... it´s faster than the others! Great job Carz!
Unkjcr said:
So far it works as any other GB ROM out there. But with 2 differences for now: It doesn´t support App2SD (i really hope you enable this feature) and... it´s faster than the others! Great job Carz!
Click to expand...
Click to collapse
Have you turned on jit yet?
Sent from my Dream/Sapphire using XDA App
i got install error, status 7 when installing this rom. Please look into this.
hellokittyr said:
i got install error, status 7 when installing this rom. Please look into this.
Click to expand...
Click to collapse
Do you have 1.76.2007 spl?
Sent from my Dream/Sapphire using XDA App
Unkjcr said:
So far it works as any other GB ROM out there. But with 2 differences for now: It doesn´t support App2SD (i really hope you enable this feature) and... it´s faster than the others! Great job Carz!
Click to expand...
Click to collapse
It supports apps2sd (native) and supports app2ext if I add the script
Sent from my Dream/Sapphire using XDA App
thx carz, testing it right now...
Just installed, replacing GBRider, so far so good, very speedy, everything seems to work.
Excellent work carz, as usual!
---
Update: seems I spoke too fast, the root portion seems to have a problem. SuperUser/Titanium don't work (exception with 'failed running exec() on SU' appear in the log
Reset your phone - it helped me -
carz - rom is very fast like 4 GB2.3 - one qestion, how about battery drain?
[email protected] said:
Just installed, replacing GBRider, so far so good, very speedy, everything seems to work.
Excellent work carz, as usual!
---
Update: seems I spoke too fast, the root portion seems to have a problem. SuperUser/Titanium don't work (exception with 'failed running exec() on SU' appear in the log
Click to expand...
Click to collapse
So far so good, are there any plans on a MTD friendly version?
orange_24 said:
Reset your phone - it helped me -
carz - rom is very fast like 4 GB2.3 - one qestion, how about battery drain?
Click to expand...
Click to collapse
Em, could you specify what do you mean by 'reset' ? Wiping? Rebooting?
I started with a wipe, and rebooted since... Didn't help.
install Completed but reboot to recovery ?
Notice (4/16/14): I'm no longer here. I've said "goodbye" to AT&T and their locked bootloader schemes. I'm voting with my wallet - I've sold my I337 and switched to T-Mobile. My apologies to the community, but you're now on your own here.
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have is, "Why did you release this - why wouldn't I just use <insert name here>'s stock rom?" It's simple: every other rom in this forum (at this time) has been modified from the original stock rom - whether they've added root, de-odexed it, debloated it, or otherwise. Because the Unadulterated rom is 100% stock (with stock kernel), it is possible for other developers to flash this rom and use it as a platform for attempting to find a root method for the MF3 users out there already. Plus, I like to make my own modifications from a stock base.
UPDATE (8-1-13): a root method has been found for MF3. See thread here. This ROM's purpose has been fulfilled, but your are still welcome to use it, of course!
UPDATE: The MF3 Odin files have been uploaded by @Shockndrop over in his thread here. Remember that the Odin files will flash your bootloader to MF3 (if you allow them), so be careful out there.
Rest assured, this rom will not update your bootloaders, it will not break your custom recovery, and it won't flash your modems. Like most roms, it will simply replace your /system and flash a Kernel. It's also scripted to wipe cache and dalvik for you. It will not wipe your /data partition - you might want to do so if you run into problems, especially when coming from other roms.
Next, you might ask, "How can you say this is 100% stock? How did you construct it?" I'll hide nothing from you - you can build it yourself if you'd like. Here's how I did it:
Rooted with motochopper
Installed TWRP 2.6.0.0
Wiped data & cache
Odin to MDL stock
Allow one full reboot:
Boot script runs (installs CSC - this is REQUIRED for the MF3 update to patch correctly)
Clears up any SysScope flags, etc. that may have persisted from previous rom or root.
"Temporary Root" using motochopper:
Code:
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
NOTE: Possible outcomes of temporary root:
Failure
Success, motochopper exploit hangs, device spontaneously reboots
Success, immediate return to prompt, but adb shell is still not root (indicated by $ prompt)
Success, immediate return to prompt, adb shell is root (indicated by # prompt)
Repeat as needed (usually only twice or so?)
NOTE: Don't both trying to run su. It isn't installed. We're just relying on motochopper to give us a temporary adb root shell.
From adb root shell, installed TWRP recovery:
Code:
dd if=/sdcard/openrecovery-twrp-2.6.0.0-jflteatt.img of=/dev/block/mmcblk0p21
Rebooted, checked to be sure system status is still Official. Note that at this point, we've got a 100% stock MDL rom, without root, but with a custom recovery. Woot.
Rebooted into TWRP, installed custom-neutered OTA update (mf3-sys-only.zip), which only does the following:
Verifies all system files
Removes "unneeded" files (as determined by AT&T, not me)
Patches files
Copies new files
Sets permissions
Patches build.prop
Wiped data & cache for good measure
Booted phone, verified ROM works okay, system status = official. Rebooted, checked Odin Mode:
Code:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Booted back to TWRP to begin pulling dumps
... Now, on to the good stuff!
ROM Install Instructions:
Download mf3-stock-rom.zip and place it on your internal sdcard.
Make a nandroid backup of your existing system, data, cache, and anything else you deem important (everything!).
Flash/install the zip using your favorite custom recovery. This part should take several minutes - the file is huge!
Optionally, flash any additional Add-ons that you want (e.g. SuperSU for root)
Optionally, flash a custom kernel (use instructions from the kernel's author!). Note that some custom kernels will need you to flash Loki-Doki. The included kernel does not require Loki patching! It is 100% stock, and your system will accept it as-is.
Optionally, wipe /data. You can skip this, but if you get a ton of force-closes or extreme problems, this would be one of the first troubleshooting steps.
Reboot, and enjoy!
Click to expand...
Click to collapse
Important Recommendation:
You are advised to disable the OTA update applications! If AT&T/Samsung release a new OTA update (beyond MF3), it is theoretically possible to download and install it while using this rom! Accepting such an update could do just as much damage as the original MF3 update did. You can easily disable OTA updates from a root ADB shell using the following commands:
Code:
pm disable com.wssyncmldm
pm disable com.LocalFota
pm disable com.sec.android.fwupgrade
You could also use Titanium Backup Pro to accomplish the same thing. I will later look into the possibility of disabling these using a flashable Add-on zip that otherwise keeps your system as stock as possible.
Known Bugs:
If you do not flash a custom kernel, you will lose WiFi. The WiFi in the MF3 Kernel is expecting the MF3 bootloaders, which we aren't flashing. Therefore it breaks.
If you happen to have the MF3 modem/baseband installed, your WiFi might work, but your sound may stop working completely. This is also a result of not having MF3 bootloaders. A custom Kernel should fix this too.
If you use the "remove-SysScope" Add-on, be careful of any other mods that may poke around with SecSettings.apk - these are rare, but there's some risk of conflict here.
With the custom kernel I installed, I frequently received the "The device has detected an application attempting..." message. This can be pinpointed to the KNOX agent, and can be fixed a different ways (your choice!):
I found this post to be very helpful.
You can also try using the command pm disable com.sec.knox.seandroid from a root ADB shell. This just freezes the app. Personally, I used this method.
@jeboo also mentioned that the KNOXAgent.apk can be patched using smali/baksmali. Check out his post about it.
Also with the kernel I installed, there was a bug regarding updating the camera firmware. I was forced to restore the stock kernel temporarily, open the camera app to update the camera firmware, and then re-flash the custom kernel. The original MF3 kernel is included in the Add-ons.
Any other bugs are likely straight from AT&T/Samsung, otherwise they could be from your custom kernel, if you flashed one.
Be sure to make good backups of everything, and be prepared to use Odin back to stock. One member has reported that after flashing away from this rom to any other rom/kernel, their SIM card would not work until they used Odin to return to stock. After Odin, it worked fine.
It seems most custom kernels are expecting you to have an MDL baseband. Some people are reporting strange issues (such as problems with video streaming) when using MF3 modems and their choice of custom kernels. Check out File #11 for various modems, NON-HLOS modems, and kernels.
Custom Kernels:
Here's a list of custom kernels that are known-working with this rom. Please feel free to test and report other working kernels, and I will gladly add them to the list!
@jeboo's Kernel - built for @shoman94's SHOstock rom. Available in post #3 of their thread.
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me. It appears that the kernels in their thread require Loki-Doki to be flashed after flashing the kernels. However, the one that I downloaded came from here: http://d-h.st/WVs and it was pre-patched for the I337.
@Jamison904's Infamous Kernel works really well, it seems. It also has BusyBox v1.19.3. I'm currently using v4.0, but there are newer versions available on his Dev-Host folder. These are for the M919, so flash Loki-Doki afterwards if you're on I337!
Downloads:
I've provided the rom in several different formats. When I last tested the odin-flashable tarballs, they did not work for me (due to signatures, etc). However, I'm still providing these for a few XDA members who will be testing them out on their semi-bricked devices. Additionally, someone might be able to get these signed somehow, and I'll leave this hanging out there as an invitation.
File #1 - mf3-stock-rom.zip - CWM/TWRP-Flashable ROM .zip file - created by hand (you are welcome to dissect it if you'd like - take a look inside the updater-script)
Files #2-#7 (individual image files and odin-flashables):
File #2 - system.img.ext4 - EXT4 format copy of the System partition - pulled using make_ext4fs in TWRP:
Used fdisk to obtain partition size:
Code:
# fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 2894 MB, 2894069760 bytes
4 heads, 16 sectors/track, 88320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
Dumped the partition:
Code:
# make_ext4fs -s -l 2894069760 -a system /sdcard/system.img.ext4 /system
Creating filesystem with parameters:
Size: 2894069760
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 11040
Label:
Blocks: 706560
Block groups: 22
Reserved block group size: 175
Created filesystem with 3192/176704 inodes and 584765/706560 blocks
File #3 - system.img - Binary copy of the System Partition - pulled using dd:
This was much easier to create:
Code:
# dd if=/dev/block/mmcblk0p16 of=/sdcard/system.img bs=4096
File #4 - boot.img - Kernel - pulled from the OTA update file
File #5 - mf3-sys-boot.tar.md5 - "Odin-flashable" tarball - created without any modification:
Using a Linux PC or Cygwin, executed the following:
Code:
$ tar -H ustar -c system.img.ext4 boot.img > mf3-sys-boot.tar
$ md5sum -t mf3-sys-boot.tar >> mf3-sys-boot.tar
$ mv mf3-sys-boot.tar mf3-sys-boot.tar.md5
File #6 - mf3-sys-boot-sgs4ext4fs.tar.md5 - "Odin-flashable" tarball - "bloated" with Chainfire's sgs4ext4fs
Using a Linux PC (I used Ubuntu 13.04 64bit - couldn't get the win32 version to process the file entirely):
Code:
$ mv ./sgs4ext4fs.linux.amd64 ./sgs4ext4fs
$ sudo chmod 755 ./sgs4ext4fs
$ mv system.img.ext4 system.img.ext4.orig
$ ./sgs4ext4fs --bloat system.img.ext4.orig system.img.ext4
Optionally, you can use the "--list" option to view the file before and after the bloating. Once complete, pack it up in a tarball again.
File #7 - mf3-factoryfs.tar.md5 - "Odin-flashable" tarball - created using the system.img instead:
Using a Linux PC or Cygwin, executed the following:
Code:
$ mv system.img factoryfs.img
$ tar -H ustar -c factoryfs.img boot.img > mf3-factoryfs.tar
$ md5sum -t mf3-factoryfs.tar >> mf3-factoryfs.tar
$ mv mf3-factoryfs.tar mf3-factoryfs.tar.md5
Files #8-#11 (Add-ons!):
File #8 - UPDATE-SuperSU-v1.41.zip - ROOT! Flash this to root your new MF3 rom!
Original is found on Chainfire's website.
File #9 - remove-SysScope.zip - Want to stay "Official", even though you rooted? Flash this! It will remove SysScope and customize your SecSettings.apk to not check for SysScope anymore. Must be flashed before first boot, otherwise you'll just be stuck with a "custom" status until you remove it by some other means.
File #10 - mf3-kernel-only.zip - Want to quickly flash back to the MF3 stock Kernel again? Flash this. No need to use Loki-Doki after flashing this - the I337 will accept this just fine and boot.
File #11 - all-kernel-modem-apnhlos.zip - My personal collection of flashable .zip's of all available versions of the stock kernel, stock modem, and stock NON-HLOS modem for the I337 - including MDB, MDL, MF3. Unzip this file first, and flash individual partitions/versions in whatever combination you want.
Disclaimers, etc.:
I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other devices, I can't guarantee anything!
You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.
If you appreciate my work, please use the THANKS button below to let me know!
reserved...
First .. ..... Hey guess u got ur phone up and running huh ?
Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748
as expected...
Aou said:
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have
.......
[*]I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other device, I can't guarantee anything!
[*]You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
[*]I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.[/list]
If you appreciate my work, please use the THANKS button below to let me know!
Click to expand...
Click to collapse
The result was what was expected.
Keeping my fingers crossed for other solutions...
iB4STiD said:
First .. ..... Hey guess u got ur phone up and running huh ?
Click to expand...
Click to collapse
Nope! Ended up needing to replace it, unfortunately. The original is a 100% hard brick. It won't even take the MF3 firmware via JTAG.
jeboo said:
Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748
Click to expand...
Click to collapse
Awesome - thanks! I'll add that to the list of options. Also, thanks again for your awesome Kernel. v1.4 is exactly what I need for my phone.
SaltyFoam said:
The result was what was expected.
Keeping my fingers crossed for other solutions...
Click to expand...
Click to collapse
This is really unfortunate, but somewhat expected (as you've said). Have you tried the Odin-flooding again (even with the MDL or MF3 Recovery) yet? That was a very interesting accidental discovery you made. I'm going to have to try that myself too! It might have been a fluke, but still worth investigating.
As an update: The last file (mf3-factoryfs.tar.md5) has finished uploading, so I'm adding the link to the OP now.
FINALLY, someone else that respects untouched firmware. Glad to see this.
The odin flooding is not working at this point.
apparently one of the features of the new odin mode (aboot?) is that once it gets the 'failed auth' it stops responding to further pushes. It does not even allow the connection to be setup until a power down and restart.
As you can see in the other thread I submitted a warranty claim and they are replacing the device: as I have no backup device and a family that needs to get in touch with me (i.e. my wife and mother scolding me for not having a phone) I ran out of time...
I still have a few days with the old device before the replacement arrives...
I any case I am off to work.
If anyone wants to help create a flashable-zip that would disable the OTA updates without touching /system, I'm working on it here:
http://forum.xda-developers.com/showthread.php?t=2379517
I just need someone to write something up in a bash script that will make modifications to a file in /data. Should work without rooting the system.
Jah0n said:
FINALLY, someone else that respects untouched firmware. Glad to see this.
Click to expand...
Click to collapse
One thing I've seen in many "stock" roms is: "Completely stock, except for this.... and this.... and this mod I made here.... and this...."
-_-
I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?
We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!
mocsab said:
I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?
Click to expand...
Click to collapse
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?
Jah0n said:
We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!
Click to expand...
Click to collapse
Awesome! If the kernel turns out alright, we could add it to the list in the OP.
Aou said:
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?
Click to expand...
Click to collapse
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -
mocsab said:
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -
Click to expand...
Click to collapse
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!
Aou said:
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!
Click to expand...
Click to collapse
The kernel lies in a separate partition but twrp wipes it away by default so you'd have to unmount the boot partition
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Is boot.img a compressed file?
jortex said:
Is boot.img a compressed file?
Click to expand...
Click to collapse
I did not compress it at all. However it is not a full 10MB either. It's the exact file that came from the MF3 update package. The way that the OTA update .zip installs it is by doing this:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
If you need a full 10MB partition dump (i.e. using dd or a nandroid), I can upload those if you need them for any reason.
UPDATE: I just did a binary comparison of the boot.img that came from the OTA .zip (the one I uploaded), and a nandroid backup I made. It was 100% identical, except the nandroid was padded with zeros at the end (a couple megabytes of zeros...)
Added another kernel to the list:
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me.
Testers wanted: Anyone who uses this method, let me know if you can access stock recovery after this method.
Summery
Thanks to the amazing work by our active member @bibikalka, a method was found to unbrick these devices Thread link here. The method he found was slightly tedious for some people, so I've decided to put together a Linux iso that you can boot into on your computer with everything you need to get your device running again. It uses the same methods proposed but makes things easier. This comes with all the necessary drivers, scripts to do everything you need, all the img files needed to flash, a hex editor for advanced users, and more. Before the scripts included in this OS, determining the option (A, B, or C) to take in order to unbrick the device required .part files to be evaluated manually. Now with the custom script, it can quickly evaluate what option to take.
Video Instructions
Brief Instructions
1. Download the Linux iso:
Linux ISO
2. Burn the iso to a USB drive or cd
3. Boot into the operating system
4. Type "root" at the login prompt
5. Right click on the desktop and choose file manager. Go to "aftv2-tools" folder
6. Right click on file manager and press "open in terminal"
7. From device turned off, enter command "./handshake.py", then plug in device. You may need to do this a couple times to get a connection. Try pressing volume keys & power etc to get it connected. See video if you have problems
8. After handshake is complete, run "./reader.sh"
9. After all addresses are read in, run "./determineOption.sh". You should get back a result of A, B, or C
10. Depending on the option returned (A,B,or C), run "./readerSpecialOptionA.sh", "./readerSpecialOptionB.sh", or "./readerSpecialOptionC.sh". This is an optional step but may be useful if you want to back up part files or their were no options available. Back up part files to a usb drive if you want to be safe.
11. Now the actual unbricking. Run "./unbrickOptionA.sh", "./unbrickOptionB.sh", or "./unbrickOptionA.sh" depending on your option. This can take about 40 minutes
12. hold volume up and run "./complete.sh" at the same time to get into TWRP
13. boot into your default operating system on your computer
BE VERY CAREFUL FROM NOW ON
13. We will be installing Fire OS 5.3.1. If you are not installing this ROM, make sure you know what you are doing. Download the ROM:
update-kindle-20.5.5.2_user_552153420.bin
14. Download 5.4.1_1133_stock_recovery_uboot.zip: 5.4.1_1133_stock_recovery_uboot.zip. Without this you could turn your device into a paperweight. This installs stock recovery and a uboot version that MUST be installed. This file was taken from the thread here: how-to-upgrade-to-lollipop-root-gapps
15. Rename the ROM extension from .bin to .zip
16. Transfer the two files to the Fire
17. Do a factory reset. Flash the ROM and uboot&recovery file
18. Reboot! Your device should now be working. It will take about 15 mins to boot up.
Big thanks to @bibikalka for helping work everything out and for the initial unbrick method.
Edit 10/13/21: Fixed Google Drive Link
Linux ISO Changelog
Updated 10/5/16:
*Optomized scripts
*Added "complete.sh" This reboots the device
Updated 9/27/16:
*Added script to auto-detect which unbrick option to use (determineOption.sh)
*Added scripts to write img files to correct addresses ( unbrickOptionA.sh, unbrickOptionB.sh, and unbrickOptionC.sh)
*Added scripts to read in and label part files (readerSpecialOptionA.sh, readerSpecialOptionB.sh, and readerSpecialOptionC.sh)
*Nemo open in terminal fixed
*.part files set to open with ghex by default
Updated 9/24/16:
*Nemo as default file manager
*Updated html page with instructions from forum
well, after seriously struggling with the parent thread mentioned in the OP I've managed to get to TWRP & am just waiting for my win10 machine to install it's updates before attempting to adb push the uboot & zip files for installation back to fireOS.
feels great to see the screen displaying something other than the looping amazon logo after months of frustration. I do not have the words to express my gratitude for @powerpoint45 for an excellent & well thought through tool and walkthrough. special mention also goes out to @bibikalka
gascomm said:
well, after seriously struggling with the parent thread mentioned in the OP I've managed to get to TWRP & am just waiting for my win10 machine to install it's updates before attempting to adb push the uboot & zip files for installation back to fireOS.
feels great to see the screen displaying something other than the looping amazon logo after months of frustration. I do not have the words to express my gratitude for @powerpoint45 for an excellent & well thought through tool and walkthrough. special mention also goes out to @bibikalka
Click to expand...
Click to collapse
great to hear! I hope everything works for you! After you get everything done, can you check if you can get into recovery.
after flashing both zips & rebooting I've now got my working fire (OS 5.3.1.0) back. thank you Mr PowerPoint!
i tried rebooting to recovery & it now takes me to the stock amazon recovery not TWRP..... which is unfortunate.
I did get asked if I wanted to install SuperUser which was a no-brainer YES. although I'm staying offline until I identify a functional (fast) flavour of android to flash. suggestions welcome.
gascomm said:
after flashing both zips & rebooting I've now got my working fire (OS 5.3.1.0) back. thank you Mr PowerPoint!
i be tried rebooting to recovery & it now takes me to the stock amazon recovery not TWRP..... which is unfortunate.
I did get asked if I wanted to install SuperUser which was a no-brainer YES. although I'm staying offline until I identify a functional (fast) flavour of android to flash. suggestions welcome.
Click to expand...
Click to collapse
Good to hear everything is working. Ya TWRP does not work with 5.x bootloader. Good to hear you can get into stock recovery because I had some incidents where I could not get into it. Thanks for responding. The only custom ROM ATM is CM13.
powerpoint45 said:
The only custom ROM ATM is CM13.
Click to expand...
Click to collapse
sorry to trouble you again but do you know where I can find a guide/walkthrough of how to root via adb & install twrp or cwm to allow flashing of a rom & gapps..
I can only find the kingroot method & the CM11 rom discussion. where might I find the CM13 you mentioned?
I have searched fruitlessly. I guess I just need a little guidance to avoid running straight into another brick.
cheers.
gascomm said:
sorry to trouble you again but do you know where I can find a guide/walkthrough of how to root via adb & install twrp or cwm to allow flashing of a rom & gapps..
I can only find the kingroot method & the CM11 rom discussion. where might I find the CM13 you mentioned?
I have searched fruitlessly. I guess I just need a little guidance to avoid running straight into another brick.
cheers.
Click to expand...
Click to collapse
I meant to say CM11. This guide is probably one of the best http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950/page1
This is a bit older one: http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351/page1
In order to have TWRP, you must have a 4.x bootloader so CM11 would work with it.
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
PRInCEI7 said:
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
Click to expand...
Click to collapse
yes you should be fine doing that
Unfortunately, did not respond
I worked
MacBook-Air-2:ROOT IP$ ./handshake.py
Waiting for preloader...
Found port = /dev/cu.usbmodem1420
Handshake complete!
In the second step does not respond to the order ./reader.sh
Also tried
/.read_mmc.py 0x0000000 0x1000 0x0000000.part
Does not respond
By the way tried way on more than one device
And tried through the system Max os x and the system arch-custom-firehd67-unbrick100516.iso did not work and also the same result
MY device Amazon Fire HD 6 version 5.3.1 All functions work, but I need to work downgrade to 4.5.3
Is there a solution to my problem
[/SIZE]
@powerpoint45 thanks for the pointers. I am now the proud owned of an hd6 booting straight into cm11 & it's been well worth the wait. I am forever in your digital debt.
gascomm said:
@powerpoint45 thanks for the pointers. I am now the proud owned of an hd6 booting straight into cm11 & it's been well worth the wait. I am forever in your digital debt.
Click to expand...
Click to collapse
sweet!!!
PRInCEI7 said:
Unfortunately, did not respond
I worked
MacBook-Air-2:ROOT IP$ ./handshake.py
Waiting for preloader...
Found port = /dev/cu.usbmodem1420
Handshake complete!
In the second step does not respond to the order ./reader.sh
Also tried
/.read_mmc.py 0x0000000 0x1000 0x0000000.part
Does not respond
By the way tried way on more than one device
And tried through the system Max os x and the system arch-custom-firehd67-unbrick100516.iso did not work and also the same result
MY device Amazon Fire HD 6 version 5.3.1 All functions work, but I need to work downgrade to 4.5.3
Is there a solution to my problem
[/SIZE]
Click to expand...
Click to collapse
I am also getting the same results with my HD 7 4th gen. The handshake completes just fine, but the reader just hangs. When I'm in recovery, I get errors saying the /cache folder failed to mount. I'm thinking the memory is corrupt and there is no way to fix this.
nai1ed said:
I am also getting the same results with my HD 7 4th gen. The handshake completes just fine, but the reader just hangs. When I'm in recovery, I get errors saying the /cache folder failed to mount. I'm thinking the memory is corrupt and there is no way to fix this.
Click to expand...
Click to collapse
Unfortunately it appears that with the latest bootloader on the latest Amazon update that they have disabled these commands (such as reading and writing). Unfortunately if you can't get into recovery with (vol+ & power) then it is currently unrecoverable. Best option for an unrecoverable device would be to buy another motherboard from eBay or some place. They are pretty cheap and easy to replace. I've had to do it a couple times now.
Confused
First you say it should be OK to downgrade:
powerpoint45 said:
PRInCEI7 said:
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
Click to expand...
Click to collapse
yes you should be fine doing that
Click to expand...
Click to collapse
Although, it's unclear how, since reports indicate that sideloading older
firmware bricks the device (or, does that only apply to 5.x?).
Then, we learn that the preloader trick (from aftv2-tools) doesn't work anymore:
Code:
[[email protected] aftv2-tools]# ./handshake.py
Waiting for preloader...
Found port = /dev/ttyACM0
Handshake complete!
[[email protected] aftv2-tools]# ./reader.sh
^CTraceback (most recent call last):
File "./read_mmc.py", line 355, in <module>
if msdc_dma_status():
File "./read_mmc.py", line 146, in msdc_dma_status
return False if sdr_read32(MSDC_CFG) & MSDC_CFG_PIO else True
File "./read_mmc.py", line 82, in sdr_read32
check(dev.read(2), b'\x00\x00') # arg check
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 450, in read
ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout)
KeyboardInterrupt
^CTraceback (most recent call last):
File "./read_mmc.py", line 355, in <module>
if msdc_dma_status():
File "./read_mmc.py", line 146, in msdc_dma_status
return False if sdr_read32(MSDC_CFG) & MSDC_CFG_PIO else True
File "./read_mmc.py", line 82, in sdr_read32
check(dev.read(2), b'\x00\x00') # arg check
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 450, in read
ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout)
KeyboardInterrupt
^Z
[1]+ Stopped ./reader.sh
[[email protected] aftv2-tools]# kill %1
[[email protected] aftv2-tools]#
[1]+ Terminated ./reader.sh
[[email protected] aftv2-tools]#
The above is for a 4th gen HD7 with this device showing in 'lsusb':
Code:
Bus 001 Device 006: ID 0e8d:3000 MediaTek Inc.
powerpoint45 said:
Unfortunately it appears that with the latest bootloader on the latest Amazon update that they have disabled these commands (such as reading and writing). Unfortunately if you can't get into recovery with (vol+ & power) then it is currently unrecoverable. Best option for an unrecoverable device would be to buy another motherboard from eBay or some place. They are pretty cheap and easy to replace. I've had to do it a couple times now.
Click to expand...
Click to collapse
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader? [Please excuse my ignorance, but would this be handled
by UBOOT, TEE1, or some other component?])
So, what's the current best option for 5.3.1?
---------- Post added at 11:23 ---------- Previous post was at 10:58 ----------
draxie said:
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader?
Click to expand...
Click to collapse
OK. So, I found this post by @zeroepoch,
which makes it very clear that said exercise has been performed for the AFTV2...
No reason to believe that this would be different for the Fire HD7...
draxie said:
First you say it should be OK to downgrade:
Although, it's unclear how, since reports indicate that sideloading older
firmware bricks the device (or, does that only apply to 5.x?).
Then, we learn that the preloader trick (from aftv2-tools) doesn't work anymore:
The above is for a 4th gen HD7 with this device showing in 'lsusb':
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader? [Please excuse my ignorance, but would this be handled
by UBOOT, TEE1, or some other component?])
So, what's the current best option for 5.3.1?
---------- Post added at 11:23 ---------- Previous post was at 10:58 ----------
OK. So, I found this post by @zeroepoch,
which makes it very clear that said exercise has been performed for the AFTV2...
No reason to believe that this would be different for the Fire HD7...
Click to expand...
Click to collapse
My understanding is that you only need to worry about bricking if You are downgrading to another lollypop ROM. We found out that the device has a fuse that is set in later lollypop ROMs where it will check against the current version. But this check only seems to be on lollipop ROM's. As for the aftv2 protocol, you might be right but I don't know enough about that yet to know. Currently we have no unbrick method for latest bootloader. If you can get into recovery then you could sideload but most can't get into recovery during brick.
I've followed the steps but not into twrp, only screen amazon and reset. I'm not good at English
error trying to unbrick hd6
[[email protected] aftv2-tools]# ./complete.sh
1: 0xd1
4: 0x00 0x00 0x00 0x00
4: 0x00 0x00 0x00 0x01
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 468, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./read32.py", line 69, in <module>
ret = read32(addr, size)
File "./read32.py", line 45, in read32
print_hex_byte(dev.read(2)) # status
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 475, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
[[email protected] aftv2-tools]#
kingwill101 said:
[[email protected] aftv2-tools]# ./complete.sh
1: 0xd1
4: 0x00 0x00 0x00 0x00
4: 0x00 0x00 0x00 0x01
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 468, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./read32.py", line 69, in <module>
ret = read32(addr, size)
File "./read32.py", line 45, in read32
print_hex_byte(dev.read(2)) # status
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 475, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
[[email protected] aftv2-tools]#
Click to expand...
Click to collapse
You are on any version.
You can access to recovery now
Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 16.0 for the ZTE Blade S6 aka P839f30.
This is the first alpha release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable pico).
Click to expand...
Click to collapse
Changelog:
25.05.2021 - new release:
los security patch level 05.05.2021
revert some kernel changes from the last release
add some cpu governors and cpu hotplug
now with Boeffla WakeLock Blocker and other things
wireguard kernel support
22.12.2019 - 1st beta release:
los security patch level 05.12.
kernel supports EU device variant
add autosmp hotplug
add cpu governors blu_active, darkness, lionfish and relaxed
Revert CwMcu sensor driver from SU6 kernel release
24.10.2019 - 2nd alpha release:
los security patch level 05.10.
CwMcu sensor driver from SU6 kernel release, with wake lock disabled
wifi mac is loaded anyway, remove the loading in the wifi driver
give bluetooth a null mac address, to overcome force close error
kang gps from oppo
04.10.2019 - 1st alpha release:
los security patch level 05.09.
initial release of pie
Click to expand...
Click to collapse
Downloads
new release - 25.05.2021:
Google Drive.
first beta release - 22.12.2019:
Google Drive or here.
second alpha release - 24.10.2019:
Google Drive or here.
first alpha release - 04.10.2019:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Click to expand...
Click to collapse
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
*PacMM79
*LineageOS team
*many others
XDA:DevDB Information
Unofficial LineageOS 16.0 [PQ3A.190801.002] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS 16.0
Version Information
Status: Beta
Current Beta Version: 20191213
Beta Release Date: 2019-12-22
Created 2019-10-04
Last Updated 2019-12-22
many thanks for the new version, i will tested later :good: :highfive:
Hello, works on my ZTE Blade S6 Plus (p839f50)
but only with a fixed updater-script
from Folder: lineage-16.0-20191002-UNOFFICIAL-p839f30.zip\META-INF\com\google\android
the bold text must delete and than save the file
after the start my phone , i have a error message with bluetooth is deactivated
updater-script - original
https://filehorst.de/d/crqjwnjI
updater-script - fixed
https://filehorst.de/d/cbmctorj
new update is in the op.
just small changes and updated security patch level.
Anybody tested with EU device?
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Gtz
Kurt
Kurt Krummbein said:
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Click to expand...
Click to collapse
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt
Kurt Krummbein said:
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt
Click to expand...
Click to collapse
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.
lightwars said:
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.
Click to expand...
Click to collapse
Hi!
Well, i loaded the def's and config's into WinMerge and did a compare ... in the def's there are some different addresses, but i have now clue what the meaning of that all is :angel:. The config files look like beeing from different kernel versions, there are some options which don't exist in both, one is modularised, the other is not ... all in all quite strange.
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Cheers
Kurt
P.S.: one thing i forgot to mention ... i coulnd't find the "OEM unlock" swich in the stock system anywhere and the bootloader seems to be quite dumb, many commands from fastboot just end in a "command unknown", perhaps there's something left to do on my side (tweak in build.prop etc ... googleed for it no result ).
Kurt Krummbein said:
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Click to expand...
Click to collapse
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I can think of two things: There is some flag in the kernel source which is called download_mode. I have seen that some devices have different default values! At the moment the value is 0, devices like the ones from bq with msm8916/msm8939 used this too, but devices from oppo with msm8939 uses a value of 1 as default. We can try this one.
Or there is a mask, which defines the restart reason so to speak says the device which mode to boot to. Here we have some differences in the meaning of the bits, a different bit shifting is used.
I can not really think that one of these causes your device to boot into download mode, because the recovery uses the same kernel on both region variants...
lightwars said:
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I'll give that one a try .
Hope my device is not "going over the Wupper" LOL (this one has to come somewhen ...)
Click to expand...
Click to collapse
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt
Kurt Krummbein said:
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt
Click to expand...
Click to collapse
It is okay to do some unusual testings. I was doing this sort of things also, back then.
I'm not sure I get you, when you write about AS keys. Do you mean the fingerprint in the build.prop? I think I used the ones from the eu version. Maybe they build in some kind of kernel version check inside the bootloader, but only for the eu and other versions.
The cause is, that android needs an advanced kernel, so we can not use the stock kernel to boot newer android version like nougat, oreo or pie.
Sorry, I can not be of much help here, because I do not have a device with eu or some other region version. But we can try do some changes, if you like to do some more testing and maybe get something like a log, last_kmseg or ramoops. We should look to activate some of them.
Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.
lightwars said:
Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.
Click to expand...
Click to collapse
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt
Kurt Krummbein said:
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt
Click to expand...
Click to collapse
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239
lightwars said:
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239
Click to expand...
Click to collapse
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt
Kurt Krummbein said:
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt
Click to expand...
Click to collapse
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.
lightwars said:
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.
Click to expand...
Click to collapse
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt
Kurt Krummbein said:
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt
Click to expand...
Click to collapse
Yeah! Would be best to build the dtb from source, rather than attaching just the right one to the kernel...
The bluetooth message can be made silent, by the way what build you are using? I think the first build has not the fix for the message. The build.prop should contain this line:
Code:
ro.boot.btmacaddr=00:00:00:00:00:00
and the message should not appear.
I hope there are not any preferences with could only be applied to msm8939 and not to msm8929.
@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.
lightwars said:
@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.
Click to expand...
Click to collapse
For which version is your latest build? the eu?
Thanks
BR Slawo
slawoko said:
For which version is your latest build? the eu?
Thanks
BR Slawo
Click to expand...
Click to collapse
AS and hopefully EU.
This is a stop-gap solution until we get a fully working TWRP with data decryption on the OnePlus 7T Pro 5G McLaren.
Tutorial video here (up to 4K; fullscreen recommended): https://youtu.be/rNwyb_gaByE
requirements:
*OnePlus 7T Pro 5G McLaren (HD1925)
*bootloader unlocked
*USB connected to PC with adb/fastboot
installation:
fastboot getvar all
(look for the (bootloader) current-slot text)
fastboot flash recovery_a recovery_11.0.1.4_adb_nosec.img
or
fastboot flash recovery_b recovery_11.0.1.4_adb_nosec.img
usage:
adb shell
removal:
fastboot getvar all
(look for the (bootloader) current-slot text)
fastboot flash recovery_a recovery_11.0.1.4.img
or
fastboot flash recovery_b recovery_11.0.1.4.img
recovery_11.0.1.4_adb_nosec.img.zip
https://drive.google.com/file/d/1iq-LyWItf1P_0LdoGs5WKaH79TX849G6/view?usp=sharing
recovery_11.0.1.4.img.zip
https://drive.google.com/file/d/1NhVeCjunEJ2X4cdyPuHbxTISu91uTR6H/view?usp=sharing
OLD
recovery_11.0.1.3_adb_nosec.img.zip
https://drive.google.com/file/d/1sxZGQpXG_Fk-yK4NZmB6Im8wSxlcbSPZ/view?usp=sharing
recovery_11.0.1.3.img.zip
https://drive.google.com/file/d/1LDydnV4fdTFbzPD2orZycaYUeSeYYnT-/view?usp=sharing
recovery_11.0.1.2_adb_nosec.img.zip
https://drive.google.com/file/d/1J0jQXJhKmEiH9sLExUPb1arehXeMQGWn/view?usp=sharing
recovery_11.0.1.2.img.zip
https://drive.google.com/file/d/1Avb2y9bc0oZGVMBS40BXQ-_-efzWNJyj/view?usp=sharing
recovery_10.0.43_adb_nosec.img.zip
https://drive.google.com/file/d/1GD1QWWN_q5Lq5-O_w0OgN2jE3dG2_-M0/view?usp=sharing
recovery_10.0.43.img.zip
https://drive.google.com/file/d/1OL1oy9yb3dFE5gsWdrUQVZd5PcHi9ap-/view?usp=sharing
recovery_10.0.42_adb_nosec.img.zip
https://drive.google.com/file/d/1n7tQWR1nRp2vDwejE2dKCjHONwm32ZTs/view?usp=sharing
recovery_10.0.42.img.zip
https://drive.google.com/file/d/1IdMuwj-onVeUYGe0u0XjlIbU0E4mnz0-/view?usp=sharing
recovery_10.0.41_adb_nosec.img.zip
https://drive.google.com/file/d/1zRBMHHIDmTCtReTUCorhNDknzwU4Z5Jf/view?usp=sharing
recovery_10.0.41.img.zip
https://drive.google.com/file/d/1jPC9R5ZY8obIXfOH9k7ghnm3oCsBfTCs/view?usp=sharing
recovery_10.0.40_adb_nosec.img.zip
https://drive.google.com/file/d/1k_GSg4EBf8ejhA2Yk6JInnd8oQTz4WPE/view?usp=sharing
recovery_10.0.40.img.zip
https://drive.google.com/file/d/12YSaIiQhroRXehGR3xi4nzBUx7oeNiNL/view?usp=sharing
recovery_10.0.39_adb_nosec.img.zip
https://drive.google.com/file/d/1eqPCZ9ExaEDpNt3huTmU07z2WVKR-i72/view?usp=sharing
recovery_10.0.39.img.zip
https://drive.google.com/file/d/1Elpc8jv1kYeNAMWyU1nJyjkzG0rd6zTg/view?usp=sharing
recovery_10.0.37_adb_nosec.img.zip
https://drive.google.com/file/d/1CUplbaMHpSV49siLzK3tSN-tmtfYJ2jd/view?usp=sharing
recovery_10.0.37.img.zip
https://drive.google.com/file/d/1z7uG-F7SedzAJwBHn6pY81Nqa44vkUcz/view?usp=sharing
recovery_10.0.36_adb_nosec.img.zip
https://drive.google.com/file/d/1AHy863Z_CFBHfRNSAhYN7E0UFCzU-YHs/view?usp=sharing
recovery_10.0.36.img.zip
https://drive.google.com/file/d/1AIk09glW0ZVLDWastbQVEXGxxJLZ6sqp/view?usp=sharing
recovery_10.0.35_adb_nosec.img.zip
https://drive.google.com/file/d/1UxRvakxsKHZ-pEaZQcGy6YiL_23jLscK/view?usp=sharing
recovery_10.0.35.img.zip
https://drive.google.com/file/d/1Ut-JqzAJKz7jNvb6bp14zO-L0haVjz57/view?usp=sharing
recovery_10.0.34_adb_nosec.img.zip
https://drive.google.com/open?id=16S3eJS3WrKIekJAijFtIgP4a34sMJE78
recovery_10.0.34.img.zip
https://drive.google.com/open?id=1yCvTsT-2NKzToGUn_-1FtiMbNur6Livw
recovery_10.0.31_adb_nosec.img.zip
https://drive.google.com/open?id=1-H92H_TIQUJjQbIElQLsryRq0299lM1k
recovery_10.0.31.img.zip
https://drive.google.com/open?id=1Lp4wuql8j0FwD1I1OPj1r4ebi1Ti3XTg
recovery_10.0.27_adb_nosec.img.zip
https://drive.google.com/open?id=13sp8k6Vk6n6v8SpnjvO9sIFr_5mJ6UYV
recovery_10.0.27.img.zip
https://drive.google.com/open?id=13uRw5yfsBiWJ_nviiXB3Qk3yLl7IPxQG
recovery_10.0.25_adb_nosec.img.zip
https://drive.google.com/open?id=1CapeyuagSK0XxKbI-OuRSXjyKf9ylstV
recovery_10.0.25.img.zip
https://drive.google.com/open?id=1CaNNsZ4q3QVKrzzJ8S7LW5r8TUPuW7OC
recovery_10.0.19_adb_nosec.img.zip
https://drive.google.com/open?id=1-gfQlKcHkIoTzWgHaGenyda6AU614dct
recovery_10.0.19.img.zip
https://drive.google.com/open?id=10Nal33Bw5q_dpBQSbdjKpizGghAV4Wda
Android SDK Platform-Tools
https://developer.android.com/studio/releases/platform-tools
-----------------------------------------------------------------
Special thanks to @aer0zer0 for his input
and to @osm0sis for his: [TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux/Mac]
https://forum.xda-developers.com/showthread.php?t=2073775
Forgive the noob question but Are we able to use this recovery to flash kernels etc?
lendawg said:
Forgive the noon question but Are we able to use this recovery to flash kernels etc?
Click to expand...
Click to collapse
If you just wanted to flash kernels, if already rooted you could could just use an app like Franco Kernel Manager, etc., to flash kernels. A main purpose of this adb enabled stock recovery is to allow decrypted filesystem access in case you could not successfully boot into OS normally. For example, I know of someone who used it to delete a particular file that was causing boot loop after they rebooted right after installing Viper. When we get a fully functioning TWRP for the 5G McLaren, this recovery will be unnecessary.
Can this be used to update our Android version since unlocking the bootloader has messed up receiving OTAs?
Bildo41383 said:
Can this be used to update our Android version since unlocking the bootloader has messed up receiving OTAs?
Click to expand...
Click to collapse
@ntzrmtthihu777 came up with an OTA fixer, which is currently located at https://forum.xda-developers.com/7t-pro-mclaren/how-to/hd1925-10-0-19-fastboot-rom-ota-fixer-t4040629 . Also, you would want to flash back the stock recovery (i.e, without adb enabled), and fully unroot, etc., before OTA as well. If you still couldn't OTA update at that point, then you'd want to backup important files to external storage and flash our device's latest MSM image.
Does anyone here know a good Post on how to unroot my device so I can go ahead and do the update for my phone?
I have a McLaren 5G T-Mobile. I'm currently on version 0.19 and I just received the OTA this morning to update to version 0.25.
I'm new to all of this rooting world. Any help is appreciated.
Thank you.
lramos_90 said:
Does anyone here know a good Post on how to unroot my device so I can go ahead and do the update for my phone?
I have a McLaren 5G T-Mobile. I'm currently on version 0.19 and I just received the OTA this morning to update to version 0.25.
I'm new to all of this rooting world. Any help is appreciated.
Thank you.
Click to expand...
Click to collapse
You could try the OTA fixer linked in the post above your post, and this restores the reserve.img file in /data/reserve/ . After restoring reserve.img, you could open Magisk Manager and choose full unroot. Then, after rebooting, OTA might be able to install; if not, a surefire option is to flash the latest MSM image. The MSM flash in our device forum should be a last resort, because you would probably want to back up important files to external storage and almost everything is replaced starting from scratch.
jhofseth said:
You could try the OTA fixer linked in the post above your post, and this restores the reserve.img file in /data/reserve/ . After restoring reserve.img, you could open Magisk Manager and choose full unroot. Then, after rebooting, OTA might be able to install; if not, a surefire option is to flash the latest MSM image. The MSM flash in our device forum should be a last resort, because you would probably want to back up important files to external storage and almost everything is replaced starting from scratch.
Click to expand...
Click to collapse
I bricked my phone but I was able to use the MSM tool and fresh install everything. Thank you very much for the recommendation..
Thank you for the update version.
im not getting any updates for my phone I am still stuck on 19 can I use this to update to 31 I am waiting for my unlock code for the bootloader should i wait to root before I update or update first
cgrimm9 said:
im not getting any updates for my phone I am still stuck on 19 can I use this to update to 31 I am waiting for my unlock code for the bootloader should i wait to root before I update or update first
Click to expand...
Click to collapse
No, you'd need to use latest MSM tool if you were stuck on 19, but you may want to backup any important files to external storage first. https://forum.xda-developers.com/7t-pro-mclaren/how-to/op7tpro-tmo-5g-unbrick-tool-to-restore-t4043925
jhofseth said:
No, you'd need to use latest MSM tool if you were stuck on 19, but you may want to backup any important files to external storage first. https://forum.xda-developers.com/7t-pro-mclaren/how-to/op7tpro-tmo-5g-unbrick-tool-to-restore-t4043925
Click to expand...
Click to collapse
I figured it out after messing around. I meant to come back and edit my post. I saw the msm post and thats the only reason I messed around with this phone. I just wish there was a working twrp for this phone so some roms come over. but that may never happen.
seems like the 31 recovery is wrong - cannot install OTA without it = = FIXED!!!! HAD TO APPLY ORIGINAL 2X for some reason" literally used the same download to apply again... I dont get this phone
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553051:ERROR:delta_performer.cc(522)] Unable to open ECC source partition recovery on slot B, file /dev/block/bootdevice/by-name/recovery_b: Invalid argument (22)
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553106:ERROR:delta_performer.cc(1230)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553148:ERROR:delta_performer.cc(1235)] Expected: sha256|hex = 001B4315FE31C5A4F1C23D1B16A2C64F137950FF2C28CBC7A7 BD85F3FCB6C987
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553187:ERROR:delta_performer.cc(1238)] Calculated: sha256|hex = 9FF662AA7D1616A5CAB2E532839F6D41429D4214CF38012A49 96D6228A806AF7
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553228:ERROR:delta_performer.cc(1249)] Operation source (offset:size) in blocks: 0:1,15252:1
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553274:ERROR:delta_performer.cc(1530)] source_fd != nullptr failed.
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553323:ERROR:delta_performer.cc(305)] Failed to perform BROTLI_BSDIFF operation 848, which is the operation 0 in partition "recovery"
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553367:ERROR:download_action.cc(336)] Error ErrorCode::kDownloadSta
I moved from TMO to Google Fi about a month ago and I haven't had any issues since moving over, other than this weird call terminating thing that I fixed with a new SIM card. However, I would like to get rid of the TMO ROM that is on here. Does anyone have any advice on what to go with? Just stock OxygenOS rom? I found it at the oneplus.in/support/softwareupgrade forums. However, I can't follow the instructions at the bottom because my "System Update" page does not have a settings button in the top right hand corner (I assume bc of TMO build). Also, the build number appears to be different. 10.3.3.HD01AA vs. 10.0.9 that I have seen elsewhere, but similar dates on them.
Do I need to unlock my bootloader and completely flash a new ROM? Sorry for being such a noob about this.
cregets said:
I moved from TMO to Google Fi about a month ago and I haven't had any issues since moving over, other than this weird call terminating thing that I fixed with a new SIM card. However, I would like to get rid of the TMO ROM that is on here. Does anyone have any advice on what to go with? Just stock OxygenOS rom? I found it at the oneplus.in/support/softwareupgrade forums. However, I can't follow the instructions at the bottom because my "System Update" page does not have a settings button in the top right hand corner (I assume bc of TMO build). Also, the build number appears to be different. 10.3.3.HD01AA vs. 10.0.9 that I have seen elsewhere, but similar dates on them.
Do I need to unlock my bootloader and completely flash a new ROM? Sorry for being such a noob about this.
Click to expand...
Click to collapse
If you're on the TMO 5G variant, I would get the bootloader unlocked and then flash AOSiP. You can definitely use stock ROM, but are limited to TMO's update schedule which differs from OnePlus devices sold directly. With a custom ROM, you get flexibility. Just know you won't have a fingerprint scanner for the time being, but the software advantages and flexibility and battery life increase are worth it in my opinion!
10.0.37.HD61CB is out now, anyone know how to download recovery and add adb?
t436h05t said:
10.0.37.HD61CB is out now, anyone know how to download recovery and add adb?
Click to expand...
Click to collapse
37 is now added to the OP
39 is now added to the OP
anyway to remove a magisk module this way - data is empty?
recovery_10.0.37_adb_nosec.img works and askes for decrypt 39 broken
7T Pro McLaren HD1913 Official Build
Hello, can someone please provide the links to the official builds for the 7T Pro McLaren Edition HD1913. I would really appreciate it.