Searching this forum is sometime a needle in a haystack, especially when you are looking for something basic. Can someone please point me to a link/page in this forum that gives basic step by step instructions on how to return my D2G to stock to accept the newest upgrades. I think they go something like this, but not sure.
Back up the entire image with Titanium
Obtain the stock sbf (2.4.29 in my case)
Rename to update.zip and copy to root dir on SD
Boot into recovery mode
First wipe cache/reset
Then run the update.zip
Is that it? Do I have to unroot or does the wipe fix that. Am I missing any steps?
Also still looking for the 2.4.33 SBF file if someone has that link.
Thanks.
EDIT: The best reference I found is here: http://forum.xda-developers.com/showthread.php?t=1060694
It is a bit more complex than I described above, but it will work.
I am upgrading to GB as we speak (about 2 hours of downloading.upgrading to get here!)
Never did find the 2.4.33 file, but just OTA'd it, no problem!
Hope this link helps someone else, there is a lot of this going around!
TC
Okay, so here's my dilemma. Unlike most other people I want boot sound enabled on my ROM's. I have spent countless hours searching every forum and post, trying everything that is suggested. Nothing seems to work. The only breakthrough I've came across the last several months is that while running a ROM with boot animation support and a stock kernel I am able to achieve both custom mods. What I'm shooting for is to be able to do the same with a custom kernel. I'm relatively new to this but through process of elimination I have concluded that the coding for this lies in the boot image. Maybe I'm wrong but it seems that way.
Listed under the features in almost every single ROM the developer usually puts "muted boot sound" my question is, how do I un mute the sound? Is there a simple fix, possibly a script that I can run or does it involve pulling apart the boot image and editing code? If it has to do with the boot image could somebody possibly tell me what code needs to be edited. I have no problem decompiling and recompiling boot images, I'm just not sure what part of the code needs to be added. Any help would be extremely appreciated! I'll keep my fingers crossed!
Sent from a Shaftamle Galaxy S3
Shaftamle said:
Okay, so here's my dilemma. Unlike most other people I want boot sound enabled on my ROM's. I have spent countless hours searching every forum and post, trying everything that is suggested. Nothing seems to work. The only breakthrough I've came across the last several months is that while running a ROM with boot animation support and a stock kernel I am able to achieve both custom mods. What I'm shooting for is to be able to do the same with a custom kernel. I'm relatively new to this but through process of elimination I have concluded that the coding for this lies in the boot image. Maybe I'm wrong but it seems that way.
Listed under the features in almost every single ROM the developer usually puts "muted boot sound" my question is, how do I un mute the sound? Is there a simple fix, possibly a script that I can run or does it involve pulling apart the boot image and editing code? If it has to do with the boot image could somebody possibly tell me what code needs to be edited. I have no problem decompiling and recompiling boot images, I'm just not sure what part of the code needs to be added. Any help would be extremely appreciated! I'll keep my fingers crossed!
Sent from a Shaftamle Galaxy S3
Click to expand...
Click to collapse
see my post in andybone's mod thread. you need an edited volumedb in system/etc folder where the volume is raised. i think they just set the volume level in the db to 0 and the file i posted raises it so you can now hear sounds. confirmed to work on CR6.2 by myself. oh and you will need a PowerOn.ogg in system/media/audio/ui folder... hope it helps!!:highfive:
Hello, I'm a noob with mild skill with jailbreak and mods. (WII,Windows,etc..) I unlocked my boot loader the other day. Apparently did not get S off. My phone now has the tampered message in the boot loader. Not really important to me because I own my phone. However I still need to root it and am not sure this will prevent me from accomplishing this. Does anyone know? Also cannot seem to nail down how to get root done or by who's instructions? Google search pulls up confusing info and I need specifics for my model correct? 3rd. Issue the recovery I used was from twrp which I festooned by computer and all worked great. Now however when I hit recovery and TWRP loads it is frozen. No touch commands work. I was told to flash newer recovery the same way I did first but command says error cannot load. So now I'm stuck. Phone works but it's not completed. Not sure which to tackle first. Please helps
You should list this is in the HTC one M7 questions forum... Not this one in order to get some help
Thank for the advice. New to xda and was not sure exactly were to go. Just fyi, i did find a resolve to my problem. Apparently I was renamining the twrp image files as I was directed to by another blog but I was putting img as part of the file name. When you are in the command prompt I was typing the file name exactly as it read but i was not adding a second img to the end of the command example: file name twrp.img has to be commanded as twrp.img.img. So infact i should of never renamed putting img at the end of the file name. It was causing confusion. So I renamed it twrp and thats it. really a Noob mistake and I shouldve known better. Anyhow I did reflash a updated twrp file and all is good and rooted now. Thanks
I dunno, but I thought maybe I could make a separate thread about a possible way to poke into the LeapFrog Epic's preloader so it could accept unsigned images. LeapFrog won't spill the beans for us, as their staff (falsely) claims to know next to nothing about it, so unless we somehow managed to social-engineer them into giving us a signed ROM or an unlocked bootloader, our only chance is to patch it so it would ignore the lack of digital signatures.
What I've done so far is to run a strings check on the preloader and uboot binaries - fastboot seems watered down somehow as it lacked references to "oem unlock" and so on, but none of that Amazon Fire-style failsafe seems present from what I can tell.
Preloader: http://pastebin.com/H9QbzqC0
lk: http://pastebin.com/kSxRKYna
Boot files from the latest firmware revision are attached here, so if anyone is interested, please please please let me know so we can fix bricked units and finally port TWRP to this underrated kids' tablet.
blakegriplingph said:
I dunno, but I thought maybe I could make a separate thread about a possible way to poke into the LeapFrog Epic's preloader so it could accept unsigned images. LeapFrog won't spill the beans for us, as their staff (falsely) claims to know next to nothing about it, so unless we somehow managed to social-engineer them into giving us a signed ROM or an unlocked bootloader, our only chance is to patch it so it would ignore the lack of digital signatures.
Click to expand...
Click to collapse
Bumping the thread.
Would also like to know is this is possible
If I may ask, how did you extract the strings from preloader and lk? Did you use a hexeditor or there is another app?
Gibz97 said:
Bumping the thread.
Would also like to know is this is possible
If I may ask, how did you extract the strings from preloader and lk? Did you use a hexeditor or there is another app?
Click to expand...
Click to collapse
I used this utility to do a strings dump off an Epic ROM:
http://split-code.com/strings2.html
It did turn up some interesting stuff but I was wondering if a binwalk or perhaps an IDA disassembly analysis would do wonders so we can finally poke into this tablet.
blakegriplingph said:
I used this utility to do a strings dump off an Epic ROM:
http://split-code.com/strings2.html
It did turn up some interesting stuff but I was wondering if a binwalk or perhaps an IDA disassembly analysis would do wonders so we can finally poke into this tablet.
Click to expand...
Click to collapse
Thanks for the tool but I cannot seem find a way to use it.
@gursewak.10 or @smartmanvartan please chime in to help us because they were able to hack the preloader of k4 note and lk of RCA Viking Pro respectively
I also know a friend who is willing to donate a spare Epic, if that helps.
As for using Strings2, the following batch script should work:
Code:
@echo off
strings2 %1 > test.txt
pause
Just drag a binary to be analysed into the batch file, and a resulting text file with strings and stuff should be generated.
Hello friend
You need to tweak lk to unlock bootloader . i am giving you my phone's both files(.you can easily compare them.
on unlocked bootloader u can flash unsigned images via write memory option of SP flash tool .
Try HxD hex editor
gursewak.10 said:
Hello friend
You need to tweak lk to unlock bootloader . i am giving you my phone's both files(.you can easily compare them.
on unlocked bootloader u can flash unsigned images via write memory option of SP flash tool .
Try HxD hex editor
Click to expand...
Click to collapse
Hmm, I can flash the preloader to my leapfrog via SPFT, but not anything else. Write memory works, and I can flash stuff one at a time to it, but I couldn't get the tablet to force itself out of flash/download mode and into normal mode. There's no reset button, and not even taking the battery off does the trick.
However, on my working Epic, I can alter the demo system image, flash it back using Write Memory and still end up with a working device, just as long as the preloader isn't messed with in any way. Right now I am at a loss as to how to revive my other Epic, short of taking it apart and shorting KCOLO and GND. It also didn't help that the testpoints aren't labeled at all. :/
Also, I did a quick logcat while running the FOTA utility, and I managed to get a few URLs off the said logs. Problem is that while the ZIPs may be of some use, they're incremental and there doesn't seem to be a full scatter/zip image to restore a faulty unit. There definitely needs to be a way to patch the bootloader so we can do whatever we want to it, but is there any one of you guys who are experts when it comes to MTK modding?
Any more ideas?
Anyone, please?
Bumping in case there's anyone interested in poking into this.
Now this is interesting let us see what we can do.
Warrior1988 said:
Now this is interesting let us see what we can do.
Click to expand...
Click to collapse
You happen to have an Epic with you? Please let me know if you need more than just the firmware images. I've tried contacting LeapFrog regarding this issue to no avail. They did give my friend and I the kernel sources, but it's no use as the bootloader has to be unlocked for custom boot or recovery images to be used.
Is anyone willing to test if SP Flash Tool 5.1532.00 works on the Epic? I managed to flash a complete system image to a bricked Epic but I was unable to revive it as it has been bricked prior due to a botched preloader flash. The ROM's on my main Epic discussion thread, but one should take note to flash just the boot, recovery and system images and see if the device still works.
im also poking around in this since my volume up button doesnt work in bootloader mode
i have a figo gravity x55l
i can also upload the stock rom files that can be checked if needed
SP6RK said:
im also poking around in this since my volume up button doesnt work in bootloader mode
i have a figo gravity x55l
i can also upload the stock rom files that can be checked if needed
Click to expand...
Click to collapse
Are you able to muck around with LK or sbchk using IDA Pro or some other tool? Makes me wonder if merely deleting /system/bin/sbchk would disable boot-time checks or if there's more to it than just that.
blakegriplingph said:
Are you able to muck around with LK or sbchk using IDA Pro or some other tool? Makes me wonder if merely deleting /system/bin/sbchk would disable boot-time checks or if there's more to it than just that.
Click to expand...
Click to collapse
well i tried hex editors but lk.bin isnt decoded for my rom so half of my lk file is not showing me anything exept weird characters but i can see some of the other half.
if you delete the file...will it brick?...will it even boot?
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
What device are you referring to? Is this for an MT8127 tablet?
blakegriplingph said:
What device are you referring to? Is this for an MT8127 tablet?
Click to expand...
Click to collapse
i have a figo gravity x55l ? and it is not a tablet
it is a mt6753 great phone btw!
im a starting developer and got this phone so i can learn from my mistakes of course?
but this should work on any device that you can get a hold of its boot.img from its firmware
I was following a guide on unlocking the bootloader and rooting my v450 device, this was using QFIL to load the abl_a and abl_b files but made a mistake and accidentally loaded the file to the MPT partition on the device. I made a backup of the abl_a partition but not of any other partitions.
Now the device gets stuck on the LG V50 boot screen and I can't get it to boot into any mode other than EFL.
One way I feel might work is by obtaining a backup of the MPT file, if this is correct does anyone know where I can find this,
Does anyone know whether this is something I can fix or if the phone is dead, any help is appreciated.
Thanks.
The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck
feyd2blak said:
The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck
Click to expand...
Click to collapse
Thank you man, this is reassuring to hear, I'm going to look for a QFIL dump now, will update this post if I find any success.
T
feyd2blak said:
The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck
Click to expand...
Click to collapse
This worked, I manually replaced every partition and the phone is working now. thank you so much, I probably wouldn't have tried this without the info you provided.
link to dump used: https://drive.google.com/file/d/13AJ8SnKmpOrTQF2EQ1odJK7-4qfUTIdF/view
doublespicc said:
T
This worked, I manually replaced every partition and the phone is working now. thank you so much, I probably wouldn't have tried this without the info you provided.
link to dump used: https://drive.google.com/file/d/13AJ8SnKmpOrTQF2EQ1odJK7-4qfUTIdF/view
Click to expand...
Click to collapse
Glad I could help!
Tell me, in the dump that is uploaded there are files rawprogram0.xml, rawprogram1.xml, etc. How to flash them?