General Root issue and fix - Google Pixel 7 Pro

Just to let ppl know the old way to flash did not work for me if you use the command at fastboot menu fastboot flash init_boot path/to/magisk_patched.img and it didn't work, you have to specify the partition your flashing to, you can see this from the fastboot menu if your on partition "a" then the command is fastboot flash init_boot_a path/to/magisk_patched.img and switch "a" for "b" if your on b. hope this helps

You don't need to specify the partition slot, because it always goes to the "Active slot".
*Fastboot flash init_boot init_boot.img*

ekin_strops said:
You don't need to specify the partition slot, because it always goes to the "Active slot".
*Fastboot flash init_boot init_boot.img*
Click to expand...
Click to collapse
This.
Also, it's easier to opened CMD in the directory you have the patched image so you don't have to type out the path to it.

I've found that a lot of people who find it necessary to specify which slot to flash (fastboot flash init_boot_a... or fastboot flash init_boot_b...) use Windows PowerShell instead of classic good ol' CMD. I'm unsure why PowerShell has little issues like this (I've seen some people are required to include the "./" in the command line or it doesn't work), but that's why I exclusively use CMD & suggest using that instead when giving advice...You don't really run into any issues using that (although, sometimes it's tricky to try and explain someone on how to run it with Administrator privileges...)

simplepinoi177 said:
(although, sometimes it's tricky to try and explain someone on how to run it with Administrator privileges...)
Click to expand...
Click to collapse
It's not that difficult.
Hit the Windows key to bring up the Start Menu, type cmd, right-click command prompt, run as administrator. Even my grandma could follow those instructions.
Honestly if people don't know how to do something that basic, they really shouldn't be messing with their phones in the first place.

EtherealRemnant said:
It's not that difficult.
Hit the Windows key to bring up the Start Menu, type cmd, right-click command prompt, run as administrator. Even my grandma could follow those instructions.
Honestly if people don't know how to do something that basic, they really shouldn't be messing with their phones in the first place.
Click to expand...
Click to collapse
Good advice...I'm a bit old school and normally advise using the Run command...I forget Windows after 7 implemented that way of doing it...
And then sometimes in certain cases using the Run command doesn't give the option to run as administrator...
But I've not found many cases (if any) that things went badly because it wasn't an elevated command prompt, but I just think it's good practice just to eliminate a possible hitch right off the bat before working on numerous solutions only to find out it was something like that...
And it's always surprising how many novice users are able to achieve advance goals without knowing the basics -- for better or worse, it probably just compels and instills confidence to be messing with their phones/devices more...

simplepinoi177 said:
Good advice...I'm a bit old school and normally advise using the Run command...I forget Windows after 7 implemented that way of doing it...
And then sometimes in certain cases using the Run command doesn't give the option to run as administrator...
But I've not found many cases (if any) that things went badly because it wasn't an elevated command prompt, but I just think it's good practice just to eliminate a possible hitch right off the bat before working on numerous solutions only to find out it was something like that...
And it's always surprising how many novice users are able to achieve advance goals without knowing the basics -- for better or worse, it probably just compels and instills confidence to be messing with their phones/devices more...
Click to expand...
Click to collapse
I used to work tech support so I got in the habit of finding the absolute easiest way to tell people to do things. Windows key shortcuts are a godsend for tech calls. They're obscure enough that if you get a techie on the line who would normally be offended by you holding their hand through things they might actually thank you for learning something new but easy enough that someone who can barely turn on a computer can key peck their way through it lol.
I also specifically like using this shortcut because it's so easy to run in admin mode. It's how I personally launch basically everything on my computer that I haven't pinned to the taskbar.

simplepinoi177 said:
But I've not found many cases (if any) that things went badly because it wasn't an elevated command prompt, but I just think it's good practice just to eliminate a possible hitch right off the bat before working on numerous solutions only to find out it was something like that...
Click to expand...
Click to collapse
Yeah, I've never had to use elevated command prompt when flashing.
I just put whatever I'm flashing in the Platform Tools folder, type "cmd" in the address bar of the Platform Tools folder to open command prompt from that folder and away I go.

Curiousn00b said:
Also, it's easier to opened CMD in the directory you have the patched image so you don't have to type out the path to it.
Click to expand...
Click to collapse
You can also just copy and paste the path - which is presumably what OP was doing.

NippleSauce said:
You can also just copy and paste the path - which is presumably what OP was doing.
Click to expand...
Click to collapse
That too. I'm so use to installing ADB/fastboot into my system's path that I forgot if you have it in one location, you need to do paths.
I be having one open in my downloads, the desktop, and a folder where I keep stuff when I mess with my phone's, lol.

ekin_strops said:
You don't need to specify the partition slot, because it always goes to the "Active slot".
*Fastboot flash init_boot init_boot.img*
Click to expand...
Click to collapse
i wrote this post because when i did not specify a partition it failed. its literally in my post that the normal way to do it failed for me. I used cmd to not powereshell.

simplepinoi177 said:
I've found that a lot of people who find it necessary to specify which slot to flash (fastboot flash init_boot_a... or fastboot flash init_boot_b...) use Windows PowerShell instead of classic good ol' CMD. I'm unsure why PowerShell has little issues like this (I've seen some people are required to include the "./" in the command line or it doesn't work), but that's why I exclusively use CMD & suggest using that instead when giving advice...You don't really run into any issues using that (although, sometimes it's tricky to try and explain someone on how to run it with Administrator privileges...)
Click to expand...
Click to collapse
i used cmd and not specifying a partition made it fail.

EtherealRemnant said:
It's not that difficult.
Hit the Windows key to bring up the Start Menu, type cmd, right-click command prompt, run as administrator. Even my grandma could follow those instructions.
Honestly if people don't know how to do something that basic, they really shouldn't be messing with their phones in the first place.
Click to expand...
Click to collapse
What are you talking bout? I did exactly that and it FAILED for me unless i specified a partition. The only thing i did a lil funky is i didnt open cmd in the folder the patched image was in so i had to drag and drop file to add path.

simplepinoi177 said:
Good advice...I'm a bit old school and normally advise using the Run command...I forget Windows after 7 implemented that way of doing it...
And then sometimes in certain cases using the Run command doesn't give the option to run as administrator...
But I've not found many cases (if any) that things went badly because it wasn't an elevated command prompt, but I just think it's good practice just to eliminate a possible hitch right off the bat before working on numerous solutions only to find out it was something like that...
And it's always surprising how many novice users are able to achieve advance goals without knowing the basics -- for better or worse, it probably just compels and instills confidence to be messing with their phones/devices more...
Click to expand...
Click to collapse
novice? yes. and this post is for other novices who want full control of their phones. im a specialized mechanic that rebuilds transmissions for a living, not a techie but i love to dabble. i dont put others down because they cant install an overdrive sprag or a rear case bearing with race, or intermediate and overdrive servos cause im not fffing 12 years old. and please explain what im doing wrong then cause everything you guys say is basic i did. I installed adb and fastboot drivers i patched the init image, opened admin cmd and tryed to flash and it didnt work until i specified a partition. the only thing i did a lil diff is i didnt open cmd in the folder the patched img was in i had to drag and drop,,, its jus sad how ppl can type like there some tough sh*t but if this was face to face youd have nothing to say, in prison we called you guys window warriors lol.

