Related
I've updated my 3.1 to 3.1.1 and then to 3.2 using the following methods and I just realized that my bluetooth wont turn on. I've tried restarting / setting to airplane mode and clearing bluetooth share data and nothing works. Can anyone with the same experience help ?
Symtom :
When i Go Into Settings > Wireless & Networks > Bluetooth , and I hit the Bluetooth to power it on it says Powering On then it goes back to the Off Settings
From rooted 3.1 to 3.1.1 ( 8.4.4.11 ) I've flashed using this thread
http://forum.xda-developers.com/showthread.php?t=1178607
and to 3.2 using this thread
http://forum.xda-developers.com/showthread.php?t=1190877
I do use the bluetooth alot for tether so it would be nice if I can regain it's functionality.
may be due to corrupt file
flash the last file after checking md5
I am almost sure thatit is the flash fro 3.1 to 3.1.1 that did it s there anything that i can do now ?
I have the exact same problem and hoping I don't have to wipe everything again. I spent some time getting everything working. I flashed the .11 cwm full in the dev section then the 3.2 cwm zip. I might backup my data and flash again.
jetway1122 said:
I have the exact same problem and hoping I don't have to wipe everything again. I spent some time getting everything working. I flashed the .11 cwm full in the dev section then the 3.2 cwm zip. I might backup my data and flash again.
Click to expand...
Click to collapse
I am already on 3.2 what should i do and what do you mean by reflash ? Do you just redo the 3.1.11 and then 3.2 via CWM ? Won't that brick the TF ?
desilva79 said:
I am already on 3.2 what should i do and what do you mean by reflash ? Do you just redo the 3.1.11 and then 3.2 via CWM ? Won't that brick the TF ?
Click to expand...
Click to collapse
I believe it will, I mean nvflash to stock and try the whole process again. I'm in the process of backing up and attempting. I did try 3.2 cwm zip again but bluetooth still wont turn on so it must be the flash to .11 that messed things up.
Okay I'm not that smart.....can you be so kind to provide steps/forum thread on how to nvflash ? I know it's a process to flash back to stock / unrooted / without CWM ( just like out of the box ) ?
Had to step out but I'm back now and will try to reflash with nvflash and post the steps for you if it works.
Thanks a lot Jetway. That would be awesome.
I figure it would be something like use nvflash to 3.1
Asus Transformer NVFlash Stock 3.1 Recovery Roms
upgrade to 3.1.1 OTA
root it using the thread below ?
Batch script Pure Root Method for 8.4.4.11 & 8.6.5.6US - v5 beta update
use the CWM to flash to 3.2 ( there's also post on the thread above stating that you can just do OTA to 3.2 and then root it using the available script )
Sounds about right ? If you can still post your steps it would be awesome. Sorry I'm total noob in this.
desilva79 said:
Thanks a lot Jetway. That would be awesome.
I figure it would be something like use nvflash to 3.1
Asus Transformer NVFlash Stock 3.1 Recovery Roms
upgrade to 3.1.1 OTA
root it using the thread below ?
Batch script Pure Root Method for 8.4.4.11 & 8.6.5.6US - v5 beta update
use the CWM to flash to 3.2 ( there's also post on the thread above stating that you can just do OTA to 3.2 and then root it using the available script )
Sounds about right ? If you can still post your steps it would be awesome. Sorry I'm total noob in this.
Click to expand...
Click to collapse
You got it right, that's what I wanted to do and skip the Full 8.4.4.11 CWR ZIP but for some reason on .11 I cannot install any version of cwm not even the failsafe one and my tablet won't see the OTA either even with the stock flash and manual update from asus website.
So flashing with nvflash from link tabletroms brought back bluetooth and when I flashed Full 8.4.4.11 CWR ZIP I still have bluetooth! I rooted with the script in the dev thread and used the failsafe cwm. About to update to 3.2 and see if it still works.
Update: So when flashing the cmw 3.2 file this is where the bluetooth is lost. If only my device would see the OTA this could be solved. Im trying to redownload the zip file.
I got to grab another microSD card so I haven't started yet , but from the sound of it I should try to upgrade all the way to 3.2 ( if possible ) and then only try to root/cwm ( using the batch script v. 5 ) it by then ? What a pain in the bottom...... thanks for your help , at least I have someone with the same scenario that knows way much more than I do and can offer help...
Jetway , will this 3.2 OTA firmware be useful to you since you cant get the 3.2 from 3.1.1 ?
http://forum.xda-developers.com/showthread.php?t=1190868
I tried everything I could with the cwm files but once going to 3.2 I always lost bluetooth. So I looked at the thread you posted which I saw before but didn't read the whole thread and now that I did I was able to update to 3.2 (no root) + bluetooth working.
I nvflashed to 3.1 (.45 not .11) then I downloaded the ota ([the one from multiupload 60+meg one] )
imtiyazee:
I followed these instructions to flash:Instructions copied from gee one post
I had trouble applying the OTA manually. It was a pain.
If you are stock and NOT rooted, it's not too bad.
Download the US version of the update. There's a thread in the dev section I think.
Rename it to EP101_SDUPDATE.zip and save it to the root directory of the external micro SD.
Put the sdcard in the slot and reboot into recovery. You should see an android guy with a gear belly for 5-10 mins. Wait and be patient until you see your homescreen again.
To get into recovery, turn off the TF. Hold the volume down button and press the power button. As soon as the screen come on, you see some text at the top. Press volume up to boot recovery. If you wait too long, it will wipe your data, so back up anything important.
If you are rooted and/or you have a custom recovery, this probably won't work.
After all this I had 3.2 with working bluetooth, I will use the script to root but follow the above and you should be good as well
Update : I used the script v5 and rooted just fine, finally I'm done!!!!
Jetway, I'm confused , how did you update from 3.1.11 to 3.2 ?
Update: What a pain in the butt. I finally managed to finish installing everything. I did the same thing you did ( I should learn to read slower) . Thanks a lot Jetway
desilva79 said:
Jetway, I'm confused , how did you update from 3.1.11 to 3.2 ?
Click to expand...
Click to collapse
I didnt, i went from 3.1.45 not the .11. I went to tabletroms and grabbed the nvflash for us transformer. So i skipped the update you see, and i grabbed the 3.2 update from OTA thread as you posted. Get the 60meg one as its for updating from 3.1 (.45) version andfollowed the steps i posted about renaming the update file and putting it on an micro sdcard.
Awesome, I'm back to 3.2 Rooted /CWMed and Bluetooth freaking works ! Thanks Jetway112
Here's what we did , in case anyone needs help
Backup Apps using Titanium
Flash back to stock
Asus Transformer NVFlash Stock 3.1 Recovery Roms
upgrade to 3.2 OTA from ( 3.1 stock to 3.2 ) using the OTA file from this post
[OTA] STOCK 3.2 zip file.
root it using the thread below
Batch script Pure Root Method for 8.4.4.11 & 8.6.5.6US - v5 beta update
Restore Apps Using Titanium
Update CWM from this thread
[Recovery] ClockworkMod 3.1.0.1-solarnz-R3 Modded for Internal media
Np we helped each other out on this one for sure. Just glad that our bluetooth is working agian.
Someone needs to sticky this so that no one else goes from 8.4.4.5 to 8.4.4.11 then 3.2 like we did and lose bluetooth.
I've lost my Bluetooth too. I'm trying to find out how I can return to what I had before without losing everything. I did a android and a titanium backup so I'm hopeful.
Second that
Yeah I agree... it was a pain in the bottom to get the bluetooth back up. I'm going to post this thread over at the other 8.4.4.11 thread
Thanks a lot! Followed everything as u said and got BT back!
I believe this is my first post on these forums. I just did the nachoroot mod today per
[ROOT] NachoRoot - supporting all firmware jan 3rd 2-118
and
[Update: Works On The OG Transformer, Too!] Exclusive: 'NachoRoot' Brings Root Access To The Transformer Prime, Even With The Newest Firmware:
on my TF101 B80 32 gb.
I did the procedure per the second link above. I've been able to verify root with Root Check Basic from the Android Market.
I've never rooted an Android device before and am quite concerned about unrooting, in case I ever need to return my unit to Asus.
I've heard I need cwm, the clockwork recovery mod, in order to unroot. I hope it is ok to do this after the initial rooting procedure.
Please pardon me if this has been asked before, as it my first time, and I find a lot of the documentation a bit cryptic.
Thanks in advance...
Yes the procedure to unroot with your build number required flashing a repacked stock ROM via CWM recovery. For TF with older SBK they can use NVFlash.
You can flash CWM anytime with RecoveryInstaller
http://forum.xda-developers.com/showthread.php?t=1346180
To unroot
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Thanks fire the response!
I've managed to browse parts of the file system previously blocked. Otherwise, I haven't made another changes to my system. Its nice to finally where some of my apps have been storing data.
I am curious about cwm which I've installed. It enables recovery mode to restore the stock ROM. It is one of the two options presented after holding the power and volume down buttons together. One option is cold boot and the other is recovery. The recovery option was there before nachoroot and the cwm installations. What is different about the recovery option now versus before?
skallal said:
Thanks fire the response!
I've managed to browse parts of the file system previously blocked. Otherwise, I haven't made another changes to my system. Its nice to finally where some of my apps have been storing data.
I am curious about cwm which I've installed. It enables recovery mode to restore the stock ROM. It is one of the two options presented after holding the power and volume down buttons together. One option is cold boot and the other is recovery. The recovery option was there before nachoroot and the cwm installations. What is different about the recovery option now versus before?
Click to expand...
Click to collapse
Are you sure you have flashed CWM recovery? You should have a lot more options.
After installing RecoveryInstaller, did you open the app and click on "flash CWM recovery" tab?
I didn't click on the flash tab because I don't intend do recovery at this time. To be clear I understand what recovery is, I think it means to return my TF101 back to an unrooted state with the current ota release, which is .23, and also wipe out all my data. If this is incorrect, please let me know.
You said I should see more options than just the flash tab. What else should I see? And when should I see it?
Now that I've successfully rooted, my main objective is to learn how to return my device back to its unrooted state in order be ready for the ICS ota update when it arrives. If that means I'll also wipe out my data in the process, then I'll need to learn how to backup and restore.
Please do let me know if I understand the process or not. I still have have a reading and learning ahead.
Recovery lets you flash packages, ROM patches, and complete ROMs that require very deep (i.e. low level) system access.
If you don't intend to flash any custom ROMs (e.g. Revolver) or install things that need low level system access (e.g. a USB to Ethernet adapter) you won't need to flash CWM.
One of the admins on Transformer Forums gave me the impression I need cwm to unroot my TF101. That is the only reason I downloaded it.
If I don't need cwm to unroot, then I'll focus my reading on unrooting link listed earlier in this thread.
I don't have any interest in other roms, at least not for now. My concern, for now, is unrooting when it comes time for the ICS update...
baseballfanz said:
Yes the procedure to unroot with your build number required flashing a repacked stock ROM via CWM recovery. For TF with older SBK they can use NVFlash.
You can flash CWM anytime with RecoveryInstaller
http://forum.xda-developers.com/showthread.php?t=1346180
To unroot
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Click to expand...
Click to collapse
The second link above (theunlockr.com) refers to old firmware (repacked-8.2.3.13_US_without_SU_app.zip).
Is that file already outdated?
Perhaps a newer version for .21?
Well it all depends on your serial number. Early builds (B60 and earlier plus some B70) you can use NVFlash to get back to totally stock.
If you have B80(and some B70) and above you'll need cwm recovery to get back to stock following the link i posted above.
I finally watched the video from your earlier post and it answered a quite a few questions.
Bottom line: when it comes time to update to ICS, do I need to unroot first?
The ICS update is my main reason for unrooting. I read for some users lost root after the last ota update to .21. I don't have any immediate need to unroot other than to prepare for the ICS update when yet comes.
And there's also a long term need unroot when and if I ever send the unit back to Asus for service.
I decided to return to stock today so i could check out the newest ota which was not implemented in my fav rom yet. I soon realized its a pain in the ass to get there. Flash rom, update, update, etc, etc. And even worse is tracking down all the threads required for it.
Though I've narrowed it down to three or four, I thought i'd make a thread to put it all in one spot.
First off thanks to the members/devs that make these updates and roms for us. I dev on the HTC eVO 4g and know how time consuming and tedious it can be.
I am renaming and reuploading all the files required to ensure links stay current and are easy to follow. I will however be linking to all original threads where i got the files as well as giving props to the members who provided them.
I have a US version TF101 and will only be testing on that device. I dont know what works on tf101G, WW, TW models etc
I will update this thread as new rooted ota's come out.
ALL YOU NEED TO INSTALL IS A ALREADY ROOTED ASUS TRANSFORMER WITH A CUSTOM RECOVERY
THIS WILL NOT ROOT YOUR DEVICE, UN-ROOT YOUR DEVICE OR CHANGE YOUR CURRENT RECOVERY.
DONT FORGET TO BACK UP ALL YOURS APPS/DATA
FOR US VERSIONS ONLY
- STEP 1 - WIPE (DOWNLOAD) (This wipe zip was originally provided HERE by mike1986.
This script will erase and format your system and cache partition using EXT4 file-system ---Your external SD card and internal virtual SD card (/data/media) will remain untouched
- STEP 2 - FLASH STOCK ROOTED 9.2.1.11 FULL ROM AND REBOOT/SETUP (DOWNLOAD) originally provided here by MrNago
- STEP 3 - FLASH ROOTED OTA 9.2.1.17 AND REBOOT (DOWNLOAD) originally provided HERE by daoist
-STEP 4 - FLASH ROOTED OTA 9.2.1.21 AND REBOOT (DOWNLOAD) originally provided HERE by gee one
FOR WW VERSIONS ONLY
- STEP 1 - WIPE (DOWNLOAD) (This wipe zip was originally provided HERE by mike1986.
This script will erase and format your system and cache partition using EXT4 file-system ---Your external SD card and internal virtual SD card (/data/media) will remain untouched
- STEP 2 - FLASH STOCK ROOTED 9.2.1.11 FULL ROM AND REBOOT/SETUP (DOWNLOAD) originally provided here by MrNago
CANT FIND ROOTED VERSIONS OF THE NEXT FEW UPDATES THAT DONT REQUIRE ROOT KEEPER, SO IM STOPPING HERE. THIS WILL GET YOU STARTED THOUGH. i JUST DONT WANT TO BE RESPONSIBLE FOR NEWBS THAT CANT READ LOSING ROOT.
FAQ
-Will this root my transformer = no
-Will I lose root if i flash this = NO
-Can i flash this on top of a custom rom = NO
-Will this replace the custom recovery with the stock recovery? = NO, this will not touch your current recovery
-OMG, I lost root after this = NO you didnt or you did something wrong.
Can you explain why step 2 and 3 are needed?
You couldn't go from 1 to 4 if you want 9.2.1.21?
locutus7o9 said:
Can you explain why step 2 and 3 are needed?
You couldn't go from 1 to 4 if you want 9.2.1.21?
Click to expand...
Click to collapse
its my understanding that you have to have the last prior ota installed to be able to install the next. The last update may not include everything from the others.
Will this replace the custom recovery with the stock recovery?
xbs said:
Will this replace the custom recovery with the stock recovery?
Click to expand...
Click to collapse
I knew i'd forget one of the typicals in the FAQ..
Answer is no, this will not change/touch your current recovery
I wanted to return to stock Rom too, but I have seen your topic too late....
I first saved my root with rootsavekeeper
I have wiped cache and dalvik, and then install the rom
Now, I have a bootloop with the Asus logo, and if I try boot in recovery, I have the red robot
If u have a solution, I take it
Sorry for my english
jouix said:
I wanted to return to stock Rom too, but I have seen your topic too late....
I first saved my root with rootsavekeeper
I have wiped cache and dalvik, and then install the rom
Now, I have a bootloop with the Asus logo, and if I try boot in recovery, I have the red robot
If u have a solution, I take it
Sorry for my english
Click to expand...
Click to collapse
What ROM did you flash? If you flashed the official ROM from Asus you unrooted the TF.
Looks like you have stock recovery now.
Yes I have
My biggest problem is to get out on this sh*t Now
jouix said:
Yes I have
My biggest problem is to get out on this sh*t Now
Click to expand...
Click to collapse
Try this.
Hold Vol down plus power button
When you get the option of COld boot Linux or wipe data,
choose wipe data.
jouix said:
Yes I have
My biggest problem is to get out on this sh*t Now
Click to expand...
Click to collapse
What model do you have? B50, B60, B70?
If you have a B50 or B60, try this
Once you get back to stock honeycomb, you'll have to root it again.
@baseballfanz : Guy, you have saved my tablet .. I had almost throwed it in the garbage
@ldc2335 : I have bought it in France, and no idea about the version, sorry .. (I don't have the dock)
Well, now, I willl see if it is stable or not :
- if it is, I need to find the way to root it (but I have read it's not possible with the last Rom, right ?)
- if not ... I will try to return to Honeycomb and sell this piece of sh*t, and I will buy the Galaxy S3 or will wait for the Note 2
Thx again !!!!
I use NVflash way and from modded(rooted/CWM/Overclock) 9.2.1.17 directly flash back to stock clean 9.2.1.17 and it's very quick... and root it agan via Vipermod and flash 9.2.1.21 update zip.. Takes about lest than 30mins..
Thats one way to do it. I just dont wanna re-root etc.
Flash, reboot, flash, reboot, flash, reboot..done Definitly 30 mins or less.
jouix said:
@baseballfanz : Guy, you have saved my tablet .. I had almost throwed it in the garbage
@ldc2335 : I have bought it in France, and no idea about the version, sorry .. (I don't have the dock)
Well, now, I willl see if it is stable or not :
- if it is, I need to find the way to root it (but I have read it's not possible with the last Rom, right ?)
- if not ... I will try to return to Honeycomb and sell this piece of sh*t, and I will buy the Galaxy S3 or will wait for the Note 2
Thx again !!!!
Click to expand...
Click to collapse
If you can return to honeycomb, then just reroot and then flash any rom you want. Whats the issue?
Simple, clear, straightforward directions - very nice. The file naming is clever also, no "now which file do I flash next?..."
Does anyone have a clue where i can find cwm flashable WW Stock Roms with Original Recovery and no root?
Want to revert back to full basic!
(Tried to flash Stock Rom from Asus Website via CWM, didn't work...)
Try This
JohnMcLane said:
Does anyone have a clue where i can find cwm flashable WW Stock Roms with Original Recovery and no root?
Want to revert back to full basic!
(Tried to flash Stock Rom from Asus Website via CWM, didn't work...)
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=1558170
i just used the search bar above, im sure theres more than this one.
You will also need a NVflashable tf101 with this....
I hve succesfully flashed the .11 version, but when I try to update to the next version, it restarts, and starts loading the installation as it is supposed to, ut then it says "installation aported"
I am using Rootkeeper and CWM, and have temp. unrooted, I am using a B70 WW.
Anyone have a solution?
Sumsar94 said:
I hve succesfully flashed the .11 version, but when I try to update to the next version, it restarts, and starts loading the installation as it is supposed to, ut then it says "installation aported"
I am using Rootkeeper and CWM, and have temp. unrooted, I am using a B70 WW.
Anyone have a solution?
Click to expand...
Click to collapse
Same here, its an assert issue, I remember dealing with it when flashing my epic touch and I believe that had to do with the version of CWM that it was being flashed from
can anyone confirm?
EDIT: B40 using roach v5.5.0.4 r2 CWM
I am on stock(P3113 rooted+cwm)...I am getting an OTA for 4.0.4 but for that i'll need to go back to stock recovery...Should i :
1) Flash stock rom n then take the OTA
2) Flash 4.0.4 through odin [ http://samsung-updates.com/device/?id=GT-P3113 ]
3) Flash stock recovery n then take the ODA.
I would like to go with option 3 cuz it will require the min. amount of downloading....But for that i need stock recovery...So what should i do n is there any other way??
On my 5113 the only thing that worked for me was to flash with Kies and then reroot. It was well worth it though.
There doesn't seem to be an easy way to get just the recovery and I think (not sure) that only Odin can unlock that partition anyway. There are some stock images in Odin format and I have been meaning to pick through them to see if I can find the stock recovery image, but since no one has posted such, I am guessing you can't.
wd5gnr said:
On my 5113 the only thing that worked for me was to flash with Kies and then reroot. It was well worth it though.
There doesn't seem to be an easy way to get just the recovery and I think (not sure) that only Odin can unlock that partition anyway. There are some stock images in Odin format and I have been meaning to pick through them to see if I can find the stock recovery image, but since no one has posted such, I am guessing you can't.
Click to expand...
Click to collapse
But the problem is that i can't update vie kies...It keeps on disconnecting, so OTA is my only option n for that i need to get rid of CWM.
I am curious too, I rooted using this method, and have CWM installed.
http://forum.xda-developers.com/showpost.php?p=25480291&postcount=137
I guess I can just flash the stock image and loose root, upgrade, then reroot. Hopefully, someone will drop a stock, rooted and deodexed 4..0.4 rom for the P3113.
Also, I have not used Kies before, so I guess I don't even know how to flash the stock image for this tablet. Can anyone help with that?
fillyo said:
I am curious too, I rooted using this method, and have CWM installed.
http://forum.xda-developers.com/showpost.php?p=25480291&postcount=137
I guess I can just flash the stock image and loose root, upgrade, then reroot. Hopefully, someone will drop a stock, rooted and deodexed 4..0.4 rom for the P3113.
Also, I have not used Kies before, so I guess I don't even know how to flash the stock image for this tablet. Can anyone help with that?
Click to expand...
Click to collapse
To flash stock you'll have to use the stock rom n flash using odin,,, But i was hoping that there is way around it...
I've updated today my rooted P3113 to 4.0.4
This is the only way to upgrade rooted P3113 (with CWM), because the samsung official upgrade scenario doesnt works on CWM
1. Backup with Titanium
2. Wipe/factory reset with CWM
3. Download and unzip stock 4.0.4 firmware from here, then flash it with odin (PDA button)
4. Configure your device (now it's clean stock apps and stock recovery)
5. Restore your apps with Titanium
6. Install CWM and root - If you wish so (just as you installed on 4.0.3)
barmalei7 said:
I've updated today my rooted P3113 to 4.0.4
This is the only way to upgrade rooted P3113 (with CWM), because the samsung official upgrade scenario doesnt works on CWM
Click to expand...
Click to collapse
I would imagine this is just like the 5113. If you use Keis instead of the OTA update it works. Apparently Keis uses the USB instead of the recovery. However, a lot of people are having trouble getting Keis to stay connected. But I used it with no problems. Just reflashed CWM and rerooted as you say, but did not have to reflash to stock.
Just updated manually from 4.0.3 + Rooted + CWM 5.5.0.4 (GT3113)
Sorry too young to post links
Went very simple (10 minutes)
Returned to Stock Recovery: h://theunlockr.com/2012/06/02/get-samsung-galaxy-tab-2-7-gtp3113-back-stock
REBOOTED
Applied Update (not 4.0.4, not sure what it was)
Downloaded 4.0.4 from Samsung directly: h://samsung-updates.com/device/?id=GT-P3113
Unzipped to Desktop
Updated to 4.0.4 using ODIN (PDA)
REBOOTED
System applied update on startup
Asked me to select language, date, Goodle backup, etc
It loaded all existing Apps, Wi-Fi, etc automatically no TiRestore needed
Up and running, seems faster- smoother, new keyboard (old keyboard was good, this one is as good better for big fingers?)
:laugh:
Back to CWM & Root
h://forum.xda-developers.com/showthread.php?t=1722304
I downloaded the file from the Samsung site, launched Odin and updated. It kept all my apps and settings since I did not wipe. Flashed recovery, then rerooted, did not take long. If it gets yucky, I will do a factory reset.
Very helpful!
Very helpful guide.
On a semi-related note, I really like 4.0.4 it's certainly an improvement over the last and seems to have cured the stupid interface lag.
Ok flashed mine using mobile odin...no need to wipe data..
JacRyan said:
Just updated manually from 4.0.3 + Rooted + CWM 5.5.0.4 (GT3113)
Sorry too young to post links
Went very simple (10 minutes)
Returned to Stock Recovery: h://theunlockr.com/2012/06/02/get-samsung-galaxy-tab-2-7-gtp3113-back-stock
REBOOTED
Applied Update (not 4.0.4, not sure what it was)
Downloaded 4.0.4 from Samsung directly: h://samsung-updates.com/device/?id=GT-P3113
Unzipped to Desktop
Updated to 4.0.4 using ODIN (PDA)
REBOOTED
System applied update on startup
Asked me to select language, date, Goodle backup, etc
It loaded all existing Apps, Wi-Fi, etc automatically no TiRestore needed
Up and running, seems faster- smoother, new keyboard (old keyboard was good, this one is as good better for big fingers?)
:laugh:
Back to CWM & Root
h://forum.xda-developers.com/showthread.php?t=1722304
Click to expand...
Click to collapse
Your steps are so easy. I wish I could follow you on this, but I can't figure out how to revert back to stock recovery only. The theunlockr.com link shows how to completely revert the entire firmware. How do you revert recovery ONLY?
Hasn't someone made a .zip file that can be flashed with CWM? Why is it different than flashing a 3rd party rom?
Procedure if you ARE NOT running baseband JYUS06032013 (ICS Basebands) :
boot ICS CWM
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
restart start recovery/adb reboot recovery (JB CWM is installed - do not try to fastboot boot ICS CWM)
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
Procedure if you ARE running baseband JYUS06032013 (JB Baseband) :
get root (Instructions HERE - use GANDALF)
install CWM (Instructions HERE)
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
reboot to CWM
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
This ROM is Pantech stock stock stock with no mods other than CWM installation protection and all stock permissions and symlinks carefully maintained and consistent with the product of a successful OTA. It runs well with nothing broken. You MUST be on JB firmware (below) to run it properly.
The firmware is also stock, with the exception of the open aboot allowing fastboot boot <bootimage>, and installation of JB CWM with nothing else added or changed.
You can let the new CWM root it if you like when you exit - it will prompt you.
Downloads:
md5: 1a0ca5f177bce2f4c428931616e0ecd1 FLEX-JB-JYUS06032013-FIRMWARE.zip
md5: 17c0e611ab6dfbca230571c1e40f3d14 FLEX-JB-JYUS06032013-ROM.zip
Code:
[B]GPL INFO[/B]
The kernel used in the ROM is the unaltered, stock rom
and boot image provided by the Pantech OTA.
The kernel used in CWM provided I built from unaltered
Pantech provided source code.
The source code for both kernels can be obtained on the
[URL="http://opensource.pantech.com/"]Pantech Open Source[/URL] website.
:good::good::good::good::good::good::good:
much appreciated. i am dreaming of it will do it tonight and post the result.
attn1 said:
Procedure if you ARE NOT running baseband JYUS06032013 (ICS Basebands) :
boot ICS CWM
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
restart start recovery/adb reboot recovery (JB CWM is installed - do not try to fastboot boot ICS CWM)
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
Procedure if you ARE running baseband JYUS06032013 (JB Baseband) :
get root (Instructions HERE - use GANDALF)
install CWM (Instructions HERE)
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
reboot to CWM
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
This ROM is Pantech stock stock stock with no mods other than CWM installation protection and all stock permissions and symlinks carefully maintained and consistent with the product of a successful OTA. It runs well with nothing broken. You MUST be on JB firmware (below) to run it properly.
The firmware is also stock, with the exception of the open aboot allowing fastboot boot <bootimage>, and installation of JB CWM with nothing else added or changed.
You can let the new CWM root it if you like when you exit - it will prompt you.
Downloads:
md5: 1a0ca5f177bce2f4c428931616e0ecd1 FLEX-JB-JYUS06032013-FIRMWARE.zip
md5: 17c0e611ab6dfbca230571c1e40f3d14 FLEX-JB-JYUS06032013-ROM.zip
Code:
[B]GPL INFO[/B]
The kernel used in the ROM is the unaltered, stock rom
and boot image provided by the Pantech OTA.
The kernel used in CWM provided I built from unaltered
Pantech provided source code.
The source code for both kernels can be obtained on the
[URL="http://opensource.pantech.com/"]Pantech Open Source[/URL] website.
Click to expand...
Click to collapse
after a few days to stay with this JB on my flex. i found big problem with WIFI connectivity:
1 - connect and used about 10 to 30mn,, it is still connected but no internet.
2 - reconnect -> authentication problem.
3 - reboot a fews time to make wifi back to work.
4 - back to problem number 1
5 - Camera App still randomly cant be used unless restart. ( same problem since ICS )
6 - some intensive graphic games cause reboot the phone, eg Clash of Clans ( new in this JB)
What is good about JB is feel smooth and faster.
Any help, please?
Thanks @attn1! Works great.
Sent from my PantechP8010 using Tapatalk
tangbunna said:
after a few days to stay with this JB on my flex. i found big problem with WIFI connectivity:
1 - connect and used about 10 to 30mn,, it is still connected but no internet.
2 - reconnect -> authentication problem.
3 - reboot a fews time to make wifi back to work.
4 - back to problem number 1
5 - Camera App still randomly cant be used unless restart. ( same problem since ICS )
6 - some intensive graphic games cause reboot the phone, eg Clash of Clans ( new in this JB)
What is good about JB is feel smooth and faster. My wifi works fine, and the camera works fine.
Any help, please?
Click to expand...
Click to collapse
Try flashing my firmware package again, then flashing the ROM again. If you still have these issues, then wipe data/factory reset from clockworkmod. This is working for everyone else reporting, including me.
THIS work on Motorola defy
ela1103 said:
THIS work on Motorola defy
Click to expand...
Click to collapse
highly unlikely to impossible in this version of reality.
Look at mac address of both phone. They are the same. And both phone connected to the same ip of a router.
Even i use 2 routers, and connect one each, they seems to drop connection very often.
Unless a phone turn wifi off to let other one stay in good connection.
Do you have another alternative firmware file? So it could have different mac address ?
tangbunna said:
Look at mac address of both phone. They are the same. And both phone connected to the same ip of a router.
Even i use 2 routers, and connect one each, they seems to drop connection very often.
Unless a phone turn wifi off to let other one stay in good connection.
Do you have another alternative firmware file? So it could have different mac address ?
Click to expand...
Click to collapse
Looks like you restored the same /data backup to each phone. MAC address is determined by your wifi hardware, not this firmware.
attn1 said:
Looks like you restored the same /data backup to each phone. MAC address is determined by your wifi hardware, not this firmware.
Click to expand...
Click to collapse
I did not restore anything. While both phones on ics they both worked fine without duplicated mac address issue. Then i followed the instruction of the 2 files for upgrade to jelly bean. I didnt do any back up or restore. Just flash the firmware zip then jb rom zip the. Everything of my data are still there wifi are working fine untill i flash another phone to jelly bean too, both phone must have one wifi to turn off to make another one's wifi works fine.
Do you have the flex and upgraded to jelly bean by this two files? Could you tell me your mac address of your wifi ?
tangbunna said:
I did not restore anything. While both phones on ics they both worked fine without duplicated mac address issue. Then i followed the instruction of the 2 files for upgrade to jelly bean. I didnt do any back up or restore. Just flash the firmware zip then jb rom zip the. Everything of my data are still there wifi are working fine untill i flash another phone to jelly bean too, both phone must have one wifi to turn off to make another one's wifi works fine.
Do you have the flex and upgraded to jelly bean by this two files? Could you tell me your mac address of your wifi ?
Click to expand...
Click to collapse
Apologies. I've verified the problem, have traced it to mmcblk0p10, and here's a fix for you that changes the MAC by one:
Flash this from CWM:
md5: 4e7940c1b5d3690e0e38b083f224a7f1 OSCAR-WIFI-MACFIX.zip
NOTES:
This problem is because the hardware MAC is stored in that partition and read by the wifi firmware. It should never present a problem for people unless they have more than one Flex running this update on the same local area network subnet.
The MAC address starts in mmcblk0p10 at hex offset 30204, and an image file of this partition can be edited CAREFULLY with a hex editor and copied back to that partition. Doing this wrong may result in a bricked device.
attn1 said:
Apologies. I've verified the problem, have traced it to mmcblk0p10, and here's a fix for you that changes the MAC by one:
Flash this from CWM:
md5: 4e7940c1b5d3690e0e38b083f224a7f1 OSCAR-WIFI-MACFIX.zip
NOTES:
This problem is because the hardware MAC is stored in that partition and read by the wifi firmware. It should never present a problem for people unless they have more than one Flex running this update on the same local area network subnet.
The MAC address starts in mmcblk0p10 at hex offset 30204, and an image file of this partition can be edited CAREFULLY with a hex editor and copied back to that partition. Doing this wrong may result in a bricked device.
Click to expand...
Click to collapse
you are genius man! my wifi now changed from ending e9 to f9. no more duplicated :good::good::good::good::good:.
send me your paypal to my inbox, i will buy you a beer! :highfive:
big thanks and cheers !!!
Flex stuck on logo.
only 25% complete. then said signature verification failed?? pls help. (no cwm. only stock)
shusan said:
only 25% complete. then said signature verification failed?? pls help. (no cwm. only stock)
Click to expand...
Click to collapse
You have not provided enough information for me to help you. What was the detailed sequence of events leading to this. Be precise and make sure you list exactly the packages you flashed.
Flex stuck on logo.
thanks for ur quick reply. i was too sick to answer u. so sorry for late. i tried with sd memory update which show me 25% with stock image then show signature verrificatin failled. al most same result from fastboot. signature verification failed. no connection via ADB. i downloaded almost each and every rom and image i found from xda or other forum result r all same. sorry for my English. best regards
attn1 said:
You have not provided enough information for me to help you. What was the detailed sequence of events leading to this. Be precise and make sure you list exactly the packages you flashed.
Click to expand...
Click to collapse
shusan said:
thanks for ur quick reply. i was too sick to answer u. so sorry for late. i tried with sd memory update which show me 25% with stock image then show signature verrificatin failled. al most same result from fastboot. signature verification failed. no connection via ADB. i downloaded almost each and every rom and image i found from xda or other forum result r all same. sorry for my English. best regards
Click to expand...
Click to collapse
In recovery (cwm), check the md5 of the file on the sdcard against the posted md5 like so:
adb shell md5sum /path/filename
If it's not matching, you will get that error.
If you don't have the shipping ICS aboot, you may be stuck. You can't flash or boot images if you've taken the jb update. You still haven't detailed what you started with and what you have tried to do and where it went wrong, so it's hard to tell you exactly what to do or even if there is anything to do.
Any idea about stock rom? I don't have cwm. Only need to restore using original farmware. P8010 already stuck.
shusan said:
Any idea about stock rom? I don't have cwm. Only need to restore using original farmware. P8010 already stuck.
Click to expand...
Click to collapse
There is no stock firmware from Pantech available. If you messed up and can't boot with the JB bootloader, you are screwed.
attn1 said:
There is no stock firmware from Pantech available. If you messed up and can't boot with the JB bootloader, you are screwed.
Click to expand...
Click to collapse
No stock firmware from Pantech? I thought the firmware in the first post is STOCK? No? What about a caught copy from the OTA from AT&T?