So, currently it boots.
Phone not working.
Credits to it goes to droid-dev and of course to Quarx.
So. Like you can see in cm7 you already have 2ndboot.ko.
So, secret here.
All files here: http://fjfalcon.ru/2ndboot/
How to use it...
Code:
insmod 2ndboot.ko
mknod /dev/hbootctrl c `cat /proc/devices |grep hboot|awk '{print $1}'` 0
./hbootuser /sdcard/2ndboot/hboot.cfg
After executing last command press touchscreen... or it won't boot.
What needs to be done for phone to work.
We need to be able to boot different kernel it would help a ton with cm7 and cm9.
Sent from my XT720 using xda premium
mchlbenner said:
What needs to be done for phone to work.
Click to expand...
Click to collapse
The milestone hackers have been stuck here for ages (well, mostly it seems they surrendered a long time ago) and I feel like they're way cleverer than I am. From what I understand, the wrigley usb modem can't be reinitialized (or at least nobody knows how to and there's a severe lack of documentation available to use) and nobody's figured out how to migrate the initialized state to the new kernel. My understanding is that they've decided that kexec wants to reinitialize everything but the modem decides to panic and die instead. I don't really know what I'm talking about, though. I think it needs new eyes. I looked at the drivers a while ago and I didn't think there was a lot of wierdness going on, it registers communication channels and can destroy them, but I guess the problem is that even that basic channel dies.
So, I been working on the ksplice approach (but haven't made any progress). Kexec would be so much easier though. I also have been thinking about making a UART... did quarx make one for defy? Do you think it's the same as the milestone one? But do we really need UART if we can already boot a custom kernel (fastboot, 2ndboot)?
Sounds very hard to do? Is their a demand for this to be done.
For myself I'm a bit burnt out on hacking on this phone.
Sent from my XT720 using xda premium
fjfalcon said:
So, secret here.
All files here: http://fjfalcon.ru/2ndboot/
Click to expand...
Click to collapse
Are you running on Russian sbf? Do you just take devtree from sbf? I assume cmdline comes from /proc/cmdline I just tried on xt720mod.sbf and it started, but crashed during bootanim so probably need to update cmdline and devtree. But really cool nonetheless!
I guess touching the screen is just to cause an interupt?
So what's rhe current thinking--does quarx think atags will help fix the phone? I can work on creating a module for it. Or maybe it's easier to also read atags from a file, too. Hmm. Need to figure out if atags is passed verbatim from cdt or modified by the bootloader... we can probably just save it once from boot5 via fastboot.
Quarx thinking that atags is only bytes.. our current problem with kexec is that function not implemented error on kexec_load
Yea, cmdline and devtree from russian sbf.
Is source for your 2ndboot.ko on github or fjfalcon.ru somewhere?
I used 2ndboot dat was.. so time ago with ms1 repo.
fjfalcon said:
I used 2ndboot dat was.. so time ago with ms1 repo.
Click to expand...
Click to collapse
Ah, ok. Did it work for you? I haven't had luck with these files yet. I'm about to build uart.
Yes, it was working.. =)
Thanks! Do you remember if you used:
http://gitorious.org/droid/2ndboot
or
http://xvilka.github.com/2ndboot-ng/
Here is a idea start new thread!!!!!!!
Sent from my SGH-T759 using xda premium
fjfalcon said:
Yes, it was working.. =)
Click to expand...
Click to collapse
Ok, got it to 2ndboot your last version (i.e. the no radio version) using CBW sbf and your CyanogenMod-7.2.0-MilestoneXT720-20120916-KANG-signed.zip build. Next, I'll try to rebuild all the parts.
Edit: attached fjfalcon's 2ndboot files
Here's a WIP build based on nadlabak and skrilex_cz's latest 2ndboot source for Milestone A853. Source is at
http://github.com/CyanogenModXT720/2ndboot
With this newer 2ndboot what I notice is that ADB works and usb pluging and unplugging is detected (that didn't work for with the previous version). I don't have a SIM with me at the moment, but I assume the radio does NOT work--from what I understand there are patches to the kernel that need to be applied.
I don't think it's necessary to touch the screen to get it to boot--but I have been making sure the screen on. The boot is slower than I expect (maybe because files are being read from sdcard rather than internal, but who knows at this point). Anyway, it takes me about 3-4 minutes after running hbootuser before I see the bootanim start (your phone looks like it's crashed until bootanim starts).
I haven't been able to build a kernel that boots. It's very strange. I can build a working boot.img that works fine via fastboot, but when I take the exact same zImage and use it for 2ndboot, I can't get it to work.
I will switch phones and test this out and let you know if radio works!
i will tests your builds.
I take it you extract from zip put 2ndboot into recovery?
It could not be found in open recovery what im i doing wrong?
Sent from my SGH-T759 using xda premium
You extract the contents of the zip into /sdcard/2ndboot an the run /sdcard/2ndboot/2ndboot.sh (I do it via adb)
I haven't been able to run it from open recovery yet. I've tried, but it causes a full reboot.
Sent from my Nexus 7 using XDA Premium HD app
Mioze7Ae said:
You extract the contents of the zip into /sdcard/2ndboot an the run /sdcard/2ndboot/2ndboot.sh (I do it via adb)
I haven't been able to run it from open recovery yet. I've tried, but it causes a full reboot.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I had same issue. I tried via openrecovery and had a full reboot.
How do you do via adb (in recovery or in Android ) ? Because when I do that from android via adb it freeze.
Well, adb does freeze... you have to wait for the boot animation... and it really takes a long time. After you 2ndboot you have to think of your phone as if it were back at the (M) stage of boot, but with whatever happened to be on the screen when 2ndboot started instead of the (M).
Sent from my Nexus 7 using XDA Premium HD app
Mioze7Ae said:
Well, adb does freeze... you have to wait for the boot animation... and it really takes a long time. After you 2ndboot you have to think of your phone as if it were back at the (M) stage of boot, but with whatever happened to be on the screen when 2ndboot started instead of the (M).
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
So I haven't wait. I will try that and tell you if I have radio. But do I have to have a custom boot.img ?
Sent from my Milestone XT720 using xda-app.
EDIT : Finally I tried : after a long time I had boot animation then screen was black. I press power button (short press) then I had M logo and bootanimation and then android. Android is fully working with radio and it doesn't ask me for pincode. But I mean I had a full reboot.
Can you confirm that I have to seen M logo with 2ndboot or that I had a full reboot ?
EDIT : When screen go black : no need to press button it reboot. I think it doesn't work and make full reboot but I am not sure.
What are the exact steps to follow to make this work?
I would like to try this as well.
Thank you.
Sent from my XT720 using xda premium
Related
Well I'm running CM7 SelfKang 10/15 and whenever I use the the reboot options from the power button it never completes the reboot. Ex. I press reboot recovery and it sorta bootloops. So i typed it into Terminal emulator and it bootlooped even after i removed the battery, I had to 3 button boot into recovery and boot it to system from there to stop it. Is this a problem with the Epic itself? Im not aware of anyone else having this problem. Need anymore info let me know.
Well...yeah. The kernel doesn't have what's called a "clockworkmod re director" which means it won't work.
ugothakd said:
Well...yeah. The kernel doesn't have what's called a "clockworkmod re director" which means it won't work.
Click to expand...
Click to collapse
Even the terminal command?
They do the same thing. Theres 3 boot methods I know of. I'll simplify them:
Normal-well, self explanatory
Recovery bml8-boots recovery from bml8 (aka where the recovery kernel is)
Recovery bml7-boots recovery from bml7 (aka where the ROM kernel is)
Download mode-Odin (sbl.bin)
When you boot from running android (terminal emulator, rom manager, etc) you boot the recovery on bml7. When you 3 finger boot, you boot the recovery on bml8.
(thanks mkasick!)
ugothakd said:
They do the same thing. Theres 3 boot methods I know of. I'll simplify them:
Normal-well, self explanatory
Recovery bml8-boots recovery from bml8 (aka where the recovery kernel is)
Recovery bml7-boots recovery from bml7 (aka where the ROM kernel is)
Download mode-Odin (sbl.bin)
When you boot from running android (terminal emulator, rom manager, etc) you boot the recovery on bml7. When you 3 finger boot, you boot the recovery on bml8.
(thanks mkasick!)
Click to expand...
Click to collapse
Oh, I guess that makes a more sense Thanks for clearing that up! +2
Fire n mage said:
Well I'm running CM7 SelfKang 10/15 and whenever I use the the reboot options from the power button it never completes the reboot.
Click to expand...
Click to collapse
It's a bug in the CM7 1015 initramfs. "recovery.rc" needs either the "on fs" line removed or commented out, or the next line that mounts /system uncommented. Reboot recovery should boot into CWM included with CM7 but it loops because of that bug.
I ran into this while working on EC05/CM7 dual boot, which is still going to take a few more days to finish.
There's a rom coming soon that boots rom recovery and download mode..and they work perfect
Sent from my SPH-D710 using xda premium
JohnCorleone said:
There's a rom coming soon that boots rom recovery and download mode..and they work perfect
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Oh you teaser!
mkasick said:
I ran into this while working on EC05/CM7 dual boot, which is still going to take a few more days to finish.
Click to expand...
Click to collapse
I just thought about your dual boot project, thinkinging I'd go back to midnight rom as my Ec05 rom But I Realized cm7 is rfs n midnight is ext4, will the EC05 rom need to be rfs?
Sent from my SPH-D700 using xda premium
JohnCorleone said:
There's a rom coming soon that boots rom recovery and download mode..and they work perfect
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Wait soon as in mystical 1.3/ Gb soon or what lol
Sent from my SPH-D700
ac16313 said:
Wait soon as in mystical 1.3/ Gb soon or what lol
Sent from my SPH-D700
Click to expand...
Click to collapse
HAHA
10char
I am currently working on porting gweedo's touch recovery to the touchpad. So far I have a working clockworkmod 5.5.0.4 with the cool battery percentage mod but the touch part is not ready yet.
I just wanted to release this as a fully functional recovery (except adb).
1) boot into clockworkmod
2) mounts and storage >> mount /boot
3) adb push uImage.CWMRT5504 /boot/uImage.CWMRT5504
4) reboot and see it in the moboot menu
The touchscreen driver doesnt work but this is a completely working clockworkmod recovery (backups, restore, installing zips, etc.) (except adb)
Thanks
uImage.CWMRT5504 (install file)
LINK: HERE
KNOWN ISSUES:
- touchscreen doesnt work (yet)
- adb doesnt work in recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changelog:
- fixed the mount points to be a fully functional recovery. (thanks gdanko)
Pretty cool man!
Sent from my Touchpad using xda premium
good job man
Sent from my SGH-T989 using xda premium
I played around and it works pretty well! No bugs that I could find.
The only feedback I would give is that when you flash ROMs it sucks that the soft touch keys on the screen get in way of a lot of the wording. The horizontal blue line also would strike through words and it looks cruddy.
Any way to change where the message output is placed?
Can't wait to try this out. Keep the work going.
Can someone post mirrors for the downloads. They are both down.
LinuxNewb said:
I played around and it works pretty well! No bugs that I could find.
The only feedback I would give is that when you flash ROMs it sucks that the soft touch keys on the screen get in way of a lot of the wording. The horizontal blue line also would strike through words and it looks cruddy.
Any way to change where the message output is placed?
Click to expand...
Click to collapse
this should be fixed in this beta 14. and also the links are updated to an unlimited bandwidth server.
I hate to be "that guy," but I looked into this before and I don't think you can get the touchscreen working. On the TouchPad, the screen is controlled by a userland-based driver versus a kernel based driver. That's swell, but since CWM is basically only a kernel, it can't load the driver. I'd love to have someone prove me wrong, really. I just couldn't figure out a way to load it on CWM
Also, you're compiling it wrong if it only works temporarily when flashed. I believe that's like "make kernel" (or the equivalent, it's been awhile lol). I can'r remember the correct command, but I might have solved it by compiling CM and then removing the recovery portion? *shrug*
Good luck, though! I meant this to be taken as someone sharing their knowledge to help others, not as a deterrent. Please, continue with this and make an awesome CWM!
I'm not a kernel/recovery dev so I wouldn't even know where to begin looking at this but I know there was a touch based recovery back before CM9 called TeamWin Recovery Project (TWRP). Maybe it might help to look back at how they got it working and see if the same process can be used for CWM?
Here's the link to the original thread with TWRP thread.
http://forum.xda-developers.com/showthread.php?t=1400649
Hope it helps. I would like to see this work. I love the touch based CWM on my GNex.
Is this still in development?
so finally got mounts to work so this is now a fully functional recovery. the only things not working are the touch options and adb. once i get ts_srv to initialize then swipe gestures will finally work. but for now its still at least a good recovery.
So everything in the touch recovery works besides the touch?
Sent from my Galaxy Nexus using XDA
blckngldhwk said:
So everything in the touch recovery works besides the touch?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
LOL not sure if you are trying to be a smart-a** or honestly asking. you must not be asking for reals since the OP answers that question.
its still an updated CWM from the original 5.0.2.6. so its still better than the one from before.
sk8erwitskil said:
LOL not sure if you are trying to be a smart-a** or honestly asking. you must not be asking for reals since the OP answers that question.
its still an updated CWM from the original 5.0.2.6. so its still better than the one from before.
Click to expand...
Click to collapse
Well in the previous post he mentions adb does NOT work in this new version and I'd consider that a critical part of recovery. Any info on progress related to that? Great work.
famewolf said:
Well in the previous post he mentions adb does NOT work in this new version and I'd consider that a critical part of recovery. Any info on progress related to that? Great work.
Click to expand...
Click to collapse
Yes I agree that adb is a critical part. I'll be looking at init.rc to why adb isn't starting. Just haven't had a chance yet.
Sent from my SAMSUNG-SGH-I727 using XDA
you should really edit the main subject line, since no adb and no touch do not equal "FULLY WORKING RECOVERY." Not sure why anyone would bother using it at this point to be honest
sk8erwitskil said:
Yes I agree that adb is a critical part. I'll be looking at init.rc to why adb isn't starting. Just haven't had a chance yet.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
You may want to search on "Aroma File Manager" (gui file manager you kick off from within recovery by installing the .zip) and see if you can potentially add a direct link to it in recovery...that would be VERY useful addon nobody else currently has as aroma file manager is relatively new.
The aroma touch installers are on most of the roms for my Xperia Arc. I wouldn't say nobody's using them yet as its the latest trend amongst developers. An aroma installer could benefit the touchpad community for those who want to choose what they do and don't want in the rom. But I'm gunna assume for the moment that if a touch recovery won't recognize touch that aroma probably won't work either.
Matt Devo said:
you should really edit the main subject line, since no adb and no touch do not equal "FULLY WORKING RECOVERY." Not sure why anyone would bother using it at this point to be honest
Click to expand...
Click to collapse
Well it is a fully functional recovery. Any recovery aspect you need (backup, restore, install, fix permissions) ALL work. Therefore, it's a working recovery. Touch is an extra and not a requirement to use recovery. So next time you should try thinking before you put down your ignorant ideas.
Sent from my SAMSUNG-SGH-I727 using XDA
sk8erwitskil said:
Well it is a fully functional recovery. Any recovery aspect you need (backup, restore, install, fix permissions) ALL work. Therefore, it's a working recovery. Touch is an extra and not a requirement to use recovery. So next time you should try thinking before you put down your ignorant ideas.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Yes but you say Fully Working and Touch... well if adb is nonfunctional then its not FULLY functional and if Touch isn't working then its not TOUCH then is it... so yes... the thread should be pulled or the title modified
Sent from my cm_tenderloin using Tapatalk 2
Hey! Here is another guide of mine. In this guide I will show you how to install AOKPlay by Supervenom, my current ROM of choice. It is found here: http://forum.xda-developers.com/showthread.php?t=1582118
This won't cover the unlocking of the bootloader or the installation of the fastboot files.
I recommend reading the whole thread before starting.
Good luck!
1. Make sure you have all the drivers installed, made a nandroid backup and have an usb cable, usb port and your phone near you. Also make sure your phone has enough battery left. About 50% should be plenty.
2. Download the rom+kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1582118
3. Download the ROM and put it on your phones memory card.
3.5 (optional, but highly recommended: download the Gapps (Google apps), this is Google Play et cetera.)
4. Download the kernel (either Doomlords or Keirans) and put it in the folder your fastboot.exe is in. For me this is C:\Program Files\Android\android-sdk\platform-tools.
If you download Doom's kernel, make sure to download the fix aswell and put it on your sd card.
5. Now grab your phone. Make sure it is turned off. Hold the search key while connecting it to your computer. The notification light should light up blue. When you have succesfully connected it (light is blue), you can release the search key.
5.5 Read steps 6-8 carefully. I have made a .bat file that will do this for you. If you choose to use it, place it in the same folder as your boot.img, and then launch. This won't work if you have renamed the dfk4.img. If you don't trust this, you can right-click it and hit edit. This way you'll see it says exactly the same as steps 7 and 8. Feel free to do it manually though.
http://www.2shared.com/file/PizbMctP/Flash_kernel.html for Keiran's kernel
http://www.2shared.com/file/8odggnur/Flash_kernel_Doom.html for Doom's kernel
6. I assume you have Windows Vista or 7. If you do, shift-click on a empty place in your fastboot folder and click "open command prompt here" or something similar (my Windows version is Dutch, so I don't know what it's called in English).
7. Flash the kernel using this command: fastboot -i 0xfce flash boot boot.img
8. Reboot the phone using this command: fastboot -i 0xfce reboot
9. While it is rebooting, spam the back key. You will now get into CWM recovery. Use the volume keys to navigate, and the home key to select. If you have Doom's kernel, you can use the touchscreen (I believe). Make a backup.
10. Press "wipe data/factory reset". Then, wipe the cache+dalvik cache (under advanced).
11. Select "install zip from sdcard", and then "choose zip from sdcard". Find the zip from step 3 and select it. (if you installed Doom's kernel, also select the fix)
12. (optional) Also install Gapps the same way as the ROM itself.
13. Press reboot system now, and enjoy your new ROM. The first boot may take a while.
Congratulations, you just installed AOKPlay!
If I made any mistakes, please let me know.
I am not responsible for any bricked phones, broken GPU's, force-closes and killed pets.
If this helped you, I would appreciate a "thanks".
Good luck!
Ridder
On new DFK kernel, it is the back button to enter recovery
Sent from my Xperia Play using Tapatalk 2
KeiranFTW said:
On new DFK kernel, it is the back button to enter recovery
Sent from my Xperia Play using Tapatalk 2
Click to expand...
Click to collapse
Thank you, fixed.
I'd stay on AOKP but games don't work. GB FTW
I'm liking CM9 atm, maybe AOKP next week
Sent from my Xperia Play using Tapatalk 2
KeiranFTW said:
I'm liking CM9 atm, maybe AOKP next week
Sent from my Xperia Play using Tapatalk 2
Click to expand...
Click to collapse
I had that last week
Noob question
sorry for the noob question but im new to flashing roms and kernels, i have downloaded flashtool and when i connect i get the blue light then it turns orange and goes on charge and get this
-Device connected with USB debugging off
- For 2011 devices line, make sure you are not in MTP mode
i have usb debugging on and mtp turned off any ideas??
ALSO can i just install the kernel through clockworkmod instead of flashtool i noticed the kernels are .img files and not .zip??
i am rooted but my phone says no about unlocking bootloader any ways around this and can i still install this rom without being unlocked
wedgess said:
sorry for the noob question but im new to flashing roms and kernels, i have downloaded flashtool and when i connect i get the blue light then it turns orange and goes on charge and get this
-Device connected with USB debugging off
- For 2011 devices line, make sure you are not in MTP mode
i have usb debugging on and mtp turned off any ideas??
ALSO can i just install the kernel through clockworkmod instead of flashtool i noticed the kernels are .img files and not .zip??
i am rooted but my phone says no about unlocking bootloader any ways around this and can i still install this rom without being unlocked
Click to expand...
Click to collapse
I do not know the solution for the first problem myself. Maybe this thread will help you: http://forum.xda-developers.com/showthread.php?t=1678215
But it is probably the bootloader, which needs to be unlocked. You can only install custom kernels with an unlocked bootloader, but there are some roms that work with the stock kernel, like Gin2ICS (I believe)
You can't install kernels through clockworkmod. I think this is because the recovery partition is inside the kernel.
Can I use the lupus cm9 based kernel for this rom?
Sent from my R800i using xda app-developers app
ShojisXperia said:
Can I use the lupus cm9 based kernel for this rom?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
I think it would, as long as you use the linaro kernel.
ShojisXperia said:
Can I use the lupus cm9 based kernel for this rom?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
yes
Sent from my GT-I9300
Hi wedgess ^_^ im a lupus fan hehe. I love ur work. By the way another noob question. Im on lupus ics v8(ics beta based) kernel right now. If I shift to lupus cm9 based kernel so I have to wipe anything? And which is better lupus cm9 or lupus ics beta? Thanks in advance.
Sent from my R800i using xda app-developers app
ShojisXperia said:
Hi wedgess ^_^ im a lupus fan hehe. I love ur work. By the way another noob question. Im on lupus ics v8(ics beta based) kernel right now. If I shift to lupus cm9 based kernel so I have to wipe anything? And which is better lupus cm9 or lupus ics beta? Thanks in advance.
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Both are roughly the same but ics one only works on ics beta based roms. CM9 kernel, can be used on any cm9 based ROMS. So depending on the ROM u use then use either the cm9 or the ICS one.
Edit- and if ur switching ROM then ye u will need to wipe data, cache & dalvik cache.
Sent from my GT-I9300
Ok thank you so much sir for ur advice and for ur great works..
Sent from my R800i using xda app-developers app
Did everything, flashed zip, rebooted, stuck at sony logo for about 10 mins
Please help
Did you remove the boot.img from zip?
Sent from my R800x using xda app-developers app
Hey all.
On the Verizon i815 tab we seem to have a modem and a separate LTE modem. In the OTA files the scripts always do a
write_firmware_image("/tmp/modem.bin")
and the LTE file gets pushed to /dev/block/mmcblk0p8.
Now the question is, WHERE does the write_firmware_image call flash the bin file and how can I extract it from a running and updated device?
Background: We have one user who by some weird coincidence got the ICS OTA update pushed from Verizon. Everyone else's update always fails (whole debacle can be found in different threads). We now managed to have this one user pull a clone copy of all of his partitions via dd if=/dev/block/mmcblk0pxx of=/sdcard/file_xx commands and pushing those into another tablet yields a working ICS with updated LTE modem but the "regular" baseband still shows the old version!!!
I need to know how this one successfully updated user can dump his modem.bin and where we need to flash this dd or using this proprietary write_firmware_image function, so that in the end everything is updated as if the OTA had worked in the first place ...
THANKS
Pershoot is the king with the 10.1 tab variants, maybe he he can shed some light.
Sent from my SCH-I815 using xda premium
Most devices will store the CDMA modem.bin in the nvram so it unfortunately cannot be dumped like a normal partition.
Perhaps the kernel drivers could be modified to extract it, though I've never looked into such things very far.
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Most devices will store the CDMA modem.bin in the nvram so it unfortunately cannot be dumped like a normal partition.
Perhaps the kernel drivers could be modified to extract it, though I've never looked into such things very far.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
electron73 said:
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
Click to expand...
Click to collapse
This may be the first instance where Honeycomb is actually useful (the recovery part LOL)
electron73 said:
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
Click to expand...
Click to collapse
Is the bootloader locked?
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Is the bootloader locked?
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Yes of course. It's Verizon
electron73 said:
Yes of course. It's Verizon
Click to expand...
Click to collapse
Lame.
How were you guys using cwm then?
I may know of a solution even if the bootloaders are locked.
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Lame.
How were you guys using cwm then?
I may know of a solution even if the bootloaders are locked.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Well it seems like it's "half locked" then. The tab allows you to flash any recovery but nothing else. No kernel, no system fs. And they are locking it down further with every update. New ICS recovery won't flash unsigned zips anymore.
What solution do you have? Always interested in learning more about this stuff.
OK. I can probably help then. I'll post more details when I get home in a little bit.
Sent from my SCH-I500 using xda app-developers app
electron73 said:
New ICS recovery won't flash unsigned zips anymore.
Click to expand...
Click to collapse
Whoa...really? If we ever deliberately unroot, how would it ever be possible to restore it post-ICS? (I'm only aware of the recovery-injection method.)
Rodney
Oh Samsung....you never change...
Seems they're still using the same type of bootstrap initramfs as they have been for years. This allows unpacking and repacking of a kernel image
Linked below is a copy of the ICS recovery.img that has been repacked with the following changes:
* start adbd as root by default
* recovery keys replaced with 'test' keys
If this boots it should allow access to stock recovery with adbd, and should allow the stock recovery to flash unsigned zip packages. If so, you may create a zip package that can flash modem deltas (or tits).
DISCLAIMER: I don't even have this device, so I haven't tested anything. I came by this forum for other reasons. If it doesn't work or breaks something, then well, have a beer or something (though I see no reason it will break things even if it does not work as intended).
http://www.mediafire.com/?wnbr1v846yldl94
Flash with Odin or Heimdall, or whatever you folks are using for such things.
rhester72 said:
Whoa...really? If we ever deliberately unroot, how would it ever be possible to restore it post-ICS? (I'm only aware of the recovery-injection method.)
Rodney
Click to expand...
Click to collapse
It seems you can simply ODIN your CWM back on and then take it from there. As long as they don't close that hole at some point... Right now with the latest ICS version, even with stock recovery installed, this is still possible.
jt1134 said:
Oh Samsung....you never change...
Seems they're still using the same type of bootstrap initramfs as they have been for years. This allows unpacking and repacking of a kernel image
Linked below is a copy of the ICS recovery.img that has been repacked with the following changes:
* start adbd as root by default
* recovery keys replaced with 'test' keys
If this boots it should allow access to stock recovery with adbd, and should allow the stock recovery to flash unsigned zip packages. If so, you may create a zip package that can flash modem deltas (or tits).
DISCLAIMER: I don't even have this device, so I haven't tested anything. I came by this forum for other reasons. If it doesn't work or breaks something, then well, have a beer or something (though I see no reason it will break things even if it does not work as intended).
http://www.mediafire.com/?wnbr1v846yldl94
Flash with Odin or Heimdall, or whatever you folks are using for such things.
Click to expand...
Click to collapse
Awesome! Thanks for your help. Now of course I have a few questions and hope you can give me a quick rundown.
how do I unpack this img. I have linux and good knowledge of linux and unix tools. You say it's an initramfs? Is there a tutorial somewhere that explains how to unpack, modify and repack such a thing? And where do I make the changes if I were to do it myself with *our* ICS recovery?
I believe I can't just flash this one as there are big differences between the international versions and our LTE version of the Tab 7.7
The partition table is different etc. I don't want to use this and end up screwing my stuff up. I'd rather take the original one that came with our ROM and modify it myself.
You don't happen to also know how to unlock the bootloader so that we could just flash a rom with ODIN ?
The recovery I posted is a modified version of the one that asenduk posted in the other ICS thread. When I get to a PC later I'll post a link to the tools that I used to modify it. Its pretty straightforward.
As far as unlocking the bootloader, that's above my pay grade. Perhaps kexec would be a useful thing to look into?
Sent from my SCH-I500 using xda app-developers app
I think maybe we could start a donation for Mr JT to get the i815?
If he's interested yeah?
He's done many marvelous things!!
repack scripts : https://github.com/project-voodoo/kernel_repack_utils
toolchain : http://www.codesourcery.com/public/...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
use extracter.sh to unpack the image into a folder, edit to taste, then use repacker.sh to put it back together.
make sure to use gzip compression when repacking.
jt1134 said:
The recovery I posted is a modified version of the one that asenduk posted in the other ICS thread. When I get to a PC later I'll post a link to the tools that I used to modify it. Its pretty straightforward.
As far as unlocking the bootloader, that's above my pay grade. Perhaps kexec would be a useful thing to look into?
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
You say it has a locked bootloader, but we have CM10 which uses a custom kernel...
okashira said:
You say it has a locked bootloader, but we have CM10 which uses a custom kernel...
Click to expand...
Click to collapse
Well... Bootloaders I have never really looked into.. I am still unable to flash a kernel or a factory fs with ODIN. Odin only lets me flash the recovery. So something is locked there. Maybe not crazy-locked like the motorola razr phones but also not completely open like the AT&T Galaxy Note was... Maybe someone with a little more experience in this stuff can shed some light
jt1134 said:
repack scripts : https://github.com/project-voodoo/kernel_repack_utils
toolchain : http://www.codesourcery.com/public/...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
use extracter.sh to unpack the image into a folder, edit to taste, then use repacker.sh to put it back together.
make sure to use gzip compression when repacking.
Click to expand...
Click to collapse
Cool! Thanks for the links. Will look at the stuff and see if I can figure it out
Has anyone tried the 4.3 cm10.2 ROMs found over here (http://androidhosting.org/Devs/Dhacker29/cm-10.2/)? I was going to give it a go last night but for some reason my device got stuck on the "warning your boot loader is unlocked" screen and had to use Matt's utility to give it life... I may give it a try tonight when I'm not expecting any calls...
Sent from my XT907 using xda app-developers app
Yeah, I'm running the latest version of it now. I had the same problem. What worked for me was the following:
1. Wipe everything - system, data and both types of cache.
2. Install CM 10.2 and NOTHING else. Boot the ROM. It should go through now.
3. Once you get to the main screen, reboot into recovery.
4. Install the 4.3 GAPPS version. Reboot, get to the main screen and reboot into recovery.
5. Now flash the 4.3 version of Supersu for CM 10.2
6. Boot one last time into CM 10.2
All the links for everything you need can be found with a Google search. Later I may edit this post to include those links.
Sent from my XT907 using Tapatalk 4
Thank you kindly for the reply... I got it booting finally but couldn't get su permission on TiB and what not... I didn't know about needing the 4.3 su ...I'll flash that now... again thank you kindly
Sent from my XT907 using xda app-developers app
TWRP isn't supported either from what I understand. You need to run CWM.
Any time I install 4.3, it won't reboot. It starts up initially, but I can't get it to get past the Motorola logo upon second boot.
I have tried the normal install method and this method.
Then recovery doesn't see the /data folder so something is wrong with the 4.3 install I presume.
Does it change the location of data?
Yeah I Tried It But It Had No Sound So I Changed Over To 4.2.2 AOKP.
grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I was using CWM on my first attempt... this time around I switched to TWRP...
Sent from my XT907 using xda app-developers app
grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I use TWRP, works ok. Got sound, data, everything working fine. Battery life sucks, but no surprise there.
My 2c
I'm running it right now. I must have missed the part about flashing SuperSu, because I can't do anything as root. I had trouble the first time I flashed with the phone bootlooping, but I flashed again and that fixed it. Battery life is somewhat poor, but I just found the performance page today (Icon was different, silly me!) so we'll see how it goes with a different governor. I've been having issues with Navigation and Bluetooth audio on anything except stock. Bluetooth audio locks the phone and I have to soft-reset it. Navigation crashes if you try to multi-task while using it.