Linxy420 said:
novice? yes. and this post is for other novices who want full control of their phones. im a specialized mechanic that rebuilds transmissions for a living, not a techie but i love to dabble. i dont put others down because they cant install an overdrive sprag or a rear case bearing with race, or intermediate and overdrive servos cause im not fffing 12 years old. and please explain what im doing wrong then cause everything you guys say is basic i did. I installed adb and fastboot drivers i patched the init image, opened admin cmd and tryed to flash and it didnt work until i specified a partition. the only thing i did a lil diff is i didnt open cmd in the folder the patched img was in i had to drag and drop,,, its jus sad how ppl can type like there some tough sh*t but if this was face to face youd have nothing to say, in prison we called you guys window warriors lol.
Click to expand...
Click to collapse
whoa whoa whoa... someone's pretty touchy...
how was I putting others down? I said I found it surprising that some "novice" users skip some steps to achieve more advanced stuff without understanding basics and can get themselves into trouble and/or not be able to properly backtrack because they skipped through the basics -- it was simply based off of a ironic situation of how if someone couldn't even run an elevated cmd yet they are trying to mod their device. Never did I say you, or anyone specifically, were these novice users. It was a general comment on that type of situation.
How am I typing "like they're some tough sh*t"? And I find it hypocritical that you make assumptions about me "talking down" and generalizing you as a novice, when you make assumptions of me that I just "type like they're some tough sh*t" but face to face I'd have nothing to say and generalizing me as "window warriors". Interesting that you're so insulted, yet sling the same type of remarks...
Linxy420 said:
... please explain what im doing wrong then ...
Click to expand...
Click to collapse
and in an attempt to posit an idea that might've been wrong, I did mention that, in many cases I found, a lot of people were required to do what you did because they were using powershell instead of cmd and powershell is iffy in its execution, so it might've been that...
I know in the end you clarified that you use an elevated cmd, not powershell, and still had to specify what slot to apply it to. Sometimes it just goes that way, I guess. None of us are Google software engineers, so we can only guess and probably can't give you a complete straight answer. Most of us don't need to specify the slot; applying it to the active slot usually is enough.
So, I hope you consider all this and re-evaluate some things....

Linxy420 said:
What are you talking bout? I did exactly that and it FAILED for me unless i specified a partition. The only thing i did a lil funky is i didnt open cmd in the folder the patched image was in so i had to drag and drop file to add path.
Click to expand...
Click to collapse
If you go back and re-read what I wrote, I wasn't talking about you, just giving @simplepinoi177 an easy way to tell people how to run command prompt and other things in administrator mode...

Strange, I've never had to specify the partition....
Two thoughts: first make sure you use the latest platform tools as available from Google and second it may be an idea to use --slot=all as parameter for flashing, this way you can make sure all slots are flashed......

simplepinoi177 said:
whoa whoa whoa... someone's pretty touchy...
how was I putting others down? I said I found it surprising that some "novice" users skip some steps to achieve more advanced stuff without understanding basics and can get themselves into trouble and/or not be able to properly backtrack because they skipped through the basics. Never did I say you, or anyone specifically, were these novice users. It was a general comment on that type of situation.
How am am I typing "like they're some tough sh*t"? And I find it hypocritical that you make assumptions about me "talking down" and generalizing you as a novice, when you make assumptions of me that I just "type like they're some tough sh*t" but face to face I'd have nothing to say and generalizing me as "window warriors". Interesting that you're so insulted, yet sling the same remarks...
and in an attempt to posit an idea that might've been wrong, I did mention that, in many cases I found, a lot of people were required to do what you did because they were using powershell instead of cmd...
I know in the end you clarified that you use an elevated cmd, not powershell, and still had to specify what slot to apply it to. Sometimes it just goes that way, I guess. None of us are Google software engineers, so we can only guess and probably can't give you a complete straight answer. Most of us don't need to specify the slot; applying it to the active slot usually is enough.
So, there is all that....
Click to expand...
Click to collapse
I posted of what i had to do to get my pixel to gain root access. your answer made it sound like only advanced users should ever have root access to their phones and a "novice" shouldn't even try, you might not have meant it but you made it sound like that and yea it ticked me off a lil but i do apologize, I might have taken it a lil far rereading my post. I try to help when I can even with my meager tech savvy and if i can help a couple people having the same issue as me im quite happy. and im sry but saying being a novice and getting it done jus instills confidence for them to mess up later is a put down, i dont know bout others but i do know my limits i toyed with many phones in my past and even bricked a couple and through a bunch of trial and error got em unbricked.

simplepinoi177 said:
And it's always surprising how many novice users are able to achieve advance goals without knowing the basics -- for better or worse, it probably just compels and instills confidence to be messing with their phones/devices more...
Click to expand...
Click to collapse
Linxy420 said:
... and im sry but saying being a novice and getting it done jus instills confidence for them to mess up later is a put down, i dont know bout others but i do know my limits i toyed with many phones in my past and even bricked a couple and through a bunch of trial and error got em unbricked.
Click to expand...
Click to collapse
I was going to leave this all well enough alone, but I wanted to give some clarification and leave a word of warning/caution for any novice users (*not anyone in particular*) that just might be perusing this, and since this is a thread about "root issues" I hope its considered still be on topic -- although being an I.T. tech I have numerous other examples, the particular situation that came to mind in my original quoted remark is on novice users who nonchalantly attempt to manually relock their bootloader on Pixels (I'm sure experts here who have assisted others in the subject are already groaning and can sense where I'm going with this...). It's pretty much always the case where there are seemingly countless users who have found themselves in this situation where they skipped through past the basics (merely unticking the OEM unlock button, unlocking the bootloader), modified partitions (whether just to root or to apply custom ROM), and because they achieved this they had become overconfident without understanding how running the unlock bootloader command is severely a lot less riskier than the locking bootloader command (without proper preparations and considerations), how to flash a Full Factory image, or why it's important to keep (or even just have remain) the OEM unlock button unticked until the end; and ultimately, hard-brick their device where no amount of trial and error will get it unbricked in the end.
As in this case, speaking on novice users who were successfully able to go straight to modifying partitions and/or applying a custom ROM (advanced goals) and had become overconfident that they didn't properly research the basics (flashing Full Factory images) or heed warnings of re-locking bootloaders and ended up hard-bricking their devices -- basically "being a novice and getting it done jus instills confidence for them to mess up later" -- is not, and was not meant to be, a "put down", but merely stating what happens from time to time. And, I did state that it is "for better or worse" that it "compels and instills confidence to be messing with their phones/devices more" -- "better" if it leads to careful experience, "worse" if it leads to overconfidence and brazen irreparable but avoidable damage. But, I'm sure, that all experienced users, both experts and not, had been led to their success due to them messing with their devices, so it's not to say one shouldn't do it and me trying to gatekeep, it's more me saying; sometimes you have to crawl before you walk before you run, it always surprises me when some people run after just learning to crawl (let alone walk), and people who do that should brace themselves for faceplanting -- but it should not be considered putting them down saying this.
In the end, don't skip the basics, thoroughly research, it is not a put down when speaking on those who do not do these things but attempt advanced scenarios anyways, and do not relock the bootloader on Pixels (unless very particular, exceptional circumstances).

