What is this?
Boot Menu S is a bootstraped recovery.
Bootstraped means that it installs itself in the system partition and
hijacks Androids boot process. This means that it will not protect
your device if you screw up you stock system. Therefore it supports
up to four rom-slots. A rom-slot is stored on your internal storage
and holds one rom. When you flash something to a rom slot it will
not touch your stock system partition and therefore protects you
from a brick.
How do I use this?
Install the app https://play.google.com/store/apps/details?id=se.pajn.bms.manager
Open the app and install the recovery.
Reboot to the recovery.
If you want to enter the recovery during boot hold volume down until the boot animation hungs.
REMEMBER TO NEVER FLASH, WIPE OR RESTORE SOMETHING
TO YOUR STOCK SYSTEM, IT MAY BRICK YOUR DEVICE.
Thanks to
Hashcode and STS dev team for writing Safestrap
TeamWin for writing TWRP
And Developers and Skrilax_CZ for writing 2nd-init
As always you are fully responsible for your device if you brick your device
using this you are on your own. I nor anyone else take any responsibility
for what you do with your device.
Reserved
wow, apparently something good is going on here theoretically via some changes should be also available for 1st tab S users ?
What about s1, buddy?
Sent from my Sony Tablet S using xda app-developers app
So we can start getting some custom roms up in this thread list?!?
Sent from my SGPT12 using Tapatalk 4 Beta
condi said:
wow, apparently something good is going on here theoretically via some changes should be also available for 1st tab S users ?
Click to expand...
Click to collapse
I can't promise anything but I espect so yes. @smgdev here have sent me some device information so I hope that it should be possible. I will start doing some real work towards STS now.
Sent from my XT910 using Tapatalk 4 Beta
See this is where im confused the is no imne number for the device therefore no way to complie or am I totally wrong
What I am intrested in is kernal and radio flashes to the oem software like doomloord but the real shame about the tablet is the sligly aggressive battery "saving" ints in the kernal that are there like the ever present wifi issue ive always found frustrating buttery smooth yes once my wifi kicks in then I can say hold on while I disable and renable the wifi because reuter is going nuts with the constant disconnects and starts a new cache every time it reconnects to it thus filling up its memory ram? And then it causes problems its not a laptop so I dont see why I was given to viao to build hard ware they knew little about and a software system even less ha ha
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
pajn said:
I can't promise anything but I espect so yes. @smgdev here have sent me some device information so I hope that it should be possible. I will start doing some real work towards STS now.
Sent from my XT910 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Awesome, if you use the uninstall option will it boot to the stock recovery like nothing happened?
Sent from my Sony Tablet S using xda premium
pajn said:
I can't promise anything but I espect so yes. @smgdev here have sent me some device information so I hope that it should be possible. I will start doing some real work towards STS now.
Sent from my XT910 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Can you post the apk? And did you use the twrp recovery from the original safestrap?
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
Can you post the apk? And did you use the twrp recovery from the original safestrap?
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
I do want the apk BUT it is a major risk since XTS and the STS are different in a few ways like the bootloader, hardware, system, 2nd init and such so we may have to wait until it is supported.
Sent from my Nexus 4 using xda app-developers app
dex9mm said:
See this is where im confused the is no imne number for the device therefore no way to complie or am I totally wrong
What I am intrested in is kernal and radio flashes to the oem software like doomloord but the real shame about the tablet is the sligly aggressive battery "saving" ints in the kernal that are there like the ever present wifi issue ive always found frustrating buttery smooth yes once my wifi kicks in then I can say hold on while I disable and renable the wifi because reuter is going nuts with the constant disconnects and starts a new cache every time it reconnects to it thus filling up its memory ram? And then it causes problems its not a laptop so I dont see why I was given to viao to build hard ware they knew little about and a software system even less ha ha
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
You can compile the kernel but you can't boot it as we have a locked bootloader, it's solvable with kexec which I have looked into a bit however the kernel is a mess so I don't relay know where to start. But it would be nice to have. With kexec and 2nd-init we have fully worked around the locked bootloader problem.
andyabc said:
Awesome, if you use the uninstall option will it boot to the stock recovery like nothing happened?
Click to expand...
Click to collapse
You can always access the stock recovery because that one is started from the bootloader where a bootstraped recovery is started from the system. What happens when you press uninstall is that it removes every file that is installed in the system partition and restores the hijack binary (currently logwrapper but I will start searching for a new one as Sony starts logwrapper very late (usually it's one of the first things to start as the mounting of the system, user and cache partitions usually are wrapped with logwrapper)).
smgdev said:
Can you post the apk? And did you use the twrp recovery from the original safestrap?
Click to expand...
Click to collapse
Ofcourse. However I don't relay know what you want to use it for. The recovery is just included as a binary so the APK doesn't realy reveal much. Is there anything special that you are searching for?
If you use the current APK on the STS there is a big risk of bricking. I will send you a test build for STS as soon as possible if you don't mind doing some testing, else I have to find someone else.
View attachment BootMenuS.apk
The recovery is TWRP however it isn't exactly the same as in the real safestrap builds because I couldn't compile the master branch of safestrap (probably some configuration error but the error I got from make wasn't very helpful so...) so I used a branch with a later version of TWRP and because TWRP had some big changes in its PartitionManager I had to rework most of the rom slot code.
I will post the full source on Github later.
wow great news !
Thanks so much! Lets see if something magical happens!
Cheers
Vatis
pajn said:
You can compile the kernel but you can't boot it as we have a locked bootloader, it's solvable with kexec which I have looked into a bit however the kernel is a mess so I don't relay know where to start. But it would be nice to have. With kexec and 2nd-init we have fully worked around the locked bootloader problem.
You can always access the stock recovery because that one is started from the bootloader where a bootstraped recovery is started from the system. What happens when you press uninstall is that it removes every file that is installed in the system partition and restores the hijack binary (currently logwrapper but I will start searching for a new one as Sony starts logwrapper very late (usually it's one of the first things to start as the mounting of the system, user and cache partitions usually are wrapped with logwrapper)).
Ofcourse. However I don't relay know what you want to use it for. The recovery is just included as a binary so the APK doesn't realy reveal much. Is there anything special that you are searching for?
If you use the current APK on the STS there is a big risk of bricking. I will send you a test build for STS as soon as possible if you don't mind doing some testing, else I have to find someone else.
View attachment 2083568
The recovery is TWRP however it isn't exactly the same as in the real safestrap builds because I couldn't compile the master branch of safestrap (probably some configuration error but the error I got from make wasn't very helpful so...) so I used a branch with a later version of TWRP and because TWRP had some big changes in its PartitionManager I had to rework most of the rom slot code.
I will post the full source on Github later.
Click to expand...
Click to collapse
I can also help out with testing!
Plays2 said:
I can also help out with testing!
Click to expand...
Click to collapse
Plus me
HOX+Viperx+Alex(V) = revolution
Okey, I post here the version I sent to smgdev in private.
Remember that this is a completely untested version, I have never even seen a STS IRL. It's only based on information smgdev sent and while that info were good there is still some possibility that something isn't right at the first try.
This version doesn't include any hijack and is therefore not modifying any existing files, only adding, so it shouldn't create a brick however as always: nothing can be guaranteed. Also there is risk that the recovery isn't correctly configured and can cause problem so please follow the protocol if you aren’t absolutely sure of what you are doing.
APK: http://ge.tt/3lBh0nk/v/0
Install the app.
On the install screen make sure that it says Device: STS in the top right corner, if it doesn't: abort!
Install the recovery.
Open adb shell and run
Code:
su
reboot-recovery
In the recovery:
Go to backup and make sure that it says the correct free space of your internal storage. If it doesn't: abort!
Do a backup.
Go to mounts and mount system
Go to advanced>file manager and check that /system contains your stock system.
Go to boot options>rom slot 1 and make sure that it says the correct free space of your internal storage. If it doesn't: abort!
Create the slot.
Go to mounts and mount system
Go to advanced>file manager and check that /system only contains lost+found. If it contains your stock system: abort!
Restore your backup
Go to mounts and mount system
Go to advanced>file manager and check that /system contains your stock system (well, the backup of it).
Go to boot options>rom slot 2 and create it
Go to mounts and mount system
Go to advanced>file manager and check that /system only contains lost+found.
Try to delete one rom slot
That should cover most things.
When I run reboot-recovery I get
"Cp can't stat '/system/etc/safestrap/bbx no such file or directory
Unable to chmod /sbin/bbx no such file or directory and a whole bunch of the same line "/system/bin/reboot-recovery[19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 31, 32,35,38,41,42,43,44,45,46,47,48,49,50,51,53] /sbin/bbx not found"
And finally,
"/system/bin/reboot-recovery[55] /sbin/hijack.killall not found
/system/bin/reboot-recovery[57] /sbin/taskset: not found
/system/bin/reboot-recovery[58] /sbin/bbx not found
/system/bin/reboot-recovery[59] /sbin/taskset not found"
Sent from my SGH-I747 using Tapatalk 4 Beta
Plays2 said:
When I run reboot-recovery I get
"Cp can't stat '/system/etc/safestrap/bbx no such file or directory
Unable to chmod /sbin/bbx no such file or directory and a whole bunch of the same line "/system/bin/reboot-recovery[19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 31, 32,35,38,41,42,43,44,45,46,47,48,49,50,51,53] /sbin/bbx not found"
And finally,
"/system/bin/reboot-recovery[55] /sbin/hijack.killall not found
/system/bin/reboot-recovery[57] /sbin/taskset: not found
/system/bin/reboot-recovery[58] /sbin/bbx not found
/system/bin/reboot-recovery[59] /sbin/taskset not found"
Sent from my SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Such a stupid misstake. I will fix it when I get home.
Sent from my XT910 using Tapatalk 4 Beta
pajn said:
Such a stupid misstake. I will fix it when I get home.
Sent from my XT910 using Tapatalk 4 Beta
Click to expand...
Click to collapse
No worries, Thanks!
Sent from my Sony Tablet S using Tapatalk HD
Plays2 said:
No worries, Thanks!
Sent from my Sony Tablet S using Tapatalk HD
Click to expand...
Click to collapse
So, also checked the other files and they seemed good, however always hard to tell.
pajn said:
So, also checked the other files and they seemed good, however always hard to tell.
Click to expand...
Click to collapse
I'm still getting the same error...
It says status:installedv0.8 but those same files are still missing
Sent from my SGH-I747 using Tapatalk 4 Beta
Related
Warning: whether you preform these steps correctly or incorrectly, you may be left with a device which cannot be recovered to a previous state. Because this process operates on the recovery partition it leaves you with little room to recover if flashed incorrectly, especially if your normal Android mode doesn't boot.
(although realistically you can just flash ESPRIMG.zip from HBOOT to recover, or fastboot)
So here it is ladies and gentlemen: Clockwork 3.0.0.5, based on a git version pulled/compiled on January 6th, 2011 from the CyanogenMod 7.x (CM7) repository. So what's new? Nothing that I can tell! Not sure why it deserves version 3.x, but I guess changing the text color and background is considered a 'major upgrade'.
This is provided in .img format - NOT an update.zip format. That means you'll have to flash it to your recovery partition using flash_image. Obviously that means you first need root AND S-OFF. No, I won't tell you how to root your phone or what S-OFF is.
Instructions:
Code:
$ su
# flash_image recovery recovery-cw3-test1.img
'flash_image' isn't included intentionally - if you're smart enough to know how to flash this properly and understand the risks, then you might be smart enough to know where to get 'flash_image'.
How'd I do it? Top Secret - I'd have to kill you if I told you.
Download link: [REMOVED - use one from CM7]http://dl.dropbox.com/u/14943973/recovery-cw3-test1.img
Need to revert back to 2.5.0.1? Flash this: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Enjoy it? Thank me!
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
SKAm69 said:
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
Click to expand...
Click to collapse
Not from me, sorry. I don't see any point in supporting the legacy method, especially when this version of CW doesn't give any readily-apparent advantages to the older one.
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
JAWheat411 said:
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
Click to expand...
Click to collapse
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash at this point
MusicMan374 said:
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
But the only new features you see would be the new color?
Ace42 said:
But the only new features you see would be the new color?
Click to expand...
Click to collapse
Pretty much yeah. It was orange instead of green. Some of the menus had different names, easier to understand for noobs, but they had the same content. But don't flash it until it's more functional.
Sent from my T-Mobile myTouch 3G Slide
Ok well can someone post an older Clockwork recovery.img so we can reflash it? We can't use this one to do anything.
MusicMan374 said:
It IS a test build.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
I was at work when I uploaded the image and because of that I only briefly tested it. The errors at the beginning aren't critical, but I'll look into the overall functionality being broken, at some point tonight.
Hence this being a "TEST".
Thanks
I appreciate that. I like beta testing new things. It does seem to have a few more functions. I just couldn't revert back.....
Sent from my T-Mobile myTouch 3G Slide using XDA App
Flash this to go back to 2.5.0.1: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Actually.. i see a new option to partition SD card straight from the recovery menu... this is a very useful feature... and i think thats why it deserves that build jump from 2.5 to 3.0..... but at this point... it is in an UNUSABLE state.. i understand it is a test build... but i cannot test anything because it crashes on every single option you can possibly choose... will go back to 2.5 and wait for a stable, or at least more functional test build... hope to see some improvements soon... I do not doubt that you guys can have this thing up and running in no timee.. its a good starting point.. Keep the work going... looking forward to it...
was anyone else hoping for a terminal like in good ol' amon_ra? I was...
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
elry567 said:
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Thnx
Sent from my T-Mobile myTouch 3G Slide using XDA App
mymomma8 said:
it crashes on every single option you can possibly choose
Click to expand...
Click to collapse
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
I don't think that file was cw3 I flashed it and still have 2.5 (file by musicman)
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
MusicMan374 said:
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Click to expand...
Click to collapse
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
guitarist5122 said:
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
mymomma8 said:
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
Click to expand...
Click to collapse
Alright thanks it works now!
A preface:
This is neither development or a question. This is simply an informative post that needs to be in the development section to save many users issues. (also most people looking for custom roms dont look in general section)
I did not create this.
New official CWM v5.8.2.0 (link below)
A few of us have confirmed that it now properly backs up and restores the boot.img
This Helps with the following issues
-Possibly fixes bricks (by properly restoring boot.img)
-Correctly comes with Staging/System unmounted
-Nandroid Restores properly the boot.img (of backups created with this CWM). This means no more issues when restoring a Rom if you are coming from another from (for example, if you are restoring Virtuous after wiping cm9)
Additionally:
-Backups are now about 10x faster
-Restores are a bit faster (not as dramatic as backups)
Still no go:
-External SD Card (Pretty sure)
-Reboot into recovery (probably a software issue within OS anyway)
Manual install:Here is the link to the file if you prefer to manually install (EASY WAY BELOW) -Must have unlocked bootloader
DeathByFugu said:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-tf201.img
Click to expand...
Click to collapse
Dexter_nlb said:
it IS a blob file, i checked it.. the guy just forgot to name it blob, instead of .img
Click to expand...
Click to collapse
Just rename to .blob and follow these instructions http://androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
------
Easy Install -Must have unlocked bootloader.
Use Rom Manager:
Install Rom Manager from the market -> Open -> First Option: 'Flash ClockworkMod Recovery'-> Done.
This can be done over your current CWM (if you installed it via ViperMod) or manually)
If you have issues installing via RM try this
Swiftks said:
I had the same issue, when I first tried to install CWM via Rom Manager.
I solved it by installing the version that installs via the Prime Time Root program. Then installed the Rom Manger version without a hitch.
Click to expand...
Click to collapse
I think he is referring to this THREAD/Tool
or
huynhc said:
you need to update the superuser binary. open the superuser app and go to the top right wrench icon. click it and scroll down to "Su Binary x.xx" click it to update, do it a couple times for good measure. re-install rom manager after uninstalling it from market. open it up and try again.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Sent from my Droid Incredible (using one of them app things)
I take Zero Credit, just trying to be informative
credits said:
Credits:
Androidroot.mobi guys for porting the original CWM (and basically giving something for koush to look at)
CWM Team for adding to it
Anyone else who has contributed
Click to expand...
Click to collapse
moderators:
This is no more or no less development than this thread
http://forum.xda-developers.com/showthread.php?t=1510983
This cwm is more up to date and will prevent many end users from making the mistake of installing an outdated version. These 2 threads can (and should) be merged as long as the thread title has the latest CWM in it and the OP has some information regarding it.
Thanks
-Mike
cool...so this wont mess with any backups already made or any ROMs that we have already flashed?
Sorry for the noob type question, just want to be sure
GreginNH said:
cool...so this wont mess with any backups already made or any ROMs that we have already flashed?
Sorry for the noob type question, just want to be sure
Click to expand...
Click to collapse
It should not. all my previous ones are there after flashing in RM
Though: I dont think it will retroactively fix the boot.img restore and backup issue meaning, you should probably make new backups if you want to be able to restore the kernel properly in the future
So since I'm n00bish, what's the best way to do this?
soulctcher said:
So since I'm n00bish, what's the best way to do this?
Click to expand...
Click to collapse
Same here, how do we properly update from this .img file?
JWallstreet said:
Same here, how do your properly update from this .img file?
Click to expand...
Click to collapse
Download Rom Manager from the market and hit 'install recovery' at the top
mtotho said:
Download Rom Manager from the market and hit 'install recovery' at the top
Click to expand...
Click to collapse
Simple and excellent. Worked like a charm. Thumbs up to you, sir!
soulctcher said:
Simple and excellent. Worked like a charm. Thumbs up to you, sir!
Click to expand...
Click to collapse
Your welcome.
Thumbs up to the CWM team for finally releasing a more working recovery.
Thumbs up to "DeathByFugu" who brought it to my attention in IRC.
Thumbs up to those who tested with me and confirmed it was working as it should (DeathByFugu, youngex/tg3x)
Just ran a backup and it was definitely quicker than the last 2 that I made.
Quick question...can we now flash from external SD in this update? Or is it still "half done"?
ATGAdmin said:
Quick question...can we now flash from external SD in this update? Or is it still "half done"?
Click to expand...
Click to collapse
I haven't tested that functionality, sorry.
Sent from my ADR6425LVW using xda premium
ATGAdmin said:
Quick question...can we now flash from external SD in this update? Or is it still "half done"?
Click to expand...
Click to collapse
Will test this right now.
edit: Deosnt seem to be showing up still
mtotho said:
Will test this right now.
edit: Deosnt seem to be showing up still
Click to expand...
Click to collapse
UGH, I guess we can hope?
ATGAdmin said:
UGH, I guess we can hope?
Click to expand...
Click to collapse
I suppose in future version.
This is really a nonissue for me as I have ADB set up, so if I am in a jam and need a file, I can simply push it... that and I dont have an sdcard for my prime (had to test the one from my phone )
just DL Rom Manager and tried to "Flash CWM Recovery" and it just FC's?
anyone else?
** It asks for model type and only lists the prime". I select that and it runs but never gets all the way across and then says RM is not responding?
GreginNH said:
just DL Rom Manager and tried to "Flash CWM Recovery" and it just FC's?
anyone else?
Click to expand...
Click to collapse
Hmm very odd.
-I assume you are unlocked.
-Rooted
-Try opening up Rom Manager in application manager and hit clear cache.
mtotho said:
Hmm very odd.
-I assume you are unlocked.
-Rooted
-Try opening up Rom Manager in application manager and hit clear cache.
Click to expand...
Click to collapse
Yep, I am runnig Virtuous ROM.
I did go in and clear cache and data and tried all over again.
It starts, the "blue bar" at the top of the screen starts to scroll across and gets to about the end and just hangs. If I remember correctly from my other phones it should boot at that point and do its thing?
I will uninstall...reboot and reinstall.
If that doesnt work, maybe I will try the old fashion adb deal.
GreginNH said:
Yep, I am runnig Virtuous ROM.
I did go in and clear cache and data and tried all over again.
It starts, the "blue bar" at the top of the screen starts to scroll across and gets to about the end and just hangs. If I remember correctly from my other phones it should boot at that point and do its thing?
I will uninstall...reboot and reinstall.
If that doesnt work, maybe I will try the old fashion adb deal.
Click to expand...
Click to collapse
Sounds like it's borking when it would normally ask for Superuser permissions. Make sure your Superuser app isn't blocking it.
awsome news....
thanks for the info man!!
jermaine151 said:
Sounds like it's borking when it would normally ask for Superuser permissions. Make sure your Superuser app isn't blocking it.
Click to expand...
Click to collapse
Hmm, I looked at SU and see entries for Terminal Em, and Root Explorere......should I be looking for something in particular?
Well, hallo there!
It's been a while since I've posted a release thread on XDA... I've been lurking in the shadows (and on IRC) for quite some time.
Here, I present to you a teaser of things to come:
ClockworkMod Recovery (non-touch) 6.0.1.5 for the AT&T Optimus G.
What is this?
This is a "recovery" for your phone, it allows you to install custom ROMs, back up your phone, fix it when it breaks, and much more.
This specific version is "ClockworkMod", which was created by the CyanogenMod team and Koush.
There are many recovery versions out there, I have picked ClockworkMod because it is very easy to compile and debug.
I will compile other recoveries as time permits.
Click to expand...
Click to collapse
Where can I get it?
UPDATE: I am now providing download links.
Please go here to download it: http://downloads.codefi.re/thecubed/lgoptimusg/att/recoveries/
Note: this is a "tethered" build of CWM, as you can not flash it. You must use fastboot to boot the image every time you wish to enter recovery.
This is due to the locked bootloader on this device.
READ THE INSTRUCTIONS BEFORE DOING ANYTHING!
This is *not* safe, and should *not* be done by anyone unsure of what they are doing.
I will post links once I have ironed out bugs, but I WILL NOT SUPPORT anyone using it to modify their phone.
Please don't use this if you don't know how to LGNPST your phone back from the dead, should you accidentally kill it.
(Also, I will find somewhere to mirror LGNPST and the related files, as I can't host them from my server due to legal reasons. I will, however, mirror the .TOT file in case LG decides to take it down.)
Click to expand...
Click to collapse
Instructions
Check back here in a few hours, I'll have something done by then
Click to expand...
Click to collapse
The goods!
Here's a (semi-arty) pic of it running on my Optimus G:
And, here's a video for extra proof
Luckily the video quality isn't potato, but the audio sure is. My explanation is that my HTC Vivid doesn't like me. An engineer's explanation would be that I was speaking softly, as it was 1:30AM at the time of recording, and the phone merely decided that my meek volume was purely background noise... at least, I think that's what an engineer would say, as I haven't graduated yet.
Click to expand...
Click to collapse
SPECIAL THANKS!
Here's my favorite section of an XDA post: the "special thanks to" section.
Without the help of these awesome people, I would have nothing of interest to say, and would just be a random guy with a phone.
Seriously, these guys are awesome.
Here's the list (in no special order, and by IRC name):
Shelnutt2
sextape
xboxfanj
jonasl
kmdm
synergy
DeamonFish
chachin
..and Zanzibar (because why not?!)
If I've forgotten anyone, please let me know-- I want to make sure everyone who had a hand in this gets a shout-out.
Please, support these awesome people if you get a chance, or drop by the IRC channel and say hi
Click to expand...
Click to collapse
How can I contact you?
Need to get a hold of me, or anybody else? Come on IRC -- just go to http://webchat.freenode.net and use #lg-optimus-g as the channel name. Pick a nice nickname and say Hi
I'm IOMonster on IRC, and if I'm around, just say my name and I'll probably say hi back.
Click to expand...
Click to collapse
Alright everyone, hope you enjoy
Wow that does look pretty nice.
Looking forward to the fruits of your continued endeavor regarding this device, sir. Well done.
Very nice, cubed. That's some good, and fast, work.
Awesome work! Can't wait to see more progress on this. I'm assuming a Sprint version will be available eventually.
Sent from my PG86100 using xda app-developers app
Very cool!
subbed hopefully this will work with the Rogers version as well or one will come out of this,
either way spectacular work
BloodBaron said:
subbed hopefully this will work with the Rogers version as well or one will come out of this,
either way spectacular work
Click to expand...
Click to collapse
Great start! I can't wait to see how it progresses, looks like it's going fairly quickly at this point.
Delete post
So it boots cwm even with a locked bootloader?
That's peculiar. Either way great job!
Sent from my HTC_Flyer_P512_NA using xda app-developers app
can't wait
Can't wait. Great job!
Awesome work....you guys are amazing
Sent from my LG-E970 using xda app-developers app
Snow_fox said:
So it boots cwm even with a locked bootloader?
That's peculiar. Either way great job!
Sent from my HTC_Flyer_P512_NA using xda app-developers app
Click to expand...
Click to collapse
Apparently fastboot BOOT will accept any unsigned image regardless of bootloader status.
Sent from my LG-E970 using Tapatalk 2
I think this thread is for AT&T version, here's International.
Although placeholder threads are generally not allowed in the Dev section, we will allow this one, as the OP has stated he will provide the link if asked. (He does not want people to brick their device.)
Woot, so I patched CWM with a little homegrown patch to enable you to mount the external SD card.
This is necessary since CWM disables USB mounting by default on devices with an internal storage card that is shared with the /data partition.
Here's the status update:
What works:
Backups to Internal and External SD card
Restore from Internal or External SD card
ADB Shell Access
Battery charging (it's part of the kernel, I merely verified it's working)
Volume Keys / Power Key
Zip install from internal/external SD
USB Mounting
(in theory) Wipe Data ***see note***
What doesn't works:
Softkeys
Party mode
***Note: I have NOT tested "Wipe Data" or "Format /data". I do not suggest you try either for the moment.
This is because the internal SD card resides in /data/media. Erasing /data has a chance of erasing your internal SD. There are checks in CWM for this, but until I investigate, let's just be safe. If you need to erase your phone, let the stock recovery do that.
I am still working on some instructions for a safe way to get into CWM without the potential of getting stuck in some unknown mode. I will write up the instructions tomorrow and post links to the recovery.
Thanks everyone for your kind words on IRC as well, I appreciate all your moral support!
Thats a great start.. i do hope it is possible for the Japanese (L-01E) Version.... though the Japanese version already has microSD card support up to 64GB via SDXC
Wow, this is awesome! Keep up the great work!
thanks for all the work, I look forward to this device as I am getting it today, I do have some background in Linux and could possibly be building a ROM soon.
I love you right now. So stoked.
Sent from my LG-E970
Hello,
I've managed to get my build.prop in a state where I can't update (I assume it's the build prop). I've tried the backups I have, but none of them are working. I'm currently on 4.1.1 and I was hoping someone has backup.
Thanks in advance!
for clarity: Verizon Galaxy Note II 4.1.1 Stock ROM, Stock Recovery, Rooted
The Failing update is update_SCH-I605_LL4_to_MC3 which fails with code 402
Download the stock ROM in Development and pull it from there
Sent from my SCH-I605 using xda app-developers app
Bfitz26 said:
Download the stock ROM in Development and pull it from there
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Trevski13 said:
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Click to expand...
Click to collapse
Download the recovery flashable stock rom, the zip file, and extract it from that using 7zip.
Sent from my SCH-I605 using XDA Premium HD app
Trevski13 said:
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Click to expand...
Click to collapse
Using ES File explorer. Setup up your root explorer. and change permissions by using tools to System R/W.
Use ES File explorer to open the stock download and navigate to system/build.prop Copy it. Go back to your system and Rename the one there to build.bak. Then paste the new one there. This way you have the original saved if it turns out not to be the build.prop. My guess is. If you are on a rooted, stock rom like you said. The build.prop's are going to be identical. Thinking the culprit might be whatever you are trying to Odin is bad.
dragonstalker said:
Using ES File explorer. Setup up your root explorer. and change permissions by using tools to System R/W.
Use ES File explorer to open the stock download and navigate to system/build.prop Copy it. Go back to your system and Rename the one there to build.bak. Then paste the new one there. This way you have the original saved if it turns out not to be the build.prop. My guess is. If you are on a rooted, stock rom like you said. The build.prop's are going to be identical. Thinking the culprit might be whatever you are trying to Odin is bad.
Click to expand...
Click to collapse
I didn't know you could explore .img files with a root explorer, of course I have never tried either.
Sent from my SCH-I605 using XDA Premium HD app
So I pulled the build.prop from a stock image, but it turned out it perfectly matched one of my backups. (I had three backups, factory, factory that I played with, and OTA Stock). So in the end that didn't solve my core issue. At this point should I make a new thread with a more appropriate title or just continue this one?
shangrila500 said:
I didn't know you could explore .img files with a root explorer, of course I have never tried either.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Actually you can't... I ended up using "Android ICS JB EXT4 imagefile unpacker" for windows, which worked nicely.
Trevski13 said:
The Failing update is update_SCH-I605_LL4_to_MC3 which fails with code 402
Click to expand...
Click to collapse
I would say just continue this thread.
I just re-read your original post. Are you trying to update from 4.1.1 to 4.1.2 via the OTA? If so, build.prop isn't your issue.
jcollier said:
I would say just continue this thread.
I just re-read your original post. Are you trying to update from 4.1.1 to 4.1.2 via the OTA? If so, build.prop isn't your issue.
Click to expand...
Click to collapse
alright, detail time!
I'm currently on 4.1.1 (I've applied one update after I bought it on release day)
I have an ota update (to what I assume is 4.1.2)
stock everything, locked boot-loader, but rooted (used Exynos Abuse)
using SuperSU
my phone lists update_SCH-I605_LL4_to_MC3 which fails to install with error code 402
my device status IS "modified" but it appears to be related to the SD card as it is "normal" when I remove it (apparently a known issue)
normally when I get an update I do the following:
1. restore build.prop
2. remove busybox
3. remove/disable any other apps that may have played with files that I think could cause issues
4. double check my root backup (Voodoo)
5. temp unroot
6. update
7. restore root
8. enjoy
this method usually works without issues :/
and the reason I suspected build.prop in the first place is that restoring it allowed me to update on another device.
I'd really rather not have to flash it back to stock, but if it's my only option, I will. So any ideas that don't involve wiping everything would be wonderful!
Trevski13 said:
alright, detail time!
I'm currently on 4.1.1 (I've applied one update after I bought it on release day)
I have an ota update (to what I assume is 4.1.2)
stock everything, locked boot-loader, but rooted (used Exynos Abuse)
using SuperSU
my phone lists update_SCH-I605_LL4_to_MC3 which fails to install with error code 402
my device status IS "modified" but it appears to be related to the SD card as it is "normal" when I remove it (apparently a known issue)
normally when I get an update I do the following:
1. restore build.prop
2. remove busybox
3. remove/disable any other apps that may have played with files that I think could cause issues
4. double check my root backup (Voodoo)
5. temp unroot
6. update
7. restore root
8. enjoy
this method usually works without issues :/
and the reason I suspected build.prop in the first place is that restoring it allowed me to update on another device.
I'd really rather not have to flash it back to stock, but if it's my only option, I will. So any ideas that don't involve wiping everything would be wonderful!
Click to expand...
Click to collapse
Really the only thing I have seen to update is to go completely back to stock.
But why do you want to do this so badly? Why not just unlock and flash the new update rom Beans provided? Thats certainly the easiest way to do it in my opinion, since you're having all these issues, and it leaves you unlocked in case you don't like one of the future updates or if you want to test out AOSP.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Really the only thing I have seen to update is to go completely back to stock.
But why do you want to do this so badly? Why not just unlock and flash the new update rom Beans provided? Thats certainly the easiest way to do it in my opinion, since you're having all these issues, and it leaves you unlocked in case you don't like one of the future updates or if you want to test out AOSP.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I rely on my phone a lot and so even the short amount of time it would take me to fix a soft brick, or reconfigure a wiped device would be a problem. I'm not worried about bricking it, I'm worried about the time it takes to fix it. I soft bricked my old X2, and it was a real inconvenience (granted that was the first time I'd ever had to fix something like that) and I had to restore my Transformer Infinity back to stock to fix lag and glitching issues. (which lead to a whole partial root fiasco). So It's not that I can't fix the problems, it's that it takes time I don't have, and disrupts my life. If I had another 4g phone (because switching between 3g and 4g is a pain on Verizon) that I could switch to if I messed up and didn't have time to fix it, I'd totally start messing with custom roms, unlocking, and all that fun stuff, but I don't
Trevski13 said:
I rely on my phone a lot and so even the short amount of time it would take me to fix a soft brick, or reconfigure a wiped device would be a problem. I'm not worried about bricking it, I'm worried about the time it takes to fix it. I soft bricked my old X2, and it was a real inconvenience (granted that was the first time I'd ever had to fix something like that) and I had to restore my Transformer Infinity back to stock to fix lag and glitching issues. (which lead to a whole partial root fiasco). So It's not that I can't fix the problems, it's that it takes time I don't have, and disrupts my life. If I had another 4g phone (because switching between 3g and 4g is a pain on Verizon) that I could switch to if I messed up and didn't have time to fix it, I'd totally start messing with custom roms, unlocking, and all that fun stuff, but I don't
Click to expand...
Click to collapse
Well unlocking would let you go ahead and update and until you wanted to flash roms you wouldnt have to except for that first flash of the new update, which is what a stock update does.
The reason I say this is some people have had this problem and when they finally do get the update to work it soft bricks them. This is rare but it has happened. In the end for me it is just easier to unlock so I can play around when I want to and when I dont I can stay on stock.
Sent from my SCH-I605 using XDA Premium HD app
I wanted to post this here since I've been busting my tail on an update for a week now. This WILL flash, Backup & Restore android 4.4 roms! USB mounting, internal & external sdcard mounts as well. There are still a few bugs to work out but give it a go & some feedback. It's still a WIP but plenty stable to use daily for now.
Also anyone interested in flashing the CandyKat sweetener packs, you may now do so with this recovery!!
TWRP 2.8.7.0
I am not responsible for misuse, bricks, or exploding devices! Flash at your own risk! You can download the zip file & flash it from within your existing recovery & reboot to recovery.
CREDITS: Javelinanddart for fixing mounts, f2fs, & for fixing vibration for 5.0 & up Disconnecktie && Santod040 I have bugged these guys to death to get this working so Please stop in & thank these guys as well. They are a huge part of the success of this! Obviously this couldn't happen without Omniroms Source! And a huge thanks for
Dees_Troy for his guide to compiling twrp recovery!!
TWRP Themes have changed a bit & if you use a them then you'll want to checkout this link.
THEMING TWRP THE NEW WAY!
What's new in 2.8.7.0
- Initial ground work for software drawn keyboard (_that)
- Fix handling of wiping internal storage on datamedia devices (xuefer)
- Allow DataManager to set and read values from the system properties (xuefer)
- Fix crash when taking screenshots on arm64 devices (xuefer)
- Fix error message after an ORS script completes (Dees_Troy)
- Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
- Add system read only option - more details below (Dees_Troy)
- Add resize2fs and GUI option to run resize2fs (Dees_Troy)
- Fix crash loop caused by empty lines in AOSP recovery command file (_that)
- Prevent duplicate page overlays such as multiple lock screens (mdmower)
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don't take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
THEMING?
USE 1080P THEMES
Yeah!!
This is working perfect! Damn I missed TWRP. So freaking sweet!!
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Works well except mount memory
Liwais said:
Works well except mount memory
Click to expand...
Click to collapse
Mounting which partition? Anyone that finds an error or a bug should try posting the recovery log after said error. Don't post the entire log in a post but put it on pastebin or something similar. Having the logs greatly increases the likely hood the issue will be fixed. Thanks.
Liwais said:
Works well except mount memory
Click to expand...
Click to collapse
What do you mean by mount memory? Where you add something from the pc to the sd card & it shows up on the internal when in twrp? The internal sd card mounts when connected to the pc, not the external sd. I don't know if that's how it's suppose to work or not. This is my first twrp attempt and I had to build it from scratch basically. Like Disconnecktie stated, a log may be helpful.
Great work. Missed TWRP. Just had to tick off my internal sd. Panicked when my partition wasn't visible with my ROMs to flash. LOL.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I had in mind when're in rekaveri not mount the memory to your PC
Maybe this Problem just me, let me know
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
gimmeitorilltell said:
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
Click to expand...
Click to collapse
For some reason (most likely that I'm a dummy, or missed reading somewhere)
Recently my SD card took a poo, so I've been saving to internal memory.
I flashed TWRP. When I look in sdcard I have no files visible. When I am booted into CandyKat I can see my files with my file explorer. Am I missing a valid mount somewhere? When I go to / I don't see a folder called storage, and in my /sdcard all I see is a folder called TWRP which is empty.
THanks!
skearton said:
For some reason (most likely that I'm a dummy, or missed reading somewhere)
Recently my SD card took a poo, so I've been saving to internal memory.
I flashed TWRP. When I look in sdcard I have no files visible. When I am booted into CandyKat I can see my files with my file explorer. Am I missing a valid mount somewhere? When I go to / I don't see a folder called storage, and in my /sdcard all I see is a folder called TWRP which is empty.
THanks!
Click to expand...
Click to collapse
When you are in TWRP recovery are you selecting "Internal SDcard" or "MicroSD card"
Edit: Latest twrp recovery with vibrations enabled!
gimmeitorilltell said:
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
Click to expand...
Click to collapse
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
No it was not. I've been waiting on more feedback from the update or any of my twrp builds. Now that I'm aware of it, I'll look into that so we can get it official in Bigbiffs twrp thread. I think it's close enough for him to release it as an official but this is my personal feelings. It'll be a couple days maybe before I get back to it since I've spent the last week concentrating on this, it's time for me to move on to other things for a moment.
Sent from my HTC One Max using Tapatalk!
Newest build is working g sweet gimme. Love how ya added the button vibrate too. So far I've done 3 full wipes/flashes and your twrp has been flawless thanks for bringing this to us gimme.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
developweb said:
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
We can probably keep this here until the bugs are worked out. Have you tried the latest here yet? I don't theme my recovery but I'm willing to so I can get it correct.
Also that may be something you can set in twrp, set a different default path for themes but I'm not 100% sure.
gimmeitorilltell said:
We can probably keep this here until the bugs are worked out. Have you tried the latest here yet? I don't theme my recovery but I'm willing to so I can get it correct.
Also that may be something you can set in twrp, set a different default path for themes but I'm not 100% sure.
Click to expand...
Click to collapse
Default path in latest is correct now. Themes work from the correct directory now (/sdcard/TWRP/theme/ui.zip ) so they won't get deleted. Love button vibration as well! Excellent work.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
Default path in latest is correct now. Themes work from the correct directory now (/sdcard/TWRP/theme/ui.zip ) so they won't get deleted. Love button vibration as well! Excellent work.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Thank you for the feedback, it is very much appreciated! If you run into anything else, good or bad, Please feel free to give a shout out. I have OCD and with the vibration as an option, well it just was NOT an option to NOT work.. Lol
gimmeitorilltell said:
Thank you for the feedback, it is very much appreciated! If you run into anything else, good or bad, Please feel free to give a shout out. I have OCD and with the vibration as an option, well it just was NOT an option to NOT work.. Lol
Click to expand...
Click to collapse
I tried to install the full aroma rom patch by pollution and it seemed to work but gave com.android.phone error on boot. So I thought easy fix, I'll restore the backup I made with TWRP yesterday and got even more errors. Yes, I factory reset before restoring. It seems that this TWRP is not doing everything like it used to under the 4.2's. I'm going to go back to CWM and restore a CWM backup, regroup, recharge.......and try again from scratch to test this thing out again. Wish me luck.
Liwais said:
I had in mind when're in rekaveri not mount the memory to your PC
Maybe this Problem just me, let me know
Click to expand...
Click to collapse
I'm not sure that I understand what you're saying? The internal sd mounts to the pc once you go into twrp & mount it.
developweb said:
I tried to install the full aroma rom patch by pollution and it seemed to work but gave com.android.phone error on boot. So I thought easy fix, I'll restore the backup I made with TWRP yesterday and got even more errors. Yes, I factory reset before restoring. It seems that this TWRP is not doing everything like it used to under the 4.2's. I'm going to go back to CWM and restore a CWM backup, regroup, recharge.......and try again from scratch to test this thing out again. Wish me luck.
Click to expand...
Click to collapse
Best of luck to ya! I have restored my nandroid with twrp but not in my latest version. I'll give it a try this evening and see what happens on my end. I have not used the aroma installer because I personally would rather not use it. I just use the camera fix from Pollution since I don't have the screen flicker or any other issues with my phone.