Database Users

Samsung Continuum Questions

Hey guys, I have a few questions that I either couldn't figure out after researching for hours (seriously) or I just need some clarification on. I apologize if these questions have already been adressed. Also, I'm new to android so try to keep it simple for me.
1. What is a kernel? Can I flash multiple kernels to the same rom? Can I flash a kernel via clockwork recovery?
2. Ive been having problems with clockwork recovery. I got it installed (meaning I can get to the clockwork recovery menu after flashing the .tar file via odin and applying the update.zip) but if I select any of the items from the clockwork recovery menu the screen immediately goes blank and I have to perform a battery pull to boot the phone up again.
3. Clockwork recovery doesnt stick. When I apply the update.zip (which contains clockwork recovery mod) from the regular recovery menu I get a "e:verification whole-file error" message thingy unless I flash the .tar file via odin every single time before hand in which case I do get to the clockwork recovery menu, but the problem from the question above occurs.
4. How to flash the latest clockwork recovery + any needed kernel + any bug fixes + latest version of needed files? Plz post a link to a place where I can download the appropriate files. I ask this even though its been asked before because im wondering if the files I used are outdated and thats why I had the problems mentioned above.
5. Is there anyway I can restore my phone back to the way i first bought it (meaning no root, no update, etc.)
Thanks in advance!
Sent from my SCH-I400 using XDA App

The only one I can answer out of those is #5 (I suck at the coding part lol, I'll let someone more knowledgable answer those)
Go to settings -> Privacy -> Factory Data Reset.
Pretty sure that's what you're looking for

You're having weird problems. My clockwork doesn't stock either but I don't think anybody's does with the continuum. I have a clean DL17 ROM, the peanutbutta jelly time kernel and I haven't had any problems
Sent from my SCH-I400 using XDA App

Ill try again later on today and ill see what happens. Maybe it was just a one time glitch. Are you supposed to select the items from the clockwork recovery menu using the camera button or the menu button?
On a separate note, about the clockwork recovery sticking, i heard about a kernel that made it stick. True or false? And if I install a kernel on my phone now, and then flash the DL17 rom, do the effects of the kernel now apply to the DL17 rom as well? does the clockwork recovery mod that i flashed before also apply to the DL17 rom as well, or do i have to reinstall clockwork recovery? what bugs does the DL17 rom have? where are the fixes?
Sent from my SCH-I400 using XDA App

Oh and whats the difference between the following kernels? and can they all be flashed using clockwork recovery? and which kernel do you use? and what bugs to each of the kernels have?
1. http://forum.xda-developers.com/showthread.php?t=1057072
2. http://forum.xda-developers.com/showthread.php?t=943833
3. http://forum.xda-developers.com/showthread.php?t=926555
Sent from my SCH-I400 using XDA App

Can someone please post a link of this thread in the continuum android development section or point this thread to a dev because I don't have permission and I really badly want these questions answered! Thanks!

I'll try and answer some of your questions as soon as I get to a computer.
Sent from my space time Continuum using the XDA App.
EDIT:
1. I'm not a dev, but here is what I understand about kernels. A kernel is part of android that contains the "drivers". You can use different kernels with the same ROM, but if you're asking if you can use 2 kernels at the same time with 1 ROM, then no, you can't. Kernels are usually flashed with clockwork, but we continuum users also use ODIN because of the difficulties with CWM not wanting to work on some phones.
2. Are uoi using the menu button to select in CWM? If you are, try clicking the lock button instead.
3. I can't help you there, sorry. :-/ My CWM always worked...
4.I'll see if I can't find a guide or 2. I'll make another video tut if needed.
5. There is a stock ODIN file that I helped make floating around here somewhere. The only thing is, the ODIN is rooted because it was needed to create the files.
I'll answer more questions later

Ok thanks a lot that helped clarify a few things. A video tutorial or a written tutorial would be great and if u could answer my other questions that would be fantastic! Thanks
Sent from my SCH-I400 using XDA App

Oh and do u flash a kernel in odin by putting the .pit file in the pit section and the kernel in the pda section?
Sent from my SCH-I400 using XDA App

Flash kernels using clockwork
Sent from my SCH-I400 using XDA Premium App

