Related
Earlier before reading the forum and all the "recall" related business, I was working on my "stock" G-Tablet. It has had no updates and I have been trying to keep it as stock as possible.
It popped up offering me OTA 1.0.1-3053.
Seems the most recent number I ever heard before was like 2960-something.
Description said it offers: (1) Improved overall system performance; (2) Improvements to the Weather application; and (3) Improved reliability of the Factory Data Reset procedure.
Is this just one of the old OTA updates I never saw before -- or is this something new?
I'm not installing it until I know what's going on.
Rev
I just got my Gtab last week, and I think that was the OTA that popped up when I powered up. Flash (from xda) works with it, whereas I have the impression that it didn't before that. Also Slingplayer, albeit with the "start it many times" problem.
Jim
OTA from stock today..
Picked up a new gtab at Sears. Had the OTA 3053 update. It's much snappier than the original. Still a bit sluggish, but much more usable than the original.
butchconner said:
Earlier before reading the forum and all the "recall" related business, I was working on my "stock" G-Tablet. It has had no updates and I have been trying to keep it as stock as possible.
It popped up offering me OTA 1.0.1-3053.
Seems the most recent number I ever heard before was like 2960-something.
Description said it offers: (1) Improved overall system performance; (2) Improvements to the Weather application; and (3) Improved reliability of the Factory Data Reset procedure.
Is this just one of the old OTA updates I never saw before -- or is this something new?
I'm not installing it until I know what's going on.
Rev
Click to expand...
Click to collapse
BTW, did you have TNT lite installed? I think roebeet said that he removed the TNT updater. Maybe that's why no notification before?
Jim
Oops. Didn't notice you said 'stock'. So not sure why you didn't get a notification before this....
jimcpl,
I deliberately kept the wifi off while I was checking out all the "stock" stuff I wanted to know.
Ironically, I installed CWM to make a backup of the original stock stuff and forgot that CWM would change the recovery.img.
Now I have to either find and replace recovery.img in the backup or find another way to take out CWM.
Or......just go ahead and MOD it, which is what I intended anyhow after checking out the stock stuff.
Thanks.
Rev
Hi.
OK. Got it.
I think that roebeet said that there's now a way to go back to stock recovery, after CWM. Might want to check with him?
That was one of the reasons I've stayed stock, plus didn't want to lose OTA yet...
Jin
jimcpl,
I found the thread, which has two images from VS in it. But when I deleted the recovery "assert" from the .zip file as it said is required not to conflict with CWM -- it didn't. It just left it there and so I still have v. 2967 with CWM.
I will leave him a note in Development.
Anyhow, thanks. I'll either find a way or move on to the next project.
Rev
3053 came out a week(?) ago - TnT Lite 2.3.0 / 2.4.0 are based on it.
There's are stock ROM's if you want to backout of a mod (see the link in the FAQ area of my sig), or you can use nvflash and use bekit's original firmware image with it.
roebeet,
I have successfully run the 2967 rom update as you suggested, but took out the "assert" line for the recovery.img as the thread says is necessary. As a result, it didn't take out CWM -- which is my main goal.
Is there a way to overwrite CWM short of going to nvflash. I think I have the files to do a flash, but not the utilities needed to do it. So it would be easier if I could overwrite.
Rev
It's bad when you have to reply to yourself???!!!
But I also had a thread in Development which Roebeet answered and triggered me to find the answer to this too.
I wound up taking the Vanilla 3053 rom as listed in Roebeet's FAQ thread. I made a "Recovery" file with Command in it to start the update. Then put that along with the downloaded 3053 update.zip in the /sdcard directory. Brought up CWM and started the zip file running. It picked up the recovery file the first time through, showed the boxwitharrow that goes with regular recover and completed.
Then it rebooted again and repeated the same load using regular recovery. When all was done, I had a OTA 3053-level tablet. I then reset the user data to make sure all was OK there, and I went in manually in ES file manager and deleted the old CWM directory and backup directory under it.
So now I am back to 3053 totally stock and should be able to get any OTA update that might come along.
Thanks to all who made suggestions.
Rev
EOT (End of Thread)
butchconner said:
roebeet,
I have successfully run the 2967 rom update as you suggested, but took out the "assert" line for the recovery.img as the thread says is necessary. As a result, it didn't take out CWM -- which is my main goal.
Is there a way to overwrite CWM short of going to nvflash. I think I have the files to do a flash, but not the utilities needed to do it. So it would be easier if I could overwrite.
Rev
Click to expand...
Click to collapse
Ah, I was the one who wrote that as I recall. Weeks ago, but it feels like a lot longer. I think earlier revisions of clockworkmod required that or else update.zip file updates would fail. But .08 seems A-OK.
roebeet, et al:
I think it would be a really good thing if folks would confirm what you are saying here -- which is what I experienced last night when I took mine back down to OTA 3053 version.
I was able to setup, flash the 3053 rom and cover up CWM (after doing necessary repairs with it) without doing an nvflash -- just using the recover process.
I think this is important because lots of folks would have the reassurance that they could recover if they make a mistake with only the normal flash procedure.
Or if someone wants to try modding they can know that they will be able to get back to an essentially "stock" machine if they need return/warranty options.
Rev
butchconner said:
roebeet, et al:
I think it would be a really good thing if folks would confirm what you are saying here -- which is what I experienced last night when I took mine back down to OTA 3053 version.
I was able to setup, flash the 3053 rom and cover up CWM (after doing necessary repairs with it) without doing an nvflash -- just using the recover process.
I think this is important because lots of folks would have the reassurance that they could recover if they make a mistake with only the normal flash procedure.
Or if someone wants to try modding they can know that they will be able to get back to an essentially "stock" machine if they need return/warranty options.
Rev
Click to expand...
Click to collapse
At this point I would recommend flashing to 3053 anyway - it's the latest one and you can do the next person who owns your device a favor. I wouldn't even look at the previous two firmware updates, at this point.
For me, it definitely works with cm .08 and it definitely wipes recovery with standard. Do that, plus a user data wipe, and you are 100% vanilla.
Yea!!!!!!
Merry Christmas to All and to all -- how about let's get some sleep and then get down to some serious modding!
Rev
I am in need of some help. I had used the one-click root to remove clockwork off my TF and upgrade to the 8.6.5.13 image tonight......and then when I tried to go into the stock recovery I get a failure. If I install clockwork I can boot into recovery but can't get the stock recovery to work.
Can someone provide the image for the stock recovery for 8.5.4.13 and also instructions on how to get it installed and working??
It would be greatly appreciated - I have a feeling that if I can't get this fixed I may not be able to install any future updates.....
Oh, yeah....the one click root failed for me so I am no longer rooted. Will need to find another way to get root again.......
thanks.
Just root again using nvflash method
Go here... http://-rom-development.com
You will need to register with the site to download the files, but this will return you to full stock rom as well as stock recovery.
There is no such thing as stock recovery.
BTW..no links to outside forums that require regristration
Well thanks for raining on the parade pal. If u want to be a smart ass about it, then I will say this. If you have ever seen the exclamation point or android screen with gears while performing an OTA update, that would be a sudo stock recovery. It is needed to install official firmware updates and is accessed by "booting into recovery partition." Secondly, I wasn't aware of me posting an external link that requires registration a violation of xda rules. If it is, my bad. Just trying to help..as thats what we do here on xda...help others. If its not, then STFU.
cavsoldier19d said:
Well thanks for raining on the parade pal. If u want to be a smart ass about it, then I will say this. If you have ever seen the exclamation point or android screen with gears while performing an OTA update, that would be a sudo stock recovery. It is needed to install official firmware updates and is accessed by "booting into recovery partition." Secondly, I wasn't aware of me posting an external link that requires registration a violation of xda rules. If it is, my bad. Just trying to help..as thats what we do here on xda...help others. If its not, then STFU.
Click to expand...
Click to collapse
WOW....A little butt hurt are we
Stock recovery
Ok, before I go too far, could someone provide the behavior of the stock recovery? If I boot into it and don't have an image to recover, would I see an Android guy with some gears that would then generate an error - due to no image to recover?
If so then I think the stock recovery is still there....I just have never used it.
Thanks....
That is correct. The "stock recovery" has no menu system. If you have cwm installed then it doesn't exist anymore. If cwm isnt installed then its there
If you rooted and then installed clockworkmod recovery, then you won't be able to access what is the stock recovery. If you don't have cwm recovery installed, then you have the stock recovery. There is almost nothing to the stock recovery, but the two graphics that I mentioned above, leading some people to believe that there is no stock recovery at all. Just because there are no options to choose from doesnt mean there isn't a recovery partition to install the firmware from. If you want the stock rom, go to asus's website and download the firmware. I believe you place it on your sd card and then boot into the recovery parition but holding down the volume down + power until at the very top of the screen it gives you the option to boot into the recovery partition by pressing the volume up button. At that point, the system should see the firmware and start installing it.
Thanks! I guess that I may be ok, will find out later.
The only wierd part is that I lost root and even though I am using the one-click method that uses the live ISO, I can't get root back. I may need to use one of the manual methods to get root again.
Thanks for all the help.
mahendrix said:
The only wierd part is that I lost root and even though I am using the one-click method that uses the live ISO, I can't get root back. I may need to use one of the manual methods to get root again.
Thanks for all the help.
Click to expand...
Click to collapse
Ok, Now I have a major lesson learned - using one-click root - I "removed" root and went thru the reboots and then re-rooted it again and NOW IT WORKS! The one difference? I had a Droid X plugged into my pc when previously attempting to root and the process wasn't working quite right.
When I removed my Droid and unrooted/rerooted, the process went right and my TF is now rooted! So when attempting to root in the future, don't have any other Android devices attached - they may cause issues.
Lesson learned - thanks for all the help.
cavsoldier19d said:
Go here... http://-rom-development.com
You will need to register with the site to download the files, but this will return you to full stock rom as well as stock recovery.
Click to expand...
Click to collapse
cavsoldier19d said:
Well thanks for raining on the parade pal. If u want to be a smart ass about it, then I will say this. If you have ever seen the exclamation point or android screen with gears while performing an OTA update, that would be a sudo stock recovery. It is needed to install official firmware updates and is accessed by "booting into recovery partition." Secondly, I wasn't aware of me posting an external link that requires registration a violation of xda rules. If it is, my bad. Just trying to help..as thats what we do here on xda...help others. If its not, then STFU.
Click to expand...
Click to collapse
Well let's just see here - how about we read the http://forum.xda-developers.com/announcement.php?a=81!
[*]Encouraging members to participate in forum activities on other phone related sites is prohibited.
[*]Off-site downloads are permitted if the site is non-commercial and does not require registration.
Ding ding! We have a winner! In your first post you nailed it right on the head! You need to register to download - two violations of XDA rules.
Closing thread as this has been answered multiple times.
Click to expand...
Click to collapse
I have a Droid Charge and two days ago I used ODIN 1.82 to install "[email protected]" (Tweaked v2 ROM); however, I just noticed there is an update "[email protected]" which has a couple of folders and not md5 (META -INF and system).
I am a newbie but it was not difficult to used ODIN to install the original md5 file; however, I am stuck trying to install the update. Any tips what tools to use of where I can have the instructions to install the update "[email protected]"?
Thanks.
BTW I have not had any problem so far using the original ROM.
White
whitejul said:
I have a Driod Charge and two days ago I used ODIN 1.82 to install [email protected]5 (Tweaked v2 ROM); however, I just noticed there is an update [email protected] which has a couple of folders and not md5 (META -INF and system).
I am a newbie but it was not difficult to used ODIN to install the original md5 file; however, I am stuck trying to install the update. Any tips what tools to use of where I can have the instructions to install the update [email protected]?
Thanks.
BTW I have not had any problem so far using the original rom.
White
Click to expand...
Click to collapse
You can flash it in CWM. Also you can get the same update by installing the black and blue theme in tweaktools.
Tweaked v2 ROM update
PaulN64007 said:
You can flash it in CWM. Also you can get the same update by installing the black and blue theme in tweaktools.
Click to expand...
Click to collapse
Thanks for pointing me to the right direction, questions are where to find instructions how to use CWM and tweaktools.
Can you help?
Thanks.
White
whitejul said:
Thanks for pointing me to the right direction, questions are where to find instructions how to use CWM and tweaktools.
Can you help?
Thanks.
White
Click to expand...
Click to collapse
There is a lot of information in the first 3 posts in the Tweaked 2.0 thread that you should read. 3rd post is where you'll find how to use tweaktools. A lot of android phones use CWM and something you should learn. There are a lot of youtube videos that maybe better to watch then trying to read about it.
PaulN64007 said:
There is a lot of information in the first 3 posts in the Tweaked 2.0 thread that you should read. 3rd post is where you'll find how to use tweaktools. A lot of android phones use CWM and something you should learn. There are a lot of youtube videos that maybe better to watch then trying to read about it.
Click to expand...
Click to collapse
It took me a while but this is what I have unsuccessfully done:
Downloaded the upgrade for CWM “[email protected]” then I checked its MD5 was correct A2B101E9556BB2BD59F226E25E87D1F6
Placed the above file on my SD card
On my Droid Charge I pressed the POWER button and from the choices I selected RECOVERY
My phone rebooted into:
Android system Recovery (3e)
enter: OK Key. Select: Vol UP / Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe catch partition
checking confirmation -> check (0)
Not need checksum confirmation
already executed!!...
--movi_checking done!...
# MANUAL MODE #
From the above choices I use Vol UP / Vol Down to select “apply update from sdcard”, then pressed the HOME key
Screen changed to:
Android system Recovery (3e)
Choose a package to install:
/mnt/sdcard
../
'[email protected]'
I used the Vol UP / Vol Down, selected the zip file and pressed the HOME key A yellow triangle with an exclamation mark and a green droid icon appeared on the screen. A few seconds later the screen flashed up
I pressed the MENU key and underneath the same caption showed in step (4) above, it was displayed:
-- Install /mnt/sdcard …
Finding update package …
Opening update package
Verifying update package …
E:signature verification failed
Installation aborted
Therefore, I had no other choice to reboot my phone and to come back to the original Tweaked 2.0 release (4.10), which I continue using.
Did I do anything wrong? Please advise.
Thanks
White
U need to install cwm using odin. U tried flashing tweaked with stock recovery whichvis why it didnt work. U need to get the .md5 for cwm n flash it using odin (same way u flashed the rom). then u hold vol down/home/power. When u see the samsung logo u can let go of the power button but keep holding down the other 2 til u see the cwm blue text. Then ull be able to flash the zip file
Sent from my SCH-I510 using XDA
cnoevl21 said:
U need to install cwm using odin. U tried flashing tweaked with stock recovery whichvis why it didnt work. U need to get the .md5 for cwm n flash it using odin (same way u flashed the rom). then u hold vol down/home/power. When u see the samsung logo u can let go of the power button but keep holding down the other 2 til u see the cwm blue text. Then ull be able to flash the zip file
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
Thanks.
I guess I'm done.
I searched and downloaded "0817_charge_recovery.tar.md5" and installed using ODIN as you suggested (I dunno is this is the last CWM release)
Then I i booted into the CWM by pressing the key combination you suggested
Then I selected the "[email protected]" file
let the install go and then rebooted
I do not what were the changes between the original built and this latest update but anyway, I'm learning; therefore, I will appreciate any other tips.
Thanks again!
White
tweak stock theme
Will Tweak Stock Theme for 1.4 work on Tweak Stock 2.0 FP1?
mromblad said:
what the hell kind of question is this. Seriously. first, read both threads, its the same friggin theme. second, read the forums there are numerous threads about using a theme from one version of a rom on another. do you make posts like this on purpose?
Click to expand...
Click to collapse
Kind of harsh but I have to agree. No matter how much people say not to use a theme for a different ROM, some idiot says that it works and then people start asking if X theme will work on Y ROM... JUST DON'T DO IT MOST LIKELY IT WILL CAUSE OTHER PROBLEMS...
mromblad said:
what the hell kind of question is this. Seriously. first, read both threads, its the same friggin theme. second, read the forums there are numerous threads about using a theme from one version of a rom on another. do you make posts like this on purpose?
Click to expand...
Click to collapse
You do realize that on the left-side of the page it shows how many times a user has posted...right?
So let's analyze the situation. That person had posted 1 time. And since you were responding to one of his posts, logic would suggest that that was his first post on here. So "do you make posts like this on purpose?" yes. I'm guessing that he purposefully made his first post on purpose.
Now I know that you have a whopping 37 posts to your name, but you should be a little nicer to the new guys b/c chances are they 1) haven't read every post on here and 2) they came to a forum thinking they could ask questions (I know, such a radical concept isn't it). and 3) they probably didn't realize that the theme was the same from 1.4 to 2.0 hence why they asked the question. </rant>
---------- Post added at 04:41 AM ---------- Previous post was at 04:35 AM ----------
whitejul said:
Thanks.
I guess I'm done.
I searched and downloaded "0817_charge_recovery.tar.md5" and installed using ODIN as you suggested (I dunno is this is the last CWM release)
Then I i booted into the CWM by pressing the key combination you suggested
Then I selected the "[email protected]" file
let the install go and then rebooted
I do not what were the changes between the original built and this latest update but anyway, I'm learning; therefore, I will appreciate any other tips.
Thanks again!
White
Click to expand...
Click to collapse
Did your install of Tweaked2.0 go well?
If not, I was having problems (it would get stuck on the SAMSUNG screen) until I used ODIN to put CWM on there (like you did) but before I flashed the Tweaked2.0 zip file, I had to go to Mounts (in CWM) and tell it to mount /system (after you do that it should then say "unmount /system" where before it simply said "mount system").
Good luck and enjoy!
lol, silly lane, adding fuel to a fire for no reason. It's ok man, it really is. a whopping 37 posts means nothing because there is no count for the amount of threads that you read. that's the important issue here friend, reading. You don't need an account to read the forums. For all you or anyone else knows he comes from a forum where asking stupid questions is allowed. Granted the mods let it happen here too, but they shouldn't.
But yes, thank you for taking the time to analyze the situation that you weren't part of to begin with. Next time, keep it to pm if you have a problem with what I said, thanks.
~Sircrazy
ah ha!
mromblad said:
lol, silly lane, adding fuel to a fire for no reason. It's ok man, it really is. a whopping 37 posts means nothing because there is no count for the amount of threads that you read. that's the important issue here friend, reading. You don't need an account to read the forums. For all you or anyone else knows he comes from a forum where asking stupid questions is allowed. Granted the mods let it happen here too, but they shouldn't.
But yes, thank you for taking the time to analyze the situation that you weren't part of to begin with. Next time, keep it to pm if you have a problem with what I said, thanks.
~Sircrazy
Click to expand...
Click to collapse
An alias! ah ha!
I only pop back over to these forums every now and again but I wanted to see what fun stuff was posted here. And anyways, there are nicer ways of telling the newbs how to browse the forums.
Some people are too quick to ask questions before reading, but you see that on a lot of threads. And at least he wasn't asking something crazy stupid like "I just flashed an HTC rom on my Motorola Droid and I know I'm in the wrong forum but could you help me..."
Did your install of Tweaked2.0 go well?
If not, I was having problems (it would get stuck on the SAMSUNG screen) until I used ODIN to put CWM on there (like you did) but before I flashed the Tweaked2.0 zip file, I had to go to Mounts (in CWM) and tell it to mount /system (after you do that it should then say "unmount /system" where before it simply said "mount system").
Good luck and enjoy!
Click to expand...
Click to collapse
Actually I did. These are the steps I went through:
I used ODIN to go back to the original Verizon ROM my phone had (stock) and then let the phone to update itself (OTA).
Once I got my phone back to "original" I use ODIN to install the latest CWM (Clockwork Recovery Mod) 0302_charge_recovery.tar.md5 which gave me version v5.0.1.7 ( I do not understand why different numbers under the same version).
Once I installed CWM, I did not know what to do with it. I just read somewhere else that I had to have that installed, so I did.
Then as a final step I use again ODIN to install the latest Tweaked v2 ROM “[email protected]”
As of now I am testing the new built. One thing that annoyed me was that there were 22 applications under the Applications menu; they were disorganized in four panes (or windows) so I had to manually rearranged them in alphabetical order, and after that I got rid off two panes, fitting 16 apps per pane/window.
Other than that, I'll continue using the new ROM.
White!
Question about physical buttons not lighting up
In order to limit thread creation I'm hijacking this one due to the general title.
After flashing TWO Charge's with Tweaked 2.0 the row of physical buttons no longer light up. I flashed one back to EP4D (which made them light up again) and then back to Tweaked (which borked them again) already to see what would happen.
Is this part of the tweaks to disable them lighting up? Is there somewhere I can go modify a script and have them light up again?
Thanks
(I'm a Chemical Engineer, I can do anything with cars but when it comes to anything past Odin and CWM, my nerdiness is superceded by this forum. )
Shimee said:
In order to limit thread creation I'm hijacking this one due to the general title.
After flashing TWO Charge's with Tweaked 2.0 the row of physical buttons no longer light up. I flashed one back to EP4D (which made them light up again) and then back to Tweaked (which borked them again) already to see what would happen.
Is this part of the tweaks to disable them lighting up? Is there somewhere I can go modify a script and have them light up again?
Thanks
(I'm a Chemical Engineer, I can do anything with cars but when it comes to anything past Odin and CWM, my nerdiness is superceded by this forum. )
Click to expand...
Click to collapse
This is due to the BLN mod that is included in the rom. See the link below for more info on what BLN does.
It can be disabled through tweaktools if you'd rather have the key backlights act normally (CWM Modifications->BLNModOff)
http://rootzwiki.com/topic/20362-mod-bln-for-droid-charge/
Thank you, that's exactly what I was looking for.
But my god finding what TweakTools is and how to enter it was difficult. You can't forget that noobs have no idea about some things so it would have been nice to get a link to tonsit's site or a brief explanation of Terminal Emulator, or something. But then again that's not as satisfying as searching on your own.
Shimee said:
Thank you, that's exactly what I was looking for.
But my god finding what TweakTools is and how to enter it was difficult. You can't forget that noobs have no idea about some things so it would have been nice to get a link to tonsit's site or a brief explanation of Terminal Emulator, or something. But then again that's not as satisfying as searching on your own.
Click to expand...
Click to collapse
To be fair - there is a link to all of that in the OP - well, it's the second post, but I figured most would look there as that outlines all the changes that had gone down. Sorry for the confusion - here is the link from that post. Check it out, it ought to be pretty helpful.
Hello all!
Do you want TWRP, a 2nd bootloader, and custom roms at your fingertips for your Kindle Fire HD? Well you have come to the right place! Over the past months, through trial and error, I've managed a full-proof, easy method to unlock the Kindle Fire HD's true potential. While this is aimed at 7" devices, it should work no problem on the 8.9 either - however you will have to use your head. These instructions are geared towards the 7", and you will have to realize what changes to this blueprint you personally will need to make with the 8.9.
!WARNING! WHILE THIS HAS WORKED FOR ME ON MULTIPLE DEVICES, YOU MUST FOLLOW THE DIRECTIONS CAREFULLY. I PERSONALLY SUGGEST YOU FIRST BUY A SkOrPn FACTORY CABLE IN CASE ANYTHING GOES WRONG. (Although using this guide, it almost certainly will not. Still, those cables come in handy!! :good:
Also, I would like to point everyone to seokhun's thread on this matter, which came before my own: http://forum.xda-developers.com/showthread.php?t=2271909
BIG thanks to LinearEquation for helping maintain this thread. Trust any advice he gives; it WILL help! :thumbup:
Although our posts on this process are essentially similar, he goes far more in depth on the process, and has an excellent troubleshooting section if something here goes wrong for you and I cannot respond to your question soon enough (although if done right, that won't happen )
Ok. Lets begin!
Step One: Download Kindle Fire First Aide, an amazing tool which is only getting better: http://forum.xda-developers.com/showthread.php?t=2096888
This is probably the most work-intensive step, although once you have it you'll be glad you do. You are to follow the directions on this thread and install the necessary files, and adb drivers. This is necessary for your KFHD7 to communicate with your computer properly. When finished, make sure your Kindle has ADB enabled under its device settings.
lets see if you're ready for step 2. Plug your kindle in and check your device manager. If your kindle fire shows up as "android adb interface" then you sir/ madam are ready. If not, please use the Kindle Fire First Aide (hereafter referred to as KFFA) thread to find out where you went wrong. The answer you seek will be there, I promise you.
Step Two: BACK UP ANY FILES/FOLDERS/MOVIES/ETC YOU WANT TO KEEP. STEP THREE WILL WIPE YOUR DEVICE!
Step Three: Here, we are going to use KFFA to reset our device to 7.2.3. Make sure you have transferred any backups you have made to your computer. Run KFFA and select the option that reads "Reboot the Kindle into Fastboot Mode". At the time of this posting, there are two options to do this. Try the preferred option first, and if that doesn't work, try the alternative method. Alternatively, just plug your kindle in with a fastboot/factory cable to get it into fastboot. YOUR DEVICE MUST BE IN FASTBOOT MODE FOR THE NEXT STEP
Step Four: while in fastboot mode, in KFFA, use the option "COMPLETELY RESTORE THE KFHD7 7.2.3. This will take a while, and you will be prompted at certain points to continue. I usually chose not to wipe user data at the end, as for me at least it takes forever and shouldn't be necessary.
Step Five: While still in KFFA, Disable Amazon's OTA updates with the option provided. This is important - If an update sneaks by, you will have to start from scratch!
Once KFFA says it's finished, unplug your device and hold the power button to hard-reset it. Now boot it back on. Your kindle will now be stock 7.2.3, with google play and superuser installed, along with root permissions.
Step Six: Here we go! Download the provided FireFlash11.apk, kfhd7-Freedom-boot-7.3.0.img, and kfhd7-twrp 2.4.4.0-recovery.img to your computer. Connect your KFHD7, make sure you check "allow installations of unknown applications" on your kindle's options (they will have reset thanks to KFFA, don't forget), and go to either the amazon or google play marketplace and find a file browser you can use to navigate to your download folder. Find where you placed the FireFlash11.apk, open it, and install.
Step Seven: Almost there guys! Open up your new FireFlash app. The first thing you (should) notice is that there is a warning that you have the incorrect bootloader at this moment. Check the box that says "Flash kfhd7-u-boot-prod-7.2.3.bin. scroll to the bottom of the app, where it says "execute", and press "flash, install script". Exit the program and reboot your device.
Step Eight: Now that your kindle has rebooted, open up the FireFlash app again. This time, you should see no warnings at the bootloader. If for some reason you do, STOP and retrace your steps. If you see no warnings, we're ready to install the 2nd bootloader and TWRP!! While still in FireFlash, under "boot partition" it should say "not flashed". Click on the "not flashed", and navigate to the "kfhd7-Freedom-boot-7.3.0.img" that we downloaded earlier. Check the box next to "apply stack override".
Now, under "recovery partition", again select the "not flashed" box and navigate this time to the "kfhd7-twrp 2.4.4.0-recovery.img". Once in place, check the "disable recovery auto update" box to the right. Now scroll to the bottom, to where it says "execute", and tap "Flash, install script" just like we did before with the bootloader.
Thats it! Select "reboot into recovery" from the Fireflash app if you're still in it, and if you followed the instructions and put everything where it belongs, you should wind up in TWRP after your kindle reboot (dont worry if you see the blue kindle fire logo for a minute before it enters TWRP - it's completely normal. From here you can install custom roms, wipe your cache, and most importantly MAKE BACKUPS! :laugh:
ATM I am using Hashcode's CM10.1 with the 1.5 ghz kernal, with Nova Launcher Prime and LMT launcher. It's simply amazing the difference in both speed and functionality. Hopefully, this guide got you there and now you too can enjoy a fully unlocked Amazon Kindle Fire HD!
Here is a link to the page for Hashcode's CM10.1, If you want to give it a shot I highly recommend it!! http://forum.xda-developers.com/showthread.php?t=2245335
One last note. I want to make it clear that I have not personally developed any of these tools, I've just organized them for you. The real ones you want to be thanking if this works are the developers. Thanks Devs!! :good:
Can u make video on youtube doing this plz thanks
Sent from my Nexus 7 using Tapatalk 2
Unfortunately, I lack the recording equipment or I would do so and link it. however, I promise if you follow the instructions closely, there should be no issues. And if for some reason you run into trouble, just post the problem and I'll do my best to walk you it. I realize there are other guides out there, but in my opinion this is currently the easiest one to get you through it. Good luck friend
Sent from my cm10.1 KFJD
+1
I will finally be doing a video this weekend if no one beats me to it got Saturday off thx open system to for the written tut as I do not have a lot of free time
Sent from my Kindle Fire HD 7
How is this different from my tutorial? I see you included KFFA, but other than that, same method, and you lack the troubleshooting portion as well as only promoting Hashcode's CM10.1.
seokhun said:
How is this different from my tutorial? I see you included KFFA, but other than that, same method, and you lack the troubleshooting portion as well as only promoting Hashcode's CM10.1.
Click to expand...
Click to collapse
I wrote this tutorial as a newer method of achieving TWRP/2nd bootloader, as every OTA update amazon pushes out makes different root methods temporarily break/ ineffective, while this method SHOULD always remain consistent with the help of KFFA doing the rooting. However upon going back and looking over your thread again, I now realize there are quite a few similarities. I strived to simplify mine as much as possible, which is why I avoided the troubleshooting section and left explanations of the process to a minimum. As your guide is more in depth, I will edit my original post to include a link to yours as well should people want additional information/help. Please, don't look at this guide as an attempt to derail yours - rather as an attempt to simplify it even more. I apologize for not mentioning your thread in my original, that was an unfortunate oversight, and thank you for bringing it to my attention :good:
techdeisel said:
I will finally be doing a video this weekend if no one beats me to it got Saturday off thx open system to for the written tut as I do not have a lot of free time
Sent from my Kindle Fire HD 7
Click to expand...
Click to collapse
You're welcome! Good luck on the video, if you complete it and follow these steps to do so, feel free to post a link on here and I will include it in the main thread to help people who need the visual aid to really drive the idea home
Opensystem
Brilliant!!
Had a look at your guide and thought why not...checked with Chris of KFFA about rooting KFHD 7 with 7.4.3 update, he gave me the 'fakebackup' file. Rooted with KFFA....followed EXACTLY from your step 6 to 8 and ATM doing a TWRP backup.
Fantastic job mate.
One question though. If I am going to put another ROM to KFHD7, do I need to do a full wipe (cache, factory, delvik) everytime before a flash install?
regards
fs1023
fs1023 said:
Opensystem
Brilliant!!
Had a look at your guide and thought why not...checked with Chris of KFFA about rooting KFHD 7 with 7.4.3 update, he gave me the 'fakebackup' file. Rooted with KFFA....followed EXACTLY from your step 6 to 8 and ATM doing a TWRP backup.
Fantastic job mate.
One question though. If I am going to put another ROM to KFHD7, do I need to do a full wipe (cache, factory, delvik) everytime before a flash install?
regards
fs1023
Click to expand...
Click to collapse
Check the bottom of my thread in my signature for instructions on installing a new ROM.
fs1023 said:
Opensystem
Brilliant!!
Had a look at your guide and thought why not...checked with Chris of KFFA about rooting KFHD 7 with 7.4.3 update, he gave me the 'fakebackup' file. Rooted with KFFA....followed EXACTLY from your step 6 to 8 and ATM doing a TWRP backup.
Fantastic job mate.
One question though. If I am going to put another ROM to KFHD7, do I need to do a full wipe (cache, factory, delvik) everytime before a flash install?
regards
fs1023
Click to expand...
Click to collapse
I'm delighted to hear that my guide helped you! And sorry for not getting back to you sooner. Seokhun seems to have managed to point you in the right direction, but in case anyone else needs an answer (or of course, you still do ) you only need to fully wipe when going from one type of Rom to another (ie: from stock Amazon to cyanogenmod). This is known as a "clean flash". Otherwise, if say you are simply upgrading cyanogenmod or whatever Rom you're on to a new update, all you really need to do is a "dirty flash" - wipe delvik/cache and you're good to go!
More info on this can be found here http://forum.xda-developers.com/showthread.php?t=1882629
Cheers!
Sent from my Android Kindle Fire HD 7 Running Cyanogenmod 10.1
seokhun said:
Check the bottom of my thread in my signature for instructions on installing a new ROM.
Click to expand...
Click to collapse
And thank you seokhun, for taking such an active role in improving my thread
Sent from my Android Kindle Fire HD 7 Running Cyanogenmod 10.1
techdeisel said:
I will finally be doing a video this weekend if no one beats me to it got Saturday off thx open system to for the written tut as I do not have a lot of free time
Sent from my Kindle Fire HD 7
Click to expand...
Click to collapse
Did u make it dude
Sent from my SGH-T989 using Tapatalk 2
Just wanted to say thanks. I followed steps 6-8 on my wife's new Kindle and all is well and running smooth.
huskyjayboy said:
Just wanted to say thanks. I followed steps 6-8 on my wife's new Kindle and all is well and running smooth.
Click to expand...
Click to collapse
awesome glad to hear it!
Hashcode Stock OS Zips for 7" HD do not block OTA updates
Opensystem said:
awesome glad to hear it!
Click to expand...
Click to collapse
I thought I would post here my experience with the latest 7.4.6 Amazon update.
I placed the update on my HD7" and was able to update.
When I booted, 2nd Bootloader/LOG was gone.
I decided to try this again.
I rooted the tablet and used Fireflash to re-load 2ndbootloader using the 7.4.3 series of Hashcode files.
Once I was not able to boot up into the 7.4.6 OS because the 7.4.3 boot image is used for 2nd bootloader as I expected.
I had downloaded, the 7.4.3.zip stock OS to the sdcard originally so, it was still present locally.
I flashed the OS zip and I was back to 7.4.3.
I downloaded 7.4.6 again to the tablet and again was presented with the Bright update Kindle in "More+/Device/About".
After, the update, I was again without 2nd boot and unrooted.
Point though is the update should not occur if the zip OS was in fact blocking OTA updates.
Is the zip file supposed to have OTA blocked?
I used KFFA to block updates as a second test and once disabled with KFFA, the update is Grayed out and then once re-enabled with KFFA, the update is bright and does update.
I know a lot of people have complained about OTA happening even when blocked...
It looks like this Zip is not blocking.
I will try the LINUX rootplus to see if it blocks OTA...
Regards
galearned said:
I thought I would post here my experience with the latest 7.4.6 Amazon update.
I placed the update on my HD7" and was able to update.
When I booted, 2nd Bootloader/LOG was gone.
I decided to try this again.
I rooted the tablet and used Fireflash to re-load 2ndbootloader using the 7.4.3 series of Hashcode files.
Once I was not able to boot up into the 7.4.6 OS because the 7.4.3 boot image is used for 2nd bootloader as I expected.
I had downloaded, the 7.4.3.zip stock OS to the sdcard originally so, it was still present locally.
I flashed the OS zip and I was back to 7.4.3.
I downloaded 7.4.6 again to the tablet and again was presented with the Bright update Kindle in "More+/Device/About".
After, the update, I was again without 2nd boot and unrooted.
Point though is the update should not occur if the zip OS was in fact blocking OTA updates.
Is the zip file supposed to have OTA blocked?
I used KFFA to block updates as a second test and once disabled with KFFA, the update is Grayed out and then once re-enabled with KFFA, the update is bright and does update.
I know a lot of people have complained about OTA happening even when blocked...
It looks like this Zip is not blocking.
I will try the LINUX rootplus to see if it blocks OTA...
Regards
Click to expand...
Click to collapse
Well if you said that KFFA works, then why not keep that?
Sent from my Kindle Fire HD 7 using xda app-developers app
Hashcode Stock OS Zips for 7" HD do not block OTA updates
r3pwn said:
Well if you said that KFFA works, then why not keep that?
Sent from my Kindle Fire HD 7 using xda app-developers app
Click to expand...
Click to collapse
Yes: Of course, you would keep what works and in this case, KFFA works.
However a ton of people have used various other methods over the last year or two and KFFA is pretty new.
Lots of people have written in saying "why did I get an update when I am blocked?"
I was just offering a reason why.
You can find lots of pre-rooted ROMs on the forum that all say "Rooted, No ADs, and OTA blocked, Gapps, etc.".
The user takes that descriptor on faith and flashes the ROM thinking they have what they need.
In my case, I purposefully updated to 7.4.6 and needed a way to get back to an older version of Kindle OS.
I restored back to 7.3.0 then flashed Hashcode's, 7.4.3 ZIP OS.
It was there I realized I could then update to 7.4.6 which I should not have been able to do.
Just a point of information.
Another point or question is whether there is a difference between a true OTA update that takes place automatically and the case where the user downloads the update to the tablet and then selects "Update" in Device/about. I have always thought it might be nice to have an option where the OTA is blocked but, the user could still download and update manually. When the KFFA method is used to block OTA, both options are blocked.
Regards
galearned said:
Yes: Of course, you would keep what works and in this case, KFFA works.
However a ton of people have used various other methods over the last year or two and KFFA is pretty new.
Lots of people have written in saying "why did I get an update when I am blocked?"
I was just offering a reason why.
You can find lots of pre-rooted ROMs on the forum that all say "Rooted, No ADs, and OTA blocked, Gapps, etc.".
The user takes that descriptor on faith and flashes the ROM thinking they have what they need.
In my case, I purposefully updated to 7.4.6 and needed a way to get back to an older version of Kindle OS.
I restored back to 7.3.0 then flashed Hashcode's, 7.4.3 ZIP OS.
It was there I realized I could then update to 7.4.6 which I should not have been able to do.
Just a point of information.
Another point or question is whether there is a difference between a true OTA update that takes place automatically and the case where the user downloads the update to the tablet and then selects "Update" in Device/about. I have always thought it might be nice to have an option where the OTA is blocked but, the user could still download and update manually. When the KFFA method is used to block OTA, both options are blocked.
Regards
Click to expand...
Click to collapse
If you're trying to get a custom Rom, this thread is for you. If you wanted the newest Amazon update with working root, wrong thread
From the first step to the last, my guide can get you twrp and root and a set up for a new rom. No more, no less
Sent from my Android Kindle Fire HD 7 Running Cyanogenmod 10.1
galearned said:
I restored back to 7.3.0 then flashed Hashcode's, 7.4.3 ZIP OS.
It was there I realized I could then update to 7.4.6 which I should not have been able to do.
Click to expand...
Click to collapse
I don't think Hashcode removed the OTA Scripts. He may have, but I'm not sure.
Sent from my Amazon Kindle Fire HD using xda app-developers app
EDIT: Let's keep this thread focused on how we can move past old methods, and make some progress towards modding. Thanks, and any relevant input is welcome.
Alright. we can get recovery most likely on MF3. many locked moto devices do with a bootstrap. the problem is that if the system breaks, so does recovery, so the actual part about recovery is useless. therefore, in order to be safe, we need a signed stock firmware. this is how it works with My A2. we have a solid recovery that just hijacks the boot, and if you bootloop, you can FXZ (similar to flashing with odin) back to stock. We can now even get custom kernels through kexec, but even without it, there were working aosp/cm based roms.
So, what we really need here to make any progress is a flashable MF3 firmware, so we can get out of soft bricks. Anyone got any ideas?
lkrasner said:
Alright. we can get recovery most likely on MF3. many locked moto devices do with a bootstrap. the problem is that if the system breaks, so does recovery, so the actual part about recovery is useless. therefore, in order to be safe, we need a signed stock firmware. this is how it works with My A2. we have a solid recovery that just hijacks the boot, and if you bootloop, you can FXZ (similar to flashing with odin) back to stock. We can now even get custom kernels through kexec, but even without it, there were working aosp/cm based roms.
So, what we really need here to make any progress is a flashable MF3 firmware, so we can get out of soft bricks. Anyone got any ideas?
Click to expand...
Click to collapse
There's a few threads about this already which contain several ideas...some tried, some theorized. Why make a new one if it isn't bringing anything new to the table?
Don't get me wrong, your help is MUCH appreciated, it's just a problem when the forum starts getting filled up with information that already exists in other threads.
I think Adam Outler's "Let's get this bootloader unlocked" thread in the "Development" section would be a good place to contribute or maybe even the 'Software Update" thread in the General section.
scott14719 said:
There's a few threads about this already which contain several ideas...some tried, some theorized. Why make a new one if it isn't bringing anything new to the table?
Don't get me wrong, your help is MUCH appreciated, it's just a problem when the forum starts getting filled up with information that already exists in other threads.
I think Adam Outler's "Let's get this bootloader unlocked" thread in the "Development" section would be a good place to contribute or maybe even the 'Software Update" thread in the General section.
Click to expand...
Click to collapse
Sorry, I will admit I jumped in a little quick here. My main point is that it should not be too difficult to get custom recovery working. I am just afraid to do it until I know I can recover, as I am sure the process will involve multiple bricks.
Part of the problem is...this isnt motorola...from what ive been reading is the bootloader checks the phone on boot and overrights any custom recovery with a stock one. Im nkt saying it isnt possible to get a recovery with out an unlock or loki like exploit because I really dont know...actually, isnt the previous loki exploit prettt mucg what your talking about? A way to get recovery and flash with out a bootloader unlock
Although I do agree we need a safe way to return to stock (firmware leak/upload for odin) before we can even try and start experimenting
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
Part of the problem is...this isnt motorola...from what ive been reading is the bootloader checks the phone on boot and overrights any custom recovery with a stock one. Im nkt saying it isnt possible to get a recovery with out an unlock or loki like exploit because I really dont know...actually, isnt the previous loki exploit prettt mucg what your talking about? A way to get recovery and flash with out a bootloader unlock
Although I do agree we need a safe way to return to stock (firmware leak/upload for odin) before we can even try and start experimenting
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Well, if anyone has a link to something that actually explains how loki works, I would appreciate it. I am trying to learn quickly, and as you all know, devices are very different.
From what I understand, LOKI allows recovery to be overwritten, or is at least more permanent. What happens if you were to totally kill your system, could you still get into recovery with loki?
I understand that this is not motorola, and I am not trying to be stubborn here, but I fell like the same basic boot hijack that a ton of locked devices use should work.
lkrasner said:
Well, if anyone has a link to something that actually explains how loki works, I would appreciate it.
Click to expand...
Click to collapse
http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html
and http://forum.xda-developers.com/showthread.php?t=2292157
lkrasner said:
Sorry, I will admit I jumped in a little quick here. My main point is that it should not be too difficult to get custom recovery working. I am just afraid to do it until I know I can recover, as I am sure the process will involve multiple bricks.
Click to expand...
Click to collapse
Please don't apologize, I have no doubt you are going to be a valuable part of what is going to go on with this phone. The only reason I brought up not making a new thread is because of the fragmentation of information different threads cause. Here is the link to Adam's Bootloader Unlock thread:
http://forum.xda-developers.com/showthread.php?t=2255644
Adam has requested (though many didn't respect his request) to not post anything in that thread that doesn't make progress in unlocking the bootloader.
That is why I also mentioned maybe using the "software update" thread as a thread to keep everything together in:
http://forum.xda-developers.com/showthread.php?t=2357039
This thread we are in now can be used as such a thread as well, I just think it is counter productive to have 3 or 4 or more threads going about the same (general) thing. The fragmentation it creates is confusing and time consuming.
So maybe we all need to decide where (which thread) to put all of the bootloader unlock / recovery information into to prevent fragmentation? Maybe rename this thread something like "Bootloader unlock discussion thread" so that ideas and discussion can occur here and any firm findings can be transferred to Adam's thread? If we do this, it will be important to import or at least take into consideration what has already been mentioned and tried in all of the other threads so we don't waste time on something that has already been done or tried.
Here is a link to the "LOKI" thread:
http://forum.xda-developers.com/showthread.php?t=2292157
There are links in the OP of that thread to give better technical information about what LOKI does and how it is used.
scott14719 said:
Please don't apologize, I have no doubt you are going to be a valuable part of what is going to go on with this phone. The only reason I brought up not making a new thread is because of the fragmentation of information different threads cause. Here is the link to Adam's Bootloader Unlock thread:
http://forum.xda-developers.com/showthread.php?t=2255644
Adam has requested (though many didn't respect his request) to not post anything in that thread that doesn't make progress in unlocking the bootloader.
That is why I also mentioned maybe using the "software update" thread as a thread to keep everything together in:
http://forum.xda-developers.com/showthread.php?t=2357039
This thread we are in now can be used as such a thread as well, I just think it is counter productive to have 3 or 4 or more threads going about the same (general) thing. The fragmentation it creates is confusing and time consuming.
So maybe we all need to decide where (which thread) to put all of the bootloader unlock / recovery information into to prevent fragmentation? Maybe rename this thread something like "Bootloader unlock discussion thread" so that ideas and discussion can occur here and any firm findings can be transferred to Adam's thread? If we do this, it will be important to import or at least take into consideration what has already been mentioned and tried in all of the other threads so we don't waste time on something that has already been done or tried.
Here is a link to the "LOKI" thread:
http://forum.xda-developers.com/showthread.php?t=2292157
There are links in the OP of that thread to give better technical information about what LOKI does and how it is used.
Click to expand...
Click to collapse
Thanks, It still looks to me like loki is a bit more advanced than what I am talking about, though the underlying principle is the same. LOKI allows the phone to actually boot a kernel (or recovery kernel) a boot hijack just loads some files on top of what is already running.
Here is Adam's post where he sums up the boot sequence for the S4: http://forum.xda-developers.com/showpost.php?p=40980436&postcount=46
That may give you some guidance. Towards the end of that thread, Aou posted a possible leaked Samsung PIT file signer but I tested it and confirmed it wasn't actually signing PITs - just making them without the signature. I'm still doing a lot of research and don't have anything more to contribute right now unfortunately.
ashaton said:
Here is Adam's post where he sums up the boot sequence for the S4: http://forum.xda-developers.com/showpost.php?p=40980436&postcount=46
That may give you some guidance. Towards the end of that thread, Aou posted a possible leaked Samsung PIT file signer but I tested it and confirmed it wasn't actually signing PITs - just making them without the signature. I'm still doing a lot of research and don't have anything more to contribute right now unfortunately.
Click to expand...
Click to collapse
Thanks, I am sure that will prove helpful.
This is Adam Outler's Samsung Galaxy S3 bootloader unlock thread. Though it is for the Verizon S3, it still goes very in depth about how the hardware and software are tightly interconnected. Many of the principals still apply to the S4 bootloader. As you can see, the S3 was unlocked via a leak (which is what I think it will take for the S4), but the information in this thread can be very helpful, especially the bootloader sequence parts.
http://forum.xda-developers.com/showthread.php?t=1769411
The entire thread is very interesting. Starting around "Post# 115" and beyond there is talk about (what i believe) you are trying to do with the bootstrap idea. Maybe it will help you.
scott14719 said:
This is Adam Outler's Samsung Galaxy S3 bootloader unlock thread. Though it is for the Verizon S3, it still goes very in depth about how the hardware and software are tightly interconnected. Many of the principals still apply to the S4 bootloader. As you can see, the S3 was unlocked via a leak (which is what I think it will take for the S4), but the information in this thread can be very helpful, especially the bootloader sequence parts.
http://forum.xda-developers.com/showthread.php?t=1769411
Click to expand...
Click to collapse
Thanks, this is what I like to see. the more info the better. If we can make sense of everything and compile a list of useful info, we aught to be able to get something done.
lkrasner said:
Thanks, this is what I like to see. the more info the better. If we can make sense of everything and compile a list of useful info, we aught to be able to get something done.
Click to expand...
Click to collapse
I edited my above post. I believe around post 115 and beyond of the above linked thread there is some information about the bootstrap idea you have.
I had edited my last post but I think this was missed
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
At least that way we can possibly have a safe way back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
I had edited my last post but I think this was missed
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
At least that way we can possibly have a safe way back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
One potential problem is that bootloaders can not be pulled from devices. They have to be obtained through official firmware releases. I'm not sure if pulling the bootloader(s) from the MF3 OTA and inserting them into an MF3 image pulled from a device will equal an ODIN flashable TAR? I think the bootloader(s) in the MF3 OTA are somehow altered once flashed onto a phone. And because the altered bootloader can not be pulled from the device after the flash it could pose a problem to try and put the unaltered version (from the pre-installed MF3 OTA into a device image and create an ODin flashable TAR. Basically, I'm not sure the phone will accept a pre-flashed MF3 bootloader onto a phone that has already experienced a post flash MF3 bootloader. If that makes any sense? (LOL)
scott14719 said:
One potential problem is that bootloaders can not be pulled from devices. They have to be obtained through official firmware releases. I'm not sure if pulling the bootloader(s) from the MF3 OTA and inserting them into an MF3 image pulled from a device will equal an ODIN flashable TAR? I think the bootloader(s) in the MF3 OTA are somehow altered once flashed onto a phone. And because the altered bootloader can not be pulled from the device after the flash it could pose a problem to try and put the unaltered version (from the pre-installed MF3 OTA into a device image and create an ODin flashable TAR. Basically, I'm not sure the phone will accept a pre-flashed MF3 bootloader onto a phone that has already experienced a post flash MF3 bootloader. If that makes any sense? (LOL)
Click to expand...
Click to collapse
Ahhhh I see...makes sense
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
Ahhhh I see...makes sense
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I'm just theorizing there from what I "think" I know. It still might be worth a try. The resulting TAR could:
1. Work, and if so we will have an ODIN flashable firmware for MF3. It doesn't matter if it is 'Frankenstein'd" or not...if it works it works!
2. Not work, but only fail in ODIN not causing anything to change or brick.
3. Not work and cause a soft or hard brick that can not be recovered from because it didn't work.
So, once again, finding someone to test the finished product out would be an issue. I'm guessing someone that is already hard bricked and already previously on MF3 could test because they already have nothing to lose (with JTAG not working for MF3).
I think Aou has deconstructed the MF3 OTA and pulled the bootloader(s) out of it. If someone can pull an MF3 image from their device and the bootloader can be added to it...and it can be made into a flashable TAR, maybe it would work. I don't think it will because of the reasons I listed in my last post...but it might.
Anyone willing to put it together and try it?
I think the problem is that it won't be signed. That is how it was with the a2. We just used fastboot but it would not flash an unsigned image
Sent from my Nexus 7 using xda premium
I think Aou already made some MF3 tarballs for Odin in his stock MF3 thread: http://forum.xda-developers.com/showthread.php?t=2378946&highlight=mf3
He says they don't work because they aren't signed:
Downloads:
I've provided the rom in several different formats. When I last tested the odin-flashable tarballs, they did not work for me (due to signatures, etc). However, I'm still providing these for a few XDA members who will be testing them out on their semi-bricked devices. Additionally, someone might be able to get these signed somehow, and I'll leave this hanging out there as an invitation.
Click to expand...
Click to collapse
ashaton said:
I think Aou already made some MF3 tarballs for Odin in his stock MF3 thread: http://forum.xda-developers.com/showthread.php?t=2378946&highlight=mf3
He says they don't work because they aren't signed:
Click to expand...
Click to collapse
Yup, that's what I was saying. I can try to port a bootstrap cwm, but I really do not want to be the one to test it
Sent from my Nexus 7 using xda premium