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

Root [Boost Mobile] I Wireless(Kroger) Warp w/Root and Overclock

Skinnyjeans21 said:
Shouldn't there be an i-wireless section...? I mean its a different carrier, neither public nor boost...? :confused:
Click to expand...

I could ask if you would like (I've never heard of I-Wireless, myself)...are the devices actually different from the other two carriers? (i.e., would the rooting methods, etc. need to be different or could we rename one of the carriers to include both names?).

Lemme know and I'll run this up the flagpole with our Admin folks...

Would this thread belong in there or were you just asking because you knew there was a third carrier?

Thanks! (and sorry for so many questions back at cha :) ;))
 
I think this thread would belong in there, I don't think the rooting method is different, but I know that custom roms for boost mess up the i-wireless variant of the phone, except with certain files in place... The devices are the same n860... I think one of the carriers could include both names, but which one?
 
Skinnyjeans21 said:
I think this thread would belong in there, I don't think the rooting method is different, but I know that custom roms for boost mess up the i-wireless variant of the phone, except with certain files in place... The devices are the same n860... I think one of the carriers could include both names, but which one?
Click to expand...

:dontknow: ;)

I'd be happy to ask our Admin folks once/if we know what how they should be treated...don't want to clutter-up this thread with more discussion re. that, but feel free (anyone) to PM me if you know what or if to do anything with the I-Wireless carrier for the ZTE Warp.

Thanks!
 
I've done the root thing and flashed a rom to my Kroger phone and it works, but battery life is bad and data seems to be degraded somewhat. It was a boost mobile rom. I know they both use Sprint, so I went for it.

I'd like to get my performance back up again without reverting to stock. Which files are funky in the rom and what do I need to change in order to flash a boost mobile or public mobile rom?

Thanks in advance.
 
shmeerz said:
I've done the root thing and flashed a rom to my Kroger phone and it works, but battery life is bad and data seems to be degraded somewhat. It was a boost mobile rom. I know they both use Sprint, so I went for it.

I'd like to get my performance back up again without reverting to stock. Which files are funky in the rom and what do I need to change in order to flash a boost mobile or public mobile rom?

Thanks in advance.
Click to expand...

Which one did you flash? Usually it takes a day or two for the rom to settle in and for the cache and dalvik to rebuild after a full wipe
 
Hey SJ... are you here? I'm sorry I took so much space on other thread-- had no idea that "public" referred to other carriers. Is there a moderator I can notify to remove those posts?


Thanks so much for offering help. You must have infinite patience!

I looked at beginning of thread & was going to start downloading file to get ready, but am already confused... there are lots of files

EDIT:
when you have time, that is :)
 
Nah, don't ask for a moderator to remove them-- we need to keep history so as to not disturb the flow of conversation.

I don't have infinite patience... I have a little brother though, and he requires me to have much patience -__-

There are quite a few files to download... I need to make something to centralize it, like a one-step root method specifically for i-wireless...
 
these are the steps you are going to want to follow:

CWM: clockworkmod recovery - Download - 4shared

Download this link:

Android SDK.rar - 4shared.com - online file sharing and storage - download

1- extract android sdk folder to c:\
2- extract the warp recovery to c:\
3- open a command prompt (open with admin if using win
vista/7)
4- navigate to your android sdk folder (cd c:\android sdk)
5- Make sure usb debugging is enabled, plug your phone in, and type: adb reboot bootloader
6- Your phone will reboot and hang. your computer should ask for a driver and it can be found in the android sdk folder
7- in your command prompt enter: fastboot flash recovery c:\recovery.img (If your OCD like me go ahead and do it twice...)
8- type fastboot reboot and pull the battery from your phone(letting your phone boot up at this stage will reinstall stock recovery)
9- now when you turn your phone on in recovery ( turn on while
pressing volume up and pwr) you will get the Clockworkmod/TWRP
recovery.
Click to expand...

EDIT: After this, go through steps 2-7 and you should be done :) except for the Halo Jelly 4.3 flash thing, that's been updated to HaloBean 8. I'm not sure if it'll work the same with other roms though... every rom is set up differently
 
