Related
New G Tablet
tried to install
ClockworkMod v2.5.1.1-bekit-0.8
and
VEGAn-GE-7.0.0-RC1-Harmony-signed
Tethered, no microSD
Copied files and installed CWB
Said it installed VEGAN
Upon reboot...
Stuck on Bird Screen. After 20 mins, I rebooted to CWM
When I go into CWM to choose zip, it says No files found
Even when tethered, it won't connect so I can see or copy files to tablet.
Thanks for your help.
nvflash is your friend
thebadfrog said:
nvflash is your friend
Click to expand...
Click to collapse
This link will take you to your friend...
http://forum.xda-developers.com/showthread.php?t=861950
read the whole thread for the ROM you're trying to install. nvflash. it's mentioned tons of times in that thread as a fix for this exact issue.
(only know because i did the exact same thing like two nights ago)
good luck!
THANK YOU!!!
The steps on http://forum.xda-developers.com/showthread.php?t=861950
fixed it.
Linking already compiled FOTA binary working with S8500XPKJ1 bootloaders only.
It needs the same files on User partition as described in tutorial.
Remember that you flash it on your own risk.
It's version 3.0 - may work, or may not.
http://code.google.com/p/badadroid/downloads/detail?name=S8500_XPKJ1_bl_univ_bootv.0.3.zip
Rebellos said:
Linking already compiled FOTA binary working with S8500XPKJ1 bootloaders only.
It needs the same files on User partition as described in tutorial.
Remember that you flash it on your own risk.
http://code.google.com/p/badadroid/downloads/detail?name=S8500XPKJ1_armlinuxboot.zip
Click to expand...
Click to collapse
Thanks! I'll try it tomorrow!
Sorry if it's an idiotic or noobish post, but I just want to make sure:
I have to install S8500XPKJ1 (bada 2.0) then flash this FOTA and I should be able to load Android just like before, right? Thanks!
i flashed the new 2.0 fw with this fota and got no problems. Will install android and report if any issues.
thanks Rebellos
I tried with the above given FOTA file
i had no problems in booting into bada
but while booting ANDROID i get oly white screen--tried about 10 times...
may be cld hav tried wrongly
Anyone else able to boot ANDROID using this fota with mentioned new firmware in phone..
indiamachi said:
I tried with the above given FOTA file
i had no problems in booting into bada
but while booting ANDROID i get oly white screen--tried about 10 times...
may be cld hav tried wrongly
Anyone else able to boot ANDROID using this fota with mentioned new firmware in phone..
Click to expand...
Click to collapse
Whitescreen with any text on it?
What key combination are you using? Ain't sure if it haven't changed.
Recovery mode is Menu+VolUp
Download mode Menu+VolDown (or Menu alone should work too)
Normal kernel boot is CallKey
Otherwise Bada does boot.
Please test it carefully, I couldn't do it by myself yet.
Rebellos said:
Linking already compiled FOTA binary working with S8500XPKJ1 bootloaders only.
It needs the same files on User partition as described in tutorial.
Remember that you flash it on your own risk.
http://code.google.com/p/badadroid/downloads/detail?name=S8500XPKJ1_armlinuxboot.zip
Click to expand...
Click to collapse
which kind of installations ? install on Nand or Memory Card ?
Flashed with S8500XPKJ1
Flashed the fota available in the first post
Copied all the needed files to boot Android.. but what I obtained is the Wave that:
Start Bada regurarly
Start the process to install Android (VolumUp+Menu+EndCall) and show me a screen with some pixels around.
What should be?
Please get me a picture of that screen.
I should have done it before, sorry.
And sorry for the bad quality too.
Here you are a photo just to give you an idea.
http://img507.imageshack.us/img507/5314/dsci0005gd.jpg
@Rebellos
A plain white screen with some pixel dots
I used Vol down+lock+power button for going into download mode
Then used power+menu+vol up button thnkin cld boot into android first time (set up the file system)
Then used power+call key to boot into android
But it dint work
FYI, i used the NAND method...
Regards,
Indiamachi
This is to boot ARM Linux or Android?
I think title may lead to misinterpretation
UP,
android ;]
Android is ARMLinux kernel + Zygote & Dalvik AFAIK.
I'm working on solution.
It really doesn't work. When you try to get into the Recovery Mode or to lauch Android, pixels are displayed like in the bada 1,2 version, but there after these pixels the Galaxy S logo is displayed, and here no reaction.
i tried it... but it doesn't work ! it doesn't even show galaxy logo. And whr can i get the files needed?
AltairBW said:
It really doesn't work. When you try to get into the Recovery Mode or to lauch Android, pixels are displayed like in the bada 1,2 version, but there after these pixels the Galaxy S logo is displayed, and here no reaction.
Click to expand...
Click to collapse
john1995 said:
i tried it... but it doesn't work ! it doesn't even show galaxy logo. And whr can i get the files needed?
Click to expand...
Click to collapse
Answer has given :
Rebellos said:
I'm working on solution.
Click to expand...
Click to collapse
Cannot start Android on Bada 2.0
I am using Modifed S8500XPKJ1. I have loaded the new fota.
I have loaded the android filesystem in memory card and tried to start it but everytime after the flickering the galaxy logo do not appears / android do not start when I press Call+Power button.
I've updated first post with v2.0 - please test it now.
Rebellos said:
I've updated first post with v2.0 - please test it now.
Click to expand...
Click to collapse
Thanks
will try it out after phone battery is full
Not sure what happened here. But basically took a totally stock US ATT Unlocked streak and tried upgrading to the Gingerbread 2.3.3 version. Upon doing this, everything flashed correctly but I was stuck at the Dell screen-15 minutes. Pulled the battery and same thing, pulled it again and it actually started loading up. It loaded up and immediately force closes a bunch of things. Tried flashing it again with no luck. Tried flashing the latest ATT recovery with update.pkg and again, stuck at Dell screen. However if I flash CWM and load a custom ROM, it will load into the ROM but immediately force closes everything and it also isn't reading my SIM card. What the heck did I do?! Please help
could we have more details about your flashing procedure?
Have you done a wipe of the dalvik cache and a factory reset? Skipping those two are the most common cause of FC's.
Sorry guys. Initially. I installed the fast-boot drivers, got the phone in fast-boot mode and recognized by the PC. Gather the correct files and flashed the 407 recovery, rebooted and then flashed the update.pkg through the stock recovery manager.
After this failed. I flashed CWM. Wiped it totally and then tried two different custom roms and also installed the amss and dsp1 and still both would instantly start force closing.
I'm a desperate move I did QDL last night and everything was successful, however I attempt to install the latest stock recovery and update.pkg and I'm still getting stuck at the Dell logo.
Try the recovery from 360.
kurdo_kolene said:
Try the recovery from 360.
Click to expand...
Click to collapse
From my understanding. QDL sets the phone back to 305 recovery to be flashed. Should I try installing that, or as soon as QDL finished install the 360 recovery with the 360 update.pkg?
flash the 360 recovery in fastboot mode, reboot into recovery mode and install the 407 update.pkg. After it is installed do a factory reset.
That method isn't working. I flash the 360 recovery in fast boot and loaded the 407 update to the SD card and renamed it. Upon flashing the update I get a "error in SD card \SDcard\update.pkg.dec"
Do I need to add that extension or what's going on here? I'm using the files provided on the Dell Wiki Rom list btw.
quickbird144 said:
That method isn't working. I flash the 360 recovery in fast boot and loaded the 407 update to the SD card and renamed it. Upon flashing the update I get a "error in SD card \SDcard\update.pkg.dec"
Do I need to add that extension or what's going on here? I'm using the files provided on the Dell Wiki Rom list btw.
Click to expand...
Click to collapse
On the wiki page there is also a link for hashes. Click on it and compare the hashes listed with the hash for the file on your local computer. If you have a bad DL the hash will not match.
If the hash matches then try using the 407 recovery, instead of the 360.
Also see this post in case you are coming from 347. I guess that there are issues updating from BB 347.
The easiest way to generate a hash for files in Windows (IMO) is to use the HashCheck shell extension. You right click on a file in Windows Explorer, select properties, and then a tab to view the hashes for a file.
marvin02 said:
On the wiki page there is also a link for hashes. Click on it and compare the hashes listed with the hash for the file on your local computer. If you have a bad DL the hash will not match.
If the hash matches then try using the 407 recovery, instead of the 360.
Also see this post in case you are coming from 347. I guess that there are issues updating from BB 347.
The easiest way to generate a hash for files in Windows (IMO) is to use the HashCheck shell extension. You right click on a file in Windows Explorer, select properties, and then a tab to view the hashes for a file.
Click to expand...
Click to collapse
I've followed everything you just said. I've checked hash files and all are matching. However when you talk about 347, I QDL'd and it put the recovery back to 305 unlocked.
I try to update viaSD card immediately after but it says it can't find the update blah blah. So from 305, I want to flash the appropriate recovery either 360 or 407 and install the 407-update.pkg correct? Then after it reboots from there, do a factory reset? I feel as if I'm very close, just gotta find the right tunnel. I do greatly appreciate all of the help thus far!
Here's a little update to bring everyone where I'm at.
I QDL and then flashed the 407 recovery. Grab the 407 update, rename it and put it on the SD. I flash via update from SD card, everything goes by. It reboots and I'm still stuck at the Dell logo.
After about 15 minutes of this, I pull the battery and then it goes to "Start recovery copy" and then reboots. Then brings me BACK to flashing the stock recovery but this time wants me to flash the 305 recovery??
quickbird144 said:
I've followed everything you just said. I've checked hash files and all are matching. However when you talk about 347, I QDL'd and it put the recovery back to 305 unlocked.
I try to update viaSD card immediately after but it says it can't find the update blah blah. So from 305, I want to flash the appropriate recovery either 360 or 407 and install the 407-update.pkg correct? Then after it reboots from there, do a factory reset? I feel as if I'm very close, just gotta find the right tunnel. I do greatly appreciate all of the help thus far!
Click to expand...
Click to collapse
If you flashed back to 305 with the QDLTool and can get to fastboot I suggest:
Put the rom file on your SD Card. Make sure it is named update.pkg.
Use fastboot to flash the recovery that matches the ROM, in this case the 407 recovery
use fastboot reboot from the command line to reboot the phone and hold down both volume buttons as it reboots to go directly to the 407 recovery you just flashed. Do not let the phone boot normally or you will have to start over.
Now select the second option to update to 407.
This will wipe all settings, apps, ect., from the phone.
---------- Post added at 12:02 PM ---------- Previous post was at 12:00 PM ----------
I believe that we cross posted. If you have done the steps in my previous post and are still stuck when you flash the 407 recovery also flash the dsp1.mbn and amss.mbn files for 407 then reboot immediately to recovery and do the update.
The phone is pretty much dead now so I'm going to let it charge before I give it another go.
But I believe my problem is dsp1 and the amss files. That's one step that I have not done yet. I think I'm going to QDL again and from there do as you stated.
I did have one question though. My phone was factory unlocked, through all this, is that unlock gone?
Thanks again and I will report back with the results!
quickbird144 said:
. . .
I did have one question though. My phone was factory unlocked, through all this, is that unlock gone?
. . .
Click to expand...
Click to collapse
From what I have read flashing a ROM does not effect the unlock status. I also have an unlocked Streak but have never used it with any other carrier except AT&T so I can not comment from personal experience.
FIXED!!!
I'm back in business!!!
I used the QDL streakflash then the QDL repair tool. Didn't feel like messing around with all those update.pkg's and stupid recoveries so I just flashed CWM recovery, flashed the basebands for Ginger Streak 2.4.4 and it's back up and running!!!!
THANKS A LOT to everyone that helped. I've lost tons of sleep over this and have been up all night trying to get this right and it all paid off. I'm happy
quickbird144 said:
I'm back in business!!!
I used the QDL streakflash then the QDL repair tool. Didn't feel like messing around with all those update.pkg's and stupid recoveries so I just flashed CWM recovery, flashed the basebands for Ginger Streak 2.4.4 and it's back up and running!!!!
THANKS A LOT to everyone that helped. I've lost tons of sleep over this and have been up all night trying to get this right and it all paid off. I'm happy
Click to expand...
Click to collapse
congratulation!!! somehow i just can"t go back to stock rom
Glad you got it going. . . . Done the QDL tool acouple times myself
posted from my Pimped out Dell
I am on vacation and my fassy decided to stay in recovery upon boot. It gets stuck in boot loop. I'm running AOKP Build 30 w/ Glitch. My fiance has a macbook with her however, everything I've read says that we can't use Mac for rooting or restoring fassy's. Is there anyway to get out of the boot loop with an option in clockwork. From what I understand we can't use the two button hard boot with ICS roms. I could use some help, I'd rather not be without my phone for a week.
Thanks guys
Keuka79 said:
I am on vacation and my fassy decided to stay in recovery upon boot. It gets stuck in boot loop. I'm running AOKP Build 30 w/ Glitch. My fiance has a macbook with her however, everything I've read says that we can't use Mac for rooting or restoring fassy's. Is there anyway to get out of the boot loop with an option in clockwork. From what I understand we can't use the two button hard boot with ICS roms. I could use some help, I'd rather not be without my phone for a week.
Thanks guys
Click to expand...
Click to collapse
Is there anyway to access a Windows computer? With Parallels, VMWare, a virtual computer lab, or something else?
If so, follow http://forum.xda-developers.com/showthread.php?t=1238070
If no, Hiemdall http://www.glassechidna.com.au/products/heimdall/
Goodluck
Apparently there's no driver for samsung fascinate with mac connectivity. I downloaded Heimall and the full tar package but didn't work. Does anyone know how to generically attatch my phone to the computer. Someone said something about a generic connection as a drive that works with heimall. I'm pretty pissed and can't seem to get this work. I'll pry end up just going down to a lab and hogging that for thirty minutes or so.
Heimdall has its own driver. It'll be in the driver folder in the suite. Also I'd use an older version of heimdall suite if you can. The newer version tried to streamline things but ended up being a downgrade IMO.
Sent from my SCH-I500 using xda premium
I tried to use Heimdall but couldn't locate the driver. I then located a "exitrecovery.zip" that was supposed to be flashed in cwm. I used my gf's phone to download it then switched sd cards and that didn't work. Still stuck in cwm loop. I can't get to a pc where i can download Odin software to. There's no other flashable file i can find to help me get out of this loop.
look at section 9 of my guide...I always keep a cm7 rom on my sd card just incase this happens!
Can I flash a cm7 rom if i'm stuck on a cm9 bootloop??
Keuka79 said:
Can I flash a cm7 rom if i'm stuck on a cm9 bootloop??
Click to expand...
Click to collapse
READ section 9 of my guide in the general section...
droidstyle said:
READ section 9 of my guide in the general section...
Click to expand...
Click to collapse
Thanks man, I got it to work. I'm surprised I didn't think of that before.
You're a life saver man.
No problem, glad to see you got things back up and running!!
ATTENTION EVERYONE (For everyone who attempted to install this ROM):
This ROM breaks the Tab splash screen and does harm to the Tablet.
I recommend calling 1-800-SAMSUNG, and ask for a factory re-flash. Do not say anything that you are / were rooted. This should be 100% free, they even pay for shipping. They did mine for free. I recommend doing this ASAP, before more damage might come to the Tablet.
Downloading and testing, do you need anything else? Like the twrp?
edit 1:
Impossible to install, the updater is badly configured, I can not locate the problem, even with normal recovery will not let me install, I will continue to try
edit 2:
Well I found the error, the rom is not well developed, did you do with some automated program? I remember that the tablet 10.1 has another processor and that the compatibility of a direct port without changing the drivers is impossible
jimmy999x said:
Downloading and testing, do you need anything else? Like the twrp?
edit 1:
Impossible to install, the updater is badly configured, I can not locate the problem, even with normal recovery will not let me install, I will continue to try
edit 2:
Well I found the error, the rom is not well developed, did you do with some automated program? I remember that the tablet 10.1 has another processor and that the compatibility of a direct port without changing the drivers is impossible
Click to expand...
Click to collapse
I made it on ES File Explorer, on my Nook, it took me an hour... I had ported it from Acclaim RC5 and Docker 6 Degaswifi, and I changed the updater script to say, "degaswifi", for the device. and I changed the build prop, to be the same cpu, exc... as the tab 4. I used Degaswifi Docker 6 boot.img and recovery folder, and some other important stuff in the system folder. What is the error are you getting?
secretwolf98 said:
I made it on ES File Explorer, on my Nook, it took me an hour... I had ported it from Acclaim RC5 and Docker 6 Degaswifi, and I changed the updater script to say, "degaswifi", for the device. and I changed the build prop, to be the same cpu, exc... as the tab 4. I used Degaswifi Docker 6 boot.img and recovery folder, and some other important stuff in the system folder. What is the error are you getting?
Click to expand...
Click to collapse
Even using other twrp I still can not install, use the recovery and the boot image I found 2 weeks ago, I even deleted the first line and it looked like it would install, but these errors appeared
jimmy999x said:
Even using other twrp I still can not install, use the recovery and the boot image I found 2 weeks ago, I even deleted the first line and it looked like it would install, but these errors appeared
Click to expand...
Click to collapse
Can I see what you had edited?
Only the first line of the updater inside google folder
jimmy999x said:
Only the first line of the updater inside google folder
Click to expand...
Click to collapse
What is in the first line? The new updated one, that you had did?
secretwolf98 said:
What is in the first line? The new updated one, that you had did?
Click to expand...
Click to collapse
this
jimmy999x said:
this
Click to expand...
Click to collapse
strange
I'll look into it later
jimmy999x said:
this
Click to expand...
Click to collapse
Question, after you flashed this rom, did the Splash Screen disappeared on the Samsung?
Because the both versions that I had made, broke my Samsung Splash Screen.
secretwolf98 said:
Question, after you flashed this rom, did the Splash Screen disappeared on the Samsung?
Because the both versions that I had made, broke my Samsung Splash Screen.
Click to expand...
Click to collapse
If, in fact, they stop seeing the logos of samsung when turning on and when entering the download mode, the only way to correct that is to install the official firmware
jimmy999x said:
If, in fact, they stop seeing the logos of samsung when turning on and when entering the download mode, the only way to correct that is to install the official firmware
Click to expand...
Click to collapse
so it did for you, when you flashed official PA1 firmware threw odin? did the screen that broke say, "Samsung Galaxy Tab 4 7.0 SM-T230NU Powered By Android"?
Interested to get this rom running smooth on our tabs