Related
hello!
does anyone can help ?
after trying to upgreade radio rom , it respring/reload and stock on this screen
I have no idea how can I help stand up my phone on foot
This message was deleted by its author
if you look at the picture, it is actually unlocked. there is a picture of an open lock there. anyways... go into recovery, wipe data(factory reset) the phone, then reupdate the rom.
I find this a tad bit amusing.
Gimpeh said:
I find this a tad bit amusing.
Click to expand...
Click to collapse
lol, i do to! but, sometimes we have to have a little patience. we all were noobs once(except i dont remember being this much a noob )
it is strange becouse i can not run Superboot,root file on it
when I was trying to type using cammand line "instal-superboot-windows.bat" it did nothing
then I was try to upgreade radio rom and it locked
i am beginer
check out this link.... http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Nexus_One_Firmware_to_CyanogenMod
I hosted another screen in first post
This message was deleted by its author
youre in fastboot and it shows that you already unlocked the bootloader. just flash amon ra recovery v1.5.3 then whichever rom you want. be aware that you might also have to flash the google apps add-on with some roms.
there is a thread here on xda for beginers. i suggest you start posting there. this is a developement section. this thread will also probably be closed shortly.
nowy57 said:
it is strange becouse i can not run Superboot,root file on it
when I was trying to type using cammand line "instal-superboot-windows.bat" it did nothing
then I was try to upgreade radio rom and it locked
i am beginer
Click to expand...
Click to collapse
Pretty sure you just need to run the .bat file from Windows and it automatically unlocks the bootloader and roots the phone. Correct me if I'm wrong on the last part of my sentence, but I know you can't flash a bat file on your phone.
simms22 said:
lol, i do to! but, sometimes we have to have a little patience. we all were noobs once(except i dont remember being this much a noob )
Click to expand...
Click to collapse
lmao... thats because some of us did research and studied everything that was needed before doing it, so if there was an issue it was serious
LOL i never rooted an android, my nexus is my first android. im not thinking rooting. but i glanced at the tutorials before and even I know that screen shot means you have a unlocked bootloader
uansari1 said:
Pretty sure you just need to run the .bat file from Windows and it automatically unlocks the bootloader and roots the phone. Correct me if I'm wrong on the last part of my sentence, but I know you can't flash a bat file on your phone.
Click to expand...
Click to collapse
exactly
when I clicked on "instal-superboot-windows.bat" black screen shows on second and do nothing on my phone ..
maktucali said:
LOL i never rooted an android, my nexus is my first android. im not thinking rooting. but i glanced at the tutorials before and even I know that screen shot means you have a unlocked bootloader
Click to expand...
Click to collapse
if u have SDK and drivers setup you dont have to be rooted to do screenshots in DDMS
Thought maybe by now someone would make a workable flashable zip to flash basically stock vibrant firmware with the nand fix (the real method, not with 130 mb limit). If it is out there I apologize, but i'm almost sure I haven't seen it on here. And I'm referring to flashing via clockwork recovery. I've come from a G1 and really never had to do anything but download and hit the "flash any zip" option from recovery, and its a method i'm most comfortable with. Thanks for any direction you might provide.
This ROM doesn't use the NAND, it uses an EXT2/EXT3 partition on your SD card.
http://forum.xda-developers.com/showthread.php?t=743506
javacody said:
This ROM doesn't use the NAND, it uses an EXT2/EXT3 partition on your SD card.
http://forum.xda-developers.com/showthread.php?t=743506
Click to expand...
Click to collapse
How is it working for you?
joe.kerwin said:
Thought maybe by now someone would make a workable flashable zip to flash basically stock vibrant firmware with the nand fix (the real method, not with 130 mb limit). If it is out there I apologize, but i'm almost sure I haven't seen it on here. And I'm referring to flashing via clockwork recovery. I've come from a G1 and really never had to do anything but download and hit the "flash any zip" option from recovery, and its a method i'm most comfortable with. Thanks for any direction you might provide.
Click to expand...
Click to collapse
..since there is no way to magically make nand bigger than 128 megs (without soldering new chips on) I suspect "the real method" is the apps2sd method..
Disconn3ct said:
..since there is no way to magically make nand bigger than 128 megs (without soldering new chips on) I suspect "the real method" is the apps2sd method..
Click to expand...
Click to collapse
Both Methods require ROOT*
*Method 1 limits the space of app data, which can possibly cause issues*
*Method 2 requires writing a new Kernel, which comes with it's own possible issues*
I'm just getting irritated. I have a 1ghz phone with lag/gps problems. It seems whenever I need to whip out my phone for something quick those are always the times it screws up too, so i get 10x more frustrated but I didn't want this to become a phone i'm constantly flashing and its already happening because it wasn't made right in the first place. Anyone with lag fix able to post a backup they might have made? I'm just looking for solutions, and easier ways to get there.
Plus maybe i'm just biased but creating an EXT? I thought those days were over when I cashed in my G1. I just dont understand how using an ext on your SD can be faster than storing the data internally.
joe.kerwin said:
Plus maybe i'm just biased but creating an EXT? I thought those days were over when I cashed in my G1. I just dont understand how using an ext on your SD can be faster than storing the data internally.
Click to expand...
Click to collapse
Read the linked thread above and you'll learn. It's pretty simple.
MTC44 said:
Read the linked thread above and you'll learn. It's pretty simple.
Click to expand...
Click to collapse
So I need to create an EXT partition first before flashing the above mentioned ROM? What are the recommended settings if any for size? And I partition through clockwork orrrr? I know there's probably an answer for all these questions but between people using UK firmware/unfamiliar terms I don't want to jump into anything without missing a step.
Just go to the userinit thread and apply it... No need to flash a whole rom... Just partition your sd and flash the zip...
I ran jf rom on my g1 for like 2 months before a rom that dramatically changed anything...
We were so gracious for just that... Be patient this is new hardware.. Look at the international development section... We have made a lot of progress in 3 weeks..
Sent from my SGH-T959 using XDA App
Why waste time asking questions when you can answer them yourself?
All~G1 said:
Why waste time asking questions when you can answer them yourself?
Click to expand...
Click to collapse
I dunno, why waste time posting that question when you can simply read on if you have no advice? The strange things we do. And yes it is new hardware, hence why I ask these questions before I dive into something I'm unfamiliar with. Id rather ask questions and wait than waste hours trying to get my phone to turn on again after jumping the gun. My question that still stands is with the partitioning. With my g1, it was cut and dry on Amon Ra, did it right in recovery, so is there anything like that for us vibrant owners? I've never used ADB or anything of that nature, so I come from a download and flash world, so excuse my unfamiliarity and please dont take it as me complaining that it's not easy enough to do.
Look how long it took for the g1 to get where it is at now? Eventually it will come. You think your the only who would like to have a lag free rom? If you would have done some reading on the development side, you would have noticed there were a couple of fixes and also some progress. Ask questions on those threads over there as far as the speed and if it will suit your needs.
joe.kerwin said:
I dunno, why waste time posting that question when you can simply read on if you have no advice? The strange things we do. And yes it is new hardware, hence why I ask these questions before I dive into something I'm unfamiliar with. Id rather ask questions and wait than waste hours trying to get my phone to turn on again after jumping the gun. My question that still stands is with the partitioning. With my g1, it was cut and dry on Amon Ra, did it right in recovery, so is there anything like that for us vibrant owners? I've never used ADB or anything of that nature, so I come from a download and flash world, so excuse my unfamiliarity and please dont take it as me complaining that it's not easy enough to do.
Click to expand...
Click to collapse
Learn ADB if you want to hack a Vibrant. Without a keyboard, we can't do shells in recovery without it. There are tutorials, so I won't repeat them. Logcat is also very useful and low level devs won't be able to help you if you run into problems and can't provide a log.
Partitioning. DO NOT USE CLOCKWORK/ROM MANAGER. Right now it will partition the phone's INTERNAL flash, which is cause boot loops and you will have to Odin flash the phone back to stock to make it boot again. Use a computer and a card reader with Paragon, Gpartd, etc.. Or a G1 with Amon RA, or adb shell into clockwork recovery and use fdisk.
EXT size, doesn't really matter. You don't need a ton. I use 1GB and it's using about 180MB. For EXT type, use ext3 with the stock kernel, or, if you install JACs kernel, ext4 is faster and more reliable.
Note that partitioning on the phone in recovery via fdisk won't format the partitions. Flash my e2fsprogs ZIP file in JACs kernel thread for the versions that support ext4.
Before you start messing with this stuff, download the stock Odin flash files from the thread in development. If you mess something up, you can get back to stock. You should also get ADB and the Samsung drivers installed. Then get Titanium backup and make backups. When you install Clockwork, do a nandroid as well. Backups are GOOD.
Keep in mind, we are in the early stages of learning how to hack on these phones. We won't get to the level the G1 is at for a while. Go read the threads in the G1 dev forum from a year ago and you will see a lot of recommendations for learning adb, partitioning manually, and all the other stuff we are doing here on the Vibrant. It's a process. If you want flash and forget, you need to wait a while still. We're working on it, but we aren't there yet. This is new hardware and a whole new way of doing things.
ttabbal said:
Learn ADB if you want to hack a Vibrant. Without a keyboard, we can't do shells in recovery without it. There are tutorials, so I won't repeat them. Logcat is also very useful and low level devs won't be able to help you if you run into problems and can't provide a log.
Partitioning. DO NOT USE CLOCKWORK/ROM MANAGER. Right now it will partition the phone's INTERNAL flash, which is cause boot loops and you will have to Odin flash the phone back to stock to make it boot again. Use a computer and a card reader with Paragon, Gpartd, etc.. Or a G1 with Amon RA, or adb shell into clockwork recovery and use fdisk.
EXT size, doesn't really matter. You don't need a ton. I use 1GB and it's using about 180MB. For EXT type, use ext3 with the stock kernel, or, if you install JACs kernel, ext4 is faster and more reliable.
Note that partitioning on the phone in recovery via fdisk won't format the partitions. Flash my e2fsprogs ZIP file in JACs kernel thread for the versions that support ext4.
Before you start messing with this stuff, download the stock Odin flash files from the thread in development. If you mess something up, you can get back to stock. You should also get ADB and the Samsung drivers installed. Then get Titanium backup and make backups. When you install Clockwork, do a nandroid as well. Backups are GOOD.
Keep in mind, we are in the early stages of learning how to hack on these phones. We won't get to the level the G1 is at for a while. Go read the threads in the G1 dev forum from a year ago and you will see a lot of recommendations for learning adb, partitioning manually, and all the other stuff we are doing here on the Vibrant. It's a process. If you want flash and forget, you need to wait a while still. We're working on it, but we aren't there yet. This is new hardware and a whole new way of doing things.
Click to expand...
Click to collapse
Thank you very much. Now this is a respectable response. i'll find some time next week to learn this ADB stuff.
joe.kerwin said:
I dunno, why waste time posting that question when you can simply read on if you have no advice? The strange things we do. And yes it is new hardware, hence why I ask these questions before I dive into something I'm unfamiliar with. Id rather ask questions and wait than waste hours trying to get my phone to turn on again after jumping the gun. My question that still stands is with the partitioning. With my g1, it was cut and dry on Amon Ra, did it right in recovery, so is there anything like that for us vibrant owners? I've never used ADB or anything of that nature, so I come from a download and flash world, so excuse my unfamiliarity and please dont take it as me complaining that it's not easy enough to do.
Click to expand...
Click to collapse
No one is asking you to take a chance on bricking your phone hard or soft. I was implying more that you could learn or develop your knowledge of what others have placed in front of you. Everything takes time, rather "wasting" it on a procedure you don't understand, "waste" it on learning it, then do it. You have everything you want to know right in front of you. If you searched and read hard enough you'd now be able to "answer the questions yourself" to where you understand it.
Oh and just to let you know there is a flashable "lag-free" Rom in the Dev forum. While its bare, it is still doing wonders on this phone!
@ttabbal- You're the man!!! Don't know how you do it... lol
could someone that doesn't mind walking me through the correct partitioning method and getting this rom to work at it's max.. send me a private message so we can talk through gtalk tonight?. Im a fast learner, just purchased an 8gb class 4 sd card. I want to be safe.
Pm sent
Sent from my SGH-T959 using XDA App
All~G1 said:
@ttabbal- You're the man!!! Don't know how you do it... lol
Click to expand...
Click to collapse
I'm glad my stuff has been useful to the community. I'm a little shocked to see it integrated into a ROM and a kernel so far.
As for how I do it, what's the quote about standing on the shoulders of giants? I learned a ton reading posts and scripts from Cyanogen, Firerat, Eugene, and many others. Combine that with running Linux boxes for a few years, and you pick up enough to contribute a bit. Most of what I'm doing is adapting G1 hacks to work on the Vibrant, but I'm glad people like them.
Now if we could just get Samsung to give us decent GPS and compass drivers, maybe a tasty Froyo?
joe.kerwin said:
How is it working for you?
Click to expand...
Click to collapse
Haven't tried it yet, my friend.
I'm using the patch mentioned above.
I am also using ADW instead of TouchWiz, which seems to help quite a bit.
junkdruggler said:
Pm sent
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
How beneficial is it to do this? Should I wait for better ROMs? I am nervous about rooting my device as many are defective after a week or two and need shipped back.
I have the Samsung Fascinate and I recently rooted it to get all the wonderful benefits that come with rooting.
I downloaded the leaked Froyo update, renamed it "update.zip" and put it in my sd card folder in order to update.
I then turned off my phone and pushed the power button plus the volume up and down until I got to the boot screen. I kept getting an error saying it couldn't verify the package (or something along those lines) and then it sent me to a screen with the triangle, exclamation point and the little droid guy.
I also tried using Rom Manager but the same thing happened.
I hear you are supposed to use Odin, but I am running on a mac and Odin is a windows application.
Please help me, I'm desperate to get the Froyo update on my device.
Thanks in advance.
Yikes u didn't do any research at all did you?? U can't use Odin on Mac....and u need it. Do u even have cwm? Probably not since u didn't Odin. U need to Odin cwm...Make a backup...Odin eb01 modem...flash rom. Update.zip is not correct...u don't rename .zip roms...you flash them via cwm. Not trying to bash u....but you are way off...and getting help via forums will b tough.
You need to go to irc and be polite and find some help there. Someone should hopefully be able to help you...I will b on eventually.
sent from my vanilla voodoo fascinate
I did my research but if I'm not literate with how or what a CWM is or how to use it, that doesn't mean I didn't do my research.
But are you telling me I can't install the update without a windows computer?
I have access to one where I am but I would rather know all the steps before I get on someone else's computer and start trying to figure it out there.
I looked through all 50 or so pages of the Froyo leaked thread and I saw a few people who understood all these things, but if I don't understand and there isn't a tutorial it makes it harder for me to accomplish my goal.
Can your phone boot up?
Someone varify my directions.
This might work if u can get into download mode. U need to find all the links urself since I'm on tapatalk.
First off...find a pc. Without one you can't do anything. Put ur eb01 rom on sdcard for later. Instal the 32 bit or 64 bit Samsung drivers depending on ur pc. For many..its the 32 bit. Then get Odin. U will need to find a link to cwm...if I'm not mistaking there is one on like the 2nd or 3rd page in android development section...will say updated cwmq for dj05 or dl09 or something like that. Find directions of how to use Odin...but simply place the cwm.tar file in the pda section on Odin...then click start. When that's done...u should make a backup...however...u may not b able to boot up because of what u have already done. U may try odining the eb01 modem. Once u have that done...hold up down and power to get I to your new updated cwm. From there click instal zip from sdcard...and flash ur eb01 rom of choice....wipe wipe wipe...reboot system.
Again...this may not work since I'm not possitive what u already did to ur phone by not doing your research. Like I already said...be polite and head over to irc. .someone will have more time than I do to fix ur phone.
sent from my vanilla voodoo fascinate
You obviously didn't research. There is an eb01 walkthrough on fascinate development section...impossible to miss. If ur incompetent at following step by step directions u should not be Modding your phone. Seek help and knowledge before doing anything...u don't want a 600 dollar paper clip do you?
sent from my vanilla voodoo fascinate
kyfredrickson said:
You obviously didn't research. There is an eb01 walkthrough on fascinate development section...impossible to miss. If ur incompetent at following step by step directions u should not be Modding your phone. Seek help and knowledge before doing anything...u don't want a 600 dollar paper clip do you?
sent from my vanilla voodoo fascinate
Click to expand...
Click to collapse
How would you use it as a paper clip? A paper weight I see, but not a paper clip?!?!
TheFake said:
I did my research but if I'm not literate with how or what a CWM is or how to use it, that doesn't mean I didn't do my research.
But are you telling me I can't install the update without a windows computer?
I have access to one where I am but I would rather know all the steps before I get on someone else's computer and start trying to figure it out there.
I looked through all 50 or so pages of the Froyo leaked thread and I saw a few people who understood all these things, but if I don't understand and there isn't a tutorial it makes it harder for me to accomplish my goal.
Click to expand...
Click to collapse
Not to be a ****...but the first thing you learn when reading is how to flash the modem using ODIN...so, yeah....
Since you've f'd up the phone already. Download the restore to stock files and odin. Go to someone with a PC and follow the restore directions to the T. DO NOT FALTER.
kyfredrickson said:
You obviously didn't research. There is an eb01 walkthrough on fascinate development section...impossible to miss. If ur incompetent at following step by step directions u should not be Modding your phone. Seek help and knowledge before doing anything...u don't want a 600 dollar paper clip do you?
sent from my vanilla voodoo fascinate
Click to expand...
Click to collapse
No, but I also don't see the need for the disrespectful way you are treating someone looking for help.
Not everyone out there is as "smart" as you may be with modding but that's what this forum is for. Questions and answers, not smartass replies that don't help at all.
I appreciate the other posters response because at least he gave me information with no attitude. If you want to help someone, help them, don't demean them and offer a little advice.
jenisiz said:
Not to be a ****...but the first thing you learn when reading is how to flash the modem using ODIN...so, yeah....
Since you've f'd up the phone already. Download the restore to stock files and odin. Go to someone with a PC and follow the restore directions to the T. DO NOT FALTER.
Click to expand...
Click to collapse
The phone is working fine, if not better than before.
TheFake said:
The phone is working fine, if not better than before.
Click to expand...
Click to collapse
Honestly, you haven't done anything to your phone yet, so it shouldn't be running any differently than it was before.
There is a way to push CWM using ADB and Terminal on a Mac, but you would still need Odin to flash the modem, so might as well do everything that way. Download this Odin package from Android Central, and flash that using the PDA box in Odin. After that, you can flash a different 2.2 ROM or theme if you like
The only thing I am having trouble with is how to "flash" something.
TheFake said:
The only thing I am having trouble with is how to "flash" something.
Click to expand...
Click to collapse
Go to the Eb01 modem thread and read it. They will tell you how to "flash". You download the modem, plug in your phone, select PDA in ODIN and hit write or whatever...
It's as easy as reading and searching,
http://forum.xda-developers.com/showthread.php?t=948679
Not searching for things will get you flamed, ignored and banned (If not reading the rules). The reason I suggested you flash back to complete stock is because until you know what flashing is, difference between a ROM and a Radio...you are in dangerous territory of bricking your phone.
Guys, I'm also new to this flashing thing, but I've used Odin before and have read all the steps in the EB01 thread. My question is: can I install EB01 on top of stock, unmodded EA28 (which is the latest Eclair from Verizon) without wiping my data? All sets of instructions I've read include wiping, wiping, wiping... But since the new ROM is supposedly signed with the same Samsung/Verizon key as my current ROM, why shouldn't I be able to just install it on top, without wiping my data?
Or is it that because the guy who posted the ROM actually modified it, it's no longer signed with the Samsung or Verizon key?
I searched, but didn't find. I think the answer to this may be relevant to the original poster of this thread too, that's why I'm posting here.
thetodor said:
Guys, I'm also new to this flashing thing, but I've used Odin before and have read all the steps in the EB01 thread. My question is: can I install EB01 on top of stock, unmodded EA28 (which is the latest Eclair from Verizon) without wiping my data? All sets of instructions I've read include wiping, wiping, wiping... But since the new ROM is supposedly signed with the same Samsung/Verizon key as my current ROM, why shouldn't I be able to just install it on top, without wiping my data?
Or is it that because the guy who posted the ROM actually modified it, it's no longer signed with the Samsung or Verizon key?
I searched, but didn't find. I think the answer to this may be relevant to the original poster of this thread too, that's why I'm posting here.
Click to expand...
Click to collapse
It's always recommended to wipe. Those that don't are typically those who end up complaining about bad battery life, force close loops and utter suckageness...now flashing let's say super clean 2.0 to 2.2...that's fine bypassing the wipe, but imho that's the only exception.
thetodor said:
Guys, I'm also new to this flashing thing, but I've used Odin before and have read all the steps in the EB01 thread. My question is: can I install EB01 on top of stock, unmodded EA28 (which is the latest Eclair from Verizon) without wiping my data? All sets of instructions I've read include wiping, wiping, wiping... But since the new ROM is supposedly signed with the same Samsung/Verizon key as my current ROM, why shouldn't I be able to just install it on top, without wiping my data?
Or is it that because the guy who posted the ROM actually modified it, it's no longer signed with the Samsung or Verizon key?
I searched, but didn't find. I think the answer to this may be relevant to the original poster of this thread too, that's why I'm posting here.
Click to expand...
Click to collapse
You can install without wiping (saying from experience) as long as you dont mind problems later. I had plenty of force close problems and widget problems when I didnt wipe data.
Most ROM here are modified, to help protect the person who leaked it.
Interesting. Do we know the cause of those problems? How come no such problems exist when you update OTA with a similar official build?
I'm a developer and it seems weird to me that if you're starting with a stock ROM and upgrading to another stock ROM, apps will have issues. Or are the issues due to the fact that the newer ROM is still buggy (and that's probably why they haven't officially released it yet)?
Also, it doesn't hurt to try, right? And if I do get problems, THEN I can just do a simple wipe and start off clean. But if I don't have huge problems, I don't have to go through the trouble of restoring all my apps and settings, logging into everything again, etc.
it's not hard to restore apps/data, use titanium backup.
go ahead and try it without wiping, just do a full nandroid backup first. then if it sucks or you get funny errors you can revert really easily. I'd wipe with a major change like this, but if you're determined to try it there's really no big downside. just back up!
I ran EB01 over the weekend, didn't like a couple of things and was back up and running on DL09 in no time when I decided to switch back.
Its recommended to wipe but I've seen it a lot where u OK not wiping... u can try without and it u get bootloop just do a wipe. Like posted...titanium backup is ur bff when I mod.
Also about the post about me being rude.. I gave u the info u need...just telling you to research. U said u did, and I pointed out u didn't. If your not going to take the time to learn what ur doing...then expect help ASAP...expect ppl to b a bit rude. Ppl are welcome to help...but if u do something dumb without research...expect people to tell you.
Glad u got it working ok
sent from my vanilla voodoo fascinate
Just FYI everyone, I was able to to install Froyo without wiping and everything works fine. (except that my home screen shortcuts and maybe even some of my settings got reset... which was one of the things I was trying to avoid... but whatever.). The only issue I've run into so far is that Google Maps hangs for many seconds every once in a while. But I reset its internal cache and it's better now. All other apps are working fine.
umm "TheFake" is obviously a troll
nobody is that stupid, and his screen name gives it away
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Click to expand...
Click to collapse
Well that i a good start. Good to see some reading before the jump in feet first.
corruptsmurf said:
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
Click to expand...
Click to collapse
That's why we're here.
corruptsmurf said:
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
Click to expand...
Click to collapse
Edited: added Later
ADB is a commander center/protocol (if you will) that allows you to control your phone via a PC/Mac/Linux. You can push files which would be taking the file and "pushing" to the phone. Or "pulling" files from the phone and putting them on the computer. It's simply as it states, pushing and pulling the files.
To see what a Kernel is read This.
A ROM is the phones physical Operating system. Similar to what Window, Mac or Linux world be.
corruptsmurf said:
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Click to expand...
Click to collapse
Before you can flash Clockwork Mod you need to root your phone and turn s=off. For one of the methods, - before you can start you need to set up the ADB (Android Debug Bridge). See my signature for the quickest and most painless way to get that set up. You will also need VISIONary.apk. A quick Google Search will find it for you. Link
corruptsmurf said:
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
If you want a 2.3 based ROM you will need to flash Recovery image 3.0.0.6, link can be found in my signature, and hit up the development section to read reviews on different ROMs. I personally like the plain AOSP look so that leave Cyanogen(mod). But i know TeamRoyal has put together some newer ROMs that i haven't tampered with yet.
I do everything on my phone through CWM (clockworkmod) or terminal emulator, so there's no need for a PC, unless to download the files and transfer them to my SDcard, as I don't understand adb. Anyways, I'm gonna explain this very short and sweet cuz I was once in your shoes, and remember how much I had to read to understand something That could've been explained so simply.
Think of it this way. You're building the software version of a car. Now, if the whole car is the ROM, then the engine is what would be the kernel. And flashing would then be another word for installing , Now, a toyota with a ferrari engine, would be a custom ROM. While a toyota with a ferrari engine and BMW insignias all over it would then be a custom themed ROM.
**Remember, you can never install a car on something, but you can always install something in a car**
Ex. You can never flash a ROM on a kernel, but you can always flash a kernel on a ROM.
Anyways, first off, you will need CWM recovery to flash. Get it from the market. In the app itself, flash (this is the "flash" in the app) recovery 3.0.0.6. This will flash (this flash is not in the app) anything; any ROM, any kernel, etc. as long as its a FLASHABLE ZIP.
To boot into the recovery (the place you do flashing), hold both volume down and power buttons down as you either turn on or restart your phone. The screen you see is the bootloader. Choose recovery using the volume buttons, and use the power button to select it.
Going to flash a new ROM? Do a factory reset (in recovery), wipe cache (in recovery), and wipe delvik cache (this is in advance in recovery). Then install zip. Its pretty straight forward from there.
Going to flash an updated ROM, skip factory reset (as this deletes all data on your phone) and do the rest.
After you've flashed the ROM, you can now flash the kernel.
Note that, kernels are ROM specific. Read what kinds of ROM's the kernel is for before you flash it.
There, easy as pie, yeah? Hope that helped.
I recommend cyanogenmod 7 (Gingerbread based ROM) with faux's kernel (Gingerbread based kernel)
Sent from my HTC Glacier using XDA App
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
Neidlinger's got your back.
1. Glad you're reading before doing. What a welcome change of pace!
2. Flashing is the process of installing new software. We "flash" it to the phone's memory.
3. ADB is using a computer to control the phone via command-prompt from DOS. Push is a command which sends a file from your computer to your phone. Do a search, there are lots of good guides on ADB. TrueBlueDrew made one just recently that I highly recommend.
Here's Drew's thread. Don't forget to hit his thanks button! - http://forum.xda-developers.com/showthread.php?t=928370
4. Start with Clockwork Recovery and a nandroid backup. That's good practice. CWR2 is compatible with Froyo (2.2) ROMs. CWR3 is compatible with Gingerbread (2.3) ROMs. CWR 3.0.0.6 is compatible with BOTH. Very convenient.
5. I say start with CM7. It's extremely stable, even though it's still in development. A ROM is a complete OS replacement for the phone. ROMs contain kernels, which control the most basic hardware, such as processor. If you flash a custom kernel on your stock ROM, you can overclock it more. You can also flash custom kernels on top of custom ROMs for different battery life, clock speed, etc.
To be honest I don't even bother with custom kernels since this phone is so damn fast out of the box I really don't see the point.
QUICK TIPS FOR CM7 - On your first boot, let it sit for 5-10 mins before setting up. There are background processes running and interrupting can harm stability. BEFORE you sign into google for the first time, after it's finished sitting, reboot. This will clear out any wifi glitches and give you smooth sailing.
Have fun!
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Uchennadi said:
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This is pretty much spot on. The developers have included kernels that they feel make the OS preform at it's peak. and most of them will allow for overclocking. However on some of them you may need to use a program called "setCPU" to adjust the frequencies. Cyanogen(mod) will have this built into the ROM natively. However most of the veterans will not promote running your phone in an over clocked status 100% of the time. most of us leave the phone at 1Ghz or slower. There are physical reasons, ie the constant expansion and contract of the chip isn't good for the mother board.
If i were you i'd stick with the Stock Kernel and leave it running as it. That way the developer can adjust their ROM, if you use an 3rd party kernel they aren't familiar with the coding so it's not going to act correct.
I'm not putting down what the kernel coders do, they do an awesome job. but for a n3wb i'd leave well enough alone.
***DISCLAIMER***
If done incorrectly, this can soft brick your device. I take no responsibility for this, and if you're unfamiliar with rooting android I suggest reading up before attempting. There are threads to fix your tablet if this goes sideways, but if this doesn't work I personally can't promise I can help you.
I used this method two days ago, and would like to thank jerbear294 for providing me with the information. I didn't come up with this, I just want to help others looking for root.
Hello guys
First, apologies if this is a redundant thread. All the root methods I've seen in individual topics seem outdated, and I just wanted to make this quick guide to help people from having to scan through pages of information to learn how to root these things. This method works on firmware WW_V12.10.1.33_20150917, which is the current release as of this post.
Lets get to it!
Download
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
(Navigate to page 1, for some reason it links to the last page)
Place it on your computer and unzip.
And the latest supersu .zip 2.46
https://download.chainfire.eu/696/supersu/
Which will be on your tablet.
Install the temp recovery to your computer, connect the tablet, make sure you enable adb (USB Debugging) on it in developer mode (Settings → about → software version → tap build number 7 times for developer mode). Once connected, run the exe in the .zip from the temp recovery.
Choose: TWRP HDPI portrait, T4.
Your device will boot into twrp recovery. Now navigate to the supersu.zip on your tablet, and install, and you should be good to go . Good luck, and happy rooting!
Thanks to everyone who developed these tools (especially Social_Design_Concepts), and XDA for providing a medium to relate them.
To run Xposed, go to http://forum.xda-developers.com/showthread.php?t=3034811
Choose 'xposed-v80-sdk21-x86', this is currently the only version I've had success with. Happy hunting folks!
404 page not found on the first link?
ThunderThighs said:
404 page not found on the first link?
Click to expand...
Click to collapse
Link fixed, thanks and my apologies
thank you a lot! you saved me a lot of browsing! :good:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
seamo123 said:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
Click to expand...
Click to collapse
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Opensystem said:
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Click to expand...
Click to collapse
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to create a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Then I placed all the files from the nandroid zip inside that (second) folder. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
I wonder should I have taken the recovery log from my own nandroid and replaced jerbear's recovery log with it? I'm starting to confuse myself at this point I think..
seamo123 said:
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to unzip the file into a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
Click to expand...
Click to collapse
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Opensystem said:
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Click to expand...
Click to collapse
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Yes the general for the memo 176 has a special working xposed, make sure you use that one. I'm a bit busy, but I'll link when I can glad you got it rooted
Joe_Bangles said:
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
Click to expand...
Click to collapse
Glad to help, xda is where it's at for community
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Delichi said:
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Click to expand...
Click to collapse
Hurray! Glad it worked out for you
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Hey sorry for the late response, work got crazy on me. I edited the original post to now include how to set up Xposed, for you or anyone else interested. Confirmed working on both .33 and .36
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
dareas said:
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
Click to expand...
Click to collapse
It's got less battery drain here, performance seems better too but that could just be a placebo
Opensystem said:
It's got less battery drain here, performance seems better too but that could just be a placebo
Click to expand...
Click to collapse
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
dareas said:
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
Click to expand...
Click to collapse
I'm not sure, we should be because of art runtime but I feel like our version is bootlegged to a degree
unable to mount /data, internal storage 0MB. How can I load the zip file?
It's probably because FDE. I used a external SD card instead