Please help me to get to JH7 - Captivate General

Hi Gurus,
While everybody is trying 2.2, I am still stuck on FJ6 (or incomplete JH7).
Here's the history:
1. Got the phone on day 1 of release.. loved it and still love it. No GPS issues - first lock took 20 secs and subsequent locks took 6 seconds at most.
2. Rooted and unlocked the phone, deleted all AT&T crapware. Running Launcher Pro, Tiatinum backup etc.
3. Installed Lagfix - was happy with a high quadrant score
4. Saw that the JH7 OTA is out
5. Read up on the forums here and unlagged lagfix.
6. Initiated the OTA update, went all the way thru, and got the message "update failed - No updated available" after restart. GPS is messed up.
7. Settings --> About Phone shows this
- Firmware version: 2.1-update1
- Baseband Version: I897UCJH7
- Kernel Version: 2.6.29 [email protected] #2
- Build Number: ECLAIR
8. Went to plan B - Kies Mini, was able to connect but stuck at "Unregistered screen".
9. Got frustrated and called Samsung.
- They said that the OTA upgrade worked "half way thru". They were expecting something after the "ECLAIR" in build number and I should not see the "PC Internet" as an option under USB Settings.
So Samsung said that they will have to reflash the phone to JH7 and have asked me to send the phone in.
1. I will be without a phone for 4-5 days which sucks.
2. They may (an will?) see my shenanigans (root etc) on the phone even after a hard reset ??
What are the implications? Is there any way around this? Can I do something (or follow some instruction by myself) to fix this? I am ok going back to stock AT&T firmware - to need to mess around with removing crapware etc. I would just like to keep the phone "unlocked" (I travel overseas quite a bit).
I have read thru most of the form postings.. which confused me more. At this point of time, I have a "brain freeze" and would appreciated a "just do this and then this" type of instruction.
Ironically, ever since switching from Windows Mobile to android, I have been a big proponent of this phone and operating system. Now I am beginning to see the downside of being on the leading/bleeding edge..
Please help..
Nick

You can always use ODIN and flash it that way...
http://forum.xda-developers.com/showpost.php?p=8567598&postcount=6

defriend said:
Hi Gurus,
While everybody is trying 2.2, I am still stuck on FJ6 (or incomplete JH7).
Here's the history:
1. Got the phone on day 1 of release.. loved it and still love it. No GPS issues - first lock took 20 secs and subsequent locks took 6 seconds at most.
2. Rooted and unlocked the phone, deleted all AT&T crapware. Running Launcher Pro, Tiatinum backup etc.
3. Installed Lagfix - was happy with a high quadrant score
4. Saw that the JH7 OTA is out
5. Read up on the forums here and unlagged lagfix.
6. Initiated the OTA update, went all the way thru, and got the message "update failed - No updated available" after restart. GPS is messed up.
7. Settings --> About Phone shows this
- Firmware version: 2.1-update1
- Baseband Version: I897UCJH7
- Kernel Version: 2.6.29 [email protected] #2
- Build Number: ECLAIR
8. Went to plan B - Kies Mini, was able to connect but stuck at "Unregistered screen".
9. Got frustrated and called Samsung.
- They said that the OTA upgrade worked "half way thru". They were expecting something after the "ECLAIR" in build number and I should not see the "PC Internet" as an option under USB Settings.
So Samsung said that they will have to reflash the phone to JH7 and have asked me to send the phone in.
1. I will be without a phone for 4-5 days which sucks.
2. They may (an will?) see my shenanigans (root etc) on the phone even after a hard reset ??
What are the implications? Is there any way around this? Can I do something (or follow some instruction by myself) to fix this? I am ok going back to stock AT&T firmware - to need to mess around with removing crapware etc. I would just like to keep the phone "unlocked" (I travel overseas quite a bit).
I have read thru most of the form postings.. which confused me more. At this point of time, I have a "brain freeze" and would appreciated a "just do this and then this" type of instruction.
Ironically, ever since switching from Windows Mobile to android, I have been a big proponent of this phone and operating system. Now I am beginning to see the downside of being on the leading/bleeding edge..
Please help..
Nick
Click to expand...
Click to collapse
You hacked your phone, now it won't update and you think it is because android is on the bleeding edge.
If you had reverted to stock first (odin one click) you may have had success. Maybe it would kill your unlock -some it does, some it doesn't.
Some phones had trouble updating even from stock - but unless you put it back - you will have no baseline. You need to make it stock before you send it anyway - or they may just return it because you did root and modify it.

