Hi all -- I have a situation and am at a loss, I've searched the other reads and found nothing QUITE like this (if there is and I missed it, I apologize). (Let me note: I am not new to flashing ROMs, SBFing, ADB, etc. -- no expert, but not new). Basically, I'm hoping someone might have an answer as to whether I'm looking at a hardware issue or not at this point.
Had NT rooted, installed CWM using one-click app. One day I went to turn on my NT and it went to the white Read Forever screen and stayed there for hours (literally). I held the power button for 30+ seconds, it turned off, and I tried to turn it back on -- same thing: Read Forever screen Forever. I could reboot into CWM (installed internally) and still can. I tried to flash the recoveries out there in the FAQ thread, I tried the Ubuntu recovery, etc. I'm confident I followed the directions in all of them. The Ubuntu Recovery went through to the part where it says to power down and remove the SD card and I did that. Turned it back on and Read Forever screen stuck.
Now, the strange thing is, no matter what I try to do, every once in a while it WILL boot all the way through. (This has been going on now for about 2 weeks until I can get the opportunity to try different things, etc.) When it does boot up it's exactly in the state it was before all of this started a few weeks ago -- no matter what I've tried -- flashing albertwertz's recovery, the Ubuntu recovery method, etc.
The LAST time I got it booted up (about 3 days ago), I attempted the flash stock recovery (through the one-click app) + the unrooter app, etc. to be able to get back to stock recovery and deregister, etc. That process SEEMED to go exactly as planned (stock recovery said it flashed, unrooter posted success message, etc.). Device restarted, got a boot loop through three attempts and then a freeze on the Read Forever. When I tried to restart by holding the N + Power button and getting to Factory Reset it goes to CWM, suggesting the previous process while booted up did NOT work.
I'm at a loss. I've tried different SD cards. I've Google searched the issue. I've tried everything I could think of (that's not to say I've tried everything -- hence why I'm asking here). If anyone has an answer, a suggestion, I'd appreciate it.
Space your question next time
Space your question next time cuz i did not bother reading everything
flash a random rom from the development. I use
http://forum.xda-developers.com/showthread.php?t=1494367
[ROM] Stock 1.4.0 + Root + Apps + Mods - GO Launcher [No B&N Store|Rebloat] 15 FEB
BUT IT DOES NOT MATTER
if that does not work for you then
http://forum.xda-developers.com/showthread.php?t=1470910
this is recovery for 1.4.0 BY ADAM OUTLER
not albertwertz
QUESTION: how the hell am i a senior member when you are a junior member.
i joined this epic forum last year when i was like in the friggen 8th grade
Edited with spacing.
As far as Junior v Senior, I tended to respond elsewhere so my posts are low but I'm changing that tendency, particularly with the NT (hopefully).
Sent from my DroidX using Tapatalk
424aca said:
Space your question next time cuz i did not bother reading everything
flash a random rom from the development. I use
http://forum.xda-developers.com/showthread.php?t=1494367
[ROM] Stock 1.4.0 + Root + Apps + Mods - GO Launcher [No B&N Store|Rebloat] 15 FEB
BUT IT DOES NOT MATTER
if that does not work for you then
http://forum.xda-developers.com/showthread.php?t=1470910
this is recovery for 1.4.0 BY ADAM OUTLER
not albertwertz
QUESTION: how the hell am i a senior member when you are a junior member.
i joined this epic forum last year when i was like in the friggen 8th grade
Click to expand...
Click to collapse
you have more posts thats why...
Related
Hello, I just bought my G-tablet and I have severely screwed it over. First, I rooted it and installed CWM, (It went fine). Then I flashed Cyanogen 7, following their wiki full update instructions. It was running fine till I found out that for some reason, my computer nor the tablet even knew it had an SD (Computer found nothing, File explorer on tablet had nothing) coupled with the fact Gapps refused to install, I figured this would be solved in a wipe then another flash. Nothing was different. So I wiped again (seemed to have froze during) but the flash of Vegan 5.1 seemed to have went well... for now. However, trying to install Adobe Flash via the preinstalled android market, it wouldn't install. It kept saying download unsuccessful, for every single app I tried. (no it's not an network problem). Being the noob I am I started following random googled XDA threads on how to fix this. I partioned 4gig from my sd to see if that would fix the market problem. I got stuck in a bootloop so I was forced to reflash vegan. When I did, I found out that when I tried to install anything it said something along the lines of "Not enough space" knowing I had 13 gigs of memory leftover, I figured I'd try rebooting. Got stuck in bootloop. Then followed yet ANOTHER googled guide (droidpirate brick fix) and now I can't even access CWM. It just loads as IF it were going to CWM but then shows me a /!\ caution sign then instantly turns off. When I normally start it, it goes into bootloop. when I try to get to CWM (holding volume up, power) it goes to a useless flash that I presume just fails, then brings me back into the bootloop. As far as I see, I have no way of fixing this...
I know this is so much to read, so in a brief explanation.. I'm in a bootloop, cannot get into CWM (brings me to a failed flash then back into boot loop) and am in dire need of assistance Please help me
Go read the posts on nvflash and learn how to use it. It is your friend!!
IndyLateNite said:
Go read the posts on nvflash and learn how to use it. It is your friend!!
Click to expand...
Click to collapse
NvFlash is currently not working for me, I don't know exactly where I messed up but my computer already has the drivers to read the tablet. when I run the .bat, it doesn't seem to do anything.
Scratch that, got it to work. I didn't extract one of the folders entirely. But my tablet is still stuck in bootloop even after this? what now?
IndyLateNite said:
Go read the posts on nvflash and learn how to use it. It is your friend!!
Click to expand...
Click to collapse
Take this with a grain of salt, as I learned it is not 'always' your friend
Now it's just on the stock Viewsonic birds and Gtablet logo bootloop...
Even after I NvFlashed it... Still can't access CMW.
Any suggestions?
Nvm, I got it to what appears to be working. (and I just about jizzed all over my tab.) Thanks so much. Saved me a beating from my parents.
I reflashed my gtablet with NVflash, the three birds comes up then the tap n tap animation comes up then disappears and it does this about 10 times then goes black. I did the volume + & power button, I get a triangle.
after looking through the forums I came to the conclusion the I needed to install CWM. I installed CWM3028.1.2micro it and the triangle was replaced with a unpacking box. It rebooted and the on and off of the Tap Ntap screen started again (this time only 4 times)
I am at a loss of what to try next, any suggestions?
Thanks
Search the forums before posting next time. Your answer is here about 100 times.
Google search "G Tablet for Dummies" and READ, READ, READ
go to the start here section. I believe that you are a code red, if memory serves me right.
Why were you NVFlashing? Were you already in a soft brick? Read the page on NVFlashing, read the page on CWM, READ, READ, READ....then post
Shadowrunner63 said:
I reflashed my gtablet with NVflash, the three birds comes up then the tap n tap animation comes up then disappears and it does this about 10 times then goes black. I did the volume + & power button, I get a triangle.
after looking through the forums I came to the conclusion the I needed to install CWM. I installed CWM3028.1.2micro it and the triangle was replaced with a unpacking box. It rebooted and the on and off of the Tap Ntap screen started again (this time only 4 times)
I am at a loss of what to try next, any suggestions?
Thanks
Click to expand...
Click to collapse
My signature. Go to start here page. You're a code red.
What you did was you didn't erase data from the previous rom. The left over data is interfering with your boot up process. What's worse, you might have installed the wrong branch of development.
try at your own risk
Shadowrunner63 said:
I reflashed my gtablet with NVflash, the three birds comes up then the tap n tap animation comes up then disappears and it does this about 10 times then goes black. I did the volume + & power button, I get a triangle.
after looking through the forums I came to the conclusion the I needed to install CWM. I installed CWM3028.1.2micro it and the triangle was replaced with a unpacking box. It rebooted and the on and off of the Tap Ntap screen started again (this time only 4 times)
I am at a loss of what to try next, any suggestions?
Thanks
Click to expand...
Click to collapse
(I am from medico line i donot have any IT knowledge, what all i have learnt is from this forum from the awesome DEVs here. If I make any mistake in my instructions then please rectify it, and I am sorry about it in advance. These instructions are according to my experience so please use at your own risk, for any doubt read, read,read the forum)
I was in same scenario after my gtab started to bootloop suddenly one day. i was using bos alpha 6. Its an awesome ROM, i think some of my apps backed up by titanium messed up......... how i sorted out this problem is as follows.
As i said i was on bos i.e 1.2 rom so when i nvflashed (to the initial 3588 stock rom) i went to 1.1 with lot of data from previous rom still there in the memory interfering with the booting process. So i used the the compatible CMW i.e the old one bekits version (CMW v08). I booted in to CMW and did my all factory reset and wipes. (Donot use the newer cmw the one meant for 1.2 bootloaders.) After all wipes i rebooted and was stuck in gtab logo. Since i have cleared all the data, so i Nvflashed again and every thing went fine from there. Now if you want to again use 1.2 loader roms then install 4349 stock rom to get bootloader 1.2 on your gtab.
hope it helps thankyou
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.
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!
Hello XDA Forum,
so in order to get rid of all the garbage Samsung pre-installed stuff I wanted to install a custom ROM like LineageOS. To do this (since I'm a complete layman) I used this guide for the most part: https://forum.xda-developers.com/t/...fn-ds-lineageos-19-too.4431737/#post-86951249
First Issue arrived at point 12, when despite "swiping to allow writing" TWRP would not allow me to copy filed onto the phone. So I read somewhere else to reinstall TWRP, which I then did after a lot of back and forth. Sadly when leaving TWRP it seems almost impossible to get back into TWRP, the phone just loops around a recovery screen telling me that bootloader is unlocked. It's also no longer being recognized by ADB and Fastboot, or Odin for that matter. And even reinstalling the USB Driver did not help.
So I read somewhere to reblock the bootloading and then enabling it again. So I did, and now I cannot unblock it anymore either. It just sits in the "Downloading Mode" and when I hold Volume Down and Power it goes into the Recovery Screen and then IMMEDIATELY back into Downloading. I can't even turn it off because it's basically stuck in Downloading.
If I could make it work again and findable by ADB I might be able to just use a different Version of TWRP (not the one advertised in the thread linked above) and maybe try again. But then I also don't know why it was so hard to get into TWRP to begin with. Or is there now no escape from this loop and the phone is essentially bricked?
{Mod edit: Post adjusted to the language required by the forum rules! - Oswald Boelcke}
so you can not flash stock?