Heh... hope you'll be at forum for a while
I have to start by getting a RAR extractor... haven't used RAR for a long time

--re step 5: how do I enable usb debugging... can't find on phone

I know I'll be getting stuck, but your directions make sense from the standpoint of not having started :)
 
The files from the 2 links are ZIP & RAR. but both DL'd as exe's. Hope it's right-- the site is a little confusing to DL from... I guess you just set them to decompress from exe's
EDIT: not what I thought... exe is some kind of installer. I couldn't get it to DL without selecting installer link :( Maybe I'll try that part again. Embarrassing to get hung up here (blush)



Need to know how to enable usb debugging.
 
aimzzz said:
Heh... hope you'll be at forum for a while
I have to start by getting a RAR extractor... haven't used RAR for a long time

--re step 5: how do I enable usb debugging... can't find on phone

I know I'll be getting stuck, but your directions make sense from the standpoint of not having started :)
Click to expand...

Go into applications, development, and enable from there :)
 
Skinnyjeans21 said:
After this, go through steps 2-7 and you should be done :) except for the Halo Jelly 4.3 flash thing, that's been updated to HaloBean 8. I'm not sure if it'll work the same with other roms though... every rom is set up differently
Click to expand...

I'm at #5...
What is the Halo Jelly 4.3 flash thing?
 
stuck at #6
At #5, after the command: adb reboot bootloader, cmd prompt response was:
* daemon not running. starting it now *
* daemon started successfully *
Then bootscreen came up & it's hanging at bootscreen, as described. Nothing came up about a driver.
Should I have pressed phone On btn or something?
What next??
 
aimzzz said:
stuck at #6
At #5, after the command: adb reboot bootloader, cmd prompt response was:
* daemon not running. starting it now *
* daemon started successfully *
Then bootscreen came up & it's hanging at bootscreen, as described. Nothing came up about a driver.
Should I have pressed phone On btn or something?
What next??
Click to expand...

Did you install the android sdk? otherwise it may not ask about the driver... if you did and it didn't ask just skip to the next step
 
--Did you install the android sdk?
yes, I have c:\andriod sdk folder

--type "adb devices"
from c:\android sdk>
I typed 'adb devices'. Got "list of deviced attached", but nothing follows
 
Initially, when nothing had happened about drivers at #6, I went ahead & tried #7"
c:\android sdk>fastboot flash recovery c:\recovery.img
Prompt said 'fastboot' not a recognized internal or external command, operable program or batch file ... maybe bec driver not there?
 
Decided to do a factory reset & start over. After
c:\android sdk>adb reboot bootloader
there was nothing about a driver (again). Typed 'adb devices'. Again got "list of devices attached" but nothing listed.
Is there a command that will load the driver without having been prompted?
 
Windows 7. Looking at it, just saw that there's an Android SDK folder inside of the Android SKD folder. The folder must have been zipped into zip file & when unzipped, it went into another folder of same name. Didn't notice. Will fix it & start over. It's amazing how many frustrating little things can happen--lol!
 
Redid everything... no change. Here are screenies. Sometimes words don't work so well. :)
Android SDK dir.jpg
Cmd prompt.jpg


EDIT:
In setting up Andriod SDK on Windows, I wasn't supposed to run any of the executables in the folder was I? It just needed to be extracted to the right place (c:\)... right?

EDIT 2:
Hope I'm not making you crazy... o_O
 
Hmm... a couple of reboots and a different usb cable helps me with the driver error... it happens to everybody at least once. There has to be an easier root method for i-wireless Warps...
 
my only other usb cable is from a LG optimus... it does fit. Would it blow up or anything?
 
Something happened... thought it had worked
Is supposed to boot up saying:

CWM-based recovery v5.0.2.8 with a top hat pic?


EDIT:
I'm not there yet. Tried installing Titanium Backup & it says 'not rooted'. Sigh. Why was the boot stuff different?
 
You must log in or register to reply here.
Back
Top Bottom