Use Odin to do a master clear, flash back to JH6 with Odin, then do the JH7 update via your phone or with Kies, then you can do the one-click root.
Or just skip JH7 and bump up to JI6.

Thanks for the link...
Some more questions:
1. Will this clear my unlock? I forgot to write down my unlock code. Is there a way to get it out again before the flash?
2. Will this completely eliminate all traces of modifications?
3. What about my apps? I have a appbrain account, will I use that to revert? What about paid apps?
Thanks in advance..
Regards
Nick
verysafety said:
You can always use ODIN and flash it that way...
http://forum.xda-developers.com/showpost.php?p=8567598&postcount=6
Click to expand...
Click to collapse

Thank you all for your help. I was able to upgrade to JH7.
1. Did the JF6 Odin 1-click update (did NOT do a Master Clear)
2. Once back to baseline, I uses Keis Mini to upgrade to JH7 - worked flawlessly
3. Rooted using Lagfix (did not install lagfix though)
4. Installed appbrain app - I see all the apps that I need to re-install. I installed some, but will wait to get home and do the "Once Button" install over wifi
5. Titanium Backup was not able to Restore Apps (no 3rd part app installation allowed). Will just wait for appbrain to do its thing and restore app data only from Titanium backup (hopefully this option exists).
6. Restored all screen from Launcher Pro backup - widgets are messed up, but not a big deal
This definitely worked out, especially comparing to the alternative of sending in the phone and what not..
As a bonus, GPS performance is fantastic - caught 7 satellites in 5 seconds 30' accuracy with my phone near my office window (did not even have to go outside). Will test more with maps on my way home..
Falling in love with Android all over again
Once again, a BIG thanks to those who helped.
I will wait for a few days before taking on 2.2 .. gulp..
Regards
Nick
defriend said:
Thanks for the link...
Some more questions:
1. Will this clear my unlock? I forgot to write down my unlock code. Is there a way to get it out again before the flash?
2. Will this completely eliminate all traces of modifications?
3. What about my apps? I have a appbrain account, will I use that to revert? What about paid apps?
Thanks in advance..
Regards
Nick
Click to expand...
Click to collapse

Just wanted to report back, GPS is awesome now. Takes max 10 seconds (first time) when fired from Google Maps. Subsequent locks are taking no more than 6 seconds.
Also, did not find a way to just restore app data from Titanium Backup. So had to recreate some stuff .. no biggie. Anybody know of an alternative backup app that will actually let me restore apps and stuff - which is the point of a backup app!!
Regards
Nick
defriend said:
Thank you all for your help. I was able to upgrade to JH7.
1. Did the JF6 Odin 1-click update (did NOT do a Master Clear)
2. Once back to baseline, I uses Keis Mini to upgrade to JH7 - worked flawlessly
3. Rooted using Lagfix (did not install lagfix though)
4. Installed appbrain app - I see all the apps that I need to re-install. I installed some, but will wait to get home and do the "Once Button" install over wifi
5. Titanium Backup was not able to Restore Apps (no 3rd part app installation allowed). Will just wait for appbrain to do its thing and restore app data only from Titanium backup (hopefully this option exists).
6. Restored all screen from Launcher Pro backup - widgets are messed up, but not a big deal
This definitely worked out, especially comparing to the alternative of sending in the phone and what not..
As a bonus, GPS performance is fantastic - caught 7 satellites in 5 seconds 30' accuracy with my phone near my office window (did not even have to go outside). Will test more with maps on my way home..
Falling in love with Android all over again
Once again, a BIG thanks to those who helped.
I will wait for a few days before taking on 2.2 .. gulp..
Regards
Nick
Click to expand...
Click to collapse

Related

[TUT][HOW TO] Netflix On Galaxy S 4G + Problems Encountered

