Related
On my last 3 androids I usually got updates early and just flashed the zips in recovery on my stock androids. I've had a tough time figuring out the process on my vibrant though. Is it the same process with the vibrant? Because when I searched it seemed like Odin and kies were mentioned often but I haven't used either and I'm not sure where to start. Is there a simple zip of froyo I can flash on my stock vibrant? I really planned on waiting for the ota but at this point my nexus will have gingerbread first and then ill go back to using it daily again so I'd like to have some time with a more smooth and snappy, flash and tether enabled vibrant..
Check out the stickies
Chalup said:
Check out the stickies
Click to expand...
Click to collapse
Thanks, can you give me another hint?
Actually I did read the stickies thoroughly before i posted this thread, the closest thing i found were instructions for installing the 2.2 version of the market which was in the really long sticky so i maybe missed what youre referring to, that sticky said the first post was about root issues but i still looked through the entire thing, both posts. i also checked the sticky in the development section. I went back to double check just now but i still dont see information about flashing froyo on a stock vibrant if its even possible. and fyi here is what i found before posting my question, these are just a few of the threads i checked. There are some "stock froyo roms" but im pretty sure they are still mods requiring root. There are many "froyo" type threads in development section. Im still trying to figure out if its even possible to flash froyo if im not rooted
http://forum.xda-developers.com/showthread.php?t=836222
http://forum.xda-developers.com/showthread.php?t=837763
http://forum.xda-developers.com/showthread.php?t=833563
Download your desired rom and save it to internal or external sd card, back up everything u don't want to lose. Flash clock work recovery , reboot into clock
Work, go to install zip from sd card, choose yours, install then reboot, enjoy.
Sent from my SGH-T959 using XDA App
ronjeremy11 said:
Thanks, can you give me another hint?
Actually I did read the stickies thoroughly before i posted this thread, the closest thing i found were instructions for installing the 2.2 version of the market which was in the really long sticky so i maybe missed what youre referring to, that sticky said the first post was about root issues but i still looked through the entire thing, both posts. i also checked the sticky in the development section. I went back to double check just now but i still dont see information about flashing froyo on a stock vibrant if its even possible. and fyi here is what i found before posting my question, these are just a few of the threads i checked. There are some "stock froyo roms" but im pretty sure they are still mods requiring root. There are many "froyo" type threads in development section. Im still trying to figure out if its even possible to flash froyo if im not rooted
http://forum.xda-developers.com/showthread.php?t=836222
http://forum.xda-developers.com/showthread.php?t=837763
http://forum.xda-developers.com/showthread.php?t=833563
Click to expand...
Click to collapse
Honestly rooting isn't even that big of a deal, what I would suggest is to go download the one click root (or use One Click Lag Fix from the market), it really is simple.
I'm not sure how to use Kies (haven't used it myself), but odin is simple, this is the video that helped me when I first flashed it. I think ODIN is only used to go back to the stock firmware which you can find on the forum.
http://www.youtube.com/watch?v=AnY7P14JSWQ
To do the one click root, you turn on USB debugging and plug in your usb cable into your computer (don't mount the drives).
Open one click root and click root, it will copy over the files and do it's thing, then your phone will reboot into recovery mode and all you do is scroll down to "re-install packages" using the volume key and use the power key to select, then your phone will reboot once again and when it starts up you should be rooted (you'll have a super user app in your app drawer).
Then when you're rooted, you install Rom Manager from the market. After installing rom manager, flash the Clockwork Recovery (the very first option) and go download a froyo rom of your choosing from the development section. Right now, choose the option to backup your rom (just a safety net in case something goes wrong, you'll be able to come back to where you are now). When this is done, mount your phone on your computer and copy the back up to your computer. Then copy the downloaded rom to your internal sd.
Once you are flashed with clockwork recovery, all you have to do in rom manager is pick the option "Install ROM from SD Card" (assuming that you have already copied the rom to your internal sd card (not the microsd)). After this the phone should reboot and start the installation process. The advice given is to leave the phone alone for the first 15 minutes after it boots up, restart the phone, and wait another 5 minutes before messing with it.
Thank you. And just to be completely clear, i take ifrom the rooting instructions and affirmations that flashing a froyo image on an unrooted vibrant is not an option...In the past I have rooted my nexus and g1 so clockworkmod/flashing in recovery, this is all familiar, I'm guessing 1 click root is similar to the nexus version in that 1 click can unroot as welll? This all sounds good so I guess ill just try to sift through all the custom Froyo Rome in dev section and try to locate a stable and as stock as possible version. I'm going to wait until later on Monday, between now and then will be my last expressed hope of hearing an update about the existence of an official froyo ota update for the vibrant. But I've read a lot about Samsung and their odd software update complex so I wont be holding my breath. But come hell or high water I will soon have full adobe flash, tethering, a smooth UI , etc., e tc., etc.
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.
Hi, This topic should have been a reply to the AiO one on the development board but since the board software thinks I'm too new to post to developments forums I'm forced to create a new topic here on General, So I'm really sorry if I did something wrong (Guess what, I'm new!)
So, I wanted to upgrade my Tablet S to a pre-rooted ICS while I had a 3.2.1r2.
I rooted it, did all the steps to have a working custom_update.zip,while flashing the custom_update thing, text warned me that I was flashing the pre-rooted, init.d'ed, whatever custom rom, so I though it was all going to be fine..
Then I discovered that Superuser wasn't there, neither was busybox and basically root in general was gone, while the "rescure-backdoor" wasn't.
Checking the topics I discovered that my best solution was to downgrade to 3.2.1r2 and do the whole thing again.
So that's what I did, I wiped the whole system and Honeycomb started without problem, except that it turns back to not-really-pre-rooted ICS the next time I reboot.
This wouldn't be a problem if it wasn't for the fact that I need to reboot the tablet some times to get root, and I need root to decrypt and prepare the custom update.
So, what am I doing wrong? I searched here and there and didn't find a solution yet .
Sometimes you need to do a factory reset or else it flips back to ICS from HC. I haven't always had to do it; I'm not sure what the contributing factor is there. Essentially there are two system partitions (system0 and system1) and the bootloader makes a decision on which one to boot based on unknown criteria. It can be a bit quirky after downgrading, but a factory reset seems to clear it up.
SOLVED.. but how?
I knew that, I wiped everything each time I reverted to 3.2.1, maybe I forgot to mention that.
But it didn't directly boot to ICS, it did boot to Honeycomb, THEN the next time I boot I'm back to ICS again.
I did manage to stop this, however.. how? I don't know, something like the 4/5th time I re-flashed it worked.
Hamcha said:
I knew that, I wiped everything each time I reverted to 3.2.1, maybe I forgot to mention that.
But it didn't directly boot to ICS, it did boot to Honeycomb, THEN the next time I boot I'm back to ICS again.
I did manage to stop this, however.. how? I don't know, something like the 4/5th time I re-flashed it worked.
Click to expand...
Click to collapse
Wipe before first boot of 3.2.1 is VERY IMPORTANT.
Downgrade step-by-step is described in AiO thread in FAQ section.
br
condi
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737
Hello,
I was able to root my SGSII GT-I9100T using Clockworkmod. I then proceeded to flash Android KitKat but during that procedure, my phone displayed an error with the emmc (or something like that) and the installation was aborted. I can get onto the Recovery screen but I can't get any further, i.e. I can't get to my apps, messages etc.
I do not have a backup of prior to the error in the flash. The top of the screen I am able to see says: CWM-based Recovery v6.0.1.2-Siyah. I have wiped my data and cache with no luck. Everytime I reboot, it goes back to the same screen.
Also, I am with Vodafone Australia, and they do not appear to have a downloadable stock ROM.
I want to get my phone back to prior to rooting, obviously with the default settings (but this doesn't matter).
What should I do? Am I able to repair it?
Yes, you're able to repair it easily. If you don't have any backup, doing a wipe from recovery (which can sometimes fix this) isn't an option for you because obviously you'll lose data if you wipe. I'm also thinking perhaps you've flashed the wrong version of Siyah; you could always re-read (or read) the Siyah threads on here to make doubly sure you've flashed the correct build for your Android version (I don't remember which is which, been ages since I've used Siyah), and if it is a case of you having flashed the wrong build, flashing the right build might well solve your problem & give you a rooted phone. You could also find the PhilZ thread on here, read it, and flash that which should also help you to achieve that aim.
But...if you really want to go back to where you were before you started...
Download a stock rom for Voda AU from Samfirmware (Doesn't matter which one, up to you. You'll need to sign up in order to do so), and flash it following the instructions in the thread titled 'Flash Stock firmware/ROM...' stickied near the top of Q&A.
If you're unable to get a successful Odin flash/or it fails for whatever reason, find Hopper8's 'Odin troubleshooting' guide stickied in the General section & try the stuff in that thread, which should enable you to get through any issues & get a successful Odin flash which will take your phone back to the state it was in before you attempted to root it.
Normally flashing a one part stock rom like this won't involve data loss, but there are never any water-tight guarantees.
Edit - For future reference, if you ever decide to mod your phone even slightly, always back everything up before you do anything. Don't be like the 95% of people on here who do this & then end up in the **** because they didn't back stuff up. The reality is, if you're going to mod, stuff goes wrong eventually for everyone (as you've just found out).
Thank you, I will attempt to flash a stock from that website.
Just to clarify, I first installed CWM (not the Siyah version), and that was working fine. I was able to boot and do whatever. I then proceeded to flash an Android KitKat ROM but this resulted in an error. I then flashed Siyah (which may have made it worse) because from what I read at the time, it could have fixed my problem. So it must have been from the ROM, whether it be my phone being not compatible with it etc., rather than the wrong version of Siyah (although, as I said before, it could have made it worse).
Yep, rom incompatibility. Siyah stopped being developed with ICS, so won't work with KK roms; kernels need to be compatible with the Android version of the rom in question.
Doing what you did is no drama usually, worst case result is normally what happened to you I.E bootloop which won't go away without going back to stock, unless you get a bad flash. It's actually a good learning experience, because now you'll know how to recover if you flash stuff in future
I managed to flash the stock version and thankfully, my phone is back to 'normal'. Luckily I always had intentions on resetting it to factory settings. Indeed it has been a good learning experience :good: Thanks for your help, MistahBungle.
No worries. Glad you got it sorted