I had my Gtab running stock 1.2 4349 and I screwed up while trying to install cwm v.8. I had not re-rooted my Gtab so instead of replacing the standard recovery with cwm I ended up with no recovery. After a few failed attempts to install cwm I gave up as I was worried I would wreck my Gtab. That was when I got the 5699 update around the beginning of Feb. Foolishly I tried to install it hoping it would install a recovery with the updated firmware. Now all I get when I boot it is "Booting recovery kernal image".
Is there anything I can do to save my Gtab? Thanks in advance for any help.
Go here http://viewsonic-gtablet-for-dummies.webs.com/ follow instructions for code red. You will be fine.
Thank you so much for the help. My Grab is alive again and running ICS!
Sent from my Malata SMBA1002 using xda premium
Related
I did the OTA update today, and attempted an install of CWM. I'm not sure if it went all the way through.
The tablet was still working fine.
When attempting to load an update of 4349 with market, the gtab gets stuck at "booting recovery kernal image".
Now the g-tab will not load at all. I attempted the NV Flash procedure but it failed at the final step during the batch where it could not find the file.
Any tips on what I should do next?
which method? Linux, windows?
windows version.
if you can, give us a list of files in your nvflash directory.
thank you, you got me in the right direction. i did not extract the gtablet file.
yea, with all these tools available, it's really hard (is it possible?) to brick g-tab . ..
210danielz,
Unless I misunderstood your first post, it sounds like you have a CWM problem.
Running CWM with 4349 will cause semi-bricks -- and several of us have tried
to post warnings to that effect all over the forum.
IMO, you probably should NVFlash back to stock and let the OTA update take
you back to 3588. Then you will be stock with a solid rom and can do what you
want.
http://forum.xda-developers.com/showthread.php?t=861950
Good Luck,
Rev
210danielz said:
I did the OTA update today, and attempted an install of CWM. I'm not sure if it went all the way through.
The tablet was still working fine.
When attempting to load an update of 4349 with market, the gtab gets stuck at "booting recovery kernal image".
Now the g-tab will not load at all. I attempted the NV Flash procedure but it failed at the final step during the batch where it could not find the file.
Any tips on what I should do next?
Click to expand...
Click to collapse
Here is more info on 4349.
http://forum.xda-developers.com/showthread.php?t=1035983
Roebeet ran a lot of tests and found that 4349 is not compatible with CWM.
210danielz,
When someone gets a bad NVFlash like that I always tell them to:
Take the procedure and go through and check everything. Make sure right
.zip files used. Check every little detail.
Re-run the NVFlash.
If previous step fails again, try nvflashing CWM only:
http://forum.xda-developers.com/showthread.php?t=1030042
If you get a good flash on CWM and get it up, the go to the
Advanced Menu and Partition (2048/0), Fix Permissions, Wipe
Dalvic Cache. Then Return to Main Menu and Wipe Cache
and Wipe/Reset Factory Data.
Having done the above, shut down and go back and NVFlash
to stock again (having cleaned out and repartitioned to
hopefully make it work right this time!)
Hopefully this will give you a working G-Tablet with Bekit 1105
or stock Version 2638 on it. If you set up wifi it will pretty
quickly offer you an OTA to 3588.
From there you can go where you want.
Hope this helps,
Rev
Just rooted latest UCKK1 leak and installed cwm recovery but when I boot into recovery mod 3e recovery starts. Can anybody tell me how to boot into cwm recovery
If you'd done a serach you would have found out that were having trouble doing that.
The only way right now is to push a kernel with it.
Or installed Jordans version.
Truckerglenn said:
If you'd done a serach you would have found out that were having trouble doing that.
The only way right now is to push a kernel with it.
Or installed Jordans version.
Click to expand...
Click to collapse
Any solution yet? I went to restore but could only get green, tried a restore anyway thinking it might be ok since it was a restore, then when I rebooted, now I'm stuck not getting past samsung logo. Not even 3 fingers is working. Kinda nervous...help?
I'm using my old school droidX, cuz my Infuse is in the shop
EDIT: Just used GTG's unbrick, finishing up my root then I'll be back up and flashing
I returned my original transformer that I rooted and installed Revolver on because of a bad touchscreen. Now on my new one I can't get to recovery. I rooted using razorclaw again, but when I try to get into recovery I get the android with an exclamation point. Any help would be appreciated.
Did you install CWM recovery?
Razorclaw only root. RecoveryInstaller
http://forum.xda-developers.com/showthread.php?p=19319421
Yeah, I found my mistake moments after I posted this. I was thinking there was a stock recovery to install CWM from. I forgot about the installer. Thanks for setting me straight. Back in business now.
I brought a transformer tf300 a few days ago that was already rooted and unlocked. I can't get adobe flash to work. I tried side loading a few version of adobe but still no success. Google market says my device is not compatible with adobe. I don't think the rooted device really serves me any purpose so I would like to take it back to factory condition. I need some help doing it since I have never rooted a device before.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
Thanks for all your help if you can. I will need step by step instructions, and thanks again for the help
jflynn0 said:
I brought a transformer tf300 a few days ago that was already rooted and unlocked. I can't get adobe flash to work. I tried side loading a few version of adobe but still no success. Google market says my device is not compatible with adobe. I don't think the rooted device really serves me any purpose so I would like to take it back to factory condition. I need some help doing it since I have never rooted a device before.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
Thanks for all your help if you can. I will need step by step instructions, and thanks again for the help
Click to expand...
Click to collapse
download the latest firmware from the asus site first. http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Then install the current software version. You can use the instructions from here to reflash stock rom in post 2
http://forum.xda-developers.com/showthread.php?t=1668173
dxwilliams40 said:
download the latest firmware from the asus site first. http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Then install the current software version. You can use the instructions from here to reflash stock rom in post 2
http://forum.xda-developers.com/showthread.php?t=1668173
Click to expand...
Click to collapse
don't know what im doing wrong when i try to flash the stock rom i get stuck as the ASUS splash screen with spinning wheel. Any suggestions?!?
cjohnsonthe2nd said:
don't know what im doing wrong when i try to flash the stock rom i get stuck as the ASUS splash screen with spinning wheel. Any suggestions?!?
Click to expand...
Click to collapse
Did you unzip the firmware and flash the zip named "US_epad-user-9.4.3.29"?
dxwilliams40 said:
Did you unzip the firmware and flash the zip named "US_epad-user-9.4.3.29"?
Click to expand...
Click to collapse
yes and CWM says install from sd card complete, no errors. I get the intial boot screen with the blue progress bar then I get stuck at the spash screen with the spinning wheel.
Luckily I had a nandroid of my AOKP setup and can go back to that. Ive tried a few times today to return to stock with the same results.
cjohnsonthe2nd said:
yes and CWM says install from sd card complete, no errors. I get the intial boot screen with the blue progress bar then I get stuck at the spash screen with the spinning wheel.
Luckily I had a nandroid of my AOKP setup and can go back to that. Ive tried a few times today to return to stock with the same results.
Click to expand...
Click to collapse
Remember to full wipe before installation including /system and after clear dalvik and cache then fix permissions.
By not wiping /system can cause some data to be left and corrupt stock installation had this happen on my g2x and have seen it on some other threads.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
I wiped the cache before I started the install and now when I boot into the usb fastboot my comp flashed a bootloader notification but then nothing else happens. I tried it a second time and I dont even get the notification. Also if I let it boot regular the Asus screen shows when i first boot but then nothing ever comes up just black screen
I have a Rogers Infuse 4G (i997r) and I have been trying to upgrade it to kitkat by using a unofficial Cyanogenmod rom. More recently have been trying to use Carbon rom to update it. I have been running into problem after problem, error after error and I have finally decided to post something on XDA in hopes that someone with more experience can help me out. More information about the errors and what I have done to the phone below.
About a year ago I got this Rogers infuse 4G from a friend. I messed around with it for a bit but what I really wanted to do with it was install a custom rom and update it to a more recent version of Android (It started out on gingerbread (2.3)).
I had a real hard time getting modified recovery 3e because there was not original recovery file in system>bin to replace.
I forget most of what happened but it ended with me using a application to convert the cwm recovery zip to a md5 because I couldn't get modified 3e to work.
I tried using odin to flash the files I made but odin got stuck (or was just taking forever) and I unplugged my Infuse.
The infuse was bricked and would only show "firmware upgrade encountered an issue please select recovery mode in kies and try again". The phone would'nt enter recovery or download mode. It was recognized by odin but seemed as if it was not responding.
About 3 days ago I finally decided to try to unbrick the phone again (I don't know why just felt like it) and I found GTG ultimate unbrick with a pit file. I tried uploading this using odin and the phone responded and downloaded the files.
The phone showed a AT&T splash screen and then the Samsung logo. It hanged at the Samsung logo for about 3 minutes then would turn off reboot, show the AT&T splash screen then the hang at the Samsung logo for 3 minutes again.
I decided that I didn't actually need to install working android because I just needed CWM Recovery and found a CWM Recovery that was flashable with odin.
Now that the phone would actually show a splash screen I could access download mode and the stock 3E recovery.
I went to download mode and flashed CWM Recovery 6 - Voodoo Lagfix with odin
In the CWM Recovery I clicked install update.zip
The phone said installing and when it finished it rebooted.
It showed the AT&T logo and then the Samsung screen then it started talking (which btw scared the **** out of me) and it said installing voodoo lagfix, estimated time remaining 2 minutes
After it was done installing it rebooted and I had the same problem as before. It would show the AT&T logo then hang at the Samsung screen for 3 minutes.
I reflashed the GTG unbrick with odin then I reflashed the CWM Recovery and I was back into the recovery. (It wouldn't just let me boot into it I had to reflash it which was weird)
This time instead of clicking install update.zip I installed the Cyanogenmod-11-infuse-4g-unofficial-2014(some build number).zip
I got (status 7) installation aborted.
when the phone rebooted it showed a cyanogen mod loading screen and I got really excited
after the loading screen it went straight to proper CWM Recovery then it instantly crashed with a little fallen over Android and a red triangle over it.
It kept boot looping like this so I asked for the unbrick files for a Rogers Infuse 4G and installed those.
Once I installed the Rogers Infuse 4G Rom I set it up but I ran into the same problem I had last time.
I can't install the modified 3E recovery because the recovery file is not system>bin. CWM Recovery also fails to install even though it says it has installed.
It turns out the recovery file is on the root of my phone not /system/bin
Im not really sure what to do and guidance would be appreciated.
It's because the CWM is not only device specific, but carrier specific (at least for the Infuse).
Flash the following file (extracted) with Odin. It will talk to you as well after reboot, but it will give you CWM red which you can use to move on to custom ROMs:
https://www.dropbox.com/s/t0kc92124jat6yt/CWM Infused Kernel.zip?dl=0
Be sure to disable Voodoo Lagfix before installing any ROM's, especially if shortcut'ing directly to CarbonROM (versus installing CM9, then CM10.1 and finally a KitKat ROM).
Good luck, let me know if you have any questions.
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error. Accidentally Double Posted... Im a noob. If someone could delete this repost it would be appereciated
OnfireNFS said:
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Click to expand...
Click to collapse
Just to be clear. With the original ROM file, did you try installing the ROM with this CWM and Voodoo Lagfix disabled? That is go into CWM's options menu, and disable there?
Just trying to pick the low hanging fruit, unfortunately I don't know where to go from there (as this is my only idea now, besides re-downloading the ROM).
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
OnfireNFS said:
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
Click to expand...
Click to collapse
It used to be that in order to get from Gingerbread to say, Jellybean, you needed to install the Ice Cream Sandwich ROM (CM9) first. This gives you a relatively new CWM in order to do your bidding. But you man need to install a Jellybean ROM (I suggest CM10.1) in order to get a CWM that will like the installation of KitKat.
So Stock (Infused CWM) -> CM9 -> CM10.1 -> CarbonROM 4.4.4
Of course, I did say used to. Apparently if you disable Voodoo lagfix in CWM you can go straight to CarbonROM. I never tried it, but it is worth a shot (avoids having to go on a scavenger hunt).
But if you already tried it with no success, now you know the classical way.
Thanks a lot. By upgrading to cm9 then cm10 then finally Carbon Rom I was able to get the phone to kitkat!
Cheers