You need to flash your device for it to work!
This is the Rom I used to get netflix working
http://forum.xda-developers.com/showthread.php?t=1131230
I recommend to use Titanium Backup, this Rom is Rooted but i can not get CWM working.
Netflix app used with the Rom:
http://forum.xda-developers.com/showthread.php?t=1076150
Use this one "com.netflix.mediaclient-1.apk is Netflix 1.2.2 (Released 6/15/11)"
About the Rom & App:
So far the Rom is perfect and great, The Rom has a nice style and is a little bit more faster than the old official stock Rom. Netflix works great on it and runs even better on 4G, Wifi is Great too. Netflix has been down for a while So if you get any errors saying the server can not respond on the login screen, try again later.
The 1005 Error should go away when you try and load the video, if you cant get past the login screen try the other Netflix app that says updated for those who cant get pass the login screen
Your Responsible For What Happens NOT Us!
Video Proof:
http://www.youtube.com/watch?v=6qt3wnJ_SJc
PROBLEMS I ENCOUNTERED & HOW I FIXED THEM:
1) Calls would not ring or ring for a second and the Phone app would crash, but you could still call people just they couldnt call you
FIX: You have To Wipe all system data when in recovery mode, If that doesnt work go back a wipe data and re-flash the Rom again
2) Status Bar Crashes
FIX: Wait A Couple of Seconds and It Should Pop Up, DONT FREAK OUT! good your done it happens sometimes but maybe estimate once a week max twice a week
3) Bootloop on the Red Fish (Fugu bootloop)
FIX: Now I dont know if this was suppose to happen but it stayed on it for like 10 mins and IF your not seeing the bootloop just your battery bootloop unplug the usb, Wait 10 mins Then Pull out the battery and go back to Download Mode
4)Galaxy S 4G Stuck On Boot Screen
FIX: Well I accidently downloaded the Nexus S CWM (Stupid Me CWM Doesnt work on this Flash & Not Even my Phone) But if that does, Take out the battery and Put the battery back in and Get it in download Mode Again and Re-Flash it
I Hope This Helps You So Please Click The Thanks Button If I Did
Won't be CWM support as long as the bootloaders are encrypted, which they are on this build. Prevents the ability to modify the recovery to support CWM. Unless someone cracks away and delivers non-encrypted bootloaders.
Always good to reference like you did, do this stuff at your own risk and always have backups, I have Titanium but also CWM backups from KD1 just in case.
Thanks still kinda new to the Rooting and Flashing thing but great to know
Added A Some Problems i encountered, mostly because they were my fault but i hope this Post helps u
Thanks for this! I already had the deodexed KF2. I just installed the recommended netflix apk and it works perfectly!
Sent from my SGH-T959V using Tapatalk
you do realize i cracked the gb boot loaders modfied them upped them with the rom and all hell broke loose on the phone some got it to work sometimes sometimes it would just give u funky screen because the kernel is also encryted to right Just hacking the sbl and boot file isnt enough need to crack the kernel or sign our own.

Verizon Has offically renewing the Gingerbread OTA update

