Related
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.
I have a BLU Quattro 4.5 android device and when I try to connect via USB Debug mode and run ADB Device it will not find my phone. I have searched high and low in order to locate the driver with no luck. The generic USB driver from google won't even work. I have even run emulator from the phone and when I type: pm set-install-location 2, it comes back with Killed and then back to command prompt. When I type: pm get-install-location it comes back as 0[auto]. My phones main memory is 1 gb and 1.5 internal usb memory. With all of the main system apps updated on the main drive, the phone cannot handle ANY other apps, even when I put apps on the usb memory it is very sluggish. I need help in trying to install and run all of the apps from the external sd card and just have the system apps running on the main disk. I would also like any help in finding the driver needed to access the phone in ADB.
BLU Quattro 4.5"
4 GB Internal Memory( Broken up to 1 GB Main, 1.5 GB USB Storage, and not sure where the other .5 GB went.)
1 GB Ram
NVIDIA Tegra 1.5 GHZ Quad Core
16 GB Class 10 Micro SD Card
Android 4.0.4 ICS
Unlocked Running Straight Talk/T-Mobile Sim
GOT IT!!!!!!!!!!!!!!!!!!
plymouthrock99 said:
I have a BLU Quattro 4.5 android device and when I try to connect via USB Debug mode and run ADB Device it will not find my phone. I have searched high and low in order to locate the driver with no luck. The generic USB driver from google won't even work. I have even run emulator from the phone and when I type: pm set-install-location 2, it comes back with Killed and then back to command prompt. When I type: pm get-install-location it comes back as 0[auto]. My phones main memory is 1 gb and 1.5 internal usb memory. With all of the main system apps updated on the main drive, the phone cannot handle ANY other apps, even when I put apps on the usb memory it is very sluggish. I need help in trying to install and run all of the apps from the external sd card and just have the system apps running on the main disk. I would also like any help in finding the driver needed to access the phone in ADB.
BLU Quattro 4.5"
4 GB Internal Memory( Broken up to 1 GB Main, 1.5 GB USB Storage, and not sure where the other .5 GB went.)
1 GB Ram
NVIDIA Tegra 1.5 GHZ Quad Core
16 GB Class 10 Micro SD Card
Android 4.0.4 ICS
Unlocked Running Straight Talk/T-Mobile Sim
Click to expand...
Click to collapse
found generic driver from PDANET that finally allowed me to access my phone from ADB and I was able to make the necessary changes. Yippeee! pdanet.co
plymouthrock99 said:
found generic driver from PDANET that finally allowed me to access my phone from ADB and I was able to make the necessary changes. Yippeee!
Click to expand...
Click to collapse
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
londonflu said:
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
Click to expand...
Click to collapse
I have one as well and was able to root it with the latest bin4ry tool! Hopefully Blu will enhance their customer support as they gain more popularity and release some source code or dev tools for the phone. Or at least, since it's rooted, the device can eventually gain support from any devs.
Kah,
Can you post root instructions for us, please?
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Any Information posted in this thread is Great!
I don't mind taking this off track of what the original thread. I like it that it is progressing the way it is, helps me out with other questions and anyone else that starts off with my problem probably wants additional information on what else could be done with these phones.
kah1593 said:
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Click to expand...
Click to collapse
Average
I am still having issues with ram and touchscreen when main storage location gets full. It becomes very unresponsive and the touchscreen becomes very sluggish. Some things I cannot move to the external sd card and all the installed apps still get installed on primary drive even after changing default install location. I need to figure out how to install and run everything, including the android os.
londonflu said:
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
Click to expand...
Click to collapse
plymouthrock99 said:
I am still having issues with ram and touchscreen when main storage location gets full. It becomes very unresponsive and the touchscreen becomes very sluggish. Some things I cannot move to the external sd card and all the installed apps still get installed on primary drive even after changing default install location. I need to figure out how to install and run everything, including the android os.
Click to expand...
Click to collapse
Try using Mounts2SD..
I doubt I'll get much help on this, but I'll give it a shot. I just got my Quattro 4.5 today, and tried to root it with Bin4ry. It never did the first reboot, it just turned the phone off. After a few minutes I turned it back on still connected to USB, Bin4ry tried to finish, but gave a permission denied error on the superuser apk. Now my phone is in continuous boot loop, it gets to the lock screen, but says Go Laucher and system UI has stopped, then reboots. Is this thing bricked? Holding volume down and power just goes to a modem download screen, but no USB connection or anything. :crying:
j21blackjack said:
I doubt I'll get much help on this, but I'll give it a shot. I just got my Quattro 4.5 today, and tried to root it with Bin4ry. It never did the first reboot, it just turned the phone off. After a few minutes I turned it back on still connected to USB, Bin4ry tried to finish, but gave a permission denied error on the superuser apk. Now my phone is in continuous boot loop, it gets to the lock screen, but says Go Laucher and system UI has stopped, then reboots. Is this thing bricked? Holding volume down and power just goes to a modem download screen, but no USB connection or anything. :crying:
Click to expand...
Click to collapse
I'm sorry to hear than man. Which version of Bin4ry did you use? You could try quickly using adb to boot into recovery mode while the phone is still in the process of booting. You'd have to keep sending
Code:
adb reboot recovery
until adb recognizes the device. Hopefully, it'll restart into recovery before it crashes. Not sure if it'll work, but it's an idea.
kah1593 said:
I'm sorry to hear than man. Which version of Bin4ry did you use? You could try quickly using adb to boot into recovery mode while the phone is still in the process of booting. You'd have to keep sending
Code:
adb reboot recovery
until adb recognizes the device. Hopefully, it'll restart into recovery before it crashes. Not sure if it'll work, but it's an idea.
Click to expand...
Click to collapse
Everything is fixed! I figured out how to get into recovery. I was able to do a factory reset from there and everything came back, actually maybe better. Then I found an old version of Bin4ry, v15, and tried again. This time it worked perfectly. This phone is pretty awesome, I just wish there was developer support for it.
j21blackjack said:
Everything is fixed! I figured out how to get into recovery. I was able to do a factory reset from there and everything came back, actually maybe better. Then I found an old version of Bin4ry, v15, and tried again. This time it worked perfectly. This phone is pretty awesome, I just wish there was developer support for it.
Click to expand...
Click to collapse
Great! How'd you manage to get into recovery mode despite the boot loop? In case anyone else runs into the same issue.
kah1593 said:
Great! How'd you manage to get into recovery mode despite the boot loop? In case anyone else runs into the same issue.
Click to expand...
Click to collapse
Hold volume up and power until it turns on. As soon as the screen changes to green, I let go of the power button and keep holding the volume up button until it's in recovery mode. It seems the power button release has to be timed right or else it just sits on the green screen, or powers off again. It takes a couple of tries for me. I probably did 10 factory resets last night before finally getting it rooted, lol. The built in recovery has an option to flash from external storage, kind of makes me wonder how easy this phone would be to get CWM working. Of course, the real problem is getting developers to write the custom ROMs for it. The only thing this $230 phone is missing from its $600 cousins is 4G LTE, but on Tmobile it doesn't even matter right now. It's still blazing fast even on stock with no overclock, I can't imagine how much more awesome it would be with a custom rom.
kah1593 said:
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Click to expand...
Click to collapse
Can anyone post a link of where I'll find the proper drivers? It just shows BLU with an exclamation in my Device Manager. The PDANET trick did not work as it won't detect the device. - and if I can get this working, I'll post an actual tutorial for it.
If anyone could post an update.zip of the original rom that would be fantastic. - and clockwork 6 will run on our devices with some work. but right now, mine is a brick, it still has recovery but the stock rom is effed.
I'm in the same situation. I deleted my contacts.apk in hopes of replacing it with a stock version, now it's stuck in a boot loop, and factory reset doesn't help.
Alright guys, I hit the jackpot. I have CM 10.1 working on my Quattro 4.5. It all began when I read somewhere on the xda forums that the Quattro 4.5 and k-touch v9 are essential the same phone. I said before, my phone was bricked so I figured I do some more research and see what I could do. Turns out that person as right. I found a website ( http://www.needrom.com/phone-roms/k-touch/k-touch-v9/ ) that has 3 roms for the v9, CM 10.1, MIUI 3.4.5, and CM 10, and instructions to install them. I decided to take a leap of faith and follow the directions given for CM 10.1. The installation directions for custom recovery CWM 6.0.1.1 worked perfectly - only problem is after you've installed the recovery, the menus are in Chinese.
Once again, My phone was bricked and essentially completely erased. If your phone isn't bricked, it should be fine as long as you do a factory reset before. I would suggest doing this before installing the CWM recovery because I have no clue how to do the reset using the Chinese menu.
I downloaded the CM 10.1 rom from the website above and gapps for 4.2.2 as well (you can find this with google). If you're using one of the other roms, obviously make sure you're using the proper gapps version.
ADB works while in recovery so use this to push the zips to the phone. I say this because I've discovered the sd card directory changes depending if your phone is bricked or not (i.e. /emmc vs /sdcard).
Flash the rom zip, then gapps - select the 2nd option in the main menu then in the following menu, the 4th option. This should lead you to the directory containing your zip files. Choose the appropriate one, and let the CWM work its magic. ( also from messing around I can also tell you the first option in the main menu is to reboot)
Once you've reboot, everything should work perfectly - WIFI, bluetooth, brightness, camera, video recording, audio, microphone, not a single problem except the volume being much louder than before. It's amazing. I have straighttalk's $30 plan, so I'm still stuck with a dumbphone until I bump up to the unlimited everything at the end of the cycle, so I can't test the phone radio, but I would expect it to work considering everything else does as well. Let me know if I left something out. I would test the other roms, but I'm so happy and content with my phone working again, I don't want to go through the effort just yet.
I found a way to create an English recovery that works from the Chinese version. Just replace the recovery.img provided with this one. Here's the link: https://www.dropbox.com/s/5y6r9gvspvouhbo/recovery.img I don't think this should cause any issues because it hasn't for me, but remember you are using this at your own risk. Though if an issue does arise, I'll try my best to help.
Install with English Recovery?
Did you install with the English recovery, because I am stuck at CM10.1 boot screen installing with the English recovery.
I used the XDA guide on my Nook Tablet 16gb 1.4.0 to have dual boot of Nook running and Android running at the same time(double touch N key to reach home screen os). It worked amazing for about a year and now my nook will only charge with power off, or turns itself off once plugged in. The CWM v5.5.0.4 that I installed internally still works, I factory reset and it boots normal now but still has charging problem (probably due to excessive use on my part).
Can someone please give me link to zip file to just re-flash the android system back on using the CWM internal?
I can bring up the CWM screen easy and it still recognizes the SD card I used. Also the android OS given at the time you made would be great or one better that you all recommend. Thank You XDA big time, it took me two weeks to properly follow all steps with clean install, and it worked better than I hoped, and loving games like DeadTrigger and EA HotPursuit both looked amazing. Also original Nook cable causes boot loop but standard android cable that came with my galaxy will charge but no boot loop, but it will only stay off while charging..=(
Found it myself
JimTheNurse_sjfan said:
I used the XDA guide on my Nook Tablet 16gb 1.4.0 to have dual boot of Nook running and Android running at the same time(double touch N key to reach home screen os). It worked amazing for about a year and now my nook will only charge with power off, or turns itself off once plugged in. The CWM v5.5.0.4 that I installed internally still works, I factory reset and it boots normal now but still has charging problem (probably due to excessive use on my part).
Can someone please give me link to zip file to just re-flash the android system back on using the CWM internal?
I can bring up the CWM screen easy and it still recognizes the SD card I used. Also the android OS given at the time you made would be great or one better that you all recommend. Thank You XDA big time, it took me two weeks to properly follow all steps with clean install, and it worked better than I hoped, and loving games like DeadTrigger and EA HotPursuit both looked amazing. Also original Nook cable causes boot loop but standard android cable that came with my galaxy will charge but no boot loop, but it will only stay off while charging..=(
Click to expand...
Click to collapse
Here is a link
http://forum.xda-developers.com/showthread.php?p=23158867
This is all the working roms that can be flashed on Nook 16gb Tablet not the color or HD this is tablet only!!
When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
We need more info like what did it specifically say. Be as specific as possible
Sent from my Nexus 4 using xda app-developers app
RedJack117 said:
When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
Click to expand...
Click to collapse
that's "usually" an error you get when the zip is corrupted.
but occasionally you'll get it if your running an i9000 roms (I've had it interchangeably with status 7 before)
I would try re-downloading and flashing the zip again.
if that doesn't work try downloading and flashing fluid kernel
then go to "advanced" and select "reboot recovery".
then try flashing the rom again.
Status 0 error on anything I try to flash using CWM
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
After you PM'd me, I started looking around about the Status 0 error being thrown. All signs point to the Updater Script that in the ROMs that you are flashing. My hunch is that once you flashed the CyanAOSP, that changed your build.prop from T959 to i9000 and that is why you are getting the error. I'm pretty sure there is a way to fix it (see below)
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
The zips that you mentioned are probably the standard Root.zip and the CWM zip from s15274n's thread stickied at the top of the Q&A section. Keep those handy.
Click to expand...
Click to collapse
Some answers in-line above.
**********************************
Let's get a few things straight before we start. I am still looking for the Heimdall JFD package, but I think that I know where it is. Pretty sure I put it on one of the external HDDs that I have. I'll try to upload it tonight or tomorrow night, as I am away all weekend with the family. I really don't think that you'll need it, but best to have it and not need it, than need it and not have it.
Theoretically, once you Odin'd back to JFD, I would think that it would've reset your device ID back to T959, but I guess that it didn't. This is what I would do. Odin to stock JFD and then boot it up and let it settle. Root it using the Root.zip that you have already used before. At some point you'll need to pick a ROM to settle on, even if only to get past this hump. (I use Sada's CM11 for my sons' Vibrants. Not that there is anything wrong with any of the others, but I just basically set it and forget it for my boys. I think though that he may have stopped development for it though, so I guess I'll be looking through the dev section myself here in the near future.) Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). My issue was a Status 7 because of the device ID being changed and the Recovery/Kernel combo weren't letting me flash. I basically opened up the ROM.zip and deleted those line and re-zipped it up and then flashed it (did it all on the phone and no PC, but I'm crazy like that).
Let's let a few of the current device Devs weigh in and see what they think. Already mentioned nirogu325 above, but let's try @epicboy and @dzee206 and @sada23. If they are inclined to come and help, it would be much appreciated.
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
Click to expand...
Click to collapse
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
The phone only had one major issue before I started messing with it - back & home buttons not working. I honestly can't remember how and what I did to put CyanAOSP on it but I ended up with 2 issues after putting it on. Only the Menu button works (eventhough all 4 lights up) and the USB seems to be grounded. I managed to work with it the past year up until I Odin-ed it back to JFD. When the phone is off and battery still has charge, the loading button would come up followed by the empty batt image at the background. This will loop until the batt dies. The only way to turn it on is by connecting the USB to a power source. Accessing download is easier because all I needed to do is remove batt then press and hold the vol up & down before putting the batt back in. Getting into recovery is a bit trickier. You'll need to wait until you actually see the phone charging before doing the 3-button combo.
Last Saturday, my daughter had a school event and I brought this along because it took better pictures than my S3 knock-off. During the parade, after shooting a video, it would automatically take me to the preview. Since, both back and home buttons were not working, I was stuck. Only option was to reboot it. What makes it interesting is that there is no reboot option on the JFD. It was a good thing that I had my power bank with me. I really did not want to constantly reboot it so I thought of installing one of those virtual button apps. I managed to install ToucherPRO before their presentation which made it much easier. To my surprise, it somehow revived the back button on the device itself - I noticed it when I got home that night to transfer the photos and vids.
I mentioned this so that you guys will have an idea on what I need to go through to get it fixed - somewhat, at least to a more tolerable state. (you won't believe it but the tips of my fingers hurt due to the number of times I have to go into recovery or download)
@Woody
Woody said:
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
Click to expand...
Click to collapse
Yup. I actually find it both weird and interesting - which games work and how they work.
Woody said:
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
Click to expand...
Click to collapse
Remember I mentioned my hesitation using Heimdall and Bay_wolf's AIO toolkit regarding hijacking drivers and stuff, Kies on this PC is now useless. It won't even recognize the phone after I tried the toolkit - which is good, I guess.
Woody said:
... Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). ...
Click to expand...
Click to collapse
I read about this when I started going back through the threads. As you mentioned, this is an old phone. Old phone = old threads. What I do is I read everything on page 1 then skip over to the last page, going back. Seems to be more effective specially for DL links.
I was actually reserving this one as part of my 'last option' fix. From experience, editing scripts is far more dangerous than flashing a 'working' one. I managed to root my other DD this way, but went downhill from there - ended up bricking it 3 times.
Anyway, I think I got it - or at least, the correct way of doing it. It took me 3 days....
After day 1, I ended up with 8 update.zips (7 CWM and one ROOT) and at least 2 copies of ROMS, GAPPS, MODEMS, and KERNELS on my SD card - only the update.zips worked, the rest either gave me status 0 or leave me with the 'Vibrant Samsung' bootloop. I had some progress on DAY 2. I read something like what epicboy said:
epicboy said:
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
Click to expand...
Click to collapse
I tried several JB ROMS listed on the Bible but, the problem was, I can't get into recovery - it was all 'blurry'. When I tried a different JB ROM, it also worked but was still 'blurry' during start up and on recovery. That's when I remembered Woody's post regarding rainbows and bootloaders.
DAY 3: For some reason, everything was flawless. I was able to install JB then KK. EFFORTLESSLY, if I may add.
@epicboy
I'm planning to spend a couple of days more on this Vibrant before I mess with my other phone - a knock-off SGS3. I was drawn to L-Droid because the screenshots and contents of page 1 of their thread was specifically for the T959 and not the I9000. I know it's not really a big deal because the ROM will work and changing the build.prop for 'cosmetic purposes is easy. What really concerns me is the camera. Sadly, the T959 only has only one camera and if the camera app that you're using (stock or otherwise) has a feature to switch from back-to-front and you accidentally press that, it messes it up to the point that you can't use it anymore. I have downloaded the ROM and will try it out in a couple of days. Will send you a PM or reply on the thread regarding my feedback. I've flashed it several times but really haven't been able to do it flawlessly like in DAY 3 - which I find really weird.
Tnx peeps!
Good evening all, my apologies in advance if i am asking a stupid or already answered question,
i have looked through this forum and many others along side through google and i am unable to find a solution or solved post in regards to fixing this phone.
I recently purchased a second hand s2 from ebay, not the best move but it was cheap, and i was in need of a phone.
the phone came with damaged screen, so i ordered a replacement and thought no more.
after receiving the screen i replaced it fitted it and was in the belief that the phone would be up and running, no no no this is not the case...
upon fitting the screen i found that the phone would lag as such, as if two fingers were placed on the screen, with motions being very sticky also requiring a large amount of force to respond when trying to use it. normal androids will switch between home screens effortlessly and relatively fluid.
Seeing this issue i thought a simple firmware upgrade would suffice and id have a usable phone. upon upgrading via kies i was unable to install the MTP drivers and so switched to the program odin for the update.
i downloaded what i believe to be uk firmware from samsung-updates,
firmware I9100XWMS2_I9100BULS3_I9100VODLSF_HOME
which has also caused the phone to boot in what looks to be spanish. although e3 and cwm show in english.
after the update the phone seems to be in a soft bricked state, the phone will repsond to input from soft keys, go into recovery and download mode accept all firmwares i have tried 9 times out of 10. but when reaching the android home screen is completely frozen, no response from touch or soft keys, except only for volume up and power to reset the device.
thinking the recently purchased LCD was the culprit i have sent it back and had a replacement, still the issue is present.
I have tried many different roms/kernels in the hope to solve this problem and i am at my wits end!
any help in bringing this thing back to life would be of great help as i am without a phone, or enough money to replace it again...
thanks for any response
cheers Ansell2k12
Hopper8's 'Odin troubleshooting' thread stickied in the General section; in particular flashing the 3 part firmware (this will wipe your phone). Also try everything in that thread for as long as you have the patience for it. These cases tend to be fixed by perseverance, or not at all. There's no easy fix. It's either a hardware issue(s), NAND corruption, or something really obvious being missed here. If it's the latter, hopefully the stuff in Hopper's thread helps you fix it. If it's either of the other two, I'd be cutting my losses.
Ansell2k12 said:
Good evening all, my apologies in advance if i am asking a stupid or already answered question,
i have looked through this forum and many others along side through google and i am unable to find a solution or solved post in regards to fixing this phone.
I recently purchased a second hand s2 from ebay, not the best move but it was cheap, and i was in need of a phone.
the phone came with damaged screen, so i ordered a replacement and thought no more.
after receiving the screen i replaced it fitted it and was in the belief that the phone would be up and running, no no no this is not the case...
upon fitting the screen i found that the phone would lag as such, as if two fingers were placed on the screen, with motions being very sticky also requiring a large amount of force to respond when trying to use it. normal androids will switch between home screens effortlessly and relatively fluid.
Seeing this issue i thought a simple firmware upgrade would suffice and id have a usable phone. upon upgrading via kies i was unable to install the MTP drivers and so switched to the program odin for the update.
i downloaded what i believe to be uk firmware from samsung-updates,
firmware I9100XWMS2_I9100BULS3_I9100VODLSF_HOME
which has also caused the phone to boot in what looks to be spanish. although e3 and cwm show in english.
after the update the phone seems to be in a soft bricked state, the phone will repsond to input from soft keys, go into recovery and download mode accept all firmwares i have tried 9 times out of 10. but when reaching the android home screen is completely frozen, no response from touch or soft keys, except only for volume up and power to reset the device.
thinking the recently purchased LCD was the culprit i have sent it back and had a replacement, still the issue is present.
I have tried many different roms/kernels in the hope to solve this problem and i am at my wits end!
any help in bringing this thing back to life would be of great help as i am without a phone, or enough money to replace it again...
thanks for any response
cheers Ansell2k12
Click to expand...
Click to collapse
lcd may be the culprit but also the firmware is crashed flash it again properly after a factory reset from e3
Progress...but not as id hoped...
first off thanks to you mistahbungle & bhavstech,
unfortunately im only little further forward.
After the flash using 3 part file firmware the phone is now running in English language on an updated firmware, but still appears to be frozen/ crashed.
updates on appearance, maybe its still salvageable?
Clock now updates after reboot
English language
charge icon does not change when unplugging/replugging charger/data cable but is recognized by the PC - MTP is now installing, but requires reboot, after reboot of the PC, MTP installs again and request reboot again... and continues to do so.
clock doesn't update at home screen, again appears to be frozen/crashed
still no response to touch, touch buttons or soft keys - only phone rest volume up and power.
when phone is at samsung splash screen i get notification of voice mails/texts on the phone.
Thanks again Ansell2k12
Ansell2k12 said:
first off thanks to you mistahbungle & bhavstech,
unfortunately im only little further forward.
After the flash using 3 part file firmware the phone is now running in English language on an updated firmware, but still appears to be frozen/ crashed.
updates on appearance, maybe its still salvageable?
Clock now updates after reboot
English language
charge icon does not change when unplugging/replugging charger/data cable but is recognized by the PC - MTP is now installing, but requires reboot, after reboot of the PC, MTP installs again and request reboot again... and continues to do so.
clock doesn't update at home screen, again appears to be frozen/crashed
still no response to touch, touch buttons or soft keys - only phone rest volume up and power.
when phone is at samsung splash screen i get notification of voice mails/texts on the phone.
Thanks again Ansell2k12
Click to expand...
Click to collapse
Your issue of a semi frozen state is very familiar to me but the reasons can be many and one of those are the /sdcard partition not mounting properly and likewise it could also be a failure of the other major partitions but if the device booted and made it to the lockscreen then you may have some hope, first if you have a external card plugged try booting without it, if the issues repeat try swapping the ext card with the internal /sdcard by flashing a modified vold.fstab file for your firmware which swaps the partitions effectively making the device mount the ext card as the /sdcard partition. I am expecting you have gone through the default troubleshooting methods like a clean flash etc.
Sent from my GT-I9100 using Tapatalk
king_below_my_lord said:
Your issue of a semi frozen state is very familiar to me but the reasons can be many and one of those are the /sdcard partition not mounting properly and likewise it could also be a failure of the other major partitions but if the device booted and made it to the lockscreen then you may have some hope, first if you have a external card plugged try booting without it, if the issues repeat try swapping the ext card with the internal /sdcard by flashing a modified vold.fstab file for your firmware which swaps the partitions effectively making the device mount the ext card as the /sdcard partition. I am expecting you have gone through the default troubleshooting methods like a clean flash etc.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Yes i have done multiple flashes, tried another sd card as the original was unreadable by the phone but picked up the second faultlessly, although flashing a custom firmware failed when trying to load in cwm.
as for a modified vold.fstab file,this is new to me. Could i ask how its modified or where i would get the file? im guessing id use odin to flash it to the device?
thanks for the response
Ansell2k12
Ansell2k12 said:
Yes i have done multiple flashes, tried another sd card as the original was unreadable by the phone but picked up the second faultlessly, although flashing a custom firmware failed when trying to load in cwm.
as for a modified vold.fstab file,this is new to me. Could i ask how its modified or where i would get the file? im guessing id use odin to flash it to the device?
thanks for the response
Ansell2k12
Click to expand...
Click to collapse
There are some threads in which I myself detailed about swapping memory its done via a custom recovery and not using Odin.
Sent from my GT-I9100 using Tapatalk
??
king_below_my_lord said:
There are some threads in which I myself detailed about swapping memory its done via a custom recovery and not using Odin.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
any chance you could point n the right direction?
i have had a look at the stuff to edit vold, and it seems i am unable to do so as my phone isnt usable once booted
cheers Ansell2k12
Phone has gone in the bin cheers guys, thanks for the help
....
You could easily flash a edited vold.fstab file by generating a flashable zip file. That's why I said via recovery or if you are clever enough you can easily use recovery flashable Aroma file manager to overwrite the file.
Sent from my GT-I9100 using Tapatalk