Related

Today I made my first Mistake (fixed it) but would like some information.

I am old school DOS user, so I don't know linux commands very well.
It is my understanding that the command line is similar in function but with different commands i.e. C\: copy file blah.exe to C:\here\.
Can the Recovery command line be used as such to move around on the sdcard in recovery mode using the same method, and if so, is there a list of linux commands I can familiarize myself with?
I would like to add this to all current/future G1 Hackers.
I learned a valuable mistake today. After doing lots of reading to correct it (thanx to the help of people who know what they are doing). I would like to make this one suggestion:
Get a cheap USB Card reader. Essentially you can do everything you need in windows w/o using a command line.
http://cgi.ebay.com/Cheap-MicroSD-Micro-SD-USB-2.0-Card-Reader---SHIP-$2.50_W0QQitemZ380101445086QQcmdZViewItem
It is a life saver if you makea mistake.
Brutal-Force said:
I am old school DOS user, so I don't know linux commands very well.
It is my understanding that the command line is similar in function but with different commands i.e. C\: copy file blah.exe to C:\here\.
Can the Recovery command line be used as such to move around on the sdcard in recovery mode using the same method, and if so, is there a list of linux commands I can familiarize myself with?
Click to expand...
Click to collapse
yes it can .. however .. the way android is setup i found everything has to be mounted from scratch .. so you wouldn't have /sdcard .. it would be blank until the mmcblk0p1 was mounted .. likewise /system would be blank etc until the mtdblock3 was mounted
So basically...
Yes it can, but not with out a lot of typing. I.e. for every command I would have to do a mount?
The linux commands I found online were difficult, because while they are comparable to the dos ones, they cannot be used verbatim. Also other commands are used while connecting to the device, which do not show up when you do a google search they way I was. I was wondering why when I did a remount from the command line, I could get to the /sdcard but then I tried to use a ls or a l command to list the files and nothing shows. I will (for my own sake) ask more questions and try to push/pull rather than do it simply by windows.
This was the first thing I tried, but it helped very little.
http://www.pixelbeat.org/cmdline.html
Thank you for your input.
I think the usb micro card reader is the best solution. Heres what I do
*8 gig sdhc micro card (everyday card)
*kingston microsd reader with 1 gig micro sd card loaded with the latest JF update.zip
Now I can just pop the 1gb card into my phone and flash the JF if I brick. And since the reader is attached to my keys, I always have the recovery with me even if Im not near a computer.
You really should learn the commands before screwing with things. The linux terminal is infinitely more powerful than dos. The side effect of this is that it is equally more complex. I suggest that you install some linux distro on your desktop computer (or an old junker you have shoved into a corner in the basement), and learn it real well. With just a little experience, you'll surely want to wipe that microshaft turd off of everything you own.
I have had ubuntu installed on my computer before
I can say that ubuntu definitely has is benefits.
A long time ago I was really into computer stuff, constantly tweaking, installing, trying out new stuff. Today I can safely say I use my computer for primarily internet browsing, googleing, information and such. That being said, it really doesn't matter which OS I actually have installed. Ubuntu, my understanding is that it simply uses less resources and of course is open source. Applications are free and there is always someone willing to lend you a hand.
Other than that, I can't see where Ubuntu was really a necessary must for me up until today. Realistically I fall back into the category of "just need it to do one thing". No doubt that Linux has its place, and If I wasn't so out of date and lazy, I would take up the coding myself.
Thanx for the Suggestion Xavier
After I read your post I was like Duhhh. Considering I have the original 1 gig that came with the phone, I did what you suggested. I have pretty much a boot disk/back up for the phone in case everything goes to pot, and I can carry it in my wallet just in case I am doing something while away from a USB port. After all, I shouldnt be tied to a usb port anyways, thats why I bought my G1 .

break down apps to sd for me....

I have downloaded the apps to sd program and when I get to the step where I have to use the terminal emulator it dosent work.
when I try to use command: "mkdir /system/sd/app" it says its a read only system
then when I try "mount data" it says device or resource busy.
what am I doing wrong and can someone break it down barney style for me?
The breakdown is this: if you didn't already understand the whole apps-to-sd process based on the stickies and long threads out there, it is probably more trouble than it is worth for you.
The fact is, if you look at the last 20 pages of this subforum, apps-to-sd is just a can of worms for a lot of people.
I am fine inputing code and all of that its just that most of the things they talk about are eiter you already know what it is or your SOL. I really dont want to spend the hours learning and tracking down what each line of code means.
on another note how come every time I run this apps to sd and it partitions my sd card my phone wont boot past the g1 splash screen?
sw20matt said:
I am fine inputing code and all of that its just that most of the things they talk about are eiter you already know what it is or your SOL. I really dont want to spend the hours learning and tracking down what each line of code means.
Click to expand...
Click to collapse
A2SD is an alpha product. It's not so much that you have to spend hours reading, but that simply the existing documentation on A2SD is spread wide and sometimes contradicts each other. Not even the pioneers of A2SD can guarantee it will work on all given rooted dreams.
A lot of people on this board (erroneously) assume that just because someone released a zip file that it has been fully tested for all cases and will work out-of-the-box. All these releases carry implicit "USE AT YOUR OWN RISK" warnings.
on another note how come every time I run this apps to sd and it partitions my sd card my phone wont boot past the g1 splash screen?
Click to expand...
Click to collapse
Like I pointed out above, I can't help you diagnose it unless you give more details about what your exact case is (what you moved, what type of A2SD, did you use an a2sd automatic setup program?).

Rooted my EVO and now I'm lost....

