Related
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Neoprimal said:
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Click to expand...
Click to collapse
I don't know how much direction pointing I can do but here goes..
Clockwork mod in my opinion is a necessity. Version 0.8 is the best one for most people because of how it deals with the memory locations. Yes, you can do things without it. The update process is as simple as putting an update.zip file, and a recovery folder with a command file in it on an sdcard and holding the vol + button while hitting power. It is easy. Clockwork has a lot of little features though that make life easier. You can make a complete system backup with it. You can install updates, and new firmware with it. You can completely lock up your tablet and using clockwork and your backup be back in business in about 3-4 minutes. You can load new roms and if you hate them you can go back to your old working stuff in minutes. Yes, there are ways to make one of these tablets work again when they get stuck. I don't think anyone has actually bricked one. Some may think they have, but I doubt it.
Unless you are dead set on wanting the stock TnT interface the easiest way to get what you want is to load one of the roms. Yes, there are ways to get most of it without loading a new rom. Most everyone that has gone the I have to stay stock but want all the mods has eventually just loaded a rom. TnT3.0 is based on the latest stock stuff. It has the market, flash, etc. already in it. VegaN is what I use mostly but they are both stable and fast.
Before you flash something brand new that just came out I would read about it and see what others have to say about issues. It usually only takes about 30 minutes until you can tell if it is going to be good or not.
All of the roms for this tablet have there own little quirks. The stock has gotten better with each update but it still is not as good as the ones I named.
Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard.
With a little bit of searching almost everything you may want it to do can be done. I really love mine, and when I got it almost 2 months ago I hated it...
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Neoprimal said:
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Click to expand...
Click to collapse
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
I can vouch for that. Erased system, boot, data and cache in preparation for a new ROM. Accidentally rebooted and couldn't get into recovery. Booted it into APX mode, flashed stock and was on my way.
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Sprdtyf350 said:
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Click to expand...
Click to collapse
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
hogasswild said:
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Click to expand...
Click to collapse
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
Thanks for the info Rothnic! I had already flashed it before I figured out it removed Clockwork. Learning new stuff every day is good... Thanks..
dragonfly1113 said:
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
Click to expand...
Click to collapse
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
hogasswild said:
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
Click to expand...
Click to collapse
Ok cool, thanks cant wait for my g tablet hopefully sat morning
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
hogasswild said:
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
Click to expand...
Click to collapse
my mom has an ipad and my dad could only buy it while i was on my honeymoon bc he knew i wouldnt approve of an apple device in the house haha.
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
My device hasn't come yet (damn you FedEx!) but I'm eagerly awaiting it.
My plan:
Unbox, start it....do a factory reset from the getgo if it has enough juice.
Set it back up. Charge it to full. If whatever comes on it is as unbearable as I've seen in on Youtube - start modifications.
Will CWM install on it AFTER I do the update if it's available to me? I've seen that the update messes with it if it's already there - but noone's mentioned putting it on there after the fact. I may just go that route for simplicity sake.
Thanks for this!, and thank you all for chiming in with your experience. I feel much better about just getting my hands dirty in it all. I had wrote something to someone yesterday about jumping in and just doing it, but when it comes to dealing with it yourself it can be a daunting task - especially when it still has that new smell, lol. Anyway, thanks again. You guys really rock.
Will stop back later on after I've done my thing
I think they are both nice devices. There are trade off for both of them. I think the screen on the iPad is wonderful, where the gTab's is okay. But the gTab has a forward facing camera, you can print from it, and you can modify it fairly easily too.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
...famous last words...
Seriously though...trust the directions from the great devs like roebeet. Follow their instructions word for word. You can switch ROMs and then flash back if you want. No worries...
Off topic!
Well...disappointment! Fedex had my package out for delivery at 8am and at 8pm, they're not here. This is why I like UPS, they show up at my door on the day of delivery, no exceptions - they have shown up at almost 9pm before. The Archos 101 I got was sent out at 8am as well but got here at 1:30pm - I suppose that was before the holiday rush.
Checking the details of my tracking I'm seeing a "delivery exception" at 7:30pm (I guess it was time to get back to the facility so they can clock out by 8pm?) and upon calling them I get a somewhat stumbling but polite CS who tells me the delivery went out "late" - upon which I asked if 8am was considered late, especially from a distribution facility WITHIN the same zip code as I am, and all he could say was "Very sorry about this".
Aaaanyway....I guess it will be tomorrow before I can report my adventures.
Think I'll be able to get my $3.99 back from Amazon? I have Prime and with that the package would have come tomorrow anyway. Basically my $3.99 is wasted. Imagine if I didn't have Prime though? Whew.
ima_UNC_fan said:
...famous last words...
Click to expand...
Click to collapse
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
I finally got the G tablet tonight and...alright, don't flame me for this - but I don't see what all the complaints about the screen being horrendous or the device being molasses slow are about?
I don't know how people are trying to view it...but when looking at it or setting it on a stand to watch media, I'm not seeing any problem with the viewing angles. It's about the same as my laptop so I watch it the same way.
It's not even a 1/4 as slow as the stuff I've seen on Youtube or in some of the review videos I've seen around the net. I haven't gotten a single FC. Granted, I haven't put in a SD Card yet so maybe problems will start then?
I guess I should note, the very first thing I did was did a factory reset. Then I hooked it up to Wifi and got the 3053 update. I'm one of those who will be waiting for the 'official' update on the 24th.
I set up the time and date, restarted and everything works. I haven't installed flash yet (don't need it that much) and stuff that I DO want on there right now works fine (skype, pandora, fring, dropbox, evernote). I'm slowly figuring out a list of what I want/need from my Mytouch 4G to port to the VS GTab. Figure I don't really NEED Gtalk, Gmail on there because I have these on my phone AND PC - do I really want them making noises all around my home on 3 devices? I was concerned about getting the Google Apps on but now I'm finding I really don't need them. So it seems to me this will be a matter of learning to separate what I need on a tablet vs. my phone - I was of the mentality that I should just get whatever's on my phone on the tablet, this is something others apparently do as they seem to want everything that's on their phone, on their tablets as well.
I personally don't see the point in that. Had I had the Google Market, that would have escaped me as I'd have used Appbrain to just get my motherload of apps from the MT4G to the GTab. Not having it has slowed me, and now I get to re-evaluate before I do grab apps for it.
Now I just have to merge/convert my HTPC into a NAS device as well and find an app that will allow me to DLNA stream media from it and I'll be in mobile heaven.
I haven't had my wifi drop at all anywhere in my home and I've marched all over with it (I use full Wifi N, no G compat. so maybe my range is wider?). Tried email, etc. to replicate crashes and force closes but haven't so far. No surfing issues. I DID find that one app got 'stuck' being downloaded and I had to delete the file before the 'downloading' icon would go away, even after restart.
Maybe the trick to getting a workable GTab in the first place is to factory reset it before first use? Iunno. Things may change and issues may pop up the more I use it and as time passes - but so far, so good!
Again, I can't thank XDA enough for the advice and info. I've found and been given.
Sprdtyf350 said:
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
Click to expand...
Click to collapse
I figured it out. Accidentally hit one of the devkit nvflash .cabs and boom
I'm not new to android whatsoever.. I've just returned from an Iphone 4s cause i was missing the openess of android. Now.. i've pulled out my old Nexus S 4g, Updated it to 4.0.4 and i cant get it to connect to my computer for the life of me! tried 4 different cables, 5 different computers, every driver i could find and nothing. I've come to believe this is a software failure... All i need is root and i will be able to sleep at night. Could someone package up .zip to give root and twrp recovery that i could flash through stock recovery? I dont know else i could do to get root... but this problem is becoming quite annoying.
1. There is no way to package a zip to flash through stock recovery since it would have to be signed.
2.For someone who is "not new to android whatsoever" making 2 threads about the same topic 2 minutes apart isn't exactly acting the part.
Try this guide.
Actually you're wrong, On the Epic 4G someone did in fact manage to do so. And yeah since i'm not new to these forums i understand that stuff like this gets overlooked so i made two posts. Cry me a river.
BTW Thanks harb... but that would involve being able to connect to my PC. Which just is not possible right now.
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
robogoflow said:
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
Click to expand...
Click to collapse
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
Bro... Chill... They're just trying to help you out. There is NO way to to root your NS without a computer (currently. We are not Epic 4G owners here). You said you didn't use your NS since GB, SO during the time in between something could have happened to the hardware. Don't rule that out just yet. Your drivers might also be bad. Is this what migrating to iOS does to people? Makes them snobby and demand fixes to problems they can't figure out on their own? Don't hate on the XDA forums. If we're not helping you "hit the thanks button anyways, you ungrateful bastard" (XDA into video ). Anywho. Chill. Keep trying.
Nexus S (GSM i9020a)
Paranoid (14.a Hybrid - 4.0.4)
Matrix Kernel (CFS - 20.0)
Intellidemmand (800/100)
Live OC (105 - 800/1000)
Deep Idle (On - Noop)
BLX - 96 (Inverted Apps)
I am chill, i am just trying to describe what I've already done so maybe someone could suggest something else. And no what i meant is i downloaded the OTA on my computer than transferred it onto my Nexus through USB mount a couple of days ago so i know its not a hardware issue. Im not demanding fixes, just trying to see if anyone has done been able to figure this out yet as i know im not the only one with this issue. And there is a big problem w/ people on the XDA forums as a whole.. i am a little frustrated and just dont like when someone is telling me is a User issue when i have tried everything conceivable and know what i am doing.. Sorry if this offended you. and IOS is a good device.. its just like.. NWO they want to control everything haha. I'd rather be part of the rebel faction. even though i love my ipad XD
There is currently no way to root 4.0.4 without an unlocked bootloader (and no custom recovery), and the only way to get an unlocked bootloader is to either have root or plug it into the PC and unlock via fastboot. As such, you are stuck with sorting out drivers - despite how annoying they are.
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Harbb said:
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Click to expand...
Click to collapse
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
grumpySasquatch said:
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
Click to expand...
Click to collapse
Pretty sure that video describes that. You need to open up device manager, double click unknown device (while device is in fastboot), hit update driver and navigate to the provided drivers on the site. Watch it a few times, you'll figure it out.
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
d_phekt said:
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
yes i second that,PDANet Drivers usually work across all devices you should try them.
Like ppl said before, try PdaNet drivers it might help.
thanks everyone, , but like i said i tried pretty much every driver you can find online. they will not install as my device comes up as "Unknown", i've literally tried every piece of literature on the web relating to this issue... at this point i'm just going to wait for the JB update and see what happens.
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
So the ICS update makes you unable to boot to fastboot and makes your device unable to be recognized by your computer from there?
That's a new one. As far as I know, "Unknown device" is actually your device being recognized, just the driver doesn't get installed correctly.
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
polobunny said:
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
Click to expand...
Click to collapse
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Epic 4G could do this in FROYO... It was patched by google in 2.3+. Do you want an app to secretly root you and install malware?
Sent from my Samsung Epic 4G using Tapatalk 2
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Well it is going to be basically one of two things.
1. Is user error of some sort. That is what people have been trying to help with.
2. Is hardware issue that no one can help you with of course. Or some software issue causing it to not show up for who knows what reason. Neither of which folks can help with since a computer is not seeing it. So they revert back to what they can. Point 1
When you asked a question like is there a zip that you can flash in stock recovery to give you root or custom recovery that also doesn't help your cause for people assuming user error.
The one other thing you can try is download mode and Odin.
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Cool. Trash your Nexus S, clearly broken.
Edit: That's nice of you albundy, but Mr grumpySasquatch (fitting name eh?) has tried everything, including modding the drivers inf. His Nexus S is broken beyond repair, also the first one we've ever seen that won't adb but works fine for USB mounting. *chuckle*
I was wondering if anyone had any info on the status of roms for the Behold II. I just got one, used but in very good shape, and I am trying to get it to work better. I am fairly sure these phones were pretty popular, and I can't believe they were (almost) completely ignored. I found a pretty nice clean android 1.6 rom that I threw on it, but it has no vibrate.
Does anyone know of any stable gingerbread roms for this phone? If not, anyone know how to get vibration to work? Is there anyone out there willing to work on this phone at all?
Or can anyone point me in the direction of some information on taking the rom apart and figuring out how to get the vibration working? Basically I need to find out how to take apart a rom, then figure out how to get vibration working properly. It's driving me nuts that the phone doesn't vibrate when I get calls/texts.
Isn't that Donut? *throws up*
Couldn't find any ROMs above 1.6 with some googling. Its also likely that you would not be able to fix the vibrate issue, if the Dev couldn't. If you want to "take the ROM apart," just take the .zip file and unzip it.
But I recommend getting a new phone.
Sent from my Nexus 4 using xda premium
It is indeed Donut. That's why I wanted to try and find a gingerbread rom or figure out how to make my own.
I unzipped the rom and dug around in there. I found some other thread on these forums about vibration and the symlinks and vibrate.ko. I checked in init.rc (on the phone) and found some lines about inserting modules relating to VibeTonez and the module "vtmdrv.ko" but I don't know if it is commented properly or turned on or symlinked or whatever. I see nothing about an actual vibrate.ko or anything.
How do I check my updater-script for the correct symlink?
I found this thread that has given me some interesting information: http://forum.xda-developers.com/showthread.php?t=1946614
and also this one: http://forum.xda-developers.com/showthread.php?t=1405366
Thanks for the interest! Unfortunately, I cannot just get a new phone. I am basically stuck with this one for the foreseeable future.
nookle said:
It is indeed Donut. That's why I wanted to try and find a gingerbread rom or figure out how to make my own.
I unzipped the rom and dug around in there. I found some other thread on these forums about vibration and the symlinks and vibrate.ko. I checked in init.rc (on the phone) and found some lines about inserting modules relating to VibeTonez and the module "vtmdrv.ko" but I don't know if it is commented properly or turned on or symlinked or whatever. I see nothing about an actual vibrate.ko or anything.
How do I check my updater-script for the correct symlink?
I found this thread that has given me some interesting information: http://forum.xda-developers.com/showthread.php?t=1946614
and also this one: http://forum.xda-developers.com/showthread.php?t=1405366
Thanks for the interest! Unfortunately, I cannot just get a new phone. I am basically stuck with this one for the foreseeable future.
Click to expand...
Click to collapse
No prob. Always interested in the legacy devices.
I wouldn't try to fix the vibrate, the developer himself states it will likely never be fixed (http://androidforums.com/behold-2-all-things-root/54769-port-galaxy-1-6-behold-2-final.html). I didn't read into the thread, but usually some user asks why vibrate doesn't work, dev explains, etc. You don't know if the problem with the ROM is the same as the issues found in the threads you searched.
If you want Gingerbread, it looks like the device is pretty much dead, however you can port CM7 from a similar device. It would be quite a chunk of work though.
Sent from my DROID2 using xda premium
Yeah, I have been going over all those threads that have that guy's roms. He made a few of them for this phone, and I am trying to find one that is better. Or the best of them.
I think I may have found a pretty major bug in the one I have, though. I got a call, I didn't want to answer it, and I hit the volume down button to silence the ringer, but it force closed android.phone.com and dropped the call. That wasn't cool.
I am also (kind of half-heartedly) pursuing creating my own rom from scratch. It's quite daunting, but I have a lot of time for the next week or so. My sister is having a complicated pregnancy so I am spending a lot of time at the hospital. There are plenty of guides and tutorials for beginners, so I am reading those and trying to figure things out.
Or I can figure out how to work on the rom this guy made, that would make life much easier.
nookle said:
Yeah, I have been going over all those threads that have that guy's roms. He made a few of them for this phone, and I am trying to find one that is better. Or the best of them.
I think I may have found a pretty major bug in the one I have, though. I got a call, I didn't want to answer it, and I hit the volume down button to silence the ringer, but it force closed android.phone.com and dropped the call. That wasn't cool.
I am also (kind of half-heartedly) pursuing creating my own rom from scratch. It's quite daunting, but I have a lot of time for the next week or so. My sister is having a complicated pregnancy so I am spending a lot of time at the hospital. There are plenty of guides and tutorials for beginners, so I am reading those and trying to figure things out.
Or I can figure out how to work on the rom this guy made, that would make life much easier.
Click to expand...
Click to collapse
I wouldn't try to make a ROM from scratch. A better thing to do would be to port. Basically find a ROM made for a phone with similar internals (type of CPU and RAM) and port the ROM. Much easier than making a ROM from scratch which requires knowledge of a few computer languages (mainly java). There are a few porting guides available on the forum.. Lemme find a link
Sent from my Nexus 4 using xda premium
Hey, thanks for your help! It's much appreciated! And believe me, if I could get a new phone I would. This phone is on my parent's plan, and only used for calling and texting family. I can't use data or anything. At this point it's more for the sake of learning about how to build an android operating system than anything else. I just want a nice, stable, useful phone that is better than the old school flip phones (of which I have had quite a few over the years).
Once again no prob. I used a legacy device just last year but it had quite some development so all I had to do was flash Roms lol.
Anyways this is how you compile GB
http://forum.xda-developers.com/showthread.php?t=1183832
And this is how you port. I would port from a similar device like the My touch 3g
http://forum.xda-developers.com/showthread.php?t=1598713
Sent from my Nexus 4 using xda premium
Haha yeah I am in the same boat with my nook. I have been following the devs over in the nook sub-forum for a couple years now. I have had several iterations of gingerbread, a couple of ics, and now a few of jelly bean. I am used to just slamming the rom zip on the sd card and booting into recovery and flashing it over.
For this phone I had to do odin, which was a new experience for me. Went pretty painless, and I figured it out. I prefer the recovery method over odin.
I have one question about the second link, about porting. It says in the first post that if you don't have gb already compiled for your (my)device that guide is useless for you (me). Is that what the first link is for? Compiling specifically for my device? What if my device is not supported at all? Do I just pick a somewhat similar phone, compile, port, make a flashable rom, and put it on the phone and hope it doesn't brick it?
Yep thats what the first link is for. Don't compile and port for a different device, that is a sure way to brick your phone.
Is your device not supported at all? Usually legacy devices are since back then (lol) there weren't a whole ton of Android phones
Sent from my Nexus 4 using xda premium
I don't know if my device is supported or not. I have not got to that part in the guide yet. I will report back if it is or isn't.
Sorry for not getting back earlier, I've been real busy the past week or two.
I finally got ubuntu set up on a computer, and was following the first guide and ran into a few problems.
First, I wasn't able to install all the required packages. If you want to know what ones they are I wrote them down. Not sure how essential they are in the grand scheme, but they weren't available.
Second, I tried to install java and ran into a problem adding the repos for it. The second one, for src, would not work at all. So I went on sun's or oracle's website and downloaded the linux package and installed it. But apparently it didn't work because all I get after trying to lunch are lots of these:
Code:
/bin/bash: java: command not found
Basically anywhere it tries to use java I get those messages. Eventually it gives up and says I have
Code:
version: /bin/bash: java: command not found
and I should have
Code:
version 1.6
Third, after I issue
Code:
source build/envsetup.sh
I see it includes some devices, like htc passion and samsung crespo4g and samsung crespo. Is this normal?
Fourth, When I do lunch I get five options
Code:
1. generic-eng
2. simulator
3. full_passion-userdebug
4. full_crespo4g-userdebug
5. full_crespo-userdebug
Should I just pick generic-eng?
I will be out of town all week for work, and won't have access to the computer I am doing all this on. For the life of me I cannot get unbuntu to install on my laptop. Never did like ubuntu, always favored fedora.
Anywho, thanks for any suggestions.
Hey there remaining Verizon S3 users!
Coming from my favorite device the T959V this has been quite a trip. This device's bootloader is seemingly impossible to unlock on the 4.4.2 NE1 firmware.
I've got a slightly modified Superlite rom rolling with SafeStrap already strapped. And it is great to say the least. Added some initd and utilities. Evie launcher is pretty nice btw- recommend a try :good:
However. I still really want this thing to be unlocked. The T959V has multiple working Fro, GB, ICS, JB, KK, L, M, AND Nougat ROMS. Totally different devices yes but-- even the newer S4-S6 have cracked loaders now.
There has to be a special way to change this things firmware.
Right now I have 2 ideas to throw out to the wind-
1- Would be that there could be a way to trick the device into thinking it is receiving a new update. Maybe somehow with CSC or something. Also I saw a file named authorized.xml and was reading through to find traces of knox. Would unauthorizing knox strings somehow render it useless?
2- I was reading a suggested post about AVB boots and how they can be resigned on devices such as the Google Pixel and allows the newer patches to still install. Including what was described as a forced re-sign method.
--- Could we somehow resign the bootloader on our device so as to gain control of it? Has anybody tried anything like this since around 2015?
I'll gladly talk about all of this more whenever I feel like popping on- and atm I have no web besides this service. :silly: so no DOS updates and no shiny linux for now.
Gladly tell me that it is "impossible" but I'm not asking that. I'm trying to add some ideas to possibly do the impossible.
Edit: This seems to be an interesting lead on emmc cracking this device. It's probably why people in other threads were in search of a "dev" edition.
http://forum.gsmhosting.com/vbb/f777/unlock-samsung-devices-bootloader-emmc-backdoor-2142981/
graycow9 said:
Hey there remaining Verizon S3 users!
Coming from my favorite device the T959V this has been quite a trip. This device's bootloader is seemingly impossible to unlock on the 4.4.2 NE1 firmware.
I've got a slightly modified Superlite rom rolling with SafeStrap already strapped. And it is great to say the least. Added some initd and utilities. Evie launcher is pretty nice btw- recommend a try :good:
However. I still really want this thing to be unlocked. The T959V has multiple working Fro, GB, ICS, JB, KK, L, M, AND Nougat ROMS. Totally different devices yes but-- even the newer S4-S6 have cracked loaders now.
There has to be a special way to change this things firmware.
Right now I have 2 ideas to throw out to the wind-
1- Would be that there could be a way to trick the device into thinking it is receiving a new update. Maybe somehow with CSC or something. Also I saw a file named authorized.xml and was reading through to find traces of knox. Would unauthorizing knox strings somehow render it useless?
2- I was reading a suggested post about AVB boots and how they can be resigned on devices such as the Google Pixel and allows the newer patches to still install. Including what was described as a forced re-sign method.
--- Could we somehow resign the bootloader on our device so as to gain control of it? Has anybody tried anything like this since around 2015?
I'll gladly talk about all of this more whenever I feel like popping on- and atm I have no web besides this service. :silly: so no DOS updates and no shiny linux for now.
Gladly tell me that it is "impossible" but I'm not asking that. I'm trying to add some ideas to possibly do the impossible.
Edit: This seems to be an interesting lead on emmc cracking this device. It's probably why people in other threads were in search of a "dev" edition.
http://forum.gsmhosting.com/vbb/f777/unlock-samsung-devices-bootloader-emmc-backdoor-2142981/
Click to expand...
Click to collapse
I've been around this and many many other forums for years now. If there was an unlock method it would of been found years ago. Devs have long moved on from the old S3. I still have my S3 lying around, bootloader unlocked but I really haven't messed around with it for quite a long time now
And yes the dev edition would of been nice had someone actually had one, it would of of course made it easier to crack the bootloader option maybe. I don't know much about the ins and outs of the device but I know many are permanently locked and will probably never be unlocked.
As far as certain other Samsung devices being unlocked those are far and few between. VZW got smart and started just locking them from the start. This is a huge reason why I left Verizon. The S3 was my last device on big red. I since have had a Nexus 5 and 6 and now a oneplus 3t. I really don't like locked devices and the ability to unlock them and customize them just intrigues me to no end. Good luck however in finding something that may work, but I highly doubt it will ever be cracked
Sent from my OnePlus 3T
Ya I expected your negatude Shapes. Already seen that you have been searching but it isn't just some application you run. It's an unknown exploit that I'm sure exists. There are exploits right now that can be considered viral potentially exploiting my device as we speak. Maybe not granted my semi-precautious take on things.
Quadrooter and dirty cow could be used to exploit the S3 and gain access to a quoted "all" physical memory. So I find it hard to believe that things can't work in our favor.
Being open minded here. After all, this is technically hacking your own device. Which--
Got me thinking the other day, becausr I was setting up my laptop proper- could we run a nix distro and poke through the bootloader's parameters via exploitation tools? Referencing Kali or it's elder BTrack. But I think it is possible and I just haven't gotten around this loop mounting issue.
To be clear, running a distro ON the device. My flat is already running square.
Sent from my SCH-I535 using XDA-Developers Legacy app
Also a purposely separate post- I'm building a ROM for this locked firmware and the goal is to have some specific updated apps and yet trim it nicely so as to save space and RAM it's mostly stock style-wise but it'd be cool to re-theme it. I haven't gotten things deodexed yet- being I haven't gotten my apktools working proper yet.
Is there anybody left to be interested in this? I haven't posted anything I've made before- usually just keep them lying around for emergency flashes.
Sent from my SCH-I535 using XDA-Developers Legacy app
graycow9 said:
Ya I expected your negatude Shapes. Already seen that you have been searching but it isn't just some application you run. It's an unknown exploit that I'm sure exists. There are exploits right now that can be considered viral potentially exploiting my device as we speak. Maybe not granted my semi-precautious take on things.
Quadrooter and dirty cow could be used to exploit the S3 and gain access to a quoted "all" physical memory. So I find it hard to believe that things can't work in our favor.
Being open minded here. After all, this is technically hacking your own device. Which--
Got me thinking the other day, becausr I was setting up my laptop proper- could we run a nix distro and poke through the bootloader's parameters via exploitation tools? Referencing Kali or it's elder BTrack. But I think it is possible and I just haven't gotten around this loop mounting issue.
To be clear, running a distro ON the device. My flat is already running square.
Click to expand...
Click to collapse
I don't think shapes was trying to act negative at all, just stating the obvious. Nobody is going to try to unlock the Verizon S3, it's pretty much a dead end.
The unlock method used on the S5 will most likely work on this phone, but we need a developer CID to rewrite to the emmc as the series chip used on the S3 likely has the same vulnerability. This is what happened on the S5.
If you read some of the other posts (sounds like you have), we looked for an S3 developer edition but had no luck in tracking one down. For one, it's an incredibly old device. Secondly, you'd have to be semi retarded to purchase one as the original unlock method was around before the developer edition was released.
So yes, if you can find a developer S3 this will likely be an unlock method. It tricks the S3 into thinking it's a developer phone and unlocks the bootloader if the method to write it works the same as in the S5.
As for your questions,
1. I think you're underestimating the amount of security that goes into the bootloader itself. If you want to learn a lot about Android security in general, in the Android security discussion section located under general forums, there's tons of info regarding how complex this all is. But basically, in order to send an update patch, it needs to be signed (you can't just fake the signature) and it must agree with the current bootloader. The way the bootloader is written, it simply won't allow a reversion back to earlier versions or it'll abort the boot.
An easier way to think of this is understanding that the changes made are preinstalled before the actual boot. There's no way for us to change this through normal methods as the emmc has to be written to directly. There is no way to do this from download or recovery mode. Wouldn't matter if you flashed it or used and update package, they are essentially the same thing.
So the only way to actually change the bootloader is to write to the emmc directly through use of the JTAG port. This changes the code of the entire bootloader before the boot and the phone will boot up with any version of the S3 bootloader you write.
2. I think I kind of answered that?
Hope it's clear.
BadUsername said:
I don't think shapes was trying to act negative at all, just stating the obvious. Nobody is going to try to unlock the Verizon S3, it's pretty much a dead end.
The unlock method used on the S5 will most likely work on this phone, but we need a developer CID to rewrite to the emmc as the series chip used on the S3 likely has the same vulnerability. This is what happened on the S5.
If you read some of the other posts (sounds like you have), we looked for an S3 developer edition but had no luck in tracking one down. For one, it's an incredibly old device. Secondly, you'd have to be semi retarded to purchase one as the original unlock method was around before the developer edition was released.
So yes, if you can find a developer S3 this will likely be an unlock method. It tricks the S3 into thinking it's a developer phone and unlocks the bootloader if the method to write it works the same as in the S5.
As for your questions,
1. I think you're underestimating the amount of security that goes into the bootloader itself. If you want to learn a lot about Android security in general, in the Android security discussion section located under general forums, there's tons of info regarding how complex this all is. But basically, in order to send an update patch, it needs to be signed (you can't just fake the signature) and it must agree with the current bootloader. The way the bootloader is written, it simply won't allow a reversion back to earlier versions or it'll abort the boot.
An easier way to think of this is understanding that the changes made are preinstalled before the actual boot. There's no way for us to change this through normal methods as the emmc has to be written to directly. There is no way to do this from download or recovery mode. Wouldn't matter if you flashed it or used and update package, they are essentially the same thing.
So the only way to actually change the bootloader is to write to the emmc directly through use of the JTAG port. This changes the code of the entire bootloader before the boot and the phone will boot up with any version of the S3 bootloader you write.
2. I think I kind of answered that?
Hope it's clear.
Click to expand...
Click to collapse
Truthfully after being around the forums for as long as I have I'm really surprised there is any interest in unlocking this device at this point in time. There are just so many other options and unlocked vzw s3s are not that hard to come by.
And I wasn't being negative it's about being realistic. Thanks for sticking up for me brother
Sent from my OnePlus 3T
Are there any updates to this by any chance, I am interested :C
any hope?
Welcome to the NOBLE ROM!
Disclaimer1: Your warranty is now void!
I am not responsible if you brick your phone. or kill your sd card!
I cannot be held responsible for smoke, fire, water, or other natural disasters.
So please READ the entire OP!
Disclaimer2: Always make a backup first!! Flash at your own risk!
Clean install is always recommended, but at minimum make sure you wipe!
ROM FEATURES
- Based on N920VVRU2AOJ3
- Fixed to work over combo firmware..
- Rooted.
- BusyBox.
Installation:
1. Download file and push to sdcard.
2. Reboot to Safestrap recovery.
4. Flash it.
5. Wipe data.
6. Reboot.
Downloads:
Android File Host
Thanks to:
@SuperR. for SuperR's Kitchen
@Chainfire For SuperSU.
@Stericson For BusyBox.
Samsung for the locked bootloader.
me.
Root your device
If you are on Rev 1 or 2 bootloader and you are on 5.1.1.
- Go to http://mobilego.wondershare.com/
- Install it on your PC.
- Press on One-Click Root.
- Follow instruction.
If you are on Rev 3 bootloader
Flash Cobo firmware then folow the previous instructions.
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
I knew there was a way! Thanks for sharing this information. I've been saying it for years, there was a way that did involve safestrap and booting a normal system over the factory binary firmware, I just didn't know where to go next. My hat is off to you, as this can open many doors.
Delgoth said:
I knew there was a way! Thanks for sharing this information. I've been saying it for years, there was a way that did involve safestrap and booting a normal system over the factory binary firmware, I just didn't know where to go next. My hat is off to you, as this can open many doors.
Click to expand...
Click to collapse
Thanks, hope it work over N920A.
afaneh92 said:
Thanks, hope it work over N920A.
Click to expand...
Click to collapse
So is what you had to do was copy "liblptcp.so" from the combination /system/lib folder and paste it into the stock system lib folder?
Did you have to copy "libsigchain.so" from combination to stock as well? All you have to do was put them in the same spot on the stock system as they were in the combination system? I wonder how device specific it is going to be. I'm looking at multiple devices pulling the common denominators.
Where did you did you find "export LD_PRELOAD" exactly?
Please and thanks.
Delgoth said:
So is what you had to do was copy "liblptcp.so" from the combination /system/lib folder and paste it into the stock system lib folder?
Did you have to copy "libsigchain.so" from combination to stock as well? All you have to do was put them in the same spot on the stock system as they were in the combination system? I wonder how device specific it is going to be. I'm looking at multiple devices pulling the common denominators.
Where did you did you find "export LD_PRELOAD" exactly?
Please and thanks.
Click to expand...
Click to collapse
libsigchain.so is there in stock 5.1.1
I think the "export LD_PRELOAD" is in init.rc
Hey, I got safestrap and this ROM flashed. It actually works pretty slick. Is there any hope of further ROM development for safestrap?
Hello. Is it possible to make rom like this, which will work over combo firmware for N920C ?
Myneamc said:
Hello. Is it possible to make rom like this, which will work over combo firmware for N920C ?
Click to expand...
Click to collapse
Why would you want to do that? The c can be fully unlocked and has ROMs up to 7.0 at least
Reverse-anastomosis said:
Hey, I got safestrap and this ROM flashed. It actually works pretty slick. Is there any hope of further ROM development for safestrap?
Click to expand...
Click to collapse
Not sure if you want to flash any other 5.1.1 roms from other note 5 or s6 threads, just push the files mentioned in the third post.
Or give me link to any compatible rom and will test it.
afaneh92 said:
Not sure if you want to flash any other 5.1.1 roms from other note 5 or s6 threads, just push the files mentioned in the third post.
Or give me link to any compatible rom and will test it.
Click to expand...
Click to collapse
Guys it's probably a stupid question and I'm pretty sure it's not possible but figured it can't hurt to double check. My USB port on my N920A is toast, luckily it has wireless charging capabilities but that doesn't help me with adb.. or am I wrong? Is there a way I can use oden via WiFi adb (or any way at all) w out the USB connector?
PS: @Delgoth, I'm sorry I ducked out on you like I did when u were trying to help. I thank you and appreciate and admire you and all the contributions you have made in the attempts to root n920a (even when you didn't own the device anymore) and have pretty much read all your available literature out there about this (which was impressive imo). Haha. Just sayin..
bonzeno85 said:
Guys it's probably a stupid question and I'm pretty sure it's not possible but figured it can't hurt to double check. My USB port on my N920A is toast, luckily it has wireless charging capabilities but that doesn't help me with adb.. or am I wrong? Is there a way I can use oden via WiFi adb (or any way at all) w out the USB connector?
PS: @Delgoth, I'm sorry I ducked out on you like I did when u were trying to help. I thank you and appreciate and admire you and all the contributions you have made in the attempts to root n920a (even when you didn't own the device anymore) and have pretty much read all your available literature out there about this (which was impressive imo). Haha. Just sayin..
Click to expand...
Click to collapse
I think no. If you are rooted use flashfire or fix your usb port.
bonzeno85 said:
Guys it's probably a stupid question and I'm pretty sure it's not possible but figured it can't hurt to double check. My USB port on my N920A is toast, luckily it has wireless charging capabilities but that doesn't help me with adb.. or am I wrong? Is there a way I can use oden via WiFi adb (or any way at all) w out the USB connector?
PS: @Delgoth, I'm sorry I ducked out on you like I did when u were trying to help. I thank you and appreciate and admire you and all the contributions you have made in the attempts to root n920a (even when you didn't own the device anymore) and have pretty much read all your available literature out there about this (which was impressive imo). Haha. Just sayin..
Click to expand...
Click to collapse
Yeah Flashfire would work well, or Safestrap would be the best option really. But I just had the USB issue with my Note8 last night actually.
Are you sure it doesn't work, or is it intermittent? "USB DEVICE NOT RECOGNIZED" because of a bad device descriptor? What happened to me was the tongue/pin in the device port was slight bent, but plugging in the cord slowly and in the direction that would straighten out the pin made the ODIN Connection work again.
In my case it wasn't the PC port, or the cable (it was still kinda beat up though), or my drivers. I just need to plug the cord in a certain way. I was in the same boat as you last night trying to flash my N950U.
What I explained fixed my problem.
P.S. EDIT: I'm still trying to flesh out those two threads. But I haven't gotten it written well enough to post yet. I'm trying to have more done before I post this time haha. I'm learning more now, but haven't quite polished the words enough yet to reorganize the Main Posts. Because I feel like with the GHR Console, we might have enough root on 6.0.1 even to use WiFi ADB through Android Studio or something.
The Great Thing about the console is, it still works on 5.1 too, and on 5.1 we do have full root. So, the console technically has even more power, that's why we needed Safestrap. Realistically using a rooted 5.1 build on Rev 4 should still be exploitable and better able to debug improvements to The Console. Having Root Access gives you the details specifically why the Console couldn't carry out the command. So we could tweak the code for 6.0.1 operations based on the results from 5.1
The methods used on the Note 7 and Note 8 are very very similar to what we'd need on the Note 5 variants. Unless we can port this method here to the N920A Firmware. The same kind of System Root because we cannot patch the boot.img
P.S.S: I've seen the line he refers to before. But I was on a Revision 3 Combo BL/CP Build using the revision 1 OGG AP/CSC build later on. I've seen the reference to LD_PRELOAD. I've only ever looked at the Rev 4 and 5 firmware from the PC OS. My device never went past revision 3 bl's on the N920A. The N920V's never even made it as far as AT&T did. IDK why either.
@Delgoth, do you still have a note 5? Are you still interested in the device? I have a n920v that I have been playing with. I just bought stuff to try to get an sboot UART console. I have no idea what I will do when/if I get there. I just can't find that anyone has tried it on the note5. Thoughts?
Reverse-anastomosis said:
@Delgoth, do you still have a note 5? Are you still interested in the device? I have a n920v that I have been playing with. I just bought stuff to try to get an sboot UART console. I have no idea what I will do when/if I get there. I just can't find that anyone has tried it on the note5. Thoughts?
Click to expand...
Click to collapse
REALLY!? Please talk to me when you get that hardware. I mean yes, I'm still highly interested in the Exynos7420 board. It's my favorite piece of hardware to come out of Samsung still.
I will help in any way I can. Just hit me up.
I've read about UART connectivity on that platform. It might be a little difficult but I got some schematics still I think that should still be, at the least, partially applicable.
I did a lot of tests on the board a few years back and had more than one device with that platform. Realistically it's what I know the most.
I don't have the device anymore but I've been more and more wanting to get a used one in decent working condition. I still have my data & knowledge. Hit me up.
Delgoth said:
REALLY!? Please talk to me when you get that hardware. I mean yes, I'm still highly interested in the Exynos7420 board. It's my favorite piece of hardware to come out of Samsung still.
I will help in any way I can. Just hit me up.
I've read about UART connectivity on that platform. It might be a little difficult but I got some schematics still I think that should still be, at the least, partially applicable.
I did a lot of tests on the board a few years back and had more than one device with that platform. Realistically it's what I know the most.
I don't have the device anymore but I've been more and more wanting to get a used one in decent working condition. I still have my data & knowledge. Hit me up.
Click to expand...
Click to collapse
OK! I built my UART jig tonight. It seems to be functional. I get some output when I connect in forced upload mode. I am still waiting on the resistor. There are so many modes available for the s7 I decided to get a variable resistor and see what we can get in to. I could not find any documentation of anyone exploring UART on these devices. I have read a lot of stuff, but nothing specific to the note 5. I have an n920V and a g925v. I plan on trying 620k ohm resistor to get the UART console, and just see what is going on in there. I read this article, and scoured the net for part 2, and it seems that it doesn't exist....hhhmmmm. If you have any info specific to UART on this platform I'd love it. Otherwise I am just going to see what happens. I am totally over my head here, but the devices were free and I am curious. I am not a programmer, just an android enthusiast. To be honest, I wouldn't probably even know if I find something exploitable. I just didn't see any discussion about UART when these devices were hot, so I figure it is worth exploring. Seeing the rediscovery of an open console on the s7 gave me hope.
Reverse-anastomosis said:
OK! I built my UART jig tonight. It seems to be functional. I get some output when I connect in forced upload mode. I am still waiting on the resistor. There are so many modes available for the s7 I decided to get a variable resistor and see what we can get in to. I could not find any documentation of anyone exploring UART on these devices. I have read a lot of stuff, but nothing specific to the note 5. I have an n920V and a g925v. I plan on trying 620k ohm resistor to get the UART console, and just see what is going on in there. I read this article, and scoured the net for part 2, and it seems that it doesn't exist....hhhmmmm. If you have any info specific to UART on this platform I'd love it. Otherwise I am just going to see what happens. I am totally over my head here, but the devices were free and I am curious. I am not a programmer, just an android enthusiast. To be honest, I wouldn't probably even know if I find something exploitable. I just didn't see any discussion about UART when these devices were hot, so I figure it is worth exploring. Seeing the rediscovery of an open console on the s7 gave me hope.
Click to expand...
Click to collapse
Most of what I've read applied to the "F" variant of the S6. Having specific resistance values is a big key, as different resistances allows different communications. That's why the Anyway Jig does what it does, it has variable resistances. I will see about going back to some old bookmarks if I can find them then, I didn't expect it to be so soon haha.
People were trying to say before that they disabled UART comms on the Exynos7420 chip at the hardware level. But I don't think they really did all the way. Most people are weirded out that the Exynos7420 still has the QC 9008 emergency mode still because of their modems. The S6 line uses QC modems that I've read were installed to the board first before Samsung applied the rest of the firmware.
But those devices wouldn't be able to boot to 9008 mode if there was not QC hardware I believe.
The S6, S6 Edge, and Note 5 variants all use the same base chipset and each variant tends to use its own modem chip. It wasn't until the S7 that they started using more universal firmware. But as far as the G925 and N920 goes, they should have different modems for each carrier basically. But the US S7 devices used QC SoC's completely. They didn't use Exynos Processors for the US models like they did with the S6 line.
But mind you, the Exynos7420 saw some of the highest number of exploits in one year than almost all years previous together. Something like almost 700 issues by the time the dirtycow craze was over. It was a huge spike.
The biggest hurdle for the G925v is going to be its SELinux policy. Even project Zero stated that Verizon did do a decent job at setting that policy up. It still wasn't perfect, just required a very tailored approach.
We will have to get more familiar with AT commands for sure. Remember the Radio group has a lot power to it. There should be some documentation on the G925F floating around unless someone got it taken down. When I first started posting files and such related to the S6 Edge there were a few people that reported my G925v folder in Google drive and got a few of my things deleted.
So let me look into it again and we will talk some more this weekend. At one point I did have the schematics for the G925F. That should help if I can find that, as the Note 5 and the S6 Edge used the same code base compared to the S6 flat.
Delgoth said:
Yeah Flashfire would work well, or Safestrap would be the best option really. But I just had the USB issue with my Note8 last night actually.
Are you sure it doesn't work, or is it intermittent? "USB DEVICE NOT RECOGNIZED" because of a bad device descriptor? What happened to me was the tongue/pin in the device port was slight bent, but plugging in the cord slowly and in the direction that would straighten out the pin made the ODIN Connection work again.
In my case it wasn't the PC port, or the cable (it was still kinda beat up though), or my drivers. I just need to plug the cord in a certain way. I was in the same boat as you last night trying to flash my N950U.
What I explained fixed my problem.
P.S. EDIT: I'm still trying to flesh out those two threads. But I haven't gotten it written well enough to post yet. I'm trying to have more done before I post this time haha. I'm learning more now, but haven't quite polished the words enough yet to reorganize the Main Posts. Because I feel like with the GHR Console, we might have enough root on 6.0.1 even to use WiFi ADB through Android Studio or something.
The Great Thing about the console is, it still works on 5.1 too, and on 5.1 we do have full root. So, the console technically has even more power, that's why we needed Safestrap. Realistically using a rooted 5.1 build on Rev 4 should still be exploitable and better able to debug improvements to The Console. Having Root Access gives you the details specifically why the Console couldn't carry out the command. So we could tweak the code for 6.0.1 operations based on the results from 5.1
The methods used on the Note 7 and Note 8 are very very similar to what we'd need on the Note 5 variants. Unless we can port this method here to the N920A Firmware. The same kind of System Root because we cannot patch the boot.img
P.S.S: I've seen the line he refers to before. But I was on a Revision 3 Combo BL/CP Build using the revision 1 OGG AP/CSC build later on. I've seen the reference to LD_PRELOAD. I've only ever looked at the Rev 4 and 5 firmware from the PC OS. My device never went past revision 3 bl's on the N920A. The N920V's never even made it as far as AT&T did. IDK why either.
Click to expand...
Click to collapse
This very thing happened on my note 5 n920a. i was stuck out, no adb or mtp all week. USB not recognized, Bad device descriptor, after flashing the safestrap. Odin picking up my device was my only choice. so i flashed back to the rev 4 MM. I tried diff PC's along with diff OS's and diff cords. I just got it to pick up adm and mtp in linux literally just now as i was reading through this. I been creeping around looking for rev 4 stuff. this is actually my first post lmao. But for real, good work guys, i admire whats going on here. Im totally ok to guinea pig my note 5 btw. its what ive been doing the passed couple weeks on free time.
Delgoth said:
Most of what I've read applied to the "F" variant of the S6. Having specific resistance values is a big key, as different resistances allows different communications. That's why the Anyway Jig does what it does, it has variable resistances. I will see about going back to some old bookmarks if I can find them then, I didn't expect it to be so soon haha.
Click to expand...
Click to collapse
Ok, so parts have been a pain for my jig-finally got it up and running. at 619/620K ohm this is what I get for output. I do not know a whole lot about mincom, or serial communication in general. When I have some more time I will read through it, and see what my next step should be. If you have any input based on what you see here let me know. I tried finding resistance values based on the MUIC driver(max77833) as outlined here but I can't find the values. I can find all of the different modes, but not the values associated with them. I'll keep posting what I find, and thanks for your input.