ntien said:
Oh and do u flash a kernel in odin by putting the .pit file in the pit section and the kernel in the pda section?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
Yes, that is how you flash a kernal in odin.

I didn't have to do mine that way
Sent from my SCH-I400 using XDA Premium App

Thanks for the answers guys! Can u look at the other questions that I posted and try to answer them?
Sent from my SCH-I400 using XDA App

ntien said:
Ill try again later on today and ill see what happens. Maybe it was just a one time glitch. Are you supposed to select the items from the clockwork recovery menu using the camera button or the menu button?
On a separate note, about the clockwork recovery sticking, i heard about a kernel that made it stick. True or false? And if I install a kernel on my phone now, and then flash the DL17 rom, do the effects of the kernel now apply to the DL17 rom as well? does the clockwork recovery mod that i flashed before also apply to the DL17 rom as well, or do i have to reinstall clockwork recovery? what bugs does the DL17 rom have? where are the fixes?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
AGH!!!! SO MANY QUESTIONS IN 1 POST >.<
ok.... Let's try and answer these *sigh*
1. If you are using the original CWM then, select is using the lock button. If you are using the new CWM the imnuts put out a few days ago, then selecting is the camera button. The latest CWM available, is the first link in the next quote.
2. ugh... I can't really comment on that, I've never had problems with CWM...
3. Yes, they do apply to the DL17 ROM.
4.CWM sticks as long as you flashed all the files correctly.
5. Which DL17 ROM? Adr's SC, or the debloated?
6. again, which one?
ntien said:
Oh and whats the difference between the following kernels? and can they all be flashed using clockwork recovery? and which kernel do you use? and what bugs to each of the kernels have?
1. http://forum.xda-developers.com/showthread.php?t=1057072
2. http://forum.xda-developers.com/showthread.php?t=943833
3. http://forum.xda-developers.com/showthread.php?t=926555
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
1. This is from what I know, just CWM. There isn't a "kernel" so to speak.
2.This is an epic kernal that I recommended trying
3. I would also recommend trying out this kernal. I'm not entirely sure what the differences between 2, and 3 are though...

ntien said:
Hey guys, I have a few questions that I either couldn't figure out after researching for hours (seriously) or I just need some clarification on. I apologize if these questions have already been adressed. Also, I'm new to android so try to keep it simple for me.
1. What is a kernel? Can I flash multiple kernels to the same rom? Can I flash a kernel via clockwork recovery?
2. Ive been having problems with clockwork recovery. I got it installed (meaning I can get to the clockwork recovery menu after flashing the .tar file via odin and applying the update.zip) but if I select any of the items from the clockwork recovery menu the screen immediately goes blank and I have to perform a battery pull to boot the phone up again.
3. Clockwork recovery doesnt stick. When I apply the update.zip (which contains clockwork recovery mod) from the regular recovery menu I get a "e:verification whole-file error" message thingy unless I flash the .tar file via odin every single time before hand in which case I do get to the clockwork recovery menu, but the problem from the question above occurs.
4. How to flash the latest clockwork recovery + any needed kernel + any bug fixes + latest version of needed files? Plz post a link to a place where I can download the appropriate files. I ask this even though its been asked before because im wondering if the files I used are outdated and thats why I had the problems mentioned above.
5. Is there anyway I can restore my phone back to the way i first bought it (meaning no root, no update, etc.)
Thanks in advance!
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
1. From wikipedia:
"In computing, the kernel is the central component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components). Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources (especially processors and I/O devices) that application software must control to perform its function. It typically makes these facilities available to application processes through inter-process communication mechanisms and system calls.
Operating system tasks are done differently by different kernels, depending on their design and implementation. While monolithic kernels execute all the operating system code in the same address space to increase the performance of the system, microkernels run most of the operating system services in user space as servers, aiming to improve maintainability and modularity of the operating system. A range of possibilities exists between these two extremes."
You can only run one kernel at a time.
2. dfggd's instruction vid might help: http://www.youtube.com/watch?v=USHpl0s7qhk
3. CWM does not stick (yet)
4. You'll have to do your own research on this one. Personal taste comes in to play and it is ever-changing.
5. I know there's a DJ20 dump around here somewhere....

