[Q] Do everything with stock recovery? - G Tablet Q&A, Help & Troubleshooting

I have been reading all the threads for several days. It may be a dumb question. But I am really curious if we can do everything only with stock 1.1 recovery since CWM .8 does not update bootloader and bring potential danger to soft-brick your gTab when future 3991 based builds include the new bootloader from VS. As far as I have found, flashing a ROM or kernel does not necessarily need CWM to do it. But with CWM we can do data wiping, which stock recovery is not able to. Calkulin posted a Format_All.zip file in his thread. It can do a wipe. I guess it works with CWM just like flashing any ROM or update. But I am not sure if I can use stock recovery to flash it to do a data wipe. Or does anyone know a good way to wipe/format data with only stock recovery?
Of course, one can use stock recovery to flash safely while use CWM to wipe the data. It is just because I am lazy and want to stick with stock recovery.

This came up in the Woot! forums as well, and it's my doing (I'll take the hit for it).
This is my suggestion: Use clockworkmod for all your day-to-day stuff (like backups and restores, SD partitioning and data wipes etc.). However, when you flash a firmware, you should look at that firmware, and the dev's post if that exists, to see if a bootloader update is required. In most cases here, that is NOT the case. However, if Viewsonic sticks to their guns and releases a new firmware with a new required bootloader, then the userbase needs to tread lightly as you might get a soft-brick if you're not careful.
I'm concerned about this because their UAT (build 3991) was like this, AND because the Notion Ink Adam (a sister device) is having these issues at this exact moment - their last update had a bootloader update and clockworkmod users were soft-bricking their devices because of it.
In TNT Lite 4.3.x and gADAM 1.3.x+. I added something called a "Recovery Pack". This allows the user to toggle between standard recovery and clockworkmod, as needed. I also create a standalone package if you wanted to add it to a 1.1-based rooted mod. This way, I (and everyone else) can use clockworkmod for day-to-day, but have the ability to toggle back to standard recovery as needed. I think this is a good balance, but users just need to be aware of the issues and when to use each.

roebeet said:
This came up in the Woot! forums as well, and it's my doing (I'll take the hit for it).
This is my suggestion: Use clockworkmod for all your day-to-day stuff (like backups and restores, SD partitioning and data wipes etc.). However, when you flash a firmware, you should look at that firmware, and the dev's post if that exists, to see if a bootloader update is required. In most cases here, that is NOT the case. However, if Viewsonic sticks to their guns and releases a new firmware with a new required bootloader, then the userbase needs to tread lightly as you might get a soft-brick if you're not careful.
I'm concerned about this because their UAT (build 3991) was like this, AND because the Notion Ink Adam (a sister device) is having these issues at this exact moment - their last update had a bootloader update and clockworkmod users were soft-bricking their devices because of it.
In TNT Lite 4.3.x and gADAM 1.3.x+. I added something called a "Recovery Pack". This allows the user to toggle between standard recovery and clockworkmod, as needed. I also create a standalone package if you wanted to add it to a 1.1-based rooted mod. This way, I (and everyone else) can use clockworkmod for day-to-day, but have the ability to toggle back to standard recovery as needed. I think this is a good balance, but users just need to be aware of the issues and when to use each.
Click to expand...
Click to collapse
Thanks a lot, Roebeet! for everything you have done for this community. I have saved your "recovery pack".

Can Standard Recovery update kernels as well?

vegeetz said:
Can Standard Recovery update kernels as well?
Click to expand...
Click to collapse
I think so,TMK. Just rename the whatever kernal.zip to "update.zip" and add recovery folder with command file in it and flash .....

Seems standard recovery is my best bet if I want to mod a little and keep things as close to original as possible.
Looking to do TNT 4.3.2 with Clemsen v7 tomorrow.

vegeetz said:
Can Standard Recovery update kernels as well?
Click to expand...
Click to collapse
Check with the developer - if they say "clockworkmod only" then you should follow their instructions, imo. My guess is that they only test with cwm, but that's only a guess.

vegeetz said:
Seems standard recovery is my best bet if I want to mod a little and keep things as close to original as possible.
Looking to do TNT 4.3.2 with Clemsen v7 tomorrow.
Click to expand...
Click to collapse
I will probably go with Calkulin's 1.1 and clemsen v6. It looks Calkulin's one is the fastesd so far.

roebeet said:
I also create a standalone package if you wanted to add it to a 1.1-based rooted mod.
Click to expand...
Click to collapse
Roebeet
Did a search and found everything but link to the "standalone Recovery Pack). Please provide again.

Rumbleweed said:
Roebeet
Did a search and found everything but link to the "standalone Recovery Pack). Please provide again.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1005080

Related

[Q] Brand new GT, NVFlashed to 1.0-2638, what next?

