[Q] Where's the error of my ways? - Xperia Play Q&A, Help & Troubleshooting

[THIS QUESTION/ISSUE HAS BEEN RESOLVED]
I spent the best part of yesterday upgrading my phone software, initially completely successfully. I rooted, unlocked boot, installed Dooms kernel all without any problems. Then came the Rom upload...
I wish I had stopped while I was ahead, I felt confident that If I took proper care and attention all would be well. However, I completed the installation only to be greeted by that infuriating exclamation mark (perhaps "completed" isn't the right word.)
My device is a UK R800i, which did have the latest firmware on. It now has nothing on, so using Flashtool doesn't seem to be an option as I can enter the device to enable USB Debugging, and searches for a way to enable this externally have been in vein.
I've tried updating the ROM using the following, with very slight variations sometimes - largely exactly how listed.
​Format
-> Enter Command Prompt, launched ClockWorkMod (CWM)
-> Formatted all, including the SD card although the SD wasn't required.
-> Rebooted [sometime just continued with Kernel install without reboot]
​Kernel
-> Reboot, and go back to CMD prompt.
-> Add Doomlords, Kernel. (various version, most recent usually but one ROM stated an older version was required so I tried that)
-> Wait to complete, then reboot device.
​Rom
-> CMD prompt. CWM.
-> "Install ZIP from SDCard"
-> Wait for completion, then reboot or shutdown through CWM menu.
Then once complete, with the two or three ROMs' I've tried, I'm stuck in a power on power off loop. With the exclamation and phone logo being breathly shown. Before I threw the handset out of the window at the closest person I dislike, I looked around to see if it's truly bricked - most seem to suggest it isn't and the term bricked is over used. Apparently the fact that I can enter CWM means I should continue to try.
The singularity in my head, I think it's called a brain cell says "no you don't want that working" and does its best to screw me over. I'm sure it's just a little moronic mistake somewhere along the way. Anybody game for making me feel more of an idiot than I already do?
Thanks in advance if you do take time to help. Oh and I apologise too, I realise the answer must be out there, just after nearly a day of searching I've decided to just bite the bullet and ask for help from somebody with one iota of intelligence remaining.
Now I'm off to chain smoke and pray...

You can use flastool, usb debugging is not needed. Infact i usually format all the partitions on my device before using flashtool.
Sent from my R800i using Tapatalk

OH okay thanks, I'll give that a try again but during my previous attempts at using it I received a message stating it must be enabled. Do you know what version you are using please?
0.5.0.0 Beta Downloading now, not sure if the version I used was outdated.

AndroHero said:
You can use flastool, usb debugging is not needed. Infact i usually format all the partitions on my device before using flashtool.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Thank you so much!! It worked this time around, I'm sure I would have got there eventually but you have just saved me a whole shipload of messing about. Thank you for reading the essay and responding.
My hero!
*blood pressure decreases*

KoqHed said:
Thank you so much!! It worked this time around, I'm sure I would have got there eventually but you have just saved me a whole shipload of messing about. Thank you for reading the essay and responding.
My hero!
*blood pressure decreases*
Click to expand...
Click to collapse
I'm glad you got it sorted for the record the message that says."turn on unknown sources and usb debugging" is a generic one, flastool ends with the same message no matter if the flash finished sucessfully or not
Sent from my R800i using Tapatalk

Related

Help, Please

So, I have tried all methods posted here. I have not gotten a new sdcard, so that could be it, but if you sift through all these threads, many people have gotten root with the card that came from verizon. Also, would it help to wipe out my phone? Not exactly sure how to do it, but would it help? Also, I hear my phone connect with the usb sounds, but it seems like sometimes I get a quick 3 tones and it doesn't connect. Not sure what that means either.
If anyone can please help, I would appreciate it!
if your not sure if it connected right, open the device manager and see if it is appearing on there.
As far as i know wiping your phone probly won't really help much either.
rstandi said:
So, I have tried all methods posted here. I have not gotten a new sdcard, so that could be it, but if you sift through all these threads, many people have gotten root with the card that came from verizon. Also, would it help to wipe out my phone? Not exactly sure how to do it, but would it help? Also, I hear my phone connect with the usb sounds, but it seems like sometimes I get a quick 3 tones and it doesn't connect. Not sure what that means either.
If anyone can please help, I would appreciate it!
Click to expand...
Click to collapse
There are about 10 threads on adb shell/rooting difficulties already. Why didn't you just bump an older one?
When you connect the usb to the phone what mounting setting did you select? It needs to be on charge only.
So, I have tried all methods posted here.
Click to expand...
Click to collapse
I have rooted two phones using various methods. The Easiest method? Who knows, but this is what I did, I in NO way take credit for this method. This is a culmination of various methods I found on various forums. Thank you to everyone here and on androidforums. Give it a shot.
1. Uninstall HTC sync and PDAnet (If installed)
2. Install drivers as specified for re-flash recovery from revoked team (HTML file has instruction in recovery zip - unrevoked.com/recovery/android-usb-driver.zip
3. Restart PC
4. Install PDANet - junefabrics.com/android/
5. Make sure to complete all steps for PDANet
6. Make default connection on phone, "Disk Drive" AND Turn on "USB Debugging"
7. Shut down the phone
8. Unclick the card
9. Volume down + Power into bootloader
10. Run adb shell in cmd prompt as loop(loop.bat)
11. Start recovery and wait .5 - 1 second after you hear the disconnect sound to click in your card.
12. You should see error device not found change to the other message IF LUCKY.
13. IF NOT,
- Let loop.bat continue to run
- Pull battery, unclick SD card
- Vol down + Power
- Recovery
- Listen for 2 tones (Count aloud..it helps)..
Quick - Insert card right after/during second (Change timing up slightly between tries)
Keep trying, my second root didn't take as long as my first but was easier. I think the unrevoked bootloader drivers with the PDANet usb drivers really make this easier. The other great thing is after you get root, you are set up to do the flash immediately using this method. Its just one more method that worked for me, hope this method helps you succeed. Good luck.
can anyone definitively explain to me which type of usb connection (e.g. "charge only", "disk drive") is necessary to get into shell and why? I have looked at what the various threads have to say about this. In fact that's the problem--I have found contradicting opinions posted on this matter. In my admittedly inexperienced mind, it seems like I should be fine either way, as long as adb recognizes my device.
davisbs999 said:
can anyone definitively explain to me which type of usb connection (e.g. "charge only", "disk drive") is necessary to get into shell and why? I have looked at what the various threads have to say about this. In fact that's the problem--I have found contradicting opinions posted on this matter. In my admittedly inexperienced mind, it seems like I should be fine either way, as long as adb recognizes my device.
Click to expand...
Click to collapse
I used disk drive the first time, and can not recall what I used on my second device. I see that it is contradicting throughout. I really do not think it even makes a difference because you are doing a battery pull and it never reaches that step on the phone. The important thing in my opinion are the drivers and timing.
Studmf said:
I used disk drive the first time, and can not recall what I used on my second device. I see that it is contradicting throughout. I really do not think it even makes a difference because you are doing a battery pull and it never reaches that step on the phone. The important thing in my opinion are the drivers and timing.
Click to expand...
Click to collapse
I rooted my cousin's Droid Incredible and I had Disk Drive enabled. I just want to say THANK YOU Studmf!!!!! I was stuck because I had HTC Sync installed and was stuck forever trying to root the Incredible. The instructions that I WAS following left that detail out.

Updated version to enable Unknown Sources

This is the latest release of my fix (June 14, 2011). This version addresses the Market ID and Moto Blur issue.
This version does not require the use of scripts on the phone. It uses ADB and sqlite3 (both are included in the zip file).
I created a new thread here because the older version was so full of bugs and comments about said bugs I figured it was time to start fresh, seeing how I am using a different method (the method I should have used to begin with) for this hack. Also, this should have been in development to begin with.
I have not had a chance to test the latest version, aside from verifying the awk command works as exptected. The rest is a strong educated guess, mixed with a re-tooling of it to just use Android Debug Bridge to do what I was having scripts do in the past. Should be much more reliable.
IF YOU DECIDE TO USE THESE INSTRUCTIONS: PLEASE, read through this page entirely from top to bottom at least once prior to doing anything. This way, if you are unsure on anything, you can ask the questions you need answers to. I am not liable for anybody messing up their phone because they didn't think to read the F'n manual prior to following these steps.
If you don't read this through completely before starting, and you brick your system, Don't come crying to me. I warned you.
This version makes it close to impossible to brick the system, but I left that bit in to cover my arse.
If you do not have the phone rooted, download the second zip file, and install the drivers found below:
Motorola Driver(install before you run the batch file)
You will need to enable USB Debugging:
On your phone,go to Settings->Applications->Development->Check "USB Debugging"
Latest version installs busybox for you, but if it doesn't, the script will pause for you to check, and tell you how to quit out of my script before proceding. If you have issues with that, let me know. I haven't tested this version, but by all accounts, it should be more reliable than my previous iterations, with the plus side of not having to purchase an app.
I have not tested it, so you may still need to tell it to install, but it should install the apk.
1. Download the attachment located in this post.
Unzip to a folder on your desktop.
PLUG IN YOUR PHONE NOW!!!
Double click on the batch file ("enable_unknown_sources.bat"). You may have to run as administrator, but I don't think so. Built on Windows XP (I'm a linux guy who wrote this at work in a couple minutes)
When it prompts for you to OK the super user for "unknown", look at your phone. It should have a prompt. If not, it may be ok. We will see....
once your phone has rebooted, you phone will have "unknown sources" enabled already. Don't worry about rebooting. The batch file did that for you.
Quite a bit less work than before. Good news: it's done! never to worry about it again...unless you upgrade....
DISCLAIMER:
DO NOT FOLLOW ANY OF MY STEPS IF YOU ARE UNSURE OF WHAT YOU ARE DOING! I have done my best to ensure that the instructions are accurate, but I made mistakes in the first revision, so who's to say that I didn't miss something this go 'round as well? If you decide to follow this walk-through, your actions are an agreement to not hold me liable if your phone becomes a pretty brick. I am not responsible for what you do with this information. If you have no idea how to do any portion of these instructions, you can either walk away (best idea), or ask for help here.
I am also not the 2nd shooter on the grassy knoll, nor am I the cause of all your woes throughout life. I always wanted to say that in a disclaimer.
Thanks to Vahnyyz for reminding me that I forgot to have you enable USB Debugging.
IF YOU HAVE PROBLEMS:
Have you installed the Motorola Drivers?
Do you have Debugging enabled?
If the answer to the 2 questions above are "yes, damnit! Give me a good answer, and stop wasting my time with these stupid questions", then you will need to tell me at what point the scripts fail. I will look into the problem as fast as I can.
so I tried the program you put on and everything because I haven't been able to root my phone as of yet, but the file I downloaded that included rooting did not work, everytime I ran the application it stated that "Device Not Found" and my phone is connected through USB at the moment.
Forgot a part
Thanks for letting me know about your issue. You need to do the following:
Ensure you have installed the drivers on you computer
Ensure USB Debugging is turned on
To enable USB Debugging, (on your phone...duh) go to Settings->Applications->Development->Check "USB Debugging"
as soon as I run the. bat file, command screen tells me to make sure that busybox is installed, which it is, to unplug phone, go to, busybox and install. Wife's phone is already rooted, once I hit next, "unknown" will pop up on the screen for a second and then....nothing.
Need to fix that to state "....after you ensure busybox is installed, plug phone back in"
Just plug the phone back up prior to proceding
Sent from my GT-I9000 using XDA App
How is the no blur version coming along....anxiously waiting for that!
JBallin4life27 said:
How is the no blur version coming along....anxiously waiting for that!
Click to expand...
Click to collapse
I am running into a problem I believe is caused by an older version of clockworkmod. I am trying to see if I can get a newer version running.
The issue:
It appears that the update file I generate is incompatable with the updater built into the version of ClockWorkMod I am running. Anybody have a newer build of the CWM I can use for testing?
jonsjava said:
I am running into a problem I believe is caused by an older version of clockworkmod. I am trying to see if I can get a newer version running.
The issue:
It appears that the update file I generate is incompatable with the updater built into the version of ClockWorkMod I am running. Anybody have a newer build of the CWM I can use for testing?
Click to expand...
Click to collapse
I had CM6 running on my motorola backflip and still have all the files saved on my computer...would it be in there somewhere and would that be useful to you?
JBallin4life27 said:
I had CM6 running on my motorola backflip and still have all the files saved on my computer...would it be in there somewhere and would that be useful to you?
Click to expand...
Click to collapse
I'm needing the second stage recovery file to make ClockWorkMod something newer than 2.x.x Needing to have it somewhere in the neighborhood of 3.x
jonsjava said:
I'm needing the second stage recovery file to make ClockWorkMod something newer than 2.x.x Needing to have it somewhere in the neighborhood of 3.x
Click to expand...
Click to collapse
Yea lol...no idea what that all means...sorry i'm not any help

Htc desire hd - sd card unavailable

Hi guys and girls.
New to XDA but not to Android.
I need some help big time as I'm totally stuck and I'm about to send my phone to "will it blend".
Long story short my memory card will not read when inside the phone all I get under phone storage is "unavailable" with mount being greyed out.
HTC DESIRE HD 2.3.3 (Not Rooted)
Things I have tried:
Factory reset soft/hard both through phone and through power + vol down.
Tried two different mem cards both coming up in storage as "unavailable" the general fix seems to be formatting in fat32 on desktop pc I have done that for both cards (which are both readable on PC) and have even tried formatting through command prompt still no luck.
read alot in ADB/fastboot as it is something I'm abit unfamiliar with saw that users where able to restore sd card function by installing adb then running command prompt: "fastboot oem enableqxdm 0" I get a message saying it was successful I reboot guess what...same problem. One thing I have noticed is if I type "adb shell" I get "Daemon started on port 5079". (I have enable debugging) followed by device not found. have tried two diff usb cables both work with my S2 on either media faceplate or backplate usb ports still no luck. Trust me on this one guys I have searched far and wide and I'm just about read to quit on this. I'm at a dead end any advice would be awesome.
I've tried to resolve the adb method by installing various drivers (running windows 7pro 64bit) the issue I seem to get is that windows doesnt like the drivers Im trying to assign so im forced into have to update them manually through "let me choose a driver from location" blah blah blah...
There is a system update available which may possibly fix my issue however suprise suprise I can't download the update without having an sd card. I have even tried downloading a HTC sdmount widget whether Im downloading the wrong one I dont know? I have got HTC sync installed as others claimed this helped windows detect the correct drivers but then technically speaking its not an ADB interface?? just like to point out that both of the sd cards work flawlessly in my s2. anyone who can help me will get paypal'd a beer!
Thanks
Seb.
OK, I had same problem with my Desire S. I'm running Win7 64bit as well. I un-installed HTC sync, including the drivers. Control Panel>Programs & Features. I then download the latest HTC sync. Went back to Programs & Features and un-installed HTC sync but, left the drivers. Rebooted PC and Win7 picked up Desire S.
Hope this helps
How old is your phone? Depending in which country you are in you may still be under warranty.
Try cleaning the contacts?
Not too sure if you can mount the sd card on phones that are not rooted, or if you have the hboot option/recovery. Fastboot turned off, phone off, then press and hold the down volume button and while pressing it down, press the power button.
If you are not sure what you are looking at do not play around with those options, and it may not work. Not sure if you get those options if you are not rooted.
Do not root your phone, it is improbable it will help, and chances are, it may cause more problems than help.
First option, find out about the warranty.
Edit: just noticed you can boot into hboot. Not too sure if you have the option for recovery and even less if you get the option to mount sd card through there.
2nd edit: I'm not responsible for bad advice. I still haven't had my second cup of coffee
3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.
eloquence intshe
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks
3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.[/QUOTE]
How do I clean the contacts on the sd reader? it doesnt look very accessible unless I remove part of the housing? also what command prompt do you recommend I try first? like I said I tried "adb shell" and got no device found I'll update in a second as soon as I have tried this I have just uninstalled htc sync now all I need to do is assign driver to "android 1.0" in device manager then I'll take it for a spin.
Thanks dude
Ironman MarkV said:
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks
Click to expand...
Click to collapse
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.
Teichopsia said:
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.
Click to expand...
Click to collapse
Lol, already saw your username and was like 'Yup, problem solved ;-)'
Flashable zip is being a pain in the rear, should have it soon (reading a crap-ton of tutorials to help me)
Sent from my Desire HD using Swype beta for Android!

[Q] Tried to update, now unuseable

So I have upgraded my i927 captivate glide using the ROM from , but I only Androidupdate com called I927UCLH2_I927ATTLH2_I927UCLH2_Home tar md5 but I get a black screen with a slide down menu saying the date ‘Ongoing’ and an option to change the way that the device connects to another computer.
The update stated pass, it booted and proceeded to tell me that it was updating apps or something like that, then a black screen with the pull down menu from the top of the screen near the usb symbol came up but nothing else. I got a message a few hours later stating that the update application or something like that was not responding and an option to wait or quit. I chose wait, but nothing came of it eventually.
I then proceeded to try reflashing the process with no success even after factory reset and rebooting.
I then tried the pre-release ICS update as per XDA developers and other websites. Same thing
I tried a few other ODIN programs and ROMs but no success. Same issues including the hang up on the Samsung logo. I tried rooting it once and for some reason it started up into what looked like the same pull down menu, but it was requesting that I needed an to input a lock code for the network. I assume that is because my sim card was in it by now, but maybe not. I got so frustrated that I tried the bootloader and update bootloader options using the official ICS update ROM for some stupid reason but nothing. The thing is that at least it booted into the pull down menu that i got with a black screen again.
I then flashed with an updated ICS, CWM6 but cannot do the:
Third: Reboot into CWM6 (Volume- and power) install from sdcard (superuser)
Link to superuser: Superuser-3.2-RC2-arm-signed zip
Forth: Repeat third step above but install keyboard fix.
Link to keyboard fix: CWM_keyboard_backlight_fix zip
since I do not have an SD card that is working. I did get the SD Card in the device but I have always had problems with the format of it and I cannot put the zips onto the card due to the computer Win7 not recognizing it. I tried reformatting the device is HPUSB format program and windows. I inserted the card into the device to hopefully have it recognized on windows, and i gave me an option to format the SD card. So I proceeded and success. I was able to put the Zips onto the card. However, I returned to the CWM6 screen by pressing the VOL- and power keys but the files were no where to be found on the SD Card.
I moved on after a few other tries at it, so I tried to go backwards to the Gingerbread ROM. No success, same hanging issue at the Samsung logo.
I then tried to reflash with the devices original ROM as provided by DroidAngel on androidupdate com. Both without success.
I wanted to try the process involved on the 'stuck on boot screen' thread, but I cannot access the zip files on the sdcard in order to be able to do that.
I also bought my phone unlocked from the US (ATT version) and had it sent to me in Canada unlocked so I cannot just return it to the seller to get a new one, so my new phone is pretty useless.
I have spent two days reading through and trying different fixes and updated ROMs on multiple sites but I just cannot figure out what the heck to do now. I know that this site is not to spoon feed people and I am a noob to all of this but I am out of ideas and cannot find anything else to help out.
Where do I go from here. Is there a possibility of reformatting EVERYTHING on the device including all partitions etc etc.? I mean the hardware is fine, it is just a software issue. I do this to my laptop whenever I get into a bind.
Have you tried booting into CWM and restoring factory?
sent from my captivate glide running ICS (NardROM 0.3 Rooted)
Just a note, the SD card you're seeing in CWMR isn't actually your physical SD card, its the internal phone memory. I don't think we have a version of CWMR that reads the real external SD unless modified. So anything you put on it won't show up there. The folder structure will look like ... /sdcard/external_sd/ where /sdcard/ is where you want to put your files for CMWR to see, /external_sd/ is your physical card you can take in/out.
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
EaglesIII said:
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
Click to expand...
Click to collapse
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Evil Alex said:
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Click to expand...
Click to collapse
Okay, so right now I can still get into the download mode to flash, the CWM6 to factory reset and reboot which I have tried already as stated, and I have not been asked for the network key again since the one time quite a long time ago. The network key is only asked when I load one of the other custom ROMS though, but I have not tried any of those in a while.
I am stuck at the black screen with white Samsung logo.
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Got it running on Bio360 but 'Not Registered on Network' now
Evil Alex said:
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Click to expand...
Click to collapse
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
EaglesIII said:
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
Click to expand...
Click to collapse
You're very welcome! Glad to hear the phone is usable again. In order to get data back you will have to set your APN manually. Stock ROMs come with the APN settings for all providers it is expected to be sold with. But custom ROMs usually come without those settings. You can find the APN settings for your provider online, just do a search. There is even an app for it, but the name eludes me at the moment. You'll need wifi to get the app, though! Once the settings are in place (You put them in under wireless & Networks), you'll have data again.
As for the limited functionality, I had the same thing, at first. The upgrade was broken for me, I guess some settings/apps were causing problems. So, after flashing the upgrade, I did a factory reset in CWM. I also wiped the cache, and the Dalvik cache, for good measure(Under advanced in CWM). It rebooted, said it was upgrading and installing, and I let it sit for a few minutes. Then I was greeted by an initial setup screen, and the phone has been on a working ICS ever since! I did lose all my settings and such, but I had a back-up of those with Titanium Backup, and got those back that way.
Hope this will help as well.

Z1C won't start - advice please

I've got myself into quite a muddle with my rooted Z1 Compact. I was prompted to update the firmware to 14.4.A.0.157, which I did over the air. Since the update, the device had been freezing, restarting and generally being unwell. What I didn't realise, based on a piece I read somewhere, was that this was likely or probable if the phone had been rooted. My memory is a bit sketchy on all the steps I took - but briefly - it suggested checking the status of the phone, from which I followed instructions using flashtool to flash a preceding firmware (xxxx.108), which it appeared to do successfully but now the phone does not boot at all. I'm now lost what to do next and I couldn't say if I've soft or hard bricked the phone. Another article (at android.gs / unbrick-sony-xperia-z1 ) says that if it's hard bricked then I need to flash the full firmware (not just kernel only). I've downloaded and installed Emma from Sony's site. I can get the software to recognise the phone but it says it is locked and I am in the process of downloading the Android SDK to [see if I can] continue this process.
I should have stopped and asked for advice before I did any of this. Now finally I am pausing to seek advice. Can anyone point me in the right direction?
The phone will charge when plugged in, at least it is showing a green LED to imply fully charged.
Brief update: I couldn't enable USB debugging on device, as device doesn't start up. I enter fastboot mode when connecting the device (Windows) and I run "fastboot devices" in the platform-tools folder without an error however when I enter the command with my unlock key, I just get "waiting for device" (several minutes). I am assuming that this might be because I couldn't enable USB debugging on the device? Any suggestions on where to go from here?
I might as well log the antics of my adventurous mind. Given that I hit a dead end, I continued on the original path and used FlashTool to flash 14.2.A.1.114_Customized firmware (why this - because it was the only full firmware that I found). Anyway, thankfully, I now have a working device running that firmware with Android 4.3. I'll try and proceed to get back up to date.
devo1d said:
(why this - because it was the only full firmware that I found).
Click to expand...
Click to collapse
Not sure how when this thread is stickied at the top of the General Section. Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More..
Oh my goodness......... It is pantomime season after all
Magic. I confess to being another dizzy head when things don't go right and reading from a multiple sources and getting a bit overwhelmed & lost. Anyway, found the way out and thank you for the pointer to the sticky right-in-front-of-the-eyes info. Bookmarked.

Categories

Resources