Got a new firmware update tonight. Tablet seems faster now. Anyone else get it? Glad to see they are still updating this tab.
can't update.
i got error on installing update.
please help me.
i also got the update
waingro808 said:
Got a new firmware update tonight. Tablet seems faster now. Anyone else get it? Glad to see they are still updating this tab.
Click to expand...
Click to collapse
i also got the update on my dell venue 7 3740. but it disabled the fastboot, now i cant root it.
Got it as well. Seems snappier. I would like to know what got updated? Kernel tweaked again?
As far as the problem your having golfyrider, reboot them just keep selecting system update under "about tablet" eventually it will download.
It's still 4.4.4 and the source code hasn't shown any signs of change yet either. Still can't pull the boot.img or recovery.img from the device, having trouble splitting the ones from hharte, still no email replies yet, kinda hate to think my email yesterday caused this as this isn't an answer to my questions, I'm just not stoked about an update that is basically the same as previous, going to snatch it and post it for those who think it's worthy of an update. excuse this rant, been sweating out my days and nights trying with this tablet, not going to stop, just isn't much of an update to me. Sound is still distorted, which really grinds my gears. ... ok, I feel an insey bit better. thanks 4 reading my O.
justlovejoy said:
It's still 4.4.4 and the source code hasn't shown any signs of change yet either. Still can't pull the boot.img or recovery.img from the device, having trouble splitting the ones from hharte, still no email replies yet, kinda hate to think my email yesterday caused this as this isn't an answer to my questions, I'm just not stoked about an update that is basically the same as previous, going to snatch it and post it for those who think it's worthy of an update. excuse this rant, been sweating out my days and nights trying with this tablet, not going to stop, just isn't much of an update to me. Sound is still distorted, which really grinds my gears. ... ok, I feel an insey bit better. thanks 4 reading my O.
Click to expand...
Click to collapse
Take a look at the kernel source for the 7840 it has a py script intended to unpack / pack the unsigned images a small modification can be made to the script to take into account the Sig . if you wanna better idea of the Intel image assembly I suggest at signing up for the baytrail bsp from wind river or other vendor.
If your on windows this might unpack the signed image and repack as a unsigned image so you'll need the boot loader unlocked.
https://www.androidfilehost.com/?fid=95864024717073970 AndImgTool_1_3_0.rar
https://www.androidfilehost.com/?fid=95864024717071926 xImgTool_1_3_32.rar
social-design-concepts said:
Take a look at the kernel source for the 7840 it has a py script intended to unpack / pack the unsigned images a small modification can be made to the script to take into account the Sig . if you wanna better idea of the Intel image assembly I suggest at signing up for the baytrail bsp from wind river or other vendor.
If your on windows this might unpack the signed image and repack as a unsigned image so you'll need the boot loader unlocked.
https://www.androidfilehost.com/?fid=95864024717073970 AndImgTool_1_3_0.rar
https://www.androidfilehost.com/?fid=95864024717071926 xImgTool_1_3_32.rar
Click to expand...
Click to collapse
Thanks for the tools that'll hopefully help a great deal. I've played with the 7840 kernel code for two days and still was left with a non-flashable boot.unsigned.img, I truly appreciate any help I can get with this. I've tried like 5 different device tree cobinations and probably more than that. Hopefully this will truly bring a light for a breakthrough. Thanks a million social-designs-concepts
Here's the update zip that this thread is based off of:
incremental4.4.4update.zip - 24.09 MBBe advised though, this is a direct download from OTA and unmodified by me other than the name of the zip.
It will temporarily disable your root and does something funky to the button combo of down and power to get into bootloader mode (I used adb reboot bootloader-perfect) but if you already obtained root, you can get it back. theres a couple patches and 3 or 4 libs added. other than that? IDK you check it, lol.
It's good your tablet is still getting updates, the 3830, and 3730 hasn't received any updates since 4.4.2.
Lollipop is suppose to start rolling out to the Venue xx40 series on Tuesday April 21st, I suspect this is a preliminary update to make the device work for lollipop. The 3x30 saw similar small updates days before the JB to KK update.
@vampirefo maybe we'll luck out and get Lollipop too, the 3x30 was suppose to get 4.4.4 and it's yet to be seen so maybe they scrapped working on 4.4.4 when Intel did the 360 on supporting 32bit ART and Clovertrail Plus. Though not going to hold my breath. You also might wanna try building cm12 since the 3830 has an unlocked bootloader , they seem to be making progress with it on a couple of other Redhookbay devices.
social-design-concepts said:
Lollipop is suppose to start rolling out to the Venue xx40 series on Tuesday April 21st, I suspect this is a preliminary update to make the device work for lollipop. The 3x30 saw similar small updates days before the JB to KK update.
Click to expand...
Click to collapse
You sure about that? I only saw the 7840 mentioned on Dell's support site for the Apr 21 update to Lollipop.
waingro808 said:
You sure about that? I only saw the 7840 mentioned on Dell's support site for the Apr 21 update to Lollipop.
Click to expand...
Click to collapse
I saw it in a 3740 thread and the 7840 all three devices are merrifield based tablets and the last email I got from dell legal said it was going to start rolling on the 21st and that at this time they have no word on if or when it would be available for the 3x30 I'd post the email but it full of Dell Private Confidential headings.
social-design-concepts said:
Take a look at the kernel source for the 7840 it has a py script intended to unpack / pack the unsigned images a small modification can be made to the script to take into account the Sig . if you wanna better idea of the Intel image assembly I suggest at signing up for the baytrail bsp from wind river or other vendor.
If your on windows this might unpack the signed image and repack as a unsigned image so you'll need the boot loader unlocked.
https://www.androidfilehost.com/?fid=95864024717073970 AndImgTool_1_3_0.rar
https://www.androidfilehost.com/?fid=95864024717071926 xImgTool_1_3_32.rar
Click to expand...
Click to collapse
This andimgtool is very interesting, works on 3830, changes output boot.img into an img that 7840 packing script can unpack and repack that flashes and works.
Sent from my Venue 8 3830 using Tapatalk
vampirefo said:
This andimgtool is very interesting, works on 3830, changes output boot.img into an img that 7840 packing script can unpack and repack that flashes and works.
Sent from my Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
it removes the 480byte signature and corrects the image flag to be unsigned what ever image it was
boot.img wasn't signed, haven't used or seen a signed boot.img since I unlocked the bootloader on this tablet.
pm-cz scripts leave the signature ? Never checked.
Sent from my T1 using XDA Free mobile app
vampirefo said:
boot.img wasn't signed, haven't used or seen a signed boot.img since I unlocked the bootloader on this tablet.
pm-cz scripts leave the signature ? Never checked.
Sent from my T1 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah the uos firmware doesn't validate the sig
social-design-concepts said:
Yeah the uos firmware doesn't validate the sig
Click to expand...
Click to collapse
Alright maybe I am missing a major point if dude are capable of unpacking, repacking and all that good stuff, My question is wtf, why not me? what on earth can i do to get the appropriate file sizes to know where the boot sector is so I can extract it and if need be modify a script that'll allow me to do all of this and re-flash it for testing? the 7840 builds so smooth and I am losing my mind. I feel like theres a whole lot of know how in a small click. Initiate me, make me an apprentice, study buddy. idk I'm loosing my mind. Must have over 20GB worth of trials and errors. I'm going to Google the mentions of sdc from earlier but am really not sure of what I am looking for. If I could get a pm tutor that'd be nice. I can do all the work. But nothing I have tried so far has been acceptable. I'm getting other things done but this is my priority goal. Thanks for helping guys. I'm generous when I got it. I fell so behind in learning the specs of this new device to be successful at what I wanna do with it. There I go again giving reading material for the pooper seat. I need to build and sign a Sig for starts, lol, if momma only knew what I did all day and night now, lol.
thanks again for reading my troublesome O.
Normally I'm just a joy, ROFL, heh
justlovejoy said:
Alright maybe I am missing a major point if dude are capable of unpacking, repacking and all that good stuff, My question is wtf, why not me? what on earth can i do to get the appropriate file sizes to know where the boot sector is so I can extract it and if need be modify a script that'll allow me to do all of this and re-flash it for testing? the 7840 builds so smooth and I am losing my mind. I feel like theres a whole lot of know how in a small click. Initiate me, make me an apprentice, study buddy. idk I'm loosing my mind. Must have over 20GB worth of trials and errors. I'm going to Google the mentions of sdc from earlier but am really not sure of what I am looking for. If I could get a pm tutor that'd be nice. I can do all the work. But nothing I have tried so far has been acceptable. I'm getting other things done but this is my priority goal. Thanks for helping guys. I'm generous when I got it. I fell so behind in learning the specs of this new device to be successful at what I wanna do with it. There I go again giving reading material for the pooper seat. I need to build and sign a Sig for starts, lol, if momma only knew what I did all day and night now, lol.
thanks again for reading my troublesome O.
Normally I'm just a joy, ROFL, heh
Click to expand...
Click to collapse
The 7840 build script is be able to unpack and repack your boot.img, don't know if it will boot on your tablet as I don't have your tablet and not interested in it, I did download a 3840 boot.img, unpacked and repacked boot.img flashed to my tablet just to see if it would flash, and it does flash without any problems, wont boot cause my tablet is a 3830.
Below is flashing same boot.img on my iview i-700 same results as 3830 both will flash the boot.img but neither can boot from image.
Code:
fastboot flash boot '/home/vampirefo/Desktop/dell-venue-boot-tools-master-3840/boot_script/Vamp_packed_boot.img'
target reported max download size of 1324206762 bytes
sending 'boot' (9610 KB)...
OKAY [ 1.402s]
writing 'boot'...
OKAY [ 1.073s]
finished. total time: 2.475s
[email protected]:~/Desktop/dell-venue-boot-tools-master-3840/boot_script$
I have uploaded image here http://www.mediafire.com/download/xbmq8h6c12l55tr/Vamp_packed_boot.img
justlovejoy said:
Alright maybe I am missing a major point if dude are capable of unpacking, repacking and all that good stuff, My question is wtf, why not me? what on earth can i do to get the appropriate file sizes to know where the boot sector is so I can extract it and if need be modify a script that'll allow me to do all of this and re-flash it for testing? the 7840 builds so smooth and I am losing my mind. I feel like theres a whole lot of know how in a small click. Initiate me, make me an apprentice, study buddy. idk I'm loosing my mind. Must have over 20GB worth of trials and errors. I'm going to Google the mentions of sdc from earlier but am really not sure of what I am looking for. If I could get a pm tutor that'd be nice. I can do all the work. But nothing I have tried so far has been acceptable. I'm getting other things done but this is my priority goal. Thanks for helping guys. I'm generous when I got it. I fell so behind in learning the specs of this new device to be successful at what I wanna do with it. There I go again giving reading material for the pooper seat. I need to build and sign a Sig for starts, lol, if momma only knew what I did all day and night now, lol.
thanks again for reading my troublesome O.
Normally I'm just a joy, ROFL, heh
Click to expand...
Click to collapse
Which device 3840 Correct? And you already unlocked the BL?
social-design-concepts said:
Which device 3840 Correct? And you already unlocked the BL?
Click to expand...
Click to collapse
LOL, yeah, if he hasn't unlocked his bootloader, he just been wasting his time. :good::good:
my 3840 has updated ......... it seem faster?
No difference. :silly:
Related
[update 2] I just summarized a way to backup and restore (all based on other great DEV's work, just put in one place) your TS before your play with your TS here: http://forum.xda-developers.com/showthread.php?p=52820278#post52820278
Go check it if you plan to root your TS!
[update] With the help of cheahcl, I got the latest F/W for 4th List 1/8/2100. With the MTK SP_Flash_Tool, I was able to upload a corrected F/W for my TS and everything goes back to normal!
Thanks for cheahcl for his dump and Lokifish Marz for his All in one tools! You guys really saved my day! (and my TS).
A Quick summary: Do NOT use any method on XDA yet to root or change TWRP recovery! It seems the TS of 4th list is different in some way than the ones before which render most of stuffs here invalid. However, fear not to play around since now we have a way to go back to stock!
In my experience, I found that it's really difficult to truly brick a MTK based system. The system will just reject flashing at slightest sign that a F/W is not compatible. The only cache is you need to have the "correct" F/W specifically for your TS!
In my observation, OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in (At least F/W configuration) of the 3rd or earlier 1/8/2100.
------------------------below is my original story of what I tried and failed--------------------------
Just got mine (1/8/2100) 5 hrs ago! I am on the 4th list. The delivery in FAST!
The watch starts normally. I played with it for a while, than decided to root it, install TWRP and apply the security hack made by +Lokifish Marz
Now I have a brick! Just after 30 min I receive the watch!
<<Can anyone help me here?>>
First of all, in respecting to all great DEVs, I have NO intention to blame anyone else but myself. (I did this to my own watch!)
Second, I have been rooting Android since Cupcake day, so I am not a Noob... (or so I think...) I am very familiar with ADB/fastboot... and use almost daily.
So here is the guide to brick. If Anyone have any idea please help me out!
--------------------------------------------------------------------------------------------------
1st, I tried to use this tool to root+TWRP+scurity patch http://forum.xda-developers.com/showthread.php?t=2713183&page=2 knowing it's NOT tested against 1/8/2100. I just tried anyway... The script went with a lot of errors, it seems the script cannot locate correct files but still push the security patched files into the /system/app (and other places).
I turn on the watch, but it just stuck at boot logo (the orange "Truesmart" logo without animation)
Also, the Recovery is still stock, TWRP is no where to be seen.
Since ADB still works, I adb reboot couple times, pull the battery, let the watch run for 2hrs, etc... Nothing works. The watch just stuck at the boot logo.
Than I follow this thread http://forum.xda-developers.com/showthread.php?t=2641261 and http://forum.xda-developers.com/showthread.php?t=2641261 with Stock firmware downloaded from http://d-h.st/users/Lokifish Marz/?fld_id=30814#files (Omate_1-8_2100_TrueSmart_20140328.zip)
I installed all drivers, restarts my Win 7 (x86) pc (several times), and after several attempts the Flashtool just flash in the Firmware.
The Tools flash with a green Check mark, indicating everything is ok!
However the watch just become a brick after this....
Than this completed the brick process! Now the watch won't even turn on, when I try to use Flash tool again, it always say S_FT_ENABLE_DRAM_FAIL. Google this and you find it's due to flashing wrong F/W, but I don't know where went wrong!
Anyone else have same problem or it's just me? Anyone have solution?
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
funky0308 said:
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Ha! Very true! I think you are right! I believe Omate have many segmentation on their HW/SW, even with same model number.... A lot of things changes between versions which makes the "factory image" not compatible....
Anyone has the latest (4th list) 1/8/2100 TS who could dump their whole image for me would be helpful...
I would like to help you but mine is 2nd list and it's still on customs office...
Omate shipment experts, you just gotta love them....
Sent from my C6903 using Tapatalk
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Lokifish Marz said:
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Click to expand...
Click to collapse
Thanks Lokifish for your comment... Is there anyway to get a latest F/W? If you know anyone I could contact, please PM me... Thanks!
Anyone have yet received a 1/8/2100 on 4th list could PM me a Factory F/W dump?
I tried another XP PC with all steps checked and rechecked but still... No luck...
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
cheahcl said:
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
Click to expand...
Click to collapse
Thanks a lot! First of all, Currently don't do anything posted on XDA yet since most of them will not work with this version of TS... (This is where I am now...)
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. it's okay to just provide the file you got after finishing the step "C) Read back the ROM with MTK Droid Tools" I should be able to do the Step D) and after myself.
Thanks a lot for your help!
Lokifish Marz said:
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
Click to expand...
Click to collapse
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
ok will get it to tonight. about 6 hours time. cheers
lssong99 said:
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
Click to expand...
Click to collapse
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Lokifish Marz said:
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Click to expand...
Click to collapse
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
lssong99 said:
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
cheahcl said:
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
Click to expand...
Click to collapse
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
lssong99 said:
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
Click to expand...
Click to collapse
don't sweat it, haha i needed to backup my original firmware as well anyways, seeing how scarce it is around here and all the weird discrepancies in HW/SW versions. good to know i can always fall back on this file. haha yeah i've also backed up my imei. time to play around and see.
cheers
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Spoetnicus said:
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Click to expand...
Click to collapse
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
lssong99 said:
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
Click to expand...
Click to collapse
Thanks!
Im pretty sure that I was on 'Omate_TrueSmart_20140513.103530_V2.0' before I bricked it, so that gives hope
I dont have it with me right now, but Ill try it as soon as I get back home on monday
Thanks again for the tutorials and reply
lssong99 said:
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Click to expand...
Click to collapse
HEY! It worked
I'm back at a functional Truesmart
Thank you soo much
And in case three smiley's aren't enough:
Also, quick note for other people bricking their phone, my issue (after I bricked it again), was that I used an app to change the density property, which broke the boot of the watch.
The app that broke my watch was: https://play.google.com/store/apps/details?id=com.birdapi.android.dpi
Need link to download the specific software specified in the title of this thread. Came across the one loaded on Google by another xda member but having difficulties downloading it. If you have it mirrored to another cloud service please provide me with the link. I am mostly gunning to get my hands on all of the .img files which come inside it so that I may review them via a hex editor and unlock my bootloader the sneaky way since Huawei refuses to reply back to my emails. Many thanks in advance.
Update: I was able to get my hands on the update.app file. So now will begin extraction and making my changes to hack the bootloader status on my device. If Huawei has responded back to you with your proper bootloader unlock code then you were fortunate. I myself have run out of patience with them and am now handling this on my own personal level.
Modding.MyMind said:
Need link to download the specific software specified in the title of this thread. Came across the one loaded on Google by another xda member but having difficulties downloading it. If you have it mirrored to another cloud service please provide me with the link. I am mostly gunning to get my hands on all of the .img files which come inside it so that I may review them via a hex editor and unlock my bootloader the sneaky way since Huawei refuses to reply back to my emails. Many thanks in advance.
Update: I was able to get my hands on the update.app file. So now will begin extraction and making my changes to hack the bootloader status on my device. If Huawei has responded back to you with your proper bootloader unlock code then you were fortunate. I myself have run out of patience with them and am now handling this on my own personal level.
Click to expand...
Click to collapse
Having trouble getting the bootloader unlock code? Try this:
Most of the issues are that emails sent outside of Shenzhen China business time during the week are not answered. They go into an email black hole. You'd have to send in the bootloader unlock request email really late here in the US or set up some way to send your email later automatically like I did with the Chrome extension Boomerang to get the code for my second HAM2. Currently sending in a request around 9pm EST to 4am EST Sunday - Thursday is the best time to email for the unlock code Sun-Thurs corresponds to Monday-Friday at Huawei in China.
I have emailed outside of those times and not gotten a response. After figuring out the time difference and setting up boomerang for an automated send later feature with my email the code arrived a couple hours after it was sent and I saw it when I woke up the next morning.
Sent from my MT2L03 using Tapatalk
@arcadesdude, thanks for your input, but unfortunately that route has failed me as well. Been at it with these emails since late last year. My guess is that my emails are getting lost in middle of a bunch of other emails they may be receiving or I'm going to their spam mail which they probably ignore. Either case, all attempts have not been successful. I found the EFI image and boot image inside the update.app last night. So far so good as it looks like I can easily hack this update and finally get my bootloader unlocked so I may do what I need to do with it.
Modding.MyMind said:
@arcadesdude, thanks for your input, but unfortunately that route has failed me as well. Been at it with these emails since late last year. My guess is that my emails are getting lost in middle of a bunch of other emails they may be receiving or I'm going to their spam mail which they probably ignore. Either case, all attempts have not been successful. I found the EFI image and boot image inside the update.app last night. So far so good as it looks like I can easily hack this update and finally get my bootloader unlocked so I may do what I need to do with it.
Click to expand...
Click to collapse
You can unlock the bootloader without the bootloader unlock code?
Did you try another email address? Another member on here used another address and got through to Huawei.
Sent from my MT2L03 using Tapatalk
arcadesdude said:
You can unlock the bootloader without the bootloader unlock code?
Did you try another email address? Another member on here used another address and got through to Huawei.
Sent from my MT2L03 using Tapatalk
Click to expand...
Click to collapse
No, the bootloader code is still required. All I am going to do is modify the source via a hex editor so that I can input a code of my choosing and force it to accept that code and thus unlock my bootloader. That is very possible . Should of done this already but I wanted to give Huawei a chance - but they failed.
Modding.MyMind said:
No, the bootloader code is still required. All I am going to do is modify the source via a hex editor so that I can input a code of my choosing and force it to accept that code and thus unlock my bootloader. That is very possible . Should of done this already but I wanted to give Huawei a chance - but they failed.
Click to expand...
Click to collapse
I didn't know you could do that. Is it essentially just flashing your modified bootloader partition to the phone using adb like we flash the recovery partition?
arcadesdude said:
I didn't know you could do that. Is it essentially just flashing your modified bootloader partition to the phone using adb like we flash the recovery partition?
Click to expand...
Click to collapse
Pretty much, but not with adb. Using fastboot.
also, i guess you also need disable the verification chain? but how? I heard it probably start from very beginning, ROM, a real read only rom. if you flash hacked aboot, sbl probably refuse to boot it, right?
xordos said:
also, i guess you also need disable the verification chain? but how? I heard it probably start from very beginning, ROM, a real read only rom. if you flash hacked aboot, sbl probably refuse to boot it, right?
Click to expand...
Click to collapse
With a bootloader being locked you are presumably limited on what can and cannot be flashed. With that in mind should a modification be incorrectly done for a device with a locked bootloader then it would be safe to say that the flash would be denied and no harm done. Because I will be modifying the source to accept my personal code then this will not have any affect towards flashing. The device will even accept it. Then, when I enter my code and reboot, the device will simply say it is unlocked. The only catch to this though is that if I flash back to the original then the bootloader should technically relock itself. I will open a thread on this procedure down the road when I get time and even include my mods so others may compare it with the stock to see the differences.
Modding.MyMind said:
With a bootloader being locked you are presumably limited on what can and cannot be flashed. With that in mind should a modification be incorrectly done for a device with a locked bootloader then it would be safe to say that the flash would be denied and no harm done. Because I will be modifying the source to accept my personal code then this will not have any affect towards flashing. The device will even accept it. Then, when I enter my code and reboot, the device will simply say it is unlocked. The only catch to this though is that if I flash back to the original then the bootloader should technically relock itself. I will open a thread on this procedure down the road when I get time and even include my mods so others may compare it with the stock to see the differences.
Click to expand...
Click to collapse
Regarding the limitation, early I thought you are going to modify/repackage the UPDATE.APP, as that way, if (a big if) it works, ideally you can flash to any partition. (There is some thread in xda that discussion about read/repackage the huawei UPDATE.APP)
But as we discussed briefly long time back, this whole thing is really really risky, if the booting path to fastboot got damage, then pretty much the phone is hard bricked.
Probably if you stick with flash with fastboot, then the risk will be lesser but man, this is scary stuff..
Regarding the validation chain, I got info from following article:
http://www.newandroidbook.com/Articles/aboot.html
A few paragraph after the Figure One.
Let's see...
PS, maybe you can continue try some different email address and sent at correct time to Huawei for the code...
PS2, another thought, maybe inject a superSU to the UPDATE.APP system image will work? not sure how strict they are validating when flashing UPDATE.APP and/or when booting the system partition.
xordos said:
Regarding the limitation, early I thought you are going to modify/repackage the UPDATE.APP, as that way, if (a big if) it works, ideally you can flash to any partition. (There is some thread in xda that discussion about read/repackage the huawei UPDATE.APP)
But as we discussed briefly long time back, this whole thing is really really risky, if the booting path to fastboot got damage, then pretty much the phone is hard bricked.
Probably if you stick with flash with fastboot, then the risk will be lesser but man, this is scary stuff..
Regarding the validation chain, I got info from following article:
http://www.newandroidbook.com/Articles/aboot.html
A few paragraph after the Figure One.
Let's see...
PS, maybe you can continue try some different email address and sent at correct time to Huawei for the code...
Click to expand...
Click to collapse
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Modding.MyMind said:
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Click to expand...
Click to collapse
Just curious, what are you planning to do that requires an unlocked bootloader?
ScoobSTi said:
Just curious, what are you planning to do that requires an unlocked bootloader?
Click to expand...
Click to collapse
Something lol
I'm not sure why you can't get the code from Huawei ...but I'm kinda glad you can't. seems your gathering nice info about this phone.
Sent from my MT2L03 using XDA Free mobile app
Modding.MyMind said:
Something lol
Click to expand...
Click to collapse
Just in case you're being super extremely nice and kind and trying to make a ROM for us, the other developer has hit a huge roadblock on CM11/12 you should know about.
ScoobSTi said:
Just in case you're being super extremely nice and kind and trying to make a ROM for us, the other developer has hit a huge roadblock on CM11/12 you should know about.
Click to expand...
Click to collapse
Even he is not plan to build CM, but as the man who build first recovery for us, I think he wont stop until he can play with his own baby in his phone.
Modding.MyMind said:
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Click to expand...
Click to collapse
1. How are you going to flash image via fastboot if your bootloader is locked?
2. You have to hack fastboot image to pass throuth unlock code verification without or with some random code. But even if you do so, you won't be able to flash fastboot image via fastboot even with unlocked bootloader.
I would'nt touch fastboot at all 'cause it's a high risk to get a hard brick.
I have found unlock code in some partition of my device, but I dunno was it there initially or was written there after unlocking. If the first case is and fastboot just compares entered code with saved one in device, then you can try to make update.app with injected su, as xordos offered, to be able to read this partition.
Injecting su into the update.app woukdnt work. The update.app has it's own crc and such. So to simply say, it won't work. You also answered your questions with remarks 1 and 2. One exception is that yes, you can flash the image. As for risks, it's only there if you mess something up - development typically is about taking risks . The fastboot image won't technically brick the device anyways. At best a soft brick may occur, but to be honest since "bricking" is up for discussion; bricking can occur simply by making a change to the build.prop file and not fixing it's permissions prior to rebooting. Unless you "hard" brick the device, then it can always be recovered.
You said the image or images can't be flashed with a locked bootloader, while yes is technically true, but understand that it isn't 100%, because you see, when your device recieves an update initially the devices bootloader is expected to be locked, right? Yet, magically enough the update goes through, the phone reboots, you either hate or love the new update. Something to think about before actually saying an image can't be flashed . Instead, I would have you ask yourself, "how?".
xordos said:
Even he is not plan to build CM, but as the man who build first recovery for us, I think he wont stop until he can play with his own baby in his phone.
Click to expand...
Click to collapse
And best believe, I want to play
I know this isn't the correct forum but I've searched and haven't found anything and since this seems to be the closet device I was wondering if there is any development for this device yet or any rooting methods that may work
I looked as well. There does not seem to be any serious develop on the V530. I'm bootloader unlocked but no root or twrp that I could find.
Mike02z said:
I looked as well. There does not seem to be any serious develop on the V530. I'm bootloader unlocked but no root or twrp that I could find.
Click to expand...
Click to collapse
Thanks. I couldn't even get that far. Don't get me wrong it's a nice device but I'm sure a custom ROM would make it fly. Hopefully soon as more people get the device we'll see some development.
First thing first. Bootloader commands must be there.
If so, you just need TWRP
I'd also be very interested in rooting/custom rom for this device, as I moved to it from my Nexus 7 2013 that was very much showing it's age. It's almost painful being on a stock rom from a 3rd party at this point. I've searched through google and nobody seems to be taking much interest in this device. The same was true for the original xperia z tablet and it's got official lineageos support, so I remain hopeful.
love this thing
I would just love to root this beast. New to LG products, not new to rooting. Can anyone point me in the right direction on where to start?
Did you root t
widto08 said:
I would just love to root this beast. New to LG products, not new to rooting. Can anyone point me in the right direction on where to start?
Click to expand...
Click to collapse
Did you ever get this tablet rooted.. I. Can't find any information about this device online it's like it they never made it
Saint$1t said:
Did you ever get this tablet rooted.. I. Can't find any information about this device online it's like it they never made it
Click to expand...
Click to collapse
I am having problems even booting into bootloader on this thing. I was able to boot into recovery mode but can't get out of the "no commands".
adb reboot recovery
adb reboot bootloader -> just reboots it.
It might be possible to use dirtyc0w exploit to get root access on this tablet.(nvm it seems our android version is already patched for that. )
I too have been able to get the bootloader unlocked but unable to find a version of TWRP or find any rooting tool that supports this device. Still holding out hope but this doesn't seem to be a super popular device :/
Hey guys! I bricked my tab and i need a stock kdz or system, recovery and boot.imgs! Does anyone have or can pull these file for me thanks in advance!
Sent from my [device_name] using XDA-Developers Legacy app
I have rooted mine..if I had the stock system.img could you used that? This is what I did to obtain root..
Download the Lg download utility mode tool '''https://github.com/Lekensteyn/lglaf''
and the sources ''https://pycryptodome.readthedocs.io/en/latest/src/installation.html'
Then open cmd in the folder and execute: python lglaf.py --debug --rawshell --cr -c '!S sh' <--- there might be an error message or laf_acess_denied but its okay.
re-enter the command: python lglaf.py --debug --rawshell <--- this should open up an interactive shell..enter ls and see if it lists the files on the device then close the interactive shell
run python extract-partitions.py to get the stock boot.bin but change the file extension to .img
push the boot.img to the device, install magisk manager, patch the boot.img, pull img then flash with fastboot
Nice! We finally get root a couple days after a seemingly innocent fall off my bed wrecked my screen :crying:. Deciding on replacing it or getting a MediaPad M5.
tbh I've rooted this device since last month or so but I really didn't have time to make a tutorial
Is anyone able to pull there kdz? My tab is bricked and ive tried LG bridge and all others! Or the the imgs in need to go back to stock! Any help please! Thanks!
Sent from my [device_name] using XDA-Developers Legacy app
Vincent_vann said:
tbh I've rooted this device since last month or so but I really didn't have time to make a tutorial
Click to expand...
Click to collapse
I followed your comment and was able to root. May I use your process to make a tutorial? I will give you credit
---------- Post added at 05:42 PM ---------- Previous post was at 05:33 PM ----------
Thanks to Vincent_vann I have root. With this I can finally start building a custom TWRP for this tablet. I wish we had a forum for this device. I requested one last year but it still hasn't been made even though it was approved. If I get one built, and there isn't a dedicated forum, I'll post it in this thread.
Just built TWRP. I noticed some folks asking for stock recovery, boot, and system img files. I have recovery and boot img. Not sure where to post these though. Same with twrp. If someone has any reccomendations on how to go about this I'll gladly provide.
I have the Canadian variant (v533) and wouldn't mind giving TWRP a whirl on it. All specs are same so I think it'll work. Don't mind testing if you do get somewhere to post TWRP. Also good job on getting it compiled ?
Jambii1987 said:
I have the Canadian variant (v533) and wouldn't mind giving TWRP a whirl on it. All specs are same so I think it'll work. Don't mind testing if you do get somewhere to post TWRP. Also good job on getting it compiled ?
Click to expand...
Click to collapse
Thank you! Unfortunately with nougat file based encryption TWRP has issues with decrypting /data after the setup of the tablet. So it's working 50% which is annoying because you'll have to wipe data whenever you want to flash something. Not a big deal for roms, but very inconvenient for other zips. If you still want it let me know and I'll find a place. Else I'll be tackling the decryption issue this weekend.
xnukemx47 said:
Thank you! Unfortunately with nougat file based encryption TWRP has issues with decrypting /data after the setup of the tablet. So it's working 50% which is annoying because you'll have to wipe data whenever you want to flash something. Not a big deal for roms, but very inconvenient for other zips. If you still want it let me know and I'll find a place. Else I'll be tackling the decryption issue this weekend.
Click to expand...
Click to collapse
I think I'll wait until you try getting decryption working. I have a had many fights with that beast lol
Jambii1987 said:
I think I'll wait until you try getting decryption working. I have a had many fights with that beast lol
Click to expand...
Click to collapse
Have any good resources you can recommend?
Hi,
I just got a new tab Lenovo M10 TB-X605F.
I tried to unlock it with fastboot-adb (minimal kit).
When I enter "fastboot devices" the serial n° displays.
But each command I tried (fastboot oem unlock, unlock-go, flashing, flashing unlock...) get the same asnwer : "FAILED (remote: unknown command)".
Does anyone know a solution?
Thank you.
I also had problems with the out-of-the-box version of fastboot.
Solution is to upgrade to Pie, because the update allows bootloader unlocking. Easiest way is to load the rescue ROM using LMSA, then let the tablet fetch the OTAs.
To learn more have a look at @Chaser42's root thread for the P10. Also in that thread @Long_Sam has a step-by-step guide for the M10.
I've also posted an updated magisk_patched .img for TB-X605F running S210097_190927 to that thread. Be careful, though. Make sure your build and model number are the same as mine before using it:
build number: X605F_S210097_190927_ROW
model number: TB-X605F (hardware code 63)
Check the sticker on the back of your tablet for the hardware code. It's in brackets after the S/N.
So mine reads: "S/N: XXXXXXXX (63)".
Thank you very, very much Yahoo Mike!
I'll try it as soon as possible!
did you have oem unlock on in developer mode?
Yes
thanks, but i wonder if i can get twrp on the tablet
turboperson123 said:
thanks, but i wonder if i can get twrp on the tablet
Click to expand...
Click to collapse
I don't know yet.
Root is ok, thanks of the links in YahooMike's post. :good:
Monpseud0 said:
I don't know yet.
Root is ok, thanks of the links in YahooMike's post. :good:
Click to expand...
Click to collapse
I would love to get custom recovery for these tablets. I submitted a request for the P10 (TB-X705F) to the guys that port TWRP images to new devices. However, I think they are completely overloaded with request so we won't see anything soon. I was working with a guy that was making an image but he got busy with real life and hasn't been able to complete it.
I'm about ready to learn Android kitchen and cook up some TWRP images myself. I've read all the documentation. I just might be able to do it if I can find the time. If I can successfully make an image for the P10 then I can also make one for the M10 and all other variants. Hopefully I'm not being overly ambitious. Wish me luck.
Chaser
TWRP is OK. I found the way to flash it somewhere in this forum. It works. Now, it is waiting for a custom ROM to flash!
Chasser, if you do that, You're my hero ! I'd like to help you but I don't know anything about building a ROM. So I wish you the best! Can't sait!
Chaser42 said:
I would love to get custom recovery for these tablets. I submitted a request for the P10 (TB-X705F) to the guys that port TWRP images to new devices. However, I think they are completely overloaded with request so we won't see anything soon. I was working with a guy that was making an image but he got busy with real life and hasn't been able to complete it.
I'm about ready to learn Android kitchen and cook up some TWRP images myself. I've read all the documentation. I just might be able to do it if I can find the time. If I can successfully make an image for the P10 then I can also make one for the M10 and all other variants. Hopefully I'm not being overly ambitious. Wish me luck.
Chaser
Click to expand...
Click to collapse
I've got some time this week. Happy to help with the TWRP port. A basic setup shouldn't take long, especially if we ignore forced data encryption.
If you're eventually going to a install custom ROM, then you'll be wiping the /data partition anyway. So probably best to avoid the nightmare of trying to crack the encryption in TWRP - at least to begin with.
If it's really true that the P10 is just an M10 with some bells and whistles added, then I suspect we'll get away with using the same kernel image for all these tablets X605F/L & X705F/L in recovery. That means we can all use the same TWRP img. Fingers crossed.
But until we have some custom ROMs, the stock boot.img will need to be patched to remove encryption. Otherwise the next time you reboot, it'll just re-encrypt the data partition. Those images will be different for each tablet.
Have you got a github repo set up for recovery tree? We should probably start a new thread for unofficial TWRP (X605F/L & X705F/L) as well. I'm happy to kick it all off, if you haven't done so already.
Yahoo Mike said:
I've got some time this week. Happy to help with the TWRP port. A basic setup shouldn't take long, especially if we ignore forced data encryption.
If you're eventually going to a install custom ROM, then you'll be wiping the /data partition anyway. So probably best to avoid the nightmare of trying to crack the encryption in TWRP - at least to begin with.
If it's really true that the P10 is just an M10 with some bells and whistles added, then I suspect we'll get away with using the same kernel image for all these tablets X605F/L & X705F/L in recovery. That means we can all use the same TWRP img. Fingers crossed.
But until we have some custom ROMs, the stock boot.img will need to be patched to remove encryption. Otherwise the next time you reboot, it'll just re-encrypt the data partition. Those images will be different for each tablet.
Have you got a github repo set up for recovery tree? We should probably start a new thread for unofficial TWRP (X605F/L & X705F/L) as well. I'm happy to kick it all off, if you haven't done so already.
Click to expand...
Click to collapse
The P10 and M10 are so similar, we could probably Port it for all of the different variants if other people are willing to help out and test. On my end I only have P10 and my test P10.
Currently I don't have a Linux machine but I saw that he made a version that works on Android. I think you I know a lot more about the process than I do. I'm just pretty good at reading documentation and coming up to speed on stuff that I've never done before. And this stuff isn't really over-the-top technology-wise so I figured it might be a neat project to tackle.
And speaking of custom roms, I think I saw that somebody had an unofficial lineage ROM started for these devices. I'll have to double-check that. And I was thinking about the stock ROM, encryption doesn't happen until after LMSA is done with the rescue and the tablet reboots. I'm not a big expert in what happens when the initial ROM is flashed but it feels like there's some sort of script running that handles a bunch of batch processes. I know that you can modify any of the files that you want before you do the rescue. Wouldn't it be nice if all we had to do is comment out some lines in the script so that encryption doesn't happen at all? Perhaps I'm being a bit too optimistic.
My big problem in the near future is time. I'm going to be very busy with my kids in the next few weeks. So I'm definitely not a position right now where I can spearhead that project. But we'll have to see how it goes. I'm sure I love some availability if you need my help.
Chaser
Yahoo Mike said:
I've got some time this week. Happy to help with the TWRP port. A basic setup shouldn't take long, especially if we ignore forced data encryption.
If you're eventually going to a install custom ROM, then you'll be wiping the /data partition anyway. So probably best to avoid the nightmare of trying to crack the encryption in TWRP - at least to begin with.
If it's really true that the P10 is just an M10 with some bells and whistles added, then I suspect we'll get away with using the same kernel image for all these tablets X605F/L & X705F/L in recovery. That means we can all use the same TWRP img. Fingers crossed.
But until we have some custom ROMs, the stock boot.img will need to be patched to remove encryption. Otherwise the next time you reboot, it'll just re-encrypt the data partition. Those images will be different for each tablet.
Have you got a github repo set up for recovery tree? We should probably start a new thread for unofficial TWRP (X605F/L & X705F/L) as well. I'm happy to kick it all off, if you haven't done so already.
Click to expand...
Click to collapse
Hi guys
I got TWRP on m'y M10. Thanks to Turboperson123
https://forum.xda-developers.com/general/help/lenovo-tb-x605f-twrp-t3976707?goto=newpost
Is there any consolidated info on this new script? I have yet to find any such thread (still searching).
I have it downloaded, and I have the python img extract script.
I was thinking of copying over the main script files with the new Android 11 images.
Is there any reason why I should not do that?
I think the trick is MSM uses the EDL flash mode, which seems to be able to bring back ANY corruption in the R/W part of the phone, no matter how bad it is messed up. I assume it only uploads signed code, and we couldn't just inject our own images into/through it like we can through fastboot.
Neat trick, though, if we can... no more stuck bootloops or wrong slot errors...
I'd also love to see it run on Linux so I don't need to keep Win images around to use it... wonder if the protocol is documented anywhere to be able to reverse engineer it? Probably over my capabilities by far.
@SomeRandomGuy
Thanks for the reply. FYI, I just tried it on my BE89BA and I replaced all the images with the latest available Android 11 images (extracted with the python script). No dice. Qualcomm crash dump screen.
I'm trying a few different things. I'll post here once I get a result that works.
TheArkive said:
@SomeRandomGuy
Thanks for the reply. FYI, I just tried it on my BE89BA and I replaced all the images with the latest available Android 11 images (extracted with the python script). No dice. Qualcomm crash dump screen.
I'm trying a few different things. I'll post here once I get a result that works.
Click to expand...
Click to collapse
Have you tried going the Install.bin route?
ninjasinabag said:
Have you tried going the Install.bin route?
Click to expand...
Click to collapse
If someone links or outlines the install.bin idea i can give it a shot.
ninjasinabag said:
Have you tried going the Install.bin route?
Click to expand...
Click to collapse
I'm sorry @ninjasinabag , I've never heard of this with respect to a OnePlus phone... and my search-fu is failing me... could you give us a hint what this entails?