I don't know anything about this programming. I am a complete idiot when it comes to this stuff. I rooted the phone because I wanted to be have full control over it's capabilities going forward, but I didn't realize I'd need to use these programs on my computer to do it. I thought things would be available through simple downloads.
Anyway, I've spent the last several hours attempting to become at least functional so that I could install another OS on my phone. I have no idea what rebooting in recovery or clearing caches or any of this is. I know it's probably simple, remedial stuff to practically everyone reading this but I am clueless.
I'm sure I could learn and was willing to do so. I downloaded SDK and Java update and Eclipse and painstakingly followed installation instructions several times from several sources. And I can't get the adb to function. My computer won't recognize the path. I'm pretty certain that I've installed everything completely and updated the path accurately, etc. I go through cmd, type in adb and it says it's not recognized as an internal or external command, operable program or batch file.
I've gotten to the point where I just want to set my phone back to the way it was when I bought it 2 days ago. I want to go back to being a simple lemming and just oblivious to this whole world. I don't belong over here. I'm out of my league and I know it.
Now the problem I have is that it's supposedly easy to "unroot" the phone. You just have to download 3 things and "flash" them. I don't even know what the **** that means though. And if it invloves using adb (or abd...I don't even know that), then I'm screwed.
I'm really frustrated guys. I'm tired. I should have never attempted this, but it all sounded so easy and awesome. Now I just want my normal, restricted phone back. Can anyone help me?
OK. I got the phone back to it's original state. I know some of you are probably shaking your heads at the decision, but it makes me feel a lot more comfortable.
Maybe if I could figure out how to access adb, it would be different but I just felt handcuffed without it. Well there eventually be ROMs that are more easily installed like re-installing the original was? Will there be ways to just steam it through HTC Sync?
i think one reason why u didnt manage to get adb working is because u didnt set up the environmental variables for java. Go into command prompt and type java. See what that returns.
SupremeBeaver said:
i think one reason why u didnt manage to get adb working is because u didnt set up the environmental variables for java. Go into command prompt and type java. See what that returns.
Click to expand...
Click to collapse
Thank you for the response. That command produced a long string of information. Is there something in that I should be looking for, or was this just a test to see if it would be recognized?
it was a test to see if java was working fine. By string of commands do u mean like this:
http://img682.imageshack.us/img682/8440/48798806.jpg
Otherwise the problem may be that you havent specified the environmental variables for the android sdk.
Right click on My Computer and go to properties, under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Now what u need to do is add the location of ur sdk to the end of the "Variable Value".
So if u put the adroid sdk folder in the root of ur C drive, then u would add this line
;C:\Android\tools
to the end of the Variable Value line. This depends on where u put the skd folder though. Whats important here is u dont replace whats already there! Just add the line to the end, even the ";" symbol.
Hope this helps. let me know how it goes
Thank you again for the response. Yes, that looks to be the same screen information that appears when I run java in command.
I have the SDK in a folder named AndroidSDK on the root of my C drive. I have added the line ";C:\AndroidSDK\tools" to the end of the path. One thing I just realized is that when I double click the AndroidSDK folder, the next screen contains a single folder named "android-sdk-windows". When I double click that folder I see subfolders for add-ons, platforms, tools, SDK readme, and SDK setup. I'm wondering now if I need to include that "android-sdk-windows" in the path line in order for it to find adb in the tools.
I would really like to solve this adb issue. I still want to learn enough about this stuff to root the phone again and feel comfortable working with it. I'm completely obsessed with this right now. It's driving me mad.
in that case the line you should add would be
;C:\AndroidSDK\android-sdk-windows\tools
I can't believe it was that simple!
Actually I can believe it. Thank you so much for your help. Sorry if I came off as a bit of a drama queen in the OP, but I have just spent about 6 hours messing with this if you include the rooting.
Ok. I think I'm going to give it all another shot. Thanks again. I may be back to this thread again if I end up running into another dead end though.
Glad it worked
Dont worry about it, i can understand ur frustration because this is by no means straight forward.
Hope u enjoy playing with ur soon to be rooted EVO
If you have time to answer another question, I went through the OTA Simple Root process again and everything appears to have worked. But I don't think that finishes the phone in root. I don't have a Superuser app, for instance.
Isn't there something else I need to do? (Install a custom rom maybe?)
If so, how do I accomplish it in the least technical way possible?
Im not too sure with that actually. I dont have an EVO (or any android phone for that matter). But yeah i think the superuser app should appear without flashing a custom rom.
I think you might want to create a thread in the EVO section where im sure many EVO owners will help u out with this. Or maybe a mod could move this thread?
JelloB said:
If you have time to answer another question, I went through the OTA Simple Root process again and everything appears to have worked. But I don't think that finishes the phone in root. I don't have a Superuser app, for instance.
Isn't there something else I need to do? (Install a custom rom maybe?)
If so, how do I accomplish it in the least technical way possible?
Click to expand...
Click to collapse
Disclaimer - I have not used the simple root method.
That being said I have helped a few people with this and it seems that the last img file that it flashes does not have super user access. You need to flash a custom ROM in order to fix that. I will post a link to the thread that I was helping in and that should answer some of your questions on how to do that.
Hope that helps
http://forum.xda-developers.com/showthread.php?t=722194
Sent via the Sprint HTC EVO
Just wanted to update this. I finally was able to put it all together. I was previously unaware of the "extras" tab on the OTASimpleRoot program. Just didn't read the instructions in post well enough, which is the story of my life....but I digress.
Anyway, I was able to root the phone again, flash recovery and now I have even gotten to the point where I understand a little bit how to install custom roms. In fact, I just installed my first using Baked Snacks latest update. I've also downloaded ROM manager so in the future I should I have no trouble at all (even though I'm pretty comfortable doing it the "long" way now).
Thanks again to both of the guys above who took the time to read and respond to a complete newbies questions.
I now that I have successfully loaded a custom ROM onto my EVO that it is full root and I don't have to worry about that anymore. I don't have a "superuser" app that I can tell, but I do have a "dev tools" app and folders which I don't think were on the phone before.
Alright, I do have a superuser permissions app. When I click it nothing happens though. I don't know if that's normal or not.
The issue I'm having now is that when the phone was rooted it took it back to the 1.17.651.1 software version. I went through the steps in the "How to start over: Fully rooted stock 1.47..." thread but the phone doesn't appear to be reading the PC36IMG.zip file. It doesn't ask if I want to update it. I tried it a couple times and then skipped to the second file in that thread (su-2.1-e-unsecure-signed.zip) and got a message about ....something "build". Went ahead with the install but I don't see anything different. Still says I'm on software 1.17.....
Wireless tethering app doesn't work for me, which was the impetus to dig further into this....deeper down the rabbit hole.
Ok. This will be my last update but I'm pretty excited because something has happened to correct issues I was having.
I thought I would go through the root process from start to see if I could get the 1.47 software. Once I got to the second step and did the factory reset, upon reboot it took me to the recovery screen which was different and made me a little nervous. I found the cue to install BakedSnack again from the sdcard and chose that function.
This time things were different than before. For instance, upon booting the phone I got a cool screen saver with streaming, trippy colors instead of the 4G and Sprint crystaline logos. I don't remember this happening the first time I installed this ROM. Once I got into the phone I noticed some minor changes I didn't notice the first time. The music widget wasn't on the second page, nor the nascar or football crap either. I think they were there before. Then I went into apps and saw ROM manager installed and superuser and Wifi tethering. Went straight to wifi tethering and low and behold it works like a charm.
Last but least, I went to check the software and I am now running 1.47. I don't know why it's on their now. This is all still a little mysterious to me. I could swear this Baked ROM is a little different than the first time I had it on the phone. Maybe that's my imigination. Maybe the factory wipe did something. I don't know but I'm very happy now.
Congrats
SupremeBeaver said:
Congrats
Click to expand...
Click to collapse
Thanks again man!
What a difference 24 hours can make. At this point last night I was ready to pull my hair out in frustration. By noon today I had unrooted the phone and re-installed the most recent OTA software update and was ready to just stick with that. Now I have re-rooted, somehow managed to get the updated software back on the phone, and have installed and am running an incredibly awesome custom ROM.
I love my new phone. Thanks again to both of you guys who offered help. I think I'm going to be good from here on.

