Hello,
I installed GingerStreak2.4.4, and it worked just fine for about 2months, one day I was playing some kind of soccer game where you have to swipe to give a direction to the ball, I stopped playing it and just let my streak on a table until it got discharged, I turned it on until the next day after charging it for a while, and my surprise was that the touchscreen became unresponsive.
I tried to re-install it with different densities, different launchers, I think I tried all the possible configurations in the intstall.txt (I cleaned dalvik machine and all that stuff prior to every new installation), I tried the Screen Calibration, wich it says that is correctly calibrated, but when I enter to the white fastboot screen, and run the tests, the touchpad test only work in a "small rectangle" rather than the whole screen, so I'm afraid that this is a configuration issue.
So, in order to discard any possible damage to the touchpad, I would like to be able to install .pkg files again, since that's the format the Stock ROM have (right now is only accepting .zip files). So I need to revert the recovery tool that I had to install before installing the custom ROM. Do you guys know how to revert the recovery, or to run .pkg files again at least?
Thanks in advance!
To change recoveries, follow the procedure you used to install StreakMod Recovery on the Streak in the first place. Just make sure it's a stock recovery you install.
From there, assuming that this is not a hardware issue, you should be able to install the stock ROM. After that, install DSC 0.7 instead of GingerStreak. GingerStreak's code is based off a beta version of the 407 ROM, whereas DSC is based off 407 itself.
Related
I install the clockworkmod for set up the GTAB rom...
but now i want to return to the stock recovery...so how to uninstall clockworkmod?
thanks!
savage,
You install CWM to replace the stock recovery. Therefore, you have to re-install the
stock recovery. If you were using a stock rom like say 3588, you would just reinstall
the rom again and let it overwrite CWM.
But since I don't know what rom you are using, you need to check the source of
your rom, make sure it contains the stock recovery -- and then inquire of the issuer
of the rom whether or not you should re-install or do some other special procedure.
Rev
thanks！ Now i am using the VEGAn-Tab Build rom~
so what should i do next?
sorry for the confusion~
GTAB ROM is not granular enough - you running stock or a modded ROM? If so, which ROM?
I can reply for TNT Lite 4.3.0+ or gADAM 1.3.0+ - there's a script setup to go back to standard recovery. If you are running either of these, please see my first posts on those ROMs for instructions on what to do. Again, this is only if you are running TNT Lite or gADAM.
You can also attempt to flash standard recovery using a build 3588 standard recovery firmware image in PART3 here: http://forum.xda-developers.com/showthread.php?t=1005080
savage,
EDIT: roebeet answered you first so I'll just stand by and see what y'all do.
Good luck!
Rev
thanks！ Now i am using the VEGAn-Tab Build rom 5.1.1~
so what should i do next?
sorry for the confusion~
problem with installing CWM
I got my gtablet yesterday and tried to install CWM v.8 using external micro SD card. It looked like it was half way done because it could not reboot by itself and stuck at a screen asking for reboot. So I selected reboot but it did not reboot. I had to force it to close. When I pressed volume+ and power, it had this message on the upper left coner: Recover key detected, booting recovery kernel image and 3 birds in the middle of the screen. It stuck there forever without doing anything. I only installed Z4root and nothing else. How can I remove the half-done CWM and redo it again. If I can do it again, what should I look out to avoid the same error?
yu203964 said:
I got my gtablet yesterday and tried to install CWM v.8 using external micro SD card. It looked like it was half way done because it could not reboot by itself and stuck at a screen asking for reboot. So I selected reboot but it did not reboot. I had to force it to close. When I pressed volume+ and power, it had this message on the upper left coner: Recover key detected, booting recovery kernel image and 3 birds in the middle of the screen. It stuck there forever without doing anything. I only installed Z4root and nothing else. How can I remove the half-done CWM and redo it again. If I can do it again, what should I look out to avoid the same error?
Click to expand...
Click to collapse
If you got your tablet yesterday, then it probqbly had firmware 1.2.4349 on it, which is a 1.2 bootloader firmware. You tried installing a CWM made for a 1.1 bootloader. how much research did you do prior to modding? Seeing as you installed Z4root, I'd imagine that you didn't do much, as it's not needed at all to root your G-tab.
go to http://viewsonic-gtablet-for-dummies.webs.com/ and start reading at "START HERE" to get an idea of what your dealing with, and what you can and can't do...look through the entire site!
to get out of where you are now, and back to a workable base, follow the "CODE RED" instructions here: http://viewsonic-gtablet-for-dummies.webs.com/
Lastly...don't do anything else silly until you've read and understand all of the instructions on Goodintentions site...it's a GREAT resource and should be a pre-requisite for all new G-Tab owners.
I have an odd problem. My Dell Streak will boot but once it gets into the OS none of the buttons are responsive. It is not frozen however. I've recalibrated the touchscreen but that does nothing.
However, the controls work when I am booted into recovery and the screen before fastboot.
The person I bought it from had tried to install StreakDroid but I'm not sure how he went about it. I followed the guides, flashing the correct amss and dsp. But I have the same issue.
I'm wondering what the problem could be. Should I try and flash the original Dell rom back on first and see if that works? It is just odd that everything works except when it has booted into Android.
I'm going to assume you have a custom recovery on there. If so, make a nandroid backup, flash a stock recovery, update via the matching pkg file, flash StreakMod recovery, then restore your nandroid backup. That will ensure all the firmwares "match", which could be causing your problem. It sounds like you aren't sure of the history of the roms and such on this phone. This will start you out at square one without losing your custom rom and settings. Certainly couldn't hurt.
I've tried to install the stock pkgs (I tried 360 and 319) but both stop working at the end of the install. How long is the install meant to take? Because I've left them for half an hour at the end but it hasn't completed
Hello. I'm a 55 year-old newbie to the wonderful world of Android, courtesy of my kid's continuously-rebooting Dell Streak 5 (AT&T, USA). It all started with the Froyo 2.2 OTA update in late 2011. The Streak would not boot after that update completed (WiFi - FIOS). We called Dell, and they advised that we Factory Reset it. That worked, and we thought all was well. Now several months later and 2000 factory resets later, my kid requested an iPhone for Christmas, and I re-claimed the Streak. I called Dell last week, and of course they wasted several hours of my time, ultimately telling me that my phone was out of warranty, but that for $249 I could buy a new phone. I advised several reps and a supervisor that Dell's OTA 2.2 update caused the problem, and that I should not be charged for any resolution to that problem. End of that story - here I am, after spending all of Saturday and most of Sunday attempting to downgrade back to 1.6. Here's what I have done:
I used SuperOneClick and successfully rooted the phone
I have used many recovery mods, ALL of which seem to lead to a black screen after selecting option 2. However, the Clockworkmod "alternate" recovery method did work. I downloaded a 4399 stock recovery zipped file, copied it to the Streak's SD card, then renamed the entire zipped file to "Update.zip". Then I used FastBoot, and flashed the Clockworkmod alternate recovery "recovery.alt.img" to the Streak. I used fastboot to reboot the Streak, then held the two Volume buttons, selected Option 2, and made my way through the awkward menu - but ultimately I was able to install "Update.zip" successfully. Upon the reboot, I am stuck with the Dell logo. I have tried factory resetting at this point, starting again from "scratch", only to return to the same old story: stuck at Dell logo. I read somewhere that it could take 10 minutes for the Streak to boot, but I have waited for 30 minutes plus.
An hour ago I was too frustrated to continue trying to downgrade to 1.6, so I read this thread: http://forum.xda-developers.com/showthread.php?t=1334487. I used the clockwork 3.0.1.9 recovery method, and attempted to upgrade to 2.3.?. This was not an "alternate" method (which had not worked in two days), but after flashing the recovery.img to the Streak, and using the 2.3.? "Update.pkg" on the SD card, the Streak did begin to verify the package - then it started the update, then - REBOOT. The first time this happened, I waited for 30 minutes, thinking that the upgrade was happening in the background while displaying the Dell logo, as Windows updates sometimes do. But then I yanked the battery, and started that process again. The next time and every subsequent attempt to perform this upgrade results in a reboot as the "verifying package" is occurring.
At this point I feel as though I am spinning my wheels, so I'm putting out an All Points Bulletin for some advice and/or help.
Thanks in advance! John in Dallas
John, have you tried with another update.pkg? The thread you link to is from sreak 7, could that be the issue? If I was you I would try one of the 407 deodexed ROMS from http://forum.xda-developers.com/showthread.php?t=1376896
I did not realize that thread was for the Streak 7. Thanks for pointing that out. I have tried several others, but nothing like what you have provided.
Being new to this technology, I have not yet quite grasped all the terminology and theory. Can I mix and match the recovery images with the Update packages? For example, where "TheManii" states that StreakMod must be pre-installed, then he provides a (407) base_v1.zip , is it OK for me to use the Clockworkmod recovery.alt.img (which has seemingly worked well on my Streak) with his base_v1.zip? Or MUST I use the StreakMod recovery image in conjunction with his base_v1.zip?
I assume that I am supposed to follow the same procedure as before:
- Save the base_v1.zip to the Streak's SD card - renamed to "Update.zip"
- use "fastboot mode" to transfer the recovery.img from PC to the Streak
- boot the Streak into recovery mode, select option 2
- then select the recovery option to load from the "Update.zip" on the SD
How long should it take to install the base and the update?
I understand that the "base" is just that, and I will also need to flash the "update", but the other "bloat" stuff is optional.
I will give this a try shortly - then re-post. Thank you!
I am not the expert here, but from what I've gathered you need the correct recovery image only when you are flashing an official update, since those updates come as encrypted ".pkg" files. I think (please check also the threads on flashing modified ROMs) that ROMs that end on ".zip" are not encrypted and don't need a special recovery file. I hope someone with actual experience on this can confirm if I am correct.
Edit: I just notice that the thread I linked to specifies that installing the matching "pkg" is a prerequisite to installing the "zip" -- this is admittedly more complex than I thought it would be. You are probably better off just installing one of the stock ROMs first just to recover your Streak -- I had recently updated to the 407 (Korean) Gingerbread ROM and like it very much; there are instructions of puttiing it here: http://forum.xda-developers.com/showthread.php?t=1416718
John,
To flash a stock ROM you need a stock recovery.
To flash a custom ROM you need StreakMod Recovery.
Even if the files are not altered any ROM packaged as a zip is a "custom" rom.
To get you started (and get your Streak working) you should flash a stock ROM. I recommend BB 351 as the most stable stock ROM.
Put the pkg file for 351 on the root of your SD card named update.pkg
Use fastboot to flash the 351 recovery,
Use fastboot reboot to reboot the Streak and as it reboots hold both volume buttons to get to recovery
Select option 2 to install 351.
If you decide to use a different stock ROM the instructions are the same, just use the correct files.
If you really want Gingerbread then flash the latest stock GB ROM and then install the DSC version of GB. See the DSC thread in the development section for info.
I've been looking for a downloadable "BB 351" since you posted - cannot locate it. I found the base 351 zipped file, but not the "pkg". Any hints?
Also, when I first attempted that "407 - base_v1.zip" installation, I used clockworkmod, named the base_v1.zip to "Update.zip", and it worked to a small degree. After confirming that the installation was successful, I rebooted the Streak, and after 3 minutes I saw a "O" logo with "elloh" beneath it. Unfortunately it never entered into a "home page" - but rather the Streak reverted to the Dell logo, and that was that.
You might try the links in my signature to find what you need - the wiki is a good place to start.
Edit: the reason you had no success with the zip you flashed is because a ROM flashed from a zip is incomplete. That is why you need to flash the stock rom it is based on first. The ROMs packaged as zips do not install some needed system files, that is why you see instructions to install those first.
You have more reading to do before you understand the process of updating/modding the Streak.
I did locate the BB 351 package just seconds after posting that I could not find it. I've now bookmarked it. I continue to have not-so-good luck.
On the "407" Base_v1.zip installation, suggested by the first poster, the installation went further than any other attempt. I actually saw the "O" with "olleh" beneath it onscreen for a few minutes, but then, poof, it was gone - replaced by the Dell logo. If I am successful, will the Dell logo still be displayed, or will the "O" or some other logo replace the Dell logo upon a successful installation?
After downloading the 351 package and corresponding recovery.img, I reached one point where the status indicator bar reached 100%, but then everything apparently froze. Rather than panic and quickly yank the battery, I left it alone for 15 more minutes. There was no change, so I removed the battery and started again. Now, after many more attempts, I see the "Verifying Update", and then the Streak reboots. Each time I leave it for several minutes in hope that it is installing the Update in the background. But nothing happens. Just reboot after reboot - with Dell logo.
I know that I am very close, so I am not giving up. But I am worn out - PLUS the Super Bowl is starting right now. I'll pick this up again tomorrow night.
If anyone has any ideas or suggestions, please post - remembering that I'm a newbie and may not understand your technical slang, although I am a Telecom Engineer now working exclusively with VoIP, so I am technical. It's been fun tinkering so far, but it would be nice to reach a happy ending! Cheers.
John - North Texas
Thanks for that tip, Marvin02. I do understand. Applying the base was step 1. I did not perform step 2: applying the update. Without the update, the base could not "launch". Unfortunately today I have returned to the wonderful world of IP Telephony, Gateways, UC, and Linux. At this moment I have no battery for the Streak, as I gave it to my daughter during the Christmas break. Yesterday I was using my son's battery, but he returned to college yesterday evening. I ordered a battery last Thursday, and it is due to arrive today. I was shocked to discover that the Streak cannot power on with only external power - it requires a battery.
I also know that I have merely scratched the surface of this technology. After I recover this Streak, I plan to install a ROM Manager, perform a backup, then experiment with other mods. But right now the mission is to revive the Streak paperweight.
Thanks!
ROM Manager and similar apps don't play well with the Streak. Don't use them.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
When you tried to install BB 407 you were installing a gingerbread ROM.
BB351 is a Froyo ROM. There have been some reports of problems reverting from GB to Froyo.
I suggest that you use fastboot to flash:
The recovery for BB 351 or BB 360
amss.mbn
dsp1.mb1
Then reboot to recovery and try installing the update.pkg.
For some reason some Streaks need the baseband files flashed first before the Froyo ROM will install properly. This happened with my Streak when reverting from GB.
blackscreen after selecting option 2
When i select option 2 from the recovery screen it is just a black screen. is there a way to fix this?
upgrade to Longthorn 2.6 is the most one I like
I flash the ROM to Longthorn 2.6. Strictly follow up the step.
My Dell Streak 5 now faster than before, no Dell Stage respone error anymore.
flashing light also resolved (read the instruction in [ROM] Longthorn 2.6 topic.)
Hi,
Issue: After system loads (I get to see launcher/sim unlock screen), couple of seconds later streak reboots. At the same time, leds swich off, than flash and reboot starts.
What I tried (almost all combinations of below points):
restore to factory settings
different roms: DSC v2.3, PCM7-Streak, Mokee OS, Longhorn 2.9.3, some ICS rom
custom recovery images: ClockworkMod 6.0.1.2, StreakMod 0.3.2.8
stock roms with corresponding recovery 366, 360, 369, 406, 407
user QDL tool from streakflash.zip/repairtool.zip do recover to Baseband GAUSB1A130500
booting without sim/SD cards
Things to note:
For flashing I have followed the procedure to wipe data, cache, dalvik, fix permissions, dell factory reset.
In the past I had not issues flashing DSC, PCM7-Streak and other roms.
When booting into service mode? (camera+power button, *#301# code) phone passed all tests (including Internal SD card).
Tests performed with two original dell batteries (one bought 8 months ago, barely used).
Batteries fully charged.
Same issue experienced with custom and stock roms.
The issue started after flashing one of the roms (DSC v2.0 probably).
To be honest I run out of ideas. Please tell me if I missed something?
You didn't say which ROM you were currently running. In any event, it doesn't appear you missed anything. I believe you should try flashing the ROM you're using again. It's possible you got a bad flash, in which case one of the files got corrupted on transfer.
Strephon Alkhalikoi said:
You didn't say which ROM you were currently running. In any event, it doesn't appear you missed anything. I believe you should try flashing the ROM you're using again. It's possible you got a bad flash, in which case one of the files got corrupted on transfer.
Click to expand...
Click to collapse
Thanks for advise.
I have tried starting with with 305 from repairtool.zip working my way up through 360, softbank and Olleh. Stopping at each step and flashing ClockworkMod + DSC. Same applies to any updates to each of mentioned custom roms.
The only thing that I know I could have checked better is the internal SD, just a moment ago found a neat way to get to the Internal SD - http://youtu.be/6w4AbtIGp8A. I might give it a try.
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb