• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [TOOL] AIO ROOT, UNROOT, and RECOVERY INSTALLER (GUI EDITION)

once i get radio buttons down ill work on an option for the fastboot install method
but for right now its using the adb method, same as the terminal method, which can be problematic
 
junkie2100 said:
once i get radio buttons down ill work on an option for the fastboot install method
but for right now its using the adb method, same as the terminal method, which can be problematic
Click to expand...

It was original stock b09. Rooted, then cwm (regular, cuz she has kids that like to play w/ phone) then tried to make a stock backup.. Went thru everything then failed@ making img. F tried installing guspeeds cyan backup =MD5 mismatch. Then stock backup = MD5 mismatch. Then Shinru's AA ROM = MD5 mismatch..by then I'm in near panic mode cuz I was thinking I messed up a ladie's phone (lmao...NOW) so I pulled out unsigned_stock b09 .zip and it went OK, saving my butt. Somewhere between the Initial stock backup failing and guspeeds cyan install, I forgot factory reset.. But wasn't SUPPOSED to when restoring backups, right? I t didn't matter tho, factory reset or not, nothing else worked besides unsigned stock b09... :confused:
 
umm. well could it be that there wasnt enough room to make a backup on the sd card? now, when you are putting these backups in, are you unpacking them to the right place? or just trying to run them through the "install zip from sd card" function? because shinru's rom should work like that, if it was downloaded uncorrupted, but the backups have to be extracted and tossed into the right place in their respective folder like any other backup it makes

just double checking ya kno, but anyway, there is also a possibility you just had corrupted downloads, did you download them over a phone? are these ones you have tested on a different phone? also failing to make a backup wont corrupt a phone, and neither will a restore attempt that doesnt get past the initial checks, but i really dont know what could be the issue here if its not something of that nature. the version of cwm on the auto installer, the newest one anyway, is the same version that is posted on the cwm site and should be identical to the touch version which i use other than the fact that it doesnt have touch functionality, maybe it differs from the original release superr and i put out, but i dont see how, because that is the one and only thing that has changed other than the look of the tool it still runs all the exact same code as the fixed auto installer and the doomlord root method
 
Hmm... Yeah. Backups/Restores were in respective folders - not zips. ROMs stayed zipped. All files were transferred via PC to SD card, but I DID have trouble w/ available space on card @ first. It was only a 2G card that was maxed w/ files from like 6 diff phones, lol. Had a bunch of erasing to do to make room just for the ROMs. I'm not really questioning ur cwm cuz it still saved my butt. Even after several minutes of boot loop it still threw me back into cwm recovery. I just didn't know WHAT could have caused it... Maybe ur right, corrupted downloads then... My PC's been ...behaving... Weird. Those ROMs had been on my PC a while and the only new stuff I put on it that day was unsigned b09.zip & ur GUI Tools... I figured I'd ask u cuz you'd be the person who's been hit up with all sorts of strangeness/questions since the development of ur CWM and may have run across dang near every situation. :D
 
eh, ive run across alot of odd things, some even other developers have never heard of... but this just seems like some sort of corruption, if your computer is corrupting things though id invest in a new hard drive immediately though

and hey, im not saying it couldnt be the cwm lol. sometimes i dont trust my own work, im sure we all remember my little "accident" involving a coding error in my auto installer that made it revert you back to stock recovery after the cwm install if you let the program continue. things do happen

also, to frank, yea that was not all that fun lol. kinda got dragged there, im not into anime, i dont like crowds, and i especially dont like crowds filled with underage girls in very tiny skirts, thats just got trouble written all over it
 
Thats no good junkie!
All i can say is i wish I was 18 again. :D:smokingsomb:. Anyways.


Hey i tried the tool here and it wouldn't do anything. I downloaded the latest gui. I have debugging on and trying to put stock recovery on and unroot. I clicked and it didnt do anything. Im going to try again.

I wanna get ready for jelly Belly Bean. ZTE style:confused: Wait that didn't sound good!?!

Ok i cant get it to recognize my phone. anyways. Its ok man.

Once i put stock recovery on another way, I tried to unroot and it worked. Trial and error my little friends.

Never mind. It didn't get rid of su, bummer
 
huh, well i dunno. i havent tested the unroot feature myself, it was just something i found around the internet with no real ties to anything. its not as device specific as rooting so it should work on nearly anything as far as i can tell

was your problem with adb not recognizing the phone? and did you make sure to keep all the files together in the same way they were? kuz the exe will run regardless but without the rest of the files its pretty well useless, it needs those bat files, and adb to be able to perform any of those functions

and are you SURE it didnt get rid of su? it should, this is all the exact same functions done the exact same way as the original version i just split things up and made it prettier
 
Yeah, it was having problems recognizing my phone. I'll try restarting the computer. But it did restart my phone. And the tool said it should be unrooted now. Idk. Its OK. I think I can still get the update if I'm rooted.
 
yea you should be able to. and i dunno why it wouldnt work ill check my code...

did it ask you for super user permissions on the phone at any point? it should ask for super user permissions during the process in order to complete
 
junkie2100 said:
yea you should be able to. and i dunno why it wouldnt work ill check my code...

did it ask you for super user permissions on the phone at any point? it should ask for super user permissions during the process in order to complete
Click to expand...


No, it didn't ask for super user permissions. Im going to try it again.
all that really happened is the phone restarted and the tool said it should be unrooted.
 
alright well, its certainly not the most elegant thing in the world, but i have managed to update the CPP version to include and option for fastboot cwm install. my hope is that this will circumvent the need for rooting prior to installation, though i make no promises, and if i made some sort of coding error again i apologize, but it took me a good 4 hours to make two tiny little buttons work right... im exhausted, but i accomplished my mission, still not the ideal setup but technically it should work
 
youre very welcome. its what i do. but yea as far as your question frank i couldnt say for sure, i only came onto the android scene around 4-5 months ago, and this is the only phone ive really had much to do with past rooting and installing cwm

ive talked to a few of the warp devs before but ive never had a n860 myself so im even less help to them than i am to you guys lol. ill put some more work in on it maybe add some features, im thinking about maybe tossing in rebooting options for the hell of it, that way you can access all modes easily, maybe throw in phone detection so youll know right away if its recognized, possibly even put in a kernel flashing feature, who knows
 
i do what i can. and i cant say i dont enjoy what i do. though i do have a little more on my plate now that im a mod over at unleashedprepaids.com im still trying to come up with ways to improve the program and even still working on theories for cm though even i am running out of ideas at this point
 
junkie2100 said:
i do what i can. and i cant say i dont enjoy what i do. though i do have a little more on my plate now that im a mod over at unleashedprepaids.com im still trying to come up with ways to improve the program and even still working on theories for cm though even i am running out of ideas at this point
Click to expand...

Well I hope if or when we get jellybean, it will help cm along. But I'm sure zte won't give up the source. Maybe we should start a petition early for jb source:banghead:
 
Frank The Tank said:
Well I hope if or when we get jellybean, it will help cm along. But I'm sure zte won't give up the source. Maybe we should start a petition early for jb source:banghead:
Click to expand...

kernel source they may just give us. they shouldnt put up too much of a fight on that one hopefully. but the rom source unfortunately we will never get, the actual jellybean source they dont have to release so they will refuse. if we had their source code from the first rom we would have probably worked it all out already. the thing that would be helpful from a jellybean release is the files in the rom itself. things updated for jellybean that we can pull directly from the phone and use as is. the kernel probably wont change much, and its very doubtful it would change in any really helpful way
 
well, my ever changing C++ edition has another update. i decided to add fotakill to it, and changed the layout a little, slightly more streamlined and less ghetto looking lol
 
its what i do. i want to find a way to make it modular though, just kind of a frontend for use on any phone, im gonna be working on that today along with instructions on how to reprogram it for different devices
 
alright so yea i got it to where it can be modified without having to rebuild it all from source and sift through all my horribly mashed together c++ code. i havent put the finishing touches on it yet so i wont be uploading it yet, but functionally it can be customized for anything that allows command line based rooting, and recovery installing

i have managed to make it to where things that arent available get greyed out, the menu items such as the links to the warp sequent sections of forums and the zte drivers and support site are customizable, and there is a device name that is changeable so as not to confuse anyone, dont want anybody thinking theyre opening the one for the sequent when theyre actually opening one for a different phone and destroying something
 
You must log in or register to reply here.
Back
Top Bottom