Hi, just after a bit of help.
device - D2203 - bootloader locked (not unlockable) 18.5.C.0.19 - completely stock
needed to root to use phone - storage really bad - used jellybean rom trick method to root, then blindly started deleting thing i thought i could (using titanium backup)
think i went a bit far as every time phone turned on asks for country location (or language - bit non specific, just country list) and have to 'agree' to important information screen. phone still works tho
have tried using flashtool to rebuild stock ftf and flash, also sony pc companion to repair, but still makes no difference.
i could live with this but need to root and now worried i can't do this as rom trick needs to boot phone with no screen
if anyone can advise would really appreciate it, bit lost!
have screenshots of these 2 pages but not sure how to attach.
thanks
SOLVED - bug in sony os, worked fine once factory reset done with sim card in place - thanks to VINAY for advice
Related
New to this site but have done days of searches for my problem. Since JB update my bluetooth is not working and I have also found out Airplane mode is messed up also. Both will have slight responses for a short time after booting , then nothing. I down graded back to ICS and I get some functionality and have actually paired a device but does not work correctly. Asus wants the tablet sent back , but it sure seems to me as it is Op system causing all of this. It was working fine before. I am new to messing around with android , So one question is since I down graded to ICS 4.0 does the actual device firmware downgrade completely also ? I see that Bluetooth Version lowered and other versions lowered , but could something else not get back to that version , some type of Bios type settings? ( I was told no Bios in android ,but is there something like it ? )
So does anyone have the same problems , any answers or thoughts ?
Is there a way to erase everything completely and go back to the exact files software , kernals etc. as when in the box it came in.
Sure seems to act like a software driver type problems.
What are the "Source Code" that are offered on the Asus Site ? Can those used to be used to Factory fresh the device ?
I do not want to void any warrenty , but before I send back I want to see if it is Hardware or software.
Thanks
wadea2 said:
What are the "Source Code" that are offered on the Asus Site ? Can those used to be used to Factory fresh the device ?
Click to expand...
Click to collapse
Source code is only useful for software developers. To restore your device as close to factory state as possible, install the full firmware package of your desired version, as you already did when downgrading, and wipe data.
Things not restored by this method:
- device-dependent settings (e.g. serial number, sensor calibration data)
- DRM key
- Partition table
These usually cannot be changed by the user and therefore do not need to be restored anyway.
My main concern is the kernal, I feel that this may be the cause of my problems , if indeed the hardware does not have a problem. So when I restored to ICS , Did the kernal complete revert to factory also ? I understand now that the Kernal is the ( Bios) of Android , takes comands from software and tells hardware what to do . ( Right ? )
I am finding that the "Factory Reset " from from "Setting" does not truely reset all settings ( I set a Sound Setting before Reset , and the same setting was "on" after the reset ), therefore a "Firmware" reset back to ICS may leave the reason my bluetooth and airplane is not working.
So is there a way to use the "blob" with-out rooting or causing a warrenty issue ?
The kernel is part of the full firmware, so it is flashed when you install the firmware. It is the core of the operating system and also contains all the hardware drivers. The PC BIOS would be more comparable to the tablet's bootloader, as it only initializes the hardware and loads the kernel.
Your problem description is completely worthless. If you expect help, state exactly what you did, which error messages appear, and describe in detail what does not work and what you expected.
I thought i expalined better. I will try again. I used my bluetooth on my tablet connected to my phone and sent photos to tablet from phone. All was fine, Did not try and use bluetooth again untill a week later ( 3 days after OTA JB update ) now the bluetooth does not work and I see that Airplane mode is not working correctly either.
Since this happened right after the JB Update , It made since to me it is an update problem. I was wanting to go back to the exact state before update to see if errors were gone. I have re installed ICS and had better response from bluetooth , was able to pair a device but after pairing would not work ( headphones , sound stayed on tablet ) .
With these findings it would lead me to beleave two things , the "Firware install of ICS " left traces of the newer Kernal , that caused the problem or the Tablet hardware is the problem.
does that make more since to you ? Sorry about the first Question. I have let the tablet do the OTA back to JB and still in the same situation. I have an RMA set up , but I just like to know for sure the cause before sending back.
Thanks for you time.
wadea2 said:
now the bluetooth does not work and I see that Airplane mode is not working correctly either.
Click to expand...
Click to collapse
I'm giving up.
Ok, Well thanks for trying ? I do not have any other info. to tell you then my last reply , that is all that I can explain , What is wrong what I did and what I was trying to figure out by process of elimination.
Hey, New to this here and in need of help with my Xperia S Lt26.
I bought it off eBay earlier this year not realising it was rooted, once I got the phone I performed a factory reset and removed apps like moxier and superSU (which I now think was a mistake).
Anyway with the new update out my android system says computer required and when I connect to Sony update on computer it says I can't do it, I have also tried to update via WiFi with no luck as my girlfriend was able to do her update this way.
How can I get my phone back to its stock factory settings and avoid this happening again?
I want my phone back to how it should be, like it was never rooted, then I can update it the correct way.
I have never rooted or flashed a phone before, so step by step would be great, thanks
just want to add I tried to reinstall superSU and do the remove root on my phone but once I opened the app it came up that no binary was found
somebody surely must have an answer
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..
Hi,
This problem happens after replace my screen and perform an update from kitkat 4.4.4 to Lolllipop 5.x. The first time I tried it the screen gets more crazy than the current video. After that I check that the same problem happens if i want to perform a factory reset or a recovery from bootloader or from the android settings menu. I don´t know what happens :s the phone works great if I use it with the current kitkat 4.4.4.
Additional information:
- Moto G 1st gen.
- Bootloader unlocked,
- original vendedor ROM (not customized, never did it)
- root (I have unrooted it today).
- My PC recognizes it
I don´t include the option when I make an update because I need to download the 370MB again and the result is the same. Also, when I make an update the phone restarts about 4 o 5 times. Finally it says that the uploaded finished correctly and then the detail description says that there was a problem.
youtube.com/watch?v=cgwKdJ4-F34
Does anyone have any idea about how to solve it?
Thanks.
Please, can anyone help me?
Umm. It looks like an hardware problem...
edit. no, the recovery screen and warning logo has no visual problems, so it is software.
Try to reflash the stock ROM.
Hello. This looks like the place I can get the best help.
Got a Xiaomi Mi5 last week - cheap and very cheerful. Having read online about possible fake roms and bloatware I thought the safest option would be to load the official stable rom to be safe.
Attempt 1
Following the MIUI guidance I downloaded the ROM, copied it to my phone in Windows explorer and then used the MIUI updater tool within the phone to load the new ROM.
http://en.miui.com/a-232.html
Everything went swimmingly for a couple of hours, but then the phone began crashing.
Attempt 2
By this stage I realised the above method was no longer available to me. So I got unlocking privalidges, unlocked my phone. Then, using MiFlash I flashed the latest ROM to the phone. Now the crashing problems happen within about a minute. It actually froze the screen first time round so I did it again.
Added fun issue - left my phone on overnight to charge. And it had stopped charging at 58%.
Attempt 3
Downloaded the EU MIUI Rom. Accessed TWRP in my phone and tried to use it to wipe and install. Not sure the wipes were fully effective - got a lot of red writing. And when I went to install the new ROM the internal storage was 0MB.
Had a look at guidance, and I forget what I did, but was finally able to see the zip file on my phone through TWRP. I got the "7" error. Have read how to fix this but seems too risky considering whats gone before.
Desired solution
I would just like any ROM on my phone which works. Don't really care which, I have followed each guide religiously. It may well just be a faulty phone but I don't want to send it back to China without ruling out the problem being me screwing with the software. Especially as I assume i've technically voided warranty... (I can reload Global Developer and relock it though so have hidden it pretty well. Only difference I can tell is that I now get a menu in recovery mode when before I got instruction to go to PCsuite).
Also - I seem to remember there originally being a downloaded_rom file in the internal memory which is no longer there. If im sending it back do I need to recreate one to hide my activity?
Appreciate any advice.
Moley1985 said:
Hello. This looks like the place I can get the best help.
Got a Xiaomi Mi5 last week - cheap and very cheerful. Having read online about possible fake roms and bloatware I thought the safest option would be to load the official stable rom to be safe.
Attempt 1
Following the MIUI guidance I downloaded the ROM, copied it to my phone in Windows explorer and then used the MIUI updater tool within the phone to load the new ROM.
http://en.miui.com/a-232.html
Everything went swimmingly for a couple of hours, but then the phone began crashing.
Attempt 2
By this stage I realised the above method was no longer available to me. So I got unlocking privalidges, unlocked my phone. Then, using MiFlash I flashed the latest ROM to the phone. Now the crashing problems happen within about a minute. It actually froze the screen first time round so I did it again.
Added fun issue - left my phone on overnight to charge. And it had stopped charging at 58%.
Attempt 3
Downloaded the EU MIUI Rom. Accessed TWRP in my phone and tried to use it to wipe and install. Not sure the wipes were fully effective - got a lot of red writing. And when I went to install the new ROM the internal storage was 0MB.
Had a look at guidance, and I forget what I did, but was finally able to see the zip file on my phone through TWRP. I got the "7" error. Have read how to fix this but seems too risky considering whats gone before.
Desired solution
I would just like any ROM on my phone which works. Don't really care which, I have followed each guide religiously. It may well just be a faulty phone but I don't want to send it back to China without ruling out the problem being me screwing with the software. Especially as I assume i've technically voided warranty... (I can reload Global Developer and relock it though so have hidden it pretty well. Only difference I can tell is that I now get a menu in recovery mode when before I got instruction to go to PCsuite).
Also - I seem to remember there originally being a downloaded_rom file in the internal memory which is no longer there. If im sending it back do I need to recreate one to hide my activity?
Appreciate any advice.
Click to expand...
Click to collapse
Greetings and welcome to assist. Xiaomi phones are encrypted by default so you need to wipe your phone in fastboot to access your storage again and you also need to flash latest su zip to disable dm verity. That should clear you internal memory issues and allow you to flash a zip through twrp
Good Luck
Sawdoctor