Take a look at Verizon'S UPDATE PAGEhttp://support.verizonwireless.com/pdf/system_update/thunderbolt.pdf
Standard data charges may apply. LTE is a trademark of ETSI. © 2011 Verizon Wireless. 1011-E0428
SOFTWARE UPDATE Get the most out of your
ThunderBolt by HTC.
Verizon Wireless is pleased to announce a new software update, Build Number: 2.11.605.5;
Baseband: 1.48.00.0906w_1, 0.01.78.0906w_2, for your ThunderBolt™ by HTC. This update
provides several improvements for your device, as well as upgrading to the Android 2.3
(Gingerbread) Operating System (OS).
For step-by-step instructions on how to perform this download,
please visit verizonwireless.com/thunderboltsupport
ThunderBolt by HTC
Enhancements:
+ Download Manager App:
New App to manage all of your downloads from web browsing,
email attachments and other apps.
+ App and Power Management Details:
Under Manage Applications, a new “Running” tab displays a list of active
applications and the storage and memory being used by each. Power
efficiency mode option has also been added under Settings > Power.
+ New Desktop User Interface:
New widgets, icons and screens with refreshed colors.
+ Full Dock Mode App:
This App includes three shortcuts at the bottom: Gallery, Music
and Calendar. In addition, this mode showcases Friend Stream
updates, upcoming meeting invites, notifications, weather clock
and has a slide show as the background wallpaper. Within this App,
a user can also enable the mobile hotspot in dock mode.
Additional Device Features:
+ Alarm notifications will no longer appear while in Emergency Mode.
+ Improved security features that reduce device vulnerability.
+ Improved data connectivity.
+ Improved audio quality while using Bluetooth®.
+ Bluetooth security patch has been included.
+ Decreased wait time when saving audio attachments.
+ Basic voicemail notification will now notify when a new
voicemail has been received.
+ V CAST Tones now comes preloaded.
+ New Google Books app.
+ Enhanced UI for data roaming.
+ SMS messages will no longer send to incorrect recipient on rare occasions.
+ Reduced Force Close errors while using TuneWiki.
+ Reduced Force Close errors when using the front camera.
+ Audio on BT Car Kit no longer reroutes to phone when receiving a SMS message.
Verizon Wireless and HT C encourage you to download this update.
Was already posted here
http://forum.xda-developers.com/showthread.php?t=1312193
Unrooted users here rename PG05IMG.zip flash in Hboot
http://www.androidpolice.com/2011/1...-fixes-several-issues-from-the-previous-leak/
Rooted version here, flash in recovery
http://rootzwiki.com/topic/7591-romrooted-2116055-full-stock/
http://www.multiupload.com/H06XI7W380
http://www.multiupload.com/WEBN5KCIHX
If I helped you in any way please use the thank you button
also a rooted, deodexed, debloated version here:
http://www.htcthunderbolt4g.com/htc...breadrockv1-0-v1-1-(newest-gingerbread-leak)/
"Improved security features that reduce device vulnerability."
LOL. Removing a really stupid security hole which they themselves created is now being called a "feature." Perfect corporate double-speak.
Will this work with the stock radio from the last gb ota? I am current stock rooted so would be selecting the rooted version of this as a rom.
recDNA said:
Will this work with the stock radio from the last gb ota? I am current stock rooted so would be selecting the rooted version of this as a rom.
Click to expand...
Click to collapse
A gingerbread radio is a gingerbread radio is it not? Yes it will and its the very same radios used it .3
If I helped you in any way please use the thank you button
I tried downloading one of those files directly to my phone so if an ota is pushed before I get home I could do an emergency install but no luck.
Is there a trick to using that multiupload site.to download to my phone? All I could download was the setup to use their system ilividv1.zip which I promptly deleted. Maybe I'm clicking on the wrong thing once transferred to that site?
Which link did u use? It's a big file takes 20 mins to download from multiupload
If I helped you in any way please use the thank you button
Try mega upload its the fastest IMO but only allows one download at a time, so never good to use when something first drops and everyone wants it.
I tried the second one on the list (megaupload) but it just tried to get me to download that stuff I already deleted.
I don't know if its because theyre busy or they're just determined to download their stuff to me before I can get the download I actually want. It started the countdown to downloading livid1.zip agains so I just closed it. I hate those download websites. They try to dupe you into downloading their stuff rather than what you went there for.
Thanks again anyway.
Any chance I could get away with installing the rooted version after only wiping cache and dalvik cache (not clear data) in order to retain my current setup?
recDNA said:
I tried the second one on the list (megaupload) but it just tried to get me to download that stuff I already deleted.
I don't know if its because theyre busy or they're just determined to download their stuff to me before I can get the download I actually want. It started the countdown to downloading livid1.zip agains so I just closed it. I hate those download websites. They try to dupe you into downloading their stuff rather than what you went there for.
Thanks again anyway.
Click to expand...
Click to collapse
Don't know what to tell you try all links till u get it. I never have any issues doing all downloading, renaming, flashing, storing, etc from my phone.
If I helped you in any way please use the thank you button
Do you know if I can flash the rooted official version without clearing my data?
If you are coming from .3 just flash in recovery with out clearing anything you will be fine. It would be just like installing the update.
If I helped you in any way please use the thank you button
Well I am rooted stock gb and just tried flashing the wiki stock rooted version and now I'm stuck on the white HTC screen.
Apparently you do need to clear data first.
Am I bricked? Any ideas?
You don't need to clear data, did you flash in recovery or hboot? Just making sure do u know the difference?
If I helped you in any way please use the thank you button
I flashed in recovery. I checked the md5 first too.
I pulled the battery and fortunately got into recovery. I'll clear everything this time and try again
I've always been thick but I hope I'm NOT a brick!
How long should it be on that first white HTC screen?
---------- Post added at 12:41 PM ---------- Previous post was at 12:30 PM ----------
I'ts stuck again....
I just hope it allows me to successfully flash a nandroid. :-(
Ok calm down so the md5 checked out perfect right? Explain to me your reboot to recovery, explain to me what clicked on in recovery to flash it....explain to me what version you are using
If I helped you in any way please use the thank you button
Sorry to get panicky on you...
I'm back on my original stock rooted rom now. Nandroid worked but those 30 seconds on the htc screen after restoring seemed like forever!
I used the wiki stock rooted rom. I'm sorry I don't remember if it was the top one or the mirror but I think the top one.
I downloaded it from megaupload.
I installed md5 checker from no and dis the checksum. It matched perfectly with the md5 at wiki. I understand the importance of a good download.
Next I booted into recovery from rm. It took me to revo recovery. I cleared cache and dalvik cache and left data alonebthe first time. I chose install zip and selected the htc stock rooted download. It installed uneventfully. The was a faint line drawn through simething ending in a 6 but I got a successful install message.
I chose go back then boot system. It booted as far as white screen with green htc on it. Let it stay of 15 minutes. Nothing.
Next I did battery pull, booted manually to hboot then recovery and repeated process except this time I also chose wipe data-factory reset. Same steps after that. Same result.
I finally pulled battery again and this time chose restore and flashed my latest nandroid successfully.
I've flashed roms before without difficulty.
You did it all correctly, sorry i can't help any further. You said Revo recovery? Is that an alternate recovery?
If I helped you in any way please use the thank you button
No - just the version if recovery you are in if you rooted with revolutionary. It's still created by cwm. The version of cwm is 5.0.2.1
I just flashed bamf forever last night with no problem but went back to stock s-off because vzw vvm wouldn't work.
Maybe I'll try the rooted debloated version on HTCThunderbolt4G.com. It will take me a while to calm down first. I had versions of my belongings being tossed out of windows by my wife if I had to pay stock price to replace my phone!
I do appreciate that you never left me hanging. That means a lot!

[Q] g2x Major Problems after Rooting / unRooting

Alrighty.. This phone has caused me so much time and trouble, I finally decided to start a thread. I really cannot find an answer for my problems by surfing...
In the beginning, all was great. Then I wanted to root my phone...
I went here and followed these instructions to root initially.
http://forum.xda-developers.com/showthread.php?t=1179748
(Stock Gingerbread OTA 2.3.3 Rooted)
I started to have problems:
-WIFI kept shutting off upon sleep. I depend on WIFI because I only have a 200MB plan..
Also, I have low signal in my apartment, so I use wifi calling very frequently. After about 10 minutes, wifi calling disables itself.
SO, I wanted to UNROOT. The link that said 'UNROOT' did not work..
Next, I used this link to unroot..
http://theunlockr.com/2011/05/23/how-to-unroot-the-t-mobile-g2x/
I returned to stock froyo OS. BUT i still wanted gingerbread!! I tried to use the LG update desktop tool, but it kept on saying that 'the phone was already up to date.'
SO, I ended up 'installing from zip' the backup that was made before I downgraded to froyo.. Unfortunately, this left me back at square one: A rooted gingerbread.. Exactly where I was before.
I went to this link next.
http://forum.xda-developers.com/showthread.php?t=1255214
I used the 'UNROOT ZIP', and it unrooted it!!
Seems perfect right??
BUT, ever since I did that, my GPS doesn't work. It is unable to pick up my location.
I tried to 'restore to stock' using BOTH the option while the phone is on, and using the 'clockwerk mod' (Where you hold power and the down button).
I just want things to go back to the way they were.
I'm hoping that I can just have a NORMAL 2.3.3, with GPS working, and everything back to the way it was before I started this whole 'root' journey..
Thank you so much ahead of time for taking the time to help me. Your 5 minutes could save me hours..
try restoring to stock, 2.2.2, then get the LG Updater tool to "Recovery Phone" which is at "Customer Support" and the last one, enter your phone model, and serial number, and it should recover it to stock with no problems for you. Good Luck.
Wifi is suppose to shut off on sleep mode unless you configure it not to.
Sent from my LG-P999 using xda premium
ed116 said:
try restoring to stock, 2.2.2, then get the LG Updater tool to "Recovery Phone" which is at "Customer Support" and the last one, enter your phone model, and serial number, and it should recover it to stock with no problems for you. Good Luck.
Click to expand...
Click to collapse
I will try this now.
Thanks. Hopefully it works.
It still says 'Update not required' after I use the recovery version.
It is saying that because just flashing 2.2 you are still on the July baseband which is telling the software you are on the latest. You should be able to find a stock nandriod in the forum somewhere to flash Gingerbread stock.
Go to Wireless and networks > Wifi > hit menu > Wifi sleep policy > never.
Sent from my MIUI G2x using XDA Premium App
GTWalling said:
It is saying that because just flashing 2.2 you are still on the July baseband which is telling the software you are on the latest. You should be able to find a stock nandriod in the forum somewhere to flash Gingerbread stock.
Click to expand...
Click to collapse
I was unable to find such a thread. I decided just to root it and go with the 'eagle' and deal with random problems..
However, the front facing camera keeps on stretching the picture..
Any thoughts?
FFC issues are common on non-stock roms trying to use LG camera instead of Android stock camera. Rooting your phone cannot cause wifi issues, etc. unless you made some errant changes to system files. Rooting does nothing but allow you or programs to get what is called in the Linux world SuperUser permissions. It allows you or the program to change or do anything it wants and removes the restrictions placed on the handset by the manufacturer and/or Google. All the rooting process does is add two files to your system and set the proper permission for su to be able to become root. The SuperUser.apk is the gateway to root. It is there to protect you from malicious programs getting root, as you have to approve all root access requests. It is actually very safe unless you do something stupid.
yoo992 said:
I was unable to find such a thread. I decided just to root it and go with the 'eagle' and deal with random problems..
However, the front facing camera keeps on stretching the picture..
Any thoughts?
Click to expand...
Click to collapse
Here is a link to both Froyo and Gingerbread.
http://forum.xda-developers.com/showthread.php?t=1037120

[Q] Issues with A701 upgrade to 4.1.1

Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
misteral1970 said:
Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
Click to expand...
Click to collapse
Mate, it doesn't sound good.
What I would do, at this point, is Fastboot the 4.1 image again.. And stay the heck out of CWM. If you Fastbooted the 4.0.4 image, and you still have it showing 4.1, then you have a serious issue. So boot to fastboot, and try it again. Clearly, whatever you did with CWM, didn't work,
Installing a rom from CWM, requires certain things to be done, either in the install script, or via CWM.
Most notably, Formatting User data, cache, dalvik, system, and data. If any of these do not get done, chances are, the rom install will not go good. The basic install script, generally only formats System and Flexrom. This is because Acer distributes a full rom with the understanding there is nothing on it. Most rom modders know this, which is why they give extra instructions via cwm.
The big thing, is when you boot your tablet, is if it says which bootloader you are on. So you have to look,. You want to be on the JB bootloader.
MD
Thanks for the response MD,
A tiny bit unsure how to proceed. I understand everything that you said (well, I think I understood correctly!)
I have in fact tried to fastboot the 4.1.1 image again, and again I am stuck on the language and location screen (did this last night before giving up for the day)
I have read and understood "Stay away from CWM" (and I know that it is in this case only - have used CWM on my Gnex without issue)
Please forgive me if what I am about to write is ridiculous - this is kind of where we'll see whether I understood correctly or not.
I'm thinking that if the various areas were not wiped, and that could be the reason for the snafu, then it would be worth going into CWM (which I have been warned to stay away from, and which I would stay away from except for this one thing) and formatting the user data, system, dalvik etc, then applying either the 4.1 or 4.0.4 to result in a working tablet.
Or possibly flashing the bootloader to make sure it is JB
Or going back to the weird 4.0.4/4.1.1 hybrid which works but doesn't allow Play Store and finding a way around that issue.
Mate, I'm not sure which way to go at this point!
Fastbooting 4.1 is a dead end at the moment (but could that be a bootloader issue....)
Fastbooting 4.0.4 gives me the hybrid (though I can check this again tonight)
BTW, the only CWM Rom work I have tried to do has been with the patched update (second downloadable file I think) - everything else has been done via ADB
So.....CWM to wipe/format caches? (I'm thinking 'NO! DID YOU NOT HEAR WHAT I SAID ABOUT STAYING AWAY FROM CWM????' but I'm asking anyway!)
Flash a new bootloader on? If so, any idea where I would find it (will obviously search here and Google)
Thanks anyway, and thanks in advance if you have any more advice. I really do appreciate the support!
Al
Well Al,
This is perplexing to say the least. Clearly fastbooting the 411 results in frozen at the wizard. My question, when you have the unlocked bootloader, does it say JBxxxxxxxx unlock mode when you boot the tab? Because it should. If it doesn't, then you're still on ICS bootloader. And will have to do the CWM thing to get JB installed. The 411 image flash, is to get a rooted version.
And this is the point. Personally, I do not trust the CWM's at this point. That's just me (already bricked 1 tab 3 months ago with a faulty CWM) I know the folks with ICS are using Pawitp's CWM, and haven't reported issues. But I don't know if they are doing wipes or not.
As with the 404 image, well, why playstore doesn't work is perplexing. You could try reinstalling the playstore via manual method (root required). Which is to delete the vending.apk, install a new vending.apk (making sure permissions are the same as the other files), then reboot. Go to settings, wipe the playstore cache's. Then try Playstore again. This was an old method we used with market issues in HC.
Personally, I feel the issue is with the wipes before running the patch. But I would hate you do the wipes and formats, then discover the emmc chip bricked. So it's 50/50.
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
Wish I could give you a definitive answer, but these processes are too new.
MD
Keep warranty
Moscow Desire said:
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
MD
Click to expand...
Click to collapse
Can you make a short tut how to replace the old unlocked Bootloader?
My Tab has some Problems with the Display so it need a service ...
witch cwm to use?
witch update.zip?
remove cwm and su if necessary
Android Version: 4.0.4
Baseband: 11.810.922.00
Kernal:2.6.39.4+
Image:ACER_AV043_A701_RV08RC02_EMEA_DE
Build: ACER_AV043_A701_1.017.00_EMEA_DE
Hi MD,
Thanks for such a speedy and useful response!
Warranty: nope! I'm in China, bought the tablet in Shanghai (now way down south in Shenzhen) and it was a dodgy deal to say the least. I suspect they were being lifted from the factory. No complaints from me about this, or about any difficulties caused by rooting/flashing/CWM. My choice of action all the way along and I am aware of the risks
Just flashed 404 again and it is fine so far, again very nice and smooth. Going to look at the Play Store and see how it behaves, see what I can do as far as vending.apk is concerned (although I'm lost when it comes to permissions. Obviously I know what permissions are in tech terms, but no idea where they would be set, how to change them, what to use as a reference) I figure this is the path of least resistance for right now.
Then I'm going to see if I can apply the standard A701 update to JB (which I won't be able to because of rooting/unlocking but I will fiddle around) and see if I have any joy.
Got my keen eyed gf to check the message on boot, you were right that with the 411 image applied it still had an ICS bootloader, so that's good to know if I want to try going back to the flashed JB image. However, I have no idea how to flash the JB bootloader/kernel, and the CWM process for the patched update fails each time (despite editing the first line of the necessary file in META-INF/Google/Android)
So, I will keep you up to date with progress. Fingers crossed!!!
Al
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
misteral1970 said:
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
Click to expand...
Click to collapse
Well, seems like Nova is the culprit. I assume you are talking about nova launcher? Or nova the game?
Hi MD
Yes, Nova launcher but no, it's not the culprit. At least I don't think so.
The play store stopped as soon as I ticked 'Install from unknown sources', before I installed Nova.
Very odd.
Quick questions:
1) Any advice/links/downloads for changing to JB bootloader if I apply the 4.1.1 again? Given that I cannot run the patched update/flash from CWM, I am guessing I would need to directly install/flash the bootloader from ADB...
2) Don't kill me for asking this. I know to stay away from CWM, I have seen you post it a good few times here, I heed the warning....BUT.....
Given that I have CWM installed and it's working ok (apart from failing to apply updates) - I have 6.0.1.4 - many of the guides to updating the 701 say it needs 6.0.1.1. Would the slightly more recent version of CWM make a difference in terms of success or failure of the update? Update is failing with a 'set_perm:some changes failed' very early in the update.
Seriously, I am being extremely wary of CWM, it's just that currently I have a slightly disabled tablet and it would be great to get this sorted.
Thanks, once again, for all your help,
Al
Update again, put 404 back on (after issue with play store and unknown sources)
Opened play store, downloaded Apex launcher - all good.
Ran Apex, all good....then suddenly Play Store stops, Apex stops, never to return.
With 404 img on, About Tablet still says 4.1.1
The saga continues!!
Aaaand that's the end of that!
Put 4.1.1 back on, pushed the boot.img from the official update.
Now no CWM, so it seems no recovery mode....if I try to get there by volume down and power on, it goes into update mode.
And of course neither the official update nor the 'patched' one will apply.
Can boot to the first start screen (language/location) but can't get any further.
Maybe I can find a service center here in Shenzhen who can sort it out.....as I said before, no harm no foul, I knew the risks!
Thanks one more time MD for all your support and advice )
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
misteral1970 said:
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
Click to expand...
Click to collapse
HA HA, you found the User Data wipe.... Yeah, a little known secret from the 500 forums.
MD
It's so strange....so now I'm back to having flashed 404 but the tablet thinks it's 411.
Play store was fine for about 40 minutes, I quickly got chrome, currents and BBC news.
I turned off the Acer ring and play store died...
But here I am, typing to you on the tablet and it's fine. And what a change in performance. It's most noticeable in currents..the increase in speed and smoothness when scrolling between pages makes it at least ten times better than before.
But the last flash was 404....weird....
I'll leave it like this for now. No market but at least it's not semi bricked!
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
misteral1970 said:
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
Click to expand...
Click to collapse
Well, good news then. I think it's an interesting set-up. Hybrid. Still not sure though, why it pulls 411 from the build.prop as it should have been changed when you flashed the 404image. But honestly, after reading the OP's steps, I believe he references going back to 404 via CWM, and not fastboot. This of course would mean installing a full 404 original rom. I'll have to look over my JB system dump and see where the other prop would be. Maybe something changed in JB.
So if you can live with it, it's probably better to leave it be till we come up with something more definitive.
MD
"So if you can live with it, it's probably better to leave it be till we come up with something more definitive"
Yeah, totally agree.
Mate, seriously, thanks for the support and advice on this. It makes a big difference. Even as I sat there last night with what seemed to be an unusable tablet, being able to chat to you about it meant that at least I didn't feel completely adrift!
Big big thanks