hahahaha im sorry but i have a lot of questions lol. thanks for the help. if u can answer the other questions thatd be great, thanks. and in response to your answers:
TO DFGGED:
1. i need plain english here. whats the difference between the two clockworks? does it really matter which one i flash? if not, then i plan on using the original clockwork recovery mod so that i can flash a different kernel.
2. maybe its becuz i used the menu button to select an item so it freaked out. ill try it again as soon as i can find somebodys windows computer i can borrow to flash odin
3. and if i flash a kernel its permanent? i cant remove the kernel or flash a different kernel and overwrite it or something?
4. i definitely flashed all the files correctly and it didnt stick for me. maybe we just have different definitions of sticking. i have to flash odin every single time prior to going in to clockwork recovery. do u not have to do the same? i heard that flashing a custom kernel made it stick though so maybe thats it...
5. wait...i thought Adr's DL17 rom was the only one out for the samsung continuum. and that is the debloated/debinged/etc. isn't it?
6. if there are different roms and im just clueless, then can u post the link for both of the actual rom and fixes?
TO DFGGED(PART 2):
1. but doesnt it say flash the recovery kernel via odin? is that not a kernel?
2. what does this kernel do?
3. again, what does this kernel do?
TO WEUDEL:
1. kind of understood that lol but at least i get the basic idea
2. yup that helps to clarify a bit, thanks
3. i heard that custom kernels DOES make it stick. true or false?
4. look at my questions to dfgged above (in this post) and see if u can explain the differences to me in the kernels and original clockwork recover vs. imnuts clockwork recovery (and if imnuts clockwork recovery's recovery kernel is actually a kernel) and if there are indeed two different roms and the difference between them. and a link to a place where i can download the latest files for the fixes and actual rom. i would really appreciate it!
5. yup found it. thanks

oh and how do you flash a kernel via clockwork?
thanks so much for ur patience!!!! i owe all of u guys lol

ntien said:
oh and how do you flash a kernel via clockwork?
thanks so much for ur patience!!!! i owe all of u guys lol
Click to expand...
Click to collapse
You go to install zip file then install from sd card
Sent from my SCH-I400 using XDA Premium App

Well, since you are now over the 10 post threshold, I would suggest that you ask the specifics of these kernels within the kernel threads. That or try them all out and go with the one you like. This is a small community and the more testing everyone can do the better off we will all be.

I would but I dont have a windows computer so testing is pretty much impossible for me so...yeah anything anybody knows about the questions I just asked would be extremely helpful. Thanks again
Sent from my SCH-I400 using XDA App

Install 3.2.2 after LTE Upgrade

I just received my US 3G model Xoom back after having the LTE upgrade done and like an idiot, flashed the ROM below instead of just rooting the already installed 3.2.2 ROM
[ROM/UPDATE] Android Honeycomb 3.2.2 - Stock & Rooted
I'm experiencing the same Wifi issue a lot of other users are reporting so I've reverted back to the Stock image. My problem is I didn't root and nandroid before installing the ROM above so I can't get to 3.2.2. I can only get as far as 3.2 and then Android reports it's up to date.
Any ideas of how to get to 3.2.2 other than the ROM above? I'll buy a USB Host cable if I can find the proper .zip files to upgrade from 3.2.

mmayhew said:
I just received my US 3G model Xoom back after having the LTE upgrade done and like an idiot, flashed the ROM below instead of just rooting the already installed 3.2.2 ROM
[ROM/UPDATE] Android Honeycomb 3.2.2 - Stock & Rooted
I'm experiencing the same Wifi issue a lot of other users are reporting so I've reverted back to the Stock image. My problem is I didn't root and nandroid before installing the ROM above so I can't get to 3.2.2. I can only get as far as 3.2 and then Android reports it's up to date.
Any ideas of how to get to 3.2.2 other than the ROM above? I'll buy a USB Host cable if I can find the proper .zip files to upgrade from 3.2.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/22648028/HLK42Bsystemboot4g.7z
That will get you to HLK42B which is 3.2.2. These are the boot and system images which you can flash thru fastboot, something you should be familiar with if you flashed back to stock images...works the same way. However, this the earlier version from the Pilot group which I was part of. Apparently the ones being sent out now are HLK75C or something like that. I am trying to find anyone with one of the recently updated Xooms that can dump the System/Boot images for me. Until then, these are better than nothing and will get you back up on 4G

AceXMachine said:
http://dl.dropbox.com/u/22648028/HLK42Bsystemboot4g.7z
That will get you to HLK42B which is 3.2.2. These are the boot and system images which you can flash thru fastboot, something you should be familiar with if you flashed back to stock images...works the same way. However, this the earlier version from the Pilot group which I was part of. Apparently the ones being sent out now are HLK75C or something like that. I am trying to find anyone with one of the recently updated Xooms that can dump the System/Boot images for me. Until then, these are better than nothing and will get you back up on 4G
Click to expand...
Click to collapse
Perfect, thanks a ton man. Is there a better place than the 'Xoom Android Development' XDA forums to look for the most recently dumped images?

mmayhew said:
Perfect, thanks a ton man. Is there a better place than the 'Xoom Android Development' XDA forums to look for the most recently dumped images?
Click to expand...
Click to collapse
Not that I know of at the moment. Trying to get someone to dump the new images for me. Also, forgot to mention, password for that 7zip is "solarnz"

AceXMachine said:
Not that I know of at the moment. Trying to get someone to dump the new images for me. Also, forgot to mention, password for that 7zip is "solarnz"
Click to expand...
Click to collapse
Thanks again. Up and running on the 3.2.2 build with no problems.

I took a nandroid after I unlocked the bootloader (which also does at least a factory reset). Can you use that?
Sent from my Xoom using Tapatalk

Unfortunately this did not work on my verizon xoom. I am still getting no internet connection even though it says 3.2.2 Initially it said the sim card was unknown, so I took it out and put it back in and did a reboot. It no longer gives that error, but I still don't get 3g or 4g.

Switch your network to cdma only and power down and back up. That will let it activate.
Sent from my Xoom using xda premium

I don't have the option for cdma only. Mine says home only and automatic. I don't have the LTE/CDMA option at all. I am on 3.2.2
Sent from my PG86100 using xda premium

short/y said:
I took a nandroid after I unlocked the bootloader (which also does at least a factory reset). Can you use that?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yes, that would be great.
Sent from my Xoom using XDA App

bathanr said:
I don't have the option for cdma only. Mine says home only and automatic. I don't have the LTE/CDMA option at all. I am on 3.2.2
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I have this problem too. I can't get 3g/4g to work on any pre-3.2.2 image including this 'pilot' 3.2.2 image uploaded here. I can get 3g working with the ROM mentioned in my original post but wifi doesn't work.
Sent from my Xoom using XDA App

If you can create a link or pm me the backup as well that would be great

mmayhew said:
Yes, that would be great.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I've uploaded a Rogue Recovery backup to MEGAUPLOAD -- http://www.multiupload.com/BTA7S2DMPZ. Unzip everything and put the files in clockworkmod/backup/<some-name> either on your microSD card or your internal memory and then boot into recovery (again, I took it with Rogue Recovery V1.2) and do a restore.
I've verified that this is the stock 3.2.2 by inspecting system/build.prop in the system backup -- it says the version is HLK75C.
Sorry, guys, but today's an exceptionally busy day for me so I don't have the time to monitor this board and answer questions as to how to flash Rogue or whether it'll work with the standard CWM or any of that. Hopefully someone else can step up and help with those questions.

How do I dump the system? I will post it if I new how.
Sent from my Xoom using xda premium

short/y said:
I've uploaded a Rogue Recovery backup to MEGAUPLOAD -- http://www.multiupload.com/BTA7S2DMPZ. Unzip everything and put the files in clockworkmod/backup/<some-name> either on your microSD card or your internal memory and then boot into recovery (again, I took it with Rogue Recovery V1.2) and do a restore.
I've verified that this is the stock 3.2.2 by inspecting system/build.prop in the system backup -- it says the version is HLK75C.
Sorry, guys, but today's an exceptionally busy day for me so I don't have the time to monitor this board and answer questions as to how to flash Rogue or whether it'll work with the standard CWM or any of that. Hopefully someone else can step up and help with those questions.
Click to expand...
Click to collapse
Thanks again for the files. I updated to rogue recovery. I created a CWM folder on my SD card and did the restore. It restored fine. I boot up and it shows 3.2.2 and it also shows build version HLK75C. It still does not show 4G nor does it have the option under mobile network settings to choose LTE/CDMA. I have been on the phone with verizon and they have no clue. Motorola said tech level 3 will call me within 24-48 hours.

You need stock files to get that back. It should show lte/CD a in network settings. You could drive to a 4g area and it should activate.
Sent from my Xoom using xda premium

hammer4203 said:
How do I dump the system? I will post it if I new how.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
You need to flash the modded recovery, then in adb shell, run
mount /data
mkdir /data/media/Stock
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/data/media/Stock/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/data/media/Stock/boot.img
sync
Then reboot and pull the files, should be in a "Stock" folder on the internal storage.
*Thanks to solarnz for these instructions
---------- Post added at 04:05 PM ---------- Previous post was at 04:00 PM ----------
bathanr said:
Thanks again for the files. I updated to rogue recovery. I created a CWM folder on my SD card and did the restore. It restored fine. I boot up and it shows 3.2.2 and it also shows build version HLK75C. It still does not show 4G nor does it have the option under mobile network settings to choose LTE/CDMA. I have been on the phone with verizon and they have no clue. Motorola said tech level 3 will call me within 24-48 hours.
Click to expand...
Click to collapse
You guys are wiping the cache and davlik after flashing right?

Is there a way to dump the img files without modding anything? I just sent my xoom out and will be receiving it completely void of any user information so I can do it at that time, but I really don't want to modify the recovery.

nubsors said:
Is there a way to dump the img files without modding anything? I just sent my xoom out and will be receiving it completely void of any user information so I can do it at that time, but I really don't want to modify the recovery.
Click to expand...
Click to collapse
I doubt it. Instructions I received specifically stated that the modded recovery would be needed. You can try unlocking it and running the commands to see but I doubt it will work. You could also try backing up the stock recovery using:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/recovery of=/data/media/Stock/recovery.img
But I believe the modded recovery is what allows the device to be mounted. Wonder if this could be done via fastboot. I have to go to work or I would test it on my own Xoom. Will try later unless someone has already posted images by then.

Ok, I have pulled HLK75C images which should be flashable through fastboot thanks to short/y's Rogue CWM nandroid backup. Usual disclaimers apply here, don't try this unless you know what your doing, not my fault if something messes up. That being said, download images here: http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z zip password is "AceXMachine" without the quotes. After unpacking files go to the command prompt
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
It goes without saying that you need your xoom unlocked for this, need adb setup/working and may need to wipe data. I would do a nandroid backup of your current config before doing this. I was able to restore the "data" backup from a previous backup after restoring the "system" and "boot" from short/y's backup. Only problem I had was my market shortcut on the home screen had to be replaced since my "data" backup had the link to the older market. I rooted this before pulling these images so you should already have root when you flash this. I tested and have working WiFi and 4G with this setup. Feel free to ask questions or PM me if needed. Thanks again to short/y for his nandroid backup...even if he did make me load the Rogue recovery just so I could use it ;P

Samsung OTA update download location?

So I rooted my P6010 and installed CWM but now I'm checking for updates in anticipation of ICS (fingers crossed any day now) and I get an update (stability 17.08MB) but it won't apply as there's no stock recovery installed.
Everything it reboots to try to opens CWM obviously about to apply but can't...
No sign of a downloaded update in the obvious places.
Where do the Samsung OTAs download to?
Sent from my GT-P6810 using XDA Premium App

Jompet said:
So I rooted my P6010 and installed CWM but now I'm checking for updates in anticipation of ICS (fingers crossed any day now) and I get an update (stability 17.08MB) but it won't apply as there's no stock recovery installed.
Everything it reboots to try to opens CWM obviously about to apply but can't...
No sign of a downloaded update in the obvious places.
Where do the Samsung OTAs download to?
Sent from my GT-P6810 using XDA Premium App
Click to expand...
Click to collapse
You can flash the stock recovery back. Get your stock rom, extract the recovery.img
Make a uncompressed tar with just recovery.img in it. Then flash this tar with odin (in the pda)
Tip: dont use 7-zip to build the tar, it just wont work. You should use linux or busybox tar in your tab to create it.
This way you can switch between cwm and stock recovery as necessary.

Thanks for your help. I'm aware of this and I realise I could do this but it's a lot of hassle when I'd prefer to investigate the option of just flashing the OTA using CWM. I just need to find out where the damn file is!
Sent from my GT-P6810 using XDA Premium App

When I try
reboot fota
from a terminal as root, I get a log dumped in /cache/fota
It looks like its looking in multiple locations for a directory tmp_sec_fota.
I dont have any updates, so it all fails, but maybe a clue?

I had a good look around but can't seem to be able to find anything. Shame.
I pulled this screenshot from CWM logs and there's a lot of reference to fota but everywhere I look there's no file even approaching 17MB.
Now I have a real problem because the Tab is my only device apart from a Galaxy Nexus so I don't think I can get a copy of stock recovery. I can flash as I've got MobileOdin though. I'm wondering if it's worth the hassle to do all of this for the OTA or if I should just wait for a version I can flash with CWM.
I only really rooted to sort the rw problem out with my 64GB MSD, if Samsung had have been better devastating I wouldn't have had to.
Sent from my GT-P6810 using XDA Premium App

Stupid swiftkey. I obviously meant developers not devastating.
Sent from my GT-P6810 using XDA Premium App

Those partitions in your photo are not correct for a p6810. You must have the wrong cwm installed.
/system is on /dev/block/mmcblk0p8
on my device, and your data and preload are wrong as well.
Where did you get the cwm. Could you be using one for the p6800? It has different partitions.
See the 7.7 development thread for one suited to the p6810.
Be very careful what operations you select if you have wrong cwm!
Also, any backups you have previously made (with the wrong cwm) should probably be discarded, as the data files will be misnamed/incorrect contents.

I got it from the P6010 CWM thread...? Strange.
I've discarded it and moved back to stock, ran the updates and everything works well now. Ran into some minor permissions stuff with modin but sorted it with removal from such app.
I think a lot of people are going to bump into these problems when ICS hits if they're running CWM.
Sent from my GT-P6810 using XDA Premium App

Oh and thanks for all your help!
Sent from my GT-P6810 using XDA Premium App

Need a guinea pig/tester for a small project

I just need a tester for a small idea i have for installing twrp recovery and 2nd bootloader in a safer manner than usual. The other manners are pretty safe but i figured this seemed really safe because its so simplistic in nature. I don't know whether i will continue this project depending on the results of the test, but basically i thought why not make a 2nd init/bootstrapped twrp that runs a ota update on a zip file that just installs everything for you with a conveniently placed zip file with asserts that it checks for then deletes itself. My first test is just for a 2012 kfhd 7" that either has no 2nd bootloader + twrp and a fastboot cable handy to restore in case this soft bricks it or one with a version of twrp already installed that it higher than 2.6.0.0. I don't wanna post the actual file because i don't want accidental bricks. Chances are based on how this works it will probably brick the first time around because i have not messed with the hijack scripts to mount everything properly yet, but this was taken from another omap based device so if it doesn't work i don't think it will take too much tweaking, but the initial binary it tries to run may cause some havok. I can assure you this should be easy to restore from in twrp by simply renaming a system file, otherwise without a copy of twrp already installed you will have to restore with kffa. I need the kindle that this is being tested on to also be on a rooted amazon os, not another rom. I have no idea if twrp will work with amazon's stock kernel so this should be interesting. post back if you are interested.
If you are wondering why i didn't decide to test this on my own first its simply because i don't feel like having to wipe my entire data partition and restore the data from my pc just to clear selinux xattribs off my data partition so that amazon's kernel will not throw a fit.
So overview for those that don't want to read that big paragraph:
Requirements:
-Running Amazon OS with root
-Have a way to recover from brick (2nd bootloader + twrp or flash back with kffa/srt) - twrp preferred but plz have a never version than 2.6.0.0 installed.
-Have busybox installed

stunts513 said:
I just need a tester for a small idea i have for installing twrp recovery and 2nd bootloader in a safer manner than usual. The other manners are pretty safe but i figured this seemed really safe because its so simplistic in nature. I don't know whether i will continue this project depending on the results of the test, but basically i thought why not make a 2nd init/bootstrapped twrp that runs a ota update on a zip file that just installs everything for you with a conveniently placed zip file with asserts that it checks for then deletes itself. My first test is just for a 2012 kfhd 7" that either has no 2nd bootloader + twrp and a fastboot cable handy to restore in case this soft bricks it or one with a version of twrp already installed that it higher than 2.6.0.0. I don't wanna post the actual file because i don't want accidental bricks. Chances are based on how this works it will probably brick the first time around because i have not messed with the hijack scripts to mount everything properly yet, but this was taken from another omap based device so if it doesn't work i don't think it will take too much tweaking, but the initial binary it tries to run may cause some havok. I can assure you this should be easy to restore from in twrp by simply renaming a system file, otherwise without a copy of twrp already installed you will have to restore with kffa. I need the kindle that this is being tested on to also be on a rooted amazon os, not another rom. I have no idea if twrp will work with amazon's stock kernel so this should be interesting. post back if you are interested.
If you are wondering why i didn't decide to test this on my own first its simply because i don't feel like having to wipe my entire data partition and restore the data from my pc just to clear selinux xattribs off my data partition so that amazon's kernel will not throw a fit.
So overview for those that don't want to read that big paragraph:
Requirements:
-Running Amazon OS with root
-Have a way to recover from brick (2nd bootloader + twrp or flash back with kffa/srt) - twrp preferred but plz have a never version than 2.6.0.0 installed.
-Have busybox installed
Click to expand...
Click to collapse
If I can get my Kindle back up and running, I'll have a go at it for you. But that's a pretty big if right now.
Sent from my iPod touch using Tapatalk, somewhere in the time vortex

Ok thanks, kinda surprised no one has offered before you. This had over 100 views. I guess not too many people are using amazon os that are willing to risk a softbrick. Hopefully this will work I think it is a bit safer than the other methods for beginners that don't want to risk anything.
Tapatalk is annoying me to no end lately... Had to type this message again because quick reply is being glitchy.
Sent from my Amazon Tate using Tapatalk

I could also volunteer. I have an extra Kindle fire 7" Hd. It is rooted and running 7.4.8. I have my trusty fastboot cable and I already have system images for a quick restore.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

The safest method is to "fastboot -i 0x1949 flash bootloader oldbootloader.bin" then "fastboot -i 0x1949 reboot" (assuming you're using the cable and it auto-kicks you into bootloader mode again) "fastboot -i 0x1949 flash recovery twrp.img" and finally "fastboot -i 0x1949 oem recovery"
Edit: This is a more complex version of Hashcode's method, posted on the cm11 installation instructions page.
Sent from my Nexus 7 using Tapatalk

Yea but the thing about that method is sometimes people have bad downloads and don't check for md5sums(not to mention tons of people always having driver issues). If everything is in a signed zip file then if the signature verification fails its about the same as a bad md5sum, not to mention I can add a md5sum comparison in the update-tools script. I was just wanting to make a one click bootloader install option that comes from an apk, kinda like fire flash but simpler.
Sent from my Amazon Tate using Tapatalk

So you're suggesting using an OpenRecoveryScript to flash twrp, the old bootloader, and apply the stack override file to allow for that "2nd boot loader" hack?
Theoretically, that should work, but Amazon might have put restrictions on the recovery to only allow Amazon-signed zip files so that something like this couldn't happen.
Sent from my Nexus 7 using Tapatalk

I thought only Amazon's recovery would have issues with the signature, even if tarp does I can just disable the signature check and use the update-script to check the md5sum before flashing.
Sent from my LG-P769 using Tapatalk

stunts513 said:
I thought only Amazon's recovery would have issues with the signature, even if tarp does I can just disable the signature check and use the update-script to check the md5sum before flashing.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
If TWRP is required, doesn't that make this pointless, because you need the 2nd bootloader hack to make twrp work in the first place? Or perhaps I'm just misunderstanding...
EDIT: when I have the time, I'll see if I can manage to recover from my weird semi-brick and if so, I'll revert to stock and help you test.
Sent from my Nexus 7 using Tapatalk

Thanks, and what I,m saying is you run twrp through 2nd init. I have done it on my phone before, has the same hardware as a kf1 with twice as much ram. I have not seen tarp implemented in this manner before though, only cwm, that's another reason I wanted to test this idea.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
Thanks, and what I,m saying is you run twrp through 2nd init. I have done it on my phone before, has the same hardware as a kf1 with twice as much ram. I have not seen tarp implemented in this manner before though, only cwm, that's another reason I wanted to test this idea.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Oh. You mean a FakeFlash? That's when you flash a zip that actually just overlays a second recovery. Ex. Flashing a TWRP FakeFlash would allow you to use TWRP from the stock recovery without replacing the installed recovery.
Sent from my Nexus 7 using Tapatalk

r3pwn said:
Oh. You mean a FakeFlash? That's when you flash a zip that actually just overlays a second recovery. Ex. Flashing a TWRP FakeFlash would allow you to use TWRP from the stock recovery without replacing the installed recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That kinda sounds like it, for a more detailed explanation, this is what i'm basing it off of: http://forum.xda-developers.com/showthread.php?t=2095825
I believe thats the right link. Had to search for it so it might not be but i think it is.

stunts513 said:
That kinda sounds like it, for a more detailed explanation, this is what i'm basing it off of: http://forum.xda-developers.com/showthread.php?t=2095825
I believe thats the right link. Had to search for it so it might not be but i think it is.
Click to expand...
Click to collapse
Kindle's back up and running, I'll test it.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<

Ok I'll upload it tomorrow. I was just checking my notifications. On a side note I left my kindle in the car and woke and woke up and realized it, having to use my phone to check messages because I will cause a domino reaction if I open the front door... it starts with dogs waking up...
Sent from my LG-P769 using Tapatalk

Sorry I haven't uploaded it yet, i will upload it when I have a chance, my weekend has been chaotic because I've been having to prepare for the job I am starting training for tomorrow. I have been meaning to do it but I hit another snag when I finally got some time to myself I told Ubuntu to upgrade to 14.04 and then unity surprised me and now apparently can't set the window buttons to right so I feel like i'm using a mac which I do not like at all so I decided to use mate since its pretty much what mynfavorite Ubuntu distribution had 10.04lts) so I have been spending the better part of the day reconfiguring it so it was more so like Ubuntu 10.04's theme but I modernized it a bit. Still not done with the theme yet but it is much much better. I think I'm going to attempt to add transparency to the theme. Just realized how off topic i went. Anyways I will see about uploading it tomorrow after I get off of work.
Sent from my Amazon Tate using Tapatalk

Nexus 10 Stock (KTU84P) system.img flashing?

Hey Guys,
I get an error with my tablet about once a month or so where I am unable to use any internet on my tablet, it seems like something breaks to do with google services, I fix it by just reflashing system.img via fastboot.
I'm looking for a way to be able to flash system.img via a zip file or something in recovery so that I don't have to plug my tablet into a computer every time I want to fix it...
Any help would be appreciated.
EDIT: If I knew how to make zips I would have the zip flash system.img, supersu and then xposed framework

Bump

I would assume there is an easier method of fixing your issue but if you want to keep it as such then this may help
http://forum.xda-developers.com/showthread.php?t=2290009
You can flash raw images to partitions but I'm not 100% if you can flash a raw system.img as I believe it may be too big, if it turns out that you can't then you will need to convert the .img easily done using android kitchen (lots of tutorials on xda)
Adding supersu and xposed to the flash is super easy as well
Try it out yourself, do some digging in xda, if you're stuck let me know and I'll help you out
Best of luck!
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
I would assume there is an easier method of fixing your issue but if you want to keep it as such then this may help
http://forum.xda-developers.com/showthread.php?t=2290009
You can flash raw images to partitions but I'm not 100% if you can flash a raw system.img as I believe it may be too big, if it turns out that you can't then you will need to convert the .img easily done using android kitchen (lots of tutorials on xda)
Adding supersu and xposed to the flash is super easy as well
Try it out yourself, do some digging in xda, if you're stuck let me know and I'll help you out
Best of luck!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi,
The problem is caused by an app that I use (can't mention it publicly, but there is a valid reason I use it) and if I restart my tablet while it's running then it messes up google services, the only way I've found to fix it at the moment is by flashing system.img.
I'll have a look into the things you said, thanks so far

Hyflex said:
Hi,
The problem is caused by an app that I use (can't mention it publicly, but there is a valid reason I use it) and if I restart my tablet while it's running then it messes up google services, the only way I've found to fix it at the moment is by flashing system.img.
I'll have a look into the things you said, thanks so far
Click to expand...
Click to collapse
Been completely unable to do any of it :/