This has been the most frustrating experience I have ever had with an Android device...
I was one of the lucky few who got one for $280 on Amazon and apparently it had the newest build on it that has the boot loader locked down.
I went through all the stickied guides, warnings about the locked bootloader and NVFlash. Needless to say, I have done my homework.
I tried in vain to install any ROM, but the only one that would install is TnT, which to the dev's credit it was a huge step above the stock ROM, but *shudder* that interface...
Long story, short; I managed to install CWM, fail at any install of a ROM (3 bird screen) and and ended up flashing with NVFlash to 1.0-2638, tried to flash ROM's again and again only to reflash 2638. It has been a LOOOOONG day with this thing.
I am at my wit's end.
Here is what I have 1.0-2638, no CWM and a bottle of Patron Silver...
How do I get a ROM on here...
Hey
Compusearch said:
This has been the most frustrating experience I have ever had with an Android device...
I was one of the lucky few who got one for $280 on Amazon and apparently it had the newest build on it that has the boot loader locked down.
I went through all the stickied guides, warnings about the locked bootloader and NVFlash. Needless to say, I have done my homework.
I tried in vain to install any ROM, but the only one that would install is TnT, which to the dev's credit it was a huge step above the stock ROM, but *shudder* that interface...
Long story, short; I managed to install CWM, fail at any install of a ROM (3 bird screen) and and ended up flashing with NVFlash to 1.0-2638, tried to flash ROM's again and again only to reflash 2638. It has been a LOOOOONG day with this thing.
I am at my wit's end.
Here is what I have 1.0-2638, no CWM and a bottle of Patron Silver...
How do I get a ROM on here...
Click to expand...
Click to collapse
Thats sucks, and i feel for you. I am also someone that just purchased the gtablet from amazon, and have been reading the forums throughly and it clearly says to downgrade before attempting to load cwm and flashing a given rom. So i guess my question is, did you downgrade before flashing?
@Compusearch... welcome to the G-Tablet world...
before you go ahead... look though the forum and FAQ posts...
do you have a particular ROM in mind??
keep these in mind...
if you install the latest 1.2-4329 ROM, you cannot install a custom kernel... so most custom ROMs like CM will not work... there are three 1.2 based custom ROM available (can't post the links so google Century Eyes or Mountain Laurel)
if you install a Gingerbread ROM like CM7, hardware video decoding will not work...
a start up from where you are... get the 1.1-3588 ROM from http://forum.xda-developers.com/showthread.php?t=842000 and flash it with the stock recovery... it's the best base ROM... then you can flash CWM 0.8 bekit if you want to install a 1.1-based ROM (most ROMs available here) or move to 1.2-4329 and install a 1.2 based custom ROM...
you can easily nvFlash back to the 1.1 based ROM even after you move to a 1.2 based ROM...
craigacgomez said:
@Compusearch... welcome to the G-Tablet world...
before you go ahead... look though the forum and FAQ posts...
do you have a particular ROM in mind??
keep these in mind...
if you install the latest 1.2-4329 ROM, you cannot install a custom kernel... so most custom ROMs like CM will not work... there are three 1.2 based custom ROM available (can't post the links so google Century Eyes or Mountain Laurel)
if you install a Gingerbread ROM like CM7, hardware video decoding will not work...
a start up from where you are... get the 1.1-3588 ROM from http://forum.xda-developers.com/showthread.php?t=842000 and flash it with the stock recovery... it's the best base ROM... then you can flash CWM 0.8 bekit if you want to install a 1.1-based ROM (most ROMs available here) or move to 1.2-4329 and install a 1.2 based custom ROM...
you can easily nvFlash back to the 1.1 based ROM even after you move to a 1.2 based ROM...
Click to expand...
Click to collapse
Trust me, I went through all the FAQ's and Guides here. I even found a bunch of youtube video's showing how to do the installs of CWM and ROM's. I can follow along, but the end result is always the 3-bird boot screen.
I am seasoned veteran of installing ROM's: Droid, DroidX, Nook (too easy), Galaxy Tab, Captivate, HD2 (winmo7, android), MyTouch3G, and HTC Inspire. I know the procedures and concepts very well.
I think the variable that is screwing me over, is what was initially installed on my gTablet when I got it this week.
I assumed that I had 4349 as there was no available update when I checked for it over wifi. With that in mind, I did downgrade it to 3588 per:
http://forum.xda-developers.com/showthread.php?t=1036956
Even with that, I could not install any ROM's other than TnT Lite.
I am wondering of the latest batches of gTablets are locked down beyond what the newest update 4349+ already does.
Technically as it stands, I have 1.0-2638 installed and that should have the unlocked bootloader and I should be able to follow this guide:
http://forum.xda-developers.com/showthread.php?t=865245
I would assume that logically, if I have an earlier version of the original TnT, that I can install CWM and then any gTablet ROM.
Am I wrong to assume this?
[edit] I want to be able to use the Vegan Beta 5.1.1 ROM
Stupid question but have you actually tried to install a rom after nflashing. The problem you were having before was the partition structure was wrong and nvflash should have fixed that. You can also extract "recovery.img" from bekit 0.8 zip file......
Copy recovery.img to your nvflash directory
Rename part9.img to part9.bak
Rename recovery.img to part9.img
Run nvflash again
This will flash cwm for you. Then try clearing data and flashing anather rom
Compusearch said:
Trust me, I went through all the FAQ's and Guides here. I even found a bunch of youtube video's showing how to do the installs of CWM and ROM's. I can follow along, but the end result is always the 3-bird boot screen.
I am seasoned veteran of installing ROM's: Droid, DroidX, Nook (too easy), Galaxy Tab, Captivate, HD2 (winmo7, android), MyTouch3G, and HTC Inspire. I know the procedures and concepts very well.
I think the variable that is screwing me over, is what was initially installed on my gTablet when I got it this week.
I assumed that I had 4349 as there was no available update when I checked for it over wifi. With that in mind, I did downgrade it to 3588 per:
http://forum.xda-developers.com/showthread.php?t=1036956
Even with that, I could not install any ROM's other than TnT Lite.
I am wondering of the latest batches of gTablets are locked down beyond what the newest update 4349+ already does.
Technically as it stands, I have 1.0-2638 installed and that should have the unlocked bootloader and I should be able to follow this guide:
http://forum.xda-developers.com/showthread.php?t=865245
I would assume that logically, if I have an earlier version of the original TnT, that I can install CWM and then any gTablet ROM.
Am I wrong to assume this?
[edit] I want to be able to use the Vegan Beta 5.1.1 ROM
Click to expand...
Click to collapse
nvFlashing back to the 1.0 release will definitely downgrade your bootloader... and then I recommend upgrading to the 1.1 branch (3588)... install CWM using the stock recovery or using nvFlash (as @thebadfrog said)...
Format all partitions using CWM... and even try re-partitioning the internal SD card using CWM to 2048MB ext, 0MB swap... and then install a custom ROM
craigacgomez said:
nvFlashing back to the 1.0 release will definitely downgrade your bootloader... and then I recommend upgrading to the 1.1 branch (3588)... install CWM using the stock recovery or using nvFlash (as @thebadfrog said)...
Format all partitions using CWM... and even try re-partitioning the internal SD card using CWM to 2048MB ext, 0MB swap... and then install a custom ROM
Click to expand...
Click to collapse
Trying that now:
1. upgrade to 3588 -Done!
2. install CWM -Done!
3. re-partition SD 2048/0M -Done!
Wipe Dalvik Cache -Done, but with error "Can't Mount /dev/block/mmcblk0p2"
Wipe data/factory reset -Done!
Wipe cache partition -Done!
Format SYSTEM -Done!
Format DATA -Done!
Format CACHE -Done!
Format SDCARD -Done!
4. Custom ROM - VEGAn-TAB GingerEdition STABLE RC1 - INSTALLED!!!
Thanks, Craig and Frog for the tips. This really should be added to the current FAQ.
Sadly, now that I can actually use the tablet, I am HATING the view angles on it.
For a company that prodomiately makes nice monitors and LCD's this is some BS right here.
I know that ViewSonic slapped their name on it, but seriously, who over at VS said that the screen was great and ready for production?
Yeah, the viewing angles aren't great... but it's perfect for a traveller like me... I can sit on the plane and use my tablet without anyone seeing what I'm doing!!
And ignore the dalvik wipe error!!
I wish more people would look at repartitioning as a "step" during the flashing process as apposed to a maybe. All the roms and recovery images are built off of one specific partition set and it is in my book a necessary step to make sure we are all on the same page.
Glad you got it sorted
Mantara said:
I wish more people would look at repartitioning as a "step" during the flashing process as apposed to a maybe. All the roms and recovery images are built off of one specific partition set and it is in my book a necessary step to make sure we are all on the same page.
Glad you got it sorted
Click to expand...
Click to collapse
We have debated that for several months since discovering the different partitioning. The only real way to "brick" for real is through a bad nvflash therefore it makes since to skip that step until necessary.
I think all roms should be nvflashed anyway so you have to understand and be able to use the recovery tools to even modify your tab. But thats my own opinion

[Q] Cannot boot into Recovery

Hey all. I just got a new G Tablet and am trying to install CM7 I was following the instructions to the letter from (Since I an't post links, just google this) Cyanogenmod G Tablet Wiki Full
I got through the 'Installing ClockworkMod Recovery' part and everything appeared to finish successfully.
After rebooting the device, I tried to boot into Recovery to install CM7 and the device just freezes on the ViewSonic splash screen. The screen says 'Recovery key detected Booting recovery kernel image', but it just sits there.
I am able to boot the device into the stock OS, but I can no longer get into recovery.
What can I do?
Tap UI Version: 1,2-4349
Kernel Version: 2,6,32,9-00001-g0e0c333-dirty
Build number: FRF91
Thank you in advanced for your help. Please let me know if there is any other information you need about my device.
Andrew
The key to your post is
Tap UI Version: 1,2-4349
Click to expand...
Click to collapse
You're on the 1.2 bootloader, and CWM .8 will not work on it. There is a versio nthat WILL work, but I, unfortunately don't know the exact link to provide for you. I'll attempt to look it up and get back to you, though.
basically, your G-Tablet, was at some point, updated with the most recent OTA update provided by viewsonic. The update was pulled 24 hours after it was released. You're not lost with 1.2...you have many options. You can either stay on 1.2 and flash any of the many 1.2 roms...some are listed in the development section, others can be found on "another" forum.
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Download
clockworkmod v3.0.2.8 (1.2 branch / NIA rev5) Link: http://www.mediafire...2flqn8b10ebcq44
md5sum: ac4d728d74a6b608cce588d2649e79f3
(updated on 5/15/2011)
clockworkmod v3.0.2.8 (1.2 branch rev2) Link: http://www.mediafire...x61q8jlu2dx8i9u
md5sum: 48c0c40175ab38cebc1199f9d3be8a7d
(updated on 5/05/2011)
THIS REV2 VERSION HAS BEEN TESTED MORE, but nandroid restores are not working properly. Rev5 corrects that, but I need more testers to confirm stability, please!
Many thanks to bekit and rothnic, for their work with clockworkmod!! Their documentation is what assisted me to get this functioning.
NOTE ON CWM: Do not use the Android GUI tool to wipe user data, or else cwm will get stuck in a reboot loop! If this occurs, there are two ways to fix this:
1- ADB required
In clockworkmod, go to mounts and storage and mount /system. Then, run this on your local PC:
adb shell
cd /system/bin
./fixrecovery.sh
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
2- nvflash required
Using the 4349 nvflash image, run this:
nvflash --bl bootloader.bin --download 9 part9.img
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
Click to expand...
Click to collapse
TJEvans (is it ok if I call you TJ for short?) thank you very much for your help, I appreciate it very much. I'm sorry if confuse some terms here as I try to address your posts inline below, but I would definitely still consider myself a novice at this process of installing custom roms.
TJEvans said:
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
Click to expand...
Click to collapse
This is a brand new G Tablet. I litteraly got in the mail today from Tiger Direct. I'm wondering if the Clockworkmod I tried to install is responsible for the custom kernel.
TJEvans said:
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
Click to expand...
Click to collapse
I don't necessarly need CM7, but that is what I have on my Nook Color, and I really like it.
The main question I have is that right now, I cannot get into clockwork or stock Recovery at all. I do have adb working, so I would think my next steps will require me to use adb.
At the moment since I can't get to recovery I seem to be stuck. Is there a process somewhere I can get recovery working again using adb?
OK...let's try something. It looks like you may actually be in stock recovery, but there's nothing for it to recover.
do you know of a way to get a file and a folder onto your internal SD?
if so, let's edit the instructions to be able to flash to 3588 stock...
What you need:
1. A stock 3588 image renamed to 'update.zip' (http://tapntap.http.internapcdn.net/...-3588-user.zip)
2. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
Click to expand...
Click to collapse
if yo ucan get those on the SD, then when you reboot, the stock recovery will run and install stock 3588 1.1 based rom and recovery, then you can install your CWM .8.
I have never used NVFlash or ADB, or APX...I have no experience with them. I'm just here helping people that have compatibility issues between 1.1 and 1.2 bootloaders.
After all, the key to fixing problems, is to first find out what the problem is...
I wish I could help more, but I've seen more and more people softbrick their g-tabs by using NVFlash than anything else. I'm not ready to go messing around with my own root files, yet.
If you can get that file, and that folder onto your SD, then stock recovery will automatically recognize it and run it...
I may have just really screwed things up. I ran 'adb reboot recovery' and I gets to the Splash screen with 'Booting recovery kernel image' and gets stuck. Now, I can't get into the device at all.
Also, none of the links in your posts seem to work for me.
try them from the original post, then:
http://forum.xda-developers.com/show....php?t=1039000
sorry, like I said, I'm not a techy...just a guy that doesn't like to see people suffer...
TJEvans said:
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Click to expand...
Click to collapse
It's far from being taboo since it's the honeycomb bootloader... their recovery was blue for a reason...
maybe they pulled those OTA update because they had not licensed honeycomb anyhow, 1.2 is perfectly good to install as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Ok, I was able to get the device working again using NVFlash. (http forum,xda-developers,com/showthread,php?t=861950 replace commas with periods).
Now, I have the following:
Tap UI:1,1-3588
Kernel is still: 2,6,32,9-00001-g0e0c333-dirty
I don't know anything about this kernel, or how I got it, other than maybe it came with my first errant clockwork install.
Can you give me some pointers on how I should proceed? (I would still like to get to CM7 at some point, but I don't know if I should get a different kernel or go back to the stock kernel as well)
GREAT NEWS....glad you god it running so far.
OK, that may be the stock kernel...the numbers looked familiar to me, and I've never seen the stock kernel on that report...so, I may be mistaken.
in any case, you are now back on stock 3588 1.1 bootloader...
Now, you should be able to install the CWM .8 that you tried before, and flash CM7 from there...basically, follow the guide you followed before. but this time, it should work fine, since you are on the right bootloader.
Just remember, research ANY new roms you want to try to make sure what bootloader they are on.
to P00r:
as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Click to expand...
Click to collapse
see, I didn't even know that...
The thing I'm seeing, is that Clemysn posted the BOS infromation here, and tried to emphasize that it's a 1.2 Rom...The 1.1 rom's though, do not indicate that they are 1.1 Roms. when 1.1 was all that existed, it made no difference, but now that there is another option, they should at least make sure to add "PLEASE BE SURE YOU ARE USING A 1.1 BASED BOOTLOADER BEFORE FLASHING THIS ROM!!!"
As you can see from Imarikinrat's post, he bought a supposedly factory G-Tablet with 4349 prepackaged on it...now, granted, you and I both know that it's more than likely a refurbished one, as I can't see Viewsonic intentionally releasing product with a bootloader and firmware that was pulled from their updater...
in any case. Roebeet kinda predicted that this would happen a bit. Since most moderators on XDA downplayed the impact of 1.2, it's gone fairly ignored. Think about Imaricanrat's post for a second. Had he not posted his system information there is no way that we would have known that it was a bootloader conflict. It would have been assumed that he was on 1.1 bootlaoder with a "brand new" g-tablet (seriously, man, I'd check that thing with a magnifying glass to make sure that there are no scratches or anything that would indicate that it was anythign other than BRAND NEW)
anyway...had he not posted that he was on 1.2, then who knows what advice he would have been given.
Well, now I'm back to my original problem. I cannot get into Recovery. When I start holding Power and Vol+, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
I have tried putting the recovery folder and update.zip in the internal memory, and on an sd card to no avail. Any other suggestions?
that most certainly sounds like stock recovery to me...
I'm at a loss...it worked fine for me when I flashed to 4349 from stock 3588...just ran and installed, then I ended up on 4349 stock...
you're following the CM7 install guide? Or are you trying to install CWM at this point? I never installed CWM myself, as mine came with it on it.
I'm trying to install clockworkmod so that I can install CM7. Is that the right way to do it? I know there was a stock recovery gui that I cannot get into now.
as long as the recovery folder is on the SDcard, it will automatically attempt to run it...
picture it this way...remember back in the day of windows 3.1 In some cases, if you inserted a floppy disk with a boot file on it, it would check there first, then boot from internal memory...
So, the recovery folder is telling it to run the file in it, which unpacks and installs the update.zip.
once again, though, I never installed CWM myself, but from what you're saying, it should be working.
what happens if you remove the folder and file (after running it), and attempt to go into recovery again?
When I remove the file, folder, and SD card and try to get into recovery, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
hmm...the box with the arrow and progress bar indicates that it's trying ot run something from recovery...weird..
ANYONE ELSE???
I'm not experienced enough to help...anyone else know enough about flashing CWM from stock, or flashing CM7, that can help out, please chime in.
thanks.
and sorry Imarican...I tried, but once again, no techie here.
No worries man, thanks for your help. Have a good night.
Update: Ok, I think somehow this whole process messed up the 'Recovery Partition' on my G Tablet for whatever reason. When I performed the NVFlash back to stock, it managed to 'fix' the majority of the device, allowing me to boot normally into Tap UI:1,1-3588. However that flash did not fix my Recovery Partition.
With all of that in mind, I found instructions on XDA to install 'clockworkmod via nvflash' (Since I still cannot post links, just google that and it should be the first link, also it's XDA thread 1058649).
After following those steps, I am now able to boot into Recovery which is now Clockwork Mod Recovery, and hopefully *crosses fingers* be able to flash CM7.
Given that I will probably never go back to stock anything on this device, does anyone know where I can download the 'Stock Recovery' for the G Tablet?
so is the point of this article Tiger direct sell used products as new?
so is the point of this article Tiger direct sell used products as new?
Click to expand...
Click to collapse
unconfirmed...what we know is that he had 1.2 4349 out of the box, stock firmware. There are a few possibilities. This could be a Tiger Direct return that was repackaged and sold as new. It could also be a direct from VS return that was repackaged as new, OR, VS actually sent a stock of G-Tablets to Tiger Direct that were packaged with the 4349 firmware on it.
Either way, people need to be careful when flashing roms and such. XDA has not, so far, made it clear which roms, kernels, and CWM versions are good on which bootloader. Some have been asking that devs start exiting posts to indicate which bootloader is needed for each mod, to attempt to avoid confusion.
We must also realize that new G-Tablets are being bought every day, and not every owner is knowledgable of the issues of the recent past, with VS, NVidea, 1.1, 1.2, etc. Most people probably, reasonably, assume that they can open it, root it, and start flashing whatever they want, not even aware that there is a difference.

[q] what is 1.1 and 1.2 stock? what is the bootloader?

i know these questions can probably be found somewhere but would someone be able to give me a quick run down of what 1.1 and 1.2 stock is and how does that relate to 3588 and 4349? also what is the bootloader and why do some things require the stock bootloader and not CWM? and also, how do you go back to the stock bootloader, just nvflash the stock 1.1 or 1.2? and also why are 1.1 and 1.2 bootloaders not compatible with certain roms and such?
thanks in advance!
joshtb86 said:
i know these questions can probably be found somewhere but would someone be able to give me a quick run down of what 1.1 and 1.2 stock is and how does that relate to 3588 and 4349? also what is the bootloader and why do some things require the stock bootloader and not CWM? and also, how do you go back to the stock bootloader, just nvflash the stock 1.1 or 1.2? and also why are 1.1 and 1.2 bootloaders not compatible with certain roms and such?
thanks in advance!
Click to expand...
Click to collapse
I can answer some ...
1.1 and 1.2 are the 2 common bootloaders for the gtablet.
I think of bootloaders as a layer of software that sits underneath a ROM and provides services to it. ie between the ROM and the hardware.
1.2 is the newer bootloader, which is needed by 4349, Bottle of Smoke (BOS) which is a Honeycomb distribution, and a few other. (Mountain Laurel, and Brilliant Corners which are 1.2 versions on TNT Lite and Vegan Tab).
All others 3588 (and before), TNT Lite *, Vegan Tab, CM (all versions maybe except one which I hear is for 1.2 for gadam?) use the 1.1 bootloader.
Stock recovery (update.zip and command file) , will update both ROM and bootloader, and is the preferred way to go between 1.1 and 1.2 based ROMs
CWM 0.8 will update ROM but *not* the bootloader.
So CWM cannot be used to go between 1.1 and 1.2 based ROMs.
If you currently use CWM, you can nvflash to a stock ROM (eg 3588), you get stock recovery back, and you should be then able to update to any ROM.
There is also a recovery pack for some 3588 based ROMS (maybe also for the 4349 ROMs) that has scripts to switch between stock and CWM recovery, although I do not know how well they work. Doing this would not require NV flashing.
My guess as to why different ROMs go with different Bootloaders, is that the newer Bootloaders, provide new functionality for new ROMs (due to which, new ROMs do not work with old bootloaders) and delete functionality needed by older ROMs (due to which, older ROMs do not work with newer bootloaders). However if the ROM could be made to not rely on these changes of services, they could in theory be made to work with both bootloaders. I have no idea if this is possible in practice.
joshtb86 said:
i know these questions can probably be found somewhere but would someone be able to give me a quick run down of what 1.1 and 1.2 stock is and how does that relate to 3588 and 4349? also what is the bootloader and why do some things require the stock bootloader and not CWM? and also, how do you go back to the stock bootloader, just nvflash the stock 1.1 or 1.2? and also why are 1.1 and 1.2 bootloaders not compatible with certain roms and such?
thanks in advance!
Click to expand...
Click to collapse
3588 use the 1.1 bootloader
The recovery is only able to start an update.zip
4349 use the 1.2 bootloader (same as Honeycomb based rom)
4349 also install a new recovery that look like CWM but is Honeycomb blue
Bootloader in this case is actually a combination of 2 thing, bootloader and kernel they are save on 2 different part of the nvflash image (2-3)
The stock bootloader is needed to be able to move from a rom using version version 1.1 to 1.2 or back, the proper method is to use an update.zip since this is the only method know to update the bootloader (NVFLASH doesnt flash partition 2 and 3)
To go back use UPDATE.ZIP with a STOCK 1.1 recovery, you can even nvflash the recovery directly using nvflash (position #9)
Why are they incompatible? good question, mostly kernel related afaik, there's now cross compatible kernel available that allow you to use a 1.2 bootloader with a 1.1 rom (see Clemsyn thread) this also provide the capacity to use similar rom from other brand (seem like the gtab was using an older bootloader)
very interesting subject that do require reading a few thread to be safe...
cbay, Thanks that was very informative. I had been wondering the same question.
well, now you know the what and how, but what about the why and the history...
Viewsonic is a basically a repackager. they put their name on a product and sell it to the masses. US Merchants is the US company that imports these products from China. The Chinese company that actually builds them is called Malata.
Malata is also responsible for the Notion Ink Adam as well as some other Tegra 2 based tablets.
The odd part comes in to play when you look at the bootlaoders for each device. Notion Ink always used a 1.2 bootloader for their Adam updates and firmwares. Viewsonic, though, was using what is assumed to be an older version of firmware based on the 1.1 branch. There is a lot of speculation as to why this is, and there is no real answer.
Now, back in February, one of the devs got a hold of a firmware labelled 3391. He discovered that it was on a different bootloader than the G-Tablet was currently using. he messed around with it a bit, but it proved to be difficult to crack at the time, since everyone was on 1.1 and it wasn't an official update, so nobody really had it.
Then, Viewsonic hadn't released an official update for a while. Users were getting irritated, and a mass request went out for Viewsonic to do SOMETHING...they did, they released the 4349 firmware, but then pulled it 24 hours later. It's still known as the most recent officla firmware, thought it's not available anymore (officially) 4349 also ended up being a 1.2 firmware. SO, now since this was an official update, the developer that was messing with 3391 figured that this was the direction that Viewsonic/Malata was going to go. He made his opinions known but was rejected by some of the mods here at XDA.
Since then, he has graciously moved to another forum where he houses all of his 1.2 roms. He took it upon himself ot convert his older roms to the newer 1.2 bootloader (Brilliant Corners, Mountain Laurel). He also created a seperate Clockwork mod that will work on 1.2 bootlaoder as well.
It was discovered that the new 1.2 bootloader from Viewsonic was the same bootloader that Adam had been using all along. It seemed that Viewsonic was either using, or getting outdated software from Malata. So, now we can also use Adam Roms and Kernels on our G-Tablets as well.
Honeycomb was ported from another device, but enabled to use the 1.2 bootloader. It's still in Alpha stages, but does require the 1.2 bootloader to flash.
Essentially, 3588 was the LAST 1.1 official updated firmware directly from Viewsonic. The only way that it can be improved upon is if we get more 1.1 official updates from Viewsonic. But, since we haven't recieved ANY updates from Viewsonic, we're not holding our breath.
4349 was the FIRST (and as of now ONLY) 1.2 official update from Viewsonic.
Fortunately for G-Tablet users, the Adam bootloader being compatible with our 1.2 bootlaoder opens the door for infinate possibilities. We are no longer dependant on VS to provide updates, as updates from Notion Ink can be ported more easily.
it's been suggested that the older 1.1 roms e converted to 1.2 roms ot avoid confusion and unexpected softbricks caused by such confusion, but there is resistence.
cbay said:
I can answer some ...
If you nvflash to stock (ie without CWM), you should be able to update to any ROM.
Click to expand...
Click to collapse
wrong, Nvflash doesn't update the bootloader, so the only correct way to move from one version of bootloader to the other is the update.zip method with a STOCK recovery (it also need a rom with the command "write_bootloader_image("/tmp/bootloader.bin", "EBT"" in the updater script )
Like you mentioned CWM doesn't flash the bootloader
if you check the process during nvflash, partition #2 and 3 (actually it's all the same partition only splitted in parts) are not flashed...
they can however be read using the correct command
Everything else is right, hey 2 answer for the same lazy question he's a lucky guy...
p00r, I'm very curious about that. Have you done a binary compare before and after nvflashing with different bootloaders to confirm it? If not, I may try it myself. I use nvflash to move between 1.1 and 1.2 based ROMs all the time and have never had any trouble with it. I do agree that it is probably better and safer to use stock recovery for normal usage but I've never had an nvflash fail on my tablet due to a difference in bootloaders so I'd like to learn more about it so I can use that information to avoid trouble.
P00r said:
wrong, Nvflash doesn't update the bootloader, so the only correct way to move from one version of bootloader to the other is the update.zip method with a STOCK recovery (it also need a rom with the command "write_bootloader_image("/tmp/bootloader.bin", "EBT"" in the updater script )
Click to expand...
Click to collapse
What I meant was, nvflash to a stock ROM like 3588 and then use stock recovery to update to a 1.2 based ROM, instead of CWM.
As far as I know this should work, as nvflashing to a stock ROM like 3588 would get you to stock recovery as well. (Right?)
Also, at any point when updating to a ROM using stock recovery, it is good to read the thread of instructions for the particular ROM as, it may contain more steps of wiping data/ cache etc. Some ROMs may also require a change in partitioning.
K J Rad said:
p00r, I'm very curious about that. Have you done a binary compare before and after nvflashing with different bootloaders to confirm it? If not, I may try it myself. I use nvflash to move between 1.1 and 1.2 based ROMs all the time and have never had any trouble with it. I do agree that it is probably better and safer to use stock recovery for normal usage but I've never had an nvflash fail on my tablet due to a difference in bootloaders so I'd like to learn more about it so I can use that information to avoid trouble.
Click to expand...
Click to collapse
What do you want to compare exactly ?
There's plenty of post that explain the issue to move between 1.2 and 1.1 roebeet used to call this softbrick when he discovered the 3991 leaked viewsonic rom that used 1.2 bootloader...
cbay said:
What I meant was, nvflash to a stock ROM like 3588 and then use stock recovery to update to a 1.2 based ROM, instead of CWM.
As far as I know this should work, as nvflashing to a stock ROM like 3588 would get you to stock recovery as well. (Right?)
Also, at any point when updating to a ROM using stock recovery, it is good to read the thread of instructions for the particular ROM as, it may contain more steps of wiping data/ cache etc. Some ROMs may also require a change in partitioning.
Click to expand...
Click to collapse
Yes as soon as you nvflash a stock recovery over anything and then use the recovery to do an update.zip of another rom type it will work.
wow thanks for the help everyone! i hit the thanks button to everyone who replied.
im running the clemsyn + calkulin version 5. does anyone know how to find out what version of the bootloader that is? there is a version 6 released requiring 1.2 and i also wanted to tryout the honeycomb version.
also, a backup image created with CWM - does it back up the bootloader, rom, and kernel? or just the rom
thanks again!
P00r said:
What do you want to compare exactly ?
There's plenty of post that explain the issue to move between 1.2 and 1.1 roebeet used to call this softbrick when he discovered the 3991 leaked viewsonic rom that used 1.2 bootloader...
Click to expand...
Click to collapse
Compare the bootloader before and after the nvflash. I've seen all the threads on moving between 1.1 and 1.2 and quite frankly I've never had any trouble using nvflash to do it regardless of which ROM I'm going to or from as long as I use the appropriate bootloader in the nvflash command. Based on that experience I would say the bootloader is being updated on the tablet or else I would have had considerably more trouble. The only time I've seen any trouble moving between the two is when trying to use ClockworkMod.
P00r said:
Everything else is right, hey 2 answer for the same lazy question he's a lucky guy...
Click to expand...
Click to collapse
Err, that wasn't really a "lazy question."
Everything on here and elsewhere assumes you know what "1.1" vs. "1.2" means without explanation. There's hardly anything anywhere that explains what they mean to new users.
I'm not sure how asking a question which isn't answered anywhere else is "lazy."

Couple of questions regarding ROMs and such.

Okay. Couple days ago, i got my new Samsung Galaxy S II. Fell in love with it. I previously had a Vibrant, but that met an unfortunate and violent demise. On the vibrant I hadn't been doing anything involving roms and such because i'd tried once, and completely fried the phone. LOL.
I managed to root my phone, and from what I've read, I didn't do the best method. What I did was get an unsecure kernel, and flashed that, then used a 1-click root type thing to root it. So one of my questions is, my clockwork mod isn't working, what's wrong with it? I downloaded ROM Manager, and flashed CWM. But when i reboot into recovery, i get the stock Samsung recovery screen. How can I get this to work?
And another question, is about roms such as Cyanogen mod. I really wanna get it. (I wont until I get CWM working, though.) And I'm just wondering. If I were to just go to ROM Manager, and flash cyanogen, would it work, or do i need to do more to my phone to be able to put on custom roms? I've never understood the concept of roms vs kernels vs firmware vs whatever else.
And if it matters, Samsung Galaxy S II, Android 2.3.3, rooted using SuperOneClick.
P.S Anything else that I should considering doing/putting onto my phone? And thanks in advance for halping.
Gutana said:
Okay. Couple days ago, i got my new Samsung Galaxy S II. Fell in love with it. I previously had a Vibrant, but that met an unfortunate and violent demise. On the vibrant I hadn't been doing anything involving roms and such because i'd tried once, and completely fried the phone. LOL.
I managed to root my phone, and from what I've read, I didn't do the best method. What I did was get an unsecure kernel, and flashed that, then used a 1-click root type thing to root it. So one of my questions is, my clockwork mod isn't working, what's wrong with it? I downloaded ROM Manager, and flashed CWM. But when i reboot into recovery, i get the stock Samsung recovery screen. How can I get this to work?
And another question, is about roms such as Cyanogen mod. I really wanna get it. (I wont until I get CWM working, though.) And I'm just wondering. If I were to just go to ROM Manager, and flash cyanogen, would it work, or do i need to do more to my phone to be able to put on custom roms? I've never understood the concept of roms vs kernels vs firmware vs whatever else.
And if it matters, Samsung Galaxy S II, Android 2.3.3, rooted using SuperOneClick.
P.S Anything else that I should considering doing/putting onto my phone? And thanks in advance for halping.
Click to expand...
Click to collapse
Okay, don't take this the wrong way, but it seems you're a bit lacking regarding knowledge about this phone... It'd pay to do your research beforehand in the SGS2 forum, read the FAQs, etc.
Okay, first off, all I can say is, go back to stock. Go flash a stock Samsung ROM for the device. Then, go into Chainfire's CF-Root Kernel thread, and download the appropriate kernel, and flash it using ODIN. After you've done that, you'll have ClockworkMod, and you'll be rooted. It is recommended that you flash another kernel though, after gaining root, as all the CF-Root kernel does it install ClockworkMod, and root the device. Personally, I recommend SiyahKernel.
If you need more detail or have any more questions, feel free to send me a PM.
Thanks,
screamworks.
screamworks said:
Okay, don't take this the wrong way, but it seems you're a bit lacking regarding knowledge about this phone... It'd pay to do your research beforehand in the SGS2 forum, read the FAQs, etc.
Okay, first off, all I can say is, go back to stock. Go flash a stock Samsung ROM for the device. Then, go into Chainfire's CF-Root Kernel thread, and download the appropriate kernel, and flash it using ODIN. After you've done that, you'll have ClockworkMod, and you'll be rooted. It is recommended that you flash another kernel though, after gaining root, as all the CF-Root kernel does it install ClockworkMod, and root the device. Personally, I recommend SiyahKernel.
If you need more detail or have any more questions, feel free to send me a PM.
Thanks,
screamworks.
Click to expand...
Click to collapse
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Gutana said:
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Click to expand...
Click to collapse
With a rooted device you'll be able to flash trough Odin or CMW recovery any rom you like.
Siyah kernel gives you a faster and more battery efficient phone and lets you set your own Voltage/ speed the processor has to use see this for the latest info
http://www.gokhanmoral.com/ and
http://forum.xda-developers.com/showthread.php?t=1263838
DirkTeur Velserbroncx said:
With a rooted device you'll be able to flash trough Odin or CMW recovery any rom you like.
Siyah kernel gives you a faster and more battery efficient phone and lets you set your own Voltage/ speed the processor has to use see this for the latest info
http://www.gokhanmoral.com/ and
http://forum.xda-developers.com/showthread.php?t=1263838
Click to expand...
Click to collapse
Alright, so i'm pretty much ready to go? Yayayayay.
And would you recommend any roms for me? XD
Gutana said:
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Click to expand...
Click to collapse
SiyahKernel has a lot of advantages and improvements of CF-Root, which provides null, if I'm correct. Go check out the SiyahKernel thread in Original Development for details.
Yes, as stated, you can use CWM by itself to switch ROMs. Just remember that if you're switching ROMs (as opposed to performing a flash to a newer version of the same ROM), to perform a factor reset / wipe data, wipe cache, and wipe Dalvik cache (Advanced > wipe Dalvik cache) in ClockworkMod first.
Gutana said:
Alright, so i'm pretty much ready to go? Yayayayay.
And would you recommend any roms for me? XD
Click to expand...
Click to collapse
For a beginninger, I can't recommend MIUI highly enough. You could go with GalnetMIUI, which is a variant, but I personally prefer the official MIUI build. If you're looking for a more, 'pure' experience, go with CyanogenMod 7.1 stable.
screamworks said:
SiyahKernel has a lot of advantages and improvements of CF-Root, which provides null, if I'm correct. Go check out the SiyahKernel thread in Original Development for details.
Yes, as stated, you can use CWM by itself to switch ROMs. Just remember that if you're switching ROMs (as opposed to performing a flash to a newer version of the same ROM), to perform a factor reset / wipe data, wipe cache, and wipe Dalvik cache (Advanced > wipe Dalvik cache) in ClockworkMod first.
For a beginninger, I can't recommend MIUI highly enough. You could go with GalnetMIUI, which is a variant, but I personally prefer the official MIUI build. If you're looking for a more, 'pure' experience, go with CyanogenMod 7.1 stable.
Click to expand...
Click to collapse
Alright, one more question, sorry for the nooby-ness. Haha.
So going from my phone to for example Cyanogen, I'd backup in CWM, and Titanium backup (Or does CWM backup like, EVERYTHING?) and then factory reset, flash the rom using odin, and then use titanium backup to get my apps and settings back? orwhat.
Gutana said:
Alright, one more question, sorry for the nooby-ness. Haha.
So going from my phone to for example Cyanogen, I'd backup in CWM, and Titanium backup (Or does CWM backup like, EVERYTHING?) and then factory reset, flash the rom using odin, and then use titanium backup to get my apps and settings back? orwhat.
Click to expand...
Click to collapse
CWM backup (called a NANDroid backup), backs up everything. If you perform a NANDroid back, there's no need to perform a backup in Titanium Backup - it creates a full image of your system (the advantage to TB though, is that you can backup all your download apps and settings, then install the new ROM, and restore the backed up apps - If you restore a NANDdroid backup, it'll restore the old ROM, exactly as it was when the backup was made).
So yes, the installation process is, for CWM: copy the ROM.zip to your phone, then boot into CWM recovery. Hit the 'factory reset / wipe data' option, the 'wipe cache' option, and then go to Advanced, and hit the 'wipe Dalvik cache' option. After that, choose 'install ZIP from SDCARD', and choose your ROM.zip. After it finishes installing, just hit 'reboot system now', and you're good to go!
Usually, it's not required to use ODIN to flash a new ROM, unless there's a problem with the recovery.
All that said, it pays to read the thread for the ROM beforehand, as sometimes when moving from ROM to ROM (especially from stock), there's a few small things that may be required, like flashing the ROM twice, or whatever
screamworks said:
CWM backup (called a NANDroid backup), backs up everything. If you perform a NANDroid back, there's no need to perform a backup in Titanium Backup - it creates a full image of your system (the advantage to TB though, is that you can backup all your download apps and settings, then install the new ROM, and restore the backed up apps - If you restore a NANDdroid backup, it'll restore the old ROM, exactly as it was when the backup was made).
So yes, the installation process is, for CWM: copy the ROM.zip to your phone, then boot into CWM recovery. Hit the 'factory reset / wipe data' option, the 'wipe cache' option, and then go to Advanced, and hit the 'wipe Dalvik cache' option. After that, choose 'install ZIP from SDCARD', and choose your ROM.zip. After it finishes installing, just hit 'reboot system now', and you're good to go!
Usually, it's not required to use ODIN to flash a new ROM, unless there's a problem with the recovery.
All that said, it pays to read the thread for the ROM beforehand, as sometimes when moving from ROM to ROM (especially from stock), there's a few small things that may be required, like flashing the ROM twice, or whatever
Click to expand...
Click to collapse
Alright, i got that done. I've tried both MIUI and Cyanogen, and both are working and lookin wonderful. But the problem is I dont get data on either one. I've tried reflashing, rebooting, factory reset. Idunno what else to try. Do you know what could be causing this?
Gutana said:
Alright, i got that done. I've tried both MIUI and Cyanogen, and both are working and lookin wonderful. But the problem is I dont get data on either one. I've tried reflashing, rebooting, factory reset. Idunno what else to try. Do you know what could be causing this?
Click to expand...
Click to collapse
Check your APN settings (should be somewhere in Settings under mobile network or whatever). Look your's up online ('APN settings carrier y, country z), and if they're not correct, add them in.
screamworks said:
Check your APN settings (should be somewhere in Settings under mobile network or whatever). Look your's up online ('APN settings carrier y, country z), and if they're not correct, add them in.
Click to expand...
Click to collapse
Got everything working, thank you very much. Thanked every one of your posts
And I've asked too many questions for one person in one thread, I happen to have one more. How can I get the Android Market on Cyanogenmod? I downloaded build 115, and there wasn't a market, so i'll be using MIUI till I get that fixed. ><
Gutana said:
Got everything working, thank you very much. Thanked every one of your posts
And I've asked too many questions for one person in one thread, I happen to have one more. How can I get the Android Market on Cyanogenmod? I downloaded build 115, and there wasn't a market, so i'll be using MIUI till I get that fixed. ><
Click to expand...
Click to collapse
You're more than welcome
If you've got any other questions, feel free to PM me
With CyanogenMod, there's a bit of a story to it, but basically, they're not allowed to package Market, Gmail, Maps, etc. with the ROM, so you need to download a zip file called Gapps and flash it in CWM Recovery, you can find it here. You don't need to wipe anything when flashing this.
Also, build #115 isn't the latest, build #117 is (in fact, there's another, even more current one, but there's really nothing to it), but I don't believe there's any major changes.
screamworks said:
You're more than welcome
If you've got any other questions, feel free to PM me
With CyanogenMod, there's a bit of a story to it, but basically, they're not allowed to package Market, Gmail, Maps, etc. with the ROM, so you need to download a zip file called Gapps and flash it in CWM Recovery, you can find it here. You don't need to wipe anything when flashing this.
Also, build #115 isn't the latest, build #117 is (in fact, there's another, even more current one, but there's really nothing to it), but I don't believe there's any major changes.
Click to expand...
Click to collapse
Hey, I was having troubles messaging you, since it didn't show anything in the sent box, i assumed it didnt go through. So i guess ill be still asking you on here.
So about Cyanogen, which build is the best? And if i'm going from one build to another, like from 115, to 116, would i still have to do a complete wipe? And any other roms besides MIUI and Cyanogen you recommend? cause MIUI is giving me and couldn't generate md5 errors, and i cant restore to it, and i hate starting off without it set up how i like it. D: and yeah, thanks.
Gutana said:
Hey, I was having troubles messaging you, since it didn't show anything in the sent box, i assumed it didnt go through. So i guess ill be still asking you on here.
So about Cyanogen, which build is the best? And if i'm going from one build to another, like from 115, to 116, would i still have to do a complete wipe? And any other roms besides MIUI and Cyanogen you recommend? cause MIUI is giving me and couldn't generate md5 errors, and i cant restore to it, and i hate starting off without it set up how i like it. D: and yeah, thanks.
Click to expand...
Click to collapse
I only just the message 12 hours ago, if that helps?
Usually, your best bet is to go with the latest build, which you can get here. If it's stability you're looking for, go with the stable build, instead of nightlies.
Personally, out of all ROMs I've tried, I could only ever stand MIUI and CyanogenMod - but even then, MIUI started to annoy me with little things here and there. I think I'll be sticking with CyanogenMod for awhile. So, I'm not really the best authority on that. Just try some different ones, and see what appeals to you the most

[Q] rom manager not recognizing fascinate

This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water

Categories

Resources