[Q] A very big and important question. Please help.

Well I posted this in general - but I didn't get a reply - and I'm really desperate.
When it comes to mobile platforms I'm more or less as green as they come - so forgive my ignorance regarding... Everything
I recently misplaced my beloved Nexus 4's flipcase. The day it went missing, I managed to stumble and drop my phone a distance onto tiles . It landed at such an awkward angle that the screen not only cracked but pretty much shattered - killing what I believe is known as the digitizer with it. It won't respond to touch.
Distraught I took up my dad's old Galaxy S3 - which was only cracked and a bit eaten (puppies). I went straight into using it and due to a demanding schedule I didn't have time to recover any of the data of the N4 - which I don't know how to do anyway. I quickly learn that I hate Touchwiz and the lack of personal details wakens me to how reliant I am on my phone.
So I set aside some time to get root - load a custom ROM (pa) - and transfer all my data from the N4 to the S3. The first difficulties appear when the S3 rejects towelroot. I install the towelroot apk from the official website and run it. Towelroot tells me it's currently an unsupported device. I google the model number (i9300) and apparently it works with Towelroot. Weird - I guess I'll do it manually.
So I install odin and download what I need and get the drivers for the S3 working and get root. It works without a hitch (I think until later ). Next I look into how to get a ROM on my phone. This happens: http://forum.xda-developers.com/para...4/post54744770 (that's my post btw so it's the exact scenario). I will say that while I was going through this issue I tried many things to try and get rid of the error - I played with CWM a lot - tried to update it - updating failed with unknown errors. - I tried to flash my recovery - it couldn't flash my recovery. Earlier I had tried to install the CWM recovery on it's own from the play store (again - total noob) I only got related versions of CWM from 2011-2012. All of these problems were pretty confusing - and eventually due to the generic error about not being able to flash my recovery I had no idea how to proceed so I did as advised in the thread above and installed Flashify.
Flashify told me I had root, but that it couldn't get access to SuperSU - and to delete SuperSUs memory of Flashify. I went to SuperSU and SuperSU told me that it needed to update my binaries (I don't even know what my binaries are?!). I tell it it can go ahead and it just says "installation failed" so I install SuperUser to try and replace SuperSU - and delete SuperSU. And Flashify is clinging to the remains of SuperSU. Between my odd model identification (TowelRoot - Status 7 error) and my devices seeming lack of compatibility with.. Anything really (I imagine the two are related). I decide to clean slate it with a factory reset. Which I do from the CWM BIOS (?? Volume up + Home + Power?).
So of course unlike any phone I've ever worked with - a factory reset now means wipe my SIM. (Okay that was laziness and stupidity I should have taken it out first but allow me to grieve). As I should have predicted but didn't it wiped all my backups (foolishly saved onto the internal SD card) and leaves me in the fetal position on the ground making howling noises shedding tears onto the floor.
I can't afford a new phone - or to repair my old one. I need the data off my N4 - who's touchscreen doesn't work - which is problem number 1. And I would really rather not live with touchwiz, or have to do half the process again when I otherwise find the time to get rid of it, so I want to do that now but there are so many errors and I have no idea what I'm dealing with - which is problem number 2.
So please, if anyone can help me out with a)Getting the data off my N4 (it is properly set up as a mass media device) and b)Fixing this seemingly banjaxed S3 and getting pa onto it.
Any help would be really gratefully received. It's been an awful weekend - I also lost a hard drive with all my work and a lot of personal data on it to natural causes.
Thanks - I eagerly await my knight in shining armor.
Have you tried turning it off and back on again?
derekokelly said:
Have you tried turning it off and back on again?
Click to expand...
Click to collapse
I laughed so hard before I broke down crying..

Categories

Resources