[Q] is there likely to ever be a 'one click root' ?

OK.... Ive been an HTC Desire owner for a year and regularly flash ROMs but ive managed to be able to distance myself from the whole adb 'thing' thanks to Unrevoked (ie a 1-click-root).
Being an owner of a Transformer now Id love to be able to root the beast and carry on with Flashing and tweaking but the whole rooting thing now scares me a little
ive done a fair amount of googling and I believe it requires install of software and drivers but most guides are for Android 2.1/2.2 etc and I know 3.0 is a different ballgame ..... Im also running windows 7 64 bit which seems to make things more complex. I fo have a dual boot to ubuntu but ive only really been using that to play around - im no Linux expert !!
Anyone know if there is likely to be a one-click-root developed for Honeycomb ?
adb - or the initial setup of adb - scares me
ADB setup isn't that hard, there are loads of guides on the internet already. I'm running W7 x64 and I didn't really run into any problems getting ADB up and running.
ADB isnt as hard as it sounds, its worth it to learn since there so much you can do with it. its just a matter of knowing what code to use and most of the time its posted and you just have to copy and paste. i prefer to use ADB sometimes instead to scripts that way you know exactly whats going on.
but im sure there will be easier ways to root if you just wait, there's still a huge shortage and im sure lots of people that want to develop for the TF are still waiting to get their hands on one.
ADB isn't all that daunting and besides, learning new things is enjoyable My hesitancy to root rests in some of the issues that folks are having. My screen wouldn't wake up once, I had to reboot to get my TF going again. I'm waiting now
to make sure the unit is solid and stable running the stock configuration. I don't want to root only to have the thing decide to become a paperweight 3 days later.
Using ADB should not be beyond anyone who has rooted and installed bits before. I think it is the lack of GUI and reassuring responses and prompts that people miss and are used to.
if you are following this guide and ADB is responding well, you can even cut and paste the commands into your command window (on PC you can) and this helps prevents missing spaces and syntax problems.
Bottom line though - if you are not comfortable doing it, don't risk it.
lol.... OK.... ive had a go ..... and i think it has worked
didnt help that my 'installing archives' in the Android SDK Manager is now hanging due to the washing machine in the garage catching fire and blowing the fuses therefore causing my connection to the web to break halfway through downloading
... and now im having problems downloading blob5 as it says im running concurrent downloads ....
Its always the unexpected stuff that causes problems
I love the smell of an electrical washing machine fire in the morning
Yep, had problem getting blob5 too. Didn't like my IP address? Got it from work instead - Don't tell the 'IT Police' (Although I am sure their logs will grass me up)
can anyone provide an alternative link to blob5? won't let me download
You could try resetting your ADSL modem to obtain a new IP address - that might work. As I mentioned above the site decided I had abused my download limit (at my first attempt!) and blocked my current IP.
Assuming you are not on a static address?
I'm on static
wilbur-force said:
can anyone provide an alternative link to blob5? won't let me download
Click to expand...
Click to collapse
Try this http://dl.dropbox.com/u/3387763/CWM_BLOB_V5
cheers
that's done the trick
You're welcome.
I've just ordered myself a Transformer and will no doubt want to root it after a while, if there any particular ROM that's considered the 'best so far'?
from what I gather most of the roms are still very early days. at this point I'm after root for nandroid and some of the root apps.
ok... very noob question
the root guide says to copy the blob/files to your 'adb directory' ... which directory is that ? the android-sdk directory ? or a sub folder of that ???
wilbur-force said:
ok... very noob question
the root guide says to copy the blob/files to your 'adb directory' ... which directory is that ? the android-sdk directory ? or a sub folder of that ???
Click to expand...
Click to collapse
copy it to platform-tools
android-sdk-windows/platform-tools/blob (all files + blob should be here)
also you can hold shift + right click platform-tools and choose open cmd window here.

Noob Guide: How to - from stock phone to custom ROM: includes Bali/Voodoo Lagfix

