Related
Hello & yes, yet ANOTHER person with this issue. This is what I've done:
It all started by going out to unlockr's page & following their rooting how-to. When I did this it put it in the never ending dell screen flashing lights loop. I've researched quite a few hrs on this. This is what I tried:
1) Doing factory restore (holding volume buttons & pwr buttons down) & choosing restore.
2) Borrowed a buddies SD card & tried a restore (did nothing)
3) Followed a couple of guys instructions on doing a restore one of them being here: http://forum.xda-developers.com/showthread.php?t=776883
After following the directions I did see it look like it was updating back to the 1.6 OS, but after it rebooted it was still stuck in the Dell flashing loop cycle.
SO I did probably the dumbest thing I could do & took it back to Best Buy who is shipping it off... most likely to get my warranty canceled, but I didn't know what else to do. I had purchased their protection plan, so I'm not sure how it's gonna go. They would have replaced it in the store, but I had already returned my 1st one as it wouldn't boot right out of the box (not my fault).
So I figure if they don't flash it at Dell & get it back to working, I'll have to keep working on it myself to correct the issue....
So I guess my question is, any advise on why mine is being so difficult or is this just the way it is & it takes several attempts to flash these things sometimes? Or has Dell implemented a security feature in the new releases & that's what is causing my headache?
Those of you who feel the need to rain down the "Dumb thing to do returning it" please save those comments as I've already stated "I know".... I just need some positive input on getting this thing back on "it's feet" IF Dell doesn't fix it for me.
I will keep you posted on the Best Buy/Dell Drama that I'm sure will start up... I will say that if it's not fixed, I can't say that I'll continue with paying Best Buy $10 a month for a protection plan, as they supposedly will replace the phone if it was damaged in any way. If anyone has info or a story on that part of it I'd like to hear it as well.
Thanks in advance!
Look for the upgrading downgrading guide in xda. Nornally starting from 4399 build is a good start to get you back up and running.
http://android.modaco.com/content/dell-streak-streak-modaco-com/317549/how-to-go-back-from-21-to-00-builds/&source=android-home&ved=0CBoQFjAB&usg=AFQjCNH7W3lUKYibzBQg4qVNxKs955Q0LQ
Sent from my Dell Streak using XDA App
DON'T USE THE UPGRADING/DOWNGRADING GUIDE!! IT WILL BRICK YOUR WHITE STREAK!!
The white Dell Streak is known to have something different going on with it. There is a special tool (QDLTool) that is needed to upgrade it/unbrick it. It takes you directly to stock 2.2 and you can do what you want from there. See this thread here for more information and a fix.
http://android.modaco.com/content/d...24010/warning-white-dell-streak-is-different/
Thanks for the knowledge! Didn't know there was a difference, although I suspected something was amiss when I was doing what I was instructed to do but not getting results....
Any more info is appreciated so keep it coming!!!
erm not that im saying this BUT you got protection(inshureance)accidently drop it in a sink full of water or some such like acident pay your excess and get a new one.
but i dint say that.There norm pritty good at replaceing your phone after such an acident
We'll see what happens when I get the phone back... the post from TopShelf95 may just have saved it from a fate similar to that! HA!
FOR WHITE DELL STREAKS
You'll need the QDLTools for this... so please search/google the links or posts for that.
Typed instructions from these posted from videos that I can't link to yet as I'm a noobe here...
(Hope I didn't fat finger & mistyped anything so be on the safe side & don't cut and paste command line stuff)
1) Start, type CMD in the “programs search area”, CTL, SHIFT & Enter to start command window in Admin mode.
2) Type “bcdedit –set loadoptions DISABLE_INTEGRITY_CHECKS & press “enter”
3) Type “bcdedit -set testsigning on” & press “enter”
4) Reboot
5) Go to the directory where you’ve stored the QDLTools (ex. C:\Streak\RepairTool) , then into the subfolders until you find the driver folder, open the subfolder “Driver_2.067”, Then “Test Certificate” .
6) Right click on qcusbtest & install cert
7) Choose “place all certificates in the following store” & browse
8) Install cert in the “Trusted Publishers” store, when done click “Ok”
9) Right Click on the qcusbtest cert again & select “Install Certificate” again
10) Choose “place all certificates in the following store” & browse
11) Now install cert in the “Trusted Root Certification Authorites” store
12) Click “Ok” when done
13) Remove & replace battery in Streak.
14) Hold down the Volume Up button & plug in USB cable
15) PC should detect connection & install drivers (which will fail)
16) Open control panel & go to device manager
17) Locate the “Qualcomm HS-USB Diagnostics 9002” (if it doesn’t have a yellow exclamation mark by it, you have the driver & can skip forward to
18) Right click & select “Update Driver Software”
19) Select “Browse my computer for driver software”
20) Select “Let me pick from a list of…”
21) Choose “Show All Devices” & click “Next”
22) Click on “Have Disk” & browse to the repair folder, drivers are in the Driver_2.067 folder, if you are using 64bit OS go to WIN64 (Win32 for 32bit)
23) Select WNET unless there is a folder for your version of Windows (for 64bit choose AMD64 unless you have an Intel Itanium CPU)
24) Select “qcser.inf”, click Open, then “Ok”
25) Choose “Qualcomm Incorporated” & choose “Qualcomm HS-USB Diagnostics 9002”, then click “Next”.
26) Click “Yes” if you get an Update Driver Warning dialogue box, then “close” once installed.
27) Now go back to QDLTool folder
28) DISCONNECT USB CABLE FROM STREAK
29) Start the QDLTool utility
30) On the QDLTool Upgrade Build screen the area “Device” with “Port:” in it should say “Not Connected”.
31) Make sure USB cable is UNPLUGGED & remove batter from the Streak.
32) LEAVE BATTERY OUT FOR AT LEAST ONE MINUTE
33) Replace battery & install back cover on Streak
34) Hold down Volume Up button & connect USB cable to go back into diagnostics mode
35) “Port” in the Device window will change to ”Qalcomm HS-USB Diagnostics 9002 (COM4)” once the Streak has been identified.
36) Click “Run” to start the update. Takes from 3 to 4 minutes typically.
37) IF YOU GET A FAILURE AT THIS POINT go back to steps 31 thru 34. Wait for step 35 & follow 36.
38) When it says “Waiting for Reboot” your Streak should reboot itself, ready to go into Fastboot mode
39) IF IT FAILS AT THIS POINT: your ADB drivers for fastboot are not installed correctly, so fastboot may be erroring, install drivers & restart steps 28 thru 36.
40) At this point your device should have been updated & should soon finish booting into the updated Android release.
41) Take your PC out of Test mode by going to “Start”, type CMD in the “programs search area”, CTL, SHIFT & Enter to start command window in Admin mode
42) Type in “bcdedit /deletevalue loadoptions
43) Type in “bcdedit –set testsigning off
44) Reboot
other solution
Solution # 2
Take the phone back to where you bought it and get the black one.
As some of you may know my white one met similar fate and after hours of getting no where i just took it back and got the black one.
after 20 minutes of getting it home i had froyo 2.2 running on it.
besides..do you really want a white phone? lol
i didn't. they were supposed to give me a black one to begin with..
I told the returns lady i wanted a black one and they gave me a white one. when they booted up the phone it didnt boot and they did not say one word. they just went and got me a black one.
Frankly this was the only reason i bought one from bestbuy..
it certainly wasnt because of their pricing
Good luck.
Bigfoot, if you'll reread my original post you'll see that I've already returned one & tried to return the white one, but they would only allow one instore return. I don't care if it's white or black (I'm not racist HA!) it's gonna be in a Otterbox Defender anyway. I just want a phone/tablet that works at this point.
We'll see how the above mentioned "fix" works if I have to install it when I get my phone back.
I have the white streak too and I can tell you that the QDLTool works like a dream. Just follow the instructions to the letter and you will have 2.2 on it in no time. The Streak is virtually impossible to perma-brick. Since QDLTool works on a lower level than fastboot, it will work even when all else fails.
Awesome again good to know!
Does the qdltool work for the black streak?
Sent from the Dell streak
FINALLY (update)
So after 42 days I FINALLY got my phone back from Best Buy... WORST customer experience... I would tell the whole experience, but I'll just make it short... they couldn't find it at one point, they shipped it back 42 days later, my 16 gig sd card is missing from it & when I got it back, they'd not reflashed the phone. So they did nothing but basically steal my sd card & gave it back to me....
ANYWAY.... After I went back to BB to find out what they were gonna do about my phone not working (which I'll have to call mgr tomorrow) I got home & followed the instructions given in this thread to flash my white dell streak & IT WORKED!!!! No issue 1st time around... Perfect, almost as easy as jailbreaking an iPhone... THANK YOU VERY MUCH FOR THE HELP!!! You guys are awesome...
Now... I have a friend who is also asking will this process work for the Black Dell Streaks... so will it?
also
this puts your system into an unlocked status which enables you to download the official Dell 2.2 ver. One downside to it is it shuts off your wi-fi hotspot...
Good thing about the Dell ver. it fixes the buttons sensitivity for one thing that seems to be an issue on the QDAtools ver... I'm sure later builds that is fixed though (would think it would be)
WRONG
I was wrong (looked in the wrong spot) wi fi hotspot is there... my bad
so by using the tool method on my white streak, does it mean my phone is rooted? or is there more i need to do to root my white streak?
Raikoue said:
so by using the tool method on my white streak, does it mean my phone is rooted? or is there more i need to do to root my white streak?
Click to expand...
Click to collapse
No, it won't be rooted. But that's easy to do. You can stay with Dell stock ROMs (download from their website) or go with DJ_Steve's ROM which is rooted and has lots of other features. Rooting isn't hard, though, if you stay with stock. Just use Super One Click and you'll be good. I'm not sure if either method is supposed to work, but my wife's only was rooted by the second method (rage against the cage or something like that).
Also, QDL Tool works for both black and white streaks.
I have the same situation as the OP. However when I try the instructions I make it all the way to the part of running the QDL tool. There I get an error message at about 12 seconds, during the section just after Run HEX success. The error says:
ERROR[D14]:streaming hello Failed!
ERROR: Download fail!
It then says to remove battery and try again, which I do and get another failure.
Any thoughts besides taking a hammer to this thing?
after the first time it went through the fastboot (Downloading AMSS) it rebooted and I had to manually put it back into the fastboot mode (hold camera) for it to fishing writing everything else.
It Worked Perfect!
I've moved on to the Samsung Galaxy Note... My Streak did it's year or so service as well as it could (it's still working without issue) but I wanted a phone that had actual support, I am an IT tech by day & just don't wanna have to mess with yet another system that I have to do go thru a few hundred pages of forums to figure out the true method of getting something to work or install. iPhone hackers have Android beat in that area for sure... 1 click root/jailbreak is the way it should be.... but iPhone doesn't have a 5.3" screen!!!!!!
Hello again.
Well, more than 24 hours have passed since my original posting and nothing! Many of you read my post, but nobody felt able or willing to offer to help.
So, terrified and having no clue as to what I was doing, after another day of work - success! Amazing! And, I think, more by luck than anything else...
I am going to list below what I did, in the hope that some other poor soul might find something useful in it.
But I cannot stop myself from saying that in this whole website I was unable to find a CLEAR, ORGANIZED and COMPLETE procedure or tutorial about how to upgrade the HTC Hermes - a great pity. It would be a worthwhile endeavour to produce such a document, in language that anybody could understand. No, not even the definitions in the Glossary are enough.
This is what I did:
Preliminaries
- Since I'm working on a Windows 7 Home Premium laptop, I have first installed new drivers for the Mobile Device ("x64 AS Drivers Win 7 Tested & Working") - useful info here: http://www.techparaiso.com/windows-...flash-junkies-on-windows-mobile-phone-devices
This was done in preparation to installing Mitty.
Since these drivers are not signed, you have to restart the laptop, press F8, select to start windows without checking Digitally Signed Certificates
- Installed Mitty
- Installed Hard-SPL-V7 - this one seem to be permanent
- Then I tried to follow the Hermes Upgrade Guide (http://forum.xda-developers.com/wiki/index.php?title=Hermes_UpgradeGuide ) - no luck. No idea what was wrong, but in Step 7, I did not have any files named 00_IPL.nb, 01_SPL.nb to delete as per instructions, so I abandoned this course
What worked:
(still with Hard-SPL-V7 installed, still with drivers for Win 7 installed, still with laptop started with Windows - F8 - disable drivers signature checking)
- In the end, I downloaded 21501_1_Springtime.zip from http://www.ferretlife.com/josh/ (once again, many thanks to Hakim Rahman for pointing me to this ROM!)
- I unzipped the file in its own folder; this produced 2 files:
RUU_signed.nbh <= this is the actual update file
RUUWrapper.exe <= this is the program we have to run that will take the RUUWrapper.exe (after we rename it to HERMIMG.nbh) and apply it to the HTC Hermes
- I renamed RUU_signed.nbh to HERMIMG.nbh
- At this point:
I connected my Hermes to the laptop with the USB cable and waited until it was recognized and WMDC came up and connected to the Hermes
I configured WMDC for sync and partnership (did not check more than "Notes" for sync, since I was not really interested in any sync)
- I ran RUUWrapper.exe (from its folder on the laptop) and followed the prompts
○ => I chose proper ILP - for me it was IPL-1.04 and SPL-2.10.011pro (the AutoDetect did not work for me, whether I checked the "Is it a hard SPL?" or not)
○ => after program got to "Verifying ..." it produced Error 260 - at some point, the device was disconnected from WMDC (ActiveSync)
- All that is left is to shut down WMDC, soft-reset Hermes and try again. In one of the many tries, amazingly, it got to start the Upgrade on the Hermes before I got the Error 260, and, although the Error 260 was displayed, it continued with the upgrade and ended successfully, but it did not reboot the Hermes - I turned it off and on again - it worked!
Still confused, but elated by my luck,
Ily426
----------------------------------------------------
Jan 27, 2010
Hello everybody!
I am a real, total, complete, hopeless, newbie and I'm writing in the hope that some kind soul with knowledge and experience in upgrading may be willing to hold my hand for updating the OS on my Hermes.
I have been reading the xda-developers.com on and off for about a week now and all I can say is:
1. I am awe-struck by the passion and knowledge of the people active on this site
2. I am overwhelmed by all I have read - I fear I do not understand much of it, certainly not enough as to have the courage to proceed with the update by myself
This is where I am now:
1. I have installed Mitty on my PC and even made it work (!)
2. I ran one of the many Hard-SPL-V7 to be found here and the bootloader screen did display the modified info; eventually, I clued in to the fact that the changes this software made to my HTC were only temporary
3. I regrouped and now:
- I have read more than once the Hermes Upgrade Guide at http://forum.xda-developers.com/wiki/index.php?title=Hermes_UpgradeGuide
- I have downloaded and decompressed:
Hard-SPL.zip
[*]ModifiedRUUUpdater-V2 (ROMUpgradeUt.exe)
[*]NBHextract
[*]nbhgen0.1
[*]RUU_Hermes_WWE_WM6.5.28205.MobileVista6.50SeaDragon_UC_YouTube_V2_by_ansar
At this point, I'm ready to follow point by point the instructions in the Hermes Upgrade Guide, but I have a lot of questions about what each of these software is, what they do, how they should be installed or run.
Bottom line: I'm terrified!
That's why I would love to find a kind mentor and helper, to hold my hand and direct me in the actual upgrade.
Anybody? Please PM me. I am available on Skype. I live in Toronto, so my hour is same as New York.
I have an HTC Hermes 200 (TyTn), originally from Rogers (Canada). I had it unlocked (SIM unlock?) by a technician in a store a while back and I can use different SIM cards with it.
Very gratefully yours,
ML
P.S. Forgot to mention: I'm working on a Windows 7 Home Premium and I did update the drivers with "x64 AS Drivers Win 7 Tested & Working"
Goooooooooooood is it work with my herm 200
I sent a "Quick Reply" yesterday, but I can't see it anywhere - ?!
So here I go again. First of all, I want to thank you for writing - as you might have noticed, nobody else had anything to say in response to my post, certainly nobody offered to help.
Secondly, I'd like to ask if you installed Josh's "Springtime" ROM to your HTC Hermes and, if so, how is it working for you.
I'm having problems with it: various sounds (especially when booting, but not only), various "phantom screens", i.e. screens that flash so fast that I don't get to see what's on them, but appear empty. Also, today, when attempting to pair a BT headset, the device froze. The only way to fix it was a hard-reset, thus a reinstall of the ROM (lost all data...). Tried again the pairing with the Bluetooth headset - this time it worked. Loaded data again OK. Made a change in the order of the items in the Today screen OK. Tried to have a look at the insides of the device with "My Mobiler" and - without my actually doing anything, my Hermes is now - again! - frozen.
I'm getting fed up with this, it gives me no confidence at all in the ROM. Any thoughts?
Ily426
Ily426 said:
I sent a "Quick Reply" yesterday, but I can't see it anywhere - ?!
So here I go again. First of all, I want to thank you for writing - as you might have noticed, nobody else had anything to say in response to my post, certainly nobody offered to help.
Secondly, I'd like to ask if you installed Josh's "Springtime" ROM to your HTC Hermes and, if so, how is it working for you.
I'm having problems with it: various sounds (especially when booting, but not only), various "phantom screens", i.e. screens that flash so fast that I don't get to see what's on them, but appear empty. Also, today, when attempting to pair a BT headset, the device froze. The only way to fix it was a hard-reset, thus a reinstall of the ROM (lost all data...). Tried again the pairing with the Bluetooth headset - this time it worked. Loaded data again OK. Made a change in the order of the items in the Today screen OK. Tried to have a look at the insides of the device with "My Mobiler" and - without my actually doing anything, my Hermes is now - again! - frozen.
I'm getting fed up with this, it gives me no confidence at all in the ROM. Any thoughts?
Ily426
Click to expand...
Click to collapse
to BT headset you can try the way of sas90850 in http://forum.xda-developers.com/showthread.php?t=273105&page=2
Thanks for the suggestion - I'll check it out.
In the meantime, my HTC Hermes (with its new "Springtime" ROM, installed and re-installed several times) continues to freeze at various times, for no reason I can fathom. I'm not a happy camper...
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Potentional Tutorial
philipkroberts said:
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Click to expand...
Click to collapse
philipkroberts said:
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Click to expand...
Click to collapse
Also looks like im getting the Star N9589 just due to the more support available.
Anyhow until then, failing any answers from here, another chinese forum a spanish one and Yahoo answers I am going to go with the following method, If it dies, It dies this was my own fault for not doing enough research and at least it lets others know. I would send it back to DX But cba with postage fees and the hassle;
THIS IS DONE AT YOUR OWN RISK! -
APOLLO ONE - MTK 6589 K6589
Please note all tools and zip files mentioned I cant link to yet should you feel you want them please post in this thread and I will PM you, Gotta get my post count up first!
Guide by philipkroberts Twitter @philipkroberts
Revision 1 - People to be added to credits for leehed source, currently untested, concept only
Before anything try and boot into any form of recovery mode and backup if possible!
DISABLE UAC in WINDOWS 7
RIGHT CLICK RUN AS ADMIN ON ALL FILES
ALLOW NON TRUSTED DRIVER INSTALLATION (Google this if unsure)
On the phone install anububu on pc phone. - See what model it detects as and note it down.
Run MTK DROID TOOLS and connect phone see if drivers After a few seconds, the box should turn blue, and it should say "Apollo ONE or Other Name " besides it. The drivers are working.
If not try the other drivers in the drivers folder using device manager, there are many tutorials for this I cba typing one im so tired! and make sure you have the only trusted drivers thing turned off, if you constantly get unknown driver then your out of look and wil have to try and source some yourself.
Win7 (This method has not been tested by myself. Confirmation required.)
HOW TO MANUALLY INSTALL ANY DRIVERS IF NEEDED
a - Downloading This tool Called EASYBCD
b - Use it to restart your computer in advanced boot mode. (PRESSING F8 WHILST BOOTING UNTIL YOU GET THE OPTION FOR Disable signed driver enforcement)-Must be done everytime you wanna root a phone with this method.
c - Follow instructions and disable SDE.
d Manually install drivers, if above did not work (Yellow sign issue)
e Navigate to control panel - > Hardware and Sound - > Device Manager
f You should see a driver notice with a yellow warning sign next to it.
g Right click on it and choose "Update driver..".
h- Manually assign drivers, usually the choice furthest down.
i- In the window which should have appeared, navigate to the preload/Mt6590 folder and press OK.
j- If SDE is turned off, you should see a red warning window. This is normal, just accept the message prompted.
k- The drivers should now be successfully installed.
l - Once this is done open C:\Users\Hate\Desktop\Chinese Droid Rooting\MTKROOT TOOLS\Root_with_Restore_by_Bin4ry_v28\runme.bat Hope it ****ing works if so your rooted, If not try this next few steps, AGAIN at your own risk, no need to format just continue from here.
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
0 - Use PC to copy UPDATE-SuperSU-v.1.25.zip to the root of SD CARD, do not unpack just leave whole zip there.
1 - Turn off your phone, remove your battery. (Do not connect your phone to the computer yet!)
2 - Navigate to the "SP Flash Tool" folder, and run the tool.
3 - On the right side of the tool, there should be a button, iconed with a folder, named "Scatter-Loading". Click this.
4 - Navigate to the "Yulypis Recovery" folder, and double-click on the "Mt6589_Android_scatter-emmc.txt".
5 - You should be back at the SP Flash Tool start-screen, and there should have appeared a list of text and hex-codes.
6 - The "Recovery" line, should be ticked off, and preloader should be red.
7 - Now, click on the button named "Download", with a blue arrow on it. Press "YES" on the NOT ALL images has been correctly loaded warning.
8 - Connect your phone to a USB 2.0, with removed battery. The program should now work, and if drivers is set up correctly, the 0% will turn 100% and a green circle will appear in the middle of the screen. If your phone disconnects before the flashing tool is able to recognize your device, try putting the battery back into the phone before running SP Flash tool. Additionally, if this doesn't work, try using different drivers in the drivers folder
9 - Disconnect your K6589 from the computer when you see the green circle, insert the battery and boot the phone. Wait for it to get to the start screen.
11 - Installing SuperSU through Yulypis recovery
12 - Run "MtkDroidTools.exe" from the folder.
13 - Connect your device, and after a few seconds, information about your device should appear.
14 - Click on reboot, on the mtkDroidTools start-screen, and choose "..recovery".
15 - If recovery has been properly flashed, your device will now enter Yulypis recovery. Blue, with english text.
16 - Controllers: "Power = Enter, Initialize", "Volume down = Scrolling down". (Don't remember if volume up was bugged or not)
17 - Enter "Install zip from SDcard" - > Navigate to the earlier copied "UPDATE-SuperSU-v.1.25.zip and initialize it by pressing the power button.
18 - Follow the on-screen instructions, and it should be prompted to install after 1-2 more screens.
19 - Reboot the device by clicking on "+++++back+++++" and "Reboot now / Reboot Device".
Either way I am going to smash this in a week or so when the phone arrives from DX and will keep people update.
Peace
Please I want to buy this phone. Can you answer me a few doubts I have?
- How is the viewing angle? Cause i purchased a tablet from china and the angle is very bad.
- Has proximity sensor?
Are you ok with the phone?
thank you.
cabrote said:
Please I want to buy this phone. Can you answer me a few doubts I have?
- How is the viewing angle? Cause i purchased a tablet from china and the angle is very bad.
- Has proximity sensor?
Are you ok with the phone?
thank you.
Click to expand...
Click to collapse
I'm still awaiting the phone, hence why that guide is at your own risk.
However from what I have been told and gather that should root the phone no problems.
As for custom roms, I wouldn't even bother trying!
Once the phone gets here I will test my tutorial and re-write it into a more easy on the eyes fashion.
Thanks
http://www.fastcardtech.com/APOLLO-ONE-K6589?u=37825
They sell the phone, for an extra $3 they root before sending.
It cant be that hard, I'd love to know someone in that factory!
I'm looking for a link to download the full stock firmware for this device.
Anyone, please?
...or at least a firmware dump from a non-modified working phone.
One could use MTK Droid Tools and SPFlash to perform this task easily.
PM me for assistance if you need it.
Thank you.
Phone: HTC MyTouch 4G Slide
Android version 2.3.4, HTC sense version 3.0
Issue: No HTC Sync on device / Attempting to root.
Either looking for help on getting HTC Sync to complete this guide - or an alternative method to root the phone. Either or. Thanks in advance.
I have an HTC, and apparently to get bootloader / fastboot unlocked, i need to hvae HTC Sync - but when i go to Connect to PC options, HTC Sync is not an option. Doesn't appear to be on my phone.
I have been following this guide, to ultimately root my phone. That's my main goal.
Increase batt. life, performance, and take advantage of hacked mod/apps.
Please help. I am basically stuck at Step 4 of this guide: http://forum.xda-developers.com/show....php?t=1801106
And since step 4 of that guide is another guide, i'm stuck at Step #8 , because it is "waiting for device" permanently. http://www.htcdev.com/bootloader/unl...uctions/page-3
I have googled, and well, my computer's HTC Sync program, should be able to read my device, and it does not(Win7, i ran as admin, etc.) I have rebooted phone under fastboot, and I believe followed all necessary steps according to those guides, unless i missed something, but i read it completely before beginning to make sure i understood everything, before actually beginning.
If anyone has any insight, I would appreciate it.
This phone is still the best qwerty kb phones on the market, so I do not want to upgrade to a new phone, but increase performance/batt life by rooting.
bump--
Still looking for help
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Twink225 said:
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Click to expand...
Click to collapse
It's hard to understand all of that but it sounds like perhaps you deleted some bloat that you should have, you sound like having driver issues, and possibly wrong TWRP version. Need to clear that up and then reinstall the stock Disney ROM.
I'd start here it has all the tools/TWRP/ROM's you need.
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
So sorry hun, toshiba is driving me nuts and I'm having a bad add moment or three lol. I read about you retiring. so I tried hard not to bother you. now I'm really confused. I've read your nabi2 general info post and even ran across your youtube vids. the problem is I'm not familiar with adb. & the included NabiLabGUI drivers, win10 either fails to finish saying it was interrupted. or it just won't install the 32 bit drivers, I thought I as suppose to use.
The 64bit driver 3 out of 4 install but, I can not get the Google Inc, driver to install properly even with the inf file. (ie the android_winusb.inf ) it says the system can't find the file, it can install the older versions from NabiLabGUI or naked drivers. but doesn't show in add/remove and it still won't detect the tablet most of the time lol.
Pda also has conflicts with adb, I got the nablab disney option to detect it but still failed to install twrp saying it can't find devise and I noticed in device manager 2 driver problems that will not let me update manually or they go missing if I try to force windows to reinstall. (device descriptor request & set address failed)
I must be missing something big, I also tried the 15sec and minimal adb. I assume because the tablet won't fully boot up, windows doesn't know what to do with it. when I tried different cables. windows 10 enterprise won't play nice at all now. so I will format again to be safe but lost what to try next.
I guess my questions should be is there a work around or a full inf version of the newer drivers for NabiLabGUI2015 that might work with this demonic disney nabi2.
&
Is NabiLabGUI compatible with .net framework 4.6 advanced services? (I may have to downgrade o/s. on the nabhacks site is says .net 4.5 is a prerequisites.) I don't know much about the app but saw 4.6 comes preinstalled, I can't install 4.5 yet, I saw there has been compatibility issues. and it won't let you revert versions easily if at all.
I'm to tired of this tab to think straight anymore and so grateful any help I'm in way over my head here.
Update
I lost the battle but I won the war, now google & supersu are messing with me as usual but it boots so I win lol :victory::silly: