Related
SOLVED - How to flash the Proper (Fixed) Stock Rooted Image
Description: This is 100% stock with just Superuser/su added and overwrites every partition to stock but keeps your personal data, apps, settings the same (just like the stock factory image).
Samsung Official USB Drivers - Link
ODIN v3.07 - Link
Proper Rooted Stock Image - Download or (Torrent Link) - MD5 = be4350a56e739eaf7a4184352d653a7b
1. Install USB drivers
2. Download ODIN v3.07
3. Backup your data
4. OPTIONAL: Do a factory reset (highly recommended if you have issues with your current ROM)
***WARNING: Step #4 will erase internal storage but not microSD card***
5. Download the above Proper Rooted Stock Image file and extract the tar file from inside it
6. Boot phone into ODIN mode (See here for how-to)
7. Flash the extracted tar file using ODIN v3.07
You should now have a like new condition stock image and rooted with all issues resolved.
Credit goes completely to mrRobinson for creating this image for us. Thank you sir. (Original Post) + (Details How It Was Made)
To Install Official CWM Recovery
1. After following above process, download "Rom Manager" from the Play Store
2. Open Rom Manager
3. Select "Flash ClockworkMod Recovery"
4. Select "Samsung Galaxy S3 (Verizon)" down at the bottom and let it flash
5. Once completed you can reboot to CWM by selecting "Reboot into Recovery" from Rom Manager
ORIGINAL REQUEST
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
BungeBash said:
Just formatted back to stock until issues can be resolved. The stock image (which I'm told this root is + su) lost all Sprint instances and any strange extra options. Also the Keyboards are back to functioning. Not to be a conspiracy theorist, but I feel that the root image has more going on with it than what we are told.
Click to expand...
Click to collapse
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
If you don't like it, dont flash it.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Hardly helpful for those who already flashed it... I just want it fixed, or a work around. If it's something as simple as uninstalling a few things, or replacing some databases, I'm fine with that. I just don't want to redo everything, and re-restore everything with Titanium Backup.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.
open1your1eyes0 said:
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.
Click to expand...
Click to collapse
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.
I did have some odd issues with SwiftKey crashing after flashing the image. Not sure if that has to do with it or not.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Useless post.
What would be useful is someone with the requisite knowledge being able to remake this exploit with the Verizon source in order to have maximum compatibility.
open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI
alquimista said:
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI
Click to expand...
Click to collapse
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.
I could do it, but it'd require more time than whats it worth. Sorry.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
You are a WORM!!!!!!!
Sent from my Galaxy Nexus using xda app-developers app
tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
Two completely pointless comments.
open1your1eyes0 said:
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.
Click to expand...
Click to collapse
You sir are a better man than me for being so humble in response to these replies.
I'm assuming invisiblek DID in fact use the VZW image if the phone still had all the VZW nonsense in it (VZ Navigator, for example) as that would not be found in the Sprint image. Equally, if "all" he did was follow the steps in the link, then someone else doing the same is likely to produce the same result.
tonu42 said:
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.
Click to expand...
Click to collapse
If you have these, have you posted them anywhere? That might have been a useful thing to do.
Here is all the removed apk's in a CWR zip.
http://www.mediafire.com/?6jv8wn9l5n0li9y
I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.
BungeBash said:
I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.
Click to expand...
Click to collapse
Thank you much sir. You assistance would be greatly appreciated.
Unfortunately I do not have a linux box so the guide does not work for me.
It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.
Goose306 said:
It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.
Click to expand...
Click to collapse
Considering I loaded the first root mod, then reverted to the image that it was created from and have 2 different setups I'd say two different files were used.
open1your1eyes0 said:
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.
Click to expand...
Click to collapse
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI
alquimista said:
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI
Click to expand...
Click to collapse
According to users, flashing that sammy-update firmware got rid of all the issues and the Sprint related stuff. Just, FYI.
If anyone is up for the remake, you might want to try making it out of this one. Not sure if it's any different but it's from another well known Samsung firmware site.
Link to stock factory firmware
This is a jellybean port so it should boot and work.
LINK
Please hit thanks before u download because this took me weeks to get working. I hope u like it.
MOD Edit: Link removed, its junk, you would not want it anyway
This is system dump based port.
Enjoy
:beer:
Trying it right now I guess a build compiled from source would be better, but this at least proves we can get this thing booting
this is a port ?
a port from which device exactly ?
EDIT
post some pics if u got it working guys
qwerty warrior said:
this is a port ?
a port from which device exactly ?
Click to expand...
Click to collapse
Nexus 7
Why didn't you include an updater script? Currently pushing the whole rom via adb, lol
Edit: Okay, that didn't seem to work
How can it have taken you "weeks" to get it working? JB hasn't even been out for "weeks"...
there doesnt seem to be a boot.img file in the zip
kuroneko007 said:
How can it have taken you "weeks" to get it working? JB hasn't even been out for "weeks"...
Click to expand...
Click to collapse
because the system dump from JellyBean happened on Day 1 of I/O...Before you try and correct somone, or 'ask a loaded question' do your homework. Cool to see that were able to boot into JB with an ICS kernel. I will try making a source build off of the JB-DEV branch later today after this EXTREMELY long sync finishes,,
Does it boot correctly?
Can anyone confirm that this boots?
garylgray said:
Can anyone confirm that this boots?
Click to expand...
Click to collapse
if it doesnt have a boot.img then id guess it wouldnt.
nocoast said:
if it doesnt have a boot.img then id guess it wouldnt.
Click to expand...
Click to collapse
It works. Ill post screenshots in a few minutes
skyrocket23 said:
It works. Ill post screenshots in a few minutes
Click to expand...
Click to collapse
Backing up now, I will too.
Anything else someone wants tested? I can only do this for a hour or so, need it as a working phone
My computer cannot edit zips this large, it just freezes, could anyone make a zip with update script? I guess your just using the CM9 boot.img?
Habarug said:
My computer cannot edit zips this large, it just freezes, could anyone make a zip with update script? I guess your just using the CM9 boot.img?
Click to expand...
Click to collapse
I have no skill in this, but my computer can open it just fine.
If you give me instructions and the file il drop it in and upload it for you
Edit: Just realized I cant just flash this... epic facepalm
this is what I get for being overeager to help
What I think will work is taking the zip of the latest CM9, deleting the system folder in there and replacing it with the system folder in OP
Habarug said:
What I think will work is taking the zip of the latest CM9, deleting the system folder in there and replacing it with the system folder in OP
Click to expand...
Click to collapse
im trying that now..doesnt seem like its booting though
wauktownzown said:
im trying that now..doesnt seem like its booting though
Click to expand...
Click to collapse
Il try it also and upload it, not sure if I feel comfortable flashing it though
Hello guys,
can you please wait flashing it? I download it at the moment and will test it for you. If my device gets broken it's not a huge probelem:
1. i have s-off (no not made by myself)
2. i have flashed a new rom with wipe 1 hour ago.
SO you don't need to delete your apps or waste your time.
Showing back in, i would say 30mins
So... my question to the OP is, how did you install the rom with no META-INF folder (what actually installs it) and with no boot.img (kernel)? And where are those screenshots?
---------- Post added at 03:30 PM ---------- Previous post was at 03:30 PM ----------
I am about to try to flash it with CM9 components
this seems like something that wasnt 100% ready and just rushed out to be 1st to post it..or you made a mistake and uploaded the wrong zip file?..either way thanks i guess..waiting for the screenshots:fingers-crossed:
As the name implies this the unsecure stock kernel boot.img
You can use the adb remount command to push files to system now!
YOU MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS! See here for more info: http://forum.xda-developers.com/showpost.php?p=30274025&postcount=317
If you dont know what this then it may not be for you. This is more so developers can use in there ROMS.
No need to ask to use it, just give credit if you do.
Download HERE
Chang Log
v3 - Corrected incorrect adbd in /sbin for proper colors when using screen capture while in Dalvik Debug Manager.
v2 - Added Lib folder for that need it.
New clean ROM soon then?
Sent from my SCH-I535 using xda app-developers app
Would it be too much to ask for an AOSP kernel (ICS)? I'd do it myself, but I don't know much about kernels lol
Nopi45 said:
New clean ROM soon then?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, this is more for developers.
It just unlocks the /system partition so you can push files. I mean, yeah, it will be in the next CleanROM but its not urgent from a user perspective.
PureMotive said:
Would it be too much to ask for an AOSP kernel (ICS)? I'd do it myself, but I don't know much about kernels lol
Click to expand...
Click to collapse
This is a Stock kernel. I just modified the RAM Disk to remove security and to add init.d support and set up the script so it can be flashed.
I didint build the kernel. Its just stock.
How come your user name is in italics BTW?
Not sure on run parts... Need to check. Unsecure is still a go!
scrosler said:
This is a Stock kernel. I just modified the RAM Disk to remove security and to add init.d support and set up the script so it can be flashed.
I didint build the kernel. Its just stock.
How come your user name is in italics BTW?
Click to expand...
Click to collapse
I know it's stock. I was just wondering whether you were able to get an unsecured AOSP kernel for all of the AOSP ROMs out there. It'd also help with Sense 4.
To get your username in italics (RDs only):
Go to User CP
Select "Group Membership" from the side bar
Select "Recognized Developer - Identify me as a member of this group"
Save
Well this work on lf2?
Neverendingxsin said:
Well this work on lf2?
Click to expand...
Click to collapse
Are you a dev?
No?
Keep moving
VERIZON GALAXY S 3
PureMotive said:
I know it's stock. I was just wondering whether you were able to get an unsecured AOSP kernel for all of the AOSP ROMs out there. It'd also help with Sense 4.
To get your username in italics (RDs only):
Go to User CP
Select "Group Membership" from the side bar
Select "Recognized Developer - Identify me as a member of this group"
Save
Click to expand...
Click to collapse
To make it unsecure its just some changes in the RAM Disk. Im sure if the AOSP guys are out they know how to do that. If not they can reach out to me for help but they tend to know more than I do about kernels and all
Thanks for the heads up the italics!
Neverendingxsin said:
Well this work on lf2?
Click to expand...
Click to collapse
DROID3R said:
Are you a dev?
No?
Keep moving
VERIZON GALAXY S 3
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This is mostly for developers that want to do things that having a locked boot.img normally stops you from doing. An average user will gain little value...
But lets say you were making a theme and had to "push" files to the /system folder you can NOW do that with this boot.img. It makes Dev's lives a LOT more easy now, lol
scrosler said:
To make it unsecure its just some changes in the RAM Disk. Im sure if the AOSP guys are out they know how to do that. If not they can reach out to me for help but they tend to know more than I do about kernels and all
Thanks for the heads up the italics!
This is mostly for developers that want to do things that having a locked boot.img normally stops you from doing. An average user will gain little value...
But lets say you were making a theme and had to "push" files to the /system folder you can NOW do that with this boot.img. It makes Dev's lives a LOT more easy now, lol
Click to expand...
Click to collapse
yes it does, copying files to my sdcard and then moving them with root explorer, or packaging them in a flashable zip and copying to sdcard and flashing everytime is frustrating. specially if your doing it every 10-15 mins.
nosympathy said:
yes it does, copying files to my sdcard and then moving them with root explorer, or packaging them in a flashable zip and copying to sdcard and flashing everytime is frustrating. specially if your doing it every 10-15 mins.
Click to expand...
Click to collapse
Tell me about man, tell me about it!
And I confirmed init.d support is functional as well!
I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks
newuser134 said:
I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks
Click to expand...
Click to collapse
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.
Hey scrosler how can I identify that the flash worked. The ROM booted normally but in the kernel name I don't see any change.
wooddale said:
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.
Click to expand...
Click to collapse
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?
Try it??? If it fails just restore from backup?
Sent from my Nexus 7 using Tapatalk
newuser134 said:
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?
Click to expand...
Click to collapse
I tried this out and did not see ANY difference. But then again it's midnight and I won't know if anything will be wonky until I use it at work tomorrow
sent from a locked downloader
newuser134 said:
I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks
Click to expand...
Click to collapse
Well, you can try it but my experieince tells me that you may loose LTE and WiFi because yo dont have matching modules. The modules (aka drivers if it were windfows) hare specific to a kernel. If you took the /system/lib/modules folder from a G1 ROM like mine or nosympathy and pushed them in I bet it would work just fine. But why on earth are you on older build?
wooddale said:
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.
Click to expand...
Click to collapse
No, Gerneally ROMS dont include the radios from my experience. BUt I heard int he samsung world Devs do things differently so I dont honestly now.
jb_alphamale said:
Hey scrosler how can I identify that the flash worked. The ROM booted normally but in the kernel name I don't see any change.
Click to expand...
Click to collapse
Thats easy... Before you flashed the boot.img was USB deggign turned on? If not it would be turned on now.
If USB degging was already on or not on turn it on... Then... connect phone and wait for the connection to finish. Then type "adb remount" (assuming you have ADB handy) and it should say "remount succeeded" If it says operation not permitted then it did not take.
newuser134 said:
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?
Click to expand...
Click to collapse
Hipcatjack said:
I tried this out and did not see ANY difference. But then again it's midnight and I won't know if anything will be wonky until I use it at work tomorrow
sent from a locked downloader
Click to expand...
Click to collapse
What difference did you expect? Its a STOCK kernel and will behave like a stock kernel except give full and true root access to the device. Its not for the end user its for developers. Of course this ramdisk will also allow us to start modifying and shutting off services, tweak things at the kernel level, etc... But right now, this is just bone stock with init.d support and root level access to the file system via ADB.
Hope that explains it some.
I'm in search of a Nexus Player owner with sufficient ADB/Fastboot knowledge that would be able to run a few commands for me and test a few things. If that person happens to be you, please leave a reply in this thread so we can get started developing for the Nexus Player!
ProfessorAnomaly said:
I'm in search of a Nexus Player owner with sufficient ADB/Fastboot knowledge that would be able to run a few commands for me and test a few things. If that person happens to be you, please leave a reply in this thread so we can get started developing for the Nexus Player!
Click to expand...
Click to collapse
I might be willing to help. What is it you are wanting to do?
peppy6582 said:
I might be willing to help. What is it you are wanting to do?
Click to expand...
Click to collapse
I'd like somebody to test the custom recovery I've compiled, and to make sure it works properly.
ProfessorAnomaly said:
I'd like somebody to test the custom recovery I've compiled, and to make sure it works properly.
Click to expand...
Click to collapse
I don't intend to be rude, but what is your comfort level of non-brickage?
peppy6582 said:
I don't intend to be rude, but what is your comfort level of non-brickage?
Click to expand...
Click to collapse
There is no risk in bricking your device. You simply just have to boot the recovery.img and make sure it works.
Code:
fastboot boot recovery.img
7778c713fe675747fc4ce937fd40fe2e recovery.img
Download retracted for the time being.
ProfessorAnomaly said:
There is no risk in bricking your device. You simply just have to boot the recovery.img and make sure it works.
Click to expand...
Click to collapse
Yes, I will try. You have a pretty good track record! I had to check first, because I really like this thing!
Simply boot the image with fastboot and make sure that ClockworkMod Recovery is displaying properly on your TV. This way when you reboot your device nothing will have been changed, so there is no risk involved.
peppy6582 said:
Yes, I will try. You have a pretty good track record! I had to check first, because I really like this thing!
Click to expand...
Click to collapse
I appreciate your help! I have experience, so if you do encounter problems along the way I am available to help.
ProfessorAnomaly said:
I appreciate your help! I have experience, so if you do encounter problems along the way I am available to help.
Click to expand...
Click to collapse
I can see the device (adb devices), but when I do the fastboot command, it says waiting for device.
peppy6582 said:
I can see the device (adb devices), but when I do the fastboot command, it says waiting for device.
Click to expand...
Click to collapse
You must run this command first:
Code:
adb reboot bootloader
Followed by:
Code:
fastboot boot recovery.img
ProfessorAnomaly said:
You must run this command first:
Code:
adb reboot bootloader
Followed by:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Had to unlock it first. Nevermind. It booted into Android system recovery <3e>
peppy6582 said:
Had to unlock it first. Nevermind. It booted into Android system recovery <3e>
Click to expand...
Click to collapse
Alright, I will check my source again and recompile. I must have made a mistake along the way. If you're interested I'm also working on an auto-root that will be ready here shortly.
Do you have a gmail so that I could correspond with you via Hangouts? (If so, could you private message it to me?)
ProfessorAnomaly said:
Alright, I will check my source again and recompile. I must have made a mistake along the way. If you're interested I'm also working on an auto-root that will be ready here shortly.
Do you have a gmail so that I could correspond with you via Hangouts? (If so, could you private message it to me?)
Click to expand...
Click to collapse
I pm'ed you
I am also willing to assist if needed. I am comfortable with adb and fastboot.
I'm pretty comfortable with ADB and Fastboot. I wouldn't mind testing some stuff if you need me to.
Google already posted the factory images for the Nexus Player, so I don't mind. I'm interested in seeing what is possible with this little hockey puck.
Please add me to your list of candidates. I'd be very interested in checking out what you've got. Thanks.
ProfessorAnomaly said:
I'm in search of a Nexus Player owner with sufficient ADB/Fastboot knowledge that would be able to run a few commands for me and test a few things. If that person happens to be you, please leave a reply in this thread so we can get started developing for the Nexus Player!
Click to expand...
Click to collapse
willing to help, should you still need.
If you still need another tester tell me.
I've already worked with headless CWM during my work on the ADT1 (controlling CWM entirely via adb, I have no keyboards that work with it)
I've been trying to avoid compliling CWM myself as I dont want to have rebuild my dev vm just to compile CWM
(I've built CWM 6.0 in the past, but it was years ago)
Currently need access to a booting (doesn't matter if the CWM parts work, all I need is a root shell) image to dump the initial rom.
Fortunately, since we already have factory images, at least I/someone wont need to prepare a flashable zip for it to restore.
TheManii said:
Currently need access to a booting (doesn't matter if the CWM parts work, all I need is a root shell) image to dump the initial rom.
Fortunately, since we already have factory images, at least I/someone wont need to prepare a flashable zip for it to restore.
Click to expand...
Click to collapse
What are you trying to dump that's not in the factory images?
Hi all, did anyone build a recovery? I would do it but I haven't got a computer that runs Linux and I am not firm with it at all.
Edit: I couldn`t use any method that I found to create a custom recovery, is there anyone with more success?
Also I could not use SP-Flash tool to make a backup, did anyone succeed and how?
Thanks
Sent from my HTC One A9 using XDA-Developers mobile app
new device ordered hopefully we see some development in this section soon =)
i also hope but i think this was not the interessted phone for developper...
Is there nobody to do this recovery?
Brainwasher34 said:
Is there nobody to do this recovery?
Click to expand...
Click to collapse
We gotta wait
If anybody cares about this and is willing to test some blind builds of TWRP, let me know (by replying here).
Captain_Throwback said:
If anybody cares about this and is willing to test some blind builds of TWRP, let me know (by replying here).
Click to expand...
Click to collapse
I am interested in testing some builds of twrp on my a9s, are your offer still available?
Greetings.
patrixs94 said:
I am interested in testing some builds of twrp on my a9s, are your offer still available?
Greetings.
Click to expand...
Click to collapse
Well, a month has passed, and I've forgotten everything I knew about this device, but I'll give it a shot when I have a chance. Stay tuned.
EDIT: It seems a month ago I built a test recovery for this device, but was waiting for a response before posting it. So @patrixs94 I'm attaching it here. Give it a try and let me know if it boots, and if so, I'll need a recovery log from it.
Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
Captain_Throwback said:
Well, a month has passed, and I've forgotten everything I knew about this device, but I'll give it a shot when I have a chance. Stay tuned.
EDIT: It seems a month ago I built a test recovery for this device, but was waiting for a response before posting it. So @patrixs94 I'm attaching it here. Give it a try and let me know if it boots, and if so, I'll need a recovery log from it.
Click to expand...
Click to collapse
---------- Post added at 01:19 PM ---------- Previous post was at 12:56 PM ----------
Ok, I founded one, but it does not fit to my mid/ cid . And I dont have s-off :/
patrixs94 said:
Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
Click to expand...
Click to collapse
patrixs94 said:
Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
---------- Post added at 01:19 PM ---------- Previous post was at 12:56 PM ----------
Ok, I founded one, but it does not fit to my mid/ cid . And I dont have s-off :/
Click to expand...
Click to collapse
Flashing recovery shouldn't bootloop your device. Recovery is an entirely separate partition. You can try using "fastboot boot recovery.img" to see if that works, as that won't change anything on the device, but not all devices support it.
Honestly though, if you're not comfortable enough to test this, then there's no reason for me to work on this. Like I said, I know next to nothing about this device, so I need someone that can help me debug and provide logs, etc. Otherwise this exercise is futile.
Tested
Hi,
thank you, it´s great you are working on TWRP for this phone! I have tried to use it. After download it says booting on notebook and Start downloading on phone:
C:\fastboot\ fastboot boot recovery.img
downloading `boot.img`......
OKAY (1.453s)
booting...
After hard restart the phone works again.
Does it helps you?
T.
Captain_Throwback said:
Flashing recovery shouldn't bootloop your device. Recovery is an entirely separate partition. You can try using "fastboot boot recovery.img" to see if that works, as that won't change anything on the device, but not all devices support it.
Honestly though, if you're not comfortable enough to test this, then there's no reason for me to work on this. Like I said, I know next to nothing about this device, so I need someone that can help me debug and provide logs, etc. Otherwise this exercise is futile.
Click to expand...
Click to collapse
vejda said:
Hi,
thank you, it´s great you are working on TWRP for this phone! I have tried to use it. After download it says booting on notebook and Start downloading on phone:
C:\fastboot\ fastboot boot recovery.img
downloading `boot.img`......
OKAY (1.453s)
booting...
After hard restart the phone works again.
Does it helps you?
T.
Click to expand...
Click to collapse
All that tells me is that your device doesn't support fastboot boot. So you'll need to flash it to test whether it works or not.
Code:
fastboot flash recovery recovery.img
Thx. Flashed, after booting to recovery mode there is start screen, but I am not able to swipe to unlock it. Where can I find the log? Is it something like db.fatal.dbg?
Captain_Throwback said:
All that tells me is that your device doesn't support fastboot boot. So you'll need to flash it to test whether it works or not.
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
vejda said:
Thx. Flashed, after booting to recovery mode there is start screen, but I am not able to swipe to unlock it. Where can I find the log? Is it something like db.fatal.dbg?
Click to expand...
Click to collapse
/tmp/recovery.log
Is adb working? If so, you can adb pull the above file. Then I can at least see how much is working (besides touch being broken).
Yes, ADB works, but the file doesn´t exist (with the way /tmp/recovery.log). Only general bugreport, attached.
Captain_Throwback said:
/tmp/recovery.log
Is adb working? If so, you can adb pull the above file. Then I can at least see how much is working (besides touch being broken).
Click to expand...
Click to collapse
vejda said:
Yes, ADB works, but the file doesn´t exist (with the way /tmp/recovery.log). Only general bugreport, attached.
Click to expand...
Click to collapse
The recovery log has to exist while in TWRP.
ADB doesn´t run while TWRP, screen attached.
Captain_Throwback said:
The recovery log has to exist while in TWRP.
Click to expand...
Click to collapse
vejda said:
ADB doesn´t run while TWRP, screen attached.
Click to expand...
Click to collapse
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.
Ok, thx. I am not expirienced user of it, but try to solve it Where are all the others? Hey!!
Captain_Throwback said:
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.
Click to expand...
Click to collapse
Here it is!
Here is the log, I was using old ADB.
Captain_Throwback said:
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.
Click to expand...
Click to collapse