Related
I know fastboot isn't possible on the SG3, but the posts i found give the suggestion that it's not impossible. just not implemented yet. so my questions are:
1: is fastboot possible at all?
2: how hard would it be to implement it?
3: can i expect it to happen sometime?
thanks in advance.
Metalcookie said:
I know fastboot isn't possible on the SG3, but the posts i found give the suggestion that it's not impossible. just not implemented yet. so my questions are:
1: is fastboot possible at all?
2: how hard would it be to implement it?
3: can i expect it to happen sometime?
thanks in advance.
Click to expand...
Click to collapse
What exactly do you mean by fastboot?
neo1691 said:
What exactly do you mean by fastboot?
Click to expand...
Click to collapse
this:
"Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host via USB. It allows flashing of unsigned partition images. It is disabled in production devices since USB support has been disabled in the bootloader."
from the CyanogenMod wiki
Metalcookie said:
this:
"Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host via USB. It allows flashing of unsigned partition images. It is disabled in production devices since USB support has been disabled in the bootloader."
from the CyanogenMod wiki
Click to expand...
Click to collapse
i havent read any of these in forum section as yet..
Acid lestitious 2.0. Fugumod 2.2
I've seen some people talk about it, but can anyone answer the questions?
I think Fastboot is HTC only... and we already flash ROMs via Odin / CWM
zajkit said:
I think Fastboot is HTC only... and we already flash ROMs via Odin / CWM
Click to expand...
Click to collapse
some Samsung devices have fastboot, so it's not just HTC only..
and with fastboot you can do some stuff you can't with other methods, like change the boot splash (default it's the screen that says "GT-I5800 SAMSUNG")..
After some searching, it looks like very few people were able to get into Fastboot/Forced upload mode on Galaxy S. Other than that, only couple of older Samsung phones could do that. You could call your provider support and ask for directions on how to get into fastboot, but I dont think they would share that information.
zajkit said:
After some searching, it looks like very few people were able to get into Fastboot/Forced upload mode on Galaxy S. Other than that, only couple of older Samsung phones could do that. You could call your provider support and ask for directions on how to get into fastboot, but I dont think they would share that information.
Click to expand...
Click to collapse
hah, i don't think my provider would know. they don't even know the data usage of somebody, they always mess up things like that. i'd guess i'd get a response regarding garancy or something else irrelevant.
OK, just got the Fire today. The OS says 5.0.1 from Nov 17th, and says update is available, version 541112720. I block OTAVerifier only, thinking by blocking the verification I can intercept the update file in /cache. then I turn on airplane mode, play a bit and boot into TWRP via fastboot, install SuperSu. All is good.
Then I decide to see what the update is all about, and let it download. To my surprise, it starts installing. After the installation, I see FireOS 5.1.1 Now, I try to go into TWRP via fastboot, and it does not reboot and just hangs. A couple more tries - and still nothing.
I go back to stock recovery, and start sideloading update-kindle-37.5.2.2_user_522054520.bin . It sideloads OK, and upon reboot i get dark screen. Nothing works. This sounds very similar to the 4th gen issues where downgrades were bricking Fires :
http://forum.xda-developers.com/fire-hd/general/stop-upgrade-to-lollipop-via-twrp-t3216817
It'll be simple to install 5.1.1 via TWRP once the update file is captured, such that the older bootloaders can be kept.
But beware of the update - without TWRP there likely won't be root!
Dang, sucks about the brick! Hopefully getting TWRP to work again won't take a herculean effort. Right now I'm loving SlimLP but anyone getting one for xmas would likely get that Fire OS 5.1.1 pushed to them right away upon booting up and logging in and I would hate to see them stuck on that!
Damn!
What if an open wifi network is within range? Will the Fire OS ask before connecting?
My friend has a new fire in the box & has an open wifi network within range of their place.
The 5.1.1 update should find it's way to amazon's Software Updates page in time. It's not there yet. http://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
blueberry.sky said:
What if an open wifi network is within range? Will the Fire OS ask before connecting?
My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
afaik they don't ship with wifi on, and you have to agree to connect if wifi is detected.
Still, anyone who might want to root needs to keep wifi off until this is sorted--or until they're rooted and can rename DeviceSoftwareOTA.apk . And everyone on rooted stock should confirm /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk is renamed to .apkOFF (or whatever), which should prevent a download. Don't know how the roms handle OTA.
I do believe that you should have to agree to connect to wifi. But I'd like to be 100% sure. Don't want to take the slightest chance.
I would appreciate confirmation from anyone with a brand new Fire & an open wifi network within range, that it will not auto-connect.
bibikalka said:
It'll be simple to install 5.1.1 via TWRP once the update file is captured, such that the older bootloaders can be kept.
But beware of the update - without TWRP there likely won't be root!
Click to expand...
Click to collapse
So, 5.1.1 can't boot TWRP and downgrading produces bricks. Lovely!
Wonder if there's any chance the CM recovery will boot?
I assume some of the "old-timers" here will capture the update soon enough. If not, I'm glad to give it a go.
tried the downgrade as well, same result. I think the reason we can't get back into recovery\fastboot is because the device is just endlessly rebooting (you can see in device manager). it wont let you power it off to try the volume down+power combo and just holding them does nothing. im going to let mine die overnight hopefully and maybe getting the volume down+power from off will let us back into recovery?
---------- Post added at 01:14 AM ---------- Previous post was at 12:46 AM ----------
DoLooper said:
So, 5.1.1 can't boot TWRP and downgrading produces bricks. Lovely!
Wonder if there's any chance the CM recovery will boot?
I assume some of the "old-timers" here will capture the update soon enough. If not, I'm glad to give it a go.
Click to expand...
Click to collapse
Well 5.0.1 is available on the Amazon website here: https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180 so I contacted Amazon for the 5.1.1 file and this was what I got:
Jyothirmayi: In this case, I'll personally follow up your contact and email you the link for the update because we currently don't have the manual link for the update in our website.
I will post here if\when I hear back
dmesg on linux machine when plug usb, open mediatek preloader com port.
Have this on bricked fire ?
usb 1-2.4: Product: MT65xx Preloader
usb 1-2.4: Manufacturer: MediaTek
cdc_acm 1-2.4:1.1: ttyACM0: USB ACM device
adb
usb 1-2.4: New USB device found, idVendor=1949, idProduct=0222
usb 1-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 1-2.4: Product: Fire
usb 1-2.4: Manufacturer: Amazon
usb 1-2.4: SerialNumber: xxxxxxxxxxxxxxxxxxx
fastboot
usb 1-2.4: New USB device found, idVendor=0bb4, idProduct=0c01
usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2.4: Product: Android
usb 1-2.4: Manufacturer: MediaTek
usb 1-2.4: SerialNumber: xxxxxxxxxxxxxx
If you have TWRP, why didn't you just use the file manager to copy and paste the OTA from your /cache to your sd card? If you can boot to TWRP, see if it's still there.
You can also dump your cache via adb shell from within TWRP and get the OTA by extracting the cache.img that dumps. There are several ways, as long as TWRP and fastboot are still booting.
Also, you can use adb shell within twrp to dd a system.img dumped from another fire tab, and restore your device that way if all else fails.
hp420 said:
If you have TWRP, why didn't you just use the file manager to copy and paste the OTA from your /cache to your sd card? If you can boot to TWRP, see if it's still there.
You can also dump your cache via adb shell from within TWRP and get the OTA by extracting the cache.img that dumps. There are several ways, as long as TWRP and fastboot are still booting.
Also, you can use adb shell within twrp to dd a system.img dumped from another fire tab, and restore your device that way if all else fails.
Click to expand...
Click to collapse
I think in the OP, he mentioned that he is no longer able to get into TWRP after 5.1.1 update...
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
87racer said:
Jyothirmayi: In this case, I'll personally follow up your contact and email you the link for the update because we currently don't have the manual link for the update in our website.
I will post here if/when I hear back
Click to expand...
Click to collapse
mmoogle said:
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
Click to expand...
Click to collapse
When we get the official file from Amazon, we can format it to the way the MTK Droid Tool wants it, and then that would theoretically work.
mmoogle said:
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
Click to expand...
Click to collapse
Vlasp said:
When we get the official file from Amazon, we can format it to the way the MTK Droid Tool wants it, and then that would theoretically work.
Click to expand...
Click to collapse
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
87racer said:
tried the downgrade as well, same result. I think the reason we can't get back into recovery\fastboot is because the device is just endlessly rebooting (you can see in device manager). it wont let you power it off to try the volume down+power combo and just holding them does nothing. im going to let mine die overnight hopefully and maybe getting the volume down+power from off will let us back into recovery?
Click to expand...
Click to collapse
Just pull your battery. The back cover is very easy to get off. Use a knife just to widen the seam so you can get your fingernail in at the corner. Keep one fingernail at the corner & side a 2nd nail down along the edge.
Then the battery connector lifts out upwards.
http://forum.xda-developers.com/ama...o-photo-amazon-fire-2015-motherboard-t3227808
bibikalka said:
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
Click to expand...
Click to collapse
We might be in luck. I happen to have 3 of them One bricked, one mostly untouched on 5.1.1 and another with OTA blocked on 5.0.1. I will fiddle with the tools you posted and see if I can come up with something.
blueberry.sky said:
Just pull your battery. The back cover is very easy to get off. Use a knife just to widen the seam so you can get your fingernail in at the corner. Keep one fingernail at the corner & side a 2nd nail down along the edge.
Then the battery connector lifts out upwards.
http://forum.xda-developers.com/ama...o-photo-amazon-fire-2015-motherboard-t3227808
Click to expand...
Click to collapse
Good to know, even over night, it still isn't dead so I might give this a shot.
So, if i previously installed the google framework and blocked ota like most people did, this won't block the ota really ?
87racer said:
We might be in luck. I happen to have 3 of them One bricked, one mostly untouched on 5.1.1 and another with OTA blocked on 5.0.1. I will fiddle with the tools you posted and see if I can come up with something.
Click to expand...
Click to collapse
The best deal is of course to capture the 5.1.1 update file. I am eager to try it, provided I get root with requires installing via TWRP.
bibikalka said:
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
Click to expand...
Click to collapse
So MTK tools does talk but from what I gather it is looking for /proc/dumchar_info which contains the partition structure. This is used to create the scatter file that would allow us to push the firmware back. This file is non-existent. I tried to find some alternate way to build a scatter file but am coming up short and without it we can't really do anything using SP Flash...
Also tried looking into /proc/mtd for info but that file is basically blank. Not sure if Amazon is storing the partition information somewhere else or maybe its hard coded into a chip?
If anybody has any ideas, I have the working devices and can try pulling stuff but I am stumped atm
---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------
bibikalka said:
The best deal is of course to capture the 5.1.1 update file. I am eager to try it, provided I get root with requires installing via TWRP.
Click to expand...
Click to collapse
We were replying at the same time. I don't think a 5.1.1 file is going to help us on the bricked devices. Once bricked, the preloader seems to just endlessly loop so we would have no way to get the firmware on the device without using something like SP Flash and a scatter file (which eludes me atm)
Theoretically if we have the scatter file I think we should be able to use our 5.0.1 file and restore, then upgrade to 5.1.1 (or stay for root and fastboot boot support)
nEUTRon666 said:
So, if i previously installed the google framework and blocked ota like most people did, this won't block the ota really ?
Click to expand...
Click to collapse
What makes you say that? No one who did that has reported it updating.
I fastboot flashed a system update and now the only way i can get into the bootloader is via adb, then once i am in I cannot interact with it on screen.
Any thoughts on this?
2me3 said:
I fastboot flashed a system update and now the only way i can get into the bootloader is via adb, then once i am in I cannot interact with it on screen.
Any thoughts on this?
Click to expand...
Click to collapse
Are you sure that the Controller/Keyboard is plugged into the USB port next to the HDMI port?
!1
ACiDxCHRiST said:
Are you sure that the Controller/Keyboard is plugged into the USB port next to the HDMI port?
Click to expand...
Click to collapse
yes. this was on my first stv which i ended up bricking. I have 4 of the OG shield tablets which are much more durable in terms of software mods.
In my research I found someone on youtube with a process to downgrade the bootloader, in his tutorial he states clearly that you will no longer be able to interact with the bootloader via controller/keyboard and must use ADB to reach it (exactly where I was)
I believe i got there being trigger happy flashing DTB files, from what i've read (also elsewhere on the internet) the DTB file is the most dangerous thing to flash to the STV and in many cases is not necessary (moving between small updates)
It would seem its better to flash an update without the DTB first and have to re do it than flash it as the flashboot script provided by nvidia states.
Regardless I am disappointed there seems to be such little development on this great little machine, especially compared to the shield tablet. We barely even have a custom rom and the thing ships with an unlock-able bootloader!
Wait I to have lost control of bootloader in my Nivida Shield tv 2017 version after the 7.2.2 update I put in the keyboard and i can select anything in the bootloader. Im not sure if the controller works b/c at first it didnt I had to update the controller as well for it to recognize the controller again. Anyone also having usb driver issues. I'm on windows 7 still so that could be the reason I'm having issues finding these new tegra drivers and the ones from 2018 dont work?
Doing anything listed here will void your warranty. I don't know the laws where you are so assume it makes you a criminal. These things are posted here for educational purposes only. Never follow any guide if you don't understand the commands.
Enough BS, let's jump in.
For windows users. Installing drivers:
1. Plug USB cable into PC.
2. On the A3 prime, instead of using USB as charging, select use USB as Updating Firmware (i forget actual wording)
3. A prompt will come up on Windows, install those drivers.
4. Reboot.
Install adb and fastboot on your PC, it is up to you to do this.
Enable developer options on your phone, and enable USB debugging and OEM Unlocking.
In your CMD/Shell/Whatever you have.
adb reboot bootloader
fastboot flashing unlock (use volume up to confirm)
fastboot flashing unlock_critical (use volume up to confirm)
Congrats you've unlocked the bootloader.
Use 'fastboot reboot' to reboot if you haven't done so already.
-----
this is where the progress on this device comes to a halt.
The kernel source is available from opensource.ztedevices.com
The device codename is Z5157V, the Kernel they have is listed under Z5157V Q(10) Kernel(4.4.185)
What needs to happen next? Someone needs to compile the kernel from source.
Once that is done, they can extract the boot.img from it, use Magisk, and make a modified boot.img
Whoila, they will now have root. Once this person has root, they can extract recovery.img from the device, and we can begin making a custom TWRP, or who knows, maybe Team Win will pick it up (unlikely).
Once we have a custom recovery and working Magisk, it's just a matter of time before we start seeing custom ROMS.
If someone will sign up to be a guinea pig, or has an extra A3 Prime laying around I will continue development. I bricked mine because I was impulsive and honestly, kinda stupid. (browse through thread to see my idiocy)
Until such a time that I come to possess another A3 Prime OR someone steps up to provide a firmware dump, I am unable to help.
Good luck developing!
Only managed to unlock the bootloader but can't seem to find any information on rooting it.
The structure is indeed different than what you would normally expect to find. 'recovery' isn't a valid partition when trying to flash under fastboot for example.
The only reason I'm interested in trying to root this device is because The mtk engineering mode app doesn't work on this phone, at least not the visible version, so band locking doesn't seem possible without root and a different rom.
Yeah, I bricked my device by flashing a universal MTK TWRP.
Came here to say this, do not flash universal MTK.
It is a soft brick, bootloops with no access to stock or TWRP recovery.
The phone's model number is Z5157V and the stock firmware is Z5157VV1.0.0B17 for google indexing reasons. Only place that MAY have it is behind a $40 pay wall.
Managed to get the kernel from opensource.ztedevices.com, just beginning to work on it now (not sure how I'm gonna get my phone out of bootloop mode, but I'll solve it later)
I have never compiled a kernel from source, but I'm eager to learn, I have two days in the wilderness planned ahead of me. If anyone would compile the kernel, that is great. If not? I'll get it done when I get back.
Been playing around with the phone and key combinations, I think I have found a way to use SP Flash Tool in it's current soft brick state.
If I am successful in compiling the kernel, I will share it.
If I am able to unbrick this phone, I will write a guide.
If those two things happen, I'll be moving forward to make an AOSP based custom ROM for this phone. Maybe a first for a $100 device, but I like root.
If anyone else knows HOW to compile the kernel, you'd put me a few steps ahead when I get back.
Either way, nearly 200 lurkers on this thread, I hope to have answers soon.
ORANGE
zaduma said:
I was able to unlock the bootloader. Confirmed with a boot message on boot.
Click to expand...
Click to collapse
how does that bootmessage read?
does it say : "ORANGE STATE" et cetera ?
s4goa said:
how does that bootmessage read?
does it say : "ORANGE STATE" et cetera ?
Click to expand...
Click to collapse
Yeah
Orange State
Device can't be trusted
Booting in x seconds
1st.
zaduma said:
to make an AOSP based custom ROM for this phone. Maybe a first for a $100 device, but I like root.
Click to expand...
Click to collapse
why do you think you are first ? their are literally tons of €100 phones in circulation!
s4goa said:
why do you think you are first ? their are literally tons of €100 phones in circulation!
Click to expand...
Click to collapse
Who knows, guess I don't have much experience in this area. (Cheap phones) Figured it's usually not worth it to do all this work for a throwaway phone.
That said, I've been wrong before!
zaduma said:
Yeah
Orange State
Device can't be trusted
Booting in 5 seconds
Click to expand...
Click to collapse
same here after
Code:
fastboot flashing unlock_critical
(bootloader) Start unlock flow
FAILED ()
Finished. Total time: 21.830s
s4goa said:
same here after
Code:
fastboot flashing unlock_critical
(bootloader) Start unlock flow
FAILED ()
Finished. Total time: 21.830s
Click to expand...
Click to collapse
Strange it fails, try flashing unlock first, then flashing unlock_critical, make sure to press volume up on phone when prompted.
fastboot
dude, in order to avoid fuqqing confusion you ought not abbreviate a shell command like you do.
Anyhow, since we two guys have different phones, it makes sense only for me to generally discuss the rooting strategy on a ZTE Spreadtrum phone, as the specifics will differ too much.
I have fastboot on a Lumigon T3 as my "ZTE blade A5 2019" does not have fastboot.
---------- Post added at 16:07 ---------- Previous post was at 15:55 ----------
rooters, come join https://forum.xda-developers.com/group.php?groupid=1925
s4goa said:
dude, in order to avoid fuqqing confusion you ought not abbreviate a shell command like you do.
Anyhow, since we two fuys have different phones, it makes sense only for me to generally discuss the rooting strategy on a ZTE Spreadtrum phone, as the specifics will differ too much.
I have fastboot on a Lumigon T3 as my "ZTE blade A5 2019" does not have fastboot..
---------- Post added at 16:07 ---------- Previous post was at 15:55 ----------
rooters, come join https://forum.xda-developers.com/group.php?groupid=1925
Click to expand...
Click to collapse
Sorry, for clarity if on Linux type su and your root password, or use sudo to escalate your permissions if you don't have permission to use fastboot as a regular user.
If you're on windows, consider a free upgrade, but also leave out sudo and once in fastboot mode on a3 prime, type
1. (sudo) fastboot flashing unlock
2. (sudo) fastboot flashing unlock_critical
Press volume up when prompted and congrats your warranty is now void, bootloader unlocked. I'm not responsible for your choices.
__________
Also yeah, the phones even have different chipsets the Z5157V is a MTK phone
fastboot
this "orange state unlock bootloader" has - however - nothing or little to do with "Developer Menu option UNLOCK BOOTLOADER"
do you know more about this?
on my Lumigon these 2 unlockings are independent of each other, never mind the identical name "unlock bootloader".
s4goa said:
this "orange state unlock bootloader" has - however - nothing or little to do with "Developer Menu option UNLOCK BOOTLOADER"
do you know more about this?
on my Lumigon these 2 unlockings are independent of each other, never mind the identical name "unlock bootloader".
Click to expand...
Click to collapse
Yeah, you'll need to toggle that option to on in Developer Settings before entering the bootloader/fastboot mode and running the unlock commands or they will fail.
we're screwed !
dude, dammit! they cryptosign bootloaders now LINK
if that is true we're done for! how to hack those cryptochips?
its for Unisoc SC9863A Spreadtrum but also other CPUs.
zaduma said:
:crying:
Click to expand...
Click to collapse
s4goa said:
Click to expand...
Click to collapse
Well, I am terribly sorry to hear that, but at least the A3 prime is on mediatek chipsets which I don't believe has any such protection.
Spreadtrum SC9832E, 64bit
zaduma said:
the A3 prime is on mediatek chipsets
Click to expand...
Click to collapse
if you are sure that boot.img can be "modded" then the A3 is a superior phone, let me tell you.
---------- Post added at 22:54 ---------- Previous post was at 22:50 ----------
anyway... its kewl u posted at https://www.gizmochina.com/2020/07/01/zte-blade-a3v-key-specs-leak/
s4goa said:
if you are sure that boot.img can be "modded" then the A3 is a superior phone, let me tell you.
---------- Post added at 22:54 ---------- Previous post was at 22:50 ----------
anyway... its kewl u posted at https://www.gizmochina.com/2020/07/01/zte-blade-a3v-key-specs-leak/
Click to expand...
Click to collapse
Keep checking for updates, once I'm back in town that's exactly what I'll be working on.
Sorry to anyone following this thread, I will continue working on building the kernel, extracting boot, and getting this phone rooted. I will need a volunteer to test the root solution once it is built, and then if possible follow a few steps and extract recovery.img on your newly rooted device and send that to me.
I just don't have the time today even though I said I would be doing it. If there are any volunteers with an A3 prime let me know!
Just thought id let let you guys know if I manage to pull and write I'll keep you all updated but would need help of someone who knows how to Dev or at lest understand what I'm trying to say to post guide that's if it works fingers crossed
Ok so far I've for read and dump working in edl bootloader unlocked
I hope to get a Dev to help format this better as I am not one but basicly what I did was remove licence vererifacation on all update material and adb/fastboot and edl related stuff with lucky patcher after setting up a storage link with spatcher and then reinstalled through spatcher and odexed it all I also formatted an old recover IMG and installed that on spatcher and with all that together you can basicly enter com port 4 on edl rather than 3 that allows some basic read write functions then because I had removed varifactaion on the shell.apk it allowed me to unlock boot loader without keys then I reset every thing and did a adb reboot fastboot and used miricle box to unlock boot loader again without mods and even though it couldn't find keys it allowed it
Forgot to mention to trigger crash dump you load a dsu and boot from it
crashdumpexploit said:
I hope to get a Dev to help format this better as I am not one but basicly what I did was remove licence vererifacation on all update material and adb/fastboot and edl related stuff with lucky patcher after setting up a storage link with spatcher and then reinstalled through spatcher and odexed it all I also formatted an old recover IMG and installed that on spatcher and with all that together you can basicly enter com port 4 on edl rather than 3 that allows some basic read write functions then because I had removed varifactaion on the shell.apk it allowed me to unlock boot loader without keys then I reset every thing and did a adb reboot fastboot and used miricle box to unlock boot loader again without mods and even though it couldn't find keys it allowed it
Click to expand...
Click to collapse
Hi, I'm a tech journalist and would love to have a chat about your found exploit.
Any chance to get in touch via e.g. Discord?
HerrTiSo said:
Hi, I'm a tech journalist and would love to have a chat about your found exploit.
Any chance to get in touch via e.g. Discord?
Click to expand...
Click to collapse
Hello and dood afternoon, @HerrTiSo
Welcome to XDA! I hope you'll always have a beneficial time on XDA.
However, we'd appreciate if discussions and the exchange of information or knowledge is publicly done on XDA as the XDA members only benefit from public sharing of them. It'd be great if you refrain from pushing our members to social media in future. Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
Sure, thanks for the clarification. Let's see if we can figure this out on here.
crashdumpexploit said:
Just thought id let let you guys know if I manage to pull and write I'll keep you all updated but would need help of someone who knows how to Dev or at lest understand what I'm trying to say to post guide that's if it works fingers crossed
Ok so far I've for read and dump working in edl bootloader unlocked
I hope to get a Dev to help format this better as I am not one but basicly what I did was remove licence vererifacation on all update material and adb/fastboot and edl related stuff with lucky patcher after setting up a storage link with spatcher and then reinstalled through spatcher and odexed it all I also formatted an old recover IMG and installed that on spatcher and with all that together you can basicly enter com port 4 on edl rather than 3 that allows some basic read write functions then because I had removed varifactaion on the shell.apk it allowed me to unlock boot loader without keys then I reset every thing and did a adb reboot fastboot and used miricle box to unlock boot loader again without mods and even though it couldn't find keys it allowed it
Forgot to mention to trigger crash dump you load a dsu and boot from it
Click to expand...
Click to collapse
Yeah sure you did...LOL
Hey, is there any news?
crashdumpexploit said:
... you can basicly enter com port 4 on edl rather than 3 ...
Click to expand...
Click to collapse
I'll give you the benefit of the doubt, it's possible that you have some information not known to us mortals.
But if you're talking ComPorts you're talking though your hat.
Please clarify. Something like:
"Yeah, I'm getting this VID/PID and there is interface #0 which is a bidirectional bulk, but I'm also getting interface #1 which is a CDC for something interesting..."
(OP not seen since March.)