Ok, for anyone who finds this. I'm writing out a quick guide for what I was led through. I've borrowed a few lines from some other threads as well
This guide will take an original stock SideKick 4g that has not otherwise been modified, flashed, etc and lead you through the steps to running a custom ROM. This should lead to a smoother running system with less lag, longer battery life, etc.
[Edit] I was pointed later to a nice FAQ by xmeatizmurderx, which, while not a guide, does have some questions answered you might have, along with some definitions and whatnot that might help make things clearer for you or if you just like know what it is something actually does or is. ^..^
I personally updated to Gingerclone v2, BUT any of the custom ROMs are installed exactly the same way. I do not list links to all of them, so you might have to find the one you want when you get to that stage if you do not want to use Gingerclone.
While I did originally update to GCv2, I had some issues and we're not sure why. So I changed over to CleanFusion v3. It's much more similar to the stock system in looks and all. I would also suggest, make sure you have a backup of all your stuff (contacts in particular) off your sim, on another card/phone/google/whatever. Most of my contacts dissapeared, we think because it's an old sim that likes to be wonky with some of the new phones. But still, be forewarned.
After the device is rooted, you can use MyBackup Root (free in the market) to backup all your applications and data to your SD, which you can then copy to your computer as well.
---
First, download SuperOneClick from http://shortfuse.org/ . Whatever the most recent version is.
The file you downloaded of SuperOneClick is a .zip file. You'll need to extract it to its own folder (if you don't have a program to do this, download .7zip here http://www.7-zip.org/download.html).
Download the Samsung drivers ~ In this case, the Samsung Vibrant drivers work for the Sidekick 4g. Drivers found under the 'software' tab here http://www.samsung.com/us/support/downloads/SGH-T959ZKDTMB
Install the Drivers to your computer and reboot it.
---
With the phone unplugged, enable USB Debugging. On the home screen of the phone select Settings > Applications > Development and then select USB Debugging so that a Check appears on the selection box.
When enabled, connect the phone to your PC.
---
Run SuperOneClick (the .exe file) which is on your computer. When the program has opened click 'Root'.
The program will pop through a bunch of windows, if it asks to install something like mine did, say yes. When it finishes, it asks if you would like to test it. Say yes.
Your phone is now rooted.
I disconnected from the computer and rebooted the phone (turn off and then on again).
Plug the phone back into the computer.
---
Next step is to go to this thread here http://forum.xda-developers.com/showthread.php?t=1124453
[EDIT/UPDATE] Krylon360's files moved or something, find the recovery.zip and update.zip here http://db.androidspin.com/Developer_Display.asp?DeveloperID=248
I was advised to go through the first post, as I’d learn more. But apparently there’s an automated script somewhere in this same thread if that’s your preference. I quite enjoyed learning how to access everything myself, in case I ever need to use it for something.
You will need Root Explorer ($3.99) from the android market. I tried Astro File Manager, and it’s lovely, except for the fact that you need to buy the Pro edition in order to access the /system files. >:C
(Basically you need a file manager on the phone that will allow you to copy files into your /system/bin file on the phone.)
Download both of the files listed in the thread I just gave. You will mount your SD card (on the home page of your phone, drop down that little black menu thing at the very top, select USB storage and enable it).
Place the file ‘recovery’ and the zipped file ‘update’ onto your SD card. Nowhere in particular, just in that main area that appears when you open the SD.
Now is a good time to put the ROM you want to flash onto the SD as well.
[EDIT]: Please keep in mind I'm not a developer and I don't plan to live on this forum. So new ROMs will be developed and I probably won't be around to update this list. So make sure to look around for threads about new ROMs to start with or update to. ^..^
Those suggested to me were :
Gingerclone: Apparently themed very green.
http://forum.xda-developers.com/showthread.php?t=1231021 (check Dev forum for a newer version)
TouchMIUIwiz: Very similar to Gingerclone, but more greys.
http://forum.xda-developers.com/showthread.php?t=1207328 (check Dev forum for a newer version)
Smooth Maximus: Themed very blue and black
http://forum.xda-developers.com/showthread.php?t=1158250 (check Dev forum for a newer version)
Clean Fusion: Clean and pretty.
http://forum.xda-developers.com/showthread.php?t=1204131 (check Dev forum for a newer version)
Of course, there are likely other ones out there, these are just the main ones my supporter knows intimately enough to note. He had a really hard time recommending just one. XD
Whatever you go with, it's always a good idea to have a backup of your phone system, which we go through later in the guide when you need it, so don't fret.
---
Feel free to use whatever new ROM you'd like, either listed above or another on the Development Forums, I was told all the following steps would be exactly the same, just using a different custom ROM.
I’m going with Gingerclone v2, as I was informed that while it did crash on my helper once, it seems to be overall the most consistent one that he’s tried.
The above linked thread for GingerClone has two files, I’m using the top one, as I do not have the original release installed.
This .zip file you just downloaded can be copied onto the SD root menu (the main menu available when you access the SDcard from 'My Computer').
---
Unmount your SDcard from the computer (that little black bar on the top of your phone's home screen, turn off the usb connection). Disconnected from the computer even if you want.
---
Open Root Explorer. Navigate to access the SD card (it has its own file in the root menu you start off in). Copy the ‘recovery’ file, navigate back and paste it into /system/bin (to get there, navigate back by tapping the top option 'parent directory', select 'system', select 'bin', paste it in there). Do not delete the original 'recovery' file in here. It will automatically ask if you want to overwrite the file. Say yes.
If it give you the error “you cannot paste here because the file system is read-only.’ Then at the top, tap the “R/W” square so that it then reads “R/O”. Paste again, select ‘yes’ to overwrite the file.
---
Next you’ll turn the phone off so you can boot into recovery mode. To do this, while turned off, you’ll hold the volume up and volume down buttons together, then, while holding them, press the power button. Let go of all three together once the screen starts up.
If you get some blue text, a little warning looking sign over the droid dude, and some yellow text, then you're in the right place.
In here use the volume up and down buttons to navigate through the options and use the power button to select something.
---
Highlight “reinstall packages” and use the power button to select it once it’s highlighted.
You’ll have orange text now. So first, let’s backup the phone, JUST IN CASE something goes funky. (nothing went wonky for me)
Navigate to ‘backup and restore’ and select it.
Navigate to ‘backup’ and select it.
It should be backing up now, with a little nasty coloured yellow progress bar at the bottom.
Once the backup is done, you should be back at the original orange texted screen.
---
This next bit is important:
Navigate to ‘mounts and storage’ and select it.
It should read:
unmount /chache
mount /data
mount /sdcard
unmount /system
(My phone said “unmount /sdcard” which isn't important. The only thing that NEEDS to read correctly is 'unmount /system' - If it says 'mount system', you need to navigate to it and select it so that it reads correctly)
If your list reads like the above, then you’re good. Click the ‘back’ button, which is the arrow on the bottom left corner of the phone (if you're holding it the way I am. ;p).
---
Navigate to ‘wipe data/factory reset’ and select it.
Navigate to the ‘yes -- delete all user data’ and select it.
Repeat this twice more. (That’ll be three times total.)
Navigate to ‘wipe cache partition’ and select it.
Navigate to ‘yes -- Wipe Cache’ and select it.
Repeat this twice more. (Again, three times total.)
Next, navigate to ‘advanced’ and select it.
Navigate to ‘wipe Dalvik Cache’ and select it.
Repeat this twice more. (Three times total.)
I was told to go back to the mounts and storage menu to make sure it still says ‘unmount /system’. Mine did still say this. If it doesn't read correctly, it won't boot right. Fix it if you need to.
---
Next I’m going to install GingerClone.
To reiterate, if you want to use a different custom ROM, go for it, the steps are the exact same, you just need the correct ROM download (which should be a .zip file).
Go back up a menu, navigate to ‘install zip from sdcard’ and select it.
Navigate to ‘choose zip from sdcard’ and select it.
Navigate to the GingerClone.zip (the name is longer than that, but you should know what I’m talking about.) and select it.
It’ll go through installing GingerClone now, with that ugly yellow progress bar at the bottom again.
When it’s done installing. Go back again to the ‘mounts and storage’ menu to check that the system is still unmounted (should still read ‘unmount /system’) Mine did mount my SDcard, but that’s fine. If it reads ‘mount /system’ then navigate to it and select it so that it reads ‘unmount /system’.
Good job so far! Go back to the main menu and navigate to ‘reboot system now’ and select it.
---
Bit odd seeming. It did take longer to boot up. First my phone talked to me, which I was told was the Voodoo LagFix. Then it started blowing sparklers into an X which is also good as that means it’s booting up. (I'm not sure, but it might look different for other custom ROMs.)
The normal screen that’s still ‘locked’ before you would go to the home screen should have the options to slide up (Start Using) or down (Tune a few things first). I was told to go ahead and do the tune bit and “just hit next a buncha times and get rid of it.” ;p It’s pretty straight forward setup stuff.
In case you’re wondering, that ‘update.zip’ that you downloaded earlier when you downloaded the recovery file? Well, when you reinstalled packages, it did that one automatically. So it's taken care of, no worries.
From now on, if Voodoo LagFix is on and you go into recovery mode (when you turned it off and held the volume buttons and turned it back on) then the text should be red. You can check if you want though it's not necessary, the red just indicates that Voodoo LagFix is indeed installed.
I was told that there are options in recovery mode to disable Voodoo LagFix or to convert back to the original file system. I haven't messed with them and don't plan to so long as this keeps working nice for me.
So. Yay! Have fun exploring and customizing your improved system!
I may have typed this sucker up, but basically all credit goes to the hours of support given to me by yogi2010 who is entirely awesome.
If there *is* anything that's a bit off or inaccurate, place the blame on me as interpreter, I just wrote out what I did, and if I thought it might be necessary, how something worked to the best of my very limited knowledge.
Great work!
I tried installing a new rom on my sk4g a few months ago and couldn't get it to work so i left it alone in fear of bricking my phone. I finally got the balls to try again and used this link and it worked perfectly. Thanks so much and good work yogi2010 and Kediil!
DirtyNateDog said:
I tried installing a new rom on my sk4g a few months ago and couldn't get it to work so i left it alone in fear of bricking my phone. I finally got the balls to try again and used this link and it worked perfectly. Thanks so much and good work yogi2010 and Kediil!
Click to expand...
Click to collapse
Glad you got it all working!
Why do you think posting a noob/how to guide after we have like 4 is a good idea? How many of these guides do we need already? This forum is getting filled with junk and overposting
xmeatizmurderx said:
Why do you think posting a noob/how to guide after we have like 4 is a good idea? How many of these guides do we need already? This forum is getting filled with junk and overposting
Click to expand...
Click to collapse
If there's another guide that has all the steps, from very beginning to finish, I'd suggest you find someone to sticky it. I spent three days going through the forums and could not find a single guide that took me through everything, step by step, which is why I put this together, assuming that because I could not find it, it did not exist.
Be it this one or another, there needs to be a guide for a know-nothing-noob such as myself to follow without having to hunt down the separate bits and hope I put them together in the right order, and it needs to be stickied in the top of one of the forums, preferably in the General or Development area.
that has all the steps, from very beginning to finish, I'd suggest you find someone to sticky it. I spent three days going through the forums and could not find a single guide that took me through everything, step by step, which is why I put this together, assuming that because I could not find it, it did not exist.
Be it this one or another, there needs to be a guide for a know-nothing-noob such as myself to follow without having to hunt down the separate bits and hope I put them together in the right order, and it needs to be stickied in the top of one of the forums, preferably in the General or Development area.[/QUOTE]
http://forum.xda-developers.com/showthread.php?t=1135634
It's the 3rd post down in the development section and takes everything from start to finish, you obviously didn't search very hard
xmeatizmurderx said:
Why do you think posting a noob/how to guide after we have like 4 is a good idea? How many of these guides do we need already? This forum is getting filled with junk and overposting
Click to expand...
Click to collapse
Wow, I find that comment extremely rude and out of place. I personally find this guide much easier to follow, and many may agree with me. I don't see anything wrong with having different tutorials on the same operation. Look around, I guarantee you will see it happening everywhere, not just on these forums. So long as it doesn't purposely mislead people, I don't see the harm in it. In fact, it seems to me that, your comment is the one adding more 'junk' to the forums. As you have now posted a reply that does not benefit the community at all, instead its provoking unnecessary posting. If it is so bothersome to you, and if this post really falls into your 'junk' category, discuss it in private if your position in these forums allows it, but not here where you are making a comment which puts down someones good-hearted attempt to help out the community.
@Kediil Thank you for this post. There can never be 'too many' helpful people.
xmeatizmurderx said:
http://forum.xda-developers.com/showthread.php?t=1135634
It's the 3rd post down in the development section and takes everything from start to finish, you obviously didn't search very hard
Click to expand...
Click to collapse
I did go through, and I did see that one, but I had no idea what it was. The name of the thread didn't make it obvious to me, who knew absolutely nothing, that it was a guide. I didn't know what rooting was, or if I needed to do it, or how (for all there's a guide within the rooting thread). I didn't know what CWM was. I didn't know what a kernal actually was, or how to 'flash' it.
Looking at the guide you linked, if you know more or less what you're doing, then it could prove helpful, if a bit blunt. But coming at it from the perspective of knowing absolutely nothing, it didn't help me in the least.
I know it can be difficult to know something and have to deal with people who know nothing, but if there's no sure-fire, solid way for the new person to learn without needing a knowledgeable person to help, then you'll just continue to be needlessly frustrated.
@ merman123 Thank you very much for the support. ^..^ It's already helped at least one person, so I'm satisfied. There will always be haters or frustration or drama. It's the internet! ;p
Kediil said:
I did go through, and I did see that one, but I had no idea what it was. The name of the thread didn't make it obvious to me, who knew absolutely nothing, that it was a guide. I didn't know what rooting was, or if I needed to do it, or how (for all there's a guide within the rooting thread). I didn't know what CWM was. I didn't know what a kernal actually was, or how to 'flash' it.
Looking at the guide you linked, if you know more or less what you're doing, then it could prove helpful, if a bit blunt. But coming at it from the perspective of knowing absolutely nothing, it didn't help me in the least.
I know it can be difficult to know something and have to deal with people who know nothing, but if there's no sure-fire, solid way for the new person to learn without needing a knowledgeable person to help, then you'll just continue to be needlessly frustrated.
@ merman123 Thank you very much for the support. ^..^ It's already helped at least one person, so I'm satisfied. There will always be haters or frustration or drama. It's the internet! ;p
Click to expand...
Click to collapse
Posting several threads that say basically the same thing is annoying and clutters the threads making it hard for people to find what they need. It has also annoyed the **** out of a lot of us on here and driven away several developers for this phone because noobs come on and post new threads constantly about the same couple of things.
Being a noob is fine, we all are at some point but learning to search and pm some of the senior members for help will help keep the forums clean and the devs happy, I find it hard to believe you came across xda without knowing what rooting was but honestly I don't care, just please be mindfull and spend time searching thoroughly before posting.
xmeatizmurderx said:
Posting several threads that say basically the same thing is annoying and clutters the threads making it hard for people to find what they need. It has also annoyed the **** out of a lot of us on here and driven away several developers for this phone because noobs come on and post new threads constantly about the same couple of things.
Being a noob is fine, we all are at some point but learning to search and pm some of the senior members for help will help keep the forums clean and the devs happy, I find it hard to believe you came across xda without knowing what rooting was but honestly I don't care, just please be mindfull and spend time searching thoroughly before posting.
Click to expand...
Click to collapse
I came across XDA by typing 'sidekick 4g lag fix' into google, obviously because I was experiencing lag and was hoping for a fix. One of XDA's threads was the first thing listed and people here seemed to know what they were doing and talking about here. I did spend quite a lot of time searching. I would gladly take full fault for posting something unneeded if anyone would but show me a link to a full, step by step, easy to follow guide. *shrugs* I'll eat my words if there is one.
I need help
So I'm trying to run a custom rom on my new SK4g but no matter what I do, I keep softbricking it... just gets stuck on the sidekick logo during boot. I've followed this guide STEP BY STEP a few times and with different roms, same result. After the rom install is complete I confirm the mounts are correct and then reboot to system but it never gets to system. I end up having to start over from stock via ODIN
HELP HELP HELP... what am I doing wrong. The only POSSIBLE thing I can think of is when it comes time to overwrite the recovery binary, I use adb shell and mount the system with:
Code:
# mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
then I copy the file with:
Code:
# cp -f /mnt/sdcard/recovery /system/bin/
Code:
# reboot recovery
please someone help me and tell me what im doing wrong
not too sure what's wrong, but if you are flashing ROMs, you probably are getting into ClockworkMod properly. are you checking your mounts BEFORE you install the ROM as well as after?
xmeatizmurderx said:
Posting several threads that say basically the same thing is annoying and clutters the threads making it hard for people to find what they need. It has also annoyed the **** out of a lot of us on here and driven away several developers for this phone because noobs come on and post new threads constantly about the same couple of things.
Being a noob is fine, we all are at some point but learning to search and pm some of the senior members for help will help keep the forums clean and the devs happy, I find it hard to believe you came across xda without knowing what rooting was but honestly I don't care, just please be mindfull and spend time searching thoroughly before posting.
Click to expand...
Click to collapse
Wow, your a real ass. I think this guide is probably the best one here. Very clean and very thorough. Its not people like him that cause developers to leave. Its people like you with no respect and a big attitude. And a HUGE head!!
Sent from my SGH-T839 using xda premium
Thanks so much for this post
Thanks for explaining in layman's terms how to do this. It is very helpful for me and I too had trouble making sense of the other how-to posts. With something as sensitive as flashing hardware it is really important for a novice to clearly understand the steps. I for one really appreciate and applaud your efforts Kediil and Yogi2010!
I'm glad that this has helped some people! I know for those that have been around here a while, it is basically the same thing we already know, but I do think this guide was very clearly written, and is helpful to those who are completely new to this and don't have any idea where to start, and just want to get their phones rooted and modded. kudos to kediil for the great write-up!
I get mad everytime i try to do this because whenever i try to reinstall the packages it just says failed to verify whole signature or whatever then it aborts it , help me please , im tired of this **** ass stock rom
JayNycWepa said:
I get mad everytime i try to do this because whenever i try to reinstall the packages it just says failed to verify whole signature or whatever then it aborts it , help me please , im tired of this **** ass stock rom
Click to expand...
Click to collapse
It sounds like the modified recovery didn't get properly moved into system/bin. Have you followed the steps and pasted the recovery file you downloaded into system/bin, replacing the recovery file that was already there?
Kediil said:
I came across XDA by typing 'sidekick 4g lag fix' into google, obviously because I was experiencing lag and was hoping for a fix. One of XDA's threads was the first thing listed and people here seemed to know what they were doing and talking about here. I did spend quite a lot of time searching. I would gladly take full fault for posting something unneeded if anyone would but show me a link to a full, step by step, easy to follow guide. *shrugs* I'll eat my words if there is one.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1206991
Like I said, SEARCH BEFORE POSTING
It took me all of 10 seconds to find this, it's on the second page of the development section and there are only 4 pages. It took you far longer to type this up than it would have to search.
The reason we don't have stickies is because moderators don't pay attention to us because we have no developers anymore (this is about to change though one of our members was recently sent an invite)
If this were any other phone this overposting wouldn't be tolerated, you guys treat the forums like it's facebook and would rather start a thread than take the time to search for your answer, and it clutters everything up with useless threads. When I joined XDA and had a G1 I didn't post anything for like 2 years because I was able to find the answers by searching.
I am an asshole, so get used to it but I mean you no harm. I am trying to give advice because I have been on here since day one and personally seen devs leave out of irritation with the members lack of forum etiquette. If we can all try and keep the forums clean then we have a better chance of getting support, and this will also help you guys in the future when you move onto more popular devices. If you think I'm a **** you have no idea what some of the senior members can be like lol
---------- Post added at 05:51 PM ---------- Previous post was at 05:22 PM ----------
dw9906 said:
Wow, your a real ass. I think this guide is probably the best one here. Very clean and very thorough. Its not people like him that cause developers to leave. Its people like you with no respect and a big attitude. And a HUGE head!!
Sent from my SGH-T839 using xda premium
Click to expand...
Click to collapse
That's what she said
Alright I'm done trolling now
xmeatizmurderx said:
http://forum.xda-developers.com/showthread.php?t=1206991
Eat 'em up bro
Like I said, SEARCH BEFORE POSTING
Click to expand...
Click to collapse
Um, you posted a link to a FAQ, not a step by step guide...
xmeatizmurderx said:
Alright I'm done trolling now
Click to expand...
Click to collapse
Quit trolling, noone is impressed. Unlike you, Kediil is actually adding to this forum.
vitriolix said:
Um, you posted a link to a FAQ, not a step by step guide...
Quit trolling, noone is impressed. Unlike you, Kediil is actually adding to this forum.
Click to expand...
Click to collapse
faq, guide, whatever
I have posted several links that tell you in plain terms how to root and put roms on from stock. If people find this one easier to read for some reason then good for them, I don't have the power to moderate the forums
My point has been made, I don't know why you are responding to me if you don't like what I have to say
P.S.
I have sent in a request to have this thread stickied